Frameworks for Analyzing Opportunity Selection and Problem Framing

Frameworks are decision tools, not decoration

Frameworks earn their place when they force tradeoffs you would otherwise skip. In opportunity selection, founders need repeatable ways to compare problem hypotheses, stress-test problem frames, and explain why one beachhead beats another before resources commit. A framework is not a slide garnish. It is a shared worksheet that makes disagreement visible.

This lesson covers four frameworks you will use throughout ENT 401: the Problem-Solution Fit Canvas, the Opportunity Scorecard, Forcing Functions for kill decisions, and the Problem Reframe Ladder. Each is applied to RelayOps, the fictional B2B SaaS dispatch venture for mid-market field-service firms (HVAC, plumbing, electrical contractors with 50-500 technicians).

From Lesson 1, you know opportunity selection is capital allocation. From Lesson 2, you have vocabulary for jobs, pains, beachheads, and evidence strength. Frameworks connect those ideas into worksheets you can run in a Monday staff meeting or a venture partner review.

Problem-Solution Fit Canvas (before product-solution fit)

Beginners confuse problem-solution fit with product-solution fit. Problem-solution fit means you have evidence that a defined segment experiences a painful, frequent job and that your proposed approach plausibly relieves it. Product-solution fit means customers adopt and retain a built product. You earn the right to build after problem-solution fit is trending positive.

The Problem-Solution Fit Canvas has nine blocks:

RelayOps segment block: 80-200 technician HVAC/plumbing in high heat-load metros. Current behavior: phone tree + whiteboard + legacy CRM module + texting crews. Alternative solutions: oversized incumbent suites, spreadsheets, human "firefighter" dispatch lead on peak days.

The canvas is deliberately pre-product. Your hypothesis block might read: "Consolidated mobile board with skill-aware reroute suggestions reduces same-day misses." You have not claimed AI, pricing, or feature completeness. You have claimed a testable relief path.

Managers in corporate innovation can use the same canvas to kill "innovation theater." If existing spend is zero and pain frequency is annual, the canvas exposes a science project, not a funded initiative.

Opportunity Scorecard: weight what matters

Scorecards turn arguments into numbers without pretending precision is certainty. RelayOps uses six criteria weighted for early B2B SaaS discovery:

Each hypothesis scores 1-5 per criterion with written evidence notes. Multiply by weight, sum to 100-point scale. The scorecard does not auto-pick winners. It surfaces where hypotheses differ and what evidence would change a score.

Pain intensity without frequency is a consulting project, not SaaS. High frequency without willingness to pay is a productivity nice-to-have. Reachability without competitive gap means you can talk to customers but cannot win. The scorecard forces balanced reading.

Forcing functions and pre-mortems

A forcing function is a scheduled decision point with predefined outputs. RelayOps uses two-week discovery sprints ending in a go / pivot / kill review. Inputs: interview count, pattern notes, scorecard update. Outputs: one promoted hypothesis, one demoted, explicit kill list.

A pre-mortem asks: "It is 12 months later and RelayOps failed. Why?" Teams list failure stories before attachment hardens. Common RelayOps pre-mortem items: "Incumbent shipped good-enough rebalance module," "Buyers loved dispatchers but COO would not fund," "Heat pain was regional not national," "Integration took nine months."

Pre-mortems improve problem framing by naming risks as testable assumptions. Instead of vague fear, you get: "Assumption: COO will fund if overtime reduction exceeds 8 percent in pilot." That assumption becomes an interview question and a pilot metric.

Kill decisions use stop rules, not vibes. Example stop rule: "If after 15 interviews fewer than 40 percent unprompted mention same-day rebalance pain, demote H1." Stop rules are signed before interviews to reduce founder bias.

Problem Reframe Ladder: climb down to specifics

Founders often frame problems too high on the ladder (category slogans) or too low (feature bugs). The Problem Reframe Ladder has five rungs:

1. Category: "Field service needs digital transformation."
2. Workflow: "Dispatch scheduling is inefficient."
3. Task: "Same-day reroutes take too long."
4. Moment: "When two senior techs call in sick by 9 a.m., the board breaks."
5. Metric symptom: "Missed first-visit slots rise 12-18% on heat-wave Mondays."

