Integrative Business Diagnosis

The managerial question: from frameworks to judgment under pressure

Throughout OMBA 101, you accumulated frameworks: why firms exist, how value is created and captured, how business models map to industry structure, how problems decompose into testable branches, how incentives and decision rights shape execution, and how recommendations must be communicated with clarity and honest risk. In boardrooms and operating reviews, those frameworks do not appear as labels on slides. They appear as a coherent story: what is happening, why it is happening, what to do next, and what you are willing to give up.

Integrative diagnosis is the capstone skill: applying multiple lenses until they constrain one another, not decorate a narrative you already believed. A weak diagnosis lists frameworks. A strong diagnosis shows that unit economics force a delivery fix before sales hires, that incentive misalignment explains morale symptoms, that a competitor move changes the issue tree branch with the largest variance, and that the recommendation sequence follows from those constraints.

This lesson teaches a repeatable six-step method, walks two full cases with numbers and stakeholder reads, and assigns practice that mirrors case-style work in later courses. You should finish able to diagnose a real company (employer or public) in two to three written pages with a BLUF (bottom line up front, lead with the recommendation) executives can act on.

The six-step integrative method

Use these steps in order. Skipping steps produces familiar failure modes: jumping to recommendations (Unit 5 without Unit 3), blaming culture (symptoms without incentives from Unit 4), or optimizing one metric while blended numbers hide segment decay (Unit 2 without segmentation).

Step 1: Value creation, delivery, and capture snapshot (Unit 1).
From Value Creation, Delivery, and Capture, name evidence for each leg. Creation: does the offer solve a funded job? Delivery: can customers actually receive the promised outcome on time and at quality? Capture: does pricing and renewal mechanics convert delivered value into cash? Weak capture with strong creation is a common SaaS (software as a service, subscription software) trap; strong capture with weak delivery is a services trap that produces churn.

Step 2: Business model and unit economics by segment (Unit 2).
From The Components of a Business Model and Unit Economics and Contribution Logic, split blended metrics. Compute or estimate CAC payback (customer acquisition cost payback, months until gross profit recovers acquisition spend), NRR (net revenue retention, revenue kept and expanded from existing customers net of churn), gross margin, and contribution by segment or motion. Blended ARR (annual recurring revenue, subscription revenue normalized to a year) growth often hides a decaying feeder segment funding a costly new motion.

Step 3: MECE issue tree on the top miss (Unit 3).
From Issue Trees and Structured Decomposition, build a MECE (Mutually Exclusive, Collectively Exhaustive, non-overlapping complete branches) tree on the headline problem ("growth slowed from twenty-five percent to twelve percent"). Prioritize branches by magnitude using Hypotheses, Evidence, and Managerial Judgment. Avoid fake buckets ("people, process, technology") without testable leaves.

Step 4: Incentives, decision rights, and execution audit (Unit 4).
From Goals, Incentives, and Accountability and Decision Rights and Organizational Coordination, ask whether the operating system matches the strategy. OKR weights, comp plans, roadmap allocation, and CS (customer success, post-sale retention function) staffing are evidence. Why Good Strategies Fail in Execution warns that strategy without cadence and aligned metrics produces activity theater.

Step 5: Communication and calendar reality (Units 5 and 6).
From Writing Clear Executive Memos and Adapting a Message to Stakeholders, compare what leaders say to what calendars and dashboards reward. Morale symptoms often track incentive gaps, not generic "culture problems." Communicating Risk and Uncertainty requires naming tradeoffs explicitly.

Step 6: BLUF recommendation, sequence, owners, tradeoffs.
Lead with the action. Support with the minimum data a decision maker needs. Sequence actions when dependencies exist (fix delivery before adding demand). Name costs: likely ARR miss, headcount moves, short-term growth dip.

How frameworks constrain each other (integration discipline)

Integration means frameworks vote. Example: enterprise ACV (annual contract value, yearly revenue per customer contract) rises (capture looks good), but implementation backlog lengthens (delivery failing). Unit economics on enterprise shows eighteen-month payback with services cost (Unit 2). Issue tree on growth shows new logos slower and SMB expansion weaker (Unit 3). OKRs weight enterprise ARR one hundred percent while CS runs a single motion (Unit 4). The constrained recommendation is not "hire more sales." It is cap enterprise bookings until backlog falls, split CS pods, restore SMB expansion weight in OKRs (Unit 6 Lessons 1–2 on capacity trades).

Another integration test: Why Firms Exist (Unit 1). Should the firm insource implementation or partner? If delivery is bottleneck and asset-specific knowledge is high, boundary choice matters. A diagnosis that ignores make-vs-buy may recommend headcount that raises coordination cost without speed.

From Reading a Business as a System (Unit 1), map feedback loops: SMB neglect reduces referrals that fed enterprise pipeline eighteen months later. Diagnosis must time-bound loops, not only snapshot metrics.

Decision quality with incomplete information (Unit 3 Lesson 5)

