A product discovery sprint earns its place when it changes a decision. If a team leaves with a polished deck and still cannot tell which assumption could sink the release, it has more work to do. A useful sprint links a business goal to a workflow, a test and a decision owner.
Build the product discovery sprint around evidence
Bring one sponsor, one operator and the owner of each critical dependency. Start with actual tasks from the last working week. Record the trigger, the handoff, where staff re-enter data and what they do when a step fails. For an Egyptian company with branches, compare the head office’s documented process with the branch workaround.
Test the assumption with the biggest consequence
If the product depends on live stock, request a sample export or test API access. If adoption is the risk, put a prototype in front of the operator who would use it during a busy shift. Agree on what would lead you to proceed, narrow the scope or stop. Log who will make that call.
Leave with a decision pack
The pack should include a workflow map, a prioritized MVP backlog, explicit exclusions, an architecture option, risk owners and an estimate range with assumptions. Add observable acceptance criteria. For example, a branch employee can submit a request on a shared device, and a supervisor can trace the approval without calling the branch.
Anonymized scenario: a retailer’s inventory pilot
A hypothetical retailer asks for real-time inventory across every branch. Its existing exports are generated at closing time. Discovery finds that a click-and-collect pilot can start with items physically confirmed by one branch. The wider promise stays out of scope until the data feed is tested.
FAQ
How is discovery different from a requirements meeting?
Discovery tests the assumptions in the requirements and records decisions that change what gets built.
Can we start with existing documentation?
Yes. Bring it alongside transaction samples and access to a user who can show where the written procedure diverges from practice.
Define the first decision
Ask Code Tank to scope a discovery sprint around the highest-risk workflow and the evidence your sponsor needs to approve a pilot.
