Discovery Workshop
Turn an early software idea into a useful delivery brief by agreeing the problem, users, constraints and first-release priorities.
Planning your project
What should discovery resolve?
Discovery should distinguish the underlying operational problem from the first proposed solution. Map the current workflow, identify who makes decisions, and agree how success would be recognised. A workshop may conclude that configuring an existing tool is more suitable than a custom build.
Define a decision-ready brief
Useful outputs include prioritised user journeys, integration dependencies, key risks and a staged delivery proposal. Agree which outputs are included before the workshop. Estimates should state assumptions and unresolved questions rather than presenting uncertain scope as a fixed commitment.
Who should take part?
Include someone who performs the work, someone who owns the business outcome and someone who understands existing systems. Bring representative process examples without exposing customer information. Identify technical or regulatory constraints early so they inform the proposed solution.
Bring to your first conversation
- Your current process and the problem it creates
- The people who use, approve and maintain the system
- Known budget, timing, integration and compliance constraints
Discuss your project on a free discovery call