You will rarely have perfect data. Integrative diagnosis still proceeds with explicit confidence:

• Label estimates (enterprise payback "eighteen plus months, estimated").
• State what would change the recommendation (if backlog clears in thirty days without quality drop, uncap sales).
• Use expected value thinking for sequencing: fixing delivery may have higher EV than incremental marketing spend when NRR is at risk.

Avoid paralysis: a bounded ninety-day plan with metrics beats waiting for a perfect model.

Communicating the diagnosis (Unit 5)

Structure the written output as an executive memo:

1. BLUF (two to three sentences)
2. Situation / complication (facts and metrics)
3. Analysis (integrated steps 1–5, not separate framework essays)
4. Recommendation and sequence (table with owner, metric, date)
5. Tradeoffs and risks (what you will not do, and why)
6. Ask (decision needed, resources, air cover)

Use one exhibit issue tree and one exhibit segment economics table. Using Data Without Overwhelming the Audience favors a few reconciled numbers over fifty bullets.

Self-assessment rubric and course crosswalk

Before submitting a diagnosis (in this course or at work), score yourself honestly:

Map your draft to OMBA 101 units explicitly during revision:

Strong integrative work reads like Presenting Recommendations to Decision Makers (Unit 5): confident recommendation, bounded uncertainty, explicit dissent you considered. Weak work reads like a consulting appendix without a vote.

When you disagree with leadership's prior bet (enterprise-only motion, deposit count over NIM), diagnosis must separate strategy error from execution error. Sometimes strategy is directionally right but operating system lags (ClearPeak). Sometimes strategy fights industry economics (HarborTrust deposit race while NIM bleeds). The six-step method helps you argue which case you face with evidence instead of tone.

ClearPeak Analytics is a fictional mid-size B2B SaaS company selling workflow software. Facts as of Q2 review:

Qualitative facts: enterprise security features win deals; SMB NPS (Net Promoter Score, loyalty survey metric) flat; enterprise NPS rising; product roadmap prioritized enterprise three quarters; sales comp enterprise-only; CS single team; board deck highlights enterprise wins.

Part A: Value creation, delivery, capture (Unit 1)

Creation is not the bottleneck. Delivery and capture on SMB motion are.

Part B: Business model and unit economics (Unit 2)

Motion shift from PLG SMB to sales-led enterprise without segment reporting on the board deck.

Check: Blended payback between segments during transition ✓

Business Model Canvas stress point: customer relationships and channels differ by segment but one CS motion and one roadmap serve both.

Part C: MECE issue tree on growth slowdown (Unit 3)

Growth 12% vs 25% prior
├── New logos slower (enterprise cycle ~2× SMB)
├── Expansion weaker (SMB NRR contribution down)
└── Churn slightly up (SMB outgrow tier / leave)

Quantitative prioritization (illustrative):

Largest branch: SMB expansion weak threatens feeder pipeline and referrals (system loop, Unit 1).

Hypothesis tests:

• Expansion weak because CS senior time on enterprise? (incentive/capacity)
• Product roadmap SMB integrations delayed? (execution)
• Sales comp ignores SMB expansion? (incentives)

Part D: Incentives, decision rights, execution (Unit 4)

Diagnosis: strategy shifted; operating system did not split motions or protect SMB.

Part E: Communication vs calendar (Units 5–6)

CEO all-hands: "We are an enterprise company now." SMB CS hears deprioritization; discretionary expansion calls stop. Board deck celebrates enterprise ARR; SMB leading indicators (activation, expansion pipeline) absent. Morale symptom tracks incentive story, not random culture drift.

Part F: BLUF, sequence, tradeoffs

BLUF: Stabilize the SMB expansion engine while capping new enterprise sales until implementation backlog falls below forty-five days. Rebalance OKRs and CS capacity before adding enterprise quota carriers.

Tradeoffs named:

• Q3 enterprise ARR likely miss vs plan
• Reallocate headcount from enterprise SDR to implementation
• Short-term growth rate may dip before NRR recovers

Would not do:

• Blanket sales hiring (widens backlog)
• SMB price increase to "focus" (accelerates churn)
• Single blended NRR target (masks SMB problem)

Managerial read: Board should ask for segment economics, not hero enterprise logos. CFO validates cap policy with cash and services margin. CRO needs air cover to say no to enterprise deals until delivery recovers (Unit 5 risk comms).

HarborTrust is a fictional regional bank. Digital deposits grew eight percent YoY (year over year), but NIM (net interest margin, spread between loan yield and deposit cost) compressed forty basis points. Fintech competitors raised savings rates. Legacy core system delays payment features six months.

Part A: Value triangle (Unit 1)

Part B: Business model / unit economics (Unit 2)

Profit pool shift: deposit gathering commoditized by fintech; value migrates to speed and integrated payments (Unit 2 industry structure).

Part C: Issue tree on NIM compression (Unit 3)

NIM −40 bps
├── Asset yield flat (loan mix unchanged)
├── Funding cost up (competitor savings rates +40 bps)
└── Mix shift to low-yield digital deposits (+8% volume)

