How to decide what to build with product discovery and design
Use a workshop, prototype and representative tasks to decide what to build and give designers and developers shared evidence.
Photo unavailableGive a test participant a real goal and observe where they hesitate without explaining each step.
Choose the decision the project needs to make
A useful product project starts with evidence about the people using it and the work they need to complete. Attractive screens are valuable when they help that work happen. They are less useful when the project has not yet established which problem deserves investment.
Product discovery, user experience design and interface design support different decisions. A proposal should explain which question each activity will answer.
Read the source: GOV.UK: How the discovery phase works.
Start with a specific uncertainty
A product discovery workshop can bring together what the business knows, what users experience and what remains assumed. Decide whether the workshop should help you commit to a build, choose a user journey or change a process.
GOV.UK's service guidance describes understanding the problem, users and constraints before committing to construction. Use that sequence to check whether the problem and constraints are clear enough to choose a first project.
Study the complete journey
Look at how people begin the task, where information comes from and what happens after the software step. Include the colleagues and offline work involved. A fast interface can still leave a slow approval or an unclear handover.
UI UX design services should distinguish the interaction from its appearance. User experience concerns whether the person can accomplish the task. Interface design concerns how the controls and information support it. Both should reflect the actual users and devices.
Prototype the difficult decision
Software prototyping services should make an important assumption testable. That may mean a simple sequence of screens, an interactive model or a limited working experiment. Agree what the prototype can demonstrate and what would still require production engineering.
For an illustrative test, ask a new user to submit a request, correct a mistake and find its current status. Observe where they hesitate and what they expect to happen next. Give the person a goal and see what they can complete without prompting.
Use research to change the design
Usability testing services should specify the participants, tasks and questions being investigated. Record findings in terms the team can act on, with the evidence and any limits of the sample.
A product design agency should show how those findings affect the next version. Ask which problems were resolved, which remain open and what another test would establish. A presentation of research is useful when it changes a decision.
Make consistency maintainable
Design system development creates shared patterns and rules for the interface. Scope it around the product's actual needs, including empty, loading, error and permission states. Decide who can add or change a pattern and how developers use it.
The handover should connect screens to behavior, content and acceptance examples. Keep ownership of the research, design files and decisions clear so the next build team can continue the work.
AI App Studio can help test a product need and design a useful first version. Book a call with the users, bottleneck and decision you need to make.
Sources and further reading.
Our perspective is based on these sources. Product details and availability can change after publication.
Last updated .
Ready-made skills for work like this.
Skills teach Claude or Codex to do a job the same way every time. Pay once, download straight away, and keep it.
Browse the store
