A click dummy — also called a clickable prototype or HTML prototype — is a linked set of static screens that simulate the navigation and interaction of a digital product without containing any real functionality. Clicking a button takes you to the next screen; clicking back takes you to the previous one. It is the minimum viable interactive prototype: enough to test navigation flow and screen structure with real users, but fast and cheap to produce because nothing behind the interface actually works.
What It Is
Click dummies sit between wireframes and fully functional prototypes in the fidelity spectrum. They can be built in tools like Figma, Axure, Marvel, or InVision by linking hotspot areas on each screen to the next screen in the intended flow. They simulate the feel of using the product without requiring any coding. Their value lies in being just real enough for users to suspend disbelief and behave as they would with an actual product.
How to Run It
- Design the key screens for the flow you want to test — focus on the most critical user journey, not every possible state.
- Link interactive areas (buttons, navigation items, form fields) to the appropriate next screens.
- Add just enough visual design to communicate hierarchy and intent without investing full production time.
- Run usability test sessions using the click dummy: give participants realistic tasks and observe where navigation breaks down.
- Note every moment of hesitation, wrong turn, or confusion — these are your primary findings.
- Iterate the click dummy based on test findings before advancing to higher-fidelity or coded prototypes.
When to Use It
Click dummies are most valuable during the early-to-mid design phase when the navigation structure and screen hierarchy need to be validated with users before visual design work begins. They are particularly effective for testing complex information architectures, multi-step flows, and applications with many navigational paths. Use them when the investment in a fully coded prototype cannot be justified until the structural approach has been validated.
Tips for Success
- Link only the screens necessary for the test tasks — a click dummy that covers every edge case takes as long to build as the real product.
- Use realistic content rather than placeholder text: users make navigation decisions based on content, not layout.
- Test on the actual device type the product is designed for: mobile prototypes tested on desktop and vice versa produce unreliable navigation findings.
- Capture misclicks as carefully as successful navigation: they reveal which interface elements are generating incorrect affordances.