Discovery interviews should climb down to rung 4 or 5. Sales demos often mistakenly climb up to rung 1 or 2. RelayOps interview scripts start at rung 4 moments, then validate metric symptoms with buyer data requests.

Climbing the ladder is also how you negotiate internal alignment. Engineers gravitate to rung 5 specifics. Executives sometimes speak at rung 2. The framework gives a neutral path: "Let's agree on the moment and metric before we debate architecture."

Integrating frameworks in a one-week cadence

Monday: pick hypotheses and update canvases. Tuesday-Thursday: interviews and behavior observation. Friday: scorecard refresh and forcing function review. Document what changed in evidence strength, not only interview count.

This cadence prevents two failure modes: endless exploration without decision, and premature build without pattern density. RelayOps founders capped explore to three hypotheses to keep Friday reviews honest.

RelayOps completed 14 interviews across HVAC and plumbing ops leaders. Apply frameworks to decide next step.

Part A: Canvas excerpt (H1 dispatch rebalance)

Part B: Scorecard update

Check: 25+20+16+12+6+10 = 89 ✓

Part C: Pre-mortem top risk

"COO funds only if integration is under 30 days." Forcing function: run three technical discovery calls with IT stakeholders in week 5.

Part D: Reframe Ladder placement

Interview transcripts cluster at rung 4 ("two techs out by 9 a.m.") with metric pull at rung 5 when ops leaders share overtime reports. RelayOps keeps marketing at rung 4-5, not rung 1.

Managerial read: Score 89 supports promote H1 from validate toward commit pilot, conditional on integration risk tests. Competitive gap score 3 warns against claiming full-suite replacement; wedge language stays narrow.

Weighting criteria when hypotheses look similar

Scorecards fail when teams treat weights as decoration. RelayOps assigns highest weight to pain intensity and frequency because a venture cannot fund sales and engineering on annual pains or mild inconveniences. Willingness to pay signals receive equal weight to frequency in early B2B because dispatch software competes with overtime, headcount, and incumbent modules, not with curiosity.

When two hypotheses score within five points, the scorecard does not pick automatically. Founders run a tie-breaker worksheet: Which hypothesis has more level 1-2 evidence? Which has shorter integration path? Which has clearer economic buyer? RelayOps H1 beat H4 (customer churn from unreliable windows) because churn pain was real but attribution to dispatch was noisy; buyers cited many causes for cancellations.

Weights should shift by stage. At explore, reachability and founder edge matter more because you need conversations. At validate, willingness to pay and competitive gap matter more because you need a wedge that wins checks. RelayOps revisits weights at Gate 1 and Gate 2 explicitly rather than recycling Week 1 scores.

Using the Problem Reframe Ladder in live interviews

The Problem Reframe Ladder is not only a post-interview sorting tool. RelayOps interviewers use it actively when a buyer speaks at rung 2 ("scheduling is inefficient"). The interviewer climbs down with prompts: "Tell me about the last time scheduling broke before noon." Then: "What did you see on the board?" Then: "What metric moved that week?"

Climbing down live prevents premature solution talk. If the buyer jumps to rung 5 with overtime percentages, the interviewer confirms data source and period before recording. If the buyer stays at rung 2, the interview is scored low evidence strength for problem framing until a rung 4 moment appears.

RelayOps marketing copy uses rung 4-5 language only after interviews confirm those rungs dominate. Website hero text references "two techs out by 9 a.m." not "field service digitization." The ladder keeps marketing, sales, and discovery aligned on the same specificity.

After 14 interviews, H1 (dispatch rebalance) scores 89 and H4 (unreliable appointment windows driving churn) scores 84.

Part A: Score breakdown delta

Part B: Tie-breaker worksheet

Part C: Decision

Promote H1; keep H4 as messaging support only (customer-facing symptom) not separate wedge.

Part D: Managerial read

Churn is a lagging pain; rebalance is operational cause candidates can test in shadowing. Scorecard plus tie-breaker prevents emotional choice based on "growth narrative" language.

Check: 89 vs 84 resolved with explicit tie-breaker ✓

RelayOps scores H7 (appointment reminders) at 57 and considers raising H7 frequency score because "no-shows are terrible."

