What it is
Structured reviews that iterate designs using usability findings, stakeholder input, and engineering feasibility, to reach an approved, development-ready state.
Why use it
Reviews at this stage surface feasibility limits, stakeholder concerns, and edge cases before development, reducing mid-sprint design changes.
Use this when
- Testing or stakeholder feedback calls for refinements
- Engineering must assess feasibility of specific decisions
- Final alignment is needed before handoff
You may not need this when
- Designs are approved and no significant feedback remains
- The change is minor and needs no engineering alignment
Dependencies — what you need
- Stakeholders available at key milestones
- Alignment with engineering on feasibility
- Time to iterate on feedback
People involved
- Design
- Product
- Engineering
- Stakeholders
Typical outputs
- Designs reviewed and approved by the team
- Resolved questions and feasibility decisions
- Updated specifications ready for development
Template
Implementation Design Reviews template
A fill-in structure for running this method: what to prepare, what to do, what to record, and how to read the result.
How AI can help
AI as augmentation — not replacement
- Generate a checklist of review criteria
- Identify edge cases the design may miss
- Draft documentation of decisions and rationale
- Suggest accessibility review points
AI prompt
A prompt for any AI assistant. It works only from material you paste in, keeps assumptions apart from findings, and leaves the decisions to you.