BizThinkFrame
← Back to frameworks
Framework 3-3-3 / Discuss a bounded test using value and feasibility evidence

Value-feasibility Matrix

Compare value hypotheses and implementation conditions on separate axes, retaining unknowns and hard-limit failures.

When to use it

Use the matrix after concepts are concrete enough to compare. Define the beneficiary, evaluation window, evidence and constraints before placement. This guide puts higher value upward and greater feasibility to the right.

What to bring

Comparable candidates, value criteria, budget/capacity/permission records and each judgment's evidence gaps.

What you will have

A two-axis comparison, explicit unknowns and a proposed test with conditions for a separate decision.

How to use it

  1. Agree the goal, unit, window and candidates before screening them.
  2. Define independent high/low criteria and axis directions, plus non-negotiable constraints.
  3. Check records, marking hard-limit failures and keeping insufficient evidence outside the quadrants.
  4. Place supported judgments, retaining assumptions and disagreements without adding scores.
  5. Propose a stoppable test and review conditions; a responsible decision-maker separately confirms execution.

Keep its limits in mind

This value-feasibility matrix is not a game-theory payoff table. It supplies no total score, return rate or success probability. High value may be hypothetical; unknowns are not zeros. Resolve hard constraints first, and do not treat a high/high position as approval.

Fictional teaching example

Comparing four pilot concepts without announcing returns

Fictional teaching example: Starbridge Library Service explores after-hours returns. C4 contains 20 synthetic visits on Oct 12–14, 2026 (12 during staffed hours, eight outside), three people's writing records, pilot estimates and a hypothetical monthly model. People, permissions, prices and behavior are invented. No pilot or paid service has run.

Goal and pilot limitsC4 fictional one-off pilot: cash ≤CNY1000, effort ≤8 staff-hours.Estimates and permission are synthetic; no pilot run.Value axis and criteriaUpward. H=expected after-hours return plus traceable reference; L=information only. All value judgments are untested hypotheses.Feasibility axis and criteriaRightward=easier. H requires cash/staff limits and pilot permission.Permission excludes a permanent service or paid launch; ?=unknown.Value ↑ H · feasibility → H (easier) · categories supplied by the author,no summed scoreValue H / feasibility LC · Locker, CNY4000/20h; exceedsboth caps, excludedValue H / feasibility HB · Box, CNY800/6h; onecontrolled pilot onlyValue L / feasibility LNo supplied candidateValue L / feasibility HA · Information, CNY80/1h;noticeboard allowedUnknown · not assigned a quadrantD · Counter quote, staff and agreement unknownProposed test and unknownsPropose preparing B; check safety, capacity and collection duty. Astub is not confirmed receipt. A lead must decide; D stays unknown. Noproven demand or benefit.

On a small screen, scroll across the diagram to read it.

Separate the axes: A is low-value/high-feasibility; B high/high; C high-value/low-feasibility. Value is an explicit hypothesis, not a measured effect. D lacks evidence for either axis and stays unplaced.

Enforce the limits: A's CNY80/1h and B's CNY800/6h fit the CNY1000/8h caps. C's CNY4000/20h exceeds both and excludes it from this pilot. B's synthetic venue permission covers only one controlled removable-box test.

Result: B is proposed for preparation, subject to safety, capacity, collection duties and a separate decision. No test, paid service or improvement has occurred.

A=80/1, B=800/6 and C=4000/20 in CNY/staff-hours, against caps 1000/8. C fails both limits, D stays unknown, and B is only a proposed pilot.

Next step: Confirm pilot conditions and decision authority. Use a business flow diagram if the parties and exchanges still need explanation.

Three conditions that prevent a useful comparison

First, pause if the candidates have different scopes. A removable-box pilot and a permanent paid service require different resources and permissions. Define the same test window and beneficiary before comparing them. A small estimate is meaningful only when it covers the work actually proposed.

Second, resolve hard limits before discussing attractive positions. A candidate that exceeds the agreed cash or staff-hour cap cannot be rescued by a strong value hypothesis. Keep an explicit exclusion or condition rather than averaging the problem away. Unknown implementation conditions should remain unknown, not become a low numerical score.

Third, stop if an axis is ambiguous. In this guide value increases upward and feasibility increases rightward. That is different from a chart where greater effort or cost increases rightward. Define high and low in words, retain the evidence and disagreement, and avoid a total score or implied success probability.