Largest near-term branch: funding cost up with mix shift amplifying.

Part D: Incentives and execution (Unit 4)

Product OKRs weight accounts opened, not funded balance quality or NIM. Branch marketing spend continues despite digital channel mismatch. Decision rights: pricing committee slow; fintech moves weekly. Short-term vs long-term (Unit 4 Lesson 4): chasing deposit count without margin erodes capital.

Part E: BLUF and sequence

BLUF: Pause broad acquisition spend; reprice savings tier with transparent communication; fund core payment fix before branch marketing expansion; tie product OKRs to funded balance and NIM proxy.

Tradeoff: Slower deposit growth two quarters; avoids locking in high-cost deposits.

Stakeholder messages (Unit 5):

• Board: margin defense vs vanity deposit count
• Branches: explain digital-first investment
• Customers: rate transparency, not bait-and-switch

Check: Actions map to largest tree branches ✓

RidgeLine Outdoor (fictional D2C (direct-to-consumer, selling straight to buyers) brand):

• Revenue +15% YoY; gross margin −6 points
• Freight costs +20%; email promos deepened to clear inventory
• Repeat purchase rate −12% among cohort from last holiday
• New CTO insourced warehouse software; project three months late
• Marketing OKR: revenue; ops OKR: cost per package; no owner for margin

Run the six-step integrative method. Deliver BLUF, one issue tree, one segment or cohort table, recommendation sequence with two tradeoffs.

Solution

Step 1 Value triangle: Creation still resonates (product reviews strong). Delivery hurt by late warehouse software (missed ship windows). Capture degraded via deep promos clearing inventory.

Step 2 Unit economics:

Promo-heavy acquisition buys revenue, destroys repeat and margin (Unit 2).

Step 3 Issue tree on gross margin −6 pts:

GM −6 pts
├── Input cost up (freight +20%)
├── Price/promo depth up (discounting)
└── Mix shift to clearance SKUs

Freight + promos + mix ≈ explain majority; verify with finance bridge table.

Step 4 Incentives: Marketing rewarded revenue, not contribution or repeat; ops rewarded cost per package, not on-time ship; CTO project late without escalation cadence (Unit 4 execution failure).

Step 5 Comms: Leadership celebrates +15% revenue in all-hands; cohort repeat collapse not on dashboard (Unit 5 data discipline).

BLUF: Pause broad promo escalations; implement freight surcharge/pass-through on new orders; finish warehouse software or revert to 3PL (third-party logistics) for peak; align marketing OKR to contribution margin and ninety-day repeat.

Tradeoffs: Lower headline revenue growth two quarters; short-term email list revenue hit. Would not do: blanket 20% site-wide promo to "hit quarter" (worsens repeat).

Check: Recommendation addresses top tree branches and incentive gaps ✓

You join as GM of a B2B marketplace connecting contractors and suppliers. GMV (gross merchandise value, total transaction volume) +22%; take rate flat; liquidity thin in two regions; supply side churn up after fee trial ends; product roadmap built seller features; buyers wait longer for quotes. Sales OKRs on signed suppliers; product OKRs on features shipped; no OKR on match rate or quote latency.

Tasks:

1. Apply Steps 1–2 only in prose (value triangle + unit economics/levers).
2. Build Level 1 MECE tree on "buyer wait time up thirty percent."
3. One BLUF sentence and two sequenced actions with tradeoffs.

Solution

1. Steps 1–2 prose

Value creation still valid for buyers who get quotes; weak for buyers who wait. Delivery failing on match speed and regional liquidity. Capture via take rate stable but GMV quality questionable if transactions do not complete. Unit economics: seller CAC (customer acquisition cost) subsidized by fee trial; churn when fees return implies negative contribution on churned sellers. Buyer side LTV (lifetime value, total profit over relationship) at risk if latency rises. Marketplace model (Unit 2) requires liquidity both sides; seller-only roadmap misaligned.

2. Tree on buyer wait +30%

Quote latency +30%
├── Supply insufficient in region (thin liquidity)
├── Matching algorithm deprioritizes speed
└── Seller response rate down post-fee reinstatement

3. BLUF and actions

BLUF: Pause seller-only feature work; reinstate subsidized fees selectively in thin regions; add buyer-side OKR on median quote time until match rate recovers.

Check: Actions tie to tree branches and marketplace economics ✓

Key takeaways

• Integrative diagnosis applies Units 1–5 until frameworks constrain the recommendation.
• Segment and cohort splits expose stories blended metrics hide.
• MECE trees prioritize variance; incentives explain persistent symptoms.
• BLUF, owners, metrics, sequence, and tradeoffs make analysis actionable.
• Strong case work shows judgment: what not to do matters as much as what to do.

1. Run the six-step template on your employer or a public company; compare your BLUF to a peer or mentor.
2. Return to the unit page for assessments when ready.
3. Continue to OMBA 102: Data, Statistics and Managerial Decisions.