1. What ladder rung is "no-shows are terrible"?
2. What evidence would justify raising frequency from 3 to 4?
3. Write a stop rule for H7 explore spend.
4. Can H7 attach to H1 later without becoming a second beachhead? Explain.

Solution

1. Rung 2 (workflow slogan) without situational specificity.

2. Evidence needed: 6+ interviews with unprompted same-week no-show fires tied to dispatch workflow (not marketing automation owned by another team); existing SMS spend cited in 4+ accounts.

3. Stop rule: If after 8 reminder-focused interviews fewer than 3 rank no-shows in top three dispatch-owned pains, kill H7 explore and cap at zero hours.

4. Yes as attach: Reminders may become a module after H1 wins dispatch board adoption; beachhead remains rebalance because budget hooks and shadows center on dispatcher loop time.

Check: attach path preserves selection discipline ✓

Canvas block quality standards

Each Problem-Solution Fit Canvas block at RelayOps requires an evidence label: Supported, Testing, or Assumption. Supported means at least two independent interviews or one shadow plus interview agree. Testing means single source. Assumption means no customer contact yet. Blocks without labels are rejected in Friday review.

Quality standards prevent canvases from becoming creative writing exercises. Maya once wrote "pain intensity high" without quotes; Jordan downgraded the block to Assumption until COO overtime PDF arrived. The discipline feels bureaucratic until a board member asks which blocks are real.

Canvas quality also means date stamps. RelayOps snapshots canvases weekly. Comparing Week 4 and Week 8 canvases shows whether competitive gap score should move when incumbent ships features. Historical canvas PDFs become audit trail for validation committee.

Scorecard sensitivity to new evidence

RelayOps recomputes scorecards when material evidence arrives: new shadow median, IT review tail, LOI signed, incumbent release. Materiality rule: any change that would move a single criterion by two or more points triggers rescore. Immaterial anecdotes do not trigger rescore.

Sensitivity reviews avoid both overreaction and inertia. When QuickReroute launched, competitive gap dropped from 3 to 2, not instantly to 1, because win/loss data was incomplete. Two weeks later, with three losses documented, gap moved to 1 with written note in scorecard appendix.

RelayOps adds hypothesis H7: automated customer appointment reminders to reduce no-shows. Week 1 evidence: 8 interviews, 3 rank no-shows top five, 2 cite SMS tools already, 5 mention dispatch pain higher.

1. Complete a mini canvas for H7 (three rows minimum: segment, pain frequency, existing spend).
2. Score H7 on the six criteria with brief evidence notes; compute weighted total.
3. Write one pre-mortem failure story and convert it to a testable assumption.
4. Place H7 on the Reframe Ladder; recommend rung for next interviews.

Solution

1. Mini canvas:

• Segment: Maintenance-plan HVAC firms with high residential volume.
• Pain frequency: No-shows spike on Mondays and after holidays; 3/8 top-five rank.
• Existing spend: 2/8 already pay SMS reminder tools; others use manual texts.

2. Scorecard:

Check: 15+12+8+12+4+6 = 57 ✓

3. Pre-mortem: "RelayOps built reminders but COO saw no utilization lift because no-shows were not dispatch's KPI." Assumption test: "No-show rate times job margin exceeds dispatcher pain economically; verify with buyer P&L view."

4. Ladder: Start interviews at rung 4 ("customer forgets AM slot after confirmation text") not rung 2 ("reduce no-shows"). H7 stays explore; H1 remains primary at score 89 vs 57.

Key takeaways

• Problem-Solution Fit Canvas structures evidence before build decisions.
• Weighted scorecards compare hypotheses while exposing weak dimensions.
• Forcing functions and pre-mortems turn anxiety into testable assumptions.
• Reframe Ladder keeps problem statements at interview-ready specificity.
• RelayOps promotes dispatch rebalance when canvas, score, and ladder align.

1. Run a one-page Problem-Solution Fit Canvas on your top hypothesis with evidence labels.
2. Schedule a forcing function review date and write two stop rules before your next five interviews.
3. Continue to Lesson 4: Opportunity Selection and Problem Framing: Applied Business Decisions.