The playbook
Website Redesign: Template and Field Guide
This website redesign template turns a broad task into a record another person can use. It captures current issue, new solution, URL impact, 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
Inventory current landing URLs and working inquiries before replacing templates. Keep a record of old-to-new destinations and important content decisions. Test the redesigned user journeys with actual copy and routing before moving the public site.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| current issue | Record the current issue associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| new solution | Record the new solution associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| URL impact | Record the URL impact associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| test | Record the test 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 current issue. Use the same reference throughout the record so notes are not attached to the wrong item. Then identify the specific problems a redesign must solve. This establishes the information required before the worksheet becomes a request for action.
Next, inventory pages functionality and search-sensitive URLs. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as changing navigation URLs and messaging without a migration plan, rather than a broad instruction to “improve performance.”
Finally, test the new experience before replacing the old one. Put track changes and map important journeys and destinations 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 | Changing navigation URLs and messaging without a migration plan |
| Action | Track changes and map important journeys and destinations |
| First check | Identify the specific problems a redesign must solve |
| Follow-up check | Test the new experience before replacing the old one |
| Outcome to define | priority redesign goals achieved |
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 new solution 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 priority redesign goals achieved 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