Find the real need.
Look at the current experience, the alternatives and the friction. Turn a broad ambition into a problem someone can recognise.
There is a difference between an idea that sounds good and a product that helps someone. We work in the space between the two.
Look at the current experience, the alternatives and the friction. Turn a broad ambition into a problem someone can recognise.
Explore the central interaction before committing to every feature. A focused prototype can surface the questions a document misses.
Connect the design, the application rules and the technical foundations. Keep the purpose visible as the detail grows.
Ask what needs to change, who benefits and why the proposed approach is the right one. A clear challenge is more useful than a long feature list.
Keep the smallest experience that can demonstrate the core value. Define what has deliberately been left for a later conversation.
Put the working interaction in front of the people it is for. Use their questions and behaviour to sharpen the next decision.
Record the evidence behind a change. Give the team a shared view of what was tested, what was learned and what remains uncertain.
A well-considered application earns its place by making a task clearer, a process simpler or a decision easier to take.
Prepare a starting briefDescribe who the product is for, what they are trying to do and what gets in the way today. Bring examples, constraints and the questions you have not answered yet.