Purpose Before Polish: Give Every Page One Job
Use a page job card to decide what a visitor should understand and do before the layout starts showing off.
Start with the moment where the interface asks too much.
The redesign review starts well. The page is handsome. The type is large, the animation is smooth, the mockups look expensive, and every stakeholder can point to something they asked for. Then three people are asked a simple question: what is this page trying to get a visitor to do? One says book a call. One says understand the service. One says subscribe to the newsletter. Nobody is wrong. That is the problem. The page has become a negotiation record instead of a decision path.
A page cannot have clear hierarchy, useful proof, or meaningful measurement until the team agrees what job the page is doing for one visitor in one moment.
Show the failure and the correction.
The lab uses controlled markup instead of raster text so the lesson stays legible, accessible, and easy to revise.
- A visitor arrives with one questionThe visitor has to decide the page purpose before they can decide whether the offer fits.
- Stakeholders add reasonable asksReasonable additions accumulate into strategic ambiguity.
- Polish hides disagreementThe team approves a beautiful page with no measurable job.
- The page job gets writtenCopy, proof, hierarchy, and measurement point at the same outcome.
Name the visitor state
Start the page around the person most likely to arrive there and the question they are trying to resolve.
Make the useful path easier.
The page job card
Write: this page helps this person understand this decision-relevant value and take this next useful action. Then add arrival context, required proof, success signal, and explicit non-jobs. Non-jobs are not hostility toward other teams; they are protection from accidental page sprawl.
Purpose makes measurement honest
A vague goal produces vague reporting. If the job is a qualified inquiry, measure inquiry quality and completion friction. If the job is education, measure comprehension and the next helpful step. Time on page is not useful until the page has a named job.
One job does not mean one element
A page can contain story, proof, detail, and objections. The question is whether those parts help the same decision. A homepage may introduce several paths, but it still needs a dominant visitor state and a clear order of importance.
Turn critique into a usable rule.
Remove
Five equal CTAs
The hypothetical homepage asks a new visitor to book, subscribe, watch, browse, and download before it explains why any of those actions matter.
Proof without a decision
A testimonial, metric, or screenshot appears impressive but does not answer the doubt that blocks the primary action.
Content with no non-jobs
Recruiting language, investor language, support language, and sales language all appear in the first screen because nobody named what the page should not do.
Build
Name the visitor state
Start the page around the person most likely to arrive there and the question they are trying to resolve.
Move proof next to the decision
Use proof only where it answers a real doubt: capability, fit, risk, timing, price, process, or trust.
Let secondary actions support the path
Secondary links can exist, but they should feel like useful side doors, not rival exits.
Use it on a real page.
Show the page to three people who did not attend the design review.
Give them five seconds with the page.
Ask what the page is, who it is for, and what they would do next.
Compare their answers with the written page job card.
Record the misunderstanding before changing copy or visuals.
- Use notes from the three answers, not team opinions about how clear the page feels.
- The answers converge on the intended offer, audience, and next action.
- People name different jobs, choose rival CTAs, or cannot explain why the next step matters.
The rule should help the person making the next decision.
Business owner
Decide which visitor and outcome matter most for this page before asking for more sections.
Designer
Use the page job card as the hierarchy brief. Visual weight should reveal the chosen job.
Developer
Keep CTA destinations, analytics attributes, and success states aligned with the same primary action.
Reviewer
Ask what the page is not responsible for. A missing non-job is often where scope creep enters.
Complex product, dashboard, and marketplace pages may support several tasks. The rule bends into priority by user state, not artificial reduction to one button.
Check the page, then answer the doubt.
- The page job can be written in one sentence.
- The primary visitor is named.
- The main doubt is answered before the action.
- Secondary CTAs are visibly secondary.
- Every section supports the same decision.
- Non-jobs are documented.
- Analytics match the stated success signal.
- Can a page have more than one CTA?
- Yes. It should not have more than one primary job competing for the same visitor state.
- Is a homepage’s job always conversion?
- No. A homepage may orient, segment, reassure, and route. Conversion is only useful when the visitor is ready for it.
- What if stakeholders want different outcomes?
- Write the non-jobs and route secondary needs to better surfaces instead of forcing every goal into the hero.
Standards and research links support the factual parts of the rule. They do not replace original judgment on the page.
Use the rule on the page that matters.
Use this when the reader is ready to inspect their own page before asking for a rebuild.
Get the conversion checklist