Choose the comparison that the evidence can support

This matrix is useful when concepts are concrete enough to discuss both a beneficiary’s task and implementation conditions. It is not a game-theory payoff table. Use other methods if the team still needs concepts, a traceable operating sequence, or a more explicit tradeoff among several feasible options.

Choose by the missing decision material
Question and inputMethodOutput and limit
Comparable concepts with value hypotheses and pilot constraintsValue-feasibility matrixSeparate-axis judgments and a proposed check; no authorization.
Distinct dimensions but incomplete conceptsMorphological analysisConfigurations and exclusions; no automatic winner.
An operational concept has unclear handoffsBusiness process flowchartSteps, parties and exceptions; not a measured benefit.
Feasible alternatives require several stated tradeoffsDecision matrixCriteria, reasons and sensitivity; hard limits still apply.

Compare four Starbridge concepts within one pilot boundary

The complete fictional C4 comparison is a one-off pilot with cash no more than CNY1000 and effort no more than eight staff-hours. A provides information only: CNY80, one hour, with noticeboard permission. B uses a removable box: CNY800, six hours, with permission for one controlled pilot only. C uses a locker: CNY4000, twenty hours, exceeding both limits. D uses a partner counter, but quote, staffing, and agreement are unknown. All estimates and permission records are synthetic; no pilot has run.

High value means an expected after-hours return with a traceable reference; low value means information only. Both are untested judgments against this stated task, not a statement that information is worthless. High feasibility requires fitting both caps and the relevant pilot permission. B’s venue permission does not authorize a permanent or paid service and does not replace a separate execution decision.

A is low-value/high-feasibility; B high/high. C is described as high-value/low-feasibility but explicitly excluded from this pilot. D remains unplaced. The proposed next step is preparation for a possible B test, subject to safety, capacity, collection duties, and the lead’s decision. A high/high label does not supply those missing checks.

Evidence, constraints, and decision status for every candidate
Candidate and supplied estimateValue / feasibility judgmentLimit and next check
A: information, CNY80 / 1 staff-hourL / H under this taskFits caps, noticeboard allowed; benefit remains hypothetical.
B: removable box, CNY800 / 6 staff-hoursH / H, conditional pilot scopeFits caps, one controlled pilot permission; safety, capacity, collection and execution decision remain.
C: locker, CNY4000 / 20 staff-hoursH / L; excludedExceeds cash by 3000 and effort by 12 hours; not eligible under current caps.
D: partner counter, quote and agreement unknown? / ?; unplacedGather quote, staffing, agreement and task evidence; no guessed zero.

Turn a position into a conditional test request

Before requesting execution, describe what B would do, where it would operate, the allowed scope, who would collect returns, and how the trial could stop. Reconcile the complete proposed work against both caps. CNY800 leaves CNY200 within the cash cap, and six hours leaves two staff-hours, but neither remainder proves contingency is sufficient.

Check that the proposed communication distinguishes a numbered reference, deposit, and confirmed inventory receipt. Define what readers should understand and what staff would record. Agree the safety and capacity conditions with the appropriate authority. The fictional venue permission is evidence for its stated scope, not proof that every operating condition is satisfied.

If the lead authorizes a test, preserve the actual decision and any conditions before starting. During a later review, separate estimated from actual cash and effort, participation from demonstrated understanding, and completion from benefit. Include exceptions and unresolved cases rather than reporting only successful returns. No outcome figures are supplied here.

Revisit the placement when scope, estimates, permission, or the beneficiary’s task changes. D may become assessable when evidence arrives; C needs a separately agreed scope or changed limits before reconsideration. The matrix supports a transparent discussion, while stopping, continuing, or expanding the service remains a distinct decision.

Check your work

  • Higher feasibility means easier implementation, not higher cost.
  • Unknowns and hard-limit failures remain explicit; no summed score.
  • Proposal, approval, execution and observed benefit remain separate.

Framework references

References explain the framework and its scope; they do not validate the fictional example's results.

Put the framework to work

Copy the outline and add your question, evidence, and open questions.

When to consider another framework

Business Model Flow DiagramIf a concept's parties, goods, information and payment relationships remain unclear, map them and their agreement gaps; pilot permission does not approve the business model.