Chapter 6: EROM for Commercial TRIO Enterprises
Book: Enterprise Risk and Opportunity Management: Concepts and Step-by-Step Examples for Pioneering Scientific and Technical Organizations
Author: Allan S. Benjamin
ISBN: 9781119288428
Most of Benjamin’s book follows government and nonprofit TRIO enterprises whose top goals sound like mission statements: advance science, serve the public, explore the cosmos. Chapter 6 turns to the companies that actually build the hardware. For them, the fundamental objective is financial gain. Technical work is a means, not the finish line.
That shift changes the math, but not as much as you might expect.
The qualitative-quantitative split
Commercial TRIO enterprises still face qualitative risks: management performance rated excellent-to-poor, succession planning gaps, labor relations, technology exploitation, even acts of terror. What differs is how success is scored. Dollars replace “understanding the universe.”
Benjamin’s key insight is dual modeling. The qualitative machinery from Chapters 3 through 5 (scenario statements, leading indicators, watch and response triggers, roll-up templates) feeds a financial model. The financial model feeds back:
- Predicted gain or loss becomes a leading indicator in qualitative analysis.
- Financial modeling assumptions clarify which real-world assumptions need internal controls.
Because financial models carry epistemic uncertainty, analysts often run optimistic, most likely, and pessimistic cases. Monte Carlo runs can replace those labels with confidence levels (5%, 50%, 95%). The qualitative and quantitative tracks should tell a consistent story. When they diverge, something is wrong in the rationale chain.
Faster decisions need branching scenarios
Government programs can deliberate. Commercial firms sometimes must decide in days. A competitor drops prices; you match or walk away. Near-term profit risk diverges from long-term revenue risk depending on the branch you take.
Benjamin extends standard scenario statements with scenario event diagrams. Each decision branch becomes a pathway with its own consequences. Company XYZ, a fictional aerospace prime, illustrates the pattern across a full taxonomy:
- Competition: new entrant forces a price war or market exit.
- Customer satisfaction: reassign a star project manager to fix a cryocooler crisis, saving one program while jeopardizing another.
- Leadership mortality: CEO health events and succession readiness.
- Accidents: human fatalities and liability exposure.
- Macro shocks: foreign exchange and interest rate moves.
- Labor: strike risk and negotiation branches.
- Technology: exploit a breakthrough or miss the window.
- Security: terror events disrupting operations.
Each diagram pairs with the familiar “Given current conditions…” scenario prose, but the branches make management choices explicit. That matters when the risk is not just “something bad might happen” but “if we respond this way versus that way, the financial picture changes.”
Templates at pathway level
For commercial enterprises, each pathway through a scenario event diagram is treated as its own scenario for template purposes. The roll-up proceeds in layers:
- Qualitative concern or interest per leading indicator.
- Concern or interest per pathway.
- Cumulative concern or interest against financial objectives.
When the objective is monetary, pathways also get quantitative treatment: likelihood estimates (often via event tree or fault tree thinking) plus financial consequence models.
Table 6.3 introduces a Qualitative/Quantitative Roll-Up Comparison Template. It displays qualitative “levels of concern” beside optimistic, most likely, and pessimistic dollar outcomes at each roll-up stage. The color coding from Chapter 4 still applies. The template is a consistency check: if qualitative red flags do not align with quantitative downside, analysts revisit assumptions on both sides.
Risk and opportunity matrices that actually fit dollars
Classic 5×5 likelihood-impact matrices are everywhere in program management. Benjamin notes they work better when top objectives are monetary because impact scales are interpretable consistently. For qualitative mission objectives, the same matrix can feel forced.
For enterprise risk and opportunity management, he pairs mirror matrices: one for risks, one for opportunities, cells numbered 1 through 25 for rank ordering. Scenario pathways from event diagrams map onto the cells using quantitative roll-up results. A pathway landing in cell 25 outranks one in cell 10, full stop.
Near-term “very high” dollar impact and long-term “very high” dollar impact may mean different actual dollar thresholds. The 1-to-5 scales are judgment calls tied to the objective horizon, not universal constants.
Controllable drivers beyond the government checklist
Commercial primes share many drivers with their government customers. Schedule reserve and cost reserve depletion worry both sides. But commercial enterprises carry a longer list tied to financial health.
Benjamin’s XYZ Company table lists controllable drivers with existing safeguards, mitigations/actions, and internal controls. Examples that felt uncomfortably real:
| Driver | Safeguard example | Mitigation example | Control example |
|---|---|---|---|
| Insufficient customer diversification | 500+ customers | Close unprofitable contracts, pursue new markets | Monitor revenue per customer |
| Capital/liquidity stress in inflation | 10% margin on current needs | Convert long-term investments to cash; consider merger | Peer-reviewed investment plan with monitoring |
| Inadequate liability insurance | $200M per incident coverage | Raise deductible to expand max coverage | Continuous sufficiency monitoring |
| Weak market analysis | Analysis embedded in business plan | Hire specialist consultants | Vet analyst credentials |
| CEO dependency | Succession plan on file | Delegate responsibilities downward | Track delegation effectiveness |
| Stress-driven human error | Employee assistance program | Survey stress, reduce workload | Report stress and error incidents upward |
The driver definition from Chapter 3 still applies: a single constituent rarely qualifies. It is the combination that moves cumulative risk from green to yellow to red.
Tables 6.5 excerpts show mitigations and controls linked back to specific scenario diagrams from earlier figures, closing the loop between identification and response.
Why this chapter matters for partnerships
Government TRIO enterprises depend on commercial partners. Noncommercial sponsors depend on primes who must stay solvent, insurable, and competitive while delivering on technically brutal contracts. EROM alliances only work if both sides can speak a shared risk language even when success metrics differ.
Chapter 6 is Benjamin’s bridge. Qualitative scenario discipline stays. Financial modeling joins the party. Branching diagrams capture management decisions that pure event lists flatten. Comparison templates keep the two worldviews honest with each other.
If you are on the industry side of a major aerospace or defense program, this is the chapter that translates NASA-style EROM into something your CFO’s office can engage with without dismissing it as “mission rhetoric.”
← Chapter 5: Technical Centers · Chapter 7: Risk Acceptance Examples →