KEY TAKEAWAYS
Start here.
- Define journeys before counting screens.
- Give prototype reviews specific questions.
- Handoff needs behavior and states.
Start with the decisions
UI/UX work should clarify user journeys, information, and interface behavior. A startup may need a first-product prototype; an enterprise may need shared patterns across legacy systems. Define the decisions, constraints, and journeys before buying a screen count.
Review six deliverable areas
For each area, agree on coverage, fidelity, client inputs, and review method.
| Area | Artifact | Question |
|---|---|---|
| Discovery | Brief and constraints | Who is this for? |
| Structure | Flows and hierarchy | How is the task completed? |
| Exploration | Prototype | Which assumptions need testing? |
| Interface | Layouts and states | How does it work and look? |
| Foundations | Components and styles | What stays consistent? |
| Handoff | Files and behavior notes | What must engineering build? |
Make prototype reviews purposeful
An account-setup prototype might test whether people understand requested information, recover from errors, and recognize completion. Stakeholder approval and user testing answer different questions; a visual review does not prove usability for every audience.
If user participants must be recruited, include access, permissions, scheduling, and recruitment responsibilities in the agreement.
- List the decisions the prototype informs.
- Use realistic content and task sequences.
- Name reviewers, participants, and review methods.
- Record findings and unresolved questions.
Cover states and engineering handoff
Specify relevant loading, empty, error, validation, disabled, success, and permission states. Include responsive behavior and keyboard interaction. Reuse existing enterprise foundations where appropriate; a new product can start with typography, spacing, controls, and repeated patterns.
A proposal should specify the journeys, responsive breakpoints, relevant screen states, and review rounds. Avoid assuming a prototype includes every production behavior. Involve engineering before approval so technical constraints are resolved while changes are still easy to make.
Agree on source files, assets, naming, behavior notes, and implementation reviews. Identify final and illustrative work. Recruitment, extensive research, brand work, and specialist accessibility audits need explicit scope.
Bring your product, audience, priority journey, brand assets, and technical constraints to Unanimous. We can define reviewable design deliverables and a practical handoff into development.