Responsive Design
Can the intended user understand the next action and recover when the journey is interrupted? Prioritise content and interaction at constrained widths rather than merely shrinking the desktop composition.
What You Will Be Able to Decide
- Explain responsive design in product and business terms.
- Apply this decision: Prioritise content and interaction at constrained widths rather than merely shrinking the desktop composition.
- Recognise this material risk: important actions become hidden, crowded, or unusable on the devices customers actually use.
- Use this review: Walk through one client approval on a phone with a missing file, a validation error, and a successful submission.
A founder is reviewing an interface before development effort makes its structure expensive to change. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
Can the intended user understand the next action and recover when the journey is interrupted? The course example is A client portal where a small agency collects project approvals; use it to decide what evidence would justify the choice before a builder implements it.
What Does Responsive Design Mean for Your Product?
A founder is reviewing an interface before development effort makes its structure expensive to change.
Use the illustrative service for this course (A client portal where a small agency collects project approvals) to make the choice concrete. Can the intended user understand the next action and recover when the journey is interrupted?
Technical term
Responsive Design
Responsive design adapts content, controls, and layout to different viewport sizes and input conditions without losing meaning or function.
How Should a Founder Use Responsive Design?
For a client portal where a small agency collects project approvals, ask what would happen if important actions become hidden, crowded, or unusable on the devices customers actually use.
For this decision, the useful standard is that a representative user can understand the next action and recover when the interface changes state.
- Decision: Prioritise content and interaction at constrained widths rather than merely shrinking the desktop composition.
- Evidence to request: show that a representative user can understand the next action and recover when the interface changes state.
- Owner: name who will respond if important actions become hidden, crowded, or unusable on the devices customers actually use.
- Record the result in the user flow, wireframes, and interface review.
- Practical review: Walk through one client approval on a phone with a missing file, a validation error, and a successful submission.
How Do You Choose an Approach to Responsive Design?
Can the intended user understand the next action and recover when the journey is interrupted? Prioritise content and interaction at constrained widths rather than merely shrinking the desktop composition.
The risk is that important actions become hidden, crowded, or unusable on the devices customers actually use. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Responsive Design?
What Warning Signs Should You Look For?
- The proposal does not address this risk: important actions become hidden, crowded, or unusable on the devices customers actually use.
- Nobody can show whether a representative user can understand the next action and recover when the interface changes state.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to responsive design?
- How have we reduced or accepted this risk: important actions become hidden, crowded, or unusable on the devices customers actually use.
- Can you demonstrate that a representative user can understand the next action and recover when the interface changes state?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Prioritise content and interaction at constrained widths rather than merely shrinking the desktop composition. Ask for evidence against the specific risk: important actions become hidden, crowded, or unusable on the devices customers actually use.