A prototype should support a decision
Before designing screens, record what remains uncertain about the application. Does a coordinator understand the proposed job states? Can sales prepare a quote without a colleague's help? Does a handover show what the next person needs? These questions determine what the prototype should demonstrate.
A clickable prototype is an interface model for walking through a prepared scenario. Its business value lies in decisions made before implementation. Without a specific question, it can become an attractive presentation without a clear next step.
Choose one workflow and define its boundaries
Start with a case from input to outcome. A service request might cover receipt, missing information, technician assignment, and handover. For each step, define who acts, what evidence they have, and what they need before deciding.
You do not need to draw an entire ERP immediately. Include screens that address the selected uncertainty and identify shortcuts. If login, customer selection, or a calculation is skipped, record that limitation so the handover explains what participants actually tried.
Give participants a goal rather than clicking instructions
Invite actual or likely users of the workflow. Set a clear task without revealing its solution. Observe where people pause and where their interpretation differs from the design.
In our model scenario, a task might be: 'A customer needs a visit this week. Find a suitable technician and prepare the assignment.' Telling someone to open the Technician tab and click Assign would reveal the answer. Separate what participants say, what they do, and when they need help in your notes.
Include an incomplete case
Show a situation with missing information or an unavailable option: no suitable appointment, an incomplete address, or a case that needs returning to a colleague. This helps the business clarify the decision and information required at that point.
For each branch, record what users should understand and what they can do next. You do not need to model every possible system error. Select exceptions that affect the core workflow and keep the rest as open questions.
- Is the missing information and its owner clear?
- Can users distinguish a draft from a handed-over case?
- Do they understand confirmation and cancellation?
- Can the task be completed under the agreed exception?
Clickability does not prove technical readiness
Showing an available appointment or price does not establish that existing systems can supply those values. At handover, identify illustrative data, simulated rules, and steps prepared only for the selected scenario.
The technical team must separately investigate availability sources, integrations, access rules, and concurrent updates. A technical uncertainty may require a separate proof of concept or integration test. Interface testing should not be presented as evidence of a finished application's performance or security.
Translate findings into specific brief updates
After testing, list observations and decisions. For each, record the affected task, problem, proposed change, and decision owner. Distinguish button wording, missing business rules, and technical questions: their next steps differ.
If a participant could not tell whether a case was handed over, 'improve UX' is insufficient. Specify the status information required and how the next version will be checked. Prepared task findings do not prove that the entire product or every user group has been validated.
Agree the deliverables before prototyping
Deliverables can include the current prototype link, tested flows, limitations, and decisions for the first release. Add open questions and responsibility for resolving them. This helps developers understand the reasons behind the design as well as its appearance.
If you are planning an application or changing an internal workflow, bring one uncertainty and a concrete work task to a consultation. At DAVOND, we can review whether interface design, a clickable prototype, or technical investigation best addresses it and use that to scope the next step.