{ "schemaVersion": "1.0.0", "documents": [ { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Macroeconomics for Strategic Leaders", "headingId": "chapter-01-macroeconomics-for-strategic-leaders", "url": "#chapter-01-macroeconomics-for-strategic-leaders", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-executive-summary", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Executive Summary", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-executive-summary", "url": "#chapter-01-macroeconomics-for-strategic-leaders-executive-summary", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter presents a toolkit for interpreting the macroeconomic environment. It connects national output, employment, inflation, monetary and fiscal policy, exchange rates, and supply shocks to managerial assumptions about pricing, investment, capacity, and risk. These tools organize evidence; they do not remove forecast error or replace firm-specific finance, marketing, operations, legal, or people decisions. Key Frameworks Covered: 1. GDP Growth & Business Cycle Analysis 2. Inflation & Pricing Strategy Matrix 3. Interest Rate & Capital Investment Decision Tree 4. Unemployment & Labor Market Analysis 5. Currency Exchange Rate & Global Strategy 6. Fiscal Policy Impact Assessment 7. Monetary Policy Radar (Central Bank Watching) 8. Global Economic Indicators Dashboard 9. Supply & Demand Shock Analysis 10. Yield Curve & Recession Forecasting ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-1-gdp-growth-business-cycle-analysis", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "1. GDP Growth & Business Cycle Analysis", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-1-gdp-growth-business-cycle-analysis", "url": "#chapter-01-macroeconomics-for-strategic-leaders-1-gdp-growth-business-cycle-analysis", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "GDP Growth & Business Cycle Analysis Macroeconomic Scenario Analysis" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-overview", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-overview", "url": "#chapter-01-macroeconomics-for-strategic-leaders-overview", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Gross domestic product (GDP) measures the value of final goods and services produced within an economy. The U.S. Bureau of Economic Analysis publishes current-dollar and inflation-adjusted estimates, supporting data, revision information, and historical vintages; managers should record which measure and release they use. [BB-C01-S13] Economies move through business cycles commonly described as expansion, peak, contraction, and trough. Burns and Mitchell remains a classic source on measurement and dating, while the NBER's current U.S. procedure uses multiple indicators and dates turning points retrospectively rather than in real time. [BB-C01-S04] [BB-C01-S14] Real-business-cycle theory is one influential explanation of fluctuations, emphasizing real shocks and observed cyclical facts. It is not a cycle-timing tool. Use cycle analysis as scenario context, not as proof of a firm's next-period demand or returns. [BB-C01-S01]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-how-to-apply", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply", "url": "#chapter-01-macroeconomics-for-strategic-leaders-how-to-apply", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define Your Economic Exposure: Compare inflation-adjusted company demand with relevant national and sector measures. If you estimate a regression, specify the data vintage, frequency, deflator, lags, structural breaks, uncertainty, and alternative drivers; treat the result as an association and hand the statistical mechanics to Data Analysis and Insights. 2. Monitor Complementary Indicators: GDP releases are revised and business-cycle dating is retrospective. Choose a small set of measures tied to the firm's exposure and record each measure's owner, definition, release lag, revision policy, and false-signal risk: - Yield Curve & Recession Forecasting (Framework 10): A well-studied financial leading indicator for recessions. [BB-C01-S02] - Purchasing-manager surveys: Use as directional context; do not treat them as a recession call. - Customer and operating evidence: Use orders, cancellations, utilization, lead times, credit conditions, and churn as firm-specific corroboration. 3. Formulate Conditional Responses: For each plausible phase, test what would change demand, margin, liquidity, capacity, and talent assumptions. Separate reversible moves from long-lived commitments and state what evidence would reverse the decision. Figure 1.1. Convert macro signals into a firm-specific scenario posture. This is an original decision aid, informed by business-cycle measurement and yield-curve evidence; it is not a deterministic forecasting model. [BB-C01-S02] [BB-C01-S04] [BB-C01-S14] Text equivalent: Define the indicators and data vintage, estimate several scenarios rather than a single phase, map each scenario to the firm's exposures and constraints, then test reversible actions while applying a higher evidence bar to irreversible commitments." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-long-run-growth-and-productivity", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Long-run growth and productivity", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-long-run-growth-and-productivity", "url": "#chapter-01-macroeconomics-for-strategic-leaders-long-run-growth-and-productivity", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Short-run cycle management is incomplete without a long-run view. In a later retrospective on his seminal growth-accounting exercise, Solow describes continuing efforts to assign parts of the residual to better-measured inputs or outputs and identifies measurement, modeling, and aggregate-production-function limitations. Use productivity, capital deepening, labor input, and institutional or technology context to test whether a demand change is cyclical or reflects a shift in potential output. Do not treat the residual as a pure measure of technology or a firm-level causal estimate. [BB-C01-S19]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers", "url": "#chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Translate macro data into firm-specific scenarios; do not manage to a headline GDP number. - Require stronger evidence before irreversible capacity, capital, or workforce commitments. - Preserve the data vintage and the evidence that would reverse each decision." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques", "url": "#chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- GDP is revised, aggregates unlike sectors, and can diverge from the firm's actual markets. [BB-C01-S13] - Business-cycle turning points are dated retrospectively, so this framework cannot identify the current phase with certainty. [BB-C01-S14] - The framework organizes scenarios; it does not establish a causal forecast of firm demand or returns. [BB-C01-S01]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-connections", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-connections", "url": "#chapter-01-macroeconomics-for-strategic-leaders-connections", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: This analysis is informed by the macro-environmental scan from PESTLE Analysis. - Input: Requires an understanding of the firm's financial structure from Financial Analysis and Valuation to assess sensitivity. - Output: The demand scenarios inform Operations and Supply Chain and Go-to-Market Strategy. ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-2-inflation-pricing-strategy-matrix", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "2. Inflation & Pricing Strategy Matrix", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-2-inflation-pricing-strategy-matrix", "url": "#chapter-01-macroeconomics-for-strategic-leaders-2-inflation-pricing-strategy-matrix", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Inflation & Pricing Strategy Matrix Margin Protection" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-overview-2", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-overview-2", "url": "#chapter-01-macroeconomics-for-strategic-leaders-overview-2", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Inflation should be mapped through product-level cost, demand, financing, and contract evidence before a firm response is chosen. Author-created diagnostic: Distinguish input-cost pressure, excess demand, and weak demand with persistent inflation, then test the pricing response against firm-specific evidence." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-2", "url": "#chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-2", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The table below presents hypotheses to test, not evidence-backed default actions. Any packaging, disclosure, promotion, or dynamic-pricing change requires applicable consumer-protection, contract, and sector review. | Working diagnosis | Evidence to collect | Options to test | Stop rule / constraint | | :--- | :--- | :--- | :--- | | Input-cost pressure | Cost bridge, contract resets, competitor moves, unit margin | Selective pass-through, product redesign, supplier or process changes | Stop if volume, trust, or contribution margin deteriorates beyond the approved range | | Demand pressure | Capacity utilization, backlog quality, elasticity tests, service levels | Capacity allocation, tier design, transparent price tests | Stop if the signal reflects a temporary spike or harms priority relationships | | Weak demand with persistent inflation | Real income, churn, mix shift, working capital | Value tiers, cost redesign, smaller reversible experiments | Stop if affordability, legal, brand, or channel constraints are breached |" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-2", "url": "#chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-2", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Diagnose the source of pressure before choosing a pricing response. - Pair every price test with an approved stop rule covering margin, volume, trust, contracts, and legal constraints. - Treat packaging, product redesign, and cost changes as alternatives to a broad price increase." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-2", "url": "#chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-2", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Perceived fairness is a design constraint, not a universal estimate of churn or profit. Test actual customer response. [BB-C01-S12] - The matrix is a diagnostic aid, not an elasticity estimate or a guarantee that a price change will protect margin. - Cost pass-through, elasticity, competition, and contract timing remain firm- and segment-specific." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-connections-2", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-connections-2", "url": "#chapter-01-macroeconomics-for-strategic-leaders-connections-2", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Requires product-level elasticity and experiment design from Marketing and Customer Analytics. - Output: Informs Financial Analysis and Valuation and Go-to-Market Strategy. ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-troubleshooting-guide-macroeconomic-analysis", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Troubleshooting guide: Macroeconomic analysis", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-troubleshooting-guide-macroeconomic-analysis", "url": "#chapter-01-macroeconomics-for-strategic-leaders-troubleshooting-guide-macroeconomic-analysis", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Treat each diagnosis below as a hypothesis to test, not as a conclusion from the symptom alone. - Symptom: \"Our forecasts are consistently over-optimistic, and we're always surprised by downturns.\" - Possible hypothesis: Test whether the process overweights coincident or lagging indicators, underweights disconfirming evidence, or embeds optimistic assumptions. - Action: Build a dashboard of exposure-linked indicators with definitions, vintages, revisions, and falsification tests. Compare a downside scenario with base and upside cases and seek disconfirming evidence. - Symptom: \"We raised prices to combat inflation, but our sales volume collapsed.\" - Possible hypothesis: Test whether elasticity differed by segment, whether the price/mix/volume bridge is correct, and whether competition, affordability, execution, or the offer—not inflation alone—explains the decline. - Action: Re-estimate elasticity by segment, reconcile price/mix/volume, and test a transparent, reversible offer change within legal and brand constraints. - Symptom: \"We invested heavily in a new factory, but now interest rates are high, and our financing costs are crippling us.\" - Possible hypothesis: Test whether the decision used the wrong yield curve, credit spread, debt terms, cash-flow scenario, project risk, or liquidity constraint. - Action: Ask Finance to update the risk-free curve, credit spread, debt schedule, covenants, project cash flows, and liquidity scenarios. Refinancing and hedging decisions require treasury, accounting, tax, and legal review. - Symptom: \"Our international sales are strong in local currency, but our reported dollar-based revenue is disappointing.\" - Possible hypothesis: Test whether translation, transaction, or economic exposure—and not volume, mix, local pricing, accounting, or another driver—explains the reported difference. - Action: Separate translation, transaction, and economic exposure; then evaluate operational and financial hedges under an approved treasury policy. Currency alone is not a sufficient reason to change sourcing. ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-3-interest-rate-capital-investment-decision-tree", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "3. Interest Rate & Capital Investment Decision Tree", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-3-interest-rate-capital-investment-decision-tree", "url": "#chapter-01-macroeconomics-for-strategic-leaders-3-interest-rate-capital-investment-decision-tree", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Interest Rate & Capital Investment Decision Tree Capital Allocation" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-overview-3", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-overview-3", "url": "#chapter-01-macroeconomics-for-strategic-leaders-overview-3", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Interest rates influence the user cost of capital. Policy rates therefore matter to investment analysis but do not determine a project's cost of capital by themselves. [BB-C01-S05] Author-created risk checklist: A project's risk-adjusted discount rate may also reflect term, credit, country, currency, tax, and project-specific risks. The relationship between interest rates and investment decisions is grounded in neoclassical investment theory: firms compare expected returns with the user cost of capital. The exact investment response varies by firm leverage, sector, and financing constraints, so treat this as a hurdle-rate discipline rather than a universal elasticity. [BB-C01-S05]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-3", "url": "#chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-3", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Step 1: Update the financing and risk inputs - Record the risk-free curve, relevant credit spread, inflation assumption, tax treatment, funding term, and currency. - Separate a change in financing conditions from a change in the project's operating risk. Step 2: Estimate risk-adjusted project value - Build base, upside, and downside cash-flow cases. - Constructed decision rule: Use risk-adjusted NPV as the primary value test; use IRR as a secondary diagnostic and check for non-standard cash flows or mutually exclusive alternatives (see Financial Analysis and Valuation). Step 3: Test strategic and financing constraints - Quantify the loss avoided or option created by strategic necessity. - Test liquidity, covenants, concentration, execution capacity, and reversibility. - Stage, redesign, delay, or reject the project when uncertainty is material. Step 4: Apply the Decision Tree Figure 1.2. Capital-investment decision gate. This original synthesis applies user-cost logic without treating strategic importance or IRR as an automatic approval. [BB-C01-S05] Text equivalent: Estimate both the strategic loss avoided and the project's risk-adjusted NPV. Approve only if value, liquidity, risk, and execution constraints pass; otherwise redesign, stage, delay, or reject." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-3", "url": "#chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-3", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Recalculate project value when financing, operating risk, or cash-flow assumptions change. - Use NPV as the primary value test, then stage or preserve options when uncertainty is material. - Approve only with explicit liquidity, execution, monitoring, and stop-rule ownership." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-3", "url": "#chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-3", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Author synthesis: A tighter financing environment may change competitive behavior, but it does not make investment automatically attractive. - Test counter-cyclical investment against project value, financing resilience, capacity, strategic options, and the cost of waiting. - NPV remains sensitive to forecast error, discount-rate assumptions, terminal value, and omitted execution constraints. - Strategic importance is not a substitute for quantifying downside exposure." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-connections-3", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-connections-3", "url": "#chapter-01-macroeconomics-for-strategic-leaders-connections-3", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Requires understanding of monetary policy from Monetary Policy Radar (Framework 7) and economic cycles from GDP Growth & Business Cycle Analysis (Framework 1) . - Input: Project cash flows and discount-rate assumptions from Financial Analysis and Valuation. Use the DCF valuation template and DCF workbook as reviewable starting artifacts, not as substitutes for approved assumptions. - Output: Approved investment assumptions feed Operations and Supply Chain and strategic execution. ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-4-unemployment-labor-market-analysis", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "4. Unemployment & Labor Market Analysis", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-4-unemployment-labor-market-analysis", "url": "#chapter-01-macroeconomics-for-strategic-leaders-4-unemployment-labor-market-analysis", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Unemployment & Labor Market Analysis Workforce Strategy" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-overview-4", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-overview-4", "url": "#chapter-01-macroeconomics-for-strategic-leaders-overview-4", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The unemployment rate is one input to workforce planning, but aggregate conditions can differ sharply by occupation, location, industry, and skill. Interpret it alongside participation, wages, vacancies, hires, quits, layoffs, and firm-specific recruiting evidence. [BB-C01-S10] Beveridge-curve analysis connects unemployment with job vacancies; BLS JOLTS data makes this practical by tracking job openings, hires, quits, layoffs, and separations. The curve can shift, so use it as a joint diagnostic rather than a fixed law or a substitute for occupation- and geography-specific evidence. [BB-C01-S10] [BB-C01-S20]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-4", "url": "#chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-4", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Monitor Key Labor Market Indicators - Unemployment Rate: The headline number; interpret it alongside participation, wages, and vacancies. - Labor Force Participation Rate: Are people entering or leaving the workforce? - Wage Growth: Compare nominal wage growth with inflation, productivity, occupation, and location. - Quit Rate: Treat quits as one mobility measure; do not assume a single motive. - Job Openings (JOLTS): Compare openings, hires, and unemployed workers while allowing for matching frictions and industry mix. [BB-C01-S10] 2. Determine Market Condition | Indicator | Tight Market | Balanced | Loose Market | | :--- | :--- | :--- | :--- | | Unemployment | Historically low | Near recent norm | Rising or elevated | | Wage Growth | Above the relevant historical/occupation range | Near the relevant range | Below the relevant range | | Quit Rate | Elevated versus a comparable period | Near a comparable period | Depressed versus a comparable period | | Job openings, hires, and unemployed | Vacancies persist and hiring is difficult | Evidence is mixed | Applicant supply rises or vacancies fall | 3. Adjust Your Talent Strategy When the relevant talent market appears tight, test: - compensation benchmarks, internal equity, and pay-transparency constraints; - job-related selection criteria, trainability, and internal mobility; - the causes of regretted turnover by role and manager; and - whether process delay is losing qualified candidates. When the relevant talent market appears loose, test: - whether applicant supply has actually improved for the required role and location; - whether hiring remains job-related, documented, and consistent; - whether lower external mobility masks engagement or retention risk; and - whether the business has durable demand and budget for the role." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-4", "url": "#chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-4", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Combine public labor indicators with role-, location-, and firm-specific recruiting evidence. - Test whether hiring difficulty is caused by compensation, criteria, process delay, management, or a genuinely scarce skill. - Keep selection criteria job-related and documented in both tight and loose markets." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-4", "url": "#chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-4", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- For some roles and locations, weaker labor conditions may increase applicant supply; test that inference with role-specific evidence. [BB-C01-S10] [BB-C01-S20] - Treat selective hiring as an option subject to durable demand, budget, fair selection, and workforce plans—not as a general recession rule. - Aggregate measures can hide differences by occupation, geography, industry, and skill. - The Beveridge curve can shift, so it should not be treated as a fixed hiring rule. [BB-C01-S20]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-connections-4", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-connections-4", "url": "#chapter-01-macroeconomics-for-strategic-leaders-connections-4", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Economic cycle analysis from GDP Growth & Business Cycle Analysis (Framework 1) . - Input: Labor cost data from Finance and competitive intelligence from HR . - Output: Informs Talent Acquisition Strategy and Compensation Planning in HR operations. ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-5-currency-exchange-rate-global-strategy", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "5. Currency Exchange Rate & Global Strategy", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-5-currency-exchange-rate-global-strategy", "url": "#chapter-01-macroeconomics-for-strategic-leaders-5-currency-exchange-rate-global-strategy", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Currency Exchange Rate & Global Strategy International Operations" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-overview-5", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-overview-5", "url": "#chapter-01-macroeconomics-for-strategic-leaders-overview-5", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Currency movements can affect transaction cash flows, the translated results of foreign operations, and longer-run competitive exposure. Direction and magnitude depend on invoice currency, pass-through, elasticity, contracts, operational location, and hedges; “strong” or “weak” currency labels alone do not determine the business outcome. Foreign-currency derivatives are one tool for managing this exposure. Allayannis and Weston find a positive relationship between foreign-currency derivative use and firm value among exposed firms, but that evidence should not be overread as a universal rule that hedging always improves outcomes. [BB-C01-S06]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-5", "url": "#chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-5", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Understand Your Currency Exposure Build a simple matrix: Simplifying assumption: EUR/USD means U.S. dollars per euro, while CNY/USD below is used informally to denote a yuan-dollar exposure rather than a market quote convention. Define the quoted pair and functional currency before analysis. The table isolates direct USD translation/transaction direction while holding invoice currency, volumes, pass-through, contracts, taxes, tariffs, and hedges constant. Real exposures can reverse the simplified sign. | Business Activity | Currency Exposure | Impact of Strong USD | Impact of Weak USD | | :--- | :--- | :--- | :--- | | Export Sales (US → Europe) | EUR/USD | Negative (US goods more expensive in EUR) | Positive (US goods cheaper in EUR) | | Import Costs (Parts from China) | CNY/USD | Positive (Chinese parts cheaper in USD) | Negative (Chinese parts more expensive in USD) | | Overseas Subsidiary Revenue | EUR/USD | Negative (EUR revenue worth less USD) | Positive (EUR revenue worth more USD) | 2. Monitor Exchange Rate Trends Track the actual currency pair, horizon, and exposure channel; do not infer firm impact from the exchange-rate label alone. 3. Formulate Strategy Based on Exchange Rate Environment When the home currency strengthens, ask: - Which exposures are transactional, translational, or economic? - What is the invoice currency and pass-through behavior? - Do tariffs, taxes, transfer pricing, local costs, contracts, or operational risk outweigh the currency move? - What portion is already hedged naturally or financially? When the home currency weakens, ask the same questions in reverse. Do not assume exports become more competitive, foreign-market prices can rise, earnings should be repatriated, or domestic production becomes superior without customer, tax, capacity, and contract evidence. 4. Implement Currency Hedging For approved, measurable foreign-currency exposures, Treasury may evaluate: - Forward contracts: Fix an exchange rate for a specified amount and date, reducing one risk while retaining forecast, basis, counterparty, liquidity, and opportunity risks. - Options: Provide defined rights for a premium; payoff, accounting, liquidity, and counterparty terms still matter. - Natural hedges: Align some revenues and costs in the same currency, while measuring residual timing and amount mismatches. Author-created governance checklist: Implementation should follow the firm's approved mandate and involve Treasury, Accounting, Tax, Procurement, and Legal/Compliance review, including any applicable sanctions or reporting controls." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-5", "url": "#chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-5", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Measure transaction, translation, and economic exposure separately before choosing a hedge. - Base decisions on invoice currency, timing, pass-through, contracts, taxes, and existing hedges—not a generic “strong currency” label. - Give Treasury a defined mandate, exposure limit, counterparty controls, and residual-risk reporting." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-5", "url": "#chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-5", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The directional matrix holds several variables constant; real pass-through, volumes, taxes, tariffs, and local costs can reverse the simplified sign. - Author-created operational checklist: Derivatives reduce selected risks but add basis, forecast, liquidity, accounting, counterparty, and opportunity risks. - The cited association between derivative use and firm value does not prove that hedging creates value for every firm. [BB-C01-S06]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-connections-5", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-connections-5", "url": "#chapter-01-macroeconomics-for-strategic-leaders-connections-5", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Monetary policy divergence from Monetary Policy Radar (Framework 7) and economic growth differentials from GDP Growth & Business Cycle Analysis (Framework 1) . - Input: Cost structure data from Finance and supplier contracts from Procurement . - Output: Informs global expansion plus Operations and Supply Chain and Marketing and Customer Analytics. ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-6-fiscal-policy-impact-assessment", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "6. Fiscal Policy Impact Assessment", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-6-fiscal-policy-impact-assessment", "url": "#chapter-01-macroeconomics-for-strategic-leaders-6-fiscal-policy-impact-assessment", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Fiscal Policy Impact Assessment Government Policy Analysis" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-overview-6", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-overview-6", "url": "#chapter-01-macroeconomics-for-strategic-leaders-overview-6", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Fiscal policy concerns government spending, taxation, and transfers. Regulation, trade policy, and industrial policy can interact with fiscal choices but should be analyzed separately rather than folded into the same category. Fiscal multipliers are real but context-dependent. Ramey's review of post-crisis fiscal research concludes that many average spending-multiplier estimates cluster around 0.6 to 1, while the effect depends heavily on identification method, economic slack, monetary-policy conditions, and the type of fiscal change. [BB-C01-S08]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-6", "url": "#chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-6", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Map Your Fiscal Policy Exposure Identify how your business is affected by government policy: | Policy change | Transmission questions | Firm evidence required | | :--- | :--- | :--- | | Tax rate, base, or credit | Which entity, jurisdiction, income, timing, and behavioral responses change? | Effective and cash tax bridge; eligibility; legal interpretation; scenario range | | Government spending or transfer | Who receives demand, on what schedule, with what multiplier and capacity constraint? | Contract pipeline; customer exposure; procurement timing; crowding-in/out assumptions | | Tariff or trade measure | Which inputs and competitors are covered; what pass-through, retaliation, substitution, and compliance costs follow? | Product classification; origin; supplier and customer elasticity; legal review | | Subsidy or industrial policy | What eligibility, duration, conditions, clawbacks, and competitive responses apply? | Program text; compliance owner; investment economics with and without support | 2. Monitor Fiscal Policy Signals - Budget proposals: Record stated priorities as scenarios; do not treat proposals as enacted policy. - Legislation in progress: Track bills moving through committee. - Election and legislative calendars: Treat proposals as scenarios until enacted and implemented. - Debt, deficit, and fiscal-space measures: Record the assumed channel and uncertainty rather than treating one measure as a deterministic policy forecast. 3. Formulate Response Strategy Expansionary fiscal scenario: Test the size, timing, recipient, economic slack, monetary response, financing, and sector capacity. Ramey's review shows that average spending-multiplier estimates vary materially by method and context. [BB-C01-S08] Contractionary fiscal scenario: Test which taxes or spending change, who bears the incidence, whether private demand offsets the change, and how monetary and credit conditions respond. Convert results into ranges, not automatic cash or investment commands. 4. Engage in Policy Advocacy (When Appropriate) Policy engagement is jurisdiction-specific. Assign Government Affairs and Legal/Compliance ownership to determine the applicable registration, disclosure, procurement, gifts, anti-bribery, campaign-finance, and trade-association rules before communicating with public officials; distinguish evidence-sharing from advocacy and document approvals." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-6", "url": "#chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-6", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Trace each proposal through the specific entity, customer, supplier, timing, and legal channel that affects the firm. - Keep proposals, enacted law, implementation guidance, and realized effects separate in scenario models. - Compare investment economics with and without a subsidy, credit, tariff, or public-demand assumption." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-6", "url": "#chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-6", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Multiplier estimates vary with identification method, slack, monetary conditions, financing, timing, and the type of fiscal change. [BB-C01-S08] - National averages do not establish the effect on one sector or firm. - Tax, trade, regulatory, and industrial-policy questions require jurisdiction-specific legal interpretation." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-connections-6", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-connections-6", "url": "#chapter-01-macroeconomics-for-strategic-leaders-connections-6", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Political and non-market context from PESTLE Analysis and economic outlook from GDP Growth & Business Cycle Analysis (Framework 1) . - Input: Tax structure analysis from Finance/Tax team . - Output: Informs Strategic Planning , Lobbying/Public Affairs strategy , and Tax Planning . ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-7-monetary-policy-radar-central-bank-watching", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "7. Monetary Policy Radar (Central Bank Watching)", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-7-monetary-policy-radar-central-bank-watching", "url": "#chapter-01-macroeconomics-for-strategic-leaders-7-monetary-policy-radar-central-bank-watching", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Monetary Policy Radar (Central Bank Watching) Monetary-Policy Sensitivity" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-overview-7", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-overview-7", "url": "#chapter-01-macroeconomics-for-strategic-leaders-overview-7", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Author-created diagnostic: Use financing, demand, currency, and expectations channels as questions to test rather than assuming a fixed response. Bernanke and Kuttner's U.S. event study is a bounded example of the equity-market response to unexpected policy changes, not evidence for every transmission channel or a universal trading rule. [BB-C01-S03] The Taylor Rule provides a framework for thinking about policy-rate decisions based on inflation and output gaps. Use it as a disciplined forecasting aid, not as a guarantee of what a central bank will do at the next meeting. [BB-C01-S07]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-7", "url": "#chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-7", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Understand Your Central Bank's Mandate - Federal Reserve (U.S.): Dual mandate: maximum employment and stable prices. [BB-C01-S11] - ECB (euro area): Primary objective of price stability, operationalized as a 2% medium-term inflation aim; support for broader EU policies is subordinate to that objective. [BB-C01-S17] - Bank of England: Primary price-stability objective with a 2% medium-term target set by government; subject to that objective, it supports strong, sustainable, balanced growth. [BB-C01-S18] 2. Monitor the Key Signals | Signal | What to Watch | How to Interpret | | :--- | :--- | :--- | | Policy Rate Decisions | Fed Funds Rate, ECB Deposit Rate | Influence short rates and borrowing conditions; pass-through varies | | Forward Guidance | Statement language and published reaction-function context | Informs market expectations; it is not a promised rate path | | Summary of Economic Projections (Fed) | Individual participant projections | Distribution of views, not a consensus promise | | Minutes or accounts | Institution-specific publication schedule | Recorded discussion, votes, and stated risks; details differ by institution | | Policymaker Speeches | Formal speeches and testimony | Clarify individual views, risks, and possible framework implications | | Quantitative Easing/Tightening | Asset holdings, reserves, and market functioning | Balance-sheet transmission; do not equate it mechanically with broad money growth | 3. Translate to Business Strategy Easing-policy scenario: Ask how much was expected, which maturities moved, whether credit spreads and bank standards changed, and how the firm's debt, cash, customers, and valuation inputs respond. An expected rate cut may already be priced, while deteriorating demand or wider spreads may offset it. Tightening-policy scenario: Recalculate the relevant yield curve, credit spreads, floating-rate exposure, refinancing schedule, customer sensitivity, and project value. Decide from the combined evidence rather than assuming assets fall, targets become cheap, or all firms should favor the same strategy. 4. Use the Taylor Rule as a Historical Reference Taylor's 1993 illustration provided a historical policy benchmark. [BB-C01-S07] Taylor explicitly cautioned against mechanical use. The inflation measure, output-gap method, equilibrium real rate, coefficients, data vintage, and central-bank reaction function are uncertain and can change the result. Use the rule for sensitivity analysis, not as a next-meeting forecast. [BB-C01-S07]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-7", "url": "#chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-7", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Separate an expected policy move from a surprise, then measure what changed in the firm's actual funding and demand channels. - Recalculate debt, liquidity, customer sensitivity, and project assumptions across the relevant yield curve and credit spreads. - Use policy rules and projections as scenario inputs, not automatic trading or capital-allocation commands." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-7", "url": "#chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-7", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Market prices incorporate expectations before a decision; the cited historical U.S. equity response concerns unexpected policy changes, not a universal asset-allocation rule. [BB-C01-S03] - Author-created synthesis: Policy transmission can vary by maturity, credit quality, borrower, regime, and expectations. - The Taylor Rule is a sensitivity benchmark, not a promise of the next decision. [BB-C01-S07]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-connections-7", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-connections-7", "url": "#chapter-01-macroeconomics-for-strategic-leaders-connections-7", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Inflation data from Inflation & Pricing Strategy Matrix (Framework 2) and labor market data from Unemployment & Labor Market Analysis (Framework 4) . - Output: Informs Interest Rate & Capital Investment Decision Tree (Framework 3) , Capital Structure decisions , and Investment Timing . ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-8-global-economic-indicators-dashboard", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "8. Global Economic Indicators Dashboard", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-8-global-economic-indicators-dashboard", "url": "#chapter-01-macroeconomics-for-strategic-leaders-8-global-economic-indicators-dashboard", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Global Economic Indicators Dashboard Macro Monitoring" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-overview-8", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-overview-8", "url": "#chapter-01-macroeconomics-for-strategic-leaders-overview-8", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The global indicators dashboard is an author-created monitoring checklist, not a published standard or a validated forecasting model. External conditions can reach a firm through customers, suppliers, commodities, financing, currencies, and competitors, so the checklist begins with a firm exposure map rather than a universal list of indicators. Use the dashboard as an early-warning system, not as a claim that any single indicator mechanically predicts the firm's performance. Combine it with currency, supply-chain, financing, and demand exposure from the earlier frameworks." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-provenance-first-dashboard-design", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Provenance-first dashboard design", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-provenance-first-dashboard-design", "url": "#chapter-01-macroeconomics-for-strategic-leaders-provenance-first-dashboard-design", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "| Field | Required entry | Why it matters | | :--- | :--- | :--- | | Indicator and unit | Exact series, transformation, currency, nominal/real basis | Prevents comparisons of unlike measures | | Owner and canonical source | Statistical agency, central bank, exchange, or licensed provider | Establishes provenance and usage rights | | As-of and release dates | Data period, release timestamp, next release | Prevents stale-data decisions | | Revision policy | Initial/final release, vintage archive, seasonal adjustment | Makes forecast evaluation reproducible | | Economic channel | Specific customer, supplier, financing, cost, or currency exposure | Connects the measure to the firm | | Validation and false-signal risk | Historical horizon, comparator, misses, structural breaks | Prevents “indicator equals outcome” reasoning | | Decision threshold and owner | Scenario trigger, required corroboration, accountable role | Separates monitoring from automatic action |" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-8", "url": "#chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-8", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Set Up a Monthly Dashboard Create a versioned dashboard containing the fields above. Use official or properly licensed data and retain enough vintage information to reproduce what was known at the time. 2. Watch for model breakdowns Author-created diagnostic: Pre-specify the relationships you expect, the horizon, and what would falsify them. A correlation breakdown can reflect data revisions, a changing regime, different geographic coverage, or noise; it does not identify one cause by itself. Constructed example: Falling customer orders, longer supplier lead times, and wider company credit spreads could justify a downside scenario review. They do not prove a global recession; the team must test data quality, alternative explanations, and firm-specific exposure. 3. Translate to Business Decisions | Observed signal | Confirm before acting | Decision test | | :--- | :--- | :--- | | Demand indicator weakens | Coverage, revision, customer orders, backlog, sector output | Which inventory or capacity decision is reversible, and what evidence would restore the base case? | | Commodity or freight cost rises | Contract exposure, hedge position, duration, substitutes, customer elasticity | How much reaches cash cost and margin under each scenario? | | Currency moves materially | Invoice currency, pass-through, tax, hedge, supplier/customer response | What is the net transaction, translation, and economic exposure? | | Market volatility or credit spreads rise | Funding maturity, lender terms, cash runway, operating demand | Which liquidity or financing action is authorized after covenant and legal review? |" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-8", "url": "#chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-8", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Monitor only indicators tied to a named customer, supplier, financing, cost, or currency exposure. - Record the source, vintage, revision policy, threshold, confirming evidence, and decision owner for every indicator. - Treat a dashboard alert as a prompt for investigation, not as an automatic action." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-8", "url": "#chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-8", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Author-created diagnostic: Indicator relationships can break because of revisions, structural change, geography, coverage, or noise. - A dashboard can create false precision when thresholds are chosen after outcomes are known. - More indicators can increase contradiction and maintenance burden without improving decisions." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-connections-8", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-connections-8", "url": "#chapter-01-macroeconomics-for-strategic-leaders-connections-8", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Combines with Currency Exchange Rate & Global Strategy (Framework 5) and GDP Growth & Business Cycle Analysis (Framework 1) for comprehensive macro view. - Output: Informs Operations and Supply Chain, Scenario Planning, and global expansion decisions. ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-9-supply-demand-shock-analysis", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "9. Supply & Demand Shock Analysis", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-9-supply-demand-shock-analysis", "url": "#chapter-01-macroeconomics-for-strategic-leaders-9-supply-demand-shock-analysis", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Supply & Demand Shock Analysis Crisis Management" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-overview-9", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-overview-9", "url": "#chapter-01-macroeconomics-for-strategic-leaders-overview-9", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Economic shocks can disrupt supply, demand, finance, or several channels at once. Carvalho and colleagues document how the 2011 Great East Japan Earthquake propagated upstream and downstream through supplier and customer networks; the setting is a real case, not proof that every shock follows the same path. [BB-C01-S09]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-9", "url": "#chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-9", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Understand the Two Types of Shocks Supply shock: An event that changes the ability or cost to produce or deliver goods and services. - Examples: Factory fire, port closure, material shortage, natural disaster, or commodity disruption. - In a simple aggregate supply/demand model, a negative supply shift raises the price level and reduces output, holding other conditions constant. [BB-C01-S21] Demand shock: An event that changes willingness or ability to buy. - In the simple model, a positive demand shift raises prices and output; a negative shift reduces output and may reduce prices, subject to price rigidity, capacity, policy response, and mixed shocks. [BB-C01-S21] 2. Build a Constructed Shock-Response Checklist The time bands below are planning buckets, not empirically validated universal deadlines. Assign owners and replace them with contractual, regulatory, business-impact, and risk-appetite requirements where applicable. | Shock | Immediate questions | Near-term tests | Longer-term options to evaluate | | :--- | :--- | :--- | :--- | | Negative supply | Which products, sites, customers, contracts, and cash flows are exposed? Who owns customer, legal, and safety escalation? | Which substitute inputs, suppliers, logistics modes, designs, prices, or allocations are feasible, lawful, and reversible? | What redundancy, inventory, redesign, nearshoring, or integration option has a positive risk-adjusted case? | | Negative demand | Is the decline real, broad, and persistent? What do liquidity, covenants, working capital, and workforce plans permit? | Which forecast, vendor, discretionary-spend, capital, and staffing options are reversible, and what trigger authorizes each? | Which portfolio, capacity, and cost-structure choices remain valuable across scenarios? | | Positive demand | Is the increase temporary or structural? Where are the service, quality, labor, and supplier bottlenecks? | Which price, allocation, shift, supplier, and hiring experiments protect service and remain reversible? | What staged capacity or contract commitment clears the downside case if demand normalizes? | | Finance shock | Which funding, covenant, counterparty, or liquidity exposure is impaired? | Which actions preserve runway without creating a larger refinancing or compliance risk? | What staged financing, liquidity, or operating option remains valuable across scenarios? | 3. Identify Your Vulnerabilities Set the stress-test cadence from business-impact analysis, risk appetite, contract obligations, and regulation rather than using one frequency for every firm: - What if your largest supplier went bankrupt? - What if your top customer sharply reduced orders? - What if a key input price doubled overnight? - What if your primary market entered recession? - What if a new technology made your product obsolete? For each scenario, document: - early-warning and confirmation indicators; - decision owner and required legal/finance/operations approvals; - immediate continuity questions; - mitigation options, triggers, stop rules, and residual risk; and - longer-term adaptation choices and review dates." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-real-world-case-network-propagation-after-the-2011-great-east-japan-earthquake", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Real-world case: Network propagation after the 2011 Great East Japan earthquake", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-real-world-case-network-propagation-after-the-2011-great-east-japan-earthquake", "url": "#chapter-01-macroeconomics-for-strategic-leaders-real-world-case-network-propagation-after-the-2011-great-east-japan-earthquake", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Carvalho and colleagues use firm-level supplier and customer data to show that the earthquake's production effects propagated to connected firms both upstream and downstream. The managerial lesson is bounded: map critical dependencies and test indirect exposure before a crisis. The study does not establish one universal inventory level, diversification rule, or response schedule. [BB-C01-S09]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-9", "url": "#chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-9", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Map critical upstream and downstream dependencies before a disruption occurs. - Pre-authorize reversible continuity options with owners, triggers, stop rules, and escalation paths. - Evaluate redundancy, inventory, redesign, and diversification using risk-adjusted economics rather than slogans." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-9", "url": "#chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-9", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The aggregate supply-and-demand model holds other conditions constant and can obscure simultaneous demand, supply, financial, and policy shocks. [BB-C01-S21] - Evidence from one disaster does not establish a universal inventory level, diversification rule, or response schedule. [BB-C01-S09] - Dependency maps become stale unless procurement, operations, finance, and risk owners maintain them." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-connections-9", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-connections-9", "url": "#chapter-01-macroeconomics-for-strategic-leaders-connections-9", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Early warning signals from Global Economic Indicators Dashboard (Framework 8) and Operations and Supply Chain. - Output: Feeds into Operations and Supply Chain, Scenario Planning, and business-continuity planning. Use Cybersecurity and Risk Management only for cyber and technology-supplier risk. ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-10-yield-curve-recession-forecasting", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "10. Yield Curve & Recession Forecasting", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-10-yield-curve-recession-forecasting", "url": "#chapter-01-macroeconomics-for-strategic-leaders-10-yield-curve-recession-forecasting", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Yield Curve & Recession Forecasting Recession Scenario Inputs" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-overview-10", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-overview-10", "url": "#chapter-01-macroeconomics-for-strategic-leaders-overview-10", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The yield curve plots interest rates across maturities. An inverted yield curve has some short-term yields above longer-term yields, but recession evidence depends on the spread, horizon, sample, and regime. Estrella and Mishkin found useful predictive information in the slope beyond two quarters. This chapter uses the 10-year Treasury rate minus the 3-month Treasury bill rate and treats that specification as a model choice to validate. [BB-C01-S02] Recent Federal Reserve work is an important challenge to simplistic inversion rules. A 2022 note argues that the 10-year/2-year spread adds no incremental information once a near-term forward spread is monitored, and a 2026 note records that the 10-year/3-month spread was negative during 2023 and 2024 without a recession in those years. Use term spreads as probabilistic scenario inputs, not deterministic triggers. [BB-C01-S15] [BB-C01-S16]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-10", "url": "#chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-10", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Understand the Normal Yield Curve Upward sloping: - Short-term rates are below longer-term rates for the selected maturities. - Possible contributors include expected short rates, inflation expectations, and term premiums. Flat: - Selected short- and long-term rates are similar. - Interpretation still requires expected policy, inflation, term-premium, and credit evidence. Inverted: - The selected short-term rate is above the longer-term rate. - It can be consistent with expected policy easing or weaker growth, but term premiums and other forces also matter. It is not a “safe” or “red alert” investment instruction. [BB-C01-S15] 2. Define the spread before using it: 10-year minus 3-month Treasury For consistency within this chapter, calculate: Spread = 10Y Treasury Yield - 3M Treasury Yield . Other spreads answer different questions and require their own validation. [BB-C01-S02] [BB-C01-S16] - Positive spread: Record the level and its historical/regime context. - Near-zero spread: Examine expected policy, term premiums, credit conditions, and confirming indicators. - Negative spread: Increase the weight on downside scenarios only after checking forecast horizon, false positives, and firm evidence. [BB-C01-S02] [BB-C01-S16] 3. Build a Conditional Downside Scenario When a validated spread and other evidence raise downside risk: - update base, downside, and upside demand assumptions; - test liquidity, debt maturity, covenants, working capital, and reversible capital choices with Finance; - identify operational and workforce triggers rather than executing pre-committed cuts; - document customer, supplier, lender, and legal constraints; and - define which new evidence would reduce or increase the downside probability. The NBER does not define a recession as simply one quarter or two quarters of GDP contraction; it evaluates depth, diffusion, and duration across multiple real-activity indicators and dates turning points retrospectively. [BB-C01-S14] 4. Understand the Lag and Limitations - Horizon: The cited forecasting relationship is measured at multi-quarter horizons, not as an immediate timing signal. [BB-C01-S02] - False positives: No leading indicator is perfect. Treat inversion as a scenario input, not a certainty. [BB-C01-S02] [BB-C01-S16] - Model risk: Spread choice, term premiums, sample period, regime change, and data vintage can alter performance. Compare models and preserve misses rather than dismissing them. [BB-C01-S15] [BB-C01-S16]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-10", "url": "#chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-10", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define and validate the spread before monitoring it; do not mix the 10-year/3-month and 10-year/2-year measures. - Use inversion to increase the weight on downside scenarios only when credit, labor, demand, and firm evidence corroborate it. - Preserve forecast vintages and score misses so the model can be recalibrated." }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-10", "url": "#chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-10", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- An inversion that is not followed by recession is evidence about model limits; preserve the forecast vintage and score the prediction. [BB-C01-S15] [BB-C01-S16] - Performance depends on the spread, horizon, sample, term premium, and policy regime. [BB-C01-S15] [BB-C01-S16] - Recent evidence documents a prolonged 10-year/3-month inversion without a recession in 2023 or 2024. [BB-C01-S16]" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-connections-10", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-connections-10", "url": "#chapter-01-macroeconomics-for-strategic-leaders-connections-10", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Interest rate data from Monetary Policy Radar (Framework 7) and economic data from GDP Growth & Business Cycle Analysis (Framework 1) . - Output: Informs Scenario Planning, cash-management protocols, and strategic positioning for downturn. ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-applied-exercise-a-vintage-aware-macro-scenario", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Applied exercise: A vintage-aware macro scenario", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-applied-exercise-a-vintage-aware-macro-scenario", "url": "#chapter-01-macroeconomics-for-strategic-leaders-applied-exercise-a-vintage-aware-macro-scenario", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Choose one public company with disclosed demand, pricing, currency, debt, and input-cost exposure. Build base, upside, and downside cases using official GDP and labor data, a defined Treasury spread, and the company's filings. For every input, record the as-of date, release date, revision status, unit, source, and reason it belongs in the model. For every scenario, record a probability or range, at least one disconfirming indicator, a reversible action, an irreversible decision held back, and the evidence that would change the recommendation. Use Data Analysis and Insights for regression, uncertainty, and causal-interpretation rules. This is a learning exercise, not investment, employment, legal, or treasury advice. ---" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders::chapter-01-macroeconomics-for-strategic-leaders-chapter-summary", "kind": "chapter", "itemSlug": "chapter-01-macroeconomics-for-strategic-leaders", "itemTitle": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "heading": "Chapter summary", "headingId": "chapter-01-macroeconomics-for-strategic-leaders-chapter-summary", "url": "#chapter-01-macroeconomics-for-strategic-leaders-chapter-summary", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "concepts": [ "GDP", "business cycle", "inflation", "interest rates", "monetary policy", "fiscal policy", "exchange rates", "labor markets", "yield curve", "term spread", "Taylor Rule", "supply and demand shocks", "macroeconomic indicators" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter has introduced ten macroeconomic planning frameworks: 1. GDP & Business Cycle Analysis — Estimate firm exposure under alternative cycle scenarios 2. Inflation & Pricing Strategy Matrix — Test pricing options against evidence and constraints 3. Interest Rate & Capital Investment Decision Tree — Integrate financing, risk-adjusted NPV, liquidity, and strategic options 4. Unemployment & Labor Market Analysis — Interpret labor indicators for the relevant role, place, industry, and period 5. Currency Exchange Rate & Global Strategy — Map transaction, translation, and economic exposure before evaluating hedges 6. Fiscal Policy Impact Assessment — Trace policy changes through firm-specific transmission channels 7. Monetary Policy Radar — Distinguish expected policy, surprises, transmission channels, and lags 8. Global Economic Indicators Dashboard — Maintain a provenance-first, vintage-aware external watchlist 9. Supply & Demand Shock Analysis — Map direct and network exposure with owned decision questions 10. Yield Curve & Recession Forecasting — Use a defined term spread as one probabilistic scenario input Key Takeaways: - Separate real from nominal measures and initial releases from revised data. - Treat business-cycle dating as retrospective and forecasts as probabilistic. - Trace each macro signal through a specific firm exposure before choosing an action. - Use multiple indicators, disconfirming evidence, and preserved forecast vintages. - Apply a higher evidence bar to irreversible capital, workforce, pricing, legal, and treasury decisions. - Use the yield curve as one model input and score its false positives rather than treating inversion as a command. Next Chapter: Business Law, Governance, and Ethics — tools for navigating legal and ethical landscapes while building sustainable organizations." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Business Law, Governance, and Ethics", "headingId": "chapter-02-business-law-governance-and-ethics", "url": "#chapter-02-business-law-governance-and-ethics", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-executive-summary", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Executive Summary", "headingId": "chapter-02-business-law-governance-and-ethics-executive-summary", "url": "#chapter-02-business-law-governance-and-ethics-executive-summary", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Author synthesis: Law, governance, and ethics shape which decisions an organization may make, who may make them, which process and evidence are required, and how benefits and harms are allocated. This chapter gives managers issue-spotting and decision-record tools while reserving legal interpretation for qualified counsel and moral judgment for accountable human decision-makers. The tools can expose risks and alternatives; they do not promise compliance, trust, or superior performance. Constructed material: Unless a source or named regulatory record is identified, scenarios, symptoms, policy examples, and numerical illustrations in this chapter are constructed teaching material. They are not reports about a named organization and do not establish a legal, ethical, or performance conclusion. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-1-business-judgment-review-as-a-governance-process", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "1. Business-Judgment Review as a Governance Process", "headingId": "chapter-02-business-law-governance-and-ethics-1-business-judgment-review-as-a-governance-process", "url": "#chapter-02-business-law-governance-and-ethics-1-business-judgment-review-as-a-governance-process", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Business-Judgment Review Director Process & Decision Records" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview", "url": "#chapter-02-business-law-governance-and-ethics-overview", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "In Delaware corporate law, business-judgment review is a rebuttable presumption used when courts review certain board decisions; it is not a promise that a decision or director is protected. The applicable standard depends on the entity, jurisdiction, claim, conflicts, independence, good faith, information considered, and other facts. Smith v. Van Gorkom is a prominent duty-of-care case about an inadequately informed sale process, not the complete doctrine. [BB-C02-S01] For a manager supporting a material board decision, the useful lesson is procedural: build an accurate record of authority, information, alternatives, conflicts, expert input, dissent, approvals, and monitoring. Counsel should determine the governing law and standard of review. [BB-C02-S01]" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the following as a board-process checklist, not a legal safe harbor: First identify the entity's ownership, board, committees, officers, delegated authorities, governing documents, and conflicts. Different entity forms and jurisdictions allocate decision rights differently; the manager's job is to surface the authority and evidence questions for counsel and the authorized decision-maker. 1. Purpose and authority: State the decision requested, who has authority, the applicable governing documents, and the corporation-level interest being evaluated. 2. Information and deliberation: Give the board enough reliable information and time for the decision's importance. This can include: Presenting a well-researched case with data. Outlining alternatives that were considered. Including expert opinions (e.g., from legal, finance, or external consultants). Allowing sufficient time for debate and questioning. 3. Conflicts and independence: Surface potential conflicts promptly so counsel and the board can determine disclosure, recusal, committee, consent, or other requirements. 4. Record and monitoring: Preserve the materials, assumptions, minutes, dissent, approval conditions, owners, and post-decision monitoring plan." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Treat the decision record as an operating control: make authority, evidence, alternatives, conflicts, dissent, approvals, and monitoring visible. - Give counsel and the board a decision that is timely, factually accurate, and explicit about uncertainty rather than a conclusory request for protection. - Re-open the record when facts, conflicts, or the decision horizon change." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The doctrine is jurisdiction- and fact-specific; a checklist cannot establish the applicable standard of review or outcome. - A well-documented process does not cure bad faith, conflicts, unlawful conduct, lack of authority, or materially misleading information." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections", "url": "#chapter-02-business-law-governance-and-ethics-connections", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: A proposal for a major strategic decision, informed by strategy and competitive analysis in Chapter 3 or operations and capacity analysis in Chapter 6. Input: A financial analysis of the proposed decision from financial analysis and valuation in Chapter 4 to demonstrate due diligence. Output: A board-ready decision record for legal review and accountable execution; legal defensibility remains a jurisdiction- and fact-specific conclusion. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-2-intellectual-property-ip-protection-matrix", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "2. Intellectual Property (IP) Protection Matrix", "headingId": "chapter-02-business-law-governance-and-ethics-2-intellectual-property-ip-protection-matrix", "url": "#chapter-02-business-law-governance-and-ethics-2-intellectual-property-ip-protection-matrix", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Intellectual Property (IP) Protection Matrix Innovation Safeguard" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview-2", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview-2", "url": "#chapter-02-business-law-governance-and-ethics-overview-2", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Intellectual property rules can affect whether and how a firm owns, uses, licenses, discloses, or enforces innovation-related assets. This IP issue-routing matrix is a first-pass routing device for specialist analysis, not a diagnosis of eligibility or ownership. The matrix is intentionally operational rather than a complete account of IP economics. Managers should compare the potential incentive, disclosure, timing, licensing, enforcement, and freedom-to-operate tradeoffs with IP counsel rather than infer commercial value from protection alone." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply-2", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply-2", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 2.1. IP issue-routing map. This author-created decision aid distinguishes the questions commonly associated with trademarks, patents, copyright, and trade secrets; it does not determine eligibility, ownership, territorial coverage, or enforceability. The later patent-publication statement is separately supported by [BB-C02-S07]. Text equivalent: Identify whether the business value lies primarily in identity, function, expression, or confidential know-how; then investigate the relevant protection route, ownership, disclosure history, territory, timing, and enforcement economics with IP counsel. Source note: Author-created routing synthesis. [BB-C02-S07] supports only the later patent-publication timing statement. Table 2.1. IP protection routing comparison. Author-created comparison for issue spotting; it does not determine eligibility, ownership, or enforceability. | Asset Type | Protection Method | Key Characteristic | Operator's Action | | :--- | :--- | :--- | :--- | | Brand, logo, or slogan | Trademark | May protect a source identifier; distinctiveness, use, territory, and conflicts matter. | Run a jurisdiction-specific clearance and filing analysis before launch. | | Invention or process | Patent | Eligibility, novelty, non-obviousness, disclosure, inventorship, timing, and territory matter. | Preserve invention records and seek advice before public disclosure or filing decisions. | | Code, article, design, or video | Copyright | May protect original expression, not the underlying idea, system, or method. | Confirm authorship, employment/contractor ownership, licenses, and any assignments. | | Confidential know-how or information | Trade secret | Protection depends on value from secrecy and reasonable measures to preserve secrecy. | Classify the information and test access controls, contracts, training, and incident response. |" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-patent-secrecy-and-speed-are-portfolio-choices", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Patent, secrecy, and speed are portfolio choices", "headingId": "chapter-02-business-law-governance-and-ethics-patent-secrecy-and-speed-are-portfolio-choices", "url": "#chapter-02-business-law-governance-and-ethics-patent-secrecy-and-speed-are-portfolio-choices", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "U.S. utility and plant patent applications are generally published 18 months after the earliest claimed filing date, subject to statutory exceptions and nonpublication rules. Publication timing is not the same as grant timing, and it does not prove that a technology will be obsolete. [BB-C02-S07] A firm should compare patentability, disclosure, detectability of infringement, expected asset life, territorial strategy, secrecy controls, freedom to operate, licensing value, enforcement economics, and speed. Patent, copyright, trademark, trade-secret, contract, and operational strategies can complement one another; counsel should evaluate the portfolio rather than apply a startup-wide default." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-2", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers-2", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Classify the asset before choosing a protection route; identity, function, expression, and confidential know-how create different questions. - Preserve ownership, disclosure, territory, timing, and access facts before launch, hiring, licensing, or public release. - Use the output to improve an IP-counsel conversation and product decision, not to declare an asset protectable." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-2", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques-2", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Protection categories overlap and depend on jurisdiction, facts, eligibility, ownership, registration, secrecy measures, and enforcement economics. - IP protection can create disclosure, cost, timing, and freedom-to-operate tradeoffs; it does not guarantee competitive advantage or commercial value." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections-2", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections-2", "url": "#chapter-02-business-law-governance-and-ethics-connections-2", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: An innovation or new product idea from your R&D or Product Development process. Input: A new brand identity from Marketing (Chapter 5) . Output: An IP issue list that can inform VRIO and competitive analysis in Chapter 3. Protection does not by itself make a resource valuable, rare, hard to imitate, organized, enforceable, or commercially successful. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-troubleshooting-guide-law-governance-and-ethics", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Troubleshooting Guide: Law, Governance, and Ethics", "headingId": "chapter-02-business-law-governance-and-ethics-troubleshooting-guide-law-governance-and-ethics", "url": "#chapter-02-business-law-governance-and-ethics-troubleshooting-guide-law-governance-and-ethics", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The scenarios in this diagnostic are constructed prompts. Test the hypotheses against the facts, applicable law, affected people, and accountable owners; do not treat a symptom or action as a report about a named organization. Symptom: \"Our legal team is seen as the 'Department of No.' They always block our new ideas.\" Possible hypothesis: Legal may be engaged after material design choices are fixed, or the team may not be providing the jurisdiction, facts, risk appetite, alternatives, and decision deadline needed for useful advice. Action to test: Engage Legal early with the customer objective, proposed data and system flows, alternatives, evidence, owners, and explicit questions. Track whether earlier issue spotting changes redesign time, escalation quality, or launch decisions; do not assume the relationship problem has one cause. Symptom: \"Our employees roll their eyes at our company values. They feel like meaningless corporate jargon.\" Possible hypotheses: Stated values may conflict with incentives, leader behavior, promotion decisions, or employees' observed experience. Action to test: Compare each value with observable behavior, decision rights, incentives, complaints, promotion criteria, and consequences. Employment counsel and HR should review any assessment or disciplinary change for consistency, documentation, and disparate-impact risk. Symptom: \"We received credible evidence of potentially unlawful or unethical labor practices at a key supplier.\" Possible hypotheses: The allegation, contractual rights, supply-chain tier, jurisdiction, severity, and immediate worker or customer risks may differ from the initial information. Action: Preserve evidence; activate the approved investigation and escalation process; involve procurement, operations, communications, and counsel; assess immediate harm and legal duties; and choose proportionate interim controls. Suspension, remediation, disclosure, or termination should follow the facts and governing obligations rather than an automatic rule. See Chapter 6 for supplier continuity and Chapter 19 for enterprise-risk controls. Symptom: \"A senior executive was accused of a conflict of interest on a major deal.\" Possible hypotheses: The allegation may involve a disclosed and managed interest, an undisclosed conflict, an appearance issue, or inaccurate information. Action: Preserve relevant records and escalate through the approved board, compliance, and counsel process. Counsel and independent decision-makers should determine investigation scope, interim restrictions, recusal, disclosure, and remediation; avoid prejudging the allegation. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-3-contract-law-essentials-for-managers", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "3. Contract Law Essentials for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-3-contract-law-essentials-for-managers", "url": "#chapter-02-business-law-governance-and-ethics-3-contract-law-essentials-for-managers", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Contract Law Essentials for Managers Risk Management" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview-3", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview-3", "url": "#chapter-02-business-law-governance-and-ethics-overview-3", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The six-clause checklist below is an author-created contract risk review aid, not a published legal framework, contract template, or clause recommendation. Many business relationships are structured through contracts—with customers, suppliers, employees, and partners—alongside statutes, regulations, common law, and non-contractual duties. An operator's role is to provide the commercial facts, quantify exposures, identify dependencies, and escalate legal interpretation. Contract analysis depends on the governing law, statutes, commercial rules, cross-border requirements, and facts. Contract structure can influence incentives and dispute processes without guaranteeing an outcome. The six clauses below are prompts for commercial issue spotting, not a substitute for counsel's analysis." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply-3", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply-3", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Liability & Indemnification - What It Means: Who pays if something goes wrong? - Key Questions: - Are liability caps reasonable relative to the contract value? - Is there mutual indemnification or one-sided exposure? - Does it cover third-party claims? - Questions for the deal team: Model plausible loss paths; insurance; service credits; indemnities; exclusions; privacy, security, safety, and regulatory exposure; statutory limits; and bargaining leverage. Finance, risk, security, and counsel should approve the allocation. No single fee multiple is a universal default. 2. Termination Rights - What It Means: How and when can either party exit? - Key Questions: - Termination for convenience vs. cause only? - What is the notice period (30/60/90 days)? - Are there early termination penalties? - Questions for the deal team: Compare convenience and cause rights, cure periods, notice, transition assistance, data return/deletion, stranded cost, continuity, minimum commitments, and reciprocal consequences. The appropriate exit structure depends on the relationship and bargaining context. 3. Intellectual Property Ownership - What It Means: Who owns the work product created? - Key Questions: - Do not assume a “work made for hire” label transfers every deliverable; have counsel check employee or contractor status, the statutory category, signed terms, assignment language, background IP, third-party components, data rights, and license-back provisions. - For software: Who owns the code, data, and improvements? - Are there license-back provisions? - Questions for the deal team: Distinguish background IP, deliverables, modifications, data, models, feedback, open-source components, licenses, assignment, residual knowledge, infringement risk, and termination effects. Ownership is not always the economically best or legally available structure. 4. Payment Terms - What It Means: When and how payment occurs - Key Questions: - Net 30, 60, or 90 days? (Affects cash flow) - Payment upon milestone completion or delivery? - Late payment penalties? - Questions for the deal team: Evaluate bargaining power, cash conversion, financing cost, supplier resilience, applicable prompt-payment rules, milestone acceptance, disputes, taxes, currency, and late-payment remedies. Avoid improving one party's working capital by creating an unmanaged continuity risk. 5. Warranties & Representations - What It Means: What promises are you making about your product/service? - Key Questions: - Are you warranting specific performance metrics (e.g., 99.9% uptime)? - Can you realistically deliver on these warranties? - What happens if you breach? (Links to liability) - Questions for the deal team: Ensure promises match evidence, operating capability, product documentation, remedies, exclusions, regulatory duties, and monitoring. Counsel should assess how an efforts standard is interpreted under the governing law; the phrase is not a universal escape clause. 6. Governing Law & Dispute Resolution - What It Means: Where and how are disputes resolved? - Key Questions: - Which state/country's law governs? (Favorable jurisdiction?) - Arbitration, court litigation, expert determination, escalation, or a staged combination? Cost, speed, confidentiality, appeal, discovery, interim relief, enforceability, and multiparty disputes vary. - Are legal fees recoverable by the prevailing party? - Questions for the deal team: Compare the connection to the chosen law and forum, mandatory statutes, enforceability, remedies, confidentiality, interim relief, dispute size, counterparties, and cross-border execution. Counsel should design the clause; neither a home forum nor arbitration is universally preferable." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-3", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers-3", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Translate clauses into loss paths, dependencies, operational owners, evidence requirements, and decision deadlines. - Compare the proposed allocation with insurance, service levels, data and security exposure, continuity needs, and bargaining leverage. - Escalate clause language that changes rights, remedies, ownership, disclosure, or exit conditions to counsel before signature." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-3", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques-3", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- No clause set, fee multiple, notice period, forum, or remedy is universally appropriate; governing law and bargaining context matter. - Commercially attractive wording can still be unenforceable, operationally impossible, or inconsistent with statute, regulation, or the rest of the agreement." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections-3", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections-3", "url": "#chapter-02-business-law-governance-and-ethics-connections-3", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Understanding of business risk from cybersecurity and risk management in Chapter 19 and negotiation facts from the accountable deal team. Output: A documented allocation of commercial responsibilities, rights, remedies, uncertainty, and escalation for counsel and accountable owners. Whether the agreement reduces exposure is an empirical and legal question. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-4-corporate-governance-models-shareholder-vs-stakeholder", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "4. Corporate Governance Models (Shareholder vs. Stakeholder)", "headingId": "chapter-02-business-law-governance-and-ethics-4-corporate-governance-models-shareholder-vs-stakeholder", "url": "#chapter-02-business-law-governance-and-ethics-4-corporate-governance-models-shareholder-vs-stakeholder", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Corporate Governance Models Strategic Orientation" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview-4", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview-4", "url": "#chapter-02-business-law-governance-and-ethics-overview-4", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Corporate governance allocates authority and accountability through applicable law, organizational documents, boards, owners, executives, and controls. Shareholder primacy and stakeholder theory are competing lenses for corporate purpose and decision consequences; management cannot simply choose a philosophy that displaces fiduciary duties or other applicable law. The comparison below is an author synthesis, not a selectable legal duty. The shareholder-stakeholder debate draws on distinct scholarly and practitioner traditions and remains contested. Stakeholder governance should be evaluated through the employee, customer, community, and financial measures that matter to the business, rather than assumed to produce a universal performance premium. [BB-C02-S04] [BB-C02-S05]" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-the-two-models", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "The Two Models", "headingId": "chapter-02-business-law-governance-and-ethics-the-two-models", "url": "#chapter-02-business-law-governance-and-ethics-the-two-models", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 2.2. Corporate-purpose and governance lenses. Author-created comparison; neither column selects a legal duty or displaces governing law. | Dimension | Shareholder Primacy | Stakeholder Capitalism | | :--- | :--- | :--- | | Primary emphasis | Owners' financial interests within the governing legal framework | Consequences for owners and other affected parties | | Stakeholders analyzed | Owners, with other parties considered through strategy, contract, regulation, or risk | Owners, employees, customers, suppliers, communities, and environmental systems | | Decision question | How does this choice affect durable owner value, duties, and constraints? | How are benefits, harms, rights, voice, and dependencies distributed? | | Time horizon | Can be short or long; the lens does not require quarterly optimization | Can be short or long; stakeholder language does not guarantee long-term action | | Measurement challenge | Avoid stock-price-only proxies and unmanaged externalities | Make tradeoffs, weights, baselines, and decision authority explicit |" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply-4", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply-4", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Do not select a legal duty from this table. Instead: 1. Confirm the entity, jurisdiction, governing documents, board authority, and applicable duties with counsel. 2. Map owners and other parties affected by the decision, including rights, contracts, dependencies, externalities, and ability to bear harm. 3. State the time horizon and decision criteria; distinguish survival constraints from a rhetorical preference for short- or long-term action. 4. Test alternatives against financial resilience, legal duties, stakeholder consequences, reversibility, and monitoring evidence. 5. Document unresolved tradeoffs and who is authorized to decide them. Implementation questions include board appointment rights, independence, skills, conflicts, committee needs, and any stakeholder representation required or permitted by the governing regime. A decision dashboard can combine financial resilience with material customer, employee, supplier, community, environmental, compliance, and control measures, but the metrics do not resolve the underlying value judgment. Incentive measures should be tested for controllability, gaming, verification, time horizon, and unintended harm." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-contrarian-thinking-the-false-dichotomy", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: The False Dichotomy", "headingId": "chapter-02-business-law-governance-and-ethics-contrarian-thinking-the-false-dichotomy", "url": "#chapter-02-business-law-governance-and-ethics-contrarian-thinking-the-false-dichotomy", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This framing need not be a false choice. Evidence on employee satisfaction indicates that how firms treat employees can be relevant to long-run value, but the business effect should be evaluated in context. [BB-C02-S05] The practical question is how a legally authorized decision-maker evaluates durable value and distributes benefits, risks, rights, and voice under uncertainty." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-4", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers-4", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use both lenses to surface decision criteria, affected parties, time horizons, rights, dependencies, and externalities. - Make tradeoffs, weights, decision authority, and monitoring measures explicit instead of hiding them behind a purpose statement. - Confirm that the selected action fits the entity's governing documents, duties, and authorization." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-4", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques-4", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Shareholder and stakeholder labels do not themselves determine fiduciary duties, legal authority, or the correct decision. - Stakeholder language can become symbolic unless the organization assigns decision rights, measures outcomes, and accepts accountable tradeoffs." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections-4", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections-4", "url": "#chapter-02-business-law-governance-and-ethics-connections-4", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Company mission, values, and execution choices from strategy execution in Chapter 8. Output: Governance philosophy shapes KPI design in Chapter 8, Framework 5's compensation analysis, and Framework 6's ESG analysis. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-5-agency-theory-executive-compensation", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "5. Agency Theory & Executive Compensation", "headingId": "chapter-02-business-law-governance-and-ethics-5-agency-theory-executive-compensation", "url": "#chapter-02-business-law-governance-and-ethics-5-agency-theory-executive-compensation", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Agency Theory & Executive Compensation Alignment Mechanisms" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview-5", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview-5", "url": "#chapter-02-business-law-governance-and-ethics-overview-5", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Agency theory examines conflicts that can arise when one party delegates authority to another and their information, incentives, risk, or objectives differ. Compensation is one governance mechanism among monitoring, selection, authority, disclosure, culture, contracts, ownership, and markets; any design can create intended and unintended incentives. Agency theory, developed by Jensen and Meckling (1976), explains why compensation design matters for agency costs and incentive alignment. [BB-C02-S02] Bebchuk and Fried analyze compensation both as a potential response to agency problems and as a possible product of managerial influence that can yield weak or perverse incentives. Boards should therefore test how plan design, governance, and time horizons could shape intended and unintended behavior rather than assume that nominal pay-for-performance creates alignment. [BB-C02-S03]" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-the-agency-problem", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "The Agency Problem", "headingId": "chapter-02-business-law-governance-and-ethics-the-agency-problem", "url": "#chapter-02-business-law-governance-and-ethics-the-agency-problem", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Core Conflict: - Shareholders want: Long-term value creation, prudent risk management - Potential agency hypotheses to test include: short-term compensation seeking, job-security concerns, effort shirking, or empire building; these are not universal executive motives. How Misalignment Manifests: - Executives take excessive risks (upside accrues to them via options; downside to shareholders) - Executives manipulate earnings to hit bonus targets (accounting gimmicks) - Executives pursue growth for growth's sake (empire building increases their status/salary, but not shareholder value)" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply-5", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply-5", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. The Three Components Table 2.3. Illustrative compensation-plan components. Author-created diagnostic; the components and questions are not universal recommendations. | Component | Illustrative role in a plan | Purpose | Questions for the compensation committee | | :--- | :--- | :--- | :--- | | Base salary | Fixed compensation | Attract and retain talent without making all pay contingent | What market, role, geography, internal equity, and risk-bearing assumptions support the level? | | Annual incentive | Shorter-horizon contingent compensation | Link a portion of pay to defined outcomes and conduct | Are measures controllable, auditable, balanced, and resistant to gaming? What downside or clawback applies? | | Long-term incentive | Multi-period equity or cash award | Expose the executive to longer-horizon value and risk | Do vesting, holding, performance, dilution, liquidity, tax, and risk-taking effects fit the strategy? | 2. Key Design Principles - Vesting and holding periods: Match the time horizon to the strategy and risk; a longer period can change incentives but does not by itself prevent short-term behavior. - Clawback clauses: Test whether recovery rights are authorized, enforceable, administrable, and proportionate to the relevant misconduct or restatement. - Performance hurdles: Compare outcome, conduct, risk, and time-horizon measures; a target does not prove controllability or alignment. - Upside and downside exposure: Test whether dilution, concentration, liquidity, tax, and risk-taking effects create unacceptable behavior rather than assuming a compensation cap solves the problem. - Peer benchmarking: Use comparable data cautiously; benchmarking can ratchet pay and does not prove fairness, alignment, or causal effectiveness. 3. Avoid Common Pitfalls Design question 1: Convex incentives and downside exposure - Hypothesis to test: Options can increase sensitivity to upside while limited downside, wealth, employment risk, portfolio concentration, exercise price, dilution, and governance also affect behavior. - Options to compare: Different equity instruments, cash, holding periods, performance conditions, downside mechanisms, and ownership guidelines. No instrument guarantees a “balanced” risk appetite. Pitfall 2: Purely Financial Metrics - Problem: Ignores customer satisfaction, employee retention, innovation, ethics - Option to test: Use a limited set of financial, strategic, risk, conduct, and stakeholder measures with explicit weights, verification, and override rules. The weights require board judgment. Design question 3: Target setting and gaming - Hypothesis to test: Annual resets can create information and negotiation incentives, while multi-year targets can become stale or encourage different forms of gaming. - Options to compare: Multi-period measures, relative performance, ranges, board discretion with documented limits, clawbacks, and regular evidence review." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-5", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers-5", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Treat compensation as a hypothesis about behavior, not proof that incentives are aligned. - Test controllability, measurement quality, time horizon, gaming, downside exposure, concentration, conduct, and unintended effects. - Pair pay design with governance, monitoring, disclosure, and correction mechanisms owned by the board or its committee." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-5", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques-5", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Incentive plans can be gamed, can shift risk, and can reward measured outputs that diverge from durable value or lawful conduct. - Benchmarking and performance conditions are inputs to judgment, not evidence that a plan is fair, optimal, or causally effective." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections-5", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections-5", "url": "#chapter-02-business-law-governance-and-ethics-connections-5", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Company valuation from Financial Analysis (Chapter 4) to determine equity grant values. Input: Strategic priorities from OKRs (Chapter 8) to set performance metrics. Output: A board-owned incentive hypothesis and monitoring plan linked to strategy (Chapter 3); observed behavior and outcomes must be tested rather than presumed. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-6-the-esg-environmental-social-governance-framework", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "6. The ESG (Environmental, Social, Governance) Framework", "headingId": "chapter-02-business-law-governance-and-ethics-6-the-esg-environmental-social-governance-framework", "url": "#chapter-02-business-law-governance-and-ethics-6-the-esg-environmental-social-governance-framework", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "ESG Framework Sustainable Value Creation" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview-6", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview-6", "url": "#chapter-02-business-law-governance-and-ethics-overview-6", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Materiality is the decision about which sustainability-related risks, opportunities, impacts, and evidence matter for a defined audience and regime. “ESG” groups environmental, social, and governance topics, but it is not one uniform measurement or legal regime. The investment-market lineage represented by the Who Cares Wins initiative is one strand of a broader set of sustainability, reporting, governance, and regulatory traditions. Managerial analysis should begin with the applicable regime, decision audience, materiality lens, measurement boundary, and controls needed to substantiate claims. Do not infer financial outperformance from an ESG label alone. [BB-C02-S12] Investor initiatives and reporting standards are not interchangeable; evidence is most informative when it distinguishes the materiality lens, topic, boundary, operating context, and outcome rather than assuming uniform valuation or cost-of-capital effects. [BB-C02-S12] [BB-C02-S13] [BB-C02-S14]" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-the-three-pillars", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "The Three Pillars", "headingId": "chapter-02-business-law-governance-and-ethics-the-three-pillars", "url": "#chapter-02-business-law-governance-and-ethics-the-three-pillars", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Environmental (E): - Climate impact (carbon emissions, energy use) - Resource management (water use, waste, recycling) - Pollution and environmental degradation - Biodiversity impact Social (S): - Labor practices (fair wages, working conditions, diversity & inclusion) - Human rights (supply chain labor practices) - Customer welfare (product safety, data privacy) - Community relations (local economic impact, philanthropy) Governance (G): - Board structure (independence, diversity, expertise) - Executive compensation (alignment with long-term value) - Shareholder rights - Business ethics and anti-corruption" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply-6", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply-6", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The sequence below is an original managerial synthesis, not an ESG reporting standard, materiality definition, or compliance procedure. Apply only after identifying the governing regime and qualified owners. Step 1: Materiality Assessment Do not collapse materiality into one meaning. IFRS S1 focuses on sustainability-related risks and opportunities that could reasonably affect an entity's prospects for capital-provider decisions, while EU sustainability reporting also addresses company impacts on people and the environment. Confirm the governing definition, entity scope, effective date, and time horizon rather than importing one regime's test into another. [BB-C02-S13] [BB-C02-S14] Constructed prompts—not sector conclusions—include greenhouse-gas emissions and spills for an energy business, privacy and governance for a technology business, or labor and water use for an apparel business. Each topic still requires entity-specific evidence, boundary, stakeholder and financial analysis, and current legal review. Step 2: Establish Definitions, Boundaries, Baselines, and Controls Define the reporting entity, value-chain boundary, methodology, data owner, baseline period, restatement policy, and evidence control before setting a target. IFRS S1's governance, strategy, risk-management, metrics, and targets content areas provide one investor-focused reporting reference; they are not a universal operating checklist. The figures below are a constructed planning example, not benchmarks. [BB-C02-S13] Table 2.4. Constructed ESG planning example. These are example metrics and target-setting prompts, not benchmarks. | Pillar | Example Metrics | Target | | :--- | :--- | :--- | | Environmental | Scope 1 and 2 greenhouse-gas emissions, with stated methodology and boundary | Set after baseline quality, transition options, dependencies, and applicable commitments are reviewed | | Social | Workforce representation, pay, safety, turnover, or other material outcome with lawful definitions | Set after legal, workforce, causal, and measurement review | | Governance | Board independence, skills, conflicts, control findings, or speak-up outcomes | Set in light of entity law, listing rules, risk, and governance design | Step 3: Integrate into Business Operations Assign material sustainability risks, opportunities, data, controls, and claims to the relevant operating owners rather than isolating them in a communications function. Procurement might assess supplier evidence and remedies; product teams might evaluate lifecycle impacts and tradeoffs; HR might review workforce outcomes and incentives; and finance might evaluate capital instruments, covenants, use-of-proceeds controls, and assurance. Each option requires its own legal, financial, operational, and evidence analysis. Step 4: Disclose Progress Transparently Identify the reporting regime before selecting a framework. Depending on jurisdiction and purpose, this may include IFRS Sustainability Disclosure Standards incorporating industry-based guidance, European Sustainability Reporting Standards, securities-regulator requirements, or voluntary commitments. These regimes differ in audience, materiality, scope, assurance, and legal effect; confirm the current requirements at the reporting date. [BB-C02-S13] [BB-C02-S14]" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-contrarian-thinking-avoid-greenwashing", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: Avoid \"Greenwashing\"", "headingId": "chapter-02-business-law-governance-and-ethics-contrarian-thinking-avoid-greenwashing", "url": "#chapter-02-business-law-governance-and-ethics-contrarian-thinking-avoid-greenwashing", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Unsubstantiated, vague, or selectively framed environmental and social claims can create consumer-protection, securities, contractual, and reputation risk. Focus reporting on material issues, use defined and auditable measures, state boundaries and uncertainty, preserve contrary evidence, and route public claims through legal and control review. The appropriate number of priorities depends on the enterprise and its obligations; “authenticity” is not a substitute for substantiation. [BB-C02-S20] [BB-C02-S13] [BB-C02-S14]" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-6", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers-6", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the reporting or claims regime, audience, entity boundary, baseline, controls, and accountable owner before setting targets or publishing claims. - Separate operational impact, investor relevance, legal exposure, and communications value; they may overlap without being identical. - Preserve uncertainty and contrary evidence so that a materiality decision remains auditable and revisable." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-6", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques-6", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- ESG labels do not create a universal metric, legal duty, causal pathway, or performance premium. - Materiality, boundary, assurance, and reporting requirements vary by regime and date; a voluntary framework cannot substitute for current legal analysis." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections-6", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections-6", "url": "#chapter-02-business-law-governance-and-ethics-connections-6", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Stakeholder priorities from Framework 4 and risk assessment from cybersecurity and risk management in Chapter 19. Output: The ESG analysis can inform marketing and customer analytics in Chapter 5, investor communications, and current reporting review; it does not replace any of them. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-7-ethical-decision-making-models", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "7. Ethical Decision-Making Models", "headingId": "chapter-02-business-law-governance-and-ethics-7-ethical-decision-making-models", "url": "#chapter-02-business-law-governance-and-ethics-7-ethical-decision-making-models", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Ethical Decision-Making Models Moral Reasoning" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview-7", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview-7", "url": "#chapter-02-business-law-governance-and-ethics-overview-7", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Ethical decision-making addresses choices where legal permission, commercial value, duties, and moral consequences may diverge. This framework provides a structured approach to ethical reasoning, moving beyond gut feelings to a defensible decision-making process. [BB-C02-S11] Ethical decision-making frameworks draw on philosophical traditions and behavioral-ethics research. A formal process can make affected parties, assumptions, conflicts, escalation, dissent, and accountability more visible, but it does not mechanically produce an ethically correct answer or performance outcome. [BB-C02-S11]" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply-7", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply-7", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Author-created decision aid: The four-step sequence and its publicity test are an original managerial synthesis informed by behavioral-ethics research. They organize questions and documentation; they are not a universal ethical standard or a pass/fail test. Step 1: Identify the Ethical Dimension Many \"business\" problems have hidden ethical dimensions. Ask: - Who could be harmed by this decision? - Are there competing duties or loyalties in conflict? - Would I be comfortable if this decision were public knowledge? Step 2: Apply Multiple Ethical Lenses The following table is an original comparative synthesis for discussion, not a claim that each tradition has one uncontested definition or decision rule. [BB-C02-S11] Table 2.5. Author-created comparison of ethical lenses. The questions, strengths, and limits are a discussion aid, not a canonical taxonomy or decision rule. | Ethical Framework | Key Question | Strengths | Weaknesses | | :--- | :--- | :--- | :--- | | Utilitarian (Consequentialist) | \"Which option produces the greatest good for the greatest number?\" | Pragmatic, measurable | Can justify harming minorities for majority benefit | | Deontological (Duty-Based) | \"Is this action inherently right or wrong, regardless of outcome?\" | Principled, consistent | Can be rigid, impractical | | Virtue Ethics | \"What would a person of good character do?\" | Focus on moral development | Subjective, culturally dependent | | Justice/Fairness | \"Does this decision treat all parties fairly?\" | Promotes equity | Difficult to define \"fair\" | | Rights-Based | \"Does this decision respect fundamental human rights?\" | Protects individuals | Can conflict with collective good | | Care Ethics | \"How do relationships, vulnerability, dependence, and responsibilities shape the choice?\" | Surfaces relational and contextual harms | Can be difficult to scale or reconcile with impartial rules | Step 3: Run the \"Publicity Test\" Ask: \"Would I be comfortable if this decision were on the front page of the New York Times?\" - If yes → Record why, then continue through rights, duties, consequences, justice, care, legal constraints, dissent, and authorization. Comfort with publicity is not approval. - If no → Identify whether the problem is harm, secrecy, weak reasoning, legitimate confidentiality, or another concern; revise or justify the option and continue the analysis. Step 4: Make a Decision and Document Reasoning - Do not count how many lenses an option “passes.” Explain conflicts among duties, rights, consequences, character, justice, care, and stakeholder claims, including who bears uncertainty and harm. - Document your reasoning (creates accountability and precedent) - Communicate the decision transparently to stakeholders The decision process works best as a revisable gate sequence, not a one-step judgment call. Figure 2.2. Ethical-decision deliberation loop. This original synthesis turns multiple ethical lenses into an iterative process; it does not imply that publicity or consensus proves an action is ethical. [BB-C02-S11] Text equivalent: Identify potential harm and affected parties, examine the alternatives through several ethical lenses, test whether the reasoning can withstand informed public scrutiny, revise weak options, then document the authorized decision, dissent, communication, and monitoring. Source note: Author-created synthesis informed by behavioral-ethics research. [BB-C02-S11] supports the multi-level framing and the limitation that a process does not guarantee a correct outcome." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-constructed-example-the-layoff-dilemma", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Constructed example: The \"Layoff\" dilemma", "headingId": "chapter-02-business-law-governance-and-ethics-constructed-example-the-layoff-dilemma", "url": "#chapter-02-business-law-governance-and-ethics-constructed-example-the-layoff-dilemma", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scenario: Your company must cut costs. You can either: - Option A: Lay off 10% of workforce (100 people) to preserve profitability - Option B: Cut everyone's salary by 10% (no layoffs) Ethical Analysis: Table 2.6. Constructed layoff/pay-cut decision lenses. The questions apply to either option; the exercise does not recommend one option. | Decision lens | Questions to test for either option | | :--- | :--- | | Consequences | Which harms, benefits, probabilities, time horizons, and second-order effects follow for affected groups? | | Justice | What process, criteria, burden distribution, voice, and remedy would be defensible? | | Rights and duties | Which legal and moral rights, contracts, duties, and legitimate expectations apply? | | Virtue and care | What would responsible, candid, compassionate leadership require, including treatment during and after the decision? | Decision record: The exercise does not establish that Option B is preferable. A responsible decision would test legal and contractual constraints, liquidity saved, role criticality, pay floors, distributional impact, disparate effects, employee voice, business continuity, duration, reversibility, and alternatives such as reduced hours, redeployment, voluntary programs, financing, or staged reductions. The accountable decision-maker should document why the selected option is necessary and how harms will be monitored. All quantities in the scenario are constructed, not recommended thresholds." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-7", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers-7", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Make affected parties, harms, duties, conflicts, dissent, uncertainty, authorization, and remedies visible before acting. - Use multiple lenses to explain disagreement and revise weak options; do not count “passes” as an ethical score. - Document the reasoning, communication, monitoring, and decision owner so the process can be revisited." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-7", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques-7", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ethical lenses conflict and depend on contested judgments about rights, harms, duties, virtues, and distribution. - A publicity test or documented process does not prove that an action is ethical, legal, effective, or acceptable to affected people." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections-7", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections-7", "url": "#chapter-02-business-law-governance-and-ethics-connections-7", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Company values and behavior from organizational behavior and leadership (Chapter 7) and legal constraints from Contract Law (Framework 3) . Output: A documented ethical analysis that can expose disagreement, assumptions, affected parties, and remedy needs; outcomes for trust, engagement, and reputation remain empirical questions. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-8-rawlsian-fairness-challenge-author-adaptation", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "8. Rawlsian Fairness Challenge (Author Adaptation)", "headingId": "chapter-02-business-law-governance-and-ethics-8-rawlsian-fairness-challenge-author-adaptation", "url": "#chapter-02-business-law-governance-and-ethics-8-rawlsian-fairness-challenge-author-adaptation", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Rawlsian Fairness Challenge Fairness Evaluation" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview-8", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview-8", "url": "#chapter-02-business-law-governance-and-ethics-overview-8", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The veil of ignorance is part of Rawls's original position: a device of representation for reasoning about principles of justice for society's basic structure under restrictions on knowledge intended to represent impartiality and equality. The managerial question below is an adaptation, not Rawls's full theory: would a policy remain defensible if the decision-maker did not know which affected position they would occupy? [BB-C02-S15] Rawls's theory of justice provides foundational material for evaluating distributional fairness. [BB-C02-S15] This adaptation can surface distributional concerns, but it does not yield a unique policy answer, reproduce the original position, establish legality, or guarantee an employee or conflict outcome." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply-8", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply-8", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Thought Experiment: Before implementing a new policy (compensation structure, benefits, promotion criteria), ask: \"If I didn't know whether I would be: - A senior executive or an entry-level employee - A high performer or an average performer - A parent or childless - Healthy or dealing with chronic illness ...would I still support this policy?\" If yes → Record why the policy remains acceptable from positions unlike your own, then test other ethical and legal constraints. If no → Identify who bears the disadvantage and redesign or justify it; the thought experiment alone does not determine legality or fairness." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-constructed-examples", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Constructed examples", "headingId": "chapter-02-business-law-governance-and-ethics-constructed-examples", "url": "#chapter-02-business-law-governance-and-ethics-constructed-examples", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed example 1: Performance bonus structure Proposed Policy: Bonuses are paid only to the top 10% of performers (large bonus), with nothing for the other 90%. Veil of Ignorance Test: \"If I didn't know whether I'd be in the top 10% or the bottom 90%, would I support this?\" - Questions surfaced: Are ratings reliable and comparable? What behavior does the tournament encourage? Who bears measurement error? What outcome is the plan intended to produce? - Alternative to test: Compare a tiered plan, team and individual measures, and no-bonus alternatives for cost, motivation, gaming, internal equity, and lawful administration. The sample tiers are illustrative, not a fairness result. Constructed example 2: Parental leave policy Proposed Policy: 6 months paid leave for biological mothers only. Veil of Ignorance Test: \"If I didn't know whether I'd be a mother, father, or adoptive parent, would I support this?\" - Questions surfaced: Which caregiving, recovery, bonding, disability, and job-protection needs are recognized; who is excluded; and what laws, benefits, collective agreements, and operational constraints apply? - Alternative to test: Develop inclusive options with HR, affected employees, finance, operations, and employment counsel. The veil-of-ignorance exercise informs the discussion but does not establish the lawful duration or eligibility rule. Constructed example 3: Remote work policy Proposed Policy: Only senior directors (VP+) can work remotely full-time; everyone else must be in-office. Veil of Ignorance Test: \"If I didn't know whether I'd be an executive or a mid-level employee, would I support this?\" - Questions surfaced: What job requirements, accommodations, geographic rules, team dependencies, performance evidence, and employee impacts justify different treatment? - Alternative to test: Compare role-based, team-based, location-based, and individual-exception policies using transparent criteria and legal/HR review; no single work arrangement is inherently fair." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-8", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers-8", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the thought experiment to expose who bears measurement error, disadvantage, uncertainty, and limited voice. - Compare role-based alternatives against evidence, legal constraints, operational feasibility, and remedies rather than treating discomfort as proof. - Record whose perspective is missing and which accountable owner must decide." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-8", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques-8", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The adaptation is not Rawls's complete theory, a legal test, or a calculator that produces one fair policy. - It can obscure relevant differences or practical constraints unless paired with evidence from affected people, operations, finance, HR, and counsel." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections-8", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections-8", "url": "#chapter-02-business-law-governance-and-ethics-connections-8", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Works in conjunction with Ethical Decision-Making Models (Framework 7) and Stakeholder Governance (Framework 4) . Output: A documented distributional-fairness challenge that can inform policy design alongside legal, operational, financial, and employee evidence; it does not guarantee engagement, retention, or cultural outcomes. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-9-ai-ethics-risk-assessment-matrix", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "9. AI Ethics & Risk Assessment Matrix", "headingId": "chapter-02-business-law-governance-and-ethics-9-ai-ethics-risk-assessment-matrix", "url": "#chapter-02-business-law-governance-and-ethics-9-ai-ethics-risk-assessment-matrix", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "AI Ethics & Risk Assessment Matrix Responsible AI" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview-9", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview-9", "url": "#chapter-02-business-law-governance-and-ethics-overview-9", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "AI risk triage asks how a system's use, affected people, deployment context, capability, data, degree of reliance, and controls shape risks involving discrimination, opacity, privacy, security, safety, labor, market power, and human autonomy. [BB-C02-S08] [BB-C02-S09] NIST AI RMF 1.0 is a voluntary, use-case-agnostic framework organized around Govern, Map, Measure, and Manage ; NIST states that version 1.0 is being revised. [BB-C02-S08] The EU AI Act is Regulation (EU) 2024/1689, with risk-based duties and phased application. Whether a system falls within a legal category requires analysis of the regulation, role, use, exclusions, and applicable date. [BB-C02-S09] Neither framework proves that completing a checklist will reduce incidents or increase trust." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply-9", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply-9", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Author-created triage prompts: The six principles and two-axis matrix below organize questions about purpose, harm, autonomy, evidence, ownership, and remedy. They are not NIST functions, an EU AI Act classification, or a universal ethical standard. [BB-C02-S08] [BB-C02-S09] 1. Transparency and explainability - Question: What information do operators, affected people, reviewers, and regulators need for the use and risk? - Control options to assess: Interpretable models, system and data documentation, user notice, reason codes, uncertainty communication, independent review, and meaningful human authority. The appropriate combination depends on the use and applicable law. [BB-C02-S08] - Escalation signal: Consequential use with no tested way for operators or affected people to understand, challenge, or remedy material errors. 2. Fairness and harmful bias - Question: Which groups, outcomes, error types, legal protections, historical patterns, and allocation decisions must be evaluated? - Control options to assess: Data and label review, subgroup performance and allocation analysis, causal and qualitative investigation, accessibility testing, affected-person input, and remedy. Group definitions and legal tests are context-specific. [BB-C02-S08] - Escalation signal: Material outcome or error disparities without a defensible purpose, measurement basis, investigation, owner, or remedy. 3. Privacy and data protection - Question: What data is used, for which purpose and lawful basis, with what provenance, retention, access, transfer, security, and data-subject controls? Consent is not the only possible lawful basis, and “anonymized” is a conclusion requiring evidence. [BB-C02-S06] - Control options to assess: Minimize data where required and appropriate; test de-identification claims; document access, retention, deletion, and transfer controls. [BB-C02-S06] [BB-C02-S08] - Red flag to investigate: Using data for a materially different purpose without assessing the legal basis, notice, rights, contracts, and model/data risks. 4. Accountability and human roles - Question: Who can authorize, challenge, stop, override, investigate, and remediate the system, and do they have information, competence, time, and authority? - Control options to assess: Allocate accountable roles, preserve decision and change records, define escalation and stop conditions, and test whether human review is meaningful rather than ceremonial. [BB-C02-S08] - Escalation signal: A consequential decision with no competent person able to challenge, stop, investigate, or remedy it. 5. Safety and security - Question: Which foreseeable failures, misuse, attacks, environmental changes, and downstream dependencies create material harm? - Control options to assess: Threat modeling, misuse and failure testing, red teaming where useful, fail-safe design, change control, monitoring, incident response, and sector-specific validation. [BB-C02-S08] - Escalation signal: Safety-critical or security-sensitive deployment without evidence proportionate to plausible harm and applicable sector requirements. 6. Purpose, necessity, and distribution of impact - Question: Is AI necessary for the objective, which alternatives exist, and how are benefits, burdens, errors, voice, and remedies distributed? - Control options to assess: Compare non-AI and lower-risk alternatives; include affected functions and people; assess labor and societal impacts without assuming augmentation or replacement is inherently preferable. [BB-C02-S08] - Red flag to investigate: An engagement or optimization objective that ignores foreseeable harm, vulnerable users, manipulation, or remedy." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-the-ai-risk-assessment-matrix", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "The AI Risk Assessment Matrix", "headingId": "chapter-02-business-law-governance-and-ethics-the-ai-risk-assessment-matrix", "url": "#chapter-02-business-law-governance-and-ethics-the-ai-risk-assessment-matrix", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 2.3. Constructed AI triage map. This original teaching diagram uses autonomy and severity of harm to prompt escalation. It is not the legal classification system in the EU AI Act and is not a substitute for the NIST AI RMF's contextual risk process. [BB-C02-S08] [BB-C02-S09] Text equivalent: Place a proposed use on two questions—how much consequential action the system can take and how severe plausible harm could be—then increase evidence, independent challenge, human authority, and approval as either dimension rises. Legal classification requires a separate jurisdiction-specific analysis. Before deployment, use the visual only for initial triage: Source note: Constructed decision rule. [BB-C02-S08] and [BB-C02-S09] support the external framework and legal boundaries, not the axes, coordinates, or thresholds. Table 2.7. Constructed AI risk-triage levels. The categories and examples are illustrative; legal classification requires current, context-specific analysis. | Risk Level | Criteria | Control questions and options | Example | | :--- | :--- | :--- | :--- | | Lower initial concern | Limited capability, exposure, reliance, and plausible harm in the stated context | Document purpose, data, testing, ownership, monitoring, and escalation proportional to risk | A locally deployed spam filter may fit, subject to data and security facts | | Material concern | Meaningful financial, privacy, security, access, or reputation effects | Add affected-group analysis, independent challenge, human authority, incident response, and approval | Personalization or fraud support can range widely by use and consequence | | High consequence | Potential effect on rights, safety, livelihood, essential services, or regulated decisions | Require specialist legal/regulatory analysis, rigorous validation, meaningful human governance, monitoring, and stop/remedy capability | Employment, credit, healthcare, or safety uses require context-specific analysis | | Prohibited or unacceptable | Prohibited by applicable law or outside the organization's approved risk boundary | Do not deploy; preserve the legal/risk decision record | Determine from current law and policy, not from this illustrative matrix |" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-9", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers-9", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Start with purpose, affected people, reliance, plausible harm, accountable roles, evidence, and remedy—not with a model label. - Increase independent challenge, human authority, testing, monitoring, and approval as consequence or uncertainty rises. - Keep legal classification, ethical judgment, product ownership, security controls, and incident response connected but distinct." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-9", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques-9", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- NIST AI RMF is voluntary and the constructed matrix is not the EU AI Act's legal classification system or a universal risk scale. [BB-C02-S08] [BB-C02-S09] - A completed assessment cannot prove safety, fairness, compliance, or trust; data, context, law, and system behavior can change." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-applied-regulatory-case-facial-recognition-in-retail", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Applied regulatory case: facial recognition in retail", "headingId": "chapter-02-business-law-governance-and-ethics-applied-regulatory-case-facial-recognition-in-retail", "url": "#chapter-02-business-law-governance-and-ethics-applied-regulatory-case-facial-recognition-in-retail", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "In December 2023, the U.S. Federal Trade Commission announced a complaint and proposed stipulated order concerning Rite Aid's use of facial-recognition surveillance. The FTC alleged that the retailer lacked reasonable safeguards and that false-positive matches caused consumer harm; the proposed order included a five-year prohibition on using facial recognition for surveillance. The announcement also stated that court and bankruptcy approvals were still required at that stage. [BB-C02-S10] The managerial lesson is not that every biometric use has the same legal result: record the use purpose, affected people, error evidence, vendor controls, notice, complaint process, human response, stop rule, and approval status, and distinguish allegations from final adjudicated findings." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections-9", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections-9", "url": "#chapter-02-business-law-governance-and-ethics-connections-9", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Data governance from Data Privacy Framework (Framework 10) and ethical principles from Ethical Decision-Making (Framework 7) . Output: An AI risk record informing product decisions, AI strategy (Chapter 16), cybersecurity (Chapter 19), and AI and data ethics (Chapter 20); completing it does not guarantee a safe or compliant deployment. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-10-privacy-and-gdpr-issue-spotting-checklist", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "10. Privacy and GDPR Issue-Spotting Checklist", "headingId": "chapter-02-business-law-governance-and-ethics-10-privacy-and-gdpr-issue-spotting-checklist", "url": "#chapter-02-business-law-governance-and-ethics-10-privacy-and-gdpr-issue-spotting-checklist", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Privacy and GDPR Issue-Spotting Checklist Privacy by Design" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview-10", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview-10", "url": "#chapter-02-business-law-governance-and-ethics-overview-10", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Privacy-by-design issue spotting starts with the people, data, entity roles, processing purpose, geography, sector, contracts, and applicable law. The GDPR can apply to processing in the context of an EU establishment and to certain offerings or monitoring involving people in the Union; it should not be described simply as “Europe.” California and other jurisdictions use different definitions, rights, thresholds, exemptions, and enforcement structures. Determine scope with current counsel before applying this checklist. [BB-C02-S06] The GDPR has applied since 25 May 2018. Article 5 sets principles including lawfulness, fairness, transparency, purpose limitation, data minimization, accuracy, storage limitation, integrity/confidentiality, and accountability. Consent is one lawful basis among those in Article 6, not a universal requirement. Data-protection by design and by default appears in Article 25. [BB-C02-S06]" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply-10", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply-10", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Lawfulness, Fairness, Transparency - Identify and document the applicable lawful basis; Article 6 includes consent, contract, legal obligation, vital interests, public task, and legitimate interests, subject to the provision's conditions. Special-category and criminal-offence data require additional analysis. - Be transparent about what data you collect and why - Provide clear, accessible privacy policies (not legal jargon) 2. Purpose Limitation - Collect data only for specified, explicit purposes - Assess compatibility, transparency, and the applicable legal basis before a new purpose; new consent is not the only possible outcome. 3. Data Minimization - Collect only the data you actually need (not \"nice to have\") - Example: If you're running a newsletter, you need email—not home address, phone, or birthdate 4. Accuracy - Keep data accurate and up-to-date - Provide mechanisms for users to correct their data 5. Storage Limitation - Don't keep data longer than necessary - Set retention policies based on purpose, legal obligations, and risk. 6. Integrity & Confidentiality (Security) - Assess technical and organizational measures proportionate to the nature, scope, context, purposes, state of the art, cost, and risk. Article 32 lists examples rather than mandating one technology in every case. [BB-C02-S06] - Options can include encryption or pseudonymization, access controls, resilience, restoration, testing, audit, and other measures justified by the risk analysis. 7. Accountability - Demonstrate compliance (documentation, audits) - Determine whether Articles 37–39 require a Data Protection Officer and preserve the analysis." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-the-operator-s-gdpr-issue-spotting-checklist", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "The operator's GDPR issue-spotting checklist", "headingId": "chapter-02-business-law-governance-and-ethics-the-operator-s-gdpr-issue-spotting-checklist", "url": "#chapter-02-business-law-governance-and-ethics-the-operator-s-gdpr-issue-spotting-checklist", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Phase 1: Data Mapping (Before You Build) - [ ] Document what personal data you collect (name, email, location, behavior, etc.). [BB-C02-S06] - [ ] Document each purpose, lawful basis, affected people, controller/processor role, and any additional conditions for sensitive data. - [ ] Document where data is stored (cloud provider, region, security controls) - [ ] Document who has access (internal teams, third-party vendors) - [ ] Document how long you retain data (set retention periods) Phase 2: Legal Basis & Consent (Design) - [ ] If relying on consent, test whether it is freely given, specific, informed, unambiguous, demonstrable, and as easy to withdraw as to give; determine whether explicit consent is required for the processing at issue. [BB-C02-S06] - [ ] If relying on another basis, document the elements, balancing or necessity assessment, and required notice or objection controls. - [ ] Apply the age and parental-consent rules in the applicable jurisdiction. [BB-C02-S06] Phase 3: User Rights Implementation (Build) - [ ] Map access, rectification, erasure, restriction, portability, objection, and automated-decision rights to their distinct conditions, exceptions, identity checks, deadlines, and recipients. Access and portability are not the same right, and erasure is not absolute. [BB-C02-S06] - [ ] Identify profiling or automated individual decision-making, the role it plays, the information and human intervention available, and the separate legal and operational analysis required before relying on an automated outcome. [BB-C02-S06] - [ ] Decide whether a Data Protection Impact Assessment is required before high-risk processing, assign an owner, document the assessment, and define review and escalation triggers. [BB-C02-S06] Phase 4: Security & Breach Response - [ ] Apply the Article 32 risk analysis and document which confidentiality, integrity, availability, resilience, restoration, testing, access, encryption, pseudonymization, or other measures are appropriate; do not treat any single control as universally sufficient or mandatory. [BB-C02-S06] - [ ] Establish a breach assessment and response plan. Article 33 generally requires controller notification to the competent supervisory authority without undue delay and, where feasible, within 72 hours after awareness unless the breach is unlikely to risk people's rights and freedoms; Article 34 has a separate high-risk communication test and exceptions. [BB-C02-S06] Phase 5: Vendor Management - [ ] Inventory processors, sub-processors, joint-controller questions, instructions, security evidence, assistance duties, audit rights, deletion/return, incident terms, and Article 28 contract requirements where applicable. - [ ] For non-EU transfers, document the destination, applicable mechanism, supplementary measures, transfer-risk analysis, vendor roles, and counsel's current assessment; a transfer mechanism alone is not a universal approval. [BB-C02-S06] Phase 6: Documentation & Training - [ ] Map Articles 12–14 and other applicable notice duties to the collection context, source, role, recipients, transfer, retention, rights, and exceptions; determine which notice must be provided, when, and by whom. [BB-C02-S06] - [ ] Document data-processing activities where required, including the GDPR Article 30 record. [BB-C02-S06] - [ ] Assess role-based training, instructions, confidentiality, and evidence needed for the processing and risk; align it with applicable duties and internal controls. - [ ] Apply the Article 37 DPO tests, including public-authority status and relevant core-activity, scale, monitoring, and special-category/criminal-data conditions. [BB-C02-S06]" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-administrative-fine-ceilings-are-not-automatic-outcomes", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Administrative-fine ceilings are not automatic outcomes", "headingId": "chapter-02-business-law-governance-and-ethics-administrative-fine-ceilings-are-not-automatic-outcomes", "url": "#chapter-02-business-law-governance-and-ethics-administrative-fine-ceilings-are-not-automatic-outcomes", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Article 83 provides different maximum administrative-fine bands. Depending on the infringement, the ceiling can be €10 million or, for an undertaking, up to 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; the higher band can be €20 million or up to 4%, whichever is higher. Authorities must consider the Article 83 factors, and other corrective powers or member-state rules may also matter. Confirm the current official text, scope, and regulator decision before using a fine figure in a policy or presentation. [BB-C02-S06]" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-10", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers-10", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Build a dated data map that names purposes, roles, lawful-basis questions, notices, retention, access, transfers, vendors, security, and response owners. - Use the checklist to surface evidence and decisions for counsel, privacy specialists, security, and product teams before launch or material change. - Treat rights, incidents, vendor changes, and new uses as lifecycle events that can reopen the analysis." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-10", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques-10", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The checklist is not a compliance certification, legal opinion, universal deadline set, or substitute for jurisdiction-specific analysis. - GDPR obligations depend on scope, role, facts, exceptions, regulator interpretation, and current law; a documented control plan can still be incomplete or ineffective." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections-10", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections-10", "url": "#chapter-02-business-law-governance-and-ethics-connections-10", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Applicable legal requirements and security controls from cybersecurity and risk management in Chapter 19. Output: A documented privacy issue list and control plan for counsel and accountable owners. It can inform a launch decision but does not by itself establish compliance, eliminate risk, or create customer trust. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-11-legal-lifecycle-issue-spotting-for-managers", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "11. Legal Lifecycle Issue-Spotting for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-11-legal-lifecycle-issue-spotting-for-managers", "url": "#chapter-02-business-law-governance-and-ethics-11-legal-lifecycle-issue-spotting-for-managers", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Legal Lifecycle Risk Gate Issue Routing, Not Legal Advice" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-overview-11", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-02-business-law-governance-and-ethics-overview-11", "url": "#chapter-02-business-law-governance-and-ethics-overview-11", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This module is educational issue-spotting, not legal advice. It uses selected U.S. federal, Delaware-corporation, and EU competition examples to teach routing. It does not state the law for every U.S. state, EU member state, industry, entity, worker, security, product, transaction, or insolvency process. Before relying on any rule, record the relevant legal entity, place of incorporation, people and worker locations, customer and product locations, transaction venue, governing documents and contracts, regulator or filing regime, and decision date. Counsel should confirm the current rule and advise on the facts; managers should preserve accurate facts, evidence, alternatives, owners, and timing. The question for a manager is therefore not “Does this checklist make the action legal?” It is “What fact could trigger a legal duty, who must assess it, and what must pause until that assessment is complete?”" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-how-to-apply-11", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-02-business-law-governance-and-ethics-how-to-apply-11", "url": "#chapter-02-business-law-governance-and-ethics-how-to-apply-11", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 2.8. Legal lifecycle issue lanes and escalation gates. Author-created routing matrix using selected jurisdictional anchors; it is not a legal taxonomy or conclusion. | Issue lane | Selected jurisdiction anchor | Manager-facing trigger facts | Counsel or specialist gate before action | | :--- | :--- | :--- | :--- | | Antitrust / competition | U.S. federal: the FTC distinguishes agreements among competitors from exclusionary single-firm conduct; price fixing, market division, and bid rigging are described as almost always illegal. EU: TFEU Articles 101 and 102 address anticompetitive agreements or concerted practices and abuse of a dominant position. [BB-C02-S16] [BB-C02-S17] | Competitor contact about price, wages, customers, territories, capacity, bids, strategic plans, or other competitively sensitive information; trade-association activity; exclusivity, tying, access, self-preferencing, or platform rules; joint ventures, licensing, acquisitions, and information sharing. The U.S. agencies' 2025 worker guidelines also flag wage-fixing, no-poach, compensation-information exchange, and other practices for fact-specific antitrust assessment; their list does not make every listed activity unlawful. [BB-C02-S26] | Pause substantive competitor discussions and sensitive-data exchange until competition counsel defines participants, purpose, agenda, safeguards, recordkeeping, and permitted scope. Route exclusivity, platform conduct, labor-market conduct, collaboration, and transaction documents for jurisdiction-specific review before commitment. Use Chapter 3 for market analysis and Chapter 18 for platform economics—not as legal tests. | | Employment / worker classification | U.S. federal FLSA example only: status turns on the economic reality of the relationship, not the contract label alone. The Department of Labor's 2024 regulation remains relevant to private litigation, while Wage and Hour Division enforcement has followed different interim guidance since May 2025; the Department proposed another rule in February 2026. State, tax, benefits, immigration, leave, discrimination, collective-labor, and other regimes may use different tests. [BB-C02-S18] [BB-C02-S19] | Hiring or managing “contractors” like employees; controlling schedule, method, pricing, or exclusivity; supplying core tools; indefinite or core-business work; cross-border or multi-state work; reclassification, discipline, leave, pay, surveillance, organizing activity, or termination. | Have employment counsel and the relevant tax/HR owners assess the actual working relationship and every applicable regime before engagement, conversion, material role change, or termination. Do not treat a contractor agreement, incorporated vendor, or tax form as dispositive. Connect the resulting role and control design to Chapter 7. | | Consumer claims / product safety and liability | U.S. federal examples: the FTC expects a reasonable basis for objective express and implied advertising claims before dissemination. CPSC guidance says businesses subject to its statutes can have rapid reporting duties when they obtain reportable information about a potentially hazardous or noncompliant consumer product; reporting does not itself mean a recall is required. Product-liability theories, defenses, warnings, and damages vary by jurisdiction. [BB-C02-S20] [BB-C02-S21] | Performance, comparative, health, safety, environmental, AI, or “tests prove” claims; design or warning changes; complaints, near misses, injuries, warranty patterns, quality-control failures, noncompliance, or supplier defects; entry into a new product or customer jurisdiction. | Before launch, the accountable claims owner and counsel should approve the exact claim, audience, evidence, qualifications, and retention record. On a safety signal, preserve complaints and chronology, stop unsafe activity where warranted, and escalate immediately to product-safety counsel and the designated reporting owner; do not wait for a completed causal investigation if a reporting clock may be running. Use Chapter 14 for market execution and Chapter 21 for lifecycle controls. | | Securities / disclosure | U.S. public-company anchor: Form 8-K is a current-report form for specified events, and Regulation FD addresses certain selective disclosures of material nonpublic information by covered issuers. Other public and private offerings, exemptions, antifraud duties, exchange rules, and non-U.S. regimes differ. [BB-C02-S22] [BB-C02-S23] | Financing, forecasts, major contracts, acquisitions, leadership or auditor changes, impairments, defaults, cybersecurity incidents, bankruptcy or receivership, significant product events, investor communications, analyst conversations, employee trading, or accidental external disclosure. | Managers should report potentially material events and nonpublic information promptly to securities counsel, finance, investor relations, and the disclosure committee. They should not decide materiality, filing obligations, disclosure timing, trading clearance, or audience on their own. Preserve who knew what and when. Connect fundraising mechanics to Chapter 15 and incident facts to Chapter 19. | | Entity authority | Delaware corporation example: §141 generally places management of the corporation's business and affairs under the board's direction; §142 ties officer titles and duties to bylaws or board resolutions. Actual authority can also depend on the certificate, bylaws, resolutions, delegations, contracts, and other law. [BB-C02-S24] | Signing a material contract, guarantee, debt, equity issuance, acquisition, asset sale, related-party transaction, dividend, settlement, IP transfer, bank instruction, or government filing; ambiguity about which entity owns an asset or employs a person. | Before signature or performance, confirm the correct entity, governing law, board or committee authority, officer delegation, approval thresholds, conflicts, conditions, and evidence of approval. Apparent business seniority is not a substitute for the authority record. Use Chapter 12 to align the resulting authority and escalation path with client and contract governance. | | Distress / insolvency | U.S. federal bankruptcy example: U.S. Bankruptcy Code Chapter 11 generally permits reorganization; a debtor in possession usually continues operating with statutory duties and court or U.S.-trustee oversight. Chapter 7, state-law processes, receivership, sector regimes, and cross-border cases differ. [BB-C02-S25] | Liquidity runway compression, missed payroll or taxes, covenant breach, payment default, threatened enforcement, inability to pay debts when due, emergency financing, unusual asset transfer, insider payment, customer prepayment exposure, creditor preference, wind-down, or board concern about solvency. | Escalate early to restructuring counsel, the board, finance, and the appropriate turnaround or insolvency specialists—before moving assets, preferring stakeholders, taking emergency financing, or announcing a plan. Preserve cash forecasts, obligations, decisions, and communications. Do not infer that “bankruptcy” automatically means liquidation or that ordinary operating discretion is unchanged. | The anchors above are intentionally narrow. For example, a worker can be treated differently under wage, tax, benefits, and state-law tests; a product can fall under a regulator other than the CPSC; and a private financing can create securities obligations without Form 8-K applying. The manager's control is a reliable routing record, not a universal legal conclusion." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-the-lifecycle-risk-gate", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "The lifecycle risk gate", "headingId": "chapter-02-business-law-governance-and-ethics-the-lifecycle-risk-gate", "url": "#chapter-02-business-law-governance-and-ethics-the-lifecycle-risk-gate", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 2.4. Legal lifecycle and escalation gate. This author-created routing visual shows where the six issue lanes commonly arise and the evidence-preserving gate that should precede a consequential action. It does not determine governing law, materiality, liability, reportability, authority, solvency, or the legal outcome. The inline markers identify representative anchors; the canonical citation registry records the full S16–S26 source family. Text equivalent: At every stage—from formation and authorization through workforce design, product and claims, financing and disclosure, monitoring and incidents, and restructuring or exit—first re-identify the entity, jurisdictions, roles, governing documents, and decision date. If a competition, worker, consumer/product, disclosure, authority, or distress trigger appears, pause the affected action, preserve facts and chronology, notify the accountable legal and business owners, obtain the required advice and approval, then document the decision, conditions, and monitoring. Source note: Author-created synthesis based on the issue categories and official sources [BB-C02-S16] [BB-C02-S17] [BB-C02-S18] [BB-C02-S19] [BB-C02-S20] [BB-C02-S21] [BB-C02-S22] [BB-C02-S23] [BB-C02-S24] [BB-C02-S25] [BB-C02-S26]. The visual is a management-control aid, not a statement that one sequence or gate satisfies any law." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-a-reusable-legal-escalation-record", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "A reusable legal escalation record", "headingId": "chapter-02-business-law-governance-and-ethics-a-reusable-legal-escalation-record", "url": "#chapter-02-business-law-governance-and-ethics-a-reusable-legal-escalation-record", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For a material trigger, capture one short record before the decision moves forward: 1. Action and deadline: What is proposed, what would become difficult to reverse, and when? 2. Scope facts: Which entity, people, products, counterparties, investors, and jurisdictions are involved? 3. Trigger and uncertainty: Which fact raised competition, workforce, consumer/product, disclosure, authority, or distress risk? What remains unknown? 4. Evidence and chronology: What documents, messages, complaints, tests, approvals, forecasts, or incident records exist, and when were they created or received? 5. Owners and gate: Which business executive, counsel, regulator-facing owner, board or committee, and specialist must act before release, signature, payment, communication, or shutdown? 6. Decision record: What advice and approvals were received, what conditions or limits apply, who monitors them, and when will the analysis be refreshed?" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-constructed-exercise-one-company-six-legal-lanes", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Constructed exercise — one company, six legal lanes", "headingId": "chapter-02-business-law-governance-and-ethics-constructed-exercise-one-company-six-legal-lanes", "url": "#chapter-02-business-law-governance-and-ethics-constructed-exercise-one-company-six-legal-lanes", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A constructed company sells connected workplace hardware and subscription analytics in the United States and European Union. It plans a competitor interoperability meeting, uses long-term “independent contractors” in core operations, advertises a safety improvement, receives two overheating complaints, briefs selected investors before a financing, discovers the proposed contract is assigned to the wrong subsidiary, and projects that it may miss payroll in six weeks. Prepare a one-page escalation record. For each fact, identify: (1) the entity and jurisdictions; (2) the potential trigger without stating a legal conclusion; (3) the evidence and chronology to preserve; (4) the business and legal owners; (5) the action that pauses; and (6) the advice, approval, report, or monitoring needed to reopen the gate. Then identify which issues interact—for example, whether a product incident also creates disclosure, contract, insurance, and distress implications. The exercise is successful when the decision owners and unknowns are visible, not when the learner declares the company “compliant.”" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-so-what-for-managers-11", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-11", "url": "#chapter-02-business-law-governance-and-ethics-so-what-for-managers-11", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the gate to identify a trigger, preserve the facts and chronology, pause the affected action, and route the issue to the accountable legal and business owners. - Re-scope every issue by entity, jurisdiction, role, governing document, regulator, and decision date before relying on an anchor. - Keep the manager's output to facts, unknowns, owners, questions, approvals, and monitoring; legal conclusions remain with qualified counsel." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-limits-and-critiques-11", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-11", "url": "#chapter-02-business-law-governance-and-ethics-limits-and-critiques-11", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The six lanes are selected teaching anchors, not a complete legal taxonomy or a substitute for current specialist advice. - A pause-and-route process cannot determine materiality, liability, reportability, authority, solvency, or the outcome of a dispute." }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-connections-11", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-02-business-law-governance-and-ethics-connections-11", "url": "#chapter-02-business-law-governance-and-ethics-connections-11", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Inputs: Market definition and competitor facts from Chapter 3 ; operating roles from Chapter 7 ; claims and launch evidence from Chapters 14 and 21 ; financing and runway from Chapter 15 ; platform conduct from Chapter 18 ; and incident facts from Chapter 19 . Output: A dated legal escalation record containing scope facts, evidence, unknowns, owners, paused actions, counsel questions, approvals, and monitoring. It supports—not replaces—legal advice and accountable business judgment. ---" }, { "id": "chapter-02-business-law-governance-and-ethics::chapter-02-business-law-governance-and-ethics-chapter-summary", "kind": "chapter", "itemSlug": "chapter-02-business-law-governance-and-ethics", "itemTitle": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "heading": "Chapter Summary", "headingId": "chapter-02-business-law-governance-and-ethics-chapter-summary", "url": "#chapter-02-business-law-governance-and-ethics-chapter-summary", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter has equipped you with eleven essential frameworks for navigating law, governance, and ethics: 1. Business-judgment review - Prepare an informed, conflict-aware decision record without promising legal protection 2. IP issue routing - Distinguish asset types and questions requiring specialist analysis 3. Contract risk review - Quantify commercial exposures and reserve clause design for the accountable deal team and counsel 4. Corporate-purpose lenses - Surface owner and stakeholder consequences without choosing a legal duty from a framework 5. Agency theory and compensation - Test incentive alignment, gaming, risk shifting, time horizon, and verification 6. Sustainability and materiality - Define the applicable regime, boundary, evidence, and controls before making claims 7. Ethical decision-making - Explain conflicts among ethical lenses rather than count “passes” 8. Veil of ignorance - Challenge distributional fairness without treating a thought experiment as a legal or policy calculator 9. AI risk governance - Combine contextual risk assessment, accountable roles, evidence, monitoring, and legal classification 10. GDPR issue spotting - Map scope, roles, purposes, lawful bases, rights, security, transfers, and regulator-facing evidence 11. Legal lifecycle routing - Spot competition, workforce, consumer/product, disclosure, authority, and distress triggers and route them through a documented human-counsel gate Key Takeaways: - Legal checklists are issue-spotting tools , not legal conclusions or safe harbors - Engage legal early with facts, alternatives, evidence, owners, jurisdictions, and explicit questions - Governance lenses inform analysis but do not displace entity law, fiduciary duties, contracts, or authorized decision rights - Material ESG issues should be assessed against the firm's strategy and operating context. [BB-C02-S13] [BB-C02-S14] - Privacy requirements should be built into design rather than treated as an after-the-fact task [BB-C02-S06] - Ethical processes can clarify expectations, conflicts, escalation, dissent, and accountability, but they do not mechanically produce one correct answer. [BB-C02-S11] Next Chapter: Strategy & Competitive Analysis - Tools for identifying competitive advantages and formulating winning strategies." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Strategy and Competitive Analysis", "headingId": "chapter-03-strategy-and-competitive-analysis", "url": "#chapter-03-strategy-and-competitive-analysis", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-executive-summary", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Executive Summary", "headingId": "chapter-03-strategy-and-competitive-analysis-executive-summary", "url": "#chapter-03-strategy-and-competitive-analysis-executive-summary", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter uses ten frameworks inside one decision workflow: frame the problem, diagnose external structure and internal capabilities, generate alternatives, test value and feasibility, choose a guiding policy with explicit tradeoffs, stress-test it under uncertainty, and specify coherent actions. No matrix certifies a “winning” strategy; each produces hypotheses that require evidence, economics, and accountable judgment. [BB-C03-S03] [BB-C03-S16] Author synthesis: The decision workflow, integrated strategy record, and recommendations in this chapter are author-created teaching devices that organize the cited frameworks; they are not a validated causal model or a substitute for case-specific evidence. Constructed material: Examples, anonymous products, diagrams, scores, and decision records are illustrative unless a named source or company record is identified. Label a real case and verify its facts before relying on it. The framework sequence is: external structure, internal resources and capabilities, growth options, organizational alignment, uncertainty, platform economics, and the managerial-economics tests that connect diagnosis to choice." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-integrated-case-northstar-industrial-analytics-constructed", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Integrated Case: Northstar Industrial Analytics (Constructed)", "headingId": "chapter-03-strategy-and-competitive-analysis-integrated-case-northstar-industrial-analytics-constructed", "url": "#chapter-03-strategy-and-competitive-analysis-integrated-case-northstar-industrial-analytics-constructed", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Northstar is a fictional industrial-analytics provider whose largest customer segment is asking for a lower-priced monitoring package while a new entrant offers a simpler product. You are the general manager. The evidence packet is incomplete by design: win/loss interviews suggest price sensitivity but have a small, non-random sample; the finance team reports contribution margin is positive but service costs rise sharply at peak utilization; engineering has a reusable data pipeline but limited implementation capacity; and two competitors are testing similar features. No source establishes the “right” choice. Choose among three constructed options: (A) defend a differentiated reliability position for a narrow regulated segment; (B) launch a lower-priced, self-service package with staged capacity; or (C) partner with a channel or platform that supplies distribution but reduces control over the customer relationship. A no-action and exit/harvest comparison is required. Decision prompt: Produce a two-page strategy record that states the focal problem and boundary, diagnosis and disconfirming evidence, guiding policy and rejected alternatives, three coherent actions with owners, one quantified assumption table, a two-scenario stress test with signposts, and a reversible first commitment. The assessor should be able to identify what would change the choice, when it will be reviewed, and what would cause the team to redesign or stop. ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-1-porter-s-five-forces-analysis", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "1. Porter's Five Forces Analysis", "headingId": "chapter-03-strategy-and-competitive-analysis-1-porter-s-five-forces-analysis", "url": "#chapter-03-strategy-and-competitive-analysis-1-porter-s-five-forces-analysis", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Porter's Five Forces Analysis Industry Analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-overview", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-03-strategy-and-competitive-analysis-overview", "url": "#chapter-03-strategy-and-competitive-analysis-overview", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Porter's Five Forces analyzes mechanisms through which entrants, suppliers, buyers, substitutes, and rivalry can affect prices, costs, investment requirements, and bargaining power. Industry structure matters, but firms within an industry can differ, boundaries can change, and complements, regulation, and ecosystem design may require separate analysis. [BB-C03-S01] [BB-C03-S02]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-how-to-apply", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-03-strategy-and-competitive-analysis-how-to-apply", "url": "#chapter-03-strategy-and-competitive-analysis-how-to-apply", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define the boundary and decision: State the customer need, product or service, geography, value-chain position, time horizon, complements, and decision being informed. Test at least one alternative boundary. 2. Trace each mechanism: Record evidence, trend, uncertainty, and the mechanism connecting each force to price, cost, investment, or bargaining power. Threat of New Entrants: How easy is it for new players to enter? High barriers (e.g., patents, high capital costs, network effects) are attractive for incumbents. Bargaining Power of Buyers: How much power do your customers have? High power (e.g., low switching costs, many alternatives) is unattractive. Bargaining Power of Suppliers: How concentrated and differentiated are critical inputs, and what switching, integration, capacity, or hold-up options exist? Threat of Substitutes: How easily can customers solve their problem with a different type of solution? (e.g., using Zoom is a substitute for business travel). High threat is unattractive. Rivalry Among Existing Competitors: How intense is the competition? High rivalry (e.g., many competitors, slow industry growth) is unattractive. 3. Synthesize without false precision: Do not average ordinal scores. Identify the few mechanisms that materially change the decision, the evidence that could disconfirm them, and the actions that could alter or avoid those mechanisms. [BB-C03-S01]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-academic-citations-evidence", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Academic Citations & Evidence", "headingId": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence", "url": "#chapter-03-strategy-and-competitive-analysis-academic-citations-evidence", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Seminal Work: - Porter, M. E. (1979). How Competitive Forces Shape Strategy. Harvard Business Review , 57(2), 137-145. [BB-C03-S01] - Porter's article introduced the five-force structure for analyzing competition beyond direct rivals. Use the source for the framework and mechanisms, not as proof that industry structure mechanically determines a particular firm's profitability. Scope note: This chapter uses the 1979 source for the Five Forces structure and mechanisms. Technology, complements, regulation, and ecosystem effects are treated as manager hypotheses to test, not as claims that rely on unregistered later sources." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers", "url": "#chapter-03-strategy-and-competitive-analysis-so-what-for-managers", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the force diagnosis to choose where to compete, what mechanism to change, and which assumptions require evidence. - Convert material forces into an owner, signpost, and option to monitor, redesign, partner, or stop. - Test at least one alternative industry boundary before committing resources." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques", "url": "#chapter-03-strategy-and-competitive-analysis-limits-and-critiques", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Industry structure is not a profitability guarantee; test firm position, complements, regulation, and execution evidence. - Do not average ordinal force scores or treat a convenient market boundary as the economic truth." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-connections", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-03-strategy-and-competitive-analysis-connections", "url": "#chapter-03-strategy-and-competitive-analysis-connections", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires macroeconomic context from Chapter 1 (Macroeconomics) and an understanding of the political and legal environment from PESTLE Analysis (This Chapter) . Input: Data on competitor market share and customer concentration from your Marketing & Sales teams. Output: An understanding of industry attractiveness that directly informs your Go-to-Market Strategy (Chapter 14) . If the industry is unattractive, this analysis provides the \"why\" for pursuing a Blue Ocean Strategy (This Chapter) . ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-2-vrio-framework-dynamic-capabilities", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "2. VRIO Framework & Dynamic Capabilities", "headingId": "chapter-03-strategy-and-competitive-analysis-2-vrio-framework-dynamic-capabilities", "url": "#chapter-03-strategy-and-competitive-analysis-2-vrio-framework-dynamic-capabilities", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "VRIO Framework & Dynamic Capabilities Competitive Advantage Analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-overview-2", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-03-strategy-and-competitive-analysis-overview-2", "url": "#chapter-03-strategy-and-competitive-analysis-overview-2", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "VRIO examines whether a resource or capability is valuable, rare, difficult to imitate, and supported by the organization. Barney's 1991 VRIN conditions formalized resource attributes associated with sustained advantage; the familiar VRIO teaching sequence is a later operationalization. Use it to structure hypotheses about value creation and capture, not to certify a resource as permanently defensible. [BB-C03-S04]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-03-strategy-and-competitive-analysis-how-to-apply-2", "url": "#chapter-03-strategy-and-competitive-analysis-how-to-apply-2", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For each major resource or capability (e.g., \"our brand,\" \"our proprietary algorithm,\" \"our elite engineering team\"), ask four sequential questions: 1. Valuable? Does it help you exploit an opportunity or neutralize a threat? If not, it's a weakness. 2. Rare? Do few or no competitors possess it? If not, you have competitive parity, not an advantage. 3. Inimitable? Is it difficult or costly for competitors to copy? This is the key to defensibility. Sources of inimitability include unique historical path (e.g., years of data collection), causal ambiguity (it's unclear why it works), or social complexity (your unique culture). 4. Organized? Do you have the management systems, processes, and culture to fully exploit this resource? If not, it's an \"unrealized\" advantage. A resource that appears to satisfy all four questions is a candidate explanation for advantage. Test customer value, appropriability, substitutes, complements, imitation paths, erosion, and whether observed performance has another cause." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-evidence-based-contrarian-thinking-the-limits-of-vrio-the-rise-of-dynamic-capabilities", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Evidence-Based Contrarian Thinking: The Limits of VRIO & The Rise of Dynamic Capabilities", "headingId": "chapter-03-strategy-and-competitive-analysis-evidence-based-contrarian-thinking-the-limits-of-vrio-the-rise-of-dynamic-capabilities", "url": "#chapter-03-strategy-and-competitive-analysis-evidence-based-contrarian-thinking-the-limits-of-vrio-the-rise-of-dynamic-capabilities", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "VRIO is a point-in-time diagnosis and can become static or tautological if success is used as proof of the resource's value. The duration of an advantage is an empirical question; there is no universal 18-month window. Dynamic-capabilities research examines how firms integrate, build, and reconfigure competences under change. “Sense, seize, and reconfigure” is useful operational language, but the concept can be difficult to measure and does not make ordinary operating capabilities or economics irrelevant. [BB-C03-S05] Sensing: The ability to spot and interpret market trends and technological shifts. Seizing: The ability to mobilize resources and capture value from new opportunities. Reconfiguring: The ability to transform the organization, assets, and structures as markets evolve. For an operator, this means: Don't just ask \"What is our advantage today?\" (VRIO). Ask \"How good are we at building new advantages tomorrow?\" (Dynamic Capabilities)." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-2", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Academic Citations & Evidence", "headingId": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-2", "url": "#chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-2", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Seminal Work: - Barney, J. B. (1991). Firm Resources and Sustained Competitive Advantage. Journal of Management , 17(1), 99-120. - Jay Barney's foundational article introduced the Resource-Based View (RBV) of the firm and the VRIN framework (Valuable, Rare, Inimitable, Non-substitutable), which later evolved into VRIO. Barney argued that sustained competitive advantage comes from possessing bundles of resources that meet these four criteria, shifting strategic focus from external market positioning (Porter) to internal resource assessment. This became a foundational paper in strategic management. Supporting Research: - Teece, D. J., Pisano, G., & Shuen, A. (1997). Dynamic Capabilities and Strategic Management. Strategic Management Journal , 18(7), 509-533. - The paper develops dynamic capabilities as the ability to integrate, build, and reconfigure competences under changing environments. It supports analysis of renewal and adaptation but does not establish an “ultimate” capability or guarantee advantage. [BB-C03-S05]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-2", "url": "#chapter-03-strategy-and-competitive-analysis-so-what-for-managers-2", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use VRIO to decide which capabilities deserve investment, protection, renewal, or a partner-or-buy alternative. - Require evidence for customer value, appropriability, and organizational support rather than treating a resource as self-proving advantage. - Pair the point-in-time assessment with renewal metrics, imitation signals, and a named capability owner." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-2", "url": "#chapter-03-strategy-and-competitive-analysis-limits-and-critiques-2", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A resource can be valuable without being rare, appropriable, or durable; test alternatives and erosion rather than certifying advantage. - Dynamic capabilities are difficult to measure and do not replace ordinary operating capability, economics, or governance." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-connections-2", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-03-strategy-and-competitive-analysis-connections-2", "url": "#chapter-03-strategy-and-competitive-analysis-connections-2", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires an inventory of your firm's Intellectual Property (Chapter 2) and an understanding of your Core Competencies (This Chapter) . Output: The identified \"Strengths\" and \"Weaknesses\" from VRIO are direct inputs into a SWOT Analysis . The \"Organized\" question links directly to the McKinsey 7S Framework (This Chapter) . [BB-C03-S04] ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-3-blue-ocean-strategy-canvas", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "3. Blue Ocean Strategy Canvas", "headingId": "chapter-03-strategy-and-competitive-analysis-3-blue-ocean-strategy-canvas", "url": "#chapter-03-strategy-and-competitive-analysis-3-blue-ocean-strategy-canvas", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Blue Ocean Strategy Canvas Strategic Differentiation" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-overview-3", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-03-strategy-and-competitive-analysis-overview-3", "url": "#chapter-03-strategy-and-competitive-analysis-overview-3", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Blue Ocean Strategy combines a strategy canvas with eliminate-reduce-raise-create questions to explore a different value curve. Treat “uncontested market space” as an option hypothesis, not a factual state or promise that competition becomes irrelevant. [BB-C03-S06]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-when-to-use", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "When to Use", "headingId": "chapter-03-strategy-and-competitive-analysis-when-to-use", "url": "#chapter-03-strategy-and-competitive-analysis-when-to-use", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Your industry has commoditized and price competition is intense - Your VRIO analysis reveals no sustained competitive advantages - Porter's Five Forces shows your industry is structurally unattractive - You want to test whether a different value curve can reduce direct rivalry or create a defensible position" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-03-strategy-and-competitive-analysis-how-to-apply-3", "url": "#chapter-03-strategy-and-competitive-analysis-how-to-apply-3", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Map the Current State: - Identify the key competing factors your industry competes on (price, features, service, etc.) - Record how your company and competitors perform on those factors in a defined comparison table; a separate strategy canvas is optional and should not be confused with Figure 3.1. - State which customer, cost, capability, and imitation assumptions the current profile depends on. 2. Apply the Four Actions Framework: - Eliminate: Which factors the industry takes for granted should be eliminated? - Reduce: Which factors should be reduced well below the industry standard? - Raise: Which factors should be raised well above the industry standard? - Create: Which factors should be created that the industry has never offered? 3. Reconstruct the Value Curve: - Design a new value curve that diverges from the industry's traditional profile - Ensure it has three characteristics: Focus (concentrated effort), Divergence (distinct from competition), and Compelling Tagline (memorable positioning) 4. Validate with Non-Customers: - Test your new value proposition with people who currently don't buy in your category - Test whether the option creates new demand, shifts existing demand, or merely relabels a segment" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-3", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Academic Citations & Evidence", "headingId": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-3", "url": "#chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-3", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Primary framework documentation: - Kim, W. C., & Mauborgne, R. (2025). Blue Ocean Tools and Frameworks: Blue Ocean Toolkit 2025 . Blue Ocean Strategy. [BB-C03-S06] - The author-published toolkit defines the strategy canvas, value curve, and Four Actions Framework. Its market-creation language states the framework's intended logic; it is not controlled evidence that the method causes superior performance or makes competition disappear." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-mermaid-diagram-errc-decision-flow", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Mermaid Diagram: ERRC Decision Flow", "headingId": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-errc-decision-flow", "url": "#chapter-03-strategy-and-competitive-analysis-mermaid-diagram-errc-decision-flow", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 3.1. Constructed eliminate-reduce-raise-create decision flow. This original adaptation converts the Blue Ocean questions into an option-design sequence. It does not reproduce a company strategy canvas or establish market demand. [BB-C03-S06] Text equivalent: Start with the factors on which an industry currently competes, test which factors to eliminate or reduce and which to raise or create, then validate the resulting value curve with customers, noncustomers, economics, capabilities, and imitation scenarios." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-blue-ocean-trap", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: The Blue Ocean Trap", "headingId": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-blue-ocean-trap", "url": "#chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-blue-ocean-trap", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The framework can understate imitation, incumbent response, customer acquisition, regulation, execution, and the cost of educating a market. Treat the proposed value curve as a falsifiable option: test willingness to pay, total cost, adoption friction, capability gaps, competitor response, and how long any difference could remain valuable and appropriable. Pair the option with VRIO and dynamic-capabilities analysis rather than assuming first-mover advantage." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-3", "url": "#chapter-03-strategy-and-competitive-analysis-so-what-for-managers-3", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the Four Actions questions to generate incompatible value propositions, then compare willingness to pay, delivery cost, capability fit, and adoption friction. - Treat a proposed value curve as a staged option with customer and noncustomer evidence, not a claim that competition has disappeared. - State what the team will stop funding or serving so the strategy expresses a real tradeoff." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-3", "url": "#chapter-03-strategy-and-competitive-analysis-limits-and-critiques-3", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A different value curve is not evidence of demand, appropriation, or durable advantage; test customer, cost, capability, and imitation assumptions. - The framework can understate incumbent response, regulation, and the cost of educating a market." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-connections-3", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-03-strategy-and-competitive-analysis-connections-3", "url": "#chapter-03-strategy-and-competitive-analysis-connections-3", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires competitive intelligence from Porter's Five Forces and an honest assessment of your resources from VRIO Framework . Input: Customer insights from Market Research (Chapter 5) to understand which industry factors customers actually value vs. which are just traditional. Output: The proposed positioning informs product strategy (Chapter 21), Branding & Messaging (Chapter 5) , and Go-to-Market Strategy (Chapter 14) . Output: The Four Actions Framework creates a clear directive for R&D resource allocation and Operations (Chapter 6) on what capabilities to build vs. sunset. ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-4-bcg-growth-share-matrix", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "4. BCG Growth-Share Matrix", "headingId": "chapter-03-strategy-and-competitive-analysis-4-bcg-growth-share-matrix", "url": "#chapter-03-strategy-and-competitive-analysis-4-bcg-growth-share-matrix", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "BCG Growth-Share Matrix [BB-C03-S07] Portfolio Management" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-overview-4", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-03-strategy-and-competitive-analysis-overview-4", "url": "#chapter-03-strategy-and-competitive-analysis-overview-4", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The BCG Growth-Share Matrix is a portfolio heuristic using market growth and relative market share. Developed by the Boston Consulting Group around 1970, its labels embed experience-curve and cash-flow assumptions that must be tested rather than accepted as facts. [BB-C03-S07]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-when-to-use-2", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "When to Use", "headingId": "chapter-03-strategy-and-competitive-analysis-when-to-use-2", "url": "#chapter-03-strategy-and-competitive-analysis-when-to-use-2", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- You manage a multi-product company or conglomerate with diverse business units - You need to make capital allocation decisions across a portfolio - You're deciding which businesses to invest in, harvest, or divest - You want a simple visual communication tool for board-level strategy discussions" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-03-strategy-and-competitive-analysis-how-to-apply-4", "url": "#chapter-03-strategy-and-competitive-analysis-how-to-apply-4", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define Your Business Units: Break your company into distinct Strategic Business Units (SBUs), each with its own market, competitors, and P&L. 2. Gather Data: - Market Growth Rate: Annual growth rate of the industry the SBU competes in (typically shown on Y-axis) - Relative Market Share: Your SBU's market share divided by the largest competitor's share (X-axis, often shown on log scale) 3. Plot Each SBU: Place each business unit in one of four quadrants: - Stars (high growth, high relative share): Test investment needs, cash generation, defensibility, and market definition. - Cash Cows (lower growth, high relative share): Test maintenance needs, erosion, interdependencies, and genuine distributable cash. - Question Marks (high growth, low relative share): Test the value and feasibility of gaining a defensible position against staged exit options. - Dogs (lower growth, low relative share): Test standalone value, option value, obligations, capabilities, and portfolio synergies before exit. 4. Develop and value alternatives: For each business, compare invest, maintain, redesign, partner, stage, harvest, and exit options using cash flow, risk, capabilities, interdependencies, obligations, reversibility, and governance—not the quadrant label alone." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-4", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Academic Citations & Evidence", "headingId": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-4", "url": "#chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-4", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Seminal Work: - Henderson, B. D. (1970). The Product Portfolio . Boston Consulting Group Perspectives. BCG. [BB-C03-S07] - Henderson's BCG Perspective presents the Growth-Share Matrix in the context of experience-curve and portfolio cash-flow logic. Treat the lower-cost and durable-advantage propositions as framework premises to test in the focal market, not as universal empirical relationships. [BB-C03-S07] Decision limit: Relative share is an imperfect proxy for cost advantage, and growth is an imperfect proxy for attractiveness. Define the market consistently and supplement the matrix with value, capability, risk, and synergy analysis. [BB-C03-S07]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-mermaid-diagram-bcg-growth-share-matrix-bb-c03-s07", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Mermaid Diagram: BCG Growth-Share Matrix [BB-C03-S07]", "headingId": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-bcg-growth-share-matrix-bb-c03-s07", "url": "#chapter-03-strategy-and-competitive-analysis-mermaid-diagram-bcg-growth-share-matrix-bb-c03-s07", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 3.2. Constructed BCG portfolio plot. The four anonymous products illustrate placement only; their coordinates and quadrant labels do not prescribe capital allocation. [BB-C03-S07] Text equivalent: Plot each business by a consistently defined market-growth rate and relative market share, then test the assumptions, economics, interdependencies, obligations, and strategic options behind its quadrant before allocating capital." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-of-the-bcg-matrix-bb-c03-s07", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits of the BCG Matrix [BB-C03-S07]", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-of-the-bcg-matrix-bb-c03-s07", "url": "#chapter-03-strategy-and-competitive-analysis-limits-of-the-bcg-matrix-bb-c03-s07", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The matrix was built around experience-curve and portfolio cash-flow logic. Its assumptions can fail in manufacturing, services, and digital markets alike: [BB-C03-S07] 1. Market share does not automatically equal profitability: Scale can matter, but the relationship depends on monetization model, cost structure, and local competitive dynamics. 2. Market growth does not automatically equal attractiveness: Fast-growing markets can still be unattractive when volatility, regulatory risk, fraud, or weak unit economics dominate. 3. The framework ignores interdependencies: A lower-share business might house a capability, contract, or platform used elsewhere. Divestiture can destroy option or synergy value. 4. It is backward-looking: Current share and growth do not estimate future cash flow, disruption, probability, or option value. [BB-C03-S07] Modern Alternative: Use the BCG Matrix only as a conversation starter, not a decision rule. Overlay it with Core Competency Analysis (does this business house strategic capabilities?) and Real Options Pricing (what is the value of keeping options open?). [BB-C03-S07]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-4", "url": "#chapter-03-strategy-and-competitive-analysis-so-what-for-managers-4", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the matrix to frame a portfolio conversation, then make capital choices with cash flow, capability, dependency, obligation, and option-value evidence. - Require a consistent market definition and a named owner for growth, share, profitability, and synergy assumptions. - Compare invest, maintain, redesign, partner, stage, harvest, and exit options rather than allowing a quadrant label to decide." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-4", "url": "#chapter-03-strategy-and-competitive-analysis-limits-and-critiques-4", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Relative share and growth are imperfect proxies for cost advantage, attractiveness, cash flow, and portfolio value. - A quadrant cannot account for obligations, synergies, capabilities, or option value without separate analysis." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-connections-4", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-03-strategy-and-competitive-analysis-connections-4", "url": "#chapter-03-strategy-and-competitive-analysis-connections-4", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires market sizing and competitive intelligence from Porter's Five Forces and Market Analysis (Chapter 5) . Input: Financial performance data (cash flow, profitability) from Financial Analysis (Chapter 4) . Output: Informs Capital Allocation decisions and M&A Strategy (Chapter 2) (which businesses to acquire, divest, or invest in). Output: The \"Harvest\" vs. \"Invest\" decisions directly impact Budgeting & Resource Allocation (Chapter 6) . ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-5-ansoff-matrix", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "5. Ansoff Matrix", "headingId": "chapter-03-strategy-and-competitive-analysis-5-ansoff-matrix", "url": "#chapter-03-strategy-and-competitive-analysis-5-ansoff-matrix", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Ansoff Matrix (Product-Market Growth Strategy) Growth Strategy" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-overview-5", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-03-strategy-and-competitive-analysis-overview-5", "url": "#chapter-03-strategy-and-competitive-analysis-overview-5", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Ansoff Matrix classifies growth directions by existing or new products and existing or new markets. Moving farther from current knowledge can add uncertainty and capability demands, but the matrix does not establish a universal risk ranking or show whether an option creates value. [BB-C03-S08]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-when-to-use-3", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "When to Use", "headingId": "chapter-03-strategy-and-competitive-analysis-when-to-use-3", "url": "#chapter-03-strategy-and-competitive-analysis-when-to-use-3", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- You need to set strategic growth priorities and allocate resources - You're deciding between investing in current markets vs. exploring new ones - You want to communicate growth strategy options to stakeholders in a simple, clear framework - You need to assess the relative risk of different growth initiatives" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-03-strategy-and-competitive-analysis-how-to-apply-5", "url": "#chapter-03-strategy-and-competitive-analysis-how-to-apply-5", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Assess Current Position: Understand your existing products and markets clearly. 2. Evaluate Four Growth Strategies: Market Penetration (Existing Products + Existing Markets): - Increase market share by selling more of your current products to current customers - Often uses more familiar assets and customers, but can still be costly or provoke strong rivalry - Tactics: Increase usage frequency, win competitors' customers, improve distribution - Constructed example: improve distribution or use cases for an existing offer in a defined current segment Market Development (Existing Products + New Markets): - Sell existing products to new customer segments or geographies - Adds uncertainty about customer, channel, geography, regulation, or use context - Tactics: Geographic expansion, new customer segments, new use cases - Constructed example: test an existing offer with a new geography or customer segment Product Development (New Products + Existing Markets): - Create new products for existing customers - Adds product, technology, development, adoption, and cannibalization uncertainty - Tactics: Product line extensions, next-generation versions, adjacent products - Constructed example: test a new adjacent offer with a documented current customer group Diversification (New Products + New Markets): - Enter entirely new markets with new products - Combines product and market novelty; validate value, capability, governance, and staged commitment carefully - Types: Related (synergies exist) or Unrelated (pure conglomerate play) - Constructed example: enter a new category with a new offer through build, buy, partner, or staged option 3. Compare alternatives using evidence: Test expected value, downside, capital and liquidity, capability fit, customer evidence, competitive response, regulatory exposure, time, reversibility, and the value of staging. “Conservative” or “innovative” labels do not select a quadrant." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-5", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Academic Citations & Evidence", "headingId": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-5", "url": "#chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-5", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Seminal Work: - Ferguson, J., & Zamudio, C. (2026). Ch. 5: Strategic Planning. Marketing Principles From The River City . Virginia Commonwealth University Libraries. [BB-C03-S08] - This openly licensed textbook chapter defines the four product-market directions and warns against treating growth as an objective in itself. It is used for the retained operational taxonomy, not as proof of a universal risk order or performance effect. - The cited chapter presents the four product-market directions. The matrix is commonly associated with Ansoff, but this chapter does not treat the active source as a claim-level inspection of the original article; use the taxonomy to organize novelty, not to infer a probability of success or authorize investment. Supporting research: Corporate-diversification evidence is conditional on market, governance, transaction, capability, and measurement choices. Evidence of an average diversification discount does not prove that every diversified firm destroys value, while corporate-strategy research warns against assuming that a stated synergy will be realized. [BB-C03-S17] [BB-C03-S18]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-mermaid-diagram-ansoff-matrix", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Mermaid Diagram: Ansoff Matrix", "headingId": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-ansoff-matrix", "url": "#chapter-03-strategy-and-competitive-analysis-mermaid-diagram-ansoff-matrix", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 3.3. Product-market direction tree. This original adaptation shows increasing novelty in product and market assumptions; labels such as “existing” and “new” require a defined customer, offer, geography, and time horizon. [BB-C03-S08] Text equivalent: Classify an option by whether the product and market are existing or new to the firm, then compare all four directions using evidence, economics, capability fit, uncertainty, and staged commitments rather than treating the quadrant as a risk score." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-diversification-paradox", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: The Diversification Paradox", "headingId": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-diversification-paradox", "url": "#chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-diversification-paradox", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Diversification can be proposed for sound strategic reasons or distorted by incentives, overconfidence, weak governance, or unsupported synergy claims. Require the sponsor to identify the parent-level advantage, value-creation mechanism, capability transfer, alternative ownership, integration cost, downside, exit option, and evidence that the combined owner is better than separate owners. Preserve dissent and compare build, buy, ally, minority investment, and no-action alternatives. [BB-C03-S17] [BB-C03-S18]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-5", "url": "#chapter-03-strategy-and-competitive-analysis-so-what-for-managers-5", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the grid to name novelty assumptions, then test value, capability fit, competition, regulation, and the cost of learning. - Compare build, buy, partner, pilot, staged, and no-action alternatives; the quadrant describes direction, not an investment recommendation. - Record the evidence and trigger that would move the option from exploration to commitment or redesign." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-5", "url": "#chapter-03-strategy-and-competitive-analysis-limits-and-critiques-5", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Product-market novelty is not a universal risk ranking and does not estimate demand, value, capability, or execution risk. - “Conservative” and “innovative” labels do not replace staged evidence, governance, and a no-action comparison." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-connections-5", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-03-strategy-and-competitive-analysis-connections-5", "url": "#chapter-03-strategy-and-competitive-analysis-connections-5", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Market opportunity assessment from Market Analysis (Chapter 5) and Porter's Five Forces (This Chapter) . Input: Internal capability assessment from VRIO Framework (This Chapter) to evaluate if you can execute each strategy. Output: A tested growth direction informs product strategy (Chapter 21), Sales & Marketing Strategy (Chapter 5) , and capital-allocation or transaction analysis in Chapter 4. Output: The risk profile of your chosen strategy informs Financial Planning & Scenario Analysis (Chapter 4) . ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-6-pestle-analysis", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "6. PESTLE Analysis", "headingId": "chapter-03-strategy-and-competitive-analysis-6-pestle-analysis", "url": "#chapter-03-strategy-and-competitive-analysis-6-pestle-analysis", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "PESTLE Analysis (Macro-Environmental Scan) External Environment Analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-overview-6", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-03-strategy-and-competitive-analysis-overview-6", "url": "#chapter-03-strategy-and-competitive-analysis-overview-6", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "PESTLE is a practitioner taxonomy for organizing political, economic, social, technological, legal, and environmental observations. Broader environmental-scanning research treats scanning as the acquisition and use of information about external events, trends, and relationships and distinguishes multiple viewing, searching, and learning modes. That research does not validate PESTLE's six labels as a causal model. Use the taxonomy to create testable assumptions and signposts, not to infer impact, likelihood, completeness, or a required action from a category. [BB-C03-S09]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-when-to-use-4", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "When to Use", "headingId": "chapter-03-strategy-and-competitive-analysis-when-to-use-4", "url": "#chapter-03-strategy-and-competitive-analysis-when-to-use-4", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- You're entering a new market or geography and need to understand external risks - You're conducting strategic planning and need to identify long-term trends - You need to perform risk analysis for major investments or regulatory filings - You want to identify opportunities or threats from macro trends (e.g., AI, climate change, geopolitical shifts)" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-03-strategy-and-competitive-analysis-how-to-apply-6", "url": "#chapter-03-strategy-and-competitive-analysis-how-to-apply-6", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Scan Each Dimension Systematically: Political: - Government stability, tax policy, trade restrictions, lobbying, political risk - Constructed prompt: Which government, trade, national-security, or political changes could alter access or ownership? Economic: - GDP growth, inflation, interest rates, exchange rates, unemployment - Constructed prompt: How would demand, financing, input cost, and currency exposures respond across macro scenarios? Social: - Demographics, cultural trends, lifestyle changes, education levels, values - Constructed prompt: Which demographic or preference change is evidenced, for whom, and over what time horizon? Technological: - Automation, AI, R&D, technology adoption rates, infrastructure - Constructed prompt: Which capability, adoption, infrastructure, complement, safety, or substitution assumption changes the decision? Legal: - Employment, consumer-protection, competition, IP, privacy, and other applicable law - Constructed prompt: Which current jurisdiction, rule, regulator, contract, or case changes the permitted option set? Environmental: - Climate change, carbon regulations, sustainability, resource scarcity - Constructed prompt: Which physical, transition, resource, disclosure, or liability risk affects cash flow or license to operate? 2. Assess mechanism, evidence, uncertainty, and timing: - Define how each factor could change price, volume, cost, assets, rights, capability, or timing. - If using ordinal scores, state anchors and uncertainty; do not multiply them as if they were measured probabilities and impacts. 3. Develop options and signposts: Compare no action, monitor, hedge, stage, partner, redesign, or commit. Assign an evidence owner and define the signpost that would trigger review." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-6", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Academic Citations & Evidence", "headingId": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-6", "url": "#chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-6", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Open scholarly evidence: - Choo, C. W. (2001). Environmental scanning as information seeking and organizational learning. Information Research , 7(1), paper 112. [BB-C03-S09] - Choo defines environmental scanning and analyzes undirected viewing, conditioned viewing, enacting, and searching alongside sensemaking, knowledge creation, and decision use. The article cites Aguilar's earlier work but does not establish a genealogy or predictive validity for the PESTLE labels. Decision limit: Category completeness does not establish forecast accuracy or performance. Avoid double counting one mechanism in several boxes, preserve contrary evidence, and link material uncertainties to scenarios and signposts." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-mermaid-diagram-pestle-analysis-framework", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Mermaid Diagram: PESTLE Analysis Framework", "headingId": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-pestle-analysis-framework", "url": "#chapter-03-strategy-and-competitive-analysis-mermaid-diagram-pestle-analysis-framework", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 3.4. PESTLE evidence-to-implication flow. This original taxonomy shows six scanning categories converging on strategic implications; every implication still requires a causal mechanism, evidence, uncertainty, and owner. [BB-C03-S09] Text equivalent: Scan political, economic, social, technological, legal, and environmental factors; for each material observation, specify the business mechanism, evidence, uncertainty, time horizon, signpost, and option it affects." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-contrarian-thinking-pestle-s-illusion-of-control", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: PESTLE's Illusion of Control", "headingId": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-pestle-s-illusion-of-control", "url": "#chapter-03-strategy-and-competitive-analysis-contrarian-thinking-pestle-s-illusion-of-control", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "PESTLE can create an illusion of completeness. A populated list does not reveal unknowns, interacting shocks, model error, or whether the selected factors are decision-relevant. The Real Value of PESTLE: It's not a prediction tool; it's a cognitive exercise that expands your peripheral vision. The act of systematically asking \"What political/technological/legal shifts could disrupt us?\" makes your organization more cognitively prepared to respond when surprises occur. Better approach: Combine PESTLE with scenario planning to develop a small set of plausible, internally coherent futures. Do not promise to “win” in every scenario; identify robust actions, contingent actions, signposts, and commitments that should remain reversible." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-6", "url": "#chapter-03-strategy-and-competitive-analysis-so-what-for-managers-6", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Convert each material observation into a mechanism, evidence owner, uncertainty, time horizon, and decision trigger. - Use PESTLE to widen the search, then hand consequential uncertainties to scenario, financial, operating, legal, or governance analysis. - Preserve contrary evidence and avoid counting one shock several times across categories." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-6", "url": "#chapter-03-strategy-and-competitive-analysis-limits-and-critiques-6", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A filled category is not a forecast, a probability, or a materiality judgment; interacting shocks and unknowns remain possible. - PESTLE has value only when observations become mechanisms, owners, signposts, options, and review decisions." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-connections-6", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-03-strategy-and-competitive-analysis-connections-6", "url": "#chapter-03-strategy-and-competitive-analysis-connections-6", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires data from Macroeconomic Analysis (Chapter 1) for the Economic dimension and Regulatory Intelligence for Legal/Political. Input: Technology trends from product and R&D teams and AI Strategy (Chapter 16). Output: Identified macro opportunities and threats are direct inputs into Porter's Five Forces (e.g., regulatory barriers to entry) and Scenario Planning (This Chapter) . Output: Legal and environmental factors inform law, governance, and ethics (Chapter 2) and enterprise-risk analysis. ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-7-mckinsey-7s-framework", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "7. McKinsey 7S Framework", "headingId": "chapter-03-strategy-and-competitive-analysis-7-mckinsey-7s-framework", "url": "#chapter-03-strategy-and-competitive-analysis-7-mckinsey-7s-framework", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "McKinsey 7S Framework [BB-C03-S10] Organizational Alignment" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-overview-7", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-03-strategy-and-competitive-analysis-overview-7", "url": "#chapter-03-strategy-and-competitive-analysis-overview-7", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The 7S framework invites managers to examine strategy, structure, systems, shared values, style, staff, and skills as interacting elements. It was published by Robert Waterman, Thomas Peters, and Julien Phillips in 1980 and later popularized in practitioner books. It is a descriptive diagnostic, not a causal law that perfect alignment produces success. [BB-C03-S10]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-when-to-use-5", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "When to Use", "headingId": "chapter-03-strategy-and-competitive-analysis-when-to-use-5", "url": "#chapter-03-strategy-and-competitive-analysis-when-to-use-5", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- You're implementing a major organizational change (restructuring, M&A integration, strategic pivot) - Your strategy is sound on paper but failing in execution - You need to diagnose organizational dysfunction or misalignment - You're conducting organizational due diligence for an acquisition" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-03-strategy-and-competitive-analysis-how-to-apply-7", "url": "#chapter-03-strategy-and-competitive-analysis-how-to-apply-7", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The framework divides organizational elements into two categories: Hard Elements (Easier to Define and Change): 1. Strategy: The plan to achieve sustainable competitive advantage 2. Structure: The organizational chart and reporting relationships 3. Systems: The processes, procedures, and IT systems that govern work Soft Elements (Harder to Define and Change): 4. Shared Values: The core beliefs and culture (at the center of the model) 5. Style: The leadership and management approach 6. Staff: The people and their capabilities 7. Skills: The distinctive competencies and core capabilities Application Steps: 1. Map Current State: Assess the current state of each of the 7 elements 2. Define Desired State: Based on your strategy, define what each element should look like 3. Identify Gaps: Find misalignments between current and desired state, and between elements 4. Prioritize Actions: Develop change initiatives to close the gaps, starting with the elements most out of alignment" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-7", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Academic Citations & Evidence", "headingId": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-7", "url": "#chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-7", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Seminal Work: - Waterman, R. H., Peters, T. J., & Phillips, J. R. (1980). “Structure Is Not Organization.” Business Horizons , 23(3), 14–26. [BB-C03-S10] - The article is the canonical published source for the seven-element model. Use it to structure an alignment diagnosis, not to infer a quantified execution benefit. Related evidence: Kaplan and Norton discuss alignment across organizational units and management systems, but that work does not validate a universal execution-success rate or prove that 7S causes performance. [BB-C03-S19]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-mermaid-diagram-mckinsey-7s-framework-bb-c03-s10", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Mermaid Diagram: McKinsey 7S Framework [BB-C03-S10]", "headingId": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-mckinsey-7s-framework-bb-c03-s10", "url": "#chapter-03-strategy-and-competitive-analysis-mermaid-diagram-mckinsey-7s-framework-bb-c03-s10", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 3.5. Seven-element alignment map. This original redraw shows the seven elements as interdependent diagnostic categories; the arrows do not imply measured causal strength or a required central hierarchy. [BB-C03-S10] Text equivalent: Examine strategy, structure, systems, shared values, style, staff, and skills; identify where the intended strategy conflicts with current arrangements, which evidence supports the diagnosis, and which elements should remain differentiated." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-alignment-trap", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: The Alignment Trap", "headingId": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-alignment-trap", "url": "#chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-alignment-trap", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Alignment can improve consistency while also reducing variety or adaptability. The relevant question is which elements must reinforce the strategy, which should remain differentiated, and how the organization detects environmental change. Author-created hypothesis: Exploration and exploitation may require different structures, processes, incentives, and time horizons. Treat separation, integration, and senior-team coordination as design options to test—not a universal prescription for every innovation unit." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-7", "url": "#chapter-03-strategy-and-competitive-analysis-so-what-for-managers-7", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use 7S to identify which arrangements support or obstruct a chosen strategy, then assign owners and sequence the changes. - Distinguish elements that must reinforce one another from those that should remain differentiated for exploration, resilience, or local fit. - Test the diagnosis with employee, customer, process, and performance evidence instead of inferring alignment from an organization chart." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-7", "url": "#chapter-03-strategy-and-competitive-analysis-limits-and-critiques-7", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- 7S is descriptive and does not prove that alignment causes execution success or prescribe one change sequence. - More consistency can reduce adaptability; some exploration and exploitation activities may need differentiated arrangements." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-connections-7", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-03-strategy-and-competitive-analysis-connections-7", "url": "#chapter-03-strategy-and-competitive-analysis-connections-7", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The \"Strategy\" element comes from your Competitive Strategy (Porter's, Blue Ocean) and Growth Strategy (Ansoff) . Input: The \"Skills\" element is an output of your VRIO Analysis and Core Competency Analysis (This Chapter) . Output: Identified misalignments become action items for Organizational Design (Chapter 7) , Change Management , and Leadership Development . Output: The \"Systems\" element directly informs Process Improvement (Chapter 6) and IT Strategy . ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-8-core-competency-analysis", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "8. Core Competency Analysis", "headingId": "chapter-03-strategy-and-competitive-analysis-8-core-competency-analysis", "url": "#chapter-03-strategy-and-competitive-analysis-8-core-competency-analysis", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Core Competency Analysis Strategic Capabilities" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-overview-8", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-03-strategy-and-competitive-analysis-overview-8", "url": "#chapter-03-strategy-and-competitive-analysis-overview-8", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Core Competency Analysis examines integrated skills, technologies, learning, and processes that may contribute to customer value and extend across businesses. Prahalad and Hamel's work is the seminal reference for the concept; the analysis complements resource assessment but does not prove uniqueness, differentiation, or transaction fit. [BB-C03-S11]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-when-to-use-6", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "When to Use", "headingId": "chapter-03-strategy-and-competitive-analysis-when-to-use-6", "url": "#chapter-03-strategy-and-competitive-analysis-when-to-use-6", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- You're deciding which businesses to enter or exit (diversification strategy) - You want to identify the \"glue\" that holds your multi-product company together - You're evaluating M&A opportunities and need to assess strategic fit - You need to prioritize which capabilities to invest in vs. outsource" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-03-strategy-and-competitive-analysis-how-to-apply-8", "url": "#chapter-03-strategy-and-competitive-analysis-how-to-apply-8", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Identify Candidate Competencies: - Look for capabilities that cut across multiple products or business units - Describe the repeatable knowledge, routines, assets, relationships, and coordination involved; avoid naming a broad strength such as “innovation” or “our people.” 2. Test Against Three Criteria: Test each candidate against three questions: a) Customer Value: Does it provide a fundamental benefit to customers? - Not just \"we're good at it,\" but \"customers pay us because of it\" b) Competitive Differentiation: Is it unique compared to competitors? - What competitor, substitute, customer, and performance evidence shows meaningful differentiation? c) Extendability: Can it be leveraged across multiple markets or products? - Which adjacent offers or markets could use the capability, and what additional complements would be required? - A capability concentrated in one product may still be strategically important; cross-market use is a hypothesis to test. 3. Map Competencies to Products: - Create a matrix showing which competencies enable which products - Identify \"white spaces\" where your competencies could enable new products 4. Develop a capability roadmap: - Compare build, hire, partner, license, acquire, retain, and exit options, including time, learning, integration, and appropriation. - Define milestones and evidence showing whether the capability is improving customer value or merely consuming resources." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-8", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Academic Citations & Evidence", "headingId": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-8", "url": "#chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-8", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Seminal Work: - Prahalad, C. K., & Hamel, G. (1990). The Core Competence of the Corporation. Harvard Business Review , 68(3), 79-91. [BB-C03-S11] - The article contrasts a business-unit portfolio view with the cultivation of cross-business competencies and uses a tree metaphor to distinguish competencies, core products, businesses, and end products. Treat its cases as the authors' strategic interpretation. [BB-C03-S11] Related theory: Resource-based and dynamic-capabilities perspectives help test value, imitation, appropriation, renewal, and erosion. They overlap with, but are not identical to, the core-competence concept. [BB-C03-S04] [BB-C03-S05]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-mermaid-diagram-core-competency-tree", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Mermaid Diagram: Core Competency Tree", "headingId": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-core-competency-tree", "url": "#chapter-03-strategy-and-competitive-analysis-mermaid-diagram-core-competency-tree", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 3.6. Constructed capability-to-offer map. This original adaptation illustrates how two hypothetical competencies might support several offers; it does not assert that a named company's products share one verified capability. [BB-C03-S11] Text equivalent: Map each candidate competency to the products, customer benefits, processes, evidence, and complementary assets it supports, then identify gaps and test whether extension creates value." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-core-competency-trap", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: The Core Competency Trap", "headingId": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-core-competency-trap", "url": "#chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-core-competency-trap", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Capabilities can become rigidities when identity, sunk cost, incentives, measures, or complementary assets prevent renewal. Do not infer a company's failure from one capability narrative. Regularly test whether the capability still creates and captures customer value, whether substitutes or complements changed, what evidence would disconfirm the story, and which new capability is being built before the old one erodes. [BB-C03-S05] [BB-C03-S11]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-8", "url": "#chapter-03-strategy-and-competitive-analysis-so-what-for-managers-8", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the analysis to decide which capability hypotheses deserve build, hire, partner, license, acquire, retain, or exit options. - Tie each competency to a customer benefit, evidence of strategic value, complementary assets, and an accountable owner. - Monitor renewal and erosion signals so a historic strength does not become a rigid identity or sunk-cost commitment." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-8", "url": "#chapter-03-strategy-and-competitive-analysis-limits-and-critiques-8", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- “Core competency” requires repeatable routines and evidence of customer value, not a broad label such as innovation or talent. - Cross-business transfer can fail when complements, governance, customer context, or appropriation are missing." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-connections-8", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-03-strategy-and-competitive-analysis-connections-8", "url": "#chapter-03-strategy-and-competitive-analysis-connections-8", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Builds on VRIO Analysis (This Chapter) by asking which VRIO resources can be combined into integrated competencies. Input: Requires customer insight from Market Research (Chapter 5) to validate that the competency actually creates value. Output: Core-competency hypotheses inform diversification, partnership, acquisition, and divestiture analysis together with valuation (Chapter 4) and integration feasibility. Output: The competency-building roadmap shapes R&D Investment (Part 3) and Talent Strategy (Chapter 7) . ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-9-scenario-planning-matrix", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "9. Scenario Planning Matrix", "headingId": "chapter-03-strategy-and-competitive-analysis-9-scenario-planning-matrix", "url": "#chapter-03-strategy-and-competitive-analysis-9-scenario-planning-matrix", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scenario Planning Matrix Strategic Foresight" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-overview-9", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-03-strategy-and-competitive-analysis-overview-9", "url": "#chapter-03-strategy-and-competitive-analysis-overview-9", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scenario planning develops several plausible, internally coherent futures to challenge a focal decision rather than replacing one forecast with another. It can broaden assumptions and expose signposts; it does not attach probabilities, prove preparedness, or guarantee resilience. Wack's account of Shell and Schoemaker's method remain seminal practitioner sources. [BB-C03-S12] [BB-C03-S13]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-when-to-use-7", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "When to Use", "headingId": "chapter-03-strategy-and-competitive-analysis-when-to-use-7", "url": "#chapter-03-strategy-and-competitive-analysis-when-to-use-7", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- You're operating in a highly uncertain environment (emerging technology, volatile geopolitics, regulatory flux) - You need to make a major, irreversible strategic decision with a 5-10 year time horizon - A single forecast conceals decision-relevant uncertainty or repeated model error - You want to stress-test your strategy against multiple possible futures" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-03-strategy-and-competitive-analysis-how-to-apply-9", "url": "#chapter-03-strategy-and-competitive-analysis-how-to-apply-9", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define the Focal Question: - What specific strategic decision or uncertainty are you addressing? - Constructed example: “Under which conditions should we stage, redesign, or reject a major domestic manufacturing investment?” 2. Identify Key Uncertainties: - List the major external forces that will shape the future (use PESTLE) - Select a small number of decision-relevant, causally distinct uncertainties; two axes are a communication choice, not a rule 3. Build 2x2 Scenario Matrix: - Take the two most critical uncertainties as axes - Create distinct, internally consistent scenarios without treating the quadrants as forecasts - Name each scenario memorably (helps with communication) 4. Develop Scenario Narratives: - Write enough causal narrative to test the decision, including actors, mechanisms, timing, constraints, and contradictions - Describe what the world looks like in that future - Include implications for your industry, customers, and company 5. Identify Strategic Implications: - For each scenario, ask which option remains viable, which assumption breaks, and which action should stay reversible - Identify relatively robust options and state the costs or conditions that could make them fail - Treat “no-regret” as a claim to test; even monitoring, capability, or flexibility investments have cost - Identify \"hedges\" (protect against specific scenarios) - Identify \"big bets\" (only valuable in one scenario, but transformative if it occurs) 6. Define Signposts & Trigger Points: - What early indicators would signal which scenario is unfolding? - Define trigger points for strategic pivots" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-9", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Academic Citations & Evidence", "headingId": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-9", "url": "#chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-9", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Seminal Work: - Wack, P. (1985). Scenarios: Uncharted Waters Ahead. Harvard Business Review , 63(5), 73-89. [BB-C03-S12] - Wack describes Shell's scenario practice and emphasizes changing managerial assumptions rather than predicting one future. Treat Shell's preparedness advantage as the author's case account, not a controlled causal estimate. [BB-C03-S12] Supporting Research: - Schoemaker, P. J. H. (1995). Scenario Planning: A Tool for Strategic Thinking. Sloan Management Review , 36(2), 25-40. [BB-C03-S13] - Schoemaker describes constructing scenarios from basic trends and uncertainties to counter overconfidence and tunnel vision in strategic decisions. The article does not establish a universal effectiveness rate for scenario planning. Decision limit: Scenarios can become stories that confirm sponsor beliefs, conceal probabilities, or sit outside governance. Preserve disconfirming evidence and connect each scenario to owners, signposts, decision dates, and reversibility." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-mermaid-diagram-scenario-planning-matrix-example-ai-regulation", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Mermaid Diagram: Scenario Planning Matrix Example (AI Regulation)", "headingId": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-scenario-planning-matrix-example-ai-regulation", "url": "#chapter-03-strategy-and-competitive-analysis-mermaid-diagram-scenario-planning-matrix-example-ai-regulation", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 3.7. Constructed AI capability-and-regulation scenarios. The axes and quadrant names are a teaching example, not a forecast, probability model, legal classification, or claim about which firms will win. [BB-C03-S13] Text equivalent: Cross a faster/slower AI-capability uncertainty with a lighter/heavier regulatory-constraint uncertainty, describe four coherent worlds, then test options, signposts, commitments, and failure conditions in each." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-contrarian-thinking-why-most-scenario-planning-fails", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: Why Most Scenario Planning Fails", "headingId": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-why-most-scenario-planning-fails", "url": "#chapter-03-strategy-and-competitive-analysis-contrarian-thinking-why-most-scenario-planning-fails", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scenario work creates value only if it changes assumptions, options, monitoring, or decisions. A polished narrative without governance can become theater. Common Failures: 1. Unusable extremes or timid variants: Test plausibility and decision relevance without excluding difficult futures merely because they are uncomfortable. 2. Too many or too few scenarios: Use the smallest set that exposes material differences; four is a common 2x2 output, not a universal optimum. 3. Lack of signposts: Define observable indicators, evidence owners, review cadence, and ambiguity; several scenarios may share signals. 4. No strategic follow-through: Scenarios are created, but strategy doesn't change. The exercise becomes academic. Governance option: Set a review cadence appropriate to decision speed and evidence availability. Ask which assumptions changed, which scenarios remain plausible, what the signposts mean, and whether a commitment should be staged, accelerated, redesigned, or stopped." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-9", "url": "#chapter-03-strategy-and-competitive-analysis-so-what-for-managers-9", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the scenario set to compare robust, contingent, and no-action options and identify which commitments should remain reversible. - Assign evidence owners, review dates, and trigger thresholds; a scenario without governance is a narrative rather than a decision tool. - Record what evidence would disconfirm the sponsor's preferred future and what action would follow." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-9", "url": "#chapter-03-strategy-and-competitive-analysis-limits-and-critiques-9", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Scenarios are not forecasts and can still reflect sponsor bias, implausible extremes, or hidden assumptions. - They create value only when they change options, monitoring, sequencing, investment, or the decision to stop." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-connections-9", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-03-strategy-and-competitive-analysis-connections-9", "url": "#chapter-03-strategy-and-competitive-analysis-connections-9", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Key uncertainties are identified through PESTLE Analysis (This Chapter) and Macroeconomic Analysis (Chapter 1) . Input: Industry-specific uncertainties come from Porter's Five Forces and Technology Forecasting (Part 3) . Output: Scenario narratives directly inform Strategic Options and Risk Management (Chapter 2) . Output: Robust strategies identified through scenario planning shape Capital Allocation and M&A Strategy . ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-10-platform-strategy-framework", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "10. Platform Strategy Framework", "headingId": "chapter-03-strategy-and-competitive-analysis-10-platform-strategy-framework", "url": "#chapter-03-strategy-and-competitive-analysis-10-platform-strategy-framework", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Platform Strategy Framework Network Effects & Ecosystems" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-overview-10", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-03-strategy-and-competitive-analysis-overview-10", "url": "#chapter-03-strategy-and-competitive-analysis-overview-10", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Platform strategy concerns multi-sided interactions among distinct participant groups and the cross-side effects, pricing, governance, and coordination problems they may create. “Platform” and “pipeline” are not mutually exclusive company types, and a platform label does not establish scale, defensibility, profitability, or a required strategy. This section is an introduction; Chapter 18 develops the economics and governance in depth. [BB-C03-S14] [BB-C03-S15]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-when-to-use-8", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "When to Use", "headingId": "chapter-03-strategy-and-competitive-analysis-when-to-use-8", "url": "#chapter-03-strategy-and-competitive-analysis-when-to-use-8", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- You're designing a business model that connects buyers and sellers, creators and consumers, or other user groups - You're trying to create network effects and defensibility in your market - You need to decide whether to build an ecosystem vs. a traditional product - You're competing against a platform and need to understand its strategic dynamics" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-03-strategy-and-competitive-analysis-how-to-apply-10", "url": "#chapter-03-strategy-and-competitive-analysis-how-to-apply-10", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Identify the Core Interaction: - What is the fundamental value-creating interaction between users? - Constructed examples include matching a service provider with a buyer or a creator with an audience; identify the actual exchange, rights, and failure modes rather than copying a category label. 2. Design the Multi-Sided Market: - Supply Side: Who creates value? (Drivers, hosts, creators) - Demand Side: Who consumes value? (Riders, travelers, viewers) - Platform: What infrastructure facilitates the interaction? (Apps, matching algorithms, payment systems, trust/reputation) 3. Solve the Chicken-and-Egg Problem: - Platforms need both sides to be valuable, but each side only joins if the other is already there - Options to test include subsidizing a price-sensitive side, starting in a narrow geography or use case, recruiting high-value participants, providing standalone utility, seeding supply or demand, or beginning as a managed service. Model acquisition, fraud, quality, liquidity, and subsidy duration. 4. Build Network Effects: - Same-side effects: Additional participants can increase or decrease value for participants on the same side. - Cross-side effects: Additional participation on one side can change value for another side. - Data feedback: More use may improve a service only if data is relevant, usable, lawful, and converted into learning that outweighs noise, bias, privacy, and diminishing returns. 5. Establish Governance & Trust: - Determine which participation, quality, safety, dispute, content, access, and enforcement rules the interaction requires - Compare trust and remedy mechanisms such as verification, reputation, guarantees, insurance, monitoring, and appeal; their value and legal effect depend on context 6. Monetization Strategy: - Transaction fees: Take a cut of each transaction - Listing fees: Charge suppliers to list on the platform - Subscriptions: Offer premium features to power users - Advertising or sponsorship: Third parties fund access in exchange for defined attention, placement, leads, or outcomes" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-10", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Academic Citations & Evidence", "headingId": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-10", "url": "#chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-10", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Seminal and practitioner work: - Parker, G. G., Van Alstyne, M. W., & Choudary, S. P. (2016). Platform Revolution . New York: W.W. Norton. [BB-C03-S15] - The book synthesizes platform strategy and practice. Do not use a time-sensitive market-cap ranking or claim that platforms are inherently asset-light, faster-scaling, or more valuable without separate current evidence. Supporting Research: - Eisenmann, T., Parker, G., & Van Alstyne, M. (2006). Strategies for Two-Sided Markets. Harvard Business Review , 84(10), 92-101. [BB-C03-S14] - The article addresses two-sided pricing, sequencing, multi-homing, and competition. Winner-take-all outcomes depend on network effects, multi-homing, differentiation, capacity, governance, and market boundaries; they are not automatic. [BB-C03-S14]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-mermaid-diagram-platform-business-model", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Mermaid Diagram: Platform Business Model", "headingId": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-platform-business-model", "url": "#chapter-03-strategy-and-competitive-analysis-mermaid-diagram-platform-business-model", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 3.8. Constructed two-sided platform interaction map. The diagram shows participant roles, a core interaction, data feedback, governance, and monetization as design questions; it does not imply that every platform uses these mechanisms or that data feedback creates advantage. [BB-C03-S14] Text equivalent: Define each participant side and the core exchange, then test value, quality, pricing, governance, trust, data rights, feedback, monetization, multi-homing, disintermediation, congestion, and failure remedies." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-platform-delusion", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: The Platform Delusion", "headingId": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-platform-delusion", "url": "#chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-platform-delusion", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Platform strategies can fail when the core interaction creates little value, participant acquisition is too costly, quality or safety degrades, governance alienates a side, multi-homing weakens pricing power, participants transact off-platform, subsidies cannot end, or regulation changes the economics. Compare a platform with product, managed-service, licensing, vertically integrated, partnership, and marketplace alternatives. Model local liquidity, cross-side effects, take rate, cost to serve, fraud and trust costs, participant surplus, concentration, and the path to sustainable cash flow before committing. [BB-C03-S14] [BB-C03-S15]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-10", "url": "#chapter-03-strategy-and-competitive-analysis-so-what-for-managers-10", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Start with the core interaction and local liquidity, not the platform label; test value for each side and the conditions for continued participation. - Model pricing, acquisition, quality, fraud, safety, trust, governance, multi-homing, disintermediation, congestion, and remedy costs together. - Compare platform, product, managed-service, licensing, partnership, and vertically integrated alternatives before committing to subsidy or scale." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-10", "url": "#chapter-03-strategy-and-competitive-analysis-limits-and-critiques-10", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Network effects can be weak, negative, local, or reversible; more participation can increase congestion, fraud, privacy risk, or safety harm. - Platform labels do not establish winner-take-all dynamics, asset-light scaling, defensibility, profitability, or lawful operation." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-connections-10", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-03-strategy-and-competitive-analysis-connections-10", "url": "#chapter-03-strategy-and-competitive-analysis-connections-10", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Platform viability assessment requires Market Analysis (Chapter 5) to understand market fragmentation and transaction costs. Input: Competitive dynamics from Porter's Five Forces to assess threat of platform disintermediation. Output: Platform hypotheses shape product strategy (Chapter 21), technology architecture, governance, and Go-to-Market Strategy (Chapter 14) . Output: Network effects are a source of competitive advantage in the VRIO Framework if they are truly defensible. ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-managerial-economics-bridge-from-five-forces-to-positioning", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Managerial Economics Bridge: From Five Forces to Positioning", "headingId": "chapter-03-strategy-and-competitive-analysis-managerial-economics-bridge-from-five-forces-to-positioning", "url": "#chapter-03-strategy-and-competitive-analysis-managerial-economics-bridge-from-five-forces-to-positioning", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Five Forces names where competitive pressure may come from; managerial economics tests the mechanism. The bridge is not a complete microeconomics course. It gives a manager a disciplined way to ask whether a strategic move changes willingness to pay, quantity, incremental cost, bargaining power, information, or another player's incentives—and whether the firm can capture enough of the resulting value to justify the move." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-the-decision-sequence", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "The decision sequence", "headingId": "chapter-03-strategy-and-competitive-analysis-the-decision-sequence", "url": "#chapter-03-strategy-and-competitive-analysis-the-decision-sequence", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 3.9. Constructed managerial-economics decision bridge. This original synthesis links demand, unit economics, market constraints, pricing, information, and competitor response to a positioned activity system. It is a diagnostic sequence, not a claim that decisions occur once or in a fixed order. [BB-C03-S20] [BB-C03-S21] [BB-C03-S23] [BB-C03-S28] Text equivalent: Define the focal choice and market boundary; estimate how customers and suppliers respond; compare incremental benefit and cost; test entry, substitution, bargaining, and rivalry constraints; design transparent terms and information safeguards; model plausible responses; then choose, stage, redesign, or stop. Monitor evidence and repeat the sequence as conditions change." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-1-demand-elasticity-and-marginal-analysis", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "1. Demand elasticity and marginal analysis", "headingId": "chapter-03-strategy-and-competitive-analysis-1-demand-elasticity-and-marginal-analysis", "url": "#chapter-03-strategy-and-competitive-analysis-1-demand-elasticity-and-marginal-analysis", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Price elasticity of demand measures the percentage change in quantity demanded relative to a percentage change in price. Use an absolute value for a simple managerial read: above 1 is elastic, below 1 is inelastic, and 1 is unit elastic. Estimate it for a defined segment, offer, channel, geography, and time period; a company does not have one permanent elasticity. Observed price and quantity movements can also reflect promotions, seasonality, capacity, competitor actions, or customer mix, so a historical ratio is not automatically causal. [BB-C03-S20] Elasticity helps predict revenue response, not profit by itself. A manager still needs marginal analysis: compare the incremental revenue or benefit from the next unit, customer, feature, or capacity block with its incremental cost and risk. Costs already incurred and not recoverable are sunk for the focal decision; they should not be used to make a bad incremental action look good. In the long run, however, capacity, technology, and organization can change, so a sequence of short-run choices must still cover avoidable fixed costs and the required return on capital. [BB-C03-S21] [BB-C03-S22] Constructed B2B software test. A vendor sells 1,000 subscriptions at $100 with $30 incremental cost per subscription. A proposed price cut to $90 is expected to raise volume to 1,150. Arc elasticity is approximately 1.33, and revenue rises from $100,000 to $103,500. Yet contribution before fixed costs falls from $70,000 to $69,000. The example shows why “demand is elastic” is not a sufficient pricing recommendation: the team must test the demand estimate, capacity and service costs, churn, acquisition, price matching, customer fairness, and longer-run positioning." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-2-cost-scale-market-structure-and-market-power", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "2. Cost, scale, market structure, and market power", "headingId": "chapter-03-strategy-and-competitive-analysis-2-cost-scale-market-structure-and-market-power", "url": "#chapter-03-strategy-and-competitive-analysis-2-cost-scale-market-structure-and-market-power", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Marginal cost is the change in total cost caused by an incremental change in output; average cost is total cost divided by output. Economies of scale exist when long-run average cost falls as output expands; diseconomies arise when coordination, complexity, scarcity, congestion, or other costs push it up. Scale is therefore a testable cost relationship, not a synonym for size or a guarantee of advantage. [BB-C03-S21] Market structure changes which assumptions deserve the most attention: Table 3.1. Market-structure hypotheses and positioning tests. The rows are an author-created diagnostic; they do not classify a focal market or establish market power. | Structure | Managerial hypothesis | Five Forces connection | Positioning implication | | :--- | :--- | :--- | :--- | | Many close substitutes and easy entry | A firm has limited discretion over price unless it changes the offer or cost system | Rivalry, substitutes, and entrants constrain capture | Compete through a lower delivered-cost activity system, differentiated value, a narrower segment, or exit—not a slogan | | Differentiated rivals | Customer switching, brand, service, location, or features may create bounded discretion | Buyer power and substitutes differ by segment | Test willingness to pay against the full cost and imitability of differentiation | | A few interdependent rivals | Each move may change competitors' best responses | Rivalry cannot be analyzed independently of response | Model reactions, capacity, signaling, repeated interaction, and legal constraints before committing | | Durable entry barriers or bottlenecks | A firm may possess market power, but substitutes, regulation, innovation, and buyer response still constrain it | Entry barriers, supplier or buyer bottlenecks, and substitution define the mechanism | Do not confuse share with power or power with permission; test the market boundary and obtain legal review where needed | For antitrust analysis, U.S. agencies describe a relevant market as an area of effective competition with product and geographic dimensions; they use evidence including substitution, observed competition, market power, and a hypothetical-monopolist test. This regulatory method is not identical to a manager's Five Forces boundary, but it is a useful warning against choosing a convenient market definition. Legal classification is fact- and jurisdiction-specific; this chapter does not provide it. [BB-C03-S23]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-3-price-discrimination-versioning-and-bundling", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "3. Price discrimination, versioning, and bundling", "headingId": "chapter-03-strategy-and-competitive-analysis-3-price-discrimination-versioning-and-bundling", "url": "#chapter-03-strategy-and-competitive-analysis-3-price-discrimination-versioning-and-bundling", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "In economics and marketing, price discrimination describes charging different effective prices to customers or segments based on differences in willingness to pay rather than only differences in cost. Managerial implementations include negotiated terms, time or quantity tiers, versions, eligibility rules, and channel-specific offers. The economic label is broader than any particular statute. Before implementation, test measurement error, arbitrage, administration, accessibility, customer trust, disparate impact, contractual duties, and applicable law with qualified counsel. [BB-C03-S24] Bundling combines products or services under one offer. Bakos and Brynjolfsson show, in a model of information goods, that bundling can make aggregate valuations more predictable and can interact with segmentation; they also identify important limits involving marginal costs, correlated preferences, search or cognitive costs, and heterogeneous segments. Do not infer that every digital bundle raises profit or welfare. Compare separate sale, pure bundle, mixed bundle, and versioned menus using customer-level willingness-to-pay evidence, incremental cost, cannibalization, adoption, and competitive response. [BB-C03-S25] These tools connect directly to Porter positioning. A low-cost position requires an activity system that sustainably lowers delivered cost, not an indiscriminate price cut. A differentiated position requires customers in the target segment to value the difference enough to cover its incremental and fixed costs. A focused position requires evidence that the chosen segment has distinct needs or economics and that the configuration is difficult for broad rivals to match without tradeoffs. [BB-C03-S02] [BB-C03-S03]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-4-information-asymmetry-diagnose-when-the-hidden-information-matters", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "4. Information asymmetry: diagnose when the hidden information matters", "headingId": "chapter-03-strategy-and-competitive-analysis-4-information-asymmetry-diagnose-when-the-hidden-information-matters", "url": "#chapter-03-strategy-and-competitive-analysis-4-information-asymmetry-diagnose-when-the-hidden-information-matters", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Adverse selection occurs before agreement: one party has relevant private information about type or quality, so an offer can attract a worse mix than the decision-maker expects. Akerlof's used-car model shows how quality uncertainty can reduce trade and how institutions can arise to counter the problem; it is a model, not proof that every secondhand market collapses. [BB-C03-S26] Moral hazard occurs after agreement: an action or effort that affects outcomes is costly or impossible for the other party to observe, while the actor does not bear the full consequence. Arrow's analysis of medical-care markets connects uncertainty, insurance, information, and institutional responses; the logic also appears in lending, warranties, employment, outsourcing, cybersecurity, and platform governance. [BB-C03-S27] Table 3.2. Information-asymmetry issue-spotting matrix. The mechanisms are candidate controls to test; they are not universal remedies or legal requirements. | Information problem | Diagnostic question | Candidate mechanisms to test | Failure mode | | :--- | :--- | :--- | :--- | | Adverse selection | What privately known type or quality changes the expected value before we transact? | Verification, screening, warranties, reputation, certification, collateral, trial periods, self-selecting contract menus | Good types leave, bad types pool, or useful trade is deterred | | Moral hazard | What consequential action becomes hidden or weakly owned after agreement? | Monitoring, milestones, audit rights, deductibles or shared exposure, outcome measures, staged authority, termination and remedy clauses | Gaming, excessive risk, underinvestment, or distorted effort | Each mechanism has costs and can exclude, burden, or misclassify legitimate participants. Test proportionality, error rates, appeal, privacy, incentives, and who bears the downside rather than treating “more monitoring” as the default. Open educational treatments provide operational examples of warranties, reputation, collateral, cost sharing, and monitoring; the design still requires context-specific evidence and governance. [BB-C03-S28]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-5-strategic-response-with-a-payoff-matrix", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "5. Strategic response with a payoff matrix", "headingId": "chapter-03-strategy-and-competitive-analysis-5-strategic-response-with-a-payoff-matrix", "url": "#chapter-03-strategy-and-competitive-analysis-5-strategic-response-with-a-payoff-matrix", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A payoff matrix makes interdependence explicit: list each player's feasible actions and record the outcomes that each player expects under every action pair. The numbers below are constructed contribution indexes , not forecasts. Higher is better for the named firm. [BB-C03-S29] Table 3.3. Constructed two-firm response matrix for a price move. Read each cell as (Firm A, Firm B) . | Firm A \\ Firm B | Hold value-based price | Cut price | | :--- | :---: | :---: | | Hold value-based price | (8, 8) | (3, 10) | | Cut price | (10, 3) | (5, 5) | In this constructed matrix, if each firm believes a price cut protects it whether the rival holds or cuts, both may cut and reach (5,5) even though (8,8) is better for each. The matrix does not recommend coordination: competitor agreements about price, output, customers, or markets can be unlawful. It reveals assumptions to test independently—demand response, cost asymmetry, capacity, differentiation, time horizon, observability, entry, and whether the game is sequential or repeated. OpenStax uses an oligopoly payoff matrix to teach this strategic interdependence; Nash's seminal non-cooperative framework supplies the equilibrium concept, but a stylized equilibrium is not a prediction that real managers are fully informed or mechanically rational. [BB-C03-S29] [BB-C03-S30] Manager's bridge back to strategy: Replace each Five Forces label with an economic mechanism and a disconfirming test. Then choose the position and reinforcing activities that change the mechanism in the firm's favor without assuming that customer response, cost advantage, secrecy, legality, or competitor inaction will persist." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-input-output-interlinkages", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Input/Output Interlinkages", "headingId": "chapter-03-strategy-and-competitive-analysis-input-output-interlinkages", "url": "#chapter-03-strategy-and-competitive-analysis-input-output-interlinkages", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Inputs: Customer and experimentation evidence from Chapter 5; cost and capacity evidence from Chapter 6; legal and governance constraints from Chapter 2. Outputs: Pricing and segment hypotheses for Chapter 14; value and sensitivity tests for Chapter 4; operating commitments for Chapter 8. Boundary: Chapter 3 uses microeconomics to test competitive strategy. It does not replace a full course in consumer choice, production theory, welfare economics, auctions, mechanism design, labor economics, or antitrust law. ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-troubleshooting-guide-strategic-analysis", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Troubleshooting Guide: Strategic Analysis", "headingId": "chapter-03-strategy-and-competitive-analysis-troubleshooting-guide-strategic-analysis", "url": "#chapter-03-strategy-and-competitive-analysis-troubleshooting-guide-strategic-analysis", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptom: \"Our Five Forces analysis says our industry is highly attractive, but we are consistently unprofitable.\" Hypotheses to test: The industry boundary, time period, force evidence, firm position, business-model economics, accounting, execution, or interaction with complements and regulation may be wrong or incomplete. Action: Reconcile segment-level price, volume, cost, capital, and return evidence; test alternative boundaries; and analyze complements and non-market forces separately rather than forcing them into an averaged score. Symptom: \"We did a VRIO analysis, and it looks like we have no sources of sustained competitive advantage.\" Hypotheses to test: The resource may create parity, the unit of analysis may be wrong, complements or appropriation may be missing, or observed performance may come from another mechanism. Action: Validate customer value and willingness to pay, competitor access, imitation paths, substitutes, complements, organization, and erosion. Compare operational improvement, repositioning, capability building, partnership, and exit options; VRIO does not choose among them. Symptom: \"We launched a differentiated offer, but competitors copied it sooner than expected.\" Hypotheses to test: The differentiated factors may be easy to observe and imitate, customers may not value the difference, complementary assets may be weak, or the team may have confused launch novelty with appropriable advantage. Action: Re-test willingness to pay, cost, imitation, IP and secrecy options, brand, community, switching, distribution, ecosystem governance, and continuous innovation. Do not create artificial switching costs or file for protection without customer, economic, ethical, and legal analysis. Symptom: \"Our BCG Matrix says we should 'harvest' our cash cow, but that business unit is where all our best talent is.\" [BB-C03-S07] Hypothesis to test: The quadrant may omit talent, technology, brand, contracts, obligations, option value, or shared capabilities. [BB-C03-S07] Action: Treat the matrix as a prompt. Value invest, maintain, redesign, stage, harvest, and exit alternatives after mapping interdependencies and transferability; do not let a quadrant authorize the decision. ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-1-strategy-requires-tradeoffs-and-fit", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "1. Strategy requires tradeoffs and fit", "headingId": "chapter-03-strategy-and-competitive-analysis-1-strategy-requires-tradeoffs-and-fit", "url": "#chapter-03-strategy-and-competitive-analysis-1-strategy-requires-tradeoffs-and-fit", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Strategy is not a collection of attractive initiatives. It chooses a distinctive value proposition, configures reinforcing activities, and declines incompatible options. State the customer and need served, activities that differ, what the firm will not do, and the evidence that the system creates and captures value. [BB-C03-S03] Decision test: If every competitor could adopt the statement without changing activities or abandoning an option, it is probably an aspiration rather than a strategy." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-2-diagnose-before-prescribing", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "2. Diagnose before prescribing", "headingId": "chapter-03-strategy-and-competitive-analysis-2-diagnose-before-prescribing", "url": "#chapter-03-strategy-and-competitive-analysis-2-diagnose-before-prescribing", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Rumelt's strategy kernel links a diagnosis of the challenge to a guiding policy and coherent actions. The diagnosis should identify the mechanism, constraints, and disconfirming evidence—not just a symptom or goal. Actions should reinforce one another and have owners, resources, sequencing, and stop conditions. [BB-C03-S16]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-3-anticipate-response-and-second-order-effects", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "3. Anticipate response and second-order effects", "headingId": "chapter-03-strategy-and-competitive-analysis-3-anticipate-response-and-second-order-effects", "url": "#chapter-03-strategy-and-competitive-analysis-3-anticipate-response-and-second-order-effects", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A strategic action changes incentives for customers, suppliers, competitors, regulators, employees, and complementors. Map plausible responses and feedback before treating an immediate effect as the outcome. For example, a constructed price reduction might increase demand initially, prompt matching, compress industry margins, change perceived quality, or alter service capacity; which path occurs requires evidence." }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-4-treat-advantage-as-an-erosion-hypothesis", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "4. Treat advantage as an erosion hypothesis", "headingId": "chapter-03-strategy-and-competitive-analysis-4-treat-advantage-as-an-erosion-hypothesis", "url": "#chapter-03-strategy-and-competitive-analysis-4-treat-advantage-as-an-erosion-hypothesis", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Resource, capability, position, and network advantages can erode as technology, preferences, complements, regulation, or imitation change. Estimate the mechanism and time horizon, monitor signposts, and invest in renewal without assuming that “dynamic capability” itself proves adaptability. [BB-C03-S04] [BB-C03-S05]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-5-separate-industry-effects-from-firm-effects", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "5. Separate industry effects from firm effects", "headingId": "chapter-03-strategy-and-competitive-analysis-5-separate-industry-effects-from-firm-effects", "url": "#chapter-03-strategy-and-competitive-analysis-5-separate-industry-effects-from-firm-effects", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Industry structure can affect profit mechanisms, while positioning, resources, activities, execution, timing, and luck also produce within-industry differences. Do not calculate an “attractiveness average” or infer that execution cannot overcome structure. Compare segment-level economics, firm-specific evidence, and alternative boundaries before choosing repositioning, capability investment, partnership, or exit. [BB-C03-S01] [BB-C03-S02]" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-integrated-decision-record", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Integrated decision record", "headingId": "chapter-03-strategy-and-competitive-analysis-integrated-decision-record", "url": "#chapter-03-strategy-and-competitive-analysis-integrated-decision-record", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 3.4. Constructed strategy-kernel decision record. This author-created worksheet connects diagnosis, choice, coherent actions, scenarios, and review evidence. | Element | Required evidence | Decision output | | :--- | :--- | :--- | | Diagnosis | Customer, competitor, industry, capability, financial, operating, and non-market evidence; uncertainty and disconfirmers | One bounded challenge and causal mechanism | | Guiding policy | Alternatives, tradeoffs, constraints, value logic, stakeholder effects, and rejected options | A choice that narrows action | | Coherent actions | Owners, resources, dependencies, sequencing, controls, and stop conditions | Mutually reinforcing commitments | | Scenario test | Critical uncertainties, signposts, robustness, reversibility, and option value | Staged and contingent actions | | Review | Measures, evidence owner, decision date, and failure criteria | Continue, adapt, stage, or stop | This table is an original synthesis of positioning, resource, scenario, and strategy-kernel sources. [BB-C03-S03] [BB-C03-S04] [BB-C03-S13] [BB-C03-S16] ---" }, { "id": "chapter-03-strategy-and-competitive-analysis::chapter-03-strategy-and-competitive-analysis-chapter-summary", "kind": "chapter", "itemSlug": "chapter-03-strategy-and-competitive-analysis", "itemTitle": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "heading": "Chapter Summary", "headingId": "chapter-03-strategy-and-competitive-analysis-chapter-summary", "url": "#chapter-03-strategy-and-competitive-analysis-chapter-summary", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Strategy is a choice under constraints, not a framework score. A decision-grade strategy should: 1. Define the customer, need, industry boundary, time horizon, and focal challenge. 2. Diagnose external mechanisms with Five Forces and PESTLE without averaging ordinal labels or treating a scan as a forecast. [BB-C03-S01] [BB-C03-S09] 3. Replace each force label with a testable demand, cost, scale, bargaining, information, or strategic-response mechanism; distinguish revenue from contribution and average from marginal economics. [BB-C03-S20] [BB-C03-S21] [BB-C03-S28] [BB-C03-S29] 4. Diagnose resources, capabilities, appropriation, complements, and erosion with RBV, VRIO, core competence, and dynamic-capabilities lenses. [BB-C03-S04] [BB-C03-S05] [BB-C03-S11] 5. Generate genuinely different options using product-market direction, value-curve, portfolio, platform, pricing, and positioning questions without allowing a quadrant or payoff matrix to make the decision. [BB-C03-S06] [BB-C03-S07] [BB-C03-S08] [BB-C03-S14] [BB-C03-S25] 6. Choose a guiding policy, reject incompatible options, and specify mutually reinforcing actions with owners and resources. [BB-C03-S03] [BB-C03-S16] 7. Test value and operating feasibility in Chapter 4 and Chapter 6. 8. Stress-test critical uncertainties with scenarios, signposts, staged commitments, competitor responses, and stop conditions. [BB-C03-S12] [BB-C03-S13] [BB-C03-S29] 9. Translate the choice into execution and learning through Chapter 8. Manager's final check: Can the team state the diagnosis, choice, what it will not do, value mechanism, key assumptions, coherent actions, owners, signposts, and evidence that would cause the strategy to change? If not, the output remains analysis or aspiration rather than a complete strategy. Next: Chapter 4: Financial Analysis and Valuation tests whether the strategic option creates risk-adjusted value under explicit assumptions and constraints." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Financial Analysis and Valuation", "headingId": "chapter-04-financial-analysis-and-valuation", "url": "#chapter-04-financial-analysis-and-valuation", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-executive-summary", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Executive Summary", "headingId": "chapter-04-financial-analysis-and-valuation-executive-summary", "url": "#chapter-04-financial-analysis-and-valuation-executive-summary", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter provides an operator's toolkit for financial analysis and valuation. We demystify the core frameworks used by finance professionals and translate them into practical tools for making better investment decisions, managing performance, and understanding the true economic engine of your business. From the fundamentals of a DCF model to the modern metrics that drive SaaS companies, this guide focuses on practical application, troubleshooting, and the critical mental models that separate financial literacy from true financial wisdom. Author synthesis: The chapter's workflow and decision records are author-created teaching devices that organize accounting, valuation, finance, and operating concepts; they are not investment, accounting, tax, or legal advice. Constructed material: Numerical examples, ranges, diagrams, and decision records are illustrative unless a named source or company filing is identified. Validate current data and obtain qualified review before relying on a valuation or transaction conclusion." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-manager-outcomes", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Manager Outcomes", "headingId": "chapter-04-financial-analysis-and-valuation-manager-outcomes", "url": "#chapter-04-financial-analysis-and-valuation-manager-outcomes", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "By the end of this chapter, a manager should be able to reconcile operating assumptions to the statements and cash flow; build and audit a DCF; compare market, break-even, unit-economic, and option evidence; distinguish association from causation; and recommend an action with assumptions, downside liquidity, decision rights, and stop rules. Educational boundary: These tools support managerial learning; they are not investment, accounting, tax, or legal advice. High-stakes valuations and transactions require qualified finance, accounting, tax, and legal owners." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-the-managerial-finance-spine", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "The Managerial Finance Spine", "headingId": "chapter-04-financial-analysis-and-valuation-the-managerial-finance-spine", "url": "#chapter-04-financial-analysis-and-valuation-the-managerial-finance-spine", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For an operating DCF, distinguish free cash flow to the firm from free cash flow to equity and match each cash flow to its discount rate. Discount FCFF at the weighted average cost of capital to estimate operating-asset value, add non-operating assets, and subtract non-equity claims to reach equity value. Compare the range with relative-valuation evidence only after testing whether peers are similar in risk, growth, and cash-flow characteristics. [BB-C04-S13] [BB-C04-S14]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-financial-reporting-and-accounting-quality-foundation", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Financial Reporting and Accounting-Quality Foundation", "headingId": "chapter-04-financial-analysis-and-valuation-financial-reporting-and-accounting-quality-foundation", "url": "#chapter-04-financial-analysis-and-valuation-financial-reporting-and-accounting-quality-foundation", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Valuation begins with a reconciled reporting model, not a multiple or discount rate. For manager-level analysis, use the income statement, balance sheet, and statement of cash flows together, then read the statement of shareholders' equity and the notes for policies, estimates, obligations, and noncash activity. The SEC's investor guide emphasizes that the statements are related and that no one statement tells the complete story. [BB-C04-S17]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-three-statement-linkage", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Three-statement linkage", "headingId": "chapter-04-financial-analysis-and-valuation-three-statement-linkage", "url": "#chapter-04-financial-analysis-and-valuation-three-statement-linkage", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The income statement reports performance over a period under an applicable accounting framework. The balance sheet reports recognized assets, liabilities, and equity at a point in time. The cash flow statement explains changes in cash through operating, investing, and financing activities; under the indirect method, operating cash flow reconciles from net income through noncash items and changes in operating assets and liabilities. [BB-C04-S17] [BB-C04-S19] Figure 4.1. Three-statement linkage and managerial audit trail. This author-created diagram shows the main reconciliation paths; it is not a complete accounting system or a substitute for the applicable reporting standards. [BB-C04-S17] [BB-C04-S18] [BB-C04-S19] Text equivalent: Transactions, contracts, estimates, and events pass through recognition, measurement, classification, and disclosure before appearing in the financial statements. Net income and changes in operating balance-sheet accounts reconcile to operating cash flow. Investing and financing activities join operating cash flow to explain the change in cash, which must reconcile to ending balance-sheet cash. Managers review all three statements together with policies, estimates, commitments, and noncash disclosures before using the numbers in a valuation. Source note: Original teaching diagram based on the SEC's statement descriptions and reconciliation guidance and FASB's accrual-accounting concepts. [BB-C04-S17] [BB-C04-S18] [BB-C04-S19] Use a roll-forward rather than a story: 1. Start with opening balance-sheet amounts and the period's transactions. 2. Reconcile revenue, expenses, gains, losses, and net income to recognized balance-sheet changes. 3. Reconcile net income to operating cash flow, explicitly identifying noncash charges and operating working-capital movements. 4. Trace capital expenditure and asset sales to investing cash flow and the related asset roll-forwards. 5. Trace borrowing, repayment, equity issuance, repurchase, and distributions to financing cash flow, debt/equity balances, and the statement of shareholders' equity. 6. Confirm that opening cash plus operating, investing, financing, and exchange-rate effects equals closing cash. Investigate differences rather than inserting an unexplained plug." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-accrual-cash-and-recognition", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Accrual, cash, and recognition", "headingId": "chapter-04-financial-analysis-and-valuation-accrual-cash-and-recognition", "url": "#chapter-04-financial-analysis-and-valuation-accrual-cash-and-recognition", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Accrual accounting records the effects of transactions and other events in the periods in which those effects occur, even when cash is received or paid in another period. Accruals, deferrals, and allocations therefore create legitimate differences between earnings and cash. They also introduce estimates and timing judgments that must be understood. FASB's Concepts Statement explains these relationships but is nonauthoritative—it does not replace the Accounting Standards Codification or another applicable reporting framework. [BB-C04-S18] For each material line item, ask: - Recognition: What asset, liability, revenue, expense, gain, or loss was recognized, under which current policy and contract terms? - Measurement: Which price, estimate, useful life, impairment, collectibility, probability, or allocation assumption affects the amount? - Timing: What performance or obligation occurred this period, and when did or will the associated cash move? - Classification: Is the item operating, investing, financing, recurring, discontinued, segment-specific, or another disclosed category under the applicable framework? - Disclosure: Which note explains the policy, disaggregation, judgment, uncertainty, commitment, contingency, or noncash effect? Do not “correct” accrual accounting by replacing recognized revenue or expense with billings or cash receipts. For U.S. public-company disclosure, SEC staff guidance warns that an individually tailored non-GAAP measure can be misleading when it changes GAAP recognition and measurement—for example, accelerating ratable revenue or changing an accrual-basis measure to a cash basis. [BB-C04-S20]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-normalization-and-earnings-quality", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Normalization and earnings quality", "headingId": "chapter-04-financial-analysis-and-valuation-normalization-and-earnings-quality", "url": "#chapter-04-financial-analysis-and-valuation-normalization-and-earnings-quality", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Normalization is an analytical bridge from reported results to a clearly defined decision view; it is not permission to erase inconvenient costs or rewrite accounting. Start with the reported measure, reconcile every adjustment, apply the rule consistently across periods, retain gains as well as charges, and show both reported and adjusted outcomes. SEC staff guidance warns about excluding normal recurring cash operating expenses, inconsistent adjustments, asymmetric treatment of gains and charges, vague labels, and individually tailored recognition. [BB-C04-S20] Treat “earnings quality” as a structured set of questions rather than one score: Table 4.1. Earnings-quality question matrix. This author-created diagnostic organizes evidence and its limits; it is not an accounting-quality score. | Quality question | Evidence to inspect | What the evidence does not prove | | :--- | :--- | :--- | | Do earnings reconcile to cash? | Operating cash-flow reconciliation; working-capital changes; noncash charges; classification; noncash investing and financing | A high cash-conversion ratio does not by itself establish sustainable earnings or correct classification. | | Are revenues and margins repeatable? | Contract terms; recognition policy; returns; concessions; concentration; backlog definition; cohort and segment mix | Recurrence does not make a transaction profitable or low risk. | | Are estimates changing the trend? | Allowances; useful lives; capitalization; impairment; provisions; fair values; tax assumptions | A changed estimate is not automatically manipulation or error. | | Are “one-time” items actually unusual? | Multi-period adjustment ledger; cash requirements; restructuring history; gains and charges | Management's label does not determine recurrence or economic relevance. | | Does the balance sheet support the story? | Receivables, inventory, contract assets/liabilities, payables, debt, provisions, retained earnings | A balanced accounting equation does not establish measurement quality or solvency. | | Are adjusted measures decision-useful? | Exact definition, GAAP/IFRS reconciliation, consistency, tax, cash, and segment effects | Reconciliation does not make an adjusted measure comparable across companies or suitable for every decision. | The SEC Chief Accountant notes that investors may use cash-flow information to investigate differences between net income and cash receipts and payments and that cash-flow information is often used as a proxy for earnings quality. The same statement also warns that cash-flow classification and control failures are themselves reporting-quality risks. Cash is therefore a challenge to the earnings story, not an automatic verdict on it. [BB-C04-S19]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-cost-behavior-allocation-and-decision-relevance", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Cost behavior, allocation, and decision relevance", "headingId": "chapter-04-financial-analysis-and-valuation-cost-behavior-allocation-and-decision-relevance", "url": "#chapter-04-financial-analysis-and-valuation-cost-behavior-allocation-and-decision-relevance", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Cost labels depend on the decision, activity driver, time horizon, and relevant range. OpenStax distinguishes fixed, variable, and mixed behavior and stresses that the same cost can be classified differently for different managerial uses. Fixed cost per unit falls mechanically as volume rises within a stated range; that does not mean the total commitment disappears or that added volume is profitable. [BB-C04-S21] Before using a product, customer, channel, or project margin: 1. Define the decision and period. 2. Identify costs and cash flows that change because of the decision, including step costs, capacity additions, support, working capital, cannibalization, and opportunity cost. 3. Separate direct tracing from allocated overhead. 4. State each allocation pool and driver and test whether it reflects resource consumption. 5. Reconcile the managerial view to the financial-reporting totals without claiming that the internal allocation is GAAP or IFRS reporting. 6. Run sensitivity to volume, mix, driver choice, capacity, and shared-cost treatment. Traditional overhead allocation may be adequate when one driver reasonably tracks overhead; activity-based costing uses multiple activity drivers and can change product-cost comparisons, but it adds data and maintenance cost and remains a managerial model. OpenStax explicitly distinguishes supplemental ABC information from the costing required for external financial reporting. [BB-C04-S22] Managerial rule: allocated cost answers “how did we distribute a shared amount under this rule?” Incremental cost answers “what changes if we choose this alternative?” Neither answer should silently substitute for the other." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-risk-return-and-cost-of-capital-estimation", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Risk, Return, and Cost-of-Capital Estimation", "headingId": "chapter-04-financial-analysis-and-valuation-risk-return-and-cost-of-capital-estimation", "url": "#chapter-04-financial-analysis-and-valuation-risk-return-and-cost-of-capital-estimation", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The cost of capital is an opportunity-cost estimate for investments of equivalent risk and a discount rate for matching cash flows—not a historical interest rate, a desired return, or a receptacle for every uncertainty. Its inputs are estimated, time-varying, and model-dependent. Report a transparent range and the decision sensitivity rather than a ceremonial decimal. [BB-C04-S23] For a simple debt-and-equity structure: WACC = (E / (D + E)) x Cost of Equity + (D / (D + E)) x Pre-Tax Cost of Debt x (1 - Applicable Tax Rate) Add preferred stock, leases, convertibles, or other financing only after defining and valuing their debt-like and equity-like components. The tax adjustment depends on the jurisdiction, deductibility, and ability to use the tax benefit; a current loss-making company may not receive the modeled shield in the forecast period. [BB-C04-S23]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-a-transparent-estimation-workflow", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "A transparent estimation workflow", "headingId": "chapter-04-financial-analysis-and-valuation-a-transparent-estimation-workflow", "url": "#chapter-04-financial-analysis-and-valuation-a-transparent-estimation-workflow", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 4.2. Risk-consistent cost-of-capital workflow. This original control flow separates cash-flow definition, project risk, market inputs, financing, and review. It does not prescribe CAPM, one beta source, or one capital structure. [BB-C04-S23] Text equivalent: Define the decision and incremental cash flows, then set currency, inflation basis, tax, and horizon. Decide whether company risk is genuinely representative; otherwise use divisional or project-risk comparables. Estimate cost of equity, current cost of debt, usable tax benefit, and justified financing weights. Compute a range, test cash-flow and discount-rate consistency, run value sensitivity, obtain independent finance review, and record whether to approve, stage, redesign, delay, or reject. Source note: Original synthesis based on Damodaran's author-hosted cost-of-capital paper, including equivalent-risk opportunity cost, project-versus-company risk, current cost of debt, currency consistency, tax capacity, and market-value weighting. [BB-C04-S23] Use the following control record: Table 4.2. Cost-of-capital input control record. The rows identify documentation and challenge questions, not a universal estimation recipe. | Input | Minimum documentation | Challenge question | | :--- | :--- | :--- | | Cash flow | FCFF or FCFE; incremental versus total; currency; nominal/real; tax; horizon; scenario treatment | Does the discount rate price the same claim and risk as the cash flow? | | Risk-free rate | Date, currency, term, default-risk treatment, nominal/real basis | Is the rate consistent with cash-flow currency and inflation? | | Cost of equity | Model; market premium; beta or exposure estimate; comparable set; leverage adjustment; country/other risk treatment | How unstable are the inputs, and would another defensible method reverse the decision? | | Cost of debt | Current borrowing/default evidence in the analysis currency; seniority; term; fees; covenants | Are we using today's marginal cost rather than the coupon or historical book interest rate? | | Tax benefit | Applicable marginal treatment, jurisdiction, deductibility, loss and capacity constraints, timing | Is the tax shield actually usable in each forecast period? | | Weights | Current market values or justified target financing; debt-like claims and hybrids | Are book weights, project-specific funding, or circular valuation assumptions distorting the result? | | Review | Range, sensitivities, source dates, owner, independent reproduction, decision threshold | Which input most changes value, and what evidence would update it? |" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-company-division-and-project-risk-are-not-interchangeable", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Company, division, and project risk are not interchangeable", "headingId": "chapter-04-financial-analysis-and-valuation-company-division-and-project-risk-are-not-interchangeable", "url": "#chapter-04-financial-analysis-and-valuation-company-division-and-project-risk-are-not-interchangeable", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Using the company WACC can be reasonable when the company operates in one business and the project is genuinely similar in operating risk and financing. A multi-business company should normally investigate divisional risk. Entry into a new business requires project-risk evidence from comparable activities rather than automatic use of the parent company's rate. Damodaran specifically warns that one company-wide hurdle rate can cause safer businesses to subsidize riskier ones and that using a project's own debt-heavy financing ratio can create another subsidy. [BB-C04-S23] Do not hide discrete failure, approval, litigation, construction, launch, or adoption risk in an arbitrary discount-rate premium. Put decision-specific events into scenarios, decision trees, or cash flows when they can be modeled; reserve the cost of capital for the market-priced continuous risks the selected method is intended to represent. Do not double-count the same risk in both cash flows and the rate. [BB-C04-S23]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limitations-and-accountable-use", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limitations and accountable use", "headingId": "chapter-04-financial-analysis-and-valuation-limitations-and-accountable-use", "url": "#chapter-04-financial-analysis-and-valuation-limitations-and-accountable-use", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Cost-of-equity estimates change with model, market premium, comparable set, beta/exposure method, leverage, geography, and date. - A private company or project may lack traded equity and debt; comparable selection and capital structure become judgment-heavy. - Current market-value debt may require estimation, and hybrid securities may need separate components. - Leverage, business mix, and risk can change during the forecast, so one static WACC may be inconsistent with the projected company. - A lower WACC does not prove a financing plan is safer or value creating; additional debt can increase equity and default risk. - Small changes in the discount rate can matter, but cash-flow and terminal-value errors often dominate. Allocate review effort accordingly. [BB-C04-S23] The decision record should preserve the base, low, and high rate; input sources and dates; excluded risks; cash-flow adjustments; sensitivity; competing methods; reviewer; and the evidence that would trigger re-estimation." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-capital-budgeting-and-financing-policy", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Capital budgeting and financing policy", "headingId": "chapter-04-financial-analysis-and-valuation-capital-budgeting-and-financing-policy", "url": "#chapter-04-financial-analysis-and-valuation-capital-budgeting-and-financing-policy", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Investment and financing decisions interact. Compare debt, equity, retained cash, partnership, leasing, and staged commitments by cost, flexibility, covenant and control effects, distress/refinancing exposure, agency incentives, tax capacity, and the alternatives forgone. Payout, repurchase, and distribution decisions should be evaluated against investment needs, liquidity, leverage, investor rights, and downside—not as a universal residual formula. Bounded cost-of-equity method (author teaching note): When a market-based model is appropriate, a simple CAPM expression is Cost of Equity = Risk-Free Rate + Beta × Equity Risk Premium . Define the currency, date, beta or exposure estimate, market-premium method, leverage, country/other risk treatment, and why the comparable risk is relevant. CAPM is a model choice, not a measurement of a company's true required return; compare it with other defensible methods and show the decision sensitivity. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-troubleshooting-guide-financial-analysis", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Troubleshooting Guide: Financial Analysis", "headingId": "chapter-04-financial-analysis-and-valuation-troubleshooting-guide-financial-analysis", "url": "#chapter-04-financial-analysis-and-valuation-troubleshooting-guide-financial-analysis", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptom: \"Our DCF model shows our company is worth $100M, but we just got an acquisition offer for $500M. Is our model wrong?\" Diagnosis: Your DCF calculates intrinsic value. The acquisition offer includes strategic value. The acquirer may be seeing massive cost or revenue synergies that don't apply to you as a standalone entity. Action: Evaluate the offer based on strategic value. Is the acquirer a competitor (eliminating you is valuable)? Can they cross-sell your product to their massive customer base (revenue synergy)? Don't just dismiss the offer because your DCF is lower. Constructed symptom: \"Our LTV/CAC ratio is a healthy 5.0, but we are still burning cash every month.\" Diagnosis: You have a long CAC Payback Period . LTV is realized over many years, but CAC is spent upfront in cash. If it takes 24 months to recoup your CAC, you need to fund 24 months of sales and marketing costs for every new customer before they become profitable. Action: Calculate payback using consistently timed revenue and contribution margin. Compare it with liquidity, contract length, retention, sector economics, and the company's own cohorts; do not use 18 months as a universal approval cutoff. Symptom: \"Our company's ROE (Return on Equity) is an amazing 40%, but our stock price is flat.\" Diagnosis: High financial leverage is one hypothesis. DuPont Analysis shows whether leverage, margin, or asset turnover mathematically contributes to ROE; it does not establish why the stock price changed. Action: Decompose ROE, compare components over time and with accounting-consistent peers, then investigate capital structure, one-offs, buybacks, negative equity, and operating drivers. [BB-C04-S06] Constructed symptom: \"We keep running out of cash, even when we have profitable months.\" Diagnosis: You have a long Working Capital Cycle . Your cash is trapped in accounts receivable and inventory. Action: Map your Cash Conversion Cycle: CCC = DSO + DIO - DPO . Test receivables, inventory, and payables together: use early-payment discounts, JIT inventory ( Chapter 6 ), or supplier-term changes only when the cash benefit outweighs margin, service, and supplier-relationship costs. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-1-dcf-discounted-cash-flow-model", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "1. DCF (Discounted Cash Flow) Model", "headingId": "chapter-04-financial-analysis-and-valuation-1-dcf-discounted-cash-flow-model", "url": "#chapter-04-financial-analysis-and-valuation-1-dcf-discounted-cash-flow-model", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Discounted Cash Flow (DCF) Valuation Valuation & Investment Decisions" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview", "url": "#chapter-04-financial-analysis-and-valuation-overview", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A DCF model estimates a company's or project's value under a specified forecast by discounting expected future free cash flows. It makes operating, reinvestment, horizon, and risk assumptions explicit; it does not eliminate forecast or model risk. Define whether cash flow is to the firm or equity and match the discount rate accordingly. [BB-C04-S13]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Forecast Free Cash Flows (FCF): Project the cash the business will generate over a decision-appropriate horizon after accounting for operating costs and investments in capital. A 5-10 year horizon is a constructed modeling convention, not a universal rule. FCF = NOPAT + D&A - CapEx - Change in Net Working Capital . 2. Determine Discount Rate (WACC): Estimate the after-tax cost of debt and the opportunity cost of equity using target market-value weights. Match the rate to the cash flow's currency, inflation basis, tax treatment, and risk; changing leverage may require a different method. 3. Calculate Terminal Value: Since a business has value beyond the forecast period, estimate its worth at the end of the period using a perpetual growth model or an exit multiple. 4. Calculate Enterprise and Equity Value: Discount free cash flow and terminal value to enterprise value. Subtract net debt and other senior claims and add non-operating assets to reach equity value. 5. Make the Decision: For a project, compare incremental NPV with mutually exclusive alternatives, liquidity, execution capacity, strategic constraints, externalities, and option value. A positive modeled NPV is evidence, not automatic approval. NPV versus IRR: Use NPV as the primary value criterion when cash-flow timing, scale, and risk are defined consistently. IRR is a rate summary that can mis-rank mutually exclusive projects, create multiple answers when cash flows change sign more than once, and embed a reinvestment interpretation that may not fit the decision. Use both only after checking the cash-flow pattern, and explain any conflict rather than letting IRR override a risk-consistent NPV. Figure 4.3. DCF assumptions, discounting, and value bridge. This original synthesis separates cash-flow construction from discount-rate estimation and the enterprise-to-equity bridge. [BB-C04-S13] Text equivalent: Build unlevered free cash flow from revenue, margin, reinvestment, working capital, tax, and horizon assumptions. Discount forecast cash flows and terminal value with a consistent WACC, combine them as enterprise value, bridge to equity value, and test the range against sensitivities and alternatives. Source note: Original diagram based on Damodaran's author-hosted treatment of FCFF, WACC, operating-asset value, non-operating assets, and the firm-to-equity bridge. [BB-C04-S13]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-source-boundary", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Source Boundary", "headingId": "chapter-04-financial-analysis-and-valuation-source-boundary", "url": "#chapter-04-financial-analysis-and-valuation-source-boundary", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The canonical Chapter 4 DCF and relative-valuation records support the bounded claims used here. Historical and practitioner reading lists are not treated as claim-level evidence unless a source is registered and inspected for the specific statement." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the DCF to make operating, reinvestment, timing, risk, and terminal-value assumptions visible before approving a project. - Compare NPV ranges with liquidity, strategic alternatives, execution capacity, and downside scenarios; a positive point estimate is not automatic approval. - Assign finance ownership for model reproduction, sensitivity, and the evidence that would trigger re-estimation." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Forecast error, terminal value, discount-rate choice, and inconsistent cash-flow definitions can dominate the output. - DCF is not intrinsic truth; early-stage, unstable, or option-rich projects may require scenarios, relative evidence, or staged commitments." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections", "url": "#chapter-04-financial-analysis-and-valuation-connections", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Revenue growth and margin assumptions are driven by your GTM Strategy (Chapter 14) and Competitive Analysis (Chapter 3) . Input: Capital expenditure (CapEx) forecasts come from your Operations team (Chapter 6) . Output: The valuation is a key input for M&A decisions and Executive Compensation (Chapter 2) design. The project NPVs are used to make Capital Allocation decisions. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-2-lbo-leveraged-buyout-model", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "2. LBO (Leveraged Buyout) Model", "headingId": "chapter-04-financial-analysis-and-valuation-2-lbo-leveraged-buyout-model", "url": "#chapter-04-financial-analysis-and-valuation-2-lbo-leveraged-buyout-model", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Leveraged Buyout (LBO) Model M&A Valuation" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview-2", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview-2", "url": "#chapter-04-financial-analysis-and-valuation-overview-2", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "An LBO model analyzes an acquisition where debt finances part of the purchase and the acquired company's cash flow services that debt. It estimates a sponsor-implied maximum price for a specified financing plan, operating case, fees, exit assumption, and return target—not intrinsic value or a negotiation floor. [BB-C04-S02] [BB-C04-S03]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply-2", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply-2", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Structure the Deal: Determine the Sources of funds (Sponsor Equity, various layers of Debt) and Uses of funds (Purchase Price, Fees). 2. Project Financials: Build a decision-appropriate forecast of the company's financials, often 5-7 years in a constructed teaching model, focusing on the Free Cash Flow available to pay down debt. 3. Model the Debt Schedule: Create a \"debt waterfall\" to show how cash flow services debt. 4. Calculate Returns at Exit: In a constructed teaching model, test a specified exit date and EV/EBITDA multiple; do not treat 5-7 years or one multiple as a universal convention. Calculate the final equity proceeds after remaining debt is paid. 5. Solve for IRR and MOIC (Multiple on Invested Capital)." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-2", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers-2", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the LBO model to test sponsor-implied price, debt service, downside liquidity, exit assumptions, and equity returns under a specified financing plan. - Separate operating improvement from leverage and multiple expansion so the return is not attributed to the wrong mechanism. - Treat debt capacity, covenants, governance, financing markets, and alternatives as decision inputs, not spreadsheet outputs." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-2", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques-2", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- LBO outputs are highly sensitive to entry price, leverage, operating forecast, refinancing, exit multiple, fees, and timing; they are not intrinsic value or a negotiation floor. - Leverage can magnify losses, restrict operating choices, and create conflicts; historical private-equity returns are sample- and period-dependent." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections-2", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections-2", "url": "#chapter-04-financial-analysis-and-valuation-connections-2", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The operational improvement plan for margin expansion is a direct input from Operations (Chapter 6) . Input: \"Debt capacity\" is determined by Financial Ratios (Framework 3, this chapter) . Output: The LBO model provides a sponsor-implied maximum purchase price under stated assumptions; transaction value still depends on alternatives, diligence, financing, governance, and negotiation. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-3-financial-ratios-modern-metrics", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "3. Financial Ratios & Modern Metrics", "headingId": "chapter-04-financial-analysis-and-valuation-3-financial-ratios-modern-metrics", "url": "#chapter-04-financial-analysis-and-valuation-3-financial-ratios-modern-metrics", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Financial Ratios & Modern Metrics Performance Analysis" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview-3", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview-3", "url": "#chapter-04-financial-analysis-and-valuation-overview-3", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Financial ratios distill complex financial statements into a dashboard of key health metrics. For an operator, they provide a rapid assessment of performance. While traditional ratios are important, modern digital businesses rely on a new set of metrics." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply-3", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply-3", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Reconcile the Statements: Check accounting definitions, period, one-offs, revenue quality, cash conversion, and balance-sheet changes before interpreting a ratio. 2. Select Decision-Relevant Metrics: For recurring-revenue businesses, define cohort LTV/CAC, payback, retention, and growth-plus-margin consistently. Any practitioner threshold is a context-specific comparison aid—not a health law. 3. Compare Carefully: Compare with the company's own history and genuinely comparable peers, adjusting for accounting policy, business model, capital intensity, maturity, seasonality, and market conditions. [BB-C04-S04] [BB-C04-S05]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-contrarian-thinking-the-tyranny-of-gross-margin", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: The Tyranny of Gross Margin", "headingId": "chapter-04-financial-analysis-and-valuation-contrarian-thinking-the-tyranny-of-gross-margin", "url": "#chapter-04-financial-analysis-and-valuation-contrarian-thinking-the-tyranny-of-gross-margin", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For software companies, CAC is ordinarily a sales-and-marketing acquisition expense rather than cost of goods sold. When LTV is already margin-adjusted as in Framework 7, customer-level contribution after acquisition cost is LTV - CAC ; if a revenue-based LTV is used instead, apply gross margin once before subtracting CAC. Keep service cost, cash timing, retention, and allocation assumptions explicit." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-3", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers-3", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use a small, reconciled set of ratios to identify questions about margin, liquidity, leverage, efficiency, cash conversion, and cohort economics. - Compare the company with its own history and genuinely comparable peers after checking accounting policy, capital intensity, maturity, and seasonality. - Treat Rule-of-40, LTV/CAC, and other thresholds as context-dependent heuristics, not approval laws." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-3", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques-3", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ratios compress complex statements and can be distorted by accounting choices, one-offs, negative equity, mix, timing, or peer differences. - Association between a ratio and later performance does not establish causation or guarantee excess returns." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections-3", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections-3", "url": "#chapter-04-financial-analysis-and-valuation-connections-3", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires raw data from all three financial statements. Output: Profitability and efficiency ratios are key inputs for identifying problems to be solved by Operations (Chapter 6) . Valuation ratios inform your Fundraising Strategy (Chapter 15) . ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-4-dupont-analysis-tree", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "4. DuPont Analysis Tree", "headingId": "chapter-04-financial-analysis-and-valuation-4-dupont-analysis-tree", "url": "#chapter-04-financial-analysis-and-valuation-4-dupont-analysis-tree", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "DuPont Analysis Tree Performance Decomposition" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview-4", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview-4", "url": "#chapter-04-financial-analysis-and-valuation-overview-4", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Return on Equity (ROE) is a key measure of profitability, but a high ROE can be misleading. DuPont Analysis is a framework that deconstructs ROE into its three core drivers: Profitability , Efficiency , and Financial Leverage . For an operator, this tool supports diagnosis of why ROE is what it is, including whether high returns are being generated through operational performance or financial leverage." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply-4", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply-4", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The 3-Step DuPont formula is: ROE = (Net Profit Margin) (Asset Turnover) (Financial Leverage) 1. Calculate Net Profit Margin: Net Income / Revenue . This measures profitability. 2. Calculate Asset Turnover: Revenue / Total Assets . This measures efficiency. 3. Calculate Financial Leverage: Total Assets / Shareholders' Equity . This measures leverage. The identity shows which component changed mathematically; causal diagnosis requires accounting review and operating evidence. [BB-C04-S06] Figure 4.4. DuPont decomposition of return on equity. The branches are multiplicative accounting components, not a causal tree. [BB-C04-S06] Text equivalent: Return on equity equals net profit margin multiplied by asset turnover and financial leverage. Compare each component over time and with accounting-consistent peers; then investigate operating and financing causes separately. Source note: Original redraw of the three-step DuPont identity; empirical interpretation is bounded by the active DuPont source record. [BB-C04-S06]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-contrarian-thinking-high-roe-can-be-a-major-red-flag", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: High ROE Can Be a Major Red Flag", "headingId": "chapter-04-financial-analysis-and-valuation-contrarian-thinking-high-roe-can-be-a-major-red-flag", "url": "#chapter-04-financial-analysis-and-valuation-contrarian-thinking-high-roe-can-be-a-major-red-flag", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "High financial leverage can increase ROE while also increasing financial risk, but the implication depends on debt terms, business stability, taxes, sector, equity balance, and alternatives. Avoid labeling ROE “high quality” from the identity alone; investigate the economics and accounting behind each component." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-source-boundary-2", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Source Boundary", "headingId": "chapter-04-financial-analysis-and-valuation-source-boundary-2", "url": "#chapter-04-financial-analysis-and-valuation-source-boundary-2", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The active DuPont source record supports the decomposition and bounded performance-interpretation claims used here. The identity is a diagnostic starting point, not evidence that a component caused a change or that a named empirical finding applies to every company." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-4", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers-4", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Decompose ROE into margin, asset turnover, and leverage before deciding whether a return improvement is operational or financial. - Use the tree to choose a measurable follow-up owner and KPI rather than treating ROE as a diagnosis. - Compare the components over time and with accounting-consistent peers, then investigate one-offs, buybacks, and negative equity." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-4", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques-4", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- DuPont is an identity, not a causal model; the same ROE can arise from very different risks and business economics. - High ROE can reflect leverage, shrinking equity, one-time gains, or asset impairment and does not by itself establish value creation." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections-4", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections-4", "url": "#chapter-04-financial-analysis-and-valuation-connections-4", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires data from the Income Statement and Balance Sheet. Output: The insights from DuPont analysis are critical for setting meaningful KPIs (Chapter 8) . If Asset Turnover is low, an operational KPI for the Operations team (Chapter 6) should be created to address it. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-5-working-capital-cycle-diagram", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "5. Working Capital Cycle Diagram", "headingId": "chapter-04-financial-analysis-and-valuation-5-working-capital-cycle-diagram", "url": "#chapter-04-financial-analysis-and-valuation-5-working-capital-cycle-diagram", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Working Capital Cycle Diagram Cash Flow Optimization" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview-5", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview-5", "url": "#chapter-04-financial-analysis-and-valuation-overview-5", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Working Capital Cycle (or Cash Conversion Cycle) estimates the average time between cash committed to operations and cash collected from customers. A longer cycle can indicate more cash tied up in operations, while a short or negative cycle can reflect favorable timing, business-model structure, or supplier financing. Neither direction is automatically efficient or sustainable. [BB-C04-S07]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply-5", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply-5", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Calculate the three components: 1. Days Inventory Outstanding (DIO): How long does inventory sit on the shelves? 2. Days Sales Outstanding (DSO): How long does it take to collect cash from customers after a sale? 3. Days Payable Outstanding (DPO): How long does it take you to pay your suppliers? Formula: Cash Conversion Cycle (CCC) = DIO + DSO - DPO Use the CCC to locate cash tied up in operations, not as a universal instruction to make the cycle as short as possible. Assess service, stockouts, pricing, customer terms, supplier health, and bargaining effects before changing a component. [BB-C04-S07] Figure 4.5. Operating and cash-conversion timeline. The diagram separates inventory time, receivables time, and supplier-payment timing so the DIO + DSO - DPO relationship is visible. [BB-C04-S07] Text equivalent: Inventory is received and held for DIO days before sale; customer cash is collected after DSO days; supplier cash is paid after DPO days. The average cash-conversion interval is DIO plus DSO minus DPO, subject to consistent period and balance definitions. Source note: Original timeline based on the cash-conversion-cycle relationship; the adjacent evidence supports association, not a universal causal instruction. [BB-C04-S07]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-source-boundary-3", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Source Boundary", "headingId": "chapter-04-financial-analysis-and-valuation-source-boundary-3", "url": "#chapter-04-financial-analysis-and-valuation-source-boundary-3", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The active working-capital source record supports observational evidence and the DIO/DSO/DPO diagnostic. It does not establish a universal target, causal minimization rule, or supplier-term prescription; those are manager hypotheses to test." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-5", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers-5", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the cash-conversion cycle to locate where operating cash is tied up and which process owner can change the timing. - Test receivables, inventory, payables, service levels, supplier relationships, and margin together before pursuing a cash release. - Distinguish a durable operating improvement from supplier financing, seasonality, or a temporary working-capital pull." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-5", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques-5", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A shorter cycle is not automatically better; it can reflect under-stocking, delayed payment, deteriorating terms, or a different business model. - The metric is sensitive to definitions, averages, seasonality, mix, and accounting classification; it does not prove causality or solvency." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections-5", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections-5", "url": "#chapter-04-financial-analysis-and-valuation-connections-5", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires data on inventory, accounts receivable, and accounts payable from the Balance Sheet . Output: This analysis directly informs operational improvement initiatives for the Supply Chain and Operations team (Chapter 6) , such as implementing Just-in-Time (JIT) inventory. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-6-cap-table-evolution-chart", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "6. Cap Table Evolution Chart", "headingId": "chapter-04-financial-analysis-and-valuation-6-cap-table-evolution-chart", "url": "#chapter-04-financial-analysis-and-valuation-6-cap-table-evolution-chart", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Cap Table Evolution Chart Equity & Ownership" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview-6", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview-6", "url": "#chapter-04-financial-analysis-and-valuation-overview-6", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A capitalization table records securities, ownership, and modeled dilution. Before a financing decision, use a fully diluted basis and model option-pool timing, convertibles or SAFEs, liquidation preferences, anti-dilution, and control rights with qualified legal and finance owners. [BB-C04-S08]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply-6", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply-6", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Initial Setup: List all equity holders and the number of shares they own. Calculate the percentage ownership for each. 2. Model a New Financing Round: Assume a pre-money valuation (the company's value before the new investment). Add the new investment amount to get the post-money valuation . The new investor's ownership is Investment Amount / Post-Money Valuation . Calculate the new share price and the number of new shares issued. 3. Recalculate Ownership: Show how the percentage ownership of all existing holders has been diluted by the new share issuance. 4. Update the Option Pool: Founders and the board will typically expand the employee stock option pool as part of a new financing round to attract future talent." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-6", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers-6", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the fully diluted cap table to understand ownership, dilution, preferences, control, and the distribution of value under financing or exit scenarios. - Model option-pool timing, convertibles or SAFEs, anti-dilution, liquidation preferences, and governance rights with finance and legal owners. - Show who bears dilution and downside under each financing alternative rather than reporting a single post-money percentage." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-6", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques-6", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A cap table is a model of rights and assumptions, not a guarantee of legal ownership, payout, or future financing terms. - Valuation, preferences, conversion, vesting, tax, and control provisions can be disputed or fact-specific; the worksheet is not legal advice." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections-6", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections-6", "url": "#chapter-04-financial-analysis-and-valuation-connections-6", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The company's valuation is a key input, derived from a DCF (Framework 1) or, more likely for a startup, from Comparable Transactions in the venture market. Output: The cap table is a critical component of any Fundraising Strategy (Chapter 15) and informs how to structure Executive Compensation (Chapter 2) with equity. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-7-unit-economics-calculator", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "7. Unit Economics Calculator", "headingId": "chapter-04-financial-analysis-and-valuation-7-unit-economics-calculator", "url": "#chapter-04-financial-analysis-and-valuation-7-unit-economics-calculator", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Unit Economics (LTV/CAC) Business Model Viability" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview-7", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview-7", "url": "#chapter-04-financial-analysis-and-valuation-overview-7", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Unit economics describe contribution economics at a decision-relevant unit, often a customer or cohort. LTV/CAC can be useful when acquisition, retention, margin, service cost, and cash timing are consistently defined, but it does not prove company profitability, liquidity, or scalability. [BB-C04-S09]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply-7", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply-7", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Calculate Customer Acquisition Cost (CAC): CAC = Total Sales & Marketing Spend / # of New Customers Acquired . Ensure this is \"fully loaded\" including salaries and overhead. 2. Calculate Customer Lifetime Value (LTV): Simplified teaching shortcut: LTV = (Avg. Revenue Per Customer Per Year Gross Margin %) / Customer Churn Rate . Use only when the cohort, retention, service-cost, discounting, and steady-state assumptions are explicit; use a richer cohort model when they are not. 3. Interpret the Range: Compare cohorts, scenarios, cash payback, retention uncertainty, contribution margin, service/support burden, fixed costs, and capital needs. Practitioner bands such as 3x may prompt questions in some SaaS contexts; they are author-labeled heuristics, not automatic stop, scale, or spending rules." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-7", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers-7", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use cohort-level contribution economics to decide whether acquisition, retention, pricing, service, and funding assumptions support a viable unit. - Report retention, margin, service cost, CAC timing, payback, cash need, and uncertainty together; LTV/CAC alone is not a scale decision. - Assign a cohort owner and set the evidence that would change acquisition spend, pricing, product scope, or growth pace." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-7", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques-7", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- LTV is a forecast and can be dominated by retention, margin, churn, allocation, and horizon assumptions; CAC definitions can hide shared costs. - Positive unit contribution does not prove company profitability, liquidity, capacity, or scalable growth." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections-7", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections-7", "url": "#chapter-04-financial-analysis-and-valuation-connections-7", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: CAC data is an output of your Marketing & Sales analytics (Chapter 5) . Churn and revenue data come from Finance . Output: Cohort economics inform marketing analytics, go-to-market choices, and fundraising and capital planning, alongside market, product, cash, risk, and execution evidence. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-8-break-even-analysis", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "8. Break-Even Analysis", "headingId": "chapter-04-financial-analysis-and-valuation-8-break-even-analysis", "url": "#chapter-04-financial-analysis-and-valuation-8-break-even-analysis", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Break-Even Analysis Profitability Planning" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview-8", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview-8", "url": "#chapter-04-financial-analysis-and-valuation-overview-8", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Break-even analysis uses a cost-volume-profit model to estimate the sales volume at which modeled revenue equals modeled costs. Fixed and variable classifications, selling price, product mix, capacity, and cost behavior are assumptions over a stated relevant range and period; they are not permanent properties of an account. Use the result as a planning threshold, not a demand forecast or proof of product profitability. [BB-C04-S15]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply-8", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply-8", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define the model and relevant range: Classify costs as fixed or variable for the specified volume range and period; identify mixed, step, capacity, and product-mix effects separately. 2. Calculate Contribution Margin: Contribution Margin per Unit = Sales Price per Unit - Variable Cost per Unit . Under the stated assumptions, this is the amount each incremental unit contributes toward fixed costs and then operating income. 3. Calculate Break-Even Point: In Units: Break-Even Point (Units) = Total Fixed Costs / Contribution Margin per Unit . In Revenue: Break-Even Point (Revenue) = Total Fixed Costs / Contribution Margin Ratio , where Contribution Margin Ratio = Contribution Margin / Sales Revenue . For one product at one price, units multiplied by price produces the same modeled revenue threshold. [BB-C04-S15]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-8", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers-8", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use break-even to show the volume-price-mix-cost combinations required to cover modeled costs over a stated relevant range. - Stress-test mix, step costs, capacity, price response, and downside cash rather than treating the result as a demand forecast. - Translate the threshold into an owner, review date, and stop or redesign rule." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-8", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques-8", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Fixed and variable classifications, price, mix, and capacity are assumptions that can change outside the relevant range. - Break-even ignores or simplifies financing, uncertainty, competition, working capital, and the value of alternative uses of capital." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections-8", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections-8", "url": "#chapter-04-financial-analysis-and-valuation-connections-8", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires cost data from your Finance/Accounting team and pricing data from your Marketing/Sales (Chapter 5) teams. Output: Informs the sales targets for your Go-to-Market Strategy (Chapter 14) and helps set realistic goals in your OKRs (Chapter 8) . ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-9-monte-carlo-simulation", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "9. Monte Carlo Simulation", "headingId": "chapter-04-financial-analysis-and-valuation-9-monte-carlo-simulation", "url": "#chapter-04-financial-analysis-and-valuation-9-monte-carlo-simulation", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Monte Carlo Simulation Risk Analysis" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview-9", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview-9", "url": "#chapter-04-financial-analysis-and-valuation-overview-9", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A Monte Carlo simulation repeatedly samples specified input distributions to produce a model-based outcome distribution. A deterministic model reports one output for one set of inputs and can conceal uncertainty; simulation usefulness depends on the model, input evidence, dependence assumptions, and calibration. The active method record supports sampling, distributions, and iteration documentation. [BB-C04-S16]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply-9", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply-9", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Build a Base Model: Start with a standard financial model (e.g., a DCF). 2. Identify Decision-Relevant Uncertainty: Identify the assumptions whose uncertainty could materially change the decision (for example revenue growth, margins, investment cost, timing, or discount rate). 3. Define Joint Input Uncertainty: Use evidence and expert calibration to specify plausible ranges or distributions, dependencies, bounds, and scenarios. Do not default to independent normal inputs merely because they are convenient. 4. Run and Check the Simulation: Pre-specify and document an iteration count, random-seed policy, and convergence checks appropriate to the model. Increase iterations until the decision-relevant summaries are sufficiently stable; no universal count makes a weak model reliable. Each iteration samples from the specified input model. [BB-C04-S16] 5. Analyze and Challenge the Output: Report outcome ranges, downside/tail exposure, probability of crossing decision thresholds, and the inputs that drive the result. Call an interval a model-based simulation range unless its statistical calibration justifies a confidence claim." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-9", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers-9", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use simulation to expose how input uncertainty and dependence affect the distribution of a modeled outcome. - Document the model, input distributions, dependence assumptions, iteration count, calibration evidence, and what decision the distribution informs. - Compare the distribution with downside liquidity, risk appetite, staged options, and alternative models rather than treating a percentile as a probability of truth." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-9", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques-9", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Simulation can create false precision when the model, input distributions, dependencies, or calibration are weak. - An outcome distribution is model-based evidence, not an observed frequency distribution or a substitute for sensitivity and independent review." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections-9", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections-9", "url": "#chapter-04-financial-analysis-and-valuation-connections-9", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: A completed DCF Model (Framework 1) is the most common starting point. Output: Provides a model-based outcome distribution for Capital Allocation and Scenario Planning (Chapter 3) . It is one input to the decision, not an observed probability distribution or substitute for model validation. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-10-real-options-pricing", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "10. Real Options Pricing", "headingId": "chapter-04-financial-analysis-and-valuation-10-real-options-pricing", "url": "#chapter-04-financial-analysis-and-valuation-10-real-options-pricing", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Real Options Pricing Valuing Strategic Flexibility" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview-10", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview-10", "url": "#chapter-04-financial-analysis-and-valuation-overview-10", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Real-options analysis can represent the value of feasible, enforceable managerial choices such as waiting, staging, expanding, contracting, or abandoning that a static DCF can omit. Financial-option assumptions rarely map directly to projects; exclusivity, exercise control, learning, competition, path dependence, and estimation quality matter. [BB-C04-S10]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply-10", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply-10", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Identify the Real Option: Frame a strategic decision as an option (e.g., a pilot project is a \"call option\" on a full-scale launch). 2. Map to Option Variables: Stock Price (S): Present value of expected cash flows from the project. Exercise Price (K): Cost to exercise the option (e.g., cost of the full-scale launch). Time to Expiration (T): How long you can wait before making the decision. Volatility (σ): The uncertainty of the project's future cash flows. Risk-Free Rate (r): The time value of money. 3. Choose a Method: Use decision trees, staged scenarios, simulation, or a real-options model that matches the decision. Do not apply Black-Scholes mechanically when tradability, replication, continuous exercise, or volatility assumptions do not hold." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-contrarian-thinking-the-value-of-uncertainty", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: The Value of Uncertainty", "headingId": "chapter-04-financial-analysis-and-valuation-contrarian-thinking-the-value-of-uncertainty", "url": "#chapter-04-financial-analysis-and-valuation-contrarian-thinking-the-value-of-uncertainty", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Under some option structures, greater uncertainty can increase option value because the holder can choose whether to exercise. That result is not universal: the organization may face uncapped losses, correlated obligations, competition, financing constraints, expiring rights, or inability to abandon. Treat volatility effects as model- and rights-dependent, not as a general explanation of venture investing. [BB-C04-S10]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-10", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers-10", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use real-options logic when management has a credible, time-limited, enforceable choice to wait, stage, expand, contract, or abandon. - Identify the source of flexibility, the learning or trigger that changes the decision, the cost of waiting, and the competitor or obligation that can destroy the option. - Compare option value with a conventional DCF and record which assumptions make the flexibility exercisable in practice." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-10", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques-10", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Real-options analogies can overstate value when exclusivity, control, learning, timing, or financing is weak or when the underlying project cannot be traded. - Option outputs are sensitive to assumptions and can add complexity without improving the decision; use them only when flexibility is material." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections-10", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections-10", "url": "#chapter-04-financial-analysis-and-valuation-connections-10", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The present value of cash flows is an output of a DCF Model (Framework 1) . Volatility estimates can be derived from Monte Carlo Simulation (Framework 9) . Output: Provides a more complete valuation for highly uncertain strategic initiatives, informing your Strategy (Chapter 3) and Innovation (Part 3) efforts. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-11-comparable-companies-precedent-transactions-and-a-football-field", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "11. Comparable Companies, Precedent Transactions, and a Football Field", "headingId": "chapter-04-financial-analysis-and-valuation-11-comparable-companies-precedent-transactions-and-a-football-field", "url": "#chapter-04-financial-analysis-and-valuation-11-comparable-companies-precedent-transactions-and-a-football-field", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Comparable Companies, Precedent Transactions, and a Football Field Relative Valuation" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-overview-11", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-04-financial-analysis-and-valuation-overview-11", "url": "#chapter-04-financial-analysis-and-valuation-overview-11", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Relative valuation converts selected market prices or transaction prices into standardized multiples and applies them to consistently defined company metrics. It produces a range of market evidence, not an intrinsic-value proof or an automatic price recommendation. [BB-C04-S14]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-how-to-apply-11", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-04-financial-analysis-and-valuation-how-to-apply-11", "url": "#chapter-04-financial-analysis-and-valuation-how-to-apply-11", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Relative valuation converts selected market prices or transaction prices into standardized multiples, applies those multiples to a consistently defined company metric, and produces a range rather than an intrinsic-value proof. Peer selection, measurement period, accounting normalization, capital structure, growth, margin, risk, control, synergy, market regime, and date can dominate the output. [BB-C04-S14]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-comparable-company-workflow", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Comparable-company workflow", "headingId": "chapter-04-financial-analysis-and-valuation-comparable-company-workflow", "url": "#chapter-04-financial-analysis-and-valuation-comparable-company-workflow", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Set the valuation date and decision. Freeze market prices, exchange rates, filings, estimates, and share counts as of a stated date; never mix today's price with later financial information. 2. Define the subject metric. Reconcile revenue, EBITDA, EBIT, earnings, free cash flow, net debt, leases, pensions, minority interests, associates, options, and diluted shares consistently. 3. Select peers by economics, not label. Compare customer, product, geography, business model, maturity, growth, margin, capital intensity, accounting policy, cyclicality, and risk. Record inclusions, exclusions, and who approved them. 4. Calculate enterprise- and equity-value multiples. Match numerator and denominator: enterprise value with pre-financing operating metrics; equity value with equity earnings or book value. 5. Inspect dispersion and influence. Show every peer, not only the median. Test alternate sets, outliers, stale estimates, negative denominators, and the effect of one highly valued firm. 6. Apply a justified range. Explain why the subject belongs below, within, or above the peer distribution; do not hide the judgment in a mechanical premium or discount. 7. Bridge to equity value. Reconcile net debt and other claims, non-operating assets, dilution, and per-share value at the same date." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-precedent-transaction-workflow", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Precedent-transaction workflow", "headingId": "chapter-04-financial-analysis-and-valuation-precedent-transaction-workflow", "url": "#chapter-04-financial-analysis-and-valuation-precedent-transaction-workflow", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Precedent transactions add negotiated control prices but can be less comparable than public trading prices. For each deal, verify announcement and close dates, unaffected price, consideration, assumed debt and other claims, target financial period, accounting definitions, stake acquired, control, synergies, distress, auction dynamics, financing conditions, regulation, and subsequent information. Do not mix rumored, withdrawn, minority, distressed, and control transactions without explaining the consequence." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-constructed-range-exhibit", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Constructed range exhibit", "headingId": "chapter-04-financial-analysis-and-valuation-constructed-range-exhibit", "url": "#chapter-04-financial-analysis-and-valuation-constructed-range-exhibit", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following numbers are a teaching dataset, not current market evidence or a recommendation. Table 4.3. Constructed valuation-range exhibit. The values are illustrative and assumption-dependent; they are not current market evidence or a recommendation. | Method | Low equity value | High equity value | Key constructed assumption | |---|---:|---:|---| | LBO sponsor-implied maximum | $38m | $48m | Sponsor return and leverage constraints | | DCF | $42m | $58m | WACC and terminal-value sensitivity | | Trading comparables | $46m | $61m | Normalized peer-multiple range | | Precedent transactions | $51m | $70m | Control transactions after normalization | Constructed valuation football field Four horizontal ranges on a scale from 35 to 75 million dollars: LBO sponsor-implied maximum 38 to 48, DCF 42 to 58, trading comparables 46 to 61, and precedent transactions 51 to 70. $35m $45m $55m $65m $75m LBO sponsor-implied max DCF Trading comparables Precedent transactions Figure 4.6 — Constructed valuation football field. Each bar shows a method's assumption-dependent equity-value range on the same scale. The visual does not average the methods or select a price. Source note: author-constructed dataset and SVG; relative-valuation method informed by [BB-C04-S14]. Decision use: Reconcile why ranges differ before weighting or selecting a value. A wider precedent range may reflect control and deal conditions; an LBO range may act as a financing-feasibility lens, not a general valuation floor. If normalized source data and dates are unavailable, omit the method rather than fabricate precision." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-so-what-for-managers-11", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-11", "url": "#chapter-04-financial-analysis-and-valuation-so-what-for-managers-11", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use peer and transaction ranges to challenge assumptions and explain market evidence, not to replace a cash-flow model or judgment about the focal company. - Freeze the valuation date, metric definitions, peer/deal selection, normalization, and approval owner before calculating multiples. - Explain why the subject belongs below, within, or above the observed range and what evidence would change that conclusion." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-limits-and-critiques-11", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-11", "url": "#chapter-04-financial-analysis-and-valuation-limits-and-critiques-11", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Relative values inherit peer selection, market regime, accounting, control, synergy, date, and dispersion assumptions; a median is not a truth signal. - A football field is a communication exhibit, not a statistical combination rule, a negotiation floor, or a substitute for current primary data." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-connections-11", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-04-financial-analysis-and-valuation-connections-11", "url": "#chapter-04-financial-analysis-and-valuation-connections-11", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Uses accounting-quality, DCF, LBO, operating, strategy, and market evidence from the surrounding frameworks and Chapters 3, 6, and 15. Output: Provides a bounded market-evidence range for investment, fundraising, transaction, and capital-allocation decisions; finance owners must reconcile the result to the decision's rights and risks. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-why-this-matters-mental-models-valuation-wisdom", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Why This Matters: Mental Models & Valuation Wisdom", "headingId": "chapter-04-financial-analysis-and-valuation-why-this-matters-mental-models-valuation-wisdom", "url": "#chapter-04-financial-analysis-and-valuation-why-this-matters-mental-models-valuation-wisdom", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Financial valuation isn't just arithmetic—it's applied philosophy about value, time, and risk. Understanding why these models work (and when they break) transforms you from a spreadsheet operator into a strategic thinker who knows when to trust the numbers and when to question them." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-mental-model-1-the-time-value-of-money-why-dcf-works", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 1: The Time Value of Money (Why DCF Works)", "headingId": "chapter-04-financial-analysis-and-valuation-mental-model-1-the-time-value-of-money-why-dcf-works", "url": "#chapter-04-financial-analysis-and-valuation-mental-model-1-the-time-value-of-money-why-dcf-works", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The time value of money recognizes that cash received at different dates is not directly comparable. An operating DCF discounts forecast FCFF at a weighted cost of capital that represents the market-value-weighted costs of the financing components. Cash flow and rate must be defined consistently; the result remains an assumption-bound present-value estimate. [BB-C04-S13]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-mental-model-2-market-evidence-vs-intrinsic-value-why-comps-can-help", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 2: Market Evidence vs. Intrinsic Value (Why Comps Can Help)", "headingId": "chapter-04-financial-analysis-and-valuation-mental-model-2-market-evidence-vs-intrinsic-value-why-comps-can-help", "url": "#chapter-04-financial-analysis-and-valuation-mental-model-2-market-evidence-vs-intrinsic-value-why-comps-can-help", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Relative valuation derives a range from how selected comparable assets are priced after standardizing price into a multiple. Because no two firms are identical, test peer differences in risk, growth, and cash-flow potential and examine how peer selection or market repricing changes the result. [BB-C04-S14]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-mental-model-3-optionality-and-uncertainty-why-real-options-matter", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 3: Optionality and Uncertainty (Why Real Options Matter)", "headingId": "chapter-04-financial-analysis-and-valuation-mental-model-3-optionality-and-uncertainty-why-real-options-matter", "url": "#chapter-04-financial-analysis-and-valuation-mental-model-3-optionality-and-uncertainty-why-real-options-matter", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Static DCF scenarios can omit choices that management can credibly exercise. Real-options thinking asks whether the organization owns a staged, time-limited right to wait, learn, expand, contract, or abandon—and whether competition, obligations, financing, and execution make that right real. Uncertainty can increase some option values, but it can also increase losses and constrain exercise. [BB-C04-S10]" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-mental-model-4-strategic-value-vs-standalone-value", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 4: Strategic Value vs. Standalone Value", "headingId": "chapter-04-financial-analysis-and-valuation-mental-model-4-strategic-value-vs-standalone-value", "url": "#chapter-04-financial-analysis-and-valuation-mental-model-4-strategic-value-vs-standalone-value", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Standalone cash-flow value and buyer-specific value can differ because a buyer may have credible revenue, cost, capability, tax, or risk synergies. Model each synergy incrementally, including integration cost, timing, probability, cannibalization, and alternatives; do not infer motive or value from an acquisition price alone. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-failure-example-1-wework-when-financial-models-hid-operational-reality", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Failure Example 1: WeWork—When Financial Models Hid Operational Reality", "headingId": "chapter-04-financial-analysis-and-valuation-failure-example-1-wework-when-financial-models-hid-operational-reality", "url": "#chapter-04-financial-analysis-and-valuation-failure-example-1-wework-when-financial-models-hid-operational-reality", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "WeWork's 2019 registration statement disclosed large losses and long-term lease obligations alongside shorter-term membership revenue. The filing supports analysis of duration and operating-risk mismatch; it does not by itself establish a private valuation or one causal verdict. [BB-C04-S11] Lesson: Test whether growth improves cohort contribution and cash resilience after fixed obligations, service cost, financing, and downside demand scenarios. Scale is an outcome hypothesis, not a remedy." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-failure-example-2-2008-mortgage-crisis-when-comparables-failed", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Failure Example 2: 2008 Mortgage Crisis—When Comparables Failed", "headingId": "chapter-04-financial-analysis-and-valuation-failure-example-2-2008-mortgage-crisis-when-comparables-failed", "url": "#chapter-04-financial-analysis-and-valuation-failure-example-2-2008-mortgage-crisis-when-comparables-failed", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Financial Crisis Inquiry Commission documented widespread mortgage-asset valuation, leverage, and systemic-risk failures. Peer multiples can inherit a shared exposure or accounting problem, so comparable-company analysis needs asset-quality, liquidity, leverage, and stress evidence rather than a sector multiple alone. [BB-C04-S12] Lesson: Triangulate market evidence with cash-flow, balance-sheet, liquidity, and scenario analysis; no method provides a complete “sanity check” by itself." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-failure-example-3-constructed-growth-without-economics-scenario", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Failure Example 3: Constructed Growth-without-Economics Scenario", "headingId": "chapter-04-financial-analysis-and-valuation-failure-example-3-constructed-growth-without-economics-scenario", "url": "#chapter-04-financial-analysis-and-valuation-failure-example-3-constructed-growth-without-economics-scenario", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A subscription company doubles acquisition spending and reports rapid customer growth, but cohort retention falls, service cost rises, cash payback lengthens, and fixed obligations leave little downside liquidity. Lesson: Growth can create or destroy value. Test incremental contribution, retention, capacity, competitive response, cash needs, and the durability of any network or scale effect rather than treating customer growth as a valuation result. ---" }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-applied-exercise-audit-an-investment-recommendation", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Applied Exercise: Audit an Investment Recommendation", "headingId": "chapter-04-financial-analysis-and-valuation-applied-exercise-audit-an-investment-recommendation", "url": "#chapter-04-financial-analysis-and-valuation-applied-exercise-audit-an-investment-recommendation", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Using a constructed five-year project case, reconcile operating assumptions to unlevered free cash flow; estimate a consistent discount-rate range; calculate forecast and terminal-value present values; bridge enterprise to equity value; and build a two-way WACC/growth sensitivity. Compare the DCF with a break-even case and genuinely comparable market evidence. Then write a one-page recommendation that identifies the two assumptions most likely to reverse the decision, a downside liquidity case, the finance/accounting owners, and stop, stage, or scale rules." }, { "id": "chapter-04-financial-analysis-and-valuation::chapter-04-financial-analysis-and-valuation-selective-connections", "kind": "chapter", "itemSlug": "chapter-04-financial-analysis-and-valuation", "itemTitle": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "heading": "Selective Connections", "headingId": "chapter-04-financial-analysis-and-valuation-selective-connections", "url": "#chapter-04-financial-analysis-and-valuation-selective-connections", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use Chapter 1 for inflation, rates, currencies, and scenario inputs. - Use Chapter 3 to test competitive assumptions and strategic alternatives. - Use Chapter 6 for capacity, working capital, and operating-driver evidence. - Use Chapter 15 for transaction terms, dilution, preferences, and capital planning. - Use Chapter 18 for platform and cohort economics. - Use Chapter 22 for causal, sensitivity, and simulation interpretation. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Marketing and Customer Analytics", "headingId": "chapter-05-marketing-and-customer-analytics", "url": "#chapter-05-marketing-and-customer-analytics", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-executive-summary", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Executive Summary", "headingId": "chapter-05-marketing-and-customer-analytics-executive-summary", "url": "#chapter-05-marketing-and-customer-analytics-executive-summary", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter provides an operator's toolkit for modern marketing and customer analytics. It moves beyond traditional marketing theory to focus on decision evidence: customer understanding, segmentation, positioning, pricing, channels, brand, experiments, marketing-mix models, attribution, cohort economics, and cash-flow consequences. No one measurement method identifies “what worked” in every setting; managers must reconcile causal, descriptive, model-based, and financial evidence before reallocating material spend." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-authorial-and-constructed-material-boundary", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Authorial and Constructed-Material Boundary", "headingId": "chapter-05-marketing-and-customer-analytics-authorial-and-constructed-material-boundary", "url": "#chapter-05-marketing-and-customer-analytics-authorial-and-constructed-material-boundary", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The chapter's decision spine, diagrams, matrices, worked examples, and exercise are author-created teaching syntheses unless a source is named adjacent to the claim. Anonymous values, coordinates, customer stories, and operating scenarios are constructed illustrations rather than company facts, benchmarks, or recommendations. Source markers support only the claim scope described in the source map; managers must validate the focal market, customer data, privacy basis, economics, and experiment design before acting." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-the-marketing-decision-spine", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "The Marketing Decision Spine", "headingId": "chapter-05-marketing-and-customer-analytics-the-marketing-decision-spine", "url": "#chapter-05-marketing-and-customer-analytics-the-marketing-decision-spine", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the market, customer decision, and business objective; gather customer, competitor, channel, and economic evidence; segment by differences that could change the offer or route to market; select target customers; and state a differentiated value proposition and positioning. [BB-C05-S07] Author synthesis: Choose product, price, channel, and communication hypotheses; define descriptive and causal measures; run bounded tests; and update the plan when evidence changes. Customer-data boundary: Before tracking, targeting, personalizing, surveying, or experimenting, establish a lawful and ethical purpose, minimize data, assess representativeness and proxy effects, protect sensitive attributes, provide appropriate notice and choice, and define retention, access, security, and deletion. Use Chapter 2 and Chapter 20 for governance; qualified owners determine applicable law." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-1-customer-journey-mapping", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "1. Customer Journey Mapping", "headingId": "chapter-05-marketing-and-customer-analytics-1-customer-journey-mapping", "url": "#chapter-05-marketing-and-customer-analytics-1-customer-journey-mapping", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Customer Journey Mapping Experience Design & Diagnosis" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-overview", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-05-marketing-and-customer-analytics-overview", "url": "#chapter-05-marketing-and-customer-analytics-overview", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A customer journey map is a purpose-bound representation of an experience for a specified segment, context, and time. Customer-journey research emphasizes experience over time and multiple touchpoints across channels; this chapter adds observed actions, evidence, friction, ownership, and measures to generate improvement hypotheses. The map itself does not establish emotion, causality, or business impact. [BB-C05-S11]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-how-to-apply", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-05-marketing-and-customer-analytics-how-to-apply", "url": "#chapter-05-marketing-and-customer-analytics-how-to-apply", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define Scope and Persona: Choose one specific customer persona and a specific journey to map (e.g., \"the first 90 days for a new mid-market customer\"). Don't try to map everyone at once. 2. Identify Journey Stages: Outline the major phases from the customer's perspective (e.g., Awareness, Consideration, Purchase, Onboarding, Engagement, Advocacy). 3. Map the Details for Each Stage: Customer Actions: What is the customer doing ? (e.g., \"Googling solutions,\" \"requesting a demo\"). Touchpoints: Where are they interacting with you? (e.g., Website, Ads, Sales Rep, Support Ticket). Emotions: How are they feeling ? (e.g., Confused, Anxious, Hopeful, Relieved). Use qualitative data from interviews. Pain Points: Where is the friction? What takes too long? What is confusing? 4. Identify Opportunities: For each pain point, brainstorm a corresponding improvement opportunity. This becomes your action plan. Prioritize opportunities based on their impact on the customer and the business versus the effort required. Figure 5.1. Evidence-to-improvement customer-journey loop. This original synthesis shows stages, stage-level evidence, friction, ownership, and measurement rather than treating a journey as a one-way funnel. Text equivalent: For a defined segment and journey, collect behavioral, interview, and service evidence at awareness, consideration, purchase, onboarding, engagement, and advocacy. Translate friction, needs, and accessibility issues into an owned hypothesis with a metric and guardrail; test the change and feed the results back into the map. Source note: Author-created teaching diagram informed by Lemon and Verhoef's customer-journey review; no arrow represents a proven causal effect, and the example stages are illustrative rather than a reproduced published model. [BB-C05-S11]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-05-marketing-and-customer-analytics-so-what-for-managers", "url": "#chapter-05-marketing-and-customer-analytics-so-what-for-managers", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the map to decide which customer problem, stage, owner, and measure deserves attention before selecting a campaign or product change. - Convert observed friction into a bounded hypothesis with a customer benefit, business outcome, guardrail, and evidence plan. - Revisit the map after research, service changes, or experiments; a static workshop artifact should not become the operating plan by default." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-05-marketing-and-customer-analytics-limits-and-critiques", "url": "#chapter-05-marketing-and-customer-analytics-limits-and-critiques", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A map describes an experience under a chosen segment, context, and time window; it does not prove emotion, causality, incremental demand, or financial impact. - Author synthesis: Stated emotions and recalled journeys can reflect recall, selection, survey-mode, and researcher-coding bias; triangulate them with behavior and service evidence. - Stage names and touchpoints vary by business, accessibility need, channel, and customer; do not treat the illustrative sequence as a universal funnel." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-connections", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-05-marketing-and-customer-analytics-connections", "url": "#chapter-05-marketing-and-customer-analytics-connections", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inputs include qualitative research from Jobs-to-be-Done (Framework 2) and quantitative behavior, service, and drop-off data. - Outputs can generate hypotheses for A/B Testing (Framework 8) , service improvement, product discovery, and the Product Roadmap . - Use the map alongside Cohort Analysis (Framework 10) and CLV/CAC Analysis (Framework 4) when a proposed experience change has retention or economic implications. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-2-jobs-to-be-done-jtbd", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "2. Jobs-to-be-Done (JTBD)", "headingId": "chapter-05-marketing-and-customer-analytics-2-jobs-to-be-done-jtbd", "url": "#chapter-05-marketing-and-customer-analytics-2-jobs-to-be-done-jtbd", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Jobs-to-be-Done (JTBD) Understanding Customer Motivation" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-overview-2", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-05-marketing-and-customer-analytics-overview-2", "url": "#chapter-05-marketing-and-customer-analytics-overview-2", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Jobs-to-be-Done is a family of practitioner approaches associated with Christensen and collaborators, Moesta, and related customer-needs research. Across variants, it asks what progress a customer seeks in a particular circumstance. Treat interview accounts as hypotheses to triangulate with observed behavior, alternative explanations, market evidence, and experiments—not as direct access to a customer's true motive. [BB-C05-S12] [BB-C05-S13]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-05-marketing-and-customer-analytics-how-to-apply-2", "url": "#chapter-05-marketing-and-customer-analytics-how-to-apply-2", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Conduct a switch or struggle interview: In the Moesta–Spiek practitioner variant, ask for the chronology of a recent purchase, switch, or non-consumption decision and probe the circumstances, alternatives, events, concerns, and desired progress. Do not rely on stated feature preferences alone. [BB-C05-S13] 2. State a job hypothesis: Summarize what progress may have been sought and in which circumstance, then test competing explanations. For this chapter, [progress sought] + [circumstance] + [constraints or success evidence] is an author-created notation, not a standardized JTBD syntax. 3. Map one practitioner variant—the Forces of Progress: Moesta and Spiek describe four forces in a switching decision: [BB-C05-S13] Push: The pain of the current situation driving the customer to act. Pull: The appeal of the new solution. Anxiety: The fears and uncertainties about the new solution. Habit: The inertia of their current solution. The model proposes that change becomes more likely when push and pull outweigh anxiety and habit. Use it as an interview-coding hypothesis, not a quantitative law or proof that marketing caused the switch." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-2", "url": "#chapter-05-marketing-and-customer-analytics-so-what-for-managers-2", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use a recent choice, switch, or non-consumption story to define a customer problem and a testable progress hypothesis rather than collecting a feature wish list. - Compare the proposed job with alternatives, constraints, accessibility needs, behavioral evidence, and commercial outcomes before changing product or messaging. - Route the hypothesis to a bounded discovery or market test; a compelling interview account is not a demand forecast or a product requirement." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-2", "url": "#chapter-05-marketing-and-customer-analytics-limits-and-critiques-2", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- JTBD is a family of practitioner variants, not one universally standardized method; the Forces of Progress and the chapter's bracketed job notation are bounded teaching choices. - The milkshake story is a commonly reported teaching illustration, not universal evidence; verify jobs, alternatives, constraints, and desired outcomes in the market being studied. - Retrospective interviews are vulnerable to recall, selection, social-desirability, and researcher-coding bias; triangulate with behavior, market evidence, and experiments." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-connections-2", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-05-marketing-and-customer-analytics-connections-2", "url": "#chapter-05-marketing-and-customer-analytics-connections-2", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inputs include customer interviews, observed behavior, market and competitor evidence, accessibility research, and experimental results. - Outputs can inform Go-to-Market Strategy (Chapter 14) , product discovery, and messaging tests while leaving feature and investment decisions open. - Combine job hypotheses with Customer Journey Mapping (Framework 1) and A/B Testing (Framework 8) to connect context, experience, and measurable behavior. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-3-rfm-segmentation", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "3. RFM Segmentation", "headingId": "chapter-05-marketing-and-customer-analytics-3-rfm-segmentation", "url": "#chapter-05-marketing-and-customer-analytics-3-rfm-segmentation", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "RFM (Recency, Frequency, Monetary) Segmentation Customer Segmentation" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-overview-3", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-05-marketing-and-customer-analytics-overview-3", "url": "#chapter-05-marketing-and-customer-analytics-overview-3", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "RFM segmentation is a descriptive method that groups customers by recency, frequency, and monetary-value measures derived from transaction history. Fader, Hardie, and Lee formally connect RFM inputs to CLV through a model, which also shows why a simple score or segment is not itself customer lifetime value. The resulting groups do not by themselves establish loyalty, churn risk, or response to an intervention. [BB-C05-S14]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-05-marketing-and-customer-analytics-how-to-apply-3", "url": "#chapter-05-marketing-and-customer-analytics-how-to-apply-3", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Score Each Customer: For every customer, assign a score from 1 to 5 for each of the three dimensions based on their purchase history (e.g., top 20% of recent buyers get a Recency score of 5). 2. Combine Scores: Concatenate the scores to create an RFM segment (e.g., a customer with a score of 5 for Recency, 5 for Frequency, and 5 for Monetary is in the \"555\" segment). 3. Map to Hypothesis Segments: Labels such as “recent/frequent/high-spend” describe observed transactions, not customer worth, loyalty, or treatment response. For each segment, state the proposed action, customer benefit, consent/fairness limits, expected incremental effect, cost, holdout, and stop rule." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-3", "url": "#chapter-05-marketing-and-customer-analytics-so-what-for-managers-3", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use RFM cells to describe recent transaction patterns and prioritize questions, service reviews, or consent-respecting audience hypotheses. - Define the proposed customer benefit, incremental outcome, cost, fairness check, holdout, and stop rule before acting on a segment. - Reconcile segment patterns with contribution margin, service burden, retention, and customer experience rather than treating high spend as customer worth." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-3", "url": "#chapter-05-marketing-and-customer-analytics-limits-and-critiques-3", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Score cutoffs, observation windows, missing purchases, returns, and monetary definitions are design choices; the illustrative 1–5 scoring is not a benchmark. [BB-C05-S14] - RFM is descriptive and can reflect acquisition mix, seasonality, pricing, channel, or measurement coverage; it does not establish loyalty, churn risk, or treatment response. - Transaction history can omit non-purchase value, shared accounts, accessibility needs, and privacy or fairness risks; minimize data and review proxy effects before targeting." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-connections-3", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-05-marketing-and-customer-analytics-connections-3", "url": "#chapter-05-marketing-and-customer-analytics-connections-3", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inputs are defined transaction, margin, service-cost, consent, and customer-identity data from Finance/Sales and analytics systems. - Outputs can define candidate audiences for A/B Testing (Framework 8) , service changes, or research and can inform Customer Journey Mapping (Framework 1) . - Use CLV/CAC Analysis (Framework 4) and Cohort Analysis (Framework 10) to test whether a descriptive segment difference matters economically or longitudinally. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-4-clv-cac-analysis", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "4. CLV/CAC Analysis", "headingId": "chapter-05-marketing-and-customer-analytics-4-clv-cac-analysis", "url": "#chapter-05-marketing-and-customer-analytics-4-clv-cac-analysis", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "CLV/CAC Analysis Unit Economics" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-overview-4", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-05-marketing-and-customer-analytics-overview-4", "url": "#chapter-05-marketing-and-customer-analytics-overview-4", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Customer lifetime value (CLV) is the present value of expected customer net cash flows, and Fader cautions against treating a homogeneous-customer point estimate as precise. This chapter compares a cohort CLV model with allocated acquisition cost as one input to a marketing investment decision; that comparison does not prove profitability. Retention, gross margin, service cost, discounting, attribution, cash timing, fixed costs, and uncertainty still matter. [BB-C05-S04]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-05-marketing-and-customer-analytics-how-to-apply-4", "url": "#chapter-05-marketing-and-customer-analytics-how-to-apply-4", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Calculate CAC by Cohort and Channel: Allocate sales, marketing, creative, promotion, referral, and relevant overhead consistently; state the attribution method and timing. 2. Estimate CLV: Model survival/retention, contribution margin, service cost, expansion/contraction, discounting, and uncertainty. The shortcut (period revenue × gross margin) / churn assumes a stable constant hazard and should be labeled accordingly. 3. Test Sensitivity and Cash: Compare cohorts and plausible ranges, calculate cash payback, reconcile with fixed costs and capacity, and identify which assumption reverses the recommendation." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-4", "url": "#chapter-05-marketing-and-customer-analytics-so-what-for-managers-4", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use CLV/CAC to compare customer-acquisition and retention choices under explicit cohort, margin, service-cost, discounting, and cash assumptions. - Show a range, payback timing, capacity constraint, and the assumption that would reverse the recommendation before reallocating material spend. - Treat the comparison as one decision input alongside customer, market, risk, operating, and financing evidence; it is not an approval threshold by itself." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-4", "url": "#chapter-05-marketing-and-customer-analytics-limits-and-critiques-4", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The shortcut (period revenue × gross margin) / churn assumes a stable constant hazard and omits important timing, expansion, contraction, service, and uncertainty effects. - CAC allocation depends on attribution, cost boundaries, timing, discounts, returns, and shared overhead; changing the convention can change the conclusion. - Cohort averages hide heterogeneity and can be biased by censoring, selection, reactivation, pricing, and measurement changes; compare plausible alternatives and sensitivity ranges." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-connections-4", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-05-marketing-and-customer-analytics-connections-4", "url": "#chapter-05-marketing-and-customer-analytics-connections-4", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inputs include Attribution Models (Framework 5) , Cohort Analysis (Framework 10) , RFM Segmentation (Framework 3) , finance records, and customer-service costs. - Outputs inform go-to-market choices and fundraising and capital planning alongside customer, market, cash, risk, and execution evidence. - Use Pricing Strategy & Models (Framework 6) and Customer Journey Mapping (Framework 1) to test how price, experience, retention, and service burden could change the economics. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-5-marketing-attribution-models", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "5. Marketing Attribution Models", "headingId": "chapter-05-marketing-and-customer-analytics-5-marketing-attribution-models", "url": "#chapter-05-marketing-and-customer-analytics-5-marketing-attribution-models", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Marketing Attribution Models ROI Measurement" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-overview-5", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-05-marketing-and-customer-analytics-overview-5", "url": "#chapter-05-marketing-and-customer-analytics-overview-5", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Marketing attribution allocates conversion credit under a stated rule or model. Credit is not the same as incremental effect: observed touchpoints reflect targeting, customer intent, missing exposure data, platform rules, and selection. Li and Kannan demonstrate one multichannel model with a field validation in one firm; Dalessandro and colleagues show why approximations should be interpreted as variable-importance measures when causal assumptions fail. Use attribution for description and reconciliation, and use experiments or justified causal designs for incremental budget claims. [BB-C05-S15] [BB-C05-S16]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-05-marketing-and-customer-analytics-how-to-apply-5", "url": "#chapter-05-marketing-and-customer-analytics-how-to-apply-5", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Understand the Models: Last-Click: Gives all credit to the final recorded touchpoint. It is simple but sensitive to measurement coverage and customer intent. First-Click: Gives all credit to the first recorded touchpoint. It describes the first touch associated with the path; it does not establish what caused awareness or conversion. Linear: Divides credit equally among recorded touchpoints; equality is a convention, not evidence. Position-Based: Assigns chosen weights to first, last, and middle touches; the weights encode assumptions. Model-Based: Estimates patterns in observed paths. Prediction or probabilistic credit still does not establish what would have happened without exposure. 2. Triangulate: Compare credit rules, randomized holdouts where feasible, justified quasi-experiments, and aggregate marketing-mix models. Reconcile each with total spend, revenue, margin, coverage, and uncertainty; move budget only when the evidence is decision-relevant." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-5", "url": "#chapter-05-marketing-and-customer-analytics-so-what-for-managers-5", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use attribution to describe paths, reconcile recorded touchpoints, and generate sequencing or channel hypotheses under a declared rule. - Define the estimand, population, exposure window, outcome, cost boundary, data coverage, and uncertainty before comparing channels or changing spend. - Escalate material incremental-effect decisions to randomized holdouts or a justified quasi-experimental design where operations and ethics permit." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-5", "url": "#chapter-05-marketing-and-customer-analytics-limits-and-critiques-5", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Rule-based and model-based credit can reflect targeting, intent, missing exposure, identity resolution, platform definitions, and selection; it is not automatically causal. - The cited multichannel evidence is bounded to its data, model, and field setting; prediction or field validation does not make the method universal. - Privacy choices, consent, offline exposure, cross-device gaps, interference, carryover, and spillover can change both the observed path and the decision." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-connections-5", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-05-marketing-and-customer-analytics-connections-5", "url": "#chapter-05-marketing-and-customer-analytics-connections-5", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inputs include a defined Customer Journey Map (Framework 1) , exposure and conversion data, consent controls, channel costs, and a stated measurement contract. - Outputs can inform CLV/CAC Analysis (Framework 4) and journey operations, but channel CAC remains dependent on allocation assumptions. - Use the broader triangulation section below to reconcile attribution with experiments, marketing-mix models, and finance rather than averaging incompatible estimates. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-6-pricing-strategy-models", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "6. Pricing Strategy & Models", "headingId": "chapter-05-marketing-and-customer-analytics-6-pricing-strategy-models", "url": "#chapter-05-marketing-and-customer-analytics-6-pricing-strategy-models", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Pricing Strategy & Models Value Capture" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-overview-6", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-05-marketing-and-customer-analytics-overview-6", "url": "#chapter-05-marketing-and-customer-analytics-overview-6", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Pricing connects customer value, willingness to pay, demand, competitive alternatives, costs, channels, and strategic positioning. Test the decision for the target segment and context rather than treating one pricing method as universally best. [BB-C05-S08]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-05-marketing-and-customer-analytics-how-to-apply-6", "url": "#chapter-05-marketing-and-customer-analytics-how-to-apply-6", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define the price decision: Specify the target segment, use case, value metric, competitive alternatives, objective, time horizon, and constraints before selecting a pricing model. 2. Estimate willingness to pay and economics: Combine customer and market evidence with cost, capacity, margin, tax, contract, fairness, and cash analysis; state uncertainty and alternative explanations. 3. Test and govern the offer: Use bounded price research or experiments where lawful and appropriate, monitor comprehension, access, churn, margin, bill shock, and competitor response, and stage changes with a stop rule. Pricing-posture matrix: This matrix positions your price based on the perceived value you deliver versus competitors. Premium posture: Higher perceived differentiation and lower direct comparability may support a higher price, subject to willingness-to-pay evidence. Value posture: In a more comparable market, offer a defensible value-price relationship for the target segment. Economy posture: A lower price requires a cost and operating model that can sustain it. Penetration hypothesis: A temporary lower price may build trial or network participation, but future price response, customer fairness, cash, competition, and regulation must be tested. Figure 5.2. Constructed pricing-posture map. The anonymous points illustrate how teams might discuss perceived differentiation and competitive intensity; the coordinates are not market evidence or recommended prices. Text equivalent: The horizontal axis runs from lower to higher competitive intensity and the vertical axis from lower to higher perceived differentiation. Four anonymous, illustrative offers occupy the premium, value, economy, and penetration discussion regions; actual placement requires customer and market evidence. Source note: Original teaching matrix informed by open marketing-principles material; positions and labels are illustrative rather than empirical. [BB-C05-S08] Modern pricing models for digital products: 1. Cost-Plus Pricing: Adds a margin to defined cost. It can support cost recovery or regulated/contract contexts but does not by itself measure customer value or demand. 2. Competitor-Based Pricing: Setting your price based on what competitors charge. A common starting point, but it anchors you to their value proposition, not yours. 3. Value-Based Pricing: Uses evidence about differentiated customer value and willingness to pay. Validate the counterfactual, attribution, segment, implementation cost, risk, and buyer budget rather than applying a fixed share-of-value rule. 4. Usage-Based Pricing: Customers pay based on a measured unit of consumption. It aligns price with customer value only when the unit is a credible value metric; it can also create unpredictability, bill shock, gaming, weak cost recovery, or procurement friction. Test the metric, meter accuracy, fairness, caps, customer control, margin, tax, and contract implications. 5. Tiered Pricing: Multiple packages can differentiate features, service, limits, or outcomes for distinct use cases. Tiering is a hypothesis, not proof of segmentation or an automatic upsell path; test comprehension, willingness to pay, fairness, migration, cannibalization, support burden, and unit economics." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-6", "url": "#chapter-05-marketing-and-customer-analytics-so-what-for-managers-6", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Choose a pricing method that fits the segment, value metric, competitive context, operating model, and decision objective rather than copying a market convention. - Make the customer trade-off legible and protect agency with clear terms, controls, access, fairness checks, and escalation for material harm or bill shock. - Connect price changes to marginal contribution, retention, capacity, cash timing, and customer outcomes; monitor the realized result after launch." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-6", "url": "#chapter-05-marketing-and-customer-analytics-limits-and-critiques-6", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Perceived value, willingness to pay, elasticity, and competitive intensity are context-dependent and must be measured; an illustrative matrix does not establish market position. - Cost-plus, competitor-based, value-based, usage-based, and tiered pricing each encode assumptions and can fail through weak value metrics, gaming, unpredictability, cannibalization, margin leakage, or procurement friction. - Pricing experiments can create fairness, disclosure, legal, privacy, and trust risks; do not infer long-run demand or customer welfare from a short-term conversion lift alone." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-connections-6", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-05-marketing-and-customer-analytics-connections-6", "url": "#chapter-05-marketing-and-customer-analytics-connections-6", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inputs include Jobs-to-be-Done (Framework 2) , Brand Architecture (Framework 7) , competitive analysis, customer research, cost and capacity data, and finance assumptions. - Outputs feed CLV/CAC Analysis (Framework 4) , channel and go-to-market choices, and the customer-data and experimentation governance boundary. - Use A/B Testing (Framework 8) or a justified pricing-research design only when the treatment, eligible population, outcome, guardrails, and legal basis are explicit. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-7-brand-architecture", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "7. Brand Architecture", "headingId": "chapter-05-marketing-and-customer-analytics-7-brand-architecture", "url": "#chapter-05-marketing-and-customer-analytics-7-brand-architecture", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Brand Architecture Portfolio & Brand Strategy" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-overview-7", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-05-marketing-and-customer-analytics-overview-7", "url": "#chapter-05-marketing-and-customer-analytics-overview-7", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Brand architecture organizes a brand portfolio by specifying brand roles and relationships among brands, including sub-brand and endorsed-brand alternatives. It can clarify the intended structure, but the architecture alone does not guarantee a business outcome. [BB-C05-S09]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-05-marketing-and-customer-analytics-how-to-apply-7", "url": "#chapter-05-marketing-and-customer-analytics-how-to-apply-7", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Choose a Model: Branded house: A master brand covers multiple offers. Potential benefits include recognition and shared investment; risks include spillover from a failure. House of brands: Distinct brands serve different positions. Potential benefits include separation and targeting; costs include portfolio complexity and duplicated investment. Hybrid: Endorsement and independence vary by offer. The design requires explicit naming, governance, migration, and risk rules. 2. Map Your Portfolio: Visually map your current products and brands to see which architecture you are currently using (or if you have an inconsistent mix). 3. Align with Strategy: Compare customer recognition, position, channel, portfolio relationships, reputation spillover, operating cost, acquisition integration, and governance. Select an architecture as a hypothesis and measure its effects rather than labeling one model “best.”" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-7", "url": "#chapter-05-marketing-and-customer-analytics-so-what-for-managers-7", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Make brand roles, naming, endorsement, migration, investment, and failure-containment decisions explicit across the portfolio. - Treat architecture as a design hypothesis and measure recognition, consideration, choice, willingness to pay, retention, spillover, cost, and governance outcomes. - Assign an owner for portfolio coherence and review architecture changes alongside strategy, product, channel, and acquisition decisions." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-7", "url": "#chapter-05-marketing-and-customer-analytics-limits-and-critiques-7", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Branded-house, house-of-brands, and hybrid models involve trade-offs; no architecture is universally best and the architecture choice is not evidence of a market outcome. - Architecture can clarify relationships without causing efficiency, customer-based brand equity, or competitive advantage; those effects require focal-firm evidence and alternative explanations. - Author synthesis: Brand knowledge and survey measures can be noisy, culturally specific, and disconnected from behavior or cash flow; protect respondents and test the full evidence chain." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-connections-7", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-05-marketing-and-customer-analytics-connections-7", "url": "#chapter-05-marketing-and-customer-analytics-connections-7", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inputs include Corporate Strategy (Chapter 3) , target Customer Segments (Framework 3) , acquisition or portfolio plans, customer research, channel evidence, and governance constraints. - Outputs inform naming, endorsement, migration, allocation, and risk decisions and connect to the brand-equity evidence chain below. - Use Pricing Strategy & Models (Framework 6) and Customer Journey Mapping (Framework 1) to test whether architecture changes affect perceived value and experience rather than assuming they do. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-8-a-b-testing", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "8. A/B Testing", "headingId": "chapter-05-marketing-and-customer-analytics-8-a-b-testing", "url": "#chapter-05-marketing-and-customer-analytics-8-a-b-testing", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A/B Testing Experimentation & Optimization" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-overview-8", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-05-marketing-and-customer-analytics-overview-8", "url": "#chapter-05-marketing-and-customer-analytics-overview-8", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "An online controlled experiment randomly assigns eligible units to variants to estimate a treatment difference under the experiment's design and trustworthiness assumptions. Define the tested contrast explicitly. [BB-C05-S10]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-05-marketing-and-customer-analytics-how-to-apply-8", "url": "#chapter-05-marketing-and-customer-analytics-how-to-apply-8", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Formulate the Decision and Hypothesis: Define the eligible population, unit of randomization, treatment, primary outcome, rationale, and action the result can change. 2. Predefine the Design: Specify the minimum detectable effect, sample and duration, allocation, guardrails, segment analyses, multiplicity approach, stopping rule, and data-quality checks. 3. Run the Test: Randomize with an approved experimentation system; monitor sample-ratio mismatch, instrumentation, interference, novelty, operational incidents, and privacy/safety guardrails without opportunistic peeking. 4. Analyze Results: Report the estimated treatment effect and uncertainty, experiment-validity checks, practical relevance, and guardrail results; do not reduce the decision to a binary “winner.” [BB-C05-S10] 5. Decide and Stage: Ship, reject, redesign, or declare the result inconclusive using the pre-specified rule. Roll out gradually when consequences or uncertainty warrant it. 6. Monitor Durability: Verify that the effect and guardrails persist after rollout; record learning and update the next hypothesis. Figure 5.3. Marketing experiment decision loop. The flow separates validity and trustworthiness checks, decision relevance, guardrails, and staged rollout rather than equating statistical significance with shipping. [BB-C05-S10] Text equivalent: Define the decision and pre-specify the experiment, randomize and run, verify data and design, assess whether the effect is both detectable and practically material, check guardrails, then stage and monitor rollout. Invalid, unsafe, weak, or inconclusive evidence routes to repair, rejection, or redesign rather than an automatic winner. Source note: Original decision loop informed by the Cambridge guide's treatment of trustworthy analysis, guardrail metrics, decision pitfalls, and ramping exposure. [BB-C05-S10]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-8", "url": "#chapter-05-marketing-and-customer-analytics-so-what-for-managers-8", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the decision, eligible population, treatment contrast, primary outcome, minimum detectable effect, guardrails, stopping rule, and action before exposure begins. - Check randomization, delivery, sample-ratio mismatch, instrumentation, interference, novelty, multiplicity, practical materiality, and customer-safety constraints. - Stage a supported change and monitor durability; ship, reject, redesign, or declare inconclusive according to the pre-specified decision rule. [BB-C05-S10]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-8", "url": "#chapter-05-marketing-and-customer-analytics-limits-and-critiques-8", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- An experiment estimates an effect for its tested alternatives, population, implementation, and time window; it does not prove that the tested set contains the best feasible design. - Statistical detectability is not business materiality, and a null or wide result is not proof of zero effect; power, attrition, interference, and measurement quality shape the conclusion. - Qualitative research, Jobs-to-be-Done (Framework 2) , Customer Journey Mapping (Framework 1) , prototypes, and broader redesigns can generate alternatives, but none guarantees a “global maximum.”" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-connections-8", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-05-marketing-and-customer-analytics-connections-8", "url": "#chapter-05-marketing-and-customer-analytics-connections-8", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inputs include opportunities from a Customer Journey Map (Framework 1) , behavioral and qualitative evidence, operational constraints, risk review, and the customer-data boundary. - Outputs can inform a staged change; any effect on conversion, retention, or the CLV/CAC ratio (Framework 4) requires follow-up measurement and cost attribution. - Reconcile treatment effects with marketing attribution, marketing-mix models, and finance in the measurement-triangulation protocol below. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-9-nps-driver-analysis", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "9. NPS Driver Analysis", "headingId": "chapter-05-marketing-and-customer-analytics-9-nps-driver-analysis", "url": "#chapter-05-marketing-and-customer-analytics-9-nps-driver-analysis", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Net Promoter Score (NPS) Driver Analysis Loyalty Measurement & Diagnosis" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-overview-9", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-05-marketing-and-customer-analytics-overview-9", "url": "#chapter-05-marketing-and-customer-analytics-overview-9", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Net Promoter Score (NPS) is a widely used metric to measure recommendation intent. It is based on a single 0–10 question; respondents are grouped into Promoters (9–10), Passives (7–8), and Detractors (0–6), and the score is % Promoters - % Detractors . [BB-C05-S02] A driver analysis can then examine potential explanations for loyalty or dissatisfaction without treating the score as a causal measure." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-05-marketing-and-customer-analytics-how-to-apply-9", "url": "#chapter-05-marketing-and-customer-analytics-how-to-apply-9", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Ask a Bounded Follow-Up: When appropriate, invite respondents to explain the score without forcing sensitive disclosure or assuming the response is causal. 2. Tag Verbatim Feedback: Categorize the open-ended responses into themes (e.g., \"Ease of Use,\" \"Pricing,\" \"Customer Support,\" \"Feature X\"). Use text analytics tools for large volumes. 3. Associate Themes with Scores: For each theme, summarize score, response, segment, and uncertainty patterns. Theme-score relationships may reflect selection and do not establish a driver. Driver of Delight: A theme mentioned frequently by Promoters (e.g., \"Customer Support\" has an average NPS of 80). Driver of Dissatisfaction: A theme mentioned frequently by Detractors (e.g., \"Pricing\" has an average NPS of -50). 4. Prioritize Learning: Combine frequency, severity, affected customers, accessibility, behavioral evidence, feasibility, and risk; test whether a proposed improvement changes the intended outcome." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-9", "url": "#chapter-05-marketing-and-customer-analytics-so-what-for-managers-9", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use NPS as one standardized sentiment signal, then inspect response coverage, verbatims, behavioral retention, repurchase, complaints, accessibility, and economics. - Treat themes as hypotheses about experience or dissatisfaction; prioritize them using frequency, severity, affected customers, feasibility, risk, and a testable outcome. - Pair any proposed change with an owner, guardrail, and follow-up measure rather than managing to the score alone." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-9", "url": "#chapter-05-marketing-and-customer-analytics-limits-and-critiques-9", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- NPS is a recommendation-intent score and is sensitive to response/nonresponse, survey mode, customer mix, culture, timing, and instrument design. [BB-C05-S02] [BB-C05-S03] - Keiningham and colleagues did not replicate the claim that NPS is the single most reliable indicator of firm revenue growth; that study does not establish individual future behavior. [BB-C05-S03] - Theme-score associations can reflect selection, common causes, coding choices, and reverse causality; they do not identify a driver without stronger design and triangulation." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-connections-9", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-05-marketing-and-customer-analytics-connections-9", "url": "#chapter-05-marketing-and-customer-analytics-connections-9", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inputs include customer surveys, verbatim feedback, response/nonresponse diagnostics, behavioral retention, complaints, and service evidence. - Outputs generate hypotheses for Customer Journey Mapping (Framework 1) , A/B Testing (Framework 8) , product improvement, and service recovery. - Reconcile sentiment with Cohort Analysis (Framework 10) and CLV/CAC Analysis (Framework 4) without treating either relationship as automatically causal. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-10-cohort-analysis", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "10. Cohort Analysis", "headingId": "chapter-05-marketing-and-customer-analytics-10-cohort-analysis", "url": "#chapter-05-marketing-and-customer-analytics-10-cohort-analysis", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Cohort Analysis Retention Analysis" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-overview-10", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-05-marketing-and-customer-analytics-overview-10", "url": "#chapter-05-marketing-and-customer-analytics-overview-10", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Cohort analysis groups customers by a defined starting event or characteristic and follows a consistently defined outcome over time. A retention table aligns cohorts by time since the starting event so unlike-aged groups are not blended. It reveals descriptive differences that can generate hypotheses; it does not by itself show that a product change caused retention or that the product is getting “stickier.” [BB-C05-S17]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-05-marketing-and-customer-analytics-how-to-apply-10", "url": "#chapter-05-marketing-and-customer-analytics-how-to-apply-10", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Group Users by Cohort: Typically, group by the month or quarter they signed up. 2. Create a Retention Table: Create a triangle chart where each row is a cohort and each column is the month since that cohort joined (Month 0, Month 1, Month 2, etc.). The value in each cell is the percentage of the original cohort that is still active in that month. 3. Analyze the Curves: Curve shape: A flattening curve describes persistence under the chosen activity definition. Check censoring, seasonality, reactivation, customer mix, and whether the outcome represents value. Comparing cohorts: Higher or lower curves can reflect product changes, acquisition mix, pricing, seasonality, measurement, or external conditions. Use an experiment or justified causal design before attributing the difference." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-10", "url": "#chapter-05-marketing-and-customer-analytics-so-what-for-managers-10", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the cohort event, activity or value outcome, observation window, censoring rule, and decision before comparing retention curves. - Use the pattern to identify where to investigate product, acquisition, pricing, service, or customer-mix differences and to size follow-up evidence. - Translate a proposed retention action into a bounded test or justified causal design and monitor customer value, quality, and agency alongside retention." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-10", "url": "#chapter-05-marketing-and-customer-analytics-limits-and-critiques-10", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Higher or flatter curves can reflect product changes, acquisition mix, pricing, seasonality, external conditions, reactivation, censoring, or measurement changes. - Activity definitions are not interchangeable with customer value or product-market fit; a retention pattern is descriptive evidence, not a causal conclusion. - Cohorts can be small, immature, selected, or unlike the target population; report uncertainty and avoid universal retention benchmarks. [BB-C05-S17]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-connections-10", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-05-marketing-and-customer-analytics-connections-10", "url": "#chapter-05-marketing-and-customer-analytics-connections-10", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inputs include sign-up or starting-event dates, activity and transaction data, product instrumentation, cohort definitions, and data-quality checks. - Outputs supply definition-dependent retention estimates for CLV/CAC Analysis (Framework 4) and product decisions, and can guide Customer Journey Mapping (Framework 1) . - Reconcile cohort patterns with NPS Driver Analysis (Framework 9) , experiments, acquisition attribution, pricing, and finance before changing material spend. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-marketing-measurement-triangulation-mmm-experiments-attribution-and-finance", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Marketing Measurement Triangulation: MMM, Experiments, Attribution, and Finance", "headingId": "chapter-05-marketing-and-customer-analytics-marketing-measurement-triangulation-mmm-experiments-attribution-and-finance", "url": "#chapter-05-marketing-and-customer-analytics-marketing-measurement-triangulation-mmm-experiments-attribution-and-finance", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Marketing measurement methods answer different questions. Treating them as substitutes creates false certainty; treating discrepancies as diagnostic evidence makes the budget decision stronger. Figure 5.4. Constructed marketing-measurement triangulation loop. This original synthesis shows how four evidence streams inform a budget decision and then update one another. It does not imply that agreement proves causality or that disagreement can be averaged away. [BB-C05-S18] [BB-C05-S19] [BB-C05-S20] [BB-C05-S15] Text equivalent: Attribution describes how conversion credit changes under a path model or rule. Experiments estimate a defined incremental effect for the tested population, treatment, outcome, and period. Marketing-mix models estimate aggregate channel response under explicit model assumptions and may incorporate experimental evidence. Finance reconciles incremental contribution, cash timing, fixed and variable cost, risk, and value. Differences trigger a review of estimands, scope, data, assumptions, spillovers, and implementation before the budget is staged, monitored, and updated. Source note: Author-created teaching synthesis informed by the cited advertising-measurement, experimentation, marketing-mix, attribution, and finance evidence; no source supplies this exact loop or implies that its arrows are causal. [BB-C05-S18] [BB-C05-S19] [BB-C05-S20] [BB-C05-S15]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-what-each-method-can-and-cannot-decide", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "What each method can and cannot decide", "headingId": "chapter-05-marketing-and-customer-analytics-what-each-method-can-and-cannot-decide", "url": "#chapter-05-marketing-and-customer-analytics-what-each-method-can-and-cannot-decide", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "| Evidence stream | Strongest decision use | Required controls | Important limit | | :--- | :--- | :--- | :--- | | Attribution | Describe or model how observed touchpoints receive conversion credit; inspect paths and channel interactions | Identity resolution, missing/offline touches, path definition, consent, bot/fraud controls, model validation | Credit is not automatically incremental effect; the Li–Kannan field validation is one firm and one design, not a universal guarantee. [BB-C05-S15] | | Randomized experiment | Estimate a defined incremental effect for an eligible population, treatment, outcome, and period | Randomization integrity, power, interference, attrition, guardrails, treatment delivery, prespecified analysis | Advertising effects can be small relative to noisy customer spending, making precise ROI estimates expensive or infeasible; null or wide results are information, not proof of zero effect. [BB-C05-S18] [BB-C05-S19] | | Marketing-mix model (MMM) | Estimate aggregate channel contribution and response curves; support scenarios where individual paths are unavailable or incomplete | Consistent KPI/spend data, confounders, lag/saturation choices, priors, diagnostics, uncertainty, stability, out-of-sample checks | Causal interpretation depends on assumptions and data variation. Current open-source Meridian documentation supports experiment-informed calibration, but software does not make the assumptions true. [BB-C05-S20] | | Finance reconciliation | Convert a proposed response into incremental contribution, cash timing, capacity, fixed cost, risk, and value under scenarios | Agreed cost definitions, baseline, cannibalization, refunds/returns, working capital, tax/accounting owners, sensitivity | Revenue lift, platform-reported ROAS, and average ROI can each differ from marginal contribution and enterprise value. Use Chapter 4. |" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-a-decision-grade-triangulation-protocol", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "A decision-grade triangulation protocol", "headingId": "chapter-05-marketing-and-customer-analytics-a-decision-grade-triangulation-protocol", "url": "#chapter-05-marketing-and-customer-analytics-a-decision-grade-triangulation-protocol", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define the estimand before choosing the tool. Examples include incremental contribution from one more dollar in a channel, total campaign effect over a stated horizon, or the cash-flow effect of moving budget from one channel to another. 2. Create a measurement contract. Fix the eligible population, treatment, outcome, attribution window, geographic or customer unit, baseline, currency, cost boundary, horizon, and decision threshold. Record interference, carryover, cannibalization, and privacy constraints. 3. Use experiments where the decision and operations permit. Gordon and colleagues found that observational advertising models often did not recover the effects from 15 Facebook experiments despite rich covariates; the study is strong evidence for caution in that setting, not proof that every observational method always fails. [BB-C05-S18] 4. Use MMM for aggregate response with visible assumptions. Inspect data quality, trend, seasonality, confounding controls, lag, saturation, priors, fit, posterior uncertainty, and sensitivity. Calibrate with transportable experimental evidence only when the treatment, outcome, population, period, and spend range align. [BB-C05-S20] 5. Use attribution for journey operations, not causal theater. A path model can inform sequencing, messaging, and channel hypotheses. Treat channel credit as causal only when the identification assumptions and validation support that interpretation. [BB-C05-S15] 6. Reconcile to finance. Translate the candidate budget into units, price, discounts, returns, gross margin, service and fulfillment cost, acquisition and retention timing, capacity, working capital, fixed cost, and downside. Compare marginal—not only average—returns. 7. Explain disagreement rather than averaging it. Test scope mismatch, selection, spillovers, lag, organic demand, missing channels, treatment noncompliance, model extrapolation, and cost definitions. Narrow the claim or run the next most decision-relevant test." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-brand-equity-as-an-evidence-chain", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Brand equity as an evidence chain", "headingId": "chapter-05-marketing-and-customer-analytics-brand-equity-as-an-evidence-chain", "url": "#chapter-05-marketing-and-customer-analytics-brand-equity-as-an-evidence-chain", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Keller defines customer-based brand equity as a differential customer response associated with brand knowledge and develops awareness and brand image as its components. That theory does not make awareness, sentiment, or an association score a financial asset by itself. [BB-C05-S22] Figure 5.5. Constructed brand-equity evidence chain. Each arrow is a hypothesis requiring measurement; the chain can weaken, reverse, or be confounded at any step. [BB-C05-S22] [BB-C05-S23] [BB-C05-S24] Text equivalent: Brand awareness and associations may affect customer consideration, choice, willingness to pay, retention, referral, or channel response. Those behaviors may affect price, volume, mix, acquisition and retention cost, risk, and cash-flow timing. After operating costs, capital, and risk are considered, the result may affect enterprise value. Managers must test each link and alternative explanation rather than valuing a survey score directly. [BB-C05-S22] [BB-C05-S23] [BB-C05-S24] Source note: Author-created teaching synthesis informed by the cited customer-based brand-equity, revenue-premium, and market-based-assets evidence; the chain is a falsifiable decision aid, not a reproduced model or valuation formula. [BB-C05-S22] [BB-C05-S23] [BB-C05-S24] Use the chain as a falsification plan: - Customer knowledge: Measure aided/unaided awareness and specific associations with a defined population, instrument, and uncertainty; protect survey and customer-data rights. [BB-C05-S22] - Behavior: Test whether brand exposure or knowledge changes choice, willingness to pay, repeat purchase, retention, or referral—not merely whether the measures correlate. - Product-market outcome: Compare price, volume, mix, share, and a defensible comparator. Ailawadi, Lehmann, and Neslin propose revenue premium relative to private label for packaged-goods settings; the comparator and transferability must be justified elsewhere. [BB-C05-S23] - Economics and finance: Reconcile incremental contribution, acquisition and retention cost, cash timing, capital, risk, and alternatives. Srivastava, Shervani, and Fahey provide a framework connecting market-based assets to faster or larger cash flows, lower vulnerability and volatility, and residual value; the chain remains a theory to test in the focal firm. [BB-C05-S24] - Decision: Invest, maintain, reposition, extend, license, architecture-change, or retire only after identifying which link the action is expected to change, the evidence threshold, owner, guardrails, and stop rule. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-mental-model-1-the-job-vs-the-persona", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 1: The \"Job\" vs. The \"Persona\"", "headingId": "chapter-05-marketing-and-customer-analytics-mental-model-1-the-job-vs-the-persona", "url": "#chapter-05-marketing-and-customer-analytics-mental-model-1-the-job-vs-the-persona", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Jobs-to-be-Done offers a useful alternative lens to demographic or role-based personas by asking what progress is sought in a circumstance. A persona might say that “Sarah is a 35-year-old marketing manager,” while an illustrative job hypothesis says, “When preparing for a board meeting, Sarah struggles to reconcile data from several sources into a defensible report.” The second statement is more decision-specific, but it still requires research: it does not prove that integration or visualization is the right solution. [BB-C05-S12]" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-mental-model-2-the-leaky-bucket", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 2: The Leaky Bucket", "headingId": "chapter-05-marketing-and-customer-analytics-mental-model-2-the-leaky-bucket", "url": "#chapter-05-marketing-and-customer-analytics-mental-model-2-the-leaky-bucket", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Your customer base is a leaky bucket. Every month, a certain percentage (your churn rate) will leak out. Your marketing and sales efforts are pouring new customers into the top. If Acquisition Churn , the bucket fills up (you grow). If Acquisition < Churn , the bucket drains (you shrink). For a monthly comparison, express acquisition and churn as compatible counts over the same period and population, or as rates on the same defined base; do not compare a raw count with a rate. Use CLV and CAC scenarios to test whether retention, acquisition, or both could constrain the current model. Do not infer the principal constraint from one ratio; inspect cohort assumptions and operating evidence before increasing spend." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-mental-model-3-correlation-vs-causation", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 3: Correlation vs. Causation", "headingId": "chapter-05-marketing-and-customer-analytics-mental-model-3-correlation-vs-causation", "url": "#chapter-05-marketing-and-customer-analytics-mental-model-3-correlation-vs-causation", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Customers who click a branded-search advertisement may have high conversion because the advertisement caused action, because customers already intended to buy, or because both reflect prior exposure. The observed path cannot decide among those explanations. Multi-touch attribution changes credit rules; it does not establish causality. Use randomized holdouts or justified quasi-experimental methods when the budget decision requires an incremental-effect claim. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-worked-example-1-team-collaboration-and-the-aha-moment", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Worked Example 1: Team Collaboration and the \"Aha!\" Moment", "headingId": "chapter-05-marketing-and-customer-analytics-worked-example-1-team-collaboration-and-the-aha-moment", "url": "#chapter-05-marketing-and-customer-analytics-worked-example-1-team-collaboration-and-the-aha-moment", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A collaboration-product growth team might use cohort analysis not just to track retention, but to find an activation milestone correlated with long-term retention. They might compare cohorts that retained at high rates versus those that churned and identify a behavioral pattern, such as teams sending approximately 2,000 messages in their first 30 days. Action: In this scenario, the team uses the observed milestone to focus onboarding on the actions associated with it. Lesson: Treat an activation milestone as a predictive hypothesis. Validate out of sample and test whether changing the milestone changes customer value without harming quality or agency." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-worked-example-2-file-sync-and-the-two-sided-referral", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Worked Example 2: File Sync and the Two-Sided Referral", "headingId": "chapter-05-marketing-and-customer-analytics-worked-example-2-file-sync-and-the-two-sided-referral", "url": "#chapter-05-marketing-and-customer-analytics-worked-example-2-file-sync-and-the-two-sided-referral", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A file-sync product can use unit economics to decide whether paid acquisition is too expensive for a low-priced consumer product. In that situation, the team might focus on a viral loop. The \"Job\": A user may hire a file-sync service to share a file that is too large for email. The Referral Loop: The service can offer a two-sided referral incentive, such as extra storage for both the referrer and the new user. Why it Can Work: A referral design can make the benefit clear to both parties, but its economics should be measured rather than assumed. Lesson: Test whether a referral program lowers acquisition cost without eroding customer value." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-worked-example-3-streaming-subscription-and-the-nps-trap", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Worked Example 3: Streaming Subscription and the NPS Trap", "headingId": "chapter-05-marketing-and-customer-analytics-worked-example-3-streaming-subscription-and-the-nps-trap", "url": "#chapter-05-marketing-and-customer-analytics-worked-example-3-streaming-subscription-and-the-nps-trap", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A streaming subscription service might move away from using NPS as a primary corporate metric after finding that stated recommendation intent is a poor predictor of future behavior. A user might say they would recommend the service, then cancel a month later when a competitor launches a must-see show. The Real Metric: In this scenario, the service pairs stated intent with observed retention, viewing, and cancellation behavior. Lesson: Treat sentiment metrics as one input alongside behavioral metrics such as churn and lifetime value. ---" }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-applied-exercise-build-a-decision-grade-marketing-plan", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Applied Exercise: Build a Decision-Grade Marketing Plan", "headingId": "chapter-05-marketing-and-customer-analytics-applied-exercise-build-a-decision-grade-marketing-plan", "url": "#chapter-05-marketing-and-customer-analytics-applied-exercise-build-a-decision-grade-marketing-plan", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Using a constructed subscription dataset and customer-research packet, define the market and decision; build decision-relevant segments; select one target; write a positioning statement; propose a pricing and channel hypothesis; estimate cohort CLV and CAC ranges; map one customer journey; and design one randomized holdout or justified quasi-experiment. Deliver a one-page budget recommendation with a primary metric, guardrails, uncertainty, privacy/fairness controls, and stop, redesign, or scale rules." }, { "id": "chapter-05-marketing-and-customer-analytics::chapter-05-marketing-and-customer-analytics-selective-connections", "kind": "chapter", "itemSlug": "chapter-05-marketing-and-customer-analytics", "itemTitle": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "heading": "Selective Connections", "headingId": "chapter-05-marketing-and-customer-analytics-selective-connections", "url": "#chapter-05-marketing-and-customer-analytics-selective-connections", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use Chapter 3 for market definition, competition, and strategic alternatives. - Use Chapter 4 for customer economics, cash timing, and investment comparison. - Use Chapter 14 for channel and launch choices. - Use Chapter 18 for platform-side and network-effect economics. - Use Chapter 21 for discovery, roadmap, and product outcomes. - Use Chapter 22 for causal design, regression limits, and uncertainty communication. ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operations and Supply Chain", "headingId": "chapter-06-operations-and-supply-chain", "url": "#chapter-06-operations-and-supply-chain", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-executive-summary", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Executive Summary", "headingId": "chapter-06-operations-and-supply-chain-executive-summary", "url": "#chapter-06-operations-and-supply-chain-executive-summary", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter provides a practical toolkit for diagnosing operating problems, improving flow and quality, reconciling demand with constrained supply, and designing more resilient supply networks. It covers forecasting and S&OP alongside established systems such as the Toyota Production System and newer digital-representation tools while making assumptions, trade-offs, forecast error, and control needs visible." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-manager-decision-outcomes", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Manager decision outcomes", "headingId": "chapter-06-operations-and-supply-chain-manager-decision-outcomes", "url": "#chapter-06-operations-and-supply-chain-manager-decision-outcomes", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "By the end of this chapter, a manager should be able to: 1. Define process boundaries and reconcile throughput, work in process, and flow time with consistent units. 2. Test a constraint and distinguish throughput improvement from local utilization, cost, safety, quality, and risk effects. 3. Choose a capacity, queue, inventory, or supply-network response using demand, variability, service, cost, resilience, and option value. 4. Distinguish process stability from process capability and select an appropriate improvement or investigation method. 5. Recommend a staged operating change with frontline participation, financial consequences, safety/quality controls, and stop rules. 6. Evaluate forecasts out of sample, diagnose bias and absolute error, and run a closed S&OP loop that reconciles demand, capacity, inventory, supply, service, cash, and risk." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-core-quantitative-operations-spine", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Core Quantitative Operations Spine", "headingId": "chapter-06-operations-and-supply-chain-core-quantitative-operations-spine", "url": "#chapter-06-operations-and-supply-chain-core-quantitative-operations-spine", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For a stable process with consistent boundaries and units, Little's Law relates average work in process, throughput, and flow time: WIP = Throughput × Flow Time . Variability makes waiting rise sharply as utilization approaches capacity, so economically appropriate utilization depends on delay cost, service level, pooling, setup, reliability, and capacity flexibility—not on maximizing busy time. [BB-C06-S07] Inventory and capacity decisions require the same discipline. Author synthesis: Define demand and lead-time distributions, service and shortage consequences, ordering and holding costs, perishability, capacity indivisibility, ramp time, and supplier/network dependencies. EOQ, reorder points, safety stock, and lead/lag/match capacity are models under assumptions, not automatic policies. Queueing and capacity-expansion evidence supports the waiting/utilization and expansion boundaries below. [BB-C06-S07] [BB-C06-S08] ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-troubleshooting-guide-operations-supply-chain", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Troubleshooting Guide: Operations & Supply Chain", "headingId": "chapter-06-operations-and-supply-chain-troubleshooting-guide-operations-supply-chain", "url": "#chapter-06-operations-and-supply-chain-troubleshooting-guide-operations-supply-chain", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptom: \"We 'improved' a bunch of process steps, but our overall output hasn't increased.\" Diagnosis: A current constraint is one hypothesis. Local improvement may not raise system throughput, but it can still reduce defects, risk, setup, maintenance exposure, or future constraints. [BB-C06-S03] [BB-C06-S04] Action: Confirm the constraint with flow data, test demand and policy constraints, protect safety and quality, and re-evaluate after each change. Continue other work when its risk-adjusted value is independent of current throughput. Symptom: \"We implemented a 'Just-in-Time' inventory system to save costs, but now we're constantly out of stock and our customers are furious.\" Diagnosis: Treating JIT as an inventory-cutting tactic may have ignored pull design, process quality, lead-time and demand variability, supplier/network reliability, shortage consequences, and recovery options. The cause is not established until those conditions are investigated. Action: Re-evaluate the operating system and item-level protection policy. Compare replenishment, safety stock, capacity, supplier, redesign, and continuity options using demand and lead-time distributions, service and safety obligations, working capital, correlated disruption, and residual risk. Use the Supply Chain Risk Matrix as triage, not as an automatic policy selector. [BB-C06-S01] [BB-C06-S07] Symptom: \"Our team completed a Six Sigma project and proved a process is 'in control,' but customers are still unhappy with the output.\" Diagnosis: Your process may be precise and repeatable yet systematically miss the customer's actual requirements. Statistical control does not establish customer acceptance or fitness for purpose. Action: Revisit the \"Define\" phase of your DMAIC cycle. You have misidentified the \"Critical to Quality\" (CTQ) characteristics. You need to conduct deeper Voice of the Customer (VOC) research, likely using Jobs-to-be-Done interviews (Chapter 5), to understand what the customer actually values, then re-center your Six Sigma project on that attribute. Symptom: \"We did a Value Stream Mapping exercise, but six months later, nothing has changed.\" Diagnosis: The VSM was treated as an academic exercise, not the start of a continuous improvement culture. There was no ownership or follow-through mechanism. Action: Convert the current-state evidence into an owned future-state hypothesis and implementation plan. Involve affected frontline and control owners; test changes at appropriate scale; protect safety, accessibility, labor, and service; and measure whether the change improves the system rather than tying employment decisions mechanically to map adoption. [BB-C06-S10] ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-1-process-flow-diagrams", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "1. Process Flow Diagrams", "headingId": "chapter-06-operations-and-supply-chain-1-process-flow-diagrams", "url": "#chapter-06-operations-and-supply-chain-1-process-flow-diagrams", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Process Flow Diagramming Process Visualization" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-overview", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-06-operations-and-supply-chain-overview", "url": "#chapter-06-operations-and-supply-chain-overview", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Process-flow mapping represents steps, decisions, inputs and outputs, delays, rework, and handoffs within a defined boundary. ASQ's guide emphasizes defining scope, arranging activities in sequence, reviewing the map with people involved in the process, and checking bottlenecks, errors, delays, and excessive handoffs. A map can make operating hypotheses visible, but observation, logs, incidents, service data, or urgent containment may come first. [BB-C06-S11] Figure 6.1. Constructed process-map symbol flow. The diagram uses a teaching subset of common process-map symbols and does not represent a complete notation standard. [BB-C06-S11] Text equivalent: A start/end ellipse connects to a rectangular process step and then to a diamond decision. Yes and no branches lead to completion or rework. The symbols are a teaching subset, not a complete standard. Source note: Author-created Mermaid redraw informed by process-mapping guidance; the labels and symbols are a teaching subset and do not reproduce external artwork. [BB-C06-S11]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-how-to-apply", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-06-operations-and-supply-chain-how-to-apply", "url": "#chapter-06-operations-and-supply-chain-how-to-apply", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define Boundaries: Clearly define the start and end points of the process you are mapping. Example: \"From customer order submission to product shipped\" or \"From raw material receipt to finished goods inventory.\" 2. Use a declared symbol set: For a basic map, ASQ uses a rounded rectangle or oval for start/end, a rectangle for a process step, a diamond for a decision, and arrows for direction. Declare any additions or deviations; this teaching subset is not a complete or universal notation. [BB-C06-S11] 3. Use Swimlanes: Draw vertical or horizontal lanes for each department or role involved (e.g., Sales, Operations, Finance). When the process flow crosses a line, it represents a handoff—a common source of delays and miscommunication. 4. Annotate with Data: For each step, capture key metrics like Cycle Time (how long the step takes), Wait Time (how long work sits idle before this step), and Defect Rate ." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-example-e-commerce-order-fulfillment-process", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Example: E-Commerce Order Fulfillment Process", "headingId": "chapter-06-operations-and-supply-chain-example-e-commerce-order-fulfillment-process", "url": "#chapter-06-operations-and-supply-chain-example-e-commerce-order-fulfillment-process", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 6.2. Constructed order-fulfillment handoff map. The example exposes validation, rejection/remedy, warehouse, shipping, and customer handoffs without claiming that every retailer uses this sequence. Text equivalent: A customer places an order. Sales or the ordering system validates it. Invalid orders enter a correction or rejection path; valid orders move to warehouse picking, shipment, and customer receipt. Each handoff should record owner, queue time, cycle time, defects, system state, and exception/remedy path. Source note: Author-created Mermaid redraw informed by process-mapping guidance; the sequence and example are constructed and do not represent a company process. [BB-C06-S11]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-operator-s-checklist-creating-effective-process-maps", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operator's Checklist: Creating Effective Process Maps", "headingId": "chapter-06-operations-and-supply-chain-operator-s-checklist-creating-effective-process-maps", "url": "#chapter-06-operations-and-supply-chain-operator-s-checklist-creating-effective-process-maps", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Observe the Work Safely: When feasible and authorized, combine frontline observation with documentation and event data. Remote, sensitive, hazardous, or regulated work may require different access and privacy controls. - Include the Frontline Team: The people doing the work are the experts. They know the informal workarounds and hidden steps that never appear in official documentation. - Map Reality, Not Aspiration: Your first map should capture the current state, warts and all. You'll create an ideal \"future state\" map later. - Look for Handoffs: Every time work crosses a swimlane (department boundary), there's risk of delay, miscommunication, and dropped balls. These are prime targets for improvement. - Capture Wait Times: The time work spends between steps can exceed actual process time by a large margin; use observed flow, service, quality, safety, and customer evidence to identify high-leverage opportunities." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-constructed-classroom-exercise-paper-airplane-flow", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Constructed Classroom Exercise: Paper-Airplane Flow", "headingId": "chapter-06-operations-and-supply-chain-constructed-classroom-exercise-paper-airplane-flow", "url": "#chapter-06-operations-and-supply-chain-constructed-classroom-exercise-paper-airplane-flow", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A facilitator can use an explicitly constructed paper-airplane simulation to compare batch size, handoffs, WIP, throughput, defects, and flow time. Record the process and results rather than attributing universal outcomes or an unverified corporate training practice." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-contrarian-thinking-when-not-to-map", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: When NOT to Map", "headingId": "chapter-06-operations-and-supply-chain-contrarian-thinking-when-not-to-map", "url": "#chapter-06-operations-and-supply-chain-contrarian-thinking-when-not-to-map", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "While process mapping is powerful, over-mapping can be a form of waste itself. Don't map: - Creative processes: Mapping interfaces, decisions, or learning loops may help, but do not force exploratory work into a linear production model. - One-off processes: A one-time high-risk event may still warrant a map for coordination, safety, audit, or learning. - Highly variable processes: If every instance is unique (e.g., complex legal cases), a single process map won't capture the reality." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-06-operations-and-supply-chain-so-what-for-managers", "url": "#chapter-06-operations-and-supply-chain-so-what-for-managers", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the process boundary, owners, queues, handoffs, and exception paths before proposing an improvement. - Combine observation with event, service, incident, customer, and safety evidence; a map is a hypothesis record, not the evidence itself. - Use the map to stage changes and monitor cycle time, waiting, rework, quality, accessibility, labor, and risk effects." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-06-operations-and-supply-chain-limits-and-critiques", "url": "#chapter-06-operations-and-supply-chain-limits-and-critiques", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A map is a selective representation and cannot by itself establish causality, capacity, customer value, or the best intervention. - “Value-added” and “waste” classifications depend on customer, safety, regulatory, learning, and service context. - Creative, one-off, remote, or highly variable work may require scenarios, qualitative evidence, or other methods alongside mapping." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-connections", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-06-operations-and-supply-chain-connections", "url": "#chapter-06-operations-and-supply-chain-connections", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The best data comes from direct observation of the frontline team and their feedback (Gemba walk). Output: A completed process map can inform a Value Stream Map , Theory of Constraints Analysis , and Six Sigma project; it is one possible starting point for improvement. ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-2-lean-the-8-wastes", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "2. Lean & The 8 Wastes", "headingId": "chapter-06-operations-and-supply-chain-2-lean-the-8-wastes", "url": "#chapter-06-operations-and-supply-chain-2-lean-the-8-wastes", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Lean & The 8 Wastes (TIMWOODS) Waste Elimination" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-overview-2", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-06-operations-and-supply-chain-overview-2", "url": "#chapter-06-operations-and-supply-chain-overview-2", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Lean developed from Toyota Production System practices and later practitioner synthesis. Womack's retrospective states five principles: customer value, value stream, flow, pull, and continuing pursuit of perfection. Use waste categories to investigate flow and customer value while protecting safety, quality, reliability, people, supplier health, learning, and necessary resilience; a labeled “waste” is a hypothesis, not an automatic deletion. [BB-C06-S01] [BB-C06-S02]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-visual-the-8-wastes-timwoods", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Visual: The 8 Wastes (TIMWOODS)", "headingId": "chapter-06-operations-and-supply-chain-visual-the-8-wastes-timwoods", "url": "#chapter-06-operations-and-supply-chain-visual-the-8-wastes-timwoods", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 6.1. TIMWOODS investigation prompts. These categories identify places to investigate; they do not authorize removal without customer, safety, quality, resilience, labor, accessibility, learning, and risk evidence. [BB-C06-S01] [BB-C06-S02] | Category | Look for | Evidence before changing the work | | :--- | :--- | :--- | | Transportation | Unnecessary movement of material, information, or files | Route, handoff, delay, damage, security, and alternate-layout evidence | | Inventory | Stock or WIP beyond the protection required for service and risk | Demand, lead-time, shortage, expiry, cash, supplier, and disruption evidence | | Motion | Avoidable searching, reaching, walking, or interface switching | Ergonomics, safety, accessibility, time, error, and workplace-design evidence | | Waiting | Work or customers queued for a resource, approval, input, or decision | Queue, capacity, priority, service, and dependency evidence | | Overproduction | Output made earlier or in greater quantity than downstream need | Demand, batch, setup, expiry, WIP, and capacity evidence | | Over-processing | Activity or precision beyond requirement | Customer, regulation, quality, audit, learning, and simplification evidence | | Defects | Scrap, correction, rework, failed service, or inaccurate information | Definition, measurement-system, cause, severity, containment, and recurrence evidence | | Skills unused | Frontline knowledge or capability excluded from the work design | Participation, psychological safety, authorization, workload, and adoption evidence |" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-06-operations-and-supply-chain-how-to-apply-2", "url": "#chapter-06-operations-and-supply-chain-how-to-apply-2", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Conduct a \"Gemba Walk\" (go to the actual place where work is done) and hunt for the 8 Wastes: 1. T ransportation: Unnecessary movement of materials, information, or files. Example: A document that gets physically passed between 5 different offices before approval. Solution: Co-locate teams, use digital workflows, or redesign the layout to minimize movement. 2. I nventory: Excess stock or work-in-progress (WIP) that ties up cash and hides problems. Example: A warehouse full of components \"just in case\" they're needed. Solution: Test pull systems (Kanban), smaller batches, and JIT-style replenishment only when demand, lead-time, quality, service, safety, and supplier evidence supports the design. 3. M otion: Wasted movement by people (e.g., walking to a printer, searching for a tool). Constructed example: A nurse walking a long distance each shift to retrieve supplies from a central supply room. Solution: Apply 5S methods where they improve safety, access, search time, quality, or reliability; do not assume one layout fits every work setting. 4. W aiting: Idle time between process steps and decisions; investigate its causes and service consequences. Constructed example: Parts sitting for several days waiting for the next manufacturing step. Solution: Test workload balance, flow, pull, staffing, queue, and priority alternatives against service and safety requirements. 5. O verproduction: Making more, sooner, or faster than the next process needs. Constructed example: Manufacturing produces more units than the next process or customer demand requires. Solution: Align release with demand, capacity, service, shelf-life, and downstream requirements using an appropriate planning and replenishment rule. 6. O ver-processing: Doing more work than the customer values (e.g., unnecessary features, excessive reporting). Example: Creating beautiful PowerPoint decks when a simple email would suffice. Solution: Validate what the customer actually values (Voice of Customer), then remove steps that evidence shows are not required by customer, safety, quality, regulatory, or learning needs. 7. D efects: Rework, scrap, and incorrect information that requires correction. Example: 15% of manufactured parts fail quality inspection and require rework. Solution: Implement Poka-Yoke (error-proofing), use Six Sigma DMAIC to reduce variation. 8. S kills (Unused): Failing to utilize the talent, ideas, and creativity of your team. Example: In a constructed case, experienced assembly workers are not included in improvement design. Solution: Implement suggestion systems, run Kaizen events with frontline teams, create a culture of continuous improvement." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-sourced-practice-example-virginia-mason-health-system", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Sourced Practice Example: Virginia Mason Health System", "headingId": "chapter-06-operations-and-supply-chain-sourced-practice-example-virginia-mason-health-system", "url": "#chapter-06-operations-and-supply-chain-sourced-practice-example-virginia-mason-health-system", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Kenney documents Virginia Mason's use of lean-healthcare methods and Toyota-inspired learning. Use the case to discuss translation into a service and clinical environment; do not infer exact wait, inventory, savings, satisfaction, or outcome effects without page-level inspection and design evidence. [BB-C06-S05]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-5-whys-for-waste", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operator's Practical Tip: The \"5 Whys\" for Waste", "headingId": "chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-5-whys-for-waste", "url": "#chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-5-whys-for-waste", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "When you identify waste, don't just eliminate the symptom. Use the \"5 Whys\" technique to find the root cause: - Observation: \"There's a pile of work-in-progress inventory sitting here.\" - Why? \"Because the next step is backed up.\" - Why? \"Because that machine breaks down frequently.\" - Why? \"Because we don't do preventive maintenance.\" - Why? \"Because we don't have a maintenance schedule.\" - Why? \"Because no one owns the responsibility for creating one.\" - Solution: Assign ownership and create a preventive maintenance program." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-contrarian-thinking-some-waste-is-strategic", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: Some \"Waste\" is Strategic", "headingId": "chapter-06-operations-and-supply-chain-contrarian-thinking-some-waste-is-strategic", "url": "#chapter-06-operations-and-supply-chain-contrarian-thinking-some-waste-is-strategic", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Not all waste should be eliminated: - Strategic Inventory: Holding extra inventory of critical components from unreliable suppliers is insurance, not waste (see Supply Chain Risk Matrix). - Slack Capacity: Having some idle capacity in non-bottleneck steps can be rational when it protects system flow, maintenance, safety, service, or resilience. [BB-C06-S04] - Experimentation: In R&D, \"defects\" (failed experiments) are necessary learning. Eliminating them would kill innovation." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-06-operations-and-supply-chain-so-what-for-managers-2", "url": "#chapter-06-operations-and-supply-chain-so-what-for-managers-2", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use TIMWOODS categories to form testable hypotheses about flow, cost, service, quality, and customer value; do not delete work from a label alone. - Include frontline workers and supplier, safety, accessibility, resilience, and learning evidence before changing the system. - Prioritize improvements against system throughput, service, quality, cash, and risk rather than local utilization alone." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-06-operations-and-supply-chain-limits-and-critiques-2", "url": "#chapter-06-operations-and-supply-chain-limits-and-critiques-2", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Inventory, slack capacity, redundancy, and failed experiments can be protective or valuable; “waste” is context-dependent. - Gemba observation and 5 Whys can surface hypotheses but do not prove a root cause without measurement and challenge. - Lean practices depend on process stability, leadership, worker participation, supplier conditions, and the decision horizon." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-connections-2", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-06-operations-and-supply-chain-connections-2", "url": "#chapter-06-operations-and-supply-chain-connections-2", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: A Process Flow Diagram (Framework 1) makes waste, especially Waiting and Transportation, visually obvious. Output: The identified wastes are prioritized and become the targets for Kaizen (rapid improvement) events or larger Value Stream Mapping initiatives. ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-3-six-sigma-dmaic-cycle", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "3. Six Sigma (DMAIC Cycle)", "headingId": "chapter-06-operations-and-supply-chain-3-six-sigma-dmaic-cycle", "url": "#chapter-06-operations-and-supply-chain-3-six-sigma-dmaic-cycle", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Six Sigma (DMAIC Cycle) Data-Driven Quality Improvement" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-overview-3", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-06-operations-and-supply-chain-overview-3", "url": "#chapter-06-operations-and-supply-chain-overview-3", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "DMAIC is a structured improvement cycle for a defined, measurable process problem. The familiar 3.4 defects per million opportunities figure depends on a conventional long-term 1.5-sigma shift, a defined opportunity count, and distribution assumptions. Report the actual defect definition, denominator, measurement quality, stability, capability, uncertainty, and customer requirement rather than treating “sigma level” as universal quality. [BB-C06-S06]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-visual-the-dmaic-cycle", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Visual: The DMAIC Cycle", "headingId": "chapter-06-operations-and-supply-chain-visual-the-dmaic-cycle", "url": "#chapter-06-operations-and-supply-chain-visual-the-dmaic-cycle", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 6.3. DMAIC evidence-and-control loop. The redraw treats each phase as a decision gate and returns control evidence to a new problem definition; it does not imply that a phase is complete because a document exists. [BB-C06-S06] Text equivalent: Define the customer, problem, scope, requirement, owner, and safety constraints. Measure the baseline with a validated measurement system. Analyze competing causes and uncertainty. Improve through bounded tests with guardrails. Control the adopted process with owners, response plans, and monitoring, then use new evidence to redefine or close the problem. Source note: Author-created decision-loop redraw informed by DMAIC framing. The phases, labels, and return path are teaching synthesis, not a claim that documentation alone completes a project. [BB-C06-S06]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-06-operations-and-supply-chain-how-to-apply-3", "url": "#chapter-06-operations-and-supply-chain-how-to-apply-3", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "DMAIC is a rigorous, 5-phase project management methodology: 1. Define: Define the problem, the customer, and the Critical-to-Quality (CTQ) requirements. - Key Question: What does the customer consider a defect? - Tools: Project Charter, SIPOC diagram (Suppliers, Inputs, Process, Outputs, Customers), Voice of Customer research - Deliverable: A clear problem statement and measurable goal (e.g., \"Reduce order fulfillment errors from 5% to 1%\") 2. Measure: Collect data and measure the current performance of the process. Establish a baseline defect rate. - Key Question: How bad is the problem right now, and how do we measure it consistently? - Tools: Process mapping, data collection plans, measurement system analysis (to ensure your measurements are reliable) - Deliverable: Baseline metrics (e.g., \"Current defect rate: 5.2%, Sigma level: 3.1\") 3. Analyze: Use statistical tools to analyze the data and identify the root cause(s) of the defects. - Key Question: What are the root causes of variation and defects in this process? - Tools: Fishbone diagrams, Pareto charts, regression analysis, hypothesis testing - Deliverable: Validated root causes with statistical evidence 4. Improve: Brainstorm, pilot, and implement solutions that address the root causes. - Key Question: What changes will eliminate or reduce the root causes? - Tools: Brainstorming, Design of Experiments (DOE), pilot testing - Deliverable: Implemented solution with proven results (e.g., \"New process reduces defect rate to 0.8%\") 5. Control: Implement controls and monitoring systems to ensure the improvements are sustained. - Key Question: How do we prevent the process from reverting to its old state? - Tools: Statistical Process Control (SPC) charts, standard work documentation, training programs, audits - Deliverable: Control plan, updated SOPs, SPC charts monitoring key metrics" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-historical-context-and-evidence-boundary", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Historical Context and Evidence Boundary", "headingId": "chapter-06-operations-and-supply-chain-historical-context-and-evidence-boundary", "url": "#chapter-06-operations-and-supply-chain-historical-context-and-evidence-boundary", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Six Sigma is associated with Motorola's quality-improvement practice and later practitioner adoption. The registered source supports DMAIC management framing and the conventional performance target; this chapter does not retain unverified company defect, award, or savings figures. [BB-C06-S06]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-operator-s-practical-tip-define-before-analyzing", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operator's Practical Tip: Define Before Analyzing", "headingId": "chapter-06-operations-and-supply-chain-operator-s-practical-tip-define-before-analyzing", "url": "#chapter-06-operations-and-supply-chain-operator-s-practical-tip-define-before-analyzing", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A weak problem, customer, defect, or measurement definition can invalidate later analysis. Establish purpose, scope, affected parties, operational definition, measurement-system evidence, and decision ownership before modeling: - Don't assume: Just because you've always measured \"on-time delivery\" doesn't mean that's what the customer actually cares most about. - Interview customers: Use Jobs-to-be-Done interviews (Chapter 5) to understand what outcomes they're trying to achieve. - Translate to CTQ: Convert customer needs into measurable Critical to Quality characteristics." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-sigma-and-dpmo-interpretation-boundary", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Sigma and DPMO Interpretation Boundary", "headingId": "chapter-06-operations-and-supply-chain-sigma-and-dpmo-interpretation-boundary", "url": "#chapter-06-operations-and-supply-chain-sigma-and-dpmo-interpretation-boundary", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "DPMO = defects / (units × defined opportunities per unit) × 1,000,000 . The result depends on what counts as a unit, opportunity, and defect. Do not convert DPMO to a sigma label or quality judgment without stating the long-term-shift and distribution conventions. A statistically stable process can still be incapable of meeting specifications, and an apparently capable process can be unstable or poorly measured. [BB-C06-S06] [BB-C06-S09]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-contrarian-thinking-six-sigma-can-kill-innovation", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: Six Sigma Can Kill Innovation", "headingId": "chapter-06-operations-and-supply-chain-contrarian-thinking-six-sigma-can-kill-innovation", "url": "#chapter-06-operations-and-supply-chain-contrarian-thinking-six-sigma-can-kill-innovation", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "While incredibly powerful for optimizing existing, high-volume processes, applying Six Sigma to creative or innovative work (like R&D) can be disastrous: - Innovation requires variation: Experimentation means trying new things, where \"defects\" (failed experiments) are necessary learning. - Six Sigma optimizes for efficiency: It reduces variation, which is the opposite of what you need in exploration and creativity. - Rule of Thumb: Use Six Sigma for exploitation (optimizing known processes). Use Lean Startup/Agile for exploration (discovering new products/markets)." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-06-operations-and-supply-chain-so-what-for-managers-3", "url": "#chapter-06-operations-and-supply-chain-so-what-for-managers-3", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the customer requirement, defect, opportunity, unit, measurement system, owner, and decision before calculating a sigma or capability result. - Use stability and capability evidence to select a bounded pilot, then retain a control plan that states triggers, responses, and escalation. - Separate exploratory learning from repeatable-process improvement so efficiency targets do not suppress useful variation." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-06-operations-and-supply-chain-limits-and-critiques-3", "url": "#chapter-06-operations-and-supply-chain-limits-and-critiques-3", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The 3.4 DPMO convention depends on a long-term shift, opportunity definition, distribution, and measurement assumptions; it is not universal quality. - A stable process can be incapable, and an apparently capable result can be invalid if the measurement system, subgrouping, or specification is wrong. - DMAIC does not prove causality or guarantee a durable result; data quality, adoption, safety, and customer requirements remain decisive." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-connections-3", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-06-operations-and-supply-chain-connections-3", "url": "#chapter-06-operations-and-supply-chain-connections-3", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: A problem identified by a high Defect Rate on a Process Flow Diagram or a poor quality metric on a Financial Ratios Dashboard (Chapter 4) . Output: A control plan and a measured improvement hypothesis; any defect-rate change must be demonstrated with local data. The SPC Charts (Framework 8) are a key tool used in the \"Control\" phase. ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-4-theory-of-constraints-toc", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "4. Theory of Constraints (TOC)", "headingId": "chapter-06-operations-and-supply-chain-4-theory-of-constraints-toc", "url": "#chapter-06-operations-and-supply-chain-4-theory-of-constraints-toc", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Theory of Constraints (TOC) Bottleneck Management" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-overview-4", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-06-operations-and-supply-chain-overview-4", "url": "#chapter-06-operations-and-supply-chain-overview-4", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Theory of Constraints (TOC) is a management philosophy associated with Goldratt and Cox's The Goal . It focuses attention on the factor currently limiting a defined system goal, but “one constraint” is an operating abstraction: constraints can be interacting, product- or horizon-specific, misidentified, or shifting. Work away from the current throughput constraint can still create independent value through safety, quality, reliability, maintenance, risk reduction, learning, demand, or preparation for a future constraint. [BB-C06-S03] [BB-C06-S04]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-visual-identifying-the-bottleneck", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Visual: Identifying the Bottleneck", "headingId": "chapter-06-operations-and-supply-chain-visual-identifying-the-bottleneck", "url": "#chapter-06-operations-and-supply-chain-visual-identifying-the-bottleneck", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 6.4. Constructed five-step capacity line. Under one product, one route, qualified output, adequate demand, and the stated capacities, assembly is the candidate constraint at five units per hour. Actual throughput can be lower because of downtime, yield, setup, starvation, blocking, mix, labor, or policy. Text equivalent: Material moves through cutting at 10 units per hour, polishing at 15, assembly at 5, testing at 12, and packing at 20. Work may accumulate before assembly, making it the candidate constraint in this simplified case. Managers must verify qualified throughput, demand, mix, downtime, setup, flow, safety, quality, and policy before acting. Source note: Author-created capacity-line example informed by Theory of Constraints logic. Capacities and positions are constructed teaching inputs, not a measured facility or benchmark. [BB-C06-S03] [BB-C06-S04]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-06-operations-and-supply-chain-how-to-apply-4", "url": "#chapter-06-operations-and-supply-chain-how-to-apply-4", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The five focusing steps: 1. Identify the Constraint Map your process and identify a candidate constraint using qualified throughput, WIP, demand, mix, downtime, setup, and policy evidence. A pile of work or a long cycle time is a clue, not proof of the system constraint. - How to spot it: Look for the step where work piles up upstream, or the step that has the longest cycle time. - Common mistake: Focusing on the busiest resource. The constraint isn't necessarily the busiest; it's the one limiting total output. 2. Exploit the Constraint Improve use of the constraint without compromising safety, quality, maintenance, labor, or regulation. - Protect productive time: Reduce avoidable waits for materials, approvals, or repairs while preserving required controls and maintenance. - Eliminate waste at the bottleneck: Reduce setup times, eliminate defects that waste constraint time, optimize the work sequence. - Consider capacity options: Scheduling, setup reduction, cross-training, shifts, or outsourcing require fatigue, safety, quality, cost, and labor review. 3. Subordinate Everything Else Coordinate non-constraint work with the current flow hypothesis when doing so improves the defined system goal and does not compromise safety, quality, maintenance, service, learning, or other independent obligations. - Control overproduction: Match release and production to downstream demand and variability where excess WIP would create delay, cost, expiry, or quality risk. - Design buffers: Size time, capacity, or inventory protection from variability, service, perishability, cost, and risk rather than using a universal “small” buffer. - Permit protective capacity: Non-constraint resources need not maximize utilization; idle or reserved capacity can be rational when it protects flow, resilience, maintenance, or service. 4. Elevate the Constraint If evidence shows that more system output is valuable, compare capacity investment at the current constraint with demand management, redesign, quality, policy, risk, and alternative interventions. The canonical sequence is a focusing aid, not an absolute ban on earlier investment. - Options: Add staff, buy another machine, outsource the bottleneck step, or completely redesign the process. - Value test: Capacity at the current constraint may raise throughput, but compare demand, future constraints, economics, risk, and alternative interventions before investing. 5. Repeat After an intervention, remeasure the system and return to Step 1; the constraint may move, remain, or prove to have been misidentified. - Warning: Don't let inertia become the constraint. After elevating, re-examine your policies and assumptions. Figure 6.5. Theory of Constraints five focusing steps. The canonical loop returns from elevation to identification; measurement is a control across every step, not a replacement focusing step. [BB-C06-S03] [BB-C06-S04] Text equivalent: Identify the current system constraint, exploit it within safety and quality limits, subordinate other work to system flow, elevate the constraint when evidence supports investment, then return to identification and prevent old policies from becoming the constraint. Measure flow, safety, quality, cost, and risk throughout. Source note: Original redraw of the Theory of Constraints focusing steps; the dotted measurement node is an explicit control overlay, not an added canonical step. [BB-C06-S03] [BB-C06-S04]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-constructed-semiconductor-constraint-example", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Constructed Semiconductor Constraint Example", "headingId": "chapter-06-operations-and-supply-chain-constructed-semiconductor-constraint-example", "url": "#chapter-06-operations-and-supply-chain-constructed-semiconductor-constraint-example", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "In a constructed fabrication line, a lithography step limits qualified output. The team protects required maintenance and quality checks, reduces avoidable setup and starvation, limits upstream release, and compares an additional tool with scheduling, yield, and demand options. The case is illustrative and makes no claim about a named manufacturer or equipment cost." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-operator-s-critical-insight-optimize-the-system-not-local-busy-time", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operator's Critical Insight: Optimize the System, Not Local Busy Time", "headingId": "chapter-06-operations-and-supply-chain-operator-s-critical-insight-optimize-the-system-not-local-busy-time", "url": "#chapter-06-operations-and-supply-chain-operator-s-critical-insight-optimize-the-system-not-local-busy-time", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The current constraint can bound throughput under the specified demand, routing, mix, quality, and time horizon. - Lost productive constraint time can reduce feasible throughput, but maintenance, safety, quality, and controlled downtime may protect total value. - Nonconstraint improvements can reduce defects, risk, cost, setup, fatigue, or future bottlenecks even when they do not raise current throughput. [BB-C06-S03] [BB-C06-S04]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-visual-drum-buffer-rope-system", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Visual: Drum-Buffer-Rope System", "headingId": "chapter-06-operations-and-supply-chain-visual-drum-buffer-rope-system", "url": "#chapter-06-operations-and-supply-chain-visual-drum-buffer-rope-system", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "TOC uses a \"Drum-Buffer-Rope\" system to synchronize production: Figure 6.6. Constructed drum-buffer-rope control logic. The constraint schedule is the drum, a context-sized time/capacity/inventory buffer protects it from selected variation, and the rope controls upstream release. The design does not require zero upstream activity or a universally small buffer. [BB-C06-S03] [BB-C06-S04] Text equivalent: Demand and the constraint schedule set a paced release signal. Upstream work replenishes a protective buffer rather than maximizing local output. Buffer status and constraint performance feed back to release. Safety, quality, maintenance, perishability, reliability, service, and disruption risk determine whether and how the control should be used. Source note: Author-created drum-buffer-rope redraw informed by Theory of Constraints logic. Buffer size, release rules, and controls are context-specific teaching synthesis. [BB-C06-S03] [BB-C06-S04]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-contrarian-thinking-efficiency-is-a-trap", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: Efficiency is a Trap", "headingId": "chapter-06-operations-and-supply-chain-contrarian-thinking-efficiency-is-a-trap", "url": "#chapter-06-operations-and-supply-chain-contrarian-thinking-efficiency-is-a-trap", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "TOC directly contradicts traditional \"efficiency\" thinking: - Traditional view: \"Keep every machine and every person busy all the time.\" - TOC view: Local utilization should serve system flow rather than become an end in itself. - Why? Producing without downstream demand can create excess WIP; protective capacity may still support variability, maintenance, safety, and service. - Balanced measures: Track throughput, WIP, flow time, service, quality, safety, cost, and risk rather than one utilization target." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-06-operations-and-supply-chain-so-what-for-managers-4", "url": "#chapter-06-operations-and-supply-chain-so-what-for-managers-4", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Validate the system goal, demand, mix, horizon, and qualified throughput before naming the current constraint. - Exploit and elevate the constraint only after checking safety, quality, maintenance, labor, service, economics, and alternative interventions. - Remeasure after each intervention and return to identification when the constraint moves, persists, or was misidentified." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-06-operations-and-supply-chain-limits-and-critiques-4", "url": "#chapter-06-operations-and-supply-chain-limits-and-critiques-4", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Constraints can be multiple, interacting, policy-based, demand-based, or shifting; “one bottleneck” is a useful abstraction, not a law. - Nonconstraint work can create independent value through safety, quality, reliability, learning, preparation, or future-constraint reduction. - More capacity at a bottleneck does not guarantee more value if demand, mix, downstream flow, cash, or service conditions do not support it." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-connections-4", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-06-operations-and-supply-chain-connections-4", "url": "#chapter-06-operations-and-supply-chain-connections-4", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: A Process Flow Diagram (Framework 1) with cycle time data is essential for identifying the constraint. Output: The analysis informs Capacity Planning (Framework 7) by identifying precisely where investment in new capacity will actually increase system-wide output. ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-5-inventory-management-models", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "5. Inventory Management Models", "headingId": "chapter-06-operations-and-supply-chain-5-inventory-management-models", "url": "#chapter-06-operations-and-supply-chain-5-inventory-management-models", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Inventory Management Models (EOQ vs. JIT) Stock Optimization" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-overview-5", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-06-operations-and-supply-chain-overview-5", "url": "#chapter-06-operations-and-supply-chain-overview-5", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Inventory is a double-edged sword: too little, and you risk stockouts and lost sales; too much, and you tie up cash and risk obsolescence. This section compares two classic models—EOQ and JIT—alongside the separate protection-policy choices needed for uncertain demand and supply." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-visual-eoq-vs-jit-comparison", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Visual: EOQ vs. JIT Comparison", "headingId": "chapter-06-operations-and-supply-chain-visual-eoq-vs-jit-comparison", "url": "#chapter-06-operations-and-supply-chain-visual-eoq-vs-jit-comparison", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 6.7. Constructed EOQ/JIT decision path. EOQ is a cost-minimizing lot-size model under explicit assumptions. JIT is a pull-and-flow operating system, not a command to drive inventory to zero. Both require separate treatment of variability, shortage consequences, service, quality, resilience, and working capital. [BB-C06-S01] [BB-C06-S07] Text equivalent: EOQ converts demand, ordering cost, and unit holding cost into a candidate order quantity when its assumptions are adequate. JIT links replenishment to consumption while improving flow and quality. Neither approach determines the protective inventory needed for uncertain demand, unreliable supply, safety, or continuity. Source note: Author-created decision-path redraw. The EOQ and JIT labels are bounded by the adjacent assumptions and do not establish a universal inventory policy. [BB-C06-S01] [BB-C06-S07]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-06-operations-and-supply-chain-how-to-apply-5", "url": "#chapter-06-operations-and-supply-chain-how-to-apply-5", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Economic Order Quantity (EOQ) EOQ calculates the order quantity that minimizes the model's ordering and holding costs under assumptions such as stable demand, fixed order cost, constant unit holding cost, no stockouts, and unconstrained replenishment. Validate those assumptions before use. Formula: EOQ = √(2DS/H) - D = Annual demand (units/year) - S = Fixed cost per order ($) - H = Holding cost per unit per year ($) Illustrative Calculation: - Annual demand: 10,000 units - Order cost: $100 per order - Holding cost: $5 per unit per year - EOQ = √(2 × 10,000 × 100 / 5) = √400,000 = 632 units per order - Orders per year = 10,000 / 632 = 16 orders Use when: The assumptions are reasonable enough for the decision and sensitivity does not reverse it; otherwise use a model that represents uncertainty, service, shortage, perishability, capacity, or quantity discounts. 2. Reorder points and protection: - Define the service target, demand during lead time, review period, lead-time distribution, shortage consequence, perishability, and supplier recovery before setting a reorder point. - A simple teaching form is Reorder Point = expected demand during lead time + safety stock ; size safety stock from the stated service target, demand/lead-time variability, correlation, and review policy rather than a universal days-of-supply rule. - For multi-echelon networks, model where protection sits and how upstream and downstream buffers interact; do not add independent safety stock at every node without checking total cost and service. 3. Just-in-Time (JIT) JIT is a pull-oriented operating system that seeks flow, quality at source, small batches, and replenishment linked to consumption. “As little inventory as possible” is not the goal when variability, service, safety, or resilience requires protection. [BB-C06-S01] Core Principles: - Use a pull signal where appropriate: Link replenishment to consumption and an explicit protection policy; forecasts still inform capacity, procurement, and supplier planning. - Small batch sizes: Frequent deliveries of small quantities - Supplier capability and recovery: Validate lead time, quality, information, capacity, geographic exposure, and recovery options; proximity alone is not a guarantee. - Quality at the source: Build supplier and process quality into the system; retain incoming verification where risk, regulation, or evidence requires it. Use when: The pull design fits observed demand, lead-time, quality, service, supplier, and resilience evidence; validate reliability rather than assuming it." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-toyota-production-system-evidence-boundary", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Toyota Production System Evidence Boundary", "headingId": "chapter-06-operations-and-supply-chain-toyota-production-system-evidence-boundary", "url": "#chapter-06-operations-and-supply-chain-toyota-production-system-evidence-boundary", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Ohno's account supports JIT, pull, flow, and waste-elimination principles in the Toyota Production System. It does not support the exact delivery-hour, inventory-day, working-capital, earthquake, or post-disruption claims previously presented here. Use local demand, lead-time, quality, supplier, and disruption evidence to design inventory protection. [BB-C06-S01]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-the-hybrid-approach-best-of-both-worlds", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "The Hybrid Approach: Best of Both Worlds", "headingId": "chapter-06-operations-and-supply-chain-the-hybrid-approach-best-of-both-worlds", "url": "#chapter-06-operations-and-supply-chain-the-hybrid-approach-best-of-both-worlds", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 6.2. Constructed candidate hybrid inventory policies. The item descriptions suggest models to evaluate, not automatic assignments. | Item or flow condition | Candidate policy | Quantify before selecting | | :--- | :--- | :--- | | Stable demand and replenishment with material order cost | EOQ or periodic/continuous review | Demand and lead-time error, order and holding cost, service, shortage, lot and capacity constraints | | Reliable repetitive flow with short feedback | Pull/JIT with evidence-based protection | Supplier/process reliability, quality, setup, batch, recovery, labor, transport, and disruption exposure | | High-consequence or concentrated supply | Pull plus item/network-specific protection | Failure modes, correlated disruption, recovery time, substitution, qualification, safety, service, and working capital | | High-value or low-volume item with a capable supplier | Vendor-managed inventory or consignment candidate | Ownership, information rights, incentives, obsolescence, audit, liability, service, and supplier resilience |" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-operator-s-decision-matrix", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operator's Decision Matrix", "headingId": "chapter-06-operations-and-supply-chain-operator-s-decision-matrix", "url": "#chapter-06-operations-and-supply-chain-operator-s-decision-matrix", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Choose your inventory strategy based on two factors: Table 6.3. Constructed inventory-policy decision matrix. The candidate policies are prompts for scenario analysis, not automatic assignments. | Demand Variability | Supply Reliability | Candidate Strategy | |--------------------|-------------------|---------------------| | Low (predictable) | High | JIT | | Low (predictable) | Low | EOQ + Safety Stock | | High (volatile) | High | Hybrid (JIT + Buffer)| | High (volatile) | Low | Hold Safety Stock |" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-resilience-boundary", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Resilience Boundary", "headingId": "chapter-06-operations-and-supply-chain-resilience-boundary", "url": "#chapter-06-operations-and-supply-chain-resilience-boundary", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Do not optimize inventory in isolation. Compare ordering, holding, shortage, obsolescence, working-capital, service, safety, supplier, concentration, and disruption costs under explicit scenarios. A hybrid policy may be appropriate, but the buffer must be item-, network-, and decision-specific." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-06-operations-and-supply-chain-so-what-for-managers-5", "url": "#chapter-06-operations-and-supply-chain-so-what-for-managers-5", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Select EOQ, pull/JIT, reorder, safety-stock, or hybrid policies only after defining demand, lead time, service, shortage, holding, and disruption assumptions. - Use EOQ as a candidate lot-size calculation and compare it with scenario-based shortage, perishability, capacity, supplier, and quality consequences. - Reconcile inventory choices with working capital, customer service, safety, supplier concentration, and recovery options." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-06-operations-and-supply-chain-limits-and-critiques-5", "url": "#chapter-06-operations-and-supply-chain-limits-and-critiques-5", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- EOQ assumes stable demand, fixed order cost, constant holding cost, no stockouts, and unconstrained replenishment; real decisions often violate these assumptions. - JIT is a pull-and-flow system, not a universal zero-inventory policy; variability and resilience can justify protection. - Aggregate inventory ratios can hide item, location, lifecycle, substitution, and network-level risk." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-connections-5", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-06-operations-and-supply-chain-connections-5", "url": "#chapter-06-operations-and-supply-chain-connections-5", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Demand forecasts from the Sales team and lead times from the Procurement/Supply Chain team are critical inputs. Output: The chosen inventory strategy directly impacts your Working Capital Cycle (Chapter 4) and the resilience of your operations as mapped in the Supply Chain Risk Matrix (Framework 6) . ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-6-supply-chain-risk-matrix", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "6. Supply Chain Risk Matrix", "headingId": "chapter-06-operations-and-supply-chain-6-supply-chain-risk-matrix", "url": "#chapter-06-operations-and-supply-chain-6-supply-chain-risk-matrix", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Supply Chain Risk Matrix Resilience Planning" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-overview-6", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-06-operations-and-supply-chain-overview-6", "url": "#chapter-06-operations-and-supply-chain-overview-6", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Supply-chain risk triage in this matrix is an author-created ordinal aid, not a published quantitative model or estimate of expected loss. Define the disruption scenario, time horizon, evidence, affected service, dependencies, detectability, recovery, and owner; separately analyze concentration, correlated failures, tail risk, and mitigation economics. Figure 6.8. Constructed supply-chain risk triage matrix. The anonymous positions are discussion prompts, not measured probabilities, expected losses, or automatic action rules. Text equivalent: Place each explicitly defined disruption scenario on ordinal likelihood and impact axes for triage. High-impact scenarios require contingency and recovery analysis even when likelihood is uncertain; high-likelihood scenarios require process and control analysis. An owner must validate evidence, dependencies, mitigation cost, and residual risk before acting. Source note: Author-created ordinal triage aid. Scenario labels and coordinates are illustrative; they are not probability estimates, expected losses, or action recommendations." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-06-operations-and-supply-chain-how-to-apply-6", "url": "#chapter-06-operations-and-supply-chain-how-to-apply-6", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Step 1: Brainstorm Risks List all potential supply chain risks across categories: - Supplier Risks: Sole-supplier failure, quality issues, financial insolvency, labor strikes - Geopolitical Risks: Trade wars, sanctions, political instability, regulatory changes - Natural Disasters: Earthquakes, floods, hurricanes, pandemics - Logistics Risks: Port congestion, transportation delays, customs issues - Cyber Risks: Ransomware attacks on suppliers, data breaches - Demand Risks: Sudden demand spikes or drops, product obsolescence Step 2: Assess Likelihood and Impact For each scenario, use clearly anchored ordinal categories or evidence-based probability ranges; do not multiply uncalibrated ordinal scores as though they were quantities. Define impact across safety, service, finance, legal/regulatory, reputation, recovery time, and affected stakeholders. Step 3: Plot on the Matrix - High-likelihood/high-impact: Escalate for deeper analysis; urgency depends on time horizon, controls, recovery, legal/safety duties, and mitigation options. - Yellow Zone (Either High): Lower-likelihood/higher-impact scenarios may require contingency planning; higher-likelihood/lower-impact scenarios may warrant process or control improvement after exposure, cost, service, and residual-risk review. - Green Zone (Both Low): Accept and monitor the risk. Step 4: Develop Mitigation Plans For each significant risk, choose a mitigation strategy: Table 6.4. Constructed supply-chain risk mitigation options for scenario review. The options require cost, service, recovery, safety, supplier, and residual-risk analysis. | Risk Type | Mitigation Strategy | |-----------|---------------------| | Sole supplier (Red Zone) | Qualify 2nd supplier, hold safety stock, vertical integration | | Geopolitical instability | Diversify supplier geography, nearshoring | | Natural disaster | Geographic diversification, insurance, safety stock | | Transportation delays | Multi-modal logistics, local warehouses | | Cyber risk | Require supplier security audits, cyber insurance | | Quality issues | Implement supplier quality agreements, on-site inspections |" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-constructed-electronics-supply-scenario", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Constructed Electronics-Supply Scenario", "headingId": "chapter-06-operations-and-supply-chain-constructed-electronics-supply-scenario", "url": "#chapter-06-operations-and-supply-chain-constructed-electronics-supply-scenario", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A manufacturer depends on one qualified component with a long recovery time. It compares redesign, second-source qualification, supplier development, strategic inventory, contractual capacity, geographic diversification, and business-continuity options. The team models cost, qualification time, correlated failure, quality, IP, demand, and residual risk rather than claiming that any one mitigation ensures continuity." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-network-design-and-resilience-screen", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Network Design and Resilience Screen", "headingId": "chapter-06-operations-and-supply-chain-network-design-and-resilience-screen", "url": "#chapter-06-operations-and-supply-chain-network-design-and-resilience-screen", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Map supplier, plant, warehouse, route, customer, and recovery nodes; record concentration, substitutability, lead time, qualification time, and dependencies. 2. Compare total landed cost—not purchase price alone—across transport, duties, inventory, quality, labor, energy, carbon, service, disruption, and switching costs. 3. Stress-test disruption scenarios with time-to-detect, time-to-recover, service loss, liquidity, safety, contractual, and residual-risk measures. 4. Select a staged option with an owner, trigger, review date, evidence threshold, and rollback or exit path; resilience is a portfolio decision, not a matrix color." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-cone-of-uncertainty", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operator's Practical Tip: The \"Cone of Uncertainty\"", "headingId": "chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-cone-of-uncertainty", "url": "#chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-cone-of-uncertainty", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Long lead time, concentration, low visibility, correlated exposure, and slow recovery can increase vulnerability, but their effects are not captured by multiplying ordinal labels. Build scenarios with explicit probability or range evidence, time-to-detect, time-to-recover, service impact, and mitigation options." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-contrarian-thinking-resilience-costs-money-but-it-s-worth-it", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: Resilience Costs Money (But It's Worth It)", "headingId": "chapter-06-operations-and-supply-chain-contrarian-thinking-resilience-costs-money-but-it-s-worth-it", "url": "#chapter-06-operations-and-supply-chain-contrarian-thinking-resilience-costs-money-but-it-s-worth-it", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The trade-off: Resilience options can add recurring cost or complexity; compare them with scenario-specific disruption loss, liquidity, safety/service obligations, option value, and residual risk. - The decision: Compare recurring resilience cost with scenario-based disruption loss, liquidity, safety/service obligations, option value, and residual risk. Expected cost is useful only when probability and consequence estimates are decision-grade." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-06-operations-and-supply-chain-so-what-for-managers-6", "url": "#chapter-06-operations-and-supply-chain-so-what-for-managers-6", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define each disruption scenario, owner, horizon, affected service, dependencies, detectability, recovery time, and evidence before scoring it. - Use ordinal triage to prioritize deeper analysis; use calibrated probabilities or ranges when an expected-loss or investment decision requires them. - Link each material risk to a mitigation, trigger, contingency, recovery owner, review date, and residual-risk decision." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-06-operations-and-supply-chain-limits-and-critiques-6", "url": "#chapter-06-operations-and-supply-chain-limits-and-critiques-6", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ordinal likelihood and impact labels are not probabilities, expected losses, or a license to multiply scores into precise risk. - Correlated failures, tail events, changing controls, and slow recovery can dominate a simple two-axis placement. - Mitigation can add cost, supplier, cyber, quality, legal, workforce, or concentration risk; diversification is not automatically safer." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-connections-6", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-06-operations-and-supply-chain-connections-6", "url": "#chapter-06-operations-and-supply-chain-connections-6", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The matrix is informed by geopolitical analysis from your PESTLE Analysis (Chapter 3) and supplier reliability data from your Procurement team. Output: The mitigation strategies inform your Inventory Management Models (Framework 5) (e.g., justifying safety stock) and can be a key part of your overall Business Continuity Plan . ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-7-capacity-planning-model", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "7. Capacity Planning Model", "headingId": "chapter-06-operations-and-supply-chain-7-capacity-planning-model", "url": "#chapter-06-operations-and-supply-chain-7-capacity-planning-model", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Capacity Planning Resource Allocation" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-overview-7", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-06-operations-and-supply-chain-overview-7", "url": "#chapter-06-operations-and-supply-chain-overview-7", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Capacity planning compares resource options with uncertain demand, service, cost, indivisibility, ramp time, utilization/queue effects, labor, quality, and option value. Lead, lag, and match are stylized strategies, not universal prescriptions. [BB-C06-S08]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-visual-capacity-planning-strategies", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Visual: Capacity Planning Strategies", "headingId": "chapter-06-operations-and-supply-chain-visual-capacity-planning-strategies", "url": "#chapter-06-operations-and-supply-chain-visual-capacity-planning-strategies", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 6.9. Constructed capacity-strategy comparison. Lead, lag, and match describe timing choices, not guaranteed outcomes. A lead strategy creates capacity before observed demand; lag waits for stronger demand evidence; match adds capacity in increments. Each can outperform or fail depending on forecast error, queueing, ramp time, service loss, indivisibility, reversibility, and cost. [BB-C06-S08] Text equivalent: Compare the same demand scenarios against three capacity paths. Lead commits earlier and risks unused capacity; lag commits later and risks congestion or unmet demand; match stages smaller commitments but can add coordination cost and still miss abrupt changes. Choose through scenario analysis rather than a universal ranking. Source note: Author-created capacity-strategy comparison informed by capacity-expansion evidence. The strategies and paths are constructed and do not guarantee service, economics, or market outcomes. [BB-C06-S08]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-06-operations-and-supply-chain-how-to-apply-7", "url": "#chapter-06-operations-and-supply-chain-how-to-apply-7", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Step 1: Measure Current Capacity Determine the maximum theoretical output of your current resources. - Manufacturing: Units per hour, shift, or day - Service: Transactions per hour, customers served per day - Software: API requests per second, concurrent users Important: Measure effective capacity , not just theoretical. Account for: - Downtime (maintenance, changeovers) - Quality issues (scrap, rework) - Efficiency losses (breaks, training time) Step 2: Forecast Future Demand Obtain a demand forecast from Sales and Marketing teams: - Monthly or quarterly projections for the next 12-24 months - Include seasonality and growth trends - Add uncertainty bounds (best case, worst case, most likely) Step 3: Identify Capacity Gaps Constructed capacity-gap example: The following values are teaching inputs, not a benchmark or real-company result. Compare demand forecast to capacity. Create a capacity gap analysis: Step 4: Choose a Capacity Strategy LEAD Strategy: Add capacity before demand materializes - When to consider: Demand evidence is relatively strong and the service or opportunity cost of waiting is material. - Example: A constructed retailer adds seasonal capacity before demand materializes. - Pro: May protect service and capture demand if the capacity, quality, labor, and economics hold. - Con: Risky if forecast is wrong; high upfront cost LAG Strategy: Add capacity after stronger demand evidence - When to consider: Demand is uncertain, capital is constrained, or the penalty for delayed service is manageable. - Constructed example: A restaurant adds tables after sustained demand and service evidence. - Pro: Lower risk, higher asset utilization - Con: May create lost service or demand during the catch-up period. MATCH Strategy: Add capacity in smaller increments as evidence changes - When to consider: The operation can add capacity in reversible or modular increments and review frequently. - Constructed example: A digital service adds server capacity as observed demand and service thresholds change. - Pro: Balanced risk/reward - Con: Requires frequent planning cycles and flexible capacity options Step 5: Evaluate Options For a capacity shortfall, model the ROI of different options: - Overtime: Quick, flexible, but expensive per unit - Add shifts: Moderate cost, requires available labor - Outsource: May be fast, but requires service, quality, security, labor, IP, and dependency controls. - Expand facility: May offer scale, but has long lead time, capital exposure, permitting, and stranded-asset risk." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-constructed-capacity-expansion-case", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Constructed Capacity-Expansion Case", "headingId": "chapter-06-operations-and-supply-chain-constructed-capacity-expansion-case", "url": "#chapter-06-operations-and-supply-chain-constructed-capacity-expansion-case", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A manufacturer must choose among overtime, a new shift, outsourcing, modular expansion, and a large facility before demand is certain. Compare demand scenarios, ramp time, quality, labor, supply dependencies, financing, stranded-asset downside, option value, and exit/redeployment. A lead strategy can capture demand or destroy capital; the model must show both. [BB-C06-S08]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-capacity-buffer-rule", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operator's Practical Tip: The Capacity Buffer Rule", "headingId": "chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-capacity-buffer-rule", "url": "#chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-capacity-buffer-rule", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Queueing logic warns against planning at full utilization because variability causes waiting time to rise sharply as utilization approaches full load. [BB-C06-S07] - With buffer: You have room for demand spikes and maintenance. - Near full load: Disruptions such as machine breakdowns or demand spikes are more likely to cause missed deadlines and quality issues. - At full load: There is no room for error; stress rises and corners get cut." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-06-operations-and-supply-chain-so-what-for-managers-7", "url": "#chapter-06-operations-and-supply-chain-so-what-for-managers-7", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Reconcile demand scenarios with effective—not theoretical—capacity, including downtime, yield, setup, labor, quality, and service constraints. - Compare lead, lag, match, overtime, outsourcing, modular expansion, and demand-shaping options under the same scenarios and decision date. - Include financial, labor, safety, quality, supplier, reversibility, and queue effects in the capacity recommendation." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-06-operations-and-supply-chain-limits-and-critiques-7", "url": "#chapter-06-operations-and-supply-chain-limits-and-critiques-7", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Forecasts, ramp times, demand substitution, and capacity availability are uncertain; a deterministic gap table is not a demand or service forecast. - High utilization can increase waiting nonlinearly, while unused capacity can protect service, maintenance, learning, or resilience. - Capacity investments can be lumpy, slow, irreversible, and dependent on financing, skills, permits, suppliers, and future constraints." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-connections-7", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-06-operations-and-supply-chain-connections-7", "url": "#chapter-06-operations-and-supply-chain-connections-7", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires the demand forecast from your GTM Strategy (Chapter 14) . Input: The ROI calculation for a major capital investment requires a DCF model (Chapter 4) . Output: The decision to invest in new capacity is a major component of the company's Financial Forecast (Chapter 4) . ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-8-statistical-process-control-spc-charts", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "8. Statistical Process Control (SPC) Charts", "headingId": "chapter-06-operations-and-supply-chain-8-statistical-process-control-spc-charts", "url": "#chapter-06-operations-and-supply-chain-8-statistical-process-control-spc-charts", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Statistical Process Control (SPC) Quality Monitoring" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-overview-8", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-06-operations-and-supply-chain-overview-8", "url": "#chapter-06-operations-and-supply-chain-overview-8", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Statistical process control (SPC) uses time-ordered data and a chart suited to the measure and sampling design to distinguish evidence of common-cause from special-cause variation. Control limits describe process behavior under the baseline; they are not specification limits and do not establish capability, customer acceptability, causality, or safety. [BB-C06-S09]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-visual-spc-control-chart-in-control-vs-out-of-control", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Visual: SPC Control Chart (In Control vs. Out of Control)", "headingId": "chapter-06-operations-and-supply-chain-visual-spc-control-chart-in-control-vs-out-of-control", "url": "#chapter-06-operations-and-supply-chain-visual-spc-control-chart-in-control-vs-out-of-control", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 6.10. Constructed SPC signal-response loop. A pre-specified signal on a correctly chosen and validated chart triggers the response plan; it does not by itself prove a special cause, mandate a universal shutdown, or establish process capability. [BB-C06-S09] Text equivalent: Select a chart and sampling design, establish a defensible baseline, pre-specify applicable signal rules and responses, plot time-ordered data, and distinguish routine behavior from a signal. When a signal occurs, protect people or output as the context requires, verify measurement, investigate plausible causes, document the finding, and validate recovery. If a stable process is still unacceptable, redesign it rather than tampering with individual points. Source note: Author-created signal-response redraw informed by SPC interpretation guidance. The signal rules and response path are teaching synthesis and require chart- and process-specific validation. [BB-C06-S09]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-06-operations-and-supply-chain-how-to-apply-8", "url": "#chapter-06-operations-and-supply-chain-how-to-apply-8", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Step 1: Select a Critical Process Metric Choose a key quality characteristic to monitor: - Manufacturing: Product dimensions, weight, temperature, defect rate - Service: Call handle time, customer satisfaction score, delivery time - Software: Response time, error rate, uptime percentage Step 2: Establish Control Limits Collect enough representative baseline data to assess stability for the selected chart and subgroup design; no universal sample count applies. Depending on chart assumptions, estimate: - Mean (μ): Average of all baseline samples - Standard Deviation (σ): Measure of variation - Upper Control Limit (UCL): μ + 3σ - Lower Control Limit (LCL): μ - 3σ Three-sigma limits are a common Shewhart convention, but calculation and interpretation depend on chart type, subgrouping, distribution, autocorrelation, measurement quality, and the run rules chosen. A signal prompts investigation; it does not prove a cause. [BB-C06-S09] Step 3: Plot Data Over Time Continuously plot samples of your process metric on the chart. Update daily, hourly, or in real-time depending on the process. Step 4: Interpret the Signals In Control (Common Cause Variation): - All points are within UCL and LCL - Points are randomly distributed (no patterns) - Action: Avoid reacting to individual routine points as special causes. If capability, safety, service, or economics are unacceptable, redesign the system using an appropriate improvement method. Signal requiring investigation: A pre-specified chart rule, data-quality concern, or relevant specification/safety signal requires investigation; it is not a confirmed special cause. 1. Point outside selected limits: Investigate after checking the chart, data, measurement system, and applicable limits. 2. Run or trend rule: Use only a rule selected for the chart, subgroup, distribution, and operating decision; do not assume seven points is universal. 3. Cyclic or patterned behavior: Investigate when the pattern is relevant to the sampling interval and process mechanism. 4. Sudden shift: Check data integrity, measurement changes, process changes, and plausible causes before adjusting the process." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-measurement-and-capability-check", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Measurement and Capability Check", "headingId": "chapter-06-operations-and-supply-chain-measurement-and-capability-check", "url": "#chapter-06-operations-and-supply-chain-measurement-and-capability-check", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Verify calibration, repeatability/reproducibility or classification agreement, sampling, data integrity, and subgroup logic before interpreting a signal or capability result. - Define the customer, engineering, regulatory, or safety specifications separately from control limits. For a stable continuous process with defensible assumptions, capability indices can be calculated as Cp = (USL − LSL) / (6σ) and Cpk = min((USL − mean) / (3σ), (mean − LSL) / (3σ)) ; otherwise report observed nonconformance, percentiles, and uncertainty instead of forcing an index. [BB-C06-S09] - Treat capability as conditional on the measurement system, stability, distribution, specification, and sampling plan; a capability number does not prove customer acceptability or safety." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-constructed-spc-investigation", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Constructed SPC Investigation", "headingId": "chapter-06-operations-and-supply-chain-constructed-spc-investigation", "url": "#chapter-06-operations-and-supply-chain-constructed-spc-investigation", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A dimensional chart shows a pre-specified run-rule signal before measurements cross the engineering specification. The owner follows the response plan, protects potentially affected material, verifies the measurement system, investigates equipment and material changes, documents the cause, and validates recovery. Control limits and specification limits remain distinct. [BB-C06-S09]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-operator-s-critical-mistake-tampering", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operator's Critical Mistake: \"Tampering\"", "headingId": "chapter-06-operations-and-supply-chain-operator-s-critical-mistake-tampering", "url": "#chapter-06-operations-and-supply-chain-operator-s-critical-mistake-tampering", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Problem: Many operators see normal variation and overreact, constantly adjusting the process. - Example: Widget weight varies between 98g and 102g (within control limits). Operator sees 98g and increases material. Next part is 104g (out of spec). Operator decreases material. Next is 96g. The operator's adjustments are making things worse! - The Solution: Do not adjust a stable process in response to individual routine points. Improve an incapable or harmful stable process through designed system change, then establish and validate a new baseline." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-the-four-types-of-spc-charts", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "The Four Types of SPC Charts", "headingId": "chapter-06-operations-and-supply-chain-the-four-types-of-spc-charts", "url": "#chapter-06-operations-and-supply-chain-the-four-types-of-spc-charts", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 6.5. Constructed common SPC chart candidates. Selection also depends on sampling, subgroup logic, opportunity or exposure, distributional assumptions, independence, measurement quality, and the response plan. [BB-C06-S09] | Chart candidate | Data and sampling context | Verify before use | | :--- | :--- | :--- | | X-bar and R | Continuous measurements in rational subgroups | Subgroup rationale, size, range assumptions, measurement resolution, and independence | | Individuals and moving range | Continuous observations collected one at a time | Time order, autocorrelation, moving-range interpretation, and measurement stability | | p-chart | Proportion nonconforming from binary classifications | Denominator/sample size, classification accuracy, varying limits, and independence | | c-chart | Count of nonconformities with constant opportunity or inspection area | Exposure constancy, count assumptions, inspection consistency, and whether a u-chart is more suitable |" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-contrarian-thinking-spc-can-t-fix-a-bad-process", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: SPC Can't Fix a Bad Process", "headingId": "chapter-06-operations-and-supply-chain-contrarian-thinking-spc-can-t-fix-a-bad-process", "url": "#chapter-06-operations-and-supply-chain-contrarian-thinking-spc-can-t-fix-a-bad-process", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The Mistake: Putting SPC charts on a fundamentally flawed process. - The Reality: SPC tells you when a process has changed, but it doesn't tell you how to improve the process. If your process is \"in control\" at a 15% defect rate, SPC will just tell you \"Yes, you're consistently producing 15% defects.\" - The Fix: Use Six Sigma DMAIC (Framework 3) to improve the process first, then use SPC to hold the gains." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-06-operations-and-supply-chain-so-what-for-managers-8", "url": "#chapter-06-operations-and-supply-chain-so-what-for-managers-8", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Select a chart and sampling design that match the measure, subgroup, opportunity, distribution, independence, and response decision. - Establish a defensible baseline, pre-specify signal rules, verify the measurement system, and document the investigation response. - Distinguish common-cause stability from capability, specifications, customer acceptability, and safety before deciding to hold or change the process." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-06-operations-and-supply-chain-limits-and-critiques-8", "url": "#chapter-06-operations-and-supply-chain-limits-and-critiques-8", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Control limits describe baseline process behavior; they are not specification limits, safety thresholds, or proof of capability. - A signal prompts investigation but does not prove a cause; autocorrelation, subgrouping, classification, and measurement error can mislead. - SPC can monitor a bad process consistently; redesign, DMAIC, engineering, or containment may be needed instead of tampering with routine points." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-connections-8", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-06-operations-and-supply-chain-connections-8", "url": "#chapter-06-operations-and-supply-chain-connections-8", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The metric to be controlled is often a \"Critical to Quality\" (CTQ) characteristic identified during a Six Sigma DMAIC (Framework 3) project. Output: SPC charts are the core tool used in the \"Control\" phase of Six Sigma to ensure that process improvements are sustained over time. ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-9-value-stream-mapping", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "9. Value Stream Mapping", "headingId": "chapter-06-operations-and-supply-chain-9-value-stream-mapping", "url": "#chapter-06-operations-and-supply-chain-9-value-stream-mapping", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Value Stream Mapping (VSM) End-to-End Process Optimization" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-overview-9", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-06-operations-and-supply-chain-overview-9", "url": "#chapter-06-operations-and-supply-chain-overview-9", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Value Stream Mapping (VSM) records the material and information flow required to bring a product or service to a customer, beyond the steps shown in a process-flow diagram. It helps a team distinguish value-creating from non-value-creating activities and use a current-state map to design a leaner future state. [BB-C06-S10]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-visual-value-stream-map-example", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Visual: Value Stream Map Example", "headingId": "chapter-06-operations-and-supply-chain-visual-value-stream-map-example", "url": "#chapter-06-operations-and-supply-chain-visual-value-stream-map-example", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 6.11. Constructed current-state value-stream map. Cycle and queue times are teaching inputs, not a benchmark or named-factory result. The arithmetic declares the listed process time as a process-time input; it does not classify that time as customer value unless a real team separately defines the clock, states, demand, quality, rework, and customer value. [BB-C06-S10] Text equivalent: Production control receives customer demand, sends a supplier order and a daily schedule, and receives status from the flow. Material moves through stamping, welding, painting, and assembly with illustrative cycle times of 30, 45, 60, and 90 seconds. Illustrative queues of 5, 3, 4, and 2 days create 14 days of lead time versus 3.75 minutes of listed process time. The discrepancy is a diagnostic prompt, not proof that all unlisted time is removable waste. Source note: Author-created current-state redraw informed by VSM practice. The process, timings, queues, and ratio are constructed teaching inputs and not a factory benchmark. [BB-C06-S10]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-06-operations-and-supply-chain-how-to-apply-9", "url": "#chapter-06-operations-and-supply-chain-how-to-apply-9", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Step 1: Map the Current State Walk the entire process (\"Gemba\") from start to finish. Document for each step: - Cycle Time (C/T): How long the actual work takes; do not equate processing time with customer value without a separate classification. - Uptime %: Equipment availability - Changeover Time: Time to switch between products - Batch Size: How many units are processed together - Defect Rate: Percentage of defective outputs - Number of Operators: Labor required - Wait Time: Time between this step and the next; classify its customer, safety, quality, and process role separately Step 2: Compare observed work time with elapsed lead time Use a process-time ratio only as a diagnostic: it is sum of observed processing time / total elapsed lead time , not a value-added ratio unless the team separately defines customer value, required work, quality, safety, regulatory, and learning requirements. - Constructed example: (30 sec + 45 sec + 60 sec + 90 sec) / 14 days = 3.75 min / 20,160 min = 0.02% of elapsed time. This does not establish that all processing time creates customer value or that all waiting is removable. - Author synthesis: Interpret the ratio within the local process boundary, demand, quality, safety, customer, and service evidence rather than applying a universal benchmark. [BB-C06-S10] Step 3: Design the Future State The goal is to reduce avoidable waiting where customer value, system economics, safety, quality, workforce, supplier, and resilience evidence support the change: - Create Continuous Flow: Can steps be physically moved closer together so work flows directly from one to the next without waiting? - Implement Pull Systems: Use Kanban to ensure each step only produces what the next step needs, when it needs it - Reduce Batch Sizes: Smaller batches mean less WIP inventory and faster flow - Eliminate Bottlenecks: Apply Theory of Constraints to address the limiting step Constructed target: Test whether the illustrative 14-day lead time can be reduced by changing WIP, batches, flow, and handoffs; do not assume a 2–3 day target or that all WIP is removable. Step 4: Create an Implementation Plan Break the transformation into actionable Kaizen events: - Kaizen Event 1: Test whether rearranging Stamp and Weld reduces WIP or waiting under explicit safety, quality, service, and flow guardrails. - Kaizen Event 2: Implement Kanban between Weld and Paint (reduce batch sizes) - Kaizen Event 3: Cross-train operators to balance workload - Timeline: One Kaizen event per month for 6 months" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-sourced-practice-context-toyota-s-process-logic", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Sourced Practice Context: Toyota's Process Logic", "headingId": "chapter-06-operations-and-supply-chain-sourced-practice-context-toyota-s-process-logic", "url": "#chapter-06-operations-and-supply-chain-sourced-practice-context-toyota-s-process-logic", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "In Womack's retrospective, Toyota's production-system development combined machines sized for actual volume, built-in quality checks, process-sequence layout, quick changeovers, and signals from downstream steps to upstream steps. This is an author interpretation of operating-system development, not proof that copying individual tools will produce the same cost, variety, quality, or throughput outcomes in another setting. [BB-C06-S02]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-operator-s-critical-insight-lead-time-is-the-new-currency", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operator's Critical Insight: \"Lead Time is the New Currency\"", "headingId": "chapter-06-operations-and-supply-chain-operator-s-critical-insight-lead-time-is-the-new-currency", "url": "#chapter-06-operations-and-supply-chain-operator-s-critical-insight-lead-time-is-the-new-currency", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "In traditional operations, managers focus on: - Machine utilization (keep machines busy) - Labor efficiency (minimize direct labor cost per unit) VSM can show when these metrics are counterproductive under the stated demand and flow conditions: - High utilization can increase WIP: Keeping machines \"busy\" can create overproduction and downstream waiting when release is not synchronized with demand. - Large batches can lengthen lead times: Producing in big batches may increase local efficiency while increasing WIP and customer wait. The decision focus: Reduce avoidable lead time when doing so improves customer value and system economics without harming safety, quality, workforce, supplier, or resilience outcomes. Inventory, cash, and responsiveness are hypotheses to measure, not automatic effects. [BB-C06-S10]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-06-operations-and-supply-chain-so-what-for-managers-9", "url": "#chapter-06-operations-and-supply-chain-so-what-for-managers-9", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Map material and information flow with actual demand, takt, WIP, cycle time, queue time, quality, rework, and customer-value definitions. - Use the current state to test improvement hypotheses and the future state to assign owners, controls, measures, and staged experiments. - Track lead time, WIP, service, quality, cash, workforce, supplier, and resilience effects rather than optimizing value-added ratio alone." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-06-operations-and-supply-chain-limits-and-critiques-9", "url": "#chapter-06-operations-and-supply-chain-limits-and-critiques-9", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Value-added classifications depend on the customer, process boundary, regulatory work, safety, quality, and learning requirements. - Author synthesis: A low process-time ratio is a diagnostic prompt, not a universal benchmark or proof that all waiting can be removed. [BB-C06-S10] - A VSM does not establish causality or guarantee improvement; implementation, measurement, ownership, and system interactions determine outcomes." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-connections-9", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-06-operations-and-supply-chain-connections-9", "url": "#chapter-06-operations-and-supply-chain-connections-9", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: A VSM is a more advanced version of a Process Flow Diagram (Framework 1) , adding data on wait times and information flows. Output: The future state map provides a detailed project plan for a Lean (Framework 2) transformation initiative. ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-10-digital-twin-architecture", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "10. Digital Twin Architecture", "headingId": "chapter-06-operations-and-supply-chain-10-digital-twin-architecture", "url": "#chapter-06-operations-and-supply-chain-10-digital-twin-architecture", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Digital Twin Architecture Simulation & Predictive Optimization" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-overview-10", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-06-operations-and-supply-chain-overview-10", "url": "#chapter-06-operations-and-supply-chain-overview-10", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A digital twin is a purpose-defined digital representation linked to a physical asset, process, or system across an identified lifecycle. ISO 23247-1 provides public metadata for terms, definitions, general principles, and requirements for a manufacturing digital-twin framework; it does not make the teaching architecture below an ISO reference architecture. A twin can support monitoring, simulation, or prediction, but fidelity, configuration, latency, measurement, uncertainty, security, human authority, and change control determine whether an output is fit for use. [BB-C06-S12]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-visual-digital-twin-architecture", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Visual: Digital Twin Architecture", "headingId": "chapter-06-operations-and-supply-chain-visual-digital-twin-architecture", "url": "#chapter-06-operations-and-supply-chain-visual-digital-twin-architecture", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 6.12. Constructed digital-twin component architecture. Data does not flow directly into an autonomous operating change: configuration, validation, uncertainty, safety, security, authorization, and rollback govern the loop. [BB-C06-S12] Text equivalent: A physical asset or process produces sensor data that update a digital representation. Analytics may generate a failure-risk estimate, tested operating option, or other model output. Accountable owners must validate the data, model, uncertainty, safety, security, and operating guardrails before feeding any change back to the physical system. Source note: Author-created teaching sketch informed by the locally cited digital-twin literature. ISO 23247-1 supports the existence and scope of a manufacturing digital-twin framework, not this exact architecture or its arrows. [BB-C06-S12]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-06-operations-and-supply-chain-how-to-apply-10", "url": "#chapter-06-operations-and-supply-chain-how-to-apply-10", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Step 1: Build the Virtual Model Define the decision and required fidelity before building the model: - Manufacturing Line: Model each machine, buffer, conveyor, and constraint - Product: Model the product's behavior under different conditions (temperature, stress, etc.) - Supply Chain: Model inventory levels, transportation routes, supplier lead times Tool boundary: Select tools only after architecture, validation, security, interoperability, ownership, and lifecycle requirements are defined. Step 2: Integrate Real-Time Data Integrate the physical, transactional, event, or sensor data needed for the named decision; a sensor-heavy design is one option, not a default: - Sensor Types: Temperature, vibration, pressure, flow rate, GPS location, power consumption, throughput - Data Frequency: Match sampling, latency, storage, and synchronization to the physics and decision; faster is not automatically better. - Constructed architecture option: Sensors → edge or local processing → cloud or on-premise representation → analytics and control interface. Select the deployment from latency, safety, security, interoperability, cost, and ownership requirements. Step 3: Simulate & Optimize Use the digital twin to run bounded “what-if” scenarios without treating simulation as real-world validation: Manufacturing Examples: - \"What happens if we increase production line speed by 10%?\" - \"If Machine B goes down, where will the bottleneck shift?\" - \"What's the optimal preventive maintenance schedule to minimize downtime?\" Supply Chain Examples: - \"If a high-concentration supplier becomes unavailable, what is the impact on service and recovery?\" - \"What inventory levels minimize total cost (holding + stockout)?\" Step 4: Validate, Decide, and Control Change Validate the model for the intended decision, quantify uncertainty and failure modes, and keep accountable human authority over consequential operating changes. Predictive Maintenance: - Old approach: Fix machines when they break (reactive) or on a fixed schedule (preventive) - Digital-twin approach: Analyze relevant condition and use data to estimate failure risk within a validated horizon. - Decision: Compare inspection, maintenance, continued operation, shutdown, and evidence collection under safety and reliability rules. Prescriptive Optimization: - Example: The model compares bounded parameter combinations, then a controlled real-world test validates performance, energy, safety, quality, and equipment-life guardrails. Figure 6.13. Governed digital-twin decision loop. Physical data can update a digital representation, but validation, uncertainty, security, human approval, staged change, and rollback sit between a model output and an operating action. Text equivalent: Sensor and operating data update a versioned digital representation. Simulation produces a prediction or option, which must pass fidelity, uncertainty, safety, and security validation. An authorized owner either stages the change with monitoring and rollback or rejects, redesigns, or gathers more evidence. Source note: Author-created governance extension of the digital-twin concept. ISO 23247-1 is linked only for the published manufacturing-framework scope; it does not define this governance loop. [BB-C06-S12]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-constructed-condition-monitoring-example", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Constructed Condition-Monitoring Example", "headingId": "chapter-06-operations-and-supply-chain-constructed-condition-monitoring-example", "url": "#chapter-06-operations-and-supply-chain-constructed-condition-monitoring-example", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A regulated asset operator uses a versioned digital representation to compare maintenance options. It validates sensor calibration, failure labels, prediction horizon, false-negative consequences, configuration, cybersecurity, human authority, and rollback before changing a maintenance plan. The example is illustrative and makes no claim about a named engine maker, sensor count, data volume, prediction, or savings." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-constructed-scope-taxonomy", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Constructed Scope Taxonomy", "headingId": "chapter-06-operations-and-supply-chain-constructed-scope-taxonomy", "url": "#chapter-06-operations-and-supply-chain-constructed-scope-taxonomy", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The four labels below are an author-created teaching taxonomy, not a universal or standards-defined classification. Table 6.6. Constructed digital-representation scope taxonomy. Actual terminology and scope must follow the governing standard, architecture, and use case. | Teaching label | Candidate scope | Example decision use | Key boundary | | :--- | :--- | :--- | :--- | | Component representation | One part or subassembly | Condition monitoring or inspection timing | Component behavior may depend on asset and operating context | | Asset representation | One machine or physical asset | Maintenance, operating envelope, or performance option | Requires configuration, degradation, environment, and failure-mode evidence | | System representation | Interacting assets | Flow, bottleneck, reliability, or scenario analysis | Interfaces and emergent behavior can dominate component accuracy | | Process representation | End-to-end workflow or network | Capacity, inventory, service, or recovery planning | Organizational, policy, supplier, and human behavior may not be captured by physical models | Text equivalent: The teaching taxonomy distinguishes a component representation for one part, an asset representation for one machine, a system representation for interacting assets, and a process representation for an end-to-end workflow. Actual terminology and scope must follow the governing standard, architecture, and use case." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-operator-s-practical-tip-start-small", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Operator's Practical Tip: Start Small", "headingId": "chapter-06-operations-and-supply-chain-operator-s-practical-tip-start-small", "url": "#chapter-06-operations-and-supply-chain-operator-s-practical-tip-start-small", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Don't try to build a digital twin of your entire operation on day 1. Start with: 1. Name the decision and owner: Define what action the representation may inform. 2. Choose a bounded scope: Select an asset or process where better evidence could change a material decision. 3. Validate value and risk: Compare the twin with simpler sensing, rules, simulation, inspection, or process-change alternatives. 4. Expand only with evidence: Require validated performance, lifecycle cost, interoperability, security, adoption, and residual-risk evidence." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-contrarian-thinking-don-t-twin-everything", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: Don't Twin Everything", "headingId": "chapter-06-operations-and-supply-chain-contrarian-thinking-don-t-twin-everything", "url": "#chapter-06-operations-and-supply-chain-contrarian-thinking-don-t-twin-everything", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The Hype: Digital twin vendors will tell you to twin everything. - The decision: A digital twin may be useful for: - High-value assets: Assets where downtime is extremely costly (e.g., jet engines, manufacturing lines) - Complex processes: Where simulation provides insights humans can't easily see - Regulated industries: Where you need to prove compliance (pharmaceuticals, aerospace) - Prefer simpler methods: When observation, SPC, rules, conventional simulation, or process redesign provides sufficient evidence at lower lifecycle cost and risk." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-real-world-implementation-challenges", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Real-World Implementation Challenges", "headingId": "chapter-06-operations-and-supply-chain-real-world-implementation-challenges", "url": "#chapter-06-operations-and-supply-chain-real-world-implementation-challenges", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Data quality: \"Garbage in, garbage out.\" If your sensors are miscalibrated or your data is noisy, the twin will give bad predictions. - Model fidelity: Building an accurate virtual model is hard. It requires deep process knowledge and iterative refinement. - Change management: Operators must trust the twin's recommendations. This requires training and proving the twin's accuracy over time. - Lifecycle economics: Include sensing, integration, validation, compute, security, model/configuration updates, people, downtime, vendor dependence, and retirement; do not use a universal cost range." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-06-operations-and-supply-chain-so-what-for-managers-10", "url": "#chapter-06-operations-and-supply-chain-so-what-for-managers-10", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Name the decision, owner, scope, lifecycle, fidelity, data requirements, security boundary, and rollback condition before building a twin. - Validate data, configuration, model performance, uncertainty, safety, cyber controls, and human authority before staging an operating change. - Compare a twin with simpler sensing, rules, SPC, simulation, inspection, or process redesign and expand only when evidence justifies lifecycle cost." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-06-operations-and-supply-chain-limits-and-critiques-10", "url": "#chapter-06-operations-and-supply-chain-limits-and-critiques-10", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- ISO 23247-1 provides a manufacturing framework scope; it does not validate this chapter's architecture, arrows, predictions, safety, security, or economic value. - Fidelity, latency, data quality, configuration drift, model error, cyber exposure, adoption, and retirement cost can dominate technical promise. - A digital representation cannot replace physical evidence, approved controls, accountable authority, or a monitored rollback path." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-connections-10", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-06-operations-and-supply-chain-connections-10", "url": "#chapter-06-operations-and-supply-chain-connections-10", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The creation of a digital twin requires a detailed Process Flow Diagram (Framework 1) and data from Operations . Output: Validated insights may inform capacity and SPC decisions; the twin does not replace physical evidence, approved control plans, or accountable operating authority. ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-forecasting-and-s-op-converting-uncertainty-into-an-executable-plan", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Forecasting and S&OP: Converting Uncertainty into an Executable Plan", "headingId": "chapter-06-operations-and-supply-chain-forecasting-and-s-op-converting-uncertainty-into-an-executable-plan", "url": "#chapter-06-operations-and-supply-chain-forecasting-and-s-op-converting-uncertainty-into-an-executable-plan", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A forecast is a conditional estimate, not a commitment. A plan is an authorized choice about demand shaping, supply, inventory, capacity, sourcing, backlog, cash, and risk. Sales and Operations Planning (S&OP) is the recurring management process that reconciles those objects into one controlled set of tactical decisions. APICS describes S&OP as integrating customer-focused marketing with sales, development, manufacturing, sourcing, supply-chain, and financial plans; a literature synthesis frames it as a coordination problem rather than only a meeting calendar. [BB-C06-S15] [BB-C06-S16]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-forecast-for-the-decision-and-horizon", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Forecast for the decision and horizon", "headingId": "chapter-06-operations-and-supply-chain-forecast-for-the-decision-and-horizon", "url": "#chapter-06-operations-and-supply-chain-forecast-for-the-decision-and-horizon", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define the object: SKU, family, service, customer segment, location, channel, time bucket, unit, and forecast horizon. The aggregation level must match the capacity, inventory, procurement, and financial decision. 2. Separate baseline, events, and scenarios: Preserve an auditable statistical baseline; add known events with owners and evidence; represent uncertain launches, promotions, disruptions, and competitor actions as scenarios rather than hiding them in one consensus number. 3. Evaluate genuine forecasts: Training residuals are not forecast errors. Test on later observations or use rolling-origin time-series cross-validation so future information cannot leak into model selection. Compare with a transparent naïve or seasonal-naïve benchmark. [BB-C06-S13] 4. Measure more than one failure mode: Track signed error for bias, MAE or a suitable scale-free measure for magnitude, and interval/quantile performance when asymmetric service or shortage costs matter. Percentage measures become unstable near zero; aggregate metrics can hide item, horizon, segment, or directional failure. [BB-C06-S13] 5. Prefer validated performance to complexity theater: The M4 competition evaluated 61 methods across 100,000 series and both point and interval forecasts; it demonstrates the value of large out-of-sample comparisons, not a universal winning algorithm for a focal business. [BB-C06-S14] Forecast-error definitions for the exercise: - Error = Actual − Forecast. Positive total error indicates net underforecasting under this sign convention. - MAE = mean of absolute errors. - WAPE in this constructed exercise = sum of absolute errors ÷ sum of actuals. This ratio is easy to explain but can conceal mix and timing and is unusable when its aggregate denominator is not meaningful." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-the-closed-s-op-loop", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "The closed S&OP loop", "headingId": "chapter-06-operations-and-supply-chain-the-closed-s-op-loop", "url": "#chapter-06-operations-and-supply-chain-the-closed-s-op-loop", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 6.14. Constructed closed-loop S&OP decision cycle. The sequence integrates demand, supply, product, finance, risk, executive decisions, execution, and learning. It is an original synthesis, not a claim that every organization requires the same meeting design. [BB-C06-S15] [BB-C06-S16] Text equivalent: Prepare data and assumptions; review the unconstrained demand baseline and scenarios; review supply, inventory, capacity, sourcing, quality, and workforce constraints; reconcile product, commercial, operational, financial, service, and risk alternatives; obtain executive decisions and contingency triggers; translate the authorized aggregate plan into detailed schedules and controls; compare actuals with forecast and plan; then feed error, service, cost, and risk evidence into the next cycle. Source note: Original managerial synthesis informed by S&OP coordination and planning sources. The stages and decision rights are constructed and do not imply that every organization uses this meeting design. [BB-C06-S15] [BB-C06-S16]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-decision-rights-and-minimum-outputs", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Decision rights and minimum outputs", "headingId": "chapter-06-operations-and-supply-chain-decision-rights-and-minimum-outputs", "url": "#chapter-06-operations-and-supply-chain-decision-rights-and-minimum-outputs", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 6.7. Constructed S&OP decision rights and minimum outputs. The rows are a managerial synthesis, not a universal meeting design. | Review | Question | Minimum output | | :--- | :--- | :--- | | Data and portfolio | What changed in actuals, master data, lifecycle, promotions, assumptions, and prior decisions? | Reconciled inputs, data-quality exceptions, open actions, and version history | | Demand | What is the unconstrained baseline, uncertainty, event evidence, and demand-shaping option? | Baseline plus scenarios, bias/error by horizon and segment, assumptions, owner | | Supply | What can be delivered safely and reliably under current and option capacity? | Constraint and recovery evidence; inventory, capacity, supplier, workforce, quality, and service alternatives | | Reconciliation | Which alternatives best meet strategy after margin, cash, capital, service, workforce, and risk? | Comparable scenarios, financial bridge, residual risk, escalation, recommendation | | Executive | What will the enterprise commit, defer, shape, source, invest, or stop? | Authorized aggregate plan, decision log, owners, thresholds, contingencies, unresolved dissent | | Execution and learning | Did detailed schedules follow the authorized plan and what changed? | Plan adherence, service, cost, inventory, cash, forecast/plan error, causes, corrective decisions |" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-constructed-forecast-error-and-constrained-plan-exercise", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Constructed forecast-error and constrained-plan exercise", "headingId": "chapter-06-operations-and-supply-chain-constructed-forecast-error-and-constrained-plan-exercise", "url": "#chapter-06-operations-and-supply-chain-constructed-forecast-error-and-constrained-plan-exercise", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following data are teaching inputs, not a benchmark or real-company result. Table 6.8. Constructed six-period forecast-error exercise. Error definitions and values are teaching inputs; they are not a forecast-performance benchmark. | Period | Actual units | Forecast units | Error: actual − forecast | Absolute error | | :--- | ---: | ---: | ---: | ---: | | 1 | 100 | 110 | -10 | 10 | | 2 | 120 | 100 | 20 | 20 | | 3 | 80 | 90 | -10 | 10 | | 4 | 140 | 130 | 10 | 10 | | 5 | 110 | 120 | -10 | 10 | | 6 | 150 | 140 | 10 | 10 | | Total or mean | 700 | 690 | 10 total; 1.67 mean | 70 total; MAE 11.67 | Constructed WAPE is 70 ÷ 700 = 10% . The positive mean error indicates modest net underforecasting under the declared sign convention, but alternating errors show that the aggregate bias alone is not sufficient. Inspect product, customer, location, event, and horizon errors and compare the method with a naïve benchmark before changing the forecast process. [BB-C06-S13] For the next period, the unconstrained forecast is 120 units of A and 80 of B. Shared qualified capacity is 160 units; B also has a material limit of 70. Illustrative unit contribution is $40 for A and $60 for B. Commercial commitments request at least 100 A and 60 B. Table 6.9. Constructed constrained-plan alternatives. The contributions and service tensions are illustrative and require local cost, contract, quality, labor, and risk checks. | Candidate plan | A units | B units | Capacity used | Unserved forecast | Illustrative contribution | Decision tension | | :--- | ---: | ---: | ---: | :--- | ---: | :--- | | Maximize stated unit contribution | 90 | 70 | 160 | A 30; B 10 | $7,800 | Misses the requested A minimum; may harm service or contracts | | Meet stated minimum commitments | 100 | 60 | 160 | A 20; B 20 | $7,600 | Gives up $200 of modeled contribution to meet the declared mix | | Reserve 10 units of protective capacity | 90 | 60 | 150 | A 30; B 20 | $7,200 | Preserves flexibility but needs an explicit trigger and cost justification | Exercise decision: Recommend one plan only after checking whether contribution includes all avoidable cost, whether service minima are contractual or strategic, whether products consume equal constraint time, whether substitution/backlog is feasible, and whether quality, safety, labor, supplier, cash, and customer risks alter the ranking. Record the rejected alternatives, trigger for using reserved capacity, demand-shaping option, owner, and next review date. Use Chapter 4 for the financial bridge and Chapter 5 for demand evidence. ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-mental-model-1-systems-have-constraints-toc", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 1: Systems Have Constraints (TOC)", "headingId": "chapter-06-operations-and-supply-chain-mental-model-1-systems-have-constraints-toc", "url": "#chapter-06-operations-and-supply-chain-mental-model-1-systems-have-constraints-toc", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Theory of Constraints directs attention to the current factor limiting a defined system goal. Constraints can be physical, demand, policy, skill, information, or risk related; multiple and shifting constraints can exist across products and horizons. Improve system flow while preserving independent safety, quality, maintenance, and risk value. [BB-C06-S03] [BB-C06-S04]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-mental-model-2-waste-is-everywhere-lean", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 2: Waste is Everywhere (Lean)", "headingId": "chapter-06-operations-and-supply-chain-mental-model-2-waste-is-everywhere-lean", "url": "#chapter-06-operations-and-supply-chain-mental-model-2-waste-is-everywhere-lean", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Lean asks managers to examine activity, flow, and customer value rather than maximizing local busy time. Waste categories prompt investigation; safety, quality, resilience, accessibility, learning, and respect for people can justify capacity or activity that a narrow map might label non-value-added. [BB-C06-S01] [BB-C06-S02]" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-mental-model-3-interpret-variation-before-acting-six-sigma", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 3: Interpret Variation Before Acting (Six Sigma)", "headingId": "chapter-06-operations-and-supply-chain-mental-model-3-interpret-variation-before-acting-six-sigma", "url": "#chapter-06-operations-and-supply-chain-mental-model-3-interpret-variation-before-acting-six-sigma", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Variation can create defects or unpredictability when it moves a stable process away from customer, engineering, or safety requirements. First establish measurement quality, stability, and capability; then reduce harmful variation without suppressing necessary exploration, personalization, or learning. [BB-C06-S06] [BB-C06-S09] ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-example-1-responsive-apparel-network", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Example 1: Responsive Apparel Network", "headingId": "chapter-06-operations-and-supply-chain-example-1-responsive-apparel-network", "url": "#chapter-06-operations-and-supply-chain-example-1-responsive-apparel-network", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "An apparel company compares low-cost long-lead production with smaller, faster regional batches. It models demand forecast error, markdowns, unit cost, capacity, supplier/labor conditions, cash, emissions, quality, and service. Speed creates value only when the avoided uncertainty and service benefit exceed the incremental cost and risk." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-example-2-marketplace-fulfillment-loop", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Example 2: Marketplace Fulfillment Loop", "headingId": "chapter-06-operations-and-supply-chain-example-2-marketplace-fulfillment-loop", "url": "#chapter-06-operations-and-supply-chain-example-2-marketplace-fulfillment-loop", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A constructed marketplace tests whether more demand attracts supply, improves density, lowers fulfillment cost, and enables a better offer. Each arrow is a hypothesis: congestion, service failures, worker/provider economics, capital intensity, multi-homing, and competition can weaken or reverse it. Use Chapter 18 for platform governance and network effects. ---" }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-applied-exercise-diagnose-and-improve-an-operating-system", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Applied Exercise: Diagnose and Improve an Operating System", "headingId": "chapter-06-operations-and-supply-chain-applied-exercise-diagnose-and-improve-an-operating-system", "url": "#chapter-06-operations-and-supply-chain-applied-exercise-diagnose-and-improve-an-operating-system", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Using a constructed month of order, queue, defect, downtime, inventory, capacity, and supplier data, define the process boundary; reconcile WIP = Throughput × Flow Time ; identify two competing constraint diagnoses; distinguish stability from capability; compare inventory, capacity, and supplier-risk options; and propose one staged intervention. Deliver a current-state map, calculations, assumptions, safety/service/workforce controls, financial impact, owner, measurement plan, and stop, redesign, or scale rule. Table 6.10. Constructed operating-system exercise dataset. The values are teaching inputs, not a benchmark or real-company result; the exercise requires the learner to state units, boundaries, assumptions, and data-quality checks. | Evidence stream | Constructed input | Question to test | | :--- | :--- | :--- | | Orders and flow | 720 orders received; 690 shipped; average WIP 120 orders; average throughput 30 orders/day | What is the flow-time implication, and is backlog caused by capacity, policy, mix, quality, or demand? | | Quality | 36 defects recorded from 720 orders; defect definition and measurement agreement require validation | Is the process stable, capable of the stated requirement, or measured inconsistently? | | Capacity and downtime | 160 qualified units/day theoretical; 18 planned maintenance hours and 6 unplanned downtime hours in the month | Which loss is a constraint, and what service, safety, labor, or quality trade-offs follow from recovery options? | | Inventory | 700 units of monthly demand; 180 units on hand; supplier lead time 5–9 days; no service target pre-specified | What reorder/protection policy follows from demand and lead-time variability, shortage cost, perishability, and cash? | | Supplier risk | Primary supplier on-time rate 82%; second-source qualification takes 14 days; disruption recovery estimate 21 days | Compare inventory, qualification, capacity, contract, redesign, and geographic options using recovery and residual-risk evidence. | Exercise prompts: Calculate flow time using the stated WIP and throughput, define the quality measure and specification, test two competing constraint hypotheses, compare a protection policy with a capacity or supplier option, and recommend one staged intervention. Record the evidence that would change the decision, the owner, the monitoring plan, and the stop/redesign/scale trigger." }, { "id": "chapter-06-operations-and-supply-chain::chapter-06-operations-and-supply-chain-selective-connections", "kind": "chapter", "itemSlug": "chapter-06-operations-and-supply-chain", "itemTitle": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "heading": "Selective Connections", "headingId": "chapter-06-operations-and-supply-chain-selective-connections", "url": "#chapter-06-operations-and-supply-chain-selective-connections", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use Chapter 4 for working capital, capital investment, and downside liquidity. - Use Chapter 5 for demand, service, and customer-evidence methods. - Use Chapter 9 for competing diagnoses and assumption maps. - Use Chapter 11 for implementation governance and change control. - Use Chapter 19 for connected-operations and supplier cyber risk. - Use Chapter 22 for causal analysis, uncertainty, and simulation interpretation. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Organizational Behavior and Leadership", "headingId": "chapter-07-organizational-behavior-and-leadership", "url": "#chapter-07-organizational-behavior-and-leadership", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-executive-summary", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Executive Summary", "headingId": "chapter-07-organizational-behavior-and-leadership-executive-summary", "url": "#chapter-07-organizational-behavior-and-leadership-executive-summary", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter provides a manager's toolkit for the human side of the business. It treats change, team dynamics, culture, feedback, talent, motivation, conflict, organization design, and psychological safety as evidence-informed lenses—not guarantees of performance. Use them to formulate, test, and review bounded interventions with affected-party voice, safeguards, and escalation." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-manager-decision-outcomes", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Manager decision outcomes", "headingId": "chapter-07-organizational-behavior-and-leadership-manager-decision-outcomes", "url": "#chapter-07-organizational-behavior-and-leadership-manager-decision-outcomes", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "By the end of this chapter, a manager should be able to: 1. Diagnose behavior using competing individual, team, organizational, incentive, power, and environmental explanations. 2. Distinguish practitioner frameworks from causal evidence and state when a model should not determine action. 3. Design a bounded change, feedback, conflict, motivation, or organization intervention with participation and safeguards. 4. Evaluate talent and culture processes for job relevance, bias, due process, accessibility, and employment risk. 5. Recommend a reversible intervention with an evidence plan, affected-party voice, dissent, owner, and stop rules." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-the-organizational-diagnosis-spine", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "The Organizational Diagnosis Spine", "headingId": "chapter-07-organizational-behavior-and-leadership-the-organizational-diagnosis-spine", "url": "#chapter-07-organizational-behavior-and-leadership-the-organizational-diagnosis-spine", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Start with the decision and observed behavior, not a label. Gather task, workflow, role, workload, incentive, team-history, identity, power, structure, and external evidence; test at least two plausible explanations; identify who may benefit or be harmed; choose the smallest ethical intervention that could distinguish the explanations; and define measures, appeal/escalation, owner, and review date. Judgment is vulnerable to availability and halo effects, so talent and leadership decisions require structured challenge and documented evidence. [BB-C07-S05] People-process boundary: High-stakes people decisions and use of assessment content belong with designated People/HR, counsel, and permissions owners. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-troubleshooting-guide-leadership-team-dynamics", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Troubleshooting Guide: Leadership & Team Dynamics", "headingId": "chapter-07-organizational-behavior-and-leadership-troubleshooting-guide-leadership-team-dynamics", "url": "#chapter-07-organizational-behavior-and-leadership-troubleshooting-guide-leadership-team-dynamics", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptom: \"We announced a major change initiative, and the response was silence. There's no energy or buy-in.\" Diagnosis: Urgency is one hypothesis. Silence may reflect disagreement, fear, workload, unclear authority, weak evidence, exclusion, or valid control concerns. Action: Ask affected people what they see, publish evidence and uncertainty, invite challenge, clarify decision rights and non-negotiable constraints, and revise the change when objections reveal risk. Do not manufacture a “burning platform.” [BB-C07-S01] Symptom: \"My team meetings are polite and agreeable, but they lack passion and we never solve hard problems.\" Diagnosis: Fear of conflict, low trust, or low psychological safety are hypotheses. Polite meetings can also reflect sound norms, power differences, facilitation, incentives, workload, skill, culture, meeting design, or decisions being made elsewhere. Action: Invite dissent through psychologically safer channels, distinguish task from relationship conflict, protect good-faith escalation, and use an independent reviewer when status or retaliation risk is high. Do not compel public dissent or treat silence as consent. Symptom: \"I feel like I have to make every single decision myself. My team won't take ownership.\" Diagnosis: Leadership style is one hypothesis. Centralized decisions can also reflect unclear delegation, capability, workload, risk, regulation, missing information, incentives, prior punishment, or genuinely reserved authority. Action: Map actual decision rights and risk tiers, ask team members what blocks ownership, and test clearer delegation with support and review. Coaching questions may help some people and tasks; do not force a public answer, delegate reserved authority, or treat one interaction as proof of capability. Symptom: \"We have a set of company values, but they feel completely disconnected from how people actually behave.\" Diagnosis: Your values are generic platitudes, not a description of observable, rewarded behavior. Your company is likely rewarding actions (e.g., hitting a sales number at all costs) that contradict the values (e.g., \"Integrity\"). Action: Define job-related behaviors, audit whether systems and decisions apply them consistently, examine adverse patterns and retaliation risk, and involve HR/legal owners before using values in employment decisions. Do not copy an unverified company model as “best in class.” ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-1-kotter-s-8-step-change-management-model", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "1. Kotter's 8-Step Change Management Model", "headingId": "chapter-07-organizational-behavior-and-leadership-1-kotter-s-8-step-change-management-model", "url": "#chapter-07-organizational-behavior-and-leadership-1-kotter-s-8-step-change-management-model", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Kotter's 8-Step Model for Change Leading Transformation" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-overview", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-07-organizational-behavior-and-leadership-overview", "url": "#chapter-07-organizational-behavior-and-leadership-overview", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Kotter's practitioner model organizes eight activities for leading change. Use it to prompt coalition, direction, communication, enablement, wins, and institutionalization; do not treat it as a validated universal sequence or label disagreement as resistance. Change can be iterative, local, political, emergent, and constrained by legitimate controls. [BB-C07-S01]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-how-to-apply", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-07-organizational-behavior-and-leadership-how-to-apply", "url": "#chapter-07-organizational-behavior-and-leadership-how-to-apply", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The original model is presented as a sequence. In application, diagnose dependencies and revisit earlier activities as evidence, participation, and context change. [BB-C07-S01] 1. Create a Sense of Urgency: Explain the evidence, uncertainty, costs of action and inaction, and why a decision is needed; do not exaggerate danger. 2. Build a Guiding Coalition: Assemble a powerful, cross-functional group of leaders and influencers who are fully committed to the change. 3. Form a Strategic Vision: Create a clear, simple, and inspiring picture of the future state. 4. Enlist Participation: Create informed, voluntary ways for affected employees to shape and support the change; clarify workload and authority. 5. Enable Action by Removing Barriers: Actively identify and remove obstacles (e.g., legacy processes, resistant managers). 6. Generate Short-Term Wins: Plan for and celebrate visible, unambiguous successes to build momentum. 7. Sustain Acceleration: After the first wins, use that momentum to tackle bigger, more difficult changes. Don't declare victory too early. 8. Institute Change: Integrate validated practices into roles, systems, governance, and learning; employment mechanisms require job-related criteria and HR/legal review. Figure 7.1. Kotter change activities with iterative review. The solid path shows the published sequence; the return edge makes the chapter's application caveat explicit. [BB-C07-S01] Text equivalent: Move from urgency to coalition, vision, informed participation, barrier removal, short-term wins, sustained acceleration, and institutionalization. Reassess the evidence, participation, and context throughout rather than assuming a one-way causal sequence. Source note: Original redraw of Kotter's practitioner sequence with an explicit iterative-review edge. [BB-C07-S01]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers", "url": "#chapter-07-organizational-behavior-and-leadership-so-what-for-managers", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the change decision, affected parties, evidence, authority, and non-negotiable safety or legal constraints before creating urgency. - Assign owners, participation routes, workload capacity, measures, and review points to each adopted change; do not treat communication as implementation. - Use short-term wins as evidence for the next bounded commitment, not as permission to declare victory or suppress dissent." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques", "url": "#chapter-07-organizational-behavior-and-leadership-limits-and-critiques", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Kotter's practitioner sequence is not a validated universal causal model; change may be iterative, emergent, political, or locally bounded. - Coalition and urgency language can amplify status, fear, manipulation, or retaliation when participation and dissent are not protected. - Institutionalization can harden a poor intervention; recheck outcomes, equity, safety, accessibility, and unintended effects before scaling." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-connections", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-connections", "url": "#chapter-07-organizational-behavior-and-leadership-connections", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The \"why\" for Step 1 (\"Urgency\") often comes from a Porter's Five Forces (Chapter 3) analysis showing an unattractive industry or a VRIO (Chapter 3) analysis showing an eroding advantage. Output: A successful change program enables the execution of a new strategy, which is then measured by OKRs and KPIs (Chapter 8) . ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-2-leadership-styles-radical-candor", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "2. Leadership Styles & Radical Candor", "headingId": "chapter-07-organizational-behavior-and-leadership-2-leadership-styles-radical-candor", "url": "#chapter-07-organizational-behavior-and-leadership-2-leadership-styles-radical-candor", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Leadership Styles & Radical Candor Effective Communication" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-overview-2", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-07-organizational-behavior-and-leadership-overview-2", "url": "#chapter-07-organizational-behavior-and-leadership-overview-2", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Leadership styles can be adapted to situation and task. Goleman's six styles provide a practitioner taxonomy for managerial behavior [BB-C07-S02], while [BB-C07-S16] Radical Candor provides a separate communication model for day-to-day feedback." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-07-organizational-behavior-and-leadership-how-to-apply-2", "url": "#chapter-07-organizational-behavior-and-leadership-how-to-apply-2", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Identify the decision, relationship, task, authority, time pressure, and affected parties before selecting a style. 2. Use the six-style taxonomy and Radical Candor as hypotheses; test whether the behavior improves clarity, learning, feedback quality, and psychological safety. 3. Deliver specific feedback through a proportionate, accessible channel, document commitments, and provide escalation when power or retaliation risk is material." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-part-a-goleman-s-six-styles", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Part A: Goleman's Six Styles", "headingId": "chapter-07-organizational-behavior-and-leadership-part-a-goleman-s-six-styles", "url": "#chapter-07-organizational-behavior-and-leadership-part-a-goleman-s-six-styles", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Coercive (\"Do what I say\"): May be considered in a genuine emergency under clear authority and safeguards; high misuse risk. 2. Authoritative (\"Come with me\"): Can clarify direction when evidence and participation support the vision. 3. Affiliative (\"People come first\"): Can support repair and connection but may leave task conflict unresolved. 4. Democratic (\"What do you think?\"): Can improve information and voice when decision rights and timing are clear. 5. Pacesetting (\"Do as I do, now\"): Can model a standard but may increase overload, dependence, or silence. 6. Coaching (\"Try this\"): Focused on long-term professional development." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-part-b-radical-candor-kim-scott", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Part B: Radical Candor (Kim Scott)", "headingId": "chapter-07-organizational-behavior-and-leadership-part-b-radical-candor-kim-scott", "url": "#chapter-07-organizational-behavior-and-leadership-part-b-radical-candor-kim-scott", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Radical Candor is a practitioner model that places feedback behavior along two proposed dimensions: Caring Personally and Challenging Directly . It is not a validated ranking of the “best” leadership style, and its usefulness depends on relationship, power, culture, task, channel, and safeguards. Radical Candor (High Care, High Challenge): A practitioner prompt for direct, specific feedback with care. “Brutal honesty” is not a license for humiliation, bias, retaliation, or disregard of status and culture. Obnoxious Aggression (Low Care, High Challenge): Brutal honesty without the kindness. This is just being a jerk. Ruinous Empathy (High Care, Low Challenge): You care, but you're too afraid of hurting someone's feelings to give them the feedback they need to improve. This is a common failure mode for new managers. Manipulative Insincerity (Low Care, Low Challenge): You say nothing, or you say false, political things. This is the most toxic quadrant. For an operator, Radical Candor is a practical model for combining direct feedback with respect." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-2", "url": "#chapter-07-organizational-behavior-and-leadership-so-what-for-managers-2", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Choose a style to match the decision, task, relationship, authority, and risk; do not perform a style as a personality test. - Make feedback specific, job-related, two-way, and proportionate, with a channel that protects dignity, accessibility, and escalation rights. - Test whether style or feedback changes clarity, learning, and follow-through before attributing talent or performance outcomes to the manager." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-2", "url": "#chapter-07-organizational-behavior-and-leadership-limits-and-critiques-2", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Goleman's taxonomy and Radical Candor are practitioner models, not validated rankings of leaders or universal prescriptions. - Directness can become humiliation, bias, retaliation, or unsafe disclosure when power, culture, status, and channel are ignored. - Adaptation claims are difficult to separate from task, team, incentive, workload, and selection effects; treat outcome claims as hypotheses." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-connections-2", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-connections-2", "url": "#chapter-07-organizational-behavior-and-leadership-connections-2", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Leadership behavior is one possible influence on Psychological Safety (Framework 10) alongside team design, incentives, history, workload, status, and formal protections. Output: Coaching and candid feedback can be tested as inputs to talent development in the Talent 9-Box Grid (Framework 6) ; they are not presumed to be the primary driver or to cause advancement. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-3-lencioni-s-five-dysfunctions-of-a-team", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "3. Lencioni's Five Dysfunctions of a Team", "headingId": "chapter-07-organizational-behavior-and-leadership-3-lencioni-s-five-dysfunctions-of-a-team", "url": "#chapter-07-organizational-behavior-and-leadership-3-lencioni-s-five-dysfunctions-of-a-team", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Lencioni's Five Dysfunctions of a Team Team Health Diagnostic" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-overview-3", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-07-organizational-behavior-and-leadership-overview-3", "url": "#chapter-07-organizational-behavior-and-leadership-overview-3", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Lencioni's five-dysfunctions model presents five linked team concerns—absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results—in that published order. Use it as a conversation prompt, not a definitive or validated causal diagnostic. Team behavior can also reflect task design, power, incentives, skills, workload, identity, history, or external constraints. [BB-C07-S07]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-07-organizational-behavior-and-leadership-how-to-apply-3", "url": "#chapter-07-organizational-behavior-and-leadership-how-to-apply-3", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The model owner publishes the sequence as a pyramid, but this book does not reproduce the branded visual or assessment. Do not assume the sequence identifies the cause or dictates the intervention; gather evidence at each level. [BB-C07-S07] 1. Absence of Trust: Ask whether people can acknowledge uncertainty or mistakes without disproportionate interpersonal risk. Possible tests include leader fallibility, confidential feedback, clearer boundaries, and reliable follow-through. 2. Fear of Conflict: Distinguish useful task disagreement from relationship conflict, coercion, harassment, or unsafe escalation. Invite dissent through channels appropriate to status and retaliation risk. 3. Lack of Commitment: Test whether ambiguity, exclusion, weak evidence, unresolved dependency, or unclear authority explains non-commitment. Clarify the decision, rationale, dissent record, owner, and review point without compelling false agreement. 4. Avoidance of Accountability: Define job-related commitments, evidence, authority, support, and fair escalation. Public commitments and peer challenge are options, not universal or safe defaults. 5. Inattention to Results: Compare individual, team, customer, safety, risk, and enterprise goals. A public team goal can help some contexts but is not the only intervention and must not override rights or controls." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-3", "url": "#chapter-07-organizational-behavior-and-leadership-so-what-for-managers-3", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the team outcome, decision rights, dependencies, and evidence before labeling a dysfunction or prescribing a team exercise. - Use the five concerns to choose a bounded conversation, observation, or process test; record dissent and the conditions for escalation. - Track team, customer, safety, quality, and individual effects separately so a visible team result does not hide harm or exclusion." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-3", "url": "#chapter-07-organizational-behavior-and-leadership-limits-and-critiques-3", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Lencioni's pyramid is a practitioner sequence, not proof that one dysfunction causes the next or that all teams progress in that order. - Trust and conflict behavior are shaped by power, task design, workload, identity, incentives, skills, history, and external constraints. - Team-development stages are hypotheses that vary by setting; the group-development literature does not establish fixed stages or performance effects [BB-C07-S06]. - Public accountability and forced conflict can increase retaliation or silence; participation and confidentiality must fit the context." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-connections-3", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-connections-3", "url": "#chapter-07-organizational-behavior-and-leadership-connections-3", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: An \"unhealthy\" team identified through observation or poor KPIs (Chapter 8) is the trigger to use this framework. Output: The discussion can generate hypotheses for team norms, decision design, conflict handling, accountability, or goals; it does not guarantee psychological safety or performance. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-4-stakeholder-mapping-grid", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "4. Stakeholder Mapping Grid", "headingId": "chapter-07-organizational-behavior-and-leadership-4-stakeholder-mapping-grid", "url": "#chapter-07-organizational-behavior-and-leadership-4-stakeholder-mapping-grid", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Stakeholder Mapping Grid Influence & Communication Strategy" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-overview-4", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-07-organizational-behavior-and-leadership-overview-4", "url": "#chapter-07-organizational-behavior-and-leadership-overview-4", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A power-interest grid is one provisional view of stakeholders. Official UK analytical guidance defines power or influence as ability to affect decisions or outcomes and interest as concern or involvement, and recommends recording the rationale and reviewing positions as they change. The grid can help plan engagement, but low-power stakeholders may hold rights, expertise, safety information, or disproportionate exposure to harm; the map must not determine whose voice counts. [BB-C07-S08]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-07-organizational-behavior-and-leadership-how-to-apply-4", "url": "#chapter-07-organizational-behavior-and-leadership-how-to-apply-4", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. List Stakeholders: Brainstorm every individual or group affected by your project. 2. Assess Power and Interest: For each stakeholder, rate their power and interest on a High/Low scale. 3. Plot on the Grid and Define Strategy: High Power, High Interest (Manage Closely): Use proportionate, decision-relevant engagement and document authority, interests, commitments, and disagreements. High Power, Low Interest: Provide proportionate decision information and clarify authority; do not equate satisfaction with good governance. Low Power, High Interest (Consult With): Create accessible participation and escalation because affected users may hold critical evidence or rights. Low Power, Low Interest (Keep Informed): Monitor for changed impact or interest and provide baseline access to relevant information; “low power” does not mean low importance. [BB-C07-S08] Figure 7.2. Constructed power-interest engagement map. Anonymous positions illustrate the geometry only; rights, harm exposure, expertise, legitimacy, and changing context can override a quadrant tactic. Text equivalent: Plot anonymous stakeholders on provisional power and interest axes, then supplement the position with rights, expertise, legitimacy, harm exposure, access needs, and change over time. Select engagement and escalation from the full assessment rather than the quadrant alone. Source note: Author-created teaching map informed by stakeholder theory, salience research, and the UK Government Analysis Function's power-interest guidance; example coordinates are illustrative and no stakeholder is declared unimportant. [BB-C07-S08]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-4", "url": "#chapter-07-organizational-behavior-and-leadership-so-what-for-managers-4", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Record who is affected, who can act, who holds evidence or rights, and what engagement or escalation is proportionate to the decision. - Revisit the map as authority, harm exposure, interest, access needs, and dependencies change; do not let a quadrant become a permanent label. - Use the map to design participation and decision records, not to decide whose interests count." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-4", "url": "#chapter-07-organizational-behavior-and-leadership-limits-and-critiques-4", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Power and interest are provisional constructs; low formal power can coexist with legal rights, expertise, safety exposure, or implementation influence. - High/low categories can flatten differences within groups and conceal conflicts of interest, representation problems, or inaccessible participation. - A map does not establish stakeholder preferences, consent, impact, or causal leverage without direct evidence and review." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-connections-4", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-connections-4", "url": "#chapter-07-organizational-behavior-and-leadership-connections-4", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The list of stakeholders is often generated during the initial phases of a project, as defined in the Project Charter in Chapter 11. Output: Your stakeholder map is a critical input for your change management plan when using Kotter's 8-Step Model (Framework 1) , especially for \"Building a Guiding Coalition.\" ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-5-competing-values-framework-culture-assessment", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "5. Competing Values Framework (Culture Assessment)", "headingId": "chapter-07-organizational-behavior-and-leadership-5-competing-values-framework-culture-assessment", "url": "#chapter-07-organizational-behavior-and-leadership-5-competing-values-framework-culture-assessment", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Competing Values Framework (Culture) Organizational Diagnosis" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-overview-5", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-07-organizational-behavior-and-leadership-overview-5", "url": "#chapter-07-organizational-behavior-and-leadership-overview-5", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Competing Values Framework organized effectiveness criteria along control–flexibility, internal–external, and means–ends dimensions. Cameron and Quinn later applied the framework to organizational-culture profiles. This section uses the two-axis culture adaptation; it simplifies subcultures and does not identify a single “true” culture, causal diagnosis, or best target. [BB-C07-S09] [BB-C07-S10]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-07-organizational-behavior-and-leadership-how-to-apply-5", "url": "#chapter-07-organizational-behavior-and-leadership-how-to-apply-5", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Understand the Four Cultures: Clan (Collaborate): Internal focus and flexibility, emphasizing cohesion, participation, and development. Adhocracy (Create): External focus and flexibility, emphasizing experimentation, adaptation, and innovation. Hierarchy (Control): Internal focus and stability, emphasizing formalization, coordination, and reliability. Market (Compete): External focus and stability, emphasizing goals, competition, and results. [BB-C07-S10] 2. Assess Carefully: If using the OCAI, follow the licensed instrument, permissions, administration, and scoring requirements. For an unscored workshop, ask participants to discuss current and preferred emphases without calling the result an OCAI assessment. 3. Analyze Tensions: Treat current/desired differences as hypotheses. Examine strategy, task, regulation, safety, coordination, incentives, subcultures, and who defines “desired” before selecting a change." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-5", "url": "#chapter-07-organizational-behavior-and-leadership-so-what-for-managers-5", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Compare current and desired cultural emphases with strategy, work, risk, regulation, and employee evidence before selecting a change. - Use an unscored discussion or licensed instrument to surface tradeoffs, then convert findings into observable behaviors, owners, and tests. - Check whether systems, incentives, leadership behavior, and resource choices reinforce the behaviors the organization says it values." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-5", "url": "#chapter-07-organizational-behavior-and-leadership-limits-and-critiques-5", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The framework simplifies subcultures and does not identify one true culture, causal diagnosis, or universally preferred quadrant. - OCAI administration, scoring, and reproduction may require licensed materials; an informal workshop is not an OCAI assessment. - Culture labels can stereotype groups or become employment criteria; use job-related evidence and HR/legal review for people decisions." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-connections-5", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-connections-5", "url": "#chapter-07-organizational-behavior-and-leadership-connections-5", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Use strategy, task, interdependence, risk, regulation, employee evidence, and customer needs; no competitive strategy requires one culture quadrant. Output: The assessment may inform a change hypothesis. Do not use a culture label as a hiring, promotion, discipline, or termination criterion. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-6-talent-9-box-grid", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "6. Talent 9-Box Grid", "headingId": "chapter-07-organizational-behavior-and-leadership-6-talent-9-box-grid", "url": "#chapter-07-organizational-behavior-and-leadership-6-talent-9-box-grid", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Talent 9-Box Grid Talent Management & Succession" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-overview-6", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-07-organizational-behavior-and-leadership-overview-6", "url": "#chapter-07-organizational-behavior-and-leadership-overview-6", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The 9-box grid plots a performance assessment against a judgment of future potential. It can surface disagreement during calibration, but it does not ensure fairness, predict future leadership, diagnose underperformance, or determine employment action. “Potential” is subjective and vulnerable to availability and halo effects; talent-assessment research also warns that organizations differ in how they define and identify it. [BB-C07-S05] [BB-C07-S17]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-07-organizational-behavior-and-leadership-how-to-apply-6", "url": "#chapter-07-organizational-behavior-and-leadership-how-to-apply-6", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define Evidence: Use job-related criteria, comparable opportunities, a documented period, multiple evidence sources, and role context. Separate current performance from assumptions about a future role. 2. Calibrate Responsibly: Use multiple reviewers, record disagreement and uncertainty, audit demographic and opportunity patterns, and check accommodation, leave, retaliation, and assignment effects with HR/legal owners. 3. Choose Development Separately: Discuss development interests, role fit, sponsorship, feedback, support, and succession risk with the employee where appropriate. Do not let a box dictate pay, promotion, PIP, or exit. 4. Review and Appeal: Time-limit labels, provide a correction/escalation path, and validate whether the process predicts any intended outcome without creating inequity." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-6", "url": "#chapter-07-organizational-behavior-and-leadership-so-what-for-managers-6", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Keep current performance evidence separate from future-role potential, and define job-related criteria, opportunity context, reviewers, and time period. - Use calibration to surface disagreement and development needs; document uncertainty and provide correction or appeal routes. - Treat a grid as one input to development planning, never as an automatic pay, promotion, discipline, PIP, or exit decision." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-6", "url": "#chapter-07-organizational-behavior-and-leadership-limits-and-critiques-6", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Potential is subjective and vulnerable to halo, availability, sponsorship, assignment, accommodation, leave, and retaliation effects. - The grid does not prove fairness, predict future leadership, or establish that a labeled employee caused an outcome. - Employment decisions require separate approved criteria, consistency, documentation, due process, accessibility, and HR/legal review." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-connections-6", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-connections-6", "url": "#chapter-07-organizational-behavior-and-leadership-connections-6", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Performance evidence should be job-related and context-aware; KPIs/OKRs are not automatically objective. Potential is an uncertain judgment about a defined future role. Output: The discussion may inform development and succession hypotheses. Compensation and employment decisions require separate approved criteria, documentation, consistency, and review. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-7-motivation-theory-comparison", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "7. Motivation Theory Comparison", "headingId": "chapter-07-organizational-behavior-and-leadership-7-motivation-theory-comparison", "url": "#chapter-07-organizational-behavior-and-leadership-7-motivation-theory-comparison", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Motivation Theories (Herzberg & Pink) Employee Engagement" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-overview-7", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-07-organizational-behavior-and-leadership-overview-7", "url": "#chapter-07-organizational-behavior-and-leadership-overview-7", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Herzberg's two-factor theory distinguishes hygiene factors from motivators; evidence and later theories do not justify a categorical split for every person or job. Pink's practitioner model provides a separate autonomy-mastery-purpose prompt, while self-determination theory offers a distinct research-based account of autonomy, competence, and relatedness. Use these as hypotheses alongside pay fairness, job design, workload, manager behavior, identity, inclusion, labor conditions, and outside options. [BB-C07-S03] [BB-C07-S18] [BB-C07-S19]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-07-organizational-behavior-and-leadership-how-to-apply-7", "url": "#chapter-07-organizational-behavior-and-leadership-how-to-apply-7", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Separate Hygiene from Motivation (Herzberg): Hygiene Factors: In the theory, factors such as salary, security, and working conditions are associated with dissatisfaction; do not assume they cannot also affect motivation, fairness, or retention. Motivators: In the theory, achievement, recognition, responsibility, and growth can support satisfaction; effects depend on person, job, context, and implementation. Operator's Insight: Treat compensation as one component of the work environment, then consider how the role provides recognition, responsibility, growth, and achievement. 2. Focus on Intrinsic Motivators (Pink): For modern knowledge work, Daniel Pink's practitioner model uses three prompts: autonomy, mastery, and purpose. [BB-C07-S19] Autonomy: The desire to direct our own lives. Give your team control over their task, time, team, and technique. Mastery: The urge to get better at something that matters. Provide challenging work and opportunities for skill development. Purpose: The yearning to do what we do in the service of something larger than ourselves. Constantly connect your team's work to the company's Mission and Vision (Chapter 8) ." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-7", "url": "#chapter-07-organizational-behavior-and-leadership-so-what-for-managers-7", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Diagnose dissatisfaction and motivation separately: fix unfairness, workload, safety, and role conditions before prescribing intrinsic-motivation interventions. - Design bounded role or manager experiments around autonomy, mastery, purpose, recognition, growth, and clear guardrails. - Measure retention, learning, performance, workload, and employee voice without claiming that one theory explains the result." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-7", "url": "#chapter-07-organizational-behavior-and-leadership-limits-and-critiques-7", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Herzberg and Pink are not universal causal models; people, jobs, cultures, labor conditions, and economic constraints vary. - Autonomy can be unsafe or unrealistic when authority, competence, regulation, or interdependence requires structure and support. - Engagement surveys and exit interviews are selective evidence; silence, departure, and satisfaction do not identify one cause." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-connections-7", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-connections-7", "url": "#chapter-07-organizational-behavior-and-leadership-connections-7", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Data on employee dissatisfaction from engagement surveys or exit interviews can identify which Hygiene Factors are broken. Output: Motivation hypotheses can inform role and manager experiments; they do not guarantee development or retention and should not be tied to talent labels. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-8-conflict-mode-reflection-map", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "8. Conflict-Mode Reflection Map", "headingId": "chapter-07-organizational-behavior-and-leadership-8-conflict-mode-reflection-map", "url": "#chapter-07-organizational-behavior-and-leadership-8-conflict-mode-reflection-map", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Conflict-Mode Reflection Map Constructive Disagreement" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-overview-8", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-07-organizational-behavior-and-leadership-overview-8", "url": "#chapter-07-organizational-behavior-and-leadership-overview-8", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Conflict-mode reflection is an author-created aid built around the published Thomas-Kilmann geometry [BB-C07-S20]; it is not the licensed instrument, a scored assessment, or a validated decision tree. Conflict can surface information or cause harm depending on task, relationship, power, safety, culture, and process. Use the modes as reflection prompts, not personality labels or universal prescriptions. Instrument use and reproduction may require permission." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-07-organizational-behavior-and-leadership-how-to-apply-8", "url": "#chapter-07-organizational-behavior-and-leadership-how-to-apply-8", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Based on the two axes of Assertiveness (concern for your goals) and Cooperativeness (concern for the relationship), choose your mode: 1. Competing (High Assertiveness, Low Cooperativeness): May fit a time-critical decision under legitimate authority; “knowing you are right” is not sufficient. 2. Collaborating (High Assertiveness, High Cooperativeness): May fit important interdependent interests when time, safety, and power allow genuine participation; it is not always feasible or superior. 3. Compromising (Moderate Assertiveness & Cooperativeness): Use when a quick, temporary solution is needed and you're willing to \"split the difference.\" No one is fully satisfied. 4. Avoiding (Low Assertiveness, Low Cooperativeness): May create time, safety, or de-escalation; persistent avoidance can leave issues unresolved and should not be moralized as weakness. 5. Accommodating (Low Assertiveness, High Cooperativeness): May fit when preserving the relationship or learning matters more than the issue; do not use it to suppress rights, safety, or professional duties. Figure 7.3. Conflict-mode reflection map (constructed). The positions represent the published assertiveness/cooperativeness dimensions; the map does not select a mode without context, power, safety, and rights review. Text equivalent: Competing is high assertiveness and low cooperativeness; collaborating is high on both; avoiding is low on both; accommodating is low assertiveness and high cooperativeness; compromising sits near the middle. Choose only after assessing the issue, authority, time, interdependence, relationship, safety, rights, and escalation needs. Source note: Author-created illustrative redraw of the Thomas-Kilmann mode geometry. The instrument and terminology may be licensed; do not reproduce assessment items without permission. [BB-C07-S20]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-8", "url": "#chapter-07-organizational-behavior-and-leadership-so-what-for-managers-8", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the issue, authority, time, interdependence, safety, rights, and relationship before choosing a conflict response. - Use collaboration, competition, compromise, avoidance, or accommodation as context-specific options, with a review point and escalation path. - Separate task information from relationship harm and document how the decision changed after dissent or new evidence." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-8", "url": "#chapter-07-organizational-behavior-and-leadership-limits-and-critiques-8", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The Thomas-Kilmann geometry is a reflection aid, not a licensed assessment, personality diagnosis, or validated decision tree. - “Compromise” is not automatically fair, and public confrontation can be unsafe or coercive under power or retaliation risk. - Conflict style alone does not determine decision quality, psychological safety, legal compliance, or relationship outcomes." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-connections-8", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-connections-8", "url": "#chapter-07-organizational-behavior-and-leadership-connections-8", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Trust and psychological safety can support task disagreement, but conflict behavior also depends on authority, skill, incentives, identity, facilitation, workload, and risk. Output: Appropriate conflict handling can improve information quality and deliberation; it does not guarantee collaboration, decision quality, or satisfaction of legal duties. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-9-organizational-design-patterns", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "9. Organizational Design Patterns", "headingId": "chapter-07-organizational-behavior-and-leadership-9-organizational-design-patterns", "url": "#chapter-07-organizational-behavior-and-leadership-9-organizational-design-patterns", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Organizational Design Patterns Structuring for Success" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-overview-9", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-07-organizational-behavior-and-leadership-overview-9", "url": "#chapter-07-organizational-behavior-and-leadership-overview-9", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Organization design allocates work, authority, information, coordination, incentives, and accountability. Functional, divisional, and matrix forms make different specialization, duplication, coordination, and authority tradeoffs. Fit depends on strategy, uncertainty, interdependence, scale, regulation, technology, labor, capabilities, and informal networks; no structure is universally agile or superior. [BB-C07-S11]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-07-organizational-behavior-and-leadership-how-to-apply-9", "url": "#chapter-07-organizational-behavior-and-leadership-how-to-apply-9", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Understand the Classic Structures: Functional: Groups work by expertise or department. It can deepen specialization and scale within functions while increasing cross-functional coordination and silo risks. Divisional: Groups functions under product, geography, market, or another division basis. It can clarify local responsibility while duplicating functions and weakening enterprise coordination. Matrix: Combines authority dimensions, often functional and product or project, so employees have dual reporting relationships. It can integrate perspectives while creating conflict, divided loyalty, and authority ambiguity. [BB-C07-S11] 2. Examine Product-Team Patterns: Spotify snapshot: A 2012 white paper described one organization's evolving squads, tribes, chapters, and guilds; it was not a universal operating model. Squads: Small, self-organizing, cross-functional teams with a long-term mission in the 2012 description. Tribes: A collection of squads working in a related area. Chapters & Guilds: Mechanisms for people with related skills or interests to coordinate and share knowledge across squads. [BB-C07-S12] Decision: Compare product/customer flow, functional depth, architecture, decision rights, dependencies, risk, and career systems before adapting any pattern." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-9", "url": "#chapter-07-organizational-behavior-and-leadership-so-what-for-managers-9", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Choose a structure by matching strategy, work dependencies, decision rights, coordination cost, capability, risk, and labor context—not by copying a label. - Make interfaces, escalation, resource allocation, career support, and conflict-resolution authority explicit before launch. - Treat a redesign as a staged hypothesis with service, quality, workload, inclusion, and decision-speed measures." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-9", "url": "#chapter-07-organizational-behavior-and-leadership-limits-and-critiques-9", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Functional, divisional, matrix, and product-team patterns each trade specialization, duplication, coordination, and authority; none is universally superior. - Spotify's 2012 description was one evolving organization's snapshot, not a finished universal model or proof of performance. - Structure interacts with informal networks, incentives, technology, labor, regulation, and leadership; diagrams cannot substitute for operating evidence." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-connections-9", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-connections-9", "url": "#chapter-07-organizational-behavior-and-leadership-connections-9", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Organization design should support strategy and operating needs; innovation does not require one culture or structure label. Output: A design hypothesis can clarify decision rights, interfaces, escalation, career support, and resource deployment. In the VRIO framework (Chapter 3) , organization is one condition for exploiting a resource; a structure label does not turn a resource into competitive advantage by itself. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-10-psychological-safety-assessment", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "10. Psychological Safety Assessment", "headingId": "chapter-07-organizational-behavior-and-leadership-10-psychological-safety-assessment", "url": "#chapter-07-organizational-behavior-and-leadership-10-psychological-safety-assessment", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Psychological Safety Speaking Up, Learning, and Accountability" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-overview-10", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-07-organizational-behavior-and-leadership-overview-10", "url": "#chapter-07-organizational-behavior-and-leadership-overview-10", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Psychological safety is a shared belief that a team is safe for interpersonal risk-taking. Edmondson's 1999 study involved 51 teams in one manufacturing company and associated psychological safety with learning behavior; it does not establish universal innovation, retention, performance, or intervention effects. [BB-C07-S04]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-07-organizational-behavior-and-leadership-how-to-apply-10", "url": "#chapter-07-organizational-behavior-and-leadership-how-to-apply-10", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Assess It Carefully: Use voluntary, confidential, accessible methods appropriate to the context; verify instrument permissions and do not identify individuals from small groups. 2. Model Learning and Accountability: Leader behavior is one input, not a guaranteed intervention. Admit your own fallibility: Start sentences with \"I might be missing something here...\" Model curiosity: Ask powerful questions instead of giving answers. Frame the work as a learning problem, not an execution problem. 3. React Productively: Leader responses can influence psychological safety, but they do not determine it; peers, systems, incentives, workload, power, employment practices, and prior experience also matter. When someone brings you bad news, thank them . When a mistake is made, ask \"What did we learn?\" not \"Who is to blame?\"" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-10", "url": "#chapter-07-organizational-behavior-and-leadership-so-what-for-managers-10", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use voluntary, confidential, accessible channels to surface risks, questions, and dissent, especially when power or retaliation risk is material. - Respond to bad news with curiosity and accountability, then track whether the response changes reporting, learning, and correction behavior. - Keep psychological safety distinct from comfort, agreement, performance, or absence of accountability; define the work and guardrails." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-10", "url": "#chapter-07-organizational-behavior-and-leadership-limits-and-critiques-10", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Edmondson's 51-team study was observational and context-specific; it does not establish universal innovation, retention, performance, or intervention effects [BB-C07-S04]. - Measurement caution: Treat survey scores as local signals; sample size, instrument permissions, retaliation concerns, culture, workload, and changing team membership can limit interpretation [BB-C07-S04]. - Psychological safety does not replace professional duties, safety controls, performance standards, confidentiality, or fair accountability." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-connections-10", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-connections-10", "url": "#chapter-07-organizational-behavior-and-leadership-connections-10", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Psychological safety, interpersonal trust, and willingness to engage in task conflict are related managerial concerns but distinct constructs; do not infer one from another without local evidence. Output: In Edmondson's 51-team study, psychological safety was associated with team learning behavior; the study does not establish universal innovation, retention, or change-management effects. [BB-C07-S04] ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-negotiation-bridge-alternatives-range-value-power-and-ethics", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Negotiation Bridge: Alternatives, Range, Value, Power, and Ethics", "headingId": "chapter-07-organizational-behavior-and-leadership-negotiation-bridge-alternatives-range-value-power-and-ethics", "url": "#chapter-07-organizational-behavior-and-leadership-negotiation-bridge-alternatives-range-value-power-and-ethics", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Negotiation is a joint decision process under interdependence, not simply persuasion or compromise. Before exchanging proposals, define the decision authority, issues, affected parties, legal and ethical constraints, and what happens if no agreement is reached. Getting to Yes popularized interest-based negotiation and the best alternative to a negotiated agreement (BATNA) ; The Manager as Negotiator emphasizes the simultaneous work of creating value and claiming value. [BB-C07-S13] [BB-C07-S14] This is a bounded bridge to Chapter 12, not an additional numbered framework." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-core-preparation-logic", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Core preparation logic", "headingId": "chapter-07-organizational-behavior-and-leadership-core-preparation-logic", "url": "#chapter-07-organizational-behavior-and-leadership-core-preparation-logic", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 7.1. Constructed evidence-gated negotiation preparation. The table converts BATNA, reservation value, target, ZOPA, interests, and objective-criteria questions into prompts; it is not a valuation or outcome model. [BB-C07-S13] [BB-C07-S14] | Element | Managerial question | Common failure | |---|---|---| | BATNA | What will we actually do if this negotiation ends without agreement? | Calling a wish, threat, or preferred deal an alternative | | Reservation value | At what package are we indifferent between agreement and the BATNA, after risk, timing, switching, and implementation costs? | Treating one headline number as the whole package | | Target | What ambitious, supportable outcome will guide offers and tradeoffs? | Confusing aspiration with entitlement | | ZOPA | Is there a zone of possible agreement in which both sides prefer a feasible deal to their alternatives? | Assuming a ZOPA exists or estimating the other side's limit as fact | | Interests and differences | Which priorities, forecasts, capabilities, risk preferences, and timing needs differ enough to support trades? | “Splitting the difference” across unlike issues | | Objective criteria | Which market, precedent, technical, policy, or fairness standards are legitimate for this decision? | Selecting only criteria that favor one side | Figure 7.4. Constructed evidence-gated negotiation preparation. Text equivalent: Verify authority, parties, issues, and constraints; model the team's own alternative and reservation package; treat estimates of the other side as hypotheses; then test whether a bargaining range may exist. If not, change the setup, improve alternatives, add issues or parties, pause, or walk away. If a range exists or remains uncertain, compare packages using legitimate criteria, negotiate value, and document approvals and implementation. Source note: Author-created evidence-gated negotiation preparation flow informed by principled and managerial negotiation frameworks. It is a constructed decision aid, not a negotiation outcome model. [BB-C07-S13] [BB-C07-S14]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-power-multiparty-process-and-ethics", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Power, multiparty process, and ethics", "headingId": "chapter-07-organizational-behavior-and-leadership-power-multiparty-process-and-ethics", "url": "#chapter-07-organizational-behavior-and-leadership-power-multiparty-process-and-ethics", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Power is relational and issue-specific: alternatives, authority, information, legitimacy, time, coalition support, resources, and the ability to implement all matter. A strong BATNA can improve leverage, but coercion, discrimination, retaliation, misuse of confidential information, sham consultation, and commitments outside delegated authority are not negotiation tactics. For legal negotiations, professional duties vary by jurisdiction; the American Bar Association's Model Rule 4.1, for example, addresses knowingly false statements of material fact or law by lawyers and is not a universal rule for every person or jurisdiction. [BB-C07-S15] In a multiparty negotiation, prepare a party-interest-authority map; define the decision rule; establish representation, confidentiality, agenda, and recordkeeping; identify possible coalitions without assuming they are fixed; and use caucuses or working groups only with a transparent route back to the authorized decision body. Do not trade away the rights or safety of absent affected parties. When not to negotiate: use the required reporting, safety, emergency, fiduciary, regulatory, collective-bargaining, procurement, investigation, or legal process when the issue is not within the participants' authority to trade. Agreement does not cure illegality, lack of consent, unmanaged conflicts, or material implementation risk. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-mental-model-1-culture-is-what-you-reward-and-punish", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 1: Culture is What You Reward and Punish", "headingId": "chapter-07-organizational-behavior-and-leadership-mental-model-1-culture-is-what-you-reward-and-punish", "url": "#chapter-07-organizational-behavior-and-leadership-mental-model-1-culture-is-what-you-reward-and-punish", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Author synthesis: Formal rewards and sanctions influence behavior, but culture also reflects identity, norms, leadership, task, profession, history, power, and informal networks. Audit whether job-related criteria and actual decisions align, examine adverse patterns and voice, and use HR/legal review; do not infer an employee's character or the organization's “true culture” from one promotion or termination." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-mental-model-2-the-trust-cascade", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 2: The Trust Cascade", "headingId": "chapter-07-organizational-behavior-and-leadership-mental-model-2-the-trust-cascade", "url": "#chapter-07-organizational-behavior-and-leadership-mental-model-2-the-trust-cascade", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Author synthesis: Lencioni proposes a cascade from trust to conflict, commitment, accountability, and results. Treat the sequence as a practitioner hypothesis, not a causal law. Accountability problems may also arise from unclear authority, capacity, incentives, skills, process, or conflicting goals; test alternatives before intervening. [BB-C07-S07]" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-mental-model-3-leadership-is-situational-but-authenticity-is-key", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 3: Leadership is Situational, but Authenticity is Key", "headingId": "chapter-07-organizational-behavior-and-leadership-mental-model-3-leadership-is-situational-but-authenticity-is-key", "url": "#chapter-07-organizational-behavior-and-leadership-mental-model-3-leadership-is-situational-but-authenticity-is-key", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Author synthesis: While it is useful to flex between leadership styles, leaders may lose trust when their behavior reads as inauthentic. A practical approach is to understand one's default style (e.g., Authoritative or Coaching) and adapt communication within it rather than perform a completely different personality. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-illustrative-leadership-applications", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Illustrative Leadership Applications", "headingId": "chapter-07-organizational-behavior-and-leadership-illustrative-leadership-applications", "url": "#chapter-07-organizational-behavior-and-leadership-illustrative-leadership-applications", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following scenarios are hypothetical worked examples, not historical case studies." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-application-1-culture-turnaround", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Application 1: Culture Turnaround", "headingId": "chapter-07-organizational-behavior-and-leadership-application-1-culture-turnaround", "url": "#chapter-07-organizational-behavior-and-leadership-application-1-culture-turnaround", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A software company may discover that forced ranking pits employees against each other and discourages collaboration. The Problem: The leadership team sees reduced learning and weak cross-functional cooperation. The Action: The company removes forced-ranking incentives and models curiosity, learning, and respectful challenge. The Result: The team uses collaboration and learning indicators to assess whether the new practices are working. Lesson: Leaders can change the systems that reward and punish behavior." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-application-2-creative-review-process", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Application 2: Creative-Review Process", "headingId": "chapter-07-organizational-behavior-and-leadership-application-2-creative-review-process", "url": "#chapter-07-organizational-behavior-and-leadership-application-2-creative-review-process", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A creative organization can use a review forum with no formal decision authority to separate candid feedback from final ownership. The Model: Feedback is direct, specific, and focused on the work rather than the person. The Impact: This structure can make it easier to surface problems early and discuss them rigorously. Lesson: Design a process in which ideas can be challenged without personal reprisal." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-application-3-visual-accountability", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Application 3: Visual Accountability", "headingId": "chapter-07-organizational-behavior-and-leadership-application-3-visual-accountability", "url": "#chapter-07-organizational-behavior-and-leadership-application-3-visual-accountability", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A manufacturer could use a red-yellow-green operating review to make risks visible. The Problem: Teams may keep reporting green status because they expect negative consequences for bad news. The Intervention: The leader thanks people who surface a risk and asks what support would help resolve it. The Result: The review becomes a forum for solving disclosed problems rather than concealing them. Lesson: A leader's reaction to bad news shapes whether people raise it. ---" }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-applied-exercise-diagnose-a-team-without-labeling-it", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Applied Exercise: Diagnose a Team Without Labeling It", "headingId": "chapter-07-organizational-behavior-and-leadership-applied-exercise-diagnose-a-team-without-labeling-it", "url": "#chapter-07-organizational-behavior-and-leadership-applied-exercise-diagnose-a-team-without-labeling-it", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Using a constructed cross-functional team case, identify observed behavior and decision stakes; develop at least two explanations spanning individual, team, workflow, incentive, power, and external levels; use Kotter, psychological safety, motivation, conflict, and organization-design lenses; reject at least one explanation based on evidence; and propose a reversible 30-day intervention. Deliver an evidence plan, affected-party voice, HR/legal/safety triggers, owner, measures, appeal/escalation route, and stop or redesign rule." }, { "id": "chapter-07-organizational-behavior-and-leadership::chapter-07-organizational-behavior-and-leadership-selective-connections", "kind": "chapter", "itemSlug": "chapter-07-organizational-behavior-and-leadership", "itemTitle": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "heading": "Selective Connections", "headingId": "chapter-07-organizational-behavior-and-leadership-selective-connections", "url": "#chapter-07-organizational-behavior-and-leadership-selective-connections", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use Chapter 2 for employment, governance, ethics, and professional-duty boundaries. - Use Chapter 3 for strategic context and organization-design fit. - Use Chapter 8 for goals, measures, incentives, and execution learning. - Use Chapter 11 for project roles, stakeholders, and change control. - Use Chapter 12 for difficult conversations and stakeholder communication. - Use Chapter 17 for enterprise change and workforce participation. - Use Chapter 22 for evidence, bias, causal claims, and uncertainty. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-executive-summary", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Executive Summary", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-executive-summary", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-executive-summary", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter connects strategic intent to funded work, measures, review, and adaptation. Mission, vision, values, OKRs, KPIs, and scorecards can support execution, but none substitutes for choices, resources, decision rights, operating capacity, learning, and reallocation." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-manager-decision-outcomes", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Manager decision outcomes", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-manager-decision-outcomes", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-manager-decision-outcomes", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "By the end of this chapter, a manager should be able to: 1. Distinguish purpose, envisioned future, values, strategy, initiatives, outcomes, and operating measures without imposing a false hierarchy. 2. Translate a strategy kernel into a constrained portfolio with owners, resources, dependencies, risk, and decision dates. 3. Design OKRs, KPIs, and scorecards with definitions, baselines, lineage, controllability, guardrails, and gaming tests. 4. Choose a cadence, alignment method, scoring convention, and incentive boundary for the work and organization. 5. Run a review that updates forecasts, tests strategic hypotheses, records dissent, and reallocates or stops work." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-strategy-execution-operating-system", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "The Strategy-Execution Operating System", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-strategy-execution-operating-system", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-strategy-execution-operating-system", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Translate the strategy kernel into a portfolio of funded initiatives. For each initiative define the outcome hypothesis, owner, capacity and budget, dependencies, leading and lagging measures, data owner, guardrails, decision date, and stop, continue, or scale rule. This is an author-created operating model, not an empirically validated universal prescription. At each review, reconcile actuals and forecasts, examine gaming and unintended effects, test whether the strategy still fits, and reallocate resources rather than merely rescoring goals. Metric gaming and distortion are documented risks. [BB-C08-S06] ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-troubleshooting-guide-strategy-execution", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Troubleshooting Guide: Strategy & Execution", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-troubleshooting-guide-strategy-execution", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-troubleshooting-guide-strategy-execution", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptom: \"Our team's Key Results are just a list of tasks or projects we were already doing.\" Diagnosis: You are confusing Outputs (activities) with Outcomes (results). This is a common failure mode when adopting OKRs. Action: For every Key Result, ask the question: \"And what is the measurable business result of doing that?\" For example, instead of \"Ship the new onboarding flow,\" a better KR is \"Increase new user activation rate from 40% to 55% in the first 7 days.\" Symptom: \"Our company values feel like generic corporate platitudes that everyone ignores.\" Diagnosis: Values may be vague, contradicted by systems, interpreted inconsistently, or disconnected from the work. Action: Define job-related behaviors, examine conflicting values and incentives, test understanding across roles/cultures, audit adverse patterns, protect good-faith dissent, and route employment use through approved People/HR and counsel processes. Symptom: \"Our OKR process feels like a heavy, bureaucratic chore that takes weeks every quarter.\" Diagnosis: Process burden may reflect too many goals, unclear choices, duplicated planning, poor data, unresolved dependencies, or an ill-fitting cadence. Action: Remove work that does not change a decision, then choose workshop length, cadence, number of goals, and alignment method from organizational complexity, regulation, dependency, and evidence needs. Treat these as local design choices rather than universal OKR requirements. [BB-C08-S01] Symptom: \"Our strategy document is a long list of 'priorities' and vague goals.\" Diagnosis: Rumelt's “bad strategy” is one lens: the document may lack a decision-relevant diagnosis, a guiding policy, or coherent actions. Multiple interacting challenges can matter, and the framework does not prove there is one biggest challenge. Action: Use the kernel to ask: 1) Diagnosis: Which challenge or interaction is most consequential under current evidence? 2) Guiding policy: What approach addresses it and what alternatives were rejected? 3) Coherent actions: Which mutually reinforcing actions, owners, constraints, and stop rules implement the policy? Invite challenge rather than forcing premature consensus. [BB-C08-S05] ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-1-mission-vision-and-values-as-strategic-inputs", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "1. Mission, Vision, and Values as Strategic Inputs", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-1-mission-vision-and-values-as-strategic-inputs", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-1-mission-vision-and-values-as-strategic-inputs", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Mission, Vision, and Values as Strategic Inputs Purpose and Commitments" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Mission, envisioned future, and values can clarify purpose and behavioral commitments, but they are not strategy or a prerequisite taxonomy for every organization. Strategy still requires evidence, choices, trade-offs, resources, and coherent action. [BB-C08-S04]" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define Your Mission (The \"Why\"): Your enduring purpose. It's not a goal to be achieved, but a pursuit. Illustrative mission: \"Make vital information easy for people to find and use.\" 2. Define Your Envisioned Future (The \"What\"): A clear, ambitious picture of a desired future state; it is not an operating target. Illustrative vision: \"A useful computer in every workplace and home.\" 3. Define Behavioral Commitments: Specify observable, job-related behaviors and how tensions among values will be resolved. Do not use values as stand-alone hiring, promotion, discipline, or termination criteria. Illustrative values: \"Judgment,\" \"Communication,\" and \"Curiosity,\" each paired with observable behaviors. Figure 8.1. Strategy-to-learning operating system. Purpose, envisioned future, and values inform rather than mechanically cause strategy; choices and resources become a portfolio, while OKRs and KPIs supply evidence for review and adaptation. [BB-C08-S04] [BB-C08-S05] [BB-C08-S06] Text equivalent: Purpose, envisioned future, and behavioral commitments inform strategy. A diagnosis and coherent choices allocate resources to an initiative portfolio. OKRs express periodic outcome hypotheses and KPIs monitor ongoing measures and guardrails. Operating reviews update forecasts and lead to continuation, stopping, reallocation, or strategic adaptation. Source note: Original synthesis combining vision, strategy-kernel, OKR-practice, and metric-dysfunction sources; arrows are decision links, not proven causal effects. [BB-C08-S01] [BB-C08-S04] [BB-C08-S05] [BB-C08-S06]" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use purpose, an envisioned future, and behavioral commitments to clarify choices and trade-offs, not to substitute for strategy, resources, or decision rights. - Translate each value into observable, job-related behavior and define how competing values, dissent, accessibility, and escalation will be handled. - Review whether budgets, incentives, operating decisions, and observed behavior support the stated commitments before using them in people processes." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Mission, vision, and values are practitioner inputs; they do not establish strategy quality, employee commitment, or financial performance. - A values statement can be vague, contested, inaccessible, or contradicted by systems and incentives; do not treat agreement or recall as proof of impact. - Employment use requires job-related criteria, consistent documentation, due process, accessibility, and People/HR and legal review." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Use Chapter 3's diagnosis and choices to test whether purpose informs a real strategic trade-off. - Output: Use OKRs only when a periodic goal system is appropriate; purpose does not require OKRs. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-2-evidence-based-goal-setting-smart-fast", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "2. Evidence-Based Goal Setting (SMART & FAST)", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-2-evidence-based-goal-setting-smart-fast", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-2-evidence-based-goal-setting-smart-fast", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Evidence-Based Goal Setting Effective Target Definition" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-2", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-2", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-2", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "SMART is a widely used mnemonic, not a complete theory of goal effects. Its wording varies: the UF/IFAS account uses Specific, Measurable, Attainable, Relevant, and Time-bound and traces the approach to Doran's 1981 article. [BB-C08-S07] This chapter uses “Achievable,” a common variant, while treating every letter as a design prompt rather than proof that a goal is valid. Goal-setting research examines mechanisms and moderators rather than supporting a universal checklist, while a Harvard working paper documents risks including narrow focus, unethical behavior, distorted risk preferences, cultural effects, and reduced intrinsic motivation. [BB-C08-S09] [BB-C08-S10] The appropriate difficulty and review design therefore depend on commitment, ability, task complexity, feedback, incentives, controllability, learning, conflicting goals, potential harm, and the evidence available to the team. - S pecific, M easurable, A chievable, R elevant, T ime-bound." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-2", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-2", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use SMART and FAST as prompts for a goal conversation: define the decision, baseline, owner, time horizon, evidence, controllability, guardrails, and review rule before selecting letters, scoring, or transparency conventions." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-contrarian-thinking-the-problem-with-achievable", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: The Problem with \"Achievable\"", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-contrarian-thinking-the-problem-with-achievable", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-contrarian-thinking-the-problem-with-achievable", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Treat the \"A\" in SMART as an invitation to set a credible commitment rather than an automatic ceiling. Teams can use stretch goals when they are paired with clear learning loops and safeguards. The FAST framework offers one alternative for dynamic environments; Sull and Sull define it as Frequent discussions, Ambitious scope, Specific metrics, and Transparency. [BB-C08-S08] F requently Discussed: Choose a review rhythm that can change a decision; weekly is not universal. A mbitious: Stretch only when capacity, learning, safety, quality, and incentive effects are acceptable. S pecific: They are quantified as metrics and milestones. T ransparent: Make goals and progress visible to the people who need them, subject to privacy, confidentiality, labor, security, and legal constraints; transparency does not require universal public disclosure." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-2", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-2", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define a goal's decision, baseline, owner, controllability, capacity, time horizon, and guardrails before debating whether it is SMART or FAST. - Use stretch only when learning, quality, safety, workload, incentives, and affected-party risks are visible and reviewable. - Treat goal progress as evidence for a decision, not as a standalone performance judgment or proof that the target caused an outcome." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-2", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-2", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- SMART and FAST are practitioner mnemonics; neither guarantees valid targets, motivation, alignment, or performance. - Goal effects depend on commitment, ability, task complexity, feedback, competing goals, incentives, culture, and potential harm. - Transparency, ambition, and time bounds must respect privacy, confidentiality, labor, security, accessibility, and legal constraints." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-2", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-2", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-2", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Use the organization's purpose, strategy, evidence, and constraints to shape goals; vision is one input, not a prerequisite. - Output: Use OKRs only after confirming that an outcome-based goal system fits the work. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-3-good-strategy-bad-strategy-rumelt-s-kernel", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "3. \"Good Strategy / Bad Strategy\" (Rumelt's Kernel)", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-3-good-strategy-bad-strategy-rumelt-s-kernel", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-3-good-strategy-bad-strategy-rumelt-s-kernel", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Good Strategy / Bad Strategy The Kernel of Strategy" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-3", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-3", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-3", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Rumelt's strategy kernel distinguishes strategy from a list of aspirations and frames it around a diagnosis, a guiding policy, and coherent action. [BB-C08-S05]" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-3", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-3", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "To use Rumelt's practitioner kernel, articulate three components while preserving evidence and uncertainty: 1. A Diagnosis: An interpretation of the challenge and causal structure. A strategy can address interacting constraints; do not force one “single biggest” problem when the system evidence does not support it. 2. A Guiding Policy: The overall approach to dealing with the challenge identified in the diagnosis. It's not a list of action steps; it's the strategic guardrails that will guide action. Constructed examples: (e.g., \"We will compete on customer experience, not price,\" or \"We will leverage our developer ecosystem to build a platform.\"). 3. Coherent Actions: A focused set of consistent actions and resource allocations that implement the guiding policy, with dependencies, owners, evidence, and adaptation. [BB-C08-S05]" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-3", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-3", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- State the challenge, alternatives considered, guiding policy, coherent actions, owners, constraints, and evidence before turning strategy into goals. - Treat the diagnosis as an interpretation to test; update it when new evidence, dependencies, or external conditions change. - Fund and sequence only the actions the organization can support, with decision dates and stop, continue, or adapt rules." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-3", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-3", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The kernel is a practitioner framing, not a validated universal strategy process or causal model. - A diagnosis can be wrong, incomplete, politically contested, or too narrow for interacting constraints; invite dissent and alternative explanations. - Coherent action can still fail through insufficient capability, resources, execution, regulation, or changing conditions." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-3", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-3", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-3", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Use Chapter 3's external and internal analysis to test the diagnosis, while preserving alternative explanations and uncertainty. - Output: Use the guiding policy and coherent actions to inform goals or other operating commitments when those mechanisms fit the work. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-4-objectives-and-key-results-okrs", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "4. Objectives and Key Results (OKRs)", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-4-objectives-and-key-results-okrs", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-4-objectives-and-key-results-okrs", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objectives and Key Results (OKRs) Agile Strategy Execution" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-4", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-4", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-4", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "OKRs developed through Intel management practice and were later popularized more broadly. They pair qualitative objectives with measurable results, but cadence, number, scoring, alignment, and incentive treatment are design choices. An OKR can express an outcome hypothesis; it does not allocate resources or prove impact. [BB-C08-S01]" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-4", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-4", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define an Objective: State the direction and decision horizon; quarterly and inspirational are options, not requirements. 2. Define Measurable Key Results: Choose a small number that tests the intended outcome, using baselines, definitions, owners, data lineage, guardrails, and controllability. Results do not “prove” the objective or causality. Constructed output example: \"Launch 5 new marketing campaigns.\" Constructed outcome example: \"Increase marketing-qualified leads (MQLs) from 500 to 1,000.\" 3. Negotiate Alignment: Connect enterprise and team commitments vertically and horizontally; resolve dependencies, capacity, shared measures, and decision rights rather than mechanically cascading. 4. Review and Reflect: Choose scoring and incentive treatment locally. Practitioner conventions such as decimal scores are not validated performance thresholds. Separate committed and stretch work, record why a result moved, and do not infer ambition or employee performance from one score. [BB-C08-S01] [BB-C08-S06] Figure 8.2. Negotiated OKR alignment and learning loop. Enterprise priorities and team commitments meet through dependency, capacity, and guardrail negotiation rather than one-way cascade. [BB-C08-S01] [BB-C08-S06] Text equivalent: Enterprise strategy sets outcome priorities; teams propose contributions based on local evidence. Leaders and teams negotiate dependencies, capacity, and guardrails before committing. Reviews examine evidence and forecasts, then continue, stop, or reallocate work and update priorities. Source note: Original synthesis of OKR practice with an incentive/gaming control; it does not claim one alignment design is superior. [BB-C08-S01] [BB-C08-S06]" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-4", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-4", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use OKRs to make a bounded outcome hypothesis visible after strategy, resources, dependencies, authority, and capacity are explicit. - Negotiate vertical and horizontal commitments; record local constraints, guardrails, data lineage, and what will happen if the result moves. - Review OKRs with forecasts, financials, operations, people, safety, and risk evidence; stop, continue, or reallocate rather than merely rescore." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-4", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-4", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- OKRs are a practitioner goal system, not a universal operating model, causal test, resource-allocation method, or performance ranking. - Cascading, quarterly cadence, decimal scoring, stretch goals, and compensation separation are conventions that can fail or create gaming. - A result can move because of external conditions, measurement changes, dependencies, or unrelated work; do not infer ambition, causality, or employee value from one score." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-4", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-4", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-4", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: OKRs should be reconciled with enterprise strategy, vision, local evidence, delegated authority, regulation, dependencies, and capacity; some operational or control objectives arise from obligations rather than top-down derivation. - Output: OKR evidence is one input to a Quarterly Business Review (QBR) alongside financials, forecasts, customers, operations, people, safety, risk, controls, and external change. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-5-key-performance-indicators-kpis-vs-okrs", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "5. Key Performance Indicators (KPIs) vs. OKRs", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-5-key-performance-indicators-kpis-vs-okrs", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-5-key-performance-indicators-kpis-vs-okrs", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "KPIs vs. OKRs Measurement for Clarity" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-5", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-5", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-5", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "KPIs and OKRs serve overlapping measurement purposes. Doerr's practitioner account supports the Objective/Key Result structure and distinguishes committed from stretch practice. [BB-C08-S01] The comparison used here—KPIs as selected ongoing measures and OKRs as periodic objective/result commitments—is an author synthesis. A measure may serve both uses, and neither label establishes causal leverage, target validity, controllability, or data quality." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-5", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-5", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Establish Your Health Dashboard (KPIs): Define a manageable set of critical health metrics for each part of the business. These are your \"business as usual\" indicators; the appropriate number depends on the decision, work, and evidence. 2. Investigate a “Red” KPI: Deterioration can trigger diagnosis, but an OKR is only one response. First verify the definition, data, materiality, cause, controllability, urgency, existing owner, and whether incident response, corrective action, service management, risk control, or a project is more appropriate. KPI: Customer Churn Rate (the lagging indicator of health). Objective: \"Dramatically improve customer loyalty and reduce churn.\" Key Result: \"Reduce monthly customer churn rate from 5% to 2.5% this quarter.\" 3. Choose the Mechanism: Use OKRs only when a periodic objective/result system improves focus and learning. Initiatives, forecasts, service levels, risk controls, or project milestones may be more appropriate for some work." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-5", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-5", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define each measure's decision, denominator, owner, lineage, latency, uncertainty, controllability, and guardrail before calling it a KPI or Key Result. - Investigate a deteriorating KPI before choosing an OKR; an incident response, service level, risk control, forecast, or project may fit better. - Use countermetrics and affected-party evidence so improvement in one measure does not conceal quality, safety, customer, workforce, or equity harm." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-5", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-5", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- KPI and OKR labels are overlapping management conventions, not an ontology of health versus change or proof of causal leverage. - A target can be invalid, gamed, uncontrollable, or based on poor data; a visible score can narrow attention rather than improve the underlying work. - Some obligations require ongoing controls or professional judgment and should not be converted into periodic goals merely for comparability." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-5", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-5", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-5", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Use key drivers from your business model, Financial Analysis (Chapter 4) , Operations (Chapter 6) , customer evidence, and risk or control obligations as inputs to KPI selection. - Output: A deteriorating KPI may become a QBR discussion item, but the appropriate response may instead be an incident, control, service-level action, forecast, or project. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-6-the-balanced-scorecard-bsc", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "6. The Balanced Scorecard (BSC)", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-6-the-balanced-scorecard-bsc", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-6-the-balanced-scorecard-bsc", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Balanced Scorecard (BSC) Holistic Performance Management" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-6", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-6", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-6", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Balanced Scorecard was developed by Kaplan and Norton as a strategic performance-management framework that broadens attention beyond lagging financial indicators across four perspectives. It can expose neglected dimensions and strategy hypotheses, but it does not ensure long-term health, causal balance, good targets, or resistance to gaming. [BB-C08-S03]" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-6", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-6", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For your strategy, define goals, metrics, and initiatives for each of the four perspectives: 1. Financial: \"To succeed financially, how should we appear to our shareholders?\" (e.g., Revenue Growth, Profitability, ROIC). 2. Customer: \"To achieve our vision, how should we appear to our customers?\" (e.g., Customer Satisfaction, NPS, Market Share). 3. Internal Business Processes: \"To satisfy our shareholders and customers, what business processes must we excel at?\" (e.g., Operational Efficiency, Quality, Cycle Time). 4. Learning and Growth: \"To achieve our vision, how will we sustain our ability to change and improve?\" (e.g., Employee Skills, Technology Infrastructure, Culture). Figure 8.3. Balanced Scorecard strategy hypotheses. The arrows are relationships to test, not established causal chains or guaranteed financial outcomes. [BB-C08-S03] Text equivalent: Learning-and-growth, internal-process, customer, and financial perspectives are connected as hypothesized strategy logic. Review evidence for each link, adverse effects, missing measures, and whether the proposed driver is controllable before reallocating resources. Source note: Original redraw of the four Balanced Scorecard perspectives; strategy-map arrows are hypotheses. [BB-C08-S03]" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-contrarian-thinking-bsc-vs-okrs", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Contrarian Thinking: BSC vs. OKRs", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-contrarian-thinking-bsc-vs-okrs", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-contrarian-thinking-bsc-vs-okrs", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Balanced Scorecard and OKRs serve distinct purposes: the BSC emphasizes a balanced performance system, while OKRs provide a periodic goal-setting cadence. One possible design is to use the four BSC perspectives when testing whether company-level OKRs are balanced rather than focused only on financial results; local evidence should determine whether that design helps. [BB-C08-S01] [BB-C08-S03]" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-6", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-6", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the four perspectives to test whether a strategy review is ignoring customer, process, capability, or financial consequences. - Define measures, owners, baselines, data lineage, targets, guardrails, and review decisions for each perspective rather than filling a template. - Treat arrows and driver relationships as hypotheses; update or remove them when evidence, trade-offs, or unintended effects do not support the proposed logic." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-6", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-6", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The Balanced Scorecard is a practitioner framework; the perspectives do not guarantee balance, performance, causality, or long-term health. - Strategy maps can imply causal certainty, overproduce measures, or hide weak definitions, external drivers, and uncontrollable outcomes. - A scorecard can be gamed or used as an employment or incentive instrument without adequate job-related criteria, safeguards, and review." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-6", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-6", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-6", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Use the organization's overall Strategy (Chapter 3) , stakeholder outcomes, operating risks, and financial constraints to decide which quadrants or perspectives matter. - Output: BSC measures can supply candidate KPIs and review questions; they do not automatically belong on a health dashboard. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-7-the-hedgehog-concept-jim-collins", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "7. The Hedgehog Concept (Jim Collins)", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-7-the-hedgehog-concept-jim-collins", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-7-the-hedgehog-concept-jim-collins", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Hedgehog Concept Finding Your Strategic Focus" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-7", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-7", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-7", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Hedgehog Concept is Collins's practitioner model of deep understanding at the intersection of three circles: what the organization is passionate about, what it can be best in the world at, and what drives its economic or resource engine. [BB-C08-S11] The account derives the concept from retrospective comparison of selected companies. Denrell's peer-reviewed analysis shows why samples focused on survivors and successful organizations can produce misleading beliefs about management practices. [BB-C08-S12] Use the concept as a reflection and hypothesis-building model, not evidence that the intersection causes performance." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-7", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-7", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The three prompts below are an author adaptation of Collins's circles that adds feasibility, customer, risk, and externality checks. 1. What you are deeply passionate about: What is your core purpose and motivation? What work do you love? 2. Where could capabilities create differentiated value: Test the customer, competitor, capability, complementary-asset, and imitation evidence; “best in the world” is not a required or always feasible claim. 3. What drives the economics: Identify several value and cost drivers with cash, risk, externality, and guardrail measures rather than forcing one denominator. Treat the intersection as a strategic hypothesis to compare with alternatives, not a transformation guarantee." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-7", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-7", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the three prompts to compare strategic alternatives with customer, capability, economic, risk, externality, and implementation evidence. - Separate passion, differentiated capability, and economic logic; do not force one denominator or treat “best in the world” as a feasible requirement. - Record rejected alternatives, uncertainty, resource needs, and review dates before converting a Hedgehog hypothesis into policy or goals." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-7", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-7", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The Hedgehog Concept is a retrospective practitioner model, not proof that an intersection causes durable performance. - Survivor and success-sample bias can make selected management practices look more general or effective than they are. - A compelling focus can become tunnel vision if it ignores customer harm, regulation, capability gaps, externalities, or changing conditions." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-7", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-7", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-7", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Use purpose and behavioral commitments, capabilities from a VRIO Analysis (Chapter 3) , financial drivers from Financial Analysis (Chapter 4) , and customer evidence as inputs to a focus hypothesis. - Output: A provisional Hedgehog hypothesis can inform candidate guiding policies in \"Good Strategy\" (Framework 3) and questions for company-level OKRs (Framework 4) ; it does not supply either automatically. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-8-the-vsem-framework-vision-strategy-execution-metrics", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "8. The VSEM Framework (Vision, Strategy, Execution, Metrics)", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-8-the-vsem-framework-vision-strategy-execution-metrics", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-8-the-vsem-framework-vision-strategy-execution-metrics", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The VSEM Framework Integrated Execution Model" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-8", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-8", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-8", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "VSEM is used here as an author synthesis connecting vision, strategy, execution, and metrics. It is a mnemonic, not a canonical complete management system; linearity can conceal diagnosis, resources, dependencies, incentives, risk, and adaptation." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-8", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-8", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use these four prompts iteratively, not as a required sequence: 1. Vision: Where are we going? (The desired future state). 2. Strategy: What's our plan to get there? (The guiding policy and coherent actions). 3. Execution: What funded work, operating commitments, controls, or initiatives are implementing the strategy? 4. Metrics: What evidence and measures will show progress, health, risk, and unintended effects? Use the four questions as a traceability check, then add budget/capacity, owners, dependencies, decision rights, forecasts, guardrails, and review." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-8", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-8", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use VSEM as a traceability check: can the team connect the intended future to choices, funded work, measures, owners, and review decisions? - Add diagnosis, budget, capacity, dependencies, decision rights, forecasts, guardrails, and adaptation rather than treating the four labels as a complete process. - Use missing links to ask a bounded question and assign an owner; do not infer execution quality from a completed mnemonic." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-8", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-8", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- VSEM is an author synthesis, not a canonical or empirically validated management system. - A linear vision-to-metrics sequence can hide trade-offs, resources, incentives, obligations, power, risk, and learning. - The mnemonic does not establish that a metric is valid, that execution caused an outcome, or that one operating design fits every organization." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-8", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-8", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-8", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: This framework synthesizes the purpose inputs in Mission, Vision, and Values (Framework 1) and Good Strategy (Framework 3) . - Output: It can expose missing links; it does not replace the execution operating system above. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-9-goal-cascading-alignment-models", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "9. Goal Cascading & Alignment Models", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-9-goal-cascading-alignment-models", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-9-goal-cascading-alignment-models", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal Cascading & Alignment Organizational Alignment" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-9", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-9", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-9", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal alignment is an author-created coordination aid. Once enterprise priorities are set, teams need vertical and horizontal coordination. Strict cascade and alignment networks are two stylized options; matrix, product, regulated, and professional organizations may need different designs." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-9", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-9", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. The \"Strict Cascade\" (Traditional): The CEO's Key Result becomes a direct manager's Objective, which is then cascaded down to their team. Potential benefit: Can make an intended hierarchy of contributions visible when metric definitions, controllability, dependencies, and decision rights are explicit; it does not ensure mathematical or behavioral alignment. Con: Can feel very top-down and disempowering. A strict cascade can leave teams with measures they cannot fully control. 2. Alignment Network: The company sets high-level priorities and teams propose contributions based on local evidence and dependencies. Potential benefit: Can use local knowledge and improve ownership when decision rights, capacity, and conflict resolution are clear. Con: An alignment network can increase negotiation cost or ambiguity when decision rights, conflict resolution, and strategic context are unclear." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-9", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-9", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Choose cascade, network, portfolio, service-level, control, or professional-judgment mechanisms based on work dependencies, authority, capacity, and risk. - Make cross-team commitments negotiable and explicit: define owners, interfaces, shared measures, conflict routes, decision rights, and review dates. - Test whether local contributions improve the enterprise decision without forcing teams to inherit measures they cannot control." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-9", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-9", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Cascade and alignment networks are stylized operating designs, not universal solutions or proof of ownership, trust, or performance. - Strict cascade can create top-down goals, metric distortion, and accountability without control; networks can create negotiation cost and ambiguity. - Some work requires service levels, safety controls, regulatory duties, cases, portfolios, or professional judgment rather than OKRs." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-9", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-9", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-9", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Use company-level OKRs (Framework 4) only where a periodic outcome system fits the work. - Output: A proposed set of team-level contributions, dependencies, and conflicts for review. Some teams may require service levels, controls, cases, portfolios, or professional judgment, and no cascade is assumed to drive every team's daily work. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-10-contrarian-thinking-the-case-against-mission-statements", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "10. Contrarian Thinking: The Case Against Mission Statements", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-10-contrarian-thinking-the-case-against-mission-statements", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-10-contrarian-thinking-the-case-against-mission-statements", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Contrarian View: Against Mission Statements Critique & Alternative" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-10", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Overview", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-10", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-10", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Mission and values can be stress-tested with this author-created diagnostic; it is not evidence that mission statements generally fail. Mission and values statements can be vague, contradicted, or unused, but the available chapter sources do not justify broad claims that they fail or lack impact. Evaluate a statement by clarity, credibility, decision use, stakeholder legitimacy, and alignment with actual systems." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "How to Apply", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-10", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-10", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the questions below with affected people and decision owners. Record what would change in decisions, systems, resources, incentives, and behaviors; then review the evidence rather than treating agreement with a statement as proof of value." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-critique", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "The Critique", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-critique", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-critique", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Is it understood? Test whether relevant people can explain the statement's meaning; verbatim recall is not the only validity test. Does it inform action? Ask what a manager or employee would do differently because of the statement. Is it credible? Compare it with actual incentives, resource choices, controls, and observed behavior." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-alternative-a-measurable-vision-and-behavioral-values", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "The Alternative: A Measurable Vision and Behavioral Values", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-alternative-a-measurable-vision-and-behavioral-values", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-alternative-a-measurable-vision-and-behavioral-values", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Clarify the role: A mission can express enduring purpose; an envisioned future can express direction. Neither must be reduced to a measurable target, and neither substitutes for strategy. 2. Make Values Behavioral: Don't just state a value; describe the specific, observable behaviors that represent it. Vague Value: \"We value communication.\" Constructed behavioral example: “Share relevant information in accessible form, seek understanding before reacting, and raise material concerns through protected channels.” Validate job relevance, culture/accessibility, conflicts, adverse patterns, and employee rights before using a behavior in people decisions." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "So What for Managers", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-10", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-10", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ask what a mission or value changes in a real decision, resource choice, control, or behavior; remove language that cannot guide action. - Validate clarity, credibility, legitimacy, accessibility, conflicts, and adverse patterns across affected roles before adoption or revision. - Keep the statement subordinate to strategy, evidence, capacity, professional duties, and approved people-process criteria." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Limits and Critiques", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-10", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-10", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- This is an author-created diagnostic, not a validated mission-quality scale or proof that statements cause performance. - A statement may be meaningful to some groups and contested or harmful to others; recall and agreement are incomplete evidence. - Values used in employment or incentive decisions require job-related criteria, consistency, documentation, due process, accessibility, and HR/legal review." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-10", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-10", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-10", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: This critique forces a more rigorous approach to defining Mission, Vision, and Values (Framework 1) . - Output: It can inform a candidate set of guiding principles for further review across the organization. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-1-outcomes-over-outputs", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 1: Outcomes over Outputs", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-1-outcomes-over-outputs", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-1-outcomes-over-outputs", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Outputs are activities or deliverables; outcomes are changes the organization seeks. The distinction is useful, but outcomes may be delayed, partly uncontrollable, or causally ambiguous, while some outputs are safety, legal, or capability obligations. Use both with guardrails and evidence rather than labeling teams by one metric." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-2-health-vs-change", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 2: Health vs. Change", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-2-health-vs-change", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-2-health-vs-change", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Ongoing control and periodic change are useful measurement purposes, but they overlap. The same measure can diagnose health, define an objective, or act as a guardrail. Define the decision, measure, denominator, owner, lineage, latency, uncertainty, controllability, and gaming risk rather than relying on the KPI/OKR label." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-3-strategy-is-about-saying-no", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Mental Model 3: Strategy is About Saying \"No\"", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-3-strategy-is-about-saying-no", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-3-strategy-is-about-saying-no", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A good strategy is not a list of things to do. It is a focused set of choices that, by definition, means not doing many other things. As Richard Rumelt states, it requires a clear diagnosis and a coherent set of actions [BB-C08-S05]. An operator's job is often to use the strategy as a filter to say \"no\" to projects and requests that, while potentially good ideas, do not align with the core strategic focus. ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-example-1-outcome-oriented-okr", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Example 1: Outcome-Oriented OKR", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-example-1-outcome-oriented-okr", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-example-1-outcome-oriented-okr", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Doerr describes Google's early use of OKRs and uses a browser example to illustrate an adoption-oriented Key Result. [BB-C08-S01] The operational lesson is that a Key Result should define the outcome to pursue rather than a fixed activity list. The chapter does not repeat the original example's numeric target because the current registry record has not been inspected at that claim level." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-example-2-how-metrics-can-drive-dysfunction", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Example 2: How Metrics Can Drive Dysfunction", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-example-2-how-metrics-can-drive-dysfunction", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-example-2-how-metrics-can-drive-dysfunction", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following composite teaching scenario illustrates the risk Kerr identifies when rewards and desired outcomes are misaligned. [BB-C08-S06] The Problem: Leaders attach promotion, budget, or recognition to a narrow metric. Managers then optimize the metric even when that behavior undermines customer, team, or long-term outcomes. The Result: Such a system can discourage collaboration and create incentives to redefine the measure instead of improving the underlying work. Lesson: A narrow metric can reward behavior that conflicts with intended outcomes; a Balanced Scorecard is one possible countermeasure, not a guarantee. [BB-C08-S03] [BB-C08-S06] ---" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-applied-exercise-run-a-constrained-strategy-review", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Applied Exercise: Run a Constrained Strategy Review", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-applied-exercise-run-a-constrained-strategy-review", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-applied-exercise-run-a-constrained-strategy-review", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Starting from a supplied strategy kernel, allocate a fixed budget and team capacity across four competing initiatives. For each, define the outcome hypothesis, owner, dependencies, one leading and one lagging measure, data lineage, guardrail, risk, decision date, and stop/scale rule. Draft one objective with measurable results, identify one gaming risk, update an operating forecast, and make a continue, stop, or reallocate recommendation with dissent and uncertainty." }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis::chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-selective-connections", "kind": "chapter", "itemSlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "itemTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "heading": "Selective Connections", "headingId": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-selective-connections", "url": "#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-selective-connections", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use Chapter 3 for diagnosis, advantage, alternatives, and strategic coherence. - Use Chapter 4 for budgets, capital allocation, and scenario economics. - Use Chapter 7 for incentives, culture, voice, and change participation. - Use Chapter 11 for initiative governance, dependencies, and change control. - Use Chapter 17 for enterprise portfolio and operating-model change. - Use Chapter 22 for metric definitions, causality, uncertainty, and review communication. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Problem Structuring", "headingId": "chapter-09-problem-structuring", "url": "#chapter-09-problem-structuring", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-executive-summary", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Executive Summary", "headingId": "chapter-09-problem-structuring-executive-summary", "url": "#chapter-09-problem-structuring-executive-summary", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter introduces a foundational management-consulting toolkit: structured problem solving. The frameworks can help an operator reduce ambiguity, develop and test competing causal explanations, and build an evidence-bounded case for a course of action. We explore issue trees, MECE as a grouping aspiration rather than a completeness guarantee, and hypothesis-driven analysis. Proficiency can improve structure and learning; it does not ensure speed, causality, or a defensible conclusion." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-manager-decision-outcomes", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Manager decision outcomes", "headingId": "chapter-09-problem-structuring-manager-decision-outcomes", "url": "#chapter-09-problem-structuring-manager-decision-outcomes", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "By the end of this chapter, you should be able to: 1. Frame a decision problem with explicit stakeholders, scope, constraints, success measures, and ethical boundaries. 2. Build and revise an issue tree without treating MECE as a guarantee of completeness. 3. Distinguish a testable working hypothesis from a predetermined answer, and specify disconfirming evidence. 4. Compare alternatives using criteria, decision and chance nodes, consequences, probabilities, trade-offs, uncertainty, sensitivity analysis, and accountable judgment. 5. Route additional evidence using break-even probability, value-of-information, reversibility, and non-compensable legal, safety, rights, or policy gates. 6. Use root-cause, risk, premortem, and assumption-mapping tools proportionately to stakes and reversibility. The governing discipline is an evidence loop: frame the decision, generate competing explanations or options, prioritize information by its decision value, test, update, and document the residual uncertainty. This loop connects ethics and stakeholder obligations in Chapter 2, strategy choices in Chapter 3, financial consequences in Chapter 4, and framework selection in Chapter 10. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-troubleshooting-guide-problem-structuring", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Troubleshooting Guide: Problem Structuring", "headingId": "chapter-09-problem-structuring-troubleshooting-guide-problem-structuring", "url": "#chapter-09-problem-structuring-troubleshooting-guide-problem-structuring", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Symptom: \"Our issue tree has over 50 boxes and is impossible to read.\" - Diagnosis: You have gone too deep, too quickly. You are mapping every possibility instead of focusing on the most probable drivers. - Action: Limit your main issue tree to 2-3 levels. For each branch, form a high-level hypothesis. Then, for the 2-3 most likely hypotheses, create separate, more detailed issue trees. This keeps your master structure clean and your analysis focused. - Symptom: \"We built a logical issue tree, but the data analysis didn't reveal a clear root cause.\" - Diagnosis: Your initial problem statement may be flawed, or you may have missed a material branch in the MECE analysis. The problem may also be external, qualitative, or multi-causal. - Action: Revisit the Problem Statement Canvas . Check whether a critical constraint or qualitative factor is missing, then add a proportionate qualitative tool such as a Fishbone Diagram and test competing causes. - Symptom: \"Our team spends weeks building a perfect, fully exhaustive MECE issue tree before starting any analysis.\" - Diagnosis: You are treating the framework as the goal rather than as a tool to accelerate learning and decision-making. - Action: Use a proportionate stopping rule: build a provisional structure, test the most consequential hypotheses, and revise it as evidence changes the decision. - Symptom: \"I presented a data-backed recommendation, but the leadership team was unpersuaded.\" - Diagnosis: The argument may be unclear, the decision criteria may be contested, or the audience may need the uncertainty and alternative made explicit. - Action: Use the Hypothesis Pyramid to label the recommendation provisional, show supporting and contrary evidence, identify the leading alternative, and state what would change the conclusion. Top-down communication improves clarity; it does not substitute for fair analysis. - Symptom: \"We've been analyzing this problem for 6 weeks and still don't have a recommendation.\" - Diagnosis: The team may lack a clear decision criterion, evidence threshold, decision date, or stopping rule. - Action: Invoke the Decision Criteria Weighting Model (Framework 9) . Agree on criteria, identify unknowns that could change the choice, and spend additional analysis time only where its expected decision value justifies the delay. High-stakes or irreversible decisions generally require more evidence and independent challenge than reversible tests. - Symptom: \"Different stakeholders keep redefining the problem mid-project, causing scope creep and confusion.\" - Diagnosis: The decision, evidence, authority, or affected-party frame may have changed; a missed alignment conversation is one possible explanation. - Action: Pause only the work made obsolete by the scope dispute. Reconfirm the Problem Statement Canvas (Framework 6) with decision owners and affected stakeholders, document what changed and why, and reset evidence needs, responsibilities, and timing. A material change deserves governance; new evidence should not be blocked by a ceremonial sign-off. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-1-issue-tree-templates", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "1. Issue Tree Templates", "headingId": "chapter-09-problem-structuring-1-issue-tree-templates", "url": "#chapter-09-problem-structuring-1-issue-tree-templates", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Issue Trees Problem Decomposition" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-overview", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-09-problem-structuring-overview", "url": "#chapter-09-problem-structuring-overview", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "An issue tree is a practitioner tool for decomposing a complex question into smaller components that can be investigated against evidence. [BB-C09-S01] It can make analytical coverage and evidence needs visible, but the tree is only as good as its framing and branch logic; it cannot ensure that every important cause or stakeholder concern has been captured." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-evidence-routing-visual", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Evidence-routing visual", "headingId": "chapter-09-problem-structuring-evidence-routing-visual", "url": "#chapter-09-problem-structuring-evidence-routing-visual", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Profitability issue-tree example (constructed). The structure begins with an accounting identity, then routes branches to testable questions. It is not evidence that these are the only causes or that a fixed depth is sufficient. Figure 9.1. Profitability issue-tree evidence-routing tree. This constructed diagram routes a decision through revenue, cost, capacity, evidence ownership, alternatives, and a revision loop; it is not a complete causal model. Text equivalent: Decompose profit into revenue and cost. Revenue can be examined through price, volume, and mix; cost through variable, fixed, step, and capacity-related components. Each endpoint becomes a falsifiable question with an owner, definition, evidence source, alternative explanation, and stop condition. The tree must be revised when material overlap, gaps, stakeholder effects, or new evidence appear." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-how-to-apply", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-09-problem-structuring-how-to-apply", "url": "#chapter-09-problem-structuring-how-to-apply", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following provisional issue-tree procedure connects a decision frame to evidence work; depth and stopping rules should reflect consequence, uncertainty, information value, reversibility, and capacity. 1. Start with the Core Problem: State the primary question at the far left (e.g., \"How can we increase profits by $10M?\"). 2. Decompose into Branches: Break the problem into its main components, using MECE (Framework 2) as a scope-bounded challenge. For a profitability question, Profits = Revenue - Costs is one constructed accounting starting point, not a complete causal model. 3. Continue Decomposing: Break down each branch into sub-drivers only far enough to define a decision-relevant test, owner, measure, or alternative. For example, Revenue = Price Volume may be a useful identity, but depth is not a universal 2-4-level requirement. 4. Formulate Hypotheses: Each endpoint of the tree should represent a testable hypothesis (e.g., \"Have our prices declined relative to competitors?\"). Figure 9.2. Iterative issue-tree evidence loop. A provisional decomposition routes competing hypotheses to proportionate tests; evidence can revise the tree, recommendation, or decision boundary rather than merely confirm the initial frame. Text equivalent: Frame the decision and stakeholders, build a provisional decomposition, define competing hypotheses, prioritize tests by consequence and information value, evaluate evidence, and then update both the tree and the recommendation. Record remaining uncertainty and dissent. Source note: Author synthesis informed by an academic account of issue decomposition and hypothesis-driven analysis. [BB-C09-S01]" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-contrarian-thinking-when-to-break-your-issue-tree", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Contrarian Thinking: When to Break Your Issue Tree", "headingId": "chapter-09-problem-structuring-contrarian-thinking-when-to-break-your-issue-tree", "url": "#chapter-09-problem-structuring-contrarian-thinking-when-to-break-your-issue-tree", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Issue trees are useful when decomposition improves the decision, but rigid use can create analysis paralysis or hide relationships that do not fit a hierarchy. Build a provisional tree, retain credible alternative explanations, test consequential branches, and revise the structure as evidence arrives. The tree is a tool, not the goal." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-09-problem-structuring-so-what-for-managers", "url": "#chapter-09-problem-structuring-so-what-for-managers", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use an issue tree to expose decision-relevant branches, evidence owners, alternatives, and disconfirming tests; do not build a tree for completeness alone. - Prioritize branches by consequence, uncertainty, information value, and reversibility before commissioning analysis. - Reframe the tree when evidence, stakeholder effects, constraints, or the decision itself changes." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-09-problem-structuring-limits-and-critiques", "url": "#chapter-09-problem-structuring-limits-and-critiques", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- An issue tree is a practitioner structure, not proof that the listed branches are exhaustive, independent, or causal. - Hierarchies can hide interactions, feedback, power, qualitative evidence, and obligations that do not fit the chosen decomposition. - A tree can create false precision or analysis paralysis when depth, branch labels, or stopping rules are not tied to a decision." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-connections", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-09-problem-structuring-connections", "url": "#chapter-09-problem-structuring-connections", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: The Problem Statement Canvas (Framework 6) provides a revisable decision frame for the head of the tree. - Output: Testable endpoints can become working hypotheses in the Hypothesis Pyramid (Framework 3) or another evidence plan. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-2-the-mece-principle", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "2. The MECE Principle", "headingId": "chapter-09-problem-structuring-2-the-mece-principle", "url": "#chapter-09-problem-structuring-2-the-mece-principle", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "MECE Principle Analytical Rigor" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-overview-2", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-09-problem-structuring-overview-2", "url": "#chapter-09-problem-structuring-overview-2", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Pronounced \"mee-see,\" MECE stands for Mutually Exclusive, Collectively Exhaustive. [BB-C09-S02] In this chapter it is used as a scope-bounded organizing principle: categories should minimize overlap and cover the material universe defined for the analysis. - Mutually Exclusive: The components are distinct and have no overlap. This reduces double-counting within the defined scope. - Collectively Exhaustive: Components aim to cover the material aspects of the defined analytical universe. Completeness remains a judgment to challenge, not a property the label can prove." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-09-problem-structuring-how-to-apply-2", "url": "#chapter-09-problem-structuring-how-to-apply-2", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For any set of categories in your analysis, apply two tests: 1. The \"No Overlap\" Test (ME): Could any single item fit into more than one of your categories? If yes, your categories are not mutually exclusive. Example: Segmenting customers as \"Large\" and \"Strategic\" is not ME, because a customer could be both. 2. The \"No Gaps\" Test (CE): Do your categories cover the full universe you are analyzing? If not, they are not collectively exhaustive. Example: Segmenting customers as \"Large\" and \"Medium\" is not CE, because you have missed \"Small\" businesses." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-contrarian-thinking-the-80-20-rule-vs-pure-mece", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Contrarian Thinking: The 80/20 Rule vs. Pure MECE", "headingId": "chapter-09-problem-structuring-contrarian-thinking-the-80-20-rule-vs-pure-mece", "url": "#chapter-09-problem-structuring-contrarian-thinking-the-80-20-rule-vs-pure-mece", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "MECE is an organizing ideal, not a universal proof of validity. The appropriate stopping point depends on stakes, reversibility, evidence quality, and the cost of a missed branch. Record known overlaps and exclusions, and invite an independent challenge for high-consequence decisions." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-09-problem-structuring-so-what-for-managers-2", "url": "#chapter-09-problem-structuring-so-what-for-managers-2", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the analytical universe, unit of analysis, time horizon, and materiality threshold before testing overlap or coverage. - Use MECE as a challenge question for double-counting and material gaps, then invite domain experts and affected stakeholders to test the boundary. - Record exclusions, overlaps, unresolved categories, and the decision consequence of a missed branch." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-09-problem-structuring-limits-and-critiques-2", "url": "#chapter-09-problem-structuring-limits-and-critiques-2", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- MECE is an organizing ideal, not a guarantee that categories are truly independent, complete, or decision-relevant. - Some systems are interactive, adaptive, or politically contested; forcing them into mutually exclusive buckets can hide important relationships. - A neat classification can still support a false premise, weak evidence, or an illegitimate decision." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-connections-2", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-09-problem-structuring-connections-2", "url": "#chapter-09-problem-structuring-connections-2", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Apply MECE as a structuring diagnostic to an Issue Tree (Framework 1) or another purpose-bounded decomposition. - Output: A documented coverage rationale makes a recommendation easier to inspect, but it does not make the recommendation comprehensive or correct. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-3-hypothesis-pyramid-structure", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "3. Hypothesis Pyramid Structure", "headingId": "chapter-09-problem-structuring-3-hypothesis-pyramid-structure", "url": "#chapter-09-problem-structuring-3-hypothesis-pyramid-structure", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Hypothesis Pyramid Building a Defensible Argument" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-overview-3", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-09-problem-structuring-overview-3", "url": "#chapter-09-problem-structuring-overview-3", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Once you have structured a problem, you need to communicate the current answer. Pyramid logic places a governing summary above logically similar, logically ordered supporting ideas. [BB-C09-S02] During analysis, the governing thought should remain a falsifiable working hypothesis, paired with credible alternatives and evidence that could disconfirm it. During communication, distinguish observed facts, estimates, assumptions, and judgment." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-argument-structure-visual", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Argument-structure visual", "headingId": "chapter-09-problem-structuring-argument-structure-visual", "url": "#chapter-09-problem-structuring-argument-structure-visual", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Provisional hypothesis pyramid (constructed). The governing thought is a current recommendation, not a predetermined answer. Supporting reasons must be logically grouped and evidence-labeled; credible alternatives, counterevidence, and decision conditions remain visible. [BB-C09-S02] Figure 9.3. Provisional hypothesis pyramid with alternatives and evidence. This author-created adaptation keeps the recommendation, supporting reasons, counterevidence, uncertainty, and reversal condition visible; it does not prove the recommendation. Text equivalent: Place the current recommendation at the top. Under it, group the minimum supporting reasons required by the decision. Link each reason to facts, estimates, assumptions, uncertainty, and counterevidence. Maintain at least one credible alternative and state the evidence or threshold that would change the recommendation." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-09-problem-structuring-how-to-apply-3", "url": "#chapter-09-problem-structuring-how-to-apply-3", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. State a Provisional Governing Thought: Write the current answer to the core question and label its confidence (for example, \"Current recommendation: prepare an orderly UK-market exit, subject to validation of customer, workforce, regulatory, and valuation assumptions\"). 2. State Alternatives and Disconfirming Evidence: Name the strongest plausible alternative and specify what evidence would change the recommendation before gathering more confirming data. 3. Provide Supporting Reasons: Group the main reasons with minimal material overlap and gaps. The number of reasons should follow the logic, not an arbitrary rule. 4. Back Each Reason with Evidence: Identify facts, estimates, assumptions, counterevidence, and unresolved uncertainty. Evidence changes confidence; it rarely \"proves\" a business recommendation. Top-down communication is often efficient for decision makers, while bottom-up or chronological explanation may be more appropriate when the reasoning process, trust, or technical detail is itself consequential." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-contrarian-thinking-data-doesn-t-speak-for-itself", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Contrarian Thinking: Data Doesn't Speak for Itself", "headingId": "chapter-09-problem-structuring-contrarian-thinking-data-doesn-t-speak-for-itself", "url": "#chapter-09-problem-structuring-contrarian-thinking-data-doesn-t-speak-for-itself", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Two leaders can reasonably interpret the same evidence differently because objectives, risk tolerance, priors, and affected interests differ. Do not use a pyramid to rationalize a predetermined answer. Make the decision criteria visible, steelman the leading alternative, document dissent, and use independent challenge when incentives could bias the analysis." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-09-problem-structuring-so-what-for-managers-3", "url": "#chapter-09-problem-structuring-so-what-for-managers-3", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- State the current recommendation, confidence, strongest alternatives, decision criteria, and evidence that would change the recommendation. - Separate observations, estimates, assumptions, uncertainty, and judgment so audiences can challenge the reasoning rather than only the conclusion. - Use the smallest set of logically grouped supporting reasons that the decision requires; do not manufacture a fixed number of branches." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-09-problem-structuring-limits-and-critiques-3", "url": "#chapter-09-problem-structuring-limits-and-critiques-3", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Pyramid structure improves inspectability of an argument but does not establish that premises are true or that a recommendation will work. - Top-down communication can conceal omitted evidence, dissent, power effects, or an alternative that was never given a fair test. - A polished pyramid can rationalize a predetermined answer unless the hypothesis, confidence, counterevidence, and reversal conditions remain visible." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-connections-3", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-09-problem-structuring-connections-3", "url": "#chapter-09-problem-structuring-connections-3", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Validated branches from an Issue Tree (Framework 1) can supply supporting reasons, with evidence and uncertainty still attached. - Output: A provisional pyramid can inform a decision memo or presentation after the accountable owner reviews alternatives, criteria, and residual uncertainty. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-4-first-principles-thinking-the-5-whys", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "4. First Principles Thinking & The 5 Whys", "headingId": "chapter-09-problem-structuring-4-first-principles-thinking-the-5-whys", "url": "#chapter-09-problem-structuring-4-first-principles-thinking-the-5-whys", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "First Principles & The 5 Whys Root Cause Analysis" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-overview-4", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-09-problem-structuring-overview-4", "url": "#chapter-09-problem-structuring-overview-4", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "First-principles reasoning separates constraints, assumptions, and causal mechanisms rather than relying only on analogy. The 5 Whys is a questioning routine associated with Toyota Production System practice; it can help a team move from an observed failure toward process-level causes, but it does not establish causality by itself. [BB-C09-S03]" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-09-problem-structuring-how-to-apply-4", "url": "#chapter-09-problem-structuring-how-to-apply-4", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. State the observed event: Describe what was measured, when, where, and against which expectation (for example, “The server crashed at 14:10 during the reporting job”). 2. Ask and test “why?” iteratively: Treat each answer as a causal hypothesis, branch when explanations compete, seek disconfirming evidence, and stop when additional questioning no longer changes a decision. Five is a mnemonic, not a required count. 1. Why did the server crash? Because the database overloaded. 2. Why did the database overload? Because it received too many queries from a new reporting process. 3. Why did the process run so many queries? Because it was inefficiently designed to query one row at a time. 4. Why was it designed that way? Because the junior developer who built it wasn't trained on batch processing. 5. Why wasn't the developer trained? One candidate explanation is that onboarding omitted database-efficiency practice; verify this against supervision, review, workload, tooling, and incident evidence. 3. Compare response options: Restarting may be valid containment, a query change may be corrective, and an onboarding change may address a broader process hypothesis. Rank them only after testing the causal chain, safety, cost, reversibility, implementation risk, and recurrence evidence." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-contrarian-thinking-sometimes-the-symptom-is-the-problem", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Contrarian Thinking: Sometimes the Symptom IS the Problem", "headingId": "chapter-09-problem-structuring-contrarian-thinking-sometimes-the-symptom-is-the-problem", "url": "#chapter-09-problem-structuring-contrarian-thinking-sometimes-the-symptom-is-the-problem", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Not every incident has one deep or controllable root cause, and repeated questioning can create a tidy story unsupported by evidence. A one-off event may still warrant investigation when harm, legal duties, near-miss potential, or systemic exposure is high. Match the inquiry to consequence and recurrence, test the proposed causal chain, and consider multiple interacting causes." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-09-problem-structuring-so-what-for-managers-4", "url": "#chapter-09-problem-structuring-so-what-for-managers-4", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the routine to turn an observed event into competing causal hypotheses, evidence requests, containment options, and a clear stopping rule. - Branch when explanations compete and check supervision, workload, tooling, incentives, environment, and interacting causes rather than assigning blame to one person. - Match the depth of inquiry to harm, recurrence, legal or safety duties, reversibility, and the decision the evidence must support." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-09-problem-structuring-limits-and-critiques-4", "url": "#chapter-09-problem-structuring-limits-and-critiques-4", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Five iterations do not identify a root cause, establish causality, or guarantee a controllable intervention. - A linear chain can hide feedback, multiple causes, measurement error, organizational conditions, and uncertainty. - The routine should not replace incident investigation, statistical analysis, technical review, or protected people-process channels when those are required." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-connections-4", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-09-problem-structuring-connections-4", "url": "#chapter-09-problem-structuring-connections-4", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Apply the technique to a defined defect or decision identified through a Process Flow Diagram (Chapter 6) , a failing KPI (Chapter 8) , or another evidence source. - Output: A supported causal hypothesis can inform containment, further investigation, or a proportionate process-improvement initiative such as Six Sigma DMAIC (Chapter 6) . ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-5-logic-tree-construction", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "5. Logic Tree Construction", "headingId": "chapter-09-problem-structuring-5-logic-tree-construction", "url": "#chapter-09-problem-structuring-5-logic-tree-construction", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Logic Trees Building Arguments" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-overview-5", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-09-problem-structuring-overview-5", "url": "#chapter-09-problem-structuring-overview-5", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Logic Tree below is an author-created argument-mapping aid. Unlike an issue tree used to decompose a question, it organizes a proposed conclusion and its supporting or implementation branches. A completed tree does not ensure that the logic is valid, the premises are true, or material alternatives are represented." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-09-problem-structuring-how-to-apply-5", "url": "#chapter-09-problem-structuring-how-to-apply-5", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Start with Your Main Point/Recommendation: Place this at the far left. (e.g., \"We should launch Product X in Germany.\"). 2. Build Deductive or Inductive Branches: Deductive (Why?): Each branch answers \"Why?\" for the parent node. (e.g., \"Why launch in Germany?\" - \"Because the market is large,\" \"Because we have a right to win,\" and \"Because the ROI is positive.\"). This is one possible structure for organizing a recommendation; it does not guarantee persuasion. Inductive (How?): Each branch answers \"How?\" for the parent node, breaking a solution into implementation steps. (e.g., \"How do we launch in Germany?\" - \"Hire a country manager,\" \"Localize the product,\" \"Launch marketing campaign.\")." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-09-problem-structuring-so-what-for-managers-5", "url": "#chapter-09-problem-structuring-so-what-for-managers-5", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use a logic tree to distinguish reasons for a conclusion from actions required to implement it; label each branch as deductive, inductive, factual, estimated, or assumed. - Test whether each branch answers the parent question, whether alternatives are represented, and whether the decision owner can act on the proposed implication. - Stop refining the tree when additional branches no longer change evidence collection, decision criteria, or implementation choices." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-09-problem-structuring-limits-and-critiques-5", "url": "#chapter-09-problem-structuring-limits-and-critiques-5", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- An author-created tree is an argument map, not a validity proof, causal model, or completeness guarantee. - Deductive and inductive reasoning can be mixed without labeling, producing a persuasive-looking but logically ambiguous recommendation. - A tree can omit stakeholder, legal, ethical, operational, or political constraints that do not appear as neat branches." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-connections-5", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-09-problem-structuring-connections-5", "url": "#chapter-09-problem-structuring-connections-5", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: A main point may come from a Hypothesis Pyramid (Framework 3) , but it should remain provisional until premises and alternatives are reviewed. - Output: An inductive “How?” tree can inform a project plan or work-breakdown structure in Chapter 11 , subject to scope, capacity, dependencies, and governance. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-6-problem-statement-canvas", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "6. Problem Statement Canvas", "headingId": "chapter-09-problem-structuring-6-problem-statement-canvas", "url": "#chapter-09-problem-structuring-6-problem-statement-canvas", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Problem Statement Canvas Defining the Problem" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-overview-6", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-09-problem-structuring-overview-6", "url": "#chapter-09-problem-structuring-overview-6", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This Problem Statement Canvas is an author-created framing template. Before committing to a solution, clarify the decision, current evidence, stakeholders, scope, constraints, ethical boundaries, and success measures. A canvas can create a shared starting frame, but discovery may legitimately reframe the problem; record version changes and their implications." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-09-problem-structuring-how-to-apply-6", "url": "#chapter-09-problem-structuring-how-to-apply-6", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Fill in the blanks with specific, evidence-aware answers and record the canvas version: 1. Decision and Owner: What decision is required, by whom, and by what date? 2. Current State and Evidence: What is observed, estimated, assumed, or unknown? Record definitions, data quality, and the evidence owner. 3. Desired State and No-Action Option: What outcomes would count as acceptable, and what happens if the organization delays or does nothing? 4. Affected Stakeholders: Who bears benefits, costs, risks, or rights impacts, and whose voice is needed before a choice? 5. Gap and Consequence: What is the decision-relevant gap, and what could happen if it remains open? Do not convert an unvalidated estimate into a fact. 6. Scope and Constraints: What is in scope, out of scope, dependent, irreversible, legally or ethically constrained, or subject to safety, privacy, accessibility, or professional duties? 7. Success Measures and Review: Which measures, guardrails, baseline, time horizon, and review trigger will show whether the decision worked? 8. Version and Reframing Triggers: What evidence or stakeholder change would reopen the frame, and who records the change and its consequences?" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-09-problem-structuring-so-what-for-managers-6", "url": "#chapter-09-problem-structuring-so-what-for-managers-6", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the canvas to make the decision owner, affected parties, current evidence, scope, constraints, rights, and success measures explicit before analysis expands. - Treat the canvas as a versioned working agreement: record what changed, which evidence caused the change, and which work became obsolete. - Check whether the success measures are controllable, decision-relevant, and safe to use before turning them into targets or performance judgments." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-09-problem-structuring-limits-and-critiques-6", "url": "#chapter-09-problem-structuring-limits-and-critiques-6", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A canvas structures a conversation; it does not create stakeholder agreement, identify every relevant cause, or validate the stated problem. - Early framing can anchor a team on the wrong unit of analysis, timeframe, affected population, or solution boundary. - A shared template can suppress dissent or discovery if version changes are treated as scope failure rather than evidence." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-connections-6", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-09-problem-structuring-connections-6", "url": "#chapter-09-problem-structuring-connections-6", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Use an initial stakeholder workshop, existing evidence, and relevant rights or operating constraints to draft the canvas. - Output: The current problem statement becomes provisional input for the Issue Tree (Framework 1) and should be revised when material evidence changes the frame. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-7-prioritization-matrices", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "7. Prioritization Matrices", "headingId": "chapter-09-problem-structuring-7-prioritization-matrices", "url": "#chapter-09-problem-structuring-7-prioritization-matrices", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Prioritization Matrices Deciding What to Do First" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-overview-7", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-09-problem-structuring-overview-7", "url": "#chapter-09-problem-structuring-overview-7", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The effort/impact matrix below is an author-created prioritization aid, not a validated ranking model. It uses a 2x2 display to compare candidate work when demand exceeds resources; users still need defined measures, uncertainty, dependencies, rights, risk, reversibility, and accountable judgment." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-09-problem-structuring-how-to-apply-7", "url": "#chapter-09-problem-structuring-how-to-apply-7", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. The Effort vs. Impact Matrix (Most Common): Axes: Plot each initiative on a 2x2 grid with \"Effort\" on the x-axis and \"Impact\" on the y-axis. Quadrants: High Impact, Low Effort (Quick Wins): Consider these early after checking dependencies, risks, opportunity cost, and strategic fit. High Impact, High Effort (Major Projects): These are strategic initiatives that require careful planning. Low Impact, Low Effort (Fill-ins): Defer unless they enable learning, compliance, reliability, or another priority. Low Impact, High Effort: Normally deprioritize, while checking whether the score omits mandatory obligations or enabling dependencies. 2. Other Matrix Heuristics: Urgent vs. Important (Eisenhower Matrix): For personal time management. Focus on what is Important but Not Urgent (strategic work). Author-created ICE heuristic: A quick directional formula, (Impact Confidence Ease) / 3 , whose scales, weights, and validity must be defined locally; it is not a validated decision rule." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-contrarian-thinking-prioritization-matrices-create-false-precision", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Contrarian Thinking: Prioritization Matrices Create False Precision", "headingId": "chapter-09-problem-structuring-contrarian-thinking-prioritization-matrices-create-false-precision", "url": "#chapter-09-problem-structuring-contrarian-thinking-prioritization-matrices-create-false-precision", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Effort/Impact matrices assume you can accurately estimate both effort and impact before doing the work. You usually can't . Early estimates are often rough guesses, and teams can waste time debating whether something is \"High Impact, Medium Effort\" vs. \"Medium Impact, Low Effort\" when both estimates are uncertain. An operator's approach: Use the matrix for directional prioritization only. If two initiatives are in adjacent quadrants, choose using the decision stakes, reversibility, dependencies, and information value. Speed matters only within the safeguards and evidence standard the decision requires." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-09-problem-structuring-so-what-for-managers-7", "url": "#chapter-09-problem-structuring-so-what-for-managers-7", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the matrix for directional triage after defining the decision, evidence, dependencies, constraints, and non-negotiable obligations. - Treat impact, effort, confidence, and ease as ranges or hypotheses; test adjacent-quadrant choices with reversible pilots or information gathering. - Revisit the ranking when capacity, evidence, risk, stakeholder effects, or strategic priorities change." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-09-problem-structuring-limits-and-critiques-7", "url": "#chapter-09-problem-structuring-limits-and-critiques-7", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A 2x2 matrix is an author-created aid; it does not make uncertain impact or effort estimates precise or comparable. - Quadrants can hide option value, dependencies, distributional effects, mandatory work, and the cost of delaying an alternative. - Weighted scores and quick wins can reward visible short-term activity while underweighting capability, safety, reliability, or long-term value." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-connections-7", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-09-problem-structuring-connections-7", "url": "#chapter-09-problem-structuring-connections-7", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Candidate initiatives or solutions may come from an Issue Tree (Framework 1) , a Value Stream Mapping (Chapter 6) exercise, or stakeholder evidence. - Output: A provisional priority list can inform a Project Management (Chapter 11) backlog after capacity, dependencies, risk, and decision rights are reviewed. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-8-risk-assessment-framework", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "8. Risk Assessment Framework", "headingId": "chapter-09-problem-structuring-8-risk-assessment-framework", "url": "#chapter-09-problem-structuring-8-risk-assessment-framework", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Risk Assessment Matrix Anticipating Obstacles" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-overview-8", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-09-problem-structuring-overview-8", "url": "#chapter-09-problem-structuring-overview-8", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A likelihood-impact matrix is one possible risk-assessment aid, not a measurement instrument or complete risk-management process. NIST SP 800-30 Rev. 1 uses defined likelihood and impact scales to inform risk determination in federal information-security assessment and explicitly cautions that assessments can be imprecise and depend on methods, data quality, interpretation, and assessor expertise. [BB-C09-S06] Cox's peer-reviewed analysis identifies poor resolution, range compression, ranking errors, subjective inputs, and resource-allocation limits in risk matrices. [BB-C09-S07] The matrix procedure below is a constructed cross-domain teaching adaptation. Its categories and colors are locally defined triage labels; they do not quantify probability or loss, validate a priority order, or dictate a response." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-09-problem-structuring-how-to-apply-8", "url": "#chapter-09-problem-structuring-how-to-apply-8", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define the decision and harm: Identify affected objectives, stakeholders, rights, time horizon, scenarios, dependencies, and governing risk criteria. 2. Define the scales before scoring: State what each likelihood and impact category means, the evidence period, data limits, and who owns the judgment; do not multiply ordinal labels as if they were measured quantities. 3. Map and explain: Place a risk in a locally defined cell, record the rationale and uncertainty, and preserve the underlying scenario rather than reporting only a color. 4. Choose a response through accountable analysis: Compare avoidance, reduction, transfer/sharing, acceptance, contingency, monitoring, and escalation options using cost, benefit, feasibility, rights, risk appetite, and residual exposure. Do not allocate resources from matrix rank alone." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-09-problem-structuring-so-what-for-managers-8", "url": "#chapter-09-problem-structuring-so-what-for-managers-8", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the scenario, affected objectives and people, time horizon, evidence period, risk criteria, owner, and escalation path before assigning a cell. - Preserve the underlying likelihood and impact rationale, uncertainty, data limits, and alternative scenarios; do not report only a color or rank [BB-C09-S06] [BB-C09-S07]. - Compare response options, residual exposure, rights, feasibility, and reversibility, and escalate risks that exceed authorized limits." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-09-problem-structuring-limits-and-critiques-8", "url": "#chapter-09-problem-structuring-limits-and-critiques-8", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Likelihood-impact matrices use locally defined categories and judgment; they do not measure probability, loss, or total risk with precision. - Ordinal labels can compress ranges, create ranking errors, hide dependencies, and invite false confidence when multiplied or color-coded. - A matrix does not replace hazard analysis, security assessment, legal review, safety controls, business continuity, or accountable risk ownership." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-connections-8", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-09-problem-structuring-connections-8", "url": "#chapter-09-problem-structuring-connections-8", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Potential risks may be identified during problem framing, stakeholder mapping in Chapter 7 , incident review, or another evidence process. - Output: A documented risk register can inform a Project Charter (Chapter 11) , control plan, escalation, or decision gate; matrix rank alone should not allocate resources. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-9-decision-criteria-weighting-model", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "9. Decision Criteria Weighting Model", "headingId": "chapter-09-problem-structuring-9-decision-criteria-weighting-model", "url": "#chapter-09-problem-structuring-9-decision-criteria-weighting-model", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Decision Criteria Weighting Transparent Trade-offs" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-overview-9", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-09-problem-structuring-overview-9", "url": "#chapter-09-problem-structuring-overview-9", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Structured decision making makes a decision's component parts visible by defining the problem and context, objectives, alternatives, consequences, trade-offs, and uncertainty. [BB-C09-S05] The weighting worksheet below is an author-created aid; it does not make subjective weights or uncertain scores objective." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-09-problem-structuring-how-to-apply-9", "url": "#chapter-09-problem-structuring-how-to-apply-9", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. List Decision Criteria: With your stakeholders, agree on the key criteria that will drive the decision (e.g., Cost, Strategic Fit, Ease of Implementation, Risk). 2. Define Scales and Evidence Owners: Specify what each score means, which direction is favorable, the data source, and who is accountable for updating it. Avoid double-counting correlated criteria. 3. Assign Weights: Make value judgments explicit and ensure weights sum to 100 percent. Include non-negotiable legal, ethical, safety, or strategic constraints as gates rather than allowing a strong score elsewhere to compensate for failure. - Constructed calculation rule: If an additive model is appropriate, normalize each criterion to a documented commensurable scale s ij , set weights w i with sum(w i) = 1 , and calculate S j = sum(w i s ij) . Do not add unlike ordinal judgments or correlated criteria without explaining the decision-specific rationale . 4. Score Each Option: Score all feasible alternatives—including delay, pilot, or status quo—on the same documented scales. Show ranges or confidence where evidence is uncertain. 5. Calculate and Stress-Test: Calculate weighted totals, then vary plausible weights and scores. If small changes reverse the ranking, report the decision as sensitive rather than presenting a precise winner. 6. Discuss and Decide: The accountable decision owner records the choice, trade-offs, dissent, uncertainty, and triggers for review. The model informs judgment; it does not own the decision." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-decision-tree-handoff-structure-before-calculating", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Decision-Tree Handoff: Structure Before Calculating", "headingId": "chapter-09-problem-structuring-decision-tree-handoff-structure-before-calculating", "url": "#chapter-09-problem-structuring-decision-tree-handoff-structure-before-calculating", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use a decision tree when the choice depends on uncertain events or when information arrives before a later choice. A decision node represents an action under the decision owner's control; a chance node represents an uncertain event; a terminal branch records the consequence. Estimate probabilities from relevant evidence, show their provenance and uncertainty, and ensure mutually exclusive branches sum to one. HM Treasury's current appraisal guidance likewise uses expected values for probability-weighted outcomes and decision trees for sequential, uncertain, or difficult-to-reverse choices. [BB-C22-S11] Before calculating, eliminate or redesign options that fail an applicable legal requirement, safety limit, rights obligation, ethical standard, or other authorized minimum. A weighted score or favorable expected monetary value must not compensate for such a failure. Official MCDA guidance explicitly warns that compensatory models allow strength on one criterion to offset weakness on another and describes absolute minima as a way to eliminate unsuitable options before analysis. [BB-C22-S12] Send the feasible tree to Chapter 22's Managerial Decision Analysis framework to calculate expected monetary value, break-even probability, Bayesian updates, and the value of additional information. Keep expected utility separate from expected money when risk preference or consequence severity could change the ranking." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-09-problem-structuring-so-what-for-managers-9", "url": "#chapter-09-problem-structuring-so-what-for-managers-9", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the decision, alternatives including delay or pilot, criteria, evidence owners, uncertainty, non-compensable gates, and decision date before calculating a score. - Use ranges, sensitivity analysis, and independent challenge to show whether the choice is robust or depends on arbitrary weights, scores, or assumptions. - Keep the accountable decision owner responsible for trade-offs, dissent, rights, residual uncertainty, and review triggers; the worksheet is an aid." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-09-problem-structuring-limits-and-critiques-9", "url": "#chapter-09-problem-structuring-limits-and-critiques-9", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Weighted scoring is compensatory unless explicit gates are added; a high score on one criterion can mask failure on a legal, safety, rights, or ethical minimum. - Weights, scores, probabilities, and criteria may reflect contested values, correlated evidence, measurement error, or power rather than objective facts. - Expected monetary value and expected utility answer different questions and should not be substituted for one another or for accountable judgment." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-connections-9", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-09-problem-structuring-connections-9", "url": "#chapter-09-problem-structuring-connections-9", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Options may come from brainstorming or a Blue Ocean Strategy (Chapter 3) exercise; criteria should be tested against the Problem Statement Canvas (Framework 6) and affected-party obligations. - Output: An auditable comparison can inform an organizational decision, while uncertain sequential choices can be handed to Chapter 22 for quantitative analysis after minimum gates are applied. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-10-assumption-mapping", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "10. Assumption Mapping", "headingId": "chapter-09-problem-structuring-10-assumption-mapping", "url": "#chapter-09-problem-structuring-10-assumption-mapping", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Assumption Mapping Testing What You Don't Know" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-overview-10", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-09-problem-structuring-overview-10", "url": "#chapter-09-problem-structuring-overview-10", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Every strategic recommendation depends on assumptions. Assumption mapping surfaces them and routes evidence work toward beliefs that are both consequential and uncertain. It is useful for ventures and projects, but it is not a substitute for legal review, safety analysis, stakeholder consultation, or causal research where those are required." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-09-problem-structuring-how-to-apply-10", "url": "#chapter-09-problem-structuring-how-to-apply-10", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. List Material Assumptions: For a given strategy or business model, list beliefs whose failure could materially change the decision, including customer, financial, operational, legal, ethical, safety, and competitive assumptions. 2. Map Assumptions on a 2x2: Plot each assumption on a matrix with two axes: Importance (how critical is this assumption to success?) and Uncertainty (how much evidence do we have for this assumption?). 3. Prioritize Evidence Work: High-importance, high-uncertainty assumptions usually deserve early attention. High-importance, apparently low-uncertainty assumptions still require an evidence owner and monitoring because confidence can be misplaced or conditions can change. 4. Design Proportionate Tests: Choose safe, lawful, and ethical methods with sufficient validity for the decision. Consider information value, reversibility, cost, affected stakeholders, and the harm of false reassurance—not only speed and price. Figure 9.4. Assumption-routing loop. Consequence and uncertainty determine whether an assumption is tested, monitored, assigned, or recorded; new evidence can change the route. Text equivalent: List material assumptions, rate consequence and uncertainty, and route high-consequence uncertainty to a proportionate evidence test. Record lower-consequence assumptions, assign ownership for high-consequence assumptions believed to be well supported, and update ratings as evidence changes. Source note: Author synthesis. Structured-decision-making principles on problem context, objectives, alternatives, consequences, trade-offs, and uncertainty inform the routing logic; the consequence/uncertainty quadrants are not taken from the source. [BB-C09-S05]" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-09-problem-structuring-so-what-for-managers-10", "url": "#chapter-09-problem-structuring-so-what-for-managers-10", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Identify assumptions whose failure could change the decision, then assign an owner, evidence source, test method, decision date, and harm-control plan. - Prioritize by consequence and uncertainty, not by novelty or ease of testing; monitor apparently well-supported assumptions when conditions can change. - Update the recommendation, model, resource allocation, or stop rule when evidence changes an assumption's status." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-09-problem-structuring-limits-and-critiques-10", "url": "#chapter-09-problem-structuring-limits-and-critiques-10", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Assumption maps depend on the team's framing and can omit unknown unknowns, stakeholder knowledge, power, or dependencies. - Importance and uncertainty are judgments that can be miscalibrated; a test can create false reassurance if validity, sample, timing, or implementation effects are weak. - Experimentation must respect law, safety, privacy, rights, accessibility, and affected-party protections; speed is not a sufficient design criterion." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-connections-10", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-09-problem-structuring-connections-10", "url": "#chapter-09-problem-structuring-connections-10", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Input: Candidate assumptions can be derived from a Hypothesis Pyramid (Framework 3) , strategy choices, operating constraints, and stakeholder evidence. - Output: Evidence results can refine a Business Model Canvas (Chapter 10) , strategy, forecast, or decision rule; they do not automatically validate the business. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mental-model-1-first-principles-thinking", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 1: First Principles Thinking", "headingId": "chapter-09-problem-structuring-mental-model-1-first-principles-thinking", "url": "#chapter-09-problem-structuring-mental-model-1-first-principles-thinking", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "First-principles thinking attempts to decompose a problem into assumptions, constraints, mechanisms, and evidence rather than relying only on analogy. In business systems, “undeniable truths” and a single root cause may not exist. The 5 Whys can generate causal hypotheses, but it does not validate them or distinguish interacting causes by itself. Operator's Application: When a team proposes hiring because revenue is flat, separate the revenue identity, customer and product mechanisms, timing, capacity, retention, mix, price, demand, and execution assumptions. Price × volume can be one accounting decomposition, not the only causal model. Test alternatives before attributing the gap to pricing, product, or headcount." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mental-model-2-the-pyramid-principle", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 2: The Pyramid Principle", "headingId": "chapter-09-problem-structuring-mental-model-2-the-pyramid-principle", "url": "#chapter-09-problem-structuring-mental-model-2-the-pyramid-principle", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Barbara Minto's Pyramid Principle is a practitioner approach to organizing business communication: start with the current answer, then group supporting reasons and evidence. [BB-C09-S02] The Hypothesis Pyramid adapts that structure for provisional recommendations by keeping alternatives, uncertainty, and disconfirming evidence visible. It can improve inspectability for some audiences; it does not guarantee persuasion, agreement, or decision quality. Operator's Application: Before an executive presentation, draft a one-sentence bottom line that states the proposed decision, principal reasons, and uncertainty. For example: \"Subject to validating the downside and alternatives, we should consider exiting the UK market because the current model is structurally unprofitable and redeployment may create greater risk-adjusted value.\" The presentation should test that provisional conclusion, show contrary evidence and options, and make the decision and evidence needed explicit." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mental-model-3-problem-vs-symptom", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 3: Problem vs. Symptom", "headingId": "chapter-09-problem-structuring-mental-model-3-problem-vs-symptom", "url": "#chapter-09-problem-structuring-mental-model-3-problem-vs-symptom", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Observed outcomes such as declining revenue can arise from multiple interacting mechanisms. An Issue Tree can organize candidate explanations, and the 5 Whys can generate deeper hypotheses, but neither proves one root cause. Some symptom relief is appropriate while causal investigation continues, especially when safety, customers, cash, or legal obligations are at risk. Operator's Application: Ask what would remain if the proposed cause were removed, what evidence would change the conclusion, and which alternative mechanisms predict the same observation. A claim that “nothing would remain” is not validation; use experiments, comparisons, process evidence, and independent challenge where the decision warrants them." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mental-model-4-satisficing-vs-maximizing-herbert-simon-s-bounded-rationality", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 4: Satisficing vs. Maximizing (Herbert Simon's Bounded Rationality)", "headingId": "chapter-09-problem-structuring-mental-model-4-satisficing-vs-maximizing-herbert-simon-s-bounded-rationality", "url": "#chapter-09-problem-structuring-mental-model-4-satisficing-vs-maximizing-herbert-simon-s-bounded-rationality", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The concept of satisficing is associated with Herbert Simon's bounded-rationality work: choosing an option that meets a defined threshold rather than searching indefinitely for an optimum. In complex problems with incomplete information, a stopping rule can reduce analysis paralysis, but the threshold should reflect stakes, reversibility, rights, uncertainty, and decision value. Operator's Application: Before starting any analysis project, define your \"good enough\" threshold. Example: \"We need directional confidence that this is the right answer, not theoretical certainty.\" This prevents the \"one more data point\" syndrome. Make the confidence threshold explicit so the team knows when to stop analyzing and start deciding." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mental-model-5-reversibility-and-option-value", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 5: Reversibility and Option Value", "headingId": "chapter-09-problem-structuring-mental-model-5-reversibility-and-option-value", "url": "#chapter-09-problem-structuring-mental-model-5-reversibility-and-option-value", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Classifying decisions by reversibility can help calibrate evidence, authority, safeguards, and learning. Reversibility is continuous: financial, legal, safety, reputational, data, employment, and path-dependence costs can make an apparently reversible test difficult to undo. Operator's Application: Assess irreversibility, downside, affected rights, uncertainty, learning value, and cost of delay. A bounded test may justify lighter analysis only when safeguards, consent, monitoring, rollback, and authority are credible. Decision trees can expose where a later choice remains open; real-options reasoning can value flexibility as information emerges, while also warning against spurious precision in scenario probabilities. [BB-C22-S11] Do not apply a fixed analysis multiplier or assume pricing, hiring, campaigns, or software launches are inherently reversible." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mental-model-6-pre-mortem-analysis-gary-klein", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 6: Pre-Mortem Analysis (Gary Klein)", "headingId": "chapter-09-problem-structuring-mental-model-6-pre-mortem-analysis-gary-klein", "url": "#chapter-09-problem-structuring-mental-model-6-pre-mortem-analysis-gary-klein", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Instead of asking only \"How do we make this succeed?\" a premortem asks participants to imagine that the plan has failed and independently generate plausible reasons. Klein presents the technique as a way to broaden prospective risk identification before implementation. [BB-C09-S04] It can surface concerns that a conventional planning discussion misses, but it does not estimate risk probabilities or replace independent review. Operator's Application: After completing the Issue Tree and Hypothesis Pyramid , ask participants first to write plausible failure reasons independently, then discuss and cluster them. Add material scenarios to the Risk Assessment Matrix , identify evidence and mitigation owners, and invite a reviewer who was not invested in the plan. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-operator-s-playbook-problem-structuring-in-the-real-world", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Operator's Playbook: Problem Structuring in the Real World", "headingId": "chapter-09-problem-structuring-operator-s-playbook-problem-structuring-in-the-real-world", "url": "#chapter-09-problem-structuring-operator-s-playbook-problem-structuring-in-the-real-world", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following is a constructed playbook for practice, not a universal consulting cadence. For high-stakes, irreversible, legally constrained, safety-sensitive, or rights-affecting decisions, use the evidence, independent challenge, authority, and stakeholder-protection standard the decision requires." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-the-1-week-vs-1-month-approach", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "The 1-Week vs. 1-Month Approach", "headingId": "chapter-09-problem-structuring-the-1-week-vs-1-month-approach", "url": "#chapter-09-problem-structuring-the-1-week-vs-1-month-approach", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "When you have 1 week: 1. Day 1: Facilitate a time-boxed Problem Statement Canvas workshop with the decision owner and representative affected stakeholders. Record the current frame, disputed assumptions, and the evidence that would trigger reframing. 2. Days 2-3: Build a \"quick and dirty\" Issue Tree with your core team in a half-day session. Aim for enough MECE discipline to guide the work, not theoretical perfection. Identify the 3-4 most likely branches and formulate hypotheses for each. 3. Days 4-5: Test your hypotheses with proportionate analysis. Use existing data, targeted interviews, or competitor benchmarks when valid and authorized; do not trade away privacy, safety, legal review, or evidence quality merely to meet the timetable. 4. Day 6: Build your Hypothesis Pyramid presentation. Focus on the 2-3 arguments that have the strongest evidence. Be transparent about confidence levels and data gaps. 5. Day 7: Present, get feedback, iterate. Be ready to defend your logic and acknowledge uncertainties. When you have 1 month: 1. Week 1: Same as 1-week approach. Problem statement alignment and initial hypothesis formation. 2. Week 2: Deep-dive analysis on your top 3 hypotheses. Commission primary research if needed (customer surveys, focus groups, detailed financial modeling). 3. Week 3: Expand your analysis to test edge cases and alternative hypotheses. Run a Pre-Mortem session to identify blind spots. Update your Issue Tree based on findings. 4. Week 4: Build a comprehensive Hypothesis Pyramid with multiple scenarios (base case, bull case, bear case). Develop detailed implementation plans and risk mitigation strategies. Run a dry-run presentation with a \"friendly\" audience before the final stakeholder presentation." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-political-navigation-red-flags-and-how-to-handle-them", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Political Navigation: Red Flags and How to Handle Them", "headingId": "chapter-09-problem-structuring-political-navigation-red-flags-and-how-to-handle-them", "url": "#chapter-09-problem-structuring-political-navigation-red-flags-and-how-to-handle-them", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following red flags are constructed scenarios for practice, not claims about a named client, company, or advisory engagement. Red Flag 1: The Sponsor Tells You the Answer Before You Start Scenario: \"We need to prove that entering the Chinese market is the right move.\" Diagnosis: You're being asked to build a post-hoc rationalization, not conduct objective analysis. Action: Reframe the problem statement: \"Under what conditions would entering this market create durable value without breaching legal, ethical, or risk constraints, and does current evidence support those conditions?\" Preserve a genuine no-entry alternative, document sponsor assumptions, and escalate if the mandate requires post-hoc rationalization. Red Flag 2: Key Stakeholders Refuse to Participate in Problem Statement Alignment Scenario: You schedule a Problem Statement Canvas workshop, but the CFO and Head of Sales both \"have conflicts\" and send junior delegates. Diagnosis: Non-participation can reflect low expected value, workload, delegation, timing, conflict, fear, unclear authority, or strategic ambiguity; deliberate avoidance is only one hypothesis. Action: Clarify which decisions require senior authority, what representation is sufficient, and which assumptions remain disputed. Escalate material gaps, redesign participation, narrow the decision, or pause when authority/evidence is inadequate. Lack of full alignment raises risk but does not guarantee failure or make all continued work wasteful. Red Flag 3: The Data You Need Doesn't Exist or Is Being Withheld Scenario: You're trying to test a hypothesis about customer churn, but you discover the company doesn't track churn data (or worse, the data exists but you're told \"it's not ready to share\"). Diagnosis: Treat this as competing hypotheses: the measure may be undefined, the data may be incomplete or delayed, access may be restricted by privacy or governance rules, incentives may discourage disclosure, or information may be withheld. Do not infer concealment before checking definitions, ownership, permissions, timing, and data quality. Action: Document the data gap and its impact on your analysis. Present a \"bounded\" recommendation: \"Based on the data we have, our recommendation is X. However, there is a critical data gap on [metric]. To increase confidence, we recommend commissioning [specific analysis].\" Don't pretend to have more certainty than you do. Red Flag 4: Stakeholders Keep Changing the Problem Statement Mid-Project Scenario: Week 1: \"We need to reduce costs.\" Week 3: \"Actually, we need to increase revenue.\" Week 5: \"Actually, we need to improve culture.\" Diagnosis: Scope creep driven by lack of initial clarity or stakeholder politics. Action: Reference the versioned Problem Statement Canvas. Ask whether new evidence, changed objectives, or politics caused the shift. The decision owner can finish the current question, launch a separate question, or formally reframe and reset the evidence plan and timeline; record the choice and consequences." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-client-management-when-to-push-back-vs-when-to-adapt", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Client Management: When to Push Back vs. When to Adapt", "headingId": "chapter-09-problem-structuring-client-management-when-to-push-back-vs-when-to-adapt", "url": "#chapter-09-problem-structuring-client-management-when-to-push-back-vs-when-to-adapt", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Push Back When: - The problem statement seeks commercial gain by omitting foreseeable health, safety, legal, or stakeholder harm. - The timeline is impossible without sacrificing quality (e.g., \"We need a full M&A due diligence in 3 days\"). - The client is asking you to ignore data that contradicts their preferred answer. Adapt When: - The client has legitimate new information that changes the context (e.g., regulatory change, competitor move). - The client wants a different communication style (more/less detail, different format). - The client wants to prioritize a different branch of your issue tree based on their strategic priorities. A documented disagreement protocol: When you and the client disagree on the recommendation: 1. Make your perspective crystal clear in writing. Document your reasoning and the risks you see. 2. Constructed evidence-updating prompt: Ask, \"What evidence, constraint, or decision condition would change your mind?\" If no possible evidence or condition is accepted, record that the decision is not being made through an evidence-updating process and use the applicable professional, contractual, organizational, compliance, or ethics process; seek qualified counsel where the role or jurisdiction requires it. 3. If the decision owner proceeds against the recommendation, document the rationale and residual risks. Support lawful, ethical execution within your role; do not comply with misconduct or conceal material dissent. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-case-studies-structuring-in-action", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Case Studies: Structuring in Action", "headingId": "chapter-09-problem-structuring-case-studies-structuring-in-action", "url": "#chapter-09-problem-structuring-case-studies-structuring-in-action", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following six cases are constructed composites for instruction , not claims about a named company, advisory firm, client, or transaction." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-composite-1-the-profitability-problem-that-wasn-t", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite 1: The \"Profitability\" Problem That Wasn't", "headingId": "chapter-09-problem-structuring-composite-1-the-profitability-problem-that-wasn-t", "url": "#chapter-09-problem-structuring-composite-1-the-profitability-problem-that-wasn-t", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "An industrial-equipment business asks a team to diagnose declining profitability. A conventional Profit = Revenue - Cost tree identifies savings but not the magnitude of the decline. External interviews and a Five Forces analysis reveal that a lower-cost substitute is changing customer requirements. - Lesson: Test whether the presenting symptom is the decision problem. Add market and customer evidence before assuming the answer lies inside the income statement." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-composite-2-the-narrow-service-frame", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite 2: The Narrow Service Frame", "headingId": "chapter-09-problem-structuring-composite-2-the-narrow-service-frame", "url": "#chapter-09-problem-structuring-composite-2-the-narrow-service-frame", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A subscription-media provider frames its problem as reducing physical-fulfilment cost. Customer research instead reveals a broader job: convenient access to entertainment. The wider frame introduces digital delivery, licensing, and product-experience options, but also new capital, capability, and regulatory questions. - Lesson: Framing changes the option set. A broader frame can reveal alternatives, but breadth is not automatically superior; evaluate the decision consequences." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-composite-3-the-missing-m-a-branch", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite 3: The Missing M&A Branch", "headingId": "chapter-09-problem-structuring-composite-3-the-missing-m-a-branch", "url": "#chapter-09-problem-structuring-composite-3-the-missing-m-a-branch", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A technology acquirer evaluates a small software target through technology, finance, and legal branches. The financial model works, yet the deal later loses key employees because integration assumptions and retention risks were not examined. - Lesson: MECE does not guarantee that a team has chosen the right analytical universe. Add people, culture, incentives, and integration branches when they are material; connect them to Chapter 7 and valuation consequences in Chapter 4." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-composite-4-the-ethically-truncated-mandate", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite 4: The Ethically Truncated Mandate", "headingId": "chapter-09-problem-structuring-composite-4-the-ethically-truncated-mandate", "url": "#chapter-09-problem-structuring-composite-4-the-ethically-truncated-mandate", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A commercial team is asked only how to increase sales of a regulated product. The frame excludes patient harm, appropriate-use constraints, regulators, clinicians, and long-run trust. - Lesson: A commercially coherent analysis can still be ethically and legally defective. Apply the stakeholder, governance, and escalation disciplines in Chapter 2 before optimizing within the mandate." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-composite-5-the-predetermined-public-sector-answer", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite 5: The Predetermined Public-Sector Answer", "headingId": "chapter-09-problem-structuring-composite-5-the-predetermined-public-sector-answer", "url": "#chapter-09-problem-structuring-composite-5-the-predetermined-public-sector-answer", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A sponsor asks analysts to \"prove\" that a preferred infrastructure option is best. The team builds an elegant pyramid around confirming evidence while ignoring a lower-cost alternative and affected communities. - Lesson: A pyramid can communicate bias as neatly as insight. Pre-register criteria where feasible, retain a no-action alternative, assign an independent challenger, and document disconfirming evidence and conflicts of interest." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-composite-6-the-politically-constrained-turnaround", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite 6: The Politically Constrained Turnaround", "headingId": "chapter-09-problem-structuring-composite-6-the-politically-constrained-turnaround", "url": "#chapter-09-problem-structuring-composite-6-the-politically-constrained-turnaround", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A state-influenced transport company has operational cost problems, but proposed remedies depend on labor agreements, public-service obligations, regulators, and government funding. A purely commercial issue tree therefore overstates feasibility. - Lesson: Add governance, stakeholder, and implementation branches where political constraints are material. Use stakeholder analysis in Chapter 7 as an input, not a mechanical requirement for every problem. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-advanced-framework-applications-deep-dives", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Advanced Framework Applications: Deep Dives", "headingId": "chapter-09-problem-structuring-advanced-framework-applications-deep-dives", "url": "#chapter-09-problem-structuring-advanced-framework-applications-deep-dives", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "All companies, figures, scores, and outcomes in the following deep dives are illustrative constructed examples. They are teaching inputs, not benchmarks or forecasts. A real decision requires validated company data, accountable assumptions, and appropriate legal, financial, technical, and stakeholder review." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-deep-dive-1-building-a-profitability-issue-tree-from-scratch", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Deep Dive 1: Building a Profitability Issue Tree from Scratch", "headingId": "chapter-09-problem-structuring-deep-dive-1-building-a-profitability-issue-tree-from-scratch", "url": "#chapter-09-problem-structuring-deep-dive-1-building-a-profitability-issue-tree-from-scratch", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Scenario: A mid-sized SaaS company (500 employees, $50M ARR) has seen gross profit margins decline from 75 percent to 65 percent over 18 months. The CEO asks you to diagnose why and recommend a solution. Step 1: Define the Problem Statement Use the Problem Statement Canvas : - Current State: Gross profit margin is 65 percent . - Desired State: Restore gross profit margin to 75 percent . - The Gap: 10 percentage point margin decline = $5M in lost gross profit annually . - Scope: Focus on gross margin (revenue minus direct costs), not operating margin. Time frame: last 18 months. - Success Metric: Identify the top 2-3 drivers of margin decline and provide actionable recommendations to recover 7+ percentage points. Step 2: Build the Top-Level Issue Tree Start with the fundamental formula: Gross Profit Margin = (Revenue - Direct Costs) / Revenue This uses two analytical lenses rather than two fully disjoint causal branches: 1. Has Revenue declined relative to direct costs? (Revenue is growing slower than costs.) 2. Have Direct Costs increased relative to revenue? (Costs are growing faster than revenue.) Customer mix can affect both revenue and cost to serve, so the analyst must assign definitions, avoid double-counting, and explain the overlap rather than label the lenses fully MECE. Step 3: Decompose Each Branch (Level 2) Branch 1: Revenue Analysis - 1A: Has Average Revenue Per Customer (ARPC) declined? - 1B: Has Customer Mix shifted toward lower-margin customers? Branch 2: Direct Cost Analysis - 2A: Have Cost of Goods Sold (COGS) per customer increased? - 2A1: Server/infrastructure costs. - 2A2: Third-party API costs. - 2A3: Customer success headcount (if counted as direct cost). - 2B: Has Customer Mix shifted toward higher-cost-to-serve customers? Step 4: Formulate Hypotheses for Each Endpoint - H1: ARPC has declined due to price discounting to hit growth targets. - H2: Customer mix has shifted toward SMB customers (lower ARPC) and away from Enterprise (higher ARPC). - H3: Server costs per customer have increased due to inefficient database queries. - H4: Third-party API costs have increased due to a new feature that calls expensive external services. - H5: Customer success team has grown faster than revenue to combat rising churn. Step 5: Prioritize Hypotheses for Testing Use the Prioritization Matrix (Framework 7) : - High Impact, High Certainty: H1 (pricing), H2 (customer mix), H5 (CS team growth). - High Impact, Low Certainty: H3 (server costs), H4 (API costs). Prioritize tests by expected impact on the decision, evidence cost, and the risk of overlooking a material driver. Preserve H3 and H4 as alternatives and define the evidence threshold for revisiting them. Step 6: Test the Hypotheses - H1 Test: Pull pricing data for all deals closed in the last 18 months. Calculate average deal size by quarter. Result: Average deal size declined 8 percent (discount rate increased from 10 percent to 18 percent) . - H2 Test: Segment customers by size (SMB, Mid-Market, Enterprise). Calculate revenue contribution by segment. Result: SMB grew from 20 percent to 35 percent of revenue. Enterprise declined from 50 percent to 40 percent . - H5 Test: Pull headcount data for Customer Success team. Calculate CS headcount as a share of revenue. Result: CS team grew 60 percent while revenue grew 30 percent. CS cost per customer increased 25 percent . Step 7: Build the Hypothesis Pyramid - Provisional governing thought: \"Subject to validating the alternatives and downside, repricing SMB customers and reviewing CS capacity may be ways to address the modeled margin decline.\" - Supporting Argument 1: Excessive discounting has reduced ARPC by 8 percent, costing $4M in gross profit annually . - Supporting Argument 2: Shift to SMB customers has reduced average margin per customer by 5 points, costing $2.5M . - Supporting Argument 3: CS team over-hiring has added $1.5M in direct costs without improving retention . Recommended actions: 1. Implement minimum price floors for SMB deals (no discounts above 15 percent) . 2. Launch a \"High-Touch Enterprise\" sales motion to rebalance customer mix. 3. Freeze CS hiring and improve CS efficiency with automation tools. Illustrative model output: Under the constructed assumptions above, these three actions are modeled to recover 7-9 percentage points of margin within 12 months; this is not an empirical forecast or benchmark." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-deep-dive-2-using-the-5-whys-to-diagnose-a-customer-churn-problem", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Deep Dive 2: Using the 5 Whys to Diagnose a Customer Churn Problem", "headingId": "chapter-09-problem-structuring-deep-dive-2-using-the-5-whys-to-diagnose-a-customer-churn-problem", "url": "#chapter-09-problem-structuring-deep-dive-2-using-the-5-whys-to-diagnose-a-customer-churn-problem", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Scenario: A B2B SaaS company sees monthly churn increase from 3 percent to 7 percent over 6 months. The VP of Sales blames the product. The VP of Product blames customer success. The team needs to test competing explanations and identify decision-relevant mechanisms. Step 1: State the Problem (The Symptom) \"Monthly customer churn has increased from 3 percent to 7 percent.\" Step 2: Develop and test a causal chain 1. Why has churn increased? → Because more customers are canceling within the first 90 days (early churn). 2. Why are more customers canceling within the first 90 days? → Because they're not seeing value from the product during onboarding. 3. Why are they not seeing value during onboarding? → Because the new onboarding process (launched 6 months ago) is self-service and doesn't ensure customers set up key integrations. 4. Why doesn't the self-service onboarding ensure customers set up key integrations? → Because the CS team removed the \"mandatory setup call\" to improve efficiency and scale. Customers now skip the integration step. 5. Why did the CS team remove the mandatory setup call? → Because they were given an OKR to reduce \"time-to-first-value\" from 30 days to 10 days, and the setup call added 5-7 days. The team optimized for the metric, not the outcome. Working causal hypothesis: The metric and process change may have contributed to weak integration setup and early churn. Confirm the sequence with cohort data, customer interviews, and a comparison group; also test product reliability, customer mix, pricing, and sales-quality alternatives. Step 3: Compare response hypotheses - Containment option: Reintroduce a setup call for a defined cohort while measuring delay, completion, burden, and churn. - Process option: Test assisted onboarding for one segment and an integration wizard for another; the displayed ACV threshold, if used, must be justified from economics and customer evidence rather than treated as a default. - System/incentive option: Test whether a milestone-quality measure adds useful information to time-to-value without creating new gaming or exclusion. Changing an OKR does not establish that behavior or churn will improve. None of these options is inherently “bad,” “good,” or “great.” Selection depends on the confirmed mechanism, experiment results, customer impact, capacity, and guardrails. Decision and learning plan: Pilot the revised onboarding design in comparable cohorts, define primary and guardrail metrics, and review at a pre-specified date. Do not forecast a return to the target range until the intervention effect and implementation capacity are supported by evidence." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-deep-dive-3-prioritization-matrix-for-a-product-roadmap", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Deep Dive 3: Prioritization Matrix for a Product Roadmap", "headingId": "chapter-09-problem-structuring-deep-dive-3-prioritization-matrix-for-a-product-roadmap", "url": "#chapter-09-problem-structuring-deep-dive-3-prioritization-matrix-for-a-product-roadmap", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Scenario: A product team has 15 potential features to build in the next quarter. They can only build 3-4. How do you prioritize? Step 1: List All Potential Features 1. Mobile app (iOS) 2. API rate limit increase 3. Advanced analytics dashboard 4. Single Sign-On (SSO) integration 5. Slack integration 6. Salesforce integration 7. Dark mode 8. Multi-language support (Spanish, French) 9. Team collaboration features 10. Custom reporting 11. Webhooks 12. Two-factor authentication (2FA) 13. Export to Excel/CSV 14. In-app notifications 15. Role-based permissions Step 2: Define Evaluation Criteria Use a Decision Criteria Weighting Model (Framework 9) . The illustrative weights below are value judgments, not empirical facts: - Customer Demand (30 percent): What share of the relevant segment has a validated need ? - Revenue Impact (30 percent): What evidence supports acquisition, retention, or price effects ? - Strategic Alignment (25 percent): Does this reinforce the chosen position and capability roadmap ? - Ease (15 percent): On a defined scale, how low are implementation effort, dependency, and delivery risk ? Step 3: Score Each Feature Create a scoring table using a documented 1-10 scale. These scores are constructed; 10 is favorable on every criterion, including Ease. | Feature | Customer Demand | Revenue Impact | Strategic | Ease | Weighted Score | |---------|------------------------|----------------------|-----------------|--------------|----------------| | SSO integration | 9 | 10 | 8 | 6 | 8.6 | | Salesforce integration | 8 | 9 | 7 | 5 | 7.6 | | 2FA | 7 | 8 | 9 | 9 | 8.1 | | Webhooks | 6 | 7 | 8 | 7 | 7.0 | | Mobile app (iOS) | 8 | 6 | 9 | 2 | 6.8 | | API rate limit increase | 5 | 5 | 6 | 10 | 6.0 | | Custom reporting | 6 | 5 | 5 | 4 | 5.2 | | ... | ... | ... | ... | ... | ... | An evidence owner should maintain each score and its confidence range. Recalculate under plausible alternative weights; if the top-ranked options change, the portfolio is weight-sensitive and the decision memo should say so. Step 4: Plot on Effort vs. Impact Matrix - Quick Wins (High Impact, Low Effort): 2FA, API rate limit increase. - Major Projects (High Impact, High Effort): SSO, Salesforce integration, Mobile app. - Fill-ins (Low Impact, Low Effort): Dark mode, Export to Excel. - Money Pits (Low Impact, High Effort): Multi-language support (if customer demand is low). Step 5: Final Prioritization Decision Given capacity for 3-4 features: 1. 2FA (weighted score: 8.1) — subject to validating the security and customer requirement. 2. SSO integration (weighted score: 8.6) — higher score, but sequencing depends on architecture and delivery capacity. 3. Salesforce integration (weighted score: 7.6) — subject to validating segment demand and revenue impact. 4. API rate limit increase (weighted score: 6.0) — a lower-scoring candidate that may deliver useful learning or unblock a dependency. Rationale: The constructed portfolio illustrates that a total score does not determine sequence. Architecture, capacity, mandatory security work, dependencies, learning value, and strategic fit remain part of the accountable decision." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-deep-dive-4-assumption-mapping-for-a-new-market-entry", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Deep Dive 4: Assumption Mapping for a New Market Entry", "headingId": "chapter-09-problem-structuring-deep-dive-4-assumption-mapping-for-a-new-market-entry", "url": "#chapter-09-problem-structuring-deep-dive-4-assumption-mapping-for-a-new-market-entry", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Scenario: A US-based SaaS company is considering entering the European market. The CEO believes it's a \"$100M opportunity.\" You need to identify and test the riskiest assumptions before committing $5M to the expansion. Step 1: List All Assumptions 1. European customers have the same pain points as US customers. 2. The product (currently only in English) will work for European customers. 3. European customers will pay similar prices to US customers. 4. We can hire a strong sales team in Europe within 6 months. 5. GDPR compliance won't require major product changes. 6. European competitors are 2-3 years behind us in product sophistication. 7. Our US marketing playbook (webinars, SEO, paid ads) will work in Europe. 8. We can achieve a 12-month CAC payback in Europe (same as US). 9. European customers will trust a US-based company with their data. 10. We can provide customer support in European timezones without a local CS team. Step 2: Map Assumptions on 2x2 Grid (Importance vs. Uncertainty) High Importance, High Uncertainty (Test First): - Assumption 2: Product will work for European customers (requires localization?). - Assumption 3: European customers will pay similar prices (different willingness to pay?). - Assumption 6: European competitors are behind (need validation). - Assumption 8: CAC payback will be 12 months (European CAC might be higher). High Importance, Apparently Low Uncertainty (Assign Owner and Verify): - Assumption 5: Data-protection and other regulatory requirements (requires qualified legal and privacy review; not a rapid market experiment). - Assumption 4: Can hire sales team (can test with LinkedIn recruiter outreach). Low Importance, High Uncertainty (Deprioritize): - Assumption 10: European timezone support (can solve with hiring). Low Importance, Low Uncertainty (Record and Monitor): - Assumption 1: Similar pain points (desk research is preliminary evidence, not confirmation). Step 3: Design Experiments to Test High-Risk Assumptions Experiment 1: Test Assumption 2 (Product Localization) - Hypothesis: European customers can use the English-language product without major friction. - Test: Offer free trials to 20 European prospects. Track activation rate, time-to-value, and support tickets related to language/localization. - Success Criteria: Activation rate above 60 percent (comparable to US). Fewer than 10 percent of support tickets related to localization . - Cost: $5K in sales time + free trial credits . - Timeline: 6 weeks. Experiment 2: Test Assumption 3 (Pricing) - Hypothesis: European customers will pay $500/month (our US price) for the product . - Test: For this constructed exercise, treat interviews or a pricing survey as exploratory evidence, then—where lawful and appropriate—compare actual offers or pilots. Do not treat stated willingness to pay as observed purchase behavior . - Success Criteria: Median willingness-to-pay is $400-600/month (within 20 percent of US pricing) . - Cost: $10K for response collection tooling and incentives . - Timeline: 4 weeks. Experiment 3: Test Assumption 8 (CAC Payback) - Hypothesis: We can acquire European customers within a 12-month CAC-payback target under a contribution-margin model; the target is not a revenue-only calculation. - Test: Run a 3-month paid marketing pilot in UK and Germany. Spend $50K on Google Ads and LinkedIn. Track CAC and conversion rates . - Success Criteria: CAC is below 12 × monthly contribution margin for the defined segment, using observed gross margin, service cost, retention, and cash-timing assumptions. A $500/month × 12 threshold would be revenue payback, not CAC payback, unless contribution margin were 100 percent . - Cost: $50K ad spend + $10K agency fees . - Timeline: 3 months. Step 4: Update, Rather Than Mechanically Trigger, the Decision - Compare observed results with pre-specified thresholds and confidence intervals. - Update the financial model and regulatory, localization, hiring, support, and competitive assumptions. - Decide among further research, a bounded pilot, adaptation, delay, or no entry; document the owner, dissent, and review triggers. Illustrative evidence budget: The example allocates $75K over three months. A real information budget should reflect decision stakes, test validity, privacy and legal duties, participant protection, and the cost of false confidence—not merely its size relative to the investment. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mistake-1-building-an-issue-tree-before-defining-the-problem", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mistake 1: Building an Issue Tree Before Defining the Problem", "headingId": "chapter-09-problem-structuring-mistake-1-building-an-issue-tree-before-defining-the-problem", "url": "#chapter-09-problem-structuring-mistake-1-building-an-issue-tree-before-defining-the-problem", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Error: Teams jump straight into building an issue tree without aligning on the problem statement. Result: The tree answers the wrong question, and weeks of analysis are wasted. How to Avoid: Establish a current Problem Statement Canvas (Framework 6) before investing heavily in decomposition. Record disagreements, missing voices, and reframing triggers. Alignment can be partial, and material discovery can justify revising the frame. Constructed example: A team spends three weeks diagnosing retail profitability before learning that the decision owner needs to decide whether to sell the business. Clarifying the decision earlier would have changed the valuation, buyer, and timing evidence required." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mistake-2-using-mece-as-a-perfectionism-excuse", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mistake 2: Using MECE as a Perfectionism Excuse", "headingId": "chapter-09-problem-structuring-mistake-2-using-mece-as-a-perfectionism-excuse", "url": "#chapter-09-problem-structuring-mistake-2-using-mece-as-a-perfectionism-excuse", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Error: Teams spend days debating whether their categories are \"truly MECE\" and redesigning their issue tree to achieve theoretical perfection. This is analysis paralysis disguised as rigor. How to Avoid: Apply a stopping rule to MECE itself. Ask whether the structure is sufficiently complete for the stakes and whether another branch could plausibly change the decision. Document known overlap, edge cases, and exclusions; seek an independent coverage challenge for consequential decisions. Constructed example: A strategy team debates whether international partnerships belong under revenue growth or cost reduction. The item may legitimately affect both. Choose a primary location, cross-reference the secondary effect, and test the decision-relevant hypotheses rather than claiming the overlap does not matter." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mistake-3-confusing-the-hypothesis-pyramid-with-a-data-dump", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mistake 3: Confusing the Hypothesis Pyramid with a Data Dump", "headingId": "chapter-09-problem-structuring-mistake-3-confusing-the-hypothesis-pyramid-with-a-data-dump", "url": "#chapter-09-problem-structuring-mistake-3-confusing-the-hypothesis-pyramid-with-a-data-dump", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Error: Teams build a presentation with the \"pyramid\" structure but fill it with every data point they collected, thinking \"more data = more persuasive.\" Result: The audience is overwhelmed and the core message is lost. How to Avoid: Use the smallest number of supporting reasons that faithfully represents the logic. For each reason, show the most decision-relevant evidence, confidence, and counterevidence, with traceable supporting detail available for review. Clarity is the goal; a fixed number of arguments or data points is not an evidence rule. Constructed example: An investment team puts the provisional recommendation and three material arguments in the main decision memo while retaining valuation assumptions, diligence findings, downside cases, and dissent in traceable appendices. Concision does not remove the need to inspect the full evidence before authorization." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mistake-4-stopping-at-the-fourth-why-in-the-5-whys", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mistake 4: Stopping at the Fourth \"Why\" in the 5 Whys", "headingId": "chapter-09-problem-structuring-mistake-4-stopping-at-the-fourth-why-in-the-5-whys", "url": "#chapter-09-problem-structuring-mistake-4-stopping-at-the-fourth-why-in-the-5-whys", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Error: Teams get uncomfortable with the 5 Whys when it reveals organizational or leadership failures. They stop at Why #4 (\"the process is broken\") and avoid Why #5 (\"why is the process broken?\") because the answer is politically sensitive (\"because leadership doesn't prioritize quality\"). How to Avoid: Establish psychological safety before running a 5 Whys exercise. Make it clear that the goal is to fix the system, not to blame individuals. If the fifth Why points to a leadership failure, that's valuable insight—it means the solution requires leadership behavior change, not just a process tweak. Don't avoid the hard truths. Constructed example: A manufacturing team's questioning links quality defects to inspection capacity and budget incentives. The team then tests that proposed chain against process data and alternative causes before changing controls or incentives." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-mistake-5-treating-prioritization-matrices-as-objective-truth", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Mistake 5: Treating Prioritization Matrices as Objective Truth", "headingId": "chapter-09-problem-structuring-mistake-5-treating-prioritization-matrices-as-objective-truth", "url": "#chapter-09-problem-structuring-mistake-5-treating-prioritization-matrices-as-objective-truth", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Error: Teams create an Effort vs. Impact matrix, score everything, and then treat the output as gospel. \"The matrix says we should do Initiative X, so we have to do it.\" This ignores strategic judgment and context. How to Avoid: Use prioritization matrices as input to a decision , not as the decision itself . After plotting initiatives on the matrix, ask: - \"Does this prioritization align with our strategic priorities?\" (If your strategy is to move upmarket, but the matrix says to prioritize SMB features, override the matrix.). - \"What is the sequencing dependency?\" (Maybe the #2 priority must be done before the #1 priority.). - \"What are we learning?\" (Maybe you should do the high-uncertainty initiative first to learn, even if it's not the highest-scored.). Judgment beats algorithms. The matrix is a tool to structure thinking, not a replacement for strategic leadership. Constructed example: A product team's matrix ranks a cosmetic feature first, but the decision owner selects an enterprise-security dependency after documenting strategic fit, customer evidence, implementation risk, and the reasons for overriding the score. Whether that is the right call depends on those facts and the resulting outcomes. ---" }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-final-thoughts-from-frameworks-to-judgment", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Final Thoughts: From Frameworks to Judgment", "headingId": "chapter-09-problem-structuring-final-thoughts-from-frameworks-to-judgment", "url": "#chapter-09-problem-structuring-final-thoughts-from-frameworks-to-judgment", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Issue trees, MECE, pyramid logic, 5 Whys, prioritization matrices, and assumption maps are widely used practitioner tools for making reasoning visible. Their usefulness depends on the problem, evidence, facilitation, incentives, and accountable judgment; none guarantees a correct answer. The practical lesson is proportionate judgment : use enough structure to improve the decision, then simplify when additional framework work no longer changes evidence, options, or safeguards." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-when-to-follow-the-frameworks", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "When to Follow the Frameworks", "headingId": "chapter-09-problem-structuring-when-to-follow-the-frameworks", "url": "#chapter-09-problem-structuring-when-to-follow-the-frameworks", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use more of this structure when: - The problem is complex and ambiguous: If you don't know where to start, an Issue Tree forces structure. - Stakeholders are misaligned: The Problem Statement Canvas makes the disagreement, authority, and evidence needs visible. - The stakes are high and hard to reverse: Use deeper evidence, scenarios, independent challenge, risk analysis, and decision governance; no fixed stack is sufficient for every decision. - Decision makers need a concise account: Pyramid logic can communicate a recommendation and its support, provided alternatives, uncertainty, and dissent remain visible." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-when-to-break-the-frameworks", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "When to Break the Frameworks", "headingId": "chapter-09-problem-structuring-when-to-break-the-frameworks", "url": "#chapter-09-problem-structuring-when-to-break-the-frameworks", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Break or simplify the frameworks when: - The problem is simple and safely reversible: Apply a lightweight diagnosis and monitor the result. A simple appearance does not excuse skipping safety, security, legal, or root-cause obligations. - Speed matters more than perfection: In fast-moving environments or crises, a bounded and reversible decision made today may be preferable to more elaborate analysis after the decision window has closed; state the uncertainty and safeguards. - A sponsor has already chosen an answer: Do not disguise advocacy as analysis. Clarify whether the mandate is implementation planning or decision review, document assumptions and dissent, preserve escalation paths, and refuse unlawful or unethical concealment. - The framework is creating analysis paralysis: If your team has spent 2 weeks debating whether a category is \"truly MECE,\" you've lost the plot. Document the ambiguity and move forward." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-the-operator-s-mindset-frameworks-judgment", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "The Operator's Mindset: Frameworks + Judgment", "headingId": "chapter-09-problem-structuring-the-operator-s-mindset-frameworks-judgment", "url": "#chapter-09-problem-structuring-the-operator-s-mindset-frameworks-judgment", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The practical distinction is judgment : - A mechanical application treats the framework output as the answer. - An accountable operator uses the framework to structure thinking, challenge assumptions, interpret evidence, and document the final call. Example: - Junior Analyst: \"Our prioritization matrix says we should build Feature X. Therefore, we must build Feature X.\" - Seasoned Operator: \"Our prioritization matrix says we should build Feature X. But I know from experience that our estimates are often materially wrong. I also know that Feature Y, which scored lower, aligns better with our 3-year strategy. So we're doing Feature Y, and I'm documenting why we overruled the matrix.\" The frameworks in this chapter are tools. Use them to clarify the decision, expose assumptions, structure evidence, compare options, and communicate reasoning. The accountable human decision owner makes the decision and owns the documented trade-offs, uncertainty, and consequences." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-applied-exercise-structure-a-funding-decision", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Applied Exercise: Structure a Funding Decision", "headingId": "chapter-09-problem-structuring-applied-exercise-structure-a-funding-decision", "url": "#chapter-09-problem-structuring-applied-exercise-structure-a-funding-decision", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scenario: A constructed B2B software company can fund only one of three options next quarter: improve onboarding, build an enterprise-security capability, or enter a new geographic segment. Evidence is incomplete, and the sales, product, finance, customer-success, legal, and security leaders disagree. Prepare a two-page decision brief and a one-page evidence appendix: 1. Write a versioned problem statement with the decision owner, affected stakeholders, constraints, ethical and legal boundaries, success measures, time horizon, and no-action alternative. 2. Build a provisional issue tree and identify at least two competing hypotheses. For each, state one observation that would increase confidence and one that would decrease it. 3. Create decision criteria with explicit scales, weights, data sources, confidence ranges, and evidence owners. Include gates for non-compensable obligations. 4. For the leading uncertain option, draw decision and chance nodes, define consequences, calculate expected monetary value and break-even probability, and identify whether risk preference could change the recommendation. Use the worked method in Chapter 22. 5. Specify one evidence test. Update a prior probability with the test result, compare expected value with and without the information, subtract the test cost, and explain whether the information can actually change the action. 6. Run a sensitivity analysis: change each major weight, probability, consequence, and uncertain score across a defensible range and report whether the ranking changes. 7. Conduct a premortem and add the three most consequential failure scenarios to a risk register with mitigation and monitoring owners. 8. Recommend fund, pilot, delay, or reject. State reversibility, residual uncertainty, dissent, review date, and evidence that would trigger reversal. Author-created assessment rubric (100 points): framing and stakeholder/ethical scope (20); branch and hypothesis quality (20); evidence traceability and disconfirming tests (20); trade-off and sensitivity analysis (20); decision governance, risk, and communication clarity (20)." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-related-chapters", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Related Chapters", "headingId": "chapter-09-problem-structuring-related-chapters", "url": "#chapter-09-problem-structuring-related-chapters", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Chapter 2: Business Law, Governance & Ethics — duties, stakeholders, escalation, and ethical constraints. - Chapter 3: Strategy & Competitive Analysis — strategic alternatives and external analysis. - Chapter 4: Financial Analysis & Valuation — scenario economics and value consequences. - Chapter 6: Operations & Supply Chain — process evidence, variation, capacity, and improvement methods. - Chapter 8: Strategy Execution — translating a decision into objectives, measures, and review cadence. - Chapter 11: Project Management — plans, risks, dependencies, and execution governance. - Chapter 12: Client Management — sponsor alignment, dissent, and communication. - Chapter 16: AI Strategy & Data-Driven Decisions — AI/non-AI alternatives, controlled pilots, evaluation, and change gates. - Chapter 22: Data Analysis & Insights — expected value, Bayesian updating, information value, utility, analytical design, and evidence interpretation." }, { "id": "chapter-09-problem-structuring::chapter-09-problem-structuring-your-action-items", "kind": "chapter", "itemSlug": "chapter-09-problem-structuring", "itemTitle": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "heading": "Your Action Items", "headingId": "chapter-09-problem-structuring-your-action-items", "url": "#chapter-09-problem-structuring-your-action-items", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "After reading this chapter, you should be able to: 1. Build and revise an issue tree to decompose a suitable business problem into testable hypotheses without claiming guaranteed completeness. 2. Apply causal questioning proportionately and test proposed root causes against evidence and alternatives. 3. Structure a pyramid communication that keeps recommendation, evidence, uncertainty, alternatives, and dissent distinct. 4. Use a prioritization or weighting model as an auditable input to resource allocation, with sensitivity analysis and accountable override logic. 5. Structure uncertain choices with decision/chance nodes, gates, consequences, probabilities, break-even logic, and sensitivity analysis. 6. Map assumptions and choose evidence work based on consequence, uncertainty, net information value, ethics, and reversibility. The expert move is not automatically to use or skip a framework. It is to choose a proportionate method, make its limits visible, and keep human ownership of the decision." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Advanced Consulting Frameworks and Integration", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration", "url": "#chapter-10-advanced-consulting-frameworks-and-integration", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-manager-decision-outcomes-and-boundaries", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Manager Decision Outcomes and Boundaries", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-manager-decision-outcomes-and-boundaries", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-manager-decision-outcomes-and-boundaries", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "After this chapter, a manager should be able to: 1. Select and combine frameworks around a defined decision without double-counting evidence or treating a template as proof. 2. Distinguish diagnosis, hypothesis, valuation, governance, implementation, and monitoring outputs. 3. Reconcile contradictory financial, customer, operational, people, technology, legal, and risk evidence. 4. Design staged action with accountable owners, approval authority, learning criteria, and stop, separation, or revisit options. This chapter teaches integration judgment. It does not certify a universal framework stack or replace transaction, competition, securities, employment, privacy, tax, accounting, cybersecurity, or other specialist advice. For acquisitions and major transformations, use approved confidentiality, privilege, clean-team, data-room, employee-contact, and decision-rights protocols. Applied exercise — constructed acquisition: For a fictional acquisition, produce a deal-thesis tree, evidence-and-owner matrix, contradiction log, downside case, Day 1 minimum-control plan, and three integration options: full, selective, and separate. Explain which framework you rejected, identify the authority for each decision, and set three evidence-based stop or revisit rules. Link the strategy thesis to Chapter 3, valuation to Chapter 4, project governance to Chapter 11, and organizational change to Chapter 17. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-executive-summary", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Executive Summary", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-executive-summary", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-executive-summary", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter moves from discrete analytical tools to integrated frameworks used in consulting and internal strategy work to manage complex, enterprise-wide challenges. We will examine how to diagnose organizational relationships using the McKinsey 7S [BB-C10-S01], make a business-model hypothesis visible with the Business Model Canvas [BB-C10-S03], and clarify decision roles with Bain's RAPID framework [BB-C10-S04]. The centerpiece is a constructed, multi-phase playbook for launching a new business unit that integrates selected frameworks from across this book; it is a teaching aid, not a universal stack or operating prescription. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-troubleshooting-guide-advanced-frameworks", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Troubleshooting Guide: Advanced Frameworks", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-troubleshooting-guide-advanced-frameworks", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-troubleshooting-guide-advanced-frameworks", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptom: \"We did a 7S analysis and it just confirmed that everything is a mess. We don't know where to start.\" Diagnosis: The 7S framework is a relational diagnostic, not proof that one element is the root cause or linchpin. Misalignments can be interacting, reciprocal, or symptoms of evidence outside the model. Action: Define the decision, test multiple causal explanations, map dependencies and affected groups, and compare interventions by evidence, authority, reversibility, harm, cost, and learning value. Start with the smallest responsible action that can distinguish the hypotheses; do not assume one “S” will create a positive ripple. Symptom: \"Our Business Model Canvas looks beautiful, but we have no idea if it's realistic.\" Diagnosis: You have treated the canvas as a final document, not as a set of hypotheses to be tested. Action: For every box on the canvas, identify the riskiest assumption. Use the Assumption Mapping framework (Chapter 9) to prioritize these assumptions. Then, design and run experiments (e.g., landing page tests, customer interviews) to validate them before investing significant resources. Symptom: \"We implemented RAPID, but decisions are still slow because the person with the 'D' is too scared to make the call.\" Hypotheses to test: Authority may be unclear, decision evidence may be weak, incentives may punish candor, or the role holder may lack support. Psychological safety is one possible factor, not a diagnosis from this symptom alone. [BB-C10-S06] Action: Review the authority, stakes, information, escalation path, incentives, and prior treatment of dissent. Leaders can evaluate process quality separately from outcome while preserving accountability for negligence, misconduct, or ignored controls. Symptom: \"Our New Business Unit launch is bogged down in corporate bureaucracy and moving too slowly.\" Diagnosis: Process burden is one hypothesis. Delay may also reflect genuine safety, legal, financial, security, capacity, evidence, dependency, or authority requirements. Action: Compare separation, partial autonomy, shared services, protected capacity, and integration using the venture's dependencies and risks. Governance, budget, and metrics should match the decision and obligations; neither six months without revenue targets nor organizational separation is a universal prescription. Symptom: \"We completed a comprehensive M&A due diligence and identified no red flags, but post-acquisition integration is failing.\" Diagnosis: Your due diligence checklist focused on auditable, quantifiable risks (financials, legal, technology) and missed the unquantifiable but critical risks (culture, talent, leadership compatibility). Action: Revisit whether the approved diligence scope tested the operating model, leadership dependencies, critical capabilities, workforce obligations, and integration assumptions. Use 7S as one prompt set, not as a finding of cultural compatibility. [BB-C10-S01] Boundary: The confidentiality, privacy, employment, antitrust, consent, and documentation examples are author-created governance prompts, not legal advice; authorized counsel, HR, privacy, security, and transaction owners must define the lawful evidence process. Symptom: \"Our Value Chain Analysis identified cost reduction opportunities, but implementing them caused quality problems and customer complaints.\" Diagnosis: You optimized for cost without understanding which activities in the value chain directly drive customer value vs. which are truly non-value-add. Action: Before changing an activity, test its effects on customer value, safety, quality, reliability, employees, suppliers, controls, capacity, and differentiation. A customer-journey or jobs lens can help, but willingness to pay is not the only criterion and no activity is proven waste from the framework alone. Symptom: \"We used a maturity ladder and spent two years moving upward, but business results did not improve.\" Diagnosis: You treated the ladder as an outcome rather than a hypothesis about capability development. A higher label does not prove better performance. Action: Compare capability investments by decision need, current evidence, legal/control minimums, risk, expected benefit, cost, dependency, and stop rules. Organization size does not determine a universal HR or product maturity level, and “hygiene” capabilities can be critical obligations. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-1-new-business-unit-launch-framework-integrated", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "1. New Business Unit Launch Framework (Integrated)", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-1-new-business-unit-launch-framework-integrated", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-1-new-business-unit-launch-framework-integrated", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "New Business Unit Launch Framework Integrated Corporate Venture Playbook" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-overview", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-overview", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-overview", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Launching a new business unit, product line, or corporate venture can expose a firm to material strategic, financial, operational, legal, and reputation risk. The evidence-gated launch model below is a constructed integration aid. It organizes evidence and decisions; it does not prescribe a universal sequence, duration, funding model, or outcome." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-the-six-phase-evidence-gated-launch-model", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "The Six-Phase Evidence-Gated Launch Model", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-the-six-phase-evidence-gated-launch-model", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-the-six-phase-evidence-gated-launch-model", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 10.1. Evidence-gated corporate-venture loop (constructed). Each phase can run in parallel or repeat. A gate may authorize the next test, require a pivot or recycle, pause for missing evidence, or stop the venture; elapsed time is context-specific. Text equivalent: Define the strategic thesis and authority, design the operating and financial hypothesis, run the smallest responsible pilot, then decide whether evidence supports scaling. Optimization and parent-company integration follow only when they serve the venture thesis. Monitoring can return the team to any earlier phase or stop the work." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-phase-1-strategic-assessment-the-sanity-check", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 1: Strategic Assessment — The Sanity Check", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-phase-1-strategic-assessment-the-sanity-check", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-phase-1-strategic-assessment-the-sanity-check", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: To test the strategic rationale and financial feasibility of the new venture, update confidence, and identify conditions for further work before committing significant resources. Table 10.1. Phase 1 evidence-routing prompts (constructed). This teaching table links selected frameworks to questions and deliverables; it is not a complete diligence or investment checklist. | Framework Applied | Key Question It Answers | Deliverable | | :--- | :--- | :--- | | Porter's Five Forces (Chapter 3) | Which structural forces shape profitability and bargaining power? | Assumption-backed industry analysis. | | Blue Ocean Strategy (Chapter 3) | Which value factors could be changed, and how might rivals or customers respond? | A testable value-curve hypothesis. | | VRIO Analysis (Chapter 3) | Which resources might support advantage, and what evidence could disconfirm that view? | Resource and capability evidence map. | | Unit Economics (Chapter 4) | Which cohort, margin, service-cost, retention, and cash assumptions determine viability? | Scenario ranges with definitions and owners. | | DCF Model (Chapter 4) | How sensitive is value to cash-flow, timing, financing, and terminal assumptions? | Reconciled downside, base, and upside scenarios. | Gate decision: Record the authority, evidence quality, unresolved contradiction, downside exposure, next test, and stop condition. “Attractive,” “advantaged,” and “sound economics” are conclusions to support, not checklist answers." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-phase-2-business-planning-the-blueprint", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 2: Business Planning — The Blueprint", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-phase-2-business-planning-the-blueprint", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-phase-2-business-planning-the-blueprint", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: To create a detailed operational, financial, and go-to-market plan. Table 10.2. Phase 2 planning prompts (constructed). The listed frameworks are examples of inputs to a working plan; scope, evidence, and specialist review remain decision-specific. | Framework Applied | Key Question It Answers | Deliverable | | :--- | :--- | :--- | | Business Model Canvas (this chapter) | What is the current business-model hypothesis on one page? | A working 9-box hypothesis map. | | Go-to-Market Strategy (Chapter 14) | Who are our customers and how will we reach them? | A detailed GTM plan including target segments, channels, and messaging. | | Capacity Planning (Chapter 6) | What resources do we need to operate? | A headcount, technology, and capex plan. | | Organizational Design (Chapter 7) | How should the new venture team be structured? | An initial org chart and definition of the venture's relationship to the parent co. |" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-phase-3-pilot-mvp-the-reality-test", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 3: Pilot / MVP — The Reality Test", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-phase-3-pilot-mvp-the-reality-test", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-phase-3-pilot-mvp-the-reality-test", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: To test the most critical assumptions of the business plan with real customers using a Minimum Viable Product (MVP). Table 10.3. Phase 3 pilot prompts (constructed). The table organizes learning questions; it does not establish that a pilot is safe, lawful, representative, or sufficient for scale. | Framework Applied | Key Question It Answers | Deliverable | | :--- | :--- | :--- | | Lean Startup / MVP Definition (Chapter 13) | What is the smallest possible thing we can build to learn? | A scoped MVP with a clear learning objective. | | Assumption Mapping (Chapter 9) | What are our riskiest \"leaps of faith\"? | A prioritized list of assumptions to be tested during the pilot. | | A/B Testing (Chapter 5) | Which version of our landing page/ad/feature converts better? | A series of rapid experiments to optimize the user funnel. | Go/no-go/pivot decision: State the tested uncertainty, sample and limitations, observed behavior, safety and legal constraints, cash remaining, and predeclared decision rule. A pilot can update confidence; it rarely “validates the business model” by itself." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-phases-4-5-and-6-scale-optimize-and-integrate", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Phases 4, 5, and 6: Scale, Optimize, and Integrate", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-phases-4-5-and-6-scale-optimize-and-integrate", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-phases-4-5-and-6-scale-optimize-and-integrate", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "These phases are decision points, not guaranteed outcomes: - Phase 4 — Staged launch and scale: The accountable owner compares demand, delivery, economics, capacity, safety, compliance, and control evidence against the approved scale gate; a constrained launch, recycle, pause, or stop remains available. - Phase 5 — Optimize economics and controls: The team tests unit economics, service quality, reliability, security, privacy, workforce load, and operating controls against defined outcomes; it does not optimize a metric in isolation. - Phase 6 — Integrate selectively or remain separate: The parent and venture compare shared services, interfaces, autonomy, separation, and exit options against dependencies, deal thesis, rights, risk, and reversibility." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the launch model to make authority, assumptions, evidence owners, decision gates, and stop conditions visible before committing resources. - Treat each phase as a revisable hypothesis; a pilot, pause, selective integration, or responsible stop may be the best decision. - Reconcile strategy, economics, operations, people, legal, security, and customer evidence before a gate authorizes scale." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A phase sequence can create false confidence if the decision, authority, evidence quality, or failure consequences are undefined. - “MVP,” “scale,” and “integration” are not universal thresholds; safety, legal, workforce, privacy, security, and control obligations may require a different path. - A comprehensive-looking playbook can double-count evidence or hide dissent; document what the model omits and why the decision remains reversible or not." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-connections", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-connections", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-connections", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: This master framework is a consumer of almost every other strategic framework in this book. Output: A traceable launch, pivot, separation, pause, or stop decision with assumptions, owners, evidence, approvals, and monitoring. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-2-mckinsey-7s-framework", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "2. McKinsey 7S Framework", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-2-mckinsey-7s-framework", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-2-mckinsey-7s-framework", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "McKinsey 7S Framework Organizational Alignment Diagnostic" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-overview-2", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-overview-2", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-overview-2", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The 7S Framework is a McKinsey-associated model for examining relationships among seven organizational elements. It can help a team formulate hypotheses about execution problems, but it does not prove that “alignment” causes performance or that a problem belongs inside the seven categories. [BB-C10-S01] Attribution and permissions boundary: “McKinsey 7S” is a named third-party model. This chapter provides a bounded summary and constructed prompts; it does not reproduce a proprietary instrument or imply endorsement." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-2", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-2", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The seven elements are divided into \"Hard S's\" (easy for management to define) and \"Soft S's\" (harder to change, more cultural). 1. Strategy: The plan to build and maintain competitive advantage. 2. Structure: The way the organization is structured (org chart). 3. Systems: The daily activities and procedures that staff use to get the job done. --- 4. Shared Values: The core values of the company, evident in its culture and work ethic. 5. Style: The style of leadership adopted. 6. Staff: The employees and their general capabilities. 7. Skills: The actual skills and competencies of the organization's employees. The analysis involves mapping out the current state of each \"S\" and identifying points of inconsistency or misalignment. For example, a company might have a \"Strategy\" of rapid innovation but a \"Structure\" that is a rigid hierarchy and a \"Style\" of leadership that punishes failure. The 7S model makes this misalignment obvious." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-2", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-2", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use 7S to surface relationships among strategy, structure, systems, shared values, style, staff, and skills that deserve testing. - Compare at least two explanations for an operating problem and identify affected groups, evidence owners, and decision authority before intervening. - Track whether a change improves the defined outcome while monitoring control failures, workload, dissent, and unintended effects." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-2", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-2", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The framework is descriptive: apparent coherence may fit the wrong strategy, suppress challenge, or become brittle as conditions change. - Seven categories cannot capture every causal mechanism, affected group, power relationship, control obligation, or external constraint. - Do not prescribe “deliberate misalignment” from the template; test which tensions create useful options, which create harm or control failure, and what evidence would justify changing an element." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-connections-2", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-connections-2", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-connections-2", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The \"Strategy\" element should be clearly defined from your work in Chapter 3 . The \"Shared Values\" come from your Strategic Pyramid (Chapter 8) . Output: The diagnosis of misalignment is a primary driver for a Change Management (Chapter 7) initiative. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-3-competitive-advantage-context-check", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "3. Competitive-Advantage Context Check", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-3-competitive-advantage-context-check", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-3-competitive-advantage-context-check", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Competitive-Advantage Context Check Competitive Environment Analysis" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-overview-3", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-overview-3", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-overview-3", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This constructed competitive-advantage context check prevents a team from selecting a strategy before defining the market and evidence. It does not assign an industry to a universal quadrant. Use the competitive analysis in Chapter 3 for the underlying industry, resource, and positioning work." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-3", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-3", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define the market boundary, customer job, alternatives, geography, time horizon, and unit of analysis. 2. Identify candidate sources of value and advantage: scale, switching costs, network effects, learning, access, regulation, brand, location, relationships, or specialized capabilities. 3. Record the evidence, imitation path, required investment, failure mode, and rival or customer response for each candidate. 4. Compare strategic options under downside and changed-condition scenarios rather than accepting a label as a guiding policy." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-3", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-3", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define the market, customer job, alternatives, time horizon, unit of analysis, and decision before naming a source of advantage. - Require evidence for value, imitation barriers, required investment, failure modes, and likely responses rather than treating a quadrant or label as a strategy. - Revisit the advantage hypothesis when the market boundary, customer behavior, rival response, regulation, or operating capability changes." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-3", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-3", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- This prompt set is constructed; it does not replace industry analysis, customer evidence, competitive research, or specialist legal/regulatory review. - Advantage categories overlap and may be effects of the same underlying capability; avoid double-counting evidence or treating a label as causal. - A favorable context check does not establish persistence, profitability, ethical acceptability, or the organization's right or ability to act." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-connections-3", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-connections-3", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-connections-3", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: This analysis requires a deep understanding of your industry structure from Porter's Five Forces (Chapter 3) . Output: A set of evidence-backed strategic hypotheses for Chapter 3, including conditions that would invalidate each one. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-4-bain-s-rapid-decision-framework", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "4. Bain's RAPID Decision Framework", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-4-bain-s-rapid-decision-framework", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-4-bain-s-rapid-decision-framework", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Bain's RAPID Decision Framework Clarifying Decision Rights" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-overview-4", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-overview-4", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-overview-4", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Unclear decision roles can contribute to delay and rework. Bain's RAPID decision framework distinguishes five roles for a defined decision. [BB-C10-S04] It does not replace statutory authority, board or committee duties, consent rights, collective-bargaining obligations, professional accountability, or emergency command structures. Attribution and permissions boundary: “RAPID” is a Bain-associated registered mark. This chapter summarizes the role logic and uses constructed prompts; permissions and trademark treatment remain a publisher decision." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-4", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-4", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For a defined decision, map the roles only after verifying actual authority. Some roles may contain several people or a collective body; avoid duplicate or ambiguous ownership without forcing false singularity. 1. Recommend: The person or team responsible for gathering input and proposing a course of action. 2. Agree: People whose approval or consent is required before the decision can move forward under the applicable governance, contract, labor, regulatory, professional, or board authority. A veto exists only where that authority grants it; use this role sparingly. 3. Perform: The people who will execute the decision once it is made. 4. Input: People whose expertise is valuable and must be consulted before a recommendation is made. The \"Recommend\" person must listen to them, but does not have to agree. 5. Decide (The \"D\"): The authorized decision holder under the applicable governance model; this may be an individual or a collective body. Role clarity can reduce avoidable routing ambiguity, but it does not guarantee speed or decision quality." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-4", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-4", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use RAPID for consequential or recurring decisions where routing ambiguity materially impairs action, learning, or accountability. - Record the actual authority, required approvals, consultation duties, decision date, evidence threshold, and escalation route before assigning roles. - Review whether the decision process protects dissent, affected rights, safety, compliance, and professional accountability instead of measuring speed alone." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-4", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-4", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- RAPID's “D” is useful only after the actual governance authority is known; a board, committee, regulator, licensed professional, worker representative, or contracting party may hold a required approval or shared duty. - Role labels can hide collective authority, dissent, professional accountability, consent rights, or emergency command structures when a team forces a false singular decision holder. - Role clarity may reduce routing ambiguity but does not guarantee speed, decision quality, lawful authority, or a good outcome; do not invent a “Distributed D” that obscures accountability." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-connections-4", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-connections-4", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-connections-4", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The need for a RAPID is often identified when a Process Flow Diagram (Chapter 6) shows a decision diamond with multiple arrows and long delays. Output: A clear set of RAPID roles is a key part of effective Corporate Governance (Chapter 2) and a well-designed Organizational Structure (Chapter 7) . ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-5-value-chain-analysis-digital-version", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "5. Value Chain Analysis (Digital Version)", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-5-value-chain-analysis-digital-version", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-5-value-chain-analysis-digital-version", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Value Chain Analysis Activity-Based Advantage" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-overview-5", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-overview-5", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-overview-5", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Harvard Business School's Institute for Strategy and Competitiveness attributes value chain analysis to Michael Porter and defines it as disaggregating a company into strategically relevant activities to examine sources of higher prices or lower costs. It also places a firm's activities within a broader upstream and downstream value system and treats activity configuration and linkages as strategic choices. [BB-C10-S02] Stabell and Fjeldstad show that chains are not the only value-creation configuration: intensive problem solving and mediated customer exchange may be better represented as value shops or value networks. [BB-C10-S07] The operating prompts below are an author adaptation. Use them to investigate activity economics and linkages; do not infer that an activity is “world-class,” causally advantaged, or appropriately modeled as a linear chain without comparative evidence." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-5", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-5", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Map operating activities: For a transformation-oriented chain, familiar labels include: Inbound Logistics - Operations - Outbound Logistics - Marketing & Sales - Service. 2. Map enabling activities: Familiar labels include: Procurement, Technology Development, Human Resources, Firm Infrastructure. 3. Analyze Each Activity: For each activity, ask: Cost Driver: How does this activity contribute to our overall cost structure? Can we perform it more efficiently than competitors? Value Driver: How does this activity contribute to customer value and differentiation? Can we perform it in a unique way? 4. Test the configuration: If value is created mainly through intensive problem solving or mediated exchanges, compare a value shop or value network with the chain model. For a digital platform, Platform Development , Participant Acquisition , Matching/Liquidity , and Trust & Safety are constructed prompts, not canonical Porter or Stabell–Fjeldstad activity labels." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-5", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-5", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use an activity map to connect cost, customer value, quality, reliability, control, capacity, and differentiation evidence before recommending a change. - Test whether a chain, value shop, value network, or hybrid better represents how the organization actually creates and exchanges value. - Protect safety-critical, rights-protecting, and control activities from being labeled waste without consequence and failure-mode evidence." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-5", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-5", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A value chain is not a complete causal model and may fit poorly where value is created through iterative problem solving, networks, platforms, or public obligations. - Cost and value drivers can be shared, delayed, or correlated; avoid attributing advantage to one activity without comparative evidence. - Lower cost is not automatically higher value; optimization can damage quality, resilience, employee conditions, customer trust, or control performance." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-connections-5", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-connections-5", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-connections-5", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: Requires an understanding of your relative cost position from Financial Analysis (Chapter 4) and your key strengths from a VRIO Analysis (Chapter 3) . Output: The analysis identifies the specific internal activities that need improvement, which becomes the focus of Lean or Six Sigma projects (Chapter 6) . ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-6-business-model-canvas", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "6. Business Model Canvas", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-6-business-model-canvas", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-6-business-model-canvas", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Business Model Canvas Business-Model Hypothesis Map" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-overview-6", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-overview-6", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-overview-6", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Developed by Alexander Osterwalder and Yves Pigneur, the Business Model Canvas represents how an organization proposes to create, deliver, and capture value through nine building blocks. It makes assumptions visible; it is not a complete business plan, strategy, valuation, or validation result. [BB-C10-S03]" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-6", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-6", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Fill in the nine blocks, starting with the customer-facing elements on the right and moving to the cost-side elements on the left. 1. Customer Segments: Who are your most important customers? 2. Value Propositions: What \"job\" are you getting done for your customers? 3. Channels: How do you reach your customers? 4. Customer Relationships: What kind of relationship do you have with your customers? 5. Revenue Streams: How do you make money? --- 6. Key Activities: What are the most important things the company must do to make the model work? 7. Key Resources: What key assets are required? 8. Key Partnerships: Who are the key partners and suppliers? 9. Cost Structure: What are the most important costs inherent in the business model?" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-visual-representation", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Visual representation", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-visual-representation", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-visual-representation", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Source note: The nine-block structure is attributed to Osterwalder and Pigneur. The prompts below are a teaching adaptation; consult the source and determine permissions before reproducing the branded canvas externally. [BB-C10-S03] Table 10.4. Business-model hypothesis evidence system (constructed adaptation). The table is an author-created evidence-flow redraw of the nine blocks and does not reproduce the branded canvas layout. | Building block | Decision question | Illustrative evidence to gather | |---|---|---| | Customer segments | Who is served, and whose needs or economics differ materially? | Segment size, jobs, buying process, alternatives, willingness to pay | | Value propositions | What outcome is promised, for whom, and relative to what alternative? | Outcome measures, switching evidence, delivery cost, failure modes | | Channels | How will customers learn, evaluate, buy, receive, and obtain support? | Conversion, coverage, partner incentives, service capacity, channel conflict | | Customer relationships | What interaction is needed across acquisition, use, retention, and recovery? | Service expectations, support load, trust requirements, retention evidence | | Revenue streams | Who pays, for what unit, when, and under which pricing mechanism? | Price tests, usage, collections, refunds, concentration, revenue recognition | | Key resources | Which physical, intellectual, human, data, and financial assets are essential? | Availability, control, substitutability, constraints, permissions | | Key activities | Which activities must the organization perform distinctively or reliably? | Process capability, cost, quality, cycle time, dependencies | | Key partners | Which suppliers, alliances, or complementors are necessary, and why? | Incentives, concentration, switching, rights, continuity, governance | | Cost structure | Which fixed, variable, step, and shared costs determine viability? | Relevant range, unit economics, scale effects, cash timing, downside exposure | Figure 10.2 — Business-model hypothesis system. The nine blocks are shown as an evidence flow rather than a copied branded-canvas layout. Text equivalent: Define the customer and value hypothesis, then test how channels and relationships produce revenue. In parallel, test whether partners, resources, and activities can deliver the promise at a viable cost. Compare revenue and cost evidence; revise or stop when the system is not supported, and run only a bounded pilot when it is. Source note: Author-constructed evidence-flow adaptation of the nine Business Model Canvas building blocks; it does not reproduce the branded canvas layout. [BB-C10-S03] Application sequence: Start with customer segments and value propositions; map channels, relationships, and revenue; then test the resources, activities, partners, and cost structure required to deliver them. Every entry remains a hypothesis until evidence supports it." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-6", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-6", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the canvas to expose hypotheses about customers, value, channels, relationships, revenue, resources, activities, partners, and costs. - Attach evidence owners, definitions, assumptions, downside cases, and review dates to each material block rather than treating a completed canvas as validation. - Pair the canvas with customer, financial, competitive, legal, operational, privacy, and control evidence before funding a major commitment." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-6", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-6", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The canvas is a snapshot and does not establish customer demand, willingness to pay, relative advantage, legal feasibility, cash sufficiency, competitive response, or execution capacity. - The nine blocks can hide timing, dependencies, distributional effects, power, data rights, control requirements, and failure modes; keep a companion assumption ledger. - Adding boxes or completing the template does not validate the model; compare the hypotheses with customer, financial, competitive, legal, operational, privacy, and control evidence." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-connections-6", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-connections-6", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-connections-6", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The canvas is a synthesis of many other frameworks. Customer Segments come from RFM/JTBD (Chapter 5), Value Propositions from Blue Ocean Strategy (Chapter 3), and Key Resources from VRIO (Chapter 3). Output: Each box on the canvas represents a set of hypotheses that must be tested using the Assumption Mapping (Chapter 9) framework. The completed canvas is the core of a Business Plan (Framework 1) . ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-7-capability-development-ladder-constructed", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "7. Capability Development Ladder (Constructed)", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-7-capability-development-ladder-constructed", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-7-capability-development-ladder-constructed", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Capability Development Ladder Organizational Development" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-overview-7", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-overview-7", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-overview-7", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This five-stage Capability Development Ladder is a constructed planning aid for discussing one defined capability. It is not a certified assessment or a claim that every capability develops through the same sequence. Use the applicable domain standard when a formal assessment is required." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-7", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-7", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define the Capability: Choose a specific capability to assess (e.g., \"Data Analytics\"). 2. Describe observable states: For example: person-dependent, repeatable in limited settings, documented and governed, measured for a decision, and deliberately improved. Define evidence for each state rather than borrowing a generic label. 3. Choose the needed state: The target depends on failure consequence, regulation, scale, cost, strategic value, and change rate. The next useful state may not be the highest one. 4. Create and test a roadmap: Specify the capability owner, customer, control need, evidence, investment, expected benefit, stop rule, and review date. Do not assume the stages must be sequential." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-7", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-7", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define a capability in observable terms and choose the state needed for the decision, control obligation, scale, and failure consequence. - Fund evidence and operating improvement, not a maturity label; compare the expected benefit, dependency, cost, owner, and stop rule. - Reassess the capability when strategy, technology, regulation, customer need, or operating risk changes." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-7", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-7", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The ladder is author-created and should not be used as a certified maturity score, benchmark, or universal sequence. - Labels can hide within-team variation, political incentives, missing evidence, and capabilities that need to remain deliberately distinct. - A higher capability state does not prove better business performance; link the assessment to defined outcomes and contrary evidence." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-connections-7", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-connections-7", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-connections-7", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The capabilities to be assessed are often identified as weaknesses in a VRIO Analysis (Chapter 3) or as necessary for the future state in a Digital Maturity Assessment (Chapter 17) . Output: The roadmap to improve a capability informs your OKRs (Chapter 8) and your Talent Development plans. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-8-digital-transformation-framework", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "8. Digital Transformation Framework", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-8-digital-transformation-framework", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-8-digital-transformation-framework", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Digital Transformation Framework Enterprise Modernization" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-overview-8", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-overview-8", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-overview-8", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This five-domain Digital Transformation Framework is an author-created integration aid, not a canonical or complete digital-transformation framework. It broadens the discussion beyond technology to strategy and business model, customer experience, operations, technology and data, and people and culture; organizations must add the governance, security, legal, financial, workforce, accessibility, and domain requirements relevant to their context." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-8", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-8", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Structure your transformation program around these key pillars: 1. Strategy & Business Model: How will digital change how we create and capture value? (See Business Model Canvas, Framework 6 ). 2. Customer Experience: Which user outcomes, service-quality, accessibility, trust, and recovery measures should the digital journey improve? (See Customer Journey Mapping, Chapter 5 ). 3. Operations: Which defined process outcomes might digital technologies such as AI or automation improve, and what safety, quality, security, workforce, or control risks could they introduce? (See Chapter 6 ). 4. Technology & Data: What are the foundational platforms (e.g., cloud, data analytics) we need to build to enable the other pillars? 5. People & Culture: Which capabilities, incentives, participation practices, and ways of working support the chosen operating model? (See Chapter 7 ). Choose sponsorship, governance, workstreams, sequencing, and decision rights according to the transformation's scope, authority, risk, dependencies, and operating model; a dedicated C-level program is one option, not a universal success condition." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-8", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-8", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Start with the operating problem, affected users, decision rights, and value hypothesis before choosing technology or a transformation label. - Sequence strategy, customer, operations, data, technology, people, controls, and funding work around dependencies and evidence rather than a fixed roadmap. - Review adoption, service quality, security, privacy, workforce effects, accessibility, cost, and contrary evidence at explicit decision gates." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-8", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-8", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The five domains are a constructed prompt set; they do not establish readiness, causal priority, or a complete transformation program. - Technology can be a dependency or enabler without being the main constraint; people, process, governance, financing, or customer value may dominate. - A dashboard, sponsor, pilot, or “digital” label does not prove transformation progress or justify scaling." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-connections-8", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-connections-8", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-connections-8", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The impetus for a digital transformation often comes from a Strategic Analysis (Chapter 3) that reveals a changing competitive landscape. Output: The execution of a digital transformation can be monitored through OKRs (Chapter 8) and may require change-management work (Chapter 7), depending on the operating problem, affected groups, authority, and evidence. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-9-m-a-due-diligence-checklist", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "9. M&A Due Diligence Checklist", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-9-m-a-due-diligence-checklist", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-9-m-a-due-diligence-checklist", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "M&A Due Diligence Checklist Merger & Acquisition Analysis" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-overview-9", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-overview-9", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-overview-9", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This author-created M&A due diligence checklist organizes a governed investigation of a deal thesis, value drivers, liabilities, feasibility, and integration implications. It is not a professional diligence standard and cannot ensure completeness, authorize access, validate management representations, or prevent post-close loss. Transaction boundary (author-created governance prompt, not legal advice): Ask authorized counsel and accountable specialists to define the applicable confidentiality, privilege, antitrust/clean-team, privacy, cybersecurity, employee-contact, records, securities, and data-room protocols. They must define who may request, receive, test, retain, and rely on information, and the approved purpose and scope for interviews, observation, customer contact, competitor contact, and former-employee contact." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-9", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-9", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Organize diligence into key workstreams, each with a detailed checklist: 1. Financial Diligence: Validate historical financials, quality of earnings, working capital needs, and future projections. (Led by Finance/Accounting). 2. Legal Diligence: Review contracts, litigation, IP ownership, and corporate structure. (Led by Legal). 3. Commercial Diligence: Assess market position, customer concentration, churn rates, and competitive landscape. (Led by Strategy/Sales). 4. Operational Diligence: Review key processes, supply chain, and operational scalability. (Led by Operations). 5. Technology Diligence: Assess tech stack, scalability, security, and technical debt. (Led by IT/Engineering). 6. People and Operating-Model Diligence: Assess leadership dependencies, workforce obligations, critical capabilities, incentives, decision rights, retention scenarios, and ways of working with HR, employment counsel, and authorized leaders." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-9", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-9", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Tie each diligence request to a deal-thesis claim, decision consequence, evidence owner, access boundary, and possible action. - Integrate financial, commercial, operational, technology, cyber, people, legal, tax, and control evidence without hiding contradiction or uncertainty. - Preserve a documented option to renegotiate, delay, separate, or walk away when material assumptions remain unsupported." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-9", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-9", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Financial, legal, commercial, operational, technology, cyber, people, tax, and integration evidence can conflict; a completed checklist cannot prove that the deal works. - Access, privilege, confidentiality, privacy, antitrust, employment, securities, and records constraints limit what can be collected and who may rely on it. - Record the deal-thesis claim, source and access limits, contrary evidence, confidence, owner, and decision consequence; qualitative evidence matters only when collected lawfully and interpreted with comparable discipline." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-connections-9", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-connections-9", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-connections-9", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: A transaction thesis from Chapter 3, authorized scope, and specialist workplans. Output: Evidence and uncertainty for valuation scenarios in Chapter 4, deal terms, approval, integration options, and a documented walk-away decision. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-10-post-merger-integration-pmi-playbook", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "10. Post-Merger Integration (PMI) Playbook", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-10-post-merger-integration-pmi-playbook", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-10-post-merger-integration-pmi-playbook", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Post-Merger Integration (PMI) Playbook M&A Execution" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-overview-10", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-overview-10", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-overview-10", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This author-created post-merger integration playbook organizes continuity, controls, customers, people, systems, decision rights, and deal-thesis evidence after close. It is not a professional integration standard. “100 days” is a planning convention, not a universal integration duration, and full integration is only one option." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-10", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-10", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Structure the integration around decision gates and deal-specific workstreams: 1. Constructed control prompt: With authorized specialists, define legal close conditions, communications, decision authority, financial control, security, access, customer and employee continuity, and incident escalation. 2. Stabilization and evidence period: Protect continuity while testing the deal thesis and integration assumptions. Workstreams: Establish cross-functional teams for each key area (Sales, Product, Technology, HR, Finance). Synergy Capture: Create specific plans to realize the cost and revenue synergies identified during due diligence. People decisions: Apply lawful, evidence-based workforce and retention processes; do not infer “criticality” from executive preference alone. Ways of working: Decide what should converge, remain distinct, or be redesigned. 3. Staged integration, separation, or coexistence: Sequence changes by value, dependency, reversibility, control risk, customer impact, and capacity. Revisit the deal thesis as evidence changes." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-10", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-10", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Protect legal close, safety, financial control, security, access, records, payroll, customer continuity, and incident response before pursuing synergy. - Compare integration, selective integration, federation, temporary separation, and permanent separation against the deal thesis, dependencies, risk, capacity, and reversibility. - Track realized value and downside evidence with accountable owners, escalation routes, and review dates; do not convert projections into facts." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-10", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-10", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- “100 days” is a planning convention, not a universal duration, and early continuity work should not be confused with proof that integration is succeeding. - Full integration, selective integration, federation, temporary separation, and permanent separation each carry trade-offs in value, cost, dependency, control, customer impact, and accountability. - State the tradeoff and evidence rather than labeling one model “evidence-based”; projected synergies remain hypotheses until realized." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-connections-10", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-connections-10", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-connections-10", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Input: The M&A Due Diligence Checklist (Framework 9) provides the list of risks and opportunities that the PMI plan must address. Output: A governed integration or separation decision, with value and downside tracked against the Chapter 4 valuation case; projected synergies remain hypotheses until realized. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mental-model-1-frameworks-are-scaffolding-not-cages", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 1: Frameworks are Scaffolding, Not Cages", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-1-frameworks-are-scaffolding-not-cages", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mental-model-1-frameworks-are-scaffolding-not-cages", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Consulting frameworks are not meant to be rigid, prescriptive templates. They are mental scaffolding used to structure thinking, ensure completeness, and provide a common language. An inexperienced analyst follows the framework slavishly. An expert practitioner knows when to combine frameworks, when to simplify them, and when to break them entirely based on the specific context of the problem. Operator's Application: When a consultant shows you a perfectly filled-out Business Model Canvas or 7S framework, ask: \"What did you not include in this framework that matters?\" The best consultants admit what the framework misses. The dangerous ones pretend the framework is comprehensive. Example: The Business Model Canvas doesn't capture timing, competitive moats, or regulatory risk—all of which can kill a business." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mental-model-2-the-80-20-rule-in-action", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 2: The 80/20 Rule in Action", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-2-the-80-20-rule-in-action", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mental-model-2-the-80-20-rule-in-action", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "In complex analysis, evidence value is uneven, but no fixed small share reliably generates most insight. Prioritize by consequence, uncertainty, information value, legal minimums, dependency, and disconfirming evidence while preserving mandatory coverage. Operator's Application: In M&A diligence, meet the mandatory legal, financial, tax, cyber, operational, people, commercial, and transaction-control floor, then allocate incremental effort by deal thesis, consequence, uncertainty, contradiction, and information value. Do not assume one or two “usual” workstreams justify a light-touch review of other material risks." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mental-model-3-the-importance-of-a-single-source-of-truth", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 3: The Importance of a \"Single Source of Truth\"", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-3-the-importance-of-a-single-source-of-truth", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mental-model-3-the-importance-of-a-single-source-of-truth", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Complex projects can suffer from version ambiguity, conflicting assumptions, and unclear ownership. A shared information architecture—potentially including a decision record, RAID log, plan, or approved system of record—can reduce those risks, but it does not guarantee alignment or success. Operator's Application: Choose shared artifacts and systems from decision complexity, risk, regulation, privacy, security, retention, accessibility, and workflow—not a ten-person threshold. Define owners, version rules, permissions, update cadence, and links to specialized records; do not force all work into one tool or confuse a project hub with the authoritative legal, financial, clinical, security, or operational record." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mental-model-4-integration-beats-optimization-system-thinking", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 4: Integration Beats Optimization (System Thinking)", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-4-integration-beats-optimization-system-thinking", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mental-model-4-integration-beats-optimization-system-thinking", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Complex decisions may require several perspectives, but more frameworks do not guarantee better outcomes. Each added tool has cognitive, data, permissions, and coordination cost; frameworks can overlap or conflict. Operator's Application: Begin with the decision, evidence, authority, and failure modes; choose the smallest complementary set of tools that changes the decision. Record overlap, contradiction, omitted factors, and why each framework earns its place. No fixed five-to-seven framework stack applies to M&A, transformation, or product launch." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mental-model-5-culture-incentives-and-execution-interact", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 5: Culture, incentives, and execution interact", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-5-culture-incentives-and-execution-interact", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mental-model-5-culture-incentives-and-execution-interact", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Frameworks do not execute themselves. Observed norms, incentives, leadership behavior, capability, and formal controls can reinforce or contradict a stated strategy. Use the 7S relationships as diagnostic prompts; do not attribute the popular “culture eats strategy” phrase to Peter Drucker without a verified primary source. Operator's Application: Treat culture, incentives, power, workload, skills, and controls as hypotheses requiring proportionate and permission-aware evidence. Adapt the initiative, supporting system, sequencing, participation, or scope; pause or stop when risk or authority warrants it. No diagnostic by itself proves a culture is hostile or unchangeable." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mental-model-6-the-map-is-not-the-territory", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mental Model 6: The Map Is Not the Territory", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-6-the-map-is-not-the-territory", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mental-model-6-the-map-is-not-the-territory", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "All frameworks are simplifications of reality. The Business Model Canvas reduces a complex business to nine boxes. The 7S Framework reduces organizational dynamics to seven elements. These are useful simplifications, but they're not reality. Operators who confuse the map for the territory make catastrophic errors. Operator's Application: After completing any framework exercise, ask: “What important evidence, affected party, failure mode, authority, timing, or alternative did we lose by simplifying?” Document those off-framework factors and track them separately. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-selecting-a-framework-for-the-decision", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Selecting a Framework for the Decision", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-selecting-a-framework-for-the-decision", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-selecting-a-framework-for-the-decision", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Framework choice is provisional. Begin with the decision, authority, affected groups, evidence, timing, risk, and mechanism; then choose the smallest toolset that changes the analysis. | Candidate tool | Useful questions | Do not infer | | :--- | :--- | :--- | | 7S | Which strategy, structure, systems, style, staff, skills, and shared-value relationships might explain an execution issue? | That one element caused the outcome, that a small organization cannot use it, or that it establishes cultural fit | | Business Model Canvas | Which customer, value, channel, relationship, revenue, resource, activity, partner, and cost hypotheses need testing? | Demand, strategy, valuation, competitive response, or legal/financial feasibility | | RAPID | Which recommendation, agreement/input, execution, input, and decision roles remain unclear after actual authority is mapped? | That one individual can override collective, regulated, licensed, or contractual authority | | Value-chain or process analysis | Which activities create value, cost, delay, quality, control, or risk? | That a labeled activity is waste or should be removed | | Financial model | Which cash-flow, financing, accounting, timing, and terminal assumptions drive the decision? | That a model output is a forecast or that financial evidence alone resolves the decision | Use, combine, adapt, or reject a framework based on information value and fit. Record conflicts and off-framework evidence rather than routing by company size, speed, or a rigid “use/don't use” taxonomy. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-rapid-stabilization-after-close", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Rapid stabilization after close", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-rapid-stabilization-after-close", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-rapid-stabilization-after-close", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed operational prompt (not legal advice): Some transactions need immediate stabilization, but a generic seven-day schedule is unsafe. Before close, the authorized transaction team should identify the minimum actions required for legal close, safety, financial control, payroll, customer continuity, security, access, records, communications, and incident response. Retention offers, workforce representations, system access, data movement, customer contact, vendor changes, and public announcements should proceed only through the applicable legal, HR, finance, security, privacy, and communications approvals. During the first operating period: 1. Protect continuity and required controls before pursuing synergy. 2. Freeze only the changes whose risk is understood; a blanket moratorium can itself create harm. 3. Validate “quick wins” against contracts, customer consent, competition rules, security, capacity, and the deal thesis. 4. Assign an accountable integration or separation leader with explicit delegated authority and escalation routes. 5. Publish a decision calendar whose dates are assumptions, not universal milestones. Speed and control are not opposites. The objective is the fastest responsible stabilization supported by the transaction facts." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-political-navigation-when-frameworks-become-weapons", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Political Navigation: When Frameworks Become Weapons", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-political-navigation-when-frameworks-become-weapons", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-political-navigation-when-frameworks-become-weapons", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scenario 1: The \"We Already Tried That\" Objection Setup: You recommend using the 7S Framework to diagnose organizational dysfunction. A senior leader says, \"We already did a 7S analysis two years ago. It didn't help.\" What's Really Happening: The leader is signaling that they don't believe frameworks drive change. They may have had a bad experience with consultants who did academic exercises without driving action. How to Respond: \"You're right that frameworks alone don't drive change. What happened with the previous 7S? Was the issue that the diagnosis was wrong, or that the organization didn't act on it?\" This shifts from debating the framework to diagnosing why the previous effort failed. Often, the issue was lack of executive commitment, not the framework itself. Scenario 2: Framework Competition (7S vs. OKRs vs. Balanced Scorecard) Setup: Your CEO wants to implement the 7S Framework. Your COO is pushing OKRs. Your CFO loves the Balanced Scorecard. Everyone thinks their framework is \"the answer.\" What's Really Happening: Framework selection has become a proxy for power and priority. Each executive is advocating for the framework that elevates their function. How to Respond: Clarify the decision each sponsor is trying to improve, what evidence the framework would add, and where the tools overlap. Use, sequence, combine, or reject them from that analysis; 7S→OKR→Balanced Scorecard is not a fixed stack. Scenario 3: The Consultant Sold You a Framework You Don't Need Setup: A consulting firm delivered a polished Business Model Canvas and capability-ladder analysis. It looks comprehensive but does not answer the core market-entry decision. What's Really Happening: The consultants optimized for \"looking thorough\" rather than answering your question. They applied frameworks they're comfortable with rather than the frameworks you need. How to Respond: Require the team to restate the decision, alternatives, evidence, uncertainty, and recommendation. Add only the market, capability, financial, legal, or operating analysis needed to close material gaps; no fixed Five Forces/VRIO/DCF stack is mandatory." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-red-flags-when-to-fire-your-consultant", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Red Flags: When to Fire Your Consultant", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-red-flags-when-to-fire-your-consultant", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-red-flags-when-to-fire-your-consultant", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Red Flag 1: They Can't Explain the Framework in Plain English If a consultant cannot explain the Business Model Canvas or RAPID framework in plain language, ask what decision the tool supports, what evidence it adds, and what it leaves out. Jargon can obscure weak reasoning, but communication style alone does not establish competence or misconduct. Red Flag 2: Every Recommendation Fits Their Preferred Framework If every problem the consultant diagnoses is solved by the same framework (e.g., \"This is a 7S issue... this is also a 7S issue... and this one too\"), they're a hammer looking for nails. Good consultants adapt tools to problems, not problems to tools. Red Flag 3: No Contrarian Thinking If the consultant presents a Business Model Canvas or PMI Playbook without acknowledging what the framework misses or where it might be wrong, require a limitations and alternatives review. Demand contrarian perspectives without inferring intent from a polished deliverable alone. Red Flag 4: The Framework Is the Deliverable If the consulting engagement ends with \"Here's your completed 7S framework\" without a clear action plan, the deliverable may be framework theater rather than decision support. Frameworks are diagnostic tools, not solutions; require actions, owners, evidence, uncertainty, and review conditions based on the diagnosis." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-the-integration-map-combining-multiple-frameworks", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "The Integration Map: Combining Multiple Frameworks", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-the-integration-map-combining-multiple-frameworks", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-the-integration-map-combining-multiple-frameworks", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For complex initiatives (digital transformation, M&A, new business unit launch), one constructed sequencing example is below. The decision, evidence, authority, dependencies, and failure modes determine the actual toolset and timing; no initiative needs a fixed number of frameworks. Phase 1: Strategic Assessment (illustrative timing) 1. Porter's Five Forces (Chapter 3): Is the market attractive? 2. VRIO Framework (Chapter 3): Do we have a competitive advantage? 3. Competitive-Advantage Context Check (Framework 3): Which advantage hypotheses fit the defined market and evidence? Phase 2: Business Model Design (illustrative timing) 4. Business Model Canvas (Framework 6): What's the business model? 5. Unit Economics (Chapter 4): Is it profitable per customer? 6. Assumption Mapping (Chapter 9): What are our riskiest assumptions? Phase 3: Organizational Design (illustrative timing) 7. McKinsey 7S (Framework 2): Which organizational relationships and capability hypotheses require testing before execution? [BB-C10-S01] 8. RAPID (Framework 4): Who makes which decisions? 9. Capability Development Ladder (Framework 7): Which capabilities and evidence states do we need, and why? Phase 4: Execution & Measurement (illustrative timing) 10. OKRs (Chapter 8): What are our goals for the next review period? 11. Balanced Scorecard concepts (Chapter 8): Which complementary perspectives and measures matter for this decision? 12. Risk Assessment Matrix (Chapter 9): What could go wrong, and how do we mitigate it? This constructed example can expose contradictions and dependencies that a single framework misses, but adding frameworks also adds complexity and the risk of double-counting evidence. Remove any tool that does not change the decision or improve accountability. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-case-studies-integration-in-action", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Case Studies: Integration in Action", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-case-studies-integration-in-action", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-case-studies-integration-in-action", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following are composite teaching scenarios. They are fictional examples for applying the frameworks in this chapter, not accounts of real organizations or transactions." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-1-preserving-a-creative-unit-after-an-acquisition", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite Teaching Scenario 1: Preserving a Creative Unit After an Acquisition", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-1-preserving-a-creative-unit-after-an-acquisition", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-1-preserving-a-creative-unit-after-an-acquisition", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A global media organization acquires a smaller animation studio whose creative identity is central to the deal rationale. The integration team worries that standard corporate processes could weaken the studio's ability to develop original work. The PMI Playbook: The team chooses an \"autonomous but aligned\" model. It protects the studio's creative leadership, brand, working environment, and development practices while establishing clear interfaces for strategy, finance, and distribution. The Operating Choice: The combined organization shares selected capabilities without imposing a full process or cultural integration. Lesson: A PMI playbook can appropriately limit integration. When the acquisition thesis depends on distinct creative capabilities, protect the acquired unit's \"Skills,\" \"Staff,\" and \"Shared Values\" in the 7S model rather than pursuing every available cost synergy." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-2-reconciling-strategy-and-culture-in-a-media-merger", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite Teaching Scenario 2: Reconciling Strategy and Culture in a Media Merger", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-2-reconciling-strategy-and-culture-in-a-media-merger", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-2-reconciling-strategy-and-culture-in-a-media-merger", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A digital distribution company merges with an established content business. Each side assumes that the other will adopt its operating model, but neither leadership team defines a joint strategy or decision rights before close. The Error: The merger thesis relies on general expectations of synergy while leaving operating priorities, authority, and cultural differences unresolved. The 7S Misalignment: Strategy: The combined organization lacks a shared, actionable strategic direction. Culture: A fast-moving commercial culture conflicts with an editorial culture that emphasizes deliberation and autonomy. Leadership: Senior leaders lack clear decision rights for the integrated organization. Lesson: Financial modeling cannot substitute for a coherent operating model. Apply the 7S Framework and PMI Playbook before close to test strategic fit, culture, and leadership alignment." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-3-commercial-diligence-beyond-the-checklist", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite Teaching Scenario 3: Commercial Diligence Beyond the Checklist", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-3-commercial-diligence-beyond-the-checklist", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-3-commercial-diligence-beyond-the-checklist", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A software acquirer evaluates a target that reports unusually strong margins and rapid growth. The diligence team completes financial, legal, and technical workstreams, but has not independently tested the customer base, revenue pipeline, or the assumptions behind the target's performance. The Due Diligence Failure: The M&A Due Diligence Checklist (Framework 9) is treated as a completion exercise rather than a guide to investigation. The team relies on supplied materials instead of validating the commercial story with customers, market participants, and former employees where appropriate. Working causal hypothesis: The acquirer may lack sufficient time, authority, or ownership for qualitative commercial diligence and contrarian challenge; test this against incentives, access, expertise, deal timing, and contradictory evidence. Lesson for Operators: A due diligence checklist is a floor, not a ceiling. For a material acquisition, test the customer proposition, reconstruct the sales pipeline, and seek disconfirming evidence. Treat unusually favorable assumptions as hypotheses to investigate rather than facts to accept." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-4-protecting-safety-critical-activities-in-a-value-chain", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite Teaching Scenario 4: Protecting Safety-Critical Activities in a Value Chain", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-4-protecting-safety-critical-activities-in-a-value-chain", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-4-protecting-safety-critical-activities-in-a-value-chain", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "An industrial equipment manufacturer faces pressure to reduce costs and shorten delivery cycles. Leaders identify engineering, validation, and safety assurance activities as potential savings opportunities without first defining the consequences of weaker controls. The Value Chain Failure: The organization treats safety-critical work as a generic cost center. It reduces independent review, limits validation capacity, and accelerates release decisions without clear accountability for the resulting risk. The Operating Risk: The value chain no longer distinguishes waste from activities that protect customers, employees, product reliability, and the organization's ability to operate. Lesson for Operators: Value chain optimization is not about cutting every cost. Before reducing investment in a critical activity, define the failure modes, accountable owner, and minimum control standard. Do not optimize activities whose failure consequences exceed the expected savings." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-5-aligning-a-digital-platform-transformation", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite Teaching Scenario 5: Aligning a Digital Platform Transformation", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-5-aligning-a-digital-platform-transformation", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-5-aligning-a-digital-platform-transformation", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A diversified industrial company launches a proprietary digital platform intended to support several business units. It recruits software talent and funds platform development, but the program is not tied to a clear operating need, an adoption model, or a deliberate build-versus-partner decision. The Digital Transformation Framework Failure: The initiative emphasizes technology creation while leaving strategic fit, governance, and cultural readiness unresolved. Business units continue to prioritize operational improvements over platform adoption, and the software team works in ways that conflict with the existing planning and decision processes. The Operating Response: Leaders reassess which customer and business problems require proprietary capabilities, which can use external platforms, and which organizational changes are necessary to execute the chosen approach. Lesson for Operators: Digital transformation is not about technology alone. Before committing to a platform, use the 7S Framework (Framework 2) to assess whether strategy, structure, systems, style, staff, skills, and shared values can support the operating model. Transformation may require changing several elements together, not merely adding technology. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-advanced-framework-applications-deep-dives", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Advanced Framework Applications: Deep Dives", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-advanced-framework-applications-deep-dives", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-advanced-framework-applications-deep-dives", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed-case boundary: All organizations, transactions, people, amounts, dates, percentages, actions, and results in the three deep dives are fictional teaching assumptions, not benchmarks or accounts of real companies. Readers must replace them with verified facts, authority, legal constraints, and local evidence." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-1-applying-the-mckinsey-7s-framework-to-a-failing-digital-transformation", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Deep Dive 1: Applying the McKinsey 7S Framework to a Failing Digital Transformation", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-1-applying-the-mckinsey-7s-framework-to-a-failing-digital-transformation", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-1-applying-the-mckinsey-7s-framework-to-a-failing-digital-transformation", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Scenario: A traditional manufacturing company ($2B revenue, 50 years old) is attempting a digital transformation. The CEO hired a new CTO, invested $50M in cloud infrastructure, and launched an \"AI initiative.\" Two years later, no AI model is in production, and many employees still use spreadsheets for some work. The board wants to know why. Step 1: Map the Current State Across All 7 S's 1. Strategy: - Stated Strategy: \"Become a digital-first, data-driven organization.\" - Reality: No clear definition of what \"digital-first\" means. No connection between digital transformation and business outcomes (revenue, margin, customer experience). - Gap: Strategy is aspirational, not operational. 2. Structure: - Stated Structure: Matrix organization with functional leaders (Manufacturing, Sales, Finance) and a new \"Digital\" function led by the CTO. - Reality: The CTO reports to the COO, who is a 30-year veteran focused on operational efficiency, not innovation. Digital initiatives require sign-off from functional leaders who view them as \"IT projects,\" not strategic priorities. - Gap: Digital function has no authority to drive change. 3. Systems: - Stated Systems: Implementing a new ERP system and cloud data warehouse. - Reality: The ERP implementation is 18 months behind schedule. No one knows how to use the cloud data warehouse. The company still runs on a 20-year-old legacy system. - Gap: New systems exist but aren't integrated into workflows. 4. Shared Values: - Stated Values: \"Innovation, Agility, Customer-Centricity.\" - Reality: Available interview and survey evidence suggests that some teams reward process conformity, short-term earnings, and risk avoidance; the causes and distribution of those norms require testing. - Gap: Stated values contradict actual culture. 5. Style (Leadership): - CEO's Style: Visionary but hands-off. Announces big initiatives in all-hands meetings but doesn't hold leaders accountable for execution. - Functional Leaders' Style: Command-and-control. Micromanage their teams. View digital transformation as a threat to their power. - Gap: Leadership says \"transform\" but acts \"status quo.\" 6. Staff: - Current Staff: Many employees have long tenure; the digital team is 10 people out of 5,000 total employees. Workforce evidence should distinguish skills, workload, incentives, access, and change concerns rather than using age as a proxy. - Gap: The organization may have a material digital-capability and change-support gap to investigate. 7. Skills: - Current Skills: Strong manufacturing operations, supply chain experience, and deep industry expertise. - Missing Skills: Data science, cloud architecture, agile product development, design thinking. - Gap: A material gap in digital capabilities is a working hypothesis, not a complete diagnosis. Step 2: Diagnose the Misalignments The 7S mapping suggests several hypotheses to investigate: 1. Strategy ↔ Structure Misalignment: The digital strategy requires cross-functional authority, but the structure gives the CTO no power. 2. Strategy ↔ Shared Values Misalignment: The strategy requires innovation and risk-taking, but the culture punishes failure. 3. Style ↔ Staff ↔ Skills Misalignment: The leadership style may discourage challenge, some staff report change concerns, and capabilities may not match the intended operating model. Step 3: Develop a Sequenced Change Plan The 7S mapping suggests that changing one \"S\" may not address the operating problem. The team should test a sequenced plan whose scope, authority, and safeguards fit the evidence: Phase 1 (Months 1-6): Fix Structure and Style - Action 1 (constructed option): Evaluate whether the CTO should have a direct sponsor relationship with the CEO, subject to the organization's governance, accountability, and operating-model design. - Action 2 (constructed option): Consider an \"Innovation Council\" with the CEO, CTO, and three functional leaders; define its delegated budget authority, conflicts, escalation, and review conditions before granting it. - Action 3 (constructed option): The accountable sponsor reviews one failed experiment, including evidence, safeguards, losses, learning, and the resulting decision. Public celebration is not required and may be inappropriate where harm, confidentiality, compliance, or performance obligations apply. Phase 2 (Months 7-12): Build Staff and Skills - Action 4 (constructed option): Hire or develop a defined number of data, cloud, product, and change capabilities based on the evidence gap and an approved, fair workforce plan; embed capabilities where the operating model needs them. - Action 5 (constructed option): Offer role-relevant digital training and assess capability fairly, subject to HR, employment, accessibility, and collective obligations; do not treat course completion as proof of transformation. - Action 6: Create a \"reverse mentoring\" program where junior digital employees mentor senior executives on technology. Phase 3 (Months 13-24): Align Systems and Reinforce Shared Values - Action 7 (constructed option): Pause, re-scope, replace, or continue the ERP program only after comparing control, migration, security, cost, capacity, dependency, and implementation-risk evidence; a six-month replacement is not assumed. - Action 8: Launch 3-5 \"lighthouse\" projects that demonstrate quick digital wins (e.g., AI-powered demand forecasting, predictive maintenance, digital customer portal). - Action 9: Update the company's values statement to explicitly include \"Intelligent Risk-Taking\" and \"Continuous Learning.\" Tie executive bonuses to digital transformation milestones, not just quarterly earnings. Decision implication: The team should not promise a 24-month transformation from a 7S map. It should test whether changes to authority, incentives, capability, systems, and ways of working address the defined operating outcomes, while monitoring cost, harm, adoption, and contrary evidence." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-2-using-the-business-model-canvas-to-pivot-a-failing-startup", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Deep Dive 2: Using the Business Model Canvas to Pivot a Failing Startup", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-2-using-the-business-model-canvas-to-pivot-a-failing-startup", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-2-using-the-business-model-canvas-to-pivot-a-failing-startup", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Scenario: A B2B SaaS startup raised $5M in seed funding 18 months ago. The product is a \"workflow automation platform for HR teams.\" After 18 months, they have 20 customers paying an average of $500/month. Burn rate is $300K/month. Runway is 4 months. The founders need to figure out if they should pivot or shut down. Step 1: Fill Out the Current Business Model Canvas Table 10.5. Constructed startup business-model baseline. All values are fictional teaching assumptions, not benchmarks or forecasts. | Box | Current State | |-----|---------------| | Customer Segments | HR managers at mid-sized companies (100-500 employees) | | Value Proposition | \"Automate repetitive HR tasks\" (onboarding, offboarding, compliance) | | Channels | Outbound sales, cold email, LinkedIn ads | | Customer Relationships | High-touch onboarding, dedicated CSM for every customer | | Revenue Streams | $500/month SaaS subscription | | Key Activities | Product development, sales outreach, customer success | | Key Resources | 12-person engineering team, 3-person sales team, 2-person CS team | | Key Partnerships | None (built everything in-house) | | Cost Structure | $200K/month in salaries, $50K/month in AWS, $50K/month in sales/marketing | Step 2: Diagnose the Problem Using the Canvas The canvas reveals three critical flaws: 1. Revenue vs. Cost Mismatch: Generating $10K/month in revenue ($500 × 20 customers) while reporting $300K/month of burn. If that burn is treated as total monthly operating cost and relevant service/variable costs are ignored, 600 customers at the same price would be a simple break-even arithmetic threshold. Adding 580 customers at 1–2 per month would take approximately 24–48 years; cash burn and contribution margin require a separate model. 2. Customer Relationships vs. Revenue Mismatch: Providing white-glove service (dedicated CSM) to customers paying $500/month. The cost to serve each customer ($1,000-1,500/month) exceeds the revenue. 3. Channels vs. Customer Segments Mismatch: In this constructed case, outbound acquisition costs $15,000 per customer while the assumed LTV is $6,000 (12 months × $500). The resulting 0.4:1 ratio fails the case's own requirement that lifetime value exceed acquisition cost; no universal LTV:CAC cutoff is implied. Step 3: Run Customer Discovery to Identify a Pivot The founders interview their 20 existing customers and discover something surprising: - 15 of 20 customers are using the product for a specific use case: automating background checks during hiring . - These 15 customers state a higher willingness to pay for a narrower background-check workflow; stated intent still requires behavioral and commercial testing. - The other 5 customers are barely using the product and will likely churn. This is a candidate pivot signal: a narrower use case may have stronger demand, but stated willingness to pay still requires behavioral, commercial, privacy, and compliance testing. Step 4: Fill Out a New Business Model Canvas for the Pivot Table 10.6. Constructed startup pivot hypothesis. All values are fictional teaching assumptions and require commercial, privacy, compliance, and cash evidence. | Box | Pivoted State | |-----|---------------| | Customer Segments | HR managers + Recruiting teams at companies with high-volume hiring (tech, retail, healthcare) | | Value Proposition | \"The fastest, most accurate background check platform for high-volume hiring\" | | Channels | Product-led growth (free trial), inbound marketing (SEO for \"background check software\"), partnerships with ATS platforms (Greenhouse, Lever) | | Customer Relationships | Self-service onboarding, automated CS for <$2K/month customers, dedicated CSM for $5K+/month customers | | Revenue Streams | $2,500/month base plan + usage-based pricing ($10 per background check) | | Key Activities | Build deeper integrations with ATS platforms, improve background check accuracy/speed, SEO content marketing | | Key Resources | 8-person engineering team (laid off 4 people), 1-person growth marketer, 1-person CS lead | | Key Partnerships | Integrations with Greenhouse, Lever, Workday. Data partnerships with background check providers. | | Cost Structure | $120K/month in salaries (downsized team), $30K/month in AWS, $20K/month in marketing. Total burn: $170K/month. | Step 5: Validate the Pivot with a 3-Month Test The founders don't fully commit to the pivot. Instead, they run a 3-month experiment: - Month 1: Build a standalone \"background check\" product using existing code. Launch it as a separate brand. - Month 2: Run a $10K paid marketing campaign targeting HR managers searching for \"background check software.\" Track CAC and conversion rate. - Month 3: Offer existing customers the option to switch to the new product at $2,500/month. Results: - 12 of 15 target customers switched to the new product at $2,500/month = $30K MRR (up from $10K). - Paid marketing campaign generated 50 free trial signups. 10 converted to paying customers at $2,500/month = $25K MRR. - Total MRR after 3 months: $55K. New burn rate: $170K/month. Recompute cash runway from cash on hand, collections, fixed and variable costs, obligations, and financing; revenue growth alone does not establish viability. Decision rule: The results support continuing the pivot test and updating the financial, customer, privacy, compliance, and operating hypotheses. They do not by themselves establish a durable business model or justify shutting down the old product or raising a bridge round; those actions require an approved runway and evidence decision. Lesson: The Business Model Canvas is a diagnostic tool. It makes revenue, cost-to-serve, channel, customer, and partner hypotheses visible; it does not prove that a configuration is aligned or sustainable. A pivot is a staged evidence decision, not a guess or a guarantee." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-3-executing-a-post-merger-integration-with-the-pmi-playbook", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Deep Dive 3: Executing a Post-Merger Integration with the PMI Playbook", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-3-executing-a-post-merger-integration-with-the-pmi-playbook", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-3-executing-a-post-merger-integration-with-the-pmi-playbook", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Scenario: A $500M public software company acquires a $50M startup for $200M (4x revenue multiple). The acquisition rationale is clear: the startup has a product that fills a gap in the acquirer's portfolio and a customer base that doesn't overlap (zero channel conflict). The deal closes. You're appointed Integration Lead. You have 100 days to execute the PMI. Step 1: Day 1 Planning (Pre-Close) Constructed case checklist (not legal advice): Before the deal closes, authorized specialists should define the Day 1 playbook: Critical Day 1 Actions: 1. Approved communication: Issue accurate employee, customer, regulator, market, and partner communications under the transaction communication plan. 2. People continuity: Implement counsel- and HR-approved retention, consultation, payroll, benefits, and workforce actions without treating a generic “top 20” as the rule. 3. Controlled access: Provision or restrict systems only through identity, least-privilege, clean-team, privacy, security, and records protocols. 4. Asset and data control: Validate ownership and authority before moving, copying, deleting, or restricting code, IP, customer data, financial data, or contractor access. 5. Governance kickoff: Confirm workstream owners, delegated authority, required approvals, escalation, dependencies, and the integration or separation decision calendar. Step 2: First 30 Days (Stabilization) Objective: Prevent talent flight, secure assets, and build the integration roadmap. Workstream 1: Talent Retention (Led by HR) - Action 1: Use an approved workforce-listening and consultation process that protects confidentiality, avoids retaliation, and complies with applicable employment and collective obligations. - Action 2: Assess role and capability dependencies using defined evidence; review retention actions for fairness, discrimination risk, cost, and unintended incentives. - Action 3: Communicate only supportable role and career information, including what remains undecided. - Metric: Target attrition below 5 percent in first 30 days. Compare against a realistic deal-specific attrition range. Workstream 2: Customer Retention (Led by Sales + CS) - Action 1: Contact customers under the applicable contract, consent, competition, disclosure, and account-governance requirements. Do not promise that nothing changes or that service will improve without evidence. - Action 2: Identify and fix any customer-facing integration issues (e.g., billing confusion, support ticket routing). - Action 3: Create a cross-sell plan: which target customers should we introduce to acquirer products (and vice versa)? - Metric: Target customer churn below 2 percent in first 90 days. Workstream 3: Product Integration (Led by Engineering) - Action 1: Compare immediate, staged, selective, and deferred technical integration using architecture, security, control, customer, dependency, and reversibility evidence. - Action 2: Identify the top 3 integration opportunities (e.g., shared authentication, unified billing, data sync between products). - Action 3: Build a 12-month product roadmap that shows how the two products will come together. - Metric: Zero production outages related to integration. Workstream 4: Finance & Legal (Led by CFO) - Action 1: Execute the approved accounting, consolidation, control, tax, treasury, and reporting plan with qualified specialists. - Action 2: Align fiscal calendars and reporting cadences. - Action 3: Renegotiate vendor contracts (e.g., consolidate AWS accounts, SaaS tools). - Metric: Achieve $2M in cost synergies in first 90 days (from vendor consolidation). Step 3: Days 31-100 (Optimization) Objective: Realize synergies, integrate systems, and align culture. Days 31–100 Actions: 1. Synergy Capture: Execute on the cost and revenue synergies identified during due diligence. Track progress weekly in IMO meetings. 2. Culture Integration: Run joint team offsites, cross-company hackathons, and \"culture ambassadors\" program to blend cultures. 3. System Integration: Begin deeper technical integration (e.g., unified login, shared data warehouse, integrated admin panel). 4. Leadership Alignment: Merge the two leadership teams. Clarify reporting structures. Use RAPID (Framework 4) to define decision rights for key decisions. Step 4: Day 100 Review Conduct a formal review with the board and executive team: - Talent Retention: Did we retain the people in defined critical roles or dependencies, under the approved role and evidence definition? - Customer Retention: Did we keep more than 98 percent of revenue, or what deal-specific customer-continuity range was approved? - Synergy Realization: Do realized and committed savings and revenue progress match the approved deal-specific baseline, ranges, attribution rules, and controls? - Integration Milestones: Are we on track for full technical integration in 12 months? Review implication: No single threshold determines whether the PMI is on track. Reconcile the four evidence streams, explain contrary evidence, and adjust, pause, separate, or stop the plan when the approved decision rules require it. Lesson: Sequence work around the deal thesis, continuity, dependency, control risk, reversibility, and evidence. The dates and actions above are illustrative. Immediate technical integration, delayed integration, selective integration, or separation can each be appropriate depending on the transaction. ---" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mistake-1-using-the-7s-framework-as-a-checklist-not-a-diagnostic", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mistake 1: Using the 7S Framework as a Checklist, Not a Diagnostic", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mistake-1-using-the-7s-framework-as-a-checklist-not-a-diagnostic", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mistake-1-using-the-7s-framework-as-a-checklist-not-a-diagnostic", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Error: Teams fill out a template for all seven S's (\"Our strategy is X, our structure is Y...\"), put it in a slide deck, and call it done. They don't actually analyze the relationships between the S's or identify misalignments. How to Avoid: The power of the 7S framework is in the connections , not the individual elements. After mapping each S, create a \"Misalignment Matrix\": - For each pair of S's (e.g., Strategy ↔ Structure), ask: \"Are these aligned or misaligned?\" - If misaligned, ask: \"Which one should we change to bring them into alignment?\" - Document these misalignments and make them the focus of your change plan. The 7S framework is a diagnostic tool, not a documentation exercise." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mistake-2-treating-the-business-model-canvas-as-static", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mistake 2: Treating the Business Model Canvas as Static", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mistake-2-treating-the-business-model-canvas-as-static", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mistake-2-treating-the-business-model-canvas-as-static", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Error: Teams fill out the Business Model Canvas once, hang it on the wall, and never update it. Six months later, the business has evolved but the canvas is still showing the original vision. How to Avoid: The Business Model Canvas should be a living document . Review it at a cadence matched to decision frequency, market change, evidence latency, and material assumption changes: - After each quarter: Review the canvas and ask, \"What changed?\" Consider whether segments shifted, costs increased, or a key partnership ended. - For each box that changed: Ask whether strategy needs adjustment, then test price, value-proposition, and segment changes against evidence. - Version control: Keep historical versions of the canvas. It's incredibly valuable to see how your business model evolved over time. The canvas is a tool for continuous business model design, not a one-time planning exercise." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mistake-3-applying-rapid-to-decisions-that-don-t-matter", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mistake 3: Applying RAPID to Decisions That Don't Matter", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mistake-3-applying-rapid-to-decisions-that-don-t-matter", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mistake-3-applying-rapid-to-decisions-that-don-t-matter", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Error: Teams use RAPID for every single decision, even trivial ones (\"Who decides what brand of coffee we buy for the office?\"). This creates bureaucracy and slows down the organization. How to avoid: Assess consequence, reversibility, affected rights, authority, uncertainty, coordination, and cost of delay. Use role clarification only when ambiguity materially impairs the decision. An apparently reversible pricing, hiring, data, or product decision can still carry legal, safety, employment, customer, or path-dependence costs. Avoid unnecessary bureaucracy, but do not reserve RAPID to a branded binary class of decisions or assume low-value decisions can always be delegated without governance constraints." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mistake-4-skipping-talent-culture-due-diligence-in-m-a", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mistake 4: Skipping Talent & Culture Due Diligence in M&A", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mistake-4-skipping-talent-culture-due-diligence-in-m-a", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mistake-4-skipping-talent-culture-due-diligence-in-m-a", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The risk: A diligence scope can omit leadership dependencies, workforce obligations, critical capabilities, incentives, and operating norms. Those gaps can affect continuity and integration, but they do not prove why employees leave or why a transaction fails. Governed response (author-created prompt, not legal advice): Define workforce and operating hypotheses with counsel, HR, privacy, security, antitrust/clean-team, and transaction owners. Use only the evidence package they approve—such as aggregated records, approved questionnaires, representative interviews, observation, or third-party analysis—with explicit purpose, access, privilege, retention, consent/notice, and non-retaliation controls. Do not prescribe employee counts, shadowing, former-employee contact, or public-review mining without approval. Talent and culture diligence is not \"soft\". Treat it as a core workstream because it can materially affect retention, operating continuity, and integration decisions." }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration::chapter-10-advanced-consulting-frameworks-and-integration-mistake-5-building-a-digital-transformation-framework-without-leadership-buy-in", "kind": "chapter", "itemSlug": "chapter-10-advanced-consulting-frameworks-and-integration", "itemTitle": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "heading": "Mistake 5: Building a Digital Transformation Framework Without Leadership Buy-In", "headingId": "chapter-10-advanced-consulting-frameworks-and-integration-mistake-5-building-a-digital-transformation-framework-without-leadership-buy-in", "url": "#chapter-10-advanced-consulting-frameworks-and-integration-mistake-5-building-a-digital-transformation-framework-without-leadership-buy-in", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Error: The CTO or CDO builds a beautiful digital transformation roadmap with clear phases, KPIs, and investments. But the CEO and CFO aren't committed. When the transformation hits resistance or requires budget overruns, it gets defunded. Governed response: Before committing to a roadmap, test whether the accountable sponsor or governing group can articulate the decision and intended value, authorize proportionate resources, resolve cross-functional conflicts, and review evidence. Record commitments at the level required by governance and funding; neither a multi-year investment nor a CEO-only mandate is universally required. Sponsors should model the decision and learning behaviors relevant to the work. Use of Slack, email, slides, or dashboards does not prove transformation capability. Weak sponsorship, authority, capacity, or follow-through increases delivery risk; it does not make failure certain or justify labeling the work “IT theater.” ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Project Management and PMP Frameworks", "headingId": "chapter-11-project-management-and-pmp-frameworks", "url": "#chapter-11-project-management-and-pmp-frameworks", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-executive-summary", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Executive Summary", "headingId": "chapter-11-project-management-and-pmp-frameworks-executive-summary", "url": "#chapter-11-project-management-and-pmp-frameworks-executive-summary", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter distinguishes predictive process-group practice, current PMI tailoring principles, Scrum, and constructed delivery aids. It teaches managers to select controls and feedback mechanisms for the work rather than treating an exam outline, lifecycle, or branded method as universal law. [BB-C11-S01] [BB-C11-S05] [BB-C11-S06] Key Frameworks: 1. Predictive Process Groups (historical PMBOK 6) 2. Work Breakdown Structure (WBS) 3. Critical Path Method (CPM) & Gantt Charts 4. Earned Value Management (EVM) 5. Risk Management Framework 6. Stakeholder Management (PMBOK context; constructed categories) 7. Agile/Scrum Framework 8. Flow Board and WIP Policy (constructed aid; not a full Kanban-method treatment) 9. Change Control Process 10. Project Charter Template" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-manager-decision-outcomes-and-boundary", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Manager Decision Outcomes and Boundary", "headingId": "chapter-11-project-management-and-pmp-frameworks-manager-decision-outcomes-and-boundary", "url": "#chapter-11-project-management-and-pmp-frameworks-manager-decision-outcomes-and-boundary", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "After this chapter, a manager should be able to: 1. Distinguish a project lifecycle from recurring process groups and tailor governance to the work. 2. Build an auditable scope, schedule, cost, risk, stakeholder, and decision baseline. 3. Calculate and interpret critical-path and earned-value measures without confusing schedule and cost indices. 4. Separate official Scrum accountabilities, events, and artifacts from optional team tactics. 5. Combine predictive and adaptive practices while preserving safety, regulatory evidence, contracts, funding, and change authority. The chapter is educational. It does not define PMP exam requirements, reproduce PMI standards, certify Scrum or Kanban implementation, or establish approval authority. Contracts, procurement, safety, employment, privacy, cybersecurity, regulated evidence, and board or public-sector approvals require the applicable specialists and governing instruments. Applied exercise — regulated digital project: For a constructed project, choose a tailored predictive/adaptive design; create a charter, WBS, dependency network, cost baseline, and risk/authority map; calculate the critical path, SPI, and CPI from supplied data; identify two correlated risks; and defend the change authority, evidence cadence, and stop conditions. Use Chapter 6 for process constraints, Chapter 8 for objectives and measures, and Chapter 12 for client governance. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-overview", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-11-project-management-and-pmp-frameworks-overview", "url": "#chapter-11-project-management-and-pmp-frameworks-overview", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This author-created historical teaching summary uses the predictive process-group structure commonly associated with older PMBOK materials; it is not a reproduction of a PMI standard or a claim about the current edition. The PMBOK Guide Seventh Edition uses principles and performance domains and emphasizes tailoring; readers should identify the edition and artifact they are applying. [BB-C11-S01]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-the-five-historical-process-groups", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "The five historical process groups", "headingId": "chapter-11-project-management-and-pmp-frameworks-the-five-historical-process-groups", "url": "#chapter-11-project-management-and-pmp-frameworks-the-five-historical-process-groups", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 11.1. Recurring predictive process groups, not lifecycle phases. Author-created teaching summary of a historical five-group structure; monitoring and controlling interacts with planning and execution throughout the work, and closing can occur for a phase, contract, or project. Current-edition tailoring is discussed in the surrounding text. Text equivalent: Initiating authorizes defined work. Planning develops the approach and baselines. Executing produces the work. Monitoring and controlling compares evidence with plans and authorizes responses across planning and execution. Closing completes or transitions a phase, contract, or project. The groups may repeat. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-process-group-1-initiating", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Process Group 1: INITIATING", "headingId": "chapter-11-project-management-and-pmp-frameworks-process-group-1-initiating", "url": "#chapter-11-project-management-and-pmp-frameworks-process-group-1-initiating", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Authorize project and define high-level scope Key Activities: 1. Develop Project Charter 2. Identify Stakeholders 3. Conduct Feasibility Analysis 4. Assign Project Manager 5. Secure Executive Sponsorship These are common management activities used to illustrate the group, not an exhaustive or edition-neutral process inventory. Tailor the artifact, authority, and evidence to the governing standard and project context. [BB-C11-S01] Outputs: - Project Charter (see Framework #10 below) - Stakeholder Register - High-level Requirements Related analysis: - Client and stakeholder governance (Chapter 12) - Issue trees and problem structuring (Chapter 9) - Financial analysis and valuation (Chapter 4) ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-process-group-2-planning", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Process Group 2: PLANNING", "headingId": "chapter-11-project-management-and-pmp-frameworks-process-group-2-planning", "url": "#chapter-11-project-management-and-pmp-frameworks-process-group-2-planning", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Establish scope, objectives, and procedures Key Activities & Tools: | Activity | Tool/Framework | Output | |----------|---------------|--------| | Scope Management | WBS (Framework #2) | Work Breakdown Structure | | Schedule Management | CPM, Gantt (Framework #3) | Project Schedule | | Cost Management | Cost Baseline, Reserves | Budget with contingencies | | Quality Management | Quality Plan | Quality metrics and standards | | Resource Management | RACI and authority map (Chapter 12) | Responsibility and approval assignments | | Risk Management | Risk Register (Framework #5) | Risk response plans | | Communications | Comms Plan | Stakeholder communication matrix | | Procurement | Make-or-Buy Analysis | Procurement strategy | Outputs: - Project Management Plan (integrates all sub-plans) - Scope Statement (detailed requirements) - Schedule Baseline (approved timeline) - Cost Baseline (approved budget) Planning posture: Tailor planning depth, cadence, and evidence to novelty, failure consequence, dependencies, regulation, contract, funding, and reversibility. Predictive and adaptive work both require planning; they differ in when detail is committed and how change is absorbed. [BB-C11-S01] [BB-C11-S06] ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-process-group-3-executing", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Process Group 3: EXECUTING", "headingId": "chapter-11-project-management-and-pmp-frameworks-process-group-3-executing", "url": "#chapter-11-project-management-and-pmp-frameworks-process-group-3-executing", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Complete work defined in project management plan Key Activities: 1. Direct and manage project work 2. Acquire, develop, and manage team 3. Implement risk responses 4. Conduct procurements 5. Manage stakeholder engagement 6. Manage quality Leadership connections: Use Chapter 7 for team, leadership, conflict, and psychological-safety questions. Outputs: - Deliverables (actual work products) - Work Performance Data (raw observations) - Change Requests (when scope adjustments needed) - Team Performance Assessments ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-process-group-4-monitoring-controlling", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Process Group 4: MONITORING & CONTROLLING", "headingId": "chapter-11-project-management-and-pmp-frameworks-process-group-4-monitoring-controlling", "url": "#chapter-11-project-management-and-pmp-frameworks-process-group-4-monitoring-controlling", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Track, review, and regulate progress; identify variances Key Metrics: Schedule Performance: Cost Performance: See Framework #4 (Earned Value Management) for full details Control Activities: - Validate Scope (deliverable acceptance) - Control Schedule (update Gantt, adjust resources) - Control Costs (track actuals vs. budget) - Monitor Risks (risk register updates) - Control Quality (inspections, audits) - Manage Changes (Change Control Board) ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-process-group-5-closing", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Process Group 5: CLOSING", "headingId": "chapter-11-project-management-and-pmp-frameworks-process-group-5-closing", "url": "#chapter-11-project-management-and-pmp-frameworks-process-group-5-closing", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Formalize project completion and lessons learned Key Activities: 1. Obtain final acceptance of deliverables 2. Transfer deliverables to operations 3. Release resources 4. Document lessons learned 5. Archive project documents 6. Acknowledge learning and contributions where appropriate. Outputs: - Final Project Closeout Summary - Lessons Learned Repository - Updated Organizational Process Assets - Contract Closure (if external vendors) Post-Implementation Review: - What went well? - What didn't go well? - What would we do differently? - What best practices to institutionalize?" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers", "url": "#chapter-11-project-management-and-pmp-frameworks-so-what-for-managers", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Treat process groups as recurring management work, not a mandatory five-phase lifecycle. - Tailor plans, evidence, controls, and decision cadence to the project's novelty, consequence, dependencies, contract, regulation, and reversibility. - Use monitoring and controlling to update plans, risks, baselines, stakeholders, and decisions rather than merely report status. [BB-C11-S01]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques", "url": "#chapter-11-project-management-and-pmp-frameworks-limits-and-critiques", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Historical process groups do not establish a complete lifecycle, delivery method, or current PMI practice by themselves. - A process checklist cannot prove scope quality, stakeholder consent, benefit realization, safety, compliance, or delivery feasibility. - Predictive, adaptive, and hybrid practices can all require planning, documentation, controls, and change authority; the choice is contextual." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-connections", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-11-project-management-and-pmp-frameworks-connections", "url": "#chapter-11-project-management-and-pmp-frameworks-connections", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Scope and operations: Use Chapter 6 for process/capacity constraints and Chapter 8 for objectives and measures. - Stakeholders and clients: Use Chapter 7 for team/leadership questions and Chapter 12 for client governance and decision communication. - Problem and initiative integration: Use Chapter 9 for problem structuring and Chapter 10 for integrated initiatives; these are inputs, not automatic method selections. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-overview-2", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-11-project-management-and-pmp-frameworks-overview-2", "url": "#chapter-11-project-management-and-pmp-frameworks-overview-2", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Work Breakdown Structure (WBS) is a hierarchical, deliverable-oriented decomposition of the defined project scope into components and work packages. [BB-C11-S02]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-wbs-structure", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "WBS Structure", "headingId": "chapter-11-project-management-and-pmp-frameworks-wbs-structure", "url": "#chapter-11-project-management-and-pmp-frameworks-wbs-structure", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "| Level | WBS code | Illustrative element | Parent | |---:|---|---|---| | 1 | 1.0 | Project | — | | 2 | 1.1 | Deliverable 1 | 1.0 | | 3 | 1.1.1 | Sub-deliverable | 1.1 | | 4 | 1.1.1.1 | Work package | 1.1.1 | | 4 | 1.1.1.2 | Work package | 1.1.1 | | 3 | 1.1.2 | Sub-deliverable | 1.1 | | 2 | 1.2 | Deliverable 2 | 1.0 | | 3 | 1.2.1 | Sub-deliverable | 1.2 | | 3 | 1.2.2 | Sub-deliverable | 1.2 | | 2 | 1.3 | Project management | 1.0 | | 3 | 1.3.1–1.3.3 | Planning; monitoring and control; reporting | 1.3 | Text equivalent: The project is decomposed from the total scope into deliverables, then sub-deliverables and work packages. Project-management work is included as part of the total scope rather than treated as work outside the WBS." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-wbs-rules", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "WBS Rules", "headingId": "chapter-11-project-management-and-pmp-frameworks-wbs-rules", "url": "#chapter-11-project-management-and-pmp-frameworks-wbs-rules", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. 100% Rule: The WBS should represent 100% of the scope defined for the project, including project-management work; it does not prove the scope itself is complete or correct. [BB-C11-S02] 2. No double-counting at the control level: Define ownership and handoffs so the WBS does not double-count scope; it need not impose a universal MECE rule across every representation. [BB-C11-S02] 3. Deliverable-Oriented: Focus on \"what,\" not \"how\" 4. Useful depth: Decompose only far enough to support ownership, estimating, control, and acceptance; no universal number of levels applies. 5. Work-package size: Size packages for the work, risk, reporting, and control needs; generic hour ranges are not a standard." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-example-wbs-crm-implementation", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Example WBS: CRM Implementation", "headingId": "chapter-11-project-management-and-pmp-frameworks-example-wbs-crm-implementation", "url": "#chapter-11-project-management-and-pmp-frameworks-example-wbs-crm-implementation", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "All names, tasks, hours, thresholds, and totals in this WBS and dictionary are constructed teaching assumptions, not benchmarks. | WBS | Deliverable or work package | Constructed hours | Parent | |---|---|---:|---| | 1.1 | Requirements and design (roll-up heading) | — | 1.0 CRM implementation | | 1.1.1.1–1.1.1.3 | Interviews; document requirements; prioritize requirements | 80 | 1.1 | | 1.1.2.1–1.1.2.3 | Architecture; migration design; integration design | 104 | 1.1 | | 1.1.3.1–1.1.3.3 | RFP; evaluation; selection and contracting | 80 | 1.1 | | 1.2.1–1.2.4 | Configuration; customization; migration; integration | 480 | 1.2 Development and configuration | | 1.2.5.1–1.2.5.3 | Unit, integration, and user-acceptance testing | 140 | 1.2.5 Testing | | 1.3.1–1.3.4 | Training development and delivery; deployment; hypercare | 204 | 1.3 Deployment and training | | 1.4.1–1.4.5 | Planning; meetings; risk; stakeholders; closeout | 172 | 1.4 Project management | Reconciliation note: The detailed constructed line items total 1,260 hours . The phase subtotal shown for 1.1 is intentionally not used as a roll-up because its child work packages total 264 hours; a real WBS must reconcile every parent subtotal to its children before approval." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-wbs-dictionary", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "WBS Dictionary", "headingId": "chapter-11-project-management-and-pmp-frameworks-wbs-dictionary", "url": "#chapter-11-project-management-and-pmp-frameworks-wbs-dictionary", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For each work package, document: - WBS Code: 1.2.5.3 - Name: User Acceptance Testing (UAT) - Description: End users test system to validate requirements met - Owner: Mary Johnson (QA Lead) - Duration: 60 hours - Predecessors: 1.2.5.2 (Integration Testing) - Deliverable: UAT Sign-off Document - Acceptance Criteria: 95% test cases passed, P1 bugs = 0" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-2", "url": "#chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-2", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the WBS to make scope, deliverables, ownership, acceptance evidence, and management work visible before estimating or baselining. - Apply the 100% rule to the defined scope, then test whether the scope itself is complete, feasible, authorized, and aligned with benefits. [BB-C11-S02] - Reconcile every parent subtotal, dependency, acceptance criterion, and change before relying on the WBS for schedule or cost decisions." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-2", "url": "#chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-2", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A WBS is not a requirements specification, schedule, budget, risk register, or proof that omitted work is immaterial. - Decomposition depth, work-package size, hours, and coding conventions depend on the project, organization, contract, and control needs. - A neat hierarchy can hide cross-cutting dependencies, operations work, uncertainty, or stakeholder obligations; maintain complementary records." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-connections-2", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-11-project-management-and-pmp-frameworks-connections-2", "url": "#chapter-11-project-management-and-pmp-frameworks-connections-2", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Schedule and cost: WBS components feed CPM, Gantt, and EVM only after calendars, estimates, baselines, and accounting rules are defined. - Risk and authority: Link work packages to owners, acceptance, risks, procurement, quality, change authority, and operational transition. - Client governance: Use Chapter 12 for stakeholder and approval context; use Chapter 4 where financial consequences require valuation or scenario analysis. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-overview-3", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-11-project-management-and-pmp-frameworks-overview-3", "url": "#chapter-11-project-management-and-pmp-frameworks-overview-3", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Critical Path Method (CPM) identifies the longest path under specified network logic, calendars, and duration assumptions; resource constraints, uncertainty, rework, and near-critical paths can change the result. [BB-C11-S03]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-critical-path-method-cpm", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Critical Path Method (CPM)", "headingId": "chapter-11-project-management-and-pmp-frameworks-critical-path-method-cpm", "url": "#chapter-11-project-management-and-pmp-frameworks-critical-path-method-cpm", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Under the specified network logic, calendars, and duration assumptions, identify the longest path and schedule sensitivity. Key Concepts: - Critical Path: Sequence of tasks with zero modeled slack; a delay can delay the project unless an approved change, recovery, or dependency adjustment offsets it. - Float/Slack: How much a task can be delayed without delaying project - Total Float = Late Finish - Early Finish - Free Float = Next task Early Start - Current task Early Finish - Crashing: Adding resources to critical path tasks to shorten duration - Fast-Tracking: Doing tasks in parallel that were planned sequentially (increases risk)" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-cpm-example", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "CPM Example", "headingId": "chapter-11-project-management-and-pmp-frameworks-cpm-example", "url": "#chapter-11-project-management-and-pmp-frameworks-cpm-example", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Tasks: Table 11.3 — Constructed CPM task register. Durations and dependencies are teaching assumptions for the worked network, not schedule benchmarks. | Task | Duration | Predecessors | |------|----------|--------------| | A. Requirements | 2 weeks | - | | B. Design | 3 weeks | A | | C. Development | 5 weeks | B | | D. Testing | 2 weeks | C | | E. Training Prep | 1 week | A | | F. Training Delivery | 1 week | D, E | | G. Deployment | 1 week | D, F | Network Diagram: Figure 11.2 — Constructed CPM dependency network. Numbers in parentheses are durations in weeks. Text equivalent: Requirements precedes both design and training preparation. Design precedes development, which precedes testing. Training delivery waits for both testing and training preparation. Deployment waits for testing and training delivery. The controlling path is A–B–C–D–F–G. Critical Path: A → B → C → D → F → G = 2 + 3 + 5 + 2 + 1 + 1 = 14 weeks . Although G also lists D as a predecessor, G cannot start until F finishes; the direct D-to-G dependency therefore does not shorten the controlling path. Float Analysis: - Tasks on critical path (A, B, C, D, F, G): 0 float - Task E: Can start as late as week 12 under the table's discrete-week convention (has 9 weeks of total float) - Task F: Must start after D finishes; it has 0 float and is on the critical path Crashing Analysis: If the illustrative target is 12 weeks (2 weeks earlier): - Option 1: Crash C (Development) by 2 weeks (add developers) - Option 2: Crash B (1 week) + D (1 week) - Option 3: Fast-track B and C (start C before B complete) - risky!" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-gantt-chart", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Gantt Chart", "headingId": "chapter-11-project-management-and-pmp-frameworks-gantt-chart", "url": "#chapter-11-project-management-and-pmp-frameworks-gantt-chart", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Visual timeline showing: - Task bars (duration) - Dependencies (arrows) - Milestones (diamonds) - Critical path (highlighted in red) - Resource assignments - Progress (% complete shading) Table 11.1 — Constructed schedule timeline. The table is the accessible timeline equivalent of the dependency network; week numbers are discrete teaching periods. | Task | Start week | Finish week | Duration | Critical? | Dependency note | |---|---:|---:|---:|---|---| | A. Requirements | 1 | 2 | 2 weeks | Yes | Starts the project | | B. Design | 3 | 5 | 3 weeks | Yes | After A | | C. Development | 6 | 10 | 5 weeks | Yes | After B | | D. Testing | 11 | 12 | 2 weeks | Yes | After C | | E. Training preparation | 3 | 3 | 1 week | No | After A; nine weeks total float | | F. Training delivery | 13 | 13 | 1 week | Yes | After D and E | | G. Deployment | 14 | 14 | 1 week | Yes | After D and F | Text equivalent: Requirements run in weeks 1–2, design in 3–5, development in 6–10, testing in 11–12, training delivery in 13, and deployment in 14; these tasks form the critical path. Training preparation can occur in week 3 and has nine weeks of total float before it constrains training delivery. Milestones: - Week 2 milestone: Requirements approved - Week 5 milestone: Design signed off - Week 10 milestone: Development complete - Week 12 milestone: UAT passed - Week 13 milestone: Training complete - Week 14 milestone: Go-live" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-3", "url": "#chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-3", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use CPM to identify schedule sensitivity and decision points, not to promise a finish date from a deterministic diagram. - Recalculate when dependencies, calendars, resources, rework, scope, risk, or near-critical paths change. - Pair the network with stakeholder commitments, cost, quality, safety, procurement, and release evidence before compressing or resequencing work." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-3", "url": "#chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-3", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The longest path depends on the modeled network and assumptions; it is not necessarily the only source of delay or the same as a resource-constrained critical chain. - Gantt precision can create false confidence when durations, dependencies, calendars, and completion evidence are uncertain. - Schedule variance is not automatically a calendar-percent-late forecast; interpret SPI and dates through the baseline and forecasting method." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-connections-3", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-11-project-management-and-pmp-frameworks-connections-3", "url": "#chapter-11-project-management-and-pmp-frameworks-connections-3", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Scope: WBS defines the deliverables and work packages whose dependencies CPM models. - Cost: EVM connects schedule and cost baselines, but the indices answer different questions and require stated assumptions. - Risk/change: Risk triggers, change authority, and stakeholder commitments can alter the network; update the schedule through the authorized route. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-overview-4", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-11-project-management-and-pmp-frameworks-overview-4", "url": "#chapter-11-project-management-and-pmp-frameworks-overview-4", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Earned Value Management (EVM) integrates an authorized scope, schedule, and cost baseline to measure performance and support forecasting under stated assumptions. [BB-C11-S04]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-key-metrics", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Key Metrics", "headingId": "chapter-11-project-management-and-pmp-frameworks-key-metrics", "url": "#chapter-11-project-management-and-pmp-frameworks-key-metrics", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Three Core Values: 1. Planned Value (PV) = Budgeted cost of work scheduled - \"What we planned to spend by now\" 2. Earned Value (EV) = Budgeted cost of work performed - \"Value of work actually completed\" 3. Actual Cost (AC) = Actual cost of work performed - \"What we actually spent\" Variance Metrics: Performance Indices: Forecasting:" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-evm-example", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "EVM Example", "headingId": "chapter-11-project-management-and-pmp-frameworks-evm-example", "url": "#chapter-11-project-management-and-pmp-frameworks-evm-example", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Project Status (Month 6 of 12-month project): - BAC (Budget at Completion): $1,200,000 - PV (Planned Value): $600,000 (50% of work planned to be done) - EV (Earned Value): $480,000 (40% of work actually completed) - AC (Actual Cost): $540,000 (actual spend to date) Variance Analysis: Interpretation: - At this status date, earned value is 80% of planned value; SPI does not directly mean the calendar finish is 20% late. - Earned value is $0.89 per dollar of actual cost, and CV is -$60K. Forecasting: The definitions and formulas are supported by the EVM source; all amounts and results in this example are constructed. [BB-C11-S04] Management response: Verify baseline integrity and the earned-value rule first. Then analyze causes and compare schedule, scope, cost, quality, risk, funding, and contractual options through the authorized change process; adding people or cutting scope is not an automatic remedy." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-evm-dashboard-visual", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "EVM Dashboard (Visual)", "headingId": "chapter-11-project-management-and-pmp-frameworks-evm-dashboard-visual", "url": "#chapter-11-project-management-and-pmp-frameworks-evm-dashboard-visual", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed EVM status record. Calculations use the unrounded CPI; color and escalation follow the project's approved thresholds rather than a universal red-status rule. | Measure | Constructed result | Decision use | |---|---:|---| | Planned completion | 50% | Compare with the earned-value rule and schedule network | | Earned completion | 40% | Validate objective completion evidence | | SPI | 0.80 | Investigate schedule variance; not a direct percent-late forecast | | CPI | 0.8889, reported as 0.89 | Investigate cost variance and forecast assumption | | EAC | $1,350K, or 112.5% of BAC | Conditional on current CPI persisting | | VAC | -$150K | Compare authorized scope, funding, risk, and change options | Text equivalent: At the status date, earned value is below planned value and actual cost exceeds earned value. The constructed SPI is 0.80, unrounded CPI is 0.8889, EAC is $1.35 million, and projected variance at completion is negative $150,000. The owner must validate the baseline and choose any escalation or change through the authorized governance process." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-4", "url": "#chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-4", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use EVM to make scope, schedule, cost, baseline integrity, variance, and forecast assumptions visible—not to reduce delivery to one score. - Keep SPI and CPI distinct, document the EAC/TCPI assumption, and validate earned-value rules and accounting alignment before escalation. - Combine EVM with risk, quality, stakeholder, benefits, safety, and change evidence before changing scope, funding, or the forecast." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-4", "url": "#chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-4", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- EVM measures performance against a baseline; it does not prove customer value, product quality, benefit realization, or causal responsibility. - SPI/CPI can be distorted by baseline quality, timing, accounting treatment, lagging data, scope changes, and work that is hard to measure objectively. - EAC and TCPI are conditional forecasts, not universal predictions; use alternative scenarios and authorized contingency rules when uncertainty is material." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-connections-4", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-11-project-management-and-pmp-frameworks-connections-4", "url": "#chapter-11-project-management-and-pmp-frameworks-connections-4", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Schedule: CPM and Gantt provide network and calendar context; SPI is not a direct percent-late claim. - Risk: Forecasts should be reconciled with risk exposure, correlation, contingency, and response effectiveness. - Governance: Use the change-control and charter sections to define who may alter baselines, approve funding, or accept residual variance. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-overview-5", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-11-project-management-and-pmp-frameworks-overview-5", "url": "#chapter-11-project-management-and-pmp-frameworks-overview-5", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Risk Management Framework is a constructed project-risk process that defines method, authority, uncertainty, owners, triggers, responses, and monitoring; quantitative analysis is conditional on decision value and data. [BB-C11-S01]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-risk-management-process", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Risk Management Process", "headingId": "chapter-11-project-management-and-pmp-frameworks-risk-management-process", "url": "#chapter-11-project-management-and-pmp-frameworks-risk-management-process", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 11.3. Iterative project-risk process (constructed teaching summary). Plan the method and authority first; use quantitative analysis only when it is decision-useful and supported by data. Monitoring can identify new risks, change assumptions, or require a response or baseline update. [BB-C11-S01] Text equivalent: Define the risk method, categories, owners, thresholds, and escalation. Identify uncertainties and opportunities, analyze them qualitatively, perform quantitative analysis when warranted, select and implement responses, and monitor triggers, residual risk, dependencies, and response effectiveness in a recurring loop." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-risk-register-template", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Risk Register Template", "headingId": "chapter-11-project-management-and-pmp-frameworks-risk-register-template", "url": "#chapter-11-project-management-and-pmp-frameworks-risk-register-template", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 11.4 — Constructed risk register. Entries, ordinal scores, owners, and responses are teaching assumptions; define the actual method and authority locally. | Risk ID | Risk Description | Category | Probability (1-5) | Impact (1-5) | Risk Score | Response Strategy | Owner | Status | |---------|-----------------|----------|-------------------|--------------|------------|-------------------|-------|--------| | R001 | Key vendor becomes unavailable | Procurement | 2 | 5 | 10 | Mitigate: Test qualified alternatives and continuity plan | Procurement owner | Active | | R002 | Critical capability becomes unavailable | Resource | 3 | 4 | 12 | Mitigate: Document dependencies and test continuity options | People owner | Active | | R003 | Requirements change mid-project | Scope | 4 | 3 | 12 | Accept: Agile approach with change control | PM | Active | | R004 | Integration with legacy system fails | Technical | 3 | 5 | 15 | Mitigate: Early integration testing, fallback plan | CTO | Watch | | R005 | Funding is reduced | Financial | 2 | 5 | 10 | Mitigate: Define staged scope and financing decision triggers | Finance owner | Watch | Table note: All entries and 1-5 scores are illustrative ordinal judgments, not measured probabilities or dollar exposure. Define scales, owners, interactions, and escalation locally." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-risk-response-strategies", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Risk Response Strategies", "headingId": "chapter-11-project-management-and-pmp-frameworks-risk-response-strategies", "url": "#chapter-11-project-management-and-pmp-frameworks-risk-response-strategies", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For Threats (Negative Risks): 1. Avoid: Eliminate the risk - Example: Remove risky feature from scope 2. Mitigate: Reduce probability or impact - Example: Add testing to reduce defect risk 3. Transfer: Shift risk to third party - Example: Buy insurance, outsource to vendor 4. Accept: Acknowledge risk, no proactive action - Example: Low probability/impact risks, set aside contingency reserve For Opportunities (Positive Risks): 1. Exploit: Ensure opportunity happens - Example: Assign best resources to maximize success 2. Enhance: Increase probability or impact - Example: Add features that could win industry award 3. Share: Partner to realize opportunity - Example: Joint venture to access new market 4. Accept: Don't actively pursue but benefit if occurs - Example: Hope for favorable exchange rates The response taxonomy and simulation instructions below are an author-created teaching synthesis. They do not claim that the cited PMBOK source prescribes these exact categories, distributions, iteration counts, or stability checks." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-quantitative-risk-analysis", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Quantitative Risk Analysis", "headingId": "chapter-11-project-management-and-pmp-frameworks-quantitative-risk-analysis", "url": "#chapter-11-project-management-and-pmp-frameworks-quantitative-risk-analysis", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Monte Carlo simulation: - Define defensible duration or cost distributions and dependencies. - Run enough simulations to obtain stable decision-relevant estimates; no universal iteration count applies. - Inspect sensitivity, correlation, tail behavior, and model risk before using the completion distribution. Example Output: - 10% confidence: Complete by Month 10 - 50% confidence: Complete by Month 12 - 90% confidence: Complete by Month 15 Decision: Select a funding or schedule confidence level through the authorized risk-appetite and contingency process; the sample percentiles are illustrative, not a default." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-risk-monitoring", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Risk Monitoring", "headingId": "chapter-11-project-management-and-pmp-frameworks-risk-monitoring", "url": "#chapter-11-project-management-and-pmp-frameworks-risk-monitoring", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Risk review cadence: 1. Update risk register (probabilities, impacts) 2. Identify new risks 3. Close risks that no longer apply 4. Review response effectiveness 5. Escalate under the project's defined triggers; an ordinal product alone does not quantify exposure." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-5", "url": "#chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-5", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Give each material risk or opportunity an owner, trigger, response, residual-risk decision, and review cadence. - Use qualitative analysis first and quantitative analysis only when its data, model, decision value, and limitations justify the effort. - Monitor correlation, dependencies, systemic effects, response effectiveness, and new risks rather than treating a static register as control." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-5", "url": "#chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-5", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Probability-impact scores are ordinal prompts unless their scales, data, aggregation, and interpretation are explicitly defined. - A risk register does not discover every unknown, establish acceptable exposure, or replace safety, security, legal, financial, or specialist controls. - Mitigation can create new risks, transfer exposure, or reduce one consequence while increasing another; record residual and secondary effects." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-connections-5", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-11-project-management-and-pmp-frameworks-connections-5", "url": "#chapter-11-project-management-and-pmp-frameworks-connections-5", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Schedule/cost: Link risk triggers to CPM, EVM, contingency, reserves, and change authority. - Stakeholders: Risk ownership and escalation should reflect affected people, clients, suppliers, regulators, and decision rights. - Delivery method: Predictive, adaptive, and hybrid teams all need a proportionate way to surface, decide, respond, and learn from uncertainty. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-overview-6", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-11-project-management-and-pmp-frameworks-overview-6", "url": "#chapter-11-project-management-and-pmp-frameworks-overview-6", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Stakeholder management organizes engagement hypotheses, affected groups, messages, participation, and decision routes; the categories and cadences below are constructed examples, not PMI-prescribed classifications. [BB-C11-S01]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-6", "url": "#chapter-11-project-management-and-pmp-frameworks-how-to-apply-6", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "PMBOK Guide Seventh Edition treats stakeholder engagement as a project-performance domain and emphasizes tailoring. [BB-C11-S01] The categories, matrices, labels, people, cadences, and messages below are constructed examples rather than PMI-prescribed stakeholder classifications or communication frequencies." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-stakeholder-identification", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Stakeholder Identification", "headingId": "chapter-11-project-management-and-pmp-frameworks-stakeholder-identification", "url": "#chapter-11-project-management-and-pmp-frameworks-stakeholder-identification", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Stakeholder Categories: - Internal: Team members, functional managers, executives, PMO - External: Customers, suppliers, regulators, community - Upward: Sponsor, steering committee, senior leadership - Downward: Project team, contractors - Outward: Customers, partners, vendors - Sideward: Peer project managers, other departments" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-stakeholder-analysis-matrix", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Stakeholder Analysis Matrix", "headingId": "chapter-11-project-management-and-pmp-frameworks-stakeholder-analysis-matrix", "url": "#chapter-11-project-management-and-pmp-frameworks-stakeholder-analysis-matrix", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 11.5 — Constructed stakeholder analysis matrix. Categories, ratings, and strategies are teaching assumptions, not PMI-prescribed classifications. | Stakeholder | Role | Power | Interest | Influence | Attitude | Strategy | |-------------|------|-------|----------|-----------|----------|----------| | CEO | Sponsor | High | Medium | High | Supportive | Keep Satisfied | | CFO | Funding approver | High | Low | High | Neutral | Keep Satisfied | | CTO | Technical owner | High | High | High | Supportive | Manage Closely | | VP Sales | End user leader | Medium | High | Medium | Resistant | Keep Informed + Engage | | IT Director | Integration lead | Medium | High | Medium | Supportive | Manage Closely | | Sales Reps | End users | Low | High | Low | Resistant | Keep Informed | | Vendor PM | Implementation | Medium | High | Medium | Supportive | Manage Closely |" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-engagement-strategies", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Engagement Strategies", "headingId": "chapter-11-project-management-and-pmp-frameworks-engagement-strategies", "url": "#chapter-11-project-management-and-pmp-frameworks-engagement-strategies", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Based on a constructed power/interest aid: High Power, High Interest (Manage Closely): - Weekly 1-on-1 meetings - Input into major decisions - Early previews of deliverables - Example: CTO, IT Director High Power, Low Interest (Keep Satisfied): - Monthly executive briefings - Escalate only critical issues - Ensure no surprises - Example: CEO, CFO Low Power, High Interest (Keep Informed): - Email updates - Town halls / Q&A sessions - Training and demos - Example: Sales Reps Low Power, Low Interest (Monitor): - Mass communications - Annual updates - Example: Facilities team" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-communication-plan", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Communication Plan", "headingId": "chapter-11-project-management-and-pmp-frameworks-communication-plan", "url": "#chapter-11-project-management-and-pmp-frameworks-communication-plan", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 11.6 — Constructed communication plan. Cadences, channels, messages, and owners must be tailored to the actual decision and affected groups. | Stakeholder | Message | Frequency | Medium | Owner | |-------------|---------|-----------|--------|-------| | Steering Committee | Project status, major decisions | Monthly | PowerPoint + meeting | PM | | Sponsor | Red flags, budget/scope changes | Weekly | Email + 1-on-1 | PM | | Project Team | Tasks, dependencies, issues | Daily | Standup + Jira | PM + Leads | | End Users | Training, go-live readiness | Bi-weekly | Email + demos | Change Mgmt Lead | | Executives | Milestones, ROI | Quarterly | Executive dashboard | PM |" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-6", "url": "#chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-6", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Map who is affected, who decides, who must consent, who supplies evidence, and who bears delivery or operational consequences. - Tailor engagement, message, cadence, channel, accessibility, confidentiality, and escalation to the decision and affected groups. - Treat resistance, silence, support, and influence as hypotheses to investigate; do not reduce people to a fixed power-interest quadrant." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-6", "url": "#chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-6", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Stakeholder categories and communication frequencies are constructed aids, not universal classifications or guarantees of engagement. - A power/interest matrix can hide rights, dependency, expertise, vulnerability, informal influence, and groups absent from the sponsor's view. - Engagement does not replace consent, labor, privacy, safety, accessibility, procurement, regulatory, or professional obligations." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-connections-6", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-11-project-management-and-pmp-frameworks-connections-6", "url": "#chapter-11-project-management-and-pmp-frameworks-connections-6", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Governance: Project charters and change-control routes define authority, escalation, acceptance, and accountability. - Leadership: Use Chapter 7 for team, conflict, participation, and psychological-safety questions; use Chapter 12 for client governance. - Evidence: Link stakeholder feedback to scope, risk, quality, schedule, cost, benefits, and decision records rather than treating communication as an output alone. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-overview-7", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-11-project-management-and-pmp-frameworks-overview-7", "url": "#chapter-11-project-management-and-pmp-frameworks-overview-7", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scrum is an empirical framework with Product Owner, Scrum Master, and Developers accountabilities, events, artifacts, and commitments. It does not require user stories, points, velocity targets, grooming, or a separate Development Team. [BB-C11-S05]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-7", "url": "#chapter-11-project-management-and-pmp-frameworks-how-to-apply-7", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The 2020 Scrum Guide defines a Scrum Team with three accountabilities: Product Owner, Scrum Master, and Developers. It describes events, artifacts, and commitments but does not require user stories, story points, velocity targets, a points-to-hours conversion, “grooming,” or a separate Development Team. [BB-C11-S05] Accountabilities: 1. Product Owner: Accountable for maximizing product value and effective Product Backlog management. 2. Scrum Master: Accountable for establishing Scrum and the Scrum Team's effectiveness. 3. Developers: Accountable for creating a usable Increment each Sprint, including the Sprint Backlog, quality through the Definition of Done, daily adaptation, and mutual professional accountability. Artifacts: 1. Product Backlog: Emergent ordered list of what is needed to improve the product; Product Goal is its commitment. 2. Sprint Backlog: Sprint Goal, selected Product Backlog items, and the delivery plan. 3. Increment: A usable step toward the Product Goal that meets the Definition of Done. Events: 1. Sprint: Fixed-length event of one month or less containing the other events. 2. Sprint Planning: Establish why the Sprint is valuable, what can be done, and how the work will be accomplished. 3. Daily Scrum: Fifteen-minute event for Developers to inspect progress toward the Sprint Goal and adapt the plan. 4. Sprint Review: Inspect the Sprint outcome with stakeholders and determine future adaptations; it is not merely a demo. 5. Sprint Retrospective: Plan ways to increase quality and effectiveness. Product Backlog refinement is an ongoing activity, not a formal Scrum event. The Guide's maximum event timeboxes apply to a one-month Sprint and are usually shorter for shorter Sprints. [BB-C11-S05]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-constructed-two-week-team-cadence", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Constructed two-week team cadence", "headingId": "chapter-11-project-management-and-pmp-frameworks-constructed-two-week-team-cadence", "url": "#chapter-11-project-management-and-pmp-frameworks-constructed-two-week-team-cadence", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This schedule is an optional team tactic, not an official Scrum requirement." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-optional-relative-estimation", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Optional relative estimation", "headingId": "chapter-11-project-management-and-pmp-frameworks-optional-relative-estimation", "url": "#chapter-11-project-management-and-pmp-frameworks-optional-relative-estimation", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A team may use relative estimates, flow measures, probabilistic forecasts, or other aids when they improve transparency. Do not convert story points into universal hours or compare velocity across teams. If velocity is used, treat it as a local planning observation rather than a productivity target or performance score. [BB-C11-S05]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-7", "url": "#chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-7", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Separate Scrum's defined accountabilities, events, artifacts, and commitments from optional team practices such as user stories, estimation, and local cadence. - Use the Sprint Goal and usable Increment to inspect value, quality, and learning rather than treating velocity or selected backlog volume as a performance target. - Preserve predictive controls, specialist review, evidence, and release authority where the product, contract, safety, privacy, or regulatory context requires them." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-7", "url": "#chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-7", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Scrum is a framework, not a guarantee of delivery speed, product value, team health, or stakeholder agreement. - User stories, points, velocity, burndown charts, two-week cadences, and timebox examples in this chapter are optional local tactics, not Scrum requirements. - Scrum accountabilities and events do not replace architecture, risk, accessibility, security, compliance, procurement, employment, or operational-transition obligations." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-connections-7", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-11-project-management-and-pmp-frameworks-connections-7", "url": "#chapter-11-project-management-and-pmp-frameworks-connections-7", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Flow: Framework 8 can add explicit work-state and WIP policies when the team defines how they interact with Scrum. - Governance: Frameworks 6, 9, and 10 connect stakeholder engagement, change authority, charter boundaries, and evidence. - Tailoring: Use the methodology workshop below and Chapters 6, 8, 9, 10, and 12 to design a context-specific delivery system. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-overview-8", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-11-project-management-and-pmp-frameworks-overview-8", "url": "#chapter-11-project-management-and-pmp-frameworks-overview-8", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The flow board and WIP policy below is a constructed management aid for making work states, bottlenecks, and explicit operating policies visible. It is not a complete or certified presentation of the Kanban Method; any named-method claim requires an inspected authoritative source." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-8", "url": "#chapter-11-project-management-and-pmp-frameworks-how-to-apply-8", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the board to define work-item states, entry and exit policies, ownership, blocked-work handling, and a feedback cadence. Set WIP limits from observed flow, work type, service expectations, and quality constraints; treat the sample values as teaching assumptions." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-example-flow-board", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Example flow board", "headingId": "chapter-11-project-management-and-pmp-frameworks-example-flow-board", "url": "#chapter-11-project-management-and-pmp-frameworks-example-flow-board", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This section is a constructed flow-management aid, not a complete or certified presentation of the Kanban Method. A formal Kanban treatment needs an inspected authoritative source before publication under that name. Table 11.2. Constructed flow-board example. The board is a teaching aid; work-item states, policies, and ownership must be defined for the actual service system. | Backlog | To Do | In Progress | Code Review | Testing | Done | |---|---|---|---|---|---| | Story 1 | Story 2 | Story 3 (2/3) | Story 4 (1/2) | Story 5 (0/1) | Story 6 | | Story 7 | Story 8 | | | | Story 9 | | Story 10 | | | | | Story 11 |" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-wip-work-in-progress-limits", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "WIP (Work in Progress) Limits", "headingId": "chapter-11-project-management-and-pmp-frameworks-wip-work-in-progress-limits", "url": "#chapter-11-project-management-and-pmp-frameworks-wip-work-in-progress-limits", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Prevent bottlenecks and make flow constraints visible. The limits below are an illustrative operating policy; teams should adapt them to observed capacity, work type, and service expectations. Example Limits: - Backlog: No limit - To Do: 10 items - In Progress: 3 items (team of 6 = 50% capacity) - Code Review: 2 items - Testing: 1 item - Done: No limit Operating rule: If a column reaches its WIP limit, the team can choose to help clear that bottleneck before starting new work. This is an author recommendation, not a universal threshold." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-flow-metrics-constructed", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Flow Metrics (constructed)", "headingId": "chapter-11-project-management-and-pmp-frameworks-flow-metrics-constructed", "url": "#chapter-11-project-management-and-pmp-frameworks-flow-metrics-constructed", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Cycle Time: Time from \"In Progress\" to \"Done\" - Example target: <5 days for an average story Lead Time: Time from \"Backlog\" to \"Done\" - Example target: <10 days Throughput: Items completed per unit of time - Track the distribution and work-item definition. Throughput need not continually increase; quality, mix, blocked work, demand, and system constraints matter. Cumulative flow diagram: Visualize work in workflow states over time to investigate flow and accumulation; it does not diagnose the cause by itself." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-8", "url": "#chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-8", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Make work visible at the level needed to decide, coordinate, protect quality, and expose blocked work. - Use WIP limits as an explicit policy to prompt flow decisions, not as a universal capacity ratio or productivity quota. - Review cycle time, lead time, throughput, blocked time, demand, quality, and work-item mix together before changing the system." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-8", "url": "#chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-8", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- This chapter's board, limits, targets, and examples are constructed aids and are not evidence for a certified Kanban implementation. - A flow metric is descriptive; it does not by itself establish causation, customer value, quality, safety, or sustainable capacity. - Reducing WIP or increasing throughput can worsen quality, overload people, or hide work unless the service system and decision constraints are examined." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-connections-8", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-11-project-management-and-pmp-frameworks-connections-8", "url": "#chapter-11-project-management-and-pmp-frameworks-connections-8", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Predictive controls: Use the board alongside scope, dependency, schedule, risk, cost, and change-authority evidence rather than as a replacement. - Adaptive delivery: Scrum events and backlog governance can coexist with explicit flow policies when the team defines how they interact. - Operations: Connect flow evidence to Chapter 6 process constraints, Chapter 8 measures, and Chapter 12 client commitments. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-overview-9", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-11-project-management-and-pmp-frameworks-overview-9", "url": "#chapter-11-project-management-and-pmp-frameworks-overview-9", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A change-control process records a proposed change, analyzes its effects and alternatives, routes it to the authorized decision-maker, and updates affected baselines, contracts, evidence, communications, and benefits. The route is tailored to materiality and delegated authority; a Change Control Board is one possible mechanism, not a universal requirement. This is an author-created governance synthesis, not a PMI-prescribed procedure." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-change-request-workflow", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Change Request Workflow", "headingId": "chapter-11-project-management-and-pmp-frameworks-change-request-workflow", "url": "#chapter-11-project-management-and-pmp-frameworks-change-request-workflow", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This author-created workflow applies general planning, stakeholder, delivery, and uncertainty principles to a change request; organizations should adapt roles and approval levels to the project context. Figure 11.4. Tailored change-authority workflow (constructed). Route a proposed change by materiality and delegated authority; a Change Control Board is one possible authority, not a universal requirement. Update affected scope, schedule, cost, quality, risk, benefits, contracts, evidence, and communications before implementation. [BB-C11-S01] Text equivalent: Record the request and authority, analyze impacts and alternatives, route it to the authorized individual or body, record approval, rejection, or deferral, update the controlled baselines and communications, implement through the delivery system, validate the result, and monitor benefits and side effects." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-possible-change-authority", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Possible change authority", "headingId": "chapter-11-project-management-and-pmp-frameworks-possible-change-authority", "url": "#chapter-11-project-management-and-pmp-frameworks-possible-change-authority", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Depending on delegated authority and materiality, a product owner, sponsor, contract authority, licensed professional, regulator, board, or change control board may decide. A sample board might include: Illustrative composition: - Project Manager (chair) - Project Sponsor - Key stakeholders (business, technical) - Subject matter experts (as needed) Cadence: Set from decision urgency, risk, evidence, and service expectations; no universal weekly meeting applies." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-change-request-form", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Change Request Form", "headingId": "chapter-11-project-management-and-pmp-frameworks-change-request-form", "url": "#chapter-11-project-management-and-pmp-frameworks-change-request-form", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "| Field | Description | |-------|-------------| | CR ID | CR-2024-047 | | Requested By | Jane Smith (VP Sales) | | Date | 2024-11-15 | | Title | Add mobile app support | | Description | Enable sales reps to access CRM from mobile devices | | Justification | 60% of team works remotely, need access in field | | Impact Analysis | | | - Scope | +3 months development | | - Schedule | Push go-live from June to September | | - Cost | +$150K (mobile development) | | - Quality | Requires additional testing | | - Risk | New: Integration with mobile OS updates | | Alternatives | 1) Responsive web design (lower cost, less functionality) 2) Defer to Phase 2 | | CCB Decision | ☐ Approved ☐ Rejected ☑ Approved with Modifications | | Modifications | Approve responsive web design (Alternative 1), defer native app to Phase 2 | | Approvers | PM: John Doe, Sponsor: Mary Johnson, CTO: Bob Lee |" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-9", "url": "#chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-9", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Make decision rights, materiality, affected parties, evidence, alternatives, and implementation ownership explicit before approving change. - Route changes through the smallest authorized mechanism that can evaluate the consequences, while escalating when contract, safety, regulation, funding, or benefits are affected. - Update the controlled record and validate outcomes after implementation; approval alone is not evidence that the change worked." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-9", "url": "#chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-9", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The workflow and form are constructed examples and do not establish an organization's approval authority, legal obligations, or contract terms. - Not every change requires a formal CCB; backlog, product, sponsor, contract, professional, regulatory, or board authority may be appropriate depending on context. - Impact analysis is only as good as the baseline, data, alternatives, affected voices, and specialist review available to the decision." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-connections-9", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-11-project-management-and-pmp-frameworks-connections-9", "url": "#chapter-11-project-management-and-pmp-frameworks-connections-9", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Baseline integrity: Link change decisions to WBS scope, CPM dependencies, EVM baselines, risk exposure, quality evidence, and benefits. - Stakeholders: Use Framework 6 and Chapter 12 to identify consent, communication, client, supplier, and escalation needs. - Delivery method: Predictive, adaptive, and hybrid teams all need explicit change authority and learning loops, even when the artifacts differ. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-overview-10", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-11-project-management-and-pmp-frameworks-overview-10", "url": "#chapter-11-project-management-and-pmp-frameworks-overview-10", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The project charter summarizes purpose, sponsor, decision rights, boundaries, success evidence, major uncertainty, and assigned authority. Whether a charter formally authorizes work or resources depends on the organization's governance instruments; the sample below is an author-created teaching template, not a PMI template." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-10", "url": "#chapter-11-project-management-and-pmp-frameworks-how-to-apply-10", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Adapt the fields to the actual governance instrument, decision, contract, funding model, assurance needs, and operating transition. Mark every target, threshold, date, amount, and named role as an assumption until its owner and evidence are confirmed." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-project-charter-contents", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Project Charter Contents", "headingId": "chapter-11-project-management-and-pmp-frameworks-project-charter-contents", "url": "#chapter-11-project-management-and-pmp-frameworks-project-charter-contents", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Project Overview - Project Name: CRM Implementation Project - Project Manager: John Doe - Sponsor: Mary Johnson (VP Sales) - Start Date: January 1, 2025 - Target End Date: December 31, 2025 2. Business Case - Problem Statement: Current CRM is outdated, lacks integration, poor user adoption (20%) - Business Opportunity: Modern CRM can increase sales productivity 25%, improve forecast accuracy - Expected Benefits: - $2M annual revenue increase (better pipeline management) - $500K cost reduction (automation) - 80% user adoption target - Alignment to Strategy: Supports Digital Transformation Initiative 3. Project Objectives (SMART) - Implement Salesforce CRM for 100 sales users by Dec 31, 2025 - Achieve 80% user adoption within 3 months of go-live - Integrate with ERP (SAP) for real-time order sync - Migrate 10 years of customer data with 40 from users 11. Authority & Governance Project Manager Authority: - Manage day-to-day project activities - Assign tasks to team members - Approve expenditures <$10K - Escalate issues to sponsor Governance: - Steering Committee: Monthly (Sponsor, PM, IT Director, Sales VP) - Project Team Meetings: Weekly - Status Reports: Weekly to Sponsor, Monthly to Steering Committee Approvals: Project Sponsor: Date: (Mary Johnson, VP Sales) Project Manager: Date: (John Doe)" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-10", "url": "#chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-10", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use a charter to make purpose, authority, boundaries, assumptions, benefits, evidence, and stop or escalation conditions discussable before work accelerates. - Separate a teaching template from the organization's actual authorization, funding, contract, safety, privacy, regulatory, and board instruments. - Revisit the charter when evidence changes the problem, value case, authority, constraints, or delivery design; a signature is not a substitute for governance." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-10", "url": "#chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-10", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The CRM names, dates, amounts, targets, and thresholds are fictional teaching assumptions and must not be copied as benchmarks. - A charter cannot resolve ambiguous strategy, weak requirements, missing consent, untested feasibility, or specialist obligations by itself. - Success criteria should include outcome, quality, adoption, risk, equity/accessibility, operational readiness, and benefits evidence appropriate to the context." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-connections-10", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-11-project-management-and-pmp-frameworks-connections-10", "url": "#chapter-11-project-management-and-pmp-frameworks-connections-10", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Scope and schedule: Use Frameworks 2 and 3 to turn charter boundaries into an auditable WBS and dependency model. - Authority and change: Use Frameworks 5, 6, and 9 to connect risk, stakeholders, decision rights, and change routes. - Strategy and operations: Use Chapters 6, 8, 9, 10, and 12 to connect constraints, measures, problem structure, integrated initiatives, and client governance. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-how-to-get-started-choosing-your-project-methodology", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "How To Get Started: Choosing Your Project Methodology", "headingId": "chapter-11-project-management-and-pmp-frameworks-how-to-get-started-choosing-your-project-methodology", "url": "#chapter-11-project-management-and-pmp-frameworks-how-to-get-started-choosing-your-project-methodology", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Delivery approach is one design decision among governance, architecture, contracting, funding, team topology, evidence, and operating transition. Tailor those dimensions separately; do not choose a branded method by adding up binary signals. [BB-C11-S01] [BB-C11-S06]" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-rapid-tailoring-workshop", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Rapid tailoring workshop", "headingId": "chapter-11-project-management-and-pmp-frameworks-rapid-tailoring-workshop", "url": "#chapter-11-project-management-and-pmp-frameworks-rapid-tailoring-workshop", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Timebox the workshop to the decision, not a universal 90-minute rule. Record: | Dimension | Questions | Possible design response | |---|---|---| | Outcome and uncertainty | Which needs, solutions, and constraints are known? What must be learned? | Stage discovery, prototypes, experiments, or predictive definition where justified. | | Failure consequence | What safety, legal, financial, operational, or customer harm could occur? | Independent assurance, traceability, formal evidence, hold points, rollback, or specialist approval. | | Dependencies and architecture | Which work is truly sequential, coupled, resource-constrained, or reversible? | Network planning, interface controls, incremental integration, or protected architecture decisions. | | Contract and funding | How are scope, change, acceptance, incentives, cash, and risk allocated? | Align commercial terms and funding gates with uncertainty rather than forcing false certainty. | | Feedback and release | Who can evaluate increments, how often, and under what release controls? | Reviews, pilots, staged rollout, feature flags, simulations, or scheduled acceptance. | | Governance and evidence | Who decides, approves, challenges, stops, and retains records? | Tailored authority, assurance, reporting, change, and audit design. | Output: A one-page delivery-design decision that states which predictive, adaptive, flow, and assurance practices will be used, why each fits, and what evidence would trigger a change. Regulation, fixed dates, documentation, or stakeholder visibility do not mechanically select one method. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-detailed-version-full-project-initiation-6-8-weeks", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Detailed Version: Full Project Initiation (6-8 weeks)", "headingId": "chapter-11-project-management-and-pmp-frameworks-detailed-version-full-project-initiation-6-8-weeks", "url": "#chapter-11-project-management-and-pmp-frameworks-detailed-version-full-project-initiation-6-8-weeks", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed-methodology boundary: The detailed initiation, execution, and measurement examples below are fictional teaching scenarios. Hours, page counts, team sizes, cadences, thresholds, dates, and task counts are not defaults; replace each with a named owner, rationale, evidence source, authority, applicability condition, tolerance, and review rule. For larger projects requiring comprehensive planning:" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-phase-1-requirements-charter-weeks-1-3", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 1: Requirements & Charter (Weeks 1-3)", "headingId": "chapter-11-project-management-and-pmp-frameworks-phase-1-requirements-charter-weeks-1-3", "url": "#chapter-11-project-management-and-pmp-frameworks-phase-1-requirements-charter-weeks-1-3", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 1: Kickoff & Scope Definition Workshops: - Monday: Project scope workshop (2 hours) - Problem statement: \"What are we solving?\" - Success criteria: \"How will we know it worked?\" - In/Out of scope: \"What's NOT included?\" - Constraints: \"What limits us?\" (budget, timeline, regulatory) - Tuesday-Wednesday: Stakeholder interviews (1 hour each, 10 stakeholders) - Document their needs, concerns, expectations - Identify potential resistance points - Get preliminary estimate of \"flexibility\" - Thursday: Draft requirements (high-level) - 30-50 bullet points on what solution must do - NOT detailed specs, just key capabilities - Friday: Team alignment - Present draft scope to team/sponsor - Get verbal approval to proceed Outputs: - Scope statement (1 page) - Stakeholder analysis (power/interest grid) - Preliminary requirements list (50 bullets) - Constraints document (budget, timeline, risks) --- Week 2 template: Requirements, evidence, and near-term work design - Select requirements, backlog, model-based, prototype, experiment, or other representations appropriate to the decision and assurance needs. - Define traceability only to the level required for scope, design, testing, acceptance, safety, regulation, contract, and change authority. - Obtain approvals from the actual authorized roles; not every stakeholder signs every requirement. - Choose document depth from complexity, risk, volatility, supplier interfaces, and evidence obligations. Page count is not a quality target. - Expect controlled learning and change. “Zero requirement changes” is not a valid universal objective. - User stories and story points are optional local techniques, not Agile or Scrum requirements. Prioritize enough near-term work to support delivery and learning without fixed story counts or known/unknown percentages. --- Week 3: Planning & Charter Waterfall Path: 1. Project Charter: Use Framework #10 template - Business case, objectives, stakeholders, budget, timeline - Get sponsor sign-off (formal authority) 2. Work Breakdown Structure (WBS): - Decompose all scope into 3-4 levels - Include Project Management as main deliverable - Size work packages to support estimation, ownership, control, and progress visibility; no universal 8–80-hour rule applies - Total estimated effort: baseline for schedule 3. Schedule Development: - Create task list from WBS (150+ tasks) - Estimate duration (days) for each task - Identify dependencies (which must finish before others start) - Run CPM analysis (identify critical path) - Add a contingency buffer on critical path tasks based on risk exposure - Create Gantt chart with milestones 4. Budget: - Resource-loaded costs (staff, contractors, tools) - Vendor costs (licenses, hardware, services) - Contingency based on risk exposure - Get CFO approval Agile Path: 1. Product Vision Document (1 page) - \"What are we building and why?\" (elevator pitch) - Success metrics (adoption, revenue, customer satisfaction) - Timeline: How long until feature-complete? Release 1.0? 2. Release Plan: - Define MVP scope (what's in Release 1.0?) - High-level roadmap (quarters or releases) - Target launch date 3. Team Setup: - Product Owner assigned for product-value decisions - Scrum Master identified for Scrum and team effectiveness - Developers and other delivery specialists assembled as the product and assurance context requires 4. Infrastructure: - Set up Jira/Azure DevOps board - Create epics + user stories - Configure WIP limits - Schedule sprint meetings ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-phase-2-project-setup-kick-off-weeks-4-6", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 2: Project Setup & Kick-off (Weeks 4-6)", "headingId": "chapter-11-project-management-and-pmp-frameworks-phase-2-project-setup-kick-off-weeks-4-6", "url": "#chapter-11-project-management-and-pmp-frameworks-phase-2-project-setup-kick-off-weeks-4-6", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 4: Risk & Communications Planning Risk Management Setup: 1. Conduct risk identification workshop (2 hours) - Brainstorm top 15-20 risks (threats + opportunities) - Categorize: Technical, Resource, Schedule, Budget, External - Document on risk register 2. Risk Analysis: - If useful, define local ordinal probability and impact scales with owners, evidence, triggers, and review dates; the scale is not a measured probability or exposure model - A sample P × I score can support triage only when its interpretation and escalation rule are approved; it does not quantify risk by itself - Prioritize risks through the defined method, considering correlation, dependencies, severity, opportunity, and decision value 3. Risk Response Planning: - For high-score risks: develop mitigation strategy - Assign risk owner (who monitors it?) - Define contingency (if risk occurs, what's our backup plan?) Communication Planning: For Waterfall projects: - Sponsor: Weekly email + monthly 1-on-1 - Steering Committee: Monthly meetings (30 min) - Project team: Weekly 60-min status meeting - Stakeholders: Monthly updates (email or town hall) For Agile projects: - Product Owner: Daily (quick syncs as needed) - Stakeholders: Sprint reviews every 2 weeks (demo of completed work) - Team: Daily standup (15 min) - Leadership: Decision-relevant outcome, forecast, flow, quality, risk, and capacity evidence; do not use team velocity as an executive productivity score --- Week 5: Procurement & Vendor Setup - Identify make-vs-buy decisions (build in-house vs. buy/outsource) - If buying: RFP, vendor evaluation, contracting - If outsourcing: Statement of Work (SOW), KPIs, governance - Set up vendor kick-off meetings --- Week 6: Final Approvals & Kick-off - Final review of charter/plan with steering committee - Get formal approvals (Sponsor, CFO, CTO) - Announce project to all stakeholders - Kick-off meeting (1-2 hours) - Explain project goals, timeline, how to participate - Introduce team leads and key stakeholders - Set expectations for communication/engagement ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-phase-3-execution-months-2-6", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 3: Execution (Months 2-6+)", "headingId": "chapter-11-project-management-and-pmp-frameworks-phase-3-execution-months-2-6", "url": "#chapter-11-project-management-and-pmp-frameworks-phase-3-execution-months-2-6", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Waterfall Projects: Weekly Activities: - Standup: 30-min team sync (what did we complete? what's next? blockers?) - Status Update: Document schedule/cost variance using EVM metrics - Risk Review: Check risk register, look for new risks - Scope Management: Triage change requests through CCB Monthly Activities: - Sponsor 1-on-1: Review status, discuss issues, get decisions - Steering Committee: Present metrics, escalate risks 10 Control Activities: - Track actual effort vs. planned (budget variance) - Track schedule progress (milestone completion) - If SPI or CPI differs materially from the approved tolerance: verify data and EVM assumptions, diagnose drivers, update forecasts, and choose a response through the authorized owner. A 0.95 threshold does not automatically require recovery or cost reduction. --- Agile Projects: Daily Activities: - Standup: 15 min (completed yesterday, doing today, blockers) - Dev work: Build user stories from sprint backlog Sprint Cycle (2 weeks): Monday (Sprint Planning): - 2-4 hours depending on sprint length - Select user stories from product backlog - Team estimates effort (story points) - Commit to sprint goal (e.g., \"Deploy user registration features\") Tuesday-Thursday: - Daily standup (15 min) - Dev work - Code reviews - Testing Friday (Sprint Review + Retrospective): - Sprint Review (60 min): Demo completed work to stakeholders + product feedback - Retrospective (60 min): Team discusses \"What went well?\" \"What to improve?\" - Capture 2-3 action items for next sprint - Next Monday: Sprint Planning begins again Velocity Tracking: - If the team uses story points, observe them only within that team and estimation system. - Do not require stabilization after a fixed number of sprints or convert points directly into calendar duration without scope, uncertainty, capacity, dependencies, and historical forecast error. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-waterfall-pitfalls", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Waterfall Pitfalls", "headingId": "chapter-11-project-management-and-pmp-frameworks-waterfall-pitfalls", "url": "#chapter-11-project-management-and-pmp-frameworks-waterfall-pitfalls", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Pitfall 1: Frozen Requirements That Are Wrong - Problem: Spent 2 months documenting requirements, market changed, requirements are obsolete - Response: Route proposed changes by decision authority, materiality, evidence, dependency, and assurance need. A requirements freeze is one possible control, not a default; preserve traceability while allowing governed learning. - Risk if unresolved: Rework, delay, or obsolete output can result, but magnitude and timing depend on the project and evidence. Pitfall 2: No Executive Sponsor Engagement - Problem: PM manages project, sponsor ignores it, then says \"This isn't what we wanted\" at end - Response: Agree the sponsor's decisions, access, evidence, escalation route, and approval cadence from governance, consequence, and uncertainty rather than imposing weekly or monthly meetings. - Risk if unresolved: Unclear authority or delayed decisions can cause rework, pause, or cancellation; no fixed three-to-six-month loss is assumed. Pitfall 3: Schedule Overruns from Critical Path - Problem: Over-estimated task durations, didn't identify true critical path, project slips - Response: CPM identifies modeled critical and near-critical dependency paths under current duration and sequencing assumptions. Test uncertainty, resource constraints, merge points, calendars, and path changes before intervening. - Resource caveat: Adding people, equipment, overlap, or buffers can help, do nothing, or increase coordination and risk. Compare crashing, fast-tracking, resequencing, scope, capacity, and acceptance effects rather than adding resources only to one path. Pitfall 4: Vendors Not Held Accountable - Problem: Vendor misses deadlines, PM has no leverage - Fix: Clear SOW, measurable KPIs, contractual penalties/rewards, weekly governance - Cost of skipping: Material scope left undelivered on time ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-agile-pitfalls", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Agile Pitfalls", "headingId": "chapter-11-project-management-and-pmp-frameworks-agile-pitfalls", "url": "#chapter-11-project-management-and-pmp-frameworks-agile-pitfalls", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Pitfall 1: No Clear Product Vision - Problem: Team starts building, then discovers they're building wrong thing - Fix: Spend 1 week defining product vision, MVP scope, and success metrics upfront - Cost of skipping: 8-12 weeks of wasted development Pitfall 2: Absent Product Owner - Problem: PO doesn't prioritize stories, team doesn't know what's next - Fix: Require the PO to be materially available, not a nominal part-time role - Risk of skipping: Poorly understood work, weak Sprint Goals, churn, or missed decision priorities Pitfall 3: Forecast and Sprint Goal failures - Problem: The team repeatedly selects work that does not support a credible Sprint Goal or current capacity - Response: Developers forecast from current capacity, work, dependencies, risk, and relevant history; velocity is optional and not a commitment target - Risk: Persistent forecast error or weak goals can reduce confidence and delay decisions Pitfall 4: Testing Debt Piles Up - Problem: Team prioritizes features, defers testing, accumulates bugs - Fix: Definition of Done: Features not done until tested, QA integrated in sprint - Cost of skipping: 2-3 months to fix technical debt before release ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-measurement-how-to-know-you-re-on-track", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Measurement: How to Know You're On Track", "headingId": "chapter-11-project-management-and-pmp-frameworks-measurement-how-to-know-you-re-on-track", "url": "#chapter-11-project-management-and-pmp-frameworks-measurement-how-to-know-you-re-on-track", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Waterfall Projects: Every Week: - Schedule Variance (SV) -5% → On track - Cost Variance (CV) -5% → On budget - Risk register updated, no new surprises Every Month: - Milestones hit on schedule (0-5% slip acceptable) - Sponsor reports \"no surprises\" - Steering committee has <2 escalations (shows healthy governance) Before Launch: - Authorized scope, acceptance, safety, security, quality, and operational-readiness evidence satisfy the decision-specific release criteria - Defects are within severity- and exposure-based tolerance; a percentage of “critical” defects is not a valid release rule - UAT sign-off obtained - Cutover plan finalized --- Agile Projects: Every Sprint: - If used, velocity is a local observation with no required stabilization point - Sprint Goal evidence reviewed without converting story completion into a universal percentage target - Retrospective action items addressed next sprint - Technical debt not accumulating (code quality stable) Every Month (Multiple Sprints): - Flow, forecast error, outcome, quality, and risk trends interpreted from stable local definitions; no fixed velocity band - Product Owner satisfied with prioritization - User feedback incorporated in next sprint - Release plan on track to MVP launch Before Release: - The authorized product/release scope and explicit exclusions are reconciled; a Sprint 0 backlog is not a fixed baseline - Acceptance evidence meets decision-specific coverage and severity criteria rather than a universal pass percentage - Performance/load testing passed - Release notes prepared, training complete ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-red-flags-when-methodology-is-wrong", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Red Flags: When Methodology is Wrong", "headingId": "chapter-11-project-management-and-pmp-frameworks-red-flags-when-methodology-is-wrong", "url": "#chapter-11-project-management-and-pmp-frameworks-red-flags-when-methodology-is-wrong", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Predictive-design Red Flags: - ✗ Requirements constantly changing → Reassess discovery, feedback, baseline, and change authority; consider adaptive or hybrid practices if they improve evidence without violating obligations - ✗ 10%+ rework late in project → Requirements were incomplete - ✗ Vendor missing deadlines regularly → Governance/accountability weak - ✗ Steering committee escalations 1/month → Execution struggling - ✗ Team says \"we're done, just waiting for testing\" → Testing not integrated Agile Red Flags: - ✗ Material flow or forecast deterioration → Verify definitions and investigate capacity, interruptions, dependencies, quality, work mix, morale, and scope as competing hypotheses - ✗ Product Owner absent → Decisions bottlenecked, team losing direction - ✗ Technical debt accumulating → Definition of Done too loose - ✗ Same bugs showing up each sprint → Not addressing root causes - ✗ Stakeholders surprised at sprint review → PO not communicating feedback Hybrid Red Flags: - ✗ Waterfall people complaining about lack of planning → Need to strengthen Phase 1 - ✗ Agile people frustrated by bureaucracy → Over-applying Waterfall controls - ✗ Scope is growing unchecked → Need change control even in Agile phases ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-why-this-matters-mental-models-project-wisdom", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Why This Matters: Mental Models & Project Wisdom", "headingId": "chapter-11-project-management-and-pmp-frameworks-why-this-matters-mental-models-project-wisdom", "url": "#chapter-11-project-management-and-pmp-frameworks-why-this-matters-mental-models-project-wisdom", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The contrasts below are teaching simplifications, not universal properties of “Waterfall” or “Agile.” Real delivery systems combine planning, feedback, assurance, flow, and governance in different ways. All cases and quantities in this section are constructed; they do not establish that a methodology caused an outcome." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-1-why-waterfall-works-predictable-sequential-dependencies", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "1. Why Waterfall Works: Predictable, Sequential Dependencies", "headingId": "chapter-11-project-management-and-pmp-frameworks-1-why-waterfall-works-predictable-sequential-dependencies", "url": "#chapter-11-project-management-and-pmp-frameworks-1-why-waterfall-works-predictable-sequential-dependencies", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A predictive sequence can be useful when dependencies and evidence justify committing detail early; it is not automatically optimal for an entire project. Predictability Through Planning: Predictive approaches frontload selected planning and baselines. That can improve coordination, but a plan does not create certainty about scope, duration, cost, regulation, or operating conditions. Sequential Dependencies: Some work has real sequencing constraints: a component may need to exist before it can be integrated or tested, and a manufactured item may need to exist before deployment. A predictive sequence is one way to coordinate that work; staged prototypes, reviews, simulations, and incremental testing can still reduce uncertainty. Example: Building a bridge may require predictive engineering, procurement, and assurance controls, while still benefiting from staged design reviews, prototypes, incremental testing, and governed learning: - Requirements: Load capacity, environmental conditions, regulatory approvals - Design: Engineering blueprints, stress analysis, materials selection - Construction: Foundation → Supports → Deck (must be sequential) - Testing: Load testing, safety inspections - Deployment: Open to traffic Physical construction constrains what can be changed cheaply after commitment, so design assurance, prototypes, staged approvals, and controlled field learning matter; that does not require pretending every design decision is final before evidence arrives. Why It Works: For projects where the cost of rework is high (construction, hardware, safety-critical systems), proportionate upfront planning and assurance can reduce avoidable changes; they do not remove the need for feedback or authorized adaptation. Why It Fails: When a predictive design delays credible feedback on uncertain requirements. If customer needs or solution mechanisms are not knowable upfront, late validation can produce rework; staged discovery and incremental evidence may reduce that risk. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-2-why-agile-works-learning-and-adaptation-under-uncertainty", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "2. Why Agile Works: Learning and Adaptation Under Uncertainty", "headingId": "chapter-11-project-management-and-pmp-frameworks-2-why-agile-works-learning-and-adaptation-under-uncertainty", "url": "#chapter-11-project-management-and-pmp-frameworks-2-why-agile-works-learning-and-adaptation-under-uncertainty", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Adaptive approaches use short feedback loops when needs or solutions are expected to evolve. Agile does not require two-week Sprints, and Scrum permits Sprints of one month or less. [BB-C11-S05] [BB-C11-S06] Rapid Feedback Loops: An adaptive team can deliver and inspect usable increments on a chosen cadence. Whether customers can safely use an increment and whether feedback identifies causal value depend on the product, evidence, and release controls. Embrace Change: Adaptive practice treats new evidence as a reason to inspect assumptions and revise authorized decisions. Predictive practice can also learn and change through controlled baselines, reviews, and change authority; neither label owns learning. Example: A startup building a mobile app uses Agile: - Sprint 1: Build login + basic dashboard (hypothesis: users need dashboards) - Sprint 2: User feedback: \"Dashboard is confusing, but we love the notifications\" - Sprint 3: Pivot: Simplify dashboard, enhance notifications - Sprint 4: User retention improves 40% In this constructed comparison, a long feedback cycle would have risked spending six months on the full app before discovering that users preferred simple notifications. Why It Works: For projects where customer needs are uncertain (new products, consumer apps, innovation), rapid feedback may reduce the risk of building the wrong thing; it does not guarantee product-market fit or causal learning. Why It Fails: Hard constraints do not disqualify adaptive practices. The team must make scope, quality, evidence, funding, deadline, and change authority explicit so adaptation does not conceal an infeasible commitment. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-3-why-hybrid-works-and-why-it-s-hard-combining-disciplines", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "3. Why Hybrid Works (and Why It's Hard): Combining Disciplines", "headingId": "chapter-11-project-management-and-pmp-frameworks-3-why-hybrid-works-and-why-it-s-hard-combining-disciplines", "url": "#chapter-11-project-management-and-pmp-frameworks-3-why-hybrid-works-and-why-it-s-hard-combining-disciplines", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Hybrid project management combines predictive and adaptive practices when their interfaces, authorities, evidence, and commitments are deliberately designed. It can be useful, but it is not automatically superior and requires balancing competing constraints. Structured Flexibility: One hybrid design might use predictive planning, procurement, architecture, or assurance controls alongside iterative delivery and feedback. The interface must state which scope, budget, quality, evidence, and authority commitments are fixed, negotiable, or revisable. Example: An enterprise CRM implementation uses Hybrid: - Waterfall Phase 1: Requirements gathering (3 months, comprehensive) - Waterfall Phase 2: Architecture design (2 months, validated with vendors) - Agile Phase 3: Development (6 months, 2-week sprints for each module) - Agile Phase 4: Testing & iteration (3 months, continuous UAT feedback) - Waterfall Phase 5: Deployment (1 month, big bang go-live) Architecture decisions may be controlled through explicit review and change authority while feature details remain open to user-testing evidence; neither label alone determines the decision rights. Why It's Hard: Predictive and adaptive approaches differ in commitment timing and feedback design; neither is accurately summarized as “plan everything” or “planning is waste.” [BB-C11-S01] [BB-C11-S06] Hybrid requires the team to make interfaces explicit: which decisions are controlled, which can change, who decides, what evidence is needed, and how work crosses boundaries. Ambiguity—not the coexistence of practices itself—creates confusion. Why It Works: For complex projects where assurance or contractual controls coexist with uncertain user needs, a hybrid design may balance compliance, learning, and delivery if the evidence and authorities are explicit. Why It Fails: When teams combine incompatible commitments without decision rights: for example, demanding a fixed scope and date while accepting unbounded change without feasibility checks. The remedy is to make tradeoffs, baselines, and escalation explicit. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-4-why-critical-path-matters-resource-constrained-execution", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "4. Why Critical Path Matters: Resource-Constrained Execution", "headingId": "chapter-11-project-management-and-pmp-frameworks-4-why-critical-path-matters-resource-constrained-execution", "url": "#chapter-11-project-management-and-pmp-frameworks-4-why-critical-path-matters-resource-constrained-execution", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Critical Path Method (CPM) identifies the longest sequence of dependent tasks—the bottleneck determining project duration. Understanding this matters because resources are finite. Bottleneck Logic: A project with 100 tasks doesn't mean all 100 matter equally. If 95 tasks have slack (can be delayed without impacting the project), only 5 tasks on the critical path actually determine when you finish. Resource Allocation: CPM reveals where to focus: \"Add resources to critical path tasks (shortens timeline). Adding resources to non-critical tasks wastes money (doesn't shorten timeline).\" Example: A product launch has these paths: - Path A (Product development): 6 months (critical path) - Path B (Marketing campaign): 3 months (3 months slack) - Path C (Sales training): 2 months (4 months slack) Adding resources to Sales training (Path C) doesn't accelerate the launch (launch depends on Product development finishing). Adding resources to Product development shortens the critical path by 1 month, enabling a 5-month launch. Why It Works: CPM prevents waste. Without it, managers add resources everywhere (\"we need to go faster!\"), diluting impact. CPM focuses resources on the bottleneck. Why It Fails: When priorities, dependencies, or evidence shift dynamically. In iterative work, the modeled dependency network can change frequently, so CPM assumptions and forecasts need regular review rather than being discarded by method label. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-composite-failure-examples-when-project-methodologies-failed", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite Failure Examples: When Project Methodologies Failed", "headingId": "chapter-11-project-management-and-pmp-frameworks-composite-failure-examples-when-project-methodologies-failed", "url": "#chapter-11-project-management-and-pmp-frameworks-composite-failure-examples-when-project-methodologies-failed", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following scenarios are composite teaching examples, not named empirical case studies." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-case-1-healthcare-it-project-failure-methodology-mismatch", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Case 1: Healthcare IT Project Failure - Methodology Mismatch", "headingId": "chapter-11-project-management-and-pmp-frameworks-case-1-healthcare-it-project-failure-methodology-mismatch", "url": "#chapter-11-project-management-and-pmp-frameworks-case-1-healthcare-it-project-failure-methodology-mismatch", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Situation: A hospital system contracted a $50M electronic health record (EHR) implementation. The vendor used Waterfall: 6-month requirements phase, 12-month development phase, 3-month testing, 1-month deployment. Total timeline: 22 months. What Went Wrong: Month 6: Requirements completed and frozen (Waterfall phase gate). Month 18: Development completed, testing begins. Month 18 discovery: Clinical workflows had changed significantly due to new regulatory requirements (meaningful use standards). The EHR, built to old requirements, was obsolete before deployment. Hospital requested changes. Vendor response: \"That's a change order. Scope was frozen at Month 6. Changes require $15M and 12-month delay.\" Hospital faced a choice: Deploy an obsolete system or pay $65M total and delay 12 months. They deployed the obsolete system. Physician adoption: 40% (instead of target 90%). ROI: Negative. Project deemed a failure. What Methodology Failed: This constructed design treated requirements as stable despite a changing healthcare context. A 22-month timeline meant the requirements were 16 months stale by deployment. What Would Have Worked: Agile with phased rollout: - Month 1-3: Build core EHR (patient records, basic workflows) - Month 4: Deploy to 1 department (Cardiology), gather feedback - Month 5-6: Iterate based on feedback and regulatory changes - Month 7: Expand to 3 more departments - Month 12: Enterprise-wide deployment Agile's frequent iterations (every 2 weeks) would have incorporated regulatory changes as they emerged, preventing obsolescence. Lesson: In changing environments, shorten evidence and decision cycles while preserving required assurance and traceability. The appropriate mix is a design decision, not a categorical ban on predictive practice. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-case-2-software-project-death-march-waterfall-applied-to-uncertain-work", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Case 2: Software Project Death March - Waterfall Applied to Uncertain Work", "headingId": "chapter-11-project-management-and-pmp-frameworks-case-2-software-project-death-march-waterfall-applied-to-uncertain-work", "url": "#chapter-11-project-management-and-pmp-frameworks-case-2-software-project-death-march-waterfall-applied-to-uncertain-work", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Situation: A software company committed to a fixed-price, fixed-scope contract to build a custom platform for a client. Contract terms: $5M, 12-month delivery, 200 features specified in a 300-page requirements document. The company used Waterfall: - Months 1-3: Requirements review and design - Months 4-10: Development - Months 11-12: Testing and deployment What Went Wrong: Month 4: Development started. Developers discovered 30% of requirements were technically infeasible (client asked for features that conflicted with each other or violated technical constraints). Company faced a choice: 1. Tell client \"your requirements are infeasible\" → Client lawsuit for breach of contract 2. Build what's feasible and hope client accepts → Risk client rejection at delivery They chose option 2. Month 10: Integration testing revealed the 200 features didn't work together (modularity assumed in requirements didn't exist in implementation). Month 12: Delivery deadline. System was 60% complete. Company asked for extension. Client refused (contract specified 12 months). Company faced penalties: $1M/month for late delivery. Outcome: Company worked weekends and nights (death march) to deliver something. Month 15: Deployed a broken system (technical debt, poor quality). Client sued for non-performance. Settlement: $8M (original contract + $3M damages). Company lost money and reputation. What Methodology Failed: The design's requirements freeze and feasibility gaps created an impossible contract. The client specified what it wanted without understanding feasibility, and the vendor committed without validating it. Both parties treated requirements as correct without adequate evidence. What Would Have Worked: Agile with Time & Materials contract: - Month 1: Build 20 most critical features (MVP) - Month 2: Client tests MVP, refines priorities - Months 3-12: Iterative development of next-priority features - Every 2 weeks: Client sees working software, provides feedback - Month 12: Deliver 150 features that actually work (vs. 200 that don't) Earlier technical and user evidence could have surfaced infeasible requirements sooner, but the constructed case does not prove that a branded method would have done so. Lesson: For complex uncertain work, align contract structure, discovery, acceptance, incentives, change, audit, and termination rights with the uncertainty. Fixed-price and time-and-materials contracts each allocate risk and incentives differently; qualified procurement and counsel should design the arrangement. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-case-3-agile-chaos-applied-without-discipline-to-complex-delivery", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Case 3: Agile Chaos - Applied Without Discipline to Complex Delivery", "headingId": "chapter-11-project-management-and-pmp-frameworks-case-3-agile-chaos-applied-without-discipline-to-complex-delivery", "url": "#chapter-11-project-management-and-pmp-frameworks-case-3-agile-chaos-applied-without-discipline-to-complex-delivery", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Situation: A financial services firm adopted Agile for a regulatory compliance project (implementing new anti-money-laundering rules). The project had hard constraints: - Scope: Fixed (regulators specified requirements) - Deadline: Fixed (regulatory deadline 18 months away) - Budget: Fixed ($20M approved by board) The project team ran 2-week sprints. After 12 months and $15M spent: - Delivered: 40% of required features - Remaining: 60% of features, $5M budget, 6 months deadline - Math: Impossible (current pace: 40% in 12 months = 100% in 30 months, not 18) What Went Wrong: Agile's flexibility enabled scope creep: - Sprint 5: Product owner added 10 new user stories (not in original scope) - Sprint 10: Team refactored code for better architecture (didn't deliver new features) - Sprint 15: Product owner reprioritized backlog, deprioritizing 20% of regulatory features (still required by law, but pushed to \"later\") No one tracked: \"Are we on pace to finish all required features by the deadline?\" Agile's sprint-by-sprint focus obscured long-term progress. Month 12: Steering committee asked: \"Will we make the deadline?\" PM answered: \"We're doing Agile, so we're flexible.\" Steering committee: \"The regulatory deadline isn't flexible.\" Outcome: Company hired external consultants (additional $10M), worked weekends, delivered minimum viable compliance by deadline. Total cost: $30M (vs. $20M budget). Quality: Poor (technical debt accumulated from rushing). Post-launch: 18 months of bug fixes. What Methodology Failed: Adaptive delivery does not assume that legal scope is flexible. The constructed team failed to map obligations, evidence, capacity, deadline, and change authority into its delivery design. What Would Have Worked: Hybrid approach: - Waterfall Phase 1 (Months 1-2): Requirements analysis (map all regulatory requirements to features) - Waterfall Phase 2 (Month 3): Baseline plan (how much can we deliver per sprint to finish in 18 months?) - Agile Phase 3 (Months 4-16): 2-week sprints, but EVERY sprint must deliver X features (pace discipline) - Waterfall Phase 4 (Months 17-18): Integration testing and deployment (no new features) This constructed hybrid keeps iterative delivery while adding explicit feasibility, baseline, and assurance controls; it still needs rolling forecasts and authorized tradeoffs. Lesson: When scope, deadline, and budget are all constrained, test feasibility and explicitly govern tradeoffs. Baselines, rolling forecasts, incremental delivery, and adaptive planning can coexist; none guarantees predictability. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-1-predictive-vs-adaptive-project-management", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "1. Predictive vs. Adaptive Project Management", "headingId": "chapter-11-project-management-and-pmp-frameworks-1-predictive-vs-adaptive-project-management", "url": "#chapter-11-project-management-and-pmp-frameworks-1-predictive-vs-adaptive-project-management", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Predictive approaches: Use greater upfront and rolling planning where dependencies, procurement, assurance, or commitments justify it. Baselines support comparison, but forecasts and plans change through authority and materiality-appropriate control. Philosophy: Planning can reduce some uncertainty and coordinate commitments; it does not make the future knowable. Strengths: - Predictability: Stakeholders know what to expect - Accountability: Baseline plan enables variance tracking (on-time, on-budget?) - Risk management: Comprehensive risk analysis upfront Weaknesses: - Rigid: Hard to adapt when reality diverges from plan - Late validation: Deliver at the end, discover issues late - Assumes stable requirements: Fails when requirements change Potential fit signals, not automatic selections: - Construction, infrastructure, manufacturing, or other work with material physical dependencies may benefit from predictive planning and assurance; incremental validation can still be useful. - Regulatory work may require traceability, evidence, approval, and release controls; those controls do not by themselves prescribe a predictive-only delivery system. - Fixed-price contracts allocate commercial risk and change rights; procurement and governance design should determine how planning, discovery, acceptance, and change interact. --- Adaptive (Agile, Scrum): Plan iteratively. Define vision and high-level goals, while details emerge through feedback and evidence. Scope, time, budget, quality, and authority constraints can be governed in different combinations; adaptation does not mean unbounded scope. Philosophy: \"The future is unknowable. Adaptation reduces risk.\" Strengths: - Flexibility: Respond to changing requirements - Early validation: When Scrum applies, inspect a usable Increment on the chosen Sprint cadence; other adaptive teams may use different increments and release controls - Customer collaboration: Continuous feedback loops Weaknesses: - Unpredictability: Hard to forecast final scope or cost - Scope creep risk: Without discipline, teams iterate endlessly - Requires decision access: Product Owner availability must fit the product decisions and cadence; Scrum does not prescribe weekly availability Potential fit signals, not automatic selections: - Software or service work where requirements or solution mechanisms are expected to evolve may benefit from short feedback cycles. - Innovation work may benefit from experiments and staged commitments when learning value justifies the cost. - Startups may use adaptive practices, but funding, safety, contractual, technical, and operating constraints still require explicit governance. --- Hybrid (one possible design): Combine predictive and adaptive practices only where the interfaces, authority, evidence, and tradeoffs are explicit: - Some scope, timeline, budget, architecture, procurement, assurance, or release commitments may be baselined. - Other details may be discovered and delivered iteratively within stated constraints. Example: - Predictive: \"We will implement a CRM system in 12 months for $2M\" - Adaptive: \"We'll deliver via 24 sprints. Each sprint, we'll refine features based on user feedback\" ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-2-command-and-control-vs-self-organizing-teams", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "2. Command-and-Control vs. Self-Organizing Teams", "headingId": "chapter-11-project-management-and-pmp-frameworks-2-command-and-control-vs-self-organizing-teams", "url": "#chapter-11-project-management-and-pmp-frameworks-2-command-and-control-vs-self-organizing-teams", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Command-and-Control (a centralized decision pattern): An authorized manager or governance body assigns or approves work, tracks progress, and makes selected decisions; the degree of team discretion depends on capability, consequence, and decision rights. Philosophy: \"Centralized control ensures coordination.\" Strengths: - Clear accountability (PM is accountable) - Efficiency (no time wasted on consensus) - Works with junior teams (don't require self-direction) Weaknesses: - Bottleneck (all decisions go through PM) - Low engagement (team feels \"managed,\" not empowered) - Limited innovation (team doesn't challenge assumptions) Potential fit signals, not automatic selections: - Time-critical incidents or decisions where a clear incident commander or authority is required. - Work with limited capability or unclear decision rights where temporary structure, coaching, and escalation may reduce risk. - High-consequence work where explicit approvals and independent assurance are needed; centralized control is not a substitute for expertise or evidence. --- Self-managing teams (a team-discretion pattern): The team decides how to accomplish an agreed goal within its authority and constraints. In Scrum, the Scrum Master supports Scrum and team effectiveness; the role is not automatically a project manager and does not remove product, technical, safety, or governance accountability. Philosophy: \"Teams closest to the work make better decisions.\" Strengths: - Speed (no bottleneck; decisions made locally) - Engagement (team owns outcomes) - Innovation (team challenges assumptions) Weaknesses: - Requires maturity (doesn't work with junior teams) - Coordination challenges (multiple teams may work at cross-purposes) - Accountability diffusion (\"team\" accountability = no one accountable) Potential fit signals, not automatic selections: - Teams with the capability, access, psychological safety, and authority to make the relevant decisions. - Work where local expertise and feedback improve solution quality or learning. - Stable or changing teams alike, provided coordination, escalation, accountability, and onboarding are deliberately designed. --- Hybrid (Servant Leadership): PM sets vision and removes blockers (servant leadership), but team makes execution decisions (self-organizing). Example: - PM: \"Our sprint goal is to enable user login. What blockers do you need removed?\" - Team: \"We need API access to authentication service.\" - PM: \"I'll handle that. You decide how to implement the login flow.\" ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-3-phases-vs-sprints-when-to-use-each", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "3. Phases vs. Sprints (When to Use Each)", "headingId": "chapter-11-project-management-and-pmp-frameworks-3-phases-vs-sprints-when-to-use-each", "url": "#chapter-11-project-management-and-pmp-frameworks-3-phases-vs-sprints-when-to-use-each", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Phases (a predictive delivery pattern): Sequential or partially overlapping stages with formal gates. Use a gate when the evidence and authority justify it; phases need not eliminate iteration or staged validation. Phases: Requirements → Design → Build → Test → Deploy Strengths: - Clear milestones (know when each phase is \"done\") - Quality gates (don't proceed until phase is validated) - Works for sequential work (can't test before building) Weaknesses: - Long cycle times (months between validation points) - Late feedback (discover issues in Testing phase, too late to fix cheaply) - Assumes linear progress (doesn't accommodate iteration) Potential fit signals, not automatic selections: - Hardware, infrastructure, or other work with physical dependencies may need staged engineering, procurement, testing, and release controls. - Compliance work may need formal evidence and approval gates, which can coexist with iterative design or implementation. - Large-scale delivery may use phases for coordination while running incremental validation inside them. --- Sprints (an adaptive delivery pattern): Fixed-duration iterations; two weeks is a constructed example, while Scrum permits a Sprint of one month or less. A Sprint aims to produce a usable Increment when Scrum is being used. Sprint Cycle: Plan → Build → Review → Retrospective → Repeat Strengths: - Rapid feedback (validate every 2 weeks) - Flexibility (can pivot based on sprint learnings) - Momentum (frequent \"wins\" keep morale high) Weaknesses: - Fragmentation risk (focus on sprint goals, lose sight of big picture) - Overhead (sprint planning, reviews, retros take meaningful team time) - Hard to estimate total duration (how many sprints to \"done\"?) Potential fit signals, not automatic selections: - Software or customer-facing work where frequent feedback can change priorities or solution detail. - Continuous-delivery environments where release, quality, security, and operational controls support small increments. - Any context in which the cadence improves evidence and decision quality; the cadence must still fit the work and its obligations. --- Hybrid (Phased Rollout with Agile Execution): One possible design uses phases for high-level milestones and iterative delivery within phases; the interfaces and release authority must be explicit. Example: - Phase 1: Requirements (3 months, Agile sprints to iterate on requirements) - Phase 2: Build (6 months, Agile sprints to deliver features incrementally) - Phase 3: Deploy (2 months, Agile sprints for rollout by region) ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-context-dependent-delivery-design", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Context-Dependent Delivery Design", "headingId": "chapter-11-project-management-and-pmp-frameworks-context-dependent-delivery-design", "url": "#chapter-11-project-management-and-pmp-frameworks-context-dependent-delivery-design", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Organization labels such as “startup,” “scale-up,” and “enterprise” do not prescribe Agile, Waterfall, sprint length, documentation volume, governance cadence, or delivery duration. Tailor the delivery system to the work and its obligations. | Context signal | Questions for delivery design | |---|---| | Uncertainty and learning | Which customer needs, mechanisms, estimates, and dependencies remain hypotheses? How quickly can credible evidence arrive? | | Consequence and assurance | Which safety, regulatory, contractual, security, quality, or audit evidence is mandatory? | | Coordination | How many teams, suppliers, systems, jurisdictions, and decision authorities interact? | | Reversibility | Which decisions can be tested cheaply, and which require staged commitment or formal approval? | | Operating capacity | What planning, facilitation, engineering, testing, change, and support capacity actually exists? | | Stakeholder and user effects | Who bears risk, who has decision rights, and what participation or accessibility is required? | A small uncertain product team might use short experiments and lightweight artifacts; a similarly sized medical-device team may require substantial traceability and assurance. A large organization might use adaptive product discovery in one workstream and predictive procurement or migration controls in another. These are constructed contrasts, not maturity stages or duration benchmarks. Select and revise practices from observed forecast error, flow, defect and incident evidence, learning value, control effectiveness, stakeholder impact, and delivery outcomes. Tool choice, meeting frequency, page count, and organization stage are not proxies for rigor. --- Tailoring dimensions: | Dimension | Questions to resolve | |-----------|----------------------| | Uncertainty and learning | Which needs, solution mechanisms, estimates, and dependencies can change, and how quickly can evidence arrive? | | Assurance and obligations | Which safety, regulatory, contract, quality, audit, or traceability evidence is required? | | Coordination | How many teams, suppliers, systems, jurisdictions, and decision authorities interact? | | Cadence and planning horizon | What near-term commitment, rolling forecast, milestone, and long-horizon option information is useful? | | Documentation | Which artifact changes a decision, enables execution, or proves compliance? Page count and tool choice are not maturity measures. | | Governance | Which decisions are delegated, collective, regulated, or reserved, and what evidence and escalation do they require? | ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-operating-manual-your-project-execution-playbook", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Operating Manual: Your Project Execution Playbook", "headingId": "chapter-11-project-management-and-pmp-frameworks-operating-manual-your-project-execution-playbook", "url": "#chapter-11-project-management-and-pmp-frameworks-operating-manual-your-project-execution-playbook", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed-policy boundary: All hours, durations, team sizes, thresholds, budgets, meeting cadences, status labels, and escalation values in this operating manual are fictional teaching assumptions. Replace them with approved project-specific evidence, contract, safety, regulatory, accessibility, workforce, procurement, and governance constraints before use. This operating manual contains constructed sample cadences, roles, thresholds, hours, durations, budgets, statuses, and escalation triggers. None is a benchmark or default. Replace every sample with a named owner, rationale, applicable governance, evidence source, tolerance, and review rule. The two-track presentation is a teaching convenience; a real delivery design may combine or omit practices." }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-delivery-system-tailoring", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Delivery-System Tailoring", "headingId": "chapter-11-project-management-and-pmp-frameworks-delivery-system-tailoring", "url": "#chapter-11-project-management-and-pmp-frameworks-delivery-system-tailoring", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Do not select a method from a rigid Waterfall/Agile taxonomy. Tailor planning horizon, feedback, sequencing, flow, documentation, assurance, procurement, funding, release, and change authority independently. Predictive and adaptive practices can coexist, and regulation or fixed-price contracting does not prescribe one method. ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-phase-1-initiation-weeks-1-2-40-60-hours", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 1: Initiation (Weeks 1-2, 40-60 hours)", "headingId": "chapter-11-project-management-and-pmp-frameworks-phase-1-initiation-weeks-1-2-40-60-hours", "url": "#chapter-11-project-management-and-pmp-frameworks-phase-1-initiation-weeks-1-2-40-60-hours", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Define project scope, secure sponsorship, and obtain formal approval to proceed. Activities: Week 1: Project Charter Development (20-30 hours) - Business Case (8 hours): - Problem statement: What issue are we solving? - Proposed solution: High-level approach - Benefits quantification: Revenue impact, cost savings, efficiency gains - Investment required: Budget estimate with stated confidence range - Alternatives considered: Why is this the best option? - Output: Business case document (3-5 pages) - Stakeholder Identification (4 hours): - List all affected parties (typically 15-30 stakeholders) - Classify by the constructed power/interest aid in Framework 6; do not treat the categories as a universal stakeholder standard - Identify sponsor (executive accountable for success) - Identify steering committee (3-7 senior stakeholders for oversight) - Output: Stakeholder register with roles - High-Level Scope Definition (4 hours): - What IS included (in-scope): 5-10 major deliverables - What is NOT included (out-of-scope): 5-10 exclusions - Assumptions: What we're assuming to be true - Constraints: Budget limits, timeline deadlines, resource caps - Output: Scope statement (1-2 pages) - Success Criteria (4 hours): - Define \"done\": What does success look like? - Measurable outcomes: KPIs, metrics, milestones - Acceptance criteria: How will sponsor approve? - Example: \"CRM system deployed to 500 users with <5% critical bugs and <2 hour average response time\" - Output: Success criteria checklist Week 2: Charter Approval & Kickoff (20-30 hours) - Project Charter Finalization (8 hours): - Consolidate: Business case + scope + success criteria + stakeholders - Add: High-level timeline (phases with dates), budget confidence range, major risks - Format: 5-10 page document - Review with sponsor and key stakeholders - Iterate based on feedback - Approval & Sign-Off (4 hours): - Present charter to sponsor/steering committee - Secure formal approval (signature or email confirmation) - Allocate initial budget for the planning phase - Assign project manager (if not already assigned) - Project Kickoff Meeting (2-3 hours): - Attendees: Sponsor, PM, core team (5-15 people) - Agenda: - Present charter (10 min) - Introduce team and roles (10 min) - Review timeline and next steps (10 min) - Q&A (15 min) - Team building activity (optional, 30 min) - Output: Meeting minutes, action items Outputs (Phase 1): - Approved project charter - Stakeholder register - Sponsor commitment and budget allocation - Core team assembled Decision Gate: Proceed to Planning? - GREEN: Charter approved, sponsor committed, budget secured → Proceed to Phase 2 - YELLOW: Minor scope adjustments needed → Refine and re-approve within 1 week - RED: Business case weak or sponsor unavailable → STOP or revisit in 3-6 months Red Flags: - Sponsor not engaged (skips meetings, delays approval) → Escalate or pause - Scope undefined (\"improve customer experience\") → Too vague; define measurables - Budget unavailable → Cannot proceed without funding commitment - Stakeholders misaligned on goals → Facilitate alignment session (Chapter 9) Resource Requirements: - Project Manager: 40-60 hours (full-time for 1-2 weeks) - Sponsor: 4-6 hours (charter review, approval meeting) - Stakeholders: 10-15 hours total (distributed) ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-phase-2-planning-weeks-3-8-200-300-hours", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 2: Planning (Weeks 3-8, 200-300 hours)", "headingId": "chapter-11-project-management-and-pmp-frameworks-phase-2-planning-weeks-3-8-200-300-hours", "url": "#chapter-11-project-management-and-pmp-frameworks-phase-2-planning-weeks-3-8-200-300-hours", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Develop detailed project plan with scope, schedule, budget, risks, and quality standards. Week 3-4: Requirements & Scope Planning (60-80 hours) - Requirements Gathering (30-40 hours): - Stakeholder interviews (10-15 people, 1-2 hours each): \"What do you need from this project?\" - Workshops (2-3 sessions, 2-4 hours each): Facilitate group requirements definition - Document review: Existing processes, systems, contracts - Requirements documentation: - Functional requirements: What system/solution must DO (50-200 items typical) - Non-functional requirements: Performance, security, usability standards (10-30 items) - Format: Requirements traceability matrix (Excel or requirements tool) - Prioritization: Must-have (MVP), Should-have (Phase 1), Could-have (Phase 2), Won't-have - Output: Requirements specification document (20-100 pages depending on complexity) - Work Breakdown Structure (WBS) (20-30 hours): - Decompose project into hierarchical structure: - Level 1: Major phases (Initiation, Planning, Execution, etc.) - Level 2: Deliverables per phase (Requirements doc, Design spec, Build, Test, Deploy) - Level 3: Work packages sized to support ownership, estimation, control, and progress visibility - Rules: cover the defined project scope under the WBS 100% rule; do not require mutually exclusive work or a universal 8–80-hour package size. [BB-C11-S02] - Tool: Microsoft Project, Excel, or Lucidchart - Output: WBS diagram (visual) + WBS dictionary (descriptions of each element) - Scope Baseline (10 hours): - Formal documentation of approved scope - Includes: Requirements spec + WBS + Scope statement from Phase 1 - Becomes basis for scope change control - Route changes by delegated authority, materiality, contract, safety, regulation, baseline impact, and evidence; not every change requires formal review - Output: Scope baseline document (approved by sponsor) Week 5-6: Schedule & Budget Planning (80-120 hours) - Activity Sequencing & Duration Estimation (40-60 hours): - List all tasks from WBS (typically 50-500 tasks depending on project size) - Sequence: Which tasks depend on others? (predecessors/successors) - Estimate duration: Use historical data, expert judgment, or three-point estimates (optimistic/most likely/pessimistic) - Identify critical path: Longest sequence of dependent tasks (determines minimum project duration) - Tool: Microsoft Project, Smartsheet, or Gantt chart tool - Add buffer based on uncertainty and risk exposure - Output: Project schedule (Gantt chart with dependencies) - Resource Planning (20-30 hours): - Identify roles needed: PM, business analyst, developers, testers, etc. - Estimate effort per role per task - Level resources: Smooth workload to avoid over-allocation (e.g., developer not assigned 80 hours/week) - Identify resource constraints: \"Only 2 developers available; others on different projects\" - Output: Resource allocation matrix (who does what, when) - Budget Development (20-30 hours): - Calculate costs: - Labor: Hours × hourly rate (or FTE allocation) - Materials/equipment: Hardware, software licenses, facilities - External vendors: Contractors, consultants, outsourced work - Contingency based on uncertainty and risk exposure - Create budget by phase and by category (labor, materials, vendors) - Example waterfall project budget: 10% initiation, 20% planning, 50% execution, 15% testing/QA, 5% closure - Secure budget approval from sponsor/finance - Output: Project budget (detailed breakdown with approval) Week 7-8: Risk, Quality & Communication Planning (60-100 hours) - Risk Management Plan (20-30 hours): - Risk identification workshop (2-3 hours with team + stakeholders): Brainstorm 20-50 risks - Risk assessment: - Probability and impact: Use a defined local ordinal scale; this operating example may use the same 1–5 scale as Framework 5, but the labels and anchors must be approved for the project - Score: Probability × Impact only as a local ordinal triage aid, not a quantitative exposure measure - Prioritize: Record the scale, owner, trigger, evidence, and review rule; do not present a numerical cutoff as a universal threshold - Mitigation strategies for top 10 risks: - Avoid: Eliminate risk (e.g., use proven technology vs. experimental) - Mitigate: Reduce probability or impact (e.g., add testing to reduce defect risk) - Transfer: Shift to vendor/insurance (e.g., vendor guarantees uptime) - Accept: Risk acceptable; document decision - Output: Risk register (living document, updated weekly) - Quality Management Plan (15-20 hours): - Define quality standards: What level of quality is acceptable? - Example: \"Software must pass 95% of test cases with zero P0 bugs before go-live\" - Quality assurance activities: Reviews, inspections, audits - Quality control measures: Testing, validation, acceptance criteria - Tools: Defect tracking (Jira), code reviews, automated testing - Output: Quality plan (how quality will be ensured and measured) - Communication Plan (15-20 hours): - Stakeholder communication matrix: | Stakeholder Group | Frequency | Medium | Content | Owner | |-------------------|-----------|--------|---------|-------| | Sponsor | Weekly | Email | Status summary (1 page) | PM | | Steering Committee | Monthly | Meeting | Detailed review + decisions | PM | | Project Team | Daily | Standup | Progress, blockers | PM/Team Leads | | End Users | Bi-weekly | Email | Updates on progress, upcoming changes | PM | - Escalation protocol: When to escalate, to whom - Reporting templates: Status reports, dashboards, presentations - Output: Communication plan document - Procurement Plan (if applicable) (10-15 hours): - Identify what needs to be procured (software, hardware, consulting services) - Vendor selection criteria and process - Contract types (fixed-price, time-and-materials, etc.) - Output: Procurement plan (if vendors involved) Outputs (Phase 2): - Requirements specification (approved) - WBS and scope baseline - Project schedule (Gantt chart with critical path) - Resource plan and budget (approved) - Risk register (top 10 risks with mitigations) - Quality plan - Communication plan Decision Gate: Proceed to Execution? - GREEN: Plan approved, resources committed, risks acceptable → Proceed to Phase 3 - YELLOW: Plan needs refinement (schedule/budget adjustments) → Revise and re-approve within 1-2 weeks - RED: Plan not viable (timeline too aggressive, budget insufficient, risks too high) → STOP or re-scope Red Flags: - Schedule shows critical path 2× sponsor expectation → Reset expectations or add resources - Budget 30% higher than charter estimate → Re-validate business case - Top risks unmitigatable → May not be feasible; consider alternative approach - Team not aligned on plan → Facilitate planning workshop to build consensus Resource Requirements: - Project Manager: 200-300 hours (full-time for 6 weeks) - Business Analyst: 60-100 hours (requirements gathering, documentation) - Team Leads: 40-60 hours each (3-5 leads for different workstreams) - Stakeholders: 30-50 hours total (interviews, reviews, approvals) Contingency Triggers: - If planning extends beyond 8 weeks → Move to execution with rolling wave planning (detail only next phase) - If requirements unclear → Run additional discovery; may extend planning 2-4 weeks - If budget cuts forced → Reduce scope (descope should-haves and could-haves) or extend timeline ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-phase-3-execution-variable-3-12-months-depending-on-project", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 3: Execution (Variable, 3-12 months depending on project)", "headingId": "chapter-11-project-management-and-pmp-frameworks-phase-3-execution-variable-3-12-months-depending-on-project", "url": "#chapter-11-project-management-and-pmp-frameworks-phase-3-execution-variable-3-12-months-depending-on-project", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Execute the work defined in the plan; deliver project deliverables per schedule. Execution Cadence (Ongoing) Daily Activities (15-30 min/day): - Daily standup (if team co-located or on video): - 3 questions per person: - What did you complete yesterday? - What will you complete today? - Any blockers or help needed? - PM notes blockers and resolves outside meeting - Keep to 15 min max (5-10 people) Weekly Activities (4-6 hours/week): - Team sync (1-2 hours): - Review progress vs. schedule - Identify slippage: Any tasks behind? - Adjust plan if needed (re-sequence, add resources) - Review upcoming milestones - Output: Updated schedule, action items - Status reporting (2-3 hours): - Collect status from team leads - Update project dashboards: - Schedule health: On track / At risk / Behind - Budget health: Within budget / At risk / Over budget - Scope health: No changes / Minor changes / Major changes - Risk status: Top 3 active risks - Distribute weekly status email to stakeholders - Format: 1-page summary with RAG (Red/Amber/Green) status - Risk review (1 hour): - Review risk register - Update probabilities and impacts based on new information - Identify new risks - Escalate risks that meet the project's defined priority, trigger, severity, authority, or evidence rule; a score ≥6 is only an illustrative local cutoff if explicitly approved - Output: Updated risk register Monthly Activities (8-12 hours/month): - Steering Committee Meeting (2-3 hours): - Attendees: Sponsor, steering committee (3-7 executives), PM, key team leads - Agenda: - Progress update (10 min): Milestones achieved, upcoming milestones - Budget review (10 min): Spend vs. plan, forecast to complete - Decisions needed (20-30 min): Scope changes, resource requests, issue escalations - Risk review (10 min): Top 3-5 risks and mitigations - Q&A (10-15 min) - Output: Meeting minutes, decisions documented, action items - Change Control Board (as needed, 1-2 hours per request): - When change requests arise (scope additions, deletions, modifications): - Evaluate impact: Schedule (days delayed), budget ($cost increase), quality (risks introduced) - Present to sponsor/steering committee - Decision: Approve, reject, or defer - If approved: Update scope baseline, schedule, budget - Document all changes (change log) - Quality Reviews (variable): - Code reviews (for software): Ongoing, peer reviews - Design reviews: Architecture/design sign-offs before build - Testing/QA: Unit testing, integration testing, user acceptance testing (UAT) - Inspections: Review deliverables against acceptance criteria - Defect tracking: Log bugs, prioritize (P0 = critical, P1 = major, P2 = minor), fix - Target: Zero P0 defects before go-live; 10% → Escalate; crash schedule (add resources, work overtime), reduce scope, or extend deadline - Budget overrun 10% → Investigate root cause; may need scope reduction or additional funding - Quality evidence breaches the authorized severity/exposure tolerance → investigate mechanisms and compare process, design, testing, scope, and release responses - Team turnover 20% → Knowledge loss risk; cross-train and document - Scope creep 15% → Enforce change control; push back on unapproved changes - Stakeholder disengagement (missing meetings, not responding) → Escalate to sponsor Resource Requirements (example for 6-month execution): - Project Manager: 960 hours (full-time) - Business Analyst: 400-600 hours - Developers/Builders: 2,000-5,000 hours (varies by team size: 3-10 people) - Testers: 400-800 hours - Training/Change Management: 200-400 hours - Sponsor/Steering Committee: 30-50 hours (distributed) Contingency Triggers: - If project 20%+ over budget → Formal review with sponsor; options: add funds, reduce scope, or cancel - If critical team member leaves → Immediate backfill; knowledge transfer sessions - If technology choice fails → Pivot to alternative technology; may extend timeline 2-4 months - If business priorities shift → Re-validate project relevance; may pause or cancel ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-phase-4-monitoring-controlling-ongoing-parallel-to-execution", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 4: Monitoring & Controlling (Ongoing, parallel to Execution)", "headingId": "chapter-11-project-management-and-pmp-frameworks-phase-4-monitoring-controlling-ongoing-parallel-to-execution", "url": "#chapter-11-project-management-and-pmp-frameworks-phase-4-monitoring-controlling-ongoing-parallel-to-execution", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Track progress, manage changes, ensure quality, and keep project on track. Weekly Monitoring (3-5 hours/week): - Earned Value Management (EVM) (1-2 hours): - Track 3 key metrics: - Planned Value (PV): How much work should be done by now (per schedule) - Earned Value (EV): How much work is actually done - Actual Cost (AC): How much has been spent - Calculate variances: - Schedule Variance (SV) = EV - PV (negative = behind schedule) - Cost Variance (CV) = EV - AC (negative = over budget) - Calculate indices: - Schedule Performance Index (SPI) = EV / PV ( 10%: - Root cause analysis: Why did variance occur? - Corrective action: What will be done to get back on track? - Impact assessment: Does this affect downstream tasks? - Document in variance memo - Present to steering committee for major variances - Stakeholder Engagement Review (1 hour): - Assess stakeholder satisfaction: - Are stakeholders engaged? (attending meetings, responding to requests) - Are there conflicts or concerns? (proactively address) - Adjust communication plan if needed (increase frequency, change format) Outputs (Phase 4): - Weekly EVM dashboards - Weekly status reports (1 page) - Monthly performance reports (3-5 pages) - Updated schedule, budget, risk register, issue log - Change requests evaluated and approved/rejected Red Flags (constructed examples, not universal thresholds): - If the project's approved SPI or CPI alert rule is breached for the defined review period, validate the data and assumptions, investigate drivers, and route a response through the authorized owner; 2 consecutive weeks is only a local teaching example. - Critical path delayed 2 weeks → Risk of missing deadline; crash or fast-track needed - Burn rate 20% over plan → Budget will be exhausted early; need cost controls or additional funding - Issue backlog growing (not resolving issues) → Team capacity problem or escalation needed - Stakeholder satisfaction declining → Communication breakdown; schedule alignment sessions ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-phase-5-closing-weeks-1-2-after-go-live-20-40-hours", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Phase 5: Closing (Weeks 1-2 after go-live, 20-40 hours)", "headingId": "chapter-11-project-management-and-pmp-frameworks-phase-5-closing-weeks-1-2-after-go-live-20-40-hours", "url": "#chapter-11-project-management-and-pmp-frameworks-phase-5-closing-weeks-1-2-after-go-live-20-40-hours", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Formally close project, transfer to operations, and capture lessons learned. Week 1 Post-Go-Live: Transition & Handoff (10-20 hours) - Operational Handoff (4-6 hours): - Transfer solution to operations/support team: - Documentation: System architecture, user guides, support runbooks - Training: Train support team on troubleshooting, escalation procedures - Support transition: Define support SLAs (response time, resolution time) - Warranty period: Typically 30-90 days where project team provides bug fixes - Output: Operational handoff document (signed by operations team) - Final Deliverable Review (2-3 hours): - Review all deliverables against acceptance criteria (from scope baseline) - Confirm: All requirements met, all deliverables delivered - Obtain formal acceptance from sponsor (sign-off) - Output: Deliverable acceptance form - Financial Closeout (2-4 hours): - Final budget reconciliation: Actual spend vs. budget - Close purchase orders, finalize vendor payments - Release unused contingency funds - Output: Final budget summary - Resource Release (2-3 hours): - Release team members back to functional managers or other projects - Performance reviews/feedback (for team members) - Celebrate success (team celebration, recognition) - Output: Resource release notifications Week 2: Lessons Learned & Documentation (10-20 hours) - Lessons Learned Workshop (2-3 hours): - Attendees: Project team (5-15 people) - Facilitated discussion: - What went well? (strengths to replicate) - What didn't go well? (areas to improve) - What would we do differently next time? - Categorize lessons: Planning, execution, communication, risk management, technology, stakeholder management - Document specific, actionable lessons (not vague like \"communicate better\") - Output: Lessons learned summary - Project Closeout Summary (6-10 hours): - Executive summary (1 page): - Project objectives: What we set out to do - Final outcomes: What was delivered - Success metrics: Did we hit success criteria from charter? - Budget performance: Final cost vs. budget (% variance) - Schedule performance: Final duration vs. plan (% variance) - Key accomplishments and challenges - Detailed sections: - Scope delivered (summary of all deliverables) - Budget summary (spend by phase and category) - Schedule summary (timeline with milestones) - Quality metrics (defect rates, test pass rates, user satisfaction) - Risk management summary (risks that materialized, mitigation effectiveness) - Change management summary (# of change requests, impact) - Lessons learned (summary of workshop findings) - Recommendations for future projects - Output: Project closeout summary - Archive Project Documentation (2-4 hours): - Organize all project artifacts: - Charter, plans, schedules, budgets - Requirements, design docs, test results - Status updates, meeting minutes, decision logs - Lessons learned, closeout summary - Store in centralized repository (SharePoint, project folder, document management system) - Ensure accessibility for future reference - Output: Archived project documentation Outputs (Phase 5): - Formal project acceptance (sponsor sign-off) - Operational handoff complete (support team trained) - Final budget reconciliation - Lessons learned summary - Project closeout summary - Archived documentation Decision Gate: Project Closed? - GREEN: All deliverables accepted, documentation complete, team released → Project officially closed - YELLOW: Minor cleanup tasks remain (documentation gaps, final invoices) → Complete within 1-2 weeks - RED: Major issues unresolved (defects, incomplete deliverables) → Extend project or plan Phase 2 Red Flags: - Sponsor refuses to sign off → Unmet expectations; investigate and address - Support team not ready to take over → Extend transition period; provide additional training - Significant budget variance unexplained → Investigate; may indicate cost control issues - Team members reassigned before closeout → Knowledge loss; ensure documentation complete Resource Requirements: - Project Manager: 20-40 hours (closing activities) - Team members: 10-20 hours (lessons learned, documentation) - Sponsor: 2-4 hours (final acceptance review) ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-setup-phase-weeks-1-2-40-60-hours", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Setup Phase (Weeks 1-2, 40-60 hours)", "headingId": "chapter-11-project-management-and-pmp-frameworks-setup-phase-weeks-1-2-40-60-hours", "url": "#chapter-11-project-management-and-pmp-frameworks-setup-phase-weeks-1-2-40-60-hours", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Define product vision, assemble team, and prepare for iterative execution. Activities: Product Vision Definition (8-12 hours): - Product vision statement: What are we building and why? - Format: \"For [target user], who [need/opportunity], our product is [product category] that [key benefit]. Unlike [alternatives], our product [unique differentiation].\" - Example: \"For marketing teams who need to automate campaigns, our product is a marketing automation platform that requires zero coding. Unlike Marketo, our product has a visual workflow builder.\" - High-level roadmap: Major features/themes for next 6-12 months (not detailed yet) - Success metrics: How will we measure success? - Example: \"50 paying customers by Month 6, NPS 40, <10% churn\" - Output: Product vision document (2-3 pages) Team Assembly (12-16 hours): - Scrum roles: - Product Owner (PO): Accountable for maximizing product value and effective Product Backlog management - Scrum Master (SM): Accountable for establishing Scrum and improving Scrum Team effectiveness; this is not defined as a generic blocker-removal or project-manager role - Developers: Accountable for creating a usable Increment each Sprint; required skills can span engineering, design, testing, analysis, or other work. [BB-C11-S05] - Team co-location (if possible): Ideally same room or same floor; if remote, daily video standups - Team working agreement: - Working hours: Core hours when everyone is available (e.g., 10 AM - 4 PM) - Communication norms: Slack for quick questions, meetings for complex discussions - Definition of \"Done\": What does it mean for a story to be complete? (coded, tested, reviewed, deployed?) - Sprint cadence: Choose a fixed cadence that fits the product and the team's ability to inspect and adapt. [BB-C11-S05] - Output: Team charter (1 page) Product Backlog Creation (12-16 hours): - Gather user stories: Stakeholder interviews, user research, competitive analysis - User story format: \"As a [user type], I want [goal] so that [benefit]\" - Example: \"As a marketer, I want to create email campaigns so that I can engage customers\" - Write 20-50 initial user stories (high-level epics) - Prioritize using MoSCoW or value vs. effort matrix: - Must-have (MVP): Minimum viable product features - Should-have: Important but not critical for MVP - Could-have: Nice-to-have enhancements - Won't-have: Out of scope for now - Acceptance criteria for each story: How will we know the story is done? - Example: \"Email campaign can be created, previewed, scheduled, and sent. Metrics track open rate and click rate.\" - Output: Prioritized product backlog (living document, will evolve) Sprint Planning Preparation (8-12 hours): - Define sprint goal template: Each sprint will have a goal (theme/objective for that sprint) - Estimate stories using story points or t-shirt sizes (XS, S, M, L, XL): - Story points: Relative complexity (1 point = simplest story, 8 points = most complex in sprint) - Capacity and forecast: use availability, work type, dependencies, risk, and the team's own historical evidence; story points are optional and have no universal team-size range - Set sprint schedule: - Sprint length: 2 weeks (adjust if needed: 1 week for fast iteration, 4 weeks for longer cycles) - Sprint ceremonies: - Sprint Planning (Monday, start of sprint): 2-4 hours - Daily Standup (every morning): 15 min - Sprint Review (Friday, end of sprint): 1-2 hours - Sprint Retrospective (Friday, end of sprint): 1 hour - Output: Sprint calendar, estimation baseline Outputs (Setup Phase): - Product vision and roadmap - Team assembled and trained on Scrum - Product backlog (prioritized, estimated) - Sprint schedule and ceremonies defined Decision Gate: Ready to Start Sprints? - GREEN: Vision clear, team ready, backlog has 2-3 sprints worth of stories → Start Sprint 1 - YELLOW: Backlog thin or team not fully assembled → Extend setup 1 week - RED: Vision unclear or team unavailable → Pause until resolved Red Flags: - Product Owner not available (has other full-time job) → Will bottleneck; need dedicated PO or part-time commitment - Team composition or size impedes cohesion or required skills → inspect coordination, capability, dependencies, and product boundaries; no universal numeric cutoff applies - No user research or customer input → Building in a vacuum; risk building wrong thing - Backlog has no acceptance criteria → Stories not testable; will lead to scope confusion ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-sprint-execution-ongoing-2-week-sprints-example", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Sprint Execution (Ongoing, 2-week sprints example)", "headingId": "chapter-11-project-management-and-pmp-frameworks-sprint-execution-ongoing-2-week-sprints-example", "url": "#chapter-11-project-management-and-pmp-frameworks-sprint-execution-ongoing-2-week-sprints-example", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Sprint Planning (Monday, Week 1 of sprint, 2-4 hours) Activities: - Review sprint goal (30 min): - PO presents sprint goal: What will we accomplish this sprint? - Example: \"Complete user authentication feature (login, signup, password reset)\" - Select user stories from backlog (1-2 hours): - PO presents top-priority stories - Team discusses: Is story clear? Do we understand acceptance criteria? - Team estimates effort (if not already estimated) - Developers forecast the work that supports the Sprint Goal using current capacity, dependencies, risk, and relevant history; velocity does not determine a commitment - Break stories into tasks (1-2 hours): - For each story, team identifies tasks: - Example story: \"User can log in\" - Tasks: Design login UI, implement login API, write tests, integrate with existing system, deploy - Estimate tasks in hours (2-16 hours per task typical) - Assign tasks to team members (self-assignment, not top-down) - Output: Sprint Backlog: Sprint Goal, selected Product Backlog items, and a plan for delivering the Increment; selected items remain a forecast, not a universal promise. Daily Scrum (each working day of the Sprint; 15-minute timebox under the Scrum Guide) Format: - Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog. The format is theirs; standing and the historical three questions are not required. - Detailed problem-solving can follow or occur elsewhere when useful; the Scrum Master need not attend or personally resolve every blocker. Sprint Work (Daily, 6-8 hours/person) Activities: - Developers code features, designers create UI, testers write/run tests - Pair programming (if applicable): Two developers work together on complex tasks - Code reviews: Peer review before merging code - Testing: Unit tests, integration tests, manual testing - Update task board: Move tasks from \"To Do\" → \"In Progress\" → \"Done\" - Scrum Master supports the team's effectiveness and helps impediments reach the appropriate decision-maker; the role does not require personally resolving every blocker or owning all technical decisions. Tools: - Task board: Physical board (sticky notes) or digital (Jira, Trello, Azure DevOps) - Columns: To Do, In Progress, Code Review, Testing, Done - Definition of Done checklist: Code written, tests passed, peer reviewed, deployed to test environment Mid-Sprint Check-In (Optional, Wednesday of Week 1, 30 min) Activities: - Review sprint progress: Are we on track to complete committed stories? - Burndown chart review: Chart showing remaining work vs. time - Ideal: Steady decrease from start to end of sprint - Reality: Often choppy; use to identify if sprint is at risk - Adjust if needed: If behind, descope low-priority stories; if ahead, add stretch goals Sprint Review (Friday, Week 2 of sprint, 1-2 hours) Objective: Demonstrate completed work to stakeholders; get feedback. Activities: - Demo (45-60 min): - Attendees: Team, PO, stakeholders (sponsor, end users, anyone interested) - Team demonstrates each completed story: - Show working product (not slides or mockups; actual functionality) - Explain: What was built, why it's valuable - Stakeholders provide feedback: - Does it meet their needs? - Any adjustments needed? - Celebrate successes: Recognize team for what was delivered - Optional follow-on refinement (outside the event): - Based on feedback, the Product Owner may update and reorder the Product Backlog as an ongoing activity. - The team may provide input on feasibility, dependencies, and evidence; refinement is not a required Sprint Review activity. - Output: Sprint outcome inspected, stakeholder feedback captured, and any authorized backlog adaptations recorded. Sprint Retrospective (Friday, Week 2 of sprint, 1 hour) Objective: Reflect on process; identify improvements for next sprint. Activities: - What went well? (20 min): - Team shares what worked: Good collaboration? Helpful tools? Smooth deployment? - Scrum Master captures on whiteboard/doc - What didn't go well? (20 min): - Team shares challenges: Blockers? Unclear requirements? Technical debt? Slow tests? - No blaming; focus on process not people - What will we change next sprint? (20 min): - Identify 1-3 concrete improvements: - Example: \"We'll add automated testing to reduce bugs\" or \"PO will clarify stories 1 day before sprint planning\" - Assign owners for improvement actions - Output: Retrospective notes, action items for next sprint Sprint Outputs: - Potentially shippable product increment (working features added to product) - Updated backlog - Optional local measures such as a burndown chart or velocity, interpreted as diagnostic planning observations rather than productivity targets - Retrospective actions Sprint Health Metrics: - Prefer measures tied to the product decision: Sprint Goal evidence, outcome, flow, quality, reliability, customer impact, risk, and forecast error. - If velocity or completion is used, keep definitions stable within one team and treat trends as diagnostic observations, not productivity targets or cross-team comparisons. - Set defect and release tolerances from severity, exposure, safety, regulation, service level, detectability, and rollback—not universal percentages. Red Flags: - Material change in flow, goal evidence, quality, or forecast error → verify definitions and investigate multiple explanations; do not diagnose capacity from a fixed velocity decline - Repeated inability to meet Sprint Goals → inspect goal quality, scope, dependencies, interruptions, capability, and product decisions without a universal percentage - Retrospective actions not implemented → Team not learning; Scrum Master needs to follow up - Stakeholders skip sprint reviews → Disengagement; risk building wrong thing - Technical debt or quality risk accumulating → compare refactoring, redesign, testing, scope, and sequencing from risk and product value; no fixed Sprint allocation applies Contingency Triggers: - If team consistently over-commits → Reduce capacity estimate (commit to fewer points) - If PO unavailable → Escalate; Scrum doesn't work without engaged PO - If blockers persist 2 days → Scrum Master escalates to leadership - If stakeholder feedback contradicts PO direction → Facilitate alignment session ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-release-planning-parallel-to-sprints-every-3-6-sprints", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Release Planning (Parallel to Sprints, Every 3-6 Sprints)", "headingId": "chapter-11-project-management-and-pmp-frameworks-release-planning-parallel-to-sprints-every-3-6-sprints", "url": "#chapter-11-project-management-and-pmp-frameworks-release-planning-parallel-to-sprints-every-3-6-sprints", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Plan major releases (collections of features) for go-live. Activities (4-8 hours every 3-6 sprints): - Release Goal Definition: - What features will be in next release? - When will release go live? (target date) - Who is target audience? (beta users, all users, specific segment) - Release Backlog: - Group stories into release: \"Release 1.0 includes login, profile, search features\" - Estimate completion from a range using scope, dependencies, risk, capacity, flow, and relevant team history; velocity alone is insufficient - Release Criteria: - Defects within the authorized severity- and exposure-based release tolerance; some critical contexts require zero unresolved critical defects, while counts alone are insufficient - Performance acceptable (load testing passed) - Security reviewed (pen testing if applicable) - Training/documentation complete - Go/No-Go Decision: - Review release criteria - Decide: Launch, delay, or descope? - Output: Release plan (features, timeline, go-live date) Release Cadence: - Fast iteration: Release every sprint (continuous delivery; common for SaaS) - Moderate: Release every 3-6 sprints (2-3 months; common for mobile apps) - Slow: Release 2-4 times/year (common for enterprise software with long sales cycles) ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-agile-retrospectives-learning-ongoing", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Agile Retrospectives & Learning (Ongoing)", "headingId": "chapter-11-project-management-and-pmp-frameworks-agile-retrospectives-learning-ongoing", "url": "#chapter-11-project-management-and-pmp-frameworks-agile-retrospectives-learning-ongoing", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Continuously improve process, tools, and team dynamics. Metrics to Track: - If used, velocity trends interpreted as local planning observations—not “increasing is good” productivity scores - Defect severity, exposure, detection, recurrence, and escape rather than count direction alone - Sprint Goal evidence without a universal achievement percentage - Voluntary, confidential team-experience measures under approved instruments; a generic happiness rating is not NPS - Stakeholder satisfaction (are stakeholders happy with product progress?) Adjustments Over Time: - Inspect whether the delivery system produces better customer, product, flow, quality, risk, and forecasting evidence. - Teams may continue learning and redesigning at any Sprint; no fixed calibration, optimization, or maturity ranges apply, and high velocity is not maturity. Common Agile Pitfalls & Fixes: - Pitfall: PO acts as project manager (controlling tasks) instead of defining product - Fix: Empower team to self-organize; PO focuses on what, team decides how - Pitfall: Daily standups become status reports to manager - Fix: Reframe as team sync (not reporting up); manager doesn't attend or listens only - Pitfall: Sprint planning takes 4 hours (too much detail) - Fix: Refine backlog items before Sprint Planning when useful; do not treat “grooming” as a Scrum requirement - Pitfall: No retrospective improvements implemented - Fix: Scrum Master tracks actions, follows up, ensures changes happen - Pitfall: Stakeholders want detailed long-term plan (conflicts with agility) - Fix: Provide roadmap (themes/epics for next 3-6 months), but emphasize that details will emerge ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-summary-delivery-tailoring-matrix", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Summary: Delivery Tailoring Matrix", "headingId": "chapter-11-project-management-and-pmp-frameworks-summary-delivery-tailoring-matrix", "url": "#chapter-11-project-management-and-pmp-frameworks-summary-delivery-tailoring-matrix", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The matrix is a qualitative tailoring aid; evaluate the project's actual constraints rather than applying the examples as fixed thresholds. [BB-C11-S01] [BB-C11-S05] [BB-C11-S06] | Dimension | Predictive practice can help when... | Adaptive practice can help when... | Control that remains necessary | |--------|------------------|--------------|---| | Requirements and solution | Evidence supports committing selected detail early | Needs or solution choices must be learned | Traceability, acceptance, and change authority | | Dependencies | Network and interface sequence is relatively knowable | Work can be sliced and integrated safely | Architecture, configuration, and integration evidence | | Feedback | Review is meaningful at planned gates | Frequent use or testing can update decisions | Valid measures, affected-user input, and decision records | | Contract and funding | Baselines support coordination and financing | Commercial terms allow staged learning and reprioritization | Incentive, acceptance, audit, change, and termination design | | Safety and regulation | Formal evidence and hold points need advance planning | Incremental testing reduces uncertainty without unsafe release | Independent assurance and applicable approvals in either approach | | Deadline and budget | Scope and plan are feasible under bounded uncertainty | Tradeoffs can be revisited as evidence changes | Forecasting, escalation, and explicit constraint ownership | ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-when-to-use-this-operating-manual", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "When to Use This Operating Manual", "headingId": "chapter-11-project-management-and-pmp-frameworks-when-to-use-this-operating-manual", "url": "#chapter-11-project-management-and-pmp-frameworks-when-to-use-this-operating-manual", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the sample predictive track for artifacts that benefit from an explicit baseline and the sample adaptive track for work that benefits from frequent inspection and revision. A project may use both, neither, or different practices by workstream. Document the rationale, authority, interfaces, and triggers rather than calling the result “hybrid” as a substitute for design. --- ---" }, { "id": "chapter-11-project-management-and-pmp-frameworks::chapter-11-project-management-and-pmp-frameworks-chapter-summary", "kind": "chapter", "itemSlug": "chapter-11-project-management-and-pmp-frameworks", "itemTitle": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "heading": "Chapter Summary", "headingId": "chapter-11-project-management-and-pmp-frameworks-chapter-summary", "url": "#chapter-11-project-management-and-pmp-frameworks-chapter-summary", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter provided formal project management frameworks: 1. Predictive process groups - Five recurring groups, not five lifecycle phases 2. WBS - Hierarchical decomposition of scope 3. CPM & Gantt - Schedule management and critical path analysis 4. EVM - Integrated cost and schedule performance measurement 5. Risk Management - Identify, analyze, respond, monitor 6. Stakeholder Management - Engagement strategies by power/interest 7. Agile/Scrum - Iterative development with sprints 8. Constructed flow board - Visual workflow and locally justified WIP policies; not a full Kanban treatment 9. Change authority - Impact analysis and a tailored authorized decision route 10. Project charter - Purpose, boundaries, governance, and assigned authority Table 11.10 — Predictive and adaptive practices. Constructed comparison; select practices independently from the project's evidence and constraints. | Aspect | Waterfall | Agile | |--------|-----------|-------| | Planning | Commit justified detail earlier | Refine detail as evidence changes | | Scope | Baseline selected scope and assumptions | Reorder or reshape work within authority | | Change | Route material changes through tailored authority | Adapt work while preserving governance and evidence | | Delivery | Release at feasible, controlled points | Inspect usable increments on a chosen cadence | | Selection | Use where evidence supports early commitment | Use where feedback can responsibly reduce uncertainty | When these PMP-oriented frameworks may help: Use them as tailoring prompts, not numerical thresholds. Their value depends on the decision, evidence, authority, and consequences—not on project size or an industry label. [BB-C11-S01] - Projects with material scope, dependency, cost, risk, stakeholder, assurance, or change decisions - Work involving multiple teams, suppliers, jurisdictions, or decision authorities - Regulated, contractual, safety-critical, or otherwise high-consequence contexts where traceability and specialist review are required - Any project where an explicit baseline, feedback loop, forecast, or decision record would improve the next decision Next Chapter: Client Management - Stakeholder engagement, presentations, difficult conversations --- Cross-references: See Chapter 7 for teams and leadership, Chapter 9 for issue trees and MECE, Chapter 10 for integrated initiatives, and Chapter 12 for client and stakeholder governance." }, { "id": "chapter-12-client-management::chapter-12-client-management", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Client Management", "headingId": "chapter-12-client-management", "url": "#chapter-12-client-management", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-12-client-management::chapter-12-client-management-executive-summary", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Executive Summary", "headingId": "chapter-12-client-management-executive-summary", "url": "#chapter-12-client-management-executive-summary", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter treats client management as governed professional practice: clarify the decision, affected parties, authority, evidence, scope, ethics, communications, change, and relationship risks. Templates organize work; they do not override law, contract, professional duties, or the rights of people with little formal power. Key Frameworks: 1. Stakeholder Influence/Interest Matrix 2. RACI Matrix (Accountability Framework) 3. Executive Presentation Structure 4. Difficult Conversation Framework 5. Project Scoping Template 6. Statement of Work (SOW) Components 7. Risk Register & Mitigation 8. Change Request Process 9. Feedback Collection Methods 10. Relationship Mapping Tool" }, { "id": "chapter-12-client-management::chapter-12-client-management-manager-decision-outcomes-and-professional-practice-boundary", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Manager Decision Outcomes and Professional-Practice Boundary", "headingId": "chapter-12-client-management-manager-decision-outcomes-and-professional-practice-boundary", "url": "#chapter-12-client-management-manager-decision-outcomes-and-professional-practice-boundary", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "After this chapter, a manager should be able to: 1. Map stakeholder claims, rights, harm exposure, legitimacy, urgency, influence, and changing coalitions. 2. Clarify work, coordination, approvals, consultation, and communication without inventing authority. 3. Present an answer-first recommendation while preserving evidence quality, uncertainty, alternatives, dissent, and the decision ask. 4. Conduct, pause, or escalate a difficult conversation based on safety, power, law, and professional process. 5. Govern scope, change, feedback, data, confidentiality, conflicts, and client-exit decisions. Before engagement work, document the sponsor, decision owner, affected stakeholders, scope, conflicts, confidentiality and privilege, permitted data and interviews, record retention, legal and regulatory constraints, accessibility, escalation, and the team's duty to correct material misstatements. Client preference does not override law, evidence, professional integrity, or foreseeable harm. Applied exercise — composite transformation: Build a stakeholder-and-rights map, RACI-plus-approval table, one-page executive update, difficult-conversation plan, and change request for a fictional transformation. Identify one request the team must refuse or escalate, one low-power group requiring direct engagement, and the governing authority for each decision. Use Chapter 7 for team and power dynamics, Chapter 9 for the issue structure, and Chapter 11 for project controls. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-overview", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-12-client-management-overview", "url": "#chapter-12-client-management-overview", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The stakeholder influence/interest matrix is a provisional attention and inquiry aid. Stakeholder theory and salience concepts can organize relationships and interests, but the matrix does not rank human worth, create authority, or replace rights, representation, accessibility, professional, legal, or safety review. [BB-C12-S01] [BB-C12-S02]" }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-apply", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-12-client-management-how-to-apply", "url": "#chapter-12-client-management-how-to-apply", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Identify parties affected by or able to affect the work. Stakeholder theory supports examining relationships and interests, while the salience model distinguishes power, legitimacy, and urgency; neither should be reduced to a single power score. [BB-C12-S01] [BB-C12-S02] Separately document legal rights, expertise, representation, vulnerability, and harm exposure even when a party lacks formal authority. Matrix Axes: - Vertical: Level of interest in project (Low to High) - Horizontal: Degree of influence/power (Low to High) Four Quadrants:" }, { "id": "chapter-12-client-management::chapter-12-client-management-high-power-high-interest", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "High Power, High Interest", "headingId": "chapter-12-client-management-high-power-high-interest", "url": "#chapter-12-client-management-high-power-high-interest", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Strategy: Clarify authority, decision needs, evidence, conflicts, and accountability. - Cadence: Set by decision urgency and risk, not a universal weekly meeting. - Content: Decision-relevant evidence, alternatives, uncertainty, risks, and required action. - Example: CFO when managing IT transformation budget" }, { "id": "chapter-12-client-management::chapter-12-client-management-high-power-low-interest", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "High Power, Low Interest", "headingId": "chapter-12-client-management-high-power-low-interest", "url": "#chapter-12-client-management-high-power-low-interest", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Strategy: Confirm what authority or approval the person actually holds and the minimum evidence needed for responsible oversight. - Cadence: Set by governance and materiality. - Content: Exceptions, decisions, dependencies, and consequences without concealing material detail. - Example: Board member for operational project" }, { "id": "chapter-12-client-management::chapter-12-client-management-low-power-high-interest", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Low Power, High Interest", "headingId": "chapter-12-client-management-low-power-high-interest", "url": "#chapter-12-client-management-low-power-high-interest", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Strategy: Create accessible routes for input, challenge, remedy, and feedback; formal power may understate expertise or harm exposure. - Cadence: Match the timing of impact and decisions. - Content: Relevant evidence, choices, rights, effects, and response process. - Example: Project team members, affected department heads" }, { "id": "chapter-12-client-management::chapter-12-client-management-low-power-low-interest", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Low Power, Low Interest", "headingId": "chapter-12-client-management-low-power-low-interest", "url": "#chapter-12-client-management-low-power-low-interest", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Strategy: Test whether “low interest” reflects exclusion, access barriers, fear, or lack of information. Monitor for changing impact and provide a proportionate contact or notice route. - Cadence and content: Determine from rights, harm, dependency, accessibility, and legal duties—not minimal effort. - Example: Indirect stakeholders Application Steps: 1. Identify affected and responsible parties without imposing a minimum count. 2. Plot on matrix using current status 3. Add rights, legitimacy, urgency, expertise, dependency, and harm exposure; a power-interest position is not the whole assessment. 4. Define communication plan for each quadrant 5. Reassess when decisions, impacts, coalitions, or evidence change. Common pitfall: Applying identical engagement effort without considering decision need, rights, impact, accessibility, and evidence. Proportionate engagement is not permission to ignore low-power groups." }, { "id": "chapter-12-client-management::chapter-12-client-management-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-12-client-management-so-what-for-managers", "url": "#chapter-12-client-management-so-what-for-managers", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the matrix to identify whose evidence, consent, expertise, exposure, and decision rights matter for the next decision. - Treat power, interest, legitimacy, urgency, influence, and harm exposure as changing hypotheses to test rather than fixed labels. - Create accessible routes for challenge, remedy, and participation even when a group lacks formal authority." }, { "id": "chapter-12-client-management::chapter-12-client-management-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-12-client-management-limits-and-critiques", "url": "#chapter-12-client-management-limits-and-critiques", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A two-axis matrix can hide rights, representation, expertise, dependency, vulnerability, informal influence, and people absent from the sponsor's view. - Cadence, quadrant, or label does not establish a communication duty, consent, or safe engagement method. - Stakeholder mapping can reproduce sponsor bias if the team does not validate the map with affected groups and governing instruments." }, { "id": "chapter-12-client-management::chapter-12-client-management-connections", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-12-client-management-connections", "url": "#chapter-12-client-management-connections", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Authority: Use Framework 2 and Chapter 11 to connect RACI labels to actual approvals, governance, and change control. - Communication: Use Framework 3 and Framework 9 to match messages and feedback to decision need, accessibility, and evidence. - Problem and leadership context: Use Chapters 7 and 9 to examine power, conflict, coalitions, and problem structure without reducing people to a score. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-overview-2", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-12-client-management-overview-2", "url": "#chapter-12-client-management-overview-2", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The RACI matrix is a constructed conversation aid for making work coordination, contribution, consultation, information, and approval questions visible. It does not create legal, board, committee, licensed-professional, contractual, or shared accountability. [BB-C12-S03]" }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-12-client-management-how-to-apply-2", "url": "#chapter-12-client-management-how-to-apply-2", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Use RACI to define how stakeholders are involved in project activities. [BB-C12-S03] Treat it as a conversation aid after the real governance authority and required approvals are known; it does not create legal, board, committee, licensed-professional, contractual, or shared accountability. Definitions: - R (Responsible): Who coordinates or performs the work? There may be more than one responsible contributor. - A (Accountable): Who coordinates answerability under this local convention? Prefer clarity, but preserve required shared or external authority. - C (Consulted): Who provides input? (Two-way communication) - I (Informed): Who is kept in the loop? (One-way communication)" }, { "id": "chapter-12-client-management::chapter-12-client-management-visual-representation", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Visual Representation:", "headingId": "chapter-12-client-management-visual-representation", "url": "#chapter-12-client-management-visual-representation", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 12.2 — Constructed RACI working matrix. Confirm governing authority and required approvals before assigning local RACI labels. [BB-C12-S03] | Activity or decision | Product lead | Engineering lead | Design lead | Commercial lead | Executive authority | |---|---|---|---|---|---| | Define the decision and evidence need | R | C | C | C | A or governing approval | | Build and validate the solution | A or coordinating owner | R | R/C | I/C | I or required approval | | Approve release and material risk | C | C | C | C | A or governing approval | Text equivalent: The example separates work coordination, contribution, consultation, information, and governing approval. Actual authority can be shared, external, statutory, contractual, professional, or board-based and overrides the illustrative letters. Key rules: - Prefer a clearly named coordinating owner where useful, but do not erase statutory, board, committee, professional, contractual, or shared accountability. - \"R\" and \"A\" often same person; can differ for oversight - Multiple \"C\"s are fine (more coordination needed) - \"I\" is least intrusive relationship Implementation Steps: 1. List all major work streams/tasks 2. Identify key roles (Owner, Finance, Client, etc.) 3. Map each role to each task and record required approvals; workshop count is context-specific. 4. Share matrix and get explicit sign-off 5. Use the matrix to prompt clarification, then defer to the governing instrument when it conflicts. Example: New Product Launch The first two rows use a local teaching convention in which the coordinating role also carries the local accountability label; this is not a universal requirement. Replace the letters with the governing decision rule, required approvals, and any shared, external, statutory, contractual, professional, or committee authority. - Requirements gathering: Dev lead (R, A), Product manager (C), Sales (C) - Go-to-market planning: Marketing (R, A), Sales lead (C), Finance (C) - Launch execution: Project manager (R), CMO (A), Team leads (C) Digital Age Modification: Use shared RACI in Confluence/Monday.com; update quarterly as roles shift." }, { "id": "chapter-12-client-management::chapter-12-client-management-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-12-client-management-so-what-for-managers-2", "url": "#chapter-12-client-management-so-what-for-managers-2", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use RACI to surface missing work owners, consultation, information routes, and approval questions before execution. - Verify the real decision rule when authority is shared, external, statutory, contractual, professional, or committee-based. - Revisit the matrix when scope, roles, dependencies, staffing, decision rights, or affected groups change." }, { "id": "chapter-12-client-management::chapter-12-client-management-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-12-client-management-limits-and-critiques-2", "url": "#chapter-12-client-management-limits-and-critiques-2", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A RACI letter is not an appointment, legal delegation, consent, or proof that one person can decide. - Forcing one accountable person can erase dual controls, boards, collective authority, professional review, or required approvals. - RACI can create false clarity if the work, outcome, evidence, or governing instrument is ambiguous." }, { "id": "chapter-12-client-management::chapter-12-client-management-connections-2", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-12-client-management-connections-2", "url": "#chapter-12-client-management-connections-2", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Stakeholders: Use Framework 1 to test whose rights, expertise, exposure, and participation are missing. - Projects: Use Chapter 11 for scope, change, risk, and baseline controls; reconcile RACI with the project charter and contract. - Client communication: Use Framework 3 and Framework 9 to connect role clarity to the message, feedback, and decision record. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-overview-3", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-12-client-management-overview-3", "url": "#chapter-12-client-management-overview-3", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The executive decision brief places a governing summary above logically ordered support while preserving the question, evidence, implications, uncertainty, alternatives, dissent, risk, and ask. It is an author adaptation of the cited communication source, not a universal slide count or persuasion formula. [BB-C12-S04]" }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-12-client-management-how-to-apply-3", "url": "#chapter-12-client-management-how-to-apply-3", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Context: Pyramid structure places a governing summary above logically similar, logically ordered supporting ideas. [BB-C12-S04] The decision brief below is an author adaptation that also surfaces the question, evidence, implications, uncertainty, and ask; it must not hide weak evidence, material alternatives, dissent, or risk. Illustrative presentation sequence: The number of slides and order depend on the decision and evidence." }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-1-title-credibility", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 1: Title & Credibility", "headingId": "chapter-12-client-management-slide-1-title-credibility", "url": "#chapter-12-client-management-slide-1-title-credibility", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Content: Project name, date, key stakeholders - Purpose: Orient & establish authority" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-2-business-context-the-problem", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 2: Business Context (THE PROBLEM)", "headingId": "chapter-12-client-management-slide-2-business-context-the-problem", "url": "#chapter-12-client-management-slide-2-business-context-the-problem", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Market/competitive situation, customer pain, financial impact - Format: 1 key stat or graph + 1-2 bullet points - Tone: Neutral, fact-based (\"Market growing quickly but we're flat\")" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-3-opportunity-vision-the-answer", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 3: Opportunity/Vision (THE ANSWER)", "headingId": "chapter-12-client-management-slide-3-opportunity-vision-the-answer", "url": "#chapter-12-client-management-slide-3-opportunity-vision-the-answer", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: What becomes possible if we act - Format: 1 powerful image or visual + 1-2 bullet points - Tone: Optimistic but grounded (\"$50M revenue opportunity if we launch Q2\")" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-4-strategic-approach-the-how", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 4: Strategic Approach (THE HOW)", "headingId": "chapter-12-client-management-slide-4-strategic-approach-the-how", "url": "#chapter-12-client-management-slide-4-strategic-approach-the-how", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: 3-4 key initiatives or phases - Format: Simple diagram or list - Tone: Clear and logical" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-5-8-key-workstreams-proof-it-works", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 5-8: Key Workstreams (PROOF IT WORKS)", "headingId": "chapter-12-client-management-slide-5-8-key-workstreams-proof-it-works", "url": "#chapter-12-client-management-slide-5-8-key-workstreams-proof-it-works", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Content: Details on 3-4 major initiatives - Format: 1 slide per workstream with metrics and status - Example Workstream Slide: - Initiative: \"Expand sales team\" - Status: Hiring complete, ramping - Metrics: 5 reps hired, 3 in full productivity (target: 8/10 by Q3) - Risk: Attrition (mitigating with bonus structure)" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-9-financial-summary", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 9: Financial Summary", "headingId": "chapter-12-client-management-slide-9-financial-summary", "url": "#chapter-12-client-management-slide-9-financial-summary", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Total investment, expected ROI, payback period - Format: Simple waterfall or table - Standard Format: - Investment: $2M - Expected revenue impact: $8M - Timeline: 18 months - ROI: 300 percent" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-10-timeline-milestones-the-when", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 10: Timeline/Milestones (THE WHEN)", "headingId": "chapter-12-client-management-slide-10-timeline-milestones-the-when", "url": "#chapter-12-client-management-slide-10-timeline-milestones-the-when", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Key dates for next 12-18 months - Format: Gantt chart or simple timeline - Include: Major Go/No-go gates" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-11-team-governance", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 11: Team & Governance", "headingId": "chapter-12-client-management-slide-11-team-governance", "url": "#chapter-12-client-management-slide-11-team-governance", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Who's accountable, how decisions are made - Format: org chart or governance matrix - Content: Sponsor, steering committee (quarterly), working team (weekly)" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-12-top-5-risks-honest-assessment", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 12: Top 5 Risks (HONEST ASSESSMENT)", "headingId": "chapter-12-client-management-slide-12-top-5-risks-honest-assessment", "url": "#chapter-12-client-management-slide-12-top-5-risks-honest-assessment", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- List: Risks executives care about (timeline, budget, market risk, talent, tech) - Include: Mitigation for each - Format: Table with risk → mitigation → owner" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-13-next-steps-the-ask", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 13: Next Steps (THE ASK)", "headingId": "chapter-12-client-management-slide-13-next-steps-the-ask", "url": "#chapter-12-client-management-slide-13-next-steps-the-ask", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: What decision/approval you need - Format: Clear bullet points - Examples: - Approve $2M budget allocation - Commit CFO and CTO to steering committee - Authority to hire 5 new staff" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-14-q-a-backup", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 14: Q&A/Backup", "headingId": "chapter-12-client-management-slide-14-q-a-backup", "url": "#chapter-12-client-management-slide-14-q-a-backup", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Include: Detailed slides for anticipated questions (not shown unless asked) - Content: Market data, financial models, competitive analysis, detailed workplans" }, { "id": "chapter-12-client-management::chapter-12-client-management-slide-15-contact-info", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Slide 15: Contact Info", "headingId": "chapter-12-client-management-slide-15-contact-info", "url": "#chapter-12-client-management-slide-15-contact-info", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Delivery Best Practices: - Opening: \"We have 3 key points: the opportunity, the approach, what we need from you\" - Timing: 20 min presentation + 10 min Q&A (leave silence for questions) - Data: Every assertion backed by one data point (not cluttered) - Visuals: Photos/diagrams text; avoid clip art - Tone: Confident, not defensive; \"here's the situation and how we're addressing it\" Common Mistakes: - Too much detail (executives want story, not spreadsheets) - \"Death by bullet points\" (use visuals instead) - Failing to clearly state the ask - Assuming they remember context (restate once)" }, { "id": "chapter-12-client-management::chapter-12-client-management-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-12-client-management-so-what-for-managers-3", "url": "#chapter-12-client-management-so-what-for-managers-3", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Lead with the decision, evidence, implications, uncertainty, alternatives, and ask that the audience must act on. - Use the structure to improve comprehension and challenge, not to conceal weak data, dissent, uncertainty, or unresolved tradeoffs. - Tailor length, visuals, accessibility, confidentiality, and delivery channel to the decision and the people affected." }, { "id": "chapter-12-client-management::chapter-12-client-management-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-12-client-management-limits-and-critiques-3", "url": "#chapter-12-client-management-limits-and-critiques-3", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Pyramid structure does not make evidence valid, reasoning causal, or a recommendation safe. - Slide counts, “executive” preferences, visual rules, and confidence cues are context-dependent teaching examples. - A polished narrative can increase overconfidence or suppress dissent unless the brief shows limitations and alternatives." }, { "id": "chapter-12-client-management::chapter-12-client-management-connections-3", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-12-client-management-connections-3", "url": "#chapter-12-client-management-connections-3", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Problem structure: Use Chapter 9 to test the issue tree, hypotheses, alternatives, and evidence logic behind the brief. - Measures: Use Chapter 8 and Chapter 11 to connect objectives, KPIs, baselines, risk, and decision authority. - Stakeholders: Use Framework 1 and Framework 9 to design participation, feedback, accessibility, and follow-up. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-overview-4", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-12-client-management-overview-4", "url": "#chapter-12-client-management-overview-4", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The difficult-conversation framework separates observation, impact, interpretation, listening, perspective, options, agreement, pause, and escalation. Direct dialogue is conditional on safety, authority, channel, law, and professional process; it is not a substitute for protected reporting or formal investigation. [BB-C12-S05]" }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-12-client-management-how-to-apply-4", "url": "#chapter-12-client-management-how-to-apply-4", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "When to use: The source provides a framework for direct difficult conversations; use it only after separately checking safety, authority, and the appropriate channel. [BB-C12-S05] Protected reporting, discrimination, harassment, violence, retaliation, legal hold, investigation, accommodation, union, or material misconduct issues may require HR, counsel, compliance, security, or another formal channel rather than direct dialogue. 5-Step Conversation:" }, { "id": "chapter-12-client-management::chapter-12-client-management-step-1-frame-the-issue-not-accusation", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Step 1: Frame the Issue (Not Accusation)", "headingId": "chapter-12-client-management-step-1-frame-the-issue-not-accusation", "url": "#chapter-12-client-management-step-1-frame-the-issue-not-accusation", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Don't: \"You've been missing deadlines constantly\" - Do: \"We've had some challenges with timeline consistency on the last 3 deliverables\" - Format: Observation + impact (\"The delay on the API integration pushed our launch by 2 weeks\")" }, { "id": "chapter-12-client-management::chapter-12-client-management-step-2-listen-for-context", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Step 2: Listen for Context", "headingId": "chapter-12-client-management-step-2-listen-for-context", "url": "#chapter-12-client-management-step-2-listen-for-context", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ask: \"What's going on from your perspective?\" - Listen: Don't interrupt, assume good intent - Opportunity: Often uncover valid constraints (understaffed, unclear requirements)" }, { "id": "chapter-12-client-management::chapter-12-client-management-step-3-share-your-perspective", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Step 3: Share Your Perspective", "headingId": "chapter-12-client-management-step-3-share-your-perspective", "url": "#chapter-12-client-management-step-3-share-your-perspective", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Format: \"My concern is...\" or \"What I'm hearing is...\" - Content: Specific example (not pattern yet unless this is repeat conversation) - Tone: Partner, not judge (\"Help me understand how we can prevent this\")" }, { "id": "chapter-12-client-management::chapter-12-client-management-step-4-problem-solve-together", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Step 4: Problem-Solve Together", "headingId": "chapter-12-client-management-step-4-problem-solve-together", "url": "#chapter-12-client-management-step-4-problem-solve-together", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ask: \"What would help?\" or \"What do you need from me?\" - Brainstorm: 2-3 solutions - Land on: Clear commitment and next steps - Example Resolution: - \"You need a clearer requirements document\" (their ask) - \"I'll provide 48-hour advance notice of scope changes\" (your ask) - \"Weekly sync to catch issues early\" (shared solution)" }, { "id": "chapter-12-client-management::chapter-12-client-management-step-5-agreement-follow-up", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Step 5: Agreement & Follow-Up", "headingId": "chapter-12-client-management-step-5-agreement-follow-up", "url": "#chapter-12-client-management-step-5-agreement-follow-up", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Confirm: \"So we're going to... and we'll check in next Friday?\" - Document: Brief email recap of commitments - Follow-up: Actually follow up (if you don't, credibility destroyed) Figure 12.1. Difficult-conversation decision loop. Separate observed facts from interpretation, check safety and authority, listen and share perspectives, then agree, pause, or escalate. Adapted as a teaching summary from the difficult-conversations source. [BB-C12-S05] Text equivalent: Start with observable facts, impact, and the purpose of the conversation. If direct discussion is unsafe or the issue requires a formal process, pause and escalate. Otherwise listen for the other perspective, distinguish intent from impact, share your interpretation, explore options, document clear commitments, and follow up. If agreement is not appropriate or possible, record the unresolved issue and use the approved route. Script Examples: Scope Creep Conversation: - Frame: \"The client has requested 5 new features not in the original scope. This could impact budget and timeline.\" - Listen: [Team explains client relationship pressure] - Share: \"I understand the client wants results. My concern is we're eating into profit margin if these are uncompensated.\" - Solve: \"Let's evaluate each request as high/med/low priority, and I'll discuss which fall under 'change order' with the client.\" Performance Issue Conversation: - Frame: \"The last two deliverables had issues (grammar, math errors, incomplete data). This isn't like you.\" - Listen: [Team reveals personal issue or unclear requirements] - Share: \"I need deliverables that reflect our quality standard. I also want to support you.\" - Solve: \"Let's add a checklist before submission, and I can review one extra time if needed.\" Remote context: Choose a channel that supports safety, accessibility, privacy, cultural needs, records, and participation. Video or one-to-one discussion is not always appropriate or available." }, { "id": "chapter-12-client-management::chapter-12-client-management-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-12-client-management-so-what-for-managers-4", "url": "#chapter-12-client-management-so-what-for-managers-4", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Check safety, power, authority, confidentiality, accessibility, and the required formal route before initiating a direct conversation. - Separate observable facts, impacts, interpretations, emotions, requests, commitments, and unresolved issues. - Document the agreed next step and use the approved escalation, HR, legal, compliance, or safety process when direct dialogue is not appropriate." }, { "id": "chapter-12-client-management::chapter-12-client-management-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-12-client-management-limits-and-critiques-4", "url": "#chapter-12-client-management-limits-and-critiques-4", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A conversation script cannot resolve retaliation risk, discrimination, violence, legal privilege, investigation, accommodation, union, or professional-duty issues. - “Assume good intent,” private dialogue, or a weekly follow-up may be unsafe or inappropriate in some power relationships. - Agreement is not consent, remediation, accountability, or proof that the underlying issue has been resolved." }, { "id": "chapter-12-client-management::chapter-12-client-management-connections-4", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-12-client-management-connections-4", "url": "#chapter-12-client-management-connections-4", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Governance: Use Frameworks 2, 5, 6, and 8 to connect role, scope, contract, and change authority. - Leadership: Use Chapter 7 for conflict, psychological safety, power, and team dynamics. - Evidence: Use Framework 9 to close the feedback loop and retain a proportionate decision record. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-overview-5", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-12-client-management-overview-5", "url": "#chapter-12-client-management-overview-5", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The project scoping template is an author-created planning aid for making purpose, deliverables, assumptions, constraints, dependencies, risk, budget, exclusions, and authority reviewable. PMI terminology informs the boundary, but the fields and examples are not a PMI-prescribed form. [BB-C12-S03]" }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-12-client-management-how-to-apply-5", "url": "#chapter-12-client-management-how-to-apply-5", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "PMI defines a project scope statement as a description of project scope, major deliverables, assumptions, and constraints. [BB-C12-S03] The template below is an author-created planning aid that adds decision, governance, budget, dependency, risk, and exclusion prompts; it is not a PMI-prescribed form. Purpose: Establish a reviewable working boundary before work starts. [BB-C12-S03] Typical Scoping Document (1-2 pages):" }, { "id": "chapter-12-client-management::chapter-12-client-management-project-charter", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Project Charter", "headingId": "chapter-12-client-management-project-charter", "url": "#chapter-12-client-management-project-charter", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Project Name: [Clear name] - Sponsor: [Executive owner] - Duration: [Start date - End date] - Budget: $[X] (or FTE allocation)" }, { "id": "chapter-12-client-management::chapter-12-client-management-business-objective", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Business Objective", "headingId": "chapter-12-client-management-business-objective", "url": "#chapter-12-client-management-business-objective", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Problem: [What's broken/opportunity] - Goal: [Specific outcome] (e.g., \"Reduce customer onboarding time from 3 weeks to 3 days\") - Success Metric: [How we measure] (e.g., \"90 percent of customers onboard in under 3 days by June 30\")" }, { "id": "chapter-12-client-management::chapter-12-client-management-scope-included", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Scope - INCLUDED", "headingId": "chapter-12-client-management-scope-included", "url": "#chapter-12-client-management-scope-included", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 12.6 — Constructed included-scope register. Items, descriptions, owners, and examples are fictional teaching assumptions. | Item | Description | Owner | |------|-------------|-------| | Requirements gathering | Interview 10+ customer-facing teams | Client PM + Consultant | | Current process mapping | Document existing onboarding process | Client ops team | | Technology evaluation | Assess 5 tools against criteria | Consultant + IT | | Pilot implementation | Deploy solution with 1 customer segment | Joint team | | Training materials | Create guides, videos, FAQs | Consultant + Client training | | Go-live support | 2 weeks on-site support | Consultant |" }, { "id": "chapter-12-client-management::chapter-12-client-management-scope-not-included", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Scope - NOT INCLUDED", "headingId": "chapter-12-client-management-scope-not-included", "url": "#chapter-12-client-management-scope-not-included", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 12.7 — Constructed excluded-scope register. Exclusions and alternatives are fictional teaching assumptions. | Item | Why | Alternative | |------|-----|-------------| | Data migration from legacy system | Out of scope; owned by IT separately | Legacy system team to provide migration plan | | Custom development | Assuming COTS solution; custom would exceed budget | Client to decide if custom worth cost | | 24/7 ongoing support post-go-live | Consulting project, not operations | Define transition plan to Client support team |" }, { "id": "chapter-12-client-management::chapter-12-client-management-key-assumptions", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Key Assumptions", "headingId": "chapter-12-client-management-key-assumptions", "url": "#chapter-12-client-management-key-assumptions", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- \"Assumes 2 key Client stakeholders available for 5 hours/week\" - \"Assumes business rules stable (no major policy changes during project)\" - \"Assumes approval of budget by Month 1\"" }, { "id": "chapter-12-client-management::chapter-12-client-management-dependencies", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Dependencies", "headingId": "chapter-12-client-management-dependencies", "url": "#chapter-12-client-management-dependencies", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- \"Completion of current legacy system project (due June 1)\" - \"IT approval for new tool (dependency on approval process)\"" }, { "id": "chapter-12-client-management::chapter-12-client-management-timeline", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Timeline", "headingId": "chapter-12-client-management-timeline", "url": "#chapter-12-client-management-timeline", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Month 1: Discovery & requirements - Month 2: Technology selection & design - Month 3: Pilot with one customer segment - Month 4: Full rollout & training" }, { "id": "chapter-12-client-management::chapter-12-client-management-budget", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Budget", "headingId": "chapter-12-client-management-budget", "url": "#chapter-12-client-management-budget", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Consulting fees: $150K - Software licenses: $30K/year - Training: $20K - Total: $200K (project) + $30K/year (ongoing)" }, { "id": "chapter-12-client-management::chapter-12-client-management-risks-mitigation", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Risks & Mitigation", "headingId": "chapter-12-client-management-risks-mitigation", "url": "#chapter-12-client-management-risks-mitigation", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 12.8 — Constructed scoping-risk register. Risks and mitigations are fictional teaching assumptions. | Risk | Mitigation | |------|-----------| | Scope creep from new feature requests | Change control process; all new requests require sponsor approval | | Stakeholder misalignment on priorities | Monthly steering committee; decisions documented | | Delays in approval cycle | Named decision-maker; 5-day approval SLA | Usage: - Draft by Consultant, reviewed by Client leadership - Sign-off by Sponsor + Project Manager - Reference when scope disputes arise - Update quarterly with formal \"scope change\" process ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-12-client-management-so-what-for-managers-5", "url": "#chapter-12-client-management-so-what-for-managers-5", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define what decision, outcome, deliverable, assumption, exclusion, dependency, evidence, authority, and risk the engagement is actually governing. - Treat every date, amount, page count, stakeholder count, SLA, and threshold in the template as a fictional example until it has an owner and evidence. - Use the scope statement to surface tradeoffs and route change; do not treat sign-off as proof of feasibility, legality, consent, or benefits." }, { "id": "chapter-12-client-management::chapter-12-client-management-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-12-client-management-limits-and-critiques-5", "url": "#chapter-12-client-management-limits-and-critiques-5", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A scope document cannot resolve an ambiguous problem, missing authority, impossible dependency, weak evidence, or unpriced commercial risk. - Templates can privilege the sponsor's view and omit affected groups, operational transition, accessibility, privacy, safety, or professional obligations. - Scope boundaries are revisable through authorized evidence; “complete” or “fixed” is not a universal quality test." }, { "id": "chapter-12-client-management::chapter-12-client-management-connections-5", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-12-client-management-connections-5", "url": "#chapter-12-client-management-connections-5", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Project controls: Use Chapter 11 for WBS, schedule, risk, EVM, and change authority. - Problem and strategy: Use Chapter 9 to structure the problem and Chapter 8 to connect outcomes and measures. - Commercial governance: Use Framework 6 for SOW issues and Framework 8 for changes to scope, price, timeline, and acceptance. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-overview-6", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-12-client-management-overview-6", "url": "#chapter-12-client-management-overview-6", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The statement of work (SOW) checklist organizes the products, services, results, assumptions, exclusions, governance, data, intellectual property, term, termination, and authority questions that a deal team and counsel may need to address. It is not a contract, clause library, or complete legal form. [BB-C12-S03]" }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-12-client-management-how-to-apply-6", "url": "#chapter-12-client-management-how-to-apply-6", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "PMI defines a statement of work as a narrative description of the products, services, or results a project will deliver. [BB-C12-S03] The issue categories below are an author-created commercial checklist, not a complete contract form or PMI-prescribed structure. Purpose: Provide a commercial issue checklist for the authorized deal team and counsel. Whether a document is binding, incorporated into another agreement, or complete depends on the contract structure, governing law, authority, and facts. The sample terms below are placeholders, not clause language or recommended defaults. Common issue categories:" }, { "id": "chapter-12-client-management::chapter-12-client-management-1-services-description", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "1. Services Description", "headingId": "chapter-12-client-management-1-services-description", "url": "#chapter-12-client-management-1-services-description", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Paragraph format describing what consultant will do - Example: \"ABC Consulting will facilitate a 4-month strategy engagement with your leadership team to develop a 3-year growth strategy, including market analysis, competitive assessment, and go-to-market recommendations.\"" }, { "id": "chapter-12-client-management::chapter-12-client-management-2-deliverables-specific-measurable", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "2. Deliverables (Specific & Measurable)", "headingId": "chapter-12-client-management-2-deliverables-specific-measurable", "url": "#chapter-12-client-management-2-deliverables-specific-measurable", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Strategic analysis document (30 pages, includes market sizing, competitive positioning) - Go-to-market strategy (including pricing model, channel strategy, sales process) - 3-year financial projections (with sensitivity analysis) - Executive presentation (to board) - Recommendations implementation roadmap" }, { "id": "chapter-12-client-management::chapter-12-client-management-3-timeline", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "3. Timeline", "headingId": "chapter-12-client-management-3-timeline", "url": "#chapter-12-client-management-3-timeline", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Start date: [X] - Duration: [# months] - Key milestones (with dates)" }, { "id": "chapter-12-client-management::chapter-12-client-management-4-fees-expenses", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "4. Fees & Expenses", "headingId": "chapter-12-client-management-4-fees-expenses", "url": "#chapter-12-client-management-4-fees-expenses", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Consulting fee: $[X] per month or $[Y] fixed - Payment terms: Net 30 upon invoice - Expenses: Client reimburses reasonable travel at actual cost (max $X/month)" }, { "id": "chapter-12-client-management::chapter-12-client-management-5-assumptions", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "5. Assumptions", "headingId": "chapter-12-client-management-5-assumptions", "url": "#chapter-12-client-management-5-assumptions", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Client provides access to [X, Y, Z] people/systems - Client decision-makers available [frequency] - Client responsible for implementation (consulting only)" }, { "id": "chapter-12-client-management::chapter-12-client-management-6-exclusions-what-s-not-included", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "6. Exclusions (What's NOT Included)", "headingId": "chapter-12-client-management-6-exclusions-what-s-not-included", "url": "#chapter-12-client-management-6-exclusions-what-s-not-included", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Implementation of recommendations - Custom software development - Ongoing support beyond engagement end date" }, { "id": "chapter-12-client-management::chapter-12-client-management-7-governance", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "7. Governance", "headingId": "chapter-12-client-management-7-governance", "url": "#chapter-12-client-management-7-governance", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Weekly status calls with [person] - Monthly steering committee with [stakeholders] - Change requests require written approval & may affect timeline/budget" }, { "id": "chapter-12-client-management::chapter-12-client-management-8-confidentiality-data-records-and-ip", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "8. Confidentiality, data, records, and IP", "headingId": "chapter-12-client-management-8-confidentiality-data-records-and-ip", "url": "#chapter-12-client-management-8-confidentiality-data-records-and-ip", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Distinguish client data, personal data, confidential information, background IP, deliverables, tools, licenses, models, open-source components, retention/deletion, security, privilege, publicity, and compelled disclosure. - Counsel should draft the allocation; consultant ownership is not a universal default." }, { "id": "chapter-12-client-management::chapter-12-client-management-9-term-suspension-and-termination", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "9. Term, suspension, and termination", "headingId": "chapter-12-client-management-9-term-suspension-and-termination", "url": "#chapter-12-client-management-9-term-suspension-and-termination", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Record dates, notice and cure, convenience/cause rights, work stoppage, fees, transition, data and work-product return, survival, and applicable professional duties. - Notice periods and payment consequences are deal- and jurisdiction-specific." }, { "id": "chapter-12-client-management::chapter-12-client-management-10-authority-and-execution", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "10. Authority and execution", "headingId": "chapter-12-client-management-10-authority-and-execution", "url": "#chapter-12-client-management-10-authority-and-execution", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Verify each signatory's authority, the complete agreement set, required approvals, dates, and execution formalities with counsel. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-12-client-management-so-what-for-managers-6", "url": "#chapter-12-client-management-so-what-for-managers-6", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use an SOW checklist to identify what must be agreed, evidenced, priced, approved, delivered, accepted, protected, or transitioned. - Route legal, tax, employment, data, IP, confidentiality, procurement, regulatory, and professional issues to the qualified authority rather than filling gaps with defaults. - Make assumptions, exclusions, change rights, acceptance, dependencies, records, and termination consequences explicit before delivery begins." }, { "id": "chapter-12-client-management::chapter-12-client-management-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-12-client-management-limits-and-critiques-6", "url": "#chapter-12-client-management-limits-and-critiques-6", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- An SOW checklist cannot substitute for a negotiated agreement, governing law, procurement rules, counsel, or signatory authority. - Fee examples, payment terms, notice periods, support levels, ownership, and liability positions are deal- and jurisdiction-specific. - Commercial clarity does not guarantee feasibility, client value, ethical conduct, data protection, or safe implementation." }, { "id": "chapter-12-client-management::chapter-12-client-management-connections-6", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-12-client-management-connections-6", "url": "#chapter-12-client-management-connections-6", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Scope: Use Framework 5 and Chapter 11 to connect SOW deliverables to scope, WBS, schedule, evidence, and change control. - Stakeholders: Use Frameworks 1 and 2 to identify affected parties, authority, consultation, and approval. - Risk and exit: Use Framework 7 and Framework 10 to surface delivery, relationship, data, professional, and termination risks. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-overview-7", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-12-client-management-overview-7", "url": "#chapter-12-client-management-overview-7", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The risk register is a repository for uncertainty, affected objectives, triggers, owners, responses, residual exposure, and review. The fields, categories, scores, and examples below are constructed aids; ordinal scores do not quantify probability, loss, or safety exposure. [BB-C12-S03]" }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-12-client-management-how-to-apply-7", "url": "#chapter-12-client-management-how-to-apply-7", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "PMI defines a risk register as a repository for outputs of risk-management processes and separately defines risk owners, responses, and mitigation. [BB-C12-S03] The template, fields, categories, and scoring convention below are author-created examples rather than a PMI-prescribed register. Purpose: Record uncertainty, affected objectives, triggers, owners, responses, residual exposure, and review. Ordinal scores support prioritization but do not quantify probability or loss. Template: Table 12.3 — Constructed risk register. Entries, labels, scores, responses, names, and statuses are teaching assumptions, not measured exposure. | Risk | Probability | Impact | Score | Mitigation | Owner | Status | |------|-------------|--------|-------|-----------|-------|--------| | Key stakeholder departing | Medium | High | 6 | Document decisions weekly; cross-train 2 people | PM | Active | | Budget approval delays | High | Medium | 6 | Engage CFO early; have contingency plan | Sponsor | Active | | Scope creep from new requests | High | Medium | 6 | Change control process; weekly steering review | PM | Active | | Technology not proven for use case | Medium | High | 6 | Pilot with test data first; vendor reference calls | Tech lead | Active | | Team resource conflict | Medium | Medium | 4 | Define allocation in scoping; escalation path | HR/Manager | Monitoring | Table note: All risks, labels, scores, responses, names, and statuses are constructed examples. Scoring: - Probability: Low (1), Medium (2), High (3) - Impact: Low (1), Medium (2), High (3) - Score = Probability × Impact (max 9) Mitigation Categories: - Avoid: Eliminate the risk (e.g., choose proven technology) - Mitigate: Reduce probability or impact (e.g., have backup resources) - Accept: Risk is acceptable; document decision - Transfer: Move to partner/vendor (e.g., software provider supports integration) Review cadence: Set from risk velocity, decision timing, phase, obligations, and trigger events; no universal weekly/monthly cadence applies. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-12-client-management-so-what-for-managers-7", "url": "#chapter-12-client-management-so-what-for-managers-7", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Give each material uncertainty an owner, trigger, response, residual-risk decision, evidence need, and review route. - Use ordinal scores only as a clearly defined local triage aid; investigate correlation, dependency, severity, opportunity, and decision value separately. - Escalate when authority, safety, legal, regulatory, financial, client, or operational exposure requires it, not merely because a score crosses a universal cutoff." }, { "id": "chapter-12-client-management::chapter-12-client-management-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-12-client-management-limits-and-critiques-7", "url": "#chapter-12-client-management-limits-and-critiques-7", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A risk register can omit unknowns, normalize weak evidence, or imply false precision when categories and scales are not defined. - Mitigation can create secondary risks or shift exposure; record residual, transferred, accepted, and emerging effects. - A register does not replace safety, security, legal, financial, privacy, professional, or specialist controls." }, { "id": "chapter-12-client-management::chapter-12-client-management-connections-7", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-12-client-management-connections-7", "url": "#chapter-12-client-management-connections-7", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Scope and change: Use Frameworks 5 and 8 plus Chapter 11 to connect risks to baselines, dependencies, capacity, and authorized changes. - Stakeholders: Use Framework 1 to identify who bears harm, supplies evidence, owns response, or must be consulted. - Client governance: Use Framework 6 and Chapter 11 to align risk acceptance, commercial obligations, escalation, and evidence. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-overview-8", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-12-client-management-overview-8", "url": "#chapter-12-client-management-overview-8", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The change request process records a proposed change, tests whether it is already required, assesses value and impacts, routes the authorized decision, updates affected controls, and validates the result. It is a tailored governance aid, not a universal CCB or contract rule. [BB-C12-S03]" }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-12-client-management-how-to-apply-8", "url": "#chapter-12-client-management-how-to-apply-8", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Identify and document a proposed change, route it for approval or rejection, and update affected baselines through formal change control. [BB-C12-S03] The workflow below also checks the actual contract, delegated authority, impacts, priority, capacity, communication, and validation. 3-Gate Process:" }, { "id": "chapter-12-client-management::chapter-12-client-management-gate-1-request-submission", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Gate 1: Request Submission", "headingId": "chapter-12-client-management-gate-1-request-submission", "url": "#chapter-12-client-management-gate-1-request-submission", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Who: Client stakeholder - Format: Simple form: \"What change, why needed, impact if not done?\" - Trigger: Any scope expansion, timeline shift, resource change Example Change Request: - Title: Add API integration requirement - Description: Customer requests ability to sync data with their CRM - Impact: Currently not planned; would require 3-week development effort - Cost: $30K and delays launch by 3 weeks - Requestor: VP Sales (high power stakeholder)" }, { "id": "chapter-12-client-management::chapter-12-client-management-gate-2-evaluation", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Gate 2: Evaluation", "headingId": "chapter-12-client-management-gate-2-evaluation", "url": "#chapter-12-client-management-gate-2-evaluation", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Who: Project Manager + Sponsor review - Questions: - Is this in original scope? (If yes, simple answer) - What's the business impact of NOT doing this? - What's the cost/timeline impact of doing this? - Can we phase it (do later instead of now)? - Decision: Approve as submitted, approve with modifications, or defer to Phase 2" }, { "id": "chapter-12-client-management::chapter-12-client-management-gate-3-documentation-execution", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Gate 3: Documentation & Execution", "headingId": "chapter-12-client-management-gate-3-documentation-execution", "url": "#chapter-12-client-management-gate-3-documentation-execution", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- If approved, update SOW/RACI/timeline - If deferred, add to \"backlog for Phase 2\" - If rejected, document reason (protects against later blame) - Update risk register if change creates new risks Figure 12.2. Client change-authority workflow. PMI's current lexicon defines change control as identifying, documenting, approving, or rejecting modifications and treats baselines as formally controlled. [BB-C12-S03] This author-created teaching diagram adds contract, priority, capacity, dependency, communication, and acceptance checks; an approved out-of-scope request updates every affected commercial and delivery control, not only the SOW. Text equivalent: Record the request and governing authority. Determine whether it is already required by the controlled scope or contract. In either case, assess value, capacity, schedule, cost, quality, risk, data, legal, and stakeholder effects. The authorized decision-maker may approve, reject, defer, or exchange priorities. For approval, update the applicable contract, scope, budget, schedule, roles, baselines, acceptance, risks, and communications before implementation and validation. Key rule: No material change without an authorized record of tradeoffs and affected controls. Time and budget may be unchanged only if the evidence supports that conclusion. Example Dialogue: - Request: \"Can you add a mobile app?\" - Response: \"Sure! That would add 6 weeks and $100K. Do we want to: a) extend timeline, b) reduce something else, or c) deliver mobile in Phase 2?\" - Decision: Client chooses to defer mobile to Phase 2. - Documentation: Updated timeline shared with all stakeholders. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-12-client-management-so-what-for-managers-8", "url": "#chapter-12-client-management-so-what-for-managers-8", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Determine whether the request is already required by controlled scope or contract before treating it as optional scope growth. - Make value, capacity, dependency, cost, schedule, quality, risk, legal, data, stakeholder, acceptance, and communication effects visible. - Record the authorized decision and update every affected control before implementation; validate outcomes afterward." }, { "id": "chapter-12-client-management::chapter-12-client-management-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-12-client-management-limits-and-critiques-8", "url": "#chapter-12-client-management-limits-and-critiques-8", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A change workflow cannot create authority, amend a contract, waive law, or replace specialist approval. - Not every change needs a CCB or formal escalation; the route depends on materiality, delegated authority, urgency, and obligations. - “Approve” does not prove feasibility, value, consent, safety, data protection, or successful delivery." }, { "id": "chapter-12-client-management::chapter-12-client-management-connections-8", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-12-client-management-connections-8", "url": "#chapter-12-client-management-connections-8", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Commercial scope: Use Frameworks 5 and 6 to connect scope, SOW, price, acceptance, and termination implications. - Project controls: Use Chapter 11 for baselines, CPM, EVM, risk, and change authority. - Communication and relationship: Use Frameworks 1, 3, 4, and 9 to communicate, negotiate, listen, and close the feedback loop. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-overview-9", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-12-client-management-overview-9", "url": "#chapter-12-client-management-overview-9", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The feedback collection methods menu combines meeting questions, pulse checks, interviews, and retrospectives to investigate client experience and identify issues. It is an author-created teaching synthesis: cadences, scales, sample sizes, triggers, and tools are illustrative—not universal measurement standards—and must be adapted for consent, accessibility, confidentiality, power dynamics, and decision use." }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-12-client-management-how-to-apply-9", "url": "#chapter-12-client-management-how-to-apply-9", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Collect decision-useful feedback and close the loop without treating a score as a universal measure. This purpose statement is author-created; the difficult-conversation source cited elsewhere in this chapter does not establish feedback cadences, scales, sample sizes, triggers, or tools. 4-Tier Feedback System:" }, { "id": "chapter-12-client-management::chapter-12-client-management-tier-1-real-time-feedback-in-meetings", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Tier 1: Real-Time Feedback (In meetings)", "headingId": "chapter-12-client-management-tier-1-real-time-feedback-in-meetings", "url": "#chapter-12-client-management-tier-1-real-time-feedback-in-meetings", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Method: \"How are we doing so far?\" question every meeting - Cadence: Weekly - Duration: 2-3 minutes - Response format: Simple thumbs up/sideways/down or 1-10 scale - Action: If issue mentioned, add to parking lot for discussion" }, { "id": "chapter-12-client-management::chapter-12-client-management-tier-2-weekly-pulse-check-2-3-questions", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Tier 2: Weekly Pulse Check (2-3 questions)", "headingId": "chapter-12-client-management-tier-2-weekly-pulse-check-2-3-questions", "url": "#chapter-12-client-management-tier-2-weekly-pulse-check-2-3-questions", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Method: Simple Slack/email feedback form - Cadence: Every Friday - Questions: 1. How clear are project goals? (1-5) 2. How aligned is the team? (1-5) 3. Biggest concern this week? (free text) - Time: 1 minute to complete - Action: PM reviews, escalates any scores <3" }, { "id": "chapter-12-client-management::chapter-12-client-management-tier-3-mid-project-feedback-formal", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Tier 3: Mid-Project Feedback (Formal)", "headingId": "chapter-12-client-management-tier-3-mid-project-feedback-formal", "url": "#chapter-12-client-management-tier-3-mid-project-feedback-formal", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Method: In-depth feedback form + 1:1 interviews - Cadence: Halfway through project - Coverage: Ask 8-10 people (mix of levels) - Questions: - How well have we understood your needs? - What's working well? What's not? - Are we on track? Any concerns? - Output: Feedback summary + action plan" }, { "id": "chapter-12-client-management::chapter-12-client-management-tier-4-retrospective-post-project", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Tier 4: Retrospective (Post-Project)", "headingId": "chapter-12-client-management-tier-4-retrospective-post-project", "url": "#chapter-12-client-management-tier-4-retrospective-post-project", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Method: Group discussion + feedback form - Timing: Within 2 weeks of project completion - Participants: Client + Consultant team - Topics: - What worked well? - What could improve? - Deliverables met expectations? - Would you work with us again? Why/why not? - Output: Lessons learned; improvements for next engagement Feedback Loop Closure: Always communicate what you heard and what you're doing about it (\"You mentioned communication could be better, so we're adding weekly summary emails\"). Digital Age: Use tools like Typeform for feedback forms (integrates with Slack); track feedback in Confluence. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-12-client-management-so-what-for-managers-9", "url": "#chapter-12-client-management-so-what-for-managers-9", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Collect feedback only when the question, respondent, consent, confidentiality, accessibility, and decision use are clear. - Combine qualitative context with quantitative signals; do not turn a pulse score, NPS, or satisfaction label into a causal or performance claim. - Tell people what was heard, what will change, what will not change, who decides, and how to raise a concern safely." }, { "id": "chapter-12-client-management::chapter-12-client-management-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-12-client-management-limits-and-critiques-9", "url": "#chapter-12-client-management-limits-and-critiques-9", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Feedback can be biased by power, sampling, fear, fatigue, accessibility, incentives, wording, timing, and confidentiality. - A higher score does not prove value, safety, quality, inclusion, retention, or causation; a lower score does not identify the remedy. - Feedback collection can harm trust if it extracts information without consent, protection, action, or transparent limits." }, { "id": "chapter-12-client-management::chapter-12-client-management-connections-9", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-12-client-management-connections-9", "url": "#chapter-12-client-management-connections-9", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Stakeholders: Use Framework 1 to identify who is absent, affected, vulnerable, or entitled to a response. - Communication: Use Framework 3 to turn feedback into an evidence-aware decision brief. - Governance: Use Frameworks 5, 6, 7, and 8 to connect feedback to scope, contract, risk, and change decisions. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-overview-10", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Overview", "headingId": "chapter-12-client-management-overview-10", "url": "#chapter-12-client-management-overview-10", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The relationship mapping tool is an author-created aid for stating and testing hypotheses about formal authority, informal influence, dependencies, concerns, and communication routes. The map is not a license to infer motive, label dissent as obstruction, bypass representation, or disclose private or confidential information." }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How to Apply", "headingId": "chapter-12-client-management-how-to-apply-10", "url": "#chapter-12-client-management-how-to-apply-10", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: State and test relationship hypotheses while protecting rights, privacy, representation, and professional boundaries. This purpose statement is author-created; the professional-services source cited elsewhere in this chapter does not establish relationship-network mapping, influence hypotheses, or privacy safeguards. Table 12.1 — Constructed relationship-map hypotheses. The arrows and labels are hypotheses to validate, not facts about motive, authority, or allegiance. | From | To | Relationship hypothesis | Validation and guardrail | |---|---|---|---| | Executive Sponsor (CEO) | CFO | Formal budget and decision route | Verify authority, required approvals, and affected groups | | CFO | VP Operations | Budget dependency and operational concern | Validate the dependency; do not infer opposition from concern | | Project Manager | Chief Architect | Delivery coordination and technical influence | Check decision rights, expertise, confidentiality, and escalation | | Project Manager | Team Leads | Work coordination and information route | Confirm representation, workload, and safe challenge channels | Elements:" }, { "id": "chapter-12-client-management::chapter-12-client-management-power-influence-connections", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Power/Influence Connections", "headingId": "chapter-12-client-management-power-influence-connections", "url": "#chapter-12-client-management-power-influence-connections", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- →: Formal authority (CEO directs CFO) - ← →: Peer relationship (VP Ops & CIO peer pressure) - ← ← ←: Influence without authority (Architect advises CFO)" }, { "id": "chapter-12-client-management::chapter-12-client-management-individual-assessments", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Individual Assessments", "headingId": "chapter-12-client-management-individual-assessments", "url": "#chapter-12-client-management-individual-assessments", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 12.4 — Constructed relationship assessment. Ratings and attitudes are hypotheses to validate, not facts about people. | Stakeholder | Role | Power | Interest | Attitude | Key Concern | |-------------|------|-------|----------|----------|------------| | CEO | Sponsor | High | High | Champion | ROI, timeline | | CFO | Budget gatekeeper | High | Medium | Skeptical | Cost overruns | | VP Ops | Department head | Medium | High | Resistant | Change disruption | | Chief Architect | Technical leader | Medium | High | Supportive | Technical feasibility |" }, { "id": "chapter-12-client-management::chapter-12-client-management-coalition-strategy", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Coalition Strategy", "headingId": "chapter-12-client-management-coalition-strategy", "url": "#chapter-12-client-management-coalition-strategy", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Supporters: CEO + Architect (get early and often) - Skeptics: CFO (frequent, fact-based updates) - Resistors: VP Ops (involve in design, address concerns early) - Informals: Key team members (understand real dynamics)" }, { "id": "chapter-12-client-management::chapter-12-client-management-influence-tactics-by-stakeholder-type", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Influence Tactics by Stakeholder Type", "headingId": "chapter-12-client-management-influence-tactics-by-stakeholder-type", "url": "#chapter-12-client-management-influence-tactics-by-stakeholder-type", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For Supporters: - Ask for help/advice (increases commitment) - Give credit publicly - Use as advocates with skeptics For Skeptics: - Address concerns head-on with data - Involve in decisions (ownership) - Show quick wins to build confidence For Resistors: - Understand root cause of resistance - Involve in solution design (often reduces resistance) - Celebrate any wins in their area - Never bypass them (will derail project) Implementation: 1. Map all stakeholders (visual) 2. Assess attitude (champion, supporter, skeptic, resistor, blocker) 3. Identify key influencers 4. Design engagement strategy for each group 5. Revisit monthly; people's attitudes change ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "So What for Managers", "headingId": "chapter-12-client-management-so-what-for-managers-10", "url": "#chapter-12-client-management-so-what-for-managers-10", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use relationship maps to identify decision paths, dependencies, communication routes, and missing perspectives—not to diagnose personality or motive. - Validate formal authority, informal influence, and coalition hypotheses with the people affected and the governing instruments. - Revisit the map when decisions, incentives, staffing, relationships, risks, or representation change." }, { "id": "chapter-12-client-management::chapter-12-client-management-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Limits and Critiques", "headingId": "chapter-12-client-management-limits-and-critiques-10", "url": "#chapter-12-client-management-limits-and-critiques-10", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Network maps can expose or reproduce privacy, labor, professional, confidentiality, retaliation, and power risks. - Arrows, labels, ratings, and “supporter/resistor” categories are hypotheses, not facts or permission to bypass people. - Informal influence does not replace formal authority, consent, accountability, or safe participation." }, { "id": "chapter-12-client-management::chapter-12-client-management-connections-10", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Connections", "headingId": "chapter-12-client-management-connections-10", "url": "#chapter-12-client-management-connections-10", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Stakeholders: Use Framework 1 to connect relationship hypotheses to rights, salience, harm exposure, and participation. - Governance: Use Frameworks 2, 6, 7, and 8 to connect influence to authority, contract, risk, and change routes. - Leadership: Use Chapter 7 for power, conflict, psychological safety, and team dynamics. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-why-this-matters-mental-models-client-wisdom", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Why This Matters: Mental Models & Client Wisdom", "headingId": "chapter-12-client-management-why-this-matters-mental-models-client-wisdom", "url": "#chapter-12-client-management-why-this-matters-mental-models-client-wisdom", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Client management is where technical excellence meets human dynamics. Understanding why stakeholder frameworks work—and why they fail—is critical for preventing project derailment. This section explores the psychology of stakeholder engagement, examines relationship failures, and compares competing philosophies." }, { "id": "chapter-12-client-management::chapter-12-client-management-1-what-raci-can-and-cannot-clarify", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "1. What RACI can and cannot clarify", "headingId": "chapter-12-client-management-1-what-raci-can-and-cannot-clarify", "url": "#chapter-12-client-management-1-what-raci-can-and-cannot-clarify", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "RACI can expose an unnamed work owner, missing consultation, or poor communication. It does not prove that multiple accountabilities cause diffusion, and the social-psychology bystander effect should not be transferred into an organizational law without evidence. The coordination principle: Name who coordinates the work and decision, then record every governing authority, required approval, contributor, affected party, and recipient. The emergency contact may be different from the legal or final decision authority. Authority vs. Responsibility: RACI distinguishes doing the work (R) from owning the outcome (A). This matters because the person doing the work often isn't empowered to make decisions. Separating R and A surfaces this gap early. Example: A product launch has unclear ownership: - Product team thinks Marketing is accountable (they're doing the campaign) - Marketing thinks Product is accountable (it's their product) - Result: No one books the launch venue, reserves PR, or coordinates timing RACI prompts the team to verify who coordinates the launch and who actually holds each approval. Clarity can reduce avoidable handoff confusion, but execution still depends on evidence, capability, incentives, and controls. Why It Works: It prompts explicit work, decision, approval, and communication roles. If authority is unclear, verify the governing process before execution rather than assuming a RACI label creates it. Why It Fails: When the matrix conflicts with actual law, governance, contract, delegated authority, or a genuinely collective decision. A single “A” can clarify some tasks, but committees, boards, dual controls, and multiple required approvals can be legitimate. Document the real decision rule instead of forcing false singularity. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-2-why-stakeholder-mapping-works-influence-and-interest-dynamics", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "2. Why Stakeholder Mapping Works: Influence and Interest Dynamics", "headingId": "chapter-12-client-management-2-why-stakeholder-mapping-works-influence-and-interest-dynamics", "url": "#chapter-12-client-management-2-why-stakeholder-mapping-works-influence-and-interest-dynamics", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Stakeholder mapping is a provisional attention aid, not a ranking of human worth or rights. Power and interest do not capture legitimacy, expertise, dependency, representation, legal rights, public interest, or potential harm. Power Asymmetry: Formal authority and informal influence can be unevenly distributed. A finance officer may hold budget authority while frontline staff hold operational evidence, safety knowledge, protected rights, or implementation dependence. Engagement should follow the decision, rights, evidence, and harm—not power alone. Interest Levels: Engagement is effortful, but interest does not reliably predict reading behavior or information need. Tailor format and cadence through accessibility, role, decision need, legal notice, risk, preference, and feedback rather than assuming a quadrant determines attention. Quadrant Logic: - High Power, High Interest: verify authority, conflicts, information needs, and decision role; close engagement may be appropriate. - High Power, Low Interest: agree a concise cadence and exception path without presuming indifference or withholding required detail. - Lower Formal Power, High Interest: include relevant expertise, dependency, rights, representation, and harm; “low power” does not mean no veto, remedy, or decision role. - Lower Formal Power, Lower Expressed Interest: monitor context and provide accessible notice or engagement where rights, impact, safety, or public obligations require it. Potential value: The map can expose mismatches between decision authority, evidence, impact, and current engagement. It should not be used to dismiss lower-power groups or optimize only sponsor support. Why It Fails: When labels become fixed or obscure rights, informal influence, harm, and changing context. Update at decision-relevant events rather than relying on a universal quarterly cadence. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-3-why-communication-cadences-work-expectation-management", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "3. Why Communication Cadences Work: Expectation Management", "headingId": "chapter-12-client-management-3-why-communication-cadences-work-expectation-management", "url": "#chapter-12-client-management-3-why-communication-cadences-work-expectation-management", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Regular communication can improve predictability and coordination, but it does not create psychological safety or guarantee tolerance of uncertainty. Content, credibility, voice, confidentiality, decision rights, prior experience, and the ability to challenge or escalate also matter. Predictability Reduces Anxiety: A known update window may help some stakeholders plan attention. Others need event-triggered notice, different accessibility, confidentiality, or faster escalation. Test preferences and obligations rather than treating cadence as an anxiety intervention. Information Hierarchy: Different stakeholders need different levels of detail: - Executives: \"Are we on track? Red/yellow/green status.\" - Functional leaders: \"What decisions do I need to make this week?\" - Team members: \"What blockers exist?\" Communication plans can differentiate content by decision need, but monthly/weekly/daily patterns are constructed examples, not a hierarchy or universal cadence. Example: A project without cadences: - Month 1: PM sends 5 emails to CEO - Month 2: PM sends 0 emails to CEO - Month 3: CEO asks \"what's happening?\" (PM assumed \"no news is good news\") With cadences: - Every month: PM sends 1-page summary to CEO on Friday at 3 PM - CEO knows: \"If it's Friday at 3 PM, I'll hear from the PM\" Potential value: A reliable cadence can reduce ad hoc status requests when content, timing, ownership, and exception triggers meet stakeholder needs. Why It Fails: When cadence becomes ritual, suppresses material event-triggered disclosure, or delivers low-quality information. One missed update does not automatically break trust, and content, candor, accessibility, and recovery can matter more than mechanical consistency. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-4-why-escalation-protocols-work-rapid-decision-making", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "4. Why Escalation Protocols Work: Rapid Decision-Making", "headingId": "chapter-12-client-management-4-why-escalation-protocols-work-rapid-decision-making", "url": "#chapter-12-client-management-4-why-escalation-protocols-work-rapid-decision-making", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Escalation protocols can clarify triggers, authority, evidence, and response paths; they do not prevent bottlenecks or replace judgment, emergency duties, legal reporting, or direct access to protected channels. Decision Latency: Decision delay is one project risk among many. Set escalation triggers from consequence, urgency, authority, contract, safety, and legal obligations rather than a universal 48-hour rule. Escalation Paths: Clear paths prevent \"escalation ping-pong\": \"I escalated to my manager, who escalated to their manager, who said it's not their decision, escalate to Finance.\" A protocol says: \"For budget issues: PM → Sponsor → CFO. For scope issues: PM → Product Owner → Steering Committee.\" Example: A vendor misses a deadline. Without escalation protocol: - PM waits 1 week hoping vendor recovers - PM mentions it to sponsor in weekly meeting (Week 2) - Sponsor says \"handle it\" (not clear if this is direction or abdication) - PM negotiates with vendor (Week 3-4), gets nowhere - PM escalates again to sponsor (Week 5), who finally involves legal - Total delay: 5 weeks With escalation protocol: - \"If vendor misses deadline, escalate within 24 hours to Sponsor\" - \"Sponsor decides within 48 hours: Accept delay, replace vendor, or invoke penalties\" - Delay: 3 days Potential value: A well-designed path can reduce avoidable routing delay. Decisions do not happen automatically; the authorized owner still needs adequate evidence, capacity, and accountability. Why It Fails: When protocols aren't followed. If the PM escalates and the sponsor doesn't respond within the SLA (48 hours), the protocol becomes meaningless. Enforcement requires leadership accountability. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-composite-teaching-scenarios-when-client-management-breaks-down", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite Teaching Scenarios: When Client Management Breaks Down", "headingId": "chapter-12-client-management-composite-teaching-scenarios-when-client-management-breaks-down", "url": "#chapter-12-client-management-composite-teaching-scenarios-when-client-management-breaks-down", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The following cases are fictional composites created to test governance, scope, and escalation choices. They are not accounts of a named consulting firm or client, and their timing, staffing, budgets, dialogue, and outcomes are illustrative rather than empirical." }, { "id": "chapter-12-client-management::chapter-12-client-management-composite-case-1-unclear-accountability", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite Case 1: Unclear Accountability", "headingId": "chapter-12-client-management-composite-case-1-unclear-accountability", "url": "#chapter-12-client-management-composite-case-1-unclear-accountability", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Situation: A fictional consulting firm begins a six-month strategy engagement with a large client. The constructed scenario uses three consultants, five client stakeholders, and no agreed responsibility map. What Went Wrong: Month 1: Consultants interviewed stakeholders. Everyone said they were \"involved\" but no one was \"accountable.\" Month 3: Consultants delivered interim findings to the VP of Strategy. VP said: \"This looks good, but check with the CFO—he controls the budget.\" Consultants presented to CFO. CFO said: \"Strategy looks fine, but Operations needs to approve—they'll execute it.\" Consultants presented to COO. COO said: \"I like it, but the CEO needs to sign off.\" Month 5: After presenting to 5 stakeholders, still no decision. Consultants asked: \"Who approves this?\" Answer: \"The steering committee\" (which met quarterly—next meeting in 2 months). Month 6: Engagement ended. No decision made. Client didn't renew contract. Consultants blamed \"client indecision.\" Client blamed \"consultants didn't understand our process.\" What Framework Failed: No RACI. Without a single Accountable stakeholder, every stakeholder had implicit veto power. This created a \"consensus trap\"—everyone needed to agree, so no one could decide. What Would Have Worked: RACI established Week 1: - Accountable: CEO (final decision-maker) - Responsible: Consultants (do the work) - Consulted: CFO, COO, VP Strategy (provide input) - Informed: Steering committee (aware of decision, don't approve) With RACI, consultants present to consulted stakeholders (gather input), then present to CEO (the one Accountable), who decides. No steering committee delay. Lesson: Before client work, map who recommends, decides, approves, advises, and receives notice under the actual governance process. A committee or consensus rule can be legitimate; clarify quorum, reserved matters, tie-breaking, delegated authority, escalation, and decision deadlines rather than assuming collective authority will stall. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-composite-case-2-scope-expansion-and-stakeholder-misalignment", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Composite Case 2: Scope Expansion and Stakeholder Misalignment", "headingId": "chapter-12-client-management-composite-case-2-scope-expansion-and-stakeholder-misalignment", "url": "#chapter-12-client-management-composite-case-2-scope-expansion-and-stakeholder-misalignment", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Situation: A software implementation project had a signed SOW: \"Implement CRM for Sales team, $500K, 6 months.\" Month 3, the VP of Marketing asked: \"Can you also add Marketing automation?\" PM said \"sure\" (trying to be helpful). What Went Wrong: Month 4: Marketing automation requirements added (scope creep). PM didn't update SOW (assumed it was a \"small addition\"). Month 5: Development team realized Marketing automation required 3 additional months. PM went to client sponsor (VP Sales): \"We need timeline extension.\" VP Sales: \"Why? SOW says 6 months.\" PM: \"Marketing asked for additional features.\" VP Sales: \"Marketing isn't paying for this. I have a 6-month deadline.\" Month 6: PM faced impossible choice: 1. Deliver CRM only (Marketing unhappy, but meets SOW) 2. Deliver CRM + partial Marketing automation (both Sales and Marketing unhappy) 3. Delay (Sales unhappy, blames PM) PM chose option 2. Sales got a buggy CRM (rushed). Marketing got incomplete automation (not usable). Both stakeholders rated the project \"failed.\" What Framework Failed: Stakeholder mapping wasn't maintained. VP Marketing was originally Low Power (not sponsor), Low Interest (not in scope). When they showed interest, PM elevated their influence without updating the stakeholder map or escalating to the sponsor (VP Sales). What Would Have Worked: Change control process: - Month 4: VP Marketing requests features - PM: \"That's a scope change. Let me evaluate impact.\" (Runs impact analysis: +$200K, +3 months) - PM presents to sponsor (VP Sales): \"Marketing wants X. Cost: $200K, Timeline: +3 months. Approve as change order or defer to Phase 2?\" - VP Sales decides: \"Defer to Phase 2. We need CRM on time.\" Marketing's request is documented (they feel heard) but not approved (Sales' priorities preserved). Lesson: Stakeholder mapping isn't static. When a stakeholder's interest increases (Low → High), trigger change control. Don't accommodate requests without sponsor approval. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-case-3-executive-decision-stall-escalation-path-missed", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Case 3: Executive Decision Stall - Escalation Path Missed", "headingId": "chapter-12-client-management-case-3-executive-decision-stall-escalation-path-missed", "url": "#chapter-12-client-management-case-3-executive-decision-stall-escalation-path-missed", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Situation: A digital transformation project required executive approval for $10M cloud infrastructure investment. The PM presented to the CTO, who said: \"Looks good. Present to the CIO for IT approval.\" What Went Wrong: Week 1: PM presents to CIO. CIO says: \"I need Finance to approve the budget.\" Week 3: PM presents to CFO. CFO says: \"I need the business case validated by Strategy.\" Week 5: PM presents to Chief Strategy Officer. CSO says: \"This needs board approval.\" Week 8: PM requests board meeting slot. Board meets quarterly; next meeting is 6 weeks away. Week 14: Board approves (finally). Total delay: 14 weeks for a decision that should have taken 1 week. What Framework Failed: Escalation path wasn't defined. PM didn't know: \"Who is the ultimate decision-maker for $10M investments?\" PM discovered this through trial and error (presenting to 5 executives before finding the right one). What Would Have Worked: Escalation protocol defined Week 1 (during project charter): - Investments $10M: Board approval With this protocol: - Week 1: PM knows \"$10M requires board approval\" (not CTO) - Week 2: PM requests board meeting slot (6 weeks ahead) - Week 3-7: PM prepares board materials (while waiting for meeting) - Week 8: Board meeting, decision made Total time: 8 weeks (vs. 14 weeks). Difference: 6 weeks saved by knowing the path upfront. Lesson: Define decision authority BEFORE you need a decision. Include in project charter: \"Who approves scope changes? Who approves budget increases? What's the threshold for board involvement?\" ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-1-stakeholder-centric-vs-task-centric-management", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "1. Stakeholder-Centric vs. Task-Centric Management", "headingId": "chapter-12-client-management-1-stakeholder-centric-vs-task-centric-management", "url": "#chapter-12-client-management-1-stakeholder-centric-vs-task-centric-management", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Stakeholder-Centric: Prioritize relationships over tasks. Invest time building trust, understanding motivations, and managing politics. Philosophy: \"Projects succeed through people, not processes.\" Strengths: - High trust = forgiveness when things go wrong - Political savvy prevents blockers - Stakeholder buy-in ensures adoption Weaknesses: - Time-intensive (1:1s, relationship-building takes hours/week) - Can sacrifice delivery for relationships (\"we're behind schedule, but stakeholders are happy\") - Hard to scale (can't build deep relationships with 50 stakeholders) When to Use: - Political environments (government, large enterprises) - High-visibility projects (board-level scrutiny) - Change management projects (adoption is THE metric) --- Task-Centric: Prioritize execution over relationships. Follow processes (RACI, change control) and let results speak. Philosophy: \"Deliver on time and on budget, stakeholders will be satisfied.\" Strengths: - Efficient (no time wasted on \"relationship management\") - Clear accountability (RACI, not politics) - Scales (processes work with 100 stakeholders) Weaknesses: - Low trust = stakeholders don't give benefit of doubt when issues arise - Misses political dynamics (blockers emerge late) - Low adoption (stakeholders comply but don't commit) When to Use: - Technical projects (engineering, IT, operations) - Low-stakes projects (operational, not strategic) - Mature relationships (trust already established) --- Hybrid (Best Practice): Invest in relationships with high-power stakeholders (Manage Closely quadrant), use processes for others. Example: - Sponsor: Weekly 1:1s (stakeholder-centric) - Steering committee: Monthly formal meetings (process-centric) - Project team: Daily standups (process-centric) ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-2-formal-governance-vs-relationship-based-trust", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "2. Formal Governance vs. Relationship-Based Trust", "headingId": "chapter-12-client-management-2-formal-governance-vs-relationship-based-trust", "url": "#chapter-12-client-management-2-formal-governance-vs-relationship-based-trust", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Formal Governance: Use steering committees, change control boards, formal decision logs. Transparency through process. Philosophy: \"Document everything. Governance creates accountability.\" Strengths: - Audit trail (who decided what, when) - Protects against political shifts (decisions documented, can't be reversed arbitrarily) - Scales (governance works with rotating stakeholders) Weaknesses: - Bureaucracy (decisions take weeks through committees) - Stifles agility (formal change requests slow iteration) - Low engagement (stakeholders attend meetings out of obligation, not interest) When to Use: - Regulated industries (healthcare, finance, government) - Large, multi-division organizations with formal governance dependencies - High-risk projects (failures have legal/financial consequences) --- Relationship-Based Trust: Minimal formal governance. Rely on trust, informal communication, and handshake agreements. Philosophy: \"Trust accelerates decisions. Process slows them down.\" Strengths: - Speed (decisions in 1:1s, not committees) - Flexibility (pivot without formal change requests) - Engagement (stakeholders feel valued, not managed) Weaknesses: - Fragile (if key relationship breaks, project derails) - No audit trail (decisions can be reversed, \"I never agreed to that\") - Doesn't scale (trust requires stable, small group) When to Use: - Startups (small, tight teams) - Stable teams (same stakeholders for years) - Low-risk projects (experimentation, pilots) --- Hybrid (Light Governance with Trust): Use governance for major decisions (scope, budget, timeline) but trust for day-to-day (feature details, priorities). Example: - Scope change: Formal change control (steering committee approval) - Feature prioritization: Informal (PM and Product Owner decide in weekly 1:1) ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-3-frequent-communication-vs-minimal-overhead", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "3. Frequent Communication vs. Minimal Overhead", "headingId": "chapter-12-client-management-3-frequent-communication-vs-minimal-overhead", "url": "#chapter-12-client-management-3-frequent-communication-vs-minimal-overhead", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Frequent Communication: Daily standups, weekly summaries, monthly deep dives. Stakeholders are always informed. Philosophy: \"Transparency builds trust. Communicate often.\" Strengths: - No surprises (stakeholders always know status) - Quick course correction (issues raised daily, not monthly) - Engagement (frequent touchpoints build relationships) Weaknesses: - Overhead (meaningful PM time spent communicating) - Fatigue (stakeholders tune out if updates are repetitive) - Noise (too much communication = stakeholders miss critical updates) When to Use: - High-risk projects (need tight monitoring) - Agile projects (sprint-based, frequent changes) - Stakeholder anxiety (visible project, executives watching closely) --- Lower-Frequency Engagement: Use a lower cadence only when rights, potential harm, decision timing, evidence needs, obligations, accessibility, and escalation paths support it. Silence is not evidence of trust or informed consent. Strengths: - Efficiency (limited PM time spent on communication) - Focus (stakeholders aren't distracted by routine updates) - Trust (assumes stakeholders don't need hand-holding) Weaknesses: - Surprises (stakeholders blindsided by issues) - Anxiety (stakeholders check in constantly: \"Is everything okay?\") - Slow correction (issues discovered late) When to Use: - Low-risk projects (routine, proven processes) - Mature relationships (trust established) - Autonomous teams (don't need frequent oversight) --- Tailored Engagement: Set participation, channel, content, cadence, decision access, accommodation, and escalation for each stakeholder or represented group from rights, legitimacy, harm, impact, expertise, dependency, evidence need, urgency, and applicable obligations. Power/interest quadrants are prompts only: low reported interest does not justify minimal communication, and no weekly, monthly, bi-weekly, or quarterly cadence follows automatically from a quadrant. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-stage-dependency-how-client-management-evolves-with-scale", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Stage Dependency: How Client Management Evolves with Scale", "headingId": "chapter-12-client-management-stage-dependency-how-client-management-evolves-with-scale", "url": "#chapter-12-client-management-stage-dependency-how-client-management-evolves-with-scale", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The stage contrasts below are constructed heuristics, not employee thresholds, maturity stages, or governance prescriptions. Choose structure from coordination load, risk, regulation, interfaces, decision rights, uncertainty, accessibility, and affected populations." }, { "id": "chapter-12-client-management::chapter-12-client-management-startup-informal-relationship-based-management", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Startup: Informal, Relationship-Based Management", "headingId": "chapter-12-client-management-startup-informal-relationship-based-management", "url": "#chapter-12-client-management-startup-informal-relationship-based-management", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Context: This small-team scenario assumes fewer than 20 people, direct communication, and high trust; formal client-management mechanisms may be lighter, but rights, authority, evidence, and affected-party needs still apply. Approach: - Stakeholders: 3-5 people (founders, early customers) - Governance: Informal (daily conversations, no committees) - Communication: Constant (Slack, shared workspace) - RACI: Implicit (founders own everything) Example: A startup with 5 employees launching a product: - Stakeholder management: Daily standups with whole team - Decision-making: Founder decides in real-time - Communication: Slack channel (everyone sees everything) Why It Works: Small teams = low coordination overhead. Everyone knows everyone, trust is high, formal processes add bureaucracy. Failure Mode: When startups scale to 50+ people and keep informal processes → chaos (no one knows who decides, decisions bottleneck at founder). ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-scale-up-emerging-formal-structures", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Scale-Up: Emerging Formal Structures", "headingId": "chapter-12-client-management-scale-up-emerging-formal-structures", "url": "#chapter-12-client-management-scale-up-emerging-formal-structures", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Context: This scale-up scenario assumes 20–200 people, multiple departments, external stakeholders, and increasing coordination complexity; some client-management mechanisms may need to become more explicit. Approach: - Stakeholders: 15-30 people (cross-functional leaders, key customers) - Governance: Emerging (weekly standups + monthly business reviews) - Communication: Structured (weekly summaries, monthly deep dives) - RACI: Explicit (documented for key decisions) Example: A scale-up with $20M revenue managing a product launch: - Stakeholder mapping: 20 stakeholders (Product, Sales, Marketing, Finance, key customers) - RACI: Defined for launch decisions (CMO Accountable, Product and Sales Consulted) - Communication: Weekly email summary to all stakeholders, bi-weekly 1:1s with Manage Closely group - Governance: Monthly steering committee (CMO, CFO, CRO) Why It Works: Formal structures prevent chaos while maintaining agility. Stakeholders know who decides (RACI) and when they'll be updated (cadences). Failure Mode: When scale-ups over-formalize (monthly steering committees become weekly, 5-page memos for every decision) → bureaucracy slows growth. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-enterprise-formal-governance-multiple-stakeholders", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Enterprise: Formal Governance, Multiple Stakeholders", "headingId": "chapter-12-client-management-enterprise-formal-governance-multiple-stakeholders", "url": "#chapter-12-client-management-enterprise-formal-governance-multiple-stakeholders", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Context: This enterprise scenario assumes 1,000+ people, dispersed decision-making, and high accountability needs; governance may need more explicit coordination, review, and escalation, but size alone does not determine the design. Approach: - Stakeholders: 50-100 people (multiple business units, geographies, functions) - Governance: Formal (monthly steering committees, quarterly board updates) - Communication: Tiered (daily team updates, weekly functional leads, monthly executives) - RACI: Mandatory (documented in project charter, audited) Example: An enterprise with $5B revenue implementing a global ERP system: - Stakeholder mapping: 80 stakeholders (BU presidents, regional CIOs, functional VPs, board members) - RACI: Comprehensive (200+ tasks, each with explicit A) - Communication: - Daily: Team standups (20 people) - Weekly: Functional lead syncs (10 people) - Monthly: Steering committee (5 executives) - Quarterly: Board presentation (CEO, CFO, CIO) - Governance: Steering committee makes scope/budget decisions, board approves $10M investments Why It Works: Formal governance ensures accountability at scale. With 80 stakeholders, informal trust doesn't scale. Processes create clarity. Failure Mode: When governance becomes theater (committees meet but don't decide, documentation exists but isn't read) → bureaucracy without accountability. --- Stage Comparison: Table 12.9 — Constructed scale-context comparison. Stakeholder counts, cadences, and governance examples are not maturity benchmarks. | Dimension | Startup | Scale-Up | Enterprise | |-----------|---------|----------|------------| | Stakeholder Count | 3-5 | 15-30 | 50-100 | | Governance | Informal (daily chats) | Emerging (weekly/monthly) | Formal (monthly steering, quarterly board) | | Communication | Constant (Slack) | Structured (weekly summaries) | Tiered (daily/weekly/monthly/quarterly) | | RACI | Implicit (founder owns all) | Explicit (documented for key decisions) | Mandatory (all tasks documented) | | Decision Speed | Hours | Days | Weeks | | Risk of Failure | Informal → chaos as you scale | Under-govern → coordination failures | Over-govern → bureaucracy paralysis | ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-contrarian-thinking-when-client-management-orthodoxy-fails", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Contrarian Thinking: When Client Management Orthodoxy Fails", "headingId": "chapter-12-client-management-contrarian-thinking-when-client-management-orthodoxy-fails", "url": "#chapter-12-client-management-contrarian-thinking-when-client-management-orthodoxy-fails", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The contrasts below are constructed teaching hypotheses and practitioner prompts, not a systematic evidence review or prevalence claim. Replace any empirical or causal claim with inspected, adjacent evidence before publication." }, { "id": "chapter-12-client-management::chapter-12-client-management-1-the-client-is-not-always-right", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "1. The Client Is Not Always Right", "headingId": "chapter-12-client-management-1-the-client-is-not-always-right", "url": "#chapter-12-client-management-1-the-client-is-not-always-right", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Conventional Wisdom: \"The customer is always right. Give clients what they want.\" Contrarian Challenge: Clients often don't know what they need. Your job is to diagnose the real problem, not implement their requested solution. Constructed consumer-product scenario: A product team runs a blind preference test for a reformulated product and interprets the result as approval to replace the incumbent brand. The test did not measure attachment to the existing product, switching behavior, channel reaction, or response to removing choice. This is a hypothetical illustration of construct validity, not a retelling of the New Coke case. What the scenario surfaces: The research answered a narrower sensory-preference question than the replacement decision required. The team should define the actual decision, population, alternatives, behavior, uncertainty, and consequences before treating one measure as customer authorization. Client Management Parallel: Bad consultant: \"You asked for a new CRM system? Here's the RFP for Salesforce.\" Better consultant: “You requested a new CRM. Before selecting a solution, let us test the workflow, data, incentives, capability, and system constraints that may contribute to the observed problem.” Lesson: The professional obligation depends on the engagement and governing duties. The practical principle is to distinguish the requested solution from the evidence-supported problem and to disclose material disagreement. When to Push Back: - Client requests a solution before diagnosing the problem - Client solution won't address root cause (treats symptoms) - Client request violates best practices or will create future problems How to Push Back (Without Burning the Relationship): Framework: \"I understand... and I want to make sure we solve the right problem.\" Example: - Client: \"We need to build a custom analytics platform from scratch.\" - You: \"I understand you want better analytics. Before we commit to a 12-month custom build, let's validate whether off-the-shelf tools (Tableau, Power BI) meet most needs. Custom builds can cost more and take longer. Let's explore both options and compare ROI.\" Practitioner note: Treat customer input as evidence about needs, not as a substitute for diagnosis. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-2-over-communication-can-be-as-harmful-as-under-communication", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "2. Over-Communication Can Be as Harmful as Under-Communication", "headingId": "chapter-12-client-management-2-over-communication-can-be-as-harmful-as-under-communication", "url": "#chapter-12-client-management-2-over-communication-can-be-as-harmful-as-under-communication", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Conventional Wisdom: \"Communicate frequently. Stakeholders want constant updates.\" Contrarian Challenge: Too many status updates create noise, not signal. Busy executives ignore low-value communications, training them to ignore ALL your communications. Constructed attention heuristic: Information Overload Heuristic: - Busy executives receive far more messages than they can carefully process - They open relatively few emails from external consultants - They read even fewer thoroughly - They act on only the clearest asks Result: Low-value communications may be ignored; test attention, comprehension, decision response, and accessibility rather than assuming a universal rate. Root Cause: Low signal-to-noise ratio. If you send daily status emails with trivial updates (\"completed task X, Y, Z\"), executives tune out. When you send a CRITICAL update (major risk, decision needed), they've already developed the habit of ignoring your emails. Client Management Anti-Pattern: Bad practice: - Daily email: \"Today we completed requirements gathering session #3.\" - Daily email: \"Today we completed requirements gathering session #4.\" - Daily email: \"URGENT: Project timeline slipping 2 months due to scope change.\" Result: Executive ignores all three emails (trained to ignore daily noise). Misses the urgent message. Surprised at board meeting when timeline slip is revealed. Good practice: - Week 1: No email (work in progress, nothing to escalate) - Week 2: No email (work in progress) - Week 3: Email: \"Decision needed: Scope expanded materially, which delays timeline 2 months OR we descope features X, Y, Z to maintain timeline. Need your decision by Friday.\" Result: Executive opens email (rare communication = high importance). Makes decision. Project stays on track. Lesson: Communicate strategically, not frequently. Reserve communications for: 1. Decisions needed: Executive must choose between options 2. Risks escalated: Issue beyond your authority to resolve 3. Milestones hit: Major progress worth celebrating 4. Status changed: Red → Yellow or Yellow → Red Don't communicate: - Routine progress (save for weekly summaries) - FYI information (no action required) - Internal team matters (they don't care about your internal staffing) Communication Frequency by Stakeholder Tier: | Stakeholder Tier | Communication Frequency | Method | |-----------------|------------------------|--------| | Sponsor (CEO, CFO) | Monthly + ad hoc for decisions | 1-page executive summary + meetings | | Project Champion | Weekly | Email summary + 30-min meeting | | Steering Committee | Monthly | PowerPoint deck + 1-hour meeting | | Working Team | Daily/Weekly | Slack/email + standups | Practitioner note: Treat executive attention as scarce and design messages for clear action. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-3-stakeholder-alignment-is-often-impossible-and-that-s-ok", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "3. Stakeholder Alignment Is Often Impossible (And That's OK)", "headingId": "chapter-12-client-management-3-stakeholder-alignment-is-often-impossible-and-that-s-ok", "url": "#chapter-12-client-management-3-stakeholder-alignment-is-often-impossible-and-that-s-ok", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Conventional Wisdom: \"Get all stakeholders aligned before proceeding. Consensus is critical.\" Contrarian Challenge: Perfect alignment is a myth. Stakeholders have conflicting incentives. Your job is to manage conflicts, not eliminate them. Constructed alignment scenario, not prevalence evidence: Enterprise software scenario: - A complex project may miss time, budget, or scope expectations when assumptions, dependencies, authority, or evidence are weak. - Stakeholder conflict and analysis paralysis are possible mechanisms to investigate, not universal causes or prevalence claims. Paradox: Trying to eliminate stakeholder conflict creates analysis paralysis, which also causes failure. Client Management Reality: Conflicting Stakeholder Incentives: | Stakeholder | Incentive | Preferred Outcome | |------------|-----------|------------------| | CFO | Minimize cost | Cheapest solution, even if limited features | | CTO | Technical excellence | Best-in-class technology, even if expensive | | COO | Operational stability | No disruption, even if means delaying innovation | | CMO | Speed to market | Launch fast, even if means technical debt | These incentives conflict. You cannot satisfy all four simultaneously. Bad approach: Try to get all four to agree. Spend 6 months in meetings. Make no progress. Project dies from inaction. Good approach: Escalate to decision-maker (CEO). Present trade-offs. Get CEO to prioritize. Accept that 3 stakeholders will be partially unhappy. Decision Framework (for CEO): \"We have four stakeholder groups with conflicting priorities: - CFO wants lowest cost: $500K solution (basic features) - CTO wants best tech: $2M solution (cutting-edge) - COO wants stability: 18-month implementation (no disruption) - CMO wants speed: 6-month implementation (fast to market) Recommendation: $1.2M solution, 12-month implementation (balanced trade-off) - CFO: 2.4x budget (vs. ideal $500K) → Partially unhappy - CTO: Mid-tier tech (not cutting-edge) → Partially unhappy - COO: 12 months (not 18) → Manageable, some risk - CMO: 12 months (not 6) → Partially unhappy ALL stakeholders compromise. But project proceeds. \" Lesson: Don't aim for perfect alignment. Aim for \"good enough\" alignment where the CEO makes a decision and stakeholders accept it (even if they disagree). Red Flag: If stakeholders appear fully aligned without debate, you probably haven't dug deep enough. Surface-level agreement often hides underlying conflicts that will emerge mid-project. Practitioner note: Treat stakeholder alignment as an active risk area, not a one-time kickoff artifact. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-4-client-satisfaction-project-success", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "4. Client Satisfaction ≠ Project Success", "headingId": "chapter-12-client-management-4-client-satisfaction-project-success", "url": "#chapter-12-client-management-4-client-satisfaction-project-success", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Conventional Wisdom: \"If the client is happy, the project succeeded.\" Contrarian Challenge: Clients can be very satisfied with projects that fail to deliver business value. Satisfaction is a lagging indicator measured too early. Constructed outcome-measure scenario: Consulting impact pattern: - A consulting project can receive positive feedback at completion while its later business value remains uncertain. - Outcome evidence may be harder to obtain after delivery; define ownership, timing, attribution, and measurement before treating a satisfaction signal as impact. Why the Gap? Satisfaction is measured at delivery (Month 6), not at impact (Month 18). Example: Project: Digital transformation (new e-commerce platform) Month 6 (Project End): - Delivered on time, on budget - Platform looks great, modern UI - Client satisfaction score: 9/10 (\"Excellent work!\") - Consultant celebrates, moves to next client Month 18 (12 months post-launch): - E-commerce revenue: +5 percent (below 20 percent target) - Conversion rate: Flat (no improvement) - Customer complaints: Up 30 percent (platform harder to use than old one) Root cause: Platform was beautifully designed but didn't address real customer pain points (checkout friction, mobile experience). Consultant optimized for client satisfaction (impressive demos), not customer outcomes (revenue). Lesson: Measure success by business outcomes, not client satisfaction. Satisfaction is necessary but not sufficient. Success Metrics Hierarchy: 1. Tier 1 (Outcomes): Revenue, profit, cost savings, customer retention 2. Tier 2 (Outputs): Features delivered, systems deployed, processes redesigned 3. Tier 3 (Satisfaction): Client feedback scores, relationship strength Constructed heuristic: Teams may overemphasize Tier 3 because it is available at closeout; pair satisfaction with outcome, output, risk, adoption, and attribution evidence rather than ranking projects by one tier. How to Align on Outcomes: At project kickoff, define success metrics: - Bad: \"Deliver CRM system\" (output) - Good: \"Increase sales productivity 20 percent (measured by revenue per rep)\" (outcome) Track metrics throughout: - Month 3: Early indicators (CRM adoption rate) - Month 6: Intermediate indicators (pipeline growth) - Month 12: Outcome indicators (revenue per rep) Client Management Implication: Sometimes you need to make clients UNHAPPY in the short term to drive long-term outcomes. Example: - Client wants to skip user training (speeds up launch) - You insist on training (delays launch 1 month) - Client frustrated (satisfaction drops) - 6 months later: High user adoption relative to the target - Outcomes achieved Practitioner note: Validate consulting impact against business outcomes, not only closeout sentiment. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-5-re-scope-suspend-or-exit-an-engagement-through-governance", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "5. Re-scope, suspend, or exit an engagement through governance", "headingId": "chapter-12-client-management-5-re-scope-suspend-or-exit-an-engagement-through-governance", "url": "#chapter-12-client-management-5-re-scope-suspend-or-exit-an-engagement-through-governance", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Conventional Wisdom: \"The client pays your salary. Never fire a client.\" Decision challenge: A relationship can become economically, ethically, operationally, or professionally untenable. Re-scope, suspend, non-renew, or terminate only through the applicable contract, authority, professional duties, transition obligations, and legal review. Evidence: Maister's professional-services work frames management as balancing client service, professional careers, and firm economics; it does not establish a universal client-exit rate or prove that exiting a client will improve morale or profit. [BB-C12-S06] Economics of a Bad Client: Good Client: - Revenue: $500K - Delivery cost: $300K (team time) - Profit: $200K (40 percent margin) - Team satisfaction: High (normal hours, clear scope) Bad Client: - Revenue: $500K (same) - Delivery cost: $600K (scope creep, endless revisions, weekend work) - Profit: -$100K (negative margin!) - Team satisfaction: Low → 2 team members quit → $200K replacement cost Total cost of bad client: -$300K ($100K loss + $200K turnover) Issues requiring review rather than a numeric firing rule: 1. Scope creep: Every request expands beyond SOW, refuses change orders 2. Payment issues: Delinquency, disputed invoices, insolvency risk, or collection concerns under the actual contract and law 3. Abusive behavior: Yells at team, unreasonable demands (weekend calls, 24-hour turnarounds) 4. Misaligned values: Asks you to do unethical work (hide data, mislead stakeholders) 5. Unrealistic expectations: Expects 10x results with 1x budget, blames you for external factors 6. Project failure risk: High likelihood of project failure (bad data, no sponsorship) → Damages your reputation How to govern a possible exit: Step 1: Attempt to salvage (if possible) - Have difficult conversation: \"Our engagement isn't working. Here's why: [scope creep, payment issues]. Here's what needs to change: [clear boundaries, payment terms]. Can we agree?\" - If client agrees and changes behavior → Continue - If client refuses or reverts → Proceed to Step 2 Step 2: Execute an authorized exit if selected - Counsel and accountable leaders determine notice, cure, suspension, non-renewal or termination rights, fees, work completion, transition, data and records, confidentiality, privilege, publicity, and survival obligations. - Communicate accurately and preserve the decision record; do not use a generic letter as a legal script. Step 3: Learn and filter - Post-mortem: What red flags did we miss in sales process? - Update client screening: Add criteria to filter future bad clients Example: Situation: Client consistently scope creeps, refuses change orders, and demands weekend work. Consultant response: \"We value our partnership, but our engagement has expanded significantly beyond the original SOW. We've delivered $800K of work for $500K of revenue. Going forward, we need to operate within the SOW or execute change orders for additional requests. Are you able to commit to this?\" Client response (bad): \"You're being inflexible. We're a high-value client. Just do the work.\" Possible decision: The authorized firm representatives may re-scope, suspend, non-renew, or terminate under the governing agreement after legal and financial review. The sample facts do not determine which remedy is available. Alternative client response (good): \"You're right. Let's set clear boundaries. I'll approve change orders for out-of-scope work.\" Consultant decision: Continue the engagement (with new boundaries). Lesson: Revenue quality, delivery cost, independence, team welfare, client harm, transition duties, and capacity all matter. Exiting can free capacity, but it can also create loss, liability, or harm; model both sides. Practitioner note: Maister's professional-services work supports treating client selection as a strategic management decision, not only a sales decision. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-input-output-interlinkages-how-client-management-connects-to-other-business-functions", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Input/Output Interlinkages: How Client Management Connects to Other Business Functions", "headingId": "chapter-12-client-management-input-output-interlinkages-how-client-management-connects-to-other-business-functions", "url": "#chapter-12-client-management-input-output-interlinkages-how-client-management-connects-to-other-business-functions", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Show how client management inputs come from (and outputs feed into) other business domains." }, { "id": "chapter-12-client-management::chapter-12-client-management-example-enterprise-software-implementation", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Example: Enterprise Software Implementation", "headingId": "chapter-12-client-management-example-enterprise-software-implementation", "url": "#chapter-12-client-management-example-enterprise-software-implementation", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Inputs Required: | Function | Input Provided | Format | |----------|---------------|--------| | Sales | Client expectations (features, timeline, budget) | SOW, contract | | Delivery | Technical feasibility, team capacity, risks | Project plan | | Finance | Budget constraints, payment milestones | Budget spreadsheet | | Legal | Liability limits, IP ownership, SLAs | Contract terms | | HR | Team skills, availability (40 percent allocated to this project) | Resource plan | Client Management Activities: 1. Align stakeholders on scope (manage expectations from Sales) 2. Negotiate timeline (balance delivery capacity with client expectations) 3. Manage scope changes (client requests materially more features mid-project) 4. Escalate payment delays (client delayed payment milestone 2) 5. Request more resources (project needs 60 percent allocation, not 40 percent) Outputs Delivered: | Function | Output Provided | Impact | |----------|----------------|--------| | Sales | Identified upsell: Client wants Phase 2 (expand to 3 more divisions) | +$1.5M revenue opportunity | | Delivery | Approved scope change: Add feature X, descope feature Y | Updated project plan | | Finance | Change order executed: +$200K for scope expansion | Revenue recognized | | Legal | Negotiated SLA amendment: 99.5 percent to 99.9 percent uptime (client paid premium) | Risk mitigated | | HR | Resource request approved: 60 percent allocation for 2 senior engineers | Project adequately staffed | | Marketing | Client proof point: \"How we helped Client X increase productivity 40 percent\" | Lead generation | Interconnections: - Sales → Client Management: Client expectations set during sales process - Client Management → Delivery: Stakeholder decisions enable delivery progress - Delivery → Client Management: Technical constraints require stakeholder trade-offs (time vs. features) - Client Management → Finance: Scope changes generate change orders - Finance → Client Management: Budget constraints limit scope expansion - Client Management → HR: Client satisfaction drives team morale (happy client = happy team) ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-example-management-consulting-engagement", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Example: Management Consulting Engagement", "headingId": "chapter-12-client-management-example-management-consulting-engagement", "url": "#chapter-12-client-management-example-management-consulting-engagement", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Inputs Required: | Function | Input Provided | Format | |----------|---------------|--------| | Sales | Client problem statement: \"Revenue declining, don't know why\" | Proposal, engagement letter | | Delivery | Consulting team expertise (strategy, operations, analytics) | Team bios | | Finance | Engagement budget: $500K, 3 months | Budget, payment terms | | Legal | Confidentiality terms (client data is sensitive) | NDA, contract | Client Management Activities: 1. Refine problem statement: Interviews with 15 stakeholders 2. Align on hypotheses: Why is revenue declining? (5 hypotheses) 3. Prioritize analysis: Focus on top 2 hypotheses (time constraint) 4. Manage interim findings: Present findings Week 4 (early feedback) 5. Navigate politics: CFO wants cost cuts, CMO wants growth investment (conflicting) Outputs Delivered: | Function | Output Provided | Impact | |----------|----------------|--------| | Sales | Renewal: Client wants Phase 2 (implementation support, 6 months, $1.2M) | +$1.2M revenue | | Delivery | Recommendations implemented: 3 of 5 recommendations accepted, 2 rejected | Partial success | | Finance | Impact validated: Revenue increased 12 percent (6 months post-engagement) | ROI proven | | Marketing | Testimonial: \"Consultant helped us turn around our business\" | Brand credibility | | HR | Team morale: High (client praised team, challenging work) | Retention | Interconnections: - Sales → Client Management: Sales sold strategy work; client wanted implementation too (upsell) - Client Management → Delivery: Stakeholder prioritization focused analysis (avoided boiling the ocean) - Delivery → Client Management: Findings created stakeholder conflict (CFO vs. CMO) requiring mediation - Client Management - Marketing: Successful project generates proof points and referrals ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-cross-functional-client-management-challenges", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Cross-Functional Client Management Challenges", "headingId": "chapter-12-client-management-cross-functional-client-management-challenges", "url": "#chapter-12-client-management-cross-functional-client-management-challenges", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Challenge 1: Sales Over-Promised, Delivery Must Under-Deliver Situation: Sales sold \"30 percent cost reduction in 6 months\" to close deal. Delivery team estimates 15 percent reduction in 12 months (realistic). Client Management Problem: Client expects 30 percent in 6 months (per sales). You must reset expectations. Solution: 1. Acknowledge sales promise: \"I understand the proposal mentioned 30 percent cost reduction.\" 2. Present reality: \"Our detailed analysis shows 15 percent is achievable in 12 months. Here's why 30 percent in 6 months isn't feasible: [data, constraints].\" 3. Offer options: - Option A: Deliver 15 percent in 12 months (realistic) - Option B: Pursue 30 percent, but high risk of failure (unrealistic) 4. Escalate to decision-maker: Client CFO decides: \"Let's go with Option A. I'd rather get 15 percent than miss 30 percent.\" Lesson: Client management bridges Sales (promises) and Delivery (reality). Your job: Reset expectations without blame. --- Challenge 2: Client Requests Unethical Work Situation: Client asks you to \"massage the data\" to show positive results in board presentation (actual results are negative). Client Management Problem: Client is your revenue source, but request violates ethics. Solution: 1. Clarify request: \"Just to confirm: You're asking me to present data in a way that hides the negative results?\" 2. State boundary: \"I can't do that. It violates our professional standards and misrepresents reality.\" 3. Offer alternative: \"I can present the data accurately and help you explain the results to the board (e.g., 'Results fell short, here's why, here's our plan to improve').\" 4. Escalate if needed: If client insists, escalate to your firm's leadership or exit the engagement. Lesson: Some client requests are non-negotiable. Protect your professional integrity even if it means losing revenue. --- Challenge 3: Client Delays Payment, Delivery Continues Work Situation: Client is 90 days overdue on $200K invoice. Delivery team continues work (doesn't want to stop mid-project). Client Management Problem: Delivery is exposed to financial risk. Finance wants to halt work. Solution: 1. Align with Finance: Confirm payment policy (e.g., \"No work if 90 days overdue\") 2. Notify client: \"We haven't received payment for Invoice #123 ($200K, 90 days overdue). Per our contract, we must pause work until payment is received.\" 3. Offer payment plan: \"If cash flow is an issue, we can work out a payment plan. But we can't continue work without resolving this.\" 4. Route the boundary: If payment remains unresolved, follow the governing agreement and approved finance/counsel process for notice, cure, suspension, collection, transition, essential-service, safety, and client-protection consequences. Do not continue or stop work unilaterally. Lesson: Client management enforces financial boundaries. Delivery's desire to \"keep project moving\" can't override Finance's need for payment. ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-problem-client-ghosting-no-responses-to-emails-calls", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Problem: Client Ghosting (No Responses to Emails/Calls)", "headingId": "chapter-12-client-management-problem-client-ghosting-no-responses-to-emails-calls", "url": "#chapter-12-client-management-problem-client-ghosting-no-responses-to-emails-calls", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptoms: - Client stops responding to emails (3+ emails unanswered) - Client cancels meetings repeatedly - Client avoids decision-making Diagnosis: Root Cause 1: Client is overwhelmed (not ignoring you, just underwater) Solution: - Simplify requests: Instead of \"Need your feedback on 50-page document,\" ask \"Need decision on 1 question: Option A or B?\" - Reduce meeting frequency: Weekly → Bi-weekly (give them breathing room) - Async communication: Send video summary (5 min) instead of requesting 1-hour meeting Root Cause 2: Client lost interest (project no longer a priority) Test: \"I've noticed we've missed the last 3 meetings. Has project priority changed? If so, let's discuss adjusting scope or timeline.\" If yes: Rescope project to match new priority level (smaller scope, slower timeline) If no: \"Great. Let's reschedule. When works for you?\" Root Cause 3: Client is avoiding bad news (knows project is failing, doesn't want to confront it) Test: Schedule in-person meeting (harder to ghost than email). Say: \"I'd like to discuss project status and address any concerns you have. I know we've hit some roadblocks, and I want to ensure we're aligned on the path forward.\" In meeting: Create psychological safety: \"It's okay if the project isn't meeting expectations. Let's talk honestly about what's working and what's not, and figure out how to get back on track.\" ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-problem-client-constantly-changes-requirements-scope-creep", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Problem: Client Constantly Changes Requirements (Scope Creep)", "headingId": "chapter-12-client-management-problem-client-constantly-changes-requirements-scope-creep", "url": "#chapter-12-client-management-problem-client-constantly-changes-requirements-scope-creep", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptoms: - Every meeting generates new requests - \"Quick asks\" pile up (each takes 2-4 hours) - Project timeline slips because baseline keeps expanding Diagnosis: Root Cause 1: Client didn't understand original scope (thought they were buying more than SOW specified) Solution: - Review SOW together: \"Let's align on what's in scope vs. out of scope. Here's what the SOW says...\" - Visual scope boundary: Create diagram showing In Scope (green), Out of Scope (red), and Gray Area (yellow) - Agree on change process: \"Any new requests go through change request process (we estimate effort, you approve budget).\" Root Cause 2: Client's needs are evolving (original scope was right, but situation changed) Solution: - Acknowledge change: \"I understand your needs have evolved since we started. That's normal.\" - Present options: - Option A: Finish original scope, then start Phase 2 for new requests - Option B: Pause project, re-scope to include new needs (adds 2 months, $200K) - Option C: Descope original items to make room for new requests (stay on timeline/budget) - Client chooses: Force decision (don't let scope expand without trade-offs) Root Cause 3: Client doesn't understand cost of changes (\"It's just a small tweak\") Solution: - Quantify impact: \"This 'small tweak' requires 40 hours of work ($8K cost), 2-week timeline delay, and creates risk of breaking feature X.\" - Change log: Track all \"small tweaks\" and show cumulative impact: \"We've had 15 'small tweaks' totaling 300 hours ($60K) and 2 months delay.\" - Escalate: \"We're $60K over budget due to scope changes. Should we proceed, or pause to re-scope?\" ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-problem-client-rejects-your-recommendations-even-though-data-supports-it", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Problem: Client Rejects Your Recommendations (Even Though Data Supports It)", "headingId": "chapter-12-client-management-problem-client-rejects-your-recommendations-even-though-data-supports-it", "url": "#chapter-12-client-management-problem-client-rejects-your-recommendations-even-though-data-supports-it", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptoms: - You present analysis with clear recommendation - Client says \"Interesting, but we're going a different direction\" - Client ignores data, makes decision based on gut feel Diagnosis: Root Cause 1: Data threatens client's pre-existing beliefs (cognitive dissonance) Example: - Client believes: \"Our premium pricing is our competitive advantage\" - Your analysis: \"Price is 30 percent higher than competitors with no quality difference - Losing market share\" - Client reaction: Rejects analysis (accepting it means admitting pricing strategy was wrong) Solution: - Frame as evolution: \"Your premium pricing WAS the right strategy (2015-2020). Market has shifted. Competitors caught up on quality. Time to evolve.\" - Provide exit ramp: \"Let's test: Lower prices 10 percent in one region, measure impact. If it works, scale. If not, revert.\" Root Cause 2: Recommendation conflicts with client's incentives (political issue) Example: - Your recommendation: \"Shut down Division X (unprofitable, no turnaround path)\" - Client (VP of Division X): Rejects recommendation (shutting down = loses job) Solution: - Escalate above the conflicted stakeholder: Present recommendation to CEO (who has authority to shut down division) - Offer alternative with face-saving: \"Merge Division X into Division Y (preserves team, eliminates standalone losses)\" Root Cause 3: Client wants different outcome (hired you for validation, not truth) Example: - Client wanted you to prove: \"Our product is the best in market\" - Your finding: \"Your product is mid-tier (ranked #5 of 10)\" - Client rejects finding (not what they wanted to hear) Solution: - Reset expectations: \"My job is to provide accurate analysis, even if it's not what you hoped. Here's what the data shows: [evidence]. How would you like to proceed?\" - Escalate if needed: If client asks you to change findings to match their desired narrative, refuse (ethical boundary) ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-problem-project-stuck-in-analysis-paralysis-client-won-t-make-decisions", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Problem: Project Stuck in Analysis Paralysis (Client Won't Make Decisions)", "headingId": "chapter-12-client-management-problem-project-stuck-in-analysis-paralysis-client-won-t-make-decisions", "url": "#chapter-12-client-management-problem-project-stuck-in-analysis-paralysis-client-won-t-make-decisions", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptoms: - Every decision requires \"more analysis\" - Meetings produce action items like \"Let's analyze this further\" - Timeline slips, but no progress on deliverables Diagnosis: Root Cause 1: Client lacks decision-making authority (needs boss approval, doesn't want to ask) Solution: - Identify true decision-maker: \"Who has authority to approve this? Let's include them in the next meeting.\" - Escalate: Schedule meeting with CEO/CFO (whoever has authority) Root Cause 2: Client is risk-averse (afraid of making wrong decision) Solution: - Reduce decision stakes: Instead of \"Should we invest $5M in new product?\", ask \"Should we invest $50K in 3-month pilot?\" - Reversible decisions: \"This decision is reversible. If we launch and it doesn't work, we can shut it down in 6 months.\" - Structured decision: Present 2-3 options with pros/cons. Make it easy to choose. Root Cause 3: Client is avoiding decision because all options are bad (no-win scenario) Solution: - Acknowledge difficulty: \"I know this is a tough decision. All options have downsides.\" - Reframe: \"The question isn't 'Which option is perfect?' It's 'Which imperfect option is least bad?'\" - Set deadline: \"We need a decision by Friday. If we don't decide, the default is [Option X]. Is that acceptable?\" ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-summary-client-management-toolkit", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Summary: Client Management Toolkit", "headingId": "chapter-12-client-management-summary-client-management-toolkit", "url": "#chapter-12-client-management-summary-client-management-toolkit", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 12.5 — Constructed framework-selection aid. Time, cadence, and use examples depend on the decision, evidence, authority, and context; they are not benchmarks. | Framework | When to Use | Time to Apply | |-----------|------------|--------------| | Stakeholder Matrix | Project kickoff | 2 hours | | RACI | Before work starts | 3-4 hours (multiple meetings) | | Exec Presentation | Major decision point | 8-10 hours (with feedback) | | Difficult Conversation | Conflict/misalignment | 30 min conversation | | Project Scoping | Before SOW signed | 1-2 days | | SOW | Formal engagement setup | 1-2 weeks (legal review) | | Risk Register | Planning & ongoing | 2 hours initial, 30 min/week | | Change Request Process | During delivery | Ongoing (as requests arise) | | Feedback Methods | Throughout project | 1 hour/week for collection | | Relationship Mapping | Early in engagement | 2-3 hours | ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-how-to-get-started-managing-your-client-relationship", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "How To Get Started: Managing Your Client Relationship", "headingId": "chapter-12-client-management-how-to-get-started-managing-your-client-relationship", "url": "#chapter-12-client-management-how-to-get-started-managing-your-client-relationship", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed-methodology boundary: The rapid and detailed setup examples below are fictional teaching scenarios. Hours, days, stakeholder counts, meeting durations, cadences, scores, thresholds, dates, and outputs are not defaults; replace each with a named owner, rationale, authority, evidence source, accessibility/privacy condition, tolerance, and review rule. Client and stakeholder management can materially affect access, decision quality, adoption, and implementation, but it does not outrank technical delivery in every engagement. Trust and voice can help; success still depends on evidence, competence, ethics, authority, resources, implementation, and context." }, { "id": "chapter-12-client-management::chapter-12-client-management-quick-version-rapid-stakeholder-setup-2-3-days", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Quick Version: Rapid Stakeholder Setup (2-3 days)", "headingId": "chapter-12-client-management-quick-version-rapid-stakeholder-setup-2-3-days", "url": "#chapter-12-client-management-quick-version-rapid-stakeholder-setup-2-3-days", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For immediate application when starting any client engagement:" }, { "id": "chapter-12-client-management::chapter-12-client-management-day-1-stakeholder-identification-mapping-2-3-hours", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Day 1: Stakeholder Identification & Mapping (2-3 hours)", "headingId": "chapter-12-client-management-day-1-stakeholder-identification-mapping-2-3-hours", "url": "#chapter-12-client-management-day-1-stakeholder-identification-mapping-2-3-hours", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. List all stakeholders (30 min) - Who is directly involved? (client team, project team) - Who could affect the project? (finance approvers, executive sponsors, competing projects) - Who could be affected? (end users, operations, support) - Include the smallest sufficient set supported by influence, impact, rights, expertise, dependency, and representation; there is no universal 15–25-person minimum 2. Map Power/Interest (1 hour) - Create 2x2 matrix (Power on x-axis, Interest on y-axis) - Plot each stakeholder - Use the visualization as a prompt, not a target count; document rights, legitimacy, impact, expertise, dependency, representation, and uncertainty that the two axes omit 3. Develop engagement strategy (1 hour) - For every stakeholder or represented group, select participation, decision access, evidence, channel, cadence, accommodation, consent/notice, and escalation from rights, risk, impact, expertise, dependency, urgency, and information need - Quadrant labels do not authorize minimal engagement, fixed weekly/monthly/bi-weekly/quarterly cadence, or exclusion from decisions Output: 1-page stakeholder map with engagement plan ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-day-2-raci-scoping-2-3-hours", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Day 2: RACI & Scoping (2-3 hours)", "headingId": "chapter-12-client-management-day-2-raci-scoping-2-3-hours", "url": "#chapter-12-client-management-day-2-raci-scoping-2-3-hours", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Define major work streams (30 min) - 5-8 categories of work (e.g., \"Requirements gathering,\" \"Technology selection,\" \"Implementation\") - List 3-4 tasks per stream 2. Identify key roles (15 min) - Client: Client Project Manager, Sponsor, Department heads - Consultant: Engagement Manager, Team Lead, Individual contributors - Other: Finance, IT, vendor partners 3. Map RACI (1-1.5 hours) - Create table: Rows = tasks, Columns = roles - Assign R/A/C/I for each task - Key rules: - Name a coordinating owner or collective decision rule only when the governing model permits it; do not force one accountable person where a board, committee, dual control, statutory, contractual, professional, or shared rule applies. - \"R\" and coordinating accountability may be the same person, but verify actual authority and required approvals. - Multiple consulted contributors are fine; multiple approvers may be required when the governing instrument says so. 4. Validate RACI (30 min) - Share with 2-3 key people - Ask: \"Does this reflect how we're working?\" or \"Am I missing something?\" - Update based on feedback Output: RACI matrix (spreadsheet or Confluence page) with stakeholder alignment ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-day-3-project-scope-risk-2-3-hours", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Day 3: Project Scope & Risk (2-3 hours)", "headingId": "chapter-12-client-management-day-3-project-scope-risk-2-3-hours", "url": "#chapter-12-client-management-day-3-project-scope-risk-2-3-hours", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Scope in/out (1 hour) - What ARE we delivering? (write 5-7 items) - What are we NOT delivering? (write 5-7 items) - Why not? (dependency, out of budget, separate project) 2. Top 5 risks (1 hour) - Identify biggest threats to project success - Estimate probability × impact - Define mitigation for top 3 - Assign owner for each Output: 1-2 page scope document + 5-item risk register ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-detailed-version-full-client-management-setup-2-4-weeks", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Detailed Version: Full Client Management Setup (2-4 weeks)", "headingId": "chapter-12-client-management-detailed-version-full-client-management-setup-2-4-weeks", "url": "#chapter-12-client-management-detailed-version-full-client-management-setup-2-4-weeks", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "For larger engagements requiring comprehensive stakeholder management:" }, { "id": "chapter-12-client-management::chapter-12-client-management-week-1-discovery-mapping", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Week 1: Discovery & Mapping", "headingId": "chapter-12-client-management-week-1-discovery-mapping", "url": "#chapter-12-client-management-week-1-discovery-mapping", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Monday-Tuesday: Stakeholder Interviews (1 hour each, 10-12 people) Interview guide (questions for each person): - \"What's your role in this project?\" - \"What's success look like from your perspective?\" - \"What concerns do you have?\" (most important) - \"Who else should I talk to?\" - \"What's your biggest constraint?\" (time, budget, politics, technical) Document: Name, role, interest, power, concerns, constraints --- Wednesday: Stakeholder Map Workshop Participants: Client sponsor, key client PM, your engagement leader (30 min) - Review interview notes - Plot all stakeholders on Power/Interest matrix together - Identify: - Champions: Will actively support (ask them to help sell internally) - Skeptics: Need convincing (give regular updates, address concerns) - Resistors: May block (understand objections, involve in solution) - Informals: Have hidden influence (get input, leverage for influence) Output: Stakeholder map with engagement strategy per person --- Thursday: RACI Development Workshop Participants: Your team + 2-3 key client people (2-3 hours, multiple meetings) Pre-work: - Draft list of 15-20 major tasks/decisions - Group into 5-8 work streams Workshop: 1. Present draft RACI (30 min) - Walk through each task - Explain your thinking 2. Gather input (1 hour) - \"Who should be Responsible?\" - \"Who should be Accountable?\" (usually same as R) - \"Who needs to be Consulted?\" - \"Who just needs information?\" 3. Resolve conflicts (30 min) - Address overlaps (\"Why are both Jane and Tom Accountable?\") - Clarify Consulted vs. Informed (\"Do you need input or just updates?\") 4. Document decisions (30 min) - Update RACI matrix - Send to all participants - Ask for formal sign-off (\"This reflects our agreement, yes?\") Key guidance: - Name one coordinating owner only when the governing instrument permits it; otherwise document the collective decision rule, required approvals, quorum, tie-breaker, reserved matters, and escalation route. - More Consulted = more meetings, more coordination (estimate 1 hour per Consulted person per week) - Disagreement here often reveals political dynamics; address openly --- Friday: Scope & Risk Initial Assessment Meeting (1 hour): Client sponsor + PM + your engagement lead Agenda: - \"Here's what I understand we're delivering...\" (1-page scope summary) - \"Here's what's NOT in scope...\" (avoid scope creep) - \"Top risks I'm seeing...\" (5 items with probability/impact) - \"What am I missing?\" Output: Initial draft of scope document + risk register ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-week-2-formal-scoping-relationship-building", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Week 2: Formal Scoping & Relationship Building", "headingId": "chapter-12-client-management-week-2-formal-scoping-relationship-building", "url": "#chapter-12-client-management-week-2-formal-scoping-relationship-building", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Monday-Tuesday: Detailed Scoping Session (2-3 hours total) Process: 1. Draft detailed scope (with client PM) - \"Included\" section: 10-15 specific deliverables with owners - \"Not Included\" section: 5-10 things that might be assumed - Timeline with milestones - Assumptions (what does client need to do?) - Dependencies (what must happen before we start?) 2. Get stakeholder feedback - Share draft with \"Manage Closely\" stakeholders - Listen for: \"But we also need...\" (scope creep signals) - Document concerns 3. Finalize & get sign-off - Incorporate critical feedback - Sponsor signs off (\"This is what we're doing\") - Reference this when scope disputes arise --- Wednesday-Thursday: Relationship Building 1:1s with key stakeholders (30 min each): Invite: Each \"Manage Closely\" and \"Keep Satisfied\" person Script: - \"I want to understand your perspective on this project\" - \"What's important to you about this?\" - \"What concerns do you have?\" - \"How can I help you succeed?\" - \"What's the best way to keep you updated?\" (frequency, medium, detail level) Outcome: Personal relationship + understanding of what matters to them --- Friday: Risk Management & Governance Setup Risk Workshop (1 hour with client PM + sponsor): - Brainstorm top 10-12 risks - Estimate: Probability (1-3), Impact (1-3) - Identify owner for each top risk - Define mitigation for top 3-4 risks Governance Definition (30 min): - Confirm meeting cadence: - Weekly: Client PM + your lead (30 min status) - Bi-weekly: Extended team (60 min working sessions) - Monthly: Steering committee with sponsor (60 min, status + decisions) - Define escalation path (when/how to escalate issues) - Define decision-making process (\"How do you decide on scope changes?\") Output: - Risk register (spreadsheet) - Governance model (who meets when, how decisions made) ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-week-3-4-ongoing-management", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Week 3-4: Ongoing Management", "headingId": "chapter-12-client-management-week-3-4-ongoing-management", "url": "#chapter-12-client-management-week-3-4-ongoing-management", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Weekly Rhythms: Every Week: - Stakeholder 1:1s (with \"Manage Closely\" people): 15-30 min each - Quick sync on progress, blockers, decisions needed - Ask: \"How are we doing?\" (gauge satisfaction) - Project Status Update (email to all) - \"What we completed this week\" - \"What's coming next week\" - \"Any decisions needed?\" - Tailor depth: Executives get 1-pager, teams get detailed list - Risk Register Review (with client PM) - Update probabilities based on new info - Close risks that are no longer threats - Add new risks - Escalate high-score risks ( 6 out of 9) Every Two Weeks: - Working Team Meeting (60 min) - Workstream updates (15 min each for 4 workstreams) - Issue review (blockers, decisions) - Next steps Every Month: - Steering Committee (60 min) - Executive summary of progress (5 min) - Metrics/KPIs against plan (10 min) - Top issues & decisions needed (20 min) - Risk review (10 min) - Next steps (5 min) - Stakeholder Feedback (pulse check or quick 1:1) - \"How clear are goals?\" (1-5) - \"How aligned is team?\" (1-5) - \"Anything we're not addressing?\" ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-pitfall-1-wrong-raci-unclear-accountability", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Pitfall 1: Wrong RACI, Unclear Accountability", "headingId": "chapter-12-client-management-pitfall-1-wrong-raci-unclear-accountability", "url": "#chapter-12-client-management-pitfall-1-wrong-raci-unclear-accountability", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Problem: Coordination and authority are ambiguous or conflict with the governing instrument. - Fix: Name a coordinating owner where useful, preserve required shared authorities, and document the decision and escalation route. - Risk: Delay, rework, or unsafe informal decisions; no universal month estimate applies." }, { "id": "chapter-12-client-management::chapter-12-client-management-pitfall-2-not-surfacing-resistance-early", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Pitfall 2: Not Surfacing Resistance Early", "headingId": "chapter-12-client-management-pitfall-2-not-surfacing-resistance-early", "url": "#chapter-12-client-management-pitfall-2-not-surfacing-resistance-early", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Problem: Resistor stakeholder silently blocks project at last minute - Fix: Map resistors early (Stakeholder Mapping), understand concerns, involve them in solution design - Cost of skipping: Project delayed/killed in execution phase" }, { "id": "chapter-12-client-management::chapter-12-client-management-pitfall-3-absent-sponsor", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Pitfall 3: Absent Sponsor", "headingId": "chapter-12-client-management-pitfall-3-absent-sponsor", "url": "#chapter-12-client-management-pitfall-3-absent-sponsor", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Problem: Sponsor approves project but then unavailable for decisions/escalations - Fix: In Week 1, establish that sponsor needs to be in monthly steering committee and available for decisions within 5 days - Cost of skipping: Decisions bottleneck, project stalls" }, { "id": "chapter-12-client-management::chapter-12-client-management-pitfall-4-scope-creep-without-change-management", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Pitfall 4: Scope Creep Without Change Management", "headingId": "chapter-12-client-management-pitfall-4-scope-creep-without-change-management", "url": "#chapter-12-client-management-pitfall-4-scope-creep-without-change-management", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Problem: Client keeps asking for more; no process to say \"that's a change\" - Fix: Establish scope document in Week 1. Any scope change requires sponsor approval + time/budget adjustment (or priority trade-off) - Cost of skipping: material project budget overrun, team burnout" }, { "id": "chapter-12-client-management::chapter-12-client-management-pitfall-5-not-closing-feedback-loop", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Pitfall 5: Not Closing Feedback Loop", "headingId": "chapter-12-client-management-pitfall-5-not-closing-feedback-loop", "url": "#chapter-12-client-management-pitfall-5-not-closing-feedback-loop", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Problem: Stakeholder says \"communication is poor\" but nothing changes - Fix: After feedback, explicitly say: \"You mentioned X, here's what we're doing about it\" (and do it!) - Cost of skipping: Stakeholders lose faith in feedback process, become disengaged ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-measurement-how-to-know-stakeholder-management-is-working", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Measurement: How to Know Stakeholder Management is Working", "headingId": "chapter-12-client-management-measurement-how-to-know-stakeholder-management-is-working", "url": "#chapter-12-client-management-measurement-how-to-know-stakeholder-management-is-working", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Weekly: - ✓ Risk register updated (no surprises) - ✓ No escalations from \"Manage Closely\" stakeholders (they're satisfied with communication) - ✓ RACI is being referenced to clarify roles (sign it's useful) Monthly: - ✓ Steering committee has strong attendance (sign they view it as valuable) - ✓ Decisions made within target timeframe (not bottlenecked) - ✓ Feedback check shows above-target scores on \"clear goals\" and \"aligned team\" - ✓ 8/10 - ✓ Scope changes stay within the agreed tolerance - ✓ No surprises at final delivery (communication worked) - ✓ Sponsor would work with you again ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-red-flags-when-stakeholder-management-is-failing", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Red Flags: When Stakeholder Management is Failing", "headingId": "chapter-12-client-management-red-flags-when-stakeholder-management-is-failing", "url": "#chapter-12-client-management-red-flags-when-stakeholder-management-is-failing", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- ✗ Weekly escalations from sponsor → You're not solving issues before they escalate - ✗ Steering committee attendance dropping → Stakeholders losing confidence - ✗ Frequent \"I didn't know about that\" comments → Communication breakdown - ✗ Scope change requests monthly → Original scoping was poor - ✗ RACI being ignored (\"We'll figure it out as we go\") → Political dynamics undermining structure - ✗ Resistor stakeholder suddenly says \"This isn't what we agreed\" → Didn't surface concerns early - ✗ Team complaining stakeholders are hard to reach → Sponsor not enforcing availability - ✓ One-page status email gets \"thank you, very clear\" → You're communicating at right level - ✓ Scope change requests have clear business reason + sponsor approval → Good governance - ✓ Sponsor proactively removes blockers → Strong sponsorship ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-constructed-case-example-enterprise-transformation-program", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Constructed Case Example: Enterprise Transformation Program", "headingId": "chapter-12-client-management-constructed-case-example-enterprise-transformation-program", "url": "#chapter-12-client-management-constructed-case-example-enterprise-transformation-program", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "All organizations, people, amounts, durations, counts, actions, and outcomes in this case are fictional teaching assumptions, not a report of a real engagement or evidence that the frameworks caused success. Situation: $3M, 12-month IT transformation for Fortune 500 company. Complex stakeholder group (IT, Finance, Operations, C-suite). Application: 1. Stakeholder Matrix: Mapped 40+ people; focused on 8 high-power, high-interest sponsors 2. RACI: 23 major work streams defined with clear accountability (prevented \"he said/she said\") 3. Executive Presentations: Monthly steering committee (Slide 2-13 structure above) + board-level updates (more strategic, less detail) 4. Difficult Conversations: 3 major ones: CFO concerned about cost overruns, VP Ops worried about disruption, CTO questioned vendor selection - Each addressed through scoping, communication, and involving skeptics in solution design 5. Relationship Mapping: Identified that COO (low formal power) was key influencer of CFO; got COO as active supporter early 6. Risk Register: 8 major risks tracked; biggest one (key resource leaving) mitigated by documenting knowledge weekly 7. Change Control: 6 scope change requests submitted; 3 approved (integrated into timeline), 3 deferred to Phase 2 Illustrative outcome: The scenario assumes delivery on its stated budget and timeline and a 9/10 client rating; a real review would also test adoption, business value, harm, control performance, and attribution. Question to investigate: Which stakeholder, technical, commercial, governance, and operating factors contributed to the result, and what evidence would disconfirm the team's preferred explanation? ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-operating-manual-your-client-engagement-playbook", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Operating Manual: Your Client Engagement Playbook", "headingId": "chapter-12-client-management-operating-manual-your-client-engagement-playbook", "url": "#chapter-12-client-management-operating-manual-your-client-engagement-playbook", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed-policy boundary: All hours, durations, counts, cadences, scores, thresholds, scripts, and outputs in this operating manual are fictional teaching assumptions. Replace them with approved engagement-specific evidence, contract, safety, regulatory, accessibility, workforce, procurement, confidentiality, and governance constraints. This operating manual contains constructed sample hours, durations, counts, cadences, scores, thresholds, scripts, and outputs. None is a benchmark, contractual commitment, or guarantee. Replace each sample with a named owner, rationale, authority, privacy/accessibility needs, evidence source, tolerance, and review trigger. Use it alongside project execution in Chapter 11." }, { "id": "chapter-12-client-management::chapter-12-client-management-weeks-1-2-stakeholder-mapping-engagement-planning", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Weeks 1-2: Stakeholder Mapping & Engagement Planning", "headingId": "chapter-12-client-management-weeks-1-2-stakeholder-mapping-engagement-planning", "url": "#chapter-12-client-management-weeks-1-2-stakeholder-mapping-engagement-planning", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Identify all stakeholders, understand their interests and influence, and establish engagement protocols before work begins." }, { "id": "chapter-12-client-management::chapter-12-client-management-week-1-stakeholder-identification-power-interest-assessment-16-20-hours", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Week 1: Stakeholder Identification & Power/Interest Assessment (16-20 hours)", "headingId": "chapter-12-client-management-week-1-stakeholder-identification-power-interest-assessment-16-20-hours", "url": "#chapter-12-client-management-week-1-stakeholder-identification-power-interest-assessment-16-20-hours", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Day 1-2: Stakeholder Discovery (8-10 hours) Activities: - Stakeholder Brainstorming (2 hours): - With project sponsor: \"Who will be affected by this project? Who cares about outcomes? Who can block or support us?\" - Start list: Typically 20-50 people for medium-large projects - Categorize by function: Executives, managers, end users, vendors, regulators, customers (if B2B) - Document names, titles, departments, contact info - Tool: Excel spreadsheet or stakeholder management tool - Output: Initial stakeholder list - Stakeholder Interviews - Round 1 (6-8 hours): - Interview sponsor and 3-5 key executives (30-60 min each) - Questions: - \"Who else should I talk to?\" (snowball sampling to find hidden stakeholders) - \"Who will support this project? Who might resist?\" - \"Who has been involved in similar efforts before?\" (learn from history) - Output: Expanded stakeholder list (now 30-70 people typical) Day 3-5: Power/Interest Assessment (8-10 hours) Activities: - Power Assessment (3-4 hours): - For each stakeholder, rate power (High/Medium/Low): - High Power: Can approve/veto project, control budget, or mandate requirements - Examples: Sponsor, C-suite executives, board members, major customer executives - Medium Power: Can influence decisions, provide resources, or escalate concerns - Examples: Department heads, senior managers, key customers, regulatory contacts - Low Power: Affected by project but limited influence on decisions - Examples: End users, frontline staff, junior employees - Criteria: Decision authority, budget control, political capital, relationships with high-power stakeholders - Document rationale: \"CFO rated High Power because controls budget approval\" - Interest Assessment (3-4 hours): - For each stakeholder, rate interest (High/Medium/Low): - High Interest: Personally affected, accountable for outcomes, or passionate about topic - Medium Interest: Somewhat affected or interested but not primary focus - Low Interest: Minimal personal impact; may not care - Sources: Interview feedback, organizational impact, job role alignment - Example: \"VP Sales has High Interest because sales team is primary user\" - Stakeholder Matrix Plotting (2 hours): - Plot each stakeholder on 2×2 Power/Interest grid: - Identify the stakeholders needing decision engagement and the low-power or affected groups needing accessible input or remedy; do not use a fixed count. - Output: Stakeholder matrix (visual grid + prioritized list) Outputs (Week 1): - Stakeholder list sized to the decision and affected population - Power/Interest assessment for each - Stakeholder matrix (2×2 grid showing priorities) - Decision authorities, affected groups, and engagement priorities identified with rationale Red Flags: - 2 people claim to be \"the\" decision-maker → Escalate to clarify authority - Sponsor unable to identify stakeholders → Project scope unclear; revisit charter - More than half of stakeholders rated \"Low Interest\" - Risk of disengagement; revisit communication strategy - High-power stakeholder actively opposes project → Major risk; address immediately Resource Requirements: - Project Manager: 16-20 hours - Sponsor: 4-6 hours (initial interviews, validation) ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-week-2-raci-development-communication-planning-16-20-hours", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Week 2: RACI Development & Communication Planning (16-20 hours)", "headingId": "chapter-12-client-management-week-2-raci-development-communication-planning-16-20-hours", "url": "#chapter-12-client-management-week-2-raci-development-communication-planning-16-20-hours", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Day 1-3: RACI Matrix Development (10-12 hours) Activities: - Decision Inventory (2-3 hours): - List all major decisions the project will require - Categories: - Strategic: What are we building? What's the scope? (5-10 decisions) - Tactical: How will we build it? What vendors? What approach? (10-20 decisions) - Operational: Day-to-day execution decisions (ongoing, too many to list all) - Example decisions: - \"Approve project scope\" - \"Select technology vendor\" - \"Approve design specifications\" - \"Sign off on testing results\" - \"Approve go-live\" - Output: Decision inventory (15-30 major decisions documented) - RACI Assignment (6-8 hours): - For each decision, assign roles using RACI: - Responsible (R): Who does the work? (Often multiple people; project team) - Accountable (A): Who owns the outcome or decision under the chosen RACI convention? Verify actual authority; some decisions require a board, committee, dual control, or several approvals. - Consulted (C): Who provides input before decision? (Subject matter experts, impacted stakeholders) - Informed (I): Who is told after decision is made? (FYI recipients) - Example: - Rules: - Use one \"A\" only when it faithfully represents the real governance model; otherwise document the collective or multi-approval rule explicitly - \"R\" can have multiple people (team collaborates on work) - Size \"C\" from expertise, rights, impact, representation, and decision need rather than a universal limit - Size \"I\" from notice obligations, usefulness, confidentiality, and accessibility rather than assuming broad circulation is harmless - Common mistake: Using RACI labels to overwrite actual authority; reconcile ambiguity with the governing owner instead of automatically consolidating to one decider - Output: RACI matrix (decisions × stakeholders grid) - RACI Validation (2 hours): - Review RACI with sponsor and top 5 stakeholders - Check: \"Do you agree you're Accountable for X?\" (get confirmation) - Resolve conflicts: \"Both of you think you're Accountable for vendor selection. Who makes final call?\" - Document and circulate approved RACI - Output: Approved RACI matrix Day 4-5: Communication & Engagement Planning (6-8 hours) Activities: - Communication Plan Development (4-5 hours): - For each stakeholder group (not each individual), define: - Frequency: How often to communicate? (daily, weekly, bi-weekly, monthly, as-needed) - Medium: Email, meeting, dashboard, presentation, 1-on-1 - Content: What information do they need? (Status summary, detailed metrics, decisions needed, risks) - Owner: Who delivers communication? (PM, team lead, sponsor) - Example plan: - Tool: Communication matrix (spreadsheet) - Output: Communication plan document - Escalation Protocol (1-2 hours): - Define when and how to escalate issues: - Level 1 (Team): Issues team can resolve (blockers, minor delays) - Level 2 (PM): Issues requiring PM decision (resource conflicts, minor scope changes, 1 week delays, high-impact risks) - Level 4 (Steering Committee): Strategic issues (major scope changes, project viability, multi-month delays) - Escalation timeline: 24 hours for Level 1 → 48 hours Level 2 → 72 hours Level 3 → Immediate for Level 4 - Document: \"If you encounter X, escalate to Y within Z hours\" - Output: Escalation protocol (1-page decision tree) - Engagement Kickoff Prep (1 hour): - Schedule stakeholder kickoff meeting (1-2 hours, Week 3) - Invite all high-priority stakeholders (Manage Closely + Keep Satisfied quadrants) - Agenda: - Project overview (objectives, scope, timeline) - Stakeholder roles (present RACI) - Communication plan (how we'll stay connected) - Q&A - Prepare slide deck (10-15 slides) - Output: Kickoff meeting scheduled and materials prepared Outputs (Week 2): - RACI matrix (approved by sponsor and stakeholders) - Communication plan (frequency, medium, content, owner for each group) - Escalation protocol (when and how to escalate) - Stakeholder kickoff meeting scheduled Red Flags: - 2 stakeholders claim \"Accountable\" for same decision → Conflict; must resolve before proceeding - RACI shows sponsor has no \"A\" assignments → Disengaged sponsor; risk of decision delays - Communication plan has 10 different meeting cadences → Too complex; simplify to 3-4 standard rhythms - Escalation protocol unclear or 5 levels → Bureaucratic; streamline Resource Requirements: - Project Manager: 16-20 hours - Sponsor: 4-6 hours (RACI validation, escalation review) - Key stakeholders: 2-4 hours total (RACI validation input) ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-week-3-stakeholder-kickoff-alignment", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Week 3: Stakeholder Kickoff & Alignment", "headingId": "chapter-12-client-management-week-3-stakeholder-kickoff-alignment", "url": "#chapter-12-client-management-week-3-stakeholder-kickoff-alignment", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Formally launch stakeholder engagement; ensure alignment on roles, communication, and expectations." }, { "id": "chapter-12-client-management::chapter-12-client-management-stakeholder-kickoff-meeting-2-3-hours", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Stakeholder Kickoff Meeting (2-3 hours)", "headingId": "chapter-12-client-management-stakeholder-kickoff-meeting-2-3-hours", "url": "#chapter-12-client-management-stakeholder-kickoff-meeting-2-3-hours", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Attendees: Sponsor, PM, top 10-15 stakeholders (Manage Closely + Keep Satisfied quadrants), key team leads Agenda: 1. Welcome & Objectives (15 min): - Sponsor introduces project: Why we're doing this, what success looks like - PM presents objectives, scope, timeline (high-level) 2. Stakeholder Roles & RACI (30 min): - Present RACI matrix: \"Here's who is Responsible, Accountable, Consulted, Informed for key decisions\" - Highlight each person's specific role: \"Sarah, you're Accountable for vendor selection. John, you're Consulted on design.\" - Q&A: \"Do you have questions about your role?\" 3. Communication & Engagement Plan (20 min): - Present communication plan: \"Here's how we'll keep you informed\" - Review meeting cadence: Daily standups (team), weekly email (sponsor), monthly steering committee (executives) - Escalation protocol: \"If issues arise, here's how we escalate\" 4. Expectations & Ground Rules (15 min): - Set expectations: - Responsiveness: \"We need decisions within 48 hours for critical items\" - Availability: \"Monthly steering committee attendance is mandatory for Accountables\" - Scope discipline: \"Changes require formal change request; no informal adds\" - Ground rules: - Transparency: \"We'll share bad news early\" - Collaboration: \"We're one team; no finger-pointing\" - Data-driven: \"Decisions based on data, not opinions\" 5. Risk & Issue Discussion (20 min): - Present top 5 risks (from project plan) - Ask: \"What concerns you most? What are we missing?\" - Document feedback; incorporate into risk register 6. Q&A & Next Steps (20 min): - Open floor for questions - Confirm next milestones: \"Week 4-6: Requirements gathering. We'll need your input in interviews.\" - Confirm next steering committee meeting (typically 4 weeks out) Outputs: - Stakeholder alignment on roles, communication, and expectations - Meeting minutes (decisions, action items, concerns raised) - Updated risk register (based on stakeholder input) Red Flags: - Less than half of invited stakeholders attend - Low engagement; reschedule or 1-on-1 follow-ups - Stakeholders challenge RACI in meeting → Insufficient pre-alignment; pause and resolve offline - Major concerns raised that weren't in risk register → Risk identification was incomplete; extend planning ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-weeks-4-ongoing-stakeholder-engagement-recurring-cadence", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Weeks 4+: Ongoing Stakeholder Engagement (Recurring Cadence)", "headingId": "chapter-12-client-management-weeks-4-ongoing-stakeholder-engagement-recurring-cadence", "url": "#chapter-12-client-management-weeks-4-ongoing-stakeholder-engagement-recurring-cadence", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Maintain stakeholder alignment through regular communication, proactive issue management, and relationship building." }, { "id": "chapter-12-client-management::chapter-12-client-management-weekly-activities-3-5-hours-week", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Weekly Activities (3-5 hours/week)", "headingId": "chapter-12-client-management-weekly-activities-3-5-hours-week", "url": "#chapter-12-client-management-weekly-activities-3-5-hours-week", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Sponsor 1-on-1 (30-60 min) - Timing: Every Monday (or weekly recurring) - Format: 1-on-1 meeting or call - Agenda: - Progress update (5 min): What was completed last week, what's planned this week - RAG status (5 min): Schedule (Green/Amber/Red), Budget (G/A/R), Scope (G/A/R), Risk (top 3) - Decisions needed (10-20 min): Present 1-3 decisions where sponsor is Accountable - Escalations (5-10 min): Any issues requiring sponsor intervention - Relationship health check (5 min): \"How do you feel about progress? Any concerns?\" - Output: Decision log (what was decided), action items (what sponsor will do) Red Flags: - Sponsor cancels 2 consecutive meetings → Disengagement; escalate to their manager or steering committee - Sponsor defers all decisions → Decision paralysis; simplify choices or escalate - Sponsor micromanages (wants daily updates) → Reset expectations; provide more transparency but maintain boundaries 2. Status Reporting (2-3 hours) - Timing: Every Friday (or weekly recurring) - Format: 1-page email to all stakeholders (use template for consistency) - Content: - Header: Project name, reporting period (Week X), PM name - Executive Summary (3-4 sentences): - Overall status: Green/Amber/Red - Key accomplishment this week - Biggest concern or risk - Ask (if any): \"We need your input on X by Y\" - Progress This Week (5-7 bullets): - Completed: \"Finalized requirements document (signed off)\" - In Progress: \"Vendor selection (3 demos completed, decision next week)\" - Planned for Next Week: \"Begin design phase, kick off user interviews\" - RAG Status: - Schedule: GREEN - On track for Month 8 go-live - Budget: AMBER - Trending 5 percent over budget due to vendor costs - Scope: GREEN - No changes this week - Top 3 Risks: - Risk 1: Key resource (Sarah) may leave company (Probability: Medium, Impact: High, Mitigation: Cross-training backup) - Risk 2: Vendor delivery delayed by 1 week (Probability: Low, Impact: Medium, Mitigation: Compressed testing timeline) - Risk 3: End user adoption concerns (Probability: Medium, Impact: High, Mitigation: Enhanced training program) - Decisions Needed (if any): - Decision: Approve additional $50K for vendor customization - Owner: Sponsor - Due Date: Monday, Week X+1 - Context: Vendor standard product doesn't meet 2 critical requirements; customization needed - Next Milestones: - Week X+2: Design review with stakeholders - Week X+4: Steering committee meeting - Tool: Email template (reuse every week for consistency) - Output: Weekly status email (distributed Friday afternoon) Red Flags: - Stakeholders stop reading/responding to status emails → Email fatigue; shorten format or add visual dashboards - Status always \"Green\" for 8 weeks → Unrealistic; likely hiding issues - Same risks on list for 4 weeks without mitigation progress → Risk management ineffective; escalate 3. Stakeholder Pulse Check (1 hour/week) - Timing: Ad hoc throughout week - Activity: Informal check-ins with 1-2 high-priority stakeholders - Purpose: Build relationships, surface concerns early, prevent surprises - Format: Casual conversation (coffee chat, hallway conversation, Slack message) - Questions: - \"How's the project going from your perspective?\" - \"Any concerns I should know about?\" - \"Is there anything we're not communicating that you need?\" - Output: Notes on stakeholder sentiment (add to stakeholder register) ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-monthly-activities-6-10-hours-month", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Monthly Activities (6-10 hours/month)", "headingId": "chapter-12-client-management-monthly-activities-6-10-hours-month", "url": "#chapter-12-client-management-monthly-activities-6-10-hours-month", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Steering Committee Meeting (2-3 hours) - Timing: Monthly (typically last Friday of month) - Attendees: Sponsor, steering committee (3-7 executives), PM, key team leads - Format: In-person or video meeting - Agenda (2-hour meeting): - Progress Update (20 min): - Slides 1-3: Accomplishments this month, planned for next month, overall status (Green/Amber/Red) - Focus on outcomes, not activities: \"Delivered working prototype\" not \"Had 10 meetings\" - Financial Review (10 min): - Slide 4: Budget vs. actual (table showing planned, actual, variance by category) - Forecast to complete: \"We'll finish $50K over budget (5 percent variance) due to vendor costs\" - Ask if additional funding needed: \"Request approval for $50K contingency release\" - Schedule Review (10 min): - Slide 5: Gantt chart showing critical path and milestones - Status: \"On track for Month 8 go-live\" or \"At risk: 2 weeks behind due to vendor delay\" - Mitigation if behind: \"We're compressing testing timeline and adding resources\" - Risk & Issue Review (20 min): - Slides 6-7: Top 5 risks (probability, impact, mitigation) - Top 3 issues requiring steering committee decision or awareness - Example: \"Risk: Key resource Sarah may leave. Mitigation: We've cross-trained John and documented her knowledge.\" - Decisions Needed (30 min): - Slides 8-10: 2-3 major decisions requiring steering committee approval - Format per decision: - Context: What's the situation? - Options: 2-3 alternatives (with pros/cons) - Recommendation: PM's recommended option - Ask: Approve/reject/defer? - Example: \"Decision: Approve vendor customization ($50K). Options: (1) Approve customization, (2) Descope requirements, (3) Switch vendors. Recommendation: Approve customization (maintains scope, lowest risk).\" - Q&A & Next Steps (10 min): - Open floor for questions - Confirm decisions made - Next meeting date and topics - Output: Meeting minutes (decisions, action items, attendees), updated decision log Red Flags: - Less than half steering committee attendance - Low engagement; escalate to sponsor or CEO - No decisions made (all deferred) → Decision paralysis; simplify choices or escalate to CEO - Meeting extends 2.5 hours → Too detailed; elevate to strategic level - Same issues on agenda for 2 months → Not resolving issues; change approach 2. Stakeholder Satisfaction Check (1-2 hours, quarterly) - Timing: Every 3 months (Months 3, 6, 9, 12) - Format: Anonymous feedback form (5-10 questions, 5 min to complete) - Questions: - \"On a scale of 1-10, how satisfied are you with project progress?\" - \"Are you receiving enough communication? Too much? Too little?\" - \"Do you understand your role and responsibilities?\" - \"What's going well? What should we improve?\" - \"Any concerns or feedback?\" - Distribution: Email feedback link to all stakeholders - Analysis: Aggregate results; identify themes - Action: Present findings to sponsor; implement top 2-3 improvements - Output: Satisfaction memo (summary of results + action plan) Red Flags: - Average satisfaction Increase frequency or transparency - Multiple stakeholders cite same issue → Systemic problem; address urgently 3. Relationship Mapping Update (1-2 hours, quarterly) - Activity: Update stakeholder power/interest matrix and relationship map - Questions: - Has anyone's power or interest changed? (promotions, departures, shifting priorities) - Have new stakeholders emerged? (new hires, new departments affected) - Are any relationships strained? (conflicts, misalignments) - Action: Adjust engagement approach based on changes - Example: \"CFO was Low Interest, now High Interest due to budget concerns → Increase communication frequency\" - Output: Updated stakeholder matrix ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-difficult-conversations-conflict-resolution-as-needed", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Difficult Conversations & Conflict Resolution (As Needed)", "headingId": "chapter-12-client-management-difficult-conversations-conflict-resolution-as-needed", "url": "#chapter-12-client-management-difficult-conversations-conflict-resolution-as-needed", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Address stakeholder conflicts, resistance, or concerns proactively before they derail the project." }, { "id": "chapter-12-client-management::chapter-12-client-management-negotiation-bridge-prepare-before-the-conversation", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Negotiation bridge: prepare before the conversation", "headingId": "chapter-12-client-management-negotiation-bridge-prepare-before-the-conversation", "url": "#chapter-12-client-management-negotiation-bridge-prepare-before-the-conversation", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the foundational negotiation logic in Chapter 7 before treating a difficult conversation as a bargaining session. Verify who can bind each organization; identify issues that are negotiable and non-negotiable; calculate the BATNA, reservation package, target, and possible ZOPA; and separate factual evidence from estimates about the other side. [BB-C07-S13] [BB-C07-S14] For client work, translate a headline dispute into packages. A timeline package might combine scope, sequencing, staffing, acceptance criteria, governance, price, and service levels. Confirm that any package is operationally feasible and approved by the people who hold contractual, financial, legal, professional, security, or safety authority. Never promise an approval you do not control." }, { "id": "chapter-12-client-management::chapter-12-client-management-applied-multiparty-role-play-constructed-service-recovery", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Applied multiparty role play — constructed service recovery", "headingId": "chapter-12-client-management-applied-multiparty-role-play-constructed-service-recovery", "url": "#chapter-12-client-management-applied-multiparty-role-play-constructed-service-recovery", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scenario: A client wants an eight-week launch after a supplier delay. The consulting lead, client operations leader, procurement owner, security officer, and supplier each receive a private role brief with different priorities, authority, evidence, and alternatives. No role may invent facts or waive another role's required approval. Deliverables: 1. A party-interest-authority map, including absent affected groups and representation gaps. 2. Each party's BATNA, reservation package, target, uncertainty, and evidence source. 3. Three multi-issue packages covering scope, timing, staffing, cost, security evidence, acceptance, and recovery. 4. A coalition and process plan that states the decision rule, caucus boundaries, disclosure rules, and escalation route. 5. A final term sheet or documented impasse, plus an ethics review: who gained or lost power, what could not be traded, what information was withheld and why, and whether the process allowed informed dissent. Debrief: Compare outcome value with process legitimacy, implementation risk, distributional effects, relationship effects, and treatment of the least powerful party. A signed agreement is not automatically a good decision; walking away is not automatically failure." }, { "id": "chapter-12-client-management::chapter-12-client-management-framework-for-difficult-conversations", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Framework for Difficult Conversations", "headingId": "chapter-12-client-management-framework-for-difficult-conversations", "url": "#chapter-12-client-management-framework-for-difficult-conversations", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Safety and authority gate: Before any direct outreach, private meeting, empathy script, or escalation, check whether the issue involves safety, retaliation, discrimination, harassment, violence, investigation, legal hold, accommodation, union, protected reporting, professional misconduct, confidentiality, or another formal obligation. If so, pause the direct script and use the approved HR, legal, compliance, security, safety, labor, or professional route. Preparation (1-2 hours before conversation): 1. Identify the Issue: - What is the specific concern or conflict? - Example: \"CFO is blocking budget approval due to cost concerns\" 2. Understand Their Perspective: - Why do they feel this way? (empathy) - What's at stake for them? (career, budget, reputation, workload) - Example: \"CFO is under pressure to cut costs; sees this project as discretionary\" 3. Prepare Your Position: - What are the facts? (data, not opinions) - What's the business case? (why this matters) - What are you willing to compromise on? (flexibility) 4. Plan the Conversation: - Where and when? (only after the safety/authority gate; choose a channel that supports safety, accessibility, privacy, records, and participation) - Who should attend? (1-on-1 vs. including sponsor) - What's the goal? (alignment, decision, understanding) Conversation Structure (30-60 min): 1. Open with Empathy (5 min): - Acknowledge their perspective: \"I understand you're concerned about the budget. I want to understand your concerns.\" - Build rapport; show you're listening 2. Understand Their Concerns (10-15 min): - Ask open-ended questions: \"What specifically concerns you? What would make you more comfortable?\" - Listen actively; don't interrupt or defend - Summarize: \"So if I understand correctly, you're worried about X and Y. Is that right?\" 3. Share Your Perspective (10-15 min): - Present facts and data: \"Here's what the data shows...\" - Explain business case: \"If we don't do this project, the impact will be...\" - Be transparent about risks: \"I understand there are risks. Here's how we're mitigating them.\" 4. Explore Options (10-15 min): - Brainstorm together: \"What if we... (alternative approach)?\" - Find common ground: \"We both want X. How can we get there?\" - Offer compromises: \"Would it help if we... (reduce scope, phase approach, add oversight)?\" 5. Agree on Next Steps (5-10 min): - Summarize agreement: \"So we're aligned that...\" - Confirm actions: \"You'll do X, I'll do Y, by when?\" - Schedule follow-up: \"Let's check in next week to see how this is going.\" Follow-Up (Post-Conversation): - Document conversation: Email summary of what was discussed and agreed - Execute on commitments: Do what you said you'd do - Monitor relationship: Check in proactively; don't wait for next conflict Example Difficult Conversations: Scenario 1: CFO Blocking Budget Approval - Issue: CFO won't approve $50K additional budget for vendor customization - Approach: - Understand: \"What's driving your concern? Is it the amount, the vendor, or budget constraints?\" - Present data: \"Without customization, we can't meet 2 critical requirements (show impact: delayed go-live, user adoption risk)\" - Explore options: \"Could we phase the customization (do half now, half in 6 months)? Or find lower-cost alternative?\" - Outcome: Agree to phase approach ($25K now, $25K later) or descope 1 requirement Scenario 2: VP Operations Worried About Disruption - Issue: VP Ops fears project will disrupt operations during peak season - Approach: - Empathize: \"I understand you can't afford downtime during Q4. That makes sense.\" - Understand: \"What specifically worries you? Timing? Training? System downtime?\" - Propose solutions: \"What if we delay go-live until January (after peak)? Or do phased rollout (pilot team first, full rollout later)?\" - Outcome: Agree to delay go-live or phased approach Scenario 3: CTO Questions Vendor Selection - Issue: CTO disagrees with vendor choice; prefers different vendor - Approach: - Understand: \"What makes you prefer Vendor B over Vendor A? What criteria matter most to you?\" - Present decision rationale: \"Here's how we scored vendors on 10 criteria. Vendor A won on cost, integration, and support.\" - Involve in solution: \"Would it help if you attended vendor demo or reviewed technical architecture?\" - Outcome: CTO sees rationale and approves, OR surfaces valid technical concern and recommends re-evaluation Red Flags in Difficult Conversations: - Stakeholder refuses to engage → Escalate to sponsor or their manager - Conversation becomes personal or emotional → Pause, reschedule when cooler heads prevail - No agreement after 2-3 attempts → Escalate to steering committee for decision - Agreement made but stakeholder doesn't follow through → Escalate to sponsor ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-measurement-dashboard-weekly-tracking", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Measurement Dashboard (Weekly Tracking)", "headingId": "chapter-12-client-management-measurement-dashboard-weekly-tracking", "url": "#chapter-12-client-management-measurement-dashboard-weekly-tracking", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Track stakeholder health using these metrics: Stakeholder Engagement Score (1-10 scale): - For top 5-10 stakeholders, rate weekly: - 10: Highly engaged (attends all meetings, responds quickly, actively supportive) - 7-9: Engaged (participates, generally supportive) - 4-6: Neutral (attends but passive, slow to respond) - 1-3: Disengaged (skips meetings, doesn't respond, resistant) - Target: Average score 7 for top stakeholders - Red flag: Any stakeholder 2 weeks → Intervention needed Decision Velocity (Days to Decide): - Track time from \"decision needed\" to \"decision made\" - Target: 14 days → Escalate or simplify Scope Change Requests: - Count: # of change requests submitted, approved, rejected, deferred - Target: 10 change requests/month → Scope management broken Risk Escalations: - Count: # of risks escalated to sponsor or steering committee - Target: 2 times → Mitigation not working Client Satisfaction (Monthly Pulse): - Quick 1-question pulse check: \"How satisfied are you with project progress? (1-10)\" - Target: Average 8 - Red flag: Score Communication fatigue or disengagement ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-contingency-playbook", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Contingency Playbook", "headingId": "chapter-12-client-management-contingency-playbook", "url": "#chapter-12-client-management-contingency-playbook", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scenario 1: Stakeholder Disengagement - Trigger: Key stakeholder stops attending meetings, doesn't respond to emails for 1 week - Response: - Day 1: Direct outreach (phone call or in-person): \"I noticed you haven't been able to join meetings. Is everything okay? How can I support you?\" - Day 2: Escalate to sponsor: \"Stakeholder X is disengaged. Can you help re-engage them?\" - Day 3: If no response, escalate to their manager or steering committee - If participation is unavailable, check rights, representation, authority, confidentiality, accessibility, harm, and decision continuity; use an authorized substitute or pause rather than treating absence as permission to proceed. Scenario 2: Decision Stalemate (Multiple Stakeholders Can't Agree) - Trigger: Decision has been discussed 3+ times with no resolution - Response: - Facilitate decision workshop (2 hours): - Present data objectively - Use decision criteria framework (score options on agreed criteria) - Force rank options: \"If you had to choose one, which would it be?\" - If still no agreement: Escalate to sponsor or steering committee to make final call - Document decision rationale to prevent revisiting Scenario 3: Scope Creep (Unapproved Requests) - Trigger: Stakeholders requesting features or changes without formal change request - Response: - Enforce change control: \"That's a great idea. Please submit a formal change request so we can evaluate impact on scope, schedule, and budget.\" - Present trade-offs: \"To add X, we'd need to descope Y or extend timeline by Z weeks. Which do you prefer?\" - Say no when needed: \"That's out of scope for this project. We can consider it for Phase 2.\" - Document all rejected requests (change log) to prevent future conflicts Scenario 4: Relationship Breakdown (Conflict Between Stakeholders) - Trigger: Two stakeholders in open conflict, affecting project decisions - Response: - Facilitate mediation (1-2 hours): - Understand both perspectives separately (1-on-1 conversations) - Facilitate joint conversation (focus on data and shared goals, not personalities) - Find common ground: \"You both want the project to succeed. How can we make that happen?\" - If mediation fails: Escalate to sponsor to adjudicate - If a person must be recused or participation changed, document the authority, rights, representation, confidentiality, conflict, harm, and appeal/escalation basis; a project manager cannot remove a required decision-maker unilaterally. Scenario 5: Sponsor Departure or Change - Trigger: Sponsor leaves company, changes roles, or loses authority - Response: - Immediate action: Identify new sponsor within 48 hours (escalate to CEO if needed) - Onboard new sponsor: 2-hour briefing (project context, status, decisions needed) - Reset expectations: New sponsor may have different priorities; align early - Document transition: Update RACI, communication plan with new sponsor ---" }, { "id": "chapter-12-client-management::chapter-12-client-management-summary-client-management-operating-manual", "kind": "chapter", "itemSlug": "chapter-12-client-management", "itemTitle": "Client Management", "part": "Part 2: Management Consulting Toolkit", "heading": "Summary: Client Management Operating Manual", "headingId": "chapter-12-client-management-summary-client-management-operating-manual", "url": "#chapter-12-client-management-summary-client-management-operating-manual", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Key Principles: 1. Early and continuing stakeholder analysis: Identify affected parties before material decisions and update the map as impact and coalitions change. 2. Clear coordination and authority: RACI can prompt role discussion but does not prevent conflict or create approval authority. 3. Decision-relevant communication: Set cadence and channel from governance, urgency, risk, accessibility, and audience need. 4. Evidence-aware conversations: Use quantitative and qualitative evidence, values, constraints, uncertainty, affected-party input, and the business case; distinguish unsupported opinion from legitimate normative or distributional concerns. 5. Safe conflict handling: Address concerns through the appropriate direct, mediated, HR, legal, compliance, or safety route. 6. Measurement & Adjustment: Track engagement score, decision velocity, satisfaction; adjust approach as needed When to use selected components: - Engagements where the component fits the decision, contract, professional obligations, and affected parties - Projects with complex authority, impact, or stakeholder environments; no numeric stakeholder threshold applies - High-risk projects requiring executive alignment - Transformation programs affecting multiple functions Adapt Based On: - Project size and risk: Tailor using value, consequence, regulation, duration, interfaces, and uncertainty rather than fixed dollar/month cutoffs. - Stakeholder complexity: Simple stakeholder landscape (3-5 people) requires less structure - Client culture: Startup → informal communication; Enterprise → formal governance This operating manual can structure engagement decisions; it does not ensure alignment, engagement, satisfaction, adoption, business value, or legal compliance. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Startup Foundations", "headingId": "chapter-13-startup-foundations", "url": "#chapter-13-startup-foundations", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-executive-summary", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Executive Summary", "headingId": "chapter-13-startup-foundations-executive-summary", "url": "#chapter-13-startup-foundations-executive-summary", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter teaches venture hypothesis, evidence, ownership, and cash decisions across different startup types. It does not prescribe a universal venture-backed SaaS sequence or treat one diagnostic, ratio, interview count, financing round, or timeline as proof of readiness. Key Frameworks: 1. Lean Startup Cycle (Build-Measure-Learn) 2. Customer Development (Steve Blank 4 Steps) 3. MVP Definition Framework 4. Product-Market Fit Metrics 5. Founder-Governance Issue-Spotting Checklist 6. Equity Distribution Model 7. Burn Rate Calculator 8. Runway Planning 9. Pivot Decision Framework 10. Scale-Up Readiness Checklist 11. Venture-Path and Acquisition-Screening Framework This chapter is educational, not legal, tax, securities, accounting, employment, compensation, or investment advice. Founder equity, vesting, IP, governance, financing, and employee/advisor grants depend on the entity, jurisdiction, documents, tax posture, securities rules, and facts. Applied exercise — venture evidence memo: Choose a venture type and create an assumption ledger, two tests with falsification and ethics rules, a six-month cash scenario, and a founder-decision memo. Include one non-product MVP, one alternative to venture funding, a stop condition, and questions for counsel. Connect customer work to Chapter 5, finance to Chapter 4, GTM to Chapter 14, fundraising to Chapter 15, and product decisions to Chapter 21. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview", "url": "#chapter-13-startup-foundations-overview", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Lean Startup Cycle is a decision-learning model for turning a stated venture hypothesis into an ethical test, evidence review, and next investment choice. The source supports Build-Measure-Learn, MVP, and pivot/persevere framing; the safety, evidence-quality, cash, pause, and stop gates below are author adaptations. [BB-C13-S01]" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply", "url": "#chapter-13-startup-foundations-how-to-apply", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the cycle to name the uncertainty, define what would count as informative evidence, choose the smallest responsible test, and decide whether to persevere, revise, pause, or stop. Do not treat one conversion rate, interview, or user statement as validation. Core Loop: The loop is a decision cycle: evidence determines whether the next iteration keeps the current hypothesis, changes it, pauses for missing evidence, or stops investment. [BB-C13-S01] Figure 13.1. Evidence-gated venture learning loop. The smallest responsible test produces evidence of stated quality; the team compares it with predeclared criteria and available cash before persevering, pivoting, pausing, or stopping. Adapted from Build-Measure-Learn and pivot/persevere framing. [BB-C13-S01] Text equivalent: State a falsifiable hypothesis and decision. Choose the smallest ethical test that can produce relevant evidence. Measure behavior and uncertainty, then compare the result with the predeclared rule and runway. Persevere only when evidence supports the next investment; otherwise revise, pause, or stop. Every decision creates a new or revised hypothesis. Principles: - Validated learning over elaborate planning - Build-Measure-Learn feedback loop (minimize time through loop) - MVP (minimum viable product) over full product - Persevere, pivot, pause, or stop based on evidence quality, consequences, and cash—not a binary metric or intuition alone Application: 1. Build: Create smallest thing to test hypothesis (landing page, prototype, concierge MVP) 2. Measure: Define metrics before building (leading indicators, not vanity metrics) 3. Learn: Did experiment validate or invalidate hypothesis? 4. Decide: Persevere (keep going) or Pivot (change course) Example: - Hypothesis: \"Small business owners will pay $99/month for automated bookkeeping\" - MVP: Landing page describing product, \"sign up\" button - Measure: Conversion rate (% who sign up) - Learn: Compare an illustrative 0.1 percent or 5 percent result with the sample, traffic source, intent, baseline, uncertainty, economics, and predeclared rule; neither number validates a venture by itself. - Decision: Investigate, repeat, revise, persevere, or stop according to the decision rule and cost of error." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers", "url": "#chapter-13-startup-foundations-so-what-for-managers", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- State the decision and the hypothesis before approving build work or spending. - Compare observed behavior, evidence quality, uncertainty, safety, and cash—not just activity or enthusiasm. - Preserve learning and stakeholder obligations when a test is paused, revised, or stopped." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques", "url": "#chapter-13-startup-foundations-limits-and-critiques", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A rapid loop can produce precise answers to the wrong question if the hypothesis, sample, measure, or denominator is weak. - Iteration does not remove safety, privacy, accessibility, regulatory, contractual, or professional duties. - Pivoting can destroy options or trust; stop and pause rules should account for reversibility, affected parties, and cash." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections", "url": "#chapter-13-startup-foundations-connections", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Customer evidence: Use Frameworks 2, 3, and 4 plus Chapter 5 to test demand, solution, and segment assumptions. - Cash and governance: Use Chapters 4 and 15 to connect test cost, runway, financing, and authorized decision rights. - Product and market: Use Chapters 14 and 21 to connect learning to positioning, delivery, and product choices. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-2", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview-2", "url": "#chapter-13-startup-foundations-overview-2", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Customer Development framework is a four-step search structure for testing customer, market, channel, and company-building assumptions. It supports the sequence; it does not establish a universal interview count, customer count, sales milestone, or scale gate. [BB-C13-S02]" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply-2", "url": "#chapter-13-startup-foundations-how-to-apply-2", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the four steps as hypotheses to investigate, not as a mandatory linear gate. Define the segment, evidence mode, buying process, sample uncertainty, ethical safeguards, and decision cost before treating a result as informative. Steve Blank's four Customer Development steps: [BB-C13-S02] 1. Customer Discovery - Goal: Do customers have the problem you think they have? - Activities: Use a justified sample and multiple evidence modes; interviews reveal accounts and hypotheses, not demand by themselves. - Output: A problem hypothesis and evidence map; fit remains provisional. - Key Question: \"Tell me about the last time you experienced [problem]\" 2. Customer Validation - Goal: Will customers pay for your solution? - Activities: Sell MVP, iterate on positioning/pricing - Output: Evidence about willingness to buy and a candidate sales process. - Milestone: Define evidence sufficiency from segment, buying process, price, repeatability, sample uncertainty, and decision cost; no universal customer count applies. 3. Customer Creation - Goal: Scale customer acquisition - Activities: Build marketing/sales engine, optimize funnel - Output: Tested acquisition hypotheses and cohort economics; predictability remains to be demonstrated. - Milestone: Model cohort revenue, gross margin, service cost, retention, acquisition cash, payback, and uncertainty using locally justified decision ranges. 4. Company Building - Goal: Scale organization - Activities: Build departments, processes, culture - Output: Organizational evidence and operating options; sustainability remains to be demonstrated. - Milestone: Define the relevant product, people, process, cash, control, and governance evidence for this venture. The steps are a search framework, not a universal linear gate. Scaling before sufficient evidence can amplify loss, but safety, capacity, financing, and market timing may require different sequences." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers-2", "url": "#chapter-13-startup-foundations-so-what-for-managers-2", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Separate problem accounts, observed behavior, willingness to pay, repeatability, and organizational capacity. - Choose evidence modes that fit the customer, power relationship, accessibility needs, and decision risk. - Advance only when the next commitment is justified by the evidence and available alternatives." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques-2", "url": "#chapter-13-startup-foundations-limits-and-critiques-2", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Interviews can reveal language, memory, incentives, and hypotheses without proving demand or future behavior. - The four steps can imply linear progress when regulated, hardware, scientific, service, or enterprise ventures require parallel work. - “Customer creation” and “company building” depend on economics, capacity, governance, market timing, and obligations beyond the framework." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections-2", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections-2", "url": "#chapter-13-startup-foundations-connections-2", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- MVP and fit: Use Frameworks 3 and 4 to define the artifact and triangulate evidence. - Go-to-market: Use Chapter 14 for segment, positioning, channel, pricing, and sales choices. - Finance: Use Chapters 4 and 15 for cohort economics, cash timing, financing, and downside decisions. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-3", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview-3", "url": "#chapter-13-startup-foundations-overview-3", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "An MVP is the smallest responsible artifact or evidence package that can answer a named decision question with acceptable risk. It may be a prototype, concierge workflow, simulation, technical study, regulated evidence package, or limited pilot rather than a public product. [BB-C13-S01]" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply-3", "url": "#chapter-13-startup-foundations-how-to-apply-3", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the uncertainty, the observable evidence, the decision rule, the cost of error, and the safety/privacy/accessibility/legal conditions before selecting the MVP form. Minimum means minimum for the decision, not merely fastest to release. MVP Spectrum: 1. Smoke Test: Landing page, no product (test demand) 2. Concierge: Manual delivery at small scale (test solution) 3. Wizard of Oz: Appears automated but manual behind scenes 4. Single-Feature: Smallest functional product 5. Pilot/Beta: Feature-complete but limited audience MVP Litmus Test: - Is it decision-relevant ? Does it test the named uncertainty with observable evidence? - Is it responsible ? Are safety, privacy, accessibility, consent, security, and legal conditions satisfied? - Is it minimum for the decision ? A simulation, concierge workflow, prototype, technical study, regulated evidence package, or limited pilot may be smaller and safer than a public product. This is an author-created decision aid. Common Mistakes: - \"MVP\" that takes 6 months (not minimum) - MVP that doesn't solve core problem (not viable) - Confusing \"beta\" with \"MVP\" (beta is feature-complete) Constructed MVP examples: - A demonstration video tests whether the proposed workflow is understood well enough to justify deeper discovery. - A manual concierge service tests the service process and observed willingness to engage before automation. - A limited catalog with manual fulfillment tests buying behavior without committing to inventory." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers-3", "url": "#chapter-13-startup-foundations-so-what-for-managers-3", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Match the MVP to the uncertainty and harm of being wrong, not to a preferred product format. - Make consent, privacy, safety, accessibility, security, and reversibility part of the test design. - Define what evidence would support build, revise, pause, or stop before collecting results." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques-3", "url": "#chapter-13-startup-foundations-limits-and-critiques-3", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- “Minimum” can under-test reliability, integration, support, regulation, or distribution constraints that determine viability. - A smoke test can measure attention or message comprehension without measuring willingness to pay or safe delivery. - A beta or pilot can create obligations and reputational effects even when labeled experimental." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections-3", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections-3", "url": "#chapter-13-startup-foundations-connections-3", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Learning loop: Use Framework 1 to connect the chosen artifact to a falsifiable hypothesis and cash gate. - Customer development: Use Framework 2 to identify whose evidence is needed and how to interpret accounts. - Product practice: Use Chapter 21 for discovery, prioritization, quality, and release decisions. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-4", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview-4", "url": "#chapter-13-startup-foundations-overview-4", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Product-market fit is a multi-signal judgment about whether a defined segment repeatedly receives meaningful value and can be reached and served under realistic economics. The Sean Ellis question is a practitioner diagnostic, not a universal threshold or proof of sustainable growth. [BB-C13-S08] [BB-C13-S09]" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply-4", "url": "#chapter-13-startup-foundations-how-to-apply-4", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the survey, retention, paid behavior, usage, referrals, complaints, alternatives, margin, service burden, and reachable-market prompts as separate evidence streams. State the segment, denominator, exposure, horizon, uncertainty, and decision rule before interpreting any signal. Sean Ellis practitioner heuristic: Ask users: \"How would you feel if you could no longer use [product]?\" - Record the “very disappointed” share with sample, segment, recruitment, response rate, product exposure, and confidence. Ellis describes 40 percent as an admittedly arbitrary practitioner threshold derived from comparing results across nearly 100 startups; it is not representative causal validation or proof of sustainable growth. [BB-C13-S08] - Somewhat disappointed - Not disappointed An a16z practitioner account distinguishes strong fit with a narrow set of power users from evidence of a broader reachable market, warning against declaring product-market fit from an early cohort alone. [BB-C13-S09] The following triangulation prompts are an author-created evidence checklist, not validated PMF thresholds. Triangulation prompts: - Retention: Define the cohort, event, buying/use cycle, censoring, and observation window; compare behavior over time. - Paid behavior and economics: Examine willingness to pay, gross margin, service burden, acquisition cash timing, and segment-specific unit economics. - Recommendation and referral: Use a defined measure with sample and context; no universal NPS or referral threshold proves fit. - Reachable market: Test whether the satisfied segment is sufficiently large, reachable, and supportable under realistic competition and capacity. - Usage and outcomes: Define meaningful use and customer outcomes rather than treating logins or activity ratios as value by default. Constructed PMF evidence loop: 1. Ask users with Sean Ellis question 2. Segment users: Very disappointed vs. Others 3. Find common traits of \"very disappointed\" users 4. Double down on those users (ICP refinement) 5. Ask \"What would make product must-have?\" to improve 6. Reassess alongside retention, behavior, paid conversion, referrals, margin, service burden, and contrary evidence; do not optimize only to a survey cutoff. [BB-C13-S08] [BB-C13-S09]" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers-4", "url": "#chapter-13-startup-foundations-so-what-for-managers-4", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ask what “fit” means for this segment, use cycle, outcome, channel, and economic model. - Reconcile stated preference with observed retention, paid behavior, support burden, alternatives, and contrary evidence. - Treat a threshold as a prompt for investigation, never as an automatic investment or scale authorization." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques-4", "url": "#chapter-13-startup-foundations-limits-and-critiques-4", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Survey responses are sensitive to sampling, recruitment, exposure, wording, timing, incentives, and nonresponse. - Retention, referrals, usage, and unit economics have different denominators and time horizons; they cannot be collapsed into one score without loss. - A narrow power-user cohort can look strong while the reachable market, delivery capacity, regulation, or economics remain unproven." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections-4", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections-4", "url": "#chapter-13-startup-foundations-connections-4", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Customer evidence: Use Frameworks 1–3 to connect segment, problem, solution, and test design. - Economics: Use Frameworks 7 and 8 plus Chapter 4 to test margin, cash timing, service burden, and runway. - GTM and product: Use Chapters 14 and 21 to connect fit evidence to positioning, channels, prioritization, and quality. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-5", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview-5", "url": "#chapter-13-startup-foundations-overview-5", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Founder governance is a counsel-owned issue-spotting checklist , not a contract template or legal conclusion. Founder roles, equity, control, IP, compensation, financing, departure, and disputes depend on the entity, jurisdiction, documents, tax posture, securities rules, employment status, and facts. [BB-C13-S04] [BB-C13-S05]" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply-5", "url": "#chapter-13-startup-foundations-how-to-apply-5", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the checklist to identify questions for authorized founders, boards, finance, tax advisers, and qualified counsel. Do not select vesting, repurchase, acceleration, grant, salary, IP, or departure terms from this chapter alone. This is an issue-spotting checklist for founders and qualified counsel, not a contract template. Confirm entity, jurisdiction, tax, securities, employment, marital/property, IP, immigration, compensation, fiduciary, financing, and departure implications before selecting terms. Wasserman's founder research directly supports examining founding-team roles, equity splits, control, and conflict; Hellmann and Wasserman provide evidence on founder-equity allocation. [BB-C13-S04] [BB-C13-S05] The remaining legal and governance prompts are author-created issue-spotting questions, not source-derived legal advice. Issues to resolve: Equity Split: - Equal vs. unequal (based on contribution, risk, role) - Whether vesting, repurchase, forfeiture, acceleration, or other conditions are appropriate under the specific documents and law Roles & Responsibilities: - CEO, CTO, etc. (who decides what?) - Decision-making process (unanimity vs. majority) - Board composition Compensation: - Define lawful, tax-aware compensation and reimbursement through the authorized process; no universal founder salary range applies. IP ownership and licensing: - Inventory pre-existing and new IP, third-party rights, employment/contractor obligations, open-source components, data, assignments, licenses, and exclusions with counsel. Constructed vesting arithmetic only: Departure and dispute issues: - Define resignation, termination, disability/death, cause, good/bad-leaver concepts, repurchase, exercise, transfer, confidentiality, transition, deadlock, and dispute mechanisms through the applicable documents and law. Use complete executed documents and preserve approvals and cap-table records; a checklist is not a legal conclusion." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers-5", "url": "#chapter-13-startup-foundations-so-what-for-managers-5", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Make authority, contribution, control, future work, conflict, and departure assumptions explicit before allocating ownership. - Separate a constructed arithmetic example from the actual cap table, documents, tax treatment, and rights. - Escalate legal, employment, securities, tax, IP, immigration, fiduciary, and financing questions to the appropriate owner." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques-5", "url": "#chapter-13-startup-foundations-limits-and-critiques-5", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Founder research can inform questions about roles, control, and equity without prescribing a lawful or fair result for a particular entity. - Equal or unequal splits can both be rational or harmful depending on contribution, commitment, information, power, and future work. - A checklist cannot create consent, transfer IP, authorize compensation, or resolve a deadlock." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections-5", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections-5", "url": "#chapter-13-startup-foundations-connections-5", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Equity and cash: Use Framework 6 and Chapters 4 and 15 for capitalization, dilution, financing, and cash consequences. - People and law: Use Chapter 2 and qualified employment, tax, securities, IP, and corporate advisers. - Decision process: Use Chapter 7 for team conflict and authority dynamics; use Chapter 21 for product/IP ownership questions. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-6", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview-6", "url": "#chapter-13-startup-foundations-overview-6", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The equity distribution model is a constructed cap-table exercise for making ownership, dilution, control, and proceeds questions visible. Its percentages are fictional and do not recommend a founder split, option pool, financing term, or employee/advisor grant. Founder-equity research supports inquiry into allocation decisions, not universal bands. [BB-C13-S04] [BB-C13-S05]" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply-6", "url": "#chapter-13-startup-foundations-how-to-apply-6", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Start with the actual fully diluted capitalization and governing documents. Model option-pool timing, SAFEs/notes/warrants, price, new money, preferences, anti-dilution, vesting, taxes, conversion rights, approvals, control, and exit proceeds with counsel and authorized founders/boards. Table 13.1 — Constructed fully diluted cap-table illustration. The amounts and ownership percentages below are fictional, reconcile to 100 percent on the stated basis, and are not grant or financing recommendations. | Stakeholder | Shares | % | |-------------|--------|---| | Founder 1 (CEO) | 3,000,000 | 30 percent | | Founder 2 (CTO) | 2,500,000 | 25 percent | | Founder 3 (CPO) | 1,500,000 | 15 percent | | Employee Pool (unissued) | 1,500,000 | 15 percent | | Seed Investors (Series Seed) | 1,500,000 | 15 percent | | Total | 10,000,000 | 100 percent | Equity-allocation questions: Evidence on founder-equity decisions can inform the discussion, but the registered sources do not support universal percentage bands. [BB-C13-S04] [BB-C13-S05] Founders: - Discuss prior and future contribution, commitment, opportunity cost, role, cash/IP contributions, decision rights, control, financing, departure, and uncertainty. Do not infer a split from founder order alone. Employees: - Model an option or incentive pool from the hiring plan, market evidence, dilution, tax/securities/employment rules, administration, exercise economics, and board/shareholder authority. The chapter does not supply grant benchmarks. Advisors: - Define services, conflicts, confidentiality, IP, term, vesting or milestones, termination, securities/tax treatment, and approval before any grant. Dilution-model boundary: No universal founder/investor/pool path is defensible. Build a share ledger from the actual fully diluted capitalization, option-pool timing, SAFEs/notes/warrants, price per share, new money, preferences, anti-dilution, vesting, taxes, and conversion rights. Reconcile every event to 100 percent and separately model exit proceeds and control." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers-6", "url": "#chapter-13-startup-foundations-so-what-for-managers-6", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use a cap table to expose assumptions and consequences, not to make a negotiation look mathematically settled. - Test ownership, voting, economics, dilution, vesting, and downside outcomes under more than one financing or departure scenario. - Preserve a dated, approved share ledger and reconcile every change to the governing documents." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques-6", "url": "#chapter-13-startup-foundations-limits-and-critiques-6", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A percentage table omits preferences, voting, tax, vesting, conversion, information, and control rights unless modeled explicitly. - Founder-equity studies describe patterns and tradeoffs; they do not establish a fair split for a particular team. - A fully diluted total can be arithmetically correct while the underlying issuance, consent, tax, or securities treatment is invalid." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections-6", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections-6", "url": "#chapter-13-startup-foundations-connections-6", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Founder governance: Use Framework 5 for roles, decision rights, IP, departure, and counsel questions. - Financing: Use Frameworks 7 and 8 plus Chapter 15 for cash needs, dilution, instruments, and financing alternatives. - Strategy and people: Use Chapters 7 and 21 to connect ownership and control to team incentives and product/IP decisions. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-7", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview-7", "url": "#chapter-13-startup-foundations-overview-7", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The burn-rate calculation is a constructed cash-reconciliation aid, not an accounting definition, forecast, or fundraising rule. The simplified quotient is informative only after financing, investing, transfers, other non-operating movements, and period consistency are reconciled." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply-7", "url": "#chapter-13-startup-foundations-how-to-apply-7", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use a reconciled cash-flow model where possible. If using the simplified quotient, state the period, opening and closing cash, included and excluded movements, currency, restrictions, and the decision the estimate will inform. This is a constructed cash-arithmetic example, not an accounting definition or forecast. The simplified change-in-cash formula is usable only after excluding financing, investing, transfers, and other non-operating cash movements and confirming a consistent measurement period; otherwise use a reconciled cash-flow model. Formula: Components: Cash Out (Burn): - Salaries + benefits - Office/rent - Software/tools - Marketing/advertising - Professional services (legal, accounting) - Servers/infrastructure Operating Cash In: - Revenue and collections - Financing proceeds are recorded separately and are not operating cash inflows. Operating Net Cash Burn = Operating Cash Outflows - Operating Cash Inflows Example: - Cash out: $80K/month - Revenue: $20K/month - Net burn: $60K/month" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers-7", "url": "#chapter-13-startup-foundations-so-what-for-managers-7", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Treat burn as a cash movement to reconcile, not as a label for total expense or a forecast of future cash need. - Separate operating cash, financing, investing, transfers, working capital, taxes, commitments, and one-time movements. - Use the result to compare scenarios and preserve options, not to authorize hiring or financing by itself." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques-7", "url": "#chapter-13-startup-foundations-limits-and-critiques-7", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A stable-average quotient hides seasonality, step changes, restricted cash, financing timing, and obligations. - Net burn can be positive, negative, or undefined depending on revenue, working capital, financing, and measurement choices. - Cash arithmetic does not establish accounting treatment, solvency, tax compliance, or the probability that financing will close." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections-7", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections-7", "url": "#chapter-13-startup-foundations-connections-7", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Runway: Use Framework 8 to translate reconciled cash into downside scenarios and financing lead time. - Finance: Use Chapter 4 for financial statements, working capital, and valuation; use Chapter 15 for capital choices. - Governance: Use Framework 5 and authorized boards/finance/counsel for compensation, commitments, and financing decisions. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-8", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview-8", "url": "#chapter-13-startup-foundations-overview-8", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Runway planning is an author-created scenario aid for estimating how long available cash may support a defined operating plan. It is not a universal 18/12/6-month fundraising calendar, a solvency conclusion, or a promise that financing will close." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply-8", "url": "#chapter-13-startup-foundations-how-to-apply-8", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Model downside, base, and upside cash flows with revenue timing, working capital, commitments, hiring, taxes, financing probability and lead time, covenants, dilution, approvals, and failure-to-close cases. Set decision triggers early enough to preserve lawful options. This is an author-created scenario-planning aid. The simple quotient below is a static illustration only when net burn is positive and reasonably stable; it is undefined or misleading when cash flows are seasonal, step-changing, financed, restricted, or net cash-generative. Runway Formula: Runway Management: Scenario-based financing calendar: - Forecast cash by month under downside, base, and upside operating cases. - Model financing alternatives, probability, lead time, diligence, approvals, covenants, dilution, and failure to close. - Set board-approved decision triggers early enough to preserve options; no universal 18/12/6-month sequence applies. Extending Runway: - Increase cash contribution: Test revenue, pricing, collection, margin, or working-capital options without assuming demand or legal feasibility. - Reduce or stage commitments: Compare hiring, marketing, product, vendor, and operating scenarios, including employee/customer effects. - Financing: Evaluate equity, debt, grants, customer funding, strategic capital, or other lawful options with finance, board, counsel, and tax advisers. - Payables: Do not extend payment unilaterally; assess contract, supplier continuity, prompt-payment law, and reputation. Constructed burn scenarios, not stage benchmarks:" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers-8", "url": "#chapter-13-startup-foundations-so-what-for-managers-8", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Start with a cash calendar and downside case, then identify the earliest reversible decision point. - Compare cost reductions, revenue, customer funding, grants, debt, equity, strategic capital, and pause/stop options under governing constraints. - Assign owners for cash reporting, financing preparation, approvals, employee/customer effects, and counsel review." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques-8", "url": "#chapter-13-startup-foundations-limits-and-critiques-8", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Cash balance divided by average net burn fails when cash flows are seasonal, step-changing, financed, restricted, or cash-generative. - “Extend runway” choices can create contract, employment, supplier, customer, tax, securities, or reputational consequences. - A longer runway is not automatically better if it preserves a weak hypothesis while consuming stakeholder trust or scarce resources." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections-8", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections-8", "url": "#chapter-13-startup-foundations-connections-8", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Burn: Use Framework 7 to define and reconcile the cash movements behind the scenario. - Venture choice: Use Framework 9 and Chapter 15 to compare pivot, pause, stop, bootstrap, grant, debt, and equity paths. - Operations: Use Chapters 4, 14, and 21 to connect cash assumptions to pricing, channels, delivery, and product capacity. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-9", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview-9", "url": "#chapter-13-startup-foundations-overview-9", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The pivot decision is a conditional choice to change a venture hypothesis, customer, product, channel, value capture, technology, or architecture when evidence, constraints, or consequences make the current path unattractive. Ries supports pivot-or-persevere framing; the triggers below are an author-created checklist, not universal pivot rules. [BB-C13-S01]" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply-9", "url": "#chapter-13-startup-foundations-how-to-apply-9", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Predeclare the evidence, safety, legal, stakeholder, cash, and decision-authority conditions that would support persevering, revising, pausing, or stopping. Preserve useful assets and record what the team learned before changing direction. Ries's Lean Startup framework directly supports the pivot-or-persevere decision after Build-Measure-Learn evidence. [BB-C13-S01] The triggers and alternatives below are an author-created decision checklist; they are not universal pivot rules. When to Pivot: - Validated learning shows hypothesis wrong - Market smaller than thought - Can't achieve unit economics (LTV < CAC) - Regulatory blockers - Can't build technology with available resources When to Persevere: - Signs of product-market fit (even if small) - Learning how to improve (not learning that it's wrong) - Traction improving month-over-month Selected pivot patterns: 1. Zoom-in: A feature becomes the primary product. 2. Zoom-out: The product becomes one feature of a broader offering. 3. Customer Segment: The same capability is tested with a different customer group. 4. Customer Need: Same customer, different problem 5. Platform: Product → platform or vice versa 6. Business Architecture: B2C → B2B, vice versa 7. Value Capture: Pricing model change 8. Channel: Sales/distribution change 9. Technology: Same solution, different technology Pivot Process: 1. Acknowledge current approach not working (data-driven) 2. Preserve what's working (don't throw out baby with bathwater) 3. Generate pivot options (team brainstorm) 4. Evaluate against criteria (market size, defensibility, team fit) 5. Test new hypothesis with MVP 6. Communicate to team, investors, customers" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers-9", "url": "#chapter-13-startup-foundations-so-what-for-managers-9", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Distinguish a changed hypothesis from an unstructured reaction to disappointing data. - Compare pivot cost, abandonment value, affected commitments, evidence quality, cash, and responsible alternatives. - Communicate what changes, what remains, who decides, and how affected stakeholders can challenge or exit." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques-9", "url": "#chapter-13-startup-foundations-limits-and-critiques-9", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Pivot categories can make a strategic change look tidy when identity, capability, regulation, contracts, and stakeholder commitments are entangled. - A “persevere” decision can be as biased as a pivot; sunk cost, founder identity, investor pressure, and optimism need explicit challenge. - Not every problem is solved by changing the product; capacity, governance, pricing, distribution, safety, or market timing may be the constraint." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections-9", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections-9", "url": "#chapter-13-startup-foundations-connections-9", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Learning evidence: Use Frameworks 1–4 to identify which assumption failed and what test could discriminate among alternatives. - Cash and ownership: Use Frameworks 5–8 and Chapter 15 to model financing, dilution, commitments, and runway effects. - GTM and product: Use Chapters 14 and 21 to evaluate customer, channel, positioning, technology, and portfolio implications. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-10", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview-10", "url": "#chapter-13-startup-foundations-overview-10", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scale-up readiness is an author-created checklist for testing whether a defined venture can responsibly increase activity, customers, complexity, or capital exposure. It is not a validated readiness standard, a SaaS-only rule set, or a predictor of success." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply-10", "url": "#chapter-13-startup-foundations-how-to-apply-10", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Select and define only the items relevant to the venture’s product, market, cash, controls, workforce, technology, customers, legal obligations, and operating model. State evidence, owner, horizon, uncertainty, and stop conditions for each item. This is an author-created readiness checklist, not a validated scale-up standard. Select, define, and test the items relevant to the venture's product, market, cash, controls, workforce, technology, customers, and legal obligations; checking every box does not establish readiness or predict success. Product: - [ ] PMF evidence triangulates survey, retention, use, paid behavior, referrals, alternatives, and segment-specific needs. [BB-C13-S08] [BB-C13-S09] - [ ] Unit economics use consistent cohort, gross-margin, retention, service-cost, cash-timing, and acquisition definitions. - [ ] Retention strong across the relevant cohort window - [ ] Recommendation and complaint evidence is interpreted with sample and context. - [ ] Product capacity, reliability, security, support, and failure modes are tested against the proposed scale scenario. Go-to-Market: - [ ] Sales evidence is sufficiently repeatable for the defined segment, motion, price, and decision; no universal customer count applies. - [ ] Channel economics validated - [ ] Ideal Customer Profile defined - [ ] Sales playbook documented - [ ] Marketing funnel optimized (conversion rates known) Team: - [ ] Leadership and capability gaps are defined from the scale plan rather than fixed titles or hiring counts. - [ ] Recruiting, onboarding, management capacity, and workforce obligations fit the scenario. - [ ] Culture defined and documented - [ ] Performance management system - [ ] Compensation bands established Operations: - [ ] Integrated cash, income, balance-sheet, and scenario model built for a decision-relevant horizon. - [ ] Metrics and review cadence match the operating decisions and evidence latency. - [ ] Board and management governance follows the entity documents and financing obligations. - [ ] Customer success function started - [ ] Legal/compliance foundation (contracts, privacy, etc.) Funding: - [ ] Runway and financing triggers are approved under downside scenarios and alternative-capital paths. - [ ] Financing materials match the selected capital strategy and comply with securities/disclosure requirements. - [ ] Investor relationships warm - [ ] Financial targets for next round clear Constructed venture-backed SaaS milestones: These values illustrate how a team might state a financing hypothesis; they are not current market benchmarks or universal round gates." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers-10", "url": "#chapter-13-startup-foundations-so-what-for-managers-10", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Treat readiness as a decision-specific evidence review, not a scorecard that grants permission to scale. - Test capacity, quality, reliability, security, support, workforce, governance, cash, and legal obligations alongside demand and economics. - Make the cost and reversibility of scaling visible before increasing fixed commitments or exposure." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques-10", "url": "#chapter-13-startup-foundations-limits-and-critiques-10", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A checklist can create false completeness when the omitted dependency or failure mode is the material one. - SaaS metrics, round milestones, titles, and customer-success practices do not generalize to every venture type. - Strong early evidence does not remove financing, execution, competition, regulation, or organizational risks." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections-10", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections-10", "url": "#chapter-13-startup-foundations-connections-10", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Fit and economics: Use Framework 4 and Chapters 4 and 15 for segment evidence, margin, cash, and capital. - Market and product: Use Chapters 14 and 21 for channel capacity, product quality, adoption, and roadmap tradeoffs. - Governance and risk: Use Frameworks 5, 7, and 8 plus Chapter 2 for authority, controls, legal, employment, and disclosure duties. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-get-started", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How To Get Started", "headingId": "chapter-13-startup-foundations-how-to-get-started", "url": "#chapter-13-startup-foundations-how-to-get-started", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed-methodology boundary: The quick and detailed paths below are fictional venture-backed software scenarios. Their weeks, budgets, interview counts, conversion rates, PMF cutoffs, LTV:CAC ratios, payback periods, ownership, and funding milestones are illustrative inputs—not validation standards. Labels such as “red flag,” “go,” “no-go,” “pass,” “pivot,” and “scale” are prompts for a human-owned, venture-specific decision rule. Replace every value with a defined metric, denominator, observation window, evidence-quality standard, cash exposure, legal/safety condition, owner, and support/revise/pause/stop rule." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-quick-version-rapid-mvp-validation-2-3-weeks", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Quick Version: Rapid MVP Validation (2-3 Weeks)", "headingId": "chapter-13-startup-foundations-quick-version-rapid-mvp-validation-2-3-weeks", "url": "#chapter-13-startup-foundations-quick-version-rapid-mvp-validation-2-3-weeks", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Test your core hypothesis and assess product-market fit potential with minimal investment. Timeline: Day 1-2: Hypothesis Definition - Define your core hypothesis: \"We believe [customer segment] has [problem] and will [desired action] for [solution]\" - Write problem statement (1 paragraph) - Define success metrics (e.g., \"20 percent of interviews confirm severe pain\") - Create interview script with 10 open-ended questions - Identify 50 potential interview targets Example: Day 3-7: Customer Interviews (Week 1) - Conduct 20-30 customer interviews (4-6 per day) - Ask: \"Tell me about the last time you struggled with [problem]\" - Listen for: Frequency, severity, current workarounds, willingness to pay - Document: Problem validation (yes/no), pain level (1-10), buying signals - Synthesize patterns by Friday Red Flag: If below 30 percent of interviews confirm problem severity, pivot hypothesis. Week 2: MVP Scope Definition - Select MVP type: Smoke test (landing page), Concierge (manual), or Single-Feature - Define the ONE core feature that solves the validated problem - Create MVP specification (1 page): What it does, what it doesn't do, success metrics - Build/launch MVP (landing page in 2 days, concierge in 5 days) - Set measurement: Conversion rate, sign-ups, or paid pilots Example MVP (Landing Page): Week 3: Launch and Measure - Drive 100-500 people to MVP (personal network, LinkedIn, targeted ads $200 budget) - Measure: Conversion rate (sign-ups/visitors), engagement (email opens), feedback quality - Conduct 10 follow-up interviews with engaged users - Calculate preliminary PMF score: \"How disappointed if product unavailable?\" - Document findings in 1-page memo Output: 1-Page MVP Launch Plan Investment: 40-60 hours, $0-500 budget ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-detailed-version-full-startup-launch-cycle-8-12-weeks", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Detailed Version: Full Startup Launch Cycle (8-12 Weeks)", "headingId": "chapter-13-startup-foundations-detailed-version-full-startup-launch-cycle-8-12-weeks", "url": "#chapter-13-startup-foundations-detailed-version-full-startup-launch-cycle-8-12-weeks", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Go from idea to validated business with paying customers, repeatable sales process, and clear unit economics." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-phase-1-customer-discovery-week-1-2", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 1: Customer Discovery (Week 1-2)", "headingId": "chapter-13-startup-foundations-phase-1-customer-discovery-week-1-2", "url": "#chapter-13-startup-foundations-phase-1-customer-discovery-week-1-2", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 1: Problem Validation - Define 3 customer hypotheses (job title, company size, use case) - Create interview guide: 15 questions focused on problem (not solution) - Recruit 50 interview targets per segment (150 total) - Conduct 50+ interviews (5 per day) - Key questions: - \"Walk me through your process for [task related to problem]\" - \"What's the hardest part about [problem area]?\" - \"What have you tried to solve this?\" - \"How much does this problem cost you? (time/money)\" Deliverable: Problem Validation Memo Week 2: Solution Exploration - Narrow to 1 customer segment (ICP) - Conduct 30 solution interviews (show mockups, not product) - Test 3 value propositions (A/B/C messaging) - Validate pricing: \"Would you pay $X for this?\" (test 3 price points) - Map customer journey: Awareness → Consideration → Purchase → Use → Renewal Deliverable: Solution Blueprint" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-phase-2-mvp-design-build-week-3-4", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 2: MVP Design & Build (Week 3-4)", "headingId": "chapter-13-startup-foundations-phase-2-mvp-design-build-week-3-4", "url": "#chapter-13-startup-foundations-phase-2-mvp-design-build-week-3-4", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 3: MVP Specification - Select MVP type based on validation: - Concierge: Manual delivery for 10 customers (fastest validation) - Wizard of Oz: Appears automated, manual backend - Single-feature product: One core feature, well-built - Write product spec (3 pages): - User stories (5-10) - Core workflow (step-by-step) - What's NOT included (critical: avoid scope creep) - Success metrics (usage, retention, referral) - Design wireframes or clickable prototype - Plan 2-week build sprint Red Flag: If MVP spec is 10 pages or will take 2 weeks, it's not minimum. Week 4: Build MVP - Build (or manually deliver) MVP - Test with 3-5 design partners (give free access for feedback) - Iterate based on feedback (fix critical bugs only) - Create onboarding process (email sequence, tutorial, support docs) - Set up measurement: Analytics, NPS questionnaire, retention cohorts Deliverable: Launched MVP" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-phase-3-customer-validation-week-5-8", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 3: Customer Validation (Week 5-8)", "headingId": "chapter-13-startup-foundations-phase-3-customer-validation-week-5-8", "url": "#chapter-13-startup-foundations-phase-3-customer-validation-week-5-8", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 5-6: First 10 Paying Customers - Define sales process: - Lead source (outbound, referral, content) - Qualification: define the buying process, decision rights, need, timing, and evidence for this venture; BANT is optional and not a Chapter 13 framework. - Demo/pitch (30-min standard pitch) - Close (pricing, contract, onboarding) - Recruit 50 qualified leads - Conduct 30 sales conversations (close rate target: 33 percent) - Goal: 10 paying customers by end of Week 6 - Document objections and iterate pitch Success Metric: 10 customers acquired through SAME process (repeatability) Week 7-8: Retention & Iteration - Measure Week 1 retention (% still using after 7 days) - Conduct 10 customer success interviews: \"What would make this must-have?\" - Ship 2-3 improvements based on feedback - Test referral: \"Would you recommend to colleague?\" (NPS) - Calculate preliminary unit economics: - CAC: Cost to acquire 10 customers / 10 - LTV: Estimate expected contribution-margin value over a stated cohort horizon; do not use revenue as profit or a short retention proxy without sensitivity. - Decision rule: Define a locally justified comparison of contribution, acquisition cash, retention, service cost, payback, and uncertainty; no universal ratio applies. Deliverable: Validation Memo" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-phase-4-customer-creation-week-9-12", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 4: Customer Creation (Week 9-12)", "headingId": "chapter-13-startup-foundations-phase-4-customer-creation-week-9-12", "url": "#chapter-13-startup-foundations-phase-4-customer-creation-week-9-12", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 9-10: Scale Acquisition - Goal: 20 more customers (30 total by Week 10) - Test 3 acquisition channels: - Channel A: Outbound (LinkedIn, email) - Channel B: Content (blog, SEO) - Channel C: Paid (Google, Facebook ads - $1000 budget) - Measure cost-per-lead and cost-per-customer by channel - Hire or train salesperson (if B2B) or optimize funnel (if B2C) - Create sales playbook: Scripts, objection handling, closing tactics Week 11-12: Optimize & Plan - Analyze cohort retention (Week 4 cohort should be above 50 percent retained) - Optimize onboarding (reduce time-to-value) - Calculate real LTV based on 4-8 weeks of retention data - Model growth: \"If we spend $10K/month on ads, we get X customers at $Y CAC\" - Create 90-day roadmap: - Product improvements (from customer feedback) - Growth experiments (new channels, referral program) - Team hires (first sales, support, or engineering hire) Deliverable: Scale Plan" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-founder-governance-and-financial-planning-review", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Founder-governance and financial planning review", "headingId": "chapter-13-startup-foundations-founder-governance-and-financial-planning-review", "url": "#chapter-13-startup-foundations-founder-governance-and-financial-planning-review", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Before committing material time, money, ownership, or IP: Founder-governance issue-spotting checklist (Framework 5): - Discuss possible equity, vesting, transfer, departure, and decision-right provisions with qualified entity, tax, securities, employment, and IP counsel; no term shown here is standard or recommended. - Clarify roles and decision-making authority under the entity documents and any board/shareholder requirements. - Inventory pre-existing and new IP, assignments, licenses, open-source components, data, and contractor/employment obligations before relying on ownership assumptions. - Document the questions, owner, jurisdiction, evidence, approvals, and unresolved risks; do not treat this worksheet as a founders' agreement. Constructed burn-rate planning illustration (Frameworks 7–8): Constructed equity distribution illustration (Framework 6): The following is a fully diluted, pre-/post-financing arithmetic example only. It does not recommend a founder split, option pool, investor percentage, or financing term. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-common-pitfalls-and-how-to-avoid-them", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Common Pitfalls (And How to Avoid Them)", "headingId": "chapter-13-startup-foundations-common-pitfalls-and-how-to-avoid-them", "url": "#chapter-13-startup-foundations-common-pitfalls-and-how-to-avoid-them", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Building Without Validation - Risk: Committing substantial resources before testing material customer, technical, regulatory, or operating assumptions - Symptom: \"We'll talk to customers once product is ready\" - Response: Select proportionate discovery, prototype, technical, regulatory, or demand tests from consequence, heterogeneity, access, precision, ethics, and cost. No interview count validates demand. - Evidence gap: The team cannot identify credible affected users, buyers, alternatives, or disconfirming evidence 2. Too Few Customer Conversations - Risk: Treating a convenience sample or repeated interview theme as validation - Symptom: \"Everyone I talked to loved the idea!\" (selection bias) - Response: Continue sampling until the decision has adequate coverage of segments, buying roles, alternatives, negative cases, and uncertainty; triangulate interviews with behavior, transactions, experiments, and market evidence. - Evidence gap: Recruitment, questioning, coding, or missing negative cases make the inference unreliable 3. MVP Isn't Minimum - Risk: An experiment carries scope that does not improve the target decision - Symptom: \"We need just one more feature before we can launch\" - Response: Choose the smallest ethical test that can produce decision-relevant evidence. A concierge workflow, demonstration, simulation, technical study, regulated evidence package, or bounded product may fit different risks. - Evidence gap: Time, cost, features, or exposure grow without a clearer hypothesis, measure, guardrail, or stop rule 4. Ignoring Unit Economics - Risk: Increasing acquisition without defined cohort contribution, retention, service cost, cash timing, capacity, and uncertainty - Symptom: \"We'll figure out monetization later\" or \"We just need more users\" - Response: Model economics as soon as the available observations support the decision; no fixed week or ratio proves that scaling is safe or valuable. - Red Flag: Committing material advertising spend without measuring acquisition cost, retention, and customer lifetime value 5. No founder-governance record - Mistake: \"We're friends, we don't need a contract\" - Symptom: Handshake deal on equity, no vesting, no documentation - Fix: Use Framework 5 as an issue-spotting checklist, assign the relevant legal, tax, securities, employment, IP, and governance owners, and obtain qualified review before relying on any term. - Red Flag: Equity disputes 12 months in; cofounder leaves with 40 percent equity after 3 months of work ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-measurement-framework", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Measurement Framework", "headingId": "chapter-13-startup-foundations-measurement-framework", "url": "#chapter-13-startup-foundations-measurement-framework", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 13.2 — Constructed weekly venture-evidence tracker. The rows and values are placeholders for a decision-specific worksheet, not interview, conversion, or validation benchmarks. | Week | Hypothesis Tested | Validated (Y/N) | Customer Convos | Sign-ups/Sales | Key Learning | |------|-------------------|-----------------|----------------|----------------|--------------| | 1 | [Problem hypothesis] | Y/N | 25 | 0 | [Insight] | | 2 | [Solution hypothesis] | Y/N | 30 | 0 | [Insight] | | 3 | [MVP build] | - | 5 | 0 | [Insight] | | 4 | [MVP launch] | Y/N | 10 | 5 | [Insight] | | 5-6 | [Sales process] | Y/N | 30 | 10 | [Insight] | | 7-8 | [Retention/PMF] | Y/N | 10 | 5 | [Insight] | | 9-10 | [Channel A] | Y/N | 20 | 20 | [Insight] | | 11-12| [Scale readiness] | Y/N | 10 | 10 | [Insight] | Milestone Metrics (End of Week 12): Product-Market Fit: - [ ] PMF Score above 40 percent (\"very disappointed\" if product went away) - [ ] NPS 50 - [ ] Week 4 retention remains healthy - [ ] Daily Active / Monthly Active indicates recurring usage Commercial Validation: - [ ] 30+ paying customers - [ ] Documented paying demand, retention evidence, and a reconciled recurring-revenue measure - [ ] Contribution-margin economics, acquisition cash, retention, service cost, payback, and sensitivity are defined for the relevant cohort and decision horizon. - [ ] Any locally chosen CAC-payback tolerance is documented as an assumption with an owner and downside rule. Process Validation: - [ ] Repeatable sales process (can describe in playbook) - [ ] 2+ acquisition channels tested - [ ] ICP clearly defined (can describe ideal customer in 3 sentences) Team & Ops: - [ ] Founder-governance questions are documented and reviewed by the appropriate entity, tax, securities, employment, IP, and board owners. - [ ] 12+ months runway - [ ] Weekly metrics dashboard - [ ] Product roadmap (next 90 days) Illustrative readiness worksheet: ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-red-flags-when-your-startup-is-off-track", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flags: When Your Startup Is Off Track", "headingId": "chapter-13-startup-foundations-red-flags-when-your-startup-is-off-track", "url": "#chapter-13-startup-foundations-red-flags-when-your-startup-is-off-track", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Product Red Flags: - Retention declining month-over-month (Week 8 cohort < Week 4 cohort) - NPS <20 or trending down - Feature requests are all over the map (no clear pattern = no ICP) - Customers use product once and never return - Action: Return to Customer Development. Interview churned users. Market Red Flags: - Can't find 50 people who will take a free demo - Sales cycles getting longer (not shorter) - Discounting more than 20 percent to close deals - Win rate below 10 percent of qualified leads - Action: Validate ICP. May be wrong customer segment or messaging. Financial Red Flags (illustrative prompts, not universal thresholds): - CAC increasing month-over-month - LTV:CAC <1:1 (losing money on every customer) - Burn rate accelerating without revenue growth - <6 months runway and no funding plan - Action: Cut burn immediately. Extend runway to 12+ months before scaling. Team Red Flags: - Founders disagree on strategy (no decision-making process) - Cofounder not working full-time without discussion - Equity disputes (no vesting or agreement in place) - High early employee turnover (above 30 percent in first year) - Action: Hold a founder sync, review the Framework 5 issue-spotting checklist, and obtain appropriate governance or coaching support. Velocity Red Flags: - Stuck on same problem for 4+ weeks (analysis paralysis) - Haven't shipped product update in 4+ weeks - <10 customer conversations in past month - No experiments run in past month - Action: Return to Build-Measure-Learn cycle. Ship weekly. Scale Trap Red Flags: - Scaling acquisition before PMF (adding channels while retention is broken) - Hiring ahead of revenue (burning cash on team before validation) - Building features without customer requests (product-led, not customer-led) - Action: STOP scaling. Return to Customer Validation (Phase 3). ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-decision-tree-what-to-do-after-week-12", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Decision Tree: What To Do After Week 12", "headingId": "chapter-13-startup-foundations-decision-tree-what-to-do-after-week-12", "url": "#chapter-13-startup-foundations-decision-tree-what-to-do-after-week-12", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative stronger-evidence pattern (not a universal score): Illustrative mixed-evidence pattern (not a universal score): Illustrative insufficient-evidence pattern (not a universal score): --- Time Investment Summary: - Quick Version: 40-60 hours over 3 weeks - Detailed Version: 400-600 hours (full-time) over 12 weeks Financial Investment: - Quick Version: $0-500 (landing page, ads) - Detailed Version: $30K-90K (founder salaries, legal, tools, MVP, marketing) Evidence Boundary: Customer discovery, unit economics, and founder agreements are practices to test, not universal performance multipliers. BLS tracks business-establishment survival by birth cohort and reports that survival varies by both cohort and industry; its data do not measure product-market fit, Series A outcomes, or the effect of founder agreements. [BB-C13-S07] ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-11", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-13-startup-foundations-overview-11", "url": "#chapter-13-startup-foundations-overview-11", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The venture-pathway framework distinguishes organic startup creation, entrepreneurship through acquisition, sponsor-backed acquisition, and corporate acquisition. The comparison, screens, and stop gates are author-created decision aids; the bounded literature statements appear below." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-how-to-apply-11", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-13-startup-foundations-how-to-apply-11", "url": "#chapter-13-startup-foundations-how-to-apply-11", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "State the desired role, control, horizon, resources, thesis, alternatives, evidence, financing, governance, and downside limit before choosing a path. Treat path selection as a reversible next-step decision, not a commitment to close or scale. Entrepreneurship does not always begin with a new legal entity and a product built from zero. Entrepreneurship through acquisition (ETA) is an entry path in which an entrepreneur acquires and operates an existing business. The literature also covers management buy-ins, buy-outs, search funds, and business takeover as related but not identical forms. The evidence base remains much smaller and less standardized than the venture-creation literature, so a manager should not treat one search-fund cohort, return statistic, or acquisition story as a general forecast. [BB-C13-S11] [BB-C13-S12] Stanford's 2024 study reports on U.S. and Canadian search funds formed since 1984, using data through December 31, 2023. It is useful cohort evidence about the traditional search-fund model, but its population, definitions, reporting, vintage mix, and observed outcomes do not establish the probability or return of a new searcher, self-funded search, sponsor-backed deal, or corporate acquisition. [BB-C13-S10] Figure 13.2. Venture-path selection with evidence and stop gates (author-created synthesis). The four paths begin with different starting assets and capital structures, but each requires a stated thesis, evidence review, financing and governance fit, and a downside decision. The figure distinguishes a path choice from a commitment to close; the literature markers apply to the bounded ETA statements above, not to this complete decision logic. Text equivalent: A manager first states the desired role, control, time horizon, resources, and problem thesis. A greenfield opportunity leads to an organic startup test. A desire to own and operate an existing firm leads to search/ETA. A sponsor's return mandate and capital platform lead to a sponsor-backed acquisition. A strategic capability or portfolio need inside an existing company leads to a corporate acquisition. Every path then passes evidence, capital, governance, and downside gates. Failure at a gate produces revise, pause, or stop rather than automatic closing or continued investment." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-manager-facing-path-comparison", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Manager-facing path comparison", "headingId": "chapter-13-startup-foundations-manager-facing-path-comparison", "url": "#chapter-13-startup-foundations-manager-facing-path-comparison", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 13.3 — Author-created venture-path comparison. The table compares managerial jobs, evidence, capital, risks, and stop gates as a constructed decision aid; it is not a taxonomy, ranking, or forecast. The ETA literature above informs only the bounded pathway/form distinctions. | Path | Primary managerial job | Starting evidence | Capital and ownership | Distinct risks | Example stop gate | | :--- | :--- | :--- | :--- | :--- | :--- | | Organic startup | Discover and build a repeatable offering and operating system | Problem, demand, technical, regulatory, and unit-economic hypotheses | Founder/customer/grant/debt/equity mix; ownership is created and then allocated | No operating base, unproven demand, build and timing risk | Stop or redesign when a critical hypothesis fails and no responsible test or financing path remains | | Search / ETA | Find, acquire, lead, and improve one existing business | Historical operations plus a new owner's thesis; both require verification | Search costs and acquisition equity may come from the entrepreneur and investors; acquisition debt and seller financing are transaction-dependent | No-deal search, weak records, owner dependence, concentration, leverage, and transition | Stop when validated cash generation, price, financing, control, or transition cannot survive the downside case | | Sponsor-backed acquisition | Invest through a fund or sponsor platform and govern toward a defined return mandate | Target history, industry thesis, financing market, and portfolio plan | Sponsor/fund equity plus transaction-specific debt and management incentives | Leverage, incentive conflict, holding-period pressure, refinancing, and portfolio governance | Stop when the investment committee cannot support returns after normalized cash, risk, fees, and downside financing | | Corporate acquisition | Add capability, customers, assets, talent, or market access to an existing company | Strategic fit, stand-alone value, synergies, integration capacity, and alternatives | Corporate cash, shares, debt, or combinations; control sits within corporate governance | Overpaying for projected synergies, integration disruption, culture/talent loss, and management distraction | Stop when stand-alone value plus risk-adjusted synergies does not justify price, integration cost, and opportunity cost | The table is a decision aid, not a taxonomy that resolves every hybrid deal. A self-funded search can use outside debt; an independent sponsor can resemble private equity; a corporation can acquire and preserve a stand-alone operator. Classify the actual control, economics, authority, and operating role , not the label." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-search-economics-before-deal-economics", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Search economics before deal economics", "headingId": "chapter-13-startup-foundations-search-economics-before-deal-economics", "url": "#chapter-13-startup-foundations-search-economics-before-deal-economics", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A searcher can lose time and cash without acquiring anything. Keep the search phase separate from the acquisition capitalization: \\[ \\text{Search cash requirement} = \\text{living draw} + \\text{sourcing} + \\text{travel} + \\text{professional fees} + \\text{broken-deal costs} + \\text{contingency} \\] \\[ \\text{Expected search outlay} = \\text{committed search cost} + \\sum i P(\\text{diligence stage }i)\\times \\text{incremental cost} i \\] These equations organize assumptions; they do not make the uncertain probabilities objective. Record who estimated each probability, what comparable evidence informs it, and the maximum cash and time that may be spent before an explicit renewal decision. The acquisition sources-and-uses model belongs in Chapter 15; search burn is not purchase equity, and a signed letter of intent is not a closed acquisition." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-constructed-acquisition-screening-case-northstar-field-services", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Constructed acquisition-screening case: Northstar Field Services", "headingId": "chapter-13-startup-foundations-constructed-acquisition-screening-case-northstar-field-services", "url": "#chapter-13-startup-foundations-constructed-acquisition-screening-case-northstar-field-services", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "All names and numbers below are fictional and illustrative. They are not market benchmarks, an acquisition recommendation, or a valuation opinion. This is an author-created constructed screen informed by the bounded evidence boundary above. An operator is considering Northstar Field Services , a regional maintenance company offered at $4.8 million . Management reports $5.0 million revenue , $800,000 EBITDA , and 65 percent contracted or recurring revenue . Initial materials also show that the largest customer supplies 28 percent of revenue , the seller personally originates 40 percent of new sales , and equipment inspection suggests $250,000 of near-term catch-up spending . Table 13.4 — Constructed acquisition-screening case. The signals, evidence requests, and implications are fictional teaching inputs, not market data, valuation advice, or a diligence conclusion. | Screen | Evidence required before advancing | Case signal | Decision implication | | :--- | :--- | :--- | :--- | | Thesis and role fit | Written operator thesis, authority, personal constraints, and alternatives | Role fits, but value still depends on seller transfer | Advance only if transition evidence is obtainable | | Customer quality | Customer-level invoices, contracts, renewals, churn, concentration, disputes, and references with permission | Largest customer is 28 percent | Model loss, repricing, and retention; set a concentration kill criterion | | Owner dependence | Lead sources, account ownership, approvals, relationships, and replacement cost | Seller originates 40 percent of new sales | Treat seller exit as an operating risk, not an add-back | | Cash conversion | Bank, ledger, receivables, payables, payroll, tax, capex, and working-capital reconciliation | EBITDA has not yet been reconciled to cash | Do not price or size debt from reported EBITDA alone | | Asset and compliance condition | Equipment records, maintenance, permits, safety, insurance, claims, cyber, privacy, and regulatory review | $250,000 catch-up estimate | Validate scope and timing; include it in price and liquidity cases | | Financing and governance | Sources and uses, debt service, guarantees, investor rights, board, covenants, and downside liquidity | Not yet underwritten | No binding commitment until the capital and authority model passes | Screening decision: proceed only to a capped, staged diligence plan; do not sign an unconditional purchase agreement or anchor value to the reported multiple. The next decision is revise, advance, pause, or stop after customer concentration, normalized earnings, catch-up spending, financing, and seller-transition evidence are tested. Stop if the top-customer downside or seller-replacement case breaches liquidity, if required records cannot be reconciled, or if the governance/guarantee package exceeds the operator's approved risk limit." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-applied-exercise-acquisition-path-and-screen-memo", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Applied exercise — acquisition path and screen memo", "headingId": "chapter-13-startup-foundations-applied-exercise-acquisition-path-and-screen-memo", "url": "#chapter-13-startup-foundations-applied-exercise-acquisition-path-and-screen-memo", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Choose one business opportunity and compare all four paths, including the no-transaction alternative. 2. Build a search budget with a maximum time, maximum cash, stage probabilities labeled as judgments, and a renewal date. 3. Create an eight-row target screen covering thesis, customers, owner dependence, cash conversion, people, assets/technology, compliance, and transition. 4. Predeclare three kill criteria and identify the evidence owner for each. 5. Write a one-page advance / revise / pause / stop memo. Separate observed facts, seller representations, third-party evidence, assumptions, and unknowns. 6. Carry the same case into Chapter 15 to model sources and uses, dilution, debt service, quality of earnings, governance, and closing/transition gates." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-so-what-for-managers-11", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-13-startup-foundations-so-what-for-managers-11", "url": "#chapter-13-startup-foundations-so-what-for-managers-11", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Compare the job, control, capital, evidence, and downside of each path before adopting its label or financing logic. - Separate search costs, purchase price, operating cash, financing, transition, and integration risks. - Require staged evidence and an authorized stop or reprice decision before irreversible commitments." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-limits-and-critiques-11", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-13-startup-foundations-limits-and-critiques-11", "url": "#chapter-13-startup-foundations-limits-and-critiques-11", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- ETA, search funds, sponsor-backed deals, and corporate acquisitions are heterogeneous forms with different populations, incentives, controls, and evidence bases. - A cohort study or acquisition story does not forecast an individual searcher, target, geography, financing package, or outcome. - A screening table organizes diligence questions; it does not replace quality-of-earnings, legal, tax, regulatory, environmental, cyber, employment, or financing review." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-connections-11", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-13-startup-foundations-connections-11", "url": "#chapter-13-startup-foundations-connections-11", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Organic venture: Use Frameworks 1–4 and Chapters 5, 14, and 21 for evidence, customers, channels, and product decisions. - Capital and ownership: Use Frameworks 5–8 and Chapter 15 for capitalization, debt, dilution, sources and uses, and governance. - Acquisition diligence: Use Chapter 2 and specialist counsel for contracts, IP, privacy, employment, compliance, insurance, and transition obligations. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-why-this-matters-mental-models-startup-wisdom", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Why This Matters: Mental Models & Startup Wisdom", "headingId": "chapter-13-startup-foundations-why-this-matters-mental-models-startup-wisdom", "url": "#chapter-13-startup-foundations-why-this-matters-mental-models-startup-wisdom", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Understanding startup frameworks is one thing - knowing why they work (and when they fail) is what separates successful founders from those who follow formulas blindly. This section explores the psychological, economic, and strategic principles underlying startup best practices, examines high-profile failures that ignored these principles, contrasts competing methodologies, and explains how the right approach depends on your stage." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-1-customer-discovery-founder-bias-and-reality-testing", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "1. Customer Discovery: Founder Bias and Reality Testing", "headingId": "chapter-13-startup-foundations-1-customer-discovery-founder-bias-and-reality-testing", "url": "#chapter-13-startup-foundations-1-customer-discovery-founder-bias-and-reality-testing", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Psychology: Founders suffer from \"confirmation bias\" - the human tendency to seek information that confirms our existing beliefs and ignore contradictory evidence. When you have a product idea you're passionate about, your brain naturally filters for signals that support it. Customer discovery is a deliberate counter-mechanism: structured conversations designed to surface disconfirming evidence before you've invested months building the wrong thing. The Economics: Building without validation wastes the scarcest startup resource: time. If your core hypothesis is wrong, every day spent coding, designing, or marketing is compounded waste. Customer discovery front-loads learning - spending 40 hours in interviews can prevent 400 hours building something nobody wants. The economic principle: validate assumptions at lowest cost before increasing investment . Why It Works: - Forces falsification: Good customer discovery asks \"What would prove me wrong?\" not \"Who will validate me?\" - Surfaces hidden needs: Customers reveal real problems in stories (\"Last Tuesday I spent 3 hours...\") not in hypotheticals (\"Would you use...?\") - Identifies willingness to pay: Observing current behavior (what they actually spend time/money on today) predicts future behavior better than stated preferences - Builds market hypotheses: Diverse conversations can reveal language, alternatives, and patterns, but more interviews do not replace behavioral, transaction, technical, regulatory, or desk evidence. The Failure Mode: Skipping or biasing discovery leaves material demand assumptions untested. Some innovations require evidence beyond customers' stated preferences, but the chapter has no defensible 1,000:1 base rate; use behavior, experiments, technical feasibility, regulation, and alternatives to test the venture." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-2-mvp-lean-experimentation-and-minimal-waste", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "2. MVP: Lean Experimentation and Minimal Waste", "headingId": "chapter-13-startup-foundations-2-mvp-lean-experimentation-and-minimal-waste", "url": "#chapter-13-startup-foundations-2-mvp-lean-experimentation-and-minimal-waste", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Core Principle: The MVP framework operationalizes the scientific method for startups. Traditional product development follows a \"waterfall\" model: research → design → build → test → launch. This bundles all uncertainty into one big bet. MVP inverts this: launch → test → learn → iterate. Each cycle reduces uncertainty about one specific hypothesis. Why Minimum Matters: Scope creep is the natural enemy of learning. Teams instinctively want to build \"complete\" products because incomplete feels embarrassing. But completeness delays learning. The MVP principle forces uncomfortable trade-offs: what is the absolute minimum that tests our core hypothesis? Every feature beyond that minimum adds cost without adding learning. Why Viable Matters: \"Minimum\" without \"viable\" leads to testing garbage and learning nothing. If your MVP is so bad that customers bounce immediately, you don't learn whether your core value proposition works - you only learn that bad execution fails. Viable means: minimum quality to test whether the core value hypothesis is true . The Economics of Optionality: In a constructed comparison, a $5K landing-page test that invalidates a hypothesis risks less committed capital than a $500K fully built product. The amounts are illustrative; the decision should compare information value, validity, affected stakeholders, reversibility, and total downside rather than assume that every smaller test is safer. Why It Works: - Speed to learning: Days or weeks to validation vs. months - Capital efficiency: Test before scaling investment - Iteration cycles: Multiple shots on goal vs. one big bet - Market feedback: Real customer behavior vs. opinions The Failure Mode: Teams misinterpret MVP as \"ship crap fast.\" This creates a different failure: customers experience bad product, reject it, and you learn nothing about whether a good version would work. The balance: minimum completeness that still delivers core value ." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-3-unit-economics-predicting-scalability-before-scale", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "3. Unit Economics: Predicting Scalability Before Scale", "headingId": "chapter-13-startup-foundations-3-unit-economics-predicting-scalability-before-scale", "url": "#chapter-13-startup-foundations-3-unit-economics-predicting-scalability-before-scale", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The strategic question: Unit economics asks how contribution and cash change for an additional customer, order, transaction, seat, location, or other relevant unit. It is one input to scaling alongside capacity, working capital, quality, risk, fixed cost, competition, and customer evidence; small samples may not represent later cohorts. The math boundary: An LTV:CAC ratio is interpretable only when lifetime value is defined consistently—normally using expected gross-margin contribution or another explicit contribution measure rather than revenue—and acquisition cost includes the relevant sales and marketing cash. The ratio does not by itself prove profitability, scalability, or liquidity. Why no universal 3:1 rule applies: The practitioner ratio does not automatically account for support, product development, infrastructure, overhead, discounting, working capital, expansion, churn uncertainty, or payback timing. A customer generating $3,000 of revenue after $1,000 CAC has $2,000 of revenue net of CAC—not $2,000 of gross margin or profit. State every assumption and compare cash payback and sensitivity separately. This is an author-created synthesis, not a universal ratio rule. The Failure Mode: Growth-at-all-costs mentality ignores unit economics. Teams celebrate \"We grew 50 percent this month!\" while ignoring \"...but every new customer loses us $500.\" Investors eventually ask: \"When does this become profitable?\" If the answer is \"We're losing less per customer as we scale,\" that's defensible. If the answer is \"We haven't calculated it,\" that's fatal. Decision uses: - Expose cohort, pricing, retention, margin, service-cost, and acquisition assumptions early. - Compare channels and segments only after harmonizing definitions and cash timing. - Investigate why economics differ; CAC greater than LTV does not identify pricing or acquisition as the sole cause. The Nuance: Some models may show improving economics with scale, learning, density, or network effects, while others deteriorate through congestion, incentives, service burden, or competition. Treat the path as a testable scenario, not a defense by label." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-4-product-market-fit-a-multi-signal-judgment", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "4. Product-Market Fit: A multi-signal judgment", "headingId": "chapter-13-startup-foundations-4-product-market-fit-a-multi-signal-judgment", "url": "#chapter-13-startup-foundations-4-product-market-fit-a-multi-signal-judgment", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "What It Actually Measures: Product-market fit is not directly observed through one question. The “very disappointed” survey can provide one dependence signal, while paid behavior, retention, use, alternatives, complaints, referrals, margin, capacity, and segment evidence answer different questions. [BB-C13-S08] [BB-C13-S09] The Sean Ellis heuristic [BB-C13-S08]: The Sean Ellis test uses 40 percent “very disappointed” as a practitioner heuristic. Record sampling and exposure conditions and do not infer sustainable growth, retention, or causal performance from crossing it. [BB-C13-S08] Questions to test: - Does stated dependence predict retained, paid use for this segment and horizon? - Are referrals incremental, representative, and economically attractive? - Which defects or missing features create harm or unacceptable risk? - Does willingness to pay persist under a real price and alternative? The Failure Mode: Mistaking early traction for PMF. You get 100 customers - that's traction. But if only 20 percent would be \"very disappointed\" if you disappeared, you have weak PMF. These 100 customers won't refer friends, will churn when a competitor offers 20 percent off, and won't pay for premium features. Growth stalls at 500 customers and nobody knows why. Why It Works: An explicit PMF evidence review can slow premature scaling, but it cannot prevent it or establish that a product is “worth scaling.” Record who owns the decision, what evidence is sufficient, which risks remain, and what would trigger reversal. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-constructed-composite-examples-what-customer-validation-might-miss", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Constructed composite examples: What Customer Validation Might Miss", "headingId": "chapter-13-startup-foundations-constructed-composite-examples-what-customer-validation-might-miss", "url": "#chapter-13-startup-foundations-constructed-composite-examples-what-customer-validation-might-miss", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Evidence boundary: The three cases below are fictional composites inspired by recurring postmortem themes; they are not named-company histories or causal case studies. Failure postmortems are useful for identifying themes, not for estimating a universal startup failure rate. CB Insights' current report analyzes public records for 431 VC-backed companies that shut down since 2023 and notes that individual shutdowns rarely have a single cause. [BB-C13-S06]" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-case-1-on-demand-home-services-marketplace-ignored-unit-economics-until-it-was-too-late", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Case 1: On-Demand Home Services Marketplace - Ignored Unit Economics Until It Was Too Late", "headingId": "chapter-13-startup-foundations-case-1-on-demand-home-services-marketplace-ignored-unit-economics-until-it-was-too-late", "url": "#chapter-13-startup-foundations-case-1-on-demand-home-services-marketplace-ignored-unit-economics-until-it-was-too-late", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "What Happened: An on-demand home services marketplace raised substantial venture funding, expanded quickly, and then shut down after its growth model failed to produce sustainable unit economics. The Fatal Flaw: The company focused obsessively on growth (new customers, new cities) while ignoring unit economics. Its model had structural problems: - CAC Too High: Paid acquisition and promotions were too expensive for the revenue per customer - Low Repeat Rate: Many customers used the service occasionally rather than repeatedly - LTV Too Low: Customer lifetime value did not justify acquisition and operating costs - Result: Scaling amplified the economic weakness instead of fixing it What Customer Discovery Might Have Shown: Constructed interviews might have surfaced: \"I'd use home cleaning occasionally, but I'm not willing to build a relationship with a new cleaner when I have someone I trust.\" The teaching case tests whether the product solved a problem customers thought they had (finding cleaning help) while missing the real problem (building trust with someone entering your home). What They Did Instead: Raised more money and scaled the broken model into new markets. Each new market required upfront marketing investment to acquire customers who would not reliably retain. Scaling accelerated cash burn without fixing the core problem. The Learning: Unfavorable unit economics can compound with scale. In a constructed arithmetic example, a $50 contribution loss per customer produces a $5,000 loss at 100 customers and a $500,000 loss at 10,000 customers. Real decisions also require fixed costs, capacity effects, cohort behavior, cash timing, uncertainty, and the path by which economics may change. What Could Have Saved Them: - Earlier pivot: Test retention before scaling - Different model: Pivot to B2B (office cleaning with contracts) where retention is structural - Price increase: Test whether a higher-trust, higher-priced service improved retention - Stop scaling: Pause expansion, fix unit economics in one city, then expand" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-case-2-well-funded-photo-sharing-app-failed-product-market-fit", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Case 2: Well-Funded Photo-Sharing App - Failed Product-Market Fit", "headingId": "chapter-13-startup-foundations-case-2-well-funded-photo-sharing-app-failed-product-market-fit", "url": "#chapter-13-startup-foundations-case-2-well-funded-photo-sharing-app-failed-product-market-fit", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "What Happened: A well-funded photo-sharing app launched around a location-based sharing concept. It attracted attention before proving customer demand, then shut down the original consumer product and moved away from the initial concept. The Fatal Flaw: The company raised based on team pedigree and a large mobile-photo market narrative, but did not validate whether customers wanted the product. It spent a long build period developing technology before proving the customer problem. What Customer Discovery Might Have Shown: Constructed interviews might have surfaced: \"Why would I share photos with strangers nearby instead of with my friends?\" The teaching case tests how a value proposition can sound innovative while failing to solve a demonstrated customer problem. PMF Metrics at Launch: - Retention: Weak early return behavior - \"Very Disappointed\" Score: Likely weak because the product was a curiosity, not a dependency - Word-of-mouth: Minimal organic growth (no viral coefficient) - Time-to-value: Users couldn't figure out why the app existed What They Did Instead: Spent heavily building elaborate technology without validating: \"Do customers have this problem?\" They assumed product quality (technical sophistication) would create demand. It didn't. The Learning: Capital is not a substitute for product-market fit. Raising a massive round before validation creates pressure to execute the original plan (investors expect you to \"go big\"). But if the plan is wrong, more capital accelerates failure. The Lean Startup principle - raise money to scale what's working, not to figure out what works - exists to prevent this trap. What Could Have Saved Them: - MVP first: Launch a basic photo-sharing prototype in one neighborhood, test retention - Customer discovery: 100 interviews with target users asking \"How do you share photos today? What's frustrating?\" - Pivot faster: When early retention stayed weak, stop and pivot - Smaller raise: Raise enough to validate, then raise more only if PMF is achieved" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-case-3-connected-juicer-startup-solved-non-existent-problem", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Case 3: Connected Juicer Startup - Solved Non-Existent Problem", "headingId": "chapter-13-startup-foundations-case-3-connected-juicer-startup-solved-non-existent-problem", "url": "#chapter-13-startup-foundations-case-3-connected-juicer-startup-solved-non-existent-problem", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "What Happened: A connected juicer startup launched an expensive proprietary appliance around prepackaged juice. After scrutiny showed the hardware was not essential to the customer outcome, the company shut down. The Constructed Failure Hypothesis: The teaching case tests a venture assumption that nobody has the proposed problem. The founder assumed: \"People want fresh juice but don't want to clean a juicer.\" A proportionate discovery plan might reveal: - Non-users: People who don't juice don't care about juice freshness (they buy orange juice in cartons) - Current juicer users: People who already juice are willing to clean juicers (it's not the pain point) - Target market: The overlap - people who want juice but hate cleaning - was tiny What Customer Discovery Would Have Revealed: Interviews with 50 potential customers: - \"How often do you juice today?\" (Most: \"Never.\") - \"Why don't you juice?\" (Most: \"I don't care about juicing, not because cleaning is hard.\") - \"Would you pay a premium appliance price for a juicer?\" (Most would likely resist the price-value tradeoff.) - Key insight: The problem was interest in juicing , not juicer convenience . No amount of technology fixes lack of demand. What They Did Instead: Built sophisticated hardware and software to solve a problem customers didn't have. The product was a triumph of engineering and a failure of customer understanding. Why Investors Funded It: - Narrative: \"Keurig for juice\" is a compelling analogy (Keurig was successful) - Founder: Founder's passion and vision were persuasive - Market Size: Health and wellness is a huge market - What Was Missing: Evidence that customers wanted this specific product The Learning: Technology cannot create demand for something customers don't want. You can build the most sophisticated solution in the world, but if customers don't have the problem, they won't buy. Customer discovery exists to validate the problem before building the solution. What Could Have Saved Them: - Problem validation: Ask 500 people: \"Do you juice? If not, why not? If you do, what's the biggest pain point?\" - MVP: Sell juice packets at Whole Foods without the juicer; test demand for convenient juice delivery first - Pricing research: Ask target customers: \"How much would you pay for this?\" before committing to premium hardware - Stop at prototype: Build one prototype, test with 20 customers, measure: Did they use it after Week 1? (answer: no → pivot or stop) ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-competing-schools-different-philosophies-of-startup-building", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Competing Schools: Different Philosophies of Startup Building", "headingId": "chapter-13-startup-foundations-competing-schools-different-philosophies-of-startup-building", "url": "#chapter-13-startup-foundations-competing-schools-different-philosophies-of-startup-building", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Understanding competing methodologies helps founders choose the right approach for their context. Each school of thought has strengths, weaknesses, and situations where it excels." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-1-lean-startup-vs-traditional-business-planning", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "1. Lean Startup vs. Traditional Business Planning", "headingId": "chapter-13-startup-foundations-1-lean-startup-vs-traditional-business-planning", "url": "#chapter-13-startup-foundations-1-lean-startup-vs-traditional-business-planning", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Lean Startup Philosophy: - Core Belief: Speed through build-measure-learn loop is competitive advantage - Method: Launch fast, test hypotheses, iterate based on customer feedback - Capital Strategy: Raise small amounts, extend runway through learning - Success Metric: Validated learning (how fast are we disproving wrong assumptions?) - Best For: Uncertain markets, new product categories, resource-constrained teams Traditional Business Planning Philosophy: - Core Belief: Preparation and planning reduce risk - Method: Extensive research, detailed business plan, polished launch - Capital Strategy: Raise larger amounts upfront, execute against plan - Success Metric: Plan adherence (did we execute what we said we'd do?) - Best For: Established markets, replicating proven models, regulated industries The Trade-offs: Table 13.5 — Author-created comparison of learning philosophies. The dimensions and values are a constructed teaching contrast, not a complete or empirical ranking of methods. | Dimension | Lean Startup | Traditional Planning | |-----------|--------------|---------------------| | Speed to Market | Fast (weeks) | Slow (months) | | Preparation | Minimal (MVP) | Extensive (polished) | | Risk | Many small failures | One big bet | | Capital Need | Low upfront | High upfront | | Pivot Ability | High (expect pivots) | Low (locked into plan) | | Market Certainty | Low (test assumptions) | High (plan assumes certainty) | When Lean Startup Wins: - New markets: When customer behavior is unknown (e.g., first ridesharing app) - Technology risk: When technical feasibility is uncertain - Tight capital: When you can't afford to build the full vision before validating When Traditional Planning Wins: - Regulated industries: Healthcare, finance (need approvals before launch) - Capital-intensive: Hardware, biotech (can't \"iterate fast\" with 2-year development cycles) - Known markets: Franchise models, geographic expansion of proven concepts The Synthesis: Most successful startups blend both: Lean methods for product discovery (test the concept), traditional planning for scaling (execute the proven model). Use Lean Startup to find product-market fit, then switch to traditional execution discipline once you know what works." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-2-customer-first-vs-technology-first", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "2. Customer-First vs. Technology-First", "headingId": "chapter-13-startup-foundations-2-customer-first-vs-technology-first", "url": "#chapter-13-startup-foundations-2-customer-first-vs-technology-first", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Customer-First (Design Thinking) Philosophy: - Core Belief: Understand customer problems deeply before building solutions - Method: Ethnographic research, customer interviews, journey mapping - Product Development: Build what customers say they need - Validation: Customer feedback, usability testing, satisfaction scores - Best For: Improving existing product categories, B2B solutions, service businesses Technology-First (Product Innovation) Philosophy: - Core Belief: Breakthrough technology creates new demand customers didn't know they wanted - Method: Build what's technically possible, find product-market fit later - Product Development: Technology vision drives product; customers adopt when they see it - Validation: Adoption rate, market creation, paradigm shift - Best For: Deep tech, scientific breakthroughs, paradigm-shifting products The Tension: - Customer-first risk: Customers are limited by current experience. They'll ask for \"faster horses\" not cars. Over-indexing on customer feedback can prevent breakthrough innovation. - Technology-first risk: Build something technically impressive but commercially useless. Most \"breakthrough technology\" fails because there's no customer demand. Constructed examples: - A workflow venture begins with field observation and interviews, then tests whether a proposed tool changes actual behavior. - A science-based venture begins with technical feasibility, then tests applications, users, regulation, manufacturing, economics, and adoption. - A technically novel consumer device can still fail if the use context, alternatives, price, social acceptability, or distribution is wrong. The Synthesis: The best founders do both: 1. Customer-first for problem identification: Deep interviews reveal real pain points 2. Technology-first for solution innovation: Build solutions customers couldn't imagine 3. Customer validation: Test whether the innovative solution solves the real problem The synthesis is a loop: investigate problems and constraints, develop solution options, test feasibility and behavior, and update both problem and solution hypotheses." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-3-bootstrap-vs-venture-backed", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "3. Bootstrap vs. Venture-Backed", "headingId": "chapter-13-startup-foundations-3-bootstrap-vs-venture-backed", "url": "#chapter-13-startup-foundations-3-bootstrap-vs-venture-backed", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Bootstrap Philosophy: - Core Belief: Profitability from Day 1 ensures independence and sustainability - Capital Strategy: Self-funded or customer-funded; no outside investors - Growth Pace: Constrained by cashflow (grow as fast as revenue allows) - Control: Founders retain ownership and make the core decisions - Best For: Service businesses, niche products, lifestyle businesses, founder control-oriented Venture-Backed Philosophy: - Core Belief: Speed is competitive advantage; raise capital to accelerate growth before competition - Capital Strategy: Raise venture capital to fund growth before profitability - Growth Pace: Unconstrained by cashflow (grow as fast as market allows) - Control: Founders diluted, investors have board seats and veto rights - Best For: Winner-take-all markets, network effects, capital-intensive businesses The Trade-offs: Table 13.6 — Author-created bootstrap and venture-capital contrast. The dimensions and values are a constructed teaching contrast; capital, control, pressure, and upside vary by instrument, entity, market, and financing terms. | Dimension | Bootstrap | Venture-Backed | |-----------|-----------|----------------| | Growth Speed | Slow (cashflow-limited) | Fast (capital-fueled) | | Control | High (founder retains ownership) | Lower (investors share ownership and governance) | | Pressure | Low (no investor expectations) | High (grow or die) | | Optionality | High (can sell, hold, pivot freely) | Low (investors expect exit) | | Capital for Mistakes | None (every dollar counts) | High (can afford to test and fail) | | Upside | Larger share of a smaller outcome | Smaller share of a potentially huge outcome | When bootstrapping may fit: - Operating cash, customer funding, grants, or staged spending can finance the next evidence milestone - The founders value control and can bear the cash, concentration, and personal-risk trade-offs - A focused market or slower growth path supports the desired outcome When external equity may fit: - Credible milestones require capital beyond feasible operating, customer, grant, debt, or partner funding - Scale economies or network effects create option value, after testing multi-homing, congestion, governance, and competitive response - Hardware, life sciences, infrastructure, or regulated evidence requires material upfront investment and an equity risk profile - Competitor financing changes the scenario, but it does not prove that matching pace maximizes value Mixed capital paths: A venture can combine founder capital, operating cash, customer prepayment, grants, debt, strategic capital, and equity at different times. The appropriate sequence depends on cash need, risk, control, growth options, eligibility, covenants, and financing availability; named success stories do not establish a rule. The synthesis: The decision is not binary or sequentially fixed. Compare staged combinations against milestones, cash, control, covenants, eligibility, downside, stakeholder outcomes, and financing availability; revise as evidence changes. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-stage-dependency-right-tool-for-right-phase", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Stage Dependency: Right Tool for Right Phase", "headingId": "chapter-13-startup-foundations-stage-dependency-right-tool-for-right-phase", "url": "#chapter-13-startup-foundations-stage-dependency-right-tool-for-right-phase", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The stage labels and examples below are a constructed venture-backed software lens, not universal gates for services, marketplaces, hardware, life sciences, regulated ventures, bootstrapped firms, or social enterprises. Startup advice is context-dependent. A practice useful in one setting may transfer, require modification, or fail in another; stage labels alone do not determine that result. Use the sections below as constructed questions, not a maturity law." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-pre-launch-intense-customer-discovery-minimal-execution", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Pre-Launch: Intense Customer Discovery, Minimal Execution", "headingId": "chapter-13-startup-foundations-pre-launch-intense-customer-discovery-minimal-execution", "url": "#chapter-13-startup-foundations-pre-launch-intense-customer-discovery-minimal-execution", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Context: You have an idea but no product, no customers, no revenue. Your goal: validate whether anyone wants what you're building before you build it. What Matters Most: 1. Customer discovery: Select interviews and other evidence to cover relevant segments, roles, alternatives, negative cases, and decision uncertainty; no universal count or time allocation applies. 2. Problem evidence: Can you corroborate a consequential job or constraint through accounts, behavior, transactions, or operational evidence? 3. Willingness to Pay: Do they currently spend time or money on this problem? What Doesn't Matter Yet: - Unit economics: Early ranges may be highly uncertain; state what can and cannot yet be estimated. - Scale readiness: Use only the safety, quality, data, regulatory, and operating controls the current test requires. - Fundraising: Compare capital need, evidence, control, and alternatives rather than prohibiting pre-validation financing. Common Mistake: Building beyond what the next decision requires can delay learning. Customer conversations are one evidence source; poorly sampled or leading conversations can reinforce error rather than increase success probability. Success Metric: Can the team produce credible, diverse, and disconfirmable evidence about the job, alternatives, buying process, feasibility, and willingness to commit? Stated intent alone is not purchase evidence." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-early-traction-pmf-validation-unit-economics-focus", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Early Traction: PMF Validation, Unit Economics Focus", "headingId": "chapter-13-startup-foundations-early-traction-pmf-validation-unit-economics-focus", "url": "#chapter-13-startup-foundations-early-traction-pmf-validation-unit-economics-focus", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Context: You have a product and first 10-50 customers. Your goal: validate product-market fit and ensure unit economics work before scaling. What Matters Most: 1. Retention and outcomes: Define cohorts, observation windows, expected use, customer value, missingness, and guardrails. 2. PMF evidence: A disappointment survey is one practitioner heuristic, not proof; combine it with retained use, willingness to pay, alternatives, and customer outcomes. 3. Unit economics: Model cohort gross-margin contribution, acquisition, service cost, cash timing, retention, and uncertainty without a universal ratio. 4. Repeatability: Test whether an acquisition mechanism transfers across comparable cohorts without hidden founder labor or selection bias. What Doesn't Matter Yet: - Team building: Hire or delegate when skills, capacity, controls, and economics justify it; founder involvement is valuable but not an absolute requirement. - Process/systems: Add proportionate structure for safety, quality, compliance, learning, and coordination. - Fundraising: Balance customer evidence with runway, capital need, control, and financing alternatives. Common Mistake: Scaling acquisition before understanding retention can amplify waste or harm. A constructed comparison of 100 customers with 5 percent retention and 20 customers with 80 percent retention is only a prompt: cohort definitions, customer value, unit economics, selection, observation time, and uncertainty determine what either result means. Success Metric: Cohort analysis: compare recent and earlier cohorts at a justified observation window, with uncertainty and mix adjustment. An improvement is evidence to investigate—not proof of scale readiness; a decline can trigger diagnosis rather than an automatic stop." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-scaling-repeatable-customer-acquisition-operational-efficiency", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Scaling: Repeatable Customer Acquisition, Operational Efficiency", "headingId": "chapter-13-startup-foundations-scaling-repeatable-customer-acquisition-operational-efficiency", "url": "#chapter-13-startup-foundations-scaling-repeatable-customer-acquisition-operational-efficiency", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Context: The venture has some evidence of retained customer value and viable economics and is considering growth. The decision is whether and how to increase acquisition and delivery without assuming a universal growth target or predictable demand. What Matters Most: 1. Channel evidence: Compare incremental acquisition, cohort value, margin, cash timing, saturation, attribution uncertainty, and guardrails; a favorable historical LTV:CAC estimate does not justify automatically doubling spend. 2. Capability design: Test which sales, marketing, customer-success, partner, product, or founder capabilities are constrained and whether hiring, tooling, training, outsourcing, or redesign is the best response. 3. Process learning: Capture the minimum evidence, decisions, controls, and repeatable practices needed for execution and training without treating documentation as proof of transferability. 4. Capital Efficiency: Define a locally acceptable CAC-payback range from gross-margin cash, retention uncertainty, working capital, financing capacity, service cost, and downside tolerance. Twelve months may be an illustrative scenario input, not a universal threshold. What Doesn't Matter Yet: - Cash and profitability: Negative cash flow may or may not be supportable; evaluate runway, financing dependence, downside, obligations, contribution, and stakeholder consequences rather than granting an automatic exception for growth. - Product and delivery quality: Retention alone does not establish that the product is “good enough.” Preserve applicable safety, quality, reliability, accessibility, privacy, security, service, and customer-outcome thresholds while prioritizing improvements. Common Mistake: Scaling marketing or sales before understanding the operating mechanism can amplify variation and cost. In a constructed five-hire example, uneven outcomes could reflect selection, ramp time, territory, management, incentives, product, demand, or process—not simply a missing playbook. Test people, system, market, and implementation explanations together; neither “systems” nor “people” is universally primary. Success Metric: Test whether a new sales hire can execute the documented process and produce qualified progression within a locally justified ramp window. A 60-day first close may be an illustrative acceptance criterion for one sales cycle; it neither proves repeatability nor makes a longer cycle a failure." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-late-stage-growth-market-expansion-operational-excellence", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Late-Stage Growth: Market Expansion, Operational Excellence", "headingId": "chapter-13-startup-foundations-late-stage-growth-market-expansion-operational-excellence", "url": "#chapter-13-startup-foundations-late-stage-growth-market-expansion-operational-excellence", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Context: You have predictable revenue (millions in ARR), proven channels, and an established team. Your goal: expand into adjacent markets, geographies, or customer segments while maintaining efficiency. What Matters Most: 1. Market Expansion: Can you replicate success in adjacent segment or geography? 2. Operational Excellence: Margins, efficiency, retention at scale 3. Leadership Team: VPs who own functions (founders can't do everything) 4. Path to Profitability: State the assumptions and evidence under which the business could cover its costs; do not substitute a distant revenue slogan for a reconciled model. What Doesn't Matter As Much: - Founder hustle: You're no longer doing sales calls or customer support yourself - Scrappiness: Systems and processes matter more than resourcefulness now Common Mistake: Founders who can't let go. They insist on being involved in every decision, which creates bottlenecks. At this stage, founder job is: hire great leaders, give them autonomy, hold them accountable to metrics . Success Metric: Company grows meaningfully year over year without founders working unsustainable hours. If growth requires heroic founder effort, it won't scale. --- Key Takeaway: Context changes which uncertainties and constraints deserve attention. “Pre-launch,” “early,” “scaling,” and “late-stage” are teaching labels, not deterministic prescriptions. Tailor customer evidence, economics, controls, capabilities, leadership, and expansion choices to the venture and revise them as evidence changes. A tool can add cost or mislead when its assumptions do not fit; it does not by itself “kill” a startup. Hiring or manual acquisition decisions depend on the actual capability gap, sales motion, economics, controls, learning value, and alternatives—not a stage prohibition. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-constructed-operating-manual-your-12-week-mvp-validation-cycle", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Constructed Operating Manual: Your 12-Week MVP Validation Cycle", "headingId": "chapter-13-startup-foundations-constructed-operating-manual-your-12-week-mvp-validation-cycle", "url": "#chapter-13-startup-foundations-constructed-operating-manual-your-12-week-mvp-validation-cycle", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed operating-manual boundary: Every week, hour, budget, interview count, conversion target, PMF cutoff, LTV:CAC ratio, payback period, runway trigger, funding action, and “go/no-go” label below is fictional teaching material. It is not a benchmark, readiness standard, or proof of validation. Replace the sample with the venture type, safety and legal constraints, evidence latency, cash, decision owner, falsification rule, stakeholder obligations, and stop condition. A human owner must approve any operating or financing decision." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-overview-12-week-timeline", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview: 12-Week Timeline", "headingId": "chapter-13-startup-foundations-overview-12-week-timeline", "url": "#chapter-13-startup-foundations-overview-12-week-timeline", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The operating manual is structured in 5 phases: - Weeks 1-2: Problem Validation (10 days) - Weeks 3-4: Solution Validation (10 days) - Weeks 5-8: MVP Build (20 days) - Weeks 9-10: Launch & Initial Traction (10 days) - Weeks 11-12: Early Traction & Planning (10 days) Sample time and financial assumptions: The displayed 12-week sequence, 400-600 hours, and $30K-90K range are constructed scenario inputs. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-phase-1-problem-validation-weeks-1-2", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 1: Problem Validation (Weeks 1-2)", "headingId": "chapter-13-startup-foundations-phase-1-problem-validation-weeks-1-2", "url": "#chapter-13-startup-foundations-phase-1-problem-validation-weeks-1-2", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Validate that customers have the problem you think they have, and they're willing to pay to solve it." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-week-1-customer-discovery", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 1: Customer Discovery", "headingId": "chapter-13-startup-foundations-week-1-customer-discovery", "url": "#chapter-13-startup-foundations-week-1-customer-discovery", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Day 1-2: Customer Interview Planning (16 hours) - Activities: - Define 3 customer hypotheses (job title, company size, use case) - Create interview guide with 15 questions focused on problem (not solution) - Recruit 50 interview targets (25 per hypothesis) - Schedule 15-20 interviews for Week 1-2 - Output: Interview guide, scheduled interviews - Key questions to ask: - \"Walk me through your process for [task related to problem]\" - \"What's the hardest part about [problem area]?\" - \"What have you tried to solve this?\" - \"How much does this problem cost you? (time/money)\" - Red flag: Can't schedule 10+ interviews → ICP too narrow or problem not validated Day 3-5: Customer Interviews (24 hours) - Activities: - Conduct 15-20 customer interviews (5 per day) - Record notes (what they say, pain points, current solutions) - Track: Problem validation (yes/no), pain level (1-10), buying signals - Interview best practices: - Listen 80 percent, talk 20 percent - Ask \"Tell me about the last time...\" (gets specific stories) - Don't pitch your solution (you're learning, not selling) - Ask about willingness to pay: \"If solution existed, what would it be worth?\" - Output: 15-20 completed interviews, documented pain points - Red flag: below 50 percent confirm problem severity → Wrong ICP or imaginary problem" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-week-2-problem-analysis-icp-refinement", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 2: Problem Analysis & ICP Refinement", "headingId": "chapter-13-startup-foundations-week-2-problem-analysis-icp-refinement", "url": "#chapter-13-startup-foundations-week-2-problem-analysis-icp-refinement", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Day 1-2: Synthesis (16 hours) - Activities: - Review all interview notes - Identify patterns: Which customer segment has most severe pain? - Quantify pain: \"Costs them 20 hrs/week\" or \"$500K annually\" - Assess willingness to pay: above 60 percent said they'd pay → Good signal - Decision framework: - Problem severity (1-10 scale based on interviews) - Frequency (how often do they experience this problem?) - Willingness to pay (what % would pay for solution?) - Output: Problem validation scorecard Problem Validation Scorecard Template: Day 3-4: ICP Definition (16 hours) - Activities: - Narrow to 1 customer segment (who has problem most severely?) - Define ICP using the Chapter 14 go-to-market framework and document the evidence, segment boundaries, and uncertainty. - Document: Title, company size, geography, tech stack, pain severity - Output: 1-page ICP document - Red flag: Can't find 50 companies matching ICP → Market too small Day 5: Pivot or Proceed Decision (8 hours) - Activities: - Review Problem Validation Scorecard - Decision: Proceed, Pivot ICP, Pivot Problem, or Shut Down - If proceed: Document validated problem statement - If pivot: Return to Week 1 with new hypothesis - Output: Go/No-Go decision with evidence - Success metric: above 60 percent problem validation + above 40 percent willingness to pay Decision Gate #1: End of Week 2 - Illustrative evidence prompts (not thresholds): - Confirmed problem with above 60 percent of target customers - above 40 percent willing to pay for solution - Can identify 50+ companies matching ICP - Illustrative pause/revise prompts (not thresholds): - below 50 percent problem validation → Pivot to different customer segment - below 20 percent willingness to pay → Problem not painful enough - Can't find enough ICP matches → Market too small Contingency: If No-Go, you have two options: 1. Pivot to adjacent ICP (e.g., from SMB to Enterprise) 2. Pivot to adjacent problem (same customer, different pain point) 3. Shut down and save 10 weeks of wasted effort ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-phase-2-solution-validation-weeks-3-4", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 2: Solution Validation (Weeks 3-4)", "headingId": "chapter-13-startup-foundations-phase-2-solution-validation-weeks-3-4", "url": "#chapter-13-startup-foundations-phase-2-solution-validation-weeks-3-4", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Validate that your proposed solution solves the problem, and customers will pay for it." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-week-3-solution-concept-development", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 3: Solution Concept Development", "headingId": "chapter-13-startup-foundations-week-3-solution-concept-development", "url": "#chapter-13-startup-foundations-week-3-solution-concept-development", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Day 1-2: MVP Scope Definition (16 hours) - Activities: - Build simple prototype/mockup (not functional product) - Tools: Figma (design), PowerPoint (slides), Loom (video demo) - Define MVP scope: Minimum features needed to solve core problem - Create 3-5 slide pitch showing how solution works - MVP Litmus Test: - Is it viable ? (Solves real problem for real customer) - Is it minimum ? (Nothing extra that doesn't test core hypothesis) - Is it a product ? (Customers can use it, even if imperfect) - Output: Prototype/mockup, MVP spec sheet (1 page) - Red flag: MVP will take 6 weeks to build → Not minimum Day 3-4: Solution Validation Interviews (16 hours) - Activities: - Show prototype to 10 customers from Week 1-2 interviews - Ask: \"Does this solve your problem? How?\" \"What's missing?\" \"Would you use this?\" - Assess: Fit (does it solve problem?), Enthusiasm (are they excited?) - Test pricing: \"If this cost $X, would you buy it?\" (test 3 price points) - Interview script: - \"Here's what we're building [show prototype]\" - \"Does this solve the problem you described?\" - \"What would you change or add?\" - \"If this launched tomorrow at $X, would you buy it?\" - Output: 10 solution validation interviews - Red flag: below 50 percent say solution would solve their problem → Wrong solution Day 5: MVP Scoping (8 hours) - Activities: - Based on feedback, finalize MVP features (3-5 core features only) - Document what's IN: Must-have features - Document what's OUT: Nice-to-haves that can wait - Estimate build timeline: Should be 2-4 weeks max - Output: Final MVP spec sheet MVP Spec Sheet Template:" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-week-4-pricing-business-model", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 4: Pricing & Business Model", "headingId": "chapter-13-startup-foundations-week-4-pricing-business-model", "url": "#chapter-13-startup-foundations-week-4-pricing-business-model", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Day 1-2: Pricing Research (16 hours) - Activities: - Review willingness-to-pay data from interviews - Research competitor pricing (3-5 alternatives) - Calculate unit economics (estimated CAC vs LTV) - Select pricing model (subscription, one-time, usage-based) - Pricing framework: - Value-based: \"Saves customer $500K/year → Charge 20 percent = $100K\" - Competitive: \"Competitors charge $X, we'll charge X-20 percent (undercut)\" - Cost-plus: \"Estimate delivery cost, then test a proposed markup against willingness to pay, alternatives, and required margin\"; do not assume a universal multiplier. - Output: Pricing model decision, initial price point Day 3-4: Unit Economics Modeling (16 hours) - Activities: - Estimate CAC (cost to acquire one customer) - If outbound sales: Sales salary + tools / customers acquired - If inbound: Ad spend + marketing / customers acquired - Estimate LTV (customer lifetime value) - Pricing × expected retention period - Example: $99/month × 24 months = $2,376 LTV - Calculate LTV:CAC ratio (target: ≥3:1) - Output: Unit economics model (spreadsheet) - Red flag: LTV:CAC 2:1 - MVP build timeline ≤6 weeks - Have resources to build (technical co-founder or budget for developer) - Illustrative pause/revise prompts (not thresholds): - below 40 percent solution fit → Iterate on solution concept (don't build yet) - LTV:CAC 8 weeks → Scope too large, needs to be reduced Contingency: If No-Go: 1. Iterate solution: Return to Week 3 with different approach 2. Adjust pricing: If customers won't pay enough, either pivot to higher-value customer or different problem 3. Descope MVP: Cut features until build is ≤4 weeks ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-phase-3-mvp-build-weeks-5-8", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 3: MVP Build (Weeks 5-8)", "headingId": "chapter-13-startup-foundations-phase-3-mvp-build-weeks-5-8", "url": "#chapter-13-startup-foundations-phase-3-mvp-build-weeks-5-8", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Build minimum viable product and prepare for launch." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-weeks-5-6-development-sprint-1", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Weeks 5-6: Development Sprint 1", "headingId": "chapter-13-startup-foundations-weeks-5-6-development-sprint-1", "url": "#chapter-13-startup-foundations-weeks-5-6-development-sprint-1", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 5: Core Feature Development (40 hours) - Activities: - Set up development environment (code repo, hosting, databases) - Build Feature #1 (most critical feature first) - Daily standups (15 min): What did you build? What's blocking you? - End-of-week demo with 2-3 customer advisors (get early feedback) - Development best practices: - Ship working code weekly (not perfect, but functional) - Focus on core workflow (user signs up → uses feature → gets value) - Cut corners on polish (no beautiful UI yet, just functional) - Output: Feature #1 functional - Red flag: Feature #1 not working by end of Week 5 → Underestimated complexity Week 6: Remaining Features (40 hours) - Activities: - Build Feature #2 and #3 - Integrate features into cohesive workflow - Weekly check-in with customer advisors (5 people using beta) - Fix critical bugs (but don't chase perfection) - Output: MVP functional with 3-5 features - Red flag: Realized you need 10 more features → Scope creep, revisit MVP definition" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-weeks-7-8-beta-testing-refinement", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Weeks 7-8: Beta Testing & Refinement", "headingId": "chapter-13-startup-foundations-weeks-7-8-beta-testing-refinement", "url": "#chapter-13-startup-foundations-weeks-7-8-beta-testing-refinement", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 7: Beta Launch (40 hours) - Activities: - Recruit 10 beta customers (from Week 1-2 interviews) - Give free/discounted access in exchange for feedback - Set up analytics (track: signups, feature usage, time in product) - Monitor daily: Are people using it? Where do they get stuck? - Beta customer criteria: - Severe pain (will actually use product) - Willing to give feedback (not just free riders) - Representative of ICP (not edge cases) - Output: 10 beta customers actively using MVP - Red flag: <5 beta customers sign up → Product not compelling enough Week 8: Iteration & Polish (40 hours) - Activities: - Conduct 10 feedback interviews with beta users - Fix critical bugs (anything blocking usage) - Add small improvements based on feedback (but don't add big features) - Prepare for public launch: Onboarding flow, help docs (1 page) - Key questions for beta users: - \"What do you like about this?\" - \"What's confusing or frustrating?\" - \"Would you pay $X for this?\" - \"Would you recommend to a colleague?\" - Output: MVP ready for launch, feedback incorporated - Red flag: Beta users aren't using product after Week 1 → Product-market fit issue Decision Gate #3: End of Week 8 - Illustrative evidence prompts (not thresholds): - MVP functional and stable - ≥5 beta customers actively using (weekly active) - Positive feedback (above 50 percent would recommend) - Key metrics baseline: Activation (% who use in Week 1), Retention (% still using Week 2) - Illustrative pause/revise prompts (not thresholds): - MVP still buggy/unusable → Extend build 1-2 weeks - <3 beta customers using → Product doesn't solve problem - Negative feedback (no one would recommend) → Major iteration needed Contingency: If No-Go: 1. Extend beta 2 weeks: Fix major issues before launch 2. Pivot product: If beta feedback shows you built wrong thing 3. Pivot to concierge MVP: If product too complex, do manual delivery first ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-phase-4-launch-initial-traction-weeks-9-10", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 4: Launch & Initial Traction (Weeks 9-10)", "headingId": "chapter-13-startup-foundations-phase-4-launch-initial-traction-weeks-9-10", "url": "#chapter-13-startup-foundations-phase-4-launch-initial-traction-weeks-9-10", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Launch publicly and acquire first 30-50 customers." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-week-9-soft-launch", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 9: Soft Launch", "headingId": "chapter-13-startup-foundations-week-9-soft-launch", "url": "#chapter-13-startup-foundations-week-9-soft-launch", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Day 1-2: Pre-Launch Preparation (16 hours) - Activities: - Finalize pricing page (clear tiers, features, CTA) - Set up payment processing (Stripe integration) - Create launch materials: - Landing page (value prop, screenshots, pricing) - Email sequence (welcome, onboarding, usage tips) - Social posts (launch announcement) - Prepare launch list (100-200 people: interviewed customers, beta users, personal network) - Output: Launch-ready product + marketing materials Day 3-4: Soft Launch (16 hours) - Activities: - Release to launch list (email 100-200 people) - Monitor metrics daily: - Signups: How many people try product? - Activation: % who complete key action in first session - Engagement: % who return Day 2, Day 7 - Respond to all customer inquiries <2 hours (build relationships) - Launch announcement template: - Output: 20-50 signups from soft launch - Red flag: <10 signups from 100-person launch list → Message not resonating Day 5: Launch Metrics Baseline (8 hours) - Activities: - Establish Week 9 metrics baseline: - Signups: [X people] - Activation: [Y% completed key action] - Weekly active: [Z% still using by Friday] - Paying: [P% converted to paid] - Identify drop-off points (where do users abandon?) - Set Week 10 targets (10-20 percent improvement) - Output: Metrics dashboard with baseline" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-week-10-traction-iteration", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 10: Traction & Iteration", "headingId": "chapter-13-startup-foundations-week-10-traction-iteration", "url": "#chapter-13-startup-foundations-week-10-traction-iteration", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Day 1-3: Customer Acquisition (24 hours) - Activities: - Expand outreach beyond launch list: - Post on relevant communities (Reddit, HackerNews, LinkedIn) - Outbound to target ICP (personalized emails to 50 companies) - Ask beta customers for referrals - Target: 20-30 additional signups in Week 10 - Track which channel works best (most signups) - Output: 50-100 total signups by end of Week 10 Day 4-5: Iteration Based on Usage (16 hours) - Activities: - Analyze drop-off points (where do users stop using product?) - Interview 5 churned users (why did they stop?) - Make small improvements to onboarding/activation - Test: Does change improve activation rate? - Output: Product iterations based on user data Decision Gate #4: End of Week 10 - Illustrative evidence prompts (not thresholds): - ≥30 total users signed up - above 10 percent activated (completed key action) - above 30 percent weekly retention (still using after 7 days) - ≥3 paying customers or strong intent to pay - Illustrative pause/revise prompts (not thresholds): - <20 signups → Not enough demand - below 5 percent activation → Product too complex or value unclear - below 20 percent retention → Product doesn't solve problem Contingency: If No-Go: 1. Extend traction phase 2 weeks: Give more time to find PMF 2. Pivot positioning: Same product, different customer segment 3. Major product iteration: If retention terrible, rebuild core workflow ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-phase-5-early-traction-planning-weeks-11-12", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 5: Early Traction & Planning (Weeks 11-12)", "headingId": "chapter-13-startup-foundations-phase-5-early-traction-planning-weeks-11-12", "url": "#chapter-13-startup-foundations-phase-5-early-traction-planning-weeks-11-12", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Validate unit economics and plan for scaling." }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-week-11-customer-validation-metrics", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 11: Customer Validation & Metrics", "headingId": "chapter-13-startup-foundations-week-11-customer-validation-metrics", "url": "#chapter-13-startup-foundations-week-11-customer-validation-metrics", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Day 1-2: Customer Success Interviews (16 hours) - Activities: - Interview 10 active users ( 2 sessions in product) - Ask an open question about what would make the product essential; do not attribute the wording to a named company without a source. - Measure: \"How disappointed if product went away?\" (Very/Somewhat/Not) - Identify patterns: What do power users have in common? - PMF Assessment: - above 40 percent \"very disappointed\" = Product-market fit ✓ - 30-40 percent = Promising but need iteration - below 30 percent = Weak PMF, major changes needed - Output: PMF score, qualitative feedback Day 3-5: Unit Economics Validation (24 hours) - Activities: - Calculate actual CAC: - Total spend (ads, time, tools) / customers acquired - Example: $2,000 spend / 50 customers = $40 CAC - Estimate LTV based on early retention: - Pricing × estimated lifetime (use 6-month retention as proxy) - Example: $99/month × 12 months (assumed) = $1,188 LTV - Validate LTV:CAC ratio: - $1,188 / $40 = 29.7:1; treat the result as an input to sensitivity analysis, not a universal health label. - OR: $1,188 / $200 (if CAC is higher) = 5.9:1; test retention, contribution margin, cash timing, and measurement uncertainty before interpreting it. - Output: Validated unit economics model - Red flag: LTV:CAC <2:1 → Economics don't work, need to fix pricing or reduce CAC" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-week-12-growth-planning", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 12: Growth Planning", "headingId": "chapter-13-startup-foundations-week-12-growth-planning", "url": "#chapter-13-startup-foundations-week-12-growth-planning", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Day 1-2: Channel Analysis (16 hours) - Activities: - Review which acquisition channels worked: - Direct outreach: X signups, $Y CAC - Community posting: X signups, $Y CAC - Referrals: X signups, $0 CAC - Identify top 2 channels (best CAC + conversion) - Plan to double down: How to 2-3× these channels in next 12 weeks? - Output: Channel strategy for Q2 Day 3-4: Q2 Roadmap (16 hours) - Activities: - Product roadmap: Top 3 features to build based on customer feedback - Growth roadmap: Customer acquisition targets (X new customers/month) - Team roadmap: Do you need to hire? (First sales hire? First eng hire?) - Fundraising decision: Bootstrap vs. raise seed round? - Output: 90-day roadmap (Weeks 13-24) Day 5: Retrospective & Decision (8 hours) - Activities: - Review 12-week journey: What worked? What didn't? - Celebrate wins (you validated and launched!) - Make decision: Scale (double down), Iterate (improve PMF), or Pivot (change direction) - Output: Final decision on next phase Decision Gate #5: End of Week 12 - Illustrative scale-decision prompts (not thresholds): - PMF score above 40 percent - 30+ customers, growing 20 percent or more weekly - LTV:CAC 3:1 - Clear channel to acquire more customers - Action: Raise seed round OR aggressively bootstrap growth - Illustrative iteration prompts (not thresholds): - PMF score 25-40 percent - 15-30 customers, some growth - LTV:CAC 2-3:1 - Action: 12 more weeks improving product + retention - Pivot criteria (change course): - PMF score below 25 percent - <15 customers OR declining retention - LTV:CAC <1.5:1 - Action: Use learnings to pivot to adjacent problem/customer ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-red-flags-by-week-warning-signals", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flags by Week (Warning Signals)", "headingId": "chapter-13-startup-foundations-red-flags-by-week-warning-signals", "url": "#chapter-13-startup-foundations-red-flags-by-week-warning-signals", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 1-2 (Problem Validation): - [ ] below 60 percent problem validation → Wrong ICP, try different customer segment - [ ] below 20 percent willingness to pay → Problem not painful enough - [ ] Can't schedule 15+ interviews → ICP too narrow or poor outreach Week 3-4 (Solution Validation): - [ ] below 50 percent like solution concept → Feature clarity issue or wrong solution approach - [ ] Can't define MVP in 6 weeks → Not minimum, descope immediately Week 5-8 (MVP Build): - [ ] Week 5: Feature #1 not functional → Underestimated complexity, extend timeline - [ ] Week 7: MVP development above 50 percent over estimate → Scope creep or technical debt - [ ] Week 8: <5 beta customers using product → Product doesn't solve problem Week 9-10 (Launch & Traction): - [ ] Week 9: <10 signups from 100-person list → Message not resonating - [ ] Week 10: below 10 percent activation rate → Onboarding broken or value unclear - [ ] Week 10: below 5 percent paying sign-ups → Price too high or value too low Week 11-12 (Validation & Planning): - [ ] Week 11: PMF score below 30 percent → Weak product-market fit - [ ] Week 12: LTV:CAC <2:1 → Unit economics broken - [ ] Week 12: Retention below 30 percent at 4 weeks → Product not sticky ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-resource-requirements-detailed", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Resource Requirements (Detailed)", "headingId": "chapter-13-startup-foundations-resource-requirements-detailed", "url": "#chapter-13-startup-foundations-resource-requirements-detailed", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Human Resources: - Founder/CEO: 50-60 hours/week (all 12 weeks) - Weeks 1-4: Customer interviews, solution design - Weeks 5-8: Project management, customer advisors - Weeks 9-12: Customer acquisition, fundraising prep - Technical co-founder or developer: 40-50 hours/week (Weeks 5-10) - Weeks 5-8: MVP development - Weeks 9-10: Bug fixes, iterations - Customer development: 15-20 hours/week (all 12 weeks) - Ongoing customer conversations - Beta user support - Feedback synthesis Financial Resources: The following amounts form a constructed planning worksheet, not current market benchmarks. Replace them with dated quotes, fully loaded internal costs, local legal and tax requirements, founder-specific cash needs, and a justified contingency. - Pre-revenue budget (Weeks 1-8): - Founder salaries: $0-$8,000/month ($0-$16K total for 2 founders) - Tools/software: $500/month ($1,000 total) - Customer research incentives: $1,000 (coffee, gift cards for interviews) - Legal (incorporation, founder agreement): $2,500 one-time - MVP development: $0-$10,000 (if outsourced; $0 if technical co-founder) - Subtotal: $4,500-$30,500 - Early revenue budget (Weeks 9-12): - Founders: $0-$8,000/month ($0-$8K for 1 month) - Tools: $1,000/month - Ads/marketing: $1,000-$5,000 (initial customer acquisition) - Subtotal: $2,000-$14,000 - Total 12-week budget: $6,500-$44,500 (the $20K-$30K midpoint is a constructed scenario, not a market norm) Budget Sources: - Bootstrapped (founder savings) - Friends & family ($25-50K) - Pre-seed investment ($100-500K if raising) ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-decision-gates-detailed", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Decision Gates (Detailed)", "headingId": "chapter-13-startup-foundations-decision-gates-detailed", "url": "#chapter-13-startup-foundations-decision-gates-detailed", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Gate #1 (Week 2): Proceed with Problem? - Criteria: above 60 percent problem validation + above 40 percent willingness to pay - Options: - YES → Proceed to solution validation - NO (wrong ICP) → Pivot to different customer segment, restart Week 1 - NO (wrong problem) → Pivot to different problem, restart Week 1 - NO (no evidence) → Shut down, save 10 weeks Gate #2 (Week 4): Proceed to MVP Build? - Criteria: above 50 percent solution fit + LTV:CAC 2:1 + MVP ≤6 weeks - Options: - YES → Proceed to build - NO (solution) → Iterate solution concept, restart Week 3 - NO (economics) → Fix pricing or CAC estimate - NO (scope) → Descope MVP, restart Week 3 Gate #3 (Week 8): Proceed to Launch? - Criteria: MVP functional + ≥5 beta users active + positive feedback - Options: - YES → Launch in Week 9 - NO (bugs) → Extend build 1-2 weeks - NO (usage) → Major product iteration needed - NO (feedback) → Pivot to concierge MVP or rebuild Gate #4 (Week 10): Product-Market Fit Emerging? - Criteria: ≥30 users + above 10 percent activation + above 30 percent retention + ≥3 paying - Options: - YES → Continue to Week 11-12 - NO (demand) → Extend 2 weeks OR pivot positioning - NO (activation) → Fix onboarding - NO (retention) → Major product changes needed Gate #5 (Week 12): Scale, Iterate, or Pivot? - Criteria: PMF score + customer count + unit economics - Options: - SCALE (PMF above 40 percent, LTV:CAC 3:1) → Raise seed OR aggressive bootstrap - ITERATE (PMF 25-40 percent, LTV:CAC 2-3:1) → 12 more weeks improving product - PIVOT (PMF below 25 percent, LTV:CAC <1.5:1) → Use learnings to pivot ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-contingency-triggers", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Contingency Triggers", "headingId": "chapter-13-startup-foundations-contingency-triggers", "url": "#chapter-13-startup-foundations-contingency-triggers", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Trigger 1: If 8 weeks (by Week 7) - Action: Reduce scope (cut 50 percent of features) OR extend timeline 2 weeks - Rationale: Scope was too large; need to simplify Trigger 3: If customer acquisition cost 3× LTV (by Week 11) - Action: Product-market fit not proven; either fix retention (increase LTV) OR reduce CAC (cheaper channels) - Rationale: Unit economics unsustainable; can't scale Trigger 4: If co-founder conflict emerges - Action: Founders' agreement mediation OR one founder exits - Rationale: Unresolved founder conflict can kill the company; address immediately Trigger 5: If runway <3 months remaining - Action: Emergency fundraise OR pivot to revenue-generating model OR shut down gracefully - Rationale: Running out of money; need decision in next 30 days ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-timeline-variance-adapt-to-your-situation", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Timeline Variance (Adapt to Your Situation)", "headingId": "chapter-13-startup-foundations-timeline-variance-adapt-to-your-situation", "url": "#chapter-13-startup-foundations-timeline-variance-adapt-to-your-situation", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Rapid Mode (6-8 weeks): - When to use: You have strong conviction + technical capability + prior validation - Changes: - Weeks 1-2 → 1 week (10 interviews, not 20) - Weeks 5-8 → 2 weeks (build faster, less beta testing) - Weeks 9-12 → 2 weeks (faster launch, less planning) - Risk: Less validation = higher failure risk - Best for: Second-time founders, iterating on existing product Standard Mode (12 weeks): - When to use: First-time founder, unvalidated idea, need thorough validation - Changes: Follow plan as written above - Best for: Most startup founders Thorough Mode (16-20 weeks): - When to use: Complex product, regulated industry, need extensive validation - Changes: - Weeks 1-2 → 4 weeks (50+ interviews, multiple customer segments) - Weeks 5-8 → 6 weeks (extended beta with 50+ users) - Weeks 9-12 → 6 weeks (pilot with 10-20 paying customers before full launch) - Best for: Enterprise SaaS, healthcare, fintech (complex sales, regulatory requirements) ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-measurement-dashboard-track-weekly", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Measurement Dashboard (Track Weekly)", "headingId": "chapter-13-startup-foundations-measurement-dashboard-track-weekly", "url": "#chapter-13-startup-foundations-measurement-dashboard-track-weekly", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 13.7 — Constructed 12-week operating-manual tracker. The rows and values are fictional placeholders; replace them with venture-specific measures, owners, observation windows, and decision rules. | Week | Phase | Hypothesis Tested | Validated? | Customer Convos | Signups | Paying | Key Learning | |------|-------|-------------------|------------|----------------|---------|--------|--------------| | 1-2 | Problem validation | [Problem hypothesis] | Y/N | 20 | 0 | 0 | [Insight from interviews] | | 3-4 | Solution validation | [Solution hypothesis] | Y/N | 10 | 0 | 0 | [Insight on solution fit] | | 5-6 | MVP build sprint 1 | [Can we build it?] | Y/N | 5 | 0 | 0 | [Tech learning] | | 7-8 | Beta testing | [Will they use it?] | Y/N | 10 | 10 | 0 | [Usage insight] | | 9-10 | Launch | [Will they sign up?] | Y/N | 20 | 50 | 3 | [Acquisition channel insight] | | 11-12| Validation | [Will they stay & pay?] | Y/N | 10 | 30 | 10 | [PMF insight] | Milestone Metrics (End of Week 12): Product-Market Fit Indicators: - [ ] PMF Score above 40 percent (\"very disappointed\" if product went away) - [ ] NPS 50 - [ ] Week 4 retention above 50 percent (of Week 8 cohort) - [ ] Daily Active / Monthly Active above 20 percent Commercial Validation: - [ ] 30+ paying customers (or strong intent to pay) - [ ] Reconciled recurring revenue, retention, and payment evidence if pricing is finalized - [ ] LTV:CAC 2:1 (target 3:1 for scaling) - [ ] CAC payback <12 months Process Validation: - [ ] Repeatable acquisition process (can describe in playbook how you got customers) - [ ] 2+ acquisition channels tested - [ ] ICP clearly defined (can describe ideal customer in 3 sentences) - [ ] Validated pricing model (customers willing to pay the price you set) Team & Operations: - [ ] Founder-governance questions are documented and reviewed by the appropriate entity, tax, securities, employment, IP, and board owners. - [ ] 12+ months runway remaining (or clear path to profitability/fundraising) - [ ] Weekly metrics dashboard in place - [ ] Product roadmap for next 90 days Readiness Assessment: ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-success-stories-reference-points", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Success Stories & Reference Points", "headingId": "chapter-13-startup-foundations-success-stories-reference-points", "url": "#chapter-13-startup-foundations-success-stories-reference-points", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "What \"Good\" Looks Like at Week 12: - Customers: 30-50 signups, 10-20 active users, 3-10 paying - Revenue: $1K-5K MRR (if pricing is $100-500/month) - Retention: meaningful share still using after 4 weeks - PMF Score: meaningful share would be \"very disappointed\" - Unit Economics: LTV:CAC 3-5:1 What \"Struggling\" Looks Like at Week 12: - Customers: <20 signups, <5 active users, 0-1 paying - Revenue: <$500 MRR - Retention: weak retained usage after 4 weeks - PMF Score: few users would be \"very disappointed\" - Unit Economics: LTV:CAC <2:1 What to Do if Struggling: 1. Revisit the predeclared evidence, harm, and cash stop rules; elapsed weeks alone do not justify continuation. 2. Deep-dive on retention: Why are users leaving? 3. Interview churned users: What would make them come back? 4. Consider pivot: Same customer, different problem? Same problem, different customer? 5. Extend timeline: Give yourself 4-8 more weeks to improve metrics What to Do if Succeeding: 1. Lock in retention before scaling acquisition 2. Document your playbook (how did you get first 30 customers?) 3. Make fundraising decision: Bootstrap vs. raise seed 4. Compare staged growth options with capacity, quality, cash, legal, and customer guardrails. ---" }, { "id": "chapter-13-startup-foundations::chapter-13-startup-foundations-chapter-summary", "kind": "chapter", "itemSlug": "chapter-13-startup-foundations", "itemTitle": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Chapter Summary", "headingId": "chapter-13-startup-foundations-chapter-summary", "url": "#chapter-13-startup-foundations-chapter-summary", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Startup frameworks covered: 1. Lean Startup - Build-measure-learn cycle 2. Customer Development - Validate before scaling 3. MVP - Test with minimum investment 4. Product-Market Fit - Triangulate multiple segment-specific signals 5. Founder-governance issues - Prepare decisions for counsel and authorized founders/boards 6. Equity distribution - Model allocation, control, dilution, law, tax, and uncertainty 7. Burn Rate - Know your spending 8. Runway - Don't run out of cash 9. Pivot - When and how to change course 10. Scale Readiness - When to step on gas Key Principles: - Increase evidence before irreversible investment , while recognizing that no test fully validates a venture. - Combine customer accounts with observed behavior, economics, alternatives, and contrary evidence. - Measure only what serves a decision , with definitions, denominators, uncertainty, and guardrails. - Move at the fastest responsible learning rate allowed by safety, law, evidence, and reversibility. - Manage cash as scenarios and decision options , not a single runway threshold. Next Chapters: Go-to-Market Strategy, Fundraising & Finance --- Cross-references: See Chapter 5 for customer and CLV/CAC analysis, Chapter 14 for GTM, Chapter 15 for financing, and Chapter 21 for product decisions. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Go-to-Market Strategy", "headingId": "chapter-14-go-to-market-strategy", "url": "#chapter-14-go-to-market-strategy", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-executive-summary", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Executive Summary", "headingId": "chapter-14-go-to-market-strategy-executive-summary", "url": "#chapter-14-go-to-market-strategy-executive-summary", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Go-to-market (GTM) strategy coordinates a target customer and buying unit, problem and alternatives, differentiated proof, channel and sales capacity, pricing and value metric, unit economics, onboarding, retention, and learning. The chapter treats each field as a hypothesis—not a benchmark, causal result, or universal SaaS launch sequence. Key Frameworks: 1. GTM Strategy Canvas 2. Ideal Customer Profile (ICP) Framework 3. Sales Funnel Metrics Dashboard 4. Channel Strategy Matrix 5. Pricing Model Comparison 6. Product Launch Checklist 7. Growth Experimentation Framework 8. Product-mediated diffusion measure 9. Partnership Evaluation Matrix 10. Market Entry Strategy Decision Tree 11. International and Non-Market GTM Gate This chapter is educational, not advertising, competition, privacy, contract, tax, securities, or pricing advice. Public claims, targeting, referrals, incentives, testimonials, comparative statements, discounts, partner terms, and customer data require the applicable approvals and substantiation. Applied exercise — constructed GTM decision: For a B2B or B2C venture, choose a segment and buying unit, draft positioning, compare two channels, design a price test, calculate a cohort cash range, and recommend launch or pause. State the causal method, customer-harm guardrails, channel capacity, contract/privacy constraints, and three stop rules. Use Chapter 5 for segmentation and measurement, Chapter 13 for venture evidence, Chapter 21 for product decisions, and Chapter 22 for analysis. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview", "url": "#chapter-14-go-to-market-strategy-overview", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The GTM strategy canvas is an author-created hypothesis set connecting a target customer and buying unit to a problem, differentiated proof, channel, pricing/value metric, economics, capacity, onboarding, retention, and learning. Value-proposition/customer-profile concepts are bounded by the registered source; a completed canvas is not evidence of fit. [BB-C14-S01]" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply", "url": "#chapter-14-go-to-market-strategy-how-to-apply", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Fill each field with an assumption, evidence owner, uncertainty, and next test. Compare alternatives, customer harm, access, channel capacity, contract/privacy constraints, margin, cash timing, and service burden before treating the canvas as a launch recommendation. Constructed-example boundary: The customer descriptions, counts, prices, percentages, targets, and operating values in the examples below are invented teaching inputs. They are not benchmarks, forecasts, observed company results, or evidence of causality. Purpose: Reconcile a set of GTM hypotheses in one view. The canvas is an author synthesis; customer-profile/value-proposition concepts are supported by the registered source, but a completed canvas is not evidence of fit. [BB-C14-S01] Canvas Components:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-a-target-customer-who", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "A. Target Customer (WHO)", "headingId": "chapter-14-go-to-market-strategy-a-target-customer-who", "url": "#chapter-14-go-to-market-strategy-a-target-customer-who", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Definition: Who are you selling to? - Examples: - B2B: \"Mid-market SaaS companies ($5M-50M revenue)\" - B2C: \"Young professionals aged 25-35, city-based, $75K+ income\" - B2B2C: \"Retailers who sell to fashion-conscious women 18-35\" - Specificity: More specific = better (not \"any company\")" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-b-customer-problem-what", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "B. Customer Problem (WHAT)", "headingId": "chapter-14-go-to-market-strategy-b-customer-problem-what", "url": "#chapter-14-go-to-market-strategy-b-customer-problem-what", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Definition: What painful problem does your customer have? - Avoid vagueness: Not \"marketing is hard\" but \"marketing teams spend 20 percent time on manual data entry\" - Validation: Have you interviewed 20+ customers confirming this is a top-3 problem? - Urgency: Is this a \"nice to have\" or \"urgent problem threatening business\"?" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-c-unique-value-prop-why-us", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "C. Unique Value Prop (WHY US)", "headingId": "chapter-14-go-to-market-strategy-c-unique-value-prop-why-us", "url": "#chapter-14-go-to-market-strategy-c-unique-value-prop-why-us", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Definition: Why us vs. alternatives (competitor, DIY, do nothing)? - Format: \"[Quantified benefit] vs. [clear alternative]\" - Examples: - \"Reduce onboarding from 3 weeks to 3 days vs. legacy system approach\" - \"Save marketing teams 10 hours/week vs. manual data entry\" - \"Deploy AI model in 2 weeks vs. 6-month custom build\" - Test: Can customer understand it in 1 sentence?" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-d-go-to-market-channel-how", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "D. Go-to-Market Channel (HOW)", "headingId": "chapter-14-go-to-market-strategy-d-go-to-market-channel-how", "url": "#chapter-14-go-to-market-strategy-d-go-to-market-channel-how", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Definition: How will customers find you? - Options: - Direct sales: Test when explanation, procurement, implementation, or relationship needs may justify sales capacity. - Self-service: Test when users can understand, buy, onboard, and obtain value with limited assisted service. - Partnerships: Test when partner reach, capability, incentives, control, economics, and customer ownership align. - Digital marketing: Test when targeting, consent, claims, attribution, conversion, economics, and service capacity are acceptable. - Mixed: Define channel roles and conflict rather than assuming a combination is superior. This is an author-created design caution." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-e-pricing-model-how-much", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "E. Pricing Model (HOW MUCH)", "headingId": "chapter-14-go-to-market-strategy-e-pricing-model-how-much", "url": "#chapter-14-go-to-market-strategy-e-pricing-model-how-much", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Definition: How do you make money? - Common models: - Per user/month: A constructed SaaS model can charge by active seat; scalability depends on service, support, infrastructure, and acquisition economics. - Percentage of transaction: Marketplace fee; determine the basis and rate from value, cost, risk, competition, contract, and willingness-to-pay evidence. [BB-C14-S05] - Per feature: A constructed tiered model can separate basic, professional, and enterprise capabilities. - One-time license: A software vendor may quote a license for a defined scope, term, maintenance arrangement, and usage right. - Freemium: Free + premium (free-to-paid conversion)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-f-unit-economics-finances", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "F. Unit Economics (FINANCES)", "headingId": "chapter-14-go-to-market-strategy-f-unit-economics-finances", "url": "#chapter-14-go-to-market-strategy-f-unit-economics-finances", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Definition: The math at one customer level - Key metrics: - Customer Acquisition Cost (CAC): Define which sales and marketing cash, labor, incentives, and overhead are included and which acquired cohort is the denominator. - Lifetime value (LTV): Model expected gross-margin contribution or another explicit contribution measure by cohort, retention, expansion, service cost, and time—not revenue alone. - Payback period: Divide CAC by the relevant periodic contribution, not ARPU without margin and service-cost adjustments. - LTV:CAC ratio: State definitions, uncertainty, cash timing, and sensitivity; no universal ratio proves sustainability. - Example: - CAC: $500 (sales + marketing to get one customer) - ARPU: $100/month - Revenue proxy: $100/month × 24 months = $2,400; this is not LTV until margin, retention, service cost, and discounting assumptions are defined. - Revenue-proxy/CAC = 4.8:1; do not label it healthy without the missing assumptions." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-g-growth-assumption-trajectory", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "G. Growth Assumption (TRAJECTORY)", "headingId": "chapter-14-go-to-market-strategy-g-growth-assumption-trajectory", "url": "#chapter-14-go-to-market-strategy-g-growth-assumption-trajectory", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Definition: How will you scale? - Year 1 Targets: - Revenue: $1M - Customers: 100 - CAC efficiency: $5K per customer - Constraints: What's the limiting factor? (Sales team size, ad spend, product capacity) Template: Usage: - Draft by founders - Validate with 20+ customer conversations (iterate canvas 2-3 times) - Use to guide product decisions (features that support GTM strategy) - Update quarterly as you learn Figure 14.1. GTM evidence and readiness loop (constructed). Customer, product, economics, channel capacity, and launch readiness iterate together; an explicit decision gate can test, launch, pause, pivot, or stop. Text equivalent: Define the segment and buying unit, investigate the problem and alternatives, develop differentiated proof, compare channels and capacity, test pricing and cohort economics, and assess product/service readiness. At the gate, launch a bounded cohort only when evidence and controls are sufficient; otherwise run another test, revise the GTM design, pause, or stop. Onboarding, retention, churn, complaints, expansion, and closed-lost evidence feed the next decision." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use the canvas to expose dependencies between segment, proof, channel, price, delivery, and cash. - Treat every value, target, and customer description as a hypothesis until defined evidence supports the next decision. - Make launch, pause, pivot, stop, and responsible-close options visible before increasing exposure." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A canvas can create false coherence when the fields are guesses, the buying unit is wrong, or the customer evidence is selected for confirmation. - Firmographics, a value proposition, or a favorable ratio do not establish demand, willingness to pay, causal lift, or retention. - A launch decision also depends on product quality, privacy, accessibility, contracts, service capacity, legal review, and affected-party outcomes." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections", "url": "#chapter-14-go-to-market-strategy-connections", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Customer and segment: Use Framework 2 and Chapter 5 for jobs, segmentation, alternatives, and measurement. - Channels and pricing: Use Frameworks 4 and 5 for channel tests, value metrics, contracts, and unit economics. - Product and evidence: Use Chapters 13, 21, and 22 for venture tests, product readiness, cohorts, and analysis. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview-2", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview-2", "url": "#chapter-14-go-to-market-strategy-overview-2", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The ideal customer profile (ICP) is a constructed segmentation and buying-unit hypothesis that adds job, alternatives, access, urgency, economics, service fit, and decision rights to firmographic description. Jobs-to-be-Done can deepen the problem lens; Moore’s beachhead lens is a bounded practitioner aid, not a universal adoption sequence. [BB-C14-S03] [BB-C14-S02]" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply-2", "url": "#chapter-14-go-to-market-strategy-how-to-apply-2", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define inclusion, exclusion, evidence, disqualifiers, fairness/privacy constraints, and a local decision rule. Use the score to prioritize a test or allocate attention; do not use it to infer worth, authorize exclusion, or prove fit. Constructed-example boundary: The firms, budgets, scores, segment sizes, win rates, ratios, and other values below are invented teaching inputs. They are not market estimates, permission to exclude, or evidence of willingness to pay. Purpose: Define a testable segment and buying unit whose job, alternatives, access, economics, and service fit support focused learning. Jobs-to-be-Done can deepen the problem lens beyond firmographics. [BB-C14-S03] For some disruptive-technology contexts, Moore's early-market/mainstream and beachhead-market framing can prompt questions about reference customers and adoption barriers. It is a practitioner lens, not a universal adoption sequence. [BB-C14-S02] S03 is used only for the jobs-to-be-done/problem lens; the ICP dimensions, score, anti-priority rule, fairness checks, and prioritization decision are author-created and must be tested locally. ICP Dimensions:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-firmographic-company-characteristics", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Firmographic (Company Characteristics)", "headingId": "chapter-14-go-to-market-strategy-firmographic-company-characteristics", "url": "#chapter-14-go-to-market-strategy-firmographic-company-characteristics", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Industry: e.g., \"SaaS B2B\" (not insurance or nonprofits) - Company size: e.g., \"$5M-50M revenue\" or \"20-200 employees\" - Geography: e.g., \"US + Canada, tech hubs\" (not all geographies) - Growth stage: e.g., \"Series A-C funded\" (not pre-seed bootstraps) - Decision budget: e.g., \"Has a documented budget process\" (an access or buying-process signal to test, not evidence of willingness to pay)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-behavioral-how-they-operate", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Behavioral (How They Operate)", "headingId": "chapter-14-go-to-market-strategy-behavioral-how-they-operate", "url": "#chapter-14-go-to-market-strategy-behavioral-how-they-operate", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Technology stack: e.g., \"Uses Salesforce\" (integration point) - Process maturity: e.g., \"Has formalized marketing ops team\" (can execute) - Pain urgency: e.g., \"Recently had hiring surge creating data chaos\" (trigger) - Buying cycle: e.g., \"Contracts in Q1\" (budget planning cycle)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-psychographic-values-priorities", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Psychographic (Values/Priorities)", "headingId": "chapter-14-go-to-market-strategy-psychographic-values-priorities", "url": "#chapter-14-go-to-market-strategy-psychographic-values-priorities", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Growth mindset: e.g., \"Looking to optimize; willing to invest\" - Technology affinity: e.g., \"Early adopters of new tools\" - Decision style: e.g., \"Data-driven, requires clear ROI\" (vs. gut-feel driven) ICP Profile Template: Constructed scoring system: Define criteria, weights, evidence, disqualifiers, fairness/privacy constraints, and decision thresholds locally. A high score prioritizes a test; it does not prove fit or authorize exclusion. Anti-ICP (Who to Deprioritize): - \"We'll work with anyone\" can spread resources thin; define prioritization signals and review them for unfair effects. - Example anti-priority: An account whose documented product, service, payment, security, legal, or capacity requirements cannot be met under the approved offer; organization type or budget alone is not a disqualifier. - Possible outcome: Lower contribution, higher support cost, or poor retention under the defined model; measure rather than assume. Usage: - Sales team uses to qualify leads (ICP score) - Marketing uses to target ads, content - Product uses to prioritize feature requests (from ICP customers only) - Revise quarterly based on actual sales data Table 14.1: Constructed segment-prioritization illustration. The figures are invented teaching inputs, not market benchmarks, forecasts, or evidence of fit. | Segment | Size | Avg Deal | Win Rate | LTV:CAC | Priority | |---------|------|----------|----------|---------|----------| | ICP (perfect fit) | 500 companies | $50K | 25 percent | 5:1 | 1 (focus here) | | Good fit | 2000 companies | $30K | 15 percent | 3:1 | 2 | | Possible fit | 5000 companies | $20K | 5 percent | 1.5:1 | 3 (if inbound) |" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers-2", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers-2", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define who buys, who uses, who is affected, who can block, and what alternatives are available. - Treat segment size, win rate, deal size, and ratio values as locally measured or constructed, not market facts. - Reassess the ICP when evidence, access, economics, service burden, or harm patterns differ across cohorts." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques-2", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques-2", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Firmographics and an ICP score can hide jobs, power, accessibility, nonbuyers, affected people, and distributional harm. - A narrow segment may improve learning while reducing reachable market, resilience, or ethical fit; a broad segment may be necessary for a different model. - Segment evidence is vulnerable to selection, survivorship, response, attribution, and privacy errors." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections-2", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections-2", "url": "#chapter-14-go-to-market-strategy-connections-2", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Problem evidence: Use Chapter 13 and Framework 1 to connect venture hypotheses, jobs, alternatives, and proof. - Channel: Use Framework 4 to test whether the selected segment is reachable and serviceable. - Product and analytics: Use Chapter 21 for product discovery and Chapter 22 for cohort, uncertainty, and causal analysis. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview-3", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview-3", "url": "#chapter-14-go-to-market-strategy-overview-3", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The sales funnel metrics dashboard is an author-created measurement aid for defining stages, cohorts, owners, entry/exit rules, closed-lost reasons, onboarding, retention, expansion, churn, complaints, and harm. It is not a standard funnel, benchmark, or causal model. [BB-C14-S04]" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply-3", "url": "#chapter-14-go-to-market-strategy-how-to-apply-3", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the stage, unit, denominator, observation window, data quality, and decision use before comparing conversion. Separate attribution from incremental lift and include closed-lost and post-close outcomes in the learning loop. Purpose: This author-created dashboard illustrates how a team might define acquisition stages, cohort transitions, losses, onboarding, and post-close outcomes. It is not a standard funnel, benchmark, causal model, or prescribed stage taxonomy; use local definitions and validated data to investigate—not merely label—bottlenecks. Constructed funnel example: Figure 14.2. Acquisition, loss, and post-close learning loops (constructed). Every stage needs a definition, owner, entry/exit rule, cohort, and loss reason. Closed-won is the start of onboarding and retention evidence, while closed-lost evidence returns separately. Text equivalent: Prospects move from awareness to consideration, proposal, negotiation, and either closed-won or closed-lost. Closed-won proceeds through onboarding to retained use, expansion, churn, complaint, or other outcomes. Closed-lost and post-close evidence return to segment, message, price, channel, product, service, and capacity decisions for the next cohort. Key Metrics by Stage:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-awareness", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "AWARENESS", "headingId": "chapter-14-go-to-market-strategy-awareness", "url": "#chapter-14-go-to-market-strategy-awareness", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Metric: Lead volume - Target: 1000 qualified leads/month (depends on your target market size) - Drivers: - Paid ads: $10K/month budget → 500 leads - Content marketing: 10,000 monthly blog visitors → 300 leads - Partnerships: Referral program → 200 leads - Health: Increasing month-over-month" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-consideration", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "CONSIDERATION", "headingId": "chapter-14-go-to-market-strategy-consideration", "url": "#chapter-14-go-to-market-strategy-consideration", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Metric: Lead response rate, meeting booking rate - Target: 60 percent of leads book a call (60 percent conversion rate) - Drivers: - Email quality (personalized blast) - Response time (within 2 hours next day) - Value prop clarity (clear why they should talk) - Health: Declining conversion suggests bad leads or weak messaging" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-proposal", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "PROPOSAL", "headingId": "chapter-14-go-to-market-strategy-proposal", "url": "#chapter-14-go-to-market-strategy-proposal", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Metric: Proposal win rate - Target: 40-50 percent of meetings lead to proposal - Drivers: - Meeting quality (talked to actual decision maker?) - Problem confirmation (did they confirm the problem?) - Fit assessment (is your solution right for them?) - Health: Low conversion suggests selling too early" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-negotiation", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "NEGOTIATION", "headingId": "chapter-14-go-to-market-strategy-negotiation", "url": "#chapter-14-go-to-market-strategy-negotiation", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Metric: Discount rate, term length, close rate - Target: 50-60 percent of proposals close - Drivers: - Value understood (did you quantify ROI?) - Competition (did they consider alternatives?) - Urgency (do they have budget/decision timeline?) - Health: Low close rate suggests price too high or weak negotiation" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-post-close", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "POST-CLOSE", "headingId": "chapter-14-go-to-market-strategy-post-close", "url": "#chapter-14-go-to-market-strategy-post-close", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Metric: Onboarding success, support load, and a defined customer-experience measure; if NPS is used, collect the 0–10 recommendation item and calculate promoters minus detractors under the approved instrument - Target: 90 percent or more timely onboarding, below 2 percent churn - Drivers: - Expectation management (did you over-promise?) - Ramp time (how long to value?) - Support quality (responsive team?) Table 14.2: Constructed funnel dashboard for one sample month. Stage definitions, targets, actuals, and health labels require local cohort and data-quality rules. | Stage | Target | Actual | Conv Rate | Health | |-------|--------|--------|-----------|--------| | Awareness | 1000 | 950 | - | ✓ Good | | Consideration | 600 | 520 | 54 percent | ⚠ Slight dip | | Proposal | 240 | 180 | 35 percent | 🔴 Below target | | Negotiation | 120 | 90 | 50 percent | ✓ Good | | Closed Won | 72 | 54 | 60 percent | ⚠ Below target | Diagnosis: Proposal conversion low (35 percent vs 40 percent target). Action: Review 5 recent proposals (messaging? fit? timing?). Typical Funnel Economics: To close 100 customers/year: - Need 200 proposals (assuming 50 percent close rate) - Need 400 meetings (assuming 50 percent proposal rate) - Need 1000 qualified leads (assuming 40 percent meeting rate) Table 14.3: Constructed channel-funnel comparison. Conversion values are illustrative and are not channel benchmarks. | Channel | Awareness | Consideration | Proposal | Close | Efficiency | |---------|-----------|----------------|----------|-------|-----------| | Direct sales | High touch | 70 percent conv | 60 percent conv | 70 percent conv | High deal size, low volume | | Self-serve | High volume | 30 percent conv | 20 percent conv | 40 percent conv | High volume, small deals | | Partnerships | Medium | 80 percent conv | 50 percent conv | 60 percent conv | Medium, high trust |" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers-3", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers-3", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ask where evidence is lost, not merely where volume falls. - Pair acquisition metrics with onboarding, retention, support, complaints, refunds, accessibility, and customer outcomes. - Use randomized or justified quasi-experimental designs when a channel or intervention decision requires causal lift." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques-3", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques-3", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Funnels are definitions and measurement conventions; they do not prove causality, value, or customer satisfaction. - Stage conversion can be distorted by cohort mix, attribution, selection, seasonality, sales capacity, and inconsistent loss coding. - Optimizing top-of-funnel volume can increase spam, harm, service load, or low-quality demand." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections-3", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections-3", "url": "#chapter-14-go-to-market-strategy-connections-3", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Channel: Use Framework 4 to compare reach, control, capacity, incentives, and economics. - Pricing: Use Framework 5 to connect conversion and price tests to contribution and cash. - Analytics and product: Use Framework 7 and Chapters 21–22 for experiments, cohorts, causal methods, and product outcomes. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview-4", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview-4", "url": "#chapter-14-go-to-market-strategy-overview-4", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The channel strategy matrix is a constructed comparison of reach, control, explanation, access, capacity, partner incentives, service burden, risk, contribution, and cash. Bullseye supports brainstorming, ranking, small parallel tests, and focus based on evidence; the values below are not channel benchmarks. [BB-C14-S04]" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply-4", "url": "#chapter-14-go-to-market-strategy-how-to-apply-4", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Compare a small portfolio of channels using defined segment evidence, buying behavior, incremental lift, cost, capacity, customer experience, privacy, partner rights, and exit options. Choose, combine, defer, or stop channels according to the decision and downside rule. Purpose: Decide which sales/marketing channels to invest in. All volume, deal-size, cycle, margin, investment, CAC, LTV, and maturity values in this section are constructed hypotheses, not channel benchmarks. Weinberg describes Bullseye as brainstorming across acquisition channels, ranking candidates, running small parallel tests, and then focusing based on evidence; the specific outcomes below are not sourced. [BB-C14-S04] Table 14.4: Constructed channel-evaluation matrix. Volume, deal-size, cycle, margin, investment, and maturity values are hypotheses for teaching, not benchmarks. | Channel | Volume Potential | Deal Size | Sales Cycle | Margin | Investment | Notes | |---------|-----------------|-----------|-------------|--------|-----------|-------| | Direct Sales | Medium (1-2 deals/rep/month) | High ($50K+) | Long (3-6 mo) | High (70 percent or more) | High (salary, travel) | Best for enterprise | | Inside Sales | Medium-High (2-5 deals/month) | Medium ($10-50K) | Medium (1-3 mo) | High (60 percent or more) | Medium (salary) | Best for mid-market | | Self-Serve | High (unlimited) | Low ($0-1K) | Short (<1 week) | Low (30-40 percent) | Medium (product, ads) | Best for SMB | | Partnerships | Medium (depends on partner) | Variable | Variable | Medium (40-50 percent) | Low (commission only) | Best for reach | | Content Marketing | High (inbound) | Variable | Long (passive) | High (organic) | Medium (content team) | Best for brand building | | Paid Ads | High | Variable | Short (immediate) | Low (30 percent or more) | High (ad spend) | Best for quick scaling | Channel Selection Framework:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-step-1-current-evidence-and-constraints", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Step 1: Current evidence and constraints", "headingId": "chapter-14-go-to-market-strategy-step-1-current-evidence-and-constraints", "url": "#chapter-14-go-to-market-strategy-step-1-current-evidence-and-constraints", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Compare buying behavior, explanation and implementation burden, channel access, partner incentives, sales capacity, cash, service quality, privacy, attribution, and control. Stage labels do not determine the channel." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-step-2-economics-assessment", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Step 2: Economics Assessment", "headingId": "chapter-14-go-to-market-strategy-step-2-economics-assessment", "url": "#chapter-14-go-to-market-strategy-step-2-economics-assessment", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Calculate Unit Economics for Each Channel: Example - SaaS company, $300 ARPU, 2-year revenue scenario: Table 14.5: Constructed channel-economics hypothesis. The figures below illustrate a comparison method; they are not observed LTV, CAC, or channel performance. | Channel | CAC | LTV | LTV:CAC | Status | |---------|-----|-----|---------|--------| | Direct sales | $8K | $7.2K | 0.9:1 | Contribution does not recover acquisition cost under these assumptions | | Inside sales | $3K | $7.2K | 2.4:1 | Positive modeled spread; test retention, margin, and cash timing | | Self-serve | $500 | $7.2K | 14.4:1 | Large modeled spread; validate attribution and service costs | | Partnerships | $1K | $7.2K | 7.2:1 | Positive modeled spread; validate partner economics | Illustrative decision: Investigate self-service and partnerships further because the constructed model gives them more favorable contribution-to-acquisition scenarios. Validate demand, margin, support, retention, partner behavior, and capacity before scaling." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-step-3-learning-sequence", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Step 3: Learning sequence", "headingId": "chapter-14-go-to-market-strategy-step-3-learning-sequence", "url": "#chapter-14-go-to-market-strategy-step-3-learning-sequence", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Choose the smallest channel portfolio that can answer the decision without creating unmanaged conflict or service burden. Add, remove, or combine channels when incremental evidence and capacity justify it; no universal month sequence applies. Common Mistakes: - Spreading across 5 channels too early (excellence diluted) - Ignoring low-LTV:CAC channels (drains cash) - Not measuring channel quality (volume ≠ good customers)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers-4", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers-4", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Choose channels that the team can operate, measure, support, and govern for the selected customer and buying process. - Separate reach and attribution from incremental demand, contribution, retention, service load, and cash timing. - Make partner incentives, customer ownership, data rights, exclusivity, and exit terms explicit." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques-4", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques-4", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Channel performance depends on segment, product maturity, buying process, competition, capacity, and measurement quality. - A high modeled LTV:CAC or low CAC can reflect definitions, selection, delayed costs, or missing service and support burden. - Parallel tests can create channel conflict, brand inconsistency, customer confusion, or privacy and consent risk." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections-4", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections-4", "url": "#chapter-14-go-to-market-strategy-connections-4", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- ICP and funnel: Use Frameworks 2 and 3 to define who each channel reaches and how evidence is recorded. - Pricing and growth: Use Frameworks 5 and 7 to connect economics, experiments, incentives, and guardrails. - International entry: Use Framework 10 and Chapter 2 for regulatory, contract, partner, privacy, and non-market constraints. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview-5", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview-5", "url": "#chapter-14-go-to-market-strategy-overview-5", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The pricing model comparison is a constructed decision aid for testing value metrics, packages, willingness-to-pay evidence, economics, fairness, competition, tax, contract, procurement, and operating consequences. The cited source supports bounded value-based pricing concepts; sample prices, capture percentages, and evolution paths are constructed. [BB-C14-S05]" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply-5", "url": "#chapter-14-go-to-market-strategy-how-to-apply-5", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the customer value metric, cost-to-serve, contribution, alternatives, willingness-to-pay evidence, price sensitivity, contract, tax, fairness, and billing controls. Test a package or price with a defined cohort and stop rule rather than treating a model as inherently superior. Purpose: Compare value metric, package, willingness-to-pay evidence, economics, fairness, competition, tax, contract, procurement, and operating consequences. Value-based pricing is a supported concept; the sample prices, capture percentages, and evolution are constructed. [BB-C14-S05] The S05 record is used only for the bounded value-based-pricing and pricing-model concepts. Fairness, competition, tax, procurement, contract, billing, service, and operating checks are author-created prompts that require the applicable specialist review. Four Main Models:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-model-1-per-unit-pricing", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Model 1: Per-Unit Pricing", "headingId": "chapter-14-go-to-market-strategy-model-1-per-unit-pricing", "url": "#chapter-14-go-to-market-strategy-model-1-per-unit-pricing", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Mechanics: Fixed price per customer/seat/transaction - Example: $99/user/month for SaaS - Ideal for: Scalable products where value is per user - Pros: - Easy to understand (no complexity) - Scales with value (more users = more revenue) - Easy to forecast (predictable ARR) - Cons: - Leaves money on table (big companies get same price as small) - \"Sprawl\" (companies avoid adding users to save cost) - Optimization: Tiered pricing (Starter $99, Pro $299, Enterprise $999)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-model-2-value-based-pricing", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Model 2: Value-Based Pricing", "headingId": "chapter-14-go-to-market-strategy-model-2-value-based-pricing", "url": "#chapter-14-go-to-market-strategy-model-2-value-based-pricing", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Mechanics: Price based on ROI/value customer receives - Example: - If a use case is estimated to save $500K annually, test alternative packages and prices rather than applying a universal share-of-value percentage. - If a product may contribute to new revenue, separate attribution, risk, implementation effort, and customer alternatives before using the estimate in pricing. - Ideal for: Enterprise, quantifiable ROI - Potential advantages: - Can connect price to a value metric customers recognize - Can align incentives when measurement, attribution, risk, and contracts support the design - Cons: - Hard to quantify (negotiations required) - Requires trust (customer might low-ball) - Complex to administer - Usage: Enterprise sales; RFP responses include ROI calculator" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-model-3-freemium", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Model 3: Freemium", "headingId": "chapter-14-go-to-market-strategy-model-3-freemium", "url": "#chapter-14-go-to-market-strategy-model-3-freemium", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Mechanics: Free basic version; premium paid tier - Example: - Free: Up to 10K API calls/month - Pro: $99/month for unlimited - Ideal for: High-volume, low-touch, developer products - Pros: - Removes purchase friction (try before buy) - Network effects (more free users = more value) - Viral potential (easy to share) - Cons: - Free tier is expensive (server, support, churn) - Conversion can be low without a clear upgrade path - Cannibalization (some paying customers downgrade to free) - Success factors: - Free tier hits a real limitation (not just arbitrary) - Clear upgrade path (customer hits free limit and converts)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-model-4-usage-based-consumption-pricing", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Model 4: Usage-Based / Consumption Pricing", "headingId": "chapter-14-go-to-market-strategy-model-4-usage-based-consumption-pricing", "url": "#chapter-14-go-to-market-strategy-model-4-usage-based-consumption-pricing", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Mechanics: Pay for what you use (like utilities) - Example: - Computing capacity priced by measured use - Transaction service priced by a percentage and/or fixed fee - Ideal for: Infrastructure, platform products - Pros: - Aligns with customer value (use more = benefit more = pay more) - Low barrier to entry (start cheap, scale naturally) - Predictable revenue (scales with customer success) - Cons: - Revenue unpredictability (customer might not scale) - Billing complexity - Customer frustration (surprise bills if usage spikes) - Mitigation: Usage caps, annual commitments, committed tiers Table 14.6: Constructed pricing-model comparison. The dimensions are decision prompts, not universal model attributes. | Model | Predictability | Scalability | Customer Friction | Enterprise | SMB | |-------|---|---|---|---|---| | Per-Unit (seats) | High | High | Low | Medium | High ✓ | | Value-Based | Low | High | High | High ✓ | Low | | Freemium | Medium | High | Very Low | Low | High ✓ | | Usage-Based | Medium | High | Medium | Medium | Medium | | Hybrid | Medium | High | Medium | High ✓ | Medium | Hybrid Example (Common for SaaS): - Base: $99/month (per seat, includes 10K API calls) - Plus: $0.10 per API call above 10K - Result: Per-seat predictability + usage upside Pricing evolution: Revisit the value metric, package, fairness, economics, customer predictability, billing controls, and contract as evidence changes. A product need not progress from seat to tier to usage to value-based pricing on a fixed timeline." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers-5", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers-5", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Price the value metric the customer can understand and the firm can measure, deliver, support, and govern. - Separate revenue, contribution margin, cash payback, willingness to pay, and customer fairness. - Record who approved the price, what evidence supports it, what assumptions remain, and what would trigger revision." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques-5", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques-5", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Value-based pricing is not permission to claim or capture an arbitrary share of customer value. - A price test can be confounded by segment, packaging, sales effort, trust, timing, competition, procurement, and service capacity. - Freemium, usage, tier, and hybrid models can create privacy, fairness, billing, lock-in, and surprise-cost risks." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections-5", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections-5", "url": "#chapter-14-go-to-market-strategy-connections-5", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Customer: Use Framework 2 to define the buying unit, alternatives, and value evidence. - Funnel and channel: Use Frameworks 3 and 4 to link price to conversion, service, capacity, and contribution. - Finance and law: Use Chapters 4 and 15 plus qualified legal/tax owners for margin, contracts, tax, disclosure, and competition constraints. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview-6", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview-6", "url": "#chapter-14-go-to-market-strategy-overview-6", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The product launch checklist is a constructed coordination aid for a bounded market test or launch. It is not a universal four-week sequence; select activities from product risk, customer expectations, channel, evidence, capacity, privacy, advertising, accessibility, contract, and legal obligations." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply-6", "url": "#chapter-14-go-to-market-strategy-how-to-apply-6", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Assign owners, dependencies, evidence, approvals, rollback/exit conditions, support capacity, incident and complaint routes, and launch/hold decisions. Do not publish claims, testimonials, outcomes, or targeting without substantiation, consent, disclosure, and required review. Purpose: Coordinate the activities required for a bounded market test or launch. This checklist is a constructed planning aid, not a universal four-week sequence. Select only the activities warranted by the product, customers, channel, evidence, capacity, and legal obligations. 4 Weeks Pre-Launch:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-marketing-communications-week-4-to-1", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Marketing & Communications (Week -4 to -1)", "headingId": "chapter-14-go-to-market-strategy-marketing-communications-week-4-to-1", "url": "#chapter-14-go-to-market-strategy-marketing-communications-week-4-to-1", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Define launch messaging (1 sentence value prop) - [ ] Create launch landing page (value prop, screenshots, pricing, CTA) - [ ] Write press release (for media outreach) - [ ] Identify relevant journalists, analysts, communities, or other channels, if earned media is appropriate - [ ] Prepare \"about the startup\" FAQ - [ ] Schedule launch day social posts (pre-written) - [ ] Obtain substantiated testimonials or case examples only with documented permission, disclosure, and review - [ ] Brief early customers or beta users without conditioning access, support, or benefits on public endorsement - [ ] Create email launch sequence (pre-launch, launch day, post-launch)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-sales-partnership-week-4-to-1", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Sales & Partnership (Week -4 to -1)", "headingId": "chapter-14-go-to-market-strategy-sales-partnership-week-4-to-1", "url": "#chapter-14-go-to-market-strategy-sales-partnership-week-4-to-1", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Define the ICP and a feasible, consent- and capacity-aware target-account list - [ ] Prepare sales pitch deck (5 slides) - [ ] Create email outreach template (personalized intro) - [ ] Plan partnership announcements (if relevant) - [ ] Identify strategic advisors to amplify launch" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-product-operations-week-4-to-2", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Product & Operations (Week -4 to -2)", "headingId": "chapter-14-go-to-market-strategy-product-operations-week-4-to-2", "url": "#chapter-14-go-to-market-strategy-product-operations-week-4-to-2", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Approve pricing, terms, tax treatment, and any test design; do not expose similarly situated customers to hidden or unfair treatment - [ ] Complete payment setup (Stripe, etc.) - [ ] Prepare product documentation (1-page how-to guide) - [ ] Create a customer onboarding flow appropriate to the product's complexity and risk - [ ] Set up analytics (track signups, feature usage, churn) - [ ] Prepare support, escalation, incident, refund, and complaint-handling infrastructure - [ ] QA testing (try every feature as new customer) - [ ] Scale/load testing (can servers handle launch traffic?)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-launch-day-day-0", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Launch Day (Day 0)", "headingId": "chapter-14-go-to-market-strategy-launch-day-day-0", "url": "#chapter-14-go-to-market-strategy-launch-day-day-0", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Monitor product stability (check error rates, performance) - [ ] Respond to customer inquiries within the published, staffed service commitment - [ ] Publish only approved, substantiated launch communications through relevant channels - [ ] Send launch email to waitlist - [ ] Brief team on key messages (everyone on same page) - [ ] Record decisions, incidents, customer harm, and evidence gaps for the next gate" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-post-launch-days-1-7", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Post-Launch (Days 1-7)", "headingId": "chapter-14-go-to-market-strategy-post-launch-days-1-7", "url": "#chapter-14-go-to-market-strategy-post-launch-days-1-7", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Collect early customer feedback (what's working? what's not?) - [ ] Fix any critical bugs immediately - [ ] Follow up with interested leads (convert warm interest) - [ ] Publish metrics or customer outcomes only when definitions, substantiation, confidentiality, consent, and legal review permit it - [ ] Iterate based on feedback (quick feature improvements) - [ ] Plan Week 2 content/outreach (maintain momentum) Launch evidence: - Qualified reach and acquisition by consent status, segment, channel, and incremental lift where measurable - Stage conversion using stable definitions and cohorts, with closed-lost reasons - Onboarding completion, time to value, support load, reliability, complaints, refunds, accessibility, and customer-harm indicators - Retention, expansion, churn, contribution, cash timing, and capacity relative to the scenario approved at the launch gate - Communications performance, including negative feedback and misleading-claim or disclosure risks; raw impressions and press mentions are not proof of value Post-Launch Momentum (Week 2-4): - Weekly blog posts (SEO, thought leadership) - Product updates (show responsiveness to feedback) - Customer testimonials (social proof) - Expand outreach (move from launch network to cold outreach)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers-6", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers-6", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Assign one owner to each launch dependency, evidence item, approval, support route, and rollback or exit condition. - Treat launch as a bounded decision with a defined cohort, customer-outcome measures, capacity limit, and stop rule. - Review acquisition, reliability, support, complaints, refunds, accessibility, retention, contribution, and cash together." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques-6", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques-6", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A checklist can create false assurance when evidence, ownership, approval quality, or service capacity is weak. - A launch calendar does not establish demand, causal lift, product quality, legal compliance, or customer benefit. - Fixed four-week timing and generic metrics can be unsuitable for high-risk, regulated, complex, or low-volume offers." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections-6", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections-6", "url": "#chapter-14-go-to-market-strategy-connections-6", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Readiness: Use Frameworks 1–5 to connect the launch decision to segment, funnel, channel, pricing, and economics hypotheses. - Experimentation: Use Frameworks 7 and 8 to design safe tests and distinguish attribution from incremental acquisition. - Product and governance: Use Chapters 13, 21, and 22 plus qualified legal, privacy, security, tax, and accessibility owners for evidence and approvals. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview-7", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview-7", "url": "#chapter-14-go-to-market-strategy-overview-7", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The growth experimentation framework is an author-created sequence for testing whether an acquisition mechanism produces incremental, economically acceptable, and customer-safe growth. Bullseye supports channel brainstorming, ranking, small tests, and evidence-based focus; the broader experiment contract is author synthesis. [BB-C14-S04]" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply-7", "url": "#chapter-14-go-to-market-strategy-how-to-apply-7", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the mechanism, eligible population, unit, time window, counterfactual, primary outcome, guardrails, cost basis, data rights, and stop rule before exposure. Record attribution separately from incremental lift and review retention, service load, complaints, accessibility, privacy, and harm. Purpose: Test whether a channel, product mechanism, or referral process produces incremental, economically and ethically acceptable growth. Bullseye directly supports structured acquisition-channel testing; the broader experiment checklist here is author-created. [BB-C14-S04] Fast experimentation does not waive consent, consumer-protection, competition, accessibility, platform, security, or data-governance obligations. 5-Step Framework:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-step-1-identify-growth-levers", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Step 1: Identify Growth Levers", "headingId": "chapter-14-go-to-market-strategy-step-1-identify-growth-levers", "url": "#chapter-14-go-to-market-strategy-step-1-identify-growth-levers", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Definition: What action by customer leads to more customers? - Examples: - Referral: Existing customer refers friend → new customer - Referral: a retained customer voluntarily recommends the product to another eligible prospect - Product-mediated diffusion: collaboration or sharing exposes an invited non-user to the product - Network effect: utility changes with participation, subject to congestion, governance, and multi-homing - Content: useful, substantiated material attracts qualified demand - Product-led: a product experience creates evidence for a later purchase decision" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-step-2-quantify-the-lever", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Step 2: Quantify the Lever", "headingId": "chapter-14-go-to-market-strategy-step-2-quantify-the-lever", "url": "#chapter-14-go-to-market-strategy-step-2-quantify-the-lever", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Descriptive growth coefficient: Conversions attributed to the mechanism during a defined window ÷ eligible or exposed population during that same window. Report the cohort, unit, generation, time basis, overlap, retention, cost, uncertainty, and attribution limits. - Example - Referral: - 100 current customers - Each refers 0.2 new customers on average - Referral contribution proxy = 0.2 new sign-ups per current customer for the measured window; this is not a monthly growth rate unless the cohort, time basis, retention, overlap, and denominator support that interpretation." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-step-3-optimize-the-top-lever", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Step 3: Optimize the Top Lever", "headingId": "chapter-14-go-to-market-strategy-step-3-optimize-the-top-lever", "url": "#chapter-14-go-to-market-strategy-step-3-optimize-the-top-lever", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Identify: Which lever has highest potential impact? - Optimize: A/B test to increase conversion - Example - Referral Optimization: - Control: \"Refer a friend, get 1 month free\" - Test A: \"Refer a friend, get 1 month free (AND they get 1 month free)\" - Test B: \"Refer 3 friends, get lifetime discount\" - Measure: Which increases referral rate most?" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-step-4-automate-the-lever", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Step 4: Automate the Lever", "headingId": "chapter-14-go-to-market-strategy-step-4-automate-the-lever", "url": "#chapter-14-go-to-market-strategy-step-4-automate-the-lever", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Definition: Make it happen without manual effort - Example - Referral Automation: - Trigger: Customer reaches a predefined retained-activation condition appropriate to the product - Action: Auto-send referral incentive email - Tool: Built into product (share button, dashboard link)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-step-5-invest-in-winning-levers", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Step 5: Invest in Winning Levers", "headingId": "chapter-14-go-to-market-strategy-step-5-invest-in-winning-levers", "url": "#chapter-14-go-to-market-strategy-step-5-invest-in-winning-levers", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Scale: Increase exposure only after incremental lift, retention, contribution, customer outcomes, and capacity are credible - Budget: Allocate sales/marketing dollars to top levers - Example: If referral drives 20 percent growth, incentivize it; if content drives 10 percent, invest less Diffusion measure: See the next section. A product-generated invitation is not automatically causal acquisition, a network effect, or valuable retention. Experiment discipline: - State the mechanism, eligible population, unit of analysis, window, counterfactual, cost, and guardrails before launch. - Separate attribution from incremental lift and test for novelty, cannibalization, selection, spillover, and survivor bias. - Prohibit deceptive interfaces, forced invitations, contact scraping, undisclosed incentives, unauthorized testimonials, discriminatory targeting, and retaliation against non-participants. - Monitor complaint, unsubscribe, deletion, refund, security, accessibility, service-load, and vulnerable-customer indicators alongside acquisition. - Scale, revise, pause, or stop from predeclared evidence and harm rules; do not optimize only a top-of-funnel metric." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers-7", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers-7", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Require a decision-specific experiment contract before scaling exposure, budget, incentives, or automated outreach. - Compare incremental acquisition, retained value, contribution, service load, and customer-harm indicators rather than a single growth metric. - Make pause, stop, remedy, and responsible-close paths operational before the test begins." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques-7", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques-7", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Observational attribution, short windows, selection, spillover, novelty, and survivor bias can overstate a mechanism's effect. - A statistically detectable lift may still be uneconomic, operationally infeasible, unfair, or harmful to customers or nonparticipants. - A result from one segment, product, channel, or platform does not automatically transfer to another context." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections-7", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections-7", "url": "#chapter-14-go-to-market-strategy-connections-7", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Funnel and channel: Use Frameworks 3 and 4 to define stages, reach, capacity, cost, and attribution boundaries. - Diffusion: Use Framework 8 for invitation-cycle measurement and its limits; do not treat K as a viability threshold. - Analytics and product: Use Chapters 21 and 22 for experiment design, cohorts, causal inference, privacy, and guardrail analysis. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview-8", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview-8", "url": "#chapter-14-go-to-market-strategy-overview-8", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The product-mediated diffusion measure summarizes invitations and observed conversion for a defined cohort and generation. It is a descriptive local metric, not proof of causality, retention, network effects, profitability, or self-sustaining growth. [BB-C14-S06]" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply-8", "url": "#chapter-14-go-to-market-strategy-how-to-apply-8", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the included user, invitation, conversion, generation, eligibility, observation window, overlap, retention, cost, and data-quality rules. Report the measure with confidence intervals or uncertainty ranges where appropriate, and use an experiment or credible quasi-experimental design when a causal decision warrants it. Purpose: Summarize invitations and observed conversion for a defined cohort and generation. This is a local descriptive measure, not proof of causality, retention, network effects, profitability, or self-sustaining growth. Empirical work shows that diffusion is heterogeneous and sensitive to network structure and adoption dynamics. [BB-C14-S06] The Formula: Example Calculation: - Average user sends 5 invites - 20 percent of invites convert (1 in 5 friends actually signs up) - K = 5 × 0.20 = 1.0 Interpretation: Within one consistently defined and observed generation, K 1 means more than one converted invite per included user on average. It does not establish exponential or self-sustaining growth. The next generation can differ because of retention, cycle time, saturation, invitation overlap, incentives, fraud, channel quality, eligibility, service capacity, or changed product behavior. K = 1 is not financial break-even, and K < 1 does not imply that the business is shrinking. Improving Viral Coefficient:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-increase-invites-sent", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Increase Invites Sent", "headingId": "chapter-14-go-to-market-strategy-increase-invites-sent", "url": "#chapter-14-go-to-market-strategy-increase-invites-sent", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Method 1: Make sharing easy (prominent share button) - Method 2: Test a disclosed, consent-based incentive only after legal, fraud, fairness, and economic review - Method 3: Make sharing natural (product naturally involves non-users) - Guardrail: Do not force contact uploads, preselect consent, obscure sponsorship, or make core use contingent on recruiting others" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-increase-conversion-rate", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Increase Conversion Rate", "headingId": "chapter-14-go-to-market-strategy-increase-conversion-rate", "url": "#chapter-14-go-to-market-strategy-increase-conversion-rate", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Method 1: Make sign-up fast (1-click with existing email) - Method 2: Show value immediately (demo or instant usefulness) - Method 3: Social proof (\"Your friend is using this\") - Example: Team collaboration tools can show which colleagues are already active Decision view: Report K with invitation-cycle time, retained activated users, duplication, acquisition source, contribution, incentive and service cost, complaint/unsubscribe rates, and cohort confidence intervals. Use an experiment or credible quasi-experimental design to estimate causal lift where the decision warrants it. A high K paired with weak retention, poor customer outcomes, or high harm is a stop signal, not a reason to scale." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers-8", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers-8", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Treat K as a cohort-and-window diagnostic that informs a test; do not use it as a universal growth, profitability, or product-market-fit gate. - Pair diffusion with retained activation, contribution, fraud, service capacity, consent, complaints, accessibility, and customer-outcome measures. - Set invitation, incentive, privacy, and harm limits before expanding the mechanism." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques-8", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques-8", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Invitation overlap, eligibility changes, incentives, fraud, saturation, and selective retention can make K unstable or misleading. - Observed conversion does not identify the conversions caused by the product-mediated mechanism without a credible counterfactual. - Network structure and adoption dynamics differ across products, cohorts, generations, and contexts; source findings do not provide a company-specific forecast." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections-8", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections-8", "url": "#chapter-14-go-to-market-strategy-connections-8", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Experimentation: Use Framework 7 for mechanism, counterfactual, guardrail, and stop-rule design. - Funnel and economics: Use Frameworks 3–5 to connect conversion to onboarding, service cost, contribution, pricing, and cash. - Product and analysis: Use Chapters 21 and 22 for activation, retention, cohort definitions, uncertainty, and causal analysis. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview-9", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview-9", "url": "#chapter-14-go-to-market-strategy-overview-9", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The partnership evaluation matrix is an author-created comparison of partnership hypotheses across reach, customer fit, incentives, economics, execution, data/IP/security, competition, dependency, reversibility, and exit. Its categories and sample values are not benchmarks or predictions." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply-9", "url": "#chapter-14-go-to-market-strategy-how-to-apply-9", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the partner role, customer permission, incremental contribution, enablement and support cost, data and IP rights, incentive alignment, attribution, governance, dependency, audit, and termination conditions. Use a bounded pilot and staged commitment where the risks and evidence justify it. Purpose: This author-created matrix illustrates questions for comparing partnership hypotheses; its categories, weights, values, timing, and priorities are not benchmarks or predictions. Confirm authority, incentives, economics, customer effects, data/IP/security requirements, competition rules, dependencies, reversibility, and exit terms before acting. Partnership Types: 1. Distribution: Partner sells your product (e.g., reseller, channel partner) 2. Integration: Partner's product integrates with yours (e.g., API connection) 3. Co-marketing: Partner co-brands/promotes with you (e.g., joint webinar) 4. OEM: Partner embeds your solution in theirs (e.g., white-label) 5. Strategic: Partner with shared customer base (e.g., non-competing SaaS) Table 14.7: Constructed partnership-evaluation illustration. Company names, revenue potential, timing, and priorities are invented teaching inputs, not forecasts. | Partnership | Revenue Potential | Ease of Execution | Strategic Fit | Timeline | Priority | |-------------|------------------|------------------|--------------|----------|----------| | Company A (Reseller) | High ($500K yr 1) | Hard (needs sales training) | High (same customer) | 6 months | 1 | | Company B (Integration) | Medium ($100K yr 1) | Easy (API connector) | High (customers need integration) | 2 months | 2 | | Company C (Co-marketing) | Low ($20K yr 1) | Easy (webinar, email) | Medium (complementary not integrated) | 1 month | 3 | | Company D (OEM) | High potential ($1M) | Very hard (custom build) | Medium (different use case) | 12 months | 4 (future) | Scoring Methodology: - Revenue Potential: Low (< $50K), Medium ($50-200K), High ($200K+) - Ease: Hard (custom build, sales training), Medium (some requirements), Easy (standard) - Strategic Fit: How aligned with your core customer? - Timeline: Realistic time to generate first revenue? Key Evaluation Questions: 1. Do they have access to your target customer? - Example: SaaS company with 100 accountants = good partner for accounting software - Example: Random B2B tool = weak fit 2. Is the economics fair? - Reseller: negotiated margin split that leaves both parties economically motivated - Integration: Negotiate a documented share or fee from incremental contribution, enablement, support, risk, control, and customer value; no fixed split is universal - Co-marketing: Often reciprocal (both benefit equally) 3. Can they actually execute? - Do they have sales team to sell? - Do they have support team to support? - Or are you doing all the work (not a partnership)? 4. What are success metrics? - First year target: $X in revenue - Quarterly check-in: Are we on track? - Exit clause: If not working, how do we end partnership? Common Partnership Mistakes: - Pursuing partnerships instead of direct sales (less capital efficient) - Weak partners who don't deliver - Misaligned incentives (partner doesn't care about your success) - Over-investment in relationship building without revenue traction Partnership Strategy by Stage: - Earlier evidence stage: Test only the partner roles needed to learn, with explicit customer, incentive, support, control, and exit conditions. - Repeatability stage: Add integration or distribution commitments when incremental contribution, capability, governance, and capacity are evidenced. - Portfolio stage: Stage strategic or OEM relationships only when dependency, data/IP, customer ownership, service, competition, and exit risks are approved." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers-9", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers-9", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Compare partner reach and credibility with enablement, integration, support, control, attribution, dependency, and exit cost. - Require documented customer, data, IP, security, competition, sanctions, and contract approvals before irreversible commitment. - Start with a bounded pilot and predeclared evidence, remedy, renewal, and termination rules." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques-9", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques-9", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Partner-reported reach, revenue potential, and strategic fit may not translate into incremental demand or contribution. - Revenue share and stage labels are not universal rules; economics depend on effort, incentives, support, risk, control, and customer ownership. - A partner can increase concentration, operational, privacy, security, reputational, competition, and exit risk." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections-9", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections-9", "url": "#chapter-14-go-to-market-strategy-connections-9", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Channel: Use Framework 4 to compare direct, self-service, and partner routes using the same cost and capacity definitions. - Pricing and launch: Use Frameworks 5 and 6 for commercial terms, billing, readiness, support, and customer communication. - International and governance: Use Framework 11 and qualified legal, privacy, security, trade-control, tax, and competition owners for diligence. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview-10", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview-10", "url": "#chapter-14-go-to-market-strategy-overview-10", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The market-entry strategy decision tree is a constructed decision aid for comparing a new category, existing competitive market, or adjacency. It organizes evidence questions; it does not predict entry success or make a one-year commitment rule." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply-10", "url": "#chapter-14-go-to-market-strategy-how-to-apply-10", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Classify the entry context, define the first segment and job, test alternatives and incumbent response, assess channel access and service capacity, model contribution and cash, map legal and policy constraints, and choose test, adapt, partner, defer, pause, stop, or exit. State what evidence would reverse the choice. Context: This constructed decision aid compares strategic questions; it does not predict entry success. Define the market and substitutes, test demand, examine incumbent response and channel access, model cash and service capacity, and identify regulatory, competition, IP, privacy, and contract constraints before selecting an option. Figure 14.3: Evidence-gated market-entry choice (constructed). This is a decision aid, not a prediction model. Text equivalent: Classify the entry as a new category, an existing competitive market, or an adjacency. For a new category, test whether the customer job and first segment are viable. For an existing market, test whether differentiation is valuable, supportable, defensible, and deliverable. For an adjacency, test whether capabilities and permissions transfer. Each branch permits further testing, adaptation, partnership, deferral, or no entry. Strategy Definitions:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-focused-category-entry-or-new-market-development", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Focused category entry or new-market development", "headingId": "chapter-14-go-to-market-strategy-focused-category-entry-or-new-market-development", "url": "#chapter-14-go-to-market-strategy-focused-category-entry-or-new-market-development", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Goal: Test a defensible position when credible demand and operating readiness justify entry - Approach: - Bounded customer acquisition with evidence and capacity controls - Pricing and packaging supported by customer evidence and sustainable economics - Test category-education cost and whether the job is understood and valuable - Investigate switching, complements, network structure, and incumbent response rather than assuming a moat - Risk: The firm can spend heavily educating a category that lacks demand or that better-resourced competitors later enter" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-differentiation-existing-market", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Differentiation (Existing Market)", "headingId": "chapter-14-go-to-market-strategy-differentiation-existing-market", "url": "#chapter-14-go-to-market-strategy-differentiation-existing-market", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Goal: Win on unique value, not price - Approach: - Clearly articulate difference (not just \"better\") - Focus on specific use case (don't try to be everything) - Test whether willingness to pay supports the differentiated value and delivery cost - Match assisted sales, self-service, or partners to buying complexity and firm capacity - Risk: Price erosion as competitors copy features" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-niche-white-space", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Niche (White Space)", "headingId": "chapter-14-go-to-market-strategy-niche-white-space", "url": "#chapter-14-go-to-market-strategy-niche-white-space", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Goal: Own specific segment nobody else serves well - Approach: - Identify underserved customer segment (e.g., \"left-handed designers\") - Build product specifically for their needs when evidence and capacity justify the investment - Become thought leader in niche - Test adjacent niches only when transferability, economics, capacity, and customer protections are evidenced - Risk: Niche too small; outgrow it quickly and need new markets" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-land-and-expand-existing-customer", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Land-and-Expand (Existing Customer)", "headingId": "chapter-14-go-to-market-strategy-land-and-expand-existing-customer", "url": "#chapter-14-go-to-market-strategy-land-and-expand-existing-customer", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Goal: Deepen relationships with existing customers - Approach: - Introduce new product/service to existing customers (lower friction) - Focus on account growth over new customer acquisition - Cross-sell, upsell, usage expansion - Risk: Cannibalization (customer uses new product instead of old) Choosing Strategy: Table 14.8: Author-created market-entry comparison. Each row states evidence to obtain before commitment; the strategy labels do not predict success. | Situation | Candidate strategy | Evidence required before commitment | |-----------|--------------------|-------------------------------------| | New or weakly defined category | Focused category entry | Valuable job, first segment, alternatives, education cost, complements, cash, and incumbent response | | Existing market with provable difference | Differentiation | Comparative proof, willingness to pay, switching path, channel capacity, service quality, and contribution | | Existing market without broad differentiation | Niche | Segment need, reachability, viable economics, competitive response, and credible expansion or durable-focus logic | | Existing customer relationship or capability | Land-and-expand | Permission, incremental customer value, retention effects, cannibalization, capacity, and channel conflict | Decision rule: Concentration can reduce learning noise and capacity strain, but no strategy deserves a fixed one-year commitment. Define evidence, harm, cash, and authority gates, then continue, revise, pause, or stop." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers-10", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers-10", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Make the no-entry, defer, partner, adapt, bounded-pilot, and exit options visible alongside the preferred entry strategy. - Require evidence about reachability, willingness to pay, delivery, contribution, cash, incumbent response, customer protection, and reversibility. - Recheck the decision as market, policy, channel, capacity, and customer-outcome evidence changes." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques-10", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques-10", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Category, differentiation, niche, and land-and-expand labels simplify markets and can hide substitutes, power, regulation, and execution burden. - A decision tree cannot establish demand, defensibility, causal impact, or durable advantage from assumptions alone. - “Dominant,” “moat,” and fixed sequencing language can create overconfidence; entry may remain local, staged, reversible, or unattractive." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections-10", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections-10", "url": "#chapter-14-go-to-market-strategy-connections-10", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- ICP and channels: Use Frameworks 2 and 4 to define the segment, route, capacity, and learning test. - Pricing and finance: Use Framework 5 and Chapter 4 for willingness to pay, contribution, currency, cash, and downside scenarios. - International gate: Use Framework 11 for country, institutional, data, trade, partner, service, and exit constraints. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-overview-11", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-14-go-to-market-strategy-overview-11", "url": "#chapter-14-go-to-market-strategy-overview-11", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The international and non-market GTM gate is a constructed governance screen for country-, sector-, product-, channel-, entity-, and date-specific entry decisions. It highlights evidence and accountable owners; it is not a country score, legal opinion, or substitute for local advice. [BB-C14-S07] [BB-C14-S08]" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-apply-11", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-14-go-to-market-strategy-how-to-apply-11", "url": "#chapter-14-go-to-market-strategy-how-to-apply-11", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the exact entry scope and date, then map local demand, institutions, currency, tax, data, trade controls, labor, product standards, partners, service capacity, rights, and exit obligations. Treat non-compensable gates as gates; obtain documented specialist approval before transfer, launch, or irreversible investment. [BB-C14-S09] [BB-C14-S10] [BB-C14-S11] International entry is not domestic GTM with a translated website. Demand, institutions, public policy, currency, tax, data movement, product standards, trade controls, partner incentives, labor, service capacity, and exit feasibility can change the business model. Country-level indicators are a screening lens, not a substitute for country-, sector-, and transaction-specific evidence: the World Bank expressly cautions that its governance aggregates are too coarse to design specific reforms and reports uncertainty around estimates. [BB-C14-S07]" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-country-and-institution-matrix", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Country and institution matrix", "headingId": "chapter-14-go-to-market-strategy-country-and-institution-matrix", "url": "#chapter-14-go-to-market-strategy-country-and-institution-matrix", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 14.9: International and non-market entry gate. This author-created matrix assigns evidence and accountable approval; official-source markers support only their narrow rows. | Decision lane | Evidence required before commitment | Gate or trigger | |---|---|---| | Customer and competition | Local jobs, alternatives, purchasing authority, willingness to pay, switching, channel access, incumbent response | Pilot only when the first segment and buying process are evidenced | | Institutions and policy | Applicable national and subnational rules, licensing, procurement, competition, ownership, labor, consumer, product, tax, customs, IP, dispute resolution, corruption and human-rights exposure | Local counsel and accountable specialist approve the issue map; a country score never substitutes for law | | Currency and cash | Transaction, translation, and economic exposure; invoicing currency; convertibility; repatriation; tax; collections; inflation; hedge availability and cost | Finance sets exposure limits, downside rates, liquidity needs, and stop-loss or repricing rules; see Chapter 4 | | Data and technology | Data categories and subjects, hosting, cross-border transfers, localization, security, access, retention, export-control classification and end use | Privacy, security, and trade-control owners approve the architecture before transfer or release; EU transfers, for example, require an applicable GDPR transfer mechanism or condition. [BB-C14-S09] | | Partner and route to market | Beneficial ownership, competence, reputation, incentives, rights, exclusivity, subagents, audit, training, support, sanctions/export screening and termination | Diligence is risk-based and continuing; partner status is not a compliance shield. [BB-C14-S10] [BB-C14-S11] | | Operations and service | Lead time, inventory, returns, warranties, accessibility, language, local support, supplier continuity and crisis response | Capacity and customer-outcome tests pass under downside demand and disruption | | Exit and reversibility | Contract termination, employee and customer obligations, data return/deletion, inventory, licenses, asset recovery, repatriation, communications and stranded cost | Exit plan is approved before irreversible investment; trigger owners and evidence cadence are named | The S09, S10, and S11 markers support only the narrow transfer, sanctions-control, and responsible-conduct points identified in their rows. The remaining institution, tax, labor, product, partner, service, and exit questions are author-created governance prompts requiring applicable local and specialist review. The U.S. International Trade Administration's Country Commercial Guides provide current starting points for market conditions, regulations, business customs, channels, trade rules, and due diligence across more than 125 countries. They are not legal opinions or proof that a market is attractive. [BB-C14-S08] Figure 14.4: International-entry evidence and exit loop (constructed). Text equivalent: Define the exact country, segment, product, entity, channel, and decision date; test demand and economics; map institutional, policy, data, trade, tax, labor, and rights constraints; and diligence partners and capacity. If a mandatory gate fails, redesign, defer, or stop. If gates pass, run a bounded pilot with currency and customer guardrails, then scale, revise, pause, or execute the preplanned exit." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-constructed-country-comparison-exercise", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Constructed country-comparison exercise", "headingId": "chapter-14-go-to-market-strategy-constructed-country-comparison-exercise", "url": "#chapter-14-go-to-market-strategy-constructed-country-comparison-exercise", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Compare two candidate countries using the matrix above. Supply a dated local-demand exhibit, two official regulatory sources per country, a currency downside scenario, a partner-diligence packet, a data-flow map, and a service-capacity plan. Recommend direct entry, distributor, licensing, joint venture, acquisition, remote service, further research, or no entry. State which evidence is missing, which criteria are non-compensable, what would reverse the choice, and how the firm exits without abandoning customers, workers, data, or legal obligations." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-so-what-for-managers-11", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-14-go-to-market-strategy-so-what-for-managers-11", "url": "#chapter-14-go-to-market-strategy-so-what-for-managers-11", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Assign accountable owners for demand, institutional, finance, privacy, security, trade, labor, partner, service, rights, and exit decisions. - Treat non-compensable legal, safety, rights, privacy, trade, customer, and reversibility conditions as gates rather than offsetting them with market size. - Stage investment and recheck dated assumptions, policy, currency, partner, service, and customer-outcome evidence before scaling." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-limits-and-critiques-11", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-14-go-to-market-strategy-limits-and-critiques-11", "url": "#chapter-14-go-to-market-strategy-limits-and-critiques-11", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Country indicators and commercial guides are screening inputs, not transaction-specific law, permissions, forecasts, or approvals. - A complete issue map cannot remove uncertainty about enforcement, political change, currency, partners, customers, or operational disruption. - International entry can create obligations to customers, workers, communities, counterparties, and data subjects that a revenue model does not capture." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-connections-11", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-14-go-to-market-strategy-connections-11", "url": "#chapter-14-go-to-market-strategy-connections-11", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Entry choice: Use Framework 10 to compare local, adjacent, partner, defer, and no-entry options. - Partner route: Use Framework 9 for ownership, incentives, customer rights, data/IP/security, audit, and exit. - Finance, product, and evidence: Use Chapter 4 for exposure and cash, Chapter 21 for product and data decisions, and Chapter 22 for dated evidence and uncertainty; obtain qualified local review. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-summary-gtm-strategy-frameworks", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Summary: GTM Strategy Frameworks", "headingId": "chapter-14-go-to-market-strategy-summary-gtm-strategy-frameworks", "url": "#chapter-14-go-to-market-strategy-summary-gtm-strategy-frameworks", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 14.10: Constructed framework-use summary. Timing is a planning aid, not a universal sequence or readiness gate. | Framework | When to Use | Time Required | |-----------|------------|--------------| | GTM Canvas | Before any customer conversations | 2-3 hours | | ICP Framework | Before sales/marketing investments | 1-2 days | | Funnel Metrics | After first 10 customers | Ongoing (weekly review) | | Channel Strategy | When deciding sales/marketing mix | 1-2 weeks | | Pricing | Before launch | 1-2 weeks | | Launch Checklist | 4 weeks before launch | Ongoing coordination | | Growth experimentation | When a mechanism can be tested safely | Duration set by decision and measurement design | | Product-mediated diffusion | When invitations or sharing are observable | Ongoing cohort analysis | | Partnership Matrix | When partnership inquiries arrive | 1-2 days per opportunity | | Market Entry Decision | Before GTM strategy | 1 day | ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-how-to-get-started", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How To Get Started", "headingId": "chapter-14-go-to-market-strategy-how-to-get-started", "url": "#chapter-14-go-to-market-strategy-how-to-get-started", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Go-to-market strategy often feels overwhelming - there are 10+ frameworks, hundreds of decisions, and pressure to launch fast. This section provides two practical paths: a Quick Version (2-3 weeks) focused on validating your GTM Canvas and refining your ICP, and a Detailed Version (8-12 weeks) for a comprehensive GTM launch from strategy through early scale. Constructed-template boundary: Every day, week, interview count, score, target-account count, conversion rate, price, budget, workload, and decision threshold in both paths is illustrative. Managers must set a decision-specific sample and cadence from risk, heterogeneity, access, precision, capacity, cash, and legal constraints. Interviews reveal accounts and hypotheses; they do not by themselves validate demand or establish causal effects." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-version-1-quick-gtm-validation-2-3-weeks", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Version 1: Quick GTM Validation (2-3 Weeks)", "headingId": "chapter-14-go-to-market-strategy-version-1-quick-gtm-validation-2-3-weeks", "url": "#chapter-14-go-to-market-strategy-version-1-quick-gtm-validation-2-3-weeks", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Validate your GTM assumptions with real customers, refine your ICP, and prepare for launch with confidence. Timeline: 15-20 Business Days" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-days-1-2-gtm-canvas-workshop", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Days 1-2: GTM Canvas Workshop", "headingId": "chapter-14-go-to-market-strategy-days-1-2-gtm-canvas-workshop", "url": "#chapter-14-go-to-market-strategy-days-1-2-gtm-canvas-workshop", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- What: Complete the GTM Strategy Canvas (Framework #1) - How: - Gather founding team + any advisors (2-3 hour workshop) - Fill out each component: - TARGET: Who is the customer? (Be specific: industry, size, geography) - PROBLEM: What painful problem do they have? (Quantified if possible) - VALUE PROP: Why us vs. alternatives? (1 sentence, clear benefit) - CHANNEL: How will they find us? (Pick 1-2 primary channels) - PRICING: How much will they pay? (Ballpark pricing model) - ECONOMICS: What's the unit economics? (CAC estimate, LTV estimate) - GROWTH: What's Year 1 target? (Revenue, customer count) - Output: Draft GTM Canvas (1 page) - Pitfall to Avoid: Being too broad (\"anyone who needs X\" → narrow to specific segment)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-days-3-10-customer-validation-interviews", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Days 3-10: Customer Validation Interviews", "headingId": "chapter-14-go-to-market-strategy-days-3-10-customer-validation-interviews", "url": "#chapter-14-go-to-market-strategy-days-3-10-customer-validation-interviews", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- What: Talk to 20 potential customers to validate GTM assumptions - How: - Identify 50 target prospects matching your TARGET profile - Reach out via email/LinkedIn (personalized: \"Can I get 20 minutes of feedback?\") - Schedule 20 conversations (15-20 minutes each, 2-3 per day) - Interview script: - \"Tell me about [problem we think they have]\" (validate problem exists) - \"How do you solve this today?\" (understand alternatives) - \"What would make a solution worth paying for?\" (validate value prop) - \"How do you typically evaluate/buy tools like this?\" (validate channel) - \"What would you expect pricing to be?\" (validate pricing) - Track responses in spreadsheet: - Prospect name, company, role - Problem confirmed? (Yes/No/Partial) - Current solution (DIY, competitor, nothing) - Interest level (High/Medium/Low) - Pricing feedback - Output: 20 completed interviews, pattern analysis - Review signal: If the locally defined evidence share does not support urgency, revisit the PROBLEM definition; the percentage in the earlier draft was illustrative, not a universal threshold." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-days-11-15-icp-refinement-week-2", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Days 11-15: ICP Refinement (Week 2)", "headingId": "chapter-14-go-to-market-strategy-days-11-15-icp-refinement-week-2", "url": "#chapter-14-go-to-market-strategy-days-11-15-icp-refinement-week-2", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- What: Analyze interviews to identify \"who succeeds best\" - How: - Review interview notes and identify patterns: - Which companies expressed highest urgency? - Which had budget/decision authority? - Which understood value prop immediately? - Create ICP profile using Framework #2: - Firmographic: Industry, company size, revenue range, geography - Behavioral: Tech stack, buying cycle, decision process - Psychographic: Values (data-driven? risk-averse? early adopter?) - Score each interviewed company (1-10 ICP fit) - Identify top 10 best-fit prospects (your launch targets) - Output: 1-page ICP profile, scored prospect list - Pitfall to Avoid: Keeping ICP too broad (\"we can sell to anyone\") - narrow to best fit" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-days-16-20-pricing-channel-decision-launch-prep-week-3", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Days 16-20: Pricing/Channel Decision + Launch Prep (Week 3)", "headingId": "chapter-14-go-to-market-strategy-days-16-20-pricing-channel-decision-launch-prep-week-3", "url": "#chapter-14-go-to-market-strategy-days-16-20-pricing-channel-decision-launch-prep-week-3", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- What: Finalize pricing and channel strategy based on validation - How: - Pricing decision: - Review feedback from 20 interviews - Model unit economics (Framework #5): - Estimated CAC (based on channel choice) - Estimated contribution/value scenario (not observed LTV) - Target: A locally approved contribution and payback scenario with explicit margin, service cost, cash timing, and uncertainty - Pick pricing model (per-seat, value-based, freemium, usage-based) - Set initial price (can adjust later, but start somewhere) - Channel decision: - Based on ICP and interviews, which channel makes sense? (Framework #4) - Direct sales (if high-touch, complex sale) - Self-serve (if simple, low price point) - Partnerships (if need distribution help) - Pick 1-2 primary channels (focus spreading thin) - Launch prep: - Set launch date (30-60 days out) - Draft 1-page launch plan (key activities, timeline) - Identify first 10 target customers (from ICP list) - Output: Pricing decision, channel strategy, launch date set Final Deliverable (End of Week 3): - 1-page GTM Canvas (validated with 20 customers) - 1-page ICP profile (scored, with top 10 target accounts) - Pricing model decided (with unit economics modeled) - Launch date set (30-60 days out) - Confidence level: High (based on customer validation) Measurement Framework: - Daily: Customer conversations completed (target: 2-3/day during Week 1-2) - Weekly: GTM Canvas confidence (1-10 scale, target: 7+ by end of Week 3) - End of Week 3: Number of \"high interest\" prospects (target: 10+ out of 20 interviewed) ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-version-2-detailed-gtm-launch-8-12-weeks", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Version 2: Detailed GTM Launch (8-12 Weeks)", "headingId": "chapter-14-go-to-market-strategy-version-2-detailed-gtm-launch-8-12-weeks", "url": "#chapter-14-go-to-market-strategy-version-2-detailed-gtm-launch-8-12-weeks", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Comprehensive GTM strategy from canvas through launch and early optimization. Timeline: 8-12 Weeks (4 Phases)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-detailed-path-phase-1-gtm-canvas-development-validation-weeks-1-2", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Detailed-path Phase 1: GTM Canvas Development & Validation (Weeks 1-2)", "headingId": "chapter-14-go-to-market-strategy-detailed-path-phase-1-gtm-canvas-development-validation-weeks-1-2", "url": "#chapter-14-go-to-market-strategy-detailed-path-phase-1-gtm-canvas-development-validation-weeks-1-2", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 1: Draft GTM Canvas - Monday-Tuesday: GTM Canvas workshop (same as Quick Version Days 1-2) - Wednesday-Friday: Research & preparation - Identify 100 target prospects (will narrow to 50 for interviews) - Draft customer interview script - Research competitors (what's their GTM? pricing? positioning?) - Create competitor matrix (us vs. top 3 alternatives) - Output: Draft GTM Canvas, competitor analysis, interview script Week 2: Customer Validation - Monday-Friday: 20 customer interviews (4 per day) - Same interview approach as Quick Version - Focus on problem validation, alternative analysis, pricing feedback - Weekend/End of Week: Synthesize findings - Problem validation: % who confirmed urgent problem - Value prop resonance: % who understood benefit immediately - Pricing feedback: Range of acceptable pricing - Channel insights: How do they discover/evaluate tools? - Output: 20 completed interviews, synthesis memo" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-detailed-path-phase-2-icp-deep-dive-positioning-weeks-3-4", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Detailed-path Phase 2: ICP Deep Dive & Positioning (Weeks 3-4)", "headingId": "chapter-14-go-to-market-strategy-detailed-path-phase-2-icp-deep-dive-positioning-weeks-3-4", "url": "#chapter-14-go-to-market-strategy-detailed-path-phase-2-icp-deep-dive-positioning-weeks-3-4", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 3: ICP Refinement - Monday-Tuesday: Analyze interview patterns (same as Quick Version) - Create firmographic, behavioral, psychographic profile - Score all 20 interviewed companies (1-10 ICP fit) - Wednesday-Thursday: Expand ICP analysis - Identify 3-5 customer segments (if patterns emerge) - For each segment, calculate: - Size (how many companies fit this profile?) - Avg deal size (based on pricing feedback) - Win rate estimate (based on urgency/fit) - LTV:CAC estimate - Pick primary segment (best economics + best fit) - Friday: Create target account list - List 200 companies matching ICP (prioritized by fit score) - Segment into tiers: Tier 1 (top 50), Tier 2 (next 100), Tier 3 (rest) - Output: ICP profile, segmentation analysis, target account list (200 companies) Week 4: Positioning & Messaging - Monday-Tuesday: Define positioning - Value proposition (1 sentence, quantified) - Key differentiators (vs. competitors, DIY, do nothing) - Positioning statement: \"For [TARGET], who [PROBLEM], our product [SOLUTION], unlike [ALTERNATIVE]\" - Example: \"For mid-market SaaS companies who spend 3 weeks building data pipelines, DataFlow deploys in 3 days and saves $500K/year, unlike custom builds that take 6 months\" - Wednesday-Thursday: Create messaging framework - Homepage headline (7 words or less) - Value prop statement (1 sentence) - 3 key benefits (with quantified outcomes) - Customer testimonials (if available from interviews) - Objection handling (common concerns + responses) - Friday: Validate messaging - Send positioning/messaging to 5 interviewed customers (get feedback) - Iterate based on feedback (clarity, resonance) - Output: Positioning statement, messaging framework (validated)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-detailed-path-phase-3-channel-pricing-strategy-weeks-5-6", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Detailed-path Phase 3: Channel & Pricing Strategy (Weeks 5-6)", "headingId": "chapter-14-go-to-market-strategy-detailed-path-phase-3-channel-pricing-strategy-weeks-5-6", "url": "#chapter-14-go-to-market-strategy-detailed-path-phase-3-channel-pricing-strategy-weeks-5-6", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 5: Channel Strategy - Monday-Tuesday: Channel evaluation (Framework #4) - Evaluate 3-5 potential channels: - Direct sales: Calculate (# reps needed × cost per rep × ramp time) - Inside sales: Calculate (# SDRs + AEs × cost × productivity) - Self-serve: Calculate (website build + ad spend + conversion rate) - Partnerships: Identify 10 potential partners (fit, reach, feasibility) - Content marketing: Estimate (content team cost + SEO timeline) - For each channel, model: - Upfront investment (time + money) - CAC estimate (based on industry reference points) - Timeline to first customer - Scalability (can this channel get to 100 customers?) - Wednesday-Thursday: Pick 1-2 primary channels - Criteria: Best LTV:CAC ratio + fastest time to revenue + team capability - Create channel plan: - Month 1-3: Activities, budget, expected output - Month 4-6: Scale plan (if working) - Success metrics (CAC, conversion rate, payback period) - Friday: Channel partnerships (if relevant) - If partnerships is a channel, identify 5 target partners - Draft partnership proposal (1-pager: value to partner, economics, timeline) - Output: Channel strategy (1-2 primary channels), channel plan, partnership targets Week 6: Pricing & Unit Economics - Monday-Tuesday: Pricing model selection (Framework #5) - Review pricing feedback from interviews - Evaluate pricing models: - Per-user: Pros/cons, pricing range - Value-based: ROI calculation, pricing approach - Freemium: Free tier limits, conversion rate estimate - Usage-based: Pricing per unit, predictability concerns - Pick pricing model based on: - Customer preference (from interviews) - Revenue predictability - Sales complexity - Wednesday-Thursday: Unit economics modeling - Build spreadsheet model: - Inputs: Pricing, CAC (by channel), churn rate, sales cycle length - Outputs: LTV, CAC, LTV:CAC ratio, payback period, break-even timeline - Model 3 scenarios: - Base case (realistic assumptions) - Optimistic (20 percent better on all metrics) - Pessimistic (20 percent worse on all metrics) - Validate: Does the base-case contribution and payback scenario meet the locally approved threshold? (if not, adjust pricing or channel) - Friday: Finalize pricing - Set initial pricing (can iterate post-launch) - Create pricing page copy (tiers, features, pricing) - Draft pricing FAQ (common questions + answers) - Output: Pricing model decided, unit economics model, pricing page draft" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-detailed-path-phase-4-launch-preparation-execution-weeks-7-12", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Detailed-path Phase 4: Launch Preparation & Execution (Weeks 7-12)", "headingId": "chapter-14-go-to-market-strategy-detailed-path-phase-4-launch-preparation-execution-weeks-7-12", "url": "#chapter-14-go-to-market-strategy-detailed-path-phase-4-launch-preparation-execution-weeks-7-12", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 7-8: Launch Preparation - Week 7: Marketing assets - Website/landing page (value prop, product screenshots, pricing, CTA) - Sales deck (5 slides: problem, solution, differentiation, pricing, case example/testimonial) - Email templates (outreach, follow-up, launch announcement) - Product demo (recorded or live demo script) - FAQ / Help documentation (1-page \"How to Get Started\") - Week 8: Sales & partnerships - Sales process documentation (qualification, pitch, objection handling, close) - CRM setup (track leads, pipeline stages, conversion rates) - Partnership agreements (if relevant, finalize terms with 1-2 partners) - Launch target list (50 Tier 1 accounts for launch outreach) - Output: Marketing assets, sales process, partnerships finalized, launch readiness Week 9: Launch - Pre-launch (Days 1-3): - Send \"coming soon\" email to target list (50 Tier 1 accounts + interviewed prospects) - Finalize product (QA testing, performance testing) - Coordinate team (everyone knows launch plan, responsibilities) - Launch Day (Day 4): - Announce launch (email, social, website live) - Outreach to Tier 1 accounts (personalized emails from sales team) - Monitor product stability (check error rates, performance, support volume) - Respond to inquiries in real-time (<1 hour response time) - Post-launch (Days 5-7): - Follow up with interested leads (book meetings, send demos) - Collect early feedback (questionnaire or 1-on-1 conversations) - Fix critical bugs (if any identified) - Publish launch recap (metrics, wins, learnings) - Output: Launch executed, early customer feedback, first customers (target: 5-10) Weeks 10-12: Optimization & Iteration - Week 10: Measure & analyze - Track funnel metrics (Framework #3): - Awareness: Lead volume (from launch activities) - Consideration: Meeting booking rate - Proposal: Proposal submission rate - Close: Win rate - Calculate actual CAC (launch spend / customers acquired) - Calculate early LTV (based on pricing + estimated retention) - Compare to model (actual vs. projected unit economics) - Week 11: Iterate based on learnings - If low conversion: Revisit messaging (not resonating?) or ICP (wrong target?) - If high CAC: Optimize channel (reduce spend, improve targeting) - If low LTV: Revisit pricing (too low?) or retention (churn too high?) - Make 2-3 key changes based on data - Week 12: Scale preparation - Document playbook (what's working? how to replicate?) - Set Month 4-6 goals (revenue, customers, metrics) - Identify constraints (sales team capacity? product readiness? budget?) - Plan next phase (hire sales rep? expand channel? new partnerships?) - Output: GTM playbook, Month 4-6 plan, scale readiness Weekly GTM Cadences (Weeks 9-12): Sales Cadence (Weekly): - Monday: Pipeline review (where are deals? stuck? moving forward?) - Wednesday: Prospect outreach (add 20 new leads to pipeline) - Friday: Deal reviews (close deals, negotiate terms, move to next stage) Marketing Cadence (Weekly): - Tuesday: Content publish (blog post, social update, email newsletter) - Thursday: Campaign review (ad performance, email open/click rates, website traffic) - Friday: Lead handoff to sales (qualified leads from marketing → sales pipeline) Partnership Cadence (Bi-weekly): - Every other Monday: Partner check-in (leads generated? support needed? co-marketing opportunities?) Measurement Framework (Weeks 9-12): Weekly Metrics: - Customer conversations count (target: 10+ conversations/week with prospects) - Feedback patterns (are objections consistent? is messaging resonating?) - GTM Canvas confidence (1-10 scale, should be 8+ by Week 12) Launch Metrics (Weeks 9-10): - CAC (Customer Acquisition Cost): Launch spend / customers acquired, with the inclusion rule and cohort stated; compare with the approved scenario rather than a universal target. - Early value scenario: Report the contribution formula, margin, retention evidence, service cost, cohort, and uncertainty; pricing × estimated retention is not observed LTV. - Conversion rate: Leads → Meetings → Proposals → Closed (track each stage) - Retention by cohort: Are customers retained and receiving value in the defined observation window? Set the target from the decision and customer-outcome context. Monthly Metrics (Months 3-4): - Growth rate: Month-over-month revenue growth (target: 20 percent or more MoM) - Customer acquisition trend: Are we acquiring customers faster each month? - Unit economics trending: Is CAC decreasing? Is LTV increasing? (both indicate improving efficiency) Final Deliverable (End of Week 12): - GTM strategy fully executed (Canvas → ICP → Channel → Launch) - First 10-20 customers acquired - Unit economics validated (actual vs. projected) - Funnel metrics tracked (know conversion rates at each stage) - GTM playbook documented (repeatable process for next quarter) - Scale plan ready (Month 4-6 roadmap) ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-common-pitfalls", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Common Pitfalls", "headingId": "chapter-14-go-to-market-strategy-common-pitfalls", "url": "#chapter-14-go-to-market-strategy-common-pitfalls", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Even with a solid plan, GTM strategies fail for predictable reasons. Watch out for these five common pitfalls:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-1-vague-target-customer-everyone-is-not-the-customer", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "1. Vague Target Customer (\"Everyone is NOT the customer\")", "headingId": "chapter-14-go-to-market-strategy-1-vague-target-customer-everyone-is-not-the-customer", "url": "#chapter-14-go-to-market-strategy-1-vague-target-customer-everyone-is-not-the-customer", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Symptom: GTM Canvas says \"any company that needs X\" or \"B2B companies\" - Why it's a problem: Marketing becomes generic, sales wastes time on bad-fit prospects, product tries to serve everyone (serves no one well) - Fix: Force specificity in ICP - Example: Change \"SaaS companies\" → \"Series A-C SaaS companies, $5-50M ARR, 50-300 employees, US-based\" - Test: Can you list 50 companies that fit this profile? If not, too vague. - Warning sign: Conversion rates are low across all prospects (no clear \"perfect fit\" segment emerging)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-2-misaligned-channel-choice-channel-doesn-t-match-customer-buying-behavior", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "2. Misaligned Channel Choice (Channel doesn't match customer buying behavior)", "headingId": "chapter-14-go-to-market-strategy-2-misaligned-channel-choice-channel-doesn-t-match-customer-buying-behavior", "url": "#chapter-14-go-to-market-strategy-2-misaligned-channel-choice-channel-doesn-t-match-customer-buying-behavior", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Symptom: You choose self-serve, but customers need demos. Or you choose direct sales, but customers want to \"try before buy.\" - Why it's a problem: Friction between how you sell and how customers want to buy = lost deals - Fix: During interviews, ask \"How do you typically evaluate and buy tools like this?\" - If they say \"we need to see ROI analysis, talk to multiple stakeholders\" → Direct sales (high-touch) - If they say \"we just try it, if it works we buy\" → Self-serve (low-friction) - Warning sign: High lead volume but low conversion (channel mismatch)" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-3-pricing-too-high-or-too-low-no-unit-economics-analysis", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "3. Pricing Too High or Too Low (No unit economics analysis)", "headingId": "chapter-14-go-to-market-strategy-3-pricing-too-high-or-too-low-no-unit-economics-analysis", "url": "#chapter-14-go-to-market-strategy-3-pricing-too-high-or-too-low-no-unit-economics-analysis", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Symptom - Too high: Prospects say \"interested but too expensive\" OR long negotiation cycles with heavy discounting - Symptom - Too low: You're acquiring customers fast but unit economics are negative (CAC LTV) - Why it's a problem: - Too high: Kills deals, slows growth - Too low: Grows fast but burns cash (unsustainable) - Fix: Model unit economics BEFORE launch (Framework #5) - Calculate: CAC by channel and a contribution-based value scenario with margin, retention, service cost, cash timing, and uncertainty. - If ratio is too low, raise prices OR reduce CAC (improve conversion) - Test pricing with 5 customers (pilot program) before scaling - Warning sign: The value-to-acquisition relationship is below the approved decision threshold or discounting exceeds the approved policy." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-4-launch-without-measurement-no-funnel-metrics-tracked", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "4. Launch Without Measurement (No funnel metrics tracked)", "headingId": "chapter-14-go-to-market-strategy-4-launch-without-measurement-no-funnel-metrics-tracked", "url": "#chapter-14-go-to-market-strategy-4-launch-without-measurement-no-funnel-metrics-tracked", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Symptom: You launch, get some customers, but don't know which channel worked, what conversion rates are, or where prospects drop off - Why it's a problem: Can't optimize what you don't measure. You'll scale inefficient channels, miss bottlenecks, waste budget. - Fix: Set up funnel tracking BEFORE launch (Framework #3) - Track: Awareness (leads), Consideration (meetings booked), Proposal (proposals sent), Close (deals won) - Use CRM or simple spreadsheet to track every prospect through funnel - Weekly review: Where are prospects getting stuck? What's the bottleneck? - Warning sign: Can't answer \"What's our CAC?\" or \"What's our lead → customer conversion rate?\"" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-5-ignoring-competition-no-positioning-against-alternatives", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "5. Ignoring Competition (No positioning against alternatives)", "headingId": "chapter-14-go-to-market-strategy-5-ignoring-competition-no-positioning-against-alternatives", "url": "#chapter-14-go-to-market-strategy-5-ignoring-competition-no-positioning-against-alternatives", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Symptom: Prospects say \"we'll think about it\" but never close (considering alternatives) - Why it's a problem: If you don't differentiate, you're commoditized (price becomes only decision factor) - Fix: Build competitive positioning (Framework #1, Value Prop section) - Identify top 3 alternatives (competitor, DIY, do nothing) - For each, articulate: \"Unlike [alternative], we [specific benefit]\" - Example: \"Unlike custom builds that take 6 months, we deploy in 3 days\" - Validate with customers: \"Why did you choose us vs. [competitor]?\" - Warning sign: Long sales cycles with no clear reason for delay (customer is comparison shopping) How to Avoid Pitfalls: - Use frameworks (GTM Canvas, ICP, Funnel Metrics = built-in structure to catch these) - Validate early (20 customer conversations = surface issues before launch) - Measure constantly (weekly funnel review = catch problems fast) ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-red-flags-when-gtm-is-failing", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flags: When GTM is Failing", "headingId": "chapter-14-go-to-market-strategy-red-flags-when-gtm-is-failing", "url": "#chapter-14-go-to-market-strategy-red-flags-when-gtm-is-failing", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Even with a plan, GTM strategies can fail. Here are red flags that indicate you need to revisit your strategy:" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-red-flag-1-low-conversion-rates", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flag #1: Low Conversion Rates", "headingId": "chapter-14-go-to-market-strategy-red-flag-1-low-conversion-rates", "url": "#chapter-14-go-to-market-strategy-red-flag-1-low-conversion-rates", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Metric: Lead → Customer conversion materially below your modeled target - Diagnosis: - Wrong ICP (talking to companies that aren't good fit) - Weak value prop (not compelling enough) - Misaligned channel (friction in buying process) - Action: Re-interview 10 lost deals (why didn't they buy?), revisit ICP and messaging" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-red-flag-2-high-cac", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flag #2: High CAC", "headingId": "chapter-14-go-to-market-strategy-red-flag-2-high-cac", "url": "#chapter-14-go-to-market-strategy-red-flag-2-high-cac", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Metric: Acquisition cost exceeds the contribution and cash threshold approved for the defined cohort. - Diagnosis: - Inefficient channel (high cost, low conversion) - Pricing too low (not capturing enough value) - Long sales cycle (high time/cost to close) - Action: Model unit economics again, consider raising prices OR switching channels" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-red-flag-3-no-word-of-mouth-referrals", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flag #3: No Word-of-Mouth / Referrals", "headingId": "chapter-14-go-to-market-strategy-red-flag-3-no-word-of-mouth-referrals", "url": "#chapter-14-go-to-market-strategy-red-flag-3-no-word-of-mouth-referrals", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Metric: low share of new customers from referrals after the initial customer cohort - Diagnosis: - Product not sticky (customers don't love it enough to refer) - No incentive to refer (not easy/rewarding to share) - Wrong ICP (customers aren't networked) - Action: Customer interviews (why aren't they referring?), implement referral program, improve product experience" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-red-flag-4-high-early-churn", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flag #4: High Early Churn", "headingId": "chapter-14-go-to-market-strategy-red-flag-4-high-early-churn", "url": "#chapter-14-go-to-market-strategy-red-flag-4-high-early-churn", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Metric: excessive early churn in the first customer cohort - Diagnosis: - Over-promised during sales (expectations not met) - Poor onboarding (customers don't get value fast) - Wrong ICP (customers aren't right fit) - Action: Interview churned customers (why did they leave?), improve onboarding, tighten ICP" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-red-flag-5-stalled-growth", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flag #5: Stalled Growth", "headingId": "chapter-14-go-to-market-strategy-red-flag-5-stalled-growth", "url": "#chapter-14-go-to-market-strategy-red-flag-5-stalled-growth", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Metric: growth materially below the plan after the first operating quarter - Diagnosis: - Market too small (ran out of ICP targets) - Channel saturated (exhausted initial leads) - Competition caught up (differentiation eroded) - Action: Expand ICP (adjacent segments?), add new channel, revisit differentiation What to Do When You See Red Flags: 1. Stop scaling (don't pour money into broken GTM) 2. Diagnose root cause (talk to customers, analyze data) 3. Fix core issue (adjust ICP, messaging, pricing, channel) 4. Validate fix (test with 5-10 customers before scaling again) 5. Resume growth (once unit economics and conversion rates are healthy) ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-why-this-matters-mental-models-gtm-wisdom", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Why This Matters: Mental Models & GTM Wisdom", "headingId": "chapter-14-go-to-market-strategy-why-this-matters-mental-models-gtm-wisdom", "url": "#chapter-14-go-to-market-strategy-why-this-matters-mental-models-gtm-wisdom", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Go-to-market strategy is a system of interconnected decisions about how a firm creates, captures, and delivers value. The arithmetic, cases, channel ranges, stage bands, and outcomes in this section are constructed teaching examples or composites, not observed company histories, causal estimates, or benchmarks. They surface hypotheses and trade-offs that a manager must test against local evidence." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-1-gtm-canvas-holistic-customer-view-across-acquisition-activation-retention", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "1. GTM Canvas: Holistic Customer View Across Acquisition, Activation, Retention", "headingId": "chapter-14-go-to-market-strategy-1-gtm-canvas-holistic-customer-view-across-acquisition-activation-retention", "url": "#chapter-14-go-to-market-strategy-1-gtm-canvas-holistic-customer-view-across-acquisition-activation-retention", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Systems Thinking: Most founders treat acquisition, product, and pricing as separate problems. The GTM Canvas forces holistic thinking: every component affects every other component . Your pricing model affects which customers you can acquire profitably. Your ICP determines which channels work. Your channel determines what unit economics are possible. The canvas prevents the common failure mode: optimizing one part while breaking the whole. The Psychology: A GTM plan is a system : changing one variable can alter the economics of the others. A canvas can make those dependencies discussable. In a constructed example, placing \"CAC: $5K\" and \"ARPU: $100/month\" on the same page prompts the team to calculate a simple 50-month revenue payback before margin, retention, or cash-timing adjustments. Why It Works: - Supports trade-off visibility: A constructed high-touch-sales case with $30K CAC and $99 monthly pricing exposes a mismatch that requires full margin, retention, and cash analysis. - Supports scenario iteration: Changing a constructed price assumption from $99 to $299 shows how one input affects modeled unit economics; it does not establish willingness to pay. - Prevents silo optimization: Marketing can't optimize for volume if sales can't handle the leads - Creates alignment: When whole team sees the canvas, everyone understands how their work fits together The Failure Mode: Teams can optimize local metrics while degrading the overall system. A constructed example is marketing celebrating 10,000 leads while sales lacks capacity, or sales celebrating 100 customers while finance estimates that CAC exceeds LTV. A canvas can surface the disagreement, but it cannot prevent local optimization without shared definitions, incentives, governance, and decision rights. The Economic Principle: The GTM Canvas operationalizes strategic fit - Porter's concept that competitive advantage comes from how activities reinforce each other. Your channel choice reinforces your pricing, which reinforces your ICP, which reinforces your product positioning. When these elements fit together, you have a defensible business. When they don't, you have a pile of disconnected tactics." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-2-icp-focus-concentration-of-resources-on-highest-value-customers", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "2. ICP Focus: Concentration of Resources on Highest-Value Customers", "headingId": "chapter-14-go-to-market-strategy-2-icp-focus-concentration-of-resources-on-highest-value-customers", "url": "#chapter-14-go-to-market-strategy-2-icp-focus-concentration-of-resources-on-highest-value-customers", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Strategic Insight: The counter-intuitive truth about customer acquisition: narrowing your target increases your success rate . Most founders fear narrowing: \"But we're leaving money on the table!\" The opposite is true. Trying to sell to everyone means your message resonates with no one, your product serves no one excellently, and your resources scatter across hundreds of mediocre opportunities. The Math: Consider two strategies: - Broad: Target 1,000 companies, 5 percent win rate, $50K deal size, $10K CAC → 50 customers, $2.5M revenue, $500K CAC spend - Narrow ICP: Target 200 companies (perfect fit), 25 percent win rate, $50K deal size, $8K CAC → 50 customers, $2.5M revenue, $400K CAC spend Same revenue, but the narrow approach has: - Lower modeled CAC ($8K vs $10K in this constructed comparison): Investigate whether the difference reflects message fit, lead mix, sales-cycle length, attribution, exclusions, or random variation. - Higher win rate (25 percent vs 5 percent): Sales team focuses on qualified leads - Better retention : Perfect-fit customers stay longer (higher LTV) Why It Works: - Message clarity: \"For mid-market SaaS companies\" resonates more than \"for any company\" - Product focus: Build features perfect-fit customers need, ignore edge cases - Sales efficiency: Reps become experts in one customer type, learn objections, iterate playbook - Retention: Customers who perfectly fit your ICP get more value, churn less The Psychological Trap: Founders resist narrowing because it feels like artificial constraint. \"Why would I say no to a customer?\" The answer: opportunity cost . Every hour spent on a mediocre-fit customer is an hour not spent on a perfect-fit customer. The narrow ICP isn't about saying no to customers - it's about saying yes to the strategy that produces the most customers. The Failure Mode: \"Spray and pray\" GTM: Sales targets 5,000 companies with generic messaging. Win rate is 2 percent. Sales team blames product or marketing. Real problem: No ICP discipline. The solution isn't better messaging - it's narrower targeting so messaging can actually be specific." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-3-channel-strategy-matching-customer-behaviors-to-go-to-market-approaches", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "3. Channel Strategy: Matching Customer Behaviors to Go-to-Market Approaches", "headingId": "chapter-14-go-to-market-strategy-3-channel-strategy-matching-customer-behaviors-to-go-to-market-approaches", "url": "#chapter-14-go-to-market-strategy-3-channel-strategy-matching-customer-behaviors-to-go-to-market-approaches", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Core Principle: Channels are not interchangeable distribution pipes. Each has acquisition, enablement, support, control, and margin implications. Low-touch selling can fit some simple, lower-stakes purchases; complex or high-stakes purchases may require more assisted evaluation. Match the channel to observed buying behavior and economics rather than treating price as a deterministic selector. The Economics: Each channel has a natural CAC range and customer expectation: Table 14.11: Constructed channel-model comparison. Values are illustrative ranges and descriptive expectations to test locally, not natural channel properties. | Channel | Natural CAC | Customer Expectation | Works For | |---------|-------------|---------------------|-----------| | Self-serve | $50-500 | Try immediately, low assisted-sales burden | $10-100/month, simple products | | Inside sales | $1K-5K | Personalized demo and assisted evaluation | $100-500/month, some complexity | | Direct sales | $10K-50K | Multi-stakeholder, custom solution | $50K+/year, high complexity | The Mismatch Failure Mode: - Self-serve for complex product: Customers bounce (too confusing without help) - Direct sales for simple product: CAC too high (spending $20K to acquire $500/year customer) - Inside sales for tiny deals: Sales team drowns in small deals, can't hit quota Why It Works When Matched: - Self-serve + Simple product: Customer can try immediately, get value, convert - Direct sales + Complex product: Sales guides customer through evaluation, justifies ROI (Salesforce, SAP) - Inside sales + Mid-market: Balance of touch (phone/video calls) and efficiency (no travel) The Strategic Insight: Channel design influences unit economics but does not determine them alone. Direct sales can add acquisition and service cost, so test whether observed contract value, margin, retention, sales-cycle length, and cash timing support it. Customer segment, product, channel, and economics should be modeled jointly rather than derived from a universal CAC, ACV, or LTV:CAC rule." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-4-pricing-psychology-value-perception-vs-cost-basis", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "4. Pricing Psychology: Value Perception vs. Cost Basis", "headingId": "chapter-14-go-to-market-strategy-4-pricing-psychology-value-perception-vs-cost-basis", "url": "#chapter-14-go-to-market-strategy-4-pricing-psychology-value-perception-vs-cost-basis", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The Counterintuitive Truth: Value-based pricing treats the customer's perceived economic value and credible alternatives as central inputs, while cost, capacity, risk, competition, and required return constrain what is viable. A constructed cost-plus example—\"It costs us $20 to deliver, so we'll charge $30\"—does not establish willingness to pay. If an offer may create large annual savings, quantify and validate that value before using it in pricing. [BB-C14-S05] The Psychology of Price: Customers don't buy products - they buy outcomes. Your price should reflect the value of the outcome , not the cost of your inputs. Consider: - Payment processors charge per transaction: The price reflects payment reliability and business value, not only processing cost. - Constructed enterprise-software case: Assume a $100K annual price and a customer-estimated $1M annual benefit, then test implementation cost, adoption, realized benefit, alternatives, risk, and willingness to pay. The Three Pricing Failures: 1. Too low: Based on costs, not value. Customers assume low price = low quality. You leave money on table. 2. Too high: Based on wishful thinking, not value. Customers can't justify ROI. You get no customers. 3. Wrong model: Per-seat when usage-based fits better (or vice versa). Customers confused or feel cheated. Why Value-Based Pricing Works: - Tests differentiated value: If enterprise users report materially greater value than smaller buyers, test differentiated packaging and willingness to pay rather than applying a fixed multiple. - Tests shared economics: In a constructed case, compare a customer's estimated $1M benefit with a proposed $200K price, implementation cost, uncertainty, and alternatives. - Makes assumptions explicit: A claim such as \"estimated $500K annual benefit for a $100K investment\" still requires a documented baseline, causal logic, sensitivity range, and later benefit realization. - Potential retention mechanism: Clear, realized value may support retention, but churn also depends on product quality, alternatives, switching, service, contracts, price, and customer conditions. The Failure Mode: Founders who never ask \"What's this worth to the customer?\" end up either: - Underpriced: Growing fast but unit economics broken (every customer loses money) - Overpriced: No sales because customers can't justify ROI The Strategy: During customer discovery, ask what the problem costs today and what evidence supports that estimate. Treat stated willingness to pay as a hypothesis, not a binding boundary. Combine it with observed purchase behavior, alternatives, implementation burden, cost-to-serve, and controlled price tests before selecting a price. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-composite-1-consumer-file-sync-platform-gtm-conflict", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Composite 1: Consumer File-Sync Platform — GTM Conflict", "headingId": "chapter-14-go-to-market-strategy-composite-1-consumer-file-sync-platform-gtm-conflict", "url": "#chapter-14-go-to-market-strategy-composite-1-consumer-file-sync-platform-gtm-conflict", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "What Happened: A consumer file-syncing platform grew through a freemium model, then tried to move upmarket into enterprise accounts. The shift created GTM confusion because the original consumer motion and the enterprise motion required different pricing, product, and sales systems. The GTM Confusion: The company tried to run two completely different GTM motions simultaneously : - Consumer GTM: Self-serve freemium, viral growth, low monthly subscription, no sales team - Enterprise GTM: Direct sales, complex deals, annual contracts, dedicated sales team What Failed: 1. Channel Conflict: Free users in enterprises blocked paid enterprise deals (\"Why pay when we can use free?\") 2. Sales Complexity: Sales reps struggled to sell against free product their own company offered 3. Product Fragmentation: Enterprise needed security, admin controls, compliance (different product from consumer) 4. Brand Confusion: Was the product a consumer utility or enterprise tool? Market couldn't tell. 5. Economics Mismatch: Consumer and enterprise unit economics required different strategies What The GTM Should Have Shown: - ICP Clarity: The company should have chosen: consumer OR enterprise, not both - Channel Fit: Can't run self-serve freemium AND direct sales (they cannibalize each other) - Pricing Strategy: Freemium works for consumer, not for enterprise (CFOs don't want \"free trial\" culture) What Actually Happened: The company spent years trying to bridge consumer and enterprise GTM. Result: - Slow enterprise growth: Sales team struggled against free product - Consumer revenue stagnation: Free users never converted to paid at high rates - Investor narrative complexity: The market struggled to understand whether the company was a consumer utility or enterprise platform What Could Have Saved Them: 1. Separate Brands: Create a business product as a clearly distinct offer 2. Kill Freemium for Enterprise: No free tier for business email domains (force paid from Day 1) 3. Choose One Lane: Double down on consumer OR pivot fully to enterprise (don't straddle) 4. Pricing Confidence: Charge enterprise pricing that reflects security, administration, and compliance value The Learning: You can't run two conflicting GTM strategies simultaneously. Consumer GTM (freemium, viral, self-serve) and enterprise GTM (direct sales, paid, high-touch) have opposite requirements. Trying to do both created friction, confusion, and missed opportunity. Pick one GTM, execute excellently, then (maybe) expand to the other." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-composite-2-team-collaboration-platform-gtm-evolution", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Composite 2: Team Collaboration Platform — GTM Evolution", "headingId": "chapter-14-go-to-market-strategy-composite-2-team-collaboration-platform-gtm-evolution", "url": "#chapter-14-go-to-market-strategy-composite-2-team-collaboration-platform-gtm-evolution", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "What Happened: A team collaboration platform launched with a freemium, viral, self-serve GTM. The model worked well for small teams, but stopped working at enterprise scale , forcing a GTM transformation toward direct sales and enterprise controls. The Original GTM: - Freemium: Free for small teams, paid for advanced features - Viral: Every person invited to the workspace could invite others - Self-serve: No sales team, customers signed up via website - Economics: Low-touch acquisition economics were strong while teams bought on their own Why It Stopped Working: 1. Enterprise adoption hit wall: Free teams inside F500 companies grew, but companies didn't centrally adopt 2. Security/Compliance concerns: IT departments blocked adoption when enterprise controls were insufficient 3. Revenue leakage: Large companies could use free workspaces instead of central paid deployments 4. Competition: Bundled enterprise alternatives changed the buying conversation The Forced Pivot: The company had to add: - Direct sales team: Enterprise reps to sell into large accounts - Enterprise features: SSO, compliance, admin controls, data residency - New pricing: Enterprise packages for large deployments - Marketing shift: From \"fun\" consumer brand to \"secure\" enterprise brand The GTM Cost: - Sales team expense: A major new operating cost - CAC expansion: Enterprise selling costs were structurally higher than self-serve acquisition - Slower growth: Viral growth stalled; sales-led growth is slower - Lower margins: Direct sales adds operating cost and reduces contribution margin What The GTM Evolution Taught: - Viral GTM doesn't scale to enterprise: F500 companies don't adopt via bottom-up viral; they require top-down sales - Free users aren't revenue: Large free-user populations still need conversion into paid company accounts - Competitive response required GTM shift: Bundled alternatives forced the product to prove enterprise value through sales - Stage dependency: Viral GTM works early (low CAC, high growth), but mature markets require sales-led GTM What Could Have Prevented Crisis: 1. Earlier enterprise investment: Build security/compliance features before enterprise demand forced the issue 2. Hybrid GTM from start: Viral for SMB, sales-led for enterprise (not \"flip the switch\" later) 3. Kill free tier for large companies: Force companies 100 people to pay from Day 1 4. Pricing power: Charge for enterprise value and invest in enterprise sales earlier The Learning: Your GTM must evolve with market maturity. What works in early revenue stages (viral, freemium, self-serve) often doesn't work at enterprise scale (sales-led, paid, high-touch). Founders must anticipate this evolution, not react in crisis mode." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-composite-3-enterprise-analytics-vendor-mid-market-mismatch", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Composite 3: Enterprise Analytics Vendor — Mid-Market Mismatch", "headingId": "chapter-14-go-to-market-strategy-composite-3-enterprise-analytics-vendor-mid-market-mismatch", "url": "#chapter-14-go-to-market-strategy-composite-3-enterprise-analytics-vendor-mid-market-mismatch", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "What Happened: An enterprise analytics vendor built an enterprise-focused GTM: direct sales, long sales cycles, large contracts, and dedicated implementation teams. When the company tried to expand to mid-market companies with the same GTM, the motion did not fit the segment economics. The Enterprise GTM (What Worked): - ICP: Large enterprises and government agencies - Deal Size: Large multi-year contracts - Sales Cycle: 12-24 months (complex procurement) - Channel: Direct sales, C-suite relationships, multi-year contracts - CAC: High acquisition cost, justified only by large deal size The Mid-Market Disaster (What Failed): The vendor assumed: \"We can take our proven GTM and apply it to smaller companies.\" They were wrong. Why It Failed: 1. CAC Mismatch: Enterprise acquisition costs do not work for mid-market budgets 2. Sales Cycle Too Long: Mid-market companies can't afford 12-month evaluation (need revenue faster) 3. Product Complexity: The product required dedicated implementation teams; mid-market customers could not afford that burden 4. Buying Process: F500 has procurement departments; mid-market has VP who needs quick decision 5. Pricing: Enterprise minimums were too large for mid-market revenue bases What The Pattern Showed: - Win Rate: Mid-market prospects did not convert at enterprise rates - Deal Size: Average contract value could not support enterprise CAC - Sales Cycle: Evaluation stayed too long for the segment - Churn: Product fit was weaker outside the enterprise segment What The GTM Should Have Revealed: - Channel: Mid-market needs lower-touch sales, not enterprise field sales - Product: Mid-market needs self-serve onboarding, not 6-month implementations - Pricing: Mid-market needs a package sized to its budget and buying process What They Did Instead: Doubled down on enterprise GTM and abandoned the mid-market motion. The lesson was expensive but clear. What Could Have Prevented Failure: 1. Different GTM for Different Segment: Build mid-market GTM from scratch (inside sales, lower-touch, simpler product) 2. Unit Economics Modeling: Before investing, model: \"Can we acquire mid-market customers at a CAC the deal size supports?\" 3. Product Simplification: Build a simpler version with self-serve setup 4. Test Before Scale: Pilot with 10 mid-market companies using new GTM, prove it works before hiring 50 sales reps The Learning: Enterprise GTM doesn't translate to SMB/mid-market. The channels, economics, sales cycles, and product requirements are fundamentally different. Founders often assume: \"We can sell to anyone!\" False. Each customer segment requires a different GTM system . Applying the wrong GTM to the wrong segment burns money fast. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-competing-schools-different-gtm-philosophies", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Competing Schools: Different GTM Philosophies", "headingId": "chapter-14-go-to-market-strategy-competing-schools-different-gtm-philosophies", "url": "#chapter-14-go-to-market-strategy-competing-schools-different-gtm-philosophies", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Understanding competing GTM philosophies helps founders choose the right approach for their market, product, and stage. Each school of thought has fierce advocates, clear strengths, and predictable failure modes. Comparison boundary: The categories are simplified design options. All CAC, deal-size, margin, speed, sustainability, and stage claims are illustrative hypotheses; channel performance depends on definitions, segment, capacity, competition, product, service, cash timing, and causal evidence." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-1-direct-vs-indirect-sales-margin-vs-channel-scale", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "1. Direct vs. Indirect Sales (Margin vs. Channel Scale)", "headingId": "chapter-14-go-to-market-strategy-1-direct-vs-indirect-sales-margin-vs-channel-scale", "url": "#chapter-14-go-to-market-strategy-1-direct-vs-indirect-sales-margin-vs-channel-scale", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Direct Sales Philosophy: - Core Belief: Own the customer relationship; highest margin, best customer insight - Method: Build internal sales team, control entire sales process - Economics: High margin, but high CAC per customer - Possible fit: Complex, high-stakes purchases that require assisted evaluation; validate the economics and buyer process. Indirect Sales (Channel Partner) Philosophy: - Core Belief: Scale faster by leveraging partners' existing customer relationships - Method: Recruit resellers, VARs (Value-Added Resellers), system integrators - Economics: Lower margin because partners take a share, but lower CAC because partners invest in sales - Possible fit: Offers that partners can credibly sell or implement where reach, enablement, control, and margin sharing are acceptable. The Trade-offs: Table 14.12: Direct and indirect route trade-offs. The comparison is an author-created decision aid; performance depends on segment, capacity, economics, governance, and customer ownership. | Dimension | Direct Sales | Indirect Sales | |-----------|--------------|----------------| | Margin | High | Lower because partners take a share | | CAC | Often higher because the seller bears the sales motion; measure it | May be lower for the vendor but must include enablement, incentives, and channel support | | Control | High (you train, manage reps) | Low (partners do what they want) | | Scale Speed | Slow (hiring, ramping reps) | Fast (partners already have customers) | | Customer Insight | High (direct relationship) | Low (partner is intermediary) | When Direct Sales Wins: - High-value, complex products: Assisted sales may be justified when contribution margin, retention, implementation, sales-cycle length, and risk support the acquisition cost. - Product differentiation: You need to explain unique value (partners won't learn complex pitch) - Early stage: Before PMF, founders need direct customer feedback (can't outsource learning) - Enterprise: Large deals require C-suite relationships (partners don't have this access) When Indirect Sales Wins: - Commodity/known products: \"We sell CRM\" doesn't need complex explanation; partners can sell - Geographic scale: Expanding to 50 countries; partners provide local presence cheaply - Lower-value deals: Direct sales may be uneconomic when acquisition and service costs exceed risk-adjusted contribution; partner cost is not automatically lower and must be measured. - Existing relationships: Partners already sell to your ICP (instant distribution) The Hybrid Mistake: Many companies try both simultaneously. Result: Channel conflict (partners and internal reps compete for same customers), confusion (who owns the customer?), margin erosion (partners demand bigger cut to compensate for competition). Choose one, execute excellently, then (maybe) add the other with clear rules. The Synthesis: Direct, indirect, and hybrid routes can each be appropriate. A direct motion may improve early customer learning in some contexts; a partner route may add reach or capability in others. Choose from observed buying behavior, incremental economics, service capacity, governance, customer ownership, and reversibility, then test the selected route rather than treating stage or product-market-fit labels as universal sequencing rules." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-2-product-mediated-earned-and-paid-acquisition", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "2. Product-Mediated, Earned, and Paid Acquisition", "headingId": "chapter-14-go-to-market-strategy-2-product-mediated-earned-and-paid-acquisition", "url": "#chapter-14-go-to-market-strategy-2-product-mediated-earned-and-paid-acquisition", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Acquisition mechanisms are hypotheses about how exposure, adoption, and retention occur. Weinberg's Bullseye method treats acquisition-channel choice as testable: brainstorm across possible channels, rank candidates, run small tests, focus on evidence, and repeat when the current channel plateaus. [BB-C14-S04] The taxonomy below and the cautions that “organic” is not free, “viral” is not automatic, and paid growth is not inherently predictable are author synthesis. Diffusion dynamics provide context, not a company-specific forecast. Table 14.13: Author-created acquisition-mechanism questions. Use the table to define evidence and guardrails; it is not a taxonomy or performance ranking. | Dimension | Questions to test | |---|---| | Causal incrementality | Which conversions would not have occurred without the mechanism? Use holdouts or credible counterfactuals where feasible. | | Retention and customer quality | Do acquired cohorts retain, expand, support, and refer at economically meaningful rates? | | Cost | Include creative, product, incentive, agency, sales, tooling, discount, fraud, support, and opportunity costs—not media spend alone. | | Saturation and dependence | How do marginal response, auction prices, platform rules, network density, and channel concentration change with scale? | | Consent and brand | Are referral, tracking, targeting, and messaging lawful, accessible, non-deceptive, and consistent with customer expectations? | | Cash and reversibility | What working capital, commitment, learning speed, and downside exposure does the mechanism create? | Run channel tests with pre-specified primary and guardrail measures, segment and cohort reporting, attribution limits, and stop/scale rules. A product-mediated loop may work for one use case and fail in another; paid acquisition may add incremental demand, cannibalize existing demand, or attract lower-retention cohorts. Do not rank a channel until the evidence and full economics support the decision. [BB-C14-S04]" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-3-horizontal-and-vertical-gtm-as-design-choices", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "3. Horizontal and Vertical GTM as Design Choices", "headingId": "chapter-14-go-to-market-strategy-3-horizontal-and-vertical-gtm-as-design-choices", "url": "#chapter-14-go-to-market-strategy-3-horizontal-and-vertical-gtm-as-design-choices", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "“Horizontal” and “vertical” are positioning and operating choices, not fixed performance laws. A horizontal design can address a broadly shared job but may face generic positioning, integration breadth, and varied workflows. A vertical design can encode segment-specific workflow, language, regulation, and channel knowledge but may face concentration, bespoke service, or expansion limits. Compare observed segment value, workflow commonality, compliance, channel access, service capacity, contribution economics, concentration risk, and transferability. Expansion from one vertical, use case, or geography is one option; starting horizontal, remaining focused, partnering, or not entering can also be rational. The prior named-company and categorical win-rate, moat, speed, and value claims were removed because no adjacent source established them. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-stage-dependent-gtm-tailoring", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Stage-Dependent GTM Tailoring", "headingId": "chapter-14-go-to-market-strategy-stage-dependent-gtm-tailoring", "url": "#chapter-14-go-to-market-strategy-stage-dependent-gtm-tailoring", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Stage labels can organize questions, but ARR, customer count, channel count, staffing, CAC/LTV, and cadence do not define universal maturity gates. Assess the venture's evidence, product, buying process, service model, regulation, cash, capacity, and strategic options directly." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-earlier-evidence-stage", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Earlier evidence stage", "headingId": "chapter-14-go-to-market-strategy-earlier-evidence-stage", "url": "#chapter-14-go-to-market-strategy-earlier-evidence-stage", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Define a bounded segment, buying unit, job, alternatives, proof, and customer-harm guardrails. - Compare a small set of channels only to the degree needed to learn; simultaneous tests can be appropriate when attribution, capacity, and cash permit them. - Founder contact can improve learning, but founders need not perform every sale or delay all specialist hiring. - Estimate economics as ranges with explicit missing data; no ratio or customer count proves product-market fit." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-repeatability-and-expansion-stage", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Repeatability and expansion stage", "headingId": "chapter-14-go-to-market-strategy-repeatability-and-expansion-stage", "url": "#chapter-14-go-to-market-strategy-repeatability-and-expansion-stage", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Test whether acquisition, onboarding, retained value, service quality, and contribution transfer across comparable cohorts. - Add channels, segments, and staff when evidence, capacity, governance, and cash justify the added complexity. - Document decision-relevant processes without assuming one playbook, revenue band, or founder/recruit transition defines readiness. - Treat brand, profitability, risk controls, and customer success as context-dependent—not concerns that automatically wait for a later stage." }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-portfolio-stage", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Portfolio stage", "headingId": "chapter-14-go-to-market-strategy-portfolio-stage", "url": "#chapter-14-go-to-market-strategy-portfolio-stage", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Different segments may require different assisted, self-service, partner, service, pricing, and contract designs. - Portfolio complexity requires stable definitions, capacity, channel-conflict rules, customer-outcome controls, and segment-level contribution and cash evidence. - Forecast accuracy is one planning diagnostic, not proof of a mature GTM system. - Continue, adapt, pause, or retire motions from evidence; scale is not an automatic progression. Key takeaway: Match GTM design to the decision and evidence rather than to a rigid startup ladder. A single segment/channel can improve focus in some contexts; multiple motions can improve learning or coverage in others. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-case-example-b2b-saas-launch", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Case Example: B2B SaaS Launch", "headingId": "chapter-14-go-to-market-strategy-case-example-b2b-saas-launch", "url": "#chapter-14-go-to-market-strategy-case-example-b2b-saas-launch", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed case: DataFlow is fictional. Every company attribute, partner, price, funnel value, result, and causal interpretation below is illustrative and must not be attributed to a real company or treated as a benchmark. Company: DataFlow (fictional data-pipeline software venture) Application: 1. GTM Canvas: - Target: SMB data teams ($5M-50M revenue) - Problem: 3-week data pipeline setup - Value prop: Deploy in 3 days, $500K/year savings - Channel: Direct sales + partnerships - Pricing: $50K/year subscription - Unit economics hypothesis: $5K CAC and $250K five-year revenue proxy produce a 50:1 revenue-proxy/CAC ratio, not LTV:CAC. A decision-grade LTV requires retention, gross-margin contribution, service cost, discounting, and cohort uncertainty. 2. ICP: Mid-market SaaS companies with 10+ engineers, $500K annual IT budget 3. Sales Funnel: Target 300 leads → 180 meetings → 72 proposals → 36 closes (20 percent conversion) 4. Channel Strategy: 70 percent direct sales (high-touch), 30 percent partnerships (with data infrastructure vendors) 5. Pricing: $50K/year ($5K/month minimum), plus usage overage for high-volume companies 6. Launch Plan: - Week 1: Test two integration or distribution partnerships - Week 2: Launch product + press + email to 500 target customers - Week 3-4: Sales team outreach to top 100 ICP companies - Month 2: Referral program (existing customer = $10K credit for referral) 7. Growth experimentation: Product-led trial and integration hypotheses with causal, retention, service, and customer-harm guardrails 8. Partnerships: Model three hypothetical integration partners and test their access, incentives, control, support burden, and incremental contribution Constructed scenario results: - Launch month: 50 signups (15 percent from press, 60 percent from partnerships, 25 percent from direct) - Month 3: 20 closed customers ($1M ARR annualized) - Growth: 25 percent MoM on track to $3M ARR by end of year Interpretation: The figures demonstrate internal consistency checks; they do not establish that focus or execution caused the result. A real evaluation would compare cohorts or use a credible counterfactual and would examine retention, contribution, cash, capacity, and harm. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-operating-manual-your-10-week-gtm-launch", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Operating Manual: Your 10-Week GTM Launch", "headingId": "chapter-14-go-to-market-strategy-operating-manual-your-10-week-gtm-launch", "url": "#chapter-14-go-to-market-strategy-operating-manual-your-10-week-gtm-launch", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This operating manual translates the GTM Strategy frameworks into a week-by-week execution plan. Use this when you have a product ready to launch and need a structured approach to acquire your first 20-50 customers through validated channels, positioning, and pricing. Constructed operating-template boundary: The ten-week cadence, hours, counts, budgets, ratios, conversion targets, prices, and decision triggers below are worked assumptions, not evidence-based benchmarks. Adapt or reject them through the responsible owner, qualified legal/finance/privacy review, customer risk, measurement design, capacity, cash, and the actual approval path. Passing a numeric gate does not validate demand, product-market fit, causality, or legal readiness. Timeline Overview: 10 weeks from GTM canvas workshop to first revenue and optimization Prerequisites: - Product is built (MVP or beyond) - You have validated problem-solution fit with at least 10 customer interviews - Founding team can dedicate 50-60 hours/week to GTM execution Outcome Targets: - Week 10: 10-20 paying customers acquired - Validated ICP profile (scored, documented) - Proven acquisition channel with known unit economics - Pricing model validated through actual sales - Documented sales playbook for replication ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-operating-template-phase-1-gtm-strategy-development-weeks-1-2", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Operating-template Phase 1: GTM Strategy Development (Weeks 1-2)", "headingId": "chapter-14-go-to-market-strategy-operating-template-phase-1-gtm-strategy-development-weeks-1-2", "url": "#chapter-14-go-to-market-strategy-operating-template-phase-1-gtm-strategy-development-weeks-1-2", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 1: GTM Canvas & Competitive Positioning Day 1-2: GTM Canvas Workshop (16 hours total) - Monday Morning (4h): Assemble founding team + any advisors - Complete GTM Strategy Canvas (Framework #1): - TARGET: Define specific customer segment (industry, size, geography, growth stage) - PROBLEM: Quantify the painful problem (hours lost, revenue impact, cost burden) - VALUE PROP: Draft 1-sentence differentiation vs. alternatives - CHANNEL: Identify 2-3 potential acquisition channels - PRICING: Ballpark pricing model and price point - ECONOMICS: Estimate CAC and LTV based on channel/pricing assumptions - GROWTH: Set Year 1 targets (revenue, customer count) - Output: Draft GTM Canvas (1 page document) - Monday Afternoon (4h): Pressure-test each component - TARGET: Can you list 100 companies that fit this profile? - PROBLEM: Have you interviewed 10+ customers who confirm this is top-3 problem? - VALUE PROP: Can customer understand benefit in one sentence? - CHANNEL: Do you have access to this channel (network, budget, expertise)? - PRICING: Does the defined pricing and contribution scenario meet the locally approved threshold? - Output: Revised GTM Canvas with confidence scores (1-10) for each component - Tuesday Morning (4h): Competitive analysis - Identify top 3 alternatives (competitors, DIY solutions, \"do nothing\") - For each alternative, document: - Pricing model and price point - Target customer (who uses them?) - Strengths (what do they do well?) - Weaknesses (where do they fail customers?) - GTM approach (how do they acquire customers?) - Output: Competitive matrix (you vs. 3 alternatives) - Tuesday Afternoon (4h): Positioning workshop - Draft positioning statement: \"For [TARGET], who [PROBLEM], our product [SOLUTION], unlike [ALTERNATIVE]\" - Refine value proposition with quantified benefits - Identify 3 key differentiators (vs. each alternative) - Test messaging clarity: Can someone outside your team understand it? - Output: Positioning statement + messaging framework (1 page) Week 1 Outputs: - GTM Canvas with confidence scores - Competitive matrix (you vs. 3 alternatives) - Positioning statement and messaging framework - Target prospect list (100 companies matching ICP) Week 2: Customer Validation & ICP Refinement Day 1-2: Interview Preparation (8 hours) - Monday Morning (4h): Build target prospect list - Identify 50 companies matching your TARGET profile - Prioritize by fit score (firmographic, behavioral, psychographic alignment) - Research each company: pain signals, recent news, tech stack, decision makers - Output: Prioritized prospect list (50 companies with research notes) - Monday Afternoon (4h): Create interview materials - Draft interview script (15-20 minute conversation): - \"Tell me about [problem we think they have]\" (validate problem urgency) - \"How do you solve this today?\" (understand alternatives + switching cost) - \"What would make a solution worth paying for?\" (validate value prop) - \"How do you evaluate and buy tools like this?\" (validate channel fit) - \"What would you expect pricing to be?\" (validate pricing assumptions) - Prepare tracking spreadsheet: - Columns: Prospect name, company, role, problem confirmed (Y/N/Partial), current solution, interest level (High/Med/Low), pricing feedback, ICP fit score (1-10) - Output: Interview script + tracking spreadsheet Day 3-5: Customer Interviews (20+ hours, 4 interviews per day) - Tuesday-Thursday (6-7h per day): Execute 20 customer interviews - Outreach: Personalized emails/LinkedIn messages (\"Can I get 20 minutes of feedback on [problem area]?\") - Schedule: 4 interviews per day (15-20 min each + 10 min for notes) - During interview: Follow script, probe for specifics, avoid pitching product - After interview: Score ICP fit (1-10), note key quotes, identify patterns - Output: 20 completed interviews with detailed notes Week 2 Outputs: - 20 customer interviews completed - Interview synthesis: % who confirmed urgent problem, common objections, pricing range - ICP refinement: Patterns in \"high interest\" vs \"low interest\" prospects - Updated GTM Canvas based on validation learnings Decision review #1 (End of Week 2): Problem and evidence review Illustrative review prompts (not universal GO criteria): - A locally defined share of the interviewed or otherwise eligible population supports urgency under a documented coding rule; the percentage shown in the earlier draft was illustrative, not a universal threshold. - A locally defined share expresses interest under a documented sampling and interpretation rule; stated interest is not purchase or causal evidence. - Pricing feedback is consistent with the defined value, contribution, cash, fairness, and service-cost scenario; willingness to pay remains a hypothesis. - Clear pattern emerges in ICP (you can describe \"who succeeds best\") Possible review or stop signals (define locally): - If the local urgency evidence rule is not met → Revisit the PROBLEM definition in the GTM Canvas. - If the local interest evidence rule is not met → Revisit the VALUE PROP; stated interest alone is not demand evidence. - Pricing feedback too low → Rethink pricing model or target different ICP - No clear ICP pattern → Target too broad; need to narrow Contingency if the local evidence rule is not met: Pause the launch, revise the ICP or value proposition, and set the next evidence review from the decision's risk and access constraints. Proceed only with accountable approval: Move to Phase 2 (ICP Deep Dive & Positioning) when the locally defined evidence, customer-outcome, capacity, cash, and legal controls are adequate. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-operating-template-phase-2-icp-deep-dive-positioning-weeks-3-4", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Operating-template Phase 2: ICP Deep Dive & Positioning (Weeks 3-4)", "headingId": "chapter-14-go-to-market-strategy-operating-template-phase-2-icp-deep-dive-positioning-weeks-3-4", "url": "#chapter-14-go-to-market-strategy-operating-template-phase-2-icp-deep-dive-positioning-weeks-3-4", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 3: ICP Segmentation & Target Account List Day 1-2: ICP Profile Development (16 hours) - Monday Morning (4h): Analyze interview patterns - Review all 20 interviews and identify characteristics of \"high interest\" prospects: - Firmographic: Industry, company size, revenue, geography, growth stage - Behavioral: Tech stack, process maturity, pain urgency, buying cycle - Psychographic: Growth mindset, technology affinity, decision style - Calculate correlation: Which characteristics predict high interest? - Output: ICP dimensions with weights (which matter most?) - Monday Afternoon (4h): Create ICP scoring framework - Define 8-10 ICP criteria with point values (e.g., \"Series A-C funded\" = 2 points, \"Uses Salesforce\" = 1 point) - Score all 20 interviewed companies using framework - Validate: Do high-scoring companies match \"high interest\" prospects? (If not, revise criteria) - Output: ICP scoring framework (8-10 criteria, point system) - Tuesday Morning (4h): Build target account list - Use LinkedIn Sales Navigator, Crunchbase, or industry databases - Identify 200 companies matching ICP criteria - Score each company using ICP framework - Segment into tiers: Tier 1 (ICP score 8-10, top 50 companies), Tier 2 (score 6-7, next 100), Tier 3 (score 4-5, remaining 50) - Output: Target account list (200 companies, scored and tiered) - Tuesday Afternoon (4h): Anti-ICP definition - Identify characteristics of \"low interest\" prospects from interviews - Define Anti-ICP: Who to avoid? (e.g., \"Nonprofits with <$1M budget, need heavy customization\") - Document why: Low price potential, high support cost, poor retention risk - Output: Anti-ICP profile (who to disqualify) Day 3-5: Segmentation Analysis (16 hours) - Wednesday Morning (4h): Identify potential customer segments - Review ICP data: Do multiple distinct segments emerge? (e.g., \"Early-stage SaaS\" vs \"Growth-stage SaaS\") - For each potential segment (2-4 segments max): - Size: How many companies fit this profile? - Avg deal size: Based on pricing feedback - Win rate estimate: Based on interview interest levels - CAC estimate: Based on channel requirements - LTV estimate: Pricing × estimated retention - Output: Segmentation analysis (2-4 segments with economics) - Wednesday Afternoon (4h): Select primary segment - Compare segments on: Market size, win rate, LTV:CAC ratio, sales cycle - Pick primary segment: Best economics + best product fit + fastest time to revenue - Document rationale: Why this segment first? - Identify expansion path: Which segment next? (After primary is proven) - Output: Primary segment selection with expansion roadmap - Thursday-Friday (8h): Tier 1 account deep research - For top 50 Tier 1 accounts: - Identify decision maker (name, title, LinkedIn profile) - Research pain signals (recent hiring, funding, tech stack changes) - Find connection path (mutual contacts, investors, advisors) - Draft personalized outreach angle (specific to their situation) - Output: Tier 1 account research dossier (50 companies with personalized notes) Week 3 Outputs: - ICP profile (1 page) with scoring framework - Target account list (200 companies, scored and tiered) - Anti-ICP profile (disqualification criteria) - Segmentation analysis with primary segment selected - Tier 1 account research dossier (50 companies) Week 4: Messaging & Positioning Validation Day 1-2: Messaging Framework Development (16 hours) - Monday Morning (4h): Homepage messaging - Headline (7 words or less): Core benefit in plain language - Subheadline (1 sentence): Value proposition with quantified outcome - 3 key benefits: Specific outcomes customer achieves (with numbers if possible) - Social proof: Customer testimonials or case example snippets (if available from interviews) - Call-to-action: What do you want prospect to do? (Book demo, start trial, etc.) - Output: Homepage messaging framework - Monday Afternoon (4h): Sales messaging - Elevator pitch (30 seconds): Who you help, what problem you solve, unique approach - Discovery questions: 5-7 questions to qualify prospect and uncover pain - Value prop by persona: How benefit differs for CEO vs VP vs Manager - ROI calculator: Simple model to quantify customer savings/gains - Output: Sales messaging toolkit - Tuesday Morning (4h): Objection handling framework - Review interview feedback: What concerns/objections came up repeatedly? - For each objection, draft response: - Acknowledge: \"I understand the concern about [X]\" - Reframe: \"Here's how we think about that...\" - Proof: Customer testimonial, data, or case example - Common objections: Price too high, switching cost, competitor comparison, \"not urgent\" - Output: Objection handling guide (5-8 common objections with responses) - Tuesday Afternoon (4h): Competitive positioning - For each top alternative (competitor, DIY, do nothing): - Draft \"Unlike [alternative], we [specific benefit]\" statement - Quantify difference: \"3 days vs 3 weeks,\" \"$500K savings vs $100K\" - Prepare comparison matrix: Feature-by-feature or outcome-by-outcome - Output: Competitive positioning statements + comparison matrices Day 3-5: Messaging Validation (16 hours) - Wednesday-Thursday (12h): Validation interviews - Reach out to 5-10 interviewed customers (high interest prospects) - Share positioning/messaging: \"Does this resonate? Is it clear? Compelling?\" - Test headline, value prop, key benefits, pricing messaging - A/B test variants: Try 2 different headlines or value props, see which resonates more - Iterate based on feedback: Clarity issues? Jargon? Missing key benefit? - Output: Validated messaging framework (iterated based on feedback) - Friday (4h): Create messaging assets - 1-pager: Overview of product, problem, solution, benefits, pricing (sales leave-behind) - Email templates: Outreach, follow-up, demo invite (personalized but repeatable) - Pitch deck (5 slides): Problem, solution, differentiation, pricing, case example/testimonial - Output: Core messaging assets ready for launch Week 4 Outputs: - Homepage messaging framework (headline, subheadline, benefits, CTA) - Sales messaging toolkit (pitch, discovery questions, ROI calculator) - Objection handling guide (5-8 objections with responses) - Competitive positioning statements - Messaging assets (1-pager, email templates, pitch deck) Decision review #2 (End of Week 4): Messaging resonance Illustrative review prompts (not universal GO criteria): - A locally defined share of validation participants says messaging is clear and compelling under a documented sampling and coding rule; the percentage is illustrative, not a universal threshold. - Value proposition resonates (prospects immediately understand benefit) - Competitive positioning is defensible (you can articulate unique value vs alternatives) - Messaging assets are ready (1-pager, email templates, pitch deck) Possible review or stop signals (define locally): - Messaging confusing or generic → Iterate on clarity, specificity - Value prop doesn't resonate → Revisit customer pain points, quantify benefits more clearly - Can't differentiate from alternatives → Identify unique angle or narrow ICP further Contingency if the local evidence rule is not met: Iterate the message with additional customer feedback and reset the launch timing from the evidence and operating constraints. Proceed only with accountable approval: Move to Phase 3 (Channel & Pricing Strategy) when the locally defined evidence and controls are adequate. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-operating-template-phase-3-channel-selection-pricing-weeks-5-6", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Operating-template Phase 3: Channel Selection & Pricing (Weeks 5-6)", "headingId": "chapter-14-go-to-market-strategy-operating-template-phase-3-channel-selection-pricing-weeks-5-6", "url": "#chapter-14-go-to-market-strategy-operating-template-phase-3-channel-selection-pricing-weeks-5-6", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 5: Channel Strategy & Economics Day 1-2: Channel Evaluation (16 hours) - Monday Morning (4h): Evaluate potential channels - Based on ICP and interviews, assess 3-5 channels: - Direct sales: # reps needed, cost per rep, ramp time, CAC estimate - Inside sales: # SDRs + AEs, cost, productivity per rep, CAC estimate - Self-serve: Website build cost, ad spend, conversion rate estimate, CAC estimate - Partnerships: Identify 10 potential partners (fit, reach, revenue share) - Content marketing: Content team cost, SEO timeline, organic lead volume estimate - For each channel, model: - Upfront investment (time + money for first 90 days) - CAC estimate (based on industry reference points or similar companies) - Timeline to first customer - Scalability potential (can this get to 100 customers? 1,000?) - Output: Channel evaluation matrix (3-5 channels with economics) - Monday Afternoon (4h): Interview insights on buying behavior - Review customer interviews: \"How do you typically evaluate and buy tools like this?\" - Patterns to identify: - Self-serve indicators: \"We just try it, if it works we buy\" - Inside sales indicators: \"We need a demo and ROI analysis\" - Direct sales indicators: \"Multiple stakeholders, formal evaluation process\" - Match buying behavior to channel type - Output: Buying behavior analysis (which channel fits customer expectations?) - Tuesday Morning (4h): Channel economics modeling - Build spreadsheet model for top 2 channels: - Inputs: Channel investment, expected conversion rates, deal size, sales cycle - Outputs: CAC, number of customers in 90 days, payback period - Compare channels on: CAC, speed to revenue, LTV:CAC ratio - Sensitivity analysis: What if conversion rate is 50 percent worse? CAC doubles? - Output: Channel economics model (comparing top 2 channels) - Tuesday Afternoon (4h): Select primary channel(s) - Criteria: Best LTV:CAC ratio + fastest time to revenue + team capability - Pick 1-2 primary channels (not 5 - focus is critical) - Document rationale: Why this channel? What are the risks? - Create 90-day channel plan: - Month 1: Activities, budget, expected leads/customers - Month 2: Scale plan (if Month 1 works) - Month 3: Optimization (improve conversion, reduce CAC) - Output: Primary channel selection + 90-day plan Day 3-5: Partnership Development (if relevant) (16 hours) - Wednesday Morning (4h): Identify target partners (if partnerships is a channel) - Criteria: Access to your ICP, complementary product, no direct competition - Evaluate 10 potential partners: - Customer overlap: Do they sell to your ICP? - Reach: How many customers do they have? - Engagement: Active community, events, content? - Feasibility: Will they partner with early-stage startup? - Prioritize top 5 partners - Output: Target partner list (5 partners with fit scores) - Wednesday Afternoon-Friday (12h): Partnership outreach & proposals - Draft partnership proposal (1-pager): - Value to partner: How does partnering benefit them? (revenue share, customer value, co-marketing) - Economics: Revenue split, referral fees, co-marketing investment - Timeline: Pilot period (90 days), success metrics, expansion plan - Outreach to top 5 partners: Email + LinkedIn + mutual intro (if available) - Goal: Book exploratory calls with 3-5 partners - Initial conversations: Validate interest, discuss terms, explore pilot - Output: 3-5 partnership exploratory calls booked + draft agreements Week 5 Outputs: - Channel evaluation matrix (3-5 channels assessed) - Channel economics model (top 2 channels compared) - Primary channel selection + 90-day plan - Partnership target list (if relevant) + outreach initiated Week 6: Pricing Model & Unit Economics Day 1-2: Pricing Model Selection (16 hours) - Monday Morning (4h): Review pricing feedback - Analyze interview data: What did customers say about pricing? - Acceptable range: $X to $Y (based on \"what would you expect to pay?\") - Pricing model preferences: Did they mention per-user, per-transaction, flat fee? - Budget constraints: What's typical budget for this type of tool? - Output: Pricing feedback synthesis - Monday Afternoon (4h): Evaluate pricing models (Framework #5) - Consider 3-4 pricing models: - Per-user/seat: $X per user per month (e.g., $99/user/month) - Tiered: Basic ($X), Pro ($Y), Enterprise ($Z) with feature differentiation - Value-based: % of savings or revenue generated (e.g., 20 percent of $500K savings = $100K/year) - Usage-based: Pay per API call, transaction, GB processed, etc. - Hybrid: Base fee + usage overage (e.g., $99/month + $0.10 per API call above 10K) - For each model, assess: - Customer preference: Does this match how they think about value? - Revenue predictability: Can you forecast monthly/annual revenue? - Sales complexity: Easy to explain and sell? - Output: Pricing model comparison (3-4 models evaluated) - Tuesday Morning (4h): Unit economics modeling - Build detailed spreadsheet model: - Inputs: Pricing, CAC (by channel), monthly churn rate, gross margin, sales cycle length - Outputs: Monthly recurring revenue (MRR), annual recurring revenue (ARR), LTV, CAC, LTV:CAC ratio, payback period, break-even timeline - Model 3 scenarios: - Base case: Realistic assumptions based on interviews and reference points - Optimistic: 20 percent better on pricing, conversion, retention - Pessimistic: 20 percent worse on all metrics - Validate: Does the base-case contribution and payback scenario meet the locally approved threshold, with uncertainty and cash timing stated? - Output: Unit economics model (3 scenarios) - Tuesday Afternoon (4h): Price point selection - Based on model, select initial pricing: - If per-user: $X/user/month - If tiered: Define 3 tiers with feature breakdown - If value-based: % of customer savings/revenue + minimum fee - If usage-based: Price per unit + committed tiers - Justify pricing: ROI for customer (they save/earn $Y, we charge $X) - Plan for iteration: \"We'll test this price, adjust after 10 customers if needed\" - Output: Pricing decision (model + price point) Day 3-5: Pricing Page & Sales Toolkit (16 hours) - Wednesday Morning (4h): Create pricing page - For each tier/plan: - Plan name (Basic, Pro, Enterprise) - Price point ($99/month, $299/month, Custom) - Key features included (3-5 most important) - CTA (Start trial, Book demo, Contact sales) - Add: FAQ section (common pricing questions) - Add: ROI calculator or savings estimate - Output: Pricing page copy (ready for website) - Wednesday Afternoon (4h): Sales pricing toolkit - Pricing justification: How to explain pricing in sales conversation - Discount policy: When can reps discount? (e.g., annual commitment = 10 percent off, never more than 20 percent discount) - Negotiation guidelines: How to handle \"it's too expensive\" objection - Contract terms: Month-to-month vs annual, payment terms, cancellation policy - Output: Sales pricing guide - Thursday-Friday (8h): Pricing validation - Share pricing with 5 high-interest prospects from interviews - Ask: \"Does this pricing make sense? Is it in line with value?\" - Test objection handling: If they say \"too expensive,\" test your response - Iterate if needed: Adjust price point or packaging based on feedback - Output: Validated pricing (adjusted based on feedback if necessary) Week 6 Outputs: - Pricing model selected (per-user, tiered, value-based, usage, hybrid) - Unit economics model (3 scenarios: base, optimistic, pessimistic) - Pricing decision (specific price points and tiers) - Pricing page copy (ready for website) - Sales pricing guide (justification, discounts, objection handling) Decision review #3 (End of Week 6): Unit-economics review Illustrative review prompts (not universal GO criteria): - Base-case contribution and payback scenario meets the locally approved threshold, with margin, service cost, cash timing, and uncertainty stated. - Payback period is acceptable for the venture's liquidity, risk, customer, and operating context; no universal month threshold applies. - Pricing resonates with validation customers (no major objections) - Channel strategy yields a realistic path to the locally defined evidence and customer-outcome objective within the approved cash and capacity window. Possible review or stop signals (define locally): - Contribution below the approved threshold → Revisit pricing, channel, service cost, retention, or the target segment. - Payback outside the approved liquidity window → Revisit pricing, cash terms, retention, channel, or exposure before scaling. - Pricing objections → Lower price OR better justify value (improve ROI articulation) Contingency if the local evidence rule is not met: Revise pricing or channel strategy, re-model contribution and cash, and delay or reduce exposure until the responsible owner approves the economics. Proceed only with accountable approval: Move to Phase 4 (Launch Preparation & Execution) when the local contribution, cash, capacity, customer-outcome, and governance rules are satisfied. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-operating-template-phase-4-launch-preparation-week-7-8", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Operating-template Phase 4: Launch Preparation (Week 7-8)", "headingId": "chapter-14-go-to-market-strategy-operating-template-phase-4-launch-preparation-week-7-8", "url": "#chapter-14-go-to-market-strategy-operating-template-phase-4-launch-preparation-week-7-8", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 7: Marketing Assets & Sales Process Day 1-2: Website/Landing Page (16 hours) - Monday-Tuesday (16h): Build launch landing page - Core sections: - Hero: Headline, subheadline, CTA, hero image/screenshot - Problem: Describe customer pain (quantified) - Solution: How your product solves it (key features + benefits) - Differentiation: Why you vs alternatives (comparison or unique approach) - Social proof: Customer testimonials, logos, case examples (if available) - Pricing: Clear pricing table or \"Contact sales\" CTA - FAQ: 5-10 common questions answered - Technical: Use Webflow, WordPress, Framer, or similar (no-code preferred for speed) - Mobile-responsive, fast load time, clear CTAs - Output: Live landing page (ready to drive traffic) Day 3-5: Sales Assets & Process (16 hours) - Wednesday Morning (4h): Sales deck (5 slides) - Slide 1: Problem (customer pain with data/quotes) - Slide 2: Solution (your product, how it works) - Slide 3: Differentiation (you vs alternatives) - Slide 4: Pricing & ROI (tiers, ROI calculator, payback period) - Slide 5: Social proof (testimonials, case examples, logos) - Keep it visual, minimal text, clear narrative - Output: Sales pitch deck (PDF + editable version) - Wednesday Afternoon (4h): Product demo preparation - Recorded demo: 5-10 minute walkthrough of product (Loom or similar) - Live demo script: Step-by-step flow for live calls - Demo environment: Sandbox account with realistic data - Demo customization: How to tailor demo to prospect's use case - Output: Demo assets (recorded demo + live demo script) - Thursday Morning (4h): Sales process documentation - Define sales stages: - Stage 1: Outreach (email, LinkedIn) - Stage 2: Discovery call (qualify, understand pain) - Stage 3: Demo (show solution, tailor to their use case) - Stage 4: Proposal (send pricing, ROI, terms) - Stage 5: Negotiation (handle objections, finalize terms) - Stage 6: Close (sign contract, onboard) - For each stage: - Objective: What are you trying to achieve? - Duration: How long does this stage typically take? - Exit criteria: When do you move to next stage? - Disqualification: When do you disqualify prospect? - Output: Sales process playbook (6 stages documented) - Thursday Afternoon-Friday (8h): CRM setup & email sequences - Set up CRM: HubSpot, Pipedrive, or spreadsheet (track leads through funnel) - Create email sequences: - Outreach sequence: Initial email + 2 follow-ups - Post-demo sequence: Thank you + proposal + follow-ups - Nurture sequence: For \"not ready now\" prospects - Templates: Personalized but repeatable (merge fields for company, name, pain point) - Output: CRM configured + email sequences ready Week 7 Outputs: - Live landing page (hero, problem, solution, pricing, CTAs) - Sales pitch deck (5 slides) - Product demo assets (recorded demo + live script) - Sales process playbook (6 stages with objectives, duration, exit criteria) - CRM setup + email sequences Week 8: Launch Coordination & Partnerships Day 1-2: Launch Campaign Assets (16 hours) - Monday Morning (4h): Press & media outreach - Identify 10-15 journalists/bloggers covering your industry - Draft press release: Who, what, why now, customer benefit, quote from founder - Personalized pitches: Why this journalist's audience cares - Schedule outreach: 1 week before launch (embargoed), launch day (public) - Output: Press list + press release + pitch emails - Monday Afternoon (4h): Social media launch plan - Pre-write social posts for launch day: - LinkedIn: Founder post (personal story, why we built this, CTA) - Twitter: Product launch thread (problem, solution, features, pricing, link) - Company accounts: Coordinated announcement - Prepare assets: Screenshots, GIFs, short demo video - Identify amplifiers: Advisors, early customers, partners (ask them to share) - Schedule posts: Coordinate timing (all go live at same time) - Output: Social media launch plan + pre-written posts - Tuesday Morning (4h): Email launch sequence - Segment email list: - Warm leads: Interviewed customers, high interest prospects - Waitlist: Anyone who signed up for early access - Network: Friends, family, advisors (ask for intros/shares) - Create email sequence: - Pre-launch (1 week before): \"We're launching soon, here's what to expect\" - Launch day: \"We're live! Here's how it works, special launch offer\" - Post-launch (1 week after): \"Early results, case example, last chance for launch offer\" - Output: Email launch sequence (3 emails, segmented lists) - Tuesday Afternoon (4h): Launch day operations plan - Assign responsibilities: - Who monitors product stability? (error rates, performance) - Who handles customer support? (email, chat, social DMs) - Who manages social amplification? (retweets, reshares, engagement) - Who tracks metrics? (signups, demos booked, revenue) - Set up monitoring: - Product analytics: Track signups, feature usage, errors - Marketing analytics: Track website traffic, email opens/clicks, social reach - Sales pipeline: Track demos booked, proposals sent, deals closed - Contingency plan: What if servers crash? What if no one signs up? - Output: Launch day operations plan (roles, monitoring, contingencies) Day 3-5: Partnership Finalization & Target Outreach (16 hours) - Wednesday (8h): Finalize partnership agreements (if relevant) - Negotiate terms with 1-2 partners: - Revenue share or referral fee - Co-marketing commitments (webinar, email to their list, blog post) - Integration or product collaboration - Success metrics (# referrals, revenue target) - Use counsel-approved agreement or term-sheet templates; an LOI or MOU can create binding obligations and is not a substitute for legal review - Coordinate launch timing: Partner announcements on launch day - Output: 1-2 partnership agreements signed - Thursday-Friday (8h): Tier 1 target outreach preparation - Review Tier 1 account list (top 50 companies) - For each account: - Verify decision maker contact info (email, LinkedIn) - Draft personalized outreach email (reference their specific pain, recent news, mutual connection) - Plan outreach timing: Launch week - Set outreach targets: - Week 8: 20 personalized emails sent - Week 9: 30 more emails + follow-ups - Output: Tier 1 outreach plan (50 personalized emails drafted, send schedule) Week 8 Outputs: - Press release + media outreach list (10-15 journalists) - Social media launch plan (posts pre-written, amplifiers identified) - Email launch sequence (3 emails for warm leads, waitlist, network) - Launch day operations plan (roles, monitoring, contingencies) - Partnership agreements signed (1-2 partners) - Tier 1 outreach plan (50 personalized emails ready) Decision review #4 (End of Week 8): Launch readiness Illustrative review prompts (not universal GO criteria): - Landing page is live and functional (loads fast, CTAs work) - Sales assets complete (deck, demo, email sequences) - Launch campaign ready (press, social, email pre-written) - Product is stable (QA tested, no critical bugs) - Team is aligned (everyone knows their launch day role) Possible review or stop signals (define locally): - Landing page not ready → Delay launch 1 week, prioritize page completion - Critical product bugs → Fix bugs before launch (unstable product kills momentum) - Sales process unclear → Document process, test with mock sales calls Contingency if the local evidence rule is not met: Delay or narrow the launch and use the available time to close critical evidence, product, service, or approval gaps. Proceed only with accountable approval: Move to Phase 5 (Launch & Early Traction) when product, service, customer, evidence, capacity, and governance controls are ready. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-operating-template-phase-5-launch-optimization-weeks-9-10", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Operating-template Phase 5: Launch & Optimization (Weeks 9-10)", "headingId": "chapter-14-go-to-market-strategy-operating-template-phase-5-launch-optimization-weeks-9-10", "url": "#chapter-14-go-to-market-strategy-operating-template-phase-5-launch-optimization-weeks-9-10", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 9: Launch Execution Day 1-3: Launch Week (24 hours) - Monday (Pre-launch Day, 8h): - Final QA: Test every feature as new customer (signup, onboarding, core workflow, payment) - Send pre-launch email to waitlist: \"We launch tomorrow, here's what to expect\" - Confirm partnerships: Partners ready to announce on launch day - Brief team: Final check on roles, responsibilities, communication plan - Output: Everything ready for launch day - Tuesday (Launch Day, 12h): - 9am: Launch announcement goes live - Publish landing page (if not already live) - Send launch email to warm leads, waitlist, network - Post social announcements (LinkedIn, Twitter, company accounts) - Reach out to press (send press release, personalized pitches) - Partner announcements (coordinated timing) - 9am-6pm: Monitor and respond - Track signups against the locally defined qualified-reach and learning objective for launch day. - Respond to inquiries in real-time (<1 hour response time) - Engage on social (reply to comments, reshare mentions) - Monitor product stability (check error logs, performance) - 6pm-9pm: Celebrate and debrief - Share launch day metrics with team (signups, traffic, social reach) - Identify what worked, what didn't - Plan Day 2 activities (follow-ups, momentum maintenance) - Output: Launch executed, metrics tracked, team debriefed - Wednesday (Post-launch Day 1, 4h): - Follow up with launch day signups: Welcome email, onboarding support - Send thank you notes to amplifiers (partners, advisors who shared) - Publish \"launch recap\" post: Metrics, wins, learnings (builds momentum) - Continue Tier 1 outreach: 10 personalized emails to target accounts - Output: Launch momentum maintained Day 4-5: Early Customer Engagement (16 hours) - Thursday-Friday (16h): Convert interest to demos - Reach out to all signups: Book discovery calls or demos - Prioritize high-fit prospects (Tier 1 accounts, high ICP scores) - Conduct 5-10 discovery calls/demos: - Discovery: Qualify prospect, understand pain, assess fit - Demo: Show product, tailor to their use case, handle objections - Next steps: Send proposal or offer trial - Track conversion: Signup → Demo → Proposal → Close - Output: 5-10 demos completed, proposals sent Week 9 Outputs: - Launch executed (press, social, email sent) - Launch day metrics (signups, traffic, social reach) - Qualified reach and signups measured against the locally defined launch objective. - 5-10 demos completed - Proposals sent to high-fit prospects Week 10: Optimization & Early Revenue Day 1-2: Close First Customers (16 hours) - Monday-Tuesday (16h): Sales follow-up & closing - Follow up on proposals sent in Week 9: - Answer questions, handle objections - Negotiate terms (within discount policy limits) - Send contract, process payment - Onboard customers (setup, training, success plan) - Goal: Close a locally defined amount of paid evidence by the end of Week 10 - Track: Close rate (proposals → closed customers) - Output: Paid evidence recorded against the locally defined customer and quality objective. Day 3-4: Metrics Analysis & Funnel Optimization (16 hours) - Wednesday Morning (4h): Measure funnel conversion rates - Calculate conversion at each stage (Framework #3): - Awareness: How many leads generated? (launch signups + outreach responses) - Consideration: % who booked demo - Proposal: % of demos that led to proposal - Close: % of proposals that closed - Identify bottlenecks: Where are prospects dropping off? - Output: Funnel metrics dashboard - Wednesday Afternoon (4h): Calculate unit economics (actual) - Actual CAC: Launch spend (ads, tools, time) / customers acquired - Early value scenario: Do not call pricing × estimated retention actual LTV; report the contribution basis, retention evidence, service cost, cohort, uncertainty, and cash timing. - Compare to model: Actual vs projected CAC and LTV - Identify variance: Why is actual different from model? - Output: Actual unit economics vs model - Thursday (8h): Customer feedback & iteration - Interview first 5-10 customers: - What almost prevented you from buying? - What convinced you to buy? - What's missing in the product? - Would you refer us? Why or why not? - Identify patterns: Common objections, feature requests, pricing feedback - Prioritize 2-3 quick wins: Changes that would improve conversion or retention - Output: Customer feedback synthesis + iteration priorities Day 5: Playbook Documentation & Scale Planning (8 hours) - Friday Morning (4h): Document GTM playbook - What worked: - Which channel drove most qualified leads? - Which messaging resonated best? - What objection handling worked? - What didn't work: - Which channels underperformed? - Where did prospects drop off? - What objections couldn't we overcome? - Repeatable process: - Step-by-step: How to acquire next customer using what worked - Templates: Email, pitch, demo script that converted - Metrics: Reference Points for \"good\" conversion at each stage - Output: GTM playbook (1-2 page doc) - Friday Afternoon (4h): Plan Weeks 11-14 (next 30 days) - Set Month 2 goals: - Revenue target: $X MRR or ARR - Customer target: Y new customers - Funnel target: Z demos, proposals - Identify constraints: - Team capacity: Can founders handle sales volume? - Product readiness: Are there critical features needed? - Budget: Do we need more ad spend or tools? - Plan next phase: - If working: Scale what's working (more of same channel, outreach) - If not working: Iterate (change messaging, try different channel, adjust pricing) - Output: Month 2 plan (goals, activities, budget) Week 10 Outputs: - Paid evidence recorded against the locally defined customer and quality objective. - Funnel metrics dashboard (conversion rates at each stage) - Actual unit economics (CAC, LTV, LTV:CAC ratio) - Customer feedback synthesis - GTM playbook documented - Month 2 scale plan Decision review #5 (End of Week 10): GTM evidence and scale review Illustrative review prompts (not universal GO criteria): - A locally defined amount and quality of paid evidence supports the next decision; customer count alone does not validate GTM. - Contribution and payback meet the locally approved threshold, or the owner documents a bounded, evidence-backed path with downside controls. - Repeatable process documented (playbook shows how to replicate success) - Positive customer feedback under a defined measure; a single 0–10 recommendation rating is not itself NPS Possible review or stop signals (define locally): - Insufficient paid evidence → Extend or redesign the test; do not pursue a universal customer-count target. - Contribution below the approved threshold with no credible fix → Revisit pricing, channel, service cost, segment, or exposure. - No repeatable process → Continue experimenting, document what works - Negative customer feedback → Fix product issues before scaling (retention risk) Contingency if the local evidence rule is not met: - If paid evidence is insufficient: Extend or redesign the test from the approved evidence and capacity plan. - If unit economics broken: Pause scaling, fix pricing or channel strategy - If churn is high: Fix product/onboarding before acquiring more customers Proceed only with accountable approval: Increase exposure gradually only when the locally defined incremental-economics, capacity, retention, customer-outcome, and governance rules are satisfied. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-resource-requirements", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Resource Requirements", "headingId": "chapter-14-go-to-market-strategy-resource-requirements", "url": "#chapter-14-go-to-market-strategy-resource-requirements", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Human Resources: Founding Team (Weeks 1-10): - Founder/CEO: 50-60h/week (GTM strategy, customer interviews, partnerships, sales) - Co-founder/CTO (or technical lead): 20-30h/week (product stability, demo prep, analytics setup, tech integration) - Marketing/Sales (if exists): 40-50h/week (messaging, launch campaign, sales execution) - If no dedicated marketing/sales, founder takes this on (60-70h/week total) External Resources (Optional): - Freelance designer: 10-20h (landing page design, pitch deck design) - Copywriter: 5-10h (messaging polish, email copywriting) - Advisor/Mentor: 2-4h/month (GTM strategy review, objection handling coaching) Financial Resources: The following budget is a constructed worksheet, not a current price guide. Replace every amount with dated quotes, internal fully loaded costs, applicable taxes, compliance needs, and a contingency justified by the actual plan. Weeks 1-2 (Strategy Development): $500-$1,500 - Tools: LinkedIn Sales Navigator ($100/month), questionnaire tools ($50), misc research tools ($200-500) Weeks 3-4 (ICP & Messaging): $500-$1,000 - Tools: CRM setup ($100-200), design assets ($300-500), misc tools ($100-300) Weeks 5-6 (Channel & Pricing): $1,000-$3,000 - Freelance help: Designer for landing page ($500-1,500) - Tools: Website hosting ($20-50), email tool ($50-100) - Partnership development: Travel or meeting costs ($200-500) - Misc: $200-500 Weeks 7-8 (Launch Prep): $2,000-$5,000 - Website/landing page: Build or template ($500-2,000) - Marketing tools: Email platform, analytics, CRM ($200-500) - Freelance: Copywriter, designer, video editor ($500-1,500) - Press outreach: PR service (optional, $500-1,000) - Misc: $300-1,000 Weeks 9-10 (Launch & Traction): $3,000-$10,000 - Paid ads (if using): Google Ads, LinkedIn Ads ($1,000-5,000) - Partnership costs: Revenue share, co-marketing investment ($500-2,000) - Sales tools: Contracts, payment processing setup ($200-500) - Customer onboarding: Tools, support, misc ($300-1,000) - Misc/buffer: $1,000-1,500 Total Budget (10 Weeks): $7,000-$20,500 - Constructed Scenario A: $7,000-10,000 (minimal paid ads, DIY landing page, no freelancers) - Constructed Scenario B: $12,000-15,000 (moderate paid ads, freelance help, selected tools) - Constructed Scenario C: $15,000-20,500 (higher paid-ad exposure, additional tools, PR support) ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-red-flags-warning-signals", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flags & Warning Signals", "headingId": "chapter-14-go-to-market-strategy-red-flags-warning-signals", "url": "#chapter-14-go-to-market-strategy-red-flags-warning-signals", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 1-2 Red Flags: - Local urgency evidence rule is not met → Revisit the PROBLEM definition, sampling, coding, or ICP before scaling. - Customers can't articulate the problem clearly → You're solving a \"nice to have,\" not urgent pain - Wide variance in ICP fit scores → Target is too broad; need to narrow to specific segment Week 3-4 Red Flags: - Messaging doesn't resonate in validation → Value prop is unclear or not compelling; iterate on specificity and quantified benefits - Can't differentiate from alternatives → Competitive positioning is weak; find unique angle or narrow to underserved niche - ICP scoring doesn't predict interest → Scoring criteria are wrong; reassess which firmographic/behavioral traits matter Week 5-6 Red Flags: - Contribution below the approved threshold in the base case → Revisit pricing, channel, service cost, retention, or exposure. - Payback outside the approved liquidity window → Revisit pricing, cash terms, retention, channel, or exposure before scaling. - Channel doesn't match customer buying behavior → Mismatch (e.g., self-serve for complex product); switch channel strategy Week 7-8 Red Flags: - Landing page unclear or confusing → Messaging not distilled enough; simplify value prop and CTAs - Partnership negotiations stall → Partners see no value; reassess partnership value prop or find different partners - No clear sales process → Founders don't know how to sell; need to document discovery, demo, close steps Week 9-10 Red Flags: - Launch reach below the locally defined evidence level → Diagnose awareness, distribution, consent, targeting, message, or product fit. - Demo booking below the locally defined evidence level → Diagnose qualification, customer expectations, accessibility, or message/product alignment. - High drop-off after demo → Product doesn't match expectations, or objections not handled; improve demo or product - Paid evidence below the locally defined decision level by the review date → Diagnose awareness, conversion, pricing, product, service, or access. - Early churn or harm above the locally defined guardrail → Pause or narrow acquisition, investigate causes, and remedy product or onboarding issues before scaling. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-contingency-triggers", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Contingency Triggers", "headingId": "chapter-14-go-to-market-strategy-contingency-triggers", "url": "#chapter-14-go-to-market-strategy-contingency-triggers", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Trigger 1: Problem-Market Fit Failure (Week 2) - Condition: The locally defined urgency evidence rule is not met. - Action: Pause the GTM launch, revise the ICP or problem statement, and set the next evidence review from risk, access, and capacity. - Timeline impact: Re-estimate from the evidence plan; no fixed extension is universal. Trigger 2: Unit Economics Failure (Week 6) - Condition: Contribution or payback is below the approved threshold with no credible, bounded improvement path. - Action: Revise pricing, channel, service cost, retention, segment, or exposure; re-model economics before proceeding. - Timeline impact: Re-estimate from the remediation and measurement plan. Trigger 3: Launch Failure (Week 9) - Condition: Launch reach or qualified engagement is below the locally defined evidence level. - Action: Diagnose awareness, consent, message, distribution, access, product, and service readiness before relaunching. - Timeline impact: Re-estimate from the revised launch plan. Trigger 4: Conversion Failure (Week 10) - Condition: Paid evidence is insufficient for the defined decision despite qualified reach. - Action: Deep-dive on the conversion bottleneck, interview lost prospects, and fix objection handling, pricing, product, access, or service gaps before expanding. - Timeline impact: Re-estimate from the evidence and remediation plan. Trigger 5: Early Churn Crisis (Week 10) - Condition: Early churn, non-retention, complaints, or harm exceeds the locally defined guardrail. - Action: Pause or narrow new acquisition, fix product/onboarding issues, interview affected customers, and resume only when the responsible owner approves the evidence and controls. - Timeline impact: Re-estimate from the remediation and validation plan. ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-timeline-variance", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Timeline Variance", "headingId": "chapter-14-go-to-market-strategy-timeline-variance", "url": "#chapter-14-go-to-market-strategy-timeline-variance", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Rapid Mode (6-8 Weeks): - Use when: Product-market fit is validated, clear ICP, experienced founder in GTM - Compress: Combine Weeks 1-2 (GTM Canvas + Interviews in 1 week), Weeks 3-4 (ICP + Messaging in 1 week), Weeks 7-8 (Launch prep in 1 week) - Risk: Less validation, higher chance of GTM missteps - Outcome: Launch in 6 weeks, first customers by Week 7-8 Standard Mode (10 Weeks): - Use when: First-time GTM launch, need validation, moderate urgency - Timeline: As described in this operating manual - Balance: Adequate validation with reasonable speed - Outcome: Launch in Week 9, first customers by Week 10 Thorough Mode (14-16 Weeks): - Use when: Complex product, enterprise sales, need deep customer validation - Expand: +1 week for customer interviews (40 instead of 20), +1 week for messaging validation, +2 weeks for partnership negotiation - Benefit: Higher confidence, better positioning, stronger partnerships - Outcome: Launch in Week 13-15, first customers by Week 14-16 ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-measurement-dashboard", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Measurement Dashboard", "headingId": "chapter-14-go-to-market-strategy-measurement-dashboard", "url": "#chapter-14-go-to-market-strategy-measurement-dashboard", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Weekly Tracker (Weeks 1-10): Table 14.14: Constructed ten-week operating-template tracker. Targets and thresholds are illustrative prompts; set them from the defined decision, cohort, risk, capacity, cash, and approval context. | Week | Key Metric | Target | Actual | Status | |------|-----------|--------|--------|--------| | 1 | GTM Canvas confidence (1-10) | 7+ | | | | 2 | Customer interviews completed | 20 | | | | 2 | Share confirming urgent problem | Local evidence rule | | | | 3 | ICP profile confidence (1-10) | 8+ | | | | 3 | Target accounts identified | 200 | | | | 4 | Messaging validation (% positive) | Local evidence rule | | | | 5 | Primary channel selected | Yes | | | | 6 | Contribution/payback scenario | Approved local threshold | | | | 7 | Landing page live | Yes | | | | 8 | Launch campaign ready | Yes | | | | 9 | Launch day signups | 20-50 | | | | 9 | Demos booked | 5-10 | | | | 10 | Paying customers acquired | 5-10 | | | | 10 | Actual CAC | Compare with approved scenario | | | End-of-Week-10 Milestone Metrics: Customer Acquisition: - Paying customers: Report the locally defined quantity and quality of paid evidence; no universal customer-count gate applies. - Pipeline (qualified leads): 20-30 - Conversion rate (signup → customer): measured against your modeled target Unit Economics: - CAC (actual): Compare with the forecast, explain attribution and inclusion rules, and investigate material variance; no universal SMB or enterprise cutoff applies. - LTV:CAC (estimated): Report the formula, margin basis, cohort, confidence range, and sensitivity cases rather than applying a universal pass threshold. - Payback period: Compare with the approved liquidity and risk window; no universal month threshold applies. GTM Validation: - Repeatable process documented: Yes (playbook exists) - Primary channel validated: CAC known, conversion rates measured - Messaging resonance: strong customer agreement that the value prop was clear and compelling - ICP accuracy: most customers match the ICP profile Product-Market Fit Indicators: - Customer recommendation item: illustrative local range on a 0–10 scale; calculate NPS separately only with the approved instrument and full response distribution - Referral willingness: meaningful share say they would refer - Early retention: strong retained usage after 30 days ---" }, { "id": "chapter-14-go-to-market-strategy::chapter-14-go-to-market-strategy-success-vs-struggling-how-to-know", "kind": "chapter", "itemSlug": "chapter-14-go-to-market-strategy", "itemTitle": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Success vs Struggling: How to Know", "headingId": "chapter-14-go-to-market-strategy-success-vs-struggling-how-to-know", "url": "#chapter-14-go-to-market-strategy-success-vs-struggling-how-to-know", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "You're succeeding if (Week 10): - Paid evidence meets the locally defined quantity and quality requirement through a repeatable process. - Contribution and payback meet the locally approved threshold with sensitivity, service cost, cash timing, and customer outcomes stated. - Conversion rates above reference points: - Signup → Demo: above modeled target - Demo → Proposal: above modeled target - Proposal → Close: above modeled target - Customer evidence: defined recommendation responses, referrals, retained use, complaints, outcomes, and feature requests; no single item rating proves that customers “love” the product - Clear winning channel: One channel drives most customers with known economics - Founders confident: \"We know how to get next 10 customers\" Next steps (conditional success): Increase exposure gradually only after the channel's incremental economics, capacity, retention, customer outcomes, and operational risks hold under a pre-specified test. Set the next revenue milestone from the venture's cash plan rather than a generic MRR target. You're struggling if (Week 10): - Paid evidence remains below the locally defined requirement despite outreach and launch efforts. - Contribution or payback remains below the approved threshold (economics require redesign before scaling). - Low conversion rates: - Signup → Demo: below modeled target - Demo → Close: below modeled target - High early churn: too many customers cancel within 30 days - No clear pattern: Can't identify what's working vs what's not - Founders unsure: \"We don't know how to get the next customer\" Next steps (Struggling): - Diagnose bottleneck: Is it awareness (too few signups)? Conversion (signups don't convert)? Retention (customers churn)? - Customer interviews: Talk to lost prospects and churned customers to understand why - Iterate one variable: Fix messaging OR pricing OR channel (not all at once) - Extend timeline: Give yourself 4 more weeks to diagnose and fix - Consider pivot: If fundamentals are wrong (no urgent problem, bad economics), may need to revisit product or ICP ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Fundraising and Finance", "headingId": "chapter-15-fundraising-and-finance", "url": "#chapter-15-fundraising-and-finance", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-executive-summary", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Executive Summary", "headingId": "chapter-15-fundraising-and-finance-executive-summary", "url": "#chapter-15-fundraising-and-finance-executive-summary", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Fundraising is a financing decision, not a milestone. Managers must connect the amount and instrument to an operating plan, cash runway, uncertainty, investor fit, governance, dilution, downside proceeds, legal obligations, and credible alternatives. Venture-investor decisions span sourcing, selection, valuation, contract structure, monitoring, and exit; entrepreneurship remains experimentation under uncertainty. [BB-C15-S06] [BB-C15-S07] Key Frameworks: 1. Fundraising Process Timeline 2. Pitch Deck Structure (Slide-by-Slide Guide) 3. Valuation Methods Comparison 4. Term Sheet Key Terms Matrix 5. Cap Table Scenarios & Dilution 6. Investor Evaluation Criteria 7. Due Diligence Checklist 8. Financial Model Template (3-Statement) 9. Exit Strategy Options 10. SAFE vs. Convertible Note Comparison 11. Financing and No-Raise Decision Framework Applied extension: Acquisition finance, quality of earnings, and transition gates are covered in the later ETA section as an applied financing case, not as a twelfth core framework." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-decision-outcomes-and-boundary", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Decision Outcomes and Boundary", "headingId": "chapter-15-fundraising-and-finance-decision-outcomes-and-boundary", "url": "#chapter-15-fundraising-and-finance-decision-outcomes-and-boundary", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "After this chapter, a manager should be able to: 1. Determine whether external capital is warranted and compare equity, debt, customer financing, grants, partnerships, cost reduction, and no-raise paths. 2. Explain how investor fit, evidence, valuation assumptions, round size, instrument, and negotiation terms interact. 3. Build a fully diluted cap table that states every security and option-pool assumption and reconciles shares and ownership to 100 percent. 4. Calculate security-by-security liquidation proceeds, including seniority, conversion, participation, caps, and residual allocation. 5. Connect fundraising to a scenario-based operating model, runway, milestones, governance, disclosure, and stop rules. 6. Build an acquisition sources-and-uses model, reconcile normalized earnings to cash available for debt service, and gate diligence, governance, closing, and transition decisions. This chapter is educational, not legal, tax, securities, accounting, valuation, compensation, or investment advice. Use the actual current documents—not a generic summary—and obtain qualified corporate/securities counsel and tax/accounting review. Instrument terms, model documents, market data, and law change; record the jurisdiction, document version, as-of date, capitalization definition, and assumptions. A term sheet may be partly nonbinding but can include binding provisions; the executed documents govern. Applied exercise — controlled financing case: Starting with a supplied fully diluted capitalization schedule, model a seed SAFE, Series A, option-pool refresh, and three exit values. Reconcile ownership and proceeds to 100 percent, show founder and employee outcomes, compare a no-raise alternative, and recommend raise/revise/pause/stop with cash and governance triggers. Use Chapter 2 for governance and legal ownership, Chapter 4 for valuation, Chapter 13 for venture evidence, Chapter 14 for GTM assumptions, and Chapter 22 for scenario analysis. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview", "url": "#chapter-15-fundraising-and-finance-overview", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The fundraising process timeline is a constructed planning aid that connects capital need, runway, evidence, investor fit, disclosures, diligence, terms, approvals, and closing. It is not a universal duration, funnel, response rate, or financing outcome. [BB-C15-S06] [BB-C15-S07] [BB-C15-S14]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply", "url": "#chapter-15-fundraising-and-finance-how-to-apply", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Start with the operating decision and downside cash scenarios. Compare no-raise and alternative-capital paths, define the evidence and disclosure owner, set a solvency/legal stop rule, and model actual terms before treating a process as worth continuing. Purpose: Plan a financing process against runway and decision gates. The schedule, hours, funnel counts, response rates, fees, and market terms in this chapter are constructed examples unless an adjacent source and as-of date say otherwise; they are not forecasts or market standards. Current U.S. aggregate venture context is available through the registered yearbook, but it does not validate a company-specific timeline or deal term. [BB-C15-S14]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-constructed-fundraising-schedule", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Constructed Fundraising Schedule", "headingId": "chapter-15-fundraising-and-finance-constructed-fundraising-schedule", "url": "#chapter-15-fundraising-and-finance-constructed-fundraising-schedule", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Process Overview (Series A Example): Figure 15.1: Financing decision and fundraising gates (constructed). The process can choose no raise or alternative capital, requires a runway/solvency stop rule, and rejects terms that do not support the operating and governance plan. Investor decision practice and entrepreneurial uncertainty inform the questions, not the timing or outcomes. Text equivalent: Begin with the operating decision and capital need. Compare no raise, alternative capital, and external financing. If evidence, investor fit, disclosures, runway, and readiness are insufficient, revise the operating plan or stop before insolvency. If fundraising proceeds, screen interest and diligence; accept only terms whose cash, dilution, downside proceeds, control rights, and milestones support the plan. Otherwise negotiate, select another option, pause, or stop." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-illustrative-month-0-preparation-example-cadence", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Illustrative Month 0: Preparation (example cadence)", "headingId": "chapter-15-fundraising-and-finance-illustrative-month-0-preparation-example-cadence", "url": "#chapter-15-fundraising-and-finance-illustrative-month-0-preparation-example-cadence", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Update pitch deck (previous round's deck won't work) - [ ] Prepare one-pager (2 sentences + metrics) - [ ] Create a target investor list sized to the financing need, thesis fit, team capacity, and confidentiality constraints (50+ is only a constructed example) - [ ] Identify warm introductions (founder friends, advisors) - [ ] Prepare financial model (projections, unit economics) - [ ] Clean up cap table (equity allocations documented) - [ ] Update business metrics (ARR, growth rate, unit economics) - [ ] Legal review (any issues with current contracts?) Illustrative process target (not a benchmark): Professional materials, a controlled disclosure plan, and a documented introduction path." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-illustrative-month-1-outreach-example-cadence", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Illustrative Month 1: Outreach (example cadence)", "headingId": "chapter-15-fundraising-and-finance-illustrative-month-1-outreach-example-cadence", "url": "#chapter-15-fundraising-and-finance-illustrative-month-1-outreach-example-cadence", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Send a first outreach batch sized to the team's capacity and the investor-fit evidence (the batch size and pace are local choices) - [ ] Track responses (who's interested, who passed, timing) - [ ] Schedule first meetings (investor wants to hear pitch) - [ ] Prepare detailed answers to common questions - [ ] Network at pitch competitions, conferences (build relationships) - [ ] Iterate pitch based on feedback (adjust messaging weekly) Illustrative process target (not a benchmark): Enough qualified conversations to test the financing case without exhausting the team or disclosing beyond the approved boundary. Illustrative response-rate prompts (not benchmarks): - Warm introductions are the strongest path to first meetings; track them separately from cold outreach. - Cold emails usually require much higher volume and sharper targeting than warm introductions. - Conference outreach can work when the fit is clear and follow-up is immediate." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-illustrative-month-1-2-first-meetings-example-cadence", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Illustrative Month 1-2: First Meetings (example cadence)", "headingId": "chapter-15-fundraising-and-finance-illustrative-month-1-2-first-meetings-example-cadence", "url": "#chapter-15-fundraising-and-finance-illustrative-month-1-2-first-meetings-example-cadence", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Meeting cadence: Set a cadence that leaves time for preparation, follow-up, diligence, and the operating plan. - Meeting format: Use a defined pitch and question period appropriate to the audience; record the actual format and decision owner. - Outcome: Investor signals interest, requests more info, or passes - Key metrics shared: Revenue, growth rate, market size, team Tracking Spreadsheet Example: Table 15.1: Author-created or source-bounded decision aid (Investor | Intro Date | 1st Meeting | Interest Level | Feedback | Next Step ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Investor | Intro Date | 1st Meeting | Interest Level | Feedback | Next Step| | :--- | :--- | :--- | :--- | :--- | :---| | Northstar Ventures | 11/1 | 11/8 | Warm | \"Love traction, worried about market\" | Send market analysis | | Harbor Ridge Capital | 11/3 | TBD | - | No response yet | Follow up 11/10 |" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-illustrative-month-2-3-due-diligence-example-cadence", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Illustrative Month 2-3: Due Diligence (example cadence)", "headingId": "chapter-15-fundraising-and-finance-illustrative-month-2-3-due-diligence-example-cadence", "url": "#chapter-15-fundraising-and-finance-illustrative-month-2-3-due-diligence-example-cadence", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Investor level increased: Serious investors start diligence - Activities: - Deeper financial model review (investor's analyst reviews your model) - Reference calls (investor calls your customers, asks \"Would you be sad if they went away?\") - Team references (investor calls former managers/team members) - Market analysis (investor validates market size) - Competitive analysis (investor researches competitors) - Timeline: Record the actual request, response, review, and approval dates; do not infer conviction from elapsed time alone. - Parallel process: Run parallel diligence only when disclosure controls, reviewer capacity, and confidentiality boundaries permit it. Red Flags Investors Look For: - Declining growth (even if growing, if growth rate declining) - CEO unavailable (if founder too busy to fundraise, what else are they skipping?) - Unclear unit economics (if can't explain how you make money, problem) - Team departures (if key people leaving, something's wrong) - Customer concentration (if a few accounts dominate revenue, risky)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-illustrative-month-3-term-sheet-negotiation-example-cadence", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Illustrative Month 3: Term Sheet & Negotiation (example cadence)", "headingId": "chapter-15-fundraising-and-finance-illustrative-month-3-term-sheet-negotiation-example-cadence", "url": "#chapter-15-fundraising-and-finance-illustrative-month-3-term-sheet-negotiation-example-cadence", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Milestone: Lead investor proposes term sheet - Process: - Term sheet outlines: Valuation, investment size, preferences, governance - Founders negotiate terms (don't accept first draft) - Negotiate 5-6 key terms (see Term Sheet section below) - Binding status must be read from the actual term sheet; some provisions may bind before closing, and a term sheet is not a financing commitment - Timeline: Record the actual negotiation sequence and binding provisions; there is no universal negotiation duration. Illustrative outcome prompts: - Lead investor provides term sheet - 1-2 follow-on investors wait for lead to close (see what lead investor thinks)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-illustrative-month-4-legal-closing-example-cadence", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Illustrative Month 4: Legal & Closing (example cadence)", "headingId": "chapter-15-fundraising-and-finance-illustrative-month-4-legal-closing-example-cadence", "url": "#chapter-15-fundraising-and-finance-illustrative-month-4-legal-closing-example-cadence", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Activities: - Lawyers draft operative documents (SAFE, convertible note, or equity agreement) - Cap table updated (new shares issued) - Final due diligence (any last-minute issues?) - Money transfer (wires sent) - Timeline: Follow the engagement letters, document complexity, approvals, jurisdiction, and closing conditions; do not treat a duration as standard. Key Dates: - Closing date: Day money actually hits your account" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-post-close-announcement-1-week", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Post-Close: Announcement (1 week)", "headingId": "chapter-15-fundraising-and-finance-post-close-announcement-1-week", "url": "#chapter-15-fundraising-and-finance-post-close-announcement-1-week", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Press release to media - [ ] Announcement email to team, customers, advisors - [ ] Update LinkedIn, website - [ ] Thank investors publicly Illustrative process timing (not a forecast): - Outreach to first check: record the actual elapsed time and runway impact - First check to last check: model the gap, conditions, and risk of an incomplete close - Total fundraise: use scenario ranges tied to runway, capacity, approvals, and counterparties Common Bottlenecks: - No warm introductions (takes longer to get meetings) - Weak metrics (investors skeptical, longer diligence) - Vague pitch (investor can't see opportunity, passes) - Multiple decision-makers (founders disagree on terms, slows negotiation)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Start from the operating cash need, alternatives, solvency, evidence, and decision authority—not from a round label or calendar. - Stage outreach, disclosure, diligence, negotiation, and closing with explicit owners and stop conditions. - Keep feasible no-raise and alternative-capital paths alive until funds are received and obligations are understood." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Financing duration, response rates, investor counts, fees, and market terms vary by stage, jurisdiction, sector, instrument, and process quality. - A successful close does not establish product-market fit, fair value, future financing, or acceptable stakeholder outcomes. - Press, warm introductions, and investor enthusiasm can create confidentiality, disclosure, solicitation, and reputational risks." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections", "url": "#chapter-15-fundraising-and-finance-connections", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Narrative: Use Framework 2 for evidence and audience-specific financing communication. - Valuation and rights: Use Frameworks 3–5 to reconcile price, dilution, control, proceeds, and documents. - Alternatives and execution: Use Frameworks 8–11 plus Chapters 4, 13, 14, and 22 for cash, venture evidence, GTM assumptions, and scenarios. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview-2", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview-2", "url": "#chapter-15-fundraising-and-finance-overview-2", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The pitch deck structure is a practitioner communication template for presenting a defined financing narrative to a defined audience. Pitch presentation can affect early screening, but a deck does not prove demand, valuation, investability, or a funding result. [BB-C15-S01] [BB-C15-S02] [BB-C15-S04]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply-2", "url": "#chapter-15-fundraising-and-finance-how-to-apply-2", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Select, combine, or omit slides according to stage, audience, confidentiality, disclosure obligations, evidence quality, and the decision being requested. Label issuer data, management forecasts, constructed examples, and inference separately; obtain required securities, legal, privacy, and finance review before circulation. Purpose: Organize a concise, substantiated financing narrative for a defined audience. The structure is a practitioner template, not an industry standard or evidence that the company is investable. Pitch presentation can affect initial screening, while founder experience and organizational capital can matter to funding decisions; neither substitutes for the underlying evidence. [BB-C15-S01] [BB-C15-S02] [BB-C15-S04] Constructed structure: Select, combine, or omit slides according to the investor, stage, confidentiality, disclosure obligations, and decision. All company names, metrics, forecasts, market sizes, and outcomes below are fictional unless an adjacent source states otherwise." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-1-title-slide", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 1: Title Slide", "headingId": "chapter-15-fundraising-and-finance-slide-1-title-slide", "url": "#chapter-15-fundraising-and-finance-slide-1-title-slide", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Content: - Company name + tagline - Your name + title - Date - Contact info - Purpose: First impression (should be clean, memorable) - Example: - \"DataFlow: Deploy data pipelines in 3 days, not 3 weeks\" - Founder: John Smith, CEO - Date: Nov 2025 - Email: founder@example.com" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-2-the-problem", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 2: The Problem", "headingId": "chapter-15-fundraising-and-finance-slide-2-the-problem", "url": "#chapter-15-fundraising-and-finance-slide-2-the-problem", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Customer pain point - Format: 1 powerful stat/quote + visual - Don't: Be vague (\"Marketing is hard\") - Do: Be specific (\"Marketing teams spend 20 percent time on manual data entry, costing SMBs $500K+ annually\") - Avoid: Wall of text (one big stat or quote) - Example visual: Photo of frustrated data engineer + stat overlay Key Question Answered: Why should we care?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-3-your-solution", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 3: Your Solution", "headingId": "chapter-15-fundraising-and-finance-slide-3-your-solution", "url": "#chapter-15-fundraising-and-finance-slide-3-your-solution", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: How you solve the problem - Format: Simple visual + 2-3 key differentiators - Avoid: Feature list (investors don't care about features, care about benefit) - Do: Show how easy/better/different - Example: - Visual: Screenshot of DataFlow UI (drag-and-drop interface) - Differentiators: - \"Deploy in 3 days (vs. 3 weeks)\" - \"No-code pipeline builder (vs. custom coding)\" - \"AI-powered error detection (unique)\" Key Question Answered: What's your answer?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-4-market-size-tam", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 4: Market Size (TAM)", "headingId": "chapter-15-fundraising-and-finance-slide-4-market-size-tam", "url": "#chapter-15-fundraising-and-finance-slide-4-market-size-tam", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: How big is the opportunity? - Format: Single number (TAM) + breakdown - Example: - \"TAM: $50B (Data integration tools across enterprise)\" - \"SAM: $5B (Mid-market data teams)\" - \"SOM: $50M (First 1,000 customers)\" - Investor-fit question: Is reachable demand and the credible expansion case material to this audience's mandate and return model? - Math provided: How did you calculate TAM? (top-down vs. bottom-up) Top-Down (Macro): - Total IT budget ($400B) × % spent on data ($10 percent) × % spent on pipelines ($5 percent) = TAM Bottom-Up (Micro): - 50,000 mid-market companies × $100K avg annual data spend = TAM Avoid: \"TAM is everyone who needs to move data\" (too vague). Be specific on segment. Key Question Answered: Is the reachable market and credible expansion case material to the financing decision?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-5-traction-early-results", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 5: Traction / Early Results", "headingId": "chapter-15-fundraising-and-finance-slide-5-traction-early-results", "url": "#chapter-15-fundraising-and-finance-slide-5-traction-early-results", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Proof you're solving real problem - Metrics (choose 2-3 most impressive): - Revenue (ARR, MRR) - Customer count (10 customers, 5 LOIs, etc.) - Growth rate (50 percent MoM, 200 percent YoY) - User count (10K signups if free product) - Engagement (% daily active users) - Format: Graph showing hockey stick growth (if possible) - Example: - \"ARR: $500K, 20 percent MoM growth\" - \"Customers: EnterpriseDB Co., DataForge, InsightGrid (social proof)\" - Or if pre-revenue: \"200 signups, 30 percent paid conversion (beta)\" Key Question Answered: Is this actually working?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-6-business-model", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 6: Business Model", "headingId": "chapter-15-fundraising-and-finance-slide-6-business-model", "url": "#chapter-15-fundraising-and-finance-slide-6-business-model", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: How do you make money? - Format: Simple box diagram or table - Content: - Pricing ($/customer/month or per transaction) - Revenue model (subscription, usage-based, marketplace, etc.) - Unit economics (CAC, LTV, payback) - Example: - Pricing: $50K/year subscription (enterprise), $5K/year (SMB) - CAC: $8K, LTV: $250K (5-year), LTV:CAC = 3.1:1 ✓ - Gross margin: 70 percent (product margin is key for SaaS) Key Question Answered: Is there a sustainable, scalable business here?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-7-go-to-market-competitive-position", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 7: Go-to-Market / Competitive Position", "headingId": "chapter-15-fundraising-and-finance-slide-7-go-to-market-competitive-position", "url": "#chapter-15-fundraising-and-finance-slide-7-go-to-market-competitive-position", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: How will you win? - Format: Choose one angle: - Competitive positioning: 2x2 matrix (Price/Features) showing where you are - GTM strategy: \"Direct sales (70 percent) + Partnerships with data tools (30 percent)\" - Defensibility: \"Network effects, 5-year customer contracts, IP moat\" - Avoid: \"We'll win by being better\" (too vague) - Do: \"We undercut Competitors A/B by 50 percent AND have 3x faster deployment\" Key Question Answered: Why will customers choose you over alternatives?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-8-team", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 8: Team", "headingId": "chapter-15-fundraising-and-finance-slide-8-team", "url": "#chapter-15-fundraising-and-finance-slide-8-team", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Your team (3-5 key people) - Format: Photo + name/title + 1-line credential - Content for each person: - Name + role - Key achievement (e.g., \"Led engineering at Datadog, 10K customers\") - Note missing skills (transparency builds trust) - Example: - John Smith, CEO - \"Ex-Stripe (5 years), built data infrastructure\" - Sarah Chen, CTO - \"Ex-Google Brain, published 2 papers on ML efficiency\" - Mike Johnson, Sales - \"Ex-Salesforce, $10M book of business\" - Note: Hiring Head of Product, VP Marketing Investor Perspective: \"I'm investing in the team as much as the idea.\" Key Question Answered: Are these the right people to execute?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-9-financial-projections-5-year", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 9: Financial Projections (5-Year)", "headingId": "chapter-15-fundraising-and-finance-slide-9-financial-projections-5-year", "url": "#chapter-15-fundraising-and-finance-slide-9-financial-projections-5-year", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Revenue forecast - Format: Line graph (Year 1-5 revenue) - Content: - Conservative case (base case) + upside case - Show path to profitability (when do you break even?) - Include margin trajectory (gross margin, operating margin) - Example: - Year 1: $500K (currently at) - Year 2: $2M (4x growth) - Year 3: $8M (4x growth) - Year 4: $20M (2.5x growth) - Year 5: $40M (2x growth, approaching maturity) - Breakeven: Year 4 Investor-fit question: What outcomes, ownership, reserves, time horizon, and exit paths would make this opportunity material to a particular fund? Do not impose a universal revenue-growth minimum. Note: Don't explain every line item (that's in the detailed model). Just show overall trajectory. Key Question Answered: Are we targeting enough growth?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-10-fundraising-ask", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 10: Fundraising Ask", "headingId": "chapter-15-fundraising-and-finance-slide-10-fundraising-ask", "url": "#chapter-15-fundraising-and-finance-slide-10-fundraising-ask", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: How much you're raising + use of funds - Format: Pie chart or simple bar chart - Example: - Raising: $5M Series A - Use of funds: - Sales & marketing: $2M (40 percent) - hire sales team - Engineering: $1.5M (30 percent) - build product - Operations: $1.5M (30 percent) - team expansion - Timing: \"Runway until profitability\" (show you're not burning cash wastefully) Key Question Answered: What are you spending the money on?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-11-why-now", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 11: Why Now?", "headingId": "chapter-15-fundraising-and-finance-slide-11-why-now", "url": "#chapter-15-fundraising-and-finance-slide-11-why-now", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Why is this the right time to build this? - Format: 2-3 key trends/inflection points - Examples: - \"Open-source data tools (Airflow, dbt) hit critical mass\" (better platform) - \"Data engineering headcount is growing quickly\" (market emerging) - \"AI capabilities now justifiable data investment\" (new use case) - Avoid: \"Because we're ready\" (not credible) - Do: External market shifts that create opportunity Key Question Answered: Why didn't someone do this already? (Answer: Because conditions have just changed)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-12-current-metrics-milestones", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 12: Current Metrics & Milestones", "headingId": "chapter-15-fundraising-and-finance-slide-12-current-metrics-milestones", "url": "#chapter-15-fundraising-and-finance-slide-12-current-metrics-milestones", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Proof of execution (not just promises) - Format: Bullet points - Content: - Key milestone 1 (what you've accomplished in last 3 months) - Key milestone 2 (what's coming in next 3 months) - Hiring plan (2-3 next key hires) - Example: - \"Closed DataForge + InsightGrid as customers (proof of sales)\" - \"Launched AI error detection (product innovation)\" - \"Next: Hire VP Sales + VP Product (scale both)\" Key Question Answered: Can you execute on the plan you're describing?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-13-long-term-vision", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 13: Long-Term Vision", "headingId": "chapter-15-fundraising-and-finance-slide-13-long-term-vision", "url": "#chapter-15-fundraising-and-finance-slide-13-long-term-vision", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Where you're going (think 10 years) - Format: Vision statement + 2-3 bullet points - Examples: - \"Vision: Every data team deploys pipelines in hours, not months\" - \"Become the CanvasFlow of data engineering (ubiquitous, collaborative)\" - \"Expand beyond pipelines to full data platform (land and expand strategy)\" Avoid: \"We'll be a multi-billion dollar company\" (no shit, that's why investors care) Do: Specific vision (\"We'll be acquired by DataForge as the data pipeline layer\" OR \"We'll go public as the leading data integration platform\") Key Question Answered: Is this CEO thinking big enough?" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-slide-14-questions-call-to-action", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Slide 14: Questions / Call to Action", "headingId": "chapter-15-fundraising-and-finance-slide-14-questions-call-to-action", "url": "#chapter-15-fundraising-and-finance-slide-14-questions-call-to-action", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Show: Invitation to discuss - Format: \"Let's talk\" + contact info + one key ask - Content: - \"What questions do you have?\" - Email + phone + LinkedIn - Optional: \"Ideal investor = understands data infrastructure + has customer relationships\"" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers-2", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers-2", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Make the requested decision, evidence, capital use, downside, rights, and alternatives inspectable to the intended audience. - Separate issuer data, management forecasts, constructed examples, third-party evidence, allegations, testimony, and inference. - Tailor the deck to the audience and document version; do not use slide polish to conceal missing evidence or unresolved obligations." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques-2", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques-2", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Pitch quality can affect screening but cannot establish demand, valuation, governance quality, or funding outcome. - Market-size, traction, growth, and unit-economics slides are highly sensitive to definitions, cohorts, attribution, and accounting. - Circulation can create securities, confidentiality, privacy, data-room, and reputational obligations that a template does not resolve." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections-2", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections-2", "url": "#chapter-15-fundraising-and-finance-connections-2", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Evidence: Use Frameworks 1 and 6–8 for fundraising process, investor fit, diligence, and model assumptions. - Price and rights: Use Frameworks 3–5 and 10 for valuation, term-sheet, cap-table, and instrument interactions. - Operations: Use Framework 11 and Chapters 4, 13, 14, and 22 for cash, venture evidence, GTM, and analysis. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview-3", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview-3", "url": "#chapter-15-fundraising-and-finance-overview-3", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The valuation methods comparison is an author-created reconciliation aid for separating negotiated financing price, fair value, intrinsic-value scenarios, paper value, and eventual proceeds. Young-company outputs are highly assumption-sensitive; no method or multiple is a universal answer. [BB-C15-S05] [BB-C15-S12] [BB-C15-S16]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply-3", "url": "#chapter-15-fundraising-and-finance-how-to-apply-3", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "State the claim being valued, capitalization/security rights, date, cash-flow basis, failure and financing scenarios, discounting, dilution, and distribution. Present ranges and sensitivity, reproduce the arithmetic, and obtain qualified valuation, accounting, tax, and transaction review before relying on the result. Purpose: Compare valuation methods and expose the assumptions that drive the result. Young-company valuation is especially sensitive to limited history, survival, scaling, reinvestment, dilution, and uncertain forecasts. A financing price is negotiated transaction evidence; it is not automatically fair value, intrinsic value, or eventual exit proceeds. Professional portfolio-company fair-value work has a different purpose and control framework. [BB-C15-S12] [BB-C15-S16] All multiples, returns, probabilities, years, financing prices, and company examples in this section are constructed inputs, not market benchmarks. The venture-capital method is a backward-looking teaching method whose output is only as defensible as the exit, timing, failure, follow-on, dilution, ownership, and required-return assumptions. [BB-C15-S05]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-method-1-venture-capital-method", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Method 1: Venture-capital method", "headingId": "chapter-15-fundraising-and-finance-method-1-venture-capital-method", "url": "#chapter-15-fundraising-and-finance-method-1-venture-capital-method", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A controlled version works backward from explicit exit and ownership assumptions: 1. Estimate a scenario-specific terminal equity value and time. 2. Translate the investor's required return or target multiple into required exit proceeds. 3. Divide required exit proceeds by terminal equity value to obtain required ownership at exit. 4. Divide that exit ownership by the modeled retention factor for follow-on dilution to obtain required post-round ownership today. 5. Divide new money by required post-round ownership to obtain the implied post-money financing value; subtract new money for pre-money value. 6. Run failure, downside, base, and upside scenarios and reconcile the resulting cap table and waterfall. Constructed arithmetic: A $5 million investment with $40 million required exit proceeds, $500 million terminal equity value, and 60 percent retention of today's stake through later dilution implies 8 percent exit ownership, 13.3333 percent post-round ownership, a $37.5 million post-money value, and a $32.5 million pre-money value. These outputs are not a recommendation and change materially with the inputs." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-method-2-comparable-transactions-or-companies", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Method 2: Comparable transactions or companies", "headingId": "chapter-15-fundraising-and-finance-method-2-comparable-transactions-or-companies", "url": "#chapter-15-fundraising-and-finance-method-2-comparable-transactions-or-companies", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Select observations with the same valuation basis, security rights, stage, geography, sector, date, growth, margin, retention, concentration, capital intensity, risk, and accounting definitions. Normalize enterprise versus equity value and primary versus secondary pricing. Report the observation date, distribution, exclusions, and adjustments; a headline revenue multiple without these controls is not comparable." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-method-3-scenario-based-discounted-cash-flow", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Method 3: Scenario-based discounted cash flow", "headingId": "chapter-15-fundraising-and-finance-method-3-scenario-based-discounted-cash-flow", "url": "#chapter-15-fundraising-and-finance-method-3-scenario-based-discounted-cash-flow", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Build revenue, margin, reinvestment, working-capital, tax, failure, financing, and dilution scenarios. Discount cash flows with assumptions consistent with the risk and claim being valued, then test terminal-value dependence. This method exposes operating assumptions but can create false precision when history is short and survival uncertainty is high. [BB-C15-S12]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-method-4-milestone-or-scorecard-methods", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Method 4: Milestone or scorecard methods", "headingId": "chapter-15-fundraising-and-finance-method-4-milestone-or-scorecard-methods", "url": "#chapter-15-fundraising-and-finance-method-4-milestone-or-scorecard-methods", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Practitioner milestone methods can structure a conversation about team, evidence, product, market, and execution risk when cash-flow and comparable evidence are weak. Dollar weights and score adjustments are judgments, not independently observed value. Do not treat a branded scorecard as appraisal evidence. Table 15.2: Author-created or source-bounded decision aid (Method | Decision use | Main controls ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Method | Decision use | Main controls| | :--- | :--- | :---| | Venture-capital method | Backsolve financing price from exit and return assumptions | Exit value/time, required proceeds, future dilution, ownership, failure scenarios | | Comparables | Anchor to observed market transactions | As-of date, rights, stage, definitions, distribution, adjustments | | Scenario DCF | Connect operating plan to intrinsic-value range | Cash-flow reconciliation, reinvestment, failure, discount rate, terminal value | | Milestone/scorecard | Make sparse-evidence judgments explicit | No false precision; document weights, rationale, and disconfirming evidence | | Portfolio fair value | Financial reporting under a consistent policy | Applicable accounting framework, valuation policy, calibration, review and audit controls | Decision memo: Present a range from at least two methods, explain why they differ, identify the assumptions that dominate, show financing and downside proceeds, and separate negotiated price from fair value and expected founder/investor outcomes." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers-3", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers-3", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- State what is being valued, for whom, on what date, under which security and capitalization definition, and for which decision. - Reproduce the arithmetic, show sensitivity and failure cases, and distinguish price, fair value, paper value, and distributable proceeds. - Escalate valuation, tax, accounting, legal, and fiduciary implications to the responsible qualified reviewers." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques-3", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques-3", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Young-company methods can create false precision when history, survival, cash flow, comparables, and rights are uncertain. - A negotiated price, headline multiple, or target return is not proof of intrinsic value or eventual proceeds. - Scorecards, milestones, and comparables are judgments whose relevance depends on date, rights, definitions, and context." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections-3", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections-3", "url": "#chapter-15-fundraising-and-finance-connections-3", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Capitalization: Use Framework 5 for dilution, security rights, and proceeds. - Terms: Use Framework 4 for the contractual provisions that alter value and control. - Modeling: Use Frameworks 8–11 and Chapter 4 for cash-flow, runway, alternatives, and downside analysis. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview-4", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview-4", "url": "#chapter-15-fundraising-and-finance-overview-4", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The term-sheet rights and model matrix is a governance and modeling checklist for interacting economic, control, information, transfer, future-financing, and exit provisions. It is not a term sheet, legal advice, negotiation default, or statement of market standard. [BB-C15-S08] [BB-C15-S09] [BB-C15-S10] [BB-C15-S11]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply-4", "url": "#chapter-15-fundraising-and-finance-how-to-apply-4", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Translate each proposed provision into share, cash, proceeds, voting, approval, tax/accounting, and downside scenarios. Compare the full package with actual documents, jurisdiction, authority, alternatives, and stakeholder effects; use qualified counsel and finance/tax reviewers before approval or signing. Purpose: Identify interacting economic, control, information, future-financing, transfer, and exit provisions for modeling and counsel review. The matrix is not a term sheet, a statement of market standard, or negotiation advice. Actual documents, jurisdiction, approvals, securities law, tax, accounting, fiduciary duties, and the full package control the outcome. The NVCA model document set illustrates alternative contractual structures, while VC-contracting research supports the importance and variation of cash-flow, board, voting, liquidation, and exit rights. [BB-C15-S08] [BB-C15-S09] [BB-C15-S10] [BB-C15-S11] Table 15.3: Author-created or source-bounded decision aid (Provision family | Questions to model and escalate ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Provision family | Questions to model and escalate| | :--- | :---| | Capitalization and valuation | Is the price pre- or post-money? What fully diluted share denominator, option-pool change, converting security, warrant, debt, and secondary sale is included? | | Liquidation and dividends | What multiple, seniority, participation/cap, accrued or cumulative dividend, conversion choice, escrow, debt, fee, and change-of-control definition governs proceeds? | | Conversion and anti-dilution | What optional/automatic conversion thresholds and exact broad/narrow weighted-average, full-ratchet, pay-to-play, or excluded-issuance terms apply? | | Board and observer rights | Who appoints, removes, and fills vacancies? What independence, committee, observer, confidentiality, privilege, conflict, and fiduciary obligations apply? | | Voting and protective rights | Which class, series, board, shareholder, or regulator approvals are required for financing, M&A, budget, debt, compensation, related-party, charter, asset, or dissolution decisions? | | Pro-rata and future financing | Who can maintain or increase ownership, on what notice, allocation, waiver, transfer, expiry, and major-investor thresholds? | | Information and inspection | Which financial, operating, customer, security, and compliance reports are due; how are privacy, privilege, confidentiality, and competitor access protected? | | Transfer, drag, tag, ROFR/co-sale | Which holders, thresholds, prices, representations, indemnities, escrow, and exceptions govern a transfer or sale? | | Founder/employee equity | What vesting, repurchase, acceleration, leaver, option, tax, compensation, IP, and employment terms apply, and who approves them? | | Closing and binding provisions | Which exclusivity, confidentiality, expenses, governing-law, access, conduct, and no-shop provisions bind before closing? What conditions, diligence, approvals, and termination rights remain? |" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-security-by-security-analysis", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Security-by-security analysis", "headingId": "chapter-15-fundraising-and-finance-security-by-security-analysis", "url": "#chapter-15-fundraising-and-finance-security-by-security-analysis", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Convert each proposed provision into a capitalization, cash, proceeds, voting, or approval schedule. 2. Run downside, base, and upside exits; no-next-round, down-round, missed-milestone, founder-departure, and insolvency scenarios. 3. Record which term protects which risk, who bears the cost, how it interacts with other terms, and what alternative financing changes. 4. Reconcile the term-sheet model with the draft and executed documents at each revision. 5. Obtain counsel and tax/accounting review before approval. Do not label a term “founder-friendly,” “investor-friendly,” “standard,” or “non-negotiable” without context and current comparable evidence." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers-4", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers-4", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Translate every term into security-specific cash, ownership, control, approval, disclosure, tax/accounting, and downside consequences. - Model the full package and actual document version before negotiating or approving a term. - Record who owns each legal, finance, tax, governance, and stakeholder review and what remains unresolved." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques-4", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques-4", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Model documents and empirical contracting evidence illustrate variation; they do not make a provision appropriate or standard for a particular deal. - Headline valuation and “friendly” labels can hide seniority, participation, anti-dilution, control, consent, and future-financing costs. - Term-sheet language can be partly binding and can create exclusivity, confidentiality, expense, conduct, or no-shop obligations." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections-4", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections-4", "url": "#chapter-15-fundraising-and-finance-connections-4", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ownership: Use Framework 5 to reconcile dilution and rights. - Valuation: Use Framework 3 to connect price and security terms to scenario value. - Diligence and instruments: Use Frameworks 7 and 10 plus qualified counsel, tax, accounting, and fiduciary review. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview-5", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview-5", "url": "#chapter-15-fundraising-and-finance-overview-5", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The cap-table and dilution framework is a fully diluted share-and-rights reconciliation aid. It separates ownership percentages from control, preferences, conversion, vesting, option-pool, tax, and employment effects; every displayed schedule is constructed and must reconcile to 100 percent." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply-5", "url": "#chapter-15-fundraising-and-finance-how-to-apply-5", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the capitalization denominator and document version, list every security and pool assumption, calculate price per share and new shares, model security-by-security proceeds and rights, and have an independent reviewer reproduce the schedule before a financing or governance decision. Purpose: Model fully diluted ownership through financing rounds and separately model the negotiated economic and control rights. Every example is constructed. It must state the pre-round shares, security class, converting instruments, option-pool treatment, pre-/post-money convention, new money, price per share, and post-round totals. The schedule must reconcile shares and percentages to 100 percent, and a second reviewer should reproduce it. Current NVCA model documents and contracting research illustrate that cash-flow, voting, board, liquidation, information, future-financing, and transfer rights can differ from pro-rata ownership. [BB-C15-S08] [BB-C15-S09] [BB-C15-S10] [BB-C15-S11]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-capitalization-and-rights-visual", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Capitalization and Rights Visual", "headingId": "chapter-15-fundraising-and-finance-capitalization-and-rights-visual", "url": "#chapter-15-fundraising-and-finance-capitalization-and-rights-visual", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 15.2: Capitalization and control-rights model (constructed). Round size and pre-money value determine the post-money calculation only after fully diluted capitalization, converting instruments, and option-pool timing are defined. Negotiated control rights are modeled in a separate lane; ownership alone does not determine governance. Text equivalent: In the ownership lane, reconcile the existing fully diluted share schedule, conversions, and option-pool change; add the round's new shares at the stated price; then verify post-money shares and percentages total 100 percent. In the rights lane, read the actual documents and separately record board, voting, protective, information, pro-rata, anti-dilution, liquidation, dividend, and transfer rights. Legal and tax/accounting reviewers approve the final model. Scenario 1: Pre-Seed to Series B (3 Rounds)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-after-seed-round-500k-at-2m-post-money", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "After Seed Round ($500K at $2M post-money) ", "headingId": "chapter-15-fundraising-and-finance-after-seed-round-500k-at-2m-post-money", "url": "#chapter-15-fundraising-and-finance-after-seed-round-500k-at-2m-post-money", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Reconciled calculation: - Pre-money valuation: $1.5M (what investors say company worth before $500K check) - Investment: $500K - Post-money valuation: $1.5M + $500K = $2M - Investor gets: $500K / $2M = 25 percent ownership - Existing holders retain: $1.5M / $2M = 75 percent; each 50 percent founder becomes 37.5 percent." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-after-series-a-round-5m-at-25m-post-money", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "After Series A Round ($5M at $25M post-money) ", "headingId": "chapter-15-fundraising-and-finance-after-series-a-round-5m-at-25m-post-money", "url": "#chapter-15-fundraising-and-finance-after-series-a-round-5m-at-25m-post-money", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Math: - Pre-money: $20M (company was worth $20M before $5M check) - Series A investors get: $5M / $25M = 20 percent - Existing holders collectively retain 80 percent; multiply each pre-round percentage by 0.80. - Founders: 75 percent before the round × 0.80 = 60 percent total. Simpler approach: Table 15.4: Author-created or source-bounded decision aid (Round | New money | Pre-money | Post-money | New investor | Founders after round ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Round | New money | Pre-money | Post-money | New investor | Founders after round | | :--- | :--- | :--- | :--- | :--- | :--- | | Seed | $500K | $1.5M | $2M | 25 percent | 75 percent | | Series A | $5M | $20M | $25M | 20 percent | 60 percent | For a clean priced round with no other capitalization changes: Post-Round Ownership = Pre-Round Ownership × (Pre-Money / Post-Money) Seed Round: - Founders owned 100 percent - New investor gets: 500K / 2M = 25 percent - Founders post-round: 100 percent × (1.5M / 2M) = 75 percent Series A Round: - Founders owned 75 percent - New investor gets: 5M / 25M = 20 percent - Founders post-round: 75 percent × (20M / 25M) = 60 percent" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-after-series-b-round-15m-at-85m-post-money", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "After Series B Round ($15M at $85M post-money) ", "headingId": "chapter-15-fundraising-and-finance-after-series-b-round-15m-at-85m-post-money", "url": "#chapter-15-fundraising-and-finance-after-series-b-round-15m-at-85m-post-money", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Key Pattern: Founders dilute with each round (dilution is normal and expected) Dilution Path Example: - Seed: Founders 75 percent - Series A: Founders 60 percent (dilution: 15 percent) - Series B: Founders 49.4118 percent (60 percent × 70/85) Total founder dilution in this worked example: From 100 percent to approximately 49.4118 percent through Series B. Interpretation boundary: A higher financing price can increase the notional value of retained shares, but it is not liquid wealth and does not show that financing caused enterprise value. Preferences, vesting, tax, future dilution, failure risk, transaction costs, and exit proceeds can make ownership percentage an incomplete measure. Entrepreneurial payoff is highly uncertain and nondiversified. [BB-C15-S15] Cap Table Management:" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-for-employees", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "For Employees", "headingId": "chapter-15-fundraising-and-finance-for-employees", "url": "#chapter-15-fundraising-and-finance-for-employees", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Impact on IPO/Acquisition: - Ownership does not equal proceeds. Model security conversion, preferences, seniority, participation/caps, escrow, debt, fees, tax, and vesting before estimating founder or employee outcomes. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-5a-advanced-dilution-modeling-realistic-scenarios", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "5A. Advanced Dilution Modeling: Realistic Scenarios", "headingId": "chapter-15-fundraising-and-finance-5a-advanced-dilution-modeling-realistic-scenarios", "url": "#chapter-15-fundraising-and-finance-5a-advanced-dilution-modeling-realistic-scenarios", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Model complex dilution scenarios including option pools, down rounds, bridge financing, and liquidation preferences. Critical Context: The basic dilution examples above assume clean priced rounds. Option pools, down rounds, bridge instruments, anti-dilution, and liquidation rights can change ownership and proceeds; their effects depend on the capitalization schedule and actual documents." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-scenario-1-option-pool-impact-on-founder-dilution", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Scenario 1: Option Pool Impact on Founder Dilution", "headingId": "chapter-15-fundraising-and-finance-scenario-1-option-pool-impact-on-founder-dilution", "url": "#chapter-15-fundraising-and-finance-scenario-1-option-pool-impact-on-founder-dilution", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Setup: Series A investor demands a larger option pool before financing Question: Who gets diluted by the option pool—founders or investors? Answer: If the negotiated pre-money fully diluted capitalization includes a pool increase, the pre-financing holders generally bear that increase. If the pool is created post-financing, all holders generally share the dilution. The exact share schedule and documents control. Example: How Option Pool Is Negotiated: - Founders propose: 10 percent option pool (minimize dilution) - Investor counters: 20 percent option pool (maximize hiring flexibility) - Common settlement: a negotiated option pool sized for the next hiring plan Decision approach: Size the pool from an approved hiring and compensation plan, then model pre-money and post-money alternatives in shares. A three-percentage-point difference in stated ownership is not automatically a three-percentage-point change in exit proceeds because later dilution, vesting, preferences, debt, fees, and tax intervene. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-scenario-2-down-round-dilution-worst-case", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Scenario 2: Down Round Dilution (Worst Case)", "headingId": "chapter-15-fundraising-and-finance-scenario-2-down-round-dilution-worst-case", "url": "#chapter-15-fundraising-and-finance-scenario-2-down-round-dilution-worst-case", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Setup: Series B raises at lower valuation than Series A (down round) Model boundary: A down round is determined by price per share for the relevant security—not by comparing one round's pre-money or post-money headline with another. Weighted-average anti-dilution does not simply preserve an investor's investment value and cannot be calculated from percentages alone. Use the exact clause and the pre-issuance capitalization. [BB-C15-S08] [BB-C15-S09] For a broad-based weighted-average clause, a common conceptual form adjusts the preferred conversion price as: CP2 = CP1 x (A + B) / (A + C) where CP1 is the old conversion price, CP2 is the adjusted price, A is the contract-defined fully diluted shares outstanding before the issuance, B is the number of shares the new consideration would have purchased at CP1 , and C is the number of shares actually issued at the lower price. Exact definitions, exclusions, pay-to-play, and interaction with other securities come from the documents. Required schedule: 1. Record old shares, original issue/conversion price, preferences, and the clause's defined A denominator. 2. Calculate new-round price per share from the negotiated capitalization and consideration. 3. Calculate B , C , CP2 , incremental as-converted shares, the new-money shares, and any option-pool or instrument conversions. 4. Reconcile every class and holder to 100 percent before and after the adjustment. 5. Compare the financing with cost reduction, bridge/debt, sale, restructuring, and no-deal paths under solvency, fiduciary, employee, tax, disclosure, and approval constraints. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-scenario-3-bridge-financing-convertible-note-impact", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Scenario 3: Bridge Financing & Convertible Note Impact", "headingId": "chapter-15-fundraising-and-finance-scenario-3-bridge-financing-convertible-note-impact", "url": "#chapter-15-fundraising-and-finance-scenario-3-bridge-financing-convertible-note-impact", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Setup: Company needs cash before Series B, raises convertible note Question: How does bridge note affect dilution? Answer: It depends on the executed note, interest and maturity, qualified-financing definition, conversion price, discount/cap interaction, pre-/post-money convention, capitalization denominator, and treatment of the note relative to new money. Dividing principal by a headline valuation does not produce a reconciled ownership percentage. Controlled bridge model: 1. Accrue principal and any interest through the modeled conversion or repayment date. 2. Calculate the price produced by each applicable conversion mechanism using the contract-defined share denominator; apply the contractual selection rule rather than assuming both cap and discount. 3. Convert the note into a share count, add the priced-round shares and any option-pool change, and reconcile the fully diluted capitalization to 100 percent. 4. Model maturity, repayment, default, extension, change-of-control, seniority, cash, covenant, tax, and securities-law outcomes if the next financing does not occur. 5. Compare expected cash and stakeholder outcomes with feasible alternatives. A financing-price premium is not the instrument's total economic cost. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-scenario-4-liquidation-preference-impact-on-exit-economics", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Scenario 4: Liquidation Preference Impact on Exit Economics", "headingId": "chapter-15-fundraising-and-finance-scenario-4-liquidation-preference-impact-on-exit-economics", "url": "#chapter-15-fundraising-and-finance-scenario-4-liquidation-preference-impact-on-exit-economics", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Setup: Company sells for $50M, but investors have liquidation preferences Question: Who gets money in what order? Answer: It depends on the documents' seniority, multiple, participation and cap, dividends, conversion choices, debt and transaction deductions, escrow, tax, and class-specific rights. This constructed example assumes no debt, fees, tax, escrow, accrued dividends, participation cap, or seniority conflict; Series B has a 1x participating preference and Series A has a 1x non-participating preference. [BB-C15-S08] [BB-C15-S09] [BB-C15-S11] Example: Controlled waterfall method: 1. Start with distributable proceeds after contract-defined debt, fees, escrow, and other senior deductions. 2. Apply contractual class seniority and accrued rights. 3. For each non-participating class, compare its preference with its as-converted outcome under the full waterfall—not a percentage of headline exit value. 4. Apply participation and any cap to the contract-defined residual. 5. Allocate residual proceeds to eligible as-converted shares, then reconcile all distributions to total distributable proceeds. 6. Test multiple exit values and have counsel plus a second modeler reproduce the result. No reliable shortcut subtracts invested capital from nominal founder ownership. Decision implication: Participating preferences can materially reduce common-holder proceeds in some exits, but negotiation priorities depend on the complete term package, financing alternatives, cash need, and governance plan. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-scenario-5-full-dilution-journey-seed-to-ipo", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Scenario 5: Full Dilution Journey (Seed to IPO)", "headingId": "chapter-15-fundraising-and-finance-scenario-5-full-dilution-journey-seed-to-ipo", "url": "#chapter-15-fundraising-and-finance-scenario-5-full-dilution-journey-seed-to-ipo", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Controlled-model specification: A multi-round schedule should not be hand-waved from headline valuations. Create one share ledger that rolls forward each holder and security through every event: 1. Opening issued and fully diluted shares by holder and class. 2. Each SAFE/note conversion, warrant exercise, recapitalization, split, transfer, forfeiture, cancellation, and option-pool change. 3. Each priced round's pre-money fully diluted denominator, price per share, new shares, and post-round total. 4. Vesting and exercise assumptions, tax and compensation implications, and required board/shareholder approvals. 5. IPO or sale primary/secondary shares, lockups, conversion, underwriting/transaction costs, preferences, debt, escrow, and taxes. At every event, share counts roll forward exactly, ownership percentages reconcile to 100 percent, and cash sources/uses reconcile. A financing price is not an exit value; paper value is not founder proceeds; no general pattern guarantees that early or later rounds dilute more. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-dilution-modeling-tool", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Dilution Modeling Tool", "headingId": "chapter-15-fundraising-and-finance-dilution-modeling-tool", "url": "#chapter-15-fundraising-and-finance-dilution-modeling-tool", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "No controlled workbook is bundled with this chapter. Do not rely on the placeholder link from an earlier draft. A future tool should implement the following specification and include formula tests plus an independent-reproduction check: Operator Recommendation: - Model dilution BEFORE fundraising discussions (know your walkaway ownership %) - Compare scenarios: \"Series A at $10M vs. $15M valuation → how much dilution difference?\" - Model downside: \"If down round happens, what's my ownership?\" - Model exit: \"At $100M exit, do I make enough money to justify risk?\" --- Cross-Reference: - For term sheet negotiation on liquidation preferences, see Section 4: Term Sheet Key Terms - For financing and no-raise comparison, see Section 11: Financing and No-Raise Decision Framework - For financial modeling of valuation scenarios, see Chapter 4: Financial Analysis & Valuation, Section on Startup Valuation Methods" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers-5", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers-5", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Require a fully diluted, security-by-security schedule that reconciles shares, percentages, conversions, pool changes, and proceeds to 100 percent. - Separate ownership from control, preferences, vesting, employment, tax, and liquidity outcomes. - Have an independent reviewer reproduce the schedule against the actual capitalization records and documents." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques-5", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques-5", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A cap table is a model of defined rights and assumptions, not a complete governance, tax, employment, or exit conclusion. - Rounding, pool timing, conversions, warrants, secondary sales, and document definitions can materially change the result. - Ownership percentages alone do not determine proceeds, control, or founder/employee outcomes." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections-5", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections-5", "url": "#chapter-15-fundraising-and-finance-connections-5", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Terms and valuation: Use Frameworks 3 and 4 for price, rights, conversion, and control. - Modeling: Use Framework 8 for cash and scenario links, and Framework 10 for SAFE/note conversion. - Governance: Use Chapters 2, 4, 13, 14, and qualified counsel/tax/accounting reviewers. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview-6", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview-6", "url": "#chapter-15-fundraising-and-finance-overview-6", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The investor evaluation criteria framework is an author-created evidence-and-fit matrix for comparing investors, funds, strategic capital, and alternatives. Research supports attention to founder/organizational capital, alliances, intellectual capital, and human capital in particular contexts; it does not establish universal weights, red flags, or funding odds. [BB-C15-S02] [BB-C15-S03]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply-6", "url": "#chapter-15-fundraising-and-finance-how-to-apply-6", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the financing need, stage, sector, jurisdiction, investor authority, value-add hypothesis, terms, governance, confidentiality, conflicts, and downside. Score only observable, decision-relevant evidence and document uncertainty; do not infer character, fit, or outcome from reputation proxies alone. Purpose: Construct a transparent investor-fit and evidence matrix without pretending that all investors use the same weights. Research supports attention to founder experience/organizational capital and, in a biotechnology sample, alliances plus intellectual and human capital; it does not justify universal criteria, weights, or red flags. [BB-C15-S02] [BB-C15-S03] Constructed investor scorecard: Replace every weight, threshold, and label with criteria from the target investor's stated thesis and observed process; separately evaluate conflicts, fund reserves, governance behavior, reputation, follow-on capacity, and founder/company fit." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-1-team-illustrative-weighting-example", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "1. Team (illustrative weighting example) ", "headingId": "chapter-15-fundraising-and-finance-1-team-illustrative-weighting-example", "url": "#chapter-15-fundraising-and-finance-1-team-illustrative-weighting-example", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Criteria: - Relevant experience (Have they built in this space before?) - Complementary skills (Do founders cover different areas?) - Execution track record (Have they shipped products?) - Coachability (Will they listen to investor input?) - Red flags: - Missing relevant evidence or capability may require mitigation; founder status alone is not a universal risk rule - Unresolved founder conflict or unclear decision rights may require governance or operating remedies - Experience gap to test against the role, evidence, and available support—not a categorical background rule - Scoring: - Excellent: Evidence shows relevant capability, shipped work, clear decision rights, and a credible plan for remaining gaps - Good: Some relevant experience, clear division of labor - Fair: Passionate but inexperienced - Poor: No relevant background" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-2-market-size-tam-illustrative-weighting-example", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "2. Market Size / TAM (illustrative weighting example) ", "headingId": "chapter-15-fundraising-and-finance-2-market-size-tam-illustrative-weighting-example", "url": "#chapter-15-fundraising-and-finance-2-market-size-tam-illustrative-weighting-example", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Criteria: - Market scope is material to the specific fund's strategy, ownership target, reserve plan, and return requirements - Growing market (is it expanding or shrinking?) - Timing (Is market now ready or 5 years early?) - Red flags: - Market scope is inconsistent with the specific investor's mandate or the venture's credible expansion path - Declining market (e.g., fax machine market 2005) - Unproven market (e.g., \"metaverse applications\" 2022) - Scoring: - Excellent: Reconciled reachable demand, credible expansion, observed buyer evidence, and explicit uncertainty; any dollar or growth figures are local scenario inputs - Strong evidence: Reconciled bottom-up demand, reachable buyers, credible expansion paths, and explicit uncertainty - Mixed evidence: Some reachable demand, but adoption, pricing, competition, or expansion remains unresolved - Weak evidence: Top-down totals are not reconciled to reachable buyers or the market is contracting without a credible response" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-3-traction-illustrative-weighting-example", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "3. Traction (illustrative weighting example) ", "headingId": "chapter-15-fundraising-and-finance-3-traction-illustrative-weighting-example", "url": "#chapter-15-fundraising-and-finance-3-traction-illustrative-weighting-example", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Criteria: - Revenue (Have you made money from real customers?) - Growth rate (Is growth accelerating?) - Customer feedback (Do customers actually want this?) - Defensibility (Can you keep customers once you get them?) - Red flags: - No revenue + no customers (just idea) - Declining growth (even if growing, slowdown is concerning) - High churn (customers leaving once they realize product isn't good) - Vague customer names (No real logos) - Scoring: - Excellent: Evidence shows high-quality revenue or customer outcomes, cohort definitions, retention/expansion context, and a credible explanation of attribution; dollar and growth figures are local scenario inputs - Good: Some customer or revenue evidence with clear definitions and known gaps; do not apply a universal ARR or growth cutoff - Early: Limited revenue or customer evidence; describe it precisely without applying a universal cutoff - Poor: No revenue, no traction" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-4-product-illustrative-weighting-example", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "4. Product (illustrative weighting example) ", "headingId": "chapter-15-fundraising-and-finance-4-product-illustrative-weighting-example", "url": "#chapter-15-fundraising-and-finance-4-product-illustrative-weighting-example", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Criteria: - Is product building correctly? (Solving real problem vs. imaginary problem) - Differentiation (Why this over alternatives?) - Path to scale (Can product scale to millions of users?) - Red flags: - Building what founders think customers want (not validated) - Product has competitors with 10+ year head start - Product is lifestyle business (can't scale beyond founder effort) - Scoring: - Excellent: Product solves validated problem, clear differentiation, scalable architecture - Good: Product working, customers find it valuable - Fair: Product MVP exists, unproven differentiation - Poor: Product vague or too similar to existing" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-5-business-model-illustrative-weighting-example", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "5. Business Model (illustrative weighting example) ", "headingId": "chapter-15-fundraising-and-finance-5-business-model-illustrative-weighting-example", "url": "#chapter-15-fundraising-and-finance-5-business-model-illustrative-weighting-example", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Criteria: - Unit economics (Are you making money per customer?) - Defensibility (Can competitors undercut you on price?) - Scalability (Do you need to add 1 person per customer or can it scale?) - Red flags: - Unit economics don't work (CAC LTV) - Business model is commoditized (price-based competition) - Requires hand-holding every customer - Scoring: - Excellent: Contribution, acquisition cost, retention, service cost, margin, cash timing, and uncertainty are reconciled for the relevant cohort; any ratio or margin is a local scenario input - Good: Unit economics are directionally supported, with material assumptions and unresolved sensitivity clearly documented - Fair: Unit economics unclear - Poor: LTV:CAC < 1:1 (you lose money on each customer)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-6-usage-and-reference-signals-illustrative-weighting-example", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "6. Usage and reference signals (illustrative weighting example) ", "headingId": "chapter-15-fundraising-and-finance-6-usage-and-reference-signals-illustrative-weighting-example", "url": "#chapter-15-fundraising-and-finance-6-usage-and-reference-signals-illustrative-weighting-example", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Criteria: - Has investor done reference calls with customers? - Would customers be \"devastated\" if product went away? - Do customers renew / have low churn? - Red flags: - Customers don't actually love product (forced to use it) - High churn (customers leave after trial) - Scoring: - Excellent: Referenceable customers describe attributable outcomes, renewal/expansion evidence, and material switching costs; no universal churn threshold applies - Good: Customer evidence is positive but cohort maturity, concentration, or attribution remains incomplete - Fair: Customers neutral - Poor: Customers unhappy or high churn Constructed investor scorecard output (not a funding recommendation): Investment decision boundary: Do not map an illustrative score to “fund,” “pass,” or a probability of success. Define the target investor's actual decision authority, evidence rule, downside case, governance limits, alternatives, and approval path; a score can organize questions but cannot substitute for that review. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-6a-investor-decision-questions-beyond-a-scorecard", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "6A. Investor-Decision Questions Beyond a Scorecard", "headingId": "chapter-15-fundraising-and-finance-6a-investor-decision-questions-beyond-a-scorecard", "url": "#chapter-15-fundraising-and-finance-6a-investor-decision-questions-beyond-a-scorecard", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Purpose: Examine investor economics, portfolio construction, selection, valuation, contracting, monitoring, and exit as questions rather than universal hidden rules. Empirical research documents venture-capital decision practices, but it does not justify stereotypes, fabricated fund facts, or one weight set for all investors. [BB-C15-S06] Constructed comparison boundary: Every fund size, check, ownership target, probability, timeline, quote, and behavior below is a teaching scenario. Verify the target fund's current thesis, people, reserves, conflicts, decision authority, and documents directly." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-1-fund-economics-portfolio-construction-illustrative-weighting-example", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "1. Fund Economics & Portfolio Construction (illustrative weighting example) ", "headingId": "chapter-15-fundraising-and-finance-1-fund-economics-portfolio-construction-illustrative-weighting-example", "url": "#chapter-15-fundraising-and-finance-1-fund-economics-portfolio-construction-illustrative-weighting-example", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative investor claim to test: \"We invest in great teams solving big problems.\" Possible mechanisms to test: - Fund size dynamics: Fund size, ownership targets, reserves, stage, follow-on policy, and portfolio construction influence feasible check sizes. Confirm the current mandate with the investor instead of inferring a universal range from fund size alone. - Ownership targets: Many VCs underwrite to a target ownership position; if your valuation does not allow that ownership at their check size, they may pass. - Portfolio construction: A fund may have a planned portfolio count, reserves, category exposure, and follow-on policy. Verify the current portfolio and mandate instead of applying a universal investment count. - Fund vintage: Vintage, reserves, deployment pace, follow-on policy, portfolio exposure, and current authority may affect attention or capacity; verify the actual fund rather than applying a Year 1–2 or Year 7–8 rule. Example: How to Use This: - Research fund size before pitching (use PitchBook, Crunchbase) - Calculate if your raise size matches their typical check - Ask: \"What's your typical ownership target at our stage?\" - Filter out mismatched investors early (saves everyone time) Red Flag: VC says \"We love it but the check size doesn't work for us\" = their fund economics don't match your raise, nothing to do with quality. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-2-narrative-fit-with-firm-s-thesis-illustrative-weighting-example", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "2. Narrative Fit with Firm's Thesis (illustrative weighting example) ", "headingId": "chapter-15-fundraising-and-finance-2-narrative-fit-with-firm-s-thesis-illustrative-weighting-example", "url": "#chapter-15-fundraising-and-finance-2-narrative-fit-with-firm-s-thesis-illustrative-weighting-example", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative investor claim to test: \"We're thesis-driven investors focused on [sector].\" Possible mechanisms to test: - Recent experience can shape attention: Treat a firm's recent category outcome as a hypothesis about interest or caution. Ask about the current thesis, conflicts, lessons, and decision criteria rather than assuming an exit creates enthusiasm. - Avoiding recent losses: If firm lost money on similar company (e.g., invested in 3 failed SaaS companies), they're gun-shy regardless of your metrics. - Partner specialization: Individual partner has sector expertise and needs wins in that area to maintain credibility within firm. You're helping their internal politics. - LP storytelling: VCs need to tell LPs (their investors) coherent narrative. If they can pitch you as \"Next wave of AI infrastructure\" or \"Enterprise SaaS 2.0,\" you fit their fundraising story. Example: How to Use This: - Read VC's recent blog posts, podcasts, thesis statements - Mirror their language in pitch (\"We're the AI-native data platform\" vs. \"We're a data integration tool\") - Reference their portfolio companies positively (\"Like DataForge, but for X\") - Position your company as validation of their thesis (not exception to it) Operator boundary: Narrative fit can affect attention and interpretation, but it does not replace operating evidence. The relevant balance between story, metrics, governance, and risk is stage-, investor-, and transaction-specific. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-3-founder-investor-interpersonal-dynamics-illustrative-weighting-example", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "3. Founder-Investor Interpersonal Dynamics (illustrative weighting example) ", "headingId": "chapter-15-fundraising-and-finance-3-founder-investor-interpersonal-dynamics-illustrative-weighting-example", "url": "#chapter-15-fundraising-and-finance-3-founder-investor-interpersonal-dynamics-illustrative-weighting-example", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative investor claim to test: \"We invest in founders we can work with for 7-10 years.\" Possible mechanisms to test: - Social proof: A trusted referral may affect access or attention for some processes, but it does not establish credibility, demand, or a financing outcome. - Founder-role fit: An investor may evaluate the capabilities and decision rights required for the role; do not treat a preferred founder archetype as a universal standard. - Communication and coachability: Investors may assess how a team handles evidence, disagreement, and feedback; define the observable behavior and avoid turning it into a personality test. - Working relationship: Board interaction, incentives, governance, and communication may matter alongside credentials; test the actual relationship rather than assuming chemistry overrides evidence. Example: How to Use This: - Practice \"confident humility\" (have strong opinions, loosely held) - Ask investor for advice during pitch (\"What would you do about X?\") then engage thoughtfully - Show you've incorporated prior feedback (\"After talking to Northstar Ventures, we added this slide\") - Demonstrate self-awareness (\"Our weakness is go-to-market; we need help there\") - Build rapport early (coffee before formal meeting, ask about their background) Operator warning: Treat a team concern as an ambiguous signal to clarify. Ask which observable capability, governance, communication, or evidence gap is decision-relevant; do not infer motive or assume metrics cannot change the assessment. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-4-traction-relative-to-valuation-illustrative-weighting-example", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "4. Traction Relative to Valuation (illustrative weighting example) ", "headingId": "chapter-15-fundraising-and-finance-4-traction-relative-to-valuation-illustrative-weighting-example", "url": "#chapter-15-fundraising-and-finance-4-traction-relative-to-valuation-illustrative-weighting-example", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative investor claim to test: \"We need to see strong traction.\" Possible mechanisms to test: - Valuation context: Investors may interpret operating evidence relative to price, risk, ownership, rights, market conditions, and expected outcomes. Do not label the same revenue level \"great\" or \"terrible\" without the full deal context. - Growth and scale: An investor may weigh growth, revenue quality, retention, cash, price, rights, risk, and stage differently; neither growth rate nor revenue is universally primary. - Customer evidence quality: A referenceable customer in the target segment may provide stronger evidence than a larger count of poorly matched accounts, but the value depends on revenue quality, retention, concentration, representativeness, contract terms, and the investor's thesis. Do not infer validation from a prestigious logo alone. - Renewals and new logos: Renewal, expansion, new-customer quality, concentration, and attribution are evidence to compare—not a fixed hierarchy. Example: How to Use This: - Relate valuation arguments to evidence, risk, comparable instruments, ownership and rights, market conditions, and scenario outcomes; avoid celebrity analogies. - Lead with growth rate, not absolute revenue - Identify referenceable customers only with permission and accurate context; prestige alone is not evidence of demand or validation. - Show unit economics improving (CAC going down, LTV going up) - Demonstrate momentum (\"Last 3 months we accelerated from 20 percent to 50 percent MoM\") Decision boundary: Compare evidence, price, rights, cash need, alternatives, and downside scenarios together. Neither “low traction at a reasonable valuation” nor “high traction at an unreasonable valuation” is a universal outcome rule. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-1-passion-and-mission", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "1. \"Passion\" and \"Mission\"", "headingId": "chapter-15-fundraising-and-finance-1-passion-and-mission", "url": "#chapter-15-fundraising-and-finance-1-passion-and-mission", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative investor claim to test: \"We invest in founders passionate about the problem.\" Decision boundary: Treat passion, domain experience, customer understanding, and commitment as distinct hypotheses. Test observable evidence and role requirements rather than treating a tenure or identity signal as a universal rule. Possible context: In some customer or domain settings, lived or professional experience may improve understanding; verify that mechanism and do not infer it from identity alone. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-2-unique-technology", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "2. \"Unique Technology\"", "headingId": "chapter-15-fundraising-and-finance-2-unique-technology", "url": "#chapter-15-fundraising-and-finance-2-unique-technology", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative investor claim to test: \"We look for unique IP and technological moats.\" Decision boundary: Technology, distribution, service design, timing, regulation, capital, and network structure can each matter. Do not infer a general rule from named-company origin stories without verified, as-of evidence that isolates the mechanism. Possible context: In some deep-tech settings, patents, know-how, regulatory barriers, or R&D timelines may matter; test the mechanism, enforceability, and alternatives. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-3-total-addressable-market-tam", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "3. \"Total Addressable Market (TAM)\"", "headingId": "chapter-15-fundraising-and-finance-3-total-addressable-market-tam", "url": "#chapter-15-fundraising-and-finance-3-total-addressable-market-tam", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Possible investor question: \"Is the reachable market and expansion path large enough for this fund's return model?\" More defensible response: Top-down TAM can create false precision. Reconcile external market estimates with reachable buyers, buying frequency, price, adoption constraints, competition, and expansion paths. Different investors weigh near-term reachability and long-term scope differently. Example: - Bad TAM: \"$500B healthcare market × 2 percent = $10B TAM\" (meaningless) - Constructed bottom-up market statement: \"150K data engineers × $10K assumed annual tool spend = $1.5B SAM; separately test whether 50K are reachable within five years\" ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-4-product-market-fit", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "4. \"Product-Market Fit\"", "headingId": "chapter-15-fundraising-and-finance-4-product-market-fit", "url": "#chapter-15-fundraising-and-finance-4-product-market-fit", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative investor claim to test: \"We invest when we see strong product-market fit.\" Decision boundary: Product-market fit is a multi-signal, segment-specific hypothesis. Ask which customer outcomes, repeat behavior, willingness to pay, retention, alternatives, and uncertainty would change the financing decision. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-tactic-1-coordinate-a-transparent-process-without-manufacturing-fomo", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Tactic 1: Coordinate a Transparent Process (without manufacturing FOMO)", "headingId": "chapter-15-fundraising-and-finance-tactic-1-coordinate-a-transparent-process-without-manufacturing-fomo", "url": "#chapter-15-fundraising-and-finance-tactic-1-coordinate-a-transparent-process-without-manufacturing-fomo", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "How: Run a coordinated process when multiple investors are genuinely evaluating the opportunity, while preserving confidentiality and accurate disclosure. Why: A clear process can reduce uncertainty about timing and decision rights, but another investor's interest does not prove quality, create an obligation, or guarantee a better outcome. Execution: - Coordinate meetings around the runway, operating workload, and each investor's decision process; do not compress diligence merely to create urgency. - Disclose other investor activity only when accurate, authorized, non-confidential, and decision-relevant. - Use deadlines only when they are real, documented, and consistent with the transaction and approvals. - Describe interest levels precisely; distinguish an inquiry, meeting, diligence request, term sheet, and approved commitment. Warning: Do not bluff, misrepresent interest, or disclose another party's confidential information. A manufactured process can create legal, reputational, and governance risk. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-tactic-2-leverage-partner-dynamics", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Tactic 2: Leverage Partner Dynamics", "headingId": "chapter-15-fundraising-and-finance-tactic-2-leverage-partner-dynamics", "url": "#chapter-15-fundraising-and-finance-tactic-2-leverage-partner-dynamics", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "How: Identify the person with actual decision authority or sponsorship responsibility and build a professional relationship through accurate, permitted communication. Why: Decision structures differ. Understanding who evaluates, recommends, approves, and governs the investment is more useful than assuming a single champion or voting pattern. Execution: - Research which partner covers your sector (look at their LinkedIn, blog posts, portfolio) - Ask for intro to that partner specifically (not generic firm email) - Build rapport over multiple conversations (coffee, not just pitch meetings) - Ask partner to champion you internally: \"If you're excited, what would it take to bring this to partners?\" Example: ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-tactic-3-use-early-no-s-to-improve-pitch", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Tactic 3: Use Early \"No's\" to Improve Pitch", "headingId": "chapter-15-fundraising-and-finance-tactic-3-use-early-no-s-to-improve-pitch", "url": "#chapter-15-fundraising-and-finance-tactic-3-use-early-no-s-to-improve-pitch", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "How: Sequence conversations so early feedback can improve the materials without treating any investor as disposable or disclosing beyond the approved boundary. Why: Early feedback can expose ambiguity, unsupported claims, or missing evidence. The number and order of conversations should reflect the opportunity cost, access, confidentiality, and runway. Execution: - Prioritize investors by evidence-based fit, access, capacity, conflicts, and decision timing. - Sequence outreach to protect scarce relationships and allow useful iteration; do not label any investor as a practice target. - After each meeting, update pitch based on questions, objections, confusion - Hit top-tier investors after 10-15 practice meetings (pitch refined) Pattern Recognition: - If 5 VCs ask same question → add slide addressing it proactively - If 3 VCs confused by same point → simplify that explanation - If 2 VCs expressed same concern → address it in pitch (don't wait for them to ask) ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-tactic-4-signal-insider-knowledge", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Tactic 4: Signal Insider Knowledge", "headingId": "chapter-15-fundraising-and-finance-tactic-4-signal-insider-knowledge", "url": "#chapter-15-fundraising-and-finance-tactic-4-signal-insider-knowledge", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "How: Demonstrate you understand VC economics and fund dynamics. Why: Sophisticated founders get better terms. VCs respect founders who understand the game. Execution: - Ask about fund vintage: \"When did you raise your current fund?\" (tells you if they're deploying) - Ask about portfolio concentration: \"How many data infrastructure companies do you have?\" (tells you if you fit) - Reference VC economics: \"I know you underwrite to ownership targets at Series A\" (shows you understand their model) - Acknowledge trade-offs: \"We're happy to give up board seat for the right partner\" (shows you know what matters) Example: ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-the-unspoken-rejection-reasons", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "The Unspoken Rejection Reasons", "headingId": "chapter-15-fundraising-and-finance-the-unspoken-rejection-reasons", "url": "#chapter-15-fundraising-and-finance-the-unspoken-rejection-reasons", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "When VCs pass, they rarely tell you the real reason. Here's how to decode their responses: Table 15.5: Author-created or source-bounded decision aid (What VC Says | Possible interpretations to test | What to Do ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | What VC Says | Possible interpretations to test | What to Do| | :--- | :--- | :---| | \"Too early for us\" | Could indicate stage, evidence, ownership, mandate, capacity, or timing mismatch | Ask what observable evidence or timing would justify reconsideration; do not assume a universal revenue threshold | | \"We're not sure about the market\" | The reachable demand, evidence, competitive position, timing, or return case remains unresolved | Ask which evidence would change the view; sharpen the analysis where supported | | \"We'd love to see more traction\" | Operating evidence, price, rights, risk, or stage fit may not support the decision yet | Ask for the decision-relevant gap; do not assume a universal metric fix | | \"The timing isn't right for us\" | Mandate, capacity, conflicts, portfolio exposure, market conditions, or process timing may not fit | Clarify whether a dated re-engagement condition exists | | \"We have some concerns about the team\" | A capability, governance, communication, or evidence gap may be unresolved | Ask for the observable concern and compare mitigation options | | \"We need to see the next milestone\" | The investor wants additional evidence before using its authority or capacity | Define the milestone, owner, evidence rule, and whether it is actually decision-relevant | | \"The round is too small for us\" | Fund economics or decision authority may not fit the proposed amount | Confirm the mandate and compare a syndicate, different amount, or different investor | | \"We'll pass for now but stay in touch\" | The current fit or timing is insufficient; future interest is unknown | Ask whether a specific re-engagement condition exists and record the uncertainty | Operator's rule: Treat vague feedback as unresolved information, not a decoded rejection. Ask what observable evidence, timing, or fit issue drove the decision; if the investor will not clarify, record the uncertainty and allocate time to better-supported paths. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-when-to-walk-away-from-vc-money", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "When to Walk Away from VC Money", "headingId": "chapter-15-fundraising-and-finance-when-to-walk-away-from-vc-money", "url": "#chapter-15-fundraising-and-finance-when-to-walk-away-from-vc-money", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Scenario 1: Valuation Is Too Low ( 30 percent Below Your Target) If VCs are consistently offering $15M valuations when you wanted $25M+, either: 1. Your valuation expectations are unrealistic (recalibrate) 2. Your traction doesn't justify that valuation (build more) 3. Market has shifted (recent competitor failure, macro downturn) Action in this constructed scenario: Either accept the modeled lower valuation if the cash need and full terms justify it, or improve the specific evidence gap and retry when the local decision rule is met; no calendar interval is universal. Operator's Take: Compare valuation with dilution, rights, control, downside protection, cash need, milestones, financing alternatives, and the consequences of no deal. Survival matters, but accepting a lower valuation is not automatically preferable; model the actual alternatives with counsel and finance reviewers. --- Scenario 2: Term Sheet Has Aggressive Terms (2x Liquidation Pref, Full Ratchet Anti-Dilution) If investor insists on founder-unfavorable terms: - A 2x liquidation preference specifies a preference amount based on two times the defined investment base, subject to the instrument's participation, seniority, conversion, cap, dividend, and distribution terms. Model the actual documents with counsel. [BB-C15-S08] [BB-C15-S09] - Full ratchet anti-dilution (if next round is down, your shares get hammered) - Excessive board control (investor controls majority of board) Action: Model the actual terms, seek qualified counsel, compare feasible alternatives, and walk away when the package violates the approved economic, governance, legal, or downside boundary. Terms alone do not prove what an investor believes. Operator's take: Terms can materially affect future rounds, governance, and exit proceeds. Compare the complete package with bootstrapping, debt, revenue, staged spending, and no-deal scenarios; no financing path is automatically safer. --- Scenario 3: Investor Adds No Value Beyond Capital If investor can't answer \"How will you help us beyond money?\" with concrete examples: - Customer introductions - Hiring help (executive recruiting) - Strategic guidance (seen this movie before) - Next round fundraising (connections to Series B investors) Action: Choose different investor who brings real value-add. Operator's take: Capital, governance, access, conflicts, and value-add should be evaluated separately. Choose the complete package and accountable relationship—not a label alone. --- Scenario 4: You Don't Need the Money If you're profitable or can reach profitability with current cash: - Consider not raising at all (retain ownership) - Consider raising smaller amount (revenue-based financing, venture debt) - Consider raising from strategics (corporate investors who can be customers) Action: Run the math: Is the proposed capital worth its dilution, rights, obligations, and downside exposure compared with the no-raise and alternative-capital scenarios? Use company-specific operating assumptions rather than a universal growth or dilution claim. Operator's take: External capital and retained ownership can each be useful or harmful depending on the operating plan, risk, governance, liquidity, and stakeholder objectives. Choose from the modeled alternatives rather than from a slogan. --- Cross-Reference: - For a structured challenge to portfolio-construction assumptions, see Appendix B: Contrarian Business Perspectives, Perspective 20. - For financial modeling of dilution scenarios, see Section 5: Cap Table Scenarios & Dilution below - For financing and no-raise comparison, see Section 11: Financing and No-Raise Decision Framework" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers-6", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers-6", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Compare investors on decision-relevant evidence, authority, fit, value-add, governance, confidentiality, conflicts, terms, and downside—not reputation alone. - Document the scoring rule, evidence quality, uncertainty, and who owns the relationship and approval decision. - Keep multiple feasible paths open without overstating investor interest or treating a meeting as a financing commitment." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques-6", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques-6", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Research findings from a sample, fund, stage, or sector do not establish universal investor criteria or funding odds. - Fit scores can encode proxy bias, survivorship, access differences, and unobserved bargaining power. - Investor value-add, references, and stated intentions require verification and may change with the actual deal and portfolio context." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections-6", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections-6", "url": "#chapter-15-fundraising-and-finance-connections-6", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Process: Use Framework 1 for sequencing and decision authority. - Terms: Use Frameworks 3–5 and 10 for valuation, rights, dilution, and instrument consequences. - Diligence and alternatives: Use Frameworks 7, 8, and 11 for disclosure, cash, and no-raise paths. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview-7", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview-7", "url": "#chapter-15-fundraising-and-finance-overview-7", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The due-diligence checklist is an author-created disclosure and evidence index for a defined transaction. It is not complete or standard, and it does not authorize disclosure, waive privilege, or replace counsel, privacy, security, tax, accounting, employment, export, antitrust, or records review." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply-7", "url": "#chapter-15-fundraising-and-finance-how-to-apply-7", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Assign an owner, source, date, confidentiality class, privilege status, permitted recipient, validation method, and escalation route to every request. Share only what the actual process and approvals permit; reconcile claims to primary records and record unresolved gaps before any readiness decision. Provenance and purpose: This is an author-created starting checklist, not a complete or standard diligence request. Prepare a controlled disclosure index for the actual process. Scope, privilege, confidentiality, privacy, customer/employee consent, export, security, antitrust, securities-law, and record-retention decisions belong to counsel and the responsible data owners; a checklist does not authorize disclosure. The categories, sequencing, timing, and readiness labels below must be tailored to the transaction, jurisdiction, stage, and counterparty. Illustrative Due Diligence Request Index (timing varies):" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-corporate-legal", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Corporate / Legal", "headingId": "chapter-15-fundraising-and-finance-corporate-legal", "url": "#chapter-15-fundraising-and-finance-corporate-legal", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Certificate of incorporation + bylaws - [ ] Cap table (fully diluted with options) - [ ] Equity documents (founder vesting, option agreements, and any applicable tax elections such as a U.S. 83(b) election) - [ ] Major contracts (customer contracts, vendor agreements) - [ ] Litigation (any lawsuits?) + Legal issues - [ ] IP assignment agreements (who owns the code?) - [ ] Trademark/patent applications (status) - [ ] Board resolutions (document major decisions) - [ ] Employment, compensation, invention-assignment, confidentiality, and equity documents reviewed for the applicable roles and jurisdictions" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-financial", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Financial", "headingId": "chapter-15-fundraising-and-finance-financial", "url": "#chapter-15-fundraising-and-finance-financial", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Audited / reviewed financial statements (last 3 years) - [ ] Monthly P&L (last 12 months) - [ ] Bank statements (demonstrate actual revenue, not inflated) - [ ] Cap table history (show all funding rounds) - [ ] Financial projections (detailed 5-year model with assumptions) - [ ] Tax documents required for the entity, tax classification, jurisdiction, and transaction (for example, Form 1120 only where applicable) - [ ] Debt agreements (any debt instruments?) - [ ] Insurance certificates (liability, directors & officers)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-operations", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Operations", "headingId": "chapter-15-fundraising-and-finance-operations", "url": "#chapter-15-fundraising-and-finance-operations", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Detailed organizational chart - [ ] Employee roster with compensation, start dates, vesting schedules - [ ] Customer list (names, ARR per customer, churn rate) - [ ] Product roadmap (next 12-24 months) - [ ] Technical architecture (how is product built? Cloud, databases, etc.) - [ ] Security & compliance (any SOC 2? Data security practices?) - [ ] Vendor agreements (who are critical vendors? Contracts?) - [ ] Insurance policies" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-sales-marketing", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Sales & Marketing", "headingId": "chapter-15-fundraising-and-finance-sales-marketing", "url": "#chapter-15-fundraising-and-finance-sales-marketing", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Customer testimonials / case studies - [ ] Logo references (customer logos, with permission) - [ ] Sales process documentation - [ ] Customer acquisition cost analysis - [ ] Customer lifetime value calculation - [ ] Churn analysis (monthly/annual, reasons) - [ ] Pipeline analysis (potential customers, probability) - [ ] Pricing history (have you raised prices? How did customers react?)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-reference-contacts", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Reference Contacts", "headingId": "chapter-15-fundraising-and-finance-reference-contacts", "url": "#chapter-15-fundraising-and-finance-reference-contacts", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- [ ] Customer reference list (5-10 customers investor can call) - [ ] Partner / vendor references - [ ] Board member/advisor references Illustrative Readiness Checks Before Due Diligence: 1. Clean cap table: All founder equity properly documented, no surprises 2. IP assigned: All code/IP clearly owned by company, not founders 3. Audited numbers: Financial statements should be consistent with bank records 4. Clean customer contracts: Terms clear, customers happy (no bad contracts) 5. No litigation: No ongoing lawsuits or IP disputes If There Are Issues: - IP ambiguity: Get assignment agreement from person who owns it - Equity discrepancies: Reconcile cap table with option pool - Financial discrepancies: Explain difference between accounting and bank records - Unhappy customer: Call customer + understand issue Red Flags That Sink Deals: - Founder ownership or commitment appears misaligned with the actual role, vesting, governance, and operating plan; do not infer commitment from a universal percentage rule - IP not cleanly assigned (company might not own product) - Financial statements don't match reality (major red flag) - Material customer churn (customers secretly unhappy) - Founder conflict (founders fighting = messy process)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers-7", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers-7", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Treat each request as an evidence, permission, confidentiality, privacy, security, or legal-control decision with an owner and source. - Reconcile disclosures to primary records and document gaps, exceptions, remediation, and recipient permissions before readiness claims. - Escalate inconsistencies involving solvency, securities, employment, IP, customers, data, tax, accounting, export, antitrust, or safety." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques-7", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques-7", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- No checklist is complete or a substitute for transaction-specific diligence, professional judgment, privilege, consent, or approval. - “Clean” labels and red flags require defined evidence and context; they are not universal thresholds or conclusions about people. - Disclosure can create customer, employee, privacy, security, confidentiality, competition, and reputational harm if unmanaged." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections-7", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections-7", "url": "#chapter-15-fundraising-and-finance-connections-7", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Cap table and terms: Use Frameworks 4 and 5 to verify rights, ownership, and records. - Financial model: Use Framework 8 to reconcile statements, cash, debt, and forecasts. - Acquisition and governance: Use Framework 9, the applied ETA section below, Chapter 2, and qualified legal, tax, accounting, privacy, security, and employment owners. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview-8", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview-8", "url": "#chapter-15-fundraising-and-finance-overview-8", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The three-statement financial model template is a constructed teaching model connecting income statement, balance sheet, cash flow, runway, financing, working capital, tax, debt, and sensitivity. It is not accounting policy, a forecast, a valuation, or a venture benchmark." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply-8", "url": "#chapter-15-fundraising-and-finance-how-to-apply-8", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define opening balances, accounting basis, period consistency, collections, costs, working capital, taxes, debt, financing, and scenario assumptions. Reconcile the statements and cash movement, compare actuals to the model, and obtain qualified finance/accounting review before using outputs for financing or solvency decisions. Provenance and purpose: This is an author-created teaching template. The income statement, balance-sheet snapshot, and partial cash-flow schedule below are separate constructed slices—not a complete linked forecast. The values are fictional, not a standard forecast, accounting policy, or venture benchmark; qualified finance/accounting owners must supply opening balances, full-period cash rollforwards, tax, debt, working capital, financing, and retained-earnings links before relying on any output. Reconciliation status: The displayed tables intentionally do not claim to reconcile across periods: the income statement spans five years, the balance sheet shows selected year-end snapshots, and the cash-flow table covers only January through June. Treat them as worksheet components. A usable model must link net income to retained earnings, cash collections and working capital to the balance sheet, financing and investing flows to cash, and tax/debt assumptions to the statements before a financing, solvency, or valuation decision. Three Statements: 1. Income Statement: Revenue - Expenses = Profit (or loss) 2. Balance Sheet: Assets = Liabilities + Equity 3. Cash Flow: How much cash actually moving in/out (different from profit)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-income-statement-5-year-projection", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Income Statement (5-Year Projection)", "headingId": "chapter-15-fundraising-and-finance-income-statement-5-year-projection", "url": "#chapter-15-fundraising-and-finance-income-statement-5-year-projection", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Template: Table 15.6: Author-created or source-bounded decision aid (Item | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Item | Year 1 | Year 2 | Year 3 | Year 4 | Year 5| | :--- | :--- | :--- | :--- | :--- | :---| | REVENUE | | Customers | 20 | 60 | 200 | 500 | 1,200 | | ARPU ($ per customer/year) | $50K | $55K | $60K | $65K | $70K | | Total Revenue | $1M | $3.3M | $12M | $32.5M | $84M | | COSTS OF GOODS SOLD (COGS) | | Cloud infrastructure | $100K | $300K | $1M | $2M | $4M | | Payment processing (2 percent of revenue) | $20K | $66K | $240K | $650K | $1.68M | | Gross Profit | $880K | $2.93M | $10.76M | $29.85M | $78.32M | | Gross Margin % | 88 percent | 89 percent | 90 percent | 92 percent | 93 percent | | OPERATING EXPENSES | | Sales & Marketing | $400K | $900K | $2.4M | $4.9M | $8.4M | | R&D | $200K | $500K | $1.2M | $1.9M | $2.5M | | General & Admin | $150K | $300K | $600K | $1M | $1.5M | | Total OpEx | $750K | $1.7M | $4.2M | $7.8M | $12.4M | | EBITDA | $130K | $1.23M | $6.56M | $22.05M | $65.92M | | EBITDA Margin % | 13 percent | 37 percent | 55 percent | 68 percent | 78 percent | | Depreciation | $10K | $20K | $30K | $40K | $50K | | Interest | $0 | $0 | $0 | $0 | $0 | | NET INCOME | $120K | $1.21M | $6.53M | $22M | $65.87M | | Net Margin % | 12 percent | 37 percent | 54 percent | 68 percent | 78 percent | Key Assumptions (document these): - Customer growth: 200 percent Y1→Y2, 233 percent Y2→Y3, 150 percent Y3→Y4, 140 percent Y4→Y5 - ARPU growth: 10 percent annually (as customer quality improves) - COGS as % revenue: 12 percent (improves with scale) - Gross margin: The model assumes SaaS-like high gross margins - OpEx: Scales with revenue but not 1:1 (operating leverage) - Path to profitability: Year 3 in this constructed scenario; it is not presented as typical" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-balance-sheet-illustrative-year-end-snapshot", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Balance Sheet (Illustrative Year-End Snapshot)", "headingId": "chapter-15-fundraising-and-finance-balance-sheet-illustrative-year-end-snapshot", "url": "#chapter-15-fundraising-and-finance-balance-sheet-illustrative-year-end-snapshot", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 15.7: Author-created or source-bounded decision aid (Asset | Year 1 | Year 5 ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Asset | Year 1 | Year 5| | :--- | :--- | :---| | ASSETS | | Cash | $3M | $20M | | Accounts receivable (customer invoices not yet paid) | $100K | $2M | | Other current assets | $50K | $200K | | Total Current Assets | $3.15M | $22.2M | | PP&E (equipment, servers) | $50K | $200K | | Intangible assets | $0 | $0 | | Total Assets | $3.2M | $22.4M | | LIABILITIES | | Accounts payable (money owed to vendors) | $50K | $500K | | Other payables | $25K | $200K | | Total Current Liabilities | $75K | $700K | | Long-term debt | $0 | $0 | | Total Liabilities | $75K | $700K | | EQUITY | | Contributed capital (funding raised) | $5M | $5M | | Retained earnings (accumulated profits) | ($1.875M) | $16.7M | | Total Equity | $3.125M | $21.7M | | Total Liabilities + Equity | $3.2M | $22.4M | Note: Do not omit the balance sheet. Even an early-stage model must reconcile cash, working capital, debt, contributed capital, retained earnings, and other material assets and obligations across all three statements." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-cash-flow-statement-illustrative-partial-year-slice", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Cash Flow Statement (Illustrative Partial-Year Slice)", "headingId": "chapter-15-fundraising-and-finance-cash-flow-statement-illustrative-partial-year-slice", "url": "#chapter-15-fundraising-and-finance-cash-flow-statement-illustrative-partial-year-slice", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 15.8: Author-created or source-bounded decision aid (Month | Jan | Feb | Mar | Apr | May | Jun ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Month | Jan | Feb | Mar | Apr | May | Jun| | :--- | :--- | :--- | :--- | :--- | :--- | :---| | Operating Cash | | Customers | 2 | 2 | 3 | 3 | 4 | 6 | | Revenue (cash collected) | $100K | $100K | $150K | $150K | $200K | $300K | | COGS paid | -$15K | -$15K | -$20K | -$20K | -$25K | -$35K | | OpEx paid | -$65K | -$65K | -$70K | -$70K | -$75K | -$85K | | Operating Cash Flow | $20K | $20K | $60K | $60K | $100K | $180K | | Investing Cash | | Equipment purchase | $0 | $0 | -$5K | $0 | $0 | $0 | | Investing Cash Flow | -$0K | -$0K | -$5K | -$0K | -$0K | -$0K | | Financing Cash | | Funding round | $5M | $0 | $0 | $0 | $0 | $0 | | Financing Cash Flow | $5M | -$0K | -$0K | -$0K | -$0K | -$0K | | Net Cash Change | $5.02M | $20K | $55K | $60K | $100K | $180K | | Ending Cash | $5.02M | $5.04M | $5.095M | $5.155M | $5.255M | $5.435M | Key Metric: Monthly cash burn rate (money leaving company per month) - In this constructed January row, operating receipts exceed the listed operating payments by $35K; do not generalize that pattern or call it burn without a declared cash-flow definition. - Do not call a burn trajectory \"typical.\" Model collections, costs, working capital, financing, seasonality, and downside cases from the venture's own evidence. - Runway = Cash on hand / Monthly burn rate (how many months until out of money) Using the Model: - Show investors your assumptions are reasonable - Run scenarios: What if growth is 50 percent slower? (Sensitivity analysis) - Use to forecast when you'll need next fundraising round - Compare actuals to forecast monthly (track if on target)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers-8", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers-8", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Reconcile the three statements, opening balances, working capital, financing, debt, taxes, and cash before relying on runway or solvency outputs. - Use base, downside, and upside scenarios with named assumptions, owners, observation periods, and decision triggers. - Compare actuals to the model and investigate variance rather than treating the forecast as evidence of future performance." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques-8", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques-8", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A constructed model can be internally consistent and still be wrong about demand, collections, costs, taxes, capital availability, or survival. - EBITDA, revenue, gross margin, and runway are not interchangeable with cash, CADS, valuation, or debt-service capacity. - Accounting policy, financing documents, tax, and lender/investor definitions can change the required model structure." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections-8", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections-8", "url": "#chapter-15-fundraising-and-finance-connections-8", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Valuation and dilution: Use Frameworks 3–5 for price, ownership, rights, and proceeds. - Capital choice: Use Frameworks 9–11 for liquidity, instruments, and no-raise alternatives. - Operating evidence: Use Chapters 4, 13, 14, and 22 for finance, venture, GTM, and scenario analysis. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview-9", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview-9", "url": "#chapter-15-fundraising-and-finance-overview-9", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The exit, liquidity, and continuation framework compares acquisition, IPO/direct listing, secondary, recapitalization, repurchase, continued private ownership, restructuring, and wind-down as decision paths. Headline transaction value is not founder/investor proceeds, and no path has a universal frequency, multiple, timeline, or prerequisite. [BB-C15-S11]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply-9", "url": "#chapter-15-fundraising-and-finance-how-to-apply-9", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Start with the actual securities, debt, authority, fiduciary, tax/accounting, employment, competition, customer, and transaction documents. Model distributable proceeds, senior deductions, preferences, conversion, participation, residual allocation, and stakeholder outcomes; state what evidence would justify continuation, revision, pause, or exit. Purpose: Compare strategic acquisition, IPO, secondary liquidity, recapitalization, buyback, continued private ownership, restructuring, and shutdown without treating headline transaction value as investor or founder proceeds. Contract terms can influence exit choices and outcomes; each case requires the actual securities, debt, authority, fiduciary duties, market evidence, tax, accounting, competition, employment, and transaction documents. [BB-C15-S11] No option has a universal frequency, multiple, timeline, return, founder-control result, or company-size prerequisite. The prior named-company examples and fixed ranges were removed because the chapter had no adjacent current transaction evidence. Table 15.9: Author-created or source-bounded decision aid (Option | Decision questions ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Option | Decision questions| | :--- | :---| | Strategic acquisition | Strategic fit, alternatives, buyer capacity, price and form, debt, preferences, rollover, earnout, escrow, approvals, competition review, employee/customer outcomes, integration, and walk-away terms | | IPO/direct listing | Market and issuer readiness, audited reporting, controls, governance, underwriting/listing path, dilution, lockups, liquidity, disclosure, costs, and continuing public obligations | | Secondary sale or recapitalization | Eligible sellers, transfer restrictions, rights of first refusal/co-sale, pricing, information parity, tax, tender rules, concentration, governance, and primary versus secondary cash | | Company repurchase | Statutory authority, solvency, board/shareholder approval, price/fairness, tax/accounting, financing, creditor and remaining-holder effects | | Continued private ownership | Cash needs, governance, investor horizon, distributions, employee liquidity, financing access, strategic options, and concentration risk | | Down round or restructuring | Price per share, recapitalization, anti-dilution, pay-to-play, debt, solvency, fiduciary process, employee equity, disclosure, alternatives, and future financing | | Wind-down | Solvency, board/shareholder authority, creditor priority, employee/customer obligations, data/IP, tax, records, insurance, regulator notice, and remaining-asset distribution | Proceeds method: Begin with distributable transaction value after debt, fees, escrow, and other senior deductions; apply security seniority, preferences, dividends, conversion, and participation/caps; allocate residual proceeds; then model tax and vesting. Reconcile all distributions to total distributable proceeds and obtain counsel plus tax/accounting review." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers-9", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers-9", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Compare liquidity and continuation paths from actual rights, obligations, authority, solvency, stakeholder outcomes, and alternatives. - Model distributable proceeds security by security and state what would make continuation, restructuring, pause, or wind-down responsible. - Treat buyer interest, headline value, IPO readiness, and secondary demand as evidence questions rather than outcomes." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques-9", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques-9", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A transaction value is not automatically cash to founders, employees, investors, or creditors. - Exit paths can create tax, accounting, employment, competition, fiduciary, customer, data, and creditor obligations. - Market frequency, multiples, timelines, and control outcomes vary materially by jurisdiction, sector, security, cycle, and documents." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections-9", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections-9", "url": "#chapter-15-fundraising-and-finance-connections-9", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Terms and cap table: Use Frameworks 4 and 5 for rights and proceeds. - Cash and instruments: Use Frameworks 8 and 10 for debt, liquidity, conversion, and no-next-round cases. - Governance: Use Frameworks 7 and 11 plus Chapters 2 and 4 for diligence, authority, finance, and specialist review. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview-10", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview-10", "url": "#chapter-15-fundraising-and-finance-overview-10", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The SAFE and convertible-note decision boundary is a document-specific modeling aid for future equity, debt, conversion, maturity, priority, cash, tax/accounting, and legal outcomes. Neither instrument family is inherently simple, suitable, founder-friendly, investor-friendly, or cheaper; the executed form and governing law control. [BB-C15-S13]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply-10", "url": "#chapter-15-fundraising-and-finance-how-to-apply-10", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Record the dated form, jurisdiction, capitalization definition, price/cap/discount, interest/maturity, conversion, liquidity/dissolution, amendment, priority, tax/accounting, and no-next-round terms. Model shares and proceeds under each applicable clause and obtain qualified counsel and tax/accounting review before choosing or circulating an instrument. Purpose: Understand how two financing document families can create future equity and different cash, maturity, conversion, priority, tax, accounting, and legal outcomes. Neither is inherently simple, founder-friendly, investor-friendly, suitable, or cheaper. The registered February 2023 Y Combinator guide supports mechanics for that version of the post-money SAFE forms. It does not establish legal suitability, tax/accounting treatment, market prevalence, or the terms of a different SAFE or note. [BB-C15-S13]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-convertible-note", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Convertible note", "headingId": "chapter-15-fundraising-and-finance-convertible-note", "url": "#chapter-15-fundraising-and-finance-convertible-note", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A convertible note is debt under its governing documents. Model principal, interest, maturity, repayment/default, security and priority, qualified-financing threshold, conversion price, valuation cap, discount, change of control, amendments, and tax/accounting treatment. The note does not necessarily convert only in a Series A, and maturity does not dictate one universal remedy." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-safe", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "SAFE", "headingId": "chapter-15-fundraising-and-finance-safe", "url": "#chapter-15-fundraising-and-finance-safe", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A SAFE is a contract for potential future equity, not a loan in the YC form. The exact form can include a valuation cap, discount, MFN, pro-rata side letter, or other provisions; do not assume every SAFE contains both cap and discount. Model equity-financing, liquidity, dissolution, amendment, and no-trigger outcomes from the signed version. “Post-money” describes the form's capitalization mechanics and does not make percentage ownership a one-line division." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-controlled-conversion-model", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Controlled conversion model", "headingId": "chapter-15-fundraising-and-finance-controlled-conversion-model", "url": "#chapter-15-fundraising-and-finance-controlled-conversion-model", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "1. Record the dated document version, jurisdiction, investor purchase amount, and every operative term. 2. Define company capitalization exactly as the document does, including options, promised options, SAFEs/notes, and other converting securities. 3. Calculate each applicable conversion price in shares; apply the document's selection and sequencing rules. 4. Add priced-round shares and any pool change, then reconcile the fully diluted capitalization to 100 percent. 5. Model liquidity, dissolution, maturity/default where applicable, tax/accounting, priority, consent, amendment, and a no-next-round scenario. 6. Have qualified counsel and tax/accounting advisers review the model against the executed documents. Table 15.10: Author-created or source-bounded decision aid (Question | Convertible note | SAFE ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Question | Convertible note | SAFE| | :--- | :--- | :---| | Legal form | Debt under the note and governing law | Contract for potential future equity under the form and governing law | | Time-based economics | Interest and maturity/default provisions can apply | YC form has no interest or maturity; other forms must be inspected | | Conversion | Defined by financing, maturity, change-of-control, or other clauses | Defined by equity-financing, liquidity, dissolution, or other clauses | | Priority/cash risk | Depends on security, subordination, repayment, insolvency, and conversion terms | Depends on liquidity/dissolution provisions and the capital structure | | Ownership calculation | Requires share-price and capitalization definitions | Requires the form's company-capitalization and post-money mechanics | | Decision | Compare complete documents, cash needs, downside, future financing, tax/accounting, governance, and alternatives | Same | Decision rule: Choose only after modeling both instruments and a priced-equity/no-raise alternative under downside scenarios. A cap or discount changes conversion economics; it is not a promise of a particular ownership percentage or return." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers-10", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers-10", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Start with the executed form, capitalization definition, document version, jurisdiction, and actual cash need—not an instrument stereotype. - Calculate conversion and liquidity outcomes in shares and proceeds, then reconcile the full capitalization and rights package. - Obtain qualified counsel and tax/accounting review before selecting, marketing, amending, or signing an instrument." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques-10", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques-10", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- A guide for one SAFE form/version does not establish suitability, prevalence, tax treatment, or the terms of another form or note. - Cap, discount, interest, maturity, conversion, priority, and pool definitions interact; headline percentages are unreliable shortcuts. - A modeled conversion does not establish future financing, liquidity, solvency, ownership value, or return." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections-10", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections-10", "url": "#chapter-15-fundraising-and-finance-connections-10", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Cap table: Use Framework 5 for fully diluted share and pool reconciliation. - Rights and valuation: Use Frameworks 3 and 4 for price, preferences, control, and proceeds. - Alternatives: Use Framework 11 and qualified legal/finance/tax reviewers for no-raise, debt, equity, and staged paths. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overview-11", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overview", "headingId": "chapter-15-fundraising-and-finance-overview-11", "url": "#chapter-15-fundraising-and-finance-overview-11", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The financing and no-raise decision framework compares operating cash, customer financing, grants, debt, partner/strategic capital, equity, staged combinations, and no-raise paths under uncertainty. It is a constructed decision aid, not a universal capital ladder or claim about speed, safety, control, founder wealth, or value. [BB-C15-S07] [BB-C15-S15]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-apply-11", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Apply", "headingId": "chapter-15-fundraising-and-finance-how-to-apply-11", "url": "#chapter-15-fundraising-and-finance-how-to-apply-11", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the cash need, milestone, downside, reversibility, capital availability, rights, covenants, dilution, governance, stakeholder effects, and option value for each feasible path. Reconcile cash, ownership, security rights, tax, and proceeds; choose, revise, pause, or stop from evidence and authorized review. Purpose: Compare operating cash flow, customer prepayment, grants, debt, partner or strategic capital, equity, and staged combinations under uncertainty. Neither venture capital nor bootstrapping is universally faster, safer, more controllable, or more valuable. Entrepreneurship is experimentation, and founder exposure can be highly nondiversified. [BB-C15-S07] [BB-C15-S15]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-decision-questions", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Decision questions", "headingId": "chapter-15-fundraising-and-finance-decision-questions", "url": "#chapter-15-fundraising-and-finance-decision-questions", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 15.11: Author-created or source-bounded decision aid (Dimension | Questions to resolve ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Dimension | Questions to resolve| | :--- | :---| | Capital need and timing | What evidence-backed cash requirement, milestone, contingency, and timing gap exists? Which expenditures are reversible or stageable? | | Economics and cash | How do contribution, working capital, burn, runway, covenants, repayment, dilution, and no-next-round scenarios compare? | | Risk allocation | Who bears technical, market, financing, insolvency, regulatory, and personal downside under each option? | | Governance and control | Which board, voting, consent, information, transfer, preference, and operating constraints accompany the actual instrument? | | Eligibility and feasibility | Are grants, debt, customer finance, partnerships, or equity genuinely available on acceptable terms? | | Market structure | Do scale effects, timing, capacity, or regulation change the value of capital? A competitive “arms race” narrative is not proof. | | Stakeholder outcomes | How are founders, employees, customers, suppliers, investors, and communities affected under upside and downside? | | Option value | What future choices does the path create, preserve, delay, or foreclose? |" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-scenario-method", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Scenario method", "headingId": "chapter-15-fundraising-and-finance-scenario-method", "url": "#chapter-15-fundraising-and-finance-scenario-method", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "As a constructed decision exercise, compare a no-raise path, feasible non-equity paths, a staged-equity path, and downside cases in which revenue is late and no later round occurs. Reconcile cash, ownership, security rights, option pools, preferences, taxes, and proceeds against the cap table and documents. Any displayed revenue, dilution, valuation, probability, or duration is an illustrative input—not a market benchmark or forecast. [BB-C15-S07] [BB-C15-S15] Choose the path whose risk-adjusted operating case is best supported by evidence and feasible terms, then define learning milestones and review conditions. A financing label does not establish speed, control, founder wealth, success probability, or strategic quality." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-so-what-for-managers-11", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "So What for Managers", "headingId": "chapter-15-fundraising-and-finance-so-what-for-managers-11", "url": "#chapter-15-fundraising-and-finance-so-what-for-managers-11", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Compare capital paths on cash need, downside, reversibility, rights, governance, dilution, covenants, stakeholder outcomes, and feasible terms. - Keep no-raise and alternative-capital options visible until the selected path is funded and its obligations are understood. - Define evidence milestones, review cadence, responsible owners, and pause/stop conditions before increasing exposure." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-limits-and-critiques-11", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Limits and Critiques", "headingId": "chapter-15-fundraising-and-finance-limits-and-critiques-11", "url": "#chapter-15-fundraising-and-finance-limits-and-critiques-11", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Capital availability, speed, cost, control, and value vary by market, jurisdiction, stage, sector, instrument, and bargaining position. - A financing label cannot prove success, reduce risk by a known amount, or substitute for operating evidence and solvency analysis. - Founder payoff is nondiversified and uncertain; stakeholder and creditor effects may not appear in headline ownership or valuation." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-connections-11", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Connections", "headingId": "chapter-15-fundraising-and-finance-connections-11", "url": "#chapter-15-fundraising-and-finance-connections-11", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Need and timing: Use Frameworks 1 and 8 for process, cash, runway, and model scenarios. - Terms and ownership: Use Frameworks 3–5 and 10 for rights, dilution, conversion, and proceeds. - Venture/GTM evidence: Use Chapters 13, 14, and 22 for venture tests, operating assumptions, and analysis. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-12-troubleshooting-when-fundraising-goes-wrong", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "12. Troubleshooting: When Fundraising Goes Wrong", "headingId": "chapter-15-fundraising-and-finance-12-troubleshooting-when-fundraising-goes-wrong", "url": "#chapter-15-fundraising-and-finance-12-troubleshooting-when-fundraising-goes-wrong", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed-scenario boundary: Every company, amount, valuation, timing, probability, financing term, workforce action, buyer, and outcome in this troubleshooting section is hypothetical. It is not a benchmark or recommendation. Employment, WARN/consultation, benefits, solvency, fiduciary, securities, tax, contract, and transaction decisions require the responsible owners and qualified advisers. Purpose: Navigate bridge rounds, down rounds, failed raises, and emergency financing. Critical Context: Many fundraising attempts stall, fail, or produce unfavorable terms. This section provides a playbook for handling missed milestones, weak investor demand, bridge rounds, down rounds, and emergency financing." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-problem-1-no-term-sheets-after-a-sufficient-responsibly-sampled-process", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Problem 1: No Term Sheets After a Sufficient, Responsibly Sampled Process", "headingId": "chapter-15-fundraising-and-finance-problem-1-no-term-sheets-after-a-sufficient-responsibly-sampled-process", "url": "#chapter-15-fundraising-and-finance-problem-1-no-term-sheets-after-a-sufficient-responsibly-sampled-process", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Symptoms: - A sufficient, responsibly sampled set of investor conversations has completed without a credible next step - All investors passed or ghosted - Common feedback: \"Too early,\" \"Market concerns,\" \"Team concerns,\" \"Traction insufficient\" Diagnosis: Treat repeated feedback as hypothesis-generating evidence, not a diagnosis of one root cause: Table 15.12: Author-created or source-bounded decision aid (Observed pattern | Competing hypotheses to test | Possible next evidence or response ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Observed pattern | Competing hypotheses to test | Possible next evidence or response| | :--- | :--- | :---| | Repeated “too early” feedback | Evidence threshold, fund mandate, timing, risk, or polite rejection | Ask what evidence would change the decision; compare continued operation, milestone financing, and stopping costs | | Repeated market concern | Market definition, concentration, adoption mechanism, competition, or investor fit | Test with customer behavior, segment economics, alternatives, and fund thesis | | Repeated team concern | Capability gap, governance, communication, bias, or investor preference | Clarify the decision-critical capability; compare hiring, advising, partnering, development, or a different investor set | | Mixed feedback | Multiple constraints, noisy feedback, weak positioning, or heterogeneous mandates | Reconstruct evidence by investor type and seek disconfirming review | | Warm reception without terms | Price, terms, conviction, process, timing, authority, or option value | Ask for concrete conditions; compare actual alternatives rather than assuming a valuation cut | Action Plan: Step 1: Structure the evidence (illustrative timing) - Categorize all feedback into buckets (traction, market, team, valuation, timing) - Look for recurring and contradictory evidence without treating a percentage threshold as proof - If no clear pattern, request honest feedback from 3 investors who seemed most interested Step 2: Test responses (illustrative timing) - Match the response to the supported constraint and feasible alternatives; revenue, customer evidence, positioning, capability, price, terms, timing, or investor fit may each matter - Predefine what evidence would justify retrying, changing the financing path, or stopping; no ARR, case-count, hiring, valuation-cut, or calendar threshold is assumed Step 3: Retry or Alternative (after the locally defined review window) - Retry with improved pitch/traction (new investor list, not same investors) - Alternative: Bridge financing from angels ($500K-$1M to extend runway) - Alternative: Cut costs, reach profitability, avoid raising entirely Constructed example (not a real company or outcome): ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-problem-2-lower-price-financing-or-recapitalization", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Problem 2: Lower-Price Financing or Recapitalization", "headingId": "chapter-15-fundraising-and-finance-problem-2-lower-price-financing-or-recapitalization", "url": "#chapter-15-fundraising-and-finance-problem-2-lower-price-financing-or-recapitalization", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Definition boundary: Determine a down round from the new price per share for the relevant security after accounting for splits, recapitalization, rights, and the contract-defined capitalization—not by comparing one headline pre-money or post-money valuation with another. Possible effects, not automatic outcomes: - New-money dilution follows the issued shares; anti-dilution applies only if the actual prior documents trigger it and must be calculated from the clause. - Founder, employee, and investor outcomes depend on vesting, option strike prices, preferences, pay-to-play, recapitalization, debt, tax, communications, and future financing. - Morale, reputation, customer response, and financing access may improve, worsen, or remain unchanged depending on process and operating evidence. - A sale, cost reduction, bridge/debt, restructuring, no deal, or shutdown can be feasible or harmful; none is the categorical next step. Controlled decision process: 1. Reconcile cash, restricted cash, burn, obligations, covenants, and runway under multiple scenarios. A runway threshold does not compel acceptance; insolvency, fiduciary, employment, disclosure, and approval duties can narrow the available time and options. 2. Obtain actual term sheets and capitalization definitions. Model new shares, pool changes, conversions, anti-dilution, pay-to-play, preferences, governance, and exit proceeds; reconcile ownership and cash to 100 percent. 3. Compare financing, cost, revenue, asset sale, strategic transaction, debt/bridge, restructuring, and orderly wind-down paths using probability ranges, execution time, stakeholder outcomes, and legal constraints. 4. Protect privilege, ensure accurate disclosure, document conflicts and board process, and use qualified corporate/restructuring counsel plus tax/accounting owners. 5. Select, negotiate, pause, or stop from the full evidence; do not treat “less than three months” as an automatic accept rule. All earlier percentages, layoffs, prices, buyer outcomes, and timelines in this section were constructed and have been removed rather than retained as prescriptions. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-problem-3-bridge-round-emergency-financing", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Problem 3: Bridge Round (Emergency Financing)", "headingId": "chapter-15-fundraising-and-finance-problem-3-bridge-round-emergency-financing", "url": "#chapter-15-fundraising-and-finance-problem-3-bridge-round-emergency-financing", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Setup: A company is considering a bridge to preserve runway or reach a defined evidence milestone. The amount, timing, instrument, and target are company-specific. Bridge Round Structure: When Bridge May Make Sense: - The bridge extends a defined downside runway or evidence plan that remains credible under stress scenarios. - Existing or new counterparties can participate on documented authority, capacity, and acceptable terms; participation is not proof of confidence. - The bridge creates option value after modeling conversion, cash, governance, disclosure, and no-next-round outcomes. When Bridge May Be Harmful: - The evidence milestone is not credible under the downside case or the bridge merely postpones insolvency. - Terms create unacceptable conversion, priority, control, repayment, or disclosure risk. - The company or its advisers cannot reconcile the bridge with the full capitalization, cash, and no-next-round scenarios. Negotiating Bridge Terms: Table 15.13: Author-created or source-bounded decision aid (Term | Investor Scenario | Founder Scenario | Constructed Comparison Input ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Term | Investor Scenario | Founder Scenario | Constructed Comparison Input | | :--- | :--- | :--- | :--- | | Discount | Actual document term | Actual document term | Model sensitivity to the actual term | | Cap | Actual document term | Actual document term | Model sensitivity to the actual term | | Interest | Actual document term | Actual document term | Model cash and accounting effect | | Maturity | Actual document term | Actual document term | Model maturity, default, and extension conditions | Modeling boundary: A five-point change in discount changes the contractual conversion price; it does not equal five percentage points of dilution. The ownership effect depends on the financing price, cap definition, accrued amount, company capitalization specified by the instrument, option-pool treatment, other converting instruments, and the sequencing of new-money shares. Compare the full package with runway, solvency, control, tax/accounting, and no-bridge alternatives; counsel and the finance owner must use the actual documents. [BB-C15-S13] Controlled conversion worksheet: ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-problem-4-investor-pulls-term-sheet", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Problem 4: Investor Pulls Term Sheet", "headingId": "chapter-15-fundraising-and-finance-problem-4-investor-pulls-term-sheet", "url": "#chapter-15-fundraising-and-finance-problem-4-investor-pulls-term-sheet", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Setup: You signed term sheet, investor pulls out during diligence Possible explanations to verify: Diligence findings, disclosure or document gaps, changed market or fund constraints, approval failure, financing capacity, conflicts, revised price or terms, or a decision to stop. Do not infer politics, manipulation, psychology, or a competing deal without evidence. Governed response: 1. Ask the investor to identify the changed fact, condition, approval, or term and distinguish withdrawal from a proposed amendment. 2. Review the signed term sheet, exclusivity, confidentiality, expenses, closing conditions, disclosure, solvency, and communications with qualified counsel and the responsible owners. 3. Update the cash plan and compare other investors, insider support, non-equity capital, operating changes, sale, and orderly shutdown without fabricating urgency or misrepresenting pipeline status. 4. Correct any material disclosure or operating issue before approaching another counterparty; preserve a factual decision record. The removed investor-motive and “FOMO” scenario was unsupported. A counteroffer, new process, or exit is appropriate only when the evidence, authority, actual terms, cash, and legal obligations support it. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-problem-5-running-out-of-cash-distressed-financing", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Problem 5: Running Out of Cash (Distressed Financing)", "headingId": "chapter-15-fundraising-and-finance-problem-5-running-out-of-cash-distressed-financing", "url": "#chapter-15-fundraising-and-finance-problem-5-running-out-of-cash-distressed-financing", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Setup: Runway is approaching the approved solvency or contingency boundary, fundraising is stalled, and shutdown risk requires an authorized comparison of alternatives. Options to compare without a founder-friendliness ranking: Option: Insider Bridge - Ask existing investors whether a bridge sized to the downside cash plan is feasible - Terms: Actual document terms, conversion, maturity, priority, governance, and disclosure conditions - Possible fit: the bridge creates a credible, approved path after full downside modeling; participation is not proof of belief Option: Venture Debt - Seek proposals from eligible lenders based on current underwriting, security, covenant, cash, and concentration requirements; no named provider or availability is assumed - Terms: Actual lender proposal for interest, repayment, warrants, collateral, covenants, guarantees, and default; no market range is assumed - Possible underwriting input: documented revenue quality, retention, concentration, margin, cash conversion, and repayment capacity; requirements vary by lender and instrument. - Best fit: you qualify for lender underwriting and can support repayment Option 3: Revenue-Based Financing - Revenue-based financing may advance a negotiated amount repaid through a defined share of revenue or another contractual formula; compare effective cost, covenants, security, cash timing, and downside terms with qualified advisers. - Terms: Actual provider formula for repayment, revenue share, cap/multiple, fees, covenants, and duration; no market range is assumed - Possible underwriting inputs include unit economics, recurring-revenue quality, operating history, concentration, and repayment capacity; verify the provider's current criteria. - Best fit: revenue economics support repayment without starving growth Option 4: Acqui-hire - Evaluate an asset, equity, team, license, or other transaction against actual buyer terms, liabilities, approvals, employee treatment, customer and data obligations, tax, antitrust, and alternatives - Founder, employee, creditor, and investor proceeds depend on price, debt, fees, escrow, taxes, security seniority, preferences, participation, conversion, retention consideration, vesting, and the executed waterfall; no founder outcome is assumed Option 5: Shut Down - Preserve cash and records, identify creditor and stakeholder obligations, and follow board, fiduciary, solvency, tax, contract, privacy, security, IP, regulatory, and dissolution requirements with qualified advisers - Distributions follow applicable law, creditor priority, security rights, governing documents, and the approved waterfall—not an automatic pro-rata investor return - Employee notice, consultation, pay, benefits, retention, termination, and record duties depend on jurisdiction, workforce, contracts, transaction structure, and applicable employment law; no two-week rule is assumed --- Cross-Reference: - For down round dilution modeling, see Section 5A: Advanced Dilution Modeling - For failure case studies, see Section 13: Financing and Governance Lessons from Primary Records below - For term sheet negotiation, see Section 4: Term Sheet Key Terms ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-13-financing-and-governance-lessons-from-primary-records", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "13. Financing and Governance Lessons from Primary Records", "headingId": "chapter-15-fundraising-and-finance-13-financing-and-governance-lessons-from-primary-records", "url": "#chapter-15-fundraising-and-finance-13-financing-and-governance-lessons-from-primary-records", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Named-company failure analysis carries factual, legal, and reputational risk. This section therefore uses only the scope supported by the three registered primary or official records. It does not infer motives, diagnose individuals, reconstruct investor knowledge, or treat financing price as enterprise value. Later court, bankruptcy, regulatory, and transaction facts require their own verified records." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-the-we-company-what-the-2019-s-1-can-support", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "The We Company: What the 2019 S-1 Can Support", "headingId": "chapter-15-fundraising-and-finance-the-we-company-what-the-2019-s-1-can-support", "url": "#chapter-15-fundraising-and-finance-the-we-company-what-the-2019-s-1-can-support", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The We Company's 2019 Form S-1 is a contemporaneous securities filing. It can support analysis of the issuer's disclosed revenue, losses, lease obligations and risk factors, related-party transactions, and governance/control structure as of the filing. [BB-C15-S18] Applied diligence questions: - Do long-dated commitments and short-duration customer revenue create liquidity or duration mismatch? - Which adjusted performance measures reconcile to audited financial statements, and which exclude recurring economic costs? - Which related-party transactions, voting rights, board arrangements, or conflicts require independent review? - How do downside cash scenarios change when growth, occupancy, funding access, or pricing falls below plan? The filing does not establish later bankruptcy facts, investor motives, a universal valuation lesson, or the proceeds any holder ultimately received. Those questions require additional filings, court records, and transaction documents." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-theranos-sec-allegations-and-settlement-boundary", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Theranos: SEC Allegations and Settlement Boundary", "headingId": "chapter-15-fundraising-and-finance-theranos-sec-allegations-and-settlement-boundary", "url": "#chapter-15-fundraising-and-finance-theranos-sec-allegations-and-settlement-boundary", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The SEC's 2018 release states that it charged Theranos, Elizabeth Holmes, and Ramesh Balwani with a fraud involving allegedly false or exaggerated statements and says the company raised more than $700 million from investors; it also describes settlements without admission or denial for specified defendants. [BB-C15-S17] Applied diligence questions: - Which technical, regulatory, commercial, and financial claims have independent, decision-relevant evidence? - Can experts examine the evidence under appropriate confidentiality rather than accept prestige, board composition, or partnerships as substitutes? - Are management representations reconciled to regulator, laboratory, customer, and financial records? - What disclosure, escalation, and stop rules apply when evidence conflicts with the fundraising narrative? This registered SEC release does not by itself support later criminal convictions, sentences, restitution, patient outcomes, individual investment amounts, or every operational claim in prior drafts. Those facts are omitted here until the corresponding court or regulator records are registered and checked." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-ftx-debtors-post-bankruptcy-control-evidence", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "FTX Debtors: Post-Bankruptcy Control Evidence", "headingId": "chapter-15-fundraising-and-finance-ftx-debtors-post-bankruptcy-control-evidence", "url": "#chapter-15-fundraising-and-finance-ftx-debtors-post-bankruptcy-control-evidence", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "John J. Ray III's 2022 congressional testimony, given as CEO of the FTX debtors after bankruptcy filings, describes his observations of control, governance, recordkeeping, security, and asset-management failures. It is an authoritative witness statement for that limited purpose, not a substitute for adjudicated findings or a complete transaction history. [BB-C15-S19] Applied diligence questions: - Who can move customer and corporate assets, and what authorization, segregation, reconciliation, and audit evidence constrains that access? - Do the board, finance, risk, security, legal, and compliance functions have independent authority, records, and escalation paths? - Can the organization produce reliable entity-level cash, liability, ownership, and related-party records? - Which claims remain testimony, allegation, management representation, or unresolved bankruptcy issue? The testimony does not, without additional records, support every valuation, missing-funds, growth, sentencing, investor-diligence, or individual-knowledge statement that appeared in the earlier draft." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-cross-case-decision-framework", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Cross-Case Decision Framework", "headingId": "chapter-15-fundraising-and-finance-cross-case-decision-framework", "url": "#chapter-15-fundraising-and-finance-cross-case-decision-framework", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The defensible common lesson is methodological: financing narratives and headline values do not replace primary evidence, reconciled financial statements, technical/regulatory verification, cash controls, conflict governance, and security-specific downside modeling. 1. Separate evidence classes: issuer filing, regulator allegation, settlement, sworn testimony, court finding, audited statement, and management forecast are not interchangeable. 2. Reconcile the model: connect revenue, cash, commitments, ownership, related parties, and downside liquidity. 3. Verify the operating claim: use qualified independent experts and direct evidence when technology, licensing, custody, or safety is material. 4. Model control and incentives: ownership percentage does not reveal voting, board, protective, custody, or related-party rights. 5. Record uncertainty: identify what is observed, alleged, inferred, disputed, or unknown and what evidence would change the decision. 6. Escalate or stop: unresolved evidence, custody, disclosure, solvency, or legal failures can justify pausing diligence or declining financing. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-14-entrepreneurship-through-acquisition-financing-diligence-and-transition", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "14. Entrepreneurship Through Acquisition: Financing, Diligence, and Transition", "headingId": "chapter-15-fundraising-and-finance-14-entrepreneurship-through-acquisition-financing-diligence-and-transition", "url": "#chapter-15-fundraising-and-finance-14-entrepreneurship-through-acquisition-financing-diligence-and-transition", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "An acquisition creates a different financing problem from a greenfield startup. The buyer pays for an operating asset with historical claims that still require verification, while allocating fixed debt claims, equity ownership, control rights, seller obligations, and post-close operating risk. Sponsor-backed leveraged buyouts often combine a smaller equity contribution with substantial outside debt, but financing structures and outcomes vary across transactions and credit cycles. [BB-C15-S20] This section continues the constructed Northstar Field Services case from Chapter 13. Every company name, amount, rate, adjustment, ratio, and decision threshold below is fictional and illustrative. It is not a valuation, lending, accounting, quality-of-earnings, tax, legal, securities, or acquisition recommendation." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-sources-and-uses-who-funds-what-and-who-bears-which-claim", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Sources and uses: who funds what, and who bears which claim?", "headingId": "chapter-15-fundraising-and-finance-sources-and-uses-who-funds-what-and-who-bears-which-claim", "url": "#chapter-15-fundraising-and-finance-sources-and-uses-who-funds-what-and-who-bears-which-claim", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 15.14: Author-created or source-bounded decision aid (Constructed uses | Amount | Constructed sources | Amount ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Constructed uses | Amount | Constructed sources | Amount | | :--- | :--- | :--- | :--- | | Purchase price | $4,800,000 | Buyer equity | $400,000 | | Transaction and financing costs | $200,000 | Outside investor equity | $1,600,000 | | Opening cash and working-capital reserve | $300,000 | Senior acquisition debt | $2,700,000 | | | | Seller note | $600,000 | | Total uses | $5,300,000 | Total sources | $5,300,000 | The table reconciles funding, not value or suitability. In this simplified contribution-only equity pool, the buyer contributes 20 percent of the $2.0 million equity and outside investors contribute 80 percent. That does not determine the final ownership or economics if the documents include a promote, options, vesting, preferred returns, liquidation rights, fees, board rights, guarantees, future capital obligations, or dilution. Reconcile the actual security-by-security capitalization and decision rights separately. For an eligible U.S. small business, the SBA's 7(a) program may support a complete or partial change of ownership. Eligibility, underwriting, use of proceeds, repayment ability, guarantees, collateral, fees, and terms depend on current program rules and lender review; a website summary is not credit approval. [BB-C15-S21] SBA Standard Operating Procedure 50 10 is operational guidance for participating lenders and development companies and can be modified by later notices, so the current version and transaction-specific requirements must be checked at underwriting and closing. [BB-C15-S22]" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-debt-service-and-dilution-are-different-exposures", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Debt service and dilution are different exposures", "headingId": "chapter-15-fundraising-and-finance-debt-service-and-dilution-are-different-exposures", "url": "#chapter-15-fundraising-and-finance-debt-service-and-dilution-are-different-exposures", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Equity absorbs residual upside and downside but can dilute ownership and alter control. Debt does not ordinarily dilute common ownership, but it creates scheduled payments, covenants, remedies, collateral claims, and sometimes personal guarantees. Seller financing can bridge price or information gaps, but payment priority, setoff, subordination, security, covenants, and seller incentives are governed by the documents. An earnout or other contingent payment may shift some outcome risk but creates definitions, measurement, control, dispute, tax, and accounting issues. For the constructed case, assume only for teaching that the $2.7 million senior loan amortizes annually over 10 years at 9 percent, producing approximately $420,714 of annual debt service, and that the $600,000 seller note requires $36,000 of annual interest with no scheduled principal in the displayed year. Total displayed annual debt service is therefore approximately $456,714. \\[ \\text{Annual payment} = \\frac{P\\times r}{1-(1+r)^{-n}} \\] \\[ \\text{Debt-service coverage ratio (DSCR)} = \\frac{\\text{cash available for debt service}}{\\text{required debt service}} \\] If independently modeled cash available for debt service (CADS) is $900,000 in the base case, displayed DSCR is about 1.97x . If the downside case produces only $500,000, it is about 1.09x . CADS is not automatically EBITDA: define it after cash taxes, maintenance capital expenditure, working-capital needs, required owner/operator compensation, and other senior cash uses. Actual payment frequency, amortization, fees, floating rates, covenants, principal on the seller note, and lender definitions will change the result. Stop gate: do not close merely because the base case covers debt. Stop, reprice, reduce leverage, add liquidity, change structure, or obtain new evidence when the approved downside case breaches a lender covenant, minimum cash requirement, solvency boundary, personal-risk limit, or board/investor mandate." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-quality-of-earnings-reconcile-the-claim-before-sizing-price-or-debt", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Quality of earnings: reconcile the claim before sizing price or debt", "headingId": "chapter-15-fundraising-and-finance-quality-of-earnings-reconcile-the-claim-before-sizing-price-or-debt", "url": "#chapter-15-fundraising-and-finance-quality-of-earnings-reconcile-the-claim-before-sizing-price-or-debt", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A quality-of-earnings (QoE) review is a transaction-specific analysis of the sustainability and cash implications of reported earnings. It is not automatically an audit, a GAAP opinion, fraud assurance, valuation, tax opinion, or forecast. The buyer should reconcile proposed adjustments to the general ledger, bank activity, invoices, contracts, payroll, tax filings, and operating evidence and distinguish recurring economics from truly nonrecurring items. Public-company SEC guidance illustrates why non-GAAP measures require disciplined definition and reconciliation and why individually tailored recognition or measurement can be misleading. The SEC rules do not govern every private-company ETA presentation; the guidance is used here by analogy as a conservative adjustment discipline, not as a claim of legal applicability. [BB-C15-S23] Table 15.15: Author-created or source-bounded decision aid (Constructed QoE bridge | Amount | Evidence judgment ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Constructed QoE bridge | Amount | Evidence judgment | | :--- | :--- | :--- | | Reported EBITDA | $800,000 | Starting management measure; reconcile to financial statements and ledger | | Buyer-validated portion of $250,000 seller-claimed add-backs | +$80,000 | Only documented, genuinely nonrecurring items accepted | | Market-consistent replacement cost for seller's operating role | -$150,000 | Recurring economic cost after transition | | Normalized maintenance expense | -$70,000 | Recurring upkeep omitted or deferred in the historical period | | Constructed normalized EBITDA | $660,000 | Still not CADS, valuation, or guaranteed future earnings | At the $4.8 million illustrative price, the simple multiple is 6.0x reported EBITDA but approximately 7.3x constructed normalized EBITDA . Both ratios omit debt/cash conventions, working-capital mechanisms, taxes, capital expenditure, synergies, contingencies, and future performance. The point is not that 7.3x is high or low; it is that the denominator must be defined and evidenced before price, leverage, or returns can be interpreted." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-diligence-and-stop-gate-matrix", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Diligence and stop-gate matrix", "headingId": "chapter-15-fundraising-and-finance-diligence-and-stop-gate-matrix", "url": "#chapter-15-fundraising-and-finance-diligence-and-stop-gate-matrix", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 15.16: Author-created or source-bounded decision aid (Workstream | Minimum evidence package | Escalate, reprice, restructure, or stop when ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Workstream | Minimum evidence package | Escalate, reprice, restructure, or stop when| | :--- | :--- | :---| | Financial and QoE | Ledger, statements, bank, receivables/payables, payroll, tax, capex, working capital, debt, contingencies, and adjustment support | Records do not reconcile; cash conversion or normalized earnings fails the approved downside case | | Commercial | Customer- and product-level revenue/margin, contracts, churn, pipeline, concentration, pricing, complaints, competitors, and permitted references | A key customer or channel loss defeats repayment or thesis and cannot be mitigated | | Legal, tax, and regulatory | Entity/ownership, authority, material contracts, permits, disputes, employment, IP, privacy, environmental/safety, insurance, sanctions, tax, and transaction approvals | Unresolved authority, title, compliance, liability, consent, or tax exposure exceeds the approved limit | | Operations, people, and technology | Process maps, capacity, assets, maintenance, quality, key-person dependencies, compensation, retention, vendors, IT architecture, access, cyber, and continuity | The operator cannot replace the seller, retain critical capability, or secure systems within the funded plan | | Financing | Lender model, collateral, guarantees, covenants, appraisals, conditions precedent, fees, rate sensitivity, and downside liquidity | Funding is conditional on an unsupported assumption or imposes unacceptable recourse/control | | Governance and transition | Cap table, board and reserved matters, conflicts, reporting, incentive plan, seller obligations, stakeholder communications, and 100-day evidence plan | Decision rights are ambiguous, conflicts are unmanaged, or transition depends on unenforceable goodwill | Figure 15.3: Evidence-gated acquisition from thesis to transition (constructed). A letter of intent authorizes a bounded investigation; it does not prove value or compel closing. Each lane can advance, revise/restructure, pause, or stop. Text equivalent: The buyer begins with a thesis and screening decision, negotiates a bounded letter of intent, and conducts financial, commercial, legal/regulatory, operational, people/technology, and financing diligence. A quality-of-earnings and cash bridge informs price and debt capacity. Financing, governance, approvals, and definitive documents are then tested together. Only an authorized pass leads to closing. The buyer then executes transition and reports against a predeclared 100-day evidence plan. At every gate, unresolved material evidence can cause repricing, restructuring, pausing, or stopping." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-governance-and-transition-control-begins-before-close", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Governance and transition: control begins before close", "headingId": "chapter-15-fundraising-and-finance-governance-and-transition-control-begins-before-close", "url": "#chapter-15-fundraising-and-finance-governance-and-transition-control-begins-before-close", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The G20/OECD Principles emphasize strategic guidance, monitoring management, reliable information, risk oversight, conflicts, and board oversight of major acquisitions. They are broad international governance principles—primarily a framework for policymakers, markets, and corporations—not a substitute for the target's entity law, governing documents, lender rights, fiduciary analysis, or a small-company board design. [BB-C15-S24] Use an authorized transition charter rather than an informal seller handoff: Table 15.17: Author-created or source-bounded decision aid (Stage | Required decisions and evidence ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Stage | Required decisions and evidence| | :--- | :---| | Before signing/close | Confirm buyer and seller authority; board/investor/lender approvals; funds flow; conditions precedent; consents; closing balance sheet/working capital method; access and cyber cutover; communications; and explicit no-close authority | | Day 0-30 | Secure banking, payroll, tax, insurance, systems, credentials, data, and physical assets; meet key employees/customers/suppliers without unsupported promises; establish incident escalation and cash reporting | | Day 31-100 | Test customer retention, seller transfer, normalized earnings, working capital, maintenance, staffing, service/quality, covenant headroom, and thesis assumptions against the approved plan | | Ongoing governance | Maintain board cadence, reserved matters, conflict register, monthly financial/cash/covenant pack, risk/compliance reporting, capital-allocation authority, incentive review, and documented corrective actions | The day ranges are a constructed planning scaffold, not evidence that integration completes in 100 days. The seller's transition duties, employee actions, customer communications, data transfers, price adjustments, indemnities, escrow, earnouts, and post-close remedies must follow the actual documents and applicable law." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-applied-exercise-acquisition-investment-committee-memo", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Applied exercise — acquisition investment committee memo", "headingId": "chapter-15-fundraising-and-finance-applied-exercise-acquisition-investment-committee-memo", "url": "#chapter-15-fundraising-and-finance-applied-exercise-acquisition-investment-committee-memo", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Using the constructed case, or a similarly fictional case: 1. Reconcile sources and uses and a security-by-security equity capitalization to 100 percent. 2. Calculate debt service and DSCR under base, customer-loss, margin-pressure, rate, capex, and working-capital scenarios; label every assumption. 3. Build a QoE bridge that separates seller claims, accepted adjustments, rejected adjustments, replacement costs, and CADS. 4. Create a diligence request list and assign an evidence owner, reviewer, materiality rule, and stop gate to each workstream. 5. Draft the governance and transition charter, including board/reserved matters, seller duties, systems/cash control, stakeholder communication, and 30/100-day evidence reviews. 6. Recommend close / reprice or restructure / pause / stop . State which observed fact or missing evidence would reverse the recommendation. Qualified transaction counsel, tax and accounting advisers, a QoE provider or CPA as appropriate, lenders, insurance advisers, technical specialists, HR/employment advisers, and the authorized board or investment committee must own their respective conclusions. A chapter exercise cannot approve an acquisition. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-get-started-fundraising-execution", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How To Get Started: Fundraising Execution", "headingId": "chapter-15-fundraising-and-finance-how-to-get-started-fundraising-execution", "url": "#chapter-15-fundraising-and-finance-how-to-get-started-fundraising-execution", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This section provides practical, time-boxed guidance for executing a fundraising round from preparation through closing. Constructed-template boundary: Every week, hour, meeting count, response rate, valuation, milestone, score, fee, workload, and outcome in the quick and detailed paths is illustrative. Set the process from runway scenarios, evidence, investor fit, jurisdiction, disclosure controls, decision authority, team capacity, and actual counterparties. No schedule guarantees financing or authorizes solicitation, disclosure, employment action, or execution of documents." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-illustrative-quick-version-4-6-weeks-pitch-development-outreach-kickoff", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Illustrative Quick Version (4-6 Weeks): Pitch Development + Outreach Kickoff", "headingId": "chapter-15-fundraising-and-finance-illustrative-quick-version-4-6-weeks-pitch-development-outreach-kickoff", "url": "#chapter-15-fundraising-and-finance-illustrative-quick-version-4-6-weeks-pitch-development-outreach-kickoff", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Develop professional materials and initiate investor conversations. Timeline: 4-6 weeks in this constructed planning case; set the actual window from runway, evidence, access, capacity, and approvals. Use when: The team is testing whether a bounded financing process is justified; stage labels do not determine readiness." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-week-1-pitch-deck-development", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 1: Pitch Deck Development", "headingId": "chapter-15-fundraising-and-finance-week-1-pitch-deck-development", "url": "#chapter-15-fundraising-and-finance-week-1-pitch-deck-development", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Activity: Create 10-15 slide pitch deck - Content Required: - Problem (1 slide with specific pain point + quantified impact) - Solution (1 slide with visual + 2-3 differentiators) - Market size (TAM/SAM/SOM with calculation methodology) - Traction (Choose 2-3 strongest metrics: ARR, growth rate, customer count) - Team (3-5 key people with credentials) - Business model (Pricing, unit economics if available) - Fundraising ask (Amount + use of funds breakdown) - Output: First draft deck (expect 5-7 iterations before investor-ready) - Time Investment: 20-30 hours - Common Mistake: Feature lists instead of benefits (investors care about customer value, not technical specs) Sample Slide Structure: 1. Title 2. Problem (with stat) 3. Solution (with visual) 4. Market size 5. Traction 6. Business model 7. Team 8. Ask 9. Vision 10. Questions" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-week-2-financial-model-cap-table", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 2: Financial Model + Cap Table", "headingId": "chapter-15-fundraising-and-finance-week-2-financial-model-cap-table", "url": "#chapter-15-fundraising-and-finance-week-2-financial-model-cap-table", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Activity: Build basic financial projections - Required Components: - Revenue forecast (5-year, monthly for Year 1) - Key assumptions documented (customer growth rate, ARPU, churn) - Unit economics (CAC, LTV, payback period if have customers) - Cap table (current ownership + post-raise scenario) - Tools: - Google Sheets or Excel (investors expect familiar format) - Template available at Y Combinator, Carta - Output: 3-statement model (Income Statement, Balance Sheet, Cash Flow) - Time Investment: 15-25 hours - Validation: Show to CFO advisor or experienced founder for sanity check Key Metrics to Calculate: - Monthly burn rate (cash out - cash in) - Runway (cash on hand / monthly burn) - Path to profitability (when does revenue expenses?) - Funding needed (model the runway, milestones, obligations, downside, and alternatives; no universal duration is assumed)" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-week-3-investor-list-creation", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Week 3: Investor List Creation", "headingId": "chapter-15-fundraising-and-finance-week-3-investor-list-creation", "url": "#chapter-15-fundraising-and-finance-week-3-investor-list-creation", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Activity: Build target investor list (50+ names) - Criteria for Inclusion: - Stage match (seed investors for seed round, Series A investors for Series A) - Sector focus (have they invested in your market before?) - Geography (prefer local or have they done remote?) - Check size (does their typical check match your raise?) - Sources: - Crunchbase (filter by stage, sector, geography) - AngelList (see who invests in similar companies) - Your network (advisors, founder friends) - Accelerator-network introductions, when relevant and permitted - Output: Spreadsheet with a sized investor universe, source dates, and permitted introduction pathways identified - Prioritization: Rank by evidence-based fit, access, conflicts, capacity, and decision timing; do not assume a tier label predicts outcome. - Warm Intro Goal: Identify permitted, credible introduction pathways; the count is a local capacity choice. Investor List Template: Table 15.18: Author-created or source-bounded decision aid (Investor Name | Firm | Stage | Sector | Geography | Intro Path | Tier | Contact Date ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Investor Name | Firm | Stage | Sector | Geography | Intro Path | Tier | Contact Date| | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :---| | Sarah Chen | Northstar Ventures | Series A | SaaS | SF | John (advisor) | 1 | TBD | | Mike Liu | Harbor Ridge Capital | Series A | Infra | SF | No connection | 3 | TBD |" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-illustrative-week-4-6-first-investor-meetings", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Illustrative Week 4-6: First Investor Meetings", "headingId": "chapter-15-fundraising-and-finance-illustrative-week-4-6-first-investor-meetings", "url": "#chapter-15-fundraising-and-finance-illustrative-week-4-6-first-investor-meetings", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Activity: Schedule and conduct first investor meetings - Cadence: Set a pace that allows preparation, follow-up, iteration, and normal operations. - Meeting Structure: - 30 min pitch (expect interruptions, questions) - 30 min Q&A (questions reveal investor concerns) - 15 min follow-up (what materials do they need? next steps?) - Tracking: Use spreadsheet to track all interactions - Iteration: Update pitch weekly based on feedback patterns - Follow-Up: Send an accurate, approved follow-up on a defined service level; do not promise a universal response time. Meeting Tracking Template: Table 15.19: Author-created or source-bounded decision aid (Investor | Meeting Date | Interest Level | Key Feedback | Materials Sent | Next Step | Timeline ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Investor | Meeting Date | Interest Level | Key Feedback | Materials Sent | Next Step | Timeline| | :--- | :--- | :--- | :--- | :--- | :--- | :---| | Northstar Ventures | 11/8 | Warm | \"Love traction, worried about market size\" | Market analysis deck | Partner meeting | 2 weeks | | Harbor Ridge Capital | 11/12 | Cool | \"Too early for us\" | - | Follow up in 6mo | 6 months | Interest Level Definitions: - Hot: Wants partner meeting or diligence - Warm: Interested, needs more info - Cool: Not now, but maybe later - Pass: Not interested" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-quick-version-outputs", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Quick Version Outputs", "headingId": "chapter-15-fundraising-and-finance-quick-version-outputs", "url": "#chapter-15-fundraising-and-finance-quick-version-outputs", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Deliverables: 1. Investor-ready pitch deck with a slide count appropriate to the audience and decision 2. Financial model with assumptions (Excel/Google Sheets) 3. Investor tracking spreadsheet with the selected investor universe and permitted introduction paths 4. First meeting feedback summary with the actual reactions captured and evidence quality recorded 5. Updated pitch incorporating early feedback without overstating investor interest Success indicators (not universal thresholds): - The selected investor universe is fit-checked, source-dated, and manageable. - Conversations produce decision-relevant feedback and clearly defined next steps. - Materials improve without weakening disclosure, confidentiality, or evidence controls. Common outcome: This Quick Version helps the team decide whether a fuller process is justified. Use the actual evidence, access, cash, capacity, and alternative paths to decide whether to continue, revise, resize, pause, or stop; no response-rate cutoff is universal. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-illustrative-detailed-version-16-20-weeks-full-fundraising-cycle", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Illustrative Detailed Version (16-20 Weeks): Full Fundraising Cycle", "headingId": "chapter-15-fundraising-and-finance-illustrative-detailed-version-16-20-weeks-full-fundraising-cycle", "url": "#chapter-15-fundraising-and-finance-illustrative-detailed-version-16-20-weeks-full-fundraising-cycle", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Execute complete fundraising process from preparation through legal closing. Timeline: 16-20 weeks in this constructed planning case; the actual duration depends on evidence, counterparties, documents, approvals, and runway. Use when: The evidence and operating plan justify testing institutional financing; a Series label or claimed product-market fit does not determine readiness." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-phase-1-preparation-weeks-1-4", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 1: Preparation (Weeks 1-4)", "headingId": "chapter-15-fundraising-and-finance-phase-1-preparation-weeks-1-4", "url": "#chapter-15-fundraising-and-finance-phase-1-preparation-weeks-1-4", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 1: Materials Assembly - [ ] Update pitch deck (previous round's deck won't work - stale metrics, outdated positioning) - [ ] Create one-pager (2-3 sentences + key metrics for warm intro emails) - [ ] Prepare detailed financial model (5-year projections with monthly detail Year 1) - [ ] Document key assumptions (growth rates, unit economics, hiring plan) - [ ] Update business metrics dashboard (ARR, MRR, growth rate, churn, CAC, LTV) - Time Required: 30-40 hours - Output: Investor data room (digital folder with all materials) Week 2: Due Diligence Prep - [ ] Clean up cap table (ensure all equity allocations documented) - [ ] Organize corporate documents (incorporation docs, board resolutions, equity agreements) - [ ] Prepare customer references (5-10 customers willing to take investor calls) - [ ] Review contracts for issues (any problematic customer or vendor terms?) - [ ] Legal review (consult lawyer on any IP, litigation, or contract risks) - Time Required: 20-30 hours - Output: Due diligence folder ready to share Week 3: Investor Research - [ ] Build a target investor list sized to the financing need, access, capacity, and confidentiality boundary - [ ] Research each investor (portfolio, thesis, check size, decision timeline) - [ ] Identify warm intro paths (advisors, founders, mutual connections) - [ ] Prioritize by tier (Tier 1 = warm intro, Tier 2 = weak connection, Tier 3 = cold) - [ ] Draft intro request emails (templates for each intro source) - Time Required: 15-20 hours - Output: Prioritized investor list with outreach strategy Week 4: Practice & Refinement - [ ] Practice pitch with advisors (get feedback on clarity, timing, energy) - [ ] Prepare answers to hard questions (competitive threats, unit economics concerns, market size challenges) - [ ] Rehearse financials presentation (be able to explain every line item and assumption) - [ ] Set up investor tracking system (spreadsheet or CRM) - [ ] Calendar blocking (reserve 2-3 meeting slots per week for next 3 months) - Time Required: 10-15 hours - Output: Polished pitch + FAQ document Phase 1 success indicators (not universal thresholds): - The pitch deck has been challenged by appropriate reviewers and material gaps are recorded. - Financial assumptions, cash scenarios, cap table, and ownership of unresolved questions are documented. - The investor universe is fit-checked, source-dated, and sized to the team's capacity. - Due-diligence materials are organized and disclosure permissions are defined before sharing. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-phase-2-outreach-illustrative-weeks-5-8", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 2: Outreach (illustrative Weeks 5-8)", "headingId": "chapter-15-fundraising-and-finance-phase-2-outreach-illustrative-weeks-5-8", "url": "#chapter-15-fundraising-and-finance-phase-2-outreach-illustrative-weeks-5-8", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 5-6: Warm Introductions (selected investors) - Activity: Request warm intros to Tier 1 investors - Cadence: Use a pace that protects relationship quality, runway, team capacity, and confidentiality. - Process: 1. Email connector explaining raise + asking for intro 2. Provide one-pager for forwardable context 3. Follow up on the agreed or context-appropriate cadence if no response 4. Thank connector once intro made - Response Rate: Track warm-introduction conversion to first meetings - Time Required: 5-10 hours per week Sample Intro Request Email: Week 7-8: First Meetings Scheduled (illustrative window) - Activity: Lock in meeting dates with interested investors - Target: A bounded set of qualified meetings that the team can prepare for and follow up responsibly - Scheduling Strategy: - Coordinate meetings to leave time for follow-up and iteration. - Sequence conversations based on fit, access, confidentiality, and opportunity cost—not as “practice” for disposable investors. - Preparation: Customize pitch for each investor (reference their portfolio, thesis) Week 7-8: Cold Outreach (If Warm Intros Insufficient) - Activity: Direct outreach to Tier 2/3 investors - Approach: - Personalized email (reference portfolio company, recent investment) - Clear ask (15 min intro call) - Quantified traction (2-3 key metrics) - LinkedIn connection + message - Response Rate: Track cold-email conversion separately from warm introductions - Volume: Set outreach volume from evidence, access, deliverability, team capacity, and runway; do not assume a universal conversion rate. Phase 2 success indicators: - Qualified conversations are scheduled at a manageable pace with owners and next-step definitions. - Warm and cold outreach are tracked separately with accurate denominators and permissions. - Connector follow-up is timely and truthful. - Materials are tailored to the decision without overstating traction or investor interest. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-phase-3-first-meetings-iteration-weeks-9-12", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 3: First Meetings + Iteration (Weeks 9-12)", "headingId": "chapter-15-fundraising-and-finance-phase-3-first-meetings-iteration-weeks-9-12", "url": "#chapter-15-fundraising-and-finance-phase-3-first-meetings-iteration-weeks-9-12", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 9-10: Initial Investor Meetings (constructed batch example) - Meeting Structure: - 5 min small talk (build rapport) - 25 min pitch (allow interruptions) - 20 min Q&A (questions reveal concerns) - 10 min next steps (what do they need? timeline?) - During Meeting: - Read the room (Is investor engaged? Taking notes? Interrupting with questions?) - Note key feedback (What resonated? What confused them?) - Ask about process (How do they make decisions? Timeline?) - After Meeting: - Send an accurate, approved thank-you and requested material on the agreed service level - Share requested materials (detailed financials, customer references) - Update tracking spreadsheet (interest level, feedback, next steps) Week 9-10: Feedback Synthesis - Activity: Identify patterns in investor feedback - Common Feedback Themes: - Market size concerns (TAM too small? Addressable market unclear?) - Competitive positioning (How do you beat existing players?) - Unit economics (CAC too high? LTV unproven?) - Team gaps (Missing key role like CTO, VP Sales?) - Traction concerns (Growth slowing? Customer concentration risk?) - Action: Update pitch to address top 2-3 recurring concerns Example Feedback Pattern: Week 11-12: Second-Round Meetings (constructed batch example) - Activity: Continue first meetings + partner meetings with hot leads - Partner Meetings: Some investors will invite you to present to full partnership - Agree the presentation scope and duration with the actual decision-makers - More detailed questions (financial model deep-dive, technical architecture) - Confirm who is evaluating, recommending, and approving the investment - Iteration: Update the pitch when feedback is evidence-based and material; version numbers are internal controls, not a readiness rule. Phase 3 success indicators: - Conversations produce comparable notes, evidence gaps, and accountable next steps. - Any diligence request is separated from a term sheet or approved commitment. - Pitch changes address substantiated feedback without laundering uncertainty into confidence. - A weekly update records actual activity and runway impact. Week-by-Week Activity Tracker (Weeks 9-12): Table 15.20: Author-created or source-bounded decision aid (Week | Activity | Meetings | Outputs ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Week | Activity | Meetings | Outputs| | :--- | :--- | :--- | :---| | 9 | First meetings (batch 1) | 3-4 | Feedback themes identified | | 10 | First meetings (batch 2) + pitch iteration | 2-3 | Pitch v2 incorporating feedback | | 11 | First meetings (batch 3) + partner meetings | 3-4 | 2-3 hot leads confirmed | | 12 | Partner meetings + follow-ups | 2-3 | Diligence requests from 2-3 investors | ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-phase-4-due-diligence-illustrative-weeks-13-16", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 4: Due Diligence (illustrative Weeks 13-16)", "headingId": "chapter-15-fundraising-and-finance-phase-4-due-diligence-illustrative-weeks-13-16", "url": "#chapter-15-fundraising-and-finance-phase-4-due-diligence-illustrative-weeks-13-16", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 13-14: Active Diligence with Selected Investors - Activity: Deep-dive review by serious investors - Investor Actions: - Financial model review (analyst checks assumptions, unit economics) - Customer reference calls (investor calls 3-5 customers, asks \"Would you be sad if they went away?\") - Competitive analysis (investor researches competitors, validates market position) - Team references (investor calls former managers, team members) - Technical review (if deep-tech, investor may bring in technical advisor) - Founder Actions: - Provide requested materials on a controlled, agreed cadence after checking privilege, confidentiality, privacy, and consent. - Facilitate customer reference calls (intro investor to customers) - Answer follow-up questions (investor will have many) - Maintain communication (weekly check-ins on timeline) Illustrative diligence timing: Record the actual request, response, review, and approval dates; do not treat elapsed time as a universal conviction signal. Common Diligence Requests: - [ ] Detailed financial model with assumptions - [ ] Customer list (ARR per customer, contract terms, churn) - [ ] Competitive analysis (your view on competitors) - [ ] Technical architecture diagram - [ ] Cap table (fully-diluted with option pool) - [ ] Corporate documents (incorporation, IP assignments) - [ ] Team resumes + references Week 15-16: Diligence Completion + Reference Calls - Activity: Investor completes final checks - Customer Reference Calls: - Investor asks: \"How do you use the product? What would happen if it went away? What could be better?\" - Strong signal: Customer says \"We'd be devastated if they shut down\" (very positive) - Weak signal: Customer says \"It's fine, we could find alternatives\" (concerning) - Team Reference Calls: - Investor asks: \"What's it like working with [founder]? Strengths? Growth areas?\" - Strong signal: \"Best manager I've worked with, clear vision, executes fast\" - Weak signal: \"Smart but disorganized, struggles with delegation\" Red Flags That Kill Deals in Diligence: - Financials don't match bank statements (revenue inflated) - Customer references are lukewarm (don't actually love product) - Team references reveal founder conflict - IP not cleanly assigned to company - Undisclosed litigation or contract issues Phase 4 success indicators: - Active diligence has a named owner, permitted scope, source index, and unresolved-issues log. - Materials are provided on an agreed, controlled cadence with appropriate legal and privacy review. - Customer and team references are voluntary, representative, permissioned, and recorded without coaching. - Major issues are surfaced, owned, mitigated, or escalated before approval. - The investor communicates its actual decision process and remaining conditions. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-phase-5-term-sheet-negotiation-closing-weeks-17-20", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 5: Term Sheet Negotiation + Closing (Weeks 17-20)", "headingId": "chapter-15-fundraising-and-finance-phase-5-term-sheet-negotiation-closing-weeks-17-20", "url": "#chapter-15-fundraising-and-finance-phase-5-term-sheet-negotiation-closing-weeks-17-20", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 17: Term Sheet Received - Activity: Lead investor proposes term sheet - Key Terms to Review: - Valuation (pre-money and post-money) - Investment amount - Liquidation preference, seniority, participation/cap, conversion, dividends, and proceeds across exit scenarios - Board composition (founder control maintained?) - Voting rights (what requires investor approval?) - Anti-dilution (weighted average vs. full ratchet) - Protective provisions (veto rights on major decisions) - Action: Review with lawyer (do NOT sign without legal counsel) - Binding status and timing: Record which provisions bind, the actual expiration or response date, exclusivity, confidentiality, expenses, conditions, and termination rights; do not assume a universal term-sheet duration. Week 17-18: Term Sheet Negotiation - Activity: Negotiate key terms - Focus Areas: 1. Valuation: Use VC method + comparables to justify (see Section 3) 2. Liquidation rights: Model the proposed preference, seniority, participation/cap, conversion, and dividends against feasible alternatives 3. Board and control rights: Define the approved composition, appointment/removal, observer, voting, consent, and deadlock boundaries from the actual documents. 4. Protective provisions: Model the actual reserved matters, thresholds, duration, exceptions, and stakeholder effects; do not assume a generic limit. - Common Negotiation Pattern: - Investor proposes $20M post-money, 1x participating preference - Founder counters $25M post-money, 1x non-participating - Land at $22M post-money, 1x participating with cap at 2x - Timeline: Record the actual negotiation sequence; document complexity, counsel review, approvals, and conditions rather than calling a duration typical. Sample Negotiation Email: Week 18-19: Legal Documentation - Activity: Lawyers draft operative documents - Documents Required: - Stock Purchase Agreement (SPA) or SAFE/Convertible Note conversion - Investor Rights Agreement (IRA) - governs ongoing rights - Right of First Refusal Agreement (ROFR) - pro-rata rights - Voting Agreement - board composition, voting rights - Amended and Restated Certificate of Incorporation - Updated cap table - Founder Actions: - Review all documents with lawyer (do NOT rush this) - Clarify any terms that are unclear - Ensure cap table math is correct (founder ownership post-round) - Timeline: Follow the document set, jurisdiction, counsel scope, approvals, and closing conditions; no universal drafting duration applies. Week 19-20: Final Diligence + Closing - Activity: Final checks before money transfer - Final Diligence: - Bank verification (investor confirms cash balance) - No material adverse change (no major negative events since term sheet) - Board approval (investor's partnership votes to proceed) - Founder board approval (founder board votes to accept investment) - Closing Process: 1. All documents signed (DocuSign or wet signatures) 2. Closing conditions satisfied (any final items resolved) 3. Wire transfer sent (investor sends money) 4. Money hits bank account (officially closed!) - Timeline: 1-2 weeks from final documents to money in bank Week 20: Post-Close Announcement - [ ] Communications plan, if disclosure is lawful, accurate, authorized, and useful; no universal raise amount makes a press release newsworthy - [ ] Team announcement (email to all employees explaining what this means) - [ ] Customer communication (if relevant - some customers care about funding as signal of stability) - [ ] Investor thank-you (acknowledge everyone who took meetings) - [ ] LinkedIn + social media update - [ ] Update website (add investor logos if appropriate) Phase 5 completion indicators: - The term sheet's binding and non-binding provisions are understood and counsel-reviewed. - Operative documents, approvals, cap-table changes, and closing conditions are reconciled. - Funds are verified as received before the company treats the financing as closed. - Any announcement is lawful, accurate, authorized, and consistent with confidentiality obligations. - The post-close operating and governance plan has accountable owners and downside triggers. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-detailed-version-week-by-week-metrics", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Detailed Version: Week-by-Week Metrics", "headingId": "chapter-15-fundraising-and-finance-detailed-version-week-by-week-metrics", "url": "#chapter-15-fundraising-and-finance-detailed-version-week-by-week-metrics", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 15.21: Author-created or source-bounded decision aid (Week | Phase | Key Activities | Meetings | Outputs ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Week | Phase | Key Activities | Meetings | Outputs| | :--- | :--- | :--- | :--- | :---| | 1-4 | Preparation | Deck, model, investor list, practice | 0 | Materials ready | | 5-6 | Outreach | Warm intros requested | 0 | 15+ meetings scheduled | | 7-8 | Outreach | Cold outreach, scheduling | 2-3 | Calendar full for 4 weeks | | 9-10 | First Meetings | Initial investor meetings | 6-8 | Feedback themes identified | | 11-12 | First Meetings | Partner meetings, iteration | 4-6 | 3-5 hot leads | | 13-14 | Due Diligence | Materials shared, references | 2-3 | Active DD with 2-3 investors | | 15-16 | Due Diligence | Reference calls completed | 1-2 | Term sheet expected | | 17-18 | Term Sheet | Negotiation | 1-2 | Term sheet signed | | 19-20 | Closing | Legal docs, wire transfer | 0 | Money in bank | Total timeline: 16-20 weeks in this constructed Series A planning case; it is not a market-standard duration or forecast. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-common-pitfalls", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Common Pitfalls", "headingId": "chapter-15-fundraising-and-finance-common-pitfalls", "url": "#chapter-15-fundraising-and-finance-common-pitfalls", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The examples below are constructed diagnostics. Replace every count, percentage, response rate, timing, and runway value with a dated, company-specific definition and decision rule. 1. Weak Metrics / Unclear Traction - Problem: Pitch says \"growing fast\" but provides no numbers, or numbers are not strong enough for the stage and market - Impact: Investor skeptical - if traction is unclear, they assume it's bad - Solution: Lead with strongest 2-3 metrics (ARR, growth rate, customer logos). If early-stage, emphasize customer feedback, LOIs, or beta engagement. - Example: \"We have 10,000 users\" (unclear) vs. \"We have 1,000 paying customers at $100/mo, 40 percent MoM growth, <5 percent churn\" (clear) 2. No Warm Introductions / Over-Reliance on Cold Outreach - Problem: Founder sends 500 cold emails, gets 3 meetings (0.6 percent conversion) - Impact: Wastes time, demoralizing, signals lack of network - Solution: Activate network first - advisors, founder friends, accelerator connections, existing investors. Warm introductions usually outperform cold outreach. - Red Flag: If the permitted network does not produce a credible access path, diagnose access, fit, and positioning; do not infer character or coachability from an introduction count. - How to Fix: Join founder communities (YC, Techstars, local startup groups), ask for intros systematically 3. Vague Value Proposition in Pitch - Problem: Pitch says \"We make data engineering easier\" (what does that mean?) - Impact: Investor can't understand the opportunity - if they don't get it in 60 seconds, they pass - Solution: Lead with specific, quantified value. \"We reduce data pipeline deployment from 3 weeks to 3 days, saving data teams $500K/year in engineering time.\" - Test: If you can't explain your value prop in one sentence to your grandmother, it's too vague 4. Solo Founder Decision-Making / Slow Term Sheet Negotiation - Problem: Founder needs to \"check with co-founder\" on every term, delaying negotiation by days - Impact: Investor loses confidence - if founders can't decide quickly on fundraising terms, how will they make product decisions? - Solution: Align with co-founder BEFORE term sheet on key red lines (minimum valuation, liquidation preference, board control). Empower one founder to negotiate with check-ins. - Best Practice: Weekly co-founder sync during fundraise to stay aligned 5. Ignoring Cap Table / Dilution Surprises - Problem: Founder doesn't model cap table before term sheet, shocked to discover they own 40 percent post-round (expected 50 percent) - Impact: Founder upset, potentially kills deal, damages relationship with investor - Solution: Model cap table BEFORE pitching. Use Carta, Pulley, or simple Excel to calculate post-money ownership under different scenarios. - Example: - Pre-raise: Founders 75 percent, employees 10 percent, seed investors 15 percent - Raising $5M at $25M post-money = 20 percent dilution - Post-raise: Founders 60 percent, employees 8 percent, seed 12 percent, new investors 20 percent - Key Question: Are you comfortable with this dilution? If not, raise less or negotiate higher valuation. Additional Pitfalls: 6. Fundraising Without Enough Runway - Problem: Start fundraising with 3 months cash left - too late - Impact: Desperate, accept bad terms, may run out of money - Solution: Start when the downside cash model leaves enough time for the actual process, approvals, contingencies, and alternatives; no universal runway threshold applies. 7. Pitching Too Many Investors Simultaneously - Problem: Send pitch to 50 investors in week 1, get 30 meetings, can't handle volume - Impact: Poor meetings (rushed, unprepared), can't iterate pitch, burn relationships - Solution: Stagger outreach - 5-10 investors per week, allows time for feedback and iteration 8. No Follow-Up System - Problem: Investor says \"Let's reconnect in 2 weeks\" and founder forgets - Impact: Missed opportunities, signals lack of organization - Solution: Use investor tracking spreadsheet with next action and date for every interaction 9. Overselling / Inflating Metrics - Problem: Pitch says \"$1M ARR\" but it's actually $500K - Impact: Discovered in diligence, deal dies, reputation damaged - Solution: Be honest - investors respect transparency. If growth is slow, explain why and what you're doing about it. 10. Not Practicing Pitch - Problem: First investor meeting is first time saying pitch out loud - Impact: Stumbles, forgets key points, can't answer basic questions - Solution: Practice with advisors, founder friends, or record yourself 5+ times before first meeting ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-measurement-framework", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Measurement Framework", "headingId": "chapter-15-fundraising-and-finance-measurement-framework", "url": "#chapter-15-fundraising-and-finance-measurement-framework", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Track these metrics at a cadence appropriate to the process, and label each target as a constructed planning input rather than a market benchmark. Use them to identify issues—not to infer funding probability." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-outreach-metrics", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Outreach Metrics", "headingId": "chapter-15-fundraising-and-finance-outreach-metrics", "url": "#chapter-15-fundraising-and-finance-outreach-metrics", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Constructed metric examples (not benchmarks): The percentages and labels below show how to define a dashboard; replace them with a dated baseline and locally approved trigger. Response Rates: - Warm intro response rate (illustrative example): 30-50 percent of requested introductions lead to a first meeting in this constructed dashboard; replace with a dated baseline - Formula: (First meetings scheduled / Warm intros requested) × 100 - Example: 10 meetings from 25 warm intros = 40 percent (healthy) - Illustrative diagnostic: a low result prompts review of access, fit, deliverability, and positioning; it does not diagnose the cause - Cold outreach response rate (illustrative example): 1-3 percent in this constructed dashboard; replace with a dated baseline and deliverability definition - Formula: (Responses / Cold emails sent) × 100 - Example: 5 responses from 200 emails = 2.5 percent (normal) - Illustrative diagnostic: a low result prompts review of audience, deliverability, permissions, and message quality Meeting Conversion: - First meeting to follow-up (illustrative example): 20-30 percent in this constructed dashboard; replace with a dated baseline - Formula: (Follow-up meetings requested / First meetings completed) × 100 - Example: 3 follow-ups from 10 first meetings = 30 percent (strong) - Illustrative diagnostic: a low result prompts review of evidence, audience fit, and message clarity - Follow-up to term sheet (illustrative example): 20-40 percent of serious follow-ups in this constructed dashboard; do not infer a funding probability - Formula: (Term sheets received / Investors in diligence) × 100 - Example: 1 term sheet from 3 investors in diligence = 33 percent (expected) Weekly Tracking:" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-pitch-meeting-metrics", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Pitch Meeting Metrics", "headingId": "chapter-15-fundraising-and-finance-pitch-meeting-metrics", "url": "#chapter-15-fundraising-and-finance-pitch-meeting-metrics", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Interest Levels Tracked: - Hot (wants next step immediately): 20-30 percent is a constructed example, not a target or expected rate - Signals: \"Let's schedule partner meeting\", \"Can you send financials?\", \"I'd like to start diligence\" - Warm (interested but needs more): 30-40 percent is a constructed example, not a target or expected rate - Signals: \"Interesting, let's reconnect in 2 weeks\", \"Send me updates monthly\" - Cool (not now): 20-30 percent is a constructed example, not a target or expected rate - Signals: \"Too early for us\", \"Not our thesis\", \"Reconnect when you hit $X milestone\" - Pass (not interested): 10-20 percent is a constructed example, not a target or expected rate - Signals: \"Not a fit\", \"Market too crowded\", \"Team concern\" Feedback Patterns Identified: Track recurring themes in investor feedback to identify pitch weaknesses. Example Feedback Log: Table 15.22: Author-created or source-bounded decision aid (Theme | Count | Example Quote | Action ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Theme | Count | Example Quote | Action| | :--- | :--- | :--- | :---| | Market size concern | 5 | \"TAM seems small\" | Add bottom-up TAM calculation | | Competitive worry | 4 | \"How do you beat PipeLink?\" | Add competitive matrix slide | | Unit economics | 3 | \"CAC seems high\" | Show payback period improving | | Team gap | 2 | \"Need VP Sales\" | Add hiring plan slide | Illustrative trigger: If a recurring concern appears in a sufficient and diverse sample, update or test the pitch after checking whether the evidence is comparable and decision-relevant; no count is universal." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-due-diligence-metrics", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Due Diligence Metrics", "headingId": "chapter-15-fundraising-and-finance-due-diligence-metrics", "url": "#chapter-15-fundraising-and-finance-due-diligence-metrics", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Timeline Tracking: - Diligence initiation to term sheet (illustrative process range): 2-4 weeks in this constructed dashboard; record actual dates and conditions rather than treating the range as a norm - Track per investor: How long from \"let's start diligence\" to \"here's a term sheet\"? - Fast (1-2 weeks): Very interested, competitive situation - Illustrative planning case (2-4 weeks): one possible process range, not a normality claim - Slow (4+ weeks): Lower priority, may be using you for market research - Red flag: 6 weeks suggests investor not serious Diligence Request Responsiveness: - Materials provided within (illustrative service-level example): <48 hours in this constructed dashboard; set the actual service level from quality, privilege, privacy, and operating capacity - Track: How quickly are you providing requested materials? - Formula: (Requests answered within 48h / Total requests) × 100 - Illustrative target: define a response service level that preserves quality, privilege, privacy, and operating continuity Customer Reference Quality: - Positive references (illustrative example): 80 percent+ in this constructed dashboard; define “positive,” sampling, consent, and attribution locally - Track: What % of customers give strong recommendation? - Strong: \"We'd be devastated if they shut down\", \"10/10 would recommend\" - Weak: \"It's fine\", \"We could find alternatives\" - Illustrative diagnostic: mixed references prompt review of product, customer selection, attribution, and investor-specific evidence rules; they do not establish a single product or fundraising cause" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-closing-metrics", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Closing Metrics", "headingId": "chapter-15-fundraising-and-finance-closing-metrics", "url": "#chapter-15-fundraising-and-finance-closing-metrics", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Term Sheet Timeline: - First meeting to term sheet (illustrative process range): 6-10 weeks in this constructed dashboard; record actual dates and conditions rather than treating the range as a norm - Track per investor: How long from first pitch to term sheet? - Formula: (Term sheet date - First meeting date) / 7 weeks - Fast (4-6 weeks): Strong interest - Illustrative planning case (6-10 weeks): one possible process range, not a normality claim - Slow (10+ weeks): Lower conviction Money in Bank: - Term sheet to close (illustrative process range): 2-4 weeks in this constructed dashboard; follow actual documents, approvals, and closing conditions - Track: How long from signed term sheet to money in account? - Legal drafting: 1-2 weeks - Final diligence: 1 week - Wire transfer: 1-3 days - If 6 weeks: Legal issues, cold feet, or diligence problems Cap Table Accuracy: - Cap table updated within (illustrative control example): <24 hours of close in this constructed dashboard; set the actual control deadline with the finance/legal owners - New share issuance reflected - Founder ownership % correct - Option pool updated - All investor ownership documented - Use Carta, Pulley, or Excel to maintain" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overall-fundraise-health-dashboard", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overall Fundraise Health Dashboard", "headingId": "chapter-15-fundraising-and-finance-overall-fundraise-health-dashboard", "url": "#chapter-15-fundraising-and-finance-overall-fundraise-health-dashboard", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Track these weekly to assess overall momentum: Constructed dashboard example (not a benchmark or forecast): ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-red-flags-when-fundraising-is-stalling", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flags: When Fundraising Is Stalling", "headingId": "chapter-15-fundraising-and-finance-red-flags-when-fundraising-is-stalling", "url": "#chapter-15-fundraising-and-finance-red-flags-when-fundraising-is-stalling", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use these signals to identify when fundraising is off track and needs course correction. The thresholds and elapsed times below are constructed diagnostic examples, not universal investor behavior, legal deadlines, or readiness rules. Test the underlying evidence, ask the counterparty to clarify the decision, and use the actual runway and obligations to set escalation points." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-outreach-red-flags", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Outreach Red Flags", "headingId": "chapter-15-fundraising-and-finance-outreach-red-flags", "url": "#chapter-15-fundraising-and-finance-outreach-red-flags", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative signal: Low meeting conversion - Diagnosis to test: Access, audience fit, deliverability, positioning, timing, or permissions may be contributing; do not infer one cause from a rate. - Action: - Review one-pager: Is value prop clear? Are metrics compelling? - Check intro quality: Are connectors actually warm with investors? - Test messaging: Try different subject lines, value props - Timeline: Reassess after the locally defined review sample and runway checkpoint. Illustrative signal: No credible next step after a sufficient conversation sample - Diagnosis to test: Evidence, fit, process, price, rights, capacity, or timing may be unresolved; do not call the company fundamentally wrong. - Action: - Deep feedback session: Ask willing investors who passed what observable evidence, fit, or timing condition would change the decision. - Compare to funded companies: What do they have that you don't? (Traction? Team? Market?) - Consider pausing fundraise: May need more traction before investors will bite - Timeline: Consider pausing when the locally defined review sample, runway, or evidence rule indicates that continuing is not responsible." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-pitch-meeting-red-flags", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Pitch Meeting Red Flags", "headingId": "chapter-15-fundraising-and-finance-pitch-meeting-red-flags", "url": "#chapter-15-fundraising-and-finance-pitch-meeting-red-flags", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative signal: Same feedback theme recurs in a sufficient sample - Diagnosis: Investors see fundamental flaw you haven't addressed - Common Themes: - \"Market too small\" → Your TAM analysis is weak or market not proven - \"Too competitive\" → You haven't differentiated or competitors have big lead - \"Unit economics don't work\" → CAC too high or LTV too low - \"Team gap\" → Missing critical role (CTO, VP Sales, domain expert) - Action: - If solvable (TAM analysis, competitive positioning): Update pitch immediately - If structural (team gap, unit economics): May need to solve before fundraising - Timeline: Decide whether to pause, revise, or continue only after identifying whether the feedback is substantiated, decision-relevant, and solvable within the runway and disclosure plan. Illustrative signal: Investors repeatedly say \"Too Early\" - Diagnosis to test: The evidence, mandate, timing, or process may not fit; do not infer product-market fit status from the phrase alone. - Action: - Ask: \"What milestone would make this investable for you?\" - Constructed workshop answers might include a recurring-revenue milestone, a customer milestone, or profitability; replace them with the venture's evidence-based decision trigger. - Return to building: Hit that milestone, then restart fundraise - Timeline: Pause or continue only after defining the evidence rule and runway consequence; no response-rate cutoff is universal" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-due-diligence-red-flags", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Due Diligence Red Flags", "headingId": "chapter-15-fundraising-and-finance-due-diligence-red-flags", "url": "#chapter-15-fundraising-and-finance-due-diligence-red-flags", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative signal: Diligence remains unresolved beyond the local review window - Diagnosis to test: An evidence gap, approval, capacity constraint, document issue, or changed decision may be involved. - Action: - Direct ask: \"Are we still on track for a term sheet? What's the timeline?\" - If vague answer: Investor is passing softly, move on - Parallel track: Don't wait for one investor - keep other conversations active - Timeline: If the process has remained unresolved beyond the locally defined review window, ask for a dated decision or reallocate time; do not assume a pass from elapsed time alone. Illustrative signal: Customer references are mixed or lukewarm - Diagnosis to test: Product value, customer selection, attribution, cohort maturity, concentration, or reference permissions may be unresolved. - Action: - Customer feedback loop: Why aren't they enthusiastic? What needs improvement? - Product prioritization: Fix issues before continuing fundraise - Honest assessment: Weak or unrepresentative customer evidence can affect financing; test the evidence, attribution, concentration, and investor-specific decision rule rather than predicting an outcome. - Timeline: Pause or continue according to the defined evidence rule, runway, and product/customer review—not a universal reference percentage Signal: Multiple Diligence Requests for Same Document - Diagnosis: Your materials are incomplete or poorly organized - Action: - Build comprehensive data room: Organize all materials in shared folder (Google Drive, Dropbox) - Checklist: Corporate docs, financials, customer list, cap table, contracts, references - Proactive sharing: Send data room link at start of diligence (before they ask) - Timeline: Fix immediately - shows lack of preparation" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-closing-red-flags", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Closing Red Flags", "headingId": "chapter-15-fundraising-and-finance-closing-red-flags", "url": "#chapter-15-fundraising-and-finance-closing-red-flags", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative signal: Term-sheet negotiation exceeds the local review window - Diagnosis to test: A term, approval, document, authority, or changed decision may be blocking progress. - Action: - Identify sticking point: What specific term is blocking? (Valuation? Board control?) - Assess walkaway point: What's your minimum acceptable deal? - Consider alternatives: Do you have other term sheets to create competition? - Timeline: Ask directly when the locally defined review window is exceeded: \"Are we aligned on terms? If not, let's discuss differences openly.\" Illustrative signal: Legal documentation exceeds the local review window - Diagnosis to test: Drafting scope, counsel capacity, unusual terms, approvals, or hidden issues may be causing delay. - Action: - Lawyer check-in: \"What's causing delay? Are there unexpected issues?\" - Investor check-in: \"Is your team still aligned on closing?\" - Flag problems: If investor adding new terms post-term sheet, consider walking away - Timeline: Do not call a duration standard. If the actual process exceeds the locally defined review window, ask what document, approval, or issue is causing the delay. Illustrative signal: Money has not hit the account after the stated closing condition - Diagnosis: Final diligence issue, wire transfer problem, or cold feet - Action: - Daily check-ins: \"What's the status? Any blocking issues?\" - Bank confirmation: Ensure wire instructions are correct - Legal escalation: Have lawyers communicate directly - Timeline: Chase daily until money arrives - deal isn't done until cash in bank" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-overall-health-red-flags", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Overall Health Red Flags", "headingId": "chapter-15-fundraising-and-finance-overall-health-red-flags", "url": "#chapter-15-fundraising-and-finance-overall-health-red-flags", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Illustrative signal: Runway is approaching the approved solvency or contingency boundary without a term sheet - Diagnosis to test: Time, obligations, financing capacity, and alternatives may be narrowing; do not import a universal month count. - Action: - Bridge round: Ask existing investors whether a documented extension is feasible under the actual runway and terms. - Cut burn: Reduce expenses to extend runway - Timeline: Model the actual term-sheet, approval, document, and funding conditions; do not assume a close duration. - Timeline: URGENT - address immediately Illustrative signal: The process consumes the approved review window without a close - Diagnosis to test: Evidence, fit, process, terms, capacity, market conditions, or alternatives may be responsible; do not treat elapsed time as a market verdict. - Action: - Honest assessment: Talk to advisors, successful founders in your space - Options: - Smaller round: Lower raise amount, less dilution - Revenue-based financing: Non-dilutive capital to extend runway - Pause and build: Return to product, hit next milestone - Morale management: Team and existing investors are watching - communicate plan - Timeline: If the actual process consumes the runway or approved review window without a credible path, make a documented continue/revise/pause/stop decision." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-how-to-use-red-flags", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "How to Use Red Flags", "headingId": "chapter-15-fundraising-and-finance-how-to-use-red-flags", "url": "#chapter-15-fundraising-and-finance-how-to-use-red-flags", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Weekly Red Flag Check: 1. Review metrics dashboard (see Measurement Framework) 2. Identify any red flags present 3. Assess severity (minor concern vs. major blocker) 4. Take corrective action immediately 5. Track if issue resolves in 1-2 weeks Example Assessment: Decision Points: - 1-2 red flags: Normal - address and continue - 3-4 red flags: Concerning - may need pivot in approach - 5+ red flags: Stalled - consider pausing fundraise ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-why-this-matters-mental-models-fundraising-wisdom", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Why This Matters: Mental Models & Fundraising Wisdom", "headingId": "chapter-15-fundraising-and-finance-why-this-matters-mental-models-fundraising-wisdom", "url": "#chapter-15-fundraising-and-finance-why-this-matters-mental-models-fundraising-wisdom", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Fundraising combines information asymmetry, signaling, incentives, cash constraints, governance, and long-term relationships. This section uses constructed comparisons to surface trade-offs; every probability, weight, fund behavior, stage threshold, deal term, outcome, and causal statement is a hypothesis, not an empirical benchmark. The bounded named cases remain in Section 13." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-1-momentum-as-one-evidence-pattern", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "1. Momentum as One Evidence Pattern", "headingId": "chapter-15-fundraising-and-finance-1-momentum-as-one-evidence-pattern", "url": "#chapter-15-fundraising-and-finance-1-momentum-as-one-evidence-pattern", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Revenue, retention, use, customer outcomes, and operating progress can update beliefs when definitions, cohorts, attribution, cash consequences, and uncertainty are clear. None “proves” the venture's assumptions, lowers failure risk by a known amount, validates an entire market, or justifies a valuation on its own. [BB-C15-S06] [BB-C15-S07] Investor interest and scarcity can also influence a process, but managers should not manufacture competition, misrepresent demand, or infer favorable terms from growth. Compare financing while the company has sufficient cash and options where feasible; the right timing depends on operating milestones, runway distribution, disclosure readiness, market conditions, actual terms, alternatives, and stakeholder risk—not “maximum momentum” or presumed investor psychology." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-2-unit-economics-as-a-scenario-model", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "2. Unit Economics as a Scenario Model", "headingId": "chapter-15-fundraising-and-finance-2-unit-economics-as-a-scenario-model", "url": "#chapter-15-fundraising-and-finance-2-unit-economics-as-a-scenario-model", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Cohort contribution, acquisition cost, retention, expansion, service cost, gross margin, cash timing, fixed costs, capacity, and uncertainty can inform a financing decision. LTV:CAC is one model, not proof of profitability or scalability, and a 3:1 ratio is not a universal pass/fail rule. [BB-C15-S06] [BB-C15-S07] For any constructed example, show definitions, cohort and observation window, censored data, acquisition allocation, gross-margin and service costs, churn or survival method, discounting, payback, uncertainty, and sensitivity. A high ratio can coexist with small demand, long cash payback, selection bias, capacity limits, or omitted costs; a low early estimate may reflect learning or measurement error. Decide what evidence is sufficient from the operating plan, cash, risk, sector, and actual investor or lender requirements rather than asserting that one metric proves the model or commands a premium valuation." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-3-narrative-as-a-testable-explanation", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "3. Narrative as a Testable Explanation", "headingId": "chapter-15-fundraising-and-finance-3-narrative-as-a-testable-explanation", "url": "#chapter-15-fundraising-and-finance-3-narrative-as-a-testable-explanation", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A financing narrative should connect the customer problem, mechanism, evidence, operating plan, risks, capital use, governance, and alternatives in terms a decision-maker can inspect. It is not a valuation method, and growth, market size, a category label, or a named-company analogy does not prove the narrative or justify a financing price. [BB-C15-S06] [BB-C15-S07] Analogies and archetypes can prompt questions but also create survivorship, availability, base-rate, and false-equivalence errors. Test the underlying mechanism, differences, counterevidence, and downside. Unsupported named-company and fixed market/valuation examples have been removed. Judge clarity by whether the actual decision, assumptions, evidence, uncertainty, and use of funds are understandable and challengeable—not by a hero/villain template, a two-sentence rule, emotional response, or claimed investor excitement." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-4-diversified-capital-why-multiple-funding-sources-de-risk-execution", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "4. Diversified Capital: Why Multiple Funding Sources De-Risk Execution", "headingId": "chapter-15-fundraising-and-finance-4-diversified-capital-why-multiple-funding-sources-de-risk-execution", "url": "#chapter-15-fundraising-and-finance-4-diversified-capital-why-multiple-funding-sources-de-risk-execution", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Decision principle: Considering multiple capital sources can reveal alternatives, but it does not guarantee diversification, leverage, eligibility, availability, or better terms. Each source can add cost, covenants, collateral, consent rights, concentration, execution burden, disclosure, or strategic constraints. Comparing alternatives: When multiple executable offers exist, compare complete terms and operating consequences; alternatives do not confer control over the negotiation: - Scenario 1 (few alternatives): A fund offers $5M at $15M post-money with three months of modeled runway. The board still must compare the full terms with cost reduction, bridge/debt, sale, restructuring, and no-deal outcomes under solvency and fiduciary constraints. - Scenario 2 (With alternatives): VC offers $5M at $15M post-money. You also have: (1) Revenue-based financing offer for $2M, (2) Debt offer for $3M, (3) Strategic investor interest. You can negotiate: \"We'll take your $5M if you go to $20M post-money, otherwise we'll do debt + revenue financing.\" The Types of Capital: Table 15.23: Author-created or source-bounded decision aid (Source | Cost | Control | Best For ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Source | Cost | Control | Best For| | :--- | :--- | :--- | :---| | Venture Capital | Meaningful dilution | Medium (board seats) | High-growth, winner-take-all markets | | Debt | Interest, fees, warrants, collateral, and default cost as applicable | Covenants, security, reporting, consent, cash-sweep, guarantee, or other rights may constrain control | Eligible borrowers whose downside cash and collateral case supports the actual terms | | Revenue-Based | Revenue share, cap/multiple, fees, and cash-timing cost | Reporting, payment, covenant, security, consent, or operating constraints depend on the agreement | Eligible revenue profiles after downside repayment and growth-capacity testing | | Strategic Investor | Dilution + strategic strings | Medium-High (alignment needed) | Market access, partnerships | | Customers (prepayment) | Discounted economics | Low (customers, not investors) | Enterprise, annual contracts | Why Diversification Works: - Potential negotiating option: A credible executable alternative can change the walk-away set, but it does not force better terms. - Availability risk: A market shock can reduce several capital sources simultaneously; non-VC capital remains subject to eligibility, underwriting, collateral, covenants, and provider capacity. - Portfolio trade-off: A mix can reduce one exposure while adding repayment, consent, complexity, or correlated refinancing risk; model complete terms and downside cash. The Failure Mode: Constructed contrast: One team pursues only a $5M Series A and has no documented alternative if investors decline. Another evaluates $3–5M across equity, debt, strategic capital, staged spending, and operating changes while modeling 18 months of runway. The second team has more explicit options, but each alternative carries different eligibility, rights, cost, risk, and timing; it is not automatically better. The Strategic Insight: Liquidity-planning hypothesis: Beginning a financing process before the downside runway trigger can preserve more alternatives, but raising too early can create distraction, dilution, disclosure, and opportunity costs. Scenario-test timing and diversified capital sources; neither guarantees leverage or available options. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-evidence-grounded-diligence-cases", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Evidence-Grounded Diligence Cases", "headingId": "chapter-15-fundraising-and-finance-evidence-grounded-diligence-cases", "url": "#chapter-15-fundraising-and-finance-evidence-grounded-diligence-cases", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the three bounded primary-record cases in Section 13 . They illustrate different evidence classes: an issuer S-1, an SEC enforcement release, and congressional testimony from a post-bankruptcy debtor CEO. Do not merge them into a single causal story or add the earlier Zenefits narrative without authoritative regulator, company, transaction, and court sources. For an applied exercise, classify each material statement as issuer disclosure, regulator allegation, settlement, sworn testimony, adjudicated fact, management forecast, or inference. Then identify the operating, financial, technical, governance, customer, and legal evidence that would confirm or disconfirm it. [BB-C15-S17] [BB-C15-S18] [BB-C15-S19] ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-1-venture-capital-vs-strategic-investment-growth-vs-synergy", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "1. Venture Capital vs. Strategic Investment (Growth vs. Synergy)", "headingId": "chapter-15-fundraising-and-finance-1-venture-capital-vs-strategic-investment-growth-vs-synergy", "url": "#chapter-15-fundraising-and-finance-1-venture-capital-vs-strategic-investment-growth-vs-synergy", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Venture capital hypotheses to test: - Possible thesis: Speed, growth, scale, or network effects may matter to a particular fund; verify its current mandate. - Evidence to examine: Growth, reachable demand, retention, cash use, market structure, governance, and downside—not a universal TAM or growth rule. - What They May Provide: Capital under negotiated terms, relevant operating experience, governance, and introductions; verify the particular investor's check range, capacity, conflicts, incentives, and evidence of value-add. - What They May Receive: Negotiated equity, preferences, board, voting, information, transfer, and future-financing rights; model the actual documents - Possible Fit: Ventures whose evidence, capital needs, governance, and downside fit the particular fund's mandate Strategic investment hypotheses to test: - Possible thesis: Strategic fit may create value for both parties, but conflicts and execution costs can offset it. - Evidence to examine: Customer access, product integration, market access, alignment, conflicts, dependency, and actual decision rights. - What They May Provide: Capital, customer introductions, distribution, technology partnership, or industry expertise; verify the particular commitment. - What They May Receive: Negotiated equity, board, consent, information, transfer, exclusivity, or other rights; model the actual documents. - Possible Fit: A venture whose operating plan benefits from the specific strategic capability without unacceptable lock-in or channel conflict The Trade-offs: Table 15.24: Author-created or source-bounded decision aid (Dimension | Venture Capital | Strategic Investment ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Dimension | Venture Capital | Strategic Investment| | :--- | :--- | :---| | Motivation | Financial return | Strategic fit | | Involvement | Board oversight, quarterly review | Deep operational involvement | | Exit and liquidity | Fund mandate, reserves, portfolio construction, and liquidity expectations require verification | Strategic objectives, ownership, liquidity, and transaction horizon require verification | | Conflicts | Analyze mandate, portfolio overlap, governance, economics, and information rights | Analyze competition, channel conflict, data, exclusivity, and control rights | | Follow-on | Depends on reserves, authority, performance, and current fund policy | Depends on strategic priority, budget, authority, and the actual documents | Conditions that may favor financial capital: - The operating plan needs capital without a strategic dependency, and the proposed financial terms are acceptable. - Scale, timing, or optionality matter, but the actual market, governance, and downside evidence supports the plan. - A corporate investor does not provide a unique, verified capability or would create unacceptable conflicts. Conditions that may favor strategic capital: - The corporate partner can provide a specific, permissioned capability that is material to the operating plan. - The benefit is supported by accountable commitments, while lock-in, channel conflict, data, exclusivity, and control risks remain acceptable. A hybrid approach to test: Some ventures combine financial and strategic capital at different stages, while others avoid one source because of governance, conflict, concentration, or disclosure risk. Choose the sequence from the operating plan, evidence, authority, actual terms, and alternatives—not from a stage recipe or a claim about “most successful” companies. Possible strategic failure modes: Taking strategic investment before testing the full package can create: 1. Lock-in: A right of first refusal or similar term may affect a sale to a competitor. 2. Channel conflict: A corporate investor that is also a customer or competitor may change other buyers' willingness to engage. 3. Loss of independence: Board, consent, information, exclusivity, or commercial rights may constrain strategy. Decision boundary: Consider a strategic investor when its verified, accountable contribution is material and the complete rights/conflict package remains acceptable. If it provides only capital, compare the same capital from other sources and model the constraints rather than using a universal “best approach.”" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-2-financing-choice-as-a-portfolio-of-constraints-and-options", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "2. Financing Choice as a Portfolio of Constraints and Options", "headingId": "chapter-15-fundraising-and-finance-2-financing-choice-as-a-portfolio-of-constraints-and-options", "url": "#chapter-15-fundraising-and-finance-2-financing-choice-as-a-portfolio-of-constraints-and-options", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Bootstrapping, external equity, debt, grants, customer funding, and partnerships are not two mutually exclusive schools with fixed outcomes. Compare them using the cash need, evidence milestones, revenue timing, downside loss, governance rights, covenants, dilution, option value, founder concentration, and feasible terms described in Section 11. [BB-C15-S07] [BB-C15-S15] A constructed comparison can test a self-funded path, a staged external-capital path, and a no-next-round downside. Do not insert named-company success stories, fixed founder-ownership outcomes, or assumed valuation multiples without verified, as-of evidence and full transaction context." }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-3-term-package-effects-across-stakeholders", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "3. Term-Package Effects Across Stakeholders", "headingId": "chapter-15-fundraising-and-finance-3-term-package-effects-across-stakeholders", "url": "#chapter-15-fundraising-and-finance-3-term-package-effects-across-stakeholders", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "“Founder-friendly” and “investor-friendly” labels conceal who bears which risk and can misstate legal, employee, creditor, and governance effects. Analyze each provision and the package across stakeholders and scenarios. [BB-C15-S08] [BB-C15-S09] [BB-C15-S10] [BB-C15-S11] Required assumptions for any waterfall example: - Distributable proceeds after debt, fees, escrow, indemnity holdbacks, transaction expenses, and other senior claims - Security classes, invested capital, seniority, preference multiples, dividends, participation and caps - Optional and automatic conversion decisions, as-converted shares, warrants/options, and vesting - Tax, employment/compensation, transfer, board/shareholder approval, and governing-document terms Without these inputs, a statement assigning a fixed payout to founders is not valid. Table 15.25: Author-created or source-bounded decision aid (Provision | Questions to model ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Provision | Questions to model| | :--- | :---| | Liquidation | Who receives what at each exit value under seniority, multiple, participation/cap, dividends, conversion, debt, fees, escrow, and tax? | | Board/control | Who appoints/removes directors, holds class votes or protective rights, manages conflicts, and owes fiduciary duties? Percentage ownership alone does not establish control. | | Anti-dilution/pay-to-play | Which formula, capitalization denominator, excluded issuances, participation condition, and recapitalization effects apply? | | Founder and employee vesting | What prior service, future commitment, acceleration, repurchase, leaver, option, tax, compensation, employment, and approval rules apply? No universal four-year/cliff outcome is assumed. | | Information/pro-rata/transfer | What access, privacy/privilege, follow-on, allocation, ROFR/co-sale, drag/tag, and amendment rights apply? | | Closing provisions | Which exclusivity, expenses, confidentiality, conditions, approvals, and termination terms bind? | Negotiation process: 1. Model the full package, not only headline valuation or three favored terms. 2. Compare feasible financing and no-deal alternatives under downside cash and operating scenarios. 3. Use current comparable documents only when definitions, stage, jurisdiction, rights, and as-of date are genuinely comparable; “market standard” is not self-proving. 4. Record conflicts, dissent, authority, and the rationale for accepting or rejecting each material trade-off. 5. Obtain qualified counsel and tax/accounting review against the actual documents. Terms can matter as much as price, but which package is preferable depends on security-specific proceeds, governance, operating plan, alternatives, and stakeholder outcomes. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-context-dependent-capital-strategy", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Context-Dependent Capital Strategy", "headingId": "chapter-15-fundraising-and-finance-context-dependent-capital-strategy", "url": "#chapter-15-fundraising-and-finance-context-dependent-capital-strategy", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Round labels such as “seed,” “Series A,” or “growth” do not determine the correct metrics, check size, valuation, dilution, runway, investor type, or decision. Market conditions, jurisdiction, instrument, sector, revenue model, technical and regulatory evidence, capital intensity, governance, and bargaining alternatives can vary materially over time. Table 15.26: Author-created or source-bounded decision aid (Decision area | Evidence to examine ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Decision area | Evidence to examine| | :--- | :---| | Problem and demand | Quality of customer evidence, willingness and ability to pay, retention, alternatives, and uncertainty—not a required interview or customer count. | | Operating mechanism | Product/service performance, delivery capacity, unit and cohort economics, quality, safety, compliance, and leading failure modes. | | Capital requirement | Uses of funds, staged milestones, working capital, contingency, runway distribution, and a no-next-round case. | | Financing terms | Security-specific economics, dilution, preferences, governance, covenants, information and transfer rights, tax, and closing conditions. | | Growth and efficiency | Metric definitions, cohort mix, denominator, uncertainty, cash consequences, and whether growth is incremental and durable. No universal LTV:CAC, retention, payback, or growth threshold applies. | | Team and governance | Capabilities, gaps, incentives, decision rights, succession, controls, conflicts, and stakeholder effects—not a prescribed executive roster. | | Market and exit optionality | Market structure, competition, financing environment, plausible operating paths, liquidity constraints, and alternatives to an exit. | Use current comparable evidence only when definitions, stage, rights, jurisdiction, sector, and as-of date are genuinely comparable. Historical named-company anecdotes and invented investor names do not establish a financing rule. Record assumptions, sensitivities, dissent, and the human owners of legal, tax, accounting, valuation, and financing decisions. Decision rule: Match financing to the evidence-backed operating plan and actual terms, not to a maturity ladder. Revisit the choice when evidence, cash, alternatives, market conditions, or stakeholder consequences change. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-summary-fundraising-finance-frameworks", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Summary: Fundraising & Finance Frameworks", "headingId": "chapter-15-fundraising-and-finance-summary-fundraising-finance-frameworks", "url": "#chapter-15-fundraising-and-finance-summary-fundraising-finance-frameworks", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use one process template at a time: Framework 1 is the conceptual sequence; the Quick/Detailed execution guide and the Operating Manual are optional constructed implementations, not cumulative schedules. The ETA section is an applied extension rather than a core framework. All effort estimates below are planning prompts, not service levels or market norms. Table 15.27: Author-created or source-bounded decision aid (Framework | When to Use | Effort Required ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Framework | When to Use | Effort Required| | :--- | :--- | :---| | Fundraising timeline | Before raising | Define from runway, evidence, approvals, and counterparties | | Pitch deck | Before investor meetings | Set from audience, evidence, confidentiality, and iteration needs | | Valuation methods | Before term sheet | Reproduce methods, ranges, sensitivities, and review owners | | Term sheet negotiation | During funding round | Follow actual documents, counsel scope, approvals, and conditions | | Cap table modeling | Before and after each round | Reconcile security-by-security and independently review | | Investor criteria | Before pitching | Define evidence, fit, conflicts, authority, and uncertainty | | Due diligence prep | Before disclosure | Maintain a controlled request, source, permission, and escalation index | | Financial modeling | Before pitch and ongoing | Link actuals, scenarios, working capital, tax, debt, and cash | | Exit strategy | Board-level planning | Compare liquidity, continuation, sale, and no-deal scenarios | | SAFE vs. convertible | When choosing instrument | Model actual forms, conversion, cash, rights, tax, and downside | | Applied ETA extension | Acquisition financing and transition | Reconcile sources/uses, quality of earnings, debt service, governance, and transition evidence | ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-constructed-case-series-a-financing-decision", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Constructed Case: Series A Financing Decision", "headingId": "chapter-15-fundraising-and-finance-constructed-case-series-a-financing-decision", "url": "#chapter-15-fundraising-and-finance-constructed-case-series-a-financing-decision", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Fictional case: DataFlow, Northstar Ventures, every metric, term, timeline, and result below are constructed. They are not attributable to a real company or investor and are not benchmarks. Decision: DataFlow compares a no-raise operating plan with a $5 million priced round. Its pre-round fully diluted cap table is founders 75 percent, seed holders 15 percent, and unissued option pool 10 percent. Constructed priced-round inputs: - Pre-money value: $20 million - New money: $5 million - Post-money value: $25 million - No SAFE/note conversion, warrant, or pool increase - New-investor ownership: $5M / $25M = 20 percent - Existing-holder retention factor: $20M / $25M = 80 percent Reconciled post-round cap table: Table 15.28: Author-created or source-bounded decision aid (Holder | Pre-round | Post-round calculation | Post-round ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Holder | Pre-round | Post-round calculation | Post-round | | :--- | :--- | :--- | :--- | | Founders | 75 percent | 75 percent x 80 percent | 60 percent | | Seed holders | 15 percent | 15 percent x 80 percent | 12 percent | | Unissued option pool | 10 percent | 10 percent x 80 percent | 8 percent | | Northstar Ventures (fictional) | 0 percent | $5M / $25M | 20 percent | | Total | 100 percent | | 100 percent | The team separately models a 1x non-participating preference, conversion choices, board and protective rights, future financing, three constructed exit values, and a downside cash case. Ownership does not determine those rights. Counsel and tax/accounting reviewers compare the model with the actual proposed documents before any approval. [BB-C15-S08] [BB-C15-S09] Decision memo: Recommend proceeding only if the financing produces a better risk-adjusted operating path than no raise or alternative capital, the disclosures and evidence are supportable, cash and milestones are credible, the full term package is acceptable, and the cap table plus waterfall independently reconcile. Otherwise revise, pause, or stop. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-operating-manual-your-16-week-series-a-fundraising-cycle", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Operating Manual: Your 16-Week Series A Fundraising Cycle", "headingId": "chapter-15-fundraising-and-finance-operating-manual-your-16-week-series-a-fundraising-cycle", "url": "#chapter-15-fundraising-and-finance-operating-manual-your-16-week-series-a-fundraising-cycle", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This constructed operating manual illustrates one possible fundraising workflow. Tailor or reject it based on financing need, stage, jurisdiction, instrument, evidence, investor process, governance, legal advice, and alternatives; it does not define a universal Series A amount or readiness gate. Constructed operating-template boundary: The sixteen-week cadence, revenue, customer, retention, ratio, dilution, runway, fee, investor, and outcome values below are fictional planning inputs—not prerequisites, market standards, or evidence of product-market fit. Replace them with company-specific cash scenarios, measurement definitions, risk/precision requirements, investor fit, legal advice, approval paths, and stop rules. Names in examples are fictional unless an adjacent primary source explicitly identifies a real entity. Timeline overview: The 16-week sequence below is one constructed planning case from fundraising decision to wire transfer; use actual runway, approvals, counterparties, documents, and legal conditions to set the schedule. Prerequisites: - Reconciled revenue quality, retention, unit economics, cash requirements, governance readiness, and milestone evidence appropriate to the contemplated financing; no universal ARR gate applies - Unit economics reconciled for the relevant cohorts, with contribution, acquisition cost, retention, service cost, cash timing, and sensitivity documented; no universal LTV:CAC or payback gate applies - Customer and retention evidence appropriate to the stage and decision, with cohort definitions, concentration, renewals, and attribution documented; no universal customer-count or retention gate applies - Repeatable sales playbook (documented, replicated by team beyond founders) - Cash, obligations, burn, financing alternatives, and downside runway are modeled with an approved solvency and legal stop rule; no universal runway gate applies Outcome Targets: - Closing step, if a financing is actually approved and completed on acceptable terms; neither timing, amount, nor \"fair\" valuation is guaranteed - Dilution, control, preferences, proceeds, and future financing are compared against the approved ownership and governance boundary; no dilution percentage is inherently acceptable - Lead investor secured (Tier 1 or 2 VC firm) - Additional runway is sized from the operating plan, downside case, financing alternatives, and obligations; no universal runway duration is promised - Strategic value-add investors on cap table ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-phase-1-preparation-strategy-weeks-1-4", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 1: Preparation & Strategy (Weeks 1-4)", "headingId": "chapter-15-fundraising-and-finance-phase-1-preparation-strategy-weeks-1-4", "url": "#chapter-15-fundraising-and-finance-phase-1-preparation-strategy-weeks-1-4", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 1: Fundraising Strategy & Investor Targeting Day 1-2: Fundraising Readiness Assessment (8 hours) - Monday Morning (4h): Self-assess readiness - Revenue traction: What revenue, customer, outcome, and cash evidence is decision-relevant for this stage and investor? - Unit economics: Are contribution, acquisition cost, retention, service cost, cash timing, and payback assumptions reconciled for the relevant cohorts? - Retention: Are definitions, cohorts, renewals, expansion, concentration, and censoring clear enough for the decision? - Team: VP Sales or Marketing hire complete? (if not, risk) - Runway: Does the downside cash model leave enough time for the actual process, approvals, contingencies, and alternatives? (do not wait for a solvency crisis) - Output: Readiness scorecard (1-10 on each dimension) - Monday Afternoon (4h): Define fundraising goals - Raise amount: How much capital is justified by the cash plan, milestone evidence, downside case, dilution and rights, and financing alternatives? Do not rely on a generic Series A range. - Use of funds: example allocation across sales/marketing, product/engineering, and G&A - Timeline to next milestone: Define an evidence-based operating and financing runway with explicit downside triggers; no revenue figure or elapsed period guarantees readiness for a later round. - Acceptable dilution: Define the maximum ownership, control, proceeds, and future-financing impact that the board or authorized decision-maker will accept; do not import a universal percentage - Valuation analysis: Compare several methods and scenarios, explain why any comparable is relevant, and show sensitivity to revenue quality, growth, margin, risk, rights, dilution, and market date; do not treat fixed ARR multiples as current facts. - Output: Fundraising goals document (1 page) Day 3-5: Investor Target List (16 hours) - Tuesday Morning (4h): Build investor universe - Tier 1 VCs: Top-tier firms (Northstar Ventures, Harbor Ridge Capital, Summit Arc Capital, top-tier firm) - 10 firms - Tier 2 VCs: Strong regional or sector-focused firms - 20 firms - Tier 3 VCs: Emerging firms with recent traction - 10 firms - Strategic angels: 10-20 angels with relevant expertise - Criteria: Confirm the investor's current check-size range, stage focus, sector thesis, geography, ownership target, reserves, conflicts, and decision process from primary materials or direct inquiry. - Output: Investor universe sized to the thesis, access, capacity, and confidentiality boundary (50 is a constructed example) - Tuesday Afternoon (4h): Research each investor - For each VC/angel: - Recent investments (do they invest in your category?) - Portfolio companies (competitors or complements?) - Decision maker (partner name, focus areas) - Connection path (who can intro you?) - Output: Investor research spreadsheet with notes and source dates for the selected investor universe - Wednesday-Friday (8h): Prioritize and segment - Tier 1 priority (15 investors): Best fit + strong connection path - Tier 2 priority (20 investors): Good fit + possible connection - Tier 3 priority (15 investors): Backup options - Map connection paths: Who can intro you to each Tier 1 investor? - Reach out to potential introducers: \"I'm raising Series A, would you intro me to [investor]?\" - Output: Prioritized investor list with intro status Week 1 Outputs: - Fundraising readiness scorecard - Fundraising goals document (raise amount, use of funds, dilution target, valuation range) - Investor target list (50 investors, prioritized, with connection paths) Week 2-3: Pitch Deck Development Week 2 Day 1-3: Draft Pitch Deck (16 hours) - Monday Morning (4h): Story arc - Slide 1: Company intro (1 sentence what you do, traction headline) - Slide 2: Problem (quantify customer pain) - Slide 3: Solution (how your product solves it) - Slide 4: Why now? (market timing, tailwinds) - Slide 5: Market size (TAM/SAM/SOM) - Slide 6: Product demo (3-4 screenshots with captions) - Slide 7: Business model (pricing, unit economics) - Slide 8: Traction (revenue growth, customer logos, key metrics) - Slide 9: Go-to-market strategy (how you acquire customers) - Slide 10: Competitive landscape (why you vs alternatives) - Slide 11: Team (founders + key hires) - Slide 12: Financials (revenue growth, burn rate, runway) - Slide 13: The ask (raise amount, use of funds, milestones) - Output: Draft pitch deck structure (13 slides) - Monday Afternoon-Wednesday (12h): Content development - Problem slide: Customer quotes, pain quantification ($X lost per year, Y hours wasted) - Solution slide: Value prop, key benefits, differentiation - Market size: Bottom-up calculation (# companies × deal size × % addressable) - Traction slide: Revenue graph (MRR or ARR), growth rate, customer count, logos - Unit economics: CAC, LTV, LTV:CAC ratio, payback period - Financials: 3-year revenue projection, burn rate, path to profitability - The ask: \"$XM Series A to reach $YM ARR in 18 months, expand sales team from Z to Z+W reps\" - Output: Draft deck content (all slides filled in) Week 2 Day 4-5 + Week 3: Design and Iteration (24 hours) - Thursday-Friday Week 2 (8h): Design pass - Visual design: Clean, professional template (avoid generic clip art) - Data visualization: Graphs for traction, unit economics, financials (use real data) - Product screenshots: High-quality, annotated - Consistent branding: Logo, colors, fonts - Output: Designed pitch deck (v1) - Week 3 Monday-Wednesday (16h): Iteration with advisors/mentors - Share deck with 3-5 trusted advisors (ideally former founders who raised Series A) - Ask: \"What's confusing? What's missing? What would you challenge?\" - Common feedback: - \"Market size feels inflated\" → Revise with conservative bottom-up calc - \"Traction not impressive enough\" → Add context (growth rate, reference points) - \"Competitive landscape unclear\" → Sharpen differentiation - Iterate deck based on feedback (2-3 revisions) - Output: Pitch deck (v2, advisor-validated) - Week 3 Thursday-Friday (8h): Practice pitch - Record yourself pitching (15 min presentation) - Watch recording: Clarity? Confidence? Pace? - Practice with co-founder or advisor (simulate Q&A) - Refine talking points for each slide - Output: Pitch deck (final) + pitch talking points Weeks 2-3 Outputs: - Pitch deck (final, 13 slides) - Pitch talking points (1-2 page script) - Practice pitch (recorded, refined through iteration) Week 4: Financial Model & Data Room Day 1-3: Financial Model (16 hours) - Monday Morning (4h): Build 3-statement model - Income statement: Revenue (by segment if relevant), COGS, gross margin, operating expenses (sales, marketing, R&D, G&A), net income - Balance sheet: Assets (cash, AR), liabilities (AP, debt), equity - Cash flow statement: Operating cash flow, investing, financing - Model structure: Monthly for Year 1-2, quarterly for Year 3-5 - Output: 3-statement financial model (spreadsheet) - Monday Afternoon-Tuesday (8h): Revenue and expense projections - Revenue drivers: # sales reps × quota × win rate, expansion revenue, churn - Operating expenses: - Sales & Marketing: Rep salaries + acquisition spend, with cohort-level contribution and cash-payback sensitivity reviewed; no universal payback threshold applies - R&D: Engineering team (scale from X to Y engineers) - G&A: Finance, legal, HR (scale slowly) - Key assumptions: growth rate appropriate for the stage, SaaS-like gross margin, burn rate - Scenarios: Base case (realistic), optimistic (20 percent better), pessimistic (20 percent worse) - Output: Revenue and expense projections (3 scenarios) - Wednesday (4h): Unit economics and cohort analysis - CAC by channel: Direct sales, inside sales, self-serve - LTV by cohort: Month 1 cohort, Month 2, etc. (retention curves) - Payback period: Track by cohort (improving over time?) - Optional diagnostic such as growth rate plus profit margin: define the metric, period, cohort, and decision use; do not treat a “Rule of 40” score as a universal health test - Output: Unit economics dashboard + cohort analysis Day 4-5: Data Room Preparation (16 hours) - Thursday Morning (4h): Core documents - Financial statements: Last 12 months P&L, balance sheet, cash flow - Cap table: Current ownership, option pool, convertible notes/SAFEs - Customer list: All customers (anonymized if needed), MRR, cohort, retention - Employee list: All employees, roles, salaries, equity grants - Contracts: Customer contracts (top 10), vendor contracts, office lease - Output: Core financial and legal documents organized - Thursday Afternoon (4h): Product and traction materials - Product roadmap: Last 6 months shipped, next 12 months planned - KPI dashboard: MRR/ARR, growth rate, churn, CAC, LTV, NPS, active users - Customer testimonials: 5-10 quotes from happy customers - Case studies: 2-3 detailed customer success stories - Output: Product and traction documents - Friday (8h): Legal and compliance - Formation documents: Certificate of incorporation, bylaws - Board minutes: All board meetings documented - IP assignments: All employees/contractors assigned IP to company - Compliance: Any regulatory filings (depends on industry) - Material contracts: Partnership agreements, major vendor agreements - Set up virtual data room: Dropbox, Google Drive, or DocSend (organized folder structure) - Output: Data room ready (all documents uploaded, organized by category) Week 4 Outputs: - 3-statement financial model (5-year projection, 3 scenarios) - Unit economics dashboard + cohort analysis - Virtual data room (financial, legal, product, traction docs organized) Decision Gate #1 (End of Week 4): Fundraising Readiness Illustrative review prompts (not universal GO criteria): - Pitch deck finalized and advisor-validated (no major gaps or confusion) - Financial model complete with realistic projections (not hockey stick without justification) - Data room ready (all critical docs organized) - Investor target list prioritized (50 investors, Tier 1 intros secured or in progress) - Fundraising team aligned (founders + advisors clear on roles, timeline) Possible review or stop signals (define locally): - The evidence rule for the contemplated stage, investor, and operating plan is not met → revise the case, seek a different financing path, or pause; do not apply a universal ARR or growth cutoff - Cohort economics, cash timing, or downside sensitivity are not reconciled → fix the model or obtain qualified review before fundraising - The selected investor set lacks a credible access or decision path → expand or re-sequence outreach only if runway, capacity, and disclosure controls support it Contingency if the local evidence rule is not met: Delay, resize, stage, or replace the financing path according to the cash and solvency scenarios; use the time to improve the specific evidence or access gap rather than assuming a fixed calendar. Proceed only with accountable approval: Move to Phase 2 (Outreach & Initial Meetings). ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-phase-2-outreach-initial-meetings-weeks-5-8", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 2: Outreach & Initial Meetings (Weeks 5-8)", "headingId": "chapter-15-fundraising-and-finance-phase-2-outreach-initial-meetings-weeks-5-8", "url": "#chapter-15-fundraising-and-finance-phase-2-outreach-initial-meetings-weeks-5-8", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 5-6: Investor Outreach Week 5 Day 1-2: Warm Intro Outreach (8 hours) - Monday Morning (4h): Request intros to Tier 1 investors - For each selected Tier 1 investor (the number is a constructed example): - Identify connector (who can intro you?) - Email connector: \"I'm raising Series A [$XM to reach $YM ARR]. Would you intro me to [partner name] at [VC firm]? Here's a brief deck.\" - Attach teaser (3-slide deck): Company, traction, ask - Output: Intro requests sent within the approved capacity and disclosure boundary - Monday Afternoon (4h): Follow-up and scheduling - Connectors respond and make credible introductions - Once intro made: \"Thanks [connector]! [Investor], excited to connect. We're raising $XM Series A, [key traction metric]. I've attached our deck. Available [dates] for 30-min call?\" - Book meetings with investors who respond, subject to fit, runway, team capacity, and disclosure controls. - Output: Initial meetings scheduled with owners and next-step definitions Week 5 Day 3-5: Tier 2/3 Outreach (16 hours) - Tuesday-Thursday (12h): Outreach to Tier 2 investors - For selected Tier 2 investors: Use the same warm-intro process as Tier 1 where permitted - If no warm intro available: Cold email, treated as lower priority than network-led outreach - Target: A bounded number of Tier 2 meetings that the team can prepare for and follow up responsibly - Output: Additional meetings scheduled with actual dates and decision owners - Friday (4h): Calendar coordination - Schedule meetings over the next review window at a pace that leaves time to iterate the pitch and operate the business - Avoid clustering all meetings in one window when it would reduce evidence quality or create disclosure risk - Leave buffer for follow-up meetings - Output: Meeting calendar with actual capacity, follow-up owners, and stop conditions Week 6-7: Initial Investor Meetings Meeting Structure (each meeting: 45-60 min) - Pitch (15-20 min): Present deck (13 slides, conversational tone) - Q&A (20-30 min): Investor questions (be honest, don't oversell) - Next steps (5 min): \"What are your thoughts? What else would you need to see?\" Week 6 Day 1-5: Tier 1 Investor Meetings (constructed capacity example) - Monday-Friday: Conduct only the number of meetings that preserves preparation, evidence quality, and operating continuity - Meeting 1 (Northstar Ventures partner): Great traction, but worried about competitive landscape. \"How do you differentiate?\" - Meeting 2 (Harbor Ridge Capital partner): Excited about unit economics. \"Can you share customer cohort data?\" - Meeting 3 (Summit Arc Capital partner): Likes team. \"What's your path to $10M ARR?\" - After each meeting: Debrief notes (what went well? what objections? follow-up needed?) - Track investor interest level: High (wants partner meeting or diligence), Medium (needs more data), Low (pass) - Output: Tier 1 meetings completed, notes documented, and interest levels tracked against defined evidence Week 7 Day 1-5: Tier 2 Meetings + Follow-ups (constructed capacity example) - Monday-Wednesday (12h): Tier 2 investor meetings (similar format) - Conduct the number of Tier 2 meetings that the evidence and capacity plan supports - Track interest levels (same framework) - Output: Tier 2 meetings completed with comparable notes and next-step decisions - Thursday-Friday (8h): Follow-up with high-interest investors - Investors who expressed \"High\" interest: Send follow-up materials - Northstar Ventures partner requested cohort data → Send detailed retention curves - Harbor Ridge Capital partner wants customer references → Provide contact info for 3 happy customers - Schedule partner meetings or deep dives only where the investor has supplied a credible next step and the disclosure boundary permits it - Output: Follow-up materials sent and next steps scheduled with explicit scope and owners Weeks 5-7 Outputs: - Initial investor meetings completed within the approved capacity - Investor interest tracker with definitions, evidence, uncertainty, and decision authority for each investor - Partner meetings or deep dives scheduled only where the investor has supplied a credible next step - Pitch iteration based on feedback (refined deck if needed) Week 8: Partner Meetings & Pitch Refinement Day 1-3: Partner Meetings (16 hours) - Monday-Wednesday (16h): Conduct 3-5 partner meetings - Partner meetings: Full partnership presents deck, Q&A (60-90 min sessions) - More rigorous Q&A: Financial model scrutiny, competitive dynamics, team capability - Expect tough questions: - \"Why will you win in this crowded market?\" - \"What if growth slows? How do you get back on track?\" - \"What's your biggest risk?\" - Post-meeting: Gauge interest (Do they want to proceed to diligence?) - Output: 3-5 partner meetings completed, interest levels updated Day 4-5: Pitch and Strategy Iteration (8 hours) - Thursday Morning (4h): Synthesize feedback - Review all investor feedback from Weeks 6-8 - Common themes: - Competitive positioning unclear → Sharpen differentiation in deck - Market size questioned → Add bottom-up market calc - Team capability concern → Highlight recent key hire or advisor - Revise pitch deck if needed (minor adjustments, not full rewrite) - Output: Feedback synthesis + deck revisions (if needed) - Thursday Afternoon-Friday (4h): Fundraising strategy adjustment - Update investor pipeline by actual next step: inquiry, meeting, diligence request, term-sheet discussion, or approved commitment. - If the evidence or access rule is not met: Expand, re-sequence, resize, pause, or replace the path according to runway and capacity. - If credible next steps exist: Focus on diligence, terms, approvals, and alternatives without treating interest as a commitment. - Output: Updated investor pipeline + strategy for Weeks 9-12 Week 8 Outputs: - 3-5 partner meetings completed - Pitch deck refined based on feedback (if needed) - Investor pipeline updated with evidence-based status definitions and next actions - Strategy for Weeks 9-12 (focus on hot leads vs expand outreach) Decision Gate #2 (End of Week 8): Investor Interest Validation Illustrative review prompts (not universal GO criteria): - At least one credible, authorized next step exists with an investor whose mandate, capacity, conflicts, and terms remain plausible; a count of interested investors is not a commitment - Pitch is resonating (investors understand value prop, traction compelling) - No major blockers identified (competitive concerns addressable, team concerns mitigated) Possible review or stop signals (define locally): - No credible next step after a sufficient, responsibly sampled set of conversations → diagnose evidence, fit, access, and process issues; do not infer a universal meeting threshold - Consistent feedback that evidence is insufficient → identify the specific evidence rule, revise the operating plan, or pause - Price, dilution, rights, or governance expectations are misaligned → model the full package and alternatives; do not use a universal percentage gap Contingency if the local evidence rule is not met: - If access or fit is weak: expand or replace the investor set only after checking runway, confidentiality, and team capacity - If evidence is insufficient: pause, stage, or change the financing path while improving the specific evidence gap - If terms are misaligned: compare the complete package with no-raise, debt, revenue, staged-spending, and other feasible paths Proceed only with accountable approval: Move to Phase 3 (Due Diligence & Term Sheet). ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-phase-3-due-diligence-term-sheet-weeks-9-12", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 3: Due Diligence & Term Sheet (Weeks 9-12)", "headingId": "chapter-15-fundraising-and-finance-phase-3-due-diligence-term-sheet-weeks-9-12", "url": "#chapter-15-fundraising-and-finance-phase-3-due-diligence-term-sheet-weeks-9-12", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 9-10: Investor Due Diligence Week 9 Day 1-2: Due Diligence Kickoff (8 hours) - Monday Morning (4h): Organize diligence process - Hot lead investors (2-4) request due diligence access - Provide data room access (prepared in Week 4) - Create diligence tracker: - Questions from investors (track in spreadsheet) - Documents requested (track fulfillment) - Meetings scheduled (customer calls, team interviews) - Assign point person: Founder or CFO (if you have one) coordinates diligence responses - Output: Diligence tracker + data room access granted - Monday Afternoon-Tuesday (4h): Respond to initial requests - Typical requests: - Detailed financial model with assumptions - Customer retention cohort data - Product roadmap + technical architecture docs - Employee equity grants and option pool - Top 10 customer contracts - Respond on an agreed, controlled cadence that preserves accuracy, privilege, privacy, and operating continuity - Output: Initial diligence requests fulfilled Week 9 Day 3-5: Customer Reference Calls (16 hours) - Wednesday-Friday (16h): Coordinate and brief customers - Investors request calls with a selected, permissioned, representative set of customers - Select references: Mix of enterprise and SMB, different use cases, all happy customers - Brief customers: \"Investor [name] from [firm] will call you. They'll ask about your experience, results, our team. Be honest!\" - Coordinate calls: Intro investor to customer via email, let them schedule directly - Debrief with investor post-call: \"What did [customer] say? Any concerns?\" - Typical investor questions to customers: - \"Why did you buy?\" - \"What results have you seen?\" - \"What almost prevented you from buying?\" - \"How's the team? Support?\" - \"Would you recommend to others?\" - Output: 3-5 customer reference calls completed Week 10 Day 1-3: Financial and Legal Diligence (16 hours) - Monday-Wednesday (16h): Detailed financial review - Investors scrutinize financial model: - Revenue assumptions: \"How did you calculate $10M ARR by Year 3?\" (show math: # reps × quota) - Expense assumptions: \"Why does S&M expense drop as % of revenue?\" (improving CAC efficiency) - Cohort economics: \"Show me Month 1 cohort LTV curve\" (retention over 24+ months) - Respond to all questions with data (not hand-waving) - Legal diligence: - Cap table audit (confirm all equity grants are documented) - IP assignments (all employees signed IP agreements?) - Material contracts (any unusual terms in customer or vendor contracts?) - Output: Financial model scrutinized and validated, legal docs reviewed Week 10 Day 4-5: Competitive and Market Diligence (8 hours) - Thursday-Friday (8h): Address competitive questions - Investors talk to industry experts, competitors, other portfolio companies - Common questions: - \"We spoke to [competitor]. They say you're expensive and don't have feature X. Your response?\" - \"Industry expert said this market is commoditizing. How do you maintain pricing power?\" - Prepare responses: Acknowledge reality, provide counter-evidence - \"Yes, Competitor A is cheaper, but we focus on enterprise customers who value integration and support (attach case example showing $X ROI)\" - \"Market is competitive, but we're differentiated on [specific capability]. Our NPS is 9/10 vs industry avg 7/10.\" - Output: Competitive positioning validated, objections addressed Weeks 9-10 Outputs: - Investor diligence completed (financial, legal, customer, competitive) - All diligence questions answered with supporting data - Positive customer reference feedback (all references confirmed value) - Investor conviction increased (diligence validates traction and team) Week 11: Term Sheet Negotiation Day 1-2: Receive and Evaluate Term Sheets (8 hours) - Monday Morning (4h): Term sheets arrive - Receive any term sheets or written indications that actually arrive; multiple offers are not required and must not be manufactured - Example term sheet: - Lead investor: Northstar Ventures - Investment: $5M - Pre-money valuation: $20M (Post-money: $25M) - Dilution: 20 percent - Liquidation preference: 1x non-participating - Board seat: 1 investor seat (total board: 2 founders + 1 investor + 1 independent) - Option pool: 15 percent post-financing - Pro-rata rights: Investor can participate in future rounds - Review with counsel: Which provisions are supported by current comparable documents, jurisdiction, instrument, and the actual transaction? Which are unusual or unresolved? - Output: Term sheets received and reviewed - Monday Afternoon-Tuesday (4h): Compare term sheets - If multiple term sheets, compare: - Valuation (higher is better, but not only factor) - Dilution (lower is better) - Liquidation preference, seniority, participation/cap, conversion, and dividends modeled from the proposed documents - Board composition, appointment/removal, fiduciary duties, observers, and protective rights analyzed separately from ownership - Investor quality (brand, network, value-add beyond capital) - Create comparison matrix - Output: Term sheet comparison (valuation, terms, investor value-add) Day 3-5: Negotiate Key Terms (16 hours) - Wednesday Morning (4h): Valuation negotiation - If term sheet below target valuation: \"We were targeting $25M post-money. Can you move to $23M?\" - Justification: Point to traction, competitive term sheets, market comps - If investor firm: \"We're firm at $20M post. But we can offer faster close or favorable terms elsewhere.\" - Decide: Accept $20M or push for $22-23M (risk losing deal if you push too hard) - Output: Valuation agreed (or identify gap to close) - Wednesday Afternoon-Thursday (8h): Negotiate terms - Liquidation preference: - Investor proposes: 1x participating (they get $5M back + their ownership % of remaining proceeds) - You counter: 1x non-participating; in this constructed simplified model, the holder compares the defined preference with the as-converted distribution. Actual terms can alter that result and require counsel. [BB-C15-S08] [BB-C15-S09] - Outcome: Agree to 1x non-participating - Board composition: - Investor proposes: A board and consent structure that changes control or veto rights (constructed example) - You counter: A structure whose appointment, removal, fiduciary, observer, and reserved-matter effects fit the approved governance boundary - Outcome: Record the actual negotiated structure and model its control and deadlock consequences - Option pool: - Investor proposes: 20 percent post-financing option pool (dilutes founders more) - You counter: 15 percent pool (sufficient for next 10-15 hires) - Outcome: Agree to 15 percent pool - Pro-rata rights: Model the actual allocation, notice, thresholds, waiver, timing, and future-financing consequences; do not label them standard - Output: Key terms negotiated (valuation, liquidation pref, board, option pool) - Friday (4h): Sign or decline the term sheet only after counsel and authorized decision-makers identify which provisions bind - Lawyer reviews final term sheet (ensure all negotiated points are reflected) - Sign the term sheet only after recording its binding provisions, conditions, exclusivity, confidentiality, expenses, and termination rights - Announce to team: \"We have a term sheet from Northstar Ventures! $5M at $25M post-money. Next: legal docs and close.\" - Output: Non-binding term sheet signed Week 11 Outputs: - Term sheet received (1-3 investors) - Key terms negotiated (valuation, dilution, board, liquidation pref, option pool) - Term-sheet decision recorded, including binding provisions and remaining conditions Week 12: Final Diligence & Legal Documentation Day 1-3: Final Due Diligence (16 hours) - Monday-Wednesday (16h): Address remaining diligence items - Investor may have final questions: - \"We noticed customer churn spiked in Month X. What happened?\" (one-time issue with onboarding; fixed) - \"Your largest customer is 25 percent of ARR. That's risky.\" (True; we're diversifying, have 5 new enterprise customers in pipeline) - Resolve any blockers quickly (delays can kill deals) - Final customer calls if needed (investor talks to 1-2 more references) - Output: All final diligence items resolved Day 4-5: Legal Documentation (8 hours) - Thursday-Friday (8h): Work with lawyers to draft agreements - Key legal documents: - Stock Purchase Agreement (SPA): Terms of investment - Amended and Restated Certificate of Incorporation: Updates company charter with new share class - Investor Rights Agreement: Board seats, information rights, pro-rata rights - Right of First Refusal and Co-Sale Agreement: Investor rights if founders sell shares - Voting Agreement: Board composition, voting rights - Lawyers draft, both sides review, negotiate minor points - Timeline: Follow the actual document set, counsel availability, jurisdiction, approvals, and closing conditions; do not treat 2-4 weeks as a standard legal duration - Output: Legal docs drafted and under review Week 12 Outputs: - Final diligence completed and resolved - Legal documentation in progress (SPA, Certificate of Incorporation, Investor Rights Agreement) Decision Gate #3 (End of Week 12): Term Sheet to Legal Docs Illustrative review prompts (not universal GO criteria): - Term sheet signed with lead investor (valuation and key terms agreed) - All due diligence items resolved (no major blockers) - Legal documentation in progress (lawyers engaged, drafting agreements) Possible review or stop signals (define locally): - Diligence uncovers major issue (fraud, IP theft, undisclosed liabilities) → Deal may fall apart - Investor gets cold feet (market downturn, internal fund issues) → May need to re-engage other investors - Legal terms deadlock (can't agree on key provisions) → Escalate to principals, consider walking away Contingency if the local evidence rule is not met: - If diligence blocker: Address immediately (bring in lawyers, accountants, fix issue) - If investor backs out: Re-engage permitted alternative counterparties only after updating the cash, disclosure, and decision record; timing depends on the actual process - If legal deadlock: Escalate to founders and senior partner (resolve or walk away) Proceed only with accountable approval: Move to Phase 4 (Closing). ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-phase-4-closing-post-close-weeks-13-16", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Phase 4: Closing & Post-Close (Weeks 13-16)", "headingId": "chapter-15-fundraising-and-finance-phase-4-closing-post-close-weeks-13-16", "url": "#chapter-15-fundraising-and-finance-phase-4-closing-post-close-weeks-13-16", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 13-14: Legal Finalization Week 13 Day 1-5: Legal Negotiation (20+ hours) - Monday-Friday (4h per day): Negotiate legal documents - Lawyers exchange redlines (tracked changes to agreements) - Common negotiation points: - Information rights: Investor wants monthly financials; you offer quarterly (compromise: monthly for first year, quarterly after) - Board observer rights: Investor wants observer seat; you agree if non-voting - Drag-along rights: Investor wants right to force sale if majority agrees; you negotiate threshold (75 percent shareholder approval, not 51 percent) - Founder involvement: Review key provisions, delegate details to lawyers - Output: Legal docs negotiated (nearing final form) Week 14 Day 1-3: Final Legal Review (12 hours) - Monday-Wednesday (12h): Finalize all agreements - All parties review final documents - Resolve last-minute issues (typos, incorrect numbers, ambiguous language) - Founder reviews personally: Check valuation, dilution %, board seats, liquidation preference (ensure all match term sheet) - Output: Final legal documents ready for signature Week 14 Day 4-5: Board Approval (4 hours) - Thursday (4h): Board meeting to approve financing - Convene board meeting (founders + existing investors if any) - Present term sheet and legal docs - Board considers and records approval under the actual governing documents, fiduciary duties, conflicts, and applicable law; unanimity is not assumed - Document in board minutes - Output: Board approval obtained, minutes documented Weeks 13-14 Outputs: - Legal documents finalized (SPA, Certificate of Incorporation, Investor Rights Agreement, etc.) - All parties ready to sign - Board approval obtained Week 15: Signing & Wire Transfer Day 1-2: Signature Process (8 hours) - Monday-Tuesday (8h): Coordinate signatures - All parties sign legal documents (founders, investor, company) - Use DocuSign or similar for electronic signatures - Ensure all documents signed in correct order (some are conditional on others) - Make any required charter or formation filing in the applicable jurisdiction after counsel confirms the document, authority, and filing requirement - Output: All legal documents signed and filed Day 3-4: Wire Transfer (4 hours) - Wednesday-Thursday (4h): Receive funds - Investor wires $5M to company bank account - Confirm receipt with bank - Update cap table: Issue new shares to investor, update founder ownership % - Notify team: \"Funding closed! We raised $5M from Northstar Ventures.\" - Output: Funds received, cap table updated Day 5: Celebrate & Plan (4 hours) - Friday (4h): Internal and external announcements - Internal: All-hands meeting to announce raise, explain use of funds, celebrate team effort - External: Press release or blog post (if you want publicity) - Investor announcement: Coordinate with investor PR team (some VCs issue press releases) - Plan next 30 days: Hiring plan (sales reps, engineers), budget allocation, key milestones - Output: Announcements made, post-close plan ready Week 15 Outputs: - All documents signed and filed - $5M (or target raise amount) received in bank account - Cap table updated (investor shares issued, founder dilution reflected) - Internal and external announcements made Week 16: Post-Close Transition Day 1-2: Investor Onboarding (8 hours) - Monday-Tuesday (8h): Onboard new investor - Board seat logistics: Add investor to board, schedule first board meeting (within 30 days) - Reporting cadence: Agree on monthly investor updates (metrics, milestones, asks) - Intro to team: Investor meets VPs (Sales, Marketing, Engineering) - Strategic planning: Investor provides input on hiring, GTM, product roadmap - Output: Investor onboarded, first board meeting scheduled Day 3-5: Execution Planning (16 hours) - Wednesday-Friday (16h): Deploy capital toward milestones - Hiring plan: Use the approved workforce, compensation, capacity, and cash plan; role count, compensation, equity, and timing are company-specific and require current quotes and employment review - Marketing spend: Allocate only against an approved test plan, attribution method, cash downside, and applicable disclosure/consumer rules - Product roadmap: Prioritize features that support sales (enterprise features, integrations) - Milestones for the next review period: Define evidence-backed operating and financing triggers with owners, observation windows, downside cases, and no-next-round consequences; no fixed ARR or Series B gate is assumed - Output: Hiring plan, budget allocation, milestone roadmap Week 16 Outputs: - Investor onboarded (board seat, reporting cadence established) - Capital deployment plan (hiring, marketing, product priorities) - Milestones for next 18 months (path to Series B) Decision Gate #4 (End of Week 16): Post-Close Readiness Illustrative review prompts (not universal GO criteria): - Funds received and cap table updated - Investor onboarded (first board meeting scheduled, reporting established) - Capital deployment plan ready (hiring, budget, milestones documented) Success indicators (next review period): - First hires made (sales reps, marketing lead, engineers recruited) - Marketing campaigns launched (ads, content, events started) - Operating evidence is improving against the approved definitions, cash plan, and decision triggers; no universal growth rate is assumed ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-resource-requirements", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Resource Requirements", "headingId": "chapter-15-fundraising-and-finance-resource-requirements", "url": "#chapter-15-fundraising-and-finance-resource-requirements", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Human Resources: Founding Team (Weeks 1-16): - Founder/CEO: 40-50h/week (investor meetings, pitch, negotiation, team coordination) - Co-founder/CTO or VP Product: 10-15h/week (investor meetings, product questions, due diligence support) - CFO or Finance Lead (if exists): 20-30h/week (financial model, due diligence, legal docs) - If no CFO: Founder takes this on (50-60h/week total) External Resources: - Lawyer: Obtain a current written scope and jurisdiction-specific estimate from qualified startup/venture counsel. - Accounting and tax: Obtain a current written scope and estimate for diligence, financial reporting, tax, and any assurance work actually required. - Advisors/Mentors: 5-10h donated time (pitch feedback, intro facilitation, term sheet review) Financial Resources: The following amounts are constructed worksheet assumptions, not current quotes or market benchmarks. Replace every amount with dated provider quotes, fully loaded internal costs, applicable taxes and filing requirements, payment timing, and a contingency justified by the actual transaction. Weeks 1-4 (Preparation): $5,000-$15,000 - Lawyer consultation: $3K-5K (review existing docs, prep for fundraise) - Accountant: $2K-5K (financial statement cleanup) - Tools: DocSend for deck tracking ($50/mo), LinkedIn Sales Navigator ($100/mo) - Misc: Travel to in-person investor meetings ($1K-5K depending on geography) Weeks 5-12 (Outreach & Diligence): $10,000-$25,000 - Lawyer: $5K-10K (term sheet review, initial legal work) - Travel: $3K-10K (flights, hotels for investor meetings if out of town) - Misc: Meals with investors, team support ($2K-5K) Weeks 13-16 (Closing): $15,000-$30,000 - Lawyer: $12K-30K (legal doc drafting, negotiation, closing costs) - Accountant: $2K-5K (final audit, cap table management) - Misc: Filing fees, administrative costs ($1K-2K) Total Fundraising Cost (16 Weeks): $30,000-$70,000 - Constructed Scenario A: $30K-40K (limited travel and a narrower adviser scope) - Constructed Scenario B: $40K-55K (broader adviser scope and moderate travel) - Constructed Scenario C: $55K-70K (more extensive adviser, travel, and communications assumptions) Payment-timing note: Legal and other adviser fees are governed by engagement letters and transaction documents. Do not assume they are payable only at closing or from financing proceeds; model deposits, retainers, termination, no-close, reimbursement, tax, and success-fee terms with qualified advisers. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-red-flags-warning-signals", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Red Flags & Warning Signals", "headingId": "chapter-15-fundraising-and-finance-red-flags-warning-signals", "url": "#chapter-15-fundraising-and-finance-red-flags-warning-signals", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Week 1-4 red flags (illustrative): - Cannot build a permitted, fit-checked investor set → Diagnose access, mandate, conflicts, confidentiality, and runway; do not impose a calendar before choosing the response. - Reviewers identify material deck gaps → Identify the specific evidence or communication gap and decide whether to revise, resize, pause, or continue. - Financial model does not support the narrative → Reconcile definitions, sources, assumptions, cash, and downside with the finance owner. Week 5-8 red flags (illustrative): - Low or uneven response to permitted introductions → Review access, fit, deliverability, permissions, and message quality; do not infer a network or traction verdict from one rate - Investors pass after first meeting → Ask willing investors for observable evidence, fit, process, or timing feedback and compare alternatives. - Consistent feedback: \"Too early\" → Identify the actual evidence rule or mandate issue; consider revising, staging, or changing the financing path. Week 9-12 red flags (illustrative): - Diligence uncovers financial irregularities → Accounting issues, revenue recognition problems; need to fix immediately with accountant/lawyer - Customer references are lukewarm → Product issues or customer success problems; investors will notice - No credible next step after a sufficient conversation sample → Reassess evidence, valuation, terms, fit, process, and alternatives; do not diagnose a single root cause. Week 13-16 red flags (illustrative): - Legal negotiation stalls → Investor or founder digging in on unfavorable terms; may need to walk away or compromise - Investor backs out post-term sheet → Market conditions changed or investor found red flag; re-engage backup investors immediately - Closing exceeds the locally defined review window → Identify the document, approval, condition, or issue causing delay and escalate through the accountable owners. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-contingency-triggers", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Contingency Triggers", "headingId": "chapter-15-fundraising-and-finance-contingency-triggers", "url": "#chapter-15-fundraising-and-finance-contingency-triggers", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Trigger 1: Insufficient Investor Interest (local review point) - Condition: No credible, authorized next step after a sufficient and responsibly sampled process - Action: Diagnose root cause (pitch? traction? valuation?). Options: 1. Expand or replace outreach only if runway, capacity, and disclosure controls support it 2. Pause, resize, or change the financing path while improving the specific evidence gap 3. Reconcile price, rights, governance, and alternatives if investors say the package is misaligned - Timeline impact: Record the actual cash and operating impact; no calendar extension is assumed. Trigger 2: Diligence Blocker - Condition: Investor finds major issue (financial, legal, product, customer) - Action: Address immediately: - Financial issue: Engage accountant to restate financials or explain discrepancy - Legal issue: Engage lawyer to resolve IP, contract, or compliance problem - Product issue: Define a supported remediation, workaround, disclosure, or stop decision with the product owner - Customer issue: Interview churned customer, address concern, provide mitigation plan - Timeline impact: Record the actual remediation, approval, and runway consequences; the deal may continue, change, pause, or fall apart. Trigger 3: Term Sheet Misalignment - Condition: Price, dilution, proceeds, control, priority, governance, disclosure, or other terms fall outside the approved boundary - Action: Options: 1. Negotiate (push back on valuation or terms, cite competitive dynamics) 2. Walk away (if terms are unacceptable, engage other investors) 3. Accept (if only option and terms are acceptable, just lower valuation) - Timeline impact: Record the actual negotiation, approval, and fallback-path consequences. Trigger 4: Investor Backs Out After a Term Sheet - Condition: Investor withdraws or changes its proposal before closing, subject to the actual binding provisions and conditions - Action: Immediately re-engage backup investors: - Contact Tier 2 investors who were warm: \"We had a term sheet that fell through due to [reason]. Still interested?\" - Be transparent (don't hide the fact; explain why deal fell apart) - Move quickly (momentum is critical; delays signal desperation) - Timeline impact: Record the actual runway, disclosure, and fallback-path consequences. Trigger 5: Legal Deadlock - Condition: Cannot agree on key legal terms (drag-along, liquidation pref, board composition) - Action: Escalate to principals (founders + senior VC partner): - Identify deal-breaker vs negotiable points - Compromise if possible (e.g., accept investor observer seat instead of full board seat) - Walk away if terms are unacceptable (better no deal than bad deal) - Timeline impact: Record the actual counsel, approval, and alternative-financing consequences. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-timeline-variance", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Timeline Variance", "headingId": "chapter-15-fundraising-and-finance-timeline-variance", "url": "#chapter-15-fundraising-and-finance-timeline-variance", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Compressed mode (constructed example): - Use when: Evidence, counterparties, approvals, and capacity support a shorter process. - Compress: Combine phases only after checking diligence quality, disclosure, legal review, and runway. - Risk: Less time to iterate pitch, may rush due diligence - Outcome: An earlier close is possible but not guaranteed. Constructed operating-manual mode: - Use when: The sequence, evidence, capacity, and review owners fit the venture. - Timeline: As described in this operating manual, subject to actual conditions. - Balance: Adequate time for prep, iteration, diligence, negotiation - Outcome: Closing is not guaranteed. Extended mode (constructed example): - Use when: Evidence, access, counterparties, approvals, or diligence require more time. - Expand: Add only the work needed to resolve the actual evidence or process constraint. - Risk: Fundraise fatigue, market conditions may change - Outcome: A longer process may improve review or may consume runway; model the actual consequence. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-measurement-dashboard", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Measurement Dashboard", "headingId": "chapter-15-fundraising-and-finance-measurement-dashboard", "url": "#chapter-15-fundraising-and-finance-measurement-dashboard", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Tracker (illustrative phases): Table 15.29: Author-created or source-bounded decision aid (Phase | Key Metric | Local rule | Actual | Status ). Values and comparisons are constructed or source-bounded inputs; use cited evidence and local definitions before relying on them. | Phase | Key Metric | Local rule | Actual | Status| | :--- | :--- | :--- | :--- | :---| | Preparation | Pitch deck complete | Approved evidence, audience, and disclosure boundary | | | | Preparation | Financial model complete | Linked definitions, assumptions, cash, and review owner | | | | Preparation | Data room ready | Controlled sources, permissions, privilege, and escalation | | | | Outreach | Investor universe | Fit-checked, source-dated, and capacity-bounded | | | | Outreach | Introductions | Permitted, truthful, and tracked with actual denominators | | | | Meetings | Conversations | Comparable notes, evidence gaps, and next-step owner | | | | Interest review | Investor signals | Distinguish inquiry, diligence, term sheet, and commitment | | | | Diligence | Requests and references | Permissioned, source-indexed, representative, and unresolved issues owned | | | | Terms | Term sheet | Binding provisions, full economics, rights, approvals, and alternatives modeled | | | | Closing | Operative documents and funds | Conditions satisfied, funds verified, records updated | | | | Post-close | Governance and operating plan | Owners, milestones, cash controls, and downside triggers documented | | | End-of-process milestone indicators: Fundraise outcome: - Amount, price, dilution, rights, governance, and runway match the approved operating and downside cases—or the decision is revised, paused, or stopped - Lead investor and other counterparties have verified mandate, capacity, conflicts, authority, and value-add claims. - The complete package is acceptable to the authorized board or decision-maker after counsel and finance review. Investor Quality: - Brand: Reputation is recorded only as context; evaluate actual mandate, capacity, conduct, conflicts, and value-add evidence. - Value-add: Investor provides intros, hiring support, strategic guidance (not just capital) - Board: Investor participation, duties, information, conflicts, and operating boundary are documented in the actual governance arrangement. Terms: - Liquidation preference: model the actual proposed seniority, multiple, participation/cap, conversion, and dividends; do not label a package standard or friendly without context - Board composition: Appointment, removal, voting, consent, observer, fiduciary, and deadlock effects are modeled from the actual documents. - Option pool: Sized from the approved hiring and compensation plan and modeled pre-/post-money; no universal percentage or hiring count applies - No unresolved material terms: Anti-dilution, drag-along, preferences, information, transfer, and other rights are documented and reviewed. ---" }, { "id": "chapter-15-fundraising-and-finance::chapter-15-fundraising-and-finance-success-vs-struggling-how-to-know", "kind": "chapter", "itemSlug": "chapter-15-fundraising-and-finance", "itemTitle": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "heading": "Success vs Struggling: How to Know", "headingId": "chapter-15-fundraising-and-finance-success-vs-struggling-how-to-know", "url": "#chapter-15-fundraising-and-finance-success-vs-struggling-how-to-know", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "You're succeeding when the local decision rule is met: - Capital, price, dilution, rights, governance, and runway support the approved operating and downside scenarios - The counterparties' authority, capacity, conflicts, conduct, and value-add claims are verified. - Diligence, legal, tax, accounting, disclosure, and stakeholder issues are surfaced and owned. - Closing records, funds, cap table, governance, and post-close controls reconcile. Next steps (success): Execute the approved capital deployment plan, monitor evidence and cash, and revisit financing only when the actual operating and downside cases justify it. You're struggling when: - No credible next step exists after a sufficient, responsibly sampled process. - Price, dilution, rights, governance, or runway fall outside the approved boundary - Material diligence, accounting, legal, disclosure, customer, or stakeholder issues remain unresolved. - The process consumes runway or team capacity without a credible alternative. - The team lacks a documented continue/revise/pause/stop decision and accountable owners. Next steps (Struggling): - Diagnose root cause: - Evidence: If investors consistently say \"too early,\" identify the actual evidence or mandate gap and set a locally owned test before retrying. - Valuation: If investors offered much lower valuations, reassess your expectations or improve metrics to justify higher valuation - Team: If investors question capability, compare hiring, advising, partnering, role redesign, governance, and operating changes; do not prescribe a title. - Market: If investors worried about competitive landscape or market size, sharpen differentiation or consider pivot - Alternative options: - Bridge financing: Consider a bridge only if actual documents, cash scenarios, conversion, governance, and downside terms support it - Revenue financing: Use revenue-based financing or venture debt if revenue is strong (less dilutive than equity) - Slow growth: Extend runway through cost cuts, grow more slowly toward profitability (avoid Series A entirely) - Retry timing: Resume only when the specific evidence, cash, access, and approval conditions for retrying are met; no calendar interval is universal. --- ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "AI Strategy and Data-Driven Decisions", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions", "url": "#chapter-16-ai-strategy-and-data-driven-decisions", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-executive-summary", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Executive Summary", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-executive-summary", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-executive-summary", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "This chapter provides current public-source-backed frameworks for developing and implementing AI strategies as of July 2026, from opportunity assessment through governance and change management. Key Frameworks: 1. AI Opportunity Assessment Matrix 2. Build vs. Buy vs. Partner Decision Tree 3. AI Maturity Model 4. Use Case Prioritization Framework 5. ROI Calculation for AI Projects 6. Ethical AI Framework 7. Data Readiness Assessment 8. MLOps Pipeline and Change-Control Framework 9. Agentic AI Operating and Control Model 10. AI Governance Structure 11. Change Management for AI Adoption" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-decision-outcomes-and-authority-boundary", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Decision outcomes and authority boundary", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-decision-outcomes-and-authority-boundary", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-decision-outcomes-and-authority-boundary", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "After this chapter, a manager should be able to compare an AI-enabled option with process, policy, staffing, rules, and conventional-software alternatives; build a range-based business case; choose build, buy, partner, or no-AI sourcing; define versioned evaluation and change control; allocate human decision rights; and make a go, redesign, stage, or stop recommendation. Record the exact framework, profile, version, and date used. NIST AI RMF 1.0 is voluntary and under revision as of July 2026; its functions and the NIST Generative AI Profile support risk management rather than certification or legal compliance. ISO/IEC 42001 is a management-system standard. The EU AI Act is law with role-, system-, use-, jurisdiction-, and date-specific applicability. None substitutes for current legal, security, safety, privacy, accessibility, employment, or sector review. [BB-C16-S01] [BB-C16-S04] [BB-C16-S05] [BB-C16-S06] Constructed-example boundary: Unless a row has a directly supporting source, all scores, costs, durations, thresholds, committee designs, maturity levels, model choices, and rollout targets in this chapter are teaching examples to tailor and validate—not benchmarks, legal safe harbors, or recommended defaults. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The opportunity assessment matrix compares potential value with feasibility so a manager can make assumptions visible before committing resources. It is a screening aid, not a forecast or a substitute for process, policy, staffing, rules, conventional software, or other non-AI options." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Start with the decision, baseline process, accountable owner, affected stakeholders, and risk boundary. Score or describe value and feasibility using a documented local scale, record confidence and evidence, test the most consequential assumptions, and choose invest, learn, redesign, or stop with a review date. Provenance boundary: The value-feasibility matrix and quadrant labels below are an author-created screening synthesis. They expose assumptions for review; they do not predict value, feasibility, delivery time, or success, and they do not replace non-AI alternatives, risk, legal, security, workforce, accessibility, or lifecycle-cost review. Two Dimensions: - Value Potential: Impact on revenue/costs/customer experience - Feasibility: Data availability, technical complexity, organizational readiness 2×2 Matrix: Table 16.1: Author-created screening aid (Value potential | Feasibility | Suggested next move). Quadrant labels and examples are constructed teaching inputs; use a documented local scale and test the non-AI baseline before acting on them. | | Low Feasibility | High Feasibility | |---|---|---| | High Value | Strategic Bets (Invest, long-term) | Quick Wins (Do now, prove value) | | Low Value | Avoid (Don't waste resources) | Experiments (Learn, build capability) | Evaluation Criteria: Value Potential: - Revenue impact (new products, pricing optimization) - Cost reduction (automation, efficiency) - Customer experience (personalization, speed) - Risk mitigation (fraud detection, predictive maintenance) - Competitive advantage (first-mover, differentiation) Feasibility: - Data availability & quality - Technical complexity & talent - Integration with existing systems - Time to value (define an evidence-based local range; six months is only an illustrative cutoff) - Organizational readiness (culture, change management) Constructed Example Use Cases: Table 16.2: Constructed comparison aid (Use case | Value | Feasibility | Quadrant). The ratings are illustrative placeholders, not benchmark scores or a recommendation to deploy any named use case. | Use Case | Value | Feasibility | Quadrant | |----------|-------|-------------|----------| | Personalized product recommendations | High | High | Quick Win | | Generative AI customer support | High | High | Quick Win | | Supply chain optimization (full) | High | Low | Strategic Bet | | Automated email subject lines | Low | High | Experiment | | AGI-powered strategy | Low | Low | Avoid |" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Make the non-AI baseline and the decision owner explicit before scoring. - Use the matrix to sequence evidence collection, not to create an automatic investment priority. - Require risk, legal, security, workforce, accessibility, and lifecycle-cost review before a high-value idea moves forward." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Value and feasibility are judgment categories; different raters can produce different quadrants. - A two-dimensional screen can hide dependencies, distributional effects, adoption friction, and tail risk. - “Quick win” and “avoid” are local labels, not universal recommendations." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use the sourcing decision in Framework 2, the capability diagnostic in Framework 3, and the business-case worksheet in Framework 5 to test the assumptions exposed here. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview-2", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview-2", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview-2", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The sourcing decision tree asks whether an AI option improves the bounded decision, whether its authority and risk boundary are acceptable, and whether the organization can operate it over its lifecycle. The output can be build, buy, partner, stage, redesign, or stop." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-2", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-2", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-2", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Document the non-AI baseline, use-case risk, data and intellectual-property authority, strategic differentiation, lifecycle economics, portability, integration, security, evaluation, support, and exit conditions. Make the choice conditional on evidence and assign an owner for re-assessment when the product, vendor, law, workflow, or risk changes. Figure 16.1. AI sourcing decision record. This original synthesis combines value-realization, management-system, and risk-management questions. The cited sources support the need to test value, governance, and risk; they do not prescribe a sourcing outcome. [BB-C16-S01] [BB-C16-S06] [BB-C16-S08] Text equivalent: Start with the business decision and compare AI with non-AI alternatives. If AI remains plausible, assess use-case risk and data/IP authority, strategic differentiation, lifecycle economics, internal operating capability, vendor concentration and portability, integration, security, and exit. Choose build, buy, partner, stage, or stop, then revisit the choice as evidence changes. Build When: - Core differentiator (proprietary algorithms on proprietary data) - Unique requirements competitors don't have - Data moat exists (competitors can't replicate) - Illustrative rationale: the organization needs workflow control or proprietary behavior that an available option cannot provide at acceptable lifecycle risk and cost. Buy When: - Commodity capability (every company needs it) - Mature market with good vendors - Non-differentiating (operations, support) - Illustrative rationale: a vendor can meet the approved use, assurance, integration, portability, and support requirements without giving up material strategic control. Partner When: - Need expertise + your data - Complex implementation requiring both parties - Want to share risk/cost - Possible pattern: a specialist partner contributes capability while the organization retains decision rights, evidence, and exit control." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-2", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-2", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-2", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Treat sourcing as a lifecycle-control decision, not a referendum on whether a model is strategically fashionable. - Preserve portability, evidence access, incident cooperation, and a credible exit path in the operating and commercial design. - Do not outsource accountability for decisions that remain the organization's responsibility." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-2", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-2", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-2", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The tree simplifies procurement, architecture, operating-model, and legal dependencies that may require separate review. - “Strategic differentiation” is a hypothesis that needs evidence; proprietary technology alone does not create an advantage. - Vendor capability, price, terms, and regulatory posture change, so a sourcing choice has a finite review life." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections-2", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections-2", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections-2", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Pair this tree with Framework 1 for opportunity screening, Framework 7 for data authority and readiness, and Framework 8 for lifecycle change control. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview-3", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview-3", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview-3", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The AI-capability diagnostic separates strategy, data, technology, workflow adoption, talent, governance, monitoring, and realized value. It helps a manager identify the binding constraint without treating a stage label, model count, or elapsed time as an external benchmark." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-3", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-3", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-3", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Assess each capability dimension with observable evidence, record the source and date, identify the constraint that blocks the next valuable and governable use case, and choose the smallest improvement with a success criterion and stop rule. Reassess dimensions independently after deployment or a material change. Use this maturity model as a managerial diagnostic, not as an external benchmark. Current public evidence shows that AI adoption is broad, but measurable enterprise value and scaled operating changes remain uneven across organizations. [BB-C16-S03] [BB-C16-S08] 5 Levels:" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-visual-representation-ai-maturity-model-capability-diagnostic", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Visual Representation: AI Maturity Model - Capability Diagnostic", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-visual-representation-ai-maturity-model-capability-diagnostic", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-visual-representation-ai-maturity-model-capability-diagnostic", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "AI-capability diagnostic (constructed). Evaluate evidence across strategy, data, technology, workflow adoption, talent, governance, monitoring, and realized value. Do not infer maturity from a company label, model count, elapsed time, or a single composite stage. [BB-C16-S03] [BB-C16-S08] Figure 16.2. AI-capability diagnostic loop (constructed). The loop directs attention from intended outcomes and risk boundaries to capability evidence, binding constraints, a governed improvement, and post-deployment measurement. It is a local diagnostic design, not a maturity benchmark or prescribed sequence. Text equivalent: Define the business outcomes and risk boundary, assess each capability dimension independently, identify the constraints that block the next valuable use case, choose the smallest governed improvement, and reassess after deployment evidence. Organizations can be strong in one dimension and weak in another; progress is not necessarily linear. Level 1: Ad Hoc - Isolated AI experiments - No strategy or governance - Individual data scientists working alone - Possible evidence: work is disconnected from a defined decision, accountable owner, governed lifecycle, or measured outcome Level 2: Foundational - AI strategy defined - Data infrastructure investments started - Small AI team formed - Possible evidence: selected use cases have owners and enabling work has begun, but deployment and value evidence remain limited Level 3: Operational - Multiple AI models in production - MLOps processes established - Cross-functional AI teams - Possible evidence: production systems are monitored and at least some use cases show attributable adoption, value, quality, or risk outcomes Level 4: Strategic - AI core to business model - Continuous AI innovation - Strong talent pipeline - Indicator: AI drives material revenue, cost, quality, or risk outcomes Level 5: Transformative - AI-first organization - AI advantages compound (data flywheel) - Industry-leading capabilities - Possible evidence: governed AI capabilities materially shape the operating model or value proposition and remain defensible after lifecycle cost and risk Progression Path: There is no universal sequence, job title, project count, or timeline. Improve the binding capability needed for the next valuable and governable use case; retain stop criteria; measure deployment, adoption, value, incidents, and residual risk; and reassess each dimension independently. Acquisition or outsourcing can add capability, but it does not transfer accountability or guarantee integration." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-3", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-3", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-3", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Diagnose the capability that constrains the next decision rather than chasing a maturity label. - Use evidence from actual workflows, controls, adoption, outcomes, and incidents—not only strategy documents or model inventories. - Treat acquisition, vendors, and consultants as capability inputs that still require internal ownership and integration." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-3", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-3", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-3", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Stage models imply linear progress even when organizations improve unevenly across dimensions. - “Strategic” and “transformative” are context-dependent descriptions, not proof of value or defensibility. - Public adoption surveys do not establish causality, audited financial impact, or the maturity of a particular organization." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections-3", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections-3", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections-3", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use Framework 7 to investigate data constraints, Framework 8 to assess lifecycle controls, and Framework 10 to assign governance authority for the capability changes identified here. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview-4", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview-4", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview-4", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The prioritization worksheet makes assumptions about impact, confidence, ease, and data quality visible for comparison. Its arithmetic is an author-created aid; strategic fit, dependencies, risk, legal or safety obligations, and capacity can override the score." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-4", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-4", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-4", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define each factor locally, preserve the evidence behind every rating, test alternative weights and plausible ranges, and compare the leading option with a non-AI baseline. Record who rated the use case, what would falsify the assumptions, and what decision follows if the evidence is weak. Provenance boundary: This is an author-created, ICE-like comparison worksheet rather than a canonical ICE formula. Scores are ordinal judgments, not measured probabilities or value estimates; preserve the underlying evidence and let constraints or obligations override the arithmetic. Illustrative three-factor score: Enhanced for AI: Prioritization Table: The equal-weight average below is a constructed comparison aid. Preserve the four inputs, test sensitivity to weights and ranges, and allow strategic fit, dependencies, risk, legal/safety obligations, and capacity to override the ordering. Table 16.3: Constructed prioritization worksheet (Use case | Impact | Confidence | Ease | Data quality | Score | Priority). Scores are ordinal judgments for this example and should be replaced by documented local evidence. | Use Case | Impact | Confidence | Ease | Data Quality | Score | Priority | |----------|--------|------------|------|--------------|-------|----------| | Churn prediction | 9 | 8 | 7 | 9 | 8.3 | 2 | | Price optimization | 10 | 6 | 5 | 7 | 7.0 | 3 | | Gen AI support | 8 | 9 | 9 | 8 | 8.5 | 1 | | Computer vision QC | 7 | 4 | 3 | 3 | 4.3 | 4 |" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-4", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-4", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-4", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Use scoring to make disagreement and missing evidence discussable, not to automate prioritization. - Check whether a high score survives conservative assumptions, capacity limits, and risk review. - Keep the raw inputs and decision record so the ranking can be challenged and updated." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-4", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-4", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-4", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ordinal scores do not become objective probabilities merely because they are averaged. - Equal weighting can conceal a factor that is actually a constraint or legal obligation. - A high score can reflect optimism, data leakage, or an attractive but poorly defined outcome." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections-4", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections-4", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections-4", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Feed the prioritized use case into Framework 5 for range-based economics, Framework 7 for data readiness, and Framework 8 for evaluation and change control. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview-5", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview-5", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview-5", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The AI business-case worksheet connects benefits, costs, timing, uncertainty, and decision gates. It is useful only when the baseline, counterfactual, attribution method, cash-flow treatment, and residual risks are explicit." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-5", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-5", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-5", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the decision and counterfactual first. Build low, base, and high cases; separate observed results from assumptions; include recurring and transition costs; discount multi-year cash flows where material; and report a go, redesign, stage, or stop recommendation with a review date. Provenance boundary: This is an author-created business-case worksheet, not a finding from the cited survey. Current practitioner evidence supports caution about the gap between organizational AI use and realized enterprise value; it does not validate this formula's inputs, a forecast benefit, or a universal return threshold. [BB-C16-S08] Framework: Detailed Calculation: Benefits (Annual): - Revenue lift: Increased conversions, upsells, new products - Cost reduction: Labor automation, efficiency gains - Risk mitigation: estimated reduction in expected fraud loss, downtime exposure, or control failure; this is an uncertain benefit, not a guarantee - Customer experience: Retention improvement, NPS increase → revenue Costs (Total): - Development: Data science team, engineering, infrastructure (Months 0-6) - Deployment: Integration, testing, change management (Months 6-12) - Maintenance: Monitoring, retraining, updates (Ongoing annually) Example - AI Chatbot (illustrative placeholders, not external evidence): Benefits (Year 1): - Customer support cost reduction: labor hours avoided from automating defined ticket categories - Improved response time: retention or satisfaction benefit where customer behavior data supports it - Availability benefit: incremental sales or service capture if the channel is measurable - Total Gain: revenue increase + cost reduction + risk mitigation value Costs: - Development: product, engineering, data, and integration work - Data preparation: labeling, knowledge-base cleanup, evaluation sets - Platform/infrastructure: model access, retrieval, monitoring, security, and support - Total Cost: development + deployment + maintenance ROI = (Total Gain - Total Cost) / Total Cost Simple payback period = Initial net cash outlay / Expected annual net cash benefit Use cash-flow timing rather than accounting labels when calculating payback. Include recurring costs in the annual net benefit, state whether benefits ramp, discount multi-year cash flows where material, and report a range when inputs are uncertain." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-5", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-5", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-5", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Treat ROI as a decision record under uncertainty, not as a promise that a model will create value. - Make the non-AI counterfactual, benefit owner, measurement window, and cost boundary auditable. - Stop or redesign when observed evidence does not support the range or when risk controls are not viable." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-5", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-5", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-5", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Revenue lift, productivity, retention, and risk mitigation can be difficult to attribute to one intervention. - A percentage ROI can hide timing, scale, distributional effects, option value, and downside exposure. - Risk mitigation value is uncertain and should not be presented as realized cash benefit without evidence." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections-5", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections-5", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections-5", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use Framework 4 to test prioritization assumptions, Framework 8 to include lifecycle and monitoring costs, and Framework 11 to evaluate adoption and job-design effects. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview-6", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview-6", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview-6", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The ethical-AI framework translates recognized risk-management and policy principles into questions about affected people, documentation, privacy, accountability, safety, remedy, and benefit. It supports review; it does not determine legal compliance or resolve contested value judgments by itself." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-6", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-6", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-6", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Identify the use, affected people, decision rights, applicable law and policy, foreseeable harms, evidence needed, accountable owner, escalation route, and remedy. Select controls proportionate to the use and risk, document residual uncertainty, and revisit the assessment when the system, data, population, or workflow changes. Anchor responsible-AI governance in recognized public frameworks: NIST AI RMF for risk-management functions and trustworthy-AI characteristics, OECD AI Principles for policy-level values, and NIST's generative-AI profile for GenAI-specific risks. [BB-C16-S01] [BB-C16-S02] [BB-C16-S04] 6 Operating Principles: 1. Fairness & Harmful-Bias Management - Test performance and error patterns across legally and operationally relevant groups - Mitigate harmful bias through data review, model changes, process controls, and human oversight - Audit high-impact models on a defined cadence 2. Transparency, Explainability & Documentation - Document intended use, limitations, evaluation evidence, and known failure modes - Provide explanations appropriate to the decision context and audience - Use interpretable models or explanation methods where the decision is high-stakes 3. Privacy & Data Protection - Minimize data collection and respect purpose limitations - Anonymize, pseudonymize, or aggregate data where appropriate - Align with applicable privacy and sector rules - Secure data through access controls, encryption, logging, and retention limits 4. Accountability & Governance - Assign clear ownership for each AI system - Human-in-the-loop for high-risk decisions - Appeal/override mechanisms 5. Safety, Validity & Robustness - Test for realistic misuse, adversarial behavior, and out-of-distribution cases - Monitor for model drift - Fail-safe mechanisms (if model uncertain, defer to human) 6. Human-Centered Benefit - Make the intended human or organizational benefit explicit - Consider stakeholder impact beyond narrow shareholder outcomes - Avoid use cases where foreseeable harms dominate plausible benefits Ethics Review Process: 1. Categorize risk: Low, medium, high, or prohibited/restricted under relevant policy and law 2. Ethics review: High-risk applications require documented review and accountable approval 3. Bias testing: Measure performance across demographic groups 4. Ongoing monitoring: Set a documented cadence and trigger set appropriate to the use, population, impact, and applicable obligations 5. Incident response: Process for when AI causes harm" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-6", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-6", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-6", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Put affected people, accountability, explanation, appeal, and remedy into the operating design—not only into a principles statement. - Treat risk categories and review gates as authority- and jurisdiction-specific decisions. - Preserve evidence of what was tested, what was not tested, who accepted residual risk, and how incidents are handled." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-6", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-6", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-6", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Principles can conflict and do not specify one universally correct trade-off. - Group metrics and explanation methods can be incomplete, unstable, or misleading in context. - A review or audit does not prove fairness, safety, legality, or absence of harm." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections-6", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections-6", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections-6", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use Framework 7 for data and label quality, Framework 8 for technical controls, and Framework 10 for ownership, escalation, and independent challenge. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview-7", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview-7", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview-7", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The data-readiness assessment identifies whether data, labels, infrastructure, authority, and quality evidence are sufficient for the intended decision and risk boundary. Readiness is a process of resolving blocking gaps, not a single score or volume threshold." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-7", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-7", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-7", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the target, population, data authority, quality dimensions, leakage risks, labeling method, access controls, retention, and acceptance criteria. Test representative data, record missingness and uncertainty, obtain the necessary domain and control-owner review, and distinguish “ready to model” from “ready for production.” Treat data readiness as a process, not a single threshold. ISO/IEC 5259-4 frames data quality for analytics and machine learning as an organizational process; use this checklist to find gaps before model work begins. [BB-C16-S07] 5 Dimensions: 1. Data Availability (Quantity) - [ ] Sufficient volume for the model type, expected variability, and error tolerance - [ ] Historical data covers relevant scenarios - [ ] Can collect more data if needed 2. Data Quality - [ ] Missing values are quantified, explainable, and handled through a documented strategy - [ ] Errors and duplicates are profiled, corrected, or excluded with documented rules - [ ] Consistent formatting - [ ] No major outliers unless legitimate 3. Data Relevance (Right Features) - [ ] Features correlate with target variable - [ ] Causal features available (not just correlated) - [ ] Minimal data leakage (future info in training data) 4. Data Labeling - [ ] Labels accurate and consistent - [ ] Inter-annotator agreement or equivalent quality checks are appropriate for the use case - [ ] Labeling guidelines documented - [ ] Process to label new data 5. Data Infrastructure - [ ] Centralized data storage (data warehouse/lake) - [ ] Data pipelines automated - [ ] Version control for datasets - [ ] Access controls and audit logs Scoring: - All critical dimensions met → Ready to model with documented assumptions - Some dimensions weak → Prepare by fixing the blocking gaps before production work - Multiple critical gaps → Invest in the data foundation before model development" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-7", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-7", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-7", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Ask whether the data is authorized, representative, timely, fit for the decision, and traceable—not merely abundant. - Separate model-development readiness from production and monitoring readiness. - Make unresolved data gaps visible in the go, redesign, stage, or stop decision." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-7", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-7", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-7", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Data quality is use-case specific; a clean dataset can still be irrelevant, biased, stale, or unauthorized. - Checklists can create false confidence when evidence is self-reported or the population changes. - More data does not automatically improve validity, fairness, privacy, or business value." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections-7", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections-7", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections-7", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use Framework 6 for privacy, fairness, and affected-stakeholder review; Framework 8 for versioning and monitoring; and Framework 9 for agent data and memory boundaries. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview-8", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview-8", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview-8", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The MLOps change-control framework treats deployment as a governed lifecycle: versioned inputs and code, evaluation, staged release, monitoring, diagnosis, rollback or remediation, and documented authorization. A signal can open a change; it does not automatically authorize retraining or deployment." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-8", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-8", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-8", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the system boundary, decision owner, data and model versions, evaluation suite, business and risk guardrails, release authority, monitoring signals, incident path, rollback mechanism, and retirement conditions before production. Re-run the relevant evidence when the model, data, population, vendor, tool, or workflow changes. For predictive machine-learning systems, MLOps should connect data validation, training, deployment, monitoring, and retraining. For generative AI and foundation-model systems, add secure-development, evaluation, access-control, and misuse-monitoring controls to the lifecycle. [BB-C16-S09] [BB-C16-S10] End-to-End ML Lifecycle: Figure 16.3. Governed machine-learning lifecycle (constructed). Monitoring can open a controlled change, but it does not automatically authorize retraining or deployment. The lifecycle retains evidence, approvals, staged release, incident response, and rollback. [BB-C16-S09] [BB-C16-S10] Text equivalent: Governed data enters a versioned build and training process. A candidate is evaluated against technical, business, safety, fairness, security, privacy, accessibility, latency, and cost criteria. Approved candidates move through staged deployment and monitoring. A signal triggers diagnosis and change control; it can lead to rollback, remediation, a new candidate, or retirement rather than automatic retraining. Detailed Pipeline: 1. Data Pipeline - Ingestion (batch/streaming) - Validation (schema checks, quality tests) - Storage (data lake, feature store) 2. Training Pipeline - Feature engineering (transformations, feature store) - Model training (hyperparameter tuning, cross-validation) - Model evaluation (test set, business metrics) - Model registry (version control, metadata) 3. Deployment Pipeline - Containerization (Docker) - A/B testing (shadow mode, gradual rollout) - Inference serving (REST API, batch predictions) - Integration (embed in applications) 4. Monitoring Pipeline - Performance monitoring (accuracy, latency, errors) - Data drift detection (input distributions changing) - Model drift detection (accuracy degrading) - Alerting (Slack/PagerDuty when metrics degrade) 5. Retraining Loop - Trigger: Performance drops below threshold - Open a controlled change; preserve the current data, code, model, configuration, and decision record - Diagnose whether data, labels, population, workflow, environment, or measurement changed - Validate a candidate against pre-specified quality, safety, fairness, security, latency, cost, and business guardrails - Obtain required approvals, stage release, monitor, and retain rollback; do not auto-deploy because one aggregate metric improved MLOps Tools: - Orchestration: Airflow, Kubeflow, MLflow - Feature Store: Feast, Tecton - Model Registry: MLflow, Weights & Biases - Monitoring: Evidently AI, Fiddler, Arize" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-8", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-8", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-8", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Require an accountable release decision and an evidence trail for every material model or system change. - Design monitoring to detect decision, safety, security, privacy, accessibility, cost, and workflow problems—not only aggregate accuracy drift. - Preserve rollback, restriction, fallback, incident response, and retirement options before scaling exposure." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-8", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-8", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-8", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Monitoring signals can be delayed, incomplete, or unavailable when labels arrive late or outcomes are hard to observe. - A technically improved model can worsen workflow outcomes, fairness, security, or cost. - Tool names and deployment patterns change; the control requirements outlast any particular product." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections-8", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections-8", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections-8", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use Framework 6 for risk and remedy, Framework 7 for data lineage and quality, and Framework 9 for stronger authority and interruption controls in agentic systems. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview-9", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview-9", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview-9", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The agentic-AI operating and control model treats tool-using model output as delegated execution. It makes identity, authority, data and memory, tools, transaction scope, approvals, evidence, interruption, recovery, and remedy explicit before an agent can affect a consequential workflow." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-9", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-9", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-9", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Define the accountable principal, agent identity and version, goal, allowed data and tools, least-privilege scope, transaction and recursion limits, approval gates, evaluation scenarios, event records, stop conditions, revocation, fallback, and compensation or remedy path. Test complete trajectories, including ambiguity, prompt injection, tool error, duplicate action, unavailable service, partial failure, and unauthorized escalation. An AI agent can select and sequence actions through software tools, data, applications, or other agents. That changes the managerial problem: model output becomes delegated execution. The control boundary must therefore cover the agent's identity, authority, data and memory, tools, transaction scope, human approvals, evidence, interruption, and recovery—not only response quality. [BB-C16-S01] [BB-C16-S04] [BB-C16-S10] [BB-C16-S14] NIST's February 2026 software-agent identity and authorization paper is a concept paper for a potential NCCoE project, not a final standard or certification. It identifies current questions around identification, authorization, auditing, non-repudiation, and prompt-injection mitigation. The operating model below is an author synthesis that also draws on the NIST AI RMF, Generative AI Profile, and secure-development guidance. [BB-C16-S01] [BB-C16-S04] [BB-C16-S10] [BB-C16-S14]" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-authority-record-before-execution", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Authority record before execution", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-authority-record-before-execution", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-authority-record-before-execution", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Table 16.4: Agent authority record (Control | Managerial question | Minimum record). The fields are a local design aid; applicable law, policy, security architecture, and the affected workflow determine what evidence and approval are actually required. | Control | Managerial question | Minimum record | |---|---|---| | Identity and principal | Which agent instance acts for which person, service, or organization? | Authenticated identity, accountable owner, environment, version, and session/run ID | | Delegated authority | Which decisions and transactions may it make, recommend, draft, or execute? | Explicit scope, least privilege, tool allowlist, objects, amounts, recipients, jurisdictions, and expiry | | Data and memory | What may it read, retain, infer, combine, retrieve, or disclose? | Source authority, classification, purpose, minimization, retention, isolation, and deletion rules | | Approval gates | Which actions need human or independent approval before commitment? | Named approver, evidence required, separation of duties, timeout, and denial path | | Execution limits | What bounds a multi-step run? | Step, time, cost, transaction, rate, resource, and recursion limits; prohibited actions | | Evidence and evaluation | How will capability, misuse, injection, tool error, compounding failure, and side effects be tested? | Scenario suite, adversarial tests, full trajectory logs, business and risk guardrails, and acceptance/stop criteria | | Interruption and recovery | How is the agent paused, revoked, contained, rolled back, or failed over? | Kill/revoke mechanism, fallback, checkpoint, compensating transaction, incident owner, and recovery test | | Audit and remedy | Can an affected person or reviewer reconstruct and challenge the action? | Tamper-evident event record, inputs/outputs/tool calls/approvals, notice, appeal, correction, and remediation path |" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-agent-execution-control-loop", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Agent execution-control loop", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-agent-execution-control-loop", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-agent-execution-control-loop", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Figure 16.4. Agentic-AI execution and control loop (constructed). Authority is checked at both plan and action time because a permitted goal does not imply that every intermediate tool call or transaction is authorized. Monitoring can interrupt the run, and every consequential action remains attributable to a human or organizational principal. [BB-C16-S01] [BB-C16-S04] [BB-C16-S10] [BB-C16-S14] Text equivalent: An authorized principal defines the decision, agent identity, goal, data boundary, tools, limits, approvals, and stop rules. The agent proposes a bounded plan. Policy checks and, when required, a human approver authorize each consequential action. The system executes through allowlisted tools, records the trajectory, observes outcomes, and either continues, requests approval, falls back, revokes authority, rolls back, or enters incident response. Evaluation covers the complete multi-step trajectory rather than only the final answer." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-applied-control-exercise", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Applied control exercise", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-applied-control-exercise", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-applied-control-exercise", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "A procurement agent may assemble supplier evidence and draft a purchase request, but it may not add a new vendor, accept terms, expose confidential bid data, or commit funds. The team specifies approved systems, supplier records, spend ceiling, prohibited data, prompt-injection tests, approval threshold, run limits, audit evidence, revocation, and fallback. It then evaluates normal, ambiguous, malicious, unavailable-tool, duplicate-transaction, and partial-failure trajectories. A fluent final message does not pass the test if an intermediate action exceeded authority." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-9", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-9", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-9", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Treat an agent as a principal-bound workflow component with explicit authority, not as a chatbot with extra buttons. - Test and log intermediate actions because a safe-looking final message can conceal an unauthorized or harmful trajectory. - Make pause, revoke, fallback, rollback, appeal, and remediation operational before granting consequential access." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-9", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-9", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-9", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- The control model is an author synthesis and cannot replace system-specific threat modeling, legal review, or security testing. - Complete trajectory evaluation is expensive and still cannot enumerate every future tool, data, or social context. - Human approval can become ceremonial if the evidence, scope, time, or reviewer independence is inadequate." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections-9", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections-9", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections-9", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use Chapter 19 for identity, access, third-party, and incident controls; Chapter 20 for rights and remedy; Chapter 21 for product evidence gates; and Chapter 22 for evaluation, uncertainty, and reproducibility. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview-10", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview-10", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview-10", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The AI governance structure assigns decision rights, competence, independence, evidence, escalation, appeal, incident response, and remediation across existing management systems. The right design depends on the organization's risk profile and operating context, not on a required committee name or calendar." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-10", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-10", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-10", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Map each AI use to an accountable business owner and relevant legal, privacy, security, safety, accessibility, procurement, audit, workforce, and domain authorities. Record who can approve, challenge, restrict, pause, remediate, and retire the system; define evidence and escalation; then choose meeting and review cadences that fit the risk and lifecycle. Governance should match the AI risk profile and organizational management system. NIST AI RMF emphasizes Govern, Map, Measure, and Manage functions, while ISO/IEC 42001 frames AI governance as a management system with policies, roles, risk controls, and continuous improvement. [BB-C16-S01] [BB-C16-S06] The roles and cadences below are constructed design options. Existing board, executive, product, risk, legal, privacy, security, safety, audit, accessibility, procurement, and workforce structures may own these decisions. What matters is documented authority, competence, independence, evidence, escalation, appeal, incident response, and remediation—not a committee label or fixed meeting frequency. Roles & Responsibilities: AI Steering Committee (Strategic) - Composition: CEO, CTO, CDO, Chief AI Officer, Business unit heads - Cadence: Set by portfolio risk, decision volume, incidents, and material change; quarterly is only an illustrative option - Responsibilities: - Approve AI strategy and budget - Review high-risk AI projects - Resolve cross-functional conflicts - Monitor competitive AI landscape AI Center of Excellence (Operational) - Composition: Chief AI Officer (lead), ML engineers, data scientists, product managers - Cadence: Set by delivery dependencies and assurance needs; weekly is only an illustrative option - Responsibilities: - Develop AI roadmap - Prioritize use cases - Establish standards and best practices - Provide expertise to business units - Manage shared AI infrastructure AI Ethics Board (Risk) - Composition: Legal, compliance, ethicist, AI leads, domain experts - Cadence: Set by use-case risk, affected people, incidents, and applicable obligations; monthly is only an illustrative option - Responsibilities: - Review high-risk AI applications - Audit models for bias - Investigate AI incidents - Update ethical guidelines Project Teams (Execution) - Composition: Data scientist, ML engineer, product manager, domain expert - Cadence: Set locally for the delivery and risk profile; a daily standup is only one possible coordination mechanism. - Responsibilities: - Build and deploy AI models - Iterate based on feedback - Monitor production models - Document learnings" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-10", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-10", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-10", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Name the person or group that owns the decision and the person or group that can challenge or stop it. - Use existing governance where it has the authority and competence; do not create committees that merely add ceremony. - Make escalation, appeal, incident response, and remedy visible to affected people and control owners." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-10", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-10", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-10", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Committee structures can obscure accountability when authority is shared but no one can decide or stop. - Independence and competence are contextual; a role label does not prove either. - Fixed cadences are brittle when risk, incidents, exposure, or system change require faster review." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections-10", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections-10", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections-10", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use Framework 6 for ethical and rights-based review, Framework 8 for release control, and Framework 11 for workforce participation and adoption evidence. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-overview-11", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Overview", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-overview-11", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-overview-11", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "The change-management playbook connects adoption to job design, participation, training, workflow evidence, control ownership, and remedy. It is a local diagnostic and sequencing aid, not proof that a prescribed communication sequence causes adoption." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-11", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How to Apply", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-11", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-11", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Identify who is affected and how work, authority, incentives, skills, measurement, and escalation will change. Involve affected workers and control owners early, test the new workflow, measure both benefits and harms, protect good-faith challenge, and revise or stop when the change does not improve the intended outcome or creates unacceptable risk. Provenance boundary: The playbook below is an author-created AI adaptation of Kotter's change sequence. It is a diagnostic aid, not a universal causal model or a substitute for participation, labor and employment review, accessibility, job redesign, grievance and appeal channels, or local evidence about adoption barriers. Common Resistance: - \"AI will take my job\" (automation fear) - \"I don't trust the algorithm\" (black box concern) - \"It's too complex\" (technical intimidation) - \"We've always done it this way\" (status quo bias) Change Management Playbook: 1. Create Urgency (Kotter Step 1) - Show competitive threat: \"Competitors using AI to...\" - Demonstrate opportunity: \"AI can help us...\" - Use data: \"We're losing X customers because...\" 2. Build Coalition (Kotter Step 2) - Identify AI champions in each department - Train \"AI ambassadors\" (power users) - Include affected employees, domain experts, control owners, and skeptics; treat objections as evidence to investigate, protect good-faith escalation, and document unresolved disagreement 3. Communicate Vision (Kotter Steps 3-4) - Simple message: \"AI helps you focus on creative work by automating repetitive tasks\" - Show, don't tell: Demos, pilot results, case studies - Repeat through multiple channels until the operating change is understood 4. Enable Action (Kotter Step 5) - Training: \"AI Literacy 101\" for all employees - Support: Help desk, office hours, documentation - Remove barriers: Fix bad data, provide tools, update policies 5. Generate Wins (Kotter Step 6) - Start with easiest, highest-value use case - Celebrate early adopters publicly - Share metrics: \"AI saved Mary 5 hours/week\" 6. Address Job Displacement - Reskilling programs (transition to AI-adjacent roles) - Transparency about which roles affected - Compare job redesign, workload, redeployment, training, accommodation, and staffing options with affected workers, HR, Legal, accessibility, and labor-relations owners; do not promise redeployment when it is not authorized or feasible 7. Sustain (Kotter Steps 7-8) - Embed accountable workflow outcomes, safe-use expectations, and role-appropriate learning in operating reviews; do not reward tool use for its own sake - Hire for AI skills - Continuous learning culture Measurement: - AI adoption rate (% employees using AI tools) - Sentiment surveys (trust in AI, willingness to use) - Business outcomes (productivity, accuracy, speed)" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-11", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "So What for Managers", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-11", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-11", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Measure whether the redesigned workflow improves outcomes for the organization and affected people, not merely whether a tool was used. - Make participation, challenge, accommodation, training, redeployment, and appeal part of the operating design. - Treat resistance as evidence about incentives, workload, trust, safety, or job impact that needs investigation." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-11", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Limits and Critiques", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-11", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-11", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "- Change sequences are heuristics; power, labor relations, culture, incentives, and operating constraints can alter the path. - Adoption metrics can reward superficial usage and miss workarounds, exclusion, surveillance concerns, or harm. - A communication campaign cannot compensate for weak data, poor controls, unsafe work design, or an unconvincing business case." }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-connections-11", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Connections", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-connections-11", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-connections-11", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Use Framework 5 for benefit and cost ranges, Framework 6 for affected-stakeholder and remedy review, and Chapter 17 for transformation leadership and operating-model change. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-how-to-get-started", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "How To Get Started", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-get-started", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-how-to-get-started", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Most organizations struggle not with understanding AI's potential, but with execution: which use case to pursue first, how to build governance without bureaucracy, and how to deliver value before the pilot budget runs out. This guide has three deliberately different layers, with a clear hierarchy: - Quick Version: front-end triage and pilot-readiness handoff; it does not authorize production deployment. - Detailed Version: strategy, business-case, governance, and pilot-design work; it is a design path, not a second production runbook. - Operating Manual: the canonical detailed execution and decision-gate template; use it when implementing a pilot, adapting its schedule to local evidence. If the templates conflict, the approved local project record and applicable control-owner decision govern. Constructed execution-template boundary: The schedules, counts, scores, budgets, team sizes, sample ranges, product examples, thresholds, and outputs in this guide are illustrative planning placeholders. Replace them with evidence from the specific workflow, population, risk profile, staffing model, legal and policy review, procurement terms, and measurement design. A template cannot establish that an AI use case is feasible, safe, compliant, or economically attractive. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-quick-version-3-4-weeks-illustrative-path-rapid-ai-opportunity-assessment-pilot-selection", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Quick Version (3-4 Weeks; illustrative path): Rapid AI Opportunity Assessment & Pilot Selection", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-quick-version-3-4-weeks-illustrative-path-rapid-ai-opportunity-assessment-pilot-selection", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-quick-version-3-4-weeks-illustrative-path-rapid-ai-opportunity-assessment-pilot-selection", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Identify and evidence a small set of opportunities on a bounded local schedule; a pilot launch date follows the decision, data, control, and staffing evidence rather than a universal 30-day promise. Who Should Use This: Organizations new to AI, need a fast evidence triage, or have limited AI resources; use the Detailed Version and canonical Operating Manual before any consequential deployment. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-week-1-ai-opportunity-assessment", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Week 1: AI Opportunity Assessment", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-week-1-ai-opportunity-assessment", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-week-1-ai-opportunity-assessment", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Generate 20+ potential AI use cases and score them on feasibility/value. Activities: Day 1-2: Use Case Discovery Workshops - Facilitate 3 workshops with different departments (Sales, Operations, Customer Service) - Use prompt: \"What manual, repetitive, or data-heavy work consumes 5+ hours/week?\" - Capture 20-30 raw ideas (target: 7-10 per workshop) Day 3-4: Preliminary Scoring - Score each use case on 2x2 matrix (Value: Low/High, Feasibility: Low/High) - Value criteria: Revenue impact, cost reduction, customer experience improvement - Feasibility criteria: Data exists, <6 months to value, no major technical blockers - Identify 5-8 \"Quick Win\" candidates (High Value + High Feasibility) Day 5: Stakeholder Review - Present 2x2 matrix to leadership - Get buy-in on top 5 use cases for deeper assessment Deliverable: AI Opportunity Assessment Matrix with 20+ use cases mapped, 5 Quick Win candidates identified. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-week-2-icp-use-case-selection", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Week 2: ICP Use Case Selection", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-week-2-icp-use-case-selection", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-week-2-icp-use-case-selection", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Prioritize top 3 use cases using ICE scoring + data readiness check. Activities: Day 1-2: Deep Dive on Top 5 - For each Quick Win candidate, assess: - Impact (1-10): Quantify business value (e.g., \"$500K cost savings/year\") - Confidence (1-10): Technical feasibility + team capability - Ease (1-10): Time to production, resource requirements - Data Quality (1-10): Data exists, clean, sufficient volume - Calculate the illustrative AI Score as (Impact + Confidence + Ease + Data Quality) / 4 ; preserve the raw evidence and test sensitivity rather than treating the arithmetic as a decision rule. Day 3: Data Readiness Spot Checks - For top 3 scored use cases, validate data actually exists: - Request representative sample datasets - Check for missing values, labeling, data quality issues - Flag material missingness, inconsistent labels, or undocumented transformations as red flags Day 4: Build/Buy/Partner Decision - For each top 3, decide approach: - Buy: a currently available off-the-shelf solution after capability, assurance, portability, data-use, and commercial diligence - Partner: a platform plus implementation or domain support after authority, security, IP, and exit review - Build: In-house if proprietary data + core differentiator - Estimate cost for each approach Day 5: Final Prioritization - Rank top 3 by AI Score - Select #1 for immediate pilot (highest score + stakeholder support) Deliverable: Use Case Prioritization Matrix with top 3 ranked, #1 selected for pilot, Build/Buy/Partner recommendation documented. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-week-3-pilot-planning", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Week 3: Pilot Planning", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-week-3-pilot-planning", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-week-3-pilot-planning", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Scope MVP, assign team, set success metrics for first pilot. Activities: Day 1-2: Scope MVP - Define minimum viable product: - Problem: What specific pain point does this solve? - Success metric: How do we measure if it worked? (e.g., materially reduce ticket resolution time) - Scope: What's in/out? (Start narrow: one customer segment, one product line) - Timeline: 6-8 weeks to MVP (model training + initial deployment) Day 3: Assign Team - Pilot Owner: Business stakeholder who owns the problem (accountable for adoption) - Data Scientist: 1-2 people (model development) - ML Engineer: 1 person (deployment, infrastructure) - Domain Expert: SME who understands the data (e.g., sales manager for churn prediction) - Part-time: Product manager (requirements), legal (data privacy review) Day 4: Data Access & Infrastructure - Provision access to required datasets (get IT/security approvals) - Set up development environment (cloud sandbox, Jupyter notebooks, etc.) - Document data schema, glossary, known issues Day 5: Kick-off Meeting - Present 6-8 week timeline with milestones: - Weeks 1-2: Data prep, EDA, baseline model - Weeks 3-4: Model training, hyperparameter tuning - Weeks 5-6: Deployment, A/B test, monitoring - Weeks 7-8: Results analysis, iteration - Set weekly check-in cadence (every Friday) Deliverable: Pilot Scope Document (1-pager: problem, MVP, success metrics, team, 6-8 week timeline). ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-week-4-pilot-readiness-handoff", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Week 4: Pilot-Readiness Handoff", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-week-4-pilot-readiness-handoff", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-week-4-pilot-readiness-handoff", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Begin only the non-production evidence work approved by the local gate and hand off to the canonical Operating Manual if a pilot remains justified. Activities: Day 1-3: Data Preparation - Extract data from source systems (CRM, database, logs) - Clean data: Handle missing values, remove duplicates, fix outliers - Label data (if supervised learning): Use SME review and documented labeling guidelines - Split data into training, validation, and test sets using a method appropriate for the use case Day 4-5: Baseline Model - Train simple baseline (e.g., logistic regression, decision tree) - Evaluate performance: Accuracy, precision, recall, F1 - Document baseline performance and the production target in business and model terms - Set a target for iteration Deliverable: Clean dataset (versioned), baseline model performance metrics, week 5-8 plan to improve model. --- Output After Week 4: 1. AI Opportunity Assessment: candidate set and 2×2 matrix visualization 2. Use Case Prioritization: documented comparison, constraints, and decision owner 3. Pilot Scope: 1-page scope doc with MVP definition 4. Pilot handoff: evidence, scope, controls, and open questions for the canonical Operating Manual 5. Decision status: go, redesign, stage, or stop; no production commitment is implied ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-detailed-version-12-16-weeks-illustrative-path-strategy-governance-and-pilot-design", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Detailed Version (12-16 Weeks; illustrative path): Strategy, Governance, and Pilot Design", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-detailed-version-12-16-weeks-illustrative-path-strategy-governance-and-pilot-design", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-detailed-version-12-16-weeks-illustrative-path-strategy-governance-and-pilot-design", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Goal: Design a comprehensive AI strategy, governance, and first-pilot case. Execute and gate any pilot through the canonical Operating Manual and the approved local project record. Who Should Use This: Organizations serious about AI transformation, have executive buy-in, and resources for 3-4 month engagement. ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-phase-1-ai-opportunity-assessment-weeks-1-2", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Phase 1: AI Opportunity Assessment (Weeks 1-2)", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-phase-1-ai-opportunity-assessment-weeks-1-2", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-phase-1-ai-opportunity-assessment-weeks-1-2", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Identify 20-30 use cases across organization, score on feasibility/value, and create AI strategy roadmap. Week 1: Use Case Discovery Activities: - Use Case Workshops (5 sessions): Facilitate with Sales, Marketing, Operations, Finance, Customer Service - Competitive AI Analysis: Research what competitors are doing with AI (annual reports, press releases, demos) - Industry Best Practices: Identify top 3 AI use cases in your industry (e.g., retail: personalization, pricing, inventory) - Technology Scan: Review AI capability classes relevant to the use case (current foundation models for generative AI; conventional machine learning for prediction) Deliverables: - 20-30 use case ideas documented (template: Problem, Current State, AI Solution, Expected Value) - Competitive AI landscape summary (1-page) Week 2: Preliminary Scoring & Roadmap Activities: - 2×2 Matrix Mapping: Plot all use cases on Value/Feasibility matrix - Identify Quick Wins: 5-8 High Value + High Feasibility candidates - Identify Strategic Bets: 3-5 High Value + Low Feasibility long-term investments - Stakeholder Interviews: Validate assumptions with 5-7 exec stakeholders - 3-Year Roadmap: Draft high-level AI roadmap (Year 1: Quick Wins, Year 2: Scale, Year 3: Strategic Bets) Deliverables: - AI Opportunity Assessment Matrix (visualization with all use cases plotted) - 3-Year AI Roadmap (1-page timeline) ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-phase-2-use-case-prioritization-business-case-weeks-3-4", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Phase 2: Use Case Prioritization & Business Case (Weeks 3-4)", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-phase-2-use-case-prioritization-business-case-weeks-3-4", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-phase-2-use-case-prioritization-business-case-weeks-3-4", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Deep dive on top 3-5 use cases, build ROI models, select first 2 pilots. Week 3: Deep Dive Analysis Activities: - Top 5 Use Case Deep Dives (1 day each): - Map current process (flowchart, identify pain points) - Define AI solution (specific model type, input/output) - Data assessment (volume, quality, labeling requirements) - Technical feasibility (complexity, integration requirements) - Risk assessment (bias, privacy, regulatory) Example Deep Dive - Customer Churn Prediction: - Current State: material churn in a measurable customer segment - AI Solution: Predict churn in advance using customer behavior data - Data: customer records, usage features, support history, and NPS or equivalent signal - Success Metric: reduce churn enough to create measurable retained revenue - Risks: depends on data sensitivity, explainability needs, and downstream customer treatment Deliverables: - 5 Use Case Deep Dive Reports (3-5 pages each) Week 4: ROI Modeling & Prioritization Activities: - Build ROI Models (3-year NPV): - Benefits: Revenue lift + Cost reduction + Risk mitigation (quantified annually) - Costs: Development, deployment, monitoring, change management, and maintenance - ROI Calculation: NPV using the organization's normal hurdle rate Example ROI - Churn Prediction: - Year 1 Benefit: retained revenue from the first customer segment - Year 2-3 Benefit: expansion benefit if the model scales to additional segments - Total Cost: development, deployment, monitoring, and maintenance - 3-Year NPV: calculate from the actual business case; do not reuse generic target values - Prioritization worksheet: Compare the selected use cases using the documented local factors and sensitivity analysis; do not treat a rank as an automatic launch order. - Build/Buy/Partner Decision: For each use case, decide optimal approach - Risk Assessment: Flag high-risk use cases requiring ethics review Deliverables: - ROI Models (Excel/Google Sheets) for top 5 use cases - Final Prioritization (ranked 1-5, top 2 selected for pilots) - Build/Buy/Partner recommendations with cost estimates ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-phase-3-ai-governance-ethics-weeks-5-6", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Phase 3: AI Governance & Ethics (Weeks 5-6)", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-phase-3-ai-governance-ethics-weeks-5-6", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-phase-3-ai-governance-ethics-weeks-5-6", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Establish AI governance structure, ethical guidelines, and data access controls before building production models. Week 5: Governance Structure Activities: - Define AI Governance Roles: - AI Steering Committee: CEO, CTO, CDO, business unit heads (cadence set by decision rights and portfolio risk) - AI Center of Excellence: Chief AI Officer, ML leads, product managers (operating cadence set locally) - AI Ethics Board or equivalent review authority: Legal, compliance, ethicist, AI leads (review triggers and cadence set by use and risk) - Project Teams: Data scientists, ML engineers, product, domain experts (coordination cadence set by delivery needs) - Charter Each Body: - Document responsibilities, decision rights, escalation paths - Set meeting cadence and agenda templates - AI Policy Documentation: - Data Usage Policy: What data can be used for AI? (PII handling, customer consent, retention) - Model Approval Process: Low/Medium/High risk categorization, who approves each level - Incident Response: What happens if AI causes harm? (investigation, remediation, communication) Deliverables: - AI Governance Charter (5-7 pages: roles, responsibilities, processes) - AI Policy Pack (Data, Model Approval, Incident Response) Week 6: Ethics & Bias Assessment Activities: - Ethical AI Framework Implementation: - Train AI teams on 6 principles (Fairness, Transparency, Privacy, Accountability, Safety, Beneficence) - Create ethics checklist for all high-risk AI projects - Bias Testing Plan: - For selected pilot use cases, identify protected classes to test (race, gender, age, etc.) - Define fairness metrics (e.g., equal opportunity, demographic parity) - Plan for bias mitigation (data balancing, fairness constraints, post-processing) - Privacy & Security: - Data minimization: Only use data necessary for AI task - Anonymization: Remove PII where possible (differential privacy techniques) - Access controls: Role-based access to training data, model outputs - Compliance check: identify applicable privacy, sector, accessibility, employment, and AI obligations with qualified legal and control owners; examples may include GDPR, CCPA, or HIPAA where their scope applies Deliverables: - Ethical AI Checklist (1-page, used for every AI project) - Bias Testing Protocol (for pilot use cases) - Privacy & Security Controls Documentation ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-phase-4-first-pilot-planning-weeks-7-8", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Phase 4: First Pilot Planning (Weeks 7-8)", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-phase-4-first-pilot-planning-weeks-7-8", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-phase-4-first-pilot-planning-weeks-7-8", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Detailed planning for first pilot - scope, team, data pipeline, timeline, success metrics. Week 7: Pilot Scoping & Team Activities: - MVP Definition: - Problem Statement: Specific pain point (e.g., \"Support tickets taking 48 hours to resolve, target 24 hours\") - AI Solution: Model type, version, inputs, outputs, and controls (e.g., \"approved generative model + governed knowledge base → draft responses for human review\") - Scope: Boundaries (e.g., \"Start with 10 most common ticket types, English only, US customers\") - Success Metrics: - Model Metrics: quality, safety, latency, and reliability thresholds appropriate to the use case - Business Metrics: ticket resolution time, customer satisfaction, cost, or revenue change - Adoption Metrics: eligible workflow volume handled safely by the system over a defined period - Team Assembly: - Pilot Owner: named business owner for the workflow (accountable for business results) - Data Science Lead: 1 senior data scientist (model development) - ML Engineers: 2 engineers (infrastructure, deployment, monitoring) - Product Manager: Owns user experience, requirements - Domain Experts: 2 support managers (data labeling, validation, change management) - Part-time: Legal (privacy review), Security (access controls), IT (integration) - Stakeholder Alignment: - Present pilot plan to AI Steering Committee - Get budget approval based on the approved scope, loaded labor, infrastructure, vendor, governance, and change costs - Align with IT on infrastructure (cloud budget, security approvals) Deliverables: - Pilot Charter (3-5 pages: problem, MVP, team, success metrics, budget) - Stakeholder sign-off (Steering Committee approval) Week 8: Data Pipeline & Infrastructure Activities: - Data Pipeline Design: - Data Sources: Identify systems (CRM, support ticketing, product database) - Data Extraction: Batch vs. streaming, frequency (daily ETL, real-time APIs) - Data Storage: Data lake (raw), data warehouse (cleaned), feature store (ML-ready) - Data Quality: Validation rules (schema checks, null checks, outlier detection) - Infrastructure Setup: - Cloud Environment: Provision AWS/GCP/Azure resources (compute, storage) - MLOps Tooling: Set up experiment tracking (MLflow, W&B), model registry, orchestration (Airflow) - Development Environment: Jupyter notebooks, VS Code, version control (GitHub) - Security: VPN access, IAM roles, data encryption at rest/in transit - Data Access Approvals: - Legal review for data usage (customer consent, GDPR compliance) - Security review for access controls (who can see what data) - IT provisioning (database credentials, API keys) Deliverables: - Data Pipeline Architecture Diagram (data flow, systems, storage) - Infrastructure Setup Guide (how to access, security protocols) - Data Dictionary (all fields, definitions, known issues) ---" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions::chapter-16-ai-strategy-and-data-driven-decisions-phase-5-pilot-execution-weeks-9-12", "kind": "chapter", "itemSlug": "chapter-16-ai-strategy-and-data-driven-decisions", "itemTitle": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "heading": "Phase 5: Pilot Execution (Weeks 9-12)", "headingId": "chapter-16-ai-strategy-and-data-driven-decisions-phase-5-pilot-execution-weeks-9-12", "url": "#chapter-16-ai-strategy-and-data-driven-decisions-phase-5-pilot-execution-weeks-9-12", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "publicationStatus": "public", "citationStatus": "vetted", "text": "Objective: Build, train, validate, and iterate on first AI model. Week 9: Data Preparation & EDA Activities: - Data Extraction: Pull a period and sample sufficient for the task, population, seasonality, subgroup and tail coverage, uncertainty, and validation design; do not reuse a universal duration or sample count - Exploratory Data Analysis (EDA): - Univariate analysis: Distributions, missing values, outliers - Bivariate analysis: Feature correlations with target variable - Multivariate analysis: Feature interactions, multicollinearity - Data quality summary: missingness, errors, duplicates - Data Cleaning: - Handle missing values: impute, investigate, or exclude based on documented rules - Remove duplicates: De-duplicate based on unique keys - Fix outliers: Cap at 99th percentile or investigate (could be legitimate) - Normalize/standardize: Scale features for model training - Feature Engineering: - Create new features: Aggregations (sum, avg over time), ratios, lags (for time-series) - Encode categoricals: One-hot encoding, target encoding - Feature selection: Remove low-variance, highly correlated features Deliverables: - Clean Dataset (versioned in feature store) - EDA notebook with visualizations - Feature Documentation (what each feature represents) Week 10: Model Training & Validation Activities: - Baseline Model: - Train simple model (logistic regression, decision tree) - Evaluate on validation set: Accuracy, precision, recall, F1, AUC - Document baseline performance in the agreed model and business metrics - Advanced Models: - Compare a small set of plausible model classes selected for the task, baseline, data, controls, and operating constraints - Hyperparameter tuning: Grid search, random search, Bayesian optimization - Use a validation design appropriate to the data-generating process and leakage risks; fold count is a local methodological choice - Model Evaluation: - Test set performance: document final metrics on held-out test set - Business metric translation: connect model performance to workflow or financial outcomes - Error analysis: Where does model fail? (certain ticket types, edge cases) - Model Explainability: - SHAP/LIME: Which features drive predictions? - Feature importance: Top 10 most predictive features - Document for transparency (especially if high-risk use case) Deliverables: - Trained candidate models, as justified by the validation plan, versioned in the model registry - Model evaluation memo with metrics, comparison table, and recommendation - Model explainability memo with SHAP plots or feature importance Week 11: Bias Testing & Refinement Activities: - Bias Testing: - Segment test set by protected classes (if applicable: gender, age, race, geography) - Measure performance disparity across approved comparison groups - Fairness metrics: Demographic parity, equal opportunity, equalized odds - Bias Mitigation (if issues found): - Data balancing: Oversample underrepresented groups - Algorithmic fairness: Add fairness constraints to loss function - Post-processing: Adjust decision thresholds per group - Re-evaluate: Did mitigation work? Trade-offs in overall accuracy? - Model Refinement: - Incorporate feedback from domain experts (does model make sense?) - A/B test variations: Different feature sets, model types - Select final production model: Best balance of performance, explainability, fairness Deliverables: - Bias testing memo with performance by relevant group - Final Production Model (selected, documented, approved by ethics board if high-risk) Week 12: Deployment Preparation Activities: - Model Deployment: - Containerize model: Docker image with model, dependencies, API endpoint - Deploy to staging: Test in non-production environment - Integration testing: Ensure model integrates with application (API calls, latency