Business Viability Stakeholder Testing

When to Use

Apply this skill when your product discovery risk assessment has flagged business viability as Medium or High risk. This means the proposed solution may conflict with the constraints of internal functions that have power to block launch.

This skill produces a structured viability sign-off — confirmation that the solution works for the business across all relevant dimensions — before the team commits to building.

Do NOT use this skill for customer-facing validation (user testing, demand validation). Those address value and usability risk. This skill addresses the internal business dimension: will finance, legal, sales, marketing, and executive stakeholders support this solution?

Context and Input Gathering

Before running this process, collect:

1. Solution description — What is the proposed product or feature? Sufficient detail to expose constraints (not a vague concept).
2. High-fidelity prototype — Stakeholders need to see actual proposed screens, workflows, and wording. Presentations and slide decks are not sufficient.
3. Business model context — Revenue model, pricing structure, distribution channels, existing partner agreements, brand positioning.
4. Known concerns — Any constraints already surfaced (legal has flagged X; sales team worried about Y).
5. Stakeholder map — Who in this organization holds authority over each relevant domain?