Business software · 5 min read
A good discovery workshop can tell you not to build anything at all
What a software discovery workshop should produce before you fund a full build.
The short answer
A software discovery workshop turns an unclear business problem into a testable project scope. You should leave with a mapped workflow, key risks, a prioritised first release and a defensible estimate. A good discovery workshop should make it possible to decide not to build at all, if that's the honest answer.
By Raja Wahab, Co-founder, Fixby Studios · Published · Updated · 5 min read
Bring the people who do the work
A manager may know the intended process while staff know the workarounds that actually happen. Include both in the software discovery workshop. If customers will use the system, collect their questions or observe a representative task with permission. Discovery based only on the owner's wish list can miss the friction that matters most.
Prepare a recent example from beginning to end, using anonymised records. Show the emails, spreadsheets and approvals actually involved, rather than relying on a memory of the ideal workflow.
Map the normal route and the exceptions
Start with the trigger: a new request, a completed job, or an approaching renewal. Identify the owner of each step and the condition that lets it move forward. Then examine rejections, cancellations, missing data and duplicate requests.
Mark each unknown explicitly. If the project depends on a third-party system accepting an update, test that capability early rather than assuming it exists.
Owner's wish list only
- — Misses real workarounds
- — Easy to run quickly
Staff and decision-maker together
- — Surfaces actual friction
- — Produces a mapped workflow
What a discovery workshop should produce
| Output | Why it matters |
|---|---|
| Current and proposed workflow | Shows what actually changes for users |
| Roles and access matrix | Makes information boundaries explicit |
| Risk and assumption log | Reveals what could alter the estimate |
| Prototype or technical test | Checks the most uncertain behaviour |
| Prioritised backlog | Separates launch needs from later ideas |
| Estimate with exclusions | Makes the next decision understandable |
“Bring the staff who actually do the work, not just the decision-maker.”
Avoid discovery that just produces more slides
A workshop isn't automatically valuable just because many people attended. Ask what uncertainty it actually removed. If a supplier knew nothing about your existing tools beforehand and still recommends the same package afterwards, ask for the evidence behind that recommendation.
A legitimate and useful outcome might be that your current software already supports the required workflow. That can save more than the discovery cost and is a valid reason to stop there.
Decide the next step
Review the outputs with the operational owner. Are the proposed benefits measurable? Are critical dependencies tested? Is the first release small enough to evaluate properly? If not, commission only the missing investigation, not the entire build.
How much a discovery workshop should cost
Treat discovery as a small, separately priced piece of work rather than a free sales exercise. A paid discovery phase gives the supplier room to be honest about risk, including telling you that a cheaper option exists. A free workshop more often leads straight to the supplier's preferred solution.
Sources
Your questions
- What is a software discovery workshop?
- A short structured exercise that turns an unclear business problem into a testable scope, usually producing a mapped workflow, a risk log and a prioritised first release.
- Who should attend a software discovery workshop?
- The decision-maker and the staff who actually do the work day to day. Staff often know the real workarounds that matter most to the project's success.
- Can discovery conclude that I shouldn't build software?
- Yes, and that's a legitimate outcome. If your existing tools already support the workflow, discovery has done its job by saving you the build cost.
- How long does a software discovery workshop take?
- It varies with complexity, but most small business discovery exercises take from a few days to a couple of weeks, including follow-up documentation.
Raja Wahab is co-founder of Fixby Studios, a Huddersfield studio building websites, SEO, social media and business software for small, owner-managed businesses across West Yorkshire.
Next step
Let's get your business seen.
A free plan to replace spreadsheets and WhatsApp with one system.
Tell us which task takes too much time and we'll assess a focused software or automation project. Business automation and software
Prefer to talk it through? Contact Fixby Studios, email info@fixbystudios.co.uk or call 07737 067552.
