The playbook
Homepage Design: Template and Field Guide
This homepage design template turns a broad task into a record another person can use. It captures section, message, proof, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
A visitor should quickly understand who the offer serves, what it does, and where to go next. Use a real product view or specific project evidence where it explains the offering. Keep secondary audiences navigable without giving every section a competing primary button.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| section | Record the section associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| message | Record the message associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| proof | Record the proof associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| destination | Record the destination associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with section. Use the same reference throughout the record so notes are not attached to the wrong item. Then explain the offer and intended audience near the top. This establishes the information required before the worksheet becomes a request for action.
Next, show credible proof and major service paths. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as giving every section an equally prominent competing action, rather than a broad instruction to “improve performance.”
Finally, keep the main action visually clear on mobile. Put create a clear primary path and useful secondary navigation in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Giving every section an equally prominent competing action |
| Action | Create a clear primary path and useful secondary navigation |
| First check | Explain the offer and intended audience near the top |
| Follow-up check | Keep the main action visually clear on mobile |
| Outcome to define | qualified onward journeys |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If message changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep qualified onward journeys connected to the item so the team can later assess whether the action was useful.
Treat visual changes and functional changes separately in the change log. A clearer label may improve comprehension, but a broken submission destination still prevents completion. Confirm both understanding and successful delivery.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now