Product Task

Check feasibility before commitment

A shaped solution looks coherent, but an unresolved design, technical, contractual, or regulatory dependency could invalidate it.

“This could consume scarce team capacity if a critical assumption fails after commitment.”

Outcome

The result to aim for

Answer, isolate, or stop for each critical dependency before the build receives commitment.

Best practices

  • Bring the shaped solution, complete user path, product boundary, and evidence already collected.
  • Move through the path from start to finish; then at each step, ask what must be true for the user, system, organisation, supplier, and governing rules.
  • Create an issue for each approved check and record known blocked-by relationships; then resolve the risk, isolate it within the boundary, or stop the product decision.
  • Confirm that every critical dependency has evidence, a bounded check, or a stop decision.
  • Stop when a legal, safety, or contractual dependency lacks qualified review.

Related sources

Further information

Edited by MarioReviewed 27 September 2026