A design review works better when everyone knows what decision they are being asked to make. Opening with a tour of every screen often produces scattered reactions. Start with the problem and the evidence instead.
Use a simple story
- Context: who is trying to do what, and why it matters.
- Evidence: what you observed and what remains uncertain.
- Options: the approaches you explored and their tradeoffs.
- Recommendation: what you propose and why.
- Ask: the decision, feedback, or help needed now.
Show enough to make the choice real
A short flow or prototype can communicate more than twenty isolated screens. Include the moment where the tradeoff becomes visible. Explain relevant constraints and label untested assumptions.
Direct the feedback
Ask “Does this address the problem we agreed to solve?” or “Which risk should we test next?” If you need feedback on information hierarchy, say so. Capture unrelated issues without allowing them to take over the meeting.
Close with ownership
Summarize the decision, unresolved questions, next action, and owner. Write it down in a shared decision log. If disagreement remains, identify what evidence could resolve it and who will gather it.
Carry the same logic into a portfolio
Show your actual contribution and the constraints you worked within. Explain changes in your thinking. Separate measured results from expected benefits, and label conceptual work honestly. A thoughtful account of an uncertain problem is more credible than a flawless-looking story with invented outcomes.
Try it yourself
Prepare a five-slide review using context, evidence, options, recommendation, and ask. Remove any slide that does not help someone make the decision.