Who should take part from your side?
One decision maker, one person who knows the day-to-day work, and access to five or more intended users. More people are welcome but not required.
Home / Discovery
Discovery is the cheapest part of product development and the part most often skipped. This is what it involves, and what it produces.
Every product idea carries four kinds of risk. Value: will people choose to use it? Usability: can they work out how? Feasibility: can it be built with the time, skills and systems available? Viability: does it work for the business, including cost, support load and any legal constraints? Discovery tries to identify which of these is largest for your idea and to test that one first.
This happens, and it is not a failure. Finding out in four weeks that customers will not change their habit is far better than finding out after a six-month build. We will present the evidence plainly and, where we can, suggest what else might work.
It cannot guarantee success. It reduces uncertainty; it does not remove it. Some answers only arrive when real people use real software in their own context, which is why our releases are small and our learning continues after launch.
One decision maker, one person who knows the day-to-day work, and access to five or more intended users. More people are welcome but not required.
If the problem, users and scope are already well evidenced, discovery can be short. We will look at what you have and tell you honestly.
Rarely, and never at the start. Discovery works with conversations and sketches. If data is needed later, we agree a lawful, minimal approach first.
Yes. The brief, sketches and scope are written to be handed to any competent developer.