The homepage is where organizational compromise goes to live. A department wants its service named. A partner wants a logo. Sales wants a button. Human resources wants the careers message. Leadership wants the history. Everyone has a reasonable request, and the visitor gets a page that asks them to assemble the business for themselves.
A homepage needs one primary job. Usually, that job is to help the right visitor understand where they are, why the business may matter, and what conversation should happen next. It can point to other work without making every visitor carry the whole company at once.
The first draft should be written for a real person in a real moment. Are they checking whether you understand their problem? Looking for proof? Trying to decide whether to call? The answer changes the order of the page. It also tells you which internal requests belong somewhere else.
I have found that the kindest way to handle the group project is to give every team a place in the larger system, then protect the front door. The homepage does not need to say everything. It needs to make the next step feel sensible.
If the page is trying to keep everyone happy, ask whether it is helping anyone choose. That question tends to clear a little room.
- Give the homepage one primary job and one primary reader.
- Move useful secondary information to pages where it can breathe.
- Judge internal requests by whether they help the visitor make a decision.