Run a product feasibility walkthrough before commitment
Resolve, isolate, or stop for the dependencies most likely to invalidate the shaped solution.
- Preparation
- A cross-functional walkthrough plus bounded specialist checks.
- Steps
- 3
- Difficulty
- Advanced
- Task
- Check feasibility before commitment
Requires: Bring the shaped solution, complete user path, product boundary, and evidence already collected. Invite qualified reviewers for the technical, design, operational, contractual, legal, or regulatory risks that apply.
Uses: GitHub
Back to the Task: Check feasibility before commitmentBefore you start
Prepare
- Bring the shaped solution, complete user path, product boundary, and evidence already collected.
- Invite qualified reviewers for the technical, design, operational, contractual, legal, or regulatory risks that apply.
Steps
Work through the method
Use the listed inputs and tools. Check the evidence when you need to verify a step.
Walk through the product path
Move through the path from start to finish. At each step, ask what must be true for the user, system, organisation, supplier, and governing rules.
Step details and sources
Why it matters: A use-case walkthrough exposes assumptions hidden by a static feature list.
- Input
- The shaped solution, user path, and known constraints.
- Output
- A dependency list linked to each point in the product path.
Tools in this stepGitHubEvidence for this step
Basecamp describes walking through a use case, checking technical assumptions, cutting optional scope, and consulting technical experts before commitment.
Basecamp: Look for rabbit holes; Case study: Patching a hole; Present to technical expertsThe method does not guarantee that every design, legal, contractual, or technical risk will be found.
Isolate the critical dependencies
Mark dependencies that could invalidate the concept or break its boundary. Ask a qualified reviewer to define the evidence or bounded spike needed for each one.
Step details and sources
Why it matters: Critical uncertainty needs an owner and decision path before commitment.
- Input
- The dependency list and specialist review.
- Output
- A short set of critical risks with owners and evidence needs.
Tools in this stepGitHubEvidence for this step
Basecamp describes walking through a use case, checking technical assumptions, cutting optional scope, and consulting technical experts before commitment.
Basecamp: Look for rabbit holes; Case study: Patching a hole; Present to technical expertsThe method does not guarantee that every design, legal, contractual, or technical risk will be found.
Record resolve, isolate, or stop decisions
Create an issue for each approved check and record known blocked-by relationships. Resolve the risk, isolate it within the boundary, or stop the product decision.
Step details and sources
Why it matters: A recorded dependency can prevent a known risk from disappearing inside committed work.
- Input
- The critical risk set and approved checks.
- Output
- A feasibility decision with evidence, bounded spikes, dependencies, and stop reasons.
Tools in this stepGitHubEvidence for this step
Basecamp describes walking through a use case, checking technical assumptions, cutting optional scope, and consulting technical experts before commitment.
Basecamp: Look for rabbit holes; Case study: Patching a hole; Present to technical expertsThe method does not guarantee that every design, legal, contractual, or technical risk will be found.GitHub issues can record blocked-by and blocking relationships for known dependencies.
GitHub Docs: Marking an issue as blocked by, or blocking, another issueThe relation does not discover unknown dependencies or validate feasibility.
Success checks
Check the result
- Every critical dependency has evidence, a bounded check, or a stop decision.
- Qualified reviewers own risks outside the core team’s competence.
- Known blocking relationships are visible before commitment.
Failure modes
What could go wrong
- Do not treat the checklist as complete risk discovery.
- Stop when a legal, safety, or contractual dependency lacks qualified review.
- Re-shape the solution when a required check exceeds the investment boundary.
Tools
Choose tools
GitHub
An issue workspace for recording a software release boundary, milestone, and known dependencies.
Check fit, limits and pricingSources
Check the sources
Check what each source supports and where the advice has limits.
- Basecamp: Risks and Rabbit HolesFirst-hand company account and practitioner method · Publication date unavailable
- GOV.UK Service Manual: How the alpha phase worksPublic-service method guidance · Publication date unavailable
- GitHub Docs: Creating issue dependenciesOfficial product documentation · Publication date unavailable