How do you decide what goes above the fold when everything feels important?

Decide by the page’s one job, and let only what serves that job stay above the fold. The method is a ranking, not a fitting exercise, and it starts by refusing the framing that everything is important. On any given page a first-time visitor is making exactly one decision, am I in the right place, and what do I do next, and the top of the page exists to answer that and almost nothing else. So the question is not “how much can we cram up here?” but “what is the single thing this page is for, and what does a stranger need to act on it?” Everything that does not serve that single job, however much a stakeholder loves it, ranks below the fold by default. The hard part is not finding space; it is naming the job clearly enough that the ranking becomes obvious.

The reason this method beats cramming is that the fold is not a container to be filled, it is a moment of orientation, and orientation fails when it is crowded. A visitor lands cold, with no context and a few seconds of patience, and what they need is fast confirmation that this page matches their intent plus a clear next move. Pile six competing priorities into that moment and you have not given them more, you have given them a decision they cannot make, because the more you put above the fold the less any single thing reads. “Fit as much as possible” treats attention as additive when it is subtractive: every extra element you fight up top dilutes the orientation the fold is supposed to provide. Ranking by the one job protects that moment by ensuring the first thing the visitor sees is the thing the page actually needs them to grasp.

In practice the disagreement is usually a meeting, not a design problem. Imagine a product page where marketing wants the seasonal promo banner, sales wants the demo request form, the founder wants the press logos, and content wants the explainer video, all above the fold, all “essential.” The cram-it-in instinct gives each a slice and produces a top section that says nothing clearly. The job-first method asks one question: what is the single decision a first-time visitor makes on this page? If the answer is “understand what this product does and start a trial,” then the above-the-fold ranking writes itself, a headline that states the value, one supporting line, and the trial button, with the promo, the press logos, and the video all moving just below where they support the decision without competing for the orientation moment. The other priorities are not deleted, they are ranked, and ranking is what cramming refuses to do.

The edge case is the page whose one job genuinely is a menu. A homepage for a large organization, or a hub that exists to route visitors to many destinations, may legitimately need several entry points up top, because routing is its single job and a clear set of paths is the orientation. There the method still holds, you are still ranking by the page’s one job, it is only that the job is “send people to the right place,” so a small, well-ordered set of primary routes is the correct above-the-fold content rather than a single action. What stays forbidden even here is the unranked pile; even a routing page picks its few primary paths and demotes the rest.

So before you lay out the top of any page, write one sentence naming the single decision a first-time visitor makes there, then hold every candidate element against it and keep only what helps them make that decision. Let the page’s one job do the cutting for you, and the fold stops being a fight over space and becomes a clear, confident answer to the only question a stranger is actually asking.