The playbook
Responsive Web Design: Template and Field Guide
This responsive web design template turns a broad task into a record another person can use. It captures component, viewport, overflow, 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
Test long service names, validation messages, tables, and real images at narrow widths. Prefer reflowing columns to shrinking text. A horizontally scrollable data table can be appropriate, but the rest of the page should remain readable and controllable.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| component | Record the component associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| viewport | Record the viewport associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| overflow | Record the overflow associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| interaction | Record the interaction 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 component. Use the same reference throughout the record so notes are not attached to the wrong item. Then define flexible layouts and sensible content priorities. This establishes the information required before the worksheet becomes a request for action.
Next, test long text media forms and navigation at narrow widths. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as shrinking a desktop layout until text and controls become unusable, rather than a broad instruction to “improve performance.”
Finally, check touch targets zoom and overflow. Put reflow content and change composition when space is limited 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 | Shrinking a desktop layout until text and controls become unusable |
| Action | Reflow content and change composition when space is limited |
| First check | Define flexible layouts and sensible content priorities |
| Follow-up check | Check touch targets zoom and overflow |
| Outcome to define | responsive tasks completed without obstruction |
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 viewport 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 responsive tasks completed without obstruction connected to the item so the team can later assess whether the action was useful.
Use realistic content lengths and assets during review. Short placeholder headings can conceal overflow and hierarchy problems that appear with real service names, prices, or instructions. Check the result after the final content is inserted.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now