The practical answer
Review structure and information in a wireframe, proposed interactions in a prototype and actual behaviour in the implemented website. Ask what each version includes and excludes so you do not approve a visual demonstration as proof that payments, data or permissions work.
A designer sends a clickable link. You click through a registration flow and see a confirmation screen. It feels like the website is nearly finished.
But the link may be a prototype with no real registration system behind it. The confirmation may be a designed screen rather than evidence that a record was saved, a payment was verified or an email was sent.
Knowing whether you are reviewing a wireframe, prototype or finished website helps you give useful feedback and avoid approving the wrong thing. It is an important part of UI/UX and product design.
Use a wireframe to review structure
A wireframe is an early representation of layout, content hierarchy and functionality. It may be a sketch or a more organised screen outline. Its level of detail varies.
Review what appears on the page, what matters most and how a person would find the next step. Ask whether the layout supports the task and whether any essential information is missing.
Avoid spending the entire wireframe review debating the exact shade of a button. Visual style can matter later, but the early opportunity is to correct structure before the team invests heavily in detail.
Use a prototype to explore behaviour
A prototype represents an interaction or proposed flow at a chosen level of realism. It may allow people to click between screens, open a menu or move through a process.
Ask which behaviours are simulated. Can the prototype handle different answers, errors and a return visit, or does it only demonstrate one prepared route? Both can be useful, but they answer different questions.
Nielsen Norman Group distinguishes wireframes from prototypes in its design-deliverables guidance. The practical lesson for a project owner is to ask what the version is intended to demonstrate before judging it.
Review the implemented website for actual behaviour
A built website connects the interface to real content, application logic and any agreed external services. This is where you test the things that a prototype may only suggest.
Can a valid enquiry reach the business? Does an invalid form show a helpful error? Can an authorised person access the right records? Does a payment status reflect a verified transaction rather than a demonstration label?
Use agreed test conditions and test accounts where needed. Do not test a live financial process or send real applicant information casually simply because a screen appears ready.
| Stage | A useful focus | What approval does not establish |
|---|---|---|
| Wireframe | Structure, content order and task support | Final appearance or working integrations |
| Prototype | Proposed navigation and interaction | Production reliability or actual data handling |
| Visual design | Detailed interface presentation | A complete, tested implementation |
| Implemented website | Real behaviour against requirements | That every future situation has been covered |
Confirm which stage the team is presenting and keep the approval record specific to that stage.
Bring realistic content into the review
Short placeholder labels can make a layout appear easier than it will be. Test meaningful page titles, actual service descriptions and representative data lengths.
Include a long name, an empty result and a message that needs explanation. A dashboard with three perfect example rows may not show what happens when the user has no records or many records.
Use fictional or appropriately prepared test data. The objective is realistic variation, not exposing private information in a design tool or presentation.
Review a phone-sized journey early
Do not assume that a wide desktop design will automatically become a good mobile experience. Important information may move, tables may become difficult and actions may be pushed far down the page.
Ask to review the priority journey at the sizes relevant to the audience. Check reading order, field labels and the visibility of the next action. Include a small-screen review before every structural decision is treated as settled.
In the built version, test on actual supported devices as well as responsive previews. Simulated size and real device behaviour provide related but different evidence.
Write feedback as an observation and a question
Useful feedback identifies a specific difficulty: “I cannot tell whether this button saves progress or submits the application.” Then ask what the intended behaviour is.
Separate a new requirement from a correction to agreed work. Adding a new approval department is different from fixing a missing label. The team should record how the change affects scope and the next review.
Consolidate feedback through the agreed project owner. A scattered collection of messages can leave the designer uncertain about which instruction is current.
Keep a decision record between stages
Record what was approved, what remains unresolved and what depends on later testing. Use the version or date of the reviewed design so the team can refer to the same material.
An approval might say that the information structure is accepted while the error-handling approach remains under discussion. That is clearer than a general “approved” message that people later interpret differently.
Before development, check that the developer receives the relevant interaction notes and assets. Before launch, check the implementation against the agreed requirements rather than only against a screenshot.
Frequently asked questions
Should every project have all these stages?
Not necessarily. A small change may need a lighter process. The stages should resolve the uncertainty and risk in the actual work.
Can a prototype use real code?
Yes. Prototypes can take different forms. Ask about their purpose and limits rather than assuming that the tool or technology makes a version production-ready.
Does approving a design mean I cannot change anything later?
Changes can still be considered through the agreed process. Earlier approvals help the team understand which decisions are being reopened and what that means for time and cost.
Match the review to the evidence
A wireframe, prototype and live website each provide useful information. Review each for the questions it can answer, and keep the remaining implementation and testing work visible.
Further reading
Reference addresses are provided as plain text for copying.
https://www.nngroup.com/articles/ux-deliverables-glossary/https://www.nngroup.com/articles/parallel-and-iterative-design/
Discuss your next step
Need help reviewing a design before development? Share the screens, the intended user journey and the decisions you are being asked to approve. I can help make the review more focused.





