Do not index
Do not index
For context: In my experience, GTM stakeholders and managers usually skip over low-fidelity or mid-fidelity wireframes and only want to see high-fidelity ones. Because of that, I treat low-fi wireframes as part of my own process and don’t share them. But making changes to high-fi wireframes is so much more time-consuming.
Types of wireframes used in different review stages
Which types of wireframes to use depends on the purpose and who you’re sharing them with.
Here are a few examples:
1. Kickoff Meetings
Use low-fi wireframes to brainstorm with stakeholders.
They’re great for sparking ideas and imagining solutions together.
2. Developer Reviews
Low-fi or mid-fi wireframes work well here. Use them to discuss technical constraints, content types, flows, and IA.
Engineers can better visualise how things work, making their job easier.
3. User Testing
You will need hi-fi wireframes or mockups so they feel real enough for users to interact with.
If they look too rough, people might focus on the wrong things.
4. Client Presentations
If the client isn’t familiar with wireframes (most aren’t), go for hi-fi or full mockups—even at a concept stage.
Again, help those understand what you're trying to do, and set expectations upfront.
And there's plenty more examples of course.
You can always mix and match. Low-fi works for ideation and flows, while hi-fi is great for presenting concepts.
Read more about UX wireframe:
This framework is part of UX Playbook. Get shortcuts to a master of UX processes, for any projects, without expensive bootcamps.
