{ "schemaVersion": "1.1.0", "title": "The Modern MBA Toolkit", "subtitle": "Frameworks, Models & Strategic Tools for the AI Era", "version": "2.1", "contentUpdated": "2026-07-13", "edition": "public", "feedback": { "endpoint": "https://www.drjlsmith.com/contact.php", "anonymous": true, "identityFieldsRequested": [], "reportFields": [ "category", "chapter_slug", "chapter_title", "section", "page_url", "details", "reference_url" ], "networkAddress": { "use": "temporary abuse prevention", "includedInReportMessage": false }, "categories": [ { "value": "incorrect_information", "label": "Incorrect information" }, { "value": "missing_information", "label": "Missing information" }, { "value": "other_information", "label": "Other information feedback" }, { "value": "missing_reference", "label": "Missing reference" }, { "value": "incorrect_reference", "label": "Incorrect reference" }, { "value": "other", "label": "Other" } ] }, "entries": [ { "id": "chapter-01-macroeconomics-for-strategic-leaders", "slug": "chapter-01-macroeconomics-for-strategic-leaders", "kind": "chapter", "number": 1, "title": "Macroeconomics for Strategic Leaders", "part": "Part 1: Core MBA Foundations", "summary": "Business-cycle evidence, inflation, rates, fiscal policy, labor markets, currencies, shocks, and uncertainty-aware macro scenarios for operators.", "citationStatus": "vetted", "publicationStatus": "public", "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" ], "relatedSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-14-go-to-market-strategy" ], "sourcePath": "src/part1-foundations/01-macroeconomics-for-managers.md", "outputPath": "index.html#chapter-01-macroeconomics-for-strategic-leaders", "markdownPath": "markdown/chapter-01-macroeconomics-for-strategic-leaders.md", "wordCount": 6611, "checksum": "f3d9d6bd047265e504fbea5eebee2d976633b8c5426aa395be32356d2770ca21", "sourceIds": [ "BB-C01-S13", "BB-C01-S04", "BB-C01-S14", "BB-C01-S01", "BB-C01-S02", "BB-C01-S19", "BB-C01-S12", "BB-C01-S05", "BB-C01-S10", "BB-C01-S20", "BB-C01-S06", "BB-C01-S08", "BB-C01-S03", "BB-C01-S07", "BB-C01-S11", "BB-C01-S17", "BB-C01-S18", "BB-C01-S09", "BB-C01-S21", "BB-C01-S15", "BB-C01-S16" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-01-macroeconomics-for-strategic-leaders-executive-summary" }, { "level": 2, "text": "1. GDP Growth & Business Cycle Analysis", "id": "chapter-01-macroeconomics-for-strategic-leaders-1-gdp-growth-business-cycle-analysis" }, { "level": 3, "text": "Overview", "id": "chapter-01-macroeconomics-for-strategic-leaders-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply" }, { "level": 4, "text": "Long-run growth and productivity", "id": "chapter-01-macroeconomics-for-strategic-leaders-long-run-growth-and-productivity" }, { "level": 3, "text": "So What for Managers", "id": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-01-macroeconomics-for-strategic-leaders-connections" }, { "level": 2, "text": "2. Inflation & Pricing Strategy Matrix", "id": "chapter-01-macroeconomics-for-strategic-leaders-2-inflation-pricing-strategy-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-01-macroeconomics-for-strategic-leaders-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-01-macroeconomics-for-strategic-leaders-connections-2" }, { "level": 2, "text": "Troubleshooting guide: Macroeconomic analysis", "id": "chapter-01-macroeconomics-for-strategic-leaders-troubleshooting-guide-macroeconomic-analysis" }, { "level": 2, "text": "3. Interest Rate & Capital Investment Decision Tree", "id": "chapter-01-macroeconomics-for-strategic-leaders-3-interest-rate-capital-investment-decision-tree" }, { "level": 3, "text": "Overview", "id": "chapter-01-macroeconomics-for-strategic-leaders-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-01-macroeconomics-for-strategic-leaders-connections-3" }, { "level": 2, "text": "4. Unemployment & Labor Market Analysis", "id": "chapter-01-macroeconomics-for-strategic-leaders-4-unemployment-labor-market-analysis" }, { "level": 3, "text": "Overview", "id": "chapter-01-macroeconomics-for-strategic-leaders-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-01-macroeconomics-for-strategic-leaders-connections-4" }, { "level": 2, "text": "5. Currency Exchange Rate & Global Strategy", "id": "chapter-01-macroeconomics-for-strategic-leaders-5-currency-exchange-rate-global-strategy" }, { "level": 3, "text": "Overview", "id": "chapter-01-macroeconomics-for-strategic-leaders-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-01-macroeconomics-for-strategic-leaders-connections-5" }, { "level": 2, "text": "6. Fiscal Policy Impact Assessment", "id": "chapter-01-macroeconomics-for-strategic-leaders-6-fiscal-policy-impact-assessment" }, { "level": 3, "text": "Overview", "id": "chapter-01-macroeconomics-for-strategic-leaders-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-01-macroeconomics-for-strategic-leaders-connections-6" }, { "level": 2, "text": "7. Monetary Policy Radar (Central Bank Watching)", "id": "chapter-01-macroeconomics-for-strategic-leaders-7-monetary-policy-radar-central-bank-watching" }, { "level": 3, "text": "Overview", "id": "chapter-01-macroeconomics-for-strategic-leaders-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-01-macroeconomics-for-strategic-leaders-connections-7" }, { "level": 2, "text": "8. Global Economic Indicators Dashboard", "id": "chapter-01-macroeconomics-for-strategic-leaders-8-global-economic-indicators-dashboard" }, { "level": 3, "text": "Overview", "id": "chapter-01-macroeconomics-for-strategic-leaders-overview-8" }, { "level": 3, "text": "Provenance-first dashboard design", "id": "chapter-01-macroeconomics-for-strategic-leaders-provenance-first-dashboard-design" }, { "level": 3, "text": "How to Apply", "id": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-01-macroeconomics-for-strategic-leaders-connections-8" }, { "level": 2, "text": "9. Supply & Demand Shock Analysis", "id": "chapter-01-macroeconomics-for-strategic-leaders-9-supply-demand-shock-analysis" }, { "level": 3, "text": "Overview", "id": "chapter-01-macroeconomics-for-strategic-leaders-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-9" }, { "level": 3, "text": "Real-world case: Network propagation after the 2011 Great East Japan earthquake", "id": "chapter-01-macroeconomics-for-strategic-leaders-real-world-case-network-propagation-after-the-2011-great-east-japan-earthquake" }, { "level": 3, "text": "So What for Managers", "id": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-01-macroeconomics-for-strategic-leaders-connections-9" }, { "level": 2, "text": "10. Yield Curve & Recession Forecasting", "id": "chapter-01-macroeconomics-for-strategic-leaders-10-yield-curve-recession-forecasting" }, { "level": 3, "text": "Overview", "id": "chapter-01-macroeconomics-for-strategic-leaders-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-01-macroeconomics-for-strategic-leaders-how-to-apply-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-01-macroeconomics-for-strategic-leaders-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-01-macroeconomics-for-strategic-leaders-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-01-macroeconomics-for-strategic-leaders-connections-10" }, { "level": 2, "text": "Applied exercise: A vintage-aware macro scenario", "id": "chapter-01-macroeconomics-for-strategic-leaders-applied-exercise-a-vintage-aware-macro-scenario" }, { "level": 2, "text": "Chapter summary", "id": "chapter-01-macroeconomics-for-strategic-leaders-chapter-summary" } ], "figures": [ { "id": "chapter-01-macroeconomics-for-strategic-leaders-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C01-S02", "BB-C01-S04", "BB-C01-S14" ], "provenanceStatus": "constructed", "checksum": "f33c49b5827df211cde0e63ed5b1292a285352642c53d6cc051b6ad391b2f87d" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-figure-2", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C01-S05" ], "provenanceStatus": "constructed", "checksum": "0cdb496696694777e83f84e7f9ec048cf358e7ee9e6b8c6942bdc93a07acefbd" } ], "tables": [ { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-1", "caption": "Table 1. Working diagnosis / Evidence to collect / Options to test", "headers": [ "Working diagnosis", "Evidence to collect", "Options to test", "Stop rule / constraint" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 3 }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-2", "caption": "Table 2. Indicator / Tight Market / Balanced", "headers": [ "Indicator", "Tight Market", "Balanced", "Loose Market" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-3", "caption": "Table 3. Business Activity / Currency Exposure / Impact of Strong USD", "headers": [ "Business Activity", "Currency Exposure", "Impact of Strong USD", "Impact of Weak USD" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-4", "caption": "Table 4. Policy change / Transmission questions / Firm evidence required", "headers": [ "Policy change", "Transmission questions", "Firm evidence required" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-5", "caption": "Table 5. Signal / What to Watch / How to Interpret", "headers": [ "Signal", "What to Watch", "How to Interpret" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-6", "caption": "Table 6. Field / Required entry / Why it matters", "headers": [ "Field", "Required entry", "Why it matters" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-7", "caption": "Table 7. Observed signal / Confirm before acting / Decision test", "headers": [ "Observed signal", "Confirm before acting", "Decision test" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-8", "caption": "Table 8. Shock / Immediate questions / Near-term tests", "headers": [ "Shock", "Immediate questions", "Near-term tests", "Longer-term options to evaluate" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 } ], "tools": [ { "id": "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "label": "DCF valuation template", "target": "../../templates/04-DCF-Valuation-Model-Template.md", "sourcePath": "templates/04-DCF-Valuation-Model-Template.md", "outputPath": "downloads/chapter-01-macroeconomics-for-strategic-leaders-04-DCF-Valuation-Model-Template.md", "mediaType": "text/markdown", "checksum": "4e70a035bef88c72be33dc85e6b59ce96d0eeaa0e835757757546175bbedf6ba" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-tool-2", "label": "DCF workbook", "target": "../../models/04_DCF_Valuation_Model.xlsx", "sourcePath": "models/04_DCF_Valuation_Model.xlsx", "outputPath": "downloads/chapter-01-macroeconomics-for-strategic-leaders-04_DCF_Valuation_Model.xlsx", "mediaType": "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet", "checksum": "d2c5fdc418b4edf60d3f0f53d9e8cca15f5a42d93b0a09e0beffd33809a220cd" } ], "visibility": "public", "pagePath": "chapters/chapter-01-macroeconomics-for-strategic-leaders.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-14-go-to-market-strategy", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-c-public-record-decision-cases", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-19-cybersecurity-and-risk-management-for-managers" ] }, { "id": "chapter-02-business-law-governance-and-ethics", "slug": "chapter-02-business-law-governance-and-ethics", "kind": "chapter", "number": 2, "title": "Business Law, Governance, and Ethics", "part": "Part 1: Core MBA Foundations", "summary": "Governance, contracts, IP, fiduciary duties, ESG, privacy, and ethical decision-making for managers.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "relatedSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-15-fundraising-and-finance" ], "sourcePath": "src/part1-foundations/02-business-law-governance-ethics.md", "outputPath": "index.html#chapter-02-business-law-governance-and-ethics", "markdownPath": "markdown/chapter-02-business-law-governance-and-ethics.md", "wordCount": 10679, "checksum": "319f68ecff733cfb9c52fbb1a55d6e1a1988df98c17f25906e6cb23f5f3f6a81", "sourceIds": [ "BB-C02-S01", "BB-C02-S07", "BB-C02-S04", "BB-C02-S05", "BB-C02-S02", "BB-C02-S03", "BB-C02-S12", "BB-C02-S13", "BB-C02-S14", "BB-C02-S20", "BB-C02-S11", "BB-C02-S15", "BB-C02-S08", "BB-C02-S09", "BB-C02-S06", "BB-C02-S10", "BB-C02-S16", "BB-C02-S17", "BB-C02-S26", "BB-C02-S18", "BB-C02-S19", "BB-C02-S21", "BB-C02-S22", "BB-C02-S23", "BB-C02-S24", "BB-C02-S25" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-02-business-law-governance-and-ethics-executive-summary" }, { "level": 2, "text": "1. Business-Judgment Review as a Governance Process", "id": "chapter-02-business-law-governance-and-ethics-1-business-judgment-review-as-a-governance-process" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections" }, { "level": 2, "text": "2. Intellectual Property (IP) Protection Matrix", "id": "chapter-02-business-law-governance-and-ethics-2-intellectual-property-ip-protection-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply-2" }, { "level": 3, "text": "Patent, secrecy, and speed are portfolio choices", "id": "chapter-02-business-law-governance-and-ethics-patent-secrecy-and-speed-are-portfolio-choices" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections-2" }, { "level": 2, "text": "Troubleshooting Guide: Law, Governance, and Ethics", "id": "chapter-02-business-law-governance-and-ethics-troubleshooting-guide-law-governance-and-ethics" }, { "level": 2, "text": "3. Contract Law Essentials for Managers", "id": "chapter-02-business-law-governance-and-ethics-3-contract-law-essentials-for-managers" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections-3" }, { "level": 2, "text": "4. Corporate Governance Models (Shareholder vs. Stakeholder)", "id": "chapter-02-business-law-governance-and-ethics-4-corporate-governance-models-shareholder-vs-stakeholder" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview-4" }, { "level": 3, "text": "The Two Models", "id": "chapter-02-business-law-governance-and-ethics-the-two-models" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply-4" }, { "level": 3, "text": "Contrarian Thinking: The False Dichotomy", "id": "chapter-02-business-law-governance-and-ethics-contrarian-thinking-the-false-dichotomy" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections-4" }, { "level": 2, "text": "5. Agency Theory & Executive Compensation", "id": "chapter-02-business-law-governance-and-ethics-5-agency-theory-executive-compensation" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview-5" }, { "level": 3, "text": "The Agency Problem", "id": "chapter-02-business-law-governance-and-ethics-the-agency-problem" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections-5" }, { "level": 2, "text": "6. The ESG (Environmental, Social, Governance) Framework", "id": "chapter-02-business-law-governance-and-ethics-6-the-esg-environmental-social-governance-framework" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview-6" }, { "level": 3, "text": "The Three Pillars", "id": "chapter-02-business-law-governance-and-ethics-the-three-pillars" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply-6" }, { "level": 3, "text": "Contrarian Thinking: Avoid \"Greenwashing\"", "id": "chapter-02-business-law-governance-and-ethics-contrarian-thinking-avoid-greenwashing" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections-6" }, { "level": 2, "text": "7. Ethical Decision-Making Models", "id": "chapter-02-business-law-governance-and-ethics-7-ethical-decision-making-models" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply-7" }, { "level": 3, "text": "Constructed example: The \"Layoff\" dilemma", "id": "chapter-02-business-law-governance-and-ethics-constructed-example-the-layoff-dilemma" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections-7" }, { "level": 2, "text": "8. Rawlsian Fairness Challenge (Author Adaptation)", "id": "chapter-02-business-law-governance-and-ethics-8-rawlsian-fairness-challenge-author-adaptation" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply-8" }, { "level": 3, "text": "Constructed examples", "id": "chapter-02-business-law-governance-and-ethics-constructed-examples" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections-8" }, { "level": 2, "text": "9. AI Ethics & Risk Assessment Matrix", "id": "chapter-02-business-law-governance-and-ethics-9-ai-ethics-risk-assessment-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply-9" }, { "level": 3, "text": "The AI Risk Assessment Matrix", "id": "chapter-02-business-law-governance-and-ethics-the-ai-risk-assessment-matrix" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-9" }, { "level": 3, "text": "Applied regulatory case: facial recognition in retail", "id": "chapter-02-business-law-governance-and-ethics-applied-regulatory-case-facial-recognition-in-retail" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections-9" }, { "level": 2, "text": "10. Privacy and GDPR Issue-Spotting Checklist", "id": "chapter-02-business-law-governance-and-ethics-10-privacy-and-gdpr-issue-spotting-checklist" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply-10" }, { "level": 3, "text": "The operator's GDPR issue-spotting checklist", "id": "chapter-02-business-law-governance-and-ethics-the-operator-s-gdpr-issue-spotting-checklist" }, { "level": 3, "text": "Administrative-fine ceilings are not automatic outcomes", "id": "chapter-02-business-law-governance-and-ethics-administrative-fine-ceilings-are-not-automatic-outcomes" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections-10" }, { "level": 2, "text": "11. Legal Lifecycle Issue-Spotting for Managers", "id": "chapter-02-business-law-governance-and-ethics-11-legal-lifecycle-issue-spotting-for-managers" }, { "level": 3, "text": "Overview", "id": "chapter-02-business-law-governance-and-ethics-overview-11" }, { "level": 3, "text": "How to Apply", "id": "chapter-02-business-law-governance-and-ethics-how-to-apply-11" }, { "level": 3, "text": "The lifecycle risk gate", "id": "chapter-02-business-law-governance-and-ethics-the-lifecycle-risk-gate" }, { "level": 3, "text": "A reusable legal escalation record", "id": "chapter-02-business-law-governance-and-ethics-a-reusable-legal-escalation-record" }, { "level": 3, "text": "Constructed exercise — one company, six legal lanes", "id": "chapter-02-business-law-governance-and-ethics-constructed-exercise-one-company-six-legal-lanes" }, { "level": 3, "text": "So What for Managers", "id": "chapter-02-business-law-governance-and-ethics-so-what-for-managers-11" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-02-business-law-governance-and-ethics-limits-and-critiques-11" }, { "level": 3, "text": "Connections", "id": "chapter-02-business-law-governance-and-ethics-connections-11" }, { "level": 2, "text": "Chapter Summary", "id": "chapter-02-business-law-governance-and-ethics-chapter-summary" } ], "figures": [ { "id": "chapter-02-business-law-governance-and-ethics-figure-1", "type": "mermaid", "caption": "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].", "textEquivalent": "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.", "sourceIds": [ "BB-C02-S07" ], "provenanceStatus": "constructed", "checksum": "f004f7cc9a78bb57a7244c9d6696479e11c3757572483f1ccab95bbb2f65ca14" }, { "id": "chapter-02-business-law-governance-and-ethics-figure-2", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C02-S11" ], "provenanceStatus": "constructed", "checksum": "45f4fef0ac3b279cb7745296ea8fca72a978bdb076ac9d7d66443e212e2cac7f" }, { "id": "chapter-02-business-law-governance-and-ethics-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C02-S08", "BB-C02-S09" ], "provenanceStatus": "constructed", "checksum": "b904c0bd71eba1078a3054ae39d7995971c6cb08bd12731dcaacf0e13650ecb6" }, { "id": "chapter-02-business-law-governance-and-ethics-figure-4", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "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" ], "provenanceStatus": "constructed", "checksum": "20d6ef9280b14f7716d012036fd4aaa3687a3f4c4eaaa0cb2161625c8a842489" } ], "tables": [ { "id": "chapter-02-business-law-governance-and-ethics-table-1", "caption": "Table 2.1. IP protection routing comparison. Author-created comparison for issue spotting; it does not determine eligibility, ownership, or enforceability.", "headers": [ "Asset Type", "Protection Method", "Key Characteristic", "Operator's Action" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-02-business-law-governance-and-ethics-table-2", "caption": "Table 2.2. Corporate-purpose and governance lenses. Author-created comparison; neither column selects a legal duty or displaces governing law.", "headers": [ "Dimension", "Shareholder Primacy", "Stakeholder Capitalism" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-02-business-law-governance-and-ethics-table-3", "caption": "Table 2.3. Illustrative compensation-plan components. Author-created diagnostic; the components and questions are not universal recommendations.", "headers": [ "Component", "Illustrative role in a plan", "Purpose", "Questions for the compensation committee" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-02-business-law-governance-and-ethics-table-4", "caption": "Table 2.4. Constructed ESG planning example. These are example metrics and target-setting prompts, not benchmarks.", "headers": [ "Pillar", "Example Metrics", "Target" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-02-business-law-governance-and-ethics-table-5", "caption": "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.", "headers": [ "Ethical Framework", "Key Question", "Strengths", "Weaknesses" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-02-business-law-governance-and-ethics-table-6", "caption": "Table 2.6. Constructed layoff/pay-cut decision lenses. The questions apply to either option; the exercise does not recommend one option.", "headers": [ "Decision lens", "Questions to test for either option" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-02-business-law-governance-and-ethics-table-7", "caption": "Table 2.7. Constructed AI risk-triage levels. The categories and examples are illustrative; legal classification requires current, context-specific analysis.", "headers": [ "Risk Level", "Criteria", "Control questions and options", "Example" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-02-business-law-governance-and-ethics-table-8", "caption": "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.", "headers": [ "Issue lane", "Selected jurisdiction anchor", "Manager-facing trigger facts", "Counsel or specialist gate before action" ], "sourceIds": [ "BB-C02-S16", "BB-C02-S17", "BB-C02-S26", "BB-C02-S18", "BB-C02-S19", "BB-C02-S20", "BB-C02-S21", "BB-C02-S22", "BB-C02-S23", "BB-C02-S24", "BB-C02-S25" ], "provenanceStatus": "constructed", "rowCount": 6 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-02-business-law-governance-and-ethics.html", "outboundSlugs": [ "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-14-go-to-market-strategy", "chapter-15-fundraising-and-finance", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-b-contrarian-business-perspectives", "appendix-c-public-record-decision-cases", "chapter-01-macroeconomics-for-strategic-leaders", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-07-organizational-behavior-and-leadership", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy", "chapter-15-fundraising-and-finance", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy" ] }, { "id": "chapter-03-strategy-and-competitive-analysis", "slug": "chapter-03-strategy-and-competitive-analysis", "kind": "chapter", "number": 3, "title": "Strategy and Competitive Analysis", "part": "Part 1: Core MBA Foundations", "summary": "Industry structure, competitive advantage, market positioning, strategic options, and scenario planning.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "relatedSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-14-go-to-market-strategy", "chapter-18-digital-business-models-and-platform-economics" ], "sourcePath": "src/part1-foundations/03-strategy-competitive-analysis.md", "outputPath": "index.html#chapter-03-strategy-and-competitive-analysis", "markdownPath": "markdown/chapter-03-strategy-and-competitive-analysis.md", "wordCount": 10457, "checksum": "40f49032ab752a5762d3f5142b6d408c40a5149c92e6905575cc5174a733e0a9", "sourceIds": [ "BB-C03-S03", "BB-C03-S16", "BB-C03-S01", "BB-C03-S02", "BB-C03-S04", "BB-C03-S05", "BB-C03-S06", "BB-C03-S07", "BB-C03-S08", "BB-C03-S17", "BB-C03-S18", "BB-C03-S09", "BB-C03-S10", "BB-C03-S19", "BB-C03-S11", "BB-C03-S12", "BB-C03-S13", "BB-C03-S14", "BB-C03-S15", "BB-C03-S20", "BB-C03-S21", "BB-C03-S23", "BB-C03-S28", "BB-C03-S22", "BB-C03-S24", "BB-C03-S25", "BB-C03-S26", "BB-C03-S27", "BB-C03-S29", "BB-C03-S30" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-03-strategy-and-competitive-analysis-executive-summary" }, { "level": 3, "text": "Integrated Case: Northstar Industrial Analytics (Constructed)", "id": "chapter-03-strategy-and-competitive-analysis-integrated-case-northstar-industrial-analytics-constructed" }, { "level": 2, "text": "1. Porter's Five Forces Analysis", "id": "chapter-03-strategy-and-competitive-analysis-1-porter-s-five-forces-analysis" }, { "level": 3, "text": "Overview", "id": "chapter-03-strategy-and-competitive-analysis-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-03-strategy-and-competitive-analysis-how-to-apply" }, { "level": 3, "text": "Academic Citations & Evidence", "id": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence" }, { "level": 3, "text": "So What for Managers", "id": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-03-strategy-and-competitive-analysis-connections" }, { "level": 2, "text": "2. VRIO Framework & Dynamic Capabilities", "id": "chapter-03-strategy-and-competitive-analysis-2-vrio-framework-dynamic-capabilities" }, { "level": 3, "text": "Overview", "id": "chapter-03-strategy-and-competitive-analysis-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-03-strategy-and-competitive-analysis-how-to-apply-2" }, { "level": 3, "text": "Evidence-Based Contrarian Thinking: The Limits of VRIO & The Rise of Dynamic Capabilities", "id": "chapter-03-strategy-and-competitive-analysis-evidence-based-contrarian-thinking-the-limits-of-vrio-the-rise-of-dynamic-capabilities" }, { "level": 3, "text": "Academic Citations & Evidence", "id": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-03-strategy-and-competitive-analysis-connections-2" }, { "level": 2, "text": "3. Blue Ocean Strategy Canvas", "id": "chapter-03-strategy-and-competitive-analysis-3-blue-ocean-strategy-canvas" }, { "level": 3, "text": "Overview", "id": "chapter-03-strategy-and-competitive-analysis-overview-3" }, { "level": 3, "text": "When to Use", "id": "chapter-03-strategy-and-competitive-analysis-when-to-use" }, { "level": 3, "text": "How to Apply", "id": "chapter-03-strategy-and-competitive-analysis-how-to-apply-3" }, { "level": 3, "text": "Academic Citations & Evidence", "id": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-3" }, { "level": 3, "text": "Mermaid Diagram: ERRC Decision Flow", "id": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-errc-decision-flow" }, { "level": 3, "text": "Contrarian Thinking: The Blue Ocean Trap", "id": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-blue-ocean-trap" }, { "level": 3, "text": "So What for Managers", "id": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-03-strategy-and-competitive-analysis-connections-3" }, { "level": 2, "text": "4. BCG Growth-Share Matrix", "id": "chapter-03-strategy-and-competitive-analysis-4-bcg-growth-share-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-03-strategy-and-competitive-analysis-overview-4" }, { "level": 3, "text": "When to Use", "id": "chapter-03-strategy-and-competitive-analysis-when-to-use-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-03-strategy-and-competitive-analysis-how-to-apply-4" }, { "level": 3, "text": "Academic Citations & Evidence", "id": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-4" }, { "level": 3, "text": "Mermaid Diagram: BCG Growth-Share Matrix [BB-C03-S07]", "id": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-bcg-growth-share-matrix-bb-c03-s07" }, { "level": 3, "text": "Limits of the BCG Matrix [BB-C03-S07]", "id": "chapter-03-strategy-and-competitive-analysis-limits-of-the-bcg-matrix-bb-c03-s07" }, { "level": 3, "text": "So What for Managers", "id": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-03-strategy-and-competitive-analysis-connections-4" }, { "level": 2, "text": "5. Ansoff Matrix", "id": "chapter-03-strategy-and-competitive-analysis-5-ansoff-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-03-strategy-and-competitive-analysis-overview-5" }, { "level": 3, "text": "When to Use", "id": "chapter-03-strategy-and-competitive-analysis-when-to-use-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-03-strategy-and-competitive-analysis-how-to-apply-5" }, { "level": 3, "text": "Academic Citations & Evidence", "id": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-5" }, { "level": 3, "text": "Mermaid Diagram: Ansoff Matrix", "id": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-ansoff-matrix" }, { "level": 3, "text": "Contrarian Thinking: The Diversification Paradox", "id": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-diversification-paradox" }, { "level": 3, "text": "So What for Managers", "id": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-03-strategy-and-competitive-analysis-connections-5" }, { "level": 2, "text": "6. PESTLE Analysis", "id": "chapter-03-strategy-and-competitive-analysis-6-pestle-analysis" }, { "level": 3, "text": "Overview", "id": "chapter-03-strategy-and-competitive-analysis-overview-6" }, { "level": 3, "text": "When to Use", "id": "chapter-03-strategy-and-competitive-analysis-when-to-use-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-03-strategy-and-competitive-analysis-how-to-apply-6" }, { "level": 3, "text": "Academic Citations & Evidence", "id": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-6" }, { "level": 3, "text": "Mermaid Diagram: PESTLE Analysis Framework", "id": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-pestle-analysis-framework" }, { "level": 3, "text": "Contrarian Thinking: PESTLE's Illusion of Control", "id": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-pestle-s-illusion-of-control" }, { "level": 3, "text": "So What for Managers", "id": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-03-strategy-and-competitive-analysis-connections-6" }, { "level": 2, "text": "7. McKinsey 7S Framework", "id": "chapter-03-strategy-and-competitive-analysis-7-mckinsey-7s-framework" }, { "level": 3, "text": "Overview", "id": "chapter-03-strategy-and-competitive-analysis-overview-7" }, { "level": 3, "text": "When to Use", "id": "chapter-03-strategy-and-competitive-analysis-when-to-use-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-03-strategy-and-competitive-analysis-how-to-apply-7" }, { "level": 3, "text": "Academic Citations & Evidence", "id": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-7" }, { "level": 3, "text": "Mermaid Diagram: McKinsey 7S Framework [BB-C03-S10]", "id": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-mckinsey-7s-framework-bb-c03-s10" }, { "level": 3, "text": "Contrarian Thinking: The Alignment Trap", "id": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-alignment-trap" }, { "level": 3, "text": "So What for Managers", "id": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-03-strategy-and-competitive-analysis-connections-7" }, { "level": 2, "text": "8. Core Competency Analysis", "id": "chapter-03-strategy-and-competitive-analysis-8-core-competency-analysis" }, { "level": 3, "text": "Overview", "id": "chapter-03-strategy-and-competitive-analysis-overview-8" }, { "level": 3, "text": "When to Use", "id": "chapter-03-strategy-and-competitive-analysis-when-to-use-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-03-strategy-and-competitive-analysis-how-to-apply-8" }, { "level": 3, "text": "Academic Citations & Evidence", "id": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-8" }, { "level": 3, "text": "Mermaid Diagram: Core Competency Tree", "id": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-core-competency-tree" }, { "level": 3, "text": "Contrarian Thinking: The Core Competency Trap", "id": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-core-competency-trap" }, { "level": 3, "text": "So What for Managers", "id": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-03-strategy-and-competitive-analysis-connections-8" }, { "level": 2, "text": "9. Scenario Planning Matrix", "id": "chapter-03-strategy-and-competitive-analysis-9-scenario-planning-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-03-strategy-and-competitive-analysis-overview-9" }, { "level": 3, "text": "When to Use", "id": "chapter-03-strategy-and-competitive-analysis-when-to-use-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-03-strategy-and-competitive-analysis-how-to-apply-9" }, { "level": 3, "text": "Academic Citations & Evidence", "id": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-9" }, { "level": 3, "text": "Mermaid Diagram: Scenario Planning Matrix Example (AI Regulation)", "id": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-scenario-planning-matrix-example-ai-regulation" }, { "level": 3, "text": "Contrarian Thinking: Why Most Scenario Planning Fails", "id": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-why-most-scenario-planning-fails" }, { "level": 3, "text": "So What for Managers", "id": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-03-strategy-and-competitive-analysis-connections-9" }, { "level": 2, "text": "10. Platform Strategy Framework", "id": "chapter-03-strategy-and-competitive-analysis-10-platform-strategy-framework" }, { "level": 3, "text": "Overview", "id": "chapter-03-strategy-and-competitive-analysis-overview-10" }, { "level": 3, "text": "When to Use", "id": "chapter-03-strategy-and-competitive-analysis-when-to-use-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-03-strategy-and-competitive-analysis-how-to-apply-10" }, { "level": 3, "text": "Academic Citations & Evidence", "id": "chapter-03-strategy-and-competitive-analysis-academic-citations-evidence-10" }, { "level": 3, "text": "Mermaid Diagram: Platform Business Model", "id": "chapter-03-strategy-and-competitive-analysis-mermaid-diagram-platform-business-model" }, { "level": 3, "text": "Contrarian Thinking: The Platform Delusion", "id": "chapter-03-strategy-and-competitive-analysis-contrarian-thinking-the-platform-delusion" }, { "level": 3, "text": "So What for Managers", "id": "chapter-03-strategy-and-competitive-analysis-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-03-strategy-and-competitive-analysis-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-03-strategy-and-competitive-analysis-connections-10" }, { "level": 2, "text": "Managerial Economics Bridge: From Five Forces to Positioning", "id": "chapter-03-strategy-and-competitive-analysis-managerial-economics-bridge-from-five-forces-to-positioning" }, { "level": 3, "text": "The decision sequence", "id": "chapter-03-strategy-and-competitive-analysis-the-decision-sequence" }, { "level": 3, "text": "1. Demand elasticity and marginal analysis", "id": "chapter-03-strategy-and-competitive-analysis-1-demand-elasticity-and-marginal-analysis" }, { "level": 3, "text": "2. Cost, scale, market structure, and market power", "id": "chapter-03-strategy-and-competitive-analysis-2-cost-scale-market-structure-and-market-power" }, { "level": 3, "text": "3. Price discrimination, versioning, and bundling", "id": "chapter-03-strategy-and-competitive-analysis-3-price-discrimination-versioning-and-bundling" }, { "level": 3, "text": "4. Information asymmetry: diagnose when the hidden information matters", "id": "chapter-03-strategy-and-competitive-analysis-4-information-asymmetry-diagnose-when-the-hidden-information-matters" }, { "level": 3, "text": "5. Strategic response with a payoff matrix", "id": "chapter-03-strategy-and-competitive-analysis-5-strategic-response-with-a-payoff-matrix" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-03-strategy-and-competitive-analysis-input-output-interlinkages" }, { "level": 2, "text": "Troubleshooting Guide: Strategic Analysis", "id": "chapter-03-strategy-and-competitive-analysis-troubleshooting-guide-strategic-analysis" }, { "level": 2, "text": "Strategic Mental Models: From Tool Use to Choice", "id": "chapter-03-strategy-and-competitive-analysis-strategic-mental-models-from-tool-use-to-choice" }, { "level": 3, "text": "1. Strategy requires tradeoffs and fit", "id": "chapter-03-strategy-and-competitive-analysis-1-strategy-requires-tradeoffs-and-fit" }, { "level": 3, "text": "2. Diagnose before prescribing", "id": "chapter-03-strategy-and-competitive-analysis-2-diagnose-before-prescribing" }, { "level": 3, "text": "3. Anticipate response and second-order effects", "id": "chapter-03-strategy-and-competitive-analysis-3-anticipate-response-and-second-order-effects" }, { "level": 3, "text": "4. Treat advantage as an erosion hypothesis", "id": "chapter-03-strategy-and-competitive-analysis-4-treat-advantage-as-an-erosion-hypothesis" }, { "level": 3, "text": "5. Separate industry effects from firm effects", "id": "chapter-03-strategy-and-competitive-analysis-5-separate-industry-effects-from-firm-effects" }, { "level": 3, "text": "Integrated decision record", "id": "chapter-03-strategy-and-competitive-analysis-integrated-decision-record" }, { "level": 2, "text": "Chapter Summary", "id": "chapter-03-strategy-and-competitive-analysis-chapter-summary" } ], "figures": [ { "id": "chapter-03-strategy-and-competitive-analysis-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S06" ], "provenanceStatus": "constructed", "checksum": "00be95f36150dd80701080547e0a7cc994d6545a0c17037804f779c5d6cb731b" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-2", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S07" ], "provenanceStatus": "constructed", "checksum": "a07ab2b2c983145d69563bd6b34e0ad2ddade7bfd68d23fe0f26d511e0edc916" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S08" ], "provenanceStatus": "source-linked", "checksum": "a32505c251e4c1f9768b745063957b8d8dc8bec96a40f0acb80cf2f3f8d65551" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-4", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S09" ], "provenanceStatus": "source-linked", "checksum": "389a685f92794d2edd58bba27abaac53ece2d522837abac8c09037296874b098" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-5", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S10" ], "provenanceStatus": "constructed", "checksum": "9c0318cb62b7fb4d1c71f9ec7fc750453b08fbbf4edb9118266ad6571bd1d19e" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-6", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S11" ], "provenanceStatus": "constructed", "checksum": "6b1e655889967b7b98409125d010fbe9613d4475e4897928e81a3964503dbf1b" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-7", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S13" ], "provenanceStatus": "constructed", "checksum": "6a5882d0b22d8cb3ddb79fe06fbcc2d19a10a74e1ac8b60d0eb78e354ac97be7" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-8", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S14" ], "provenanceStatus": "constructed", "checksum": "dfa6236841a1b38b946f92e77f9d7a4429a44b3f39407f45b703e14e21dc7cbd" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-9", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S20", "BB-C03-S21", "BB-C03-S23", "BB-C03-S28" ], "provenanceStatus": "constructed", "checksum": "ba9e8ff3708ad0dbaee8e89994997927c68425b0fecf5c73e0a312c06fc8bf82" } ], "tables": [ { "id": "chapter-03-strategy-and-competitive-analysis-table-1", "caption": "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.", "headers": [ "Structure", "Managerial hypothesis", "Five Forces connection", "Positioning implication" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-03-strategy-and-competitive-analysis-table-2", "caption": "Table 3.2. Information-asymmetry issue-spotting matrix. The mechanisms are candidate controls to test; they are not universal remedies or legal requirements.", "headers": [ "Information problem", "Diagnostic question", "Candidate mechanisms to test", "Failure mode" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 2 }, { "id": "chapter-03-strategy-and-competitive-analysis-table-3", "caption": "Table 3.3. Constructed two-firm response matrix for a price move. Read each cell as (Firm A, Firm B) .", "headers": [ "Firm A \\ Firm B", "Hold value-based price", "Cut price" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2 }, { "id": "chapter-03-strategy-and-competitive-analysis-table-4", "caption": "Table 3.4. Constructed strategy-kernel decision record. This author-created worksheet connects diagnosis, choice, coherent actions, scenarios, and review evidence.", "headers": [ "Element", "Required evidence", "Decision output" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-03-strategy-and-competitive-analysis.html", "outboundSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-14-go-to-market-strategy", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-21-product-management-and-product-strategy" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-b-contrarian-business-perspectives", "appendix-c-public-record-decision-cases", "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-18-digital-business-models-and-platform-economics", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-04-financial-analysis-and-valuation", "slug": "chapter-04-financial-analysis-and-valuation", "kind": "chapter", "number": 4, "title": "Financial Analysis and Valuation", "part": "Part 1: Core MBA Foundations", "summary": "Financial statements, valuation, capital structure, ratios, unit economics, and investment decision tools.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "relatedSlugs": [ "chapter-15-fundraising-and-finance", "chapter-18-digital-business-models-and-platform-economics" ], "sourcePath": "src/part1-foundations/04-financial-analysis-valuation.md", "outputPath": "index.html#chapter-04-financial-analysis-and-valuation", "markdownPath": "markdown/chapter-04-financial-analysis-and-valuation.md", "wordCount": 8232, "checksum": "81699fbf211ed548a2590286be9b384ae38deb8e17ce48f9b1c47cfedcbcabf2", "sourceIds": [ "BB-C04-S13", "BB-C04-S14", "BB-C04-S17", "BB-C04-S19", "BB-C04-S18", "BB-C04-S20", "BB-C04-S21", "BB-C04-S22", "BB-C04-S23", "BB-C04-S06", "BB-C04-S02", "BB-C04-S03", "BB-C04-S04", "BB-C04-S05", "BB-C04-S07", "BB-C04-S08", "BB-C04-S09", "BB-C04-S15", "BB-C04-S16", "BB-C04-S10", "BB-C04-S11", "BB-C04-S12" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-04-financial-analysis-and-valuation-executive-summary" }, { "level": 3, "text": "Manager Outcomes", "id": "chapter-04-financial-analysis-and-valuation-manager-outcomes" }, { "level": 3, "text": "The Managerial Finance Spine", "id": "chapter-04-financial-analysis-and-valuation-the-managerial-finance-spine" }, { "level": 2, "text": "Financial Reporting and Accounting-Quality Foundation", "id": "chapter-04-financial-analysis-and-valuation-financial-reporting-and-accounting-quality-foundation" }, { "level": 3, "text": "Three-statement linkage", "id": "chapter-04-financial-analysis-and-valuation-three-statement-linkage" }, { "level": 3, "text": "Accrual, cash, and recognition", "id": "chapter-04-financial-analysis-and-valuation-accrual-cash-and-recognition" }, { "level": 3, "text": "Normalization and earnings quality", "id": "chapter-04-financial-analysis-and-valuation-normalization-and-earnings-quality" }, { "level": 3, "text": "Cost behavior, allocation, and decision relevance", "id": "chapter-04-financial-analysis-and-valuation-cost-behavior-allocation-and-decision-relevance" }, { "level": 2, "text": "Risk, Return, and Cost-of-Capital Estimation", "id": "chapter-04-financial-analysis-and-valuation-risk-return-and-cost-of-capital-estimation" }, { "level": 3, "text": "A transparent estimation workflow", "id": "chapter-04-financial-analysis-and-valuation-a-transparent-estimation-workflow" }, { "level": 3, "text": "Company, division, and project risk are not interchangeable", "id": "chapter-04-financial-analysis-and-valuation-company-division-and-project-risk-are-not-interchangeable" }, { "level": 3, "text": "Limitations and accountable use", "id": "chapter-04-financial-analysis-and-valuation-limitations-and-accountable-use" }, { "level": 3, "text": "Capital budgeting and financing policy", "id": "chapter-04-financial-analysis-and-valuation-capital-budgeting-and-financing-policy" }, { "level": 2, "text": "Troubleshooting Guide: Financial Analysis", "id": "chapter-04-financial-analysis-and-valuation-troubleshooting-guide-financial-analysis" }, { "level": 2, "text": "The Frameworks", "id": "chapter-04-financial-analysis-and-valuation-the-frameworks" }, { "level": 2, "text": "1. DCF (Discounted Cash Flow) Model", "id": "chapter-04-financial-analysis-and-valuation-1-dcf-discounted-cash-flow-model" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply" }, { "level": 3, "text": "Source Boundary", "id": "chapter-04-financial-analysis-and-valuation-source-boundary" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections" }, { "level": 2, "text": "2. LBO (Leveraged Buyout) Model", "id": "chapter-04-financial-analysis-and-valuation-2-lbo-leveraged-buyout-model" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections-2" }, { "level": 2, "text": "3. Financial Ratios & Modern Metrics", "id": "chapter-04-financial-analysis-and-valuation-3-financial-ratios-modern-metrics" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply-3" }, { "level": 3, "text": "Contrarian Thinking: The Tyranny of Gross Margin", "id": "chapter-04-financial-analysis-and-valuation-contrarian-thinking-the-tyranny-of-gross-margin" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections-3" }, { "level": 2, "text": "4. DuPont Analysis Tree", "id": "chapter-04-financial-analysis-and-valuation-4-dupont-analysis-tree" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply-4" }, { "level": 3, "text": "Contrarian Thinking: High ROE Can Be a Major Red Flag", "id": "chapter-04-financial-analysis-and-valuation-contrarian-thinking-high-roe-can-be-a-major-red-flag" }, { "level": 3, "text": "Source Boundary", "id": "chapter-04-financial-analysis-and-valuation-source-boundary-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections-4" }, { "level": 2, "text": "5. Working Capital Cycle Diagram", "id": "chapter-04-financial-analysis-and-valuation-5-working-capital-cycle-diagram" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply-5" }, { "level": 3, "text": "Source Boundary", "id": "chapter-04-financial-analysis-and-valuation-source-boundary-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections-5" }, { "level": 2, "text": "6. Cap Table Evolution Chart", "id": "chapter-04-financial-analysis-and-valuation-6-cap-table-evolution-chart" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections-6" }, { "level": 2, "text": "7. Unit Economics Calculator", "id": "chapter-04-financial-analysis-and-valuation-7-unit-economics-calculator" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections-7" }, { "level": 2, "text": "8. Break-Even Analysis", "id": "chapter-04-financial-analysis-and-valuation-8-break-even-analysis" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections-8" }, { "level": 2, "text": "9. Monte Carlo Simulation", "id": "chapter-04-financial-analysis-and-valuation-9-monte-carlo-simulation" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections-9" }, { "level": 2, "text": "10. Real Options Pricing", "id": "chapter-04-financial-analysis-and-valuation-10-real-options-pricing" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply-10" }, { "level": 3, "text": "Contrarian Thinking: The Value of Uncertainty", "id": "chapter-04-financial-analysis-and-valuation-contrarian-thinking-the-value-of-uncertainty" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections-10" }, { "level": 2, "text": "11. Comparable Companies, Precedent Transactions, and a Football Field", "id": "chapter-04-financial-analysis-and-valuation-11-comparable-companies-precedent-transactions-and-a-football-field" }, { "level": 3, "text": "Overview", "id": "chapter-04-financial-analysis-and-valuation-overview-11" }, { "level": 3, "text": "How to Apply", "id": "chapter-04-financial-analysis-and-valuation-how-to-apply-11" }, { "level": 3, "text": "Comparable-company workflow", "id": "chapter-04-financial-analysis-and-valuation-comparable-company-workflow" }, { "level": 3, "text": "Precedent-transaction workflow", "id": "chapter-04-financial-analysis-and-valuation-precedent-transaction-workflow" }, { "level": 3, "text": "Constructed range exhibit", "id": "chapter-04-financial-analysis-and-valuation-constructed-range-exhibit" }, { "level": 3, "text": "So What for Managers", "id": "chapter-04-financial-analysis-and-valuation-so-what-for-managers-11" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-04-financial-analysis-and-valuation-limits-and-critiques-11" }, { "level": 3, "text": "Connections", "id": "chapter-04-financial-analysis-and-valuation-connections-11" }, { "level": 2, "text": "Why This Matters: Mental Models & Valuation Wisdom", "id": "chapter-04-financial-analysis-and-valuation-why-this-matters-mental-models-valuation-wisdom" }, { "level": 3, "text": "Mental Model 1: The Time Value of Money (Why DCF Works)", "id": "chapter-04-financial-analysis-and-valuation-mental-model-1-the-time-value-of-money-why-dcf-works" }, { "level": 3, "text": "Mental Model 2: Market Evidence vs. Intrinsic Value (Why Comps Can Help)", "id": "chapter-04-financial-analysis-and-valuation-mental-model-2-market-evidence-vs-intrinsic-value-why-comps-can-help" }, { "level": 3, "text": "Mental Model 3: Optionality and Uncertainty (Why Real Options Matter)", "id": "chapter-04-financial-analysis-and-valuation-mental-model-3-optionality-and-uncertainty-why-real-options-matter" }, { "level": 3, "text": "Mental Model 4: Strategic Value vs. Standalone Value", "id": "chapter-04-financial-analysis-and-valuation-mental-model-4-strategic-value-vs-standalone-value" }, { "level": 2, "text": "Case Studies: When Financial Models Failed Spectacularly", "id": "chapter-04-financial-analysis-and-valuation-case-studies-when-financial-models-failed-spectacularly" }, { "level": 3, "text": "Failure Example 1: WeWork—When Financial Models Hid Operational Reality", "id": "chapter-04-financial-analysis-and-valuation-failure-example-1-wework-when-financial-models-hid-operational-reality" }, { "level": 3, "text": "Failure Example 2: 2008 Mortgage Crisis—When Comparables Failed", "id": "chapter-04-financial-analysis-and-valuation-failure-example-2-2008-mortgage-crisis-when-comparables-failed" }, { "level": 3, "text": "Failure Example 3: Constructed Growth-without-Economics Scenario", "id": "chapter-04-financial-analysis-and-valuation-failure-example-3-constructed-growth-without-economics-scenario" }, { "level": 2, "text": "Applied Exercise: Audit an Investment Recommendation", "id": "chapter-04-financial-analysis-and-valuation-applied-exercise-audit-an-investment-recommendation" }, { "level": 3, "text": "Selective Connections", "id": "chapter-04-financial-analysis-and-valuation-selective-connections" } ], "figures": [ { "id": "chapter-04-financial-analysis-and-valuation-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S17", "BB-C04-S18", "BB-C04-S19" ], "provenanceStatus": "constructed", "checksum": "78c394d58486df55c7ed48742028cf176517fb8182813dd7948640ed02b52536" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-2", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S23" ], "provenanceStatus": "constructed", "checksum": "1d0f346d0fb594fc363773c93f9db44396609c25b3ac1530d5e9494df78ca032" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S13" ], "provenanceStatus": "constructed", "checksum": "4a161065b44bbcc3b5453060947538e4faf30bec4e96572bab2b58d27b8b059d" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-4", "type": "mermaid", "caption": "Figure 4.4. DuPont decomposition of return on equity. The branches are multiplicative accounting components, not a causal tree. [BB-C04-S06]", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S06" ], "provenanceStatus": "constructed", "checksum": "a6a81d9a1973acc7961b7666f2eff1226716d2a72d7db6afab391ee9b01ca673" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-5", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S07" ], "provenanceStatus": "source-linked", "checksum": "c31487e8857203360925d836f0aaba1e6d95a6d2fd3863edf595bd21334606bc" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-6", "type": "svg", "caption": "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].", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S14" ], "provenanceStatus": "constructed", "checksum": "8383750ff45d64f0c35efbd050df7da9d0ed36a64b8ee34132da413cf1b08f74" } ], "tables": [ { "id": "chapter-04-financial-analysis-and-valuation-table-1", "caption": "Table 4.1. Earnings-quality question matrix. This author-created diagnostic organizes evidence and its limits; it is not an accounting-quality score.", "headers": [ "Quality question", "Evidence to inspect", "What the evidence does not prove" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-04-financial-analysis-and-valuation-table-2", "caption": "Table 4.2. Cost-of-capital input control record. The rows identify documentation and challenge questions, not a universal estimation recipe.", "headers": [ "Input", "Minimum documentation", "Challenge question" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-04-financial-analysis-and-valuation-table-3", "caption": "Table 4.3. Constructed valuation-range exhibit. The values are illustrative and assumption-dependent; they are not current market evidence or a recommendation.", "headers": [ "Method", "Low equity value", "High equity value", "Key constructed assumption" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-04-financial-analysis-and-valuation.html", "outboundSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-14-go-to-market-strategy", "chapter-15-fundraising-and-finance", "chapter-18-digital-business-models-and-platform-economics", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy", "chapter-15-fundraising-and-finance", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-05-marketing-and-customer-analytics", "slug": "chapter-05-marketing-and-customer-analytics", "kind": "chapter", "number": 5, "title": "Marketing and Customer Analytics", "part": "Part 1: Core MBA Foundations", "summary": "Segmentation, customer journeys, CLV/CAC, pricing, attribution, NPS, and marketing measurement.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "relatedSlugs": [ "chapter-14-go-to-market-strategy", "chapter-21-product-management-and-product-strategy", "chapter-18-digital-business-models-and-platform-economics" ], "sourcePath": "src/part1-foundations/05-marketing-customer-analytics.md", "outputPath": "index.html#chapter-05-marketing-and-customer-analytics", "markdownPath": "markdown/chapter-05-marketing-and-customer-analytics.md", "wordCount": 6612, "checksum": "1bf1bb555f64ad895a2fa1e7e61d7729122f62d41f9abfe98459ebd4bcdb8a2b", "sourceIds": [ "BB-C05-S07", "BB-C05-S11", "BB-C05-S12", "BB-C05-S13", "BB-C05-S14", "BB-C05-S04", "BB-C05-S15", "BB-C05-S16", "BB-C05-S08", "BB-C05-S09", "BB-C05-S10", "BB-C05-S02", "BB-C05-S03", "BB-C05-S17", "BB-C05-S18", "BB-C05-S19", "BB-C05-S20", "BB-C05-S22", "BB-C05-S23", "BB-C05-S24" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-05-marketing-and-customer-analytics-executive-summary" }, { "level": 3, "text": "Authorial and Constructed-Material Boundary", "id": "chapter-05-marketing-and-customer-analytics-authorial-and-constructed-material-boundary" }, { "level": 3, "text": "The Marketing Decision Spine", "id": "chapter-05-marketing-and-customer-analytics-the-marketing-decision-spine" }, { "level": 2, "text": "The Frameworks", "id": "chapter-05-marketing-and-customer-analytics-the-frameworks" }, { "level": 2, "text": "1. Customer Journey Mapping", "id": "chapter-05-marketing-and-customer-analytics-1-customer-journey-mapping" }, { "level": 3, "text": "Overview", "id": "chapter-05-marketing-and-customer-analytics-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-05-marketing-and-customer-analytics-how-to-apply" }, { "level": 3, "text": "So What for Managers", "id": "chapter-05-marketing-and-customer-analytics-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-05-marketing-and-customer-analytics-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-05-marketing-and-customer-analytics-connections" }, { "level": 2, "text": "2. Jobs-to-be-Done (JTBD)", "id": "chapter-05-marketing-and-customer-analytics-2-jobs-to-be-done-jtbd" }, { "level": 3, "text": "Overview", "id": "chapter-05-marketing-and-customer-analytics-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-05-marketing-and-customer-analytics-how-to-apply-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-05-marketing-and-customer-analytics-connections-2" }, { "level": 2, "text": "3. RFM Segmentation", "id": "chapter-05-marketing-and-customer-analytics-3-rfm-segmentation" }, { "level": 3, "text": "Overview", "id": "chapter-05-marketing-and-customer-analytics-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-05-marketing-and-customer-analytics-how-to-apply-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-05-marketing-and-customer-analytics-connections-3" }, { "level": 2, "text": "4. CLV/CAC Analysis", "id": "chapter-05-marketing-and-customer-analytics-4-clv-cac-analysis" }, { "level": 3, "text": "Overview", "id": "chapter-05-marketing-and-customer-analytics-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-05-marketing-and-customer-analytics-how-to-apply-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-05-marketing-and-customer-analytics-connections-4" }, { "level": 2, "text": "5. Marketing Attribution Models", "id": "chapter-05-marketing-and-customer-analytics-5-marketing-attribution-models" }, { "level": 3, "text": "Overview", "id": "chapter-05-marketing-and-customer-analytics-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-05-marketing-and-customer-analytics-how-to-apply-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-05-marketing-and-customer-analytics-connections-5" }, { "level": 2, "text": "6. Pricing Strategy & Models", "id": "chapter-05-marketing-and-customer-analytics-6-pricing-strategy-models" }, { "level": 3, "text": "Overview", "id": "chapter-05-marketing-and-customer-analytics-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-05-marketing-and-customer-analytics-how-to-apply-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-05-marketing-and-customer-analytics-connections-6" }, { "level": 2, "text": "7. Brand Architecture", "id": "chapter-05-marketing-and-customer-analytics-7-brand-architecture" }, { "level": 3, "text": "Overview", "id": "chapter-05-marketing-and-customer-analytics-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-05-marketing-and-customer-analytics-how-to-apply-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-05-marketing-and-customer-analytics-connections-7" }, { "level": 2, "text": "8. A/B Testing", "id": "chapter-05-marketing-and-customer-analytics-8-a-b-testing" }, { "level": 3, "text": "Overview", "id": "chapter-05-marketing-and-customer-analytics-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-05-marketing-and-customer-analytics-how-to-apply-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-05-marketing-and-customer-analytics-connections-8" }, { "level": 2, "text": "9. NPS Driver Analysis", "id": "chapter-05-marketing-and-customer-analytics-9-nps-driver-analysis" }, { "level": 3, "text": "Overview", "id": "chapter-05-marketing-and-customer-analytics-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-05-marketing-and-customer-analytics-how-to-apply-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-05-marketing-and-customer-analytics-connections-9" }, { "level": 2, "text": "10. Cohort Analysis", "id": "chapter-05-marketing-and-customer-analytics-10-cohort-analysis" }, { "level": 3, "text": "Overview", "id": "chapter-05-marketing-and-customer-analytics-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-05-marketing-and-customer-analytics-how-to-apply-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-05-marketing-and-customer-analytics-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-05-marketing-and-customer-analytics-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-05-marketing-and-customer-analytics-connections-10" }, { "level": 2, "text": "Marketing Measurement Triangulation: MMM, Experiments, Attribution, and Finance", "id": "chapter-05-marketing-and-customer-analytics-marketing-measurement-triangulation-mmm-experiments-attribution-and-finance" }, { "level": 3, "text": "What each method can and cannot decide", "id": "chapter-05-marketing-and-customer-analytics-what-each-method-can-and-cannot-decide" }, { "level": 3, "text": "A decision-grade triangulation protocol", "id": "chapter-05-marketing-and-customer-analytics-a-decision-grade-triangulation-protocol" }, { "level": 3, "text": "Brand equity as an evidence chain", "id": "chapter-05-marketing-and-customer-analytics-brand-equity-as-an-evidence-chain" }, { "level": 2, "text": "Why This Matters: Mental Models & Marketing Wisdom", "id": "chapter-05-marketing-and-customer-analytics-why-this-matters-mental-models-marketing-wisdom" }, { "level": 3, "text": "Mental Model 1: The \"Job\" vs. The \"Persona\"", "id": "chapter-05-marketing-and-customer-analytics-mental-model-1-the-job-vs-the-persona" }, { "level": 3, "text": "Mental Model 2: The Leaky Bucket", "id": "chapter-05-marketing-and-customer-analytics-mental-model-2-the-leaky-bucket" }, { "level": 3, "text": "Mental Model 3: Correlation vs. Causation", "id": "chapter-05-marketing-and-customer-analytics-mental-model-3-correlation-vs-causation" }, { "level": 2, "text": "Worked Examples: Marketing & Analytics in Action", "id": "chapter-05-marketing-and-customer-analytics-worked-examples-marketing-analytics-in-action" }, { "level": 3, "text": "Worked Example 1: Team Collaboration and the \"Aha!\" Moment", "id": "chapter-05-marketing-and-customer-analytics-worked-example-1-team-collaboration-and-the-aha-moment" }, { "level": 3, "text": "Worked Example 2: File Sync and the Two-Sided Referral", "id": "chapter-05-marketing-and-customer-analytics-worked-example-2-file-sync-and-the-two-sided-referral" }, { "level": 3, "text": "Worked Example 3: Streaming Subscription and the NPS Trap", "id": "chapter-05-marketing-and-customer-analytics-worked-example-3-streaming-subscription-and-the-nps-trap" }, { "level": 2, "text": "Applied Exercise: Build a Decision-Grade Marketing Plan", "id": "chapter-05-marketing-and-customer-analytics-applied-exercise-build-a-decision-grade-marketing-plan" }, { "level": 3, "text": "Selective Connections", "id": "chapter-05-marketing-and-customer-analytics-selective-connections" } ], "figures": [ { "id": "chapter-05-marketing-and-customer-analytics-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C05-S11" ], "provenanceStatus": "constructed", "checksum": "0f5e0ec1b0ef1a37dd2fd28e8fb2b4ca03ef7f7b5170ecc4e441e57123445a2b" }, { "id": "chapter-05-marketing-and-customer-analytics-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C05-S08" ], "provenanceStatus": "constructed", "checksum": "efac505357a9d253aca5b05f9d9a697df1c041ac02c2c7b1ba142619e83fbd5e" }, { "id": "chapter-05-marketing-and-customer-analytics-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C05-S10" ], "provenanceStatus": "source-linked", "checksum": "1ef1ee78f9c5cc27586300a2432d43586fcc258b28321fd1f49532db4aa6a082" }, { "id": "chapter-05-marketing-and-customer-analytics-figure-4", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C05-S18", "BB-C05-S19", "BB-C05-S20", "BB-C05-S15" ], "provenanceStatus": "constructed", "checksum": "0dd59bb4885f47c5e3baf2171f5058c91d31f74ed25cbb091e4ae7b36cb9394f" }, { "id": "chapter-05-marketing-and-customer-analytics-figure-5", "type": "mermaid", "caption": "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]", "textEquivalent": "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]", "sourceIds": [ "BB-C05-S22", "BB-C05-S23", "BB-C05-S24" ], "provenanceStatus": "constructed", "checksum": "41e0a451fcb19cd1476ea60bab587c2f0a55823d6b248c23f868b3c57e520f45" } ], "tables": [ { "id": "chapter-05-marketing-and-customer-analytics-table-1", "caption": "Table 1. Evidence stream / Strongest decision use / Required controls", "headers": [ "Evidence stream", "Strongest decision use", "Required controls", "Important limit" ], "sourceIds": [ "BB-C05-S15", "BB-C05-S18", "BB-C05-S19", "BB-C05-S20" ], "provenanceStatus": "constructed", "rowCount": 4 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-05-marketing-and-customer-analytics.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-14-go-to-market-strategy", "chapter-18-digital-business-models-and-platform-economics", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-06-operations-and-supply-chain", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy", "chapter-18-digital-business-models-and-platform-economics", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-06-operations-and-supply-chain", "slug": "chapter-06-operations-and-supply-chain", "kind": "chapter", "number": 6, "title": "Operations and Supply Chain", "part": "Part 1: Core MBA Foundations", "summary": "Process improvement, lean, Six Sigma, bottlenecks, inventory, capacity, quality, and supply chain risk.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "relatedSlugs": [ "chapter-09-problem-structuring", "chapter-11-project-management-and-pmp-frameworks", "chapter-19-cybersecurity-and-risk-management-for-managers" ], "sourcePath": "src/part1-foundations/06-operations-supply-chain.md", "outputPath": "index.html#chapter-06-operations-and-supply-chain", "markdownPath": "markdown/chapter-06-operations-and-supply-chain.md", "wordCount": 12816, "checksum": "5e903cc98897c83ff612b1c6e2d7c22bb47c71320f2fbd90a7c91b4a957a7545", "sourceIds": [ "BB-C06-S07", "BB-C06-S08", "BB-C06-S03", "BB-C06-S04", "BB-C06-S01", "BB-C06-S10", "BB-C06-S11", "BB-C06-S02", "BB-C06-S05", "BB-C06-S06", "BB-C06-S09", "BB-C06-S12", "BB-C06-S15", "BB-C06-S16", "BB-C06-S13", "BB-C06-S14" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-06-operations-and-supply-chain-executive-summary" }, { "level": 3, "text": "Manager decision outcomes", "id": "chapter-06-operations-and-supply-chain-manager-decision-outcomes" }, { "level": 3, "text": "Core Quantitative Operations Spine", "id": "chapter-06-operations-and-supply-chain-core-quantitative-operations-spine" }, { "level": 2, "text": "Troubleshooting Guide: Operations & Supply Chain", "id": "chapter-06-operations-and-supply-chain-troubleshooting-guide-operations-supply-chain" }, { "level": 2, "text": "The Frameworks", "id": "chapter-06-operations-and-supply-chain-the-frameworks" }, { "level": 2, "text": "1. Process Flow Diagrams", "id": "chapter-06-operations-and-supply-chain-1-process-flow-diagrams" }, { "level": 3, "text": "Overview", "id": "chapter-06-operations-and-supply-chain-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-06-operations-and-supply-chain-how-to-apply" }, { "level": 3, "text": "Example: E-Commerce Order Fulfillment Process", "id": "chapter-06-operations-and-supply-chain-example-e-commerce-order-fulfillment-process" }, { "level": 3, "text": "Operator's Checklist: Creating Effective Process Maps", "id": "chapter-06-operations-and-supply-chain-operator-s-checklist-creating-effective-process-maps" }, { "level": 3, "text": "Constructed Classroom Exercise: Paper-Airplane Flow", "id": "chapter-06-operations-and-supply-chain-constructed-classroom-exercise-paper-airplane-flow" }, { "level": 3, "text": "Contrarian Thinking: When NOT to Map", "id": "chapter-06-operations-and-supply-chain-contrarian-thinking-when-not-to-map" }, { "level": 3, "text": "So What for Managers", "id": "chapter-06-operations-and-supply-chain-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-06-operations-and-supply-chain-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-06-operations-and-supply-chain-connections" }, { "level": 2, "text": "2. Lean & The 8 Wastes", "id": "chapter-06-operations-and-supply-chain-2-lean-the-8-wastes" }, { "level": 3, "text": "Overview", "id": "chapter-06-operations-and-supply-chain-overview-2" }, { "level": 3, "text": "Visual: The 8 Wastes (TIMWOODS)", "id": "chapter-06-operations-and-supply-chain-visual-the-8-wastes-timwoods" }, { "level": 3, "text": "How to Apply", "id": "chapter-06-operations-and-supply-chain-how-to-apply-2" }, { "level": 3, "text": "Sourced Practice Example: Virginia Mason Health System", "id": "chapter-06-operations-and-supply-chain-sourced-practice-example-virginia-mason-health-system" }, { "level": 3, "text": "Operator's Practical Tip: The \"5 Whys\" for Waste", "id": "chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-5-whys-for-waste" }, { "level": 3, "text": "Contrarian Thinking: Some \"Waste\" is Strategic", "id": "chapter-06-operations-and-supply-chain-contrarian-thinking-some-waste-is-strategic" }, { "level": 3, "text": "So What for Managers", "id": "chapter-06-operations-and-supply-chain-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-06-operations-and-supply-chain-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-06-operations-and-supply-chain-connections-2" }, { "level": 2, "text": "3. Six Sigma (DMAIC Cycle)", "id": "chapter-06-operations-and-supply-chain-3-six-sigma-dmaic-cycle" }, { "level": 3, "text": "Overview", "id": "chapter-06-operations-and-supply-chain-overview-3" }, { "level": 3, "text": "Visual: The DMAIC Cycle", "id": "chapter-06-operations-and-supply-chain-visual-the-dmaic-cycle" }, { "level": 3, "text": "How to Apply", "id": "chapter-06-operations-and-supply-chain-how-to-apply-3" }, { "level": 3, "text": "Historical Context and Evidence Boundary", "id": "chapter-06-operations-and-supply-chain-historical-context-and-evidence-boundary" }, { "level": 3, "text": "Operator's Practical Tip: Define Before Analyzing", "id": "chapter-06-operations-and-supply-chain-operator-s-practical-tip-define-before-analyzing" }, { "level": 3, "text": "Sigma and DPMO Interpretation Boundary", "id": "chapter-06-operations-and-supply-chain-sigma-and-dpmo-interpretation-boundary" }, { "level": 3, "text": "Contrarian Thinking: Six Sigma Can Kill Innovation", "id": "chapter-06-operations-and-supply-chain-contrarian-thinking-six-sigma-can-kill-innovation" }, { "level": 3, "text": "So What for Managers", "id": "chapter-06-operations-and-supply-chain-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-06-operations-and-supply-chain-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-06-operations-and-supply-chain-connections-3" }, { "level": 2, "text": "4. Theory of Constraints (TOC)", "id": "chapter-06-operations-and-supply-chain-4-theory-of-constraints-toc" }, { "level": 3, "text": "Overview", "id": "chapter-06-operations-and-supply-chain-overview-4" }, { "level": 3, "text": "Visual: Identifying the Bottleneck", "id": "chapter-06-operations-and-supply-chain-visual-identifying-the-bottleneck" }, { "level": 3, "text": "How to Apply", "id": "chapter-06-operations-and-supply-chain-how-to-apply-4" }, { "level": 3, "text": "Constructed Semiconductor Constraint Example", "id": "chapter-06-operations-and-supply-chain-constructed-semiconductor-constraint-example" }, { "level": 3, "text": "Operator's Critical Insight: Optimize the System, Not Local Busy Time", "id": "chapter-06-operations-and-supply-chain-operator-s-critical-insight-optimize-the-system-not-local-busy-time" }, { "level": 3, "text": "Visual: Drum-Buffer-Rope System", "id": "chapter-06-operations-and-supply-chain-visual-drum-buffer-rope-system" }, { "level": 3, "text": "Contrarian Thinking: Efficiency is a Trap", "id": "chapter-06-operations-and-supply-chain-contrarian-thinking-efficiency-is-a-trap" }, { "level": 3, "text": "So What for Managers", "id": "chapter-06-operations-and-supply-chain-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-06-operations-and-supply-chain-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-06-operations-and-supply-chain-connections-4" }, { "level": 2, "text": "5. Inventory Management Models", "id": "chapter-06-operations-and-supply-chain-5-inventory-management-models" }, { "level": 3, "text": "Overview", "id": "chapter-06-operations-and-supply-chain-overview-5" }, { "level": 3, "text": "Visual: EOQ vs. JIT Comparison", "id": "chapter-06-operations-and-supply-chain-visual-eoq-vs-jit-comparison" }, { "level": 3, "text": "How to Apply", "id": "chapter-06-operations-and-supply-chain-how-to-apply-5" }, { "level": 3, "text": "Toyota Production System Evidence Boundary", "id": "chapter-06-operations-and-supply-chain-toyota-production-system-evidence-boundary" }, { "level": 3, "text": "The Hybrid Approach: Best of Both Worlds", "id": "chapter-06-operations-and-supply-chain-the-hybrid-approach-best-of-both-worlds" }, { "level": 3, "text": "Operator's Decision Matrix", "id": "chapter-06-operations-and-supply-chain-operator-s-decision-matrix" }, { "level": 3, "text": "Resilience Boundary", "id": "chapter-06-operations-and-supply-chain-resilience-boundary" }, { "level": 3, "text": "So What for Managers", "id": "chapter-06-operations-and-supply-chain-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-06-operations-and-supply-chain-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-06-operations-and-supply-chain-connections-5" }, { "level": 2, "text": "6. Supply Chain Risk Matrix", "id": "chapter-06-operations-and-supply-chain-6-supply-chain-risk-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-06-operations-and-supply-chain-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-06-operations-and-supply-chain-how-to-apply-6" }, { "level": 3, "text": "Constructed Electronics-Supply Scenario", "id": "chapter-06-operations-and-supply-chain-constructed-electronics-supply-scenario" }, { "level": 3, "text": "Network Design and Resilience Screen", "id": "chapter-06-operations-and-supply-chain-network-design-and-resilience-screen" }, { "level": 3, "text": "Operator's Practical Tip: The \"Cone of Uncertainty\"", "id": "chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-cone-of-uncertainty" }, { "level": 3, "text": "Contrarian Thinking: Resilience Costs Money (But It's Worth It)", "id": "chapter-06-operations-and-supply-chain-contrarian-thinking-resilience-costs-money-but-it-s-worth-it" }, { "level": 3, "text": "So What for Managers", "id": "chapter-06-operations-and-supply-chain-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-06-operations-and-supply-chain-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-06-operations-and-supply-chain-connections-6" }, { "level": 2, "text": "7. Capacity Planning Model", "id": "chapter-06-operations-and-supply-chain-7-capacity-planning-model" }, { "level": 3, "text": "Overview", "id": "chapter-06-operations-and-supply-chain-overview-7" }, { "level": 3, "text": "Visual: Capacity Planning Strategies", "id": "chapter-06-operations-and-supply-chain-visual-capacity-planning-strategies" }, { "level": 3, "text": "How to Apply", "id": "chapter-06-operations-and-supply-chain-how-to-apply-7" }, { "level": 3, "text": "Constructed Capacity-Expansion Case", "id": "chapter-06-operations-and-supply-chain-constructed-capacity-expansion-case" }, { "level": 3, "text": "Operator's Practical Tip: The Capacity Buffer Rule", "id": "chapter-06-operations-and-supply-chain-operator-s-practical-tip-the-capacity-buffer-rule" }, { "level": 3, "text": "So What for Managers", "id": "chapter-06-operations-and-supply-chain-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-06-operations-and-supply-chain-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-06-operations-and-supply-chain-connections-7" }, { "level": 2, "text": "8. Statistical Process Control (SPC) Charts", "id": "chapter-06-operations-and-supply-chain-8-statistical-process-control-spc-charts" }, { "level": 3, "text": "Overview", "id": "chapter-06-operations-and-supply-chain-overview-8" }, { "level": 3, "text": "Visual: SPC Control Chart (In Control vs. Out of Control)", "id": "chapter-06-operations-and-supply-chain-visual-spc-control-chart-in-control-vs-out-of-control" }, { "level": 3, "text": "How to Apply", "id": "chapter-06-operations-and-supply-chain-how-to-apply-8" }, { "level": 3, "text": "Measurement and Capability Check", "id": "chapter-06-operations-and-supply-chain-measurement-and-capability-check" }, { "level": 3, "text": "Constructed SPC Investigation", "id": "chapter-06-operations-and-supply-chain-constructed-spc-investigation" }, { "level": 3, "text": "Operator's Critical Mistake: \"Tampering\"", "id": "chapter-06-operations-and-supply-chain-operator-s-critical-mistake-tampering" }, { "level": 3, "text": "The Four Types of SPC Charts", "id": "chapter-06-operations-and-supply-chain-the-four-types-of-spc-charts" }, { "level": 3, "text": "Contrarian Thinking: SPC Can't Fix a Bad Process", "id": "chapter-06-operations-and-supply-chain-contrarian-thinking-spc-can-t-fix-a-bad-process" }, { "level": 3, "text": "So What for Managers", "id": "chapter-06-operations-and-supply-chain-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-06-operations-and-supply-chain-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-06-operations-and-supply-chain-connections-8" }, { "level": 2, "text": "9. Value Stream Mapping", "id": "chapter-06-operations-and-supply-chain-9-value-stream-mapping" }, { "level": 3, "text": "Overview", "id": "chapter-06-operations-and-supply-chain-overview-9" }, { "level": 3, "text": "Visual: Value Stream Map Example", "id": "chapter-06-operations-and-supply-chain-visual-value-stream-map-example" }, { "level": 3, "text": "How to Apply", "id": "chapter-06-operations-and-supply-chain-how-to-apply-9" }, { "level": 3, "text": "Sourced Practice Context: Toyota's Process Logic", "id": "chapter-06-operations-and-supply-chain-sourced-practice-context-toyota-s-process-logic" }, { "level": 3, "text": "Operator's Critical Insight: \"Lead Time is the New Currency\"", "id": "chapter-06-operations-and-supply-chain-operator-s-critical-insight-lead-time-is-the-new-currency" }, { "level": 3, "text": "So What for Managers", "id": "chapter-06-operations-and-supply-chain-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-06-operations-and-supply-chain-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-06-operations-and-supply-chain-connections-9" }, { "level": 2, "text": "10. Digital Twin Architecture", "id": "chapter-06-operations-and-supply-chain-10-digital-twin-architecture" }, { "level": 3, "text": "Overview", "id": "chapter-06-operations-and-supply-chain-overview-10" }, { "level": 3, "text": "Visual: Digital Twin Architecture", "id": "chapter-06-operations-and-supply-chain-visual-digital-twin-architecture" }, { "level": 3, "text": "How to Apply", "id": "chapter-06-operations-and-supply-chain-how-to-apply-10" }, { "level": 3, "text": "Constructed Condition-Monitoring Example", "id": "chapter-06-operations-and-supply-chain-constructed-condition-monitoring-example" }, { "level": 3, "text": "Constructed Scope Taxonomy", "id": "chapter-06-operations-and-supply-chain-constructed-scope-taxonomy" }, { "level": 3, "text": "Operator's Practical Tip: Start Small", "id": "chapter-06-operations-and-supply-chain-operator-s-practical-tip-start-small" }, { "level": 3, "text": "Contrarian Thinking: Don't Twin Everything", "id": "chapter-06-operations-and-supply-chain-contrarian-thinking-don-t-twin-everything" }, { "level": 3, "text": "Real-World Implementation Challenges", "id": "chapter-06-operations-and-supply-chain-real-world-implementation-challenges" }, { "level": 3, "text": "So What for Managers", "id": "chapter-06-operations-and-supply-chain-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-06-operations-and-supply-chain-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-06-operations-and-supply-chain-connections-10" }, { "level": 2, "text": "Forecasting and S&OP: Converting Uncertainty into an Executable Plan", "id": "chapter-06-operations-and-supply-chain-forecasting-and-s-op-converting-uncertainty-into-an-executable-plan" }, { "level": 3, "text": "Forecast for the decision and horizon", "id": "chapter-06-operations-and-supply-chain-forecast-for-the-decision-and-horizon" }, { "level": 3, "text": "The closed S&OP loop", "id": "chapter-06-operations-and-supply-chain-the-closed-s-op-loop" }, { "level": 3, "text": "Decision rights and minimum outputs", "id": "chapter-06-operations-and-supply-chain-decision-rights-and-minimum-outputs" }, { "level": 3, "text": "Constructed forecast-error and constrained-plan exercise", "id": "chapter-06-operations-and-supply-chain-constructed-forecast-error-and-constrained-plan-exercise" }, { "level": 2, "text": "Why This Matters: Mental Models & Operational Wisdom", "id": "chapter-06-operations-and-supply-chain-why-this-matters-mental-models-operational-wisdom" }, { "level": 3, "text": "Mental Model 1: Systems Have Constraints (TOC)", "id": "chapter-06-operations-and-supply-chain-mental-model-1-systems-have-constraints-toc" }, { "level": 3, "text": "Mental Model 2: Waste is Everywhere (Lean)", "id": "chapter-06-operations-and-supply-chain-mental-model-2-waste-is-everywhere-lean" }, { "level": 3, "text": "Mental Model 3: Interpret Variation Before Acting (Six Sigma)", "id": "chapter-06-operations-and-supply-chain-mental-model-3-interpret-variation-before-acting-six-sigma" }, { "level": 2, "text": "Constructed Cases: Operations in Action", "id": "chapter-06-operations-and-supply-chain-constructed-cases-operations-in-action" }, { "level": 3, "text": "Example 1: Responsive Apparel Network", "id": "chapter-06-operations-and-supply-chain-example-1-responsive-apparel-network" }, { "level": 3, "text": "Example 2: Marketplace Fulfillment Loop", "id": "chapter-06-operations-and-supply-chain-example-2-marketplace-fulfillment-loop" }, { "level": 2, "text": "Applied Exercise: Diagnose and Improve an Operating System", "id": "chapter-06-operations-and-supply-chain-applied-exercise-diagnose-and-improve-an-operating-system" }, { "level": 3, "text": "Selective Connections", "id": "chapter-06-operations-and-supply-chain-selective-connections" } ], "figures": [ { "id": "chapter-06-operations-and-supply-chain-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S11" ], "provenanceStatus": "constructed", "checksum": "64c532e4640a433fb91531b774816e494d88f257cff4311acb3c46e0c159b7d2" }, { "id": "chapter-06-operations-and-supply-chain-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S11" ], "provenanceStatus": "constructed", "checksum": "7dd703e389b15ba022eab14619939f5570a83ca2c502eb8ec52c2b06dfc44bb9" }, { "id": "chapter-06-operations-and-supply-chain-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S06" ], "provenanceStatus": "constructed", "checksum": "32411847a1f3f18c299b82e306bed8e304d723a8f8f000b72e402d9ef64aad7a" }, { "id": "chapter-06-operations-and-supply-chain-figure-4", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S03", "BB-C06-S04" ], "provenanceStatus": "constructed", "checksum": "e3d77c30d5d9f81a0dcd8194f94a70ef32fda308b53ef4e479f1550264e18bb2" }, { "id": "chapter-06-operations-and-supply-chain-figure-5", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S03", "BB-C06-S04" ], "provenanceStatus": "constructed", "checksum": "c691bdad9b6592d8cde63b383439ae72acdfb1fabad437c4283a0e3dcac62bff" }, { "id": "chapter-06-operations-and-supply-chain-figure-6", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S03", "BB-C06-S04" ], "provenanceStatus": "constructed", "checksum": "75efe5aad7b45d7bc5a1bfc7cfef306870ac04133399240a6169a78f3dc05e57" }, { "id": "chapter-06-operations-and-supply-chain-figure-7", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S01", "BB-C06-S07" ], "provenanceStatus": "constructed", "checksum": "49b2e777969bce4ba9082e314997871f9b0d80967e62bd84d2999d32efb33f44" }, { "id": "chapter-06-operations-and-supply-chain-figure-8", "type": "mermaid", "caption": "Figure 6.8. Constructed supply-chain risk triage matrix. The anonymous positions are discussion prompts, not measured probabilities, expected losses, or automatic action rules.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "05946a57603fbc2c4cceffad6ffebfd5e384a206d7729465b5a3a4790c6898e7" }, { "id": "chapter-06-operations-and-supply-chain-figure-9", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S08" ], "provenanceStatus": "constructed", "checksum": "9f926373d61eec354ae0600df8f27edb117dfeadb5b5244b83443acf0ad299f2" }, { "id": "chapter-06-operations-and-supply-chain-figure-10", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S09" ], "provenanceStatus": "constructed", "checksum": "b819e891b4be3ac818654d78620ed2b8170d4b2c0a6c9d610e72db6fc07c33c6" }, { "id": "chapter-06-operations-and-supply-chain-figure-11", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S10" ], "provenanceStatus": "constructed", "checksum": "78ea13f4a62e7f94c3b2d60b1ccc612e12b5a4ee346bea7493d3769466ea4d62" }, { "id": "chapter-06-operations-and-supply-chain-figure-12", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S12" ], "provenanceStatus": "constructed", "checksum": "50c80610176fdfb511e7e2633e3194ee8c9965829bb200a228a16306c8d46377" }, { "id": "chapter-06-operations-and-supply-chain-figure-13", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S12" ], "provenanceStatus": "constructed", "checksum": "3d8eadcbb18a66ea4350243ba6bb1781f75a5e8db56f2798e6f9d4fb83e1cf75" }, { "id": "chapter-06-operations-and-supply-chain-figure-14", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S15", "BB-C06-S16" ], "provenanceStatus": "constructed", "checksum": "0554ea829b2edda0f1fcd39adae4bbfa2808b0166298c65b5e087b72d1ba9ca2" } ], "tables": [ { "id": "chapter-06-operations-and-supply-chain-table-1", "caption": "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]", "headers": [ "Category", "Look for", "Evidence before changing the work" ], "sourceIds": [ "BB-C06-S01", "BB-C06-S02" ], "provenanceStatus": "source-linked", "rowCount": 8 }, { "id": "chapter-06-operations-and-supply-chain-table-2", "caption": "Table 6.2. Constructed candidate hybrid inventory policies. The item descriptions suggest models to evaluate, not automatic assignments.", "headers": [ "Item or flow condition", "Candidate policy", "Quantify before selecting" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-06-operations-and-supply-chain-table-3", "caption": "Table 6.3. Constructed inventory-policy decision matrix. The candidate policies are prompts for scenario analysis, not automatic assignments.", "headers": [ "Demand Variability", "Supply Reliability", "Candidate Strategy" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-06-operations-and-supply-chain-table-4", "caption": "Table 6.4. Constructed supply-chain risk mitigation options for scenario review. The options require cost, service, recovery, safety, supplier, and residual-risk analysis.", "headers": [ "Risk Type", "Mitigation Strategy" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-06-operations-and-supply-chain-table-5", "caption": "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]", "headers": [ "Chart candidate", "Data and sampling context", "Verify before use" ], "sourceIds": [ "BB-C06-S09" ], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-06-operations-and-supply-chain-table-6", "caption": "Table 6.6. Constructed digital-representation scope taxonomy. Actual terminology and scope must follow the governing standard, architecture, and use case.", "headers": [ "Teaching label", "Candidate scope", "Example decision use", "Key boundary" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-06-operations-and-supply-chain-table-7", "caption": "Table 6.7. Constructed S&OP decision rights and minimum outputs. The rows are a managerial synthesis, not a universal meeting design.", "headers": [ "Review", "Question", "Minimum output" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-06-operations-and-supply-chain-table-8", "caption": "Table 6.8. Constructed six-period forecast-error exercise. Error definitions and values are teaching inputs; they are not a forecast-performance benchmark.", "headers": [ "Period", "Actual units", "Forecast units", "Error: actual − forecast", "Absolute error" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-06-operations-and-supply-chain-table-9", "caption": "Table 6.9. Constructed constrained-plan alternatives. The contributions and service tensions are illustrative and require local cost, contract, quality, labor, and risk checks.", "headers": [ "Candidate plan", "A units", "B units", "Capacity used", "Unserved forecast", "Illustrative contribution", "Decision tension" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-06-operations-and-supply-chain-table-10", "caption": "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.", "headers": [ "Evidence stream", "Constructed input", "Question to test" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-06-operations-and-supply-chain.html", "outboundSlugs": [ "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-09-problem-structuring", "chapter-11-project-management-and-pmp-frameworks", "chapter-14-go-to-market-strategy", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-07-organizational-behavior-and-leadership", "slug": "chapter-07-organizational-behavior-and-leadership", "kind": "chapter", "number": 7, "title": "Organizational Behavior and Leadership", "part": "Part 1: Core MBA Foundations", "summary": "Leadership, motivation, culture, psychological safety, team dynamics, organizational design, and change.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "relatedSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-12-client-management", "chapter-17-leading-digital-transformation" ], "sourcePath": "src/part1-foundations/07-organizational-behavior-leadership.md", "outputPath": "index.html#chapter-07-organizational-behavior-and-leadership", "markdownPath": "markdown/chapter-07-organizational-behavior-and-leadership.md", "wordCount": 6032, "checksum": "fa1b70e38279fc370a63e6580be96685eb2d96aeb5600f529a110a5523c007dc", "sourceIds": [ "BB-C07-S05", "BB-C07-S01", "BB-C07-S02", "BB-C07-S16", "BB-C07-S07", "BB-C07-S06", "BB-C07-S08", "BB-C07-S09", "BB-C07-S10", "BB-C07-S17", "BB-C07-S03", "BB-C07-S18", "BB-C07-S19", "BB-C07-S20", "BB-C07-S11", "BB-C07-S12", "BB-C07-S04", "BB-C07-S13", "BB-C07-S14", "BB-C07-S15" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-07-organizational-behavior-and-leadership-executive-summary" }, { "level": 3, "text": "Manager decision outcomes", "id": "chapter-07-organizational-behavior-and-leadership-manager-decision-outcomes" }, { "level": 3, "text": "The Organizational Diagnosis Spine", "id": "chapter-07-organizational-behavior-and-leadership-the-organizational-diagnosis-spine" }, { "level": 2, "text": "Troubleshooting Guide: Leadership & Team Dynamics", "id": "chapter-07-organizational-behavior-and-leadership-troubleshooting-guide-leadership-team-dynamics" }, { "level": 2, "text": "The Frameworks", "id": "chapter-07-organizational-behavior-and-leadership-the-frameworks" }, { "level": 2, "text": "1. Kotter's 8-Step Change Management Model", "id": "chapter-07-organizational-behavior-and-leadership-1-kotter-s-8-step-change-management-model" }, { "level": 3, "text": "Overview", "id": "chapter-07-organizational-behavior-and-leadership-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-07-organizational-behavior-and-leadership-how-to-apply" }, { "level": 3, "text": "So What for Managers", "id": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-07-organizational-behavior-and-leadership-connections" }, { "level": 2, "text": "2. Leadership Styles & Radical Candor", "id": "chapter-07-organizational-behavior-and-leadership-2-leadership-styles-radical-candor" }, { "level": 3, "text": "Overview", "id": "chapter-07-organizational-behavior-and-leadership-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-07-organizational-behavior-and-leadership-how-to-apply-2" }, { "level": 3, "text": "Part A: Goleman's Six Styles", "id": "chapter-07-organizational-behavior-and-leadership-part-a-goleman-s-six-styles" }, { "level": 3, "text": "Part B: Radical Candor (Kim Scott)", "id": "chapter-07-organizational-behavior-and-leadership-part-b-radical-candor-kim-scott" }, { "level": 3, "text": "So What for Managers", "id": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-07-organizational-behavior-and-leadership-connections-2" }, { "level": 2, "text": "3. Lencioni's Five Dysfunctions of a Team", "id": "chapter-07-organizational-behavior-and-leadership-3-lencioni-s-five-dysfunctions-of-a-team" }, { "level": 3, "text": "Overview", "id": "chapter-07-organizational-behavior-and-leadership-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-07-organizational-behavior-and-leadership-how-to-apply-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-07-organizational-behavior-and-leadership-connections-3" }, { "level": 2, "text": "4. Stakeholder Mapping Grid", "id": "chapter-07-organizational-behavior-and-leadership-4-stakeholder-mapping-grid" }, { "level": 3, "text": "Overview", "id": "chapter-07-organizational-behavior-and-leadership-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-07-organizational-behavior-and-leadership-how-to-apply-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-07-organizational-behavior-and-leadership-connections-4" }, { "level": 2, "text": "5. Competing Values Framework (Culture Assessment)", "id": "chapter-07-organizational-behavior-and-leadership-5-competing-values-framework-culture-assessment" }, { "level": 3, "text": "Overview", "id": "chapter-07-organizational-behavior-and-leadership-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-07-organizational-behavior-and-leadership-how-to-apply-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-07-organizational-behavior-and-leadership-connections-5" }, { "level": 2, "text": "6. Talent 9-Box Grid", "id": "chapter-07-organizational-behavior-and-leadership-6-talent-9-box-grid" }, { "level": 3, "text": "Overview", "id": "chapter-07-organizational-behavior-and-leadership-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-07-organizational-behavior-and-leadership-how-to-apply-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-07-organizational-behavior-and-leadership-connections-6" }, { "level": 2, "text": "7. Motivation Theory Comparison", "id": "chapter-07-organizational-behavior-and-leadership-7-motivation-theory-comparison" }, { "level": 3, "text": "Overview", "id": "chapter-07-organizational-behavior-and-leadership-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-07-organizational-behavior-and-leadership-how-to-apply-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-07-organizational-behavior-and-leadership-connections-7" }, { "level": 2, "text": "8. Conflict-Mode Reflection Map", "id": "chapter-07-organizational-behavior-and-leadership-8-conflict-mode-reflection-map" }, { "level": 3, "text": "Overview", "id": "chapter-07-organizational-behavior-and-leadership-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-07-organizational-behavior-and-leadership-how-to-apply-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-07-organizational-behavior-and-leadership-connections-8" }, { "level": 2, "text": "9. Organizational Design Patterns", "id": "chapter-07-organizational-behavior-and-leadership-9-organizational-design-patterns" }, { "level": 3, "text": "Overview", "id": "chapter-07-organizational-behavior-and-leadership-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-07-organizational-behavior-and-leadership-how-to-apply-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-07-organizational-behavior-and-leadership-connections-9" }, { "level": 2, "text": "10. Psychological Safety Assessment", "id": "chapter-07-organizational-behavior-and-leadership-10-psychological-safety-assessment" }, { "level": 3, "text": "Overview", "id": "chapter-07-organizational-behavior-and-leadership-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-07-organizational-behavior-and-leadership-how-to-apply-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-07-organizational-behavior-and-leadership-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-07-organizational-behavior-and-leadership-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-07-organizational-behavior-and-leadership-connections-10" }, { "level": 2, "text": "Negotiation Bridge: Alternatives, Range, Value, Power, and Ethics", "id": "chapter-07-organizational-behavior-and-leadership-negotiation-bridge-alternatives-range-value-power-and-ethics" }, { "level": 3, "text": "Core preparation logic", "id": "chapter-07-organizational-behavior-and-leadership-core-preparation-logic" }, { "level": 3, "text": "Power, multiparty process, and ethics", "id": "chapter-07-organizational-behavior-and-leadership-power-multiparty-process-and-ethics" }, { "level": 2, "text": "Why This Matters: Mental Models & Leadership Wisdom", "id": "chapter-07-organizational-behavior-and-leadership-why-this-matters-mental-models-leadership-wisdom" }, { "level": 3, "text": "Mental Model 1: Culture is What You Reward and Punish", "id": "chapter-07-organizational-behavior-and-leadership-mental-model-1-culture-is-what-you-reward-and-punish" }, { "level": 3, "text": "Mental Model 2: The Trust Cascade", "id": "chapter-07-organizational-behavior-and-leadership-mental-model-2-the-trust-cascade" }, { "level": 3, "text": "Mental Model 3: Leadership is Situational, but Authenticity is Key", "id": "chapter-07-organizational-behavior-and-leadership-mental-model-3-leadership-is-situational-but-authenticity-is-key" }, { "level": 2, "text": "Illustrative Leadership Applications", "id": "chapter-07-organizational-behavior-and-leadership-illustrative-leadership-applications" }, { "level": 3, "text": "Application 1: Culture Turnaround", "id": "chapter-07-organizational-behavior-and-leadership-application-1-culture-turnaround" }, { "level": 3, "text": "Application 2: Creative-Review Process", "id": "chapter-07-organizational-behavior-and-leadership-application-2-creative-review-process" }, { "level": 3, "text": "Application 3: Visual Accountability", "id": "chapter-07-organizational-behavior-and-leadership-application-3-visual-accountability" }, { "level": 2, "text": "Applied Exercise: Diagnose a Team Without Labeling It", "id": "chapter-07-organizational-behavior-and-leadership-applied-exercise-diagnose-a-team-without-labeling-it" }, { "level": 3, "text": "Selective Connections", "id": "chapter-07-organizational-behavior-and-leadership-selective-connections" } ], "figures": [ { "id": "chapter-07-organizational-behavior-and-leadership-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C07-S01" ], "provenanceStatus": "constructed", "checksum": "d3b6a56e2557c96bbb8482fcf577ea6cacfb824bf0c4fbfa7aaa4c3a6903a812" }, { "id": "chapter-07-organizational-behavior-and-leadership-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C07-S08" ], "provenanceStatus": "constructed", "checksum": "0056678397d0efd8a32f014139df9f3a64fe0e5bc5a24224db5a3620a9462404" }, { "id": "chapter-07-organizational-behavior-and-leadership-figure-3", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C07-S20" ], "provenanceStatus": "constructed", "checksum": "d9cfbe464aa7e9fa02a41e5edee113344b76497bfee121b9d4ab1e47141ea53f" }, { "id": "chapter-07-organizational-behavior-and-leadership-figure-4", "type": "mermaid", "caption": "Figure 7.4. Constructed evidence-gated negotiation preparation.", "textEquivalent": "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.", "sourceIds": [ "BB-C07-S13", "BB-C07-S14" ], "provenanceStatus": "constructed", "checksum": "52233a0d7e8aca81b0a23d85871eb607a41c9361089183d86829ad7b4c7ee155" } ], "tables": [ { "id": "chapter-07-organizational-behavior-and-leadership-table-1", "caption": "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]", "headers": [ "Element", "Managerial question", "Common failure" ], "sourceIds": [ "BB-C07-S13", "BB-C07-S14" ], "provenanceStatus": "constructed", "rowCount": 6 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-07-organizational-behavior-and-leadership.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-17-leading-digital-transformation", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-13-startup-foundations", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy" ] }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "slug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "kind": "chapter", "number": 8, "title": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "part": "Part 1: Core MBA Foundations", "summary": "Mission, vision, operating cadence, OKRs, KPIs, scorecards, and execution systems.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "relatedSlugs": [ "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-11-project-management-and-pmp-frameworks", "chapter-17-leading-digital-transformation", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/part1-foundations/08-strategy-execution-mission-vision-values-okrs-kpis.md", "outputPath": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "markdownPath": "markdown/chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis.md", "wordCount": 5087, "checksum": "900af1418b41f74cf43fc555f93e7860c657a9aec239462fadfeb304b65063e8", "sourceIds": [ "BB-C08-S06", "BB-C08-S01", "BB-C08-S05", "BB-C08-S04", "BB-C08-S07", "BB-C08-S09", "BB-C08-S10", "BB-C08-S08", "BB-C08-S03", "BB-C08-S11", "BB-C08-S12" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-executive-summary" }, { "level": 3, "text": "Manager decision outcomes", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-manager-decision-outcomes" }, { "level": 3, "text": "The Strategy-Execution Operating System", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-strategy-execution-operating-system" }, { "level": 2, "text": "Troubleshooting Guide: Strategy & Execution", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-troubleshooting-guide-strategy-execution" }, { "level": 2, "text": "The Frameworks", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-frameworks" }, { "level": 2, "text": "1. Mission, Vision, and Values as Strategic Inputs", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-1-mission-vision-and-values-as-strategic-inputs" }, { "level": 3, "text": "Overview", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply" }, { "level": 3, "text": "So What for Managers", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections" }, { "level": 2, "text": "2. Evidence-Based Goal Setting (SMART & FAST)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-2-evidence-based-goal-setting-smart-fast" }, { "level": 3, "text": "Overview", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-2" }, { "level": 3, "text": "Contrarian Thinking: The Problem with \"Achievable\"", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-contrarian-thinking-the-problem-with-achievable" }, { "level": 3, "text": "So What for Managers", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-2" }, { "level": 2, "text": "3. \"Good Strategy / Bad Strategy\" (Rumelt's Kernel)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-3-good-strategy-bad-strategy-rumelt-s-kernel" }, { "level": 3, "text": "Overview", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-3" }, { "level": 2, "text": "4. Objectives and Key Results (OKRs)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-4-objectives-and-key-results-okrs" }, { "level": 3, "text": "Overview", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-4" }, { "level": 2, "text": "5. Key Performance Indicators (KPIs) vs. OKRs", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-5-key-performance-indicators-kpis-vs-okrs" }, { "level": 3, "text": "Overview", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-5" }, { "level": 2, "text": "6. The Balanced Scorecard (BSC)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-6-the-balanced-scorecard-bsc" }, { "level": 3, "text": "Overview", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-6" }, { "level": 3, "text": "Contrarian Thinking: BSC vs. OKRs", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-contrarian-thinking-bsc-vs-okrs" }, { "level": 3, "text": "So What for Managers", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-6" }, { "level": 2, "text": "7. The Hedgehog Concept (Jim Collins)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-7-the-hedgehog-concept-jim-collins" }, { "level": 3, "text": "Overview", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-7" }, { "level": 2, "text": "8. The VSEM Framework (Vision, Strategy, Execution, Metrics)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-8-the-vsem-framework-vision-strategy-execution-metrics" }, { "level": 3, "text": "Overview", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-8" }, { "level": 2, "text": "9. Goal Cascading & Alignment Models", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-9-goal-cascading-alignment-models" }, { "level": 3, "text": "Overview", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-9" }, { "level": 2, "text": "10. Contrarian Thinking: The Case Against Mission Statements", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-10-contrarian-thinking-the-case-against-mission-statements" }, { "level": 3, "text": "Overview", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-how-to-apply-10" }, { "level": 3, "text": "The Critique", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-critique" }, { "level": 3, "text": "The Alternative: A Measurable Vision and Behavioral Values", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-the-alternative-a-measurable-vision-and-behavioral-values" }, { "level": 3, "text": "So What for Managers", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-connections-10" }, { "level": 2, "text": "Why This Matters: Mental Models & Execution Wisdom", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-why-this-matters-mental-models-execution-wisdom" }, { "level": 3, "text": "Mental Model 1: Outcomes over Outputs", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-1-outcomes-over-outputs" }, { "level": 3, "text": "Mental Model 2: Health vs. Change", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-2-health-vs-change" }, { "level": 3, "text": "Mental Model 3: Strategy is About Saying \"No\"", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-mental-model-3-strategy-is-about-saying-no" }, { "level": 2, "text": "Execution Examples in Action", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-execution-examples-in-action" }, { "level": 3, "text": "Example 1: Outcome-Oriented OKR", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-example-1-outcome-oriented-okr" }, { "level": 3, "text": "Example 2: How Metrics Can Drive Dysfunction", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-example-2-how-metrics-can-drive-dysfunction" }, { "level": 2, "text": "Applied Exercise: Run a Constrained Strategy Review", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-applied-exercise-run-a-constrained-strategy-review" }, { "level": 3, "text": "Selective Connections", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-selective-connections" } ], "figures": [ { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C08-S04", "BB-C08-S05", "BB-C08-S06", "BB-C08-S01" ], "provenanceStatus": "constructed", "checksum": "6d3dc2c9d99afa1b9c0364e5a9dfd6ab610388797ee4ff3571f587868e4b0837" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-figure-2", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C08-S01", "BB-C08-S06" ], "provenanceStatus": "constructed", "checksum": "d694a7c6475a887be69bbc14c0579db6eddc5709c25303a6b2703507a2d6259b" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-figure-3", "type": "mermaid", "caption": "Figure 8.3. Balanced Scorecard strategy hypotheses. The arrows are relationships to test, not established causal chains or guaranteed financial outcomes. [BB-C08-S03]", "textEquivalent": "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.", "sourceIds": [ "BB-C08-S03" ], "provenanceStatus": "constructed", "checksum": "6ff232a86e7fc859428493859acd9731a9c5633b372488c453b985436adf3b9f" } ], "tables": [], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis.html", "outboundSlugs": [ "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-11-project-management-and-pmp-frameworks", "chapter-17-leading-digital-transformation", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-07-organizational-behavior-and-leadership", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-17-leading-digital-transformation", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-09-problem-structuring", "slug": "chapter-09-problem-structuring", "kind": "chapter", "number": 9, "title": "Problem Structuring", "part": "Part 2: Management Consulting Toolkit", "summary": "Issue trees, MECE problem decomposition, hypotheses, logic trees, prioritization, assumption mapping, and decision-tree structure.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "relatedSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/part2-consulting/09-problem-structuring.md", "outputPath": "index.html#chapter-09-problem-structuring", "markdownPath": "markdown/chapter-09-problem-structuring.md", "wordCount": 11866, "checksum": "65c18b23d49a5c9d3bf88c09c18824cccdc21fb65597297437ec48e56242d0a1", "sourceIds": [ "BB-C09-S01", "BB-C09-S02", "BB-C09-S03", "BB-C09-S06", "BB-C09-S07", "BB-C09-S05", "BB-C22-S11", "BB-C22-S12", "BB-C09-S04" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-09-problem-structuring-executive-summary" }, { "level": 3, "text": "Manager decision outcomes", "id": "chapter-09-problem-structuring-manager-decision-outcomes" }, { "level": 2, "text": "Troubleshooting Guide: Problem Structuring", "id": "chapter-09-problem-structuring-troubleshooting-guide-problem-structuring" }, { "level": 2, "text": "The Frameworks", "id": "chapter-09-problem-structuring-the-frameworks" }, { "level": 2, "text": "1. Issue Tree Templates", "id": "chapter-09-problem-structuring-1-issue-tree-templates" }, { "level": 3, "text": "Overview", "id": "chapter-09-problem-structuring-overview" }, { "level": 4, "text": "Evidence-routing visual", "id": "chapter-09-problem-structuring-evidence-routing-visual" }, { "level": 3, "text": "How to Apply", "id": "chapter-09-problem-structuring-how-to-apply" }, { "level": 4, "text": "Contrarian Thinking: When to Break Your Issue Tree", "id": "chapter-09-problem-structuring-contrarian-thinking-when-to-break-your-issue-tree" }, { "level": 3, "text": "So What for Managers", "id": "chapter-09-problem-structuring-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-09-problem-structuring-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-09-problem-structuring-connections" }, { "level": 2, "text": "2. The MECE Principle", "id": "chapter-09-problem-structuring-2-the-mece-principle" }, { "level": 3, "text": "Overview", "id": "chapter-09-problem-structuring-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-09-problem-structuring-how-to-apply-2" }, { "level": 4, "text": "Contrarian Thinking: The 80/20 Rule vs. Pure MECE", "id": "chapter-09-problem-structuring-contrarian-thinking-the-80-20-rule-vs-pure-mece" }, { "level": 3, "text": "So What for Managers", "id": "chapter-09-problem-structuring-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-09-problem-structuring-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-09-problem-structuring-connections-2" }, { "level": 2, "text": "3. Hypothesis Pyramid Structure", "id": "chapter-09-problem-structuring-3-hypothesis-pyramid-structure" }, { "level": 3, "text": "Overview", "id": "chapter-09-problem-structuring-overview-3" }, { "level": 4, "text": "Argument-structure visual", "id": "chapter-09-problem-structuring-argument-structure-visual" }, { "level": 3, "text": "How to Apply", "id": "chapter-09-problem-structuring-how-to-apply-3" }, { "level": 4, "text": "Contrarian Thinking: Data Doesn't Speak for Itself", "id": "chapter-09-problem-structuring-contrarian-thinking-data-doesn-t-speak-for-itself" }, { "level": 3, "text": "So What for Managers", "id": "chapter-09-problem-structuring-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-09-problem-structuring-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-09-problem-structuring-connections-3" }, { "level": 2, "text": "4. First Principles Thinking & The 5 Whys", "id": "chapter-09-problem-structuring-4-first-principles-thinking-the-5-whys" }, { "level": 3, "text": "Overview", "id": "chapter-09-problem-structuring-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-09-problem-structuring-how-to-apply-4" }, { "level": 4, "text": "Contrarian Thinking: Sometimes the Symptom IS the Problem", "id": "chapter-09-problem-structuring-contrarian-thinking-sometimes-the-symptom-is-the-problem" }, { "level": 3, "text": "So What for Managers", "id": "chapter-09-problem-structuring-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-09-problem-structuring-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-09-problem-structuring-connections-4" }, { "level": 2, "text": "5. Logic Tree Construction", "id": "chapter-09-problem-structuring-5-logic-tree-construction" }, { "level": 3, "text": "Overview", "id": "chapter-09-problem-structuring-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-09-problem-structuring-how-to-apply-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-09-problem-structuring-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-09-problem-structuring-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-09-problem-structuring-connections-5" }, { "level": 2, "text": "6. Problem Statement Canvas", "id": "chapter-09-problem-structuring-6-problem-statement-canvas" }, { "level": 3, "text": "Overview", "id": "chapter-09-problem-structuring-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-09-problem-structuring-how-to-apply-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-09-problem-structuring-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-09-problem-structuring-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-09-problem-structuring-connections-6" }, { "level": 2, "text": "7. Prioritization Matrices", "id": "chapter-09-problem-structuring-7-prioritization-matrices" }, { "level": 3, "text": "Overview", "id": "chapter-09-problem-structuring-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-09-problem-structuring-how-to-apply-7" }, { "level": 4, "text": "Contrarian Thinking: Prioritization Matrices Create False Precision", "id": "chapter-09-problem-structuring-contrarian-thinking-prioritization-matrices-create-false-precision" }, { "level": 3, "text": "So What for Managers", "id": "chapter-09-problem-structuring-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-09-problem-structuring-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-09-problem-structuring-connections-7" }, { "level": 2, "text": "8. Risk Assessment Framework", "id": "chapter-09-problem-structuring-8-risk-assessment-framework" }, { "level": 3, "text": "Overview", "id": "chapter-09-problem-structuring-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-09-problem-structuring-how-to-apply-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-09-problem-structuring-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-09-problem-structuring-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-09-problem-structuring-connections-8" }, { "level": 2, "text": "9. Decision Criteria Weighting Model", "id": "chapter-09-problem-structuring-9-decision-criteria-weighting-model" }, { "level": 3, "text": "Overview", "id": "chapter-09-problem-structuring-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-09-problem-structuring-how-to-apply-9" }, { "level": 4, "text": "Decision-Tree Handoff: Structure Before Calculating", "id": "chapter-09-problem-structuring-decision-tree-handoff-structure-before-calculating" }, { "level": 3, "text": "So What for Managers", "id": "chapter-09-problem-structuring-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-09-problem-structuring-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-09-problem-structuring-connections-9" }, { "level": 2, "text": "10. Assumption Mapping", "id": "chapter-09-problem-structuring-10-assumption-mapping" }, { "level": 3, "text": "Overview", "id": "chapter-09-problem-structuring-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-09-problem-structuring-how-to-apply-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-09-problem-structuring-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-09-problem-structuring-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-09-problem-structuring-connections-10" }, { "level": 2, "text": "Why This Matters: Mental Models & Problem-Solving Wisdom", "id": "chapter-09-problem-structuring-why-this-matters-mental-models-problem-solving-wisdom" }, { "level": 3, "text": "Mental Model 1: First Principles Thinking", "id": "chapter-09-problem-structuring-mental-model-1-first-principles-thinking" }, { "level": 3, "text": "Mental Model 2: The Pyramid Principle", "id": "chapter-09-problem-structuring-mental-model-2-the-pyramid-principle" }, { "level": 3, "text": "Mental Model 3: Problem vs. Symptom", "id": "chapter-09-problem-structuring-mental-model-3-problem-vs-symptom" }, { "level": 3, "text": "Mental Model 4: Satisficing vs. Maximizing (Herbert Simon's Bounded Rationality)", "id": "chapter-09-problem-structuring-mental-model-4-satisficing-vs-maximizing-herbert-simon-s-bounded-rationality" }, { "level": 3, "text": "Mental Model 5: Reversibility and Option Value", "id": "chapter-09-problem-structuring-mental-model-5-reversibility-and-option-value" }, { "level": 3, "text": "Mental Model 6: Pre-Mortem Analysis (Gary Klein)", "id": "chapter-09-problem-structuring-mental-model-6-pre-mortem-analysis-gary-klein" }, { "level": 2, "text": "Operator's Playbook: Problem Structuring in the Real World", "id": "chapter-09-problem-structuring-operator-s-playbook-problem-structuring-in-the-real-world" }, { "level": 3, "text": "The 1-Week vs. 1-Month Approach", "id": "chapter-09-problem-structuring-the-1-week-vs-1-month-approach" }, { "level": 3, "text": "Political Navigation: Red Flags and How to Handle Them", "id": "chapter-09-problem-structuring-political-navigation-red-flags-and-how-to-handle-them" }, { "level": 3, "text": "Client Management: When to Push Back vs. When to Adapt", "id": "chapter-09-problem-structuring-client-management-when-to-push-back-vs-when-to-adapt" }, { "level": 2, "text": "Case Studies: Structuring in Action", "id": "chapter-09-problem-structuring-case-studies-structuring-in-action" }, { "level": 3, "text": "Composite 1: The \"Profitability\" Problem That Wasn't", "id": "chapter-09-problem-structuring-composite-1-the-profitability-problem-that-wasn-t" }, { "level": 3, "text": "Composite 2: The Narrow Service Frame", "id": "chapter-09-problem-structuring-composite-2-the-narrow-service-frame" }, { "level": 3, "text": "Composite 3: The Missing M&A Branch", "id": "chapter-09-problem-structuring-composite-3-the-missing-m-a-branch" }, { "level": 3, "text": "Composite 4: The Ethically Truncated Mandate", "id": "chapter-09-problem-structuring-composite-4-the-ethically-truncated-mandate" }, { "level": 3, "text": "Composite 5: The Predetermined Public-Sector Answer", "id": "chapter-09-problem-structuring-composite-5-the-predetermined-public-sector-answer" }, { "level": 3, "text": "Composite 6: The Politically Constrained Turnaround", "id": "chapter-09-problem-structuring-composite-6-the-politically-constrained-turnaround" }, { "level": 2, "text": "Advanced Framework Applications: Deep Dives", "id": "chapter-09-problem-structuring-advanced-framework-applications-deep-dives" }, { "level": 3, "text": "Deep Dive 1: Building a Profitability Issue Tree from Scratch", "id": "chapter-09-problem-structuring-deep-dive-1-building-a-profitability-issue-tree-from-scratch" }, { "level": 3, "text": "Deep Dive 2: Using the 5 Whys to Diagnose a Customer Churn Problem", "id": "chapter-09-problem-structuring-deep-dive-2-using-the-5-whys-to-diagnose-a-customer-churn-problem" }, { "level": 3, "text": "Deep Dive 3: Prioritization Matrix for a Product Roadmap", "id": "chapter-09-problem-structuring-deep-dive-3-prioritization-matrix-for-a-product-roadmap" }, { "level": 3, "text": "Deep Dive 4: Assumption Mapping for a New Market Entry", "id": "chapter-09-problem-structuring-deep-dive-4-assumption-mapping-for-a-new-market-entry" }, { "level": 2, "text": "Common Mistakes and How to Avoid Them", "id": "chapter-09-problem-structuring-common-mistakes-and-how-to-avoid-them" }, { "level": 3, "text": "Mistake 1: Building an Issue Tree Before Defining the Problem", "id": "chapter-09-problem-structuring-mistake-1-building-an-issue-tree-before-defining-the-problem" }, { "level": 3, "text": "Mistake 2: Using MECE as a Perfectionism Excuse", "id": "chapter-09-problem-structuring-mistake-2-using-mece-as-a-perfectionism-excuse" }, { "level": 3, "text": "Mistake 3: Confusing the Hypothesis Pyramid with a Data Dump", "id": "chapter-09-problem-structuring-mistake-3-confusing-the-hypothesis-pyramid-with-a-data-dump" }, { "level": 3, "text": "Mistake 4: Stopping at the Fourth \"Why\" in the 5 Whys", "id": "chapter-09-problem-structuring-mistake-4-stopping-at-the-fourth-why-in-the-5-whys" }, { "level": 3, "text": "Mistake 5: Treating Prioritization Matrices as Objective Truth", "id": "chapter-09-problem-structuring-mistake-5-treating-prioritization-matrices-as-objective-truth" }, { "level": 2, "text": "Final Thoughts: From Frameworks to Judgment", "id": "chapter-09-problem-structuring-final-thoughts-from-frameworks-to-judgment" }, { "level": 3, "text": "When to Follow the Frameworks", "id": "chapter-09-problem-structuring-when-to-follow-the-frameworks" }, { "level": 3, "text": "When to Break the Frameworks", "id": "chapter-09-problem-structuring-when-to-break-the-frameworks" }, { "level": 3, "text": "The Operator's Mindset: Frameworks + Judgment", "id": "chapter-09-problem-structuring-the-operator-s-mindset-frameworks-judgment" }, { "level": 3, "text": "Applied Exercise: Structure a Funding Decision", "id": "chapter-09-problem-structuring-applied-exercise-structure-a-funding-decision" }, { "level": 3, "text": "Related Chapters", "id": "chapter-09-problem-structuring-related-chapters" }, { "level": 3, "text": "Your Action Items", "id": "chapter-09-problem-structuring-your-action-items" } ], "figures": [ { "id": "chapter-09-problem-structuring-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "dffaefdcf6323d4fc1181078ffcde3c1462b997dcc434bad1561913797b99344" }, { "id": "chapter-09-problem-structuring-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C09-S01" ], "provenanceStatus": "source-linked", "checksum": "0763cef4c633a20e7e282073f2f16346aa09616f0f35506437712ea083cdafef" }, { "id": "chapter-09-problem-structuring-figure-3", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "b9af2796790878a136d9ffcffdecdbb9cf0e5cbcaa48a8a139f76bf23146e35d" }, { "id": "chapter-09-problem-structuring-figure-4", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C09-S05" ], "provenanceStatus": "source-linked", "checksum": "9d1a1a367dcd5c115e9de3f6319f0584d1e889012df582cbab2abc9385fc4971" } ], "tables": [ { "id": "chapter-09-problem-structuring-table-1", "caption": "Table 1. Feature / Customer Demand / Revenue Impact", "headers": [ "Feature", "Customer Demand", "Revenue Impact", "Strategic", "Ease", "Weighted Score" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-09-problem-structuring.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-b-contrarian-business-perspectives", "chapter-06-operations-and-supply-chain", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration", "slug": "chapter-10-advanced-consulting-frameworks-and-integration", "kind": "chapter", "number": 10, "title": "Advanced Consulting Frameworks and Integration", "part": "Part 2: Management Consulting Toolkit", "summary": "Integrated consulting frameworks for organizational diagnosis, business models, new ventures, M&A, transformation, and decision governance.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "relatedSlugs": [ "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-11-project-management-and-pmp-frameworks", "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy", "chapter-17-leading-digital-transformation" ], "sourcePath": "src/part2-consulting/10-consulting-frameworks.md", "outputPath": "index.html#chapter-10-advanced-consulting-frameworks-and-integration", "markdownPath": "markdown/chapter-10-advanced-consulting-frameworks-and-integration.md", "wordCount": 11703, "checksum": "67c845e76309b9a4f2846f0a1aae96867c902202f10aa7b94836cab0d8c6bf48", "sourceIds": [ "BB-C10-S01", "BB-C10-S03", "BB-C10-S04", "BB-C10-S06", "BB-C10-S02", "BB-C10-S07" ], "headings": [ { "level": 2, "text": "Manager Decision Outcomes and Boundaries", "id": "chapter-10-advanced-consulting-frameworks-and-integration-manager-decision-outcomes-and-boundaries" }, { "level": 2, "text": "Executive Summary", "id": "chapter-10-advanced-consulting-frameworks-and-integration-executive-summary" }, { "level": 2, "text": "Troubleshooting Guide: Advanced Frameworks", "id": "chapter-10-advanced-consulting-frameworks-and-integration-troubleshooting-guide-advanced-frameworks" }, { "level": 2, "text": "The Frameworks", "id": "chapter-10-advanced-consulting-frameworks-and-integration-the-frameworks" }, { "level": 2, "text": "1. New Business Unit Launch Framework (Integrated)", "id": "chapter-10-advanced-consulting-frameworks-and-integration-1-new-business-unit-launch-framework-integrated" }, { "level": 3, "text": "Overview", "id": "chapter-10-advanced-consulting-frameworks-and-integration-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply" }, { "level": 4, "text": "The Six-Phase Evidence-Gated Launch Model", "id": "chapter-10-advanced-consulting-frameworks-and-integration-the-six-phase-evidence-gated-launch-model" }, { "level": 3, "text": "Phase 1: Strategic Assessment — The Sanity Check", "id": "chapter-10-advanced-consulting-frameworks-and-integration-phase-1-strategic-assessment-the-sanity-check" }, { "level": 3, "text": "Phase 2: Business Planning — The Blueprint", "id": "chapter-10-advanced-consulting-frameworks-and-integration-phase-2-business-planning-the-blueprint" }, { "level": 3, "text": "Phase 3: Pilot / MVP — The Reality Test", "id": "chapter-10-advanced-consulting-frameworks-and-integration-phase-3-pilot-mvp-the-reality-test" }, { "level": 3, "text": "Phases 4, 5, and 6: Scale, Optimize, and Integrate", "id": "chapter-10-advanced-consulting-frameworks-and-integration-phases-4-5-and-6-scale-optimize-and-integrate" }, { "level": 3, "text": "So What for Managers", "id": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-10-advanced-consulting-frameworks-and-integration-connections" }, { "level": 2, "text": "2. McKinsey 7S Framework", "id": "chapter-10-advanced-consulting-frameworks-and-integration-2-mckinsey-7s-framework" }, { "level": 3, "text": "Overview", "id": "chapter-10-advanced-consulting-frameworks-and-integration-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-10-advanced-consulting-frameworks-and-integration-connections-2" }, { "level": 2, "text": "3. Competitive-Advantage Context Check", "id": "chapter-10-advanced-consulting-frameworks-and-integration-3-competitive-advantage-context-check" }, { "level": 3, "text": "Overview", "id": "chapter-10-advanced-consulting-frameworks-and-integration-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-10-advanced-consulting-frameworks-and-integration-connections-3" }, { "level": 2, "text": "4. Bain's RAPID Decision Framework", "id": "chapter-10-advanced-consulting-frameworks-and-integration-4-bain-s-rapid-decision-framework" }, { "level": 3, "text": "Overview", "id": "chapter-10-advanced-consulting-frameworks-and-integration-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-10-advanced-consulting-frameworks-and-integration-connections-4" }, { "level": 2, "text": "5. Value Chain Analysis (Digital Version)", "id": "chapter-10-advanced-consulting-frameworks-and-integration-5-value-chain-analysis-digital-version" }, { "level": 3, "text": "Overview", "id": "chapter-10-advanced-consulting-frameworks-and-integration-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-10-advanced-consulting-frameworks-and-integration-connections-5" }, { "level": 2, "text": "6. Business Model Canvas", "id": "chapter-10-advanced-consulting-frameworks-and-integration-6-business-model-canvas" }, { "level": 3, "text": "Overview", "id": "chapter-10-advanced-consulting-frameworks-and-integration-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-6" }, { "level": 3, "text": "Visual representation", "id": "chapter-10-advanced-consulting-frameworks-and-integration-visual-representation" }, { "level": 3, "text": "So What for Managers", "id": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-10-advanced-consulting-frameworks-and-integration-connections-6" }, { "level": 2, "text": "7. Capability Development Ladder (Constructed)", "id": "chapter-10-advanced-consulting-frameworks-and-integration-7-capability-development-ladder-constructed" }, { "level": 3, "text": "Overview", "id": "chapter-10-advanced-consulting-frameworks-and-integration-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-10-advanced-consulting-frameworks-and-integration-connections-7" }, { "level": 2, "text": "8. Digital Transformation Framework", "id": "chapter-10-advanced-consulting-frameworks-and-integration-8-digital-transformation-framework" }, { "level": 3, "text": "Overview", "id": "chapter-10-advanced-consulting-frameworks-and-integration-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-10-advanced-consulting-frameworks-and-integration-connections-8" }, { "level": 2, "text": "9. M&A Due Diligence Checklist", "id": "chapter-10-advanced-consulting-frameworks-and-integration-9-m-a-due-diligence-checklist" }, { "level": 3, "text": "Overview", "id": "chapter-10-advanced-consulting-frameworks-and-integration-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-10-advanced-consulting-frameworks-and-integration-connections-9" }, { "level": 2, "text": "10. Post-Merger Integration (PMI) Playbook", "id": "chapter-10-advanced-consulting-frameworks-and-integration-10-post-merger-integration-pmi-playbook" }, { "level": 3, "text": "Overview", "id": "chapter-10-advanced-consulting-frameworks-and-integration-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-10-advanced-consulting-frameworks-and-integration-how-to-apply-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-10-advanced-consulting-frameworks-and-integration-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-10-advanced-consulting-frameworks-and-integration-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-10-advanced-consulting-frameworks-and-integration-connections-10" }, { "level": 2, "text": "Why This Matters: Mental Models & Consulting Wisdom", "id": "chapter-10-advanced-consulting-frameworks-and-integration-why-this-matters-mental-models-consulting-wisdom" }, { "level": 3, "text": "Mental Model 1: Frameworks are Scaffolding, Not Cages", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-1-frameworks-are-scaffolding-not-cages" }, { "level": 3, "text": "Mental Model 2: The 80/20 Rule in Action", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-2-the-80-20-rule-in-action" }, { "level": 3, "text": "Mental Model 3: The Importance of a \"Single Source of Truth\"", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-3-the-importance-of-a-single-source-of-truth" }, { "level": 3, "text": "Mental Model 4: Integration Beats Optimization (System Thinking)", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-4-integration-beats-optimization-system-thinking" }, { "level": 3, "text": "Mental Model 5: Culture, incentives, and execution interact", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-5-culture-incentives-and-execution-interact" }, { "level": 3, "text": "Mental Model 6: The Map Is Not the Territory", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mental-model-6-the-map-is-not-the-territory" }, { "level": 2, "text": "Operator's Playbook: Consulting Frameworks in Practice", "id": "chapter-10-advanced-consulting-frameworks-and-integration-operator-s-playbook-consulting-frameworks-in-practice" }, { "level": 3, "text": "Selecting a Framework for the Decision", "id": "chapter-10-advanced-consulting-frameworks-and-integration-selecting-a-framework-for-the-decision" }, { "level": 3, "text": "Rapid stabilization after close", "id": "chapter-10-advanced-consulting-frameworks-and-integration-rapid-stabilization-after-close" }, { "level": 3, "text": "Political Navigation: When Frameworks Become Weapons", "id": "chapter-10-advanced-consulting-frameworks-and-integration-political-navigation-when-frameworks-become-weapons" }, { "level": 3, "text": "Red Flags: When to Fire Your Consultant", "id": "chapter-10-advanced-consulting-frameworks-and-integration-red-flags-when-to-fire-your-consultant" }, { "level": 3, "text": "The Integration Map: Combining Multiple Frameworks", "id": "chapter-10-advanced-consulting-frameworks-and-integration-the-integration-map-combining-multiple-frameworks" }, { "level": 2, "text": "Case Studies: Integration in Action", "id": "chapter-10-advanced-consulting-frameworks-and-integration-case-studies-integration-in-action" }, { "level": 3, "text": "Composite Teaching Scenario 1: Preserving a Creative Unit After an Acquisition", "id": "chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-1-preserving-a-creative-unit-after-an-acquisition" }, { "level": 3, "text": "Composite Teaching Scenario 2: Reconciling Strategy and Culture in a Media Merger", "id": "chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-2-reconciling-strategy-and-culture-in-a-media-merger" }, { "level": 3, "text": "Composite Teaching Scenario 3: Commercial Diligence Beyond the Checklist", "id": "chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-3-commercial-diligence-beyond-the-checklist" }, { "level": 3, "text": "Composite Teaching Scenario 4: Protecting Safety-Critical Activities in a Value Chain", "id": "chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-4-protecting-safety-critical-activities-in-a-value-chain" }, { "level": 3, "text": "Composite Teaching Scenario 5: Aligning a Digital Platform Transformation", "id": "chapter-10-advanced-consulting-frameworks-and-integration-composite-teaching-scenario-5-aligning-a-digital-platform-transformation" }, { "level": 2, "text": "Advanced Framework Applications: Deep Dives", "id": "chapter-10-advanced-consulting-frameworks-and-integration-advanced-framework-applications-deep-dives" }, { "level": 3, "text": "Deep Dive 1: Applying the McKinsey 7S Framework to a Failing Digital Transformation", "id": "chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-1-applying-the-mckinsey-7s-framework-to-a-failing-digital-transformation" }, { "level": 3, "text": "Deep Dive 2: Using the Business Model Canvas to Pivot a Failing Startup", "id": "chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-2-using-the-business-model-canvas-to-pivot-a-failing-startup" }, { "level": 3, "text": "Deep Dive 3: Executing a Post-Merger Integration with the PMI Playbook", "id": "chapter-10-advanced-consulting-frameworks-and-integration-deep-dive-3-executing-a-post-merger-integration-with-the-pmi-playbook" }, { "level": 2, "text": "Common Mistakes and How to Avoid Them", "id": "chapter-10-advanced-consulting-frameworks-and-integration-common-mistakes-and-how-to-avoid-them" }, { "level": 3, "text": "Mistake 1: Using the 7S Framework as a Checklist, Not a Diagnostic", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mistake-1-using-the-7s-framework-as-a-checklist-not-a-diagnostic" }, { "level": 3, "text": "Mistake 2: Treating the Business Model Canvas as Static", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mistake-2-treating-the-business-model-canvas-as-static" }, { "level": 3, "text": "Mistake 3: Applying RAPID to Decisions That Don't Matter", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mistake-3-applying-rapid-to-decisions-that-don-t-matter" }, { "level": 3, "text": "Mistake 4: Skipping Talent & Culture Due Diligence in M&A", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mistake-4-skipping-talent-culture-due-diligence-in-m-a" }, { "level": 3, "text": "Mistake 5: Building a Digital Transformation Framework Without Leadership Buy-In", "id": "chapter-10-advanced-consulting-frameworks-and-integration-mistake-5-building-a-digital-transformation-framework-without-leadership-buy-in" } ], "figures": [ { "id": "chapter-10-advanced-consulting-frameworks-and-integration-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "1225ee9e993ba6df0564c85ac5608e102569ba7976ee2d7ab75a041fe621ffe6" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-figure-2", "type": "mermaid", "caption": "Figure 10.2 — Business-model hypothesis system. The nine blocks are shown as an evidence flow rather than a copied branded-canvas layout.", "textEquivalent": "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.", "sourceIds": [ "BB-C10-S03" ], "provenanceStatus": "constructed", "checksum": "076271038c201102f38969530119f3a8b44febda6caf0528a8451545b6668882" } ], "tables": [ { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-1", "caption": "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.", "headers": [ "Framework Applied", "Key Question It Answers", "Deliverable" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-2", "caption": "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.", "headers": [ "Framework Applied", "Key Question It Answers", "Deliverable" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-3", "caption": "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.", "headers": [ "Framework Applied", "Key Question It Answers", "Deliverable" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-4", "caption": "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.", "headers": [ "Building block", "Decision question", "Illustrative evidence to gather" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 9 }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-5", "caption": "Table 5. Candidate tool / Useful questions / Do not infer", "headers": [ "Candidate tool", "Useful questions", "Do not infer" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-6", "caption": "Table 10.5. Constructed startup business-model baseline. All values are fictional teaching assumptions, not benchmarks or forecasts.", "headers": [ "Box", "Current State" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 9 }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-7", "caption": "Table 10.6. Constructed startup pivot hypothesis. All values are fictional teaching assumptions and require commercial, privacy, compliance, and cash evidence.", "headers": [ "Box", "Pivoted State" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 9 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-10-advanced-consulting-frameworks-and-integration.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-11-project-management-and-pmp-frameworks", "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy", "chapter-17-leading-digital-transformation" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-b-contrarian-business-perspectives", "chapter-03-strategy-and-competitive-analysis", "chapter-09-problem-structuring", "chapter-11-project-management-and-pmp-frameworks", "chapter-17-leading-digital-transformation", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-11-project-management-and-pmp-frameworks", "slug": "chapter-11-project-management-and-pmp-frameworks", "kind": "chapter", "number": 11, "title": "Project Management and PMP Frameworks", "part": "Part 2: Management Consulting Toolkit", "summary": "Predictive process groups, WBS, critical path, earned value, risk, stakeholders, Scrum, constructed flow policy, and change control.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "relatedSlugs": [ "chapter-06-operations-and-supply-chain", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-12-client-management" ], "sourcePath": "src/part2-consulting/11-project-management-pmp-frameworks.md", "outputPath": "index.html#chapter-11-project-management-and-pmp-frameworks", "markdownPath": "markdown/chapter-11-project-management-and-pmp-frameworks.md", "wordCount": 15609, "checksum": "5abd5404305886787754d3c2c9251d7ba0e45c7efb037a9ccd0f634c030d48b0", "sourceIds": [ "BB-C11-S01", "BB-C11-S05", "BB-C11-S06", "BB-C11-S02", "BB-C11-S03", "BB-C11-S04" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-11-project-management-and-pmp-frameworks-executive-summary" }, { "level": 3, "text": "Manager Decision Outcomes and Boundary", "id": "chapter-11-project-management-and-pmp-frameworks-manager-decision-outcomes-and-boundary" }, { "level": 2, "text": "1. Predictive Project-Management Process Groups", "id": "chapter-11-project-management-and-pmp-frameworks-1-predictive-project-management-process-groups" }, { "level": 3, "text": "Overview", "id": "chapter-11-project-management-and-pmp-frameworks-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-apply" }, { "level": 4, "text": "The five historical process groups", "id": "chapter-11-project-management-and-pmp-frameworks-the-five-historical-process-groups" }, { "level": 3, "text": "Process Group 1: INITIATING", "id": "chapter-11-project-management-and-pmp-frameworks-process-group-1-initiating" }, { "level": 3, "text": "Process Group 2: PLANNING", "id": "chapter-11-project-management-and-pmp-frameworks-process-group-2-planning" }, { "level": 3, "text": "Process Group 3: EXECUTING", "id": "chapter-11-project-management-and-pmp-frameworks-process-group-3-executing" }, { "level": 3, "text": "Process Group 4: MONITORING & CONTROLLING", "id": "chapter-11-project-management-and-pmp-frameworks-process-group-4-monitoring-controlling" }, { "level": 3, "text": "Process Group 5: CLOSING", "id": "chapter-11-project-management-and-pmp-frameworks-process-group-5-closing" }, { "level": 3, "text": "So What for Managers", "id": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-11-project-management-and-pmp-frameworks-connections" }, { "level": 2, "text": "2. Work Breakdown Structure (WBS)", "id": "chapter-11-project-management-and-pmp-frameworks-2-work-breakdown-structure-wbs" }, { "level": 3, "text": "Overview", "id": "chapter-11-project-management-and-pmp-frameworks-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-2" }, { "level": 4, "text": "WBS Structure", "id": "chapter-11-project-management-and-pmp-frameworks-wbs-structure" }, { "level": 3, "text": "WBS Rules", "id": "chapter-11-project-management-and-pmp-frameworks-wbs-rules" }, { "level": 3, "text": "Example WBS: CRM Implementation", "id": "chapter-11-project-management-and-pmp-frameworks-example-wbs-crm-implementation" }, { "level": 3, "text": "WBS Dictionary", "id": "chapter-11-project-management-and-pmp-frameworks-wbs-dictionary" }, { "level": 3, "text": "So What for Managers", "id": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-11-project-management-and-pmp-frameworks-connections-2" }, { "level": 2, "text": "3. Critical Path Method (CPM) & Gantt Charts", "id": "chapter-11-project-management-and-pmp-frameworks-3-critical-path-method-cpm-gantt-charts" }, { "level": 3, "text": "Overview", "id": "chapter-11-project-management-and-pmp-frameworks-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-3" }, { "level": 4, "text": "Critical Path Method (CPM)", "id": "chapter-11-project-management-and-pmp-frameworks-critical-path-method-cpm" }, { "level": 3, "text": "CPM Example", "id": "chapter-11-project-management-and-pmp-frameworks-cpm-example" }, { "level": 3, "text": "Gantt Chart", "id": "chapter-11-project-management-and-pmp-frameworks-gantt-chart" }, { "level": 3, "text": "So What for Managers", "id": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-11-project-management-and-pmp-frameworks-connections-3" }, { "level": 2, "text": "4. Earned Value Management (EVM)", "id": "chapter-11-project-management-and-pmp-frameworks-4-earned-value-management-evm" }, { "level": 3, "text": "Overview", "id": "chapter-11-project-management-and-pmp-frameworks-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-4" }, { "level": 3, "text": "Key Metrics", "id": "chapter-11-project-management-and-pmp-frameworks-key-metrics" }, { "level": 3, "text": "EVM Example", "id": "chapter-11-project-management-and-pmp-frameworks-evm-example" }, { "level": 3, "text": "EVM Dashboard (Visual)", "id": "chapter-11-project-management-and-pmp-frameworks-evm-dashboard-visual" }, { "level": 3, "text": "So What for Managers", "id": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-11-project-management-and-pmp-frameworks-connections-4" }, { "level": 2, "text": "5. Risk Management Framework", "id": "chapter-11-project-management-and-pmp-frameworks-5-risk-management-framework" }, { "level": 3, "text": "Overview", "id": "chapter-11-project-management-and-pmp-frameworks-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-5" }, { "level": 4, "text": "Risk Management Process", "id": "chapter-11-project-management-and-pmp-frameworks-risk-management-process" }, { "level": 3, "text": "Risk Register Template", "id": "chapter-11-project-management-and-pmp-frameworks-risk-register-template" }, { "level": 3, "text": "Risk Response Strategies", "id": "chapter-11-project-management-and-pmp-frameworks-risk-response-strategies" }, { "level": 3, "text": "Quantitative Risk Analysis", "id": "chapter-11-project-management-and-pmp-frameworks-quantitative-risk-analysis" }, { "level": 3, "text": "Risk Monitoring", "id": "chapter-11-project-management-and-pmp-frameworks-risk-monitoring" }, { "level": 3, "text": "So What for Managers", "id": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-11-project-management-and-pmp-frameworks-connections-5" }, { "level": 2, "text": "6. Stakeholder Management (PMBOK context; constructed categories)", "id": "chapter-11-project-management-and-pmp-frameworks-6-stakeholder-management-pmbok-context-constructed-categories" }, { "level": 3, "text": "Overview", "id": "chapter-11-project-management-and-pmp-frameworks-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-6" }, { "level": 3, "text": "Stakeholder Identification", "id": "chapter-11-project-management-and-pmp-frameworks-stakeholder-identification" }, { "level": 3, "text": "Stakeholder Analysis Matrix", "id": "chapter-11-project-management-and-pmp-frameworks-stakeholder-analysis-matrix" }, { "level": 3, "text": "Engagement Strategies", "id": "chapter-11-project-management-and-pmp-frameworks-engagement-strategies" }, { "level": 3, "text": "Communication Plan", "id": "chapter-11-project-management-and-pmp-frameworks-communication-plan" }, { "level": 3, "text": "So What for Managers", "id": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-11-project-management-and-pmp-frameworks-connections-6" }, { "level": 2, "text": "7. Agile/Scrum Framework", "id": "chapter-11-project-management-and-pmp-frameworks-7-agile-scrum-framework" }, { "level": 3, "text": "Overview", "id": "chapter-11-project-management-and-pmp-frameworks-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-7" }, { "level": 3, "text": "Constructed two-week team cadence", "id": "chapter-11-project-management-and-pmp-frameworks-constructed-two-week-team-cadence" }, { "level": 3, "text": "Optional user-story template", "id": "chapter-11-project-management-and-pmp-frameworks-optional-user-story-template" }, { "level": 3, "text": "Optional relative estimation", "id": "chapter-11-project-management-and-pmp-frameworks-optional-relative-estimation" }, { "level": 3, "text": "So What for Managers", "id": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-11-project-management-and-pmp-frameworks-connections-7" }, { "level": 2, "text": "8. Flow Board and WIP Policy (Constructed)", "id": "chapter-11-project-management-and-pmp-frameworks-8-flow-board-and-wip-policy-constructed" }, { "level": 3, "text": "Overview", "id": "chapter-11-project-management-and-pmp-frameworks-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-8" }, { "level": 3, "text": "Example flow board", "id": "chapter-11-project-management-and-pmp-frameworks-example-flow-board" }, { "level": 3, "text": "WIP (Work in Progress) Limits", "id": "chapter-11-project-management-and-pmp-frameworks-wip-work-in-progress-limits" }, { "level": 3, "text": "Flow Metrics (constructed)", "id": "chapter-11-project-management-and-pmp-frameworks-flow-metrics-constructed" }, { "level": 3, "text": "So What for Managers", "id": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-11-project-management-and-pmp-frameworks-connections-8" }, { "level": 2, "text": "9. Change Control Process", "id": "chapter-11-project-management-and-pmp-frameworks-9-change-control-process" }, { "level": 3, "text": "Overview", "id": "chapter-11-project-management-and-pmp-frameworks-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-9" }, { "level": 4, "text": "Change Request Workflow", "id": "chapter-11-project-management-and-pmp-frameworks-change-request-workflow" }, { "level": 3, "text": "Possible change authority", "id": "chapter-11-project-management-and-pmp-frameworks-possible-change-authority" }, { "level": 3, "text": "Change Request Form", "id": "chapter-11-project-management-and-pmp-frameworks-change-request-form" }, { "level": 3, "text": "So What for Managers", "id": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-11-project-management-and-pmp-frameworks-connections-9" }, { "level": 2, "text": "10. Project Charter Template", "id": "chapter-11-project-management-and-pmp-frameworks-10-project-charter-template" }, { "level": 3, "text": "Overview", "id": "chapter-11-project-management-and-pmp-frameworks-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-apply-10" }, { "level": 3, "text": "Project Charter Contents", "id": "chapter-11-project-management-and-pmp-frameworks-project-charter-contents" }, { "level": 3, "text": "So What for Managers", "id": "chapter-11-project-management-and-pmp-frameworks-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-11-project-management-and-pmp-frameworks-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-11-project-management-and-pmp-frameworks-connections-10" }, { "level": 2, "text": "How To Get Started: Choosing Your Project Methodology", "id": "chapter-11-project-management-and-pmp-frameworks-how-to-get-started-choosing-your-project-methodology" }, { "level": 3, "text": "Rapid tailoring workshop", "id": "chapter-11-project-management-and-pmp-frameworks-rapid-tailoring-workshop" }, { "level": 3, "text": "Detailed Version: Full Project Initiation (6-8 weeks)", "id": "chapter-11-project-management-and-pmp-frameworks-detailed-version-full-project-initiation-6-8-weeks" }, { "level": 4, "text": "Phase 1: Requirements & Charter (Weeks 1-3)", "id": "chapter-11-project-management-and-pmp-frameworks-phase-1-requirements-charter-weeks-1-3" }, { "level": 4, "text": "Phase 2: Project Setup & Kick-off (Weeks 4-6)", "id": "chapter-11-project-management-and-pmp-frameworks-phase-2-project-setup-kick-off-weeks-4-6" }, { "level": 4, "text": "Phase 3: Execution (Months 2-6+)", "id": "chapter-11-project-management-and-pmp-frameworks-phase-3-execution-months-2-6" }, { "level": 3, "text": "Common Pitfalls & How to Avoid Them", "id": "chapter-11-project-management-and-pmp-frameworks-common-pitfalls-how-to-avoid-them" }, { "level": 4, "text": "Waterfall Pitfalls", "id": "chapter-11-project-management-and-pmp-frameworks-waterfall-pitfalls" }, { "level": 4, "text": "Agile Pitfalls", "id": "chapter-11-project-management-and-pmp-frameworks-agile-pitfalls" }, { "level": 3, "text": "Measurement: How to Know You're On Track", "id": "chapter-11-project-management-and-pmp-frameworks-measurement-how-to-know-you-re-on-track" }, { "level": 3, "text": "Red Flags: When Methodology is Wrong", "id": "chapter-11-project-management-and-pmp-frameworks-red-flags-when-methodology-is-wrong" }, { "level": 2, "text": "Why This Matters: Mental Models & Project Wisdom", "id": "chapter-11-project-management-and-pmp-frameworks-why-this-matters-mental-models-project-wisdom" }, { "level": 3, "text": "Mental Models: Why Project Methodologies Work", "id": "chapter-11-project-management-and-pmp-frameworks-mental-models-why-project-methodologies-work" }, { "level": 4, "text": "1. Why Waterfall Works: Predictable, Sequential Dependencies", "id": "chapter-11-project-management-and-pmp-frameworks-1-why-waterfall-works-predictable-sequential-dependencies" }, { "level": 4, "text": "2. Why Agile Works: Learning and Adaptation Under Uncertainty", "id": "chapter-11-project-management-and-pmp-frameworks-2-why-agile-works-learning-and-adaptation-under-uncertainty" }, { "level": 4, "text": "3. Why Hybrid Works (and Why It's Hard): Combining Disciplines", "id": "chapter-11-project-management-and-pmp-frameworks-3-why-hybrid-works-and-why-it-s-hard-combining-disciplines" }, { "level": 4, "text": "4. Why Critical Path Matters: Resource-Constrained Execution", "id": "chapter-11-project-management-and-pmp-frameworks-4-why-critical-path-matters-resource-constrained-execution" }, { "level": 3, "text": "Composite Failure Examples: When Project Methodologies Failed", "id": "chapter-11-project-management-and-pmp-frameworks-composite-failure-examples-when-project-methodologies-failed" }, { "level": 4, "text": "Case 1: Healthcare IT Project Failure - Methodology Mismatch", "id": "chapter-11-project-management-and-pmp-frameworks-case-1-healthcare-it-project-failure-methodology-mismatch" }, { "level": 4, "text": "Case 2: Software Project Death March - Waterfall Applied to Uncertain Work", "id": "chapter-11-project-management-and-pmp-frameworks-case-2-software-project-death-march-waterfall-applied-to-uncertain-work" }, { "level": 4, "text": "Case 3: Agile Chaos - Applied Without Discipline to Complex Delivery", "id": "chapter-11-project-management-and-pmp-frameworks-case-3-agile-chaos-applied-without-discipline-to-complex-delivery" }, { "level": 3, "text": "Competing Schools: Different Approaches to Project Management", "id": "chapter-11-project-management-and-pmp-frameworks-competing-schools-different-approaches-to-project-management" }, { "level": 4, "text": "1. Predictive vs. Adaptive Project Management", "id": "chapter-11-project-management-and-pmp-frameworks-1-predictive-vs-adaptive-project-management" }, { "level": 4, "text": "2. Command-and-Control vs. Self-Organizing Teams", "id": "chapter-11-project-management-and-pmp-frameworks-2-command-and-control-vs-self-organizing-teams" }, { "level": 4, "text": "3. Phases vs. Sprints (When to Use Each)", "id": "chapter-11-project-management-and-pmp-frameworks-3-phases-vs-sprints-when-to-use-each" }, { "level": 3, "text": "Context-Dependent Delivery Design", "id": "chapter-11-project-management-and-pmp-frameworks-context-dependent-delivery-design" }, { "level": 2, "text": "Operating Manual: Your Project Execution Playbook", "id": "chapter-11-project-management-and-pmp-frameworks-operating-manual-your-project-execution-playbook" }, { "level": 3, "text": "Delivery-System Tailoring", "id": "chapter-11-project-management-and-pmp-frameworks-delivery-system-tailoring" }, { "level": 2, "text": "WATERFALL TRACK: Your Phased Project Playbook", "id": "chapter-11-project-management-and-pmp-frameworks-waterfall-track-your-phased-project-playbook" }, { "level": 3, "text": "Phase 1: Initiation (Weeks 1-2, 40-60 hours)", "id": "chapter-11-project-management-and-pmp-frameworks-phase-1-initiation-weeks-1-2-40-60-hours" }, { "level": 3, "text": "Phase 2: Planning (Weeks 3-8, 200-300 hours)", "id": "chapter-11-project-management-and-pmp-frameworks-phase-2-planning-weeks-3-8-200-300-hours" }, { "level": 3, "text": "Phase 3: Execution (Variable, 3-12 months depending on project)", "id": "chapter-11-project-management-and-pmp-frameworks-phase-3-execution-variable-3-12-months-depending-on-project" }, { "level": 3, "text": "Phase 4: Monitoring & Controlling (Ongoing, parallel to Execution)", "id": "chapter-11-project-management-and-pmp-frameworks-phase-4-monitoring-controlling-ongoing-parallel-to-execution" }, { "level": 3, "text": "Phase 5: Closing (Weeks 1-2 after go-live, 20-40 hours)", "id": "chapter-11-project-management-and-pmp-frameworks-phase-5-closing-weeks-1-2-after-go-live-20-40-hours" }, { "level": 2, "text": "AGILE/SCRUM TRACK: Your Iterative Project Playbook", "id": "chapter-11-project-management-and-pmp-frameworks-agile-scrum-track-your-iterative-project-playbook" }, { "level": 3, "text": "Setup Phase (Weeks 1-2, 40-60 hours)", "id": "chapter-11-project-management-and-pmp-frameworks-setup-phase-weeks-1-2-40-60-hours" }, { "level": 3, "text": "Sprint Execution (Ongoing, 2-week sprints example)", "id": "chapter-11-project-management-and-pmp-frameworks-sprint-execution-ongoing-2-week-sprints-example" }, { "level": 3, "text": "Release Planning (Parallel to Sprints, Every 3-6 Sprints)", "id": "chapter-11-project-management-and-pmp-frameworks-release-planning-parallel-to-sprints-every-3-6-sprints" }, { "level": 3, "text": "Agile Retrospectives & Learning (Ongoing)", "id": "chapter-11-project-management-and-pmp-frameworks-agile-retrospectives-learning-ongoing" }, { "level": 2, "text": "Summary: Delivery Tailoring Matrix", "id": "chapter-11-project-management-and-pmp-frameworks-summary-delivery-tailoring-matrix" }, { "level": 2, "text": "When to Use This Operating Manual", "id": "chapter-11-project-management-and-pmp-frameworks-when-to-use-this-operating-manual" }, { "level": 2, "text": "Chapter Summary", "id": "chapter-11-project-management-and-pmp-frameworks-chapter-summary" } ], "figures": [ { "id": "chapter-11-project-management-and-pmp-frameworks-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "50e029de68c9b82cfb71d7b52f1e2fd002d28ac38d6a007d8f1b8222edb4039c" }, { "id": "chapter-11-project-management-and-pmp-frameworks-figure-2", "type": "mermaid", "caption": "Figure 11.2 — Constructed CPM dependency network. Numbers in parentheses are durations in weeks.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "d6b2ddbe023f3a0866dc35f8466b950e03fcfab122e1ae77e5aba89f30157597" }, { "id": "chapter-11-project-management-and-pmp-frameworks-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C11-S01" ], "provenanceStatus": "constructed", "checksum": "cb72e1f44888d2ace8f678ea3d3fb4d97cae22866b4fc1dd6f1dc0244129165c" }, { "id": "chapter-11-project-management-and-pmp-frameworks-figure-4", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C11-S01" ], "provenanceStatus": "constructed", "checksum": "e95fc7420359e0ccd0603003585ab1b6ac4a545a3ca73c81463ab32b8044f7a0" } ], "tables": [ { "id": "chapter-11-project-management-and-pmp-frameworks-table-1", "caption": "Table 1. Activity / Tool/Framework / Output", "headers": [ "Activity", "Tool/Framework", "Output" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-2", "caption": "Table 2. Level / WBS code / Illustrative element", "headers": [ "Level", "WBS code", "Illustrative element", "Parent" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 11 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-3", "caption": "Table 3. WBS / Deliverable or work package / Constructed hours", "headers": [ "WBS", "Deliverable or work package", "Constructed hours", "Parent" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-4", "caption": "Table 11.3 — Constructed CPM task register. Durations and dependencies are teaching assumptions for the worked network, not schedule benchmarks.", "headers": [ "Task", "Duration", "Predecessors" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-5", "caption": "Table 11.1 — Constructed schedule timeline. The table is the accessible timeline equivalent of the dependency network; week numbers are discrete teaching periods.", "headers": [ "Task", "Start week", "Finish week", "Duration", "Critical?", "Dependency note" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-6", "caption": "Table 6. Measure / Constructed result / Decision use", "headers": [ "Measure", "Constructed result", "Decision use" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-7", "caption": "Table 11.4 — Constructed risk register. Entries, ordinal scores, owners, and responses are teaching assumptions; define the actual method and authority locally.", "headers": [ "Risk ID", "Risk Description", "Category", "Probability (1-5)", "Impact (1-5)", "Risk Score", "Response Strategy", "Owner", "Status" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-8", "caption": "Table 8. Stakeholder / Role / Power", "headers": [ "Stakeholder", "Role", "Power", "Interest", "Influence", "Attitude", "Strategy" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-9", "caption": "Table 9. Stakeholder / Message / Frequency", "headers": [ "Stakeholder", "Message", "Frequency", "Medium", "Owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-10", "caption": "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.", "headers": [ "Backlog", "To Do", "In Progress", "Code Review", "Testing", "Done" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-11", "caption": "Table 11. Field / Description", "headers": [ "Field", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 16 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-12", "caption": "Table 11.7 — Constructed charter stakeholder register. Names, roles, and responsibilities are fictional teaching assumptions.", "headers": [ "Name", "Role", "Responsibility" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-13", "caption": "Table 11.8 — Constructed charter milestone register. Dates are fictional teaching assumptions.", "headers": [ "Milestone", "Target Date" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-14", "caption": "Table 11.9 — Constructed charter budget. Amounts and the total are fictional teaching assumptions; the line items sum to $1.2 million including the illustrative reserve.", "headers": [ "Category", "Amount" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-15", "caption": "Table 15. Dimension / Questions / Possible design response", "headers": [ "Dimension", "Questions", "Possible design response" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-16", "caption": "Table 16. Context signal / Questions for delivery design", "headers": [ "Context signal", "Questions for delivery design" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-17", "caption": "Table 17. Dimension / Questions to resolve", "headers": [ "Dimension", "Questions to resolve" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-18", "caption": "Table 18. Stakeholder Group / Frequency / Medium", "headers": [ "Stakeholder Group", "Frequency", "Medium", "Content", "Owner" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-19", "caption": "Table 19. Dimension / Predictive practice can help when... / Adaptive practice can help when...", "headers": [ "Dimension", "Predictive practice can help when...", "Adaptive practice can help when...", "Control that remains necessary" ], "sourceIds": [ "BB-C11-S01", "BB-C11-S05", "BB-C11-S06" ], "provenanceStatus": "source-linked", "rowCount": 6 }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-20", "caption": "Table 11.10 — Predictive and adaptive practices. Constructed comparison; select practices independently from the project's evidence and constraints.", "headers": [ "Aspect", "Waterfall", "Agile" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-11-project-management-and-pmp-frameworks.html", "outboundSlugs": [ "chapter-04-financial-analysis-and-valuation", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-12-client-management" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-02-business-law-governance-and-ethics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-12-client-management", "chapter-17-leading-digital-transformation", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-12-client-management", "slug": "chapter-12-client-management", "kind": "chapter", "number": 12, "title": "Client Management", "part": "Part 2: Management Consulting Toolkit", "summary": "Stakeholder management, RACI, executive communication, project scoping, feedback, and difficult conversations.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "relatedSlugs": [ "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-11-project-management-and-pmp-frameworks" ], "sourcePath": "src/part2-consulting/12-client-management.md", "outputPath": "index.html#chapter-12-client-management", "markdownPath": "markdown/chapter-12-client-management.md", "wordCount": 20808, "checksum": "443b6ae59c654d60be3c0fa697d548739360d858d9f69eda6c191054dcf6b7a2", "sourceIds": [ "BB-C12-S01", "BB-C12-S02", "BB-C12-S03", "BB-C12-S04", "BB-C12-S05", "BB-C12-S06", "BB-C07-S13", "BB-C07-S14" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-12-client-management-executive-summary" }, { "level": 3, "text": "Manager Decision Outcomes and Professional-Practice Boundary", "id": "chapter-12-client-management-manager-decision-outcomes-and-professional-practice-boundary" }, { "level": 2, "text": "1. Stakeholder Influence/Interest Matrix", "id": "chapter-12-client-management-1-stakeholder-influence-interest-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-12-client-management-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-12-client-management-how-to-apply" }, { "level": 3, "text": "High Power, High Interest", "id": "chapter-12-client-management-high-power-high-interest" }, { "level": 3, "text": "High Power, Low Interest", "id": "chapter-12-client-management-high-power-low-interest" }, { "level": 3, "text": "Low Power, High Interest", "id": "chapter-12-client-management-low-power-high-interest" }, { "level": 3, "text": "Low Power, Low Interest", "id": "chapter-12-client-management-low-power-low-interest" }, { "level": 3, "text": "So What for Managers", "id": "chapter-12-client-management-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-12-client-management-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-12-client-management-connections" }, { "level": 2, "text": "2. RACI Matrix", "id": "chapter-12-client-management-2-raci-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-12-client-management-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-12-client-management-how-to-apply-2" }, { "level": 3, "text": "Visual Representation:", "id": "chapter-12-client-management-visual-representation" }, { "level": 3, "text": "So What for Managers", "id": "chapter-12-client-management-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-12-client-management-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-12-client-management-connections-2" }, { "level": 2, "text": "3. Executive Presentation Structure", "id": "chapter-12-client-management-3-executive-presentation-structure" }, { "level": 3, "text": "Overview", "id": "chapter-12-client-management-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-12-client-management-how-to-apply-3" }, { "level": 3, "text": "Slide 1: Title & Credibility", "id": "chapter-12-client-management-slide-1-title-credibility" }, { "level": 3, "text": "Slide 2: Business Context (THE PROBLEM)", "id": "chapter-12-client-management-slide-2-business-context-the-problem" }, { "level": 3, "text": "Slide 3: Opportunity/Vision (THE ANSWER)", "id": "chapter-12-client-management-slide-3-opportunity-vision-the-answer" }, { "level": 3, "text": "Slide 4: Strategic Approach (THE HOW)", "id": "chapter-12-client-management-slide-4-strategic-approach-the-how" }, { "level": 3, "text": "Slide 5-8: Key Workstreams (PROOF IT WORKS)", "id": "chapter-12-client-management-slide-5-8-key-workstreams-proof-it-works" }, { "level": 3, "text": "Slide 9: Financial Summary", "id": "chapter-12-client-management-slide-9-financial-summary" }, { "level": 3, "text": "Slide 10: Timeline/Milestones (THE WHEN)", "id": "chapter-12-client-management-slide-10-timeline-milestones-the-when" }, { "level": 3, "text": "Slide 11: Team & Governance", "id": "chapter-12-client-management-slide-11-team-governance" }, { "level": 3, "text": "Slide 12: Top 5 Risks (HONEST ASSESSMENT)", "id": "chapter-12-client-management-slide-12-top-5-risks-honest-assessment" }, { "level": 3, "text": "Slide 13: Next Steps (THE ASK)", "id": "chapter-12-client-management-slide-13-next-steps-the-ask" }, { "level": 3, "text": "Slide 14: Q&A/Backup", "id": "chapter-12-client-management-slide-14-q-a-backup" }, { "level": 3, "text": "Slide 15: Contact Info", "id": "chapter-12-client-management-slide-15-contact-info" }, { "level": 3, "text": "So What for Managers", "id": "chapter-12-client-management-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-12-client-management-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-12-client-management-connections-3" }, { "level": 2, "text": "4. Difficult Conversation Framework", "id": "chapter-12-client-management-4-difficult-conversation-framework" }, { "level": 3, "text": "Overview", "id": "chapter-12-client-management-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-12-client-management-how-to-apply-4" }, { "level": 3, "text": "Step 1: Frame the Issue (Not Accusation)", "id": "chapter-12-client-management-step-1-frame-the-issue-not-accusation" }, { "level": 3, "text": "Step 2: Listen for Context", "id": "chapter-12-client-management-step-2-listen-for-context" }, { "level": 3, "text": "Step 3: Share Your Perspective", "id": "chapter-12-client-management-step-3-share-your-perspective" }, { "level": 3, "text": "Step 4: Problem-Solve Together", "id": "chapter-12-client-management-step-4-problem-solve-together" }, { "level": 3, "text": "Step 5: Agreement & Follow-Up", "id": "chapter-12-client-management-step-5-agreement-follow-up" }, { "level": 3, "text": "So What for Managers", "id": "chapter-12-client-management-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-12-client-management-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-12-client-management-connections-4" }, { "level": 2, "text": "5. Project Scoping Template", "id": "chapter-12-client-management-5-project-scoping-template" }, { "level": 3, "text": "Overview", "id": "chapter-12-client-management-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-12-client-management-how-to-apply-5" }, { "level": 3, "text": "Project Charter", "id": "chapter-12-client-management-project-charter" }, { "level": 3, "text": "Business Objective", "id": "chapter-12-client-management-business-objective" }, { "level": 3, "text": "Scope - INCLUDED", "id": "chapter-12-client-management-scope-included" }, { "level": 3, "text": "Scope - NOT INCLUDED", "id": "chapter-12-client-management-scope-not-included" }, { "level": 3, "text": "Key Assumptions", "id": "chapter-12-client-management-key-assumptions" }, { "level": 3, "text": "Dependencies", "id": "chapter-12-client-management-dependencies" }, { "level": 3, "text": "Timeline", "id": "chapter-12-client-management-timeline" }, { "level": 3, "text": "Budget", "id": "chapter-12-client-management-budget" }, { "level": 3, "text": "Risks & Mitigation", "id": "chapter-12-client-management-risks-mitigation" }, { "level": 3, "text": "So What for Managers", "id": "chapter-12-client-management-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-12-client-management-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-12-client-management-connections-5" }, { "level": 2, "text": "6. Statement of Work (SOW) Components", "id": "chapter-12-client-management-6-statement-of-work-sow-components" }, { "level": 3, "text": "Overview", "id": "chapter-12-client-management-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-12-client-management-how-to-apply-6" }, { "level": 3, "text": "1. Services Description", "id": "chapter-12-client-management-1-services-description" }, { "level": 3, "text": "2. Deliverables (Specific & Measurable)", "id": "chapter-12-client-management-2-deliverables-specific-measurable" }, { "level": 3, "text": "3. Timeline", "id": "chapter-12-client-management-3-timeline" }, { "level": 3, "text": "4. Fees & Expenses", "id": "chapter-12-client-management-4-fees-expenses" }, { "level": 3, "text": "5. Assumptions", "id": "chapter-12-client-management-5-assumptions" }, { "level": 3, "text": "6. Exclusions (What's NOT Included)", "id": "chapter-12-client-management-6-exclusions-what-s-not-included" }, { "level": 3, "text": "7. Governance", "id": "chapter-12-client-management-7-governance" }, { "level": 3, "text": "8. Confidentiality, data, records, and IP", "id": "chapter-12-client-management-8-confidentiality-data-records-and-ip" }, { "level": 3, "text": "9. Term, suspension, and termination", "id": "chapter-12-client-management-9-term-suspension-and-termination" }, { "level": 3, "text": "10. Authority and execution", "id": "chapter-12-client-management-10-authority-and-execution" }, { "level": 3, "text": "So What for Managers", "id": "chapter-12-client-management-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-12-client-management-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-12-client-management-connections-6" }, { "level": 2, "text": "7. Risk Register & Mitigation", "id": "chapter-12-client-management-7-risk-register-mitigation" }, { "level": 3, "text": "Overview", "id": "chapter-12-client-management-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-12-client-management-how-to-apply-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-12-client-management-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-12-client-management-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-12-client-management-connections-7" }, { "level": 2, "text": "8. Change Request Process", "id": "chapter-12-client-management-8-change-request-process" }, { "level": 3, "text": "Overview", "id": "chapter-12-client-management-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-12-client-management-how-to-apply-8" }, { "level": 3, "text": "Gate 1: Request Submission", "id": "chapter-12-client-management-gate-1-request-submission" }, { "level": 3, "text": "Gate 2: Evaluation", "id": "chapter-12-client-management-gate-2-evaluation" }, { "level": 3, "text": "Gate 3: Documentation & Execution", "id": "chapter-12-client-management-gate-3-documentation-execution" }, { "level": 3, "text": "So What for Managers", "id": "chapter-12-client-management-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-12-client-management-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-12-client-management-connections-8" }, { "level": 2, "text": "9. Feedback Collection Methods", "id": "chapter-12-client-management-9-feedback-collection-methods" }, { "level": 3, "text": "Overview", "id": "chapter-12-client-management-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-12-client-management-how-to-apply-9" }, { "level": 3, "text": "Tier 1: Real-Time Feedback (In meetings)", "id": "chapter-12-client-management-tier-1-real-time-feedback-in-meetings" }, { "level": 3, "text": "Tier 2: Weekly Pulse Check (2-3 questions)", "id": "chapter-12-client-management-tier-2-weekly-pulse-check-2-3-questions" }, { "level": 3, "text": "Tier 3: Mid-Project Feedback (Formal)", "id": "chapter-12-client-management-tier-3-mid-project-feedback-formal" }, { "level": 3, "text": "Tier 4: Retrospective (Post-Project)", "id": "chapter-12-client-management-tier-4-retrospective-post-project" }, { "level": 3, "text": "So What for Managers", "id": "chapter-12-client-management-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-12-client-management-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-12-client-management-connections-9" }, { "level": 2, "text": "10. Relationship Mapping Tool", "id": "chapter-12-client-management-10-relationship-mapping-tool" }, { "level": 3, "text": "Overview", "id": "chapter-12-client-management-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-12-client-management-how-to-apply-10" }, { "level": 3, "text": "Power/Influence Connections", "id": "chapter-12-client-management-power-influence-connections" }, { "level": 3, "text": "Individual Assessments", "id": "chapter-12-client-management-individual-assessments" }, { "level": 3, "text": "Coalition Strategy", "id": "chapter-12-client-management-coalition-strategy" }, { "level": 3, "text": "Influence Tactics by Stakeholder Type", "id": "chapter-12-client-management-influence-tactics-by-stakeholder-type" }, { "level": 3, "text": "So What for Managers", "id": "chapter-12-client-management-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-12-client-management-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-12-client-management-connections-10" }, { "level": 2, "text": "Why This Matters: Mental Models & Client Wisdom", "id": "chapter-12-client-management-why-this-matters-mental-models-client-wisdom" }, { "level": 3, "text": "Mental Models: Why Client Management Frameworks Work", "id": "chapter-12-client-management-mental-models-why-client-management-frameworks-work" }, { "level": 4, "text": "1. What RACI can and cannot clarify", "id": "chapter-12-client-management-1-what-raci-can-and-cannot-clarify" }, { "level": 4, "text": "2. Why Stakeholder Mapping Works: Influence and Interest Dynamics", "id": "chapter-12-client-management-2-why-stakeholder-mapping-works-influence-and-interest-dynamics" }, { "level": 4, "text": "3. Why Communication Cadences Work: Expectation Management", "id": "chapter-12-client-management-3-why-communication-cadences-work-expectation-management" }, { "level": 4, "text": "4. Why Escalation Protocols Work: Rapid Decision-Making", "id": "chapter-12-client-management-4-why-escalation-protocols-work-rapid-decision-making" }, { "level": 3, "text": "Composite Teaching Scenarios: When Client Management Breaks Down", "id": "chapter-12-client-management-composite-teaching-scenarios-when-client-management-breaks-down" }, { "level": 4, "text": "Composite Case 1: Unclear Accountability", "id": "chapter-12-client-management-composite-case-1-unclear-accountability" }, { "level": 4, "text": "Composite Case 2: Scope Expansion and Stakeholder Misalignment", "id": "chapter-12-client-management-composite-case-2-scope-expansion-and-stakeholder-misalignment" }, { "level": 4, "text": "Case 3: Executive Decision Stall - Escalation Path Missed", "id": "chapter-12-client-management-case-3-executive-decision-stall-escalation-path-missed" }, { "level": 3, "text": "Competing Schools: Different Philosophies for Client Management", "id": "chapter-12-client-management-competing-schools-different-philosophies-for-client-management" }, { "level": 4, "text": "1. Stakeholder-Centric vs. Task-Centric Management", "id": "chapter-12-client-management-1-stakeholder-centric-vs-task-centric-management" }, { "level": 4, "text": "2. Formal Governance vs. Relationship-Based Trust", "id": "chapter-12-client-management-2-formal-governance-vs-relationship-based-trust" }, { "level": 4, "text": "3. Frequent Communication vs. Minimal Overhead", "id": "chapter-12-client-management-3-frequent-communication-vs-minimal-overhead" }, { "level": 3, "text": "Stage Dependency: How Client Management Evolves with Scale", "id": "chapter-12-client-management-stage-dependency-how-client-management-evolves-with-scale" }, { "level": 4, "text": "Startup: Informal, Relationship-Based Management", "id": "chapter-12-client-management-startup-informal-relationship-based-management" }, { "level": 4, "text": "Scale-Up: Emerging Formal Structures", "id": "chapter-12-client-management-scale-up-emerging-formal-structures" }, { "level": 4, "text": "Enterprise: Formal Governance, Multiple Stakeholders", "id": "chapter-12-client-management-enterprise-formal-governance-multiple-stakeholders" }, { "level": 2, "text": "Contrarian Thinking: When Client Management Orthodoxy Fails", "id": "chapter-12-client-management-contrarian-thinking-when-client-management-orthodoxy-fails" }, { "level": 3, "text": "1. The Client Is Not Always Right", "id": "chapter-12-client-management-1-the-client-is-not-always-right" }, { "level": 3, "text": "2. Over-Communication Can Be as Harmful as Under-Communication", "id": "chapter-12-client-management-2-over-communication-can-be-as-harmful-as-under-communication" }, { "level": 3, "text": "3. Stakeholder Alignment Is Often Impossible (And That's OK)", "id": "chapter-12-client-management-3-stakeholder-alignment-is-often-impossible-and-that-s-ok" }, { "level": 3, "text": "4. Client Satisfaction ≠ Project Success", "id": "chapter-12-client-management-4-client-satisfaction-project-success" }, { "level": 3, "text": "5. Re-scope, suspend, or exit an engagement through governance", "id": "chapter-12-client-management-5-re-scope-suspend-or-exit-an-engagement-through-governance" }, { "level": 2, "text": "Input/Output Interlinkages: How Client Management Connects to Other Business Functions", "id": "chapter-12-client-management-input-output-interlinkages-how-client-management-connects-to-other-business-functions" }, { "level": 3, "text": "Client Management as a System", "id": "chapter-12-client-management-client-management-as-a-system" }, { "level": 3, "text": "Example: Enterprise Software Implementation", "id": "chapter-12-client-management-example-enterprise-software-implementation" }, { "level": 3, "text": "Example: Management Consulting Engagement", "id": "chapter-12-client-management-example-management-consulting-engagement" }, { "level": 3, "text": "Cross-Functional Client Management Challenges", "id": "chapter-12-client-management-cross-functional-client-management-challenges" }, { "level": 2, "text": "Enhanced Troubleshooting: Navigating Difficult Client Situations", "id": "chapter-12-client-management-enhanced-troubleshooting-navigating-difficult-client-situations" }, { "level": 3, "text": "Problem: Client Ghosting (No Responses to Emails/Calls)", "id": "chapter-12-client-management-problem-client-ghosting-no-responses-to-emails-calls" }, { "level": 3, "text": "Problem: Client Constantly Changes Requirements (Scope Creep)", "id": "chapter-12-client-management-problem-client-constantly-changes-requirements-scope-creep" }, { "level": 3, "text": "Problem: Client Rejects Your Recommendations (Even Though Data Supports It)", "id": "chapter-12-client-management-problem-client-rejects-your-recommendations-even-though-data-supports-it" }, { "level": 3, "text": "Problem: Project Stuck in Analysis Paralysis (Client Won't Make Decisions)", "id": "chapter-12-client-management-problem-project-stuck-in-analysis-paralysis-client-won-t-make-decisions" }, { "level": 2, "text": "Summary: Client Management Toolkit", "id": "chapter-12-client-management-summary-client-management-toolkit" }, { "level": 2, "text": "How To Get Started: Managing Your Client Relationship", "id": "chapter-12-client-management-how-to-get-started-managing-your-client-relationship" }, { "level": 3, "text": "Quick Version: Rapid Stakeholder Setup (2-3 days)", "id": "chapter-12-client-management-quick-version-rapid-stakeholder-setup-2-3-days" }, { "level": 4, "text": "Day 1: Stakeholder Identification & Mapping (2-3 hours)", "id": "chapter-12-client-management-day-1-stakeholder-identification-mapping-2-3-hours" }, { "level": 4, "text": "Day 2: RACI & Scoping (2-3 hours)", "id": "chapter-12-client-management-day-2-raci-scoping-2-3-hours" }, { "level": 4, "text": "Day 3: Project Scope & Risk (2-3 hours)", "id": "chapter-12-client-management-day-3-project-scope-risk-2-3-hours" }, { "level": 3, "text": "Detailed Version: Full Client Management Setup (2-4 weeks)", "id": "chapter-12-client-management-detailed-version-full-client-management-setup-2-4-weeks" }, { "level": 4, "text": "Week 1: Discovery & Mapping", "id": "chapter-12-client-management-week-1-discovery-mapping" }, { "level": 4, "text": "Week 2: Formal Scoping & Relationship Building", "id": "chapter-12-client-management-week-2-formal-scoping-relationship-building" }, { "level": 4, "text": "Week 3-4: Ongoing Management", "id": "chapter-12-client-management-week-3-4-ongoing-management" }, { "level": 3, "text": "Common Pitfalls & How to Avoid Them", "id": "chapter-12-client-management-common-pitfalls-how-to-avoid-them" }, { "level": 4, "text": "Pitfall 1: Wrong RACI, Unclear Accountability", "id": "chapter-12-client-management-pitfall-1-wrong-raci-unclear-accountability" }, { "level": 4, "text": "Pitfall 2: Not Surfacing Resistance Early", "id": "chapter-12-client-management-pitfall-2-not-surfacing-resistance-early" }, { "level": 4, "text": "Pitfall 3: Absent Sponsor", "id": "chapter-12-client-management-pitfall-3-absent-sponsor" }, { "level": 4, "text": "Pitfall 4: Scope Creep Without Change Management", "id": "chapter-12-client-management-pitfall-4-scope-creep-without-change-management" }, { "level": 4, "text": "Pitfall 5: Not Closing Feedback Loop", "id": "chapter-12-client-management-pitfall-5-not-closing-feedback-loop" }, { "level": 3, "text": "Measurement: How to Know Stakeholder Management is Working", "id": "chapter-12-client-management-measurement-how-to-know-stakeholder-management-is-working" }, { "level": 3, "text": "Red Flags: When Stakeholder Management is Failing", "id": "chapter-12-client-management-red-flags-when-stakeholder-management-is-failing" }, { "level": 2, "text": "Constructed Case Example: Enterprise Transformation Program", "id": "chapter-12-client-management-constructed-case-example-enterprise-transformation-program" }, { "level": 2, "text": "Operating Manual: Your Client Engagement Playbook", "id": "chapter-12-client-management-operating-manual-your-client-engagement-playbook" }, { "level": 3, "text": "Weeks 1-2: Stakeholder Mapping & Engagement Planning", "id": "chapter-12-client-management-weeks-1-2-stakeholder-mapping-engagement-planning" }, { "level": 4, "text": "Week 1: Stakeholder Identification & Power/Interest Assessment (16-20 hours)", "id": "chapter-12-client-management-week-1-stakeholder-identification-power-interest-assessment-16-20-hours" }, { "level": 4, "text": "Week 2: RACI Development & Communication Planning (16-20 hours)", "id": "chapter-12-client-management-week-2-raci-development-communication-planning-16-20-hours" }, { "level": 3, "text": "Week 3: Stakeholder Kickoff & Alignment", "id": "chapter-12-client-management-week-3-stakeholder-kickoff-alignment" }, { "level": 4, "text": "Stakeholder Kickoff Meeting (2-3 hours)", "id": "chapter-12-client-management-stakeholder-kickoff-meeting-2-3-hours" }, { "level": 3, "text": "Weeks 4+: Ongoing Stakeholder Engagement (Recurring Cadence)", "id": "chapter-12-client-management-weeks-4-ongoing-stakeholder-engagement-recurring-cadence" }, { "level": 4, "text": "Weekly Activities (3-5 hours/week)", "id": "chapter-12-client-management-weekly-activities-3-5-hours-week" }, { "level": 4, "text": "Monthly Activities (6-10 hours/month)", "id": "chapter-12-client-management-monthly-activities-6-10-hours-month" }, { "level": 3, "text": "Difficult Conversations & Conflict Resolution (As Needed)", "id": "chapter-12-client-management-difficult-conversations-conflict-resolution-as-needed" }, { "level": 4, "text": "Negotiation bridge: prepare before the conversation", "id": "chapter-12-client-management-negotiation-bridge-prepare-before-the-conversation" }, { "level": 4, "text": "Applied multiparty role play — constructed service recovery", "id": "chapter-12-client-management-applied-multiparty-role-play-constructed-service-recovery" }, { "level": 4, "text": "Framework for Difficult Conversations", "id": "chapter-12-client-management-framework-for-difficult-conversations" }, { "level": 3, "text": "Measurement Dashboard (Weekly Tracking)", "id": "chapter-12-client-management-measurement-dashboard-weekly-tracking" }, { "level": 3, "text": "Contingency Playbook", "id": "chapter-12-client-management-contingency-playbook" }, { "level": 2, "text": "Summary: Client Management Operating Manual", "id": "chapter-12-client-management-summary-client-management-operating-manual" } ], "figures": [ { "id": "chapter-12-client-management-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C12-S05" ], "provenanceStatus": "source-linked", "checksum": "c3638bbe285bf93bbf7bd238b2678c8a6533ff454c97f7c3efa6e176dc3d493b" }, { "id": "chapter-12-client-management-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C12-S03" ], "provenanceStatus": "constructed", "checksum": "44e0ac91fcfa28cdad515ca590fb9c5f7d6f95ee0e06dc6a411b7eca6ca85a5d" } ], "tables": [ { "id": "chapter-12-client-management-table-1", "caption": "Table 12.2 — Constructed RACI working matrix. Confirm governing authority and required approvals before assigning local RACI labels. [BB-C12-S03]", "headers": [ "Activity or decision", "Product lead", "Engineering lead", "Design lead", "Commercial lead", "Executive authority" ], "sourceIds": [ "BB-C12-S03" ], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-12-client-management-table-2", "caption": "Table 12.6 — Constructed included-scope register. Items, descriptions, owners, and examples are fictional teaching assumptions.", "headers": [ "Item", "Description", "Owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-12-client-management-table-3", "caption": "Table 12.7 — Constructed excluded-scope register. Exclusions and alternatives are fictional teaching assumptions.", "headers": [ "Item", "Why", "Alternative" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-12-client-management-table-4", "caption": "Table 12.8 — Constructed scoping-risk register. Risks and mitigations are fictional teaching assumptions.", "headers": [ "Risk", "Mitigation" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-12-client-management-table-5", "caption": "Table 12.3 — Constructed risk register. Entries, labels, scores, responses, names, and statuses are teaching assumptions, not measured exposure.", "headers": [ "Risk", "Probability", "Impact", "Score", "Mitigation", "Owner", "Status" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-12-client-management-table-6", "caption": "Table 12.1 — Constructed relationship-map hypotheses. The arrows and labels are hypotheses to validate, not facts about motive, authority, or allegiance.", "headers": [ "From", "To", "Relationship hypothesis", "Validation and guardrail" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-12-client-management-table-7", "caption": "Table 7. Stakeholder / Role / Power", "headers": [ "Stakeholder", "Role", "Power", "Interest", "Attitude", "Key Concern" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-12-client-management-table-8", "caption": "Table 12.9 — Constructed scale-context comparison. Stakeholder counts, cadences, and governance examples are not maturity benchmarks.", "headers": [ "Dimension", "Startup", "Scale-Up", "Enterprise" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-12-client-management-table-9", "caption": "Table 9. Stakeholder Tier / Communication Frequency / Method", "headers": [ "Stakeholder Tier", "Communication Frequency", "Method" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-12-client-management-table-10", "caption": "Table 10. Stakeholder / Incentive / Preferred Outcome", "headers": [ "Stakeholder", "Incentive", "Preferred Outcome" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-12-client-management-table-11", "caption": "Table 11. Function / Input Provided / Format", "headers": [ "Function", "Input Provided", "Format" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-12-client-management-table-12", "caption": "Table 12. Function / Output Provided / Impact", "headers": [ "Function", "Output Provided", "Impact" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-12-client-management-table-13", "caption": "Table 13. Function / Input Provided / Format", "headers": [ "Function", "Input Provided", "Format" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-12-client-management-table-14", "caption": "Table 14. Function / Output Provided / Impact", "headers": [ "Function", "Output Provided", "Impact" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-12-client-management-table-15", "caption": "Table 12.5 — Constructed framework-selection aid. Time, cadence, and use examples depend on the decision, evidence, authority, and context; they are not benchmarks.", "headers": [ "Framework", "When to Use", "Time to Apply" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 10 }, { "id": "chapter-12-client-management-table-16", "caption": "Table 16. Stakeholder Group / Frequency / Medium", "headers": [ "Stakeholder Group", "Frequency", "Medium", "Content", "Owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-12-client-management.html", "outboundSlugs": [ "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-11-project-management-and-pmp-frameworks" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-02-business-law-governance-and-ethics", "chapter-07-organizational-behavior-and-leadership", "chapter-09-problem-structuring", "chapter-11-project-management-and-pmp-frameworks", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-13-startup-foundations", "slug": "chapter-13-startup-foundations", "kind": "chapter", "number": 13, "title": "Startup Foundations", "part": "Part 3: Entrepreneurship and Innovation", "summary": "Product-market fit, MVPs, customer discovery, lean startup, founder choices, and early venture design.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "relatedSlugs": [ "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-14-go-to-market-strategy", "chapter-15-fundraising-and-finance", "chapter-21-product-management-and-product-strategy" ], "sourcePath": "src/part3-entrepreneurship/13-startup-foundations.md", "outputPath": "index.html#chapter-13-startup-foundations", "markdownPath": "markdown/chapter-13-startup-foundations.md", "wordCount": 15287, "checksum": "bed5e455fcc7cf2b6c4cfd890a2a3c008c6214db076b9ca390cd1cb7cb84ae0d", "sourceIds": [ "BB-C13-S01", "BB-C13-S02", "BB-C13-S08", "BB-C13-S09", "BB-C13-S04", "BB-C13-S05", "BB-C13-S07", "BB-C13-S11", "BB-C13-S12", "BB-C13-S10", "BB-C13-S06" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-13-startup-foundations-executive-summary" }, { "level": 2, "text": "1. Lean Startup Cycle", "id": "chapter-13-startup-foundations-1-lean-startup-cycle" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections" }, { "level": 2, "text": "2. Customer Development", "id": "chapter-13-startup-foundations-2-customer-development" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections-2" }, { "level": 2, "text": "3. MVP Definition Framework", "id": "chapter-13-startup-foundations-3-mvp-definition-framework" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections-3" }, { "level": 2, "text": "4. Product-Market Fit Metrics", "id": "chapter-13-startup-foundations-4-product-market-fit-metrics" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections-4" }, { "level": 2, "text": "5. Founder-Governance and Agreement Issues", "id": "chapter-13-startup-foundations-5-founder-governance-and-agreement-issues" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections-5" }, { "level": 2, "text": "6. Equity Distribution Model", "id": "chapter-13-startup-foundations-6-equity-distribution-model" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections-6" }, { "level": 2, "text": "7. Burn Rate Calculator", "id": "chapter-13-startup-foundations-7-burn-rate-calculator" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections-7" }, { "level": 2, "text": "8. Runway Planning", "id": "chapter-13-startup-foundations-8-runway-planning" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections-8" }, { "level": 2, "text": "9. Pivot Decision Framework", "id": "chapter-13-startup-foundations-9-pivot-decision-framework" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections-9" }, { "level": 2, "text": "10. Scale-Up Readiness Checklist", "id": "chapter-13-startup-foundations-10-scale-up-readiness-checklist" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections-10" }, { "level": 2, "text": "How To Get Started", "id": "chapter-13-startup-foundations-how-to-get-started" }, { "level": 3, "text": "Quick Version: Rapid MVP Validation (2-3 Weeks)", "id": "chapter-13-startup-foundations-quick-version-rapid-mvp-validation-2-3-weeks" }, { "level": 3, "text": "Detailed Version: Full Startup Launch Cycle (8-12 Weeks)", "id": "chapter-13-startup-foundations-detailed-version-full-startup-launch-cycle-8-12-weeks" }, { "level": 4, "text": "Phase 1: Customer Discovery (Week 1-2)", "id": "chapter-13-startup-foundations-phase-1-customer-discovery-week-1-2" }, { "level": 4, "text": "Phase 2: MVP Design & Build (Week 3-4)", "id": "chapter-13-startup-foundations-phase-2-mvp-design-build-week-3-4" }, { "level": 4, "text": "Phase 3: Customer Validation (Week 5-8)", "id": "chapter-13-startup-foundations-phase-3-customer-validation-week-5-8" }, { "level": 4, "text": "Phase 4: Customer Creation (Week 9-12)", "id": "chapter-13-startup-foundations-phase-4-customer-creation-week-9-12" }, { "level": 4, "text": "Founder-governance and financial planning review", "id": "chapter-13-startup-foundations-founder-governance-and-financial-planning-review" }, { "level": 3, "text": "Common Pitfalls (And How to Avoid Them)", "id": "chapter-13-startup-foundations-common-pitfalls-and-how-to-avoid-them" }, { "level": 3, "text": "Measurement Framework", "id": "chapter-13-startup-foundations-measurement-framework" }, { "level": 3, "text": "Red Flags: When Your Startup Is Off Track", "id": "chapter-13-startup-foundations-red-flags-when-your-startup-is-off-track" }, { "level": 3, "text": "Decision Tree: What To Do After Week 12", "id": "chapter-13-startup-foundations-decision-tree-what-to-do-after-week-12" }, { "level": 2, "text": "11. Venture Pathways: Build, Search, Sponsor, or Corporate Acquisition", "id": "chapter-13-startup-foundations-11-venture-pathways-build-search-sponsor-or-corporate-acquisition" }, { "level": 3, "text": "Overview", "id": "chapter-13-startup-foundations-overview-11" }, { "level": 3, "text": "How to Apply", "id": "chapter-13-startup-foundations-how-to-apply-11" }, { "level": 3, "text": "Manager-facing path comparison", "id": "chapter-13-startup-foundations-manager-facing-path-comparison" }, { "level": 3, "text": "Search economics before deal economics", "id": "chapter-13-startup-foundations-search-economics-before-deal-economics" }, { "level": 3, "text": "Constructed acquisition-screening case: Northstar Field Services", "id": "chapter-13-startup-foundations-constructed-acquisition-screening-case-northstar-field-services" }, { "level": 3, "text": "Applied exercise — acquisition path and screen memo", "id": "chapter-13-startup-foundations-applied-exercise-acquisition-path-and-screen-memo" }, { "level": 3, "text": "So What for Managers", "id": "chapter-13-startup-foundations-so-what-for-managers-11" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-13-startup-foundations-limits-and-critiques-11" }, { "level": 3, "text": "Connections", "id": "chapter-13-startup-foundations-connections-11" }, { "level": 2, "text": "Why This Matters: Mental Models & Startup Wisdom", "id": "chapter-13-startup-foundations-why-this-matters-mental-models-startup-wisdom" }, { "level": 3, "text": "Mental Models: Why Startup Principles Work", "id": "chapter-13-startup-foundations-mental-models-why-startup-principles-work" }, { "level": 4, "text": "1. Customer Discovery: Founder Bias and Reality Testing", "id": "chapter-13-startup-foundations-1-customer-discovery-founder-bias-and-reality-testing" }, { "level": 4, "text": "2. MVP: Lean Experimentation and Minimal Waste", "id": "chapter-13-startup-foundations-2-mvp-lean-experimentation-and-minimal-waste" }, { "level": 4, "text": "3. Unit Economics: Predicting Scalability Before Scale", "id": "chapter-13-startup-foundations-3-unit-economics-predicting-scalability-before-scale" }, { "level": 4, "text": "4. Product-Market Fit: A multi-signal judgment", "id": "chapter-13-startup-foundations-4-product-market-fit-a-multi-signal-judgment" }, { "level": 3, "text": "Constructed composite examples: What Customer Validation Might Miss", "id": "chapter-13-startup-foundations-constructed-composite-examples-what-customer-validation-might-miss" }, { "level": 4, "text": "Case 1: On-Demand Home Services Marketplace - Ignored Unit Economics Until It Was Too Late", "id": "chapter-13-startup-foundations-case-1-on-demand-home-services-marketplace-ignored-unit-economics-until-it-was-too-late" }, { "level": 4, "text": "Case 2: Well-Funded Photo-Sharing App - Failed Product-Market Fit", "id": "chapter-13-startup-foundations-case-2-well-funded-photo-sharing-app-failed-product-market-fit" }, { "level": 4, "text": "Case 3: Connected Juicer Startup - Solved Non-Existent Problem", "id": "chapter-13-startup-foundations-case-3-connected-juicer-startup-solved-non-existent-problem" }, { "level": 3, "text": "Competing Schools: Different Philosophies of Startup Building", "id": "chapter-13-startup-foundations-competing-schools-different-philosophies-of-startup-building" }, { "level": 4, "text": "1. Lean Startup vs. Traditional Business Planning", "id": "chapter-13-startup-foundations-1-lean-startup-vs-traditional-business-planning" }, { "level": 4, "text": "2. Customer-First vs. Technology-First", "id": "chapter-13-startup-foundations-2-customer-first-vs-technology-first" }, { "level": 4, "text": "3. Bootstrap vs. Venture-Backed", "id": "chapter-13-startup-foundations-3-bootstrap-vs-venture-backed" }, { "level": 3, "text": "Stage Dependency: Right Tool for Right Phase", "id": "chapter-13-startup-foundations-stage-dependency-right-tool-for-right-phase" }, { "level": 4, "text": "Pre-Launch: Intense Customer Discovery, Minimal Execution", "id": "chapter-13-startup-foundations-pre-launch-intense-customer-discovery-minimal-execution" }, { "level": 4, "text": "Early Traction: PMF Validation, Unit Economics Focus", "id": "chapter-13-startup-foundations-early-traction-pmf-validation-unit-economics-focus" }, { "level": 4, "text": "Scaling: Repeatable Customer Acquisition, Operational Efficiency", "id": "chapter-13-startup-foundations-scaling-repeatable-customer-acquisition-operational-efficiency" }, { "level": 4, "text": "Late-Stage Growth: Market Expansion, Operational Excellence", "id": "chapter-13-startup-foundations-late-stage-growth-market-expansion-operational-excellence" }, { "level": 2, "text": "Constructed Operating Manual: Your 12-Week MVP Validation Cycle", "id": "chapter-13-startup-foundations-constructed-operating-manual-your-12-week-mvp-validation-cycle" }, { "level": 3, "text": "Overview: 12-Week Timeline", "id": "chapter-13-startup-foundations-overview-12-week-timeline" }, { "level": 3, "text": "Phase 1: Problem Validation (Weeks 1-2)", "id": "chapter-13-startup-foundations-phase-1-problem-validation-weeks-1-2" }, { "level": 4, "text": "Week 1: Customer Discovery", "id": "chapter-13-startup-foundations-week-1-customer-discovery" }, { "level": 4, "text": "Week 2: Problem Analysis & ICP Refinement", "id": "chapter-13-startup-foundations-week-2-problem-analysis-icp-refinement" }, { "level": 3, "text": "Phase 2: Solution Validation (Weeks 3-4)", "id": "chapter-13-startup-foundations-phase-2-solution-validation-weeks-3-4" }, { "level": 4, "text": "Week 3: Solution Concept Development", "id": "chapter-13-startup-foundations-week-3-solution-concept-development" }, { "level": 4, "text": "Week 4: Pricing & Business Model", "id": "chapter-13-startup-foundations-week-4-pricing-business-model" }, { "level": 3, "text": "Phase 3: MVP Build (Weeks 5-8)", "id": "chapter-13-startup-foundations-phase-3-mvp-build-weeks-5-8" }, { "level": 4, "text": "Weeks 5-6: Development Sprint 1", "id": "chapter-13-startup-foundations-weeks-5-6-development-sprint-1" }, { "level": 4, "text": "Weeks 7-8: Beta Testing & Refinement", "id": "chapter-13-startup-foundations-weeks-7-8-beta-testing-refinement" }, { "level": 3, "text": "Phase 4: Launch & Initial Traction (Weeks 9-10)", "id": "chapter-13-startup-foundations-phase-4-launch-initial-traction-weeks-9-10" }, { "level": 4, "text": "Week 9: Soft Launch", "id": "chapter-13-startup-foundations-week-9-soft-launch" }, { "level": 4, "text": "Week 10: Traction & Iteration", "id": "chapter-13-startup-foundations-week-10-traction-iteration" }, { "level": 3, "text": "Phase 5: Early Traction & Planning (Weeks 11-12)", "id": "chapter-13-startup-foundations-phase-5-early-traction-planning-weeks-11-12" }, { "level": 4, "text": "Week 11: Customer Validation & Metrics", "id": "chapter-13-startup-foundations-week-11-customer-validation-metrics" }, { "level": 4, "text": "Week 12: Growth Planning", "id": "chapter-13-startup-foundations-week-12-growth-planning" }, { "level": 3, "text": "Red Flags by Week (Warning Signals)", "id": "chapter-13-startup-foundations-red-flags-by-week-warning-signals" }, { "level": 3, "text": "Resource Requirements (Detailed)", "id": "chapter-13-startup-foundations-resource-requirements-detailed" }, { "level": 3, "text": "Decision Gates (Detailed)", "id": "chapter-13-startup-foundations-decision-gates-detailed" }, { "level": 3, "text": "Contingency Triggers", "id": "chapter-13-startup-foundations-contingency-triggers" }, { "level": 3, "text": "Timeline Variance (Adapt to Your Situation)", "id": "chapter-13-startup-foundations-timeline-variance-adapt-to-your-situation" }, { "level": 3, "text": "Measurement Dashboard (Track Weekly)", "id": "chapter-13-startup-foundations-measurement-dashboard-track-weekly" }, { "level": 3, "text": "Success Stories & Reference Points", "id": "chapter-13-startup-foundations-success-stories-reference-points" }, { "level": 2, "text": "Chapter Summary", "id": "chapter-13-startup-foundations-chapter-summary" } ], "figures": [ { "id": "chapter-13-startup-foundations-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C13-S01" ], "provenanceStatus": "source-linked", "checksum": "92f62aa7965b7e06ad46a9f06b46bfc1dce03bbe376cded44a44fe5f506a303f" }, { "id": "chapter-13-startup-foundations-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "c4a22438bb907aa0fbba84c02fced3feaf4bb48253fa4120d7766a4d1557667f" } ], "tables": [ { "id": "chapter-13-startup-foundations-table-1", "caption": "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.", "headers": [ "Stakeholder", "Shares", "%" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-13-startup-foundations-table-2", "caption": "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.", "headers": [ "Week", "Hypothesis Tested", "Validated (Y/N)", "Customer Convos", "Sign-ups/Sales", "Key Learning" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8 }, { "id": "chapter-13-startup-foundations-table-3", "caption": "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.", "headers": [ "Path", "Primary managerial job", "Starting evidence", "Capital and ownership", "Distinct risks", "Example stop gate" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-13-startup-foundations-table-4", "caption": "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.", "headers": [ "Screen", "Evidence required before advancing", "Case signal", "Decision implication" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-13-startup-foundations-table-5", "caption": "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.", "headers": [ "Dimension", "Lean Startup", "Traditional Planning" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-13-startup-foundations-table-6", "caption": "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.", "headers": [ "Dimension", "Bootstrap", "Venture-Backed" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-13-startup-foundations-table-7", "caption": "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.", "headers": [ "Week", "Phase", "Hypothesis Tested", "Validated?", "Customer Convos", "Signups", "Paying", "Key Learning" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-13-startup-foundations.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-07-organizational-behavior-and-leadership", "chapter-14-go-to-market-strategy", "chapter-15-fundraising-and-finance", "chapter-21-product-management-and-product-strategy" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-14-go-to-market-strategy", "chapter-15-fundraising-and-finance", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-14-go-to-market-strategy", "slug": "chapter-14-go-to-market-strategy", "kind": "chapter", "number": 14, "title": "Go-to-Market Strategy", "part": "Part 3: Entrepreneurship and Innovation", "summary": "ICP, positioning, channels, pricing, funnel design, sales motions, and launch planning.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "relatedSlugs": [ "chapter-05-marketing-and-customer-analytics", "chapter-13-startup-foundations", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/part3-entrepreneurship/14-go-to-market-strategy.md", "outputPath": "index.html#chapter-14-go-to-market-strategy", "markdownPath": "markdown/chapter-14-go-to-market-strategy.md", "wordCount": 22291, "checksum": "f5af33856e21b51ea61eab0f3a4141e5f4e3ad5313a171fef292bf6df9ab980c", "sourceIds": [ "BB-C14-S01", "BB-C14-S05", "BB-C14-S03", "BB-C14-S02", "BB-C14-S04", "BB-C14-S06", "BB-C14-S07", "BB-C14-S08", "BB-C14-S09", "BB-C14-S10", "BB-C14-S11" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-14-go-to-market-strategy-executive-summary" }, { "level": 2, "text": "1. GTM Strategy Canvas", "id": "chapter-14-go-to-market-strategy-1-gtm-strategy-canvas" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply" }, { "level": 3, "text": "A. Target Customer (WHO)", "id": "chapter-14-go-to-market-strategy-a-target-customer-who" }, { "level": 3, "text": "B. Customer Problem (WHAT)", "id": "chapter-14-go-to-market-strategy-b-customer-problem-what" }, { "level": 3, "text": "C. Unique Value Prop (WHY US)", "id": "chapter-14-go-to-market-strategy-c-unique-value-prop-why-us" }, { "level": 3, "text": "D. Go-to-Market Channel (HOW)", "id": "chapter-14-go-to-market-strategy-d-go-to-market-channel-how" }, { "level": 3, "text": "E. Pricing Model (HOW MUCH)", "id": "chapter-14-go-to-market-strategy-e-pricing-model-how-much" }, { "level": 3, "text": "F. Unit Economics (FINANCES)", "id": "chapter-14-go-to-market-strategy-f-unit-economics-finances" }, { "level": 3, "text": "G. Growth Assumption (TRAJECTORY)", "id": "chapter-14-go-to-market-strategy-g-growth-assumption-trajectory" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections" }, { "level": 2, "text": "2. Ideal Customer Profile (ICP) Framework", "id": "chapter-14-go-to-market-strategy-2-ideal-customer-profile-icp-framework" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply-2" }, { "level": 3, "text": "Firmographic (Company Characteristics)", "id": "chapter-14-go-to-market-strategy-firmographic-company-characteristics" }, { "level": 3, "text": "Behavioral (How They Operate)", "id": "chapter-14-go-to-market-strategy-behavioral-how-they-operate" }, { "level": 3, "text": "Psychographic (Values/Priorities)", "id": "chapter-14-go-to-market-strategy-psychographic-values-priorities" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections-2" }, { "level": 2, "text": "3. Sales Funnel Metrics Dashboard", "id": "chapter-14-go-to-market-strategy-3-sales-funnel-metrics-dashboard" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply-3" }, { "level": 3, "text": "AWARENESS", "id": "chapter-14-go-to-market-strategy-awareness" }, { "level": 3, "text": "CONSIDERATION", "id": "chapter-14-go-to-market-strategy-consideration" }, { "level": 3, "text": "PROPOSAL", "id": "chapter-14-go-to-market-strategy-proposal" }, { "level": 3, "text": "NEGOTIATION", "id": "chapter-14-go-to-market-strategy-negotiation" }, { "level": 3, "text": "POST-CLOSE", "id": "chapter-14-go-to-market-strategy-post-close" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections-3" }, { "level": 2, "text": "4. Channel Strategy Matrix", "id": "chapter-14-go-to-market-strategy-4-channel-strategy-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply-4" }, { "level": 3, "text": "Step 1: Current evidence and constraints", "id": "chapter-14-go-to-market-strategy-step-1-current-evidence-and-constraints" }, { "level": 3, "text": "Step 2: Economics Assessment", "id": "chapter-14-go-to-market-strategy-step-2-economics-assessment" }, { "level": 3, "text": "Step 3: Learning sequence", "id": "chapter-14-go-to-market-strategy-step-3-learning-sequence" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections-4" }, { "level": 2, "text": "5. Pricing Model Comparison", "id": "chapter-14-go-to-market-strategy-5-pricing-model-comparison" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply-5" }, { "level": 3, "text": "Model 1: Per-Unit Pricing", "id": "chapter-14-go-to-market-strategy-model-1-per-unit-pricing" }, { "level": 3, "text": "Model 2: Value-Based Pricing", "id": "chapter-14-go-to-market-strategy-model-2-value-based-pricing" }, { "level": 3, "text": "Model 3: Freemium", "id": "chapter-14-go-to-market-strategy-model-3-freemium" }, { "level": 3, "text": "Model 4: Usage-Based / Consumption Pricing", "id": "chapter-14-go-to-market-strategy-model-4-usage-based-consumption-pricing" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections-5" }, { "level": 2, "text": "6. Product Launch Checklist", "id": "chapter-14-go-to-market-strategy-6-product-launch-checklist" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply-6" }, { "level": 3, "text": "Marketing & Communications (Week -4 to -1)", "id": "chapter-14-go-to-market-strategy-marketing-communications-week-4-to-1" }, { "level": 3, "text": "Sales & Partnership (Week -4 to -1)", "id": "chapter-14-go-to-market-strategy-sales-partnership-week-4-to-1" }, { "level": 3, "text": "Product & Operations (Week -4 to -2)", "id": "chapter-14-go-to-market-strategy-product-operations-week-4-to-2" }, { "level": 3, "text": "Launch Day (Day 0)", "id": "chapter-14-go-to-market-strategy-launch-day-day-0" }, { "level": 3, "text": "Post-Launch (Days 1-7)", "id": "chapter-14-go-to-market-strategy-post-launch-days-1-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections-6" }, { "level": 2, "text": "7. Growth Experimentation Framework", "id": "chapter-14-go-to-market-strategy-7-growth-experimentation-framework" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply-7" }, { "level": 3, "text": "Step 1: Identify Growth Levers", "id": "chapter-14-go-to-market-strategy-step-1-identify-growth-levers" }, { "level": 3, "text": "Step 2: Quantify the Lever", "id": "chapter-14-go-to-market-strategy-step-2-quantify-the-lever" }, { "level": 3, "text": "Step 3: Optimize the Top Lever", "id": "chapter-14-go-to-market-strategy-step-3-optimize-the-top-lever" }, { "level": 3, "text": "Step 4: Automate the Lever", "id": "chapter-14-go-to-market-strategy-step-4-automate-the-lever" }, { "level": 3, "text": "Step 5: Invest in Winning Levers", "id": "chapter-14-go-to-market-strategy-step-5-invest-in-winning-levers" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections-7" }, { "level": 2, "text": "8. Product-mediated diffusion measure", "id": "chapter-14-go-to-market-strategy-8-product-mediated-diffusion-measure" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply-8" }, { "level": 3, "text": "Increase Invites Sent", "id": "chapter-14-go-to-market-strategy-increase-invites-sent" }, { "level": 3, "text": "Increase Conversion Rate", "id": "chapter-14-go-to-market-strategy-increase-conversion-rate" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections-8" }, { "level": 2, "text": "9. Partnership Evaluation Matrix", "id": "chapter-14-go-to-market-strategy-9-partnership-evaluation-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections-9" }, { "level": 2, "text": "10. Market Entry Strategy Decision Tree", "id": "chapter-14-go-to-market-strategy-10-market-entry-strategy-decision-tree" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply-10" }, { "level": 3, "text": "Focused category entry or new-market development", "id": "chapter-14-go-to-market-strategy-focused-category-entry-or-new-market-development" }, { "level": 3, "text": "Differentiation (Existing Market)", "id": "chapter-14-go-to-market-strategy-differentiation-existing-market" }, { "level": 3, "text": "Niche (White Space)", "id": "chapter-14-go-to-market-strategy-niche-white-space" }, { "level": 3, "text": "Land-and-Expand (Existing Customer)", "id": "chapter-14-go-to-market-strategy-land-and-expand-existing-customer" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections-10" }, { "level": 2, "text": "11. International and Non-Market GTM Gate", "id": "chapter-14-go-to-market-strategy-11-international-and-non-market-gtm-gate" }, { "level": 3, "text": "Overview", "id": "chapter-14-go-to-market-strategy-overview-11" }, { "level": 3, "text": "How to Apply", "id": "chapter-14-go-to-market-strategy-how-to-apply-11" }, { "level": 3, "text": "Country and institution matrix", "id": "chapter-14-go-to-market-strategy-country-and-institution-matrix" }, { "level": 3, "text": "Constructed country-comparison exercise", "id": "chapter-14-go-to-market-strategy-constructed-country-comparison-exercise" }, { "level": 3, "text": "So What for Managers", "id": "chapter-14-go-to-market-strategy-so-what-for-managers-11" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-14-go-to-market-strategy-limits-and-critiques-11" }, { "level": 3, "text": "Connections", "id": "chapter-14-go-to-market-strategy-connections-11" }, { "level": 2, "text": "Summary: GTM Strategy Frameworks", "id": "chapter-14-go-to-market-strategy-summary-gtm-strategy-frameworks" }, { "level": 2, "text": "How To Get Started", "id": "chapter-14-go-to-market-strategy-how-to-get-started" }, { "level": 3, "text": "Version 1: Quick GTM Validation (2-3 Weeks)", "id": "chapter-14-go-to-market-strategy-version-1-quick-gtm-validation-2-3-weeks" }, { "level": 4, "text": "Days 1-2: GTM Canvas Workshop", "id": "chapter-14-go-to-market-strategy-days-1-2-gtm-canvas-workshop" }, { "level": 4, "text": "Days 3-10: Customer Validation Interviews", "id": "chapter-14-go-to-market-strategy-days-3-10-customer-validation-interviews" }, { "level": 4, "text": "Days 11-15: ICP Refinement (Week 2)", "id": "chapter-14-go-to-market-strategy-days-11-15-icp-refinement-week-2" }, { "level": 4, "text": "Days 16-20: Pricing/Channel Decision + Launch Prep (Week 3)", "id": "chapter-14-go-to-market-strategy-days-16-20-pricing-channel-decision-launch-prep-week-3" }, { "level": 3, "text": "Version 2: Detailed GTM Launch (8-12 Weeks)", "id": "chapter-14-go-to-market-strategy-version-2-detailed-gtm-launch-8-12-weeks" }, { "level": 4, "text": "Detailed-path Phase 1: GTM Canvas Development & Validation (Weeks 1-2)", "id": "chapter-14-go-to-market-strategy-detailed-path-phase-1-gtm-canvas-development-validation-weeks-1-2" }, { "level": 4, "text": "Detailed-path Phase 2: ICP Deep Dive & Positioning (Weeks 3-4)", "id": "chapter-14-go-to-market-strategy-detailed-path-phase-2-icp-deep-dive-positioning-weeks-3-4" }, { "level": 4, "text": "Detailed-path Phase 3: Channel & Pricing Strategy (Weeks 5-6)", "id": "chapter-14-go-to-market-strategy-detailed-path-phase-3-channel-pricing-strategy-weeks-5-6" }, { "level": 4, "text": "Detailed-path Phase 4: Launch Preparation & Execution (Weeks 7-12)", "id": "chapter-14-go-to-market-strategy-detailed-path-phase-4-launch-preparation-execution-weeks-7-12" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-14-go-to-market-strategy-common-pitfalls" }, { "level": 4, "text": "1. Vague Target Customer (\"Everyone is NOT the customer\")", "id": "chapter-14-go-to-market-strategy-1-vague-target-customer-everyone-is-not-the-customer" }, { "level": 4, "text": "2. Misaligned Channel Choice (Channel doesn't match customer buying behavior)", "id": "chapter-14-go-to-market-strategy-2-misaligned-channel-choice-channel-doesn-t-match-customer-buying-behavior" }, { "level": 4, "text": "3. Pricing Too High or Too Low (No unit economics analysis)", "id": "chapter-14-go-to-market-strategy-3-pricing-too-high-or-too-low-no-unit-economics-analysis" }, { "level": 4, "text": "4. Launch Without Measurement (No funnel metrics tracked)", "id": "chapter-14-go-to-market-strategy-4-launch-without-measurement-no-funnel-metrics-tracked" }, { "level": 4, "text": "5. Ignoring Competition (No positioning against alternatives)", "id": "chapter-14-go-to-market-strategy-5-ignoring-competition-no-positioning-against-alternatives" }, { "level": 3, "text": "Red Flags: When GTM is Failing", "id": "chapter-14-go-to-market-strategy-red-flags-when-gtm-is-failing" }, { "level": 4, "text": "Red Flag #1: Low Conversion Rates", "id": "chapter-14-go-to-market-strategy-red-flag-1-low-conversion-rates" }, { "level": 4, "text": "Red Flag #2: High CAC", "id": "chapter-14-go-to-market-strategy-red-flag-2-high-cac" }, { "level": 4, "text": "Red Flag #3: No Word-of-Mouth / Referrals", "id": "chapter-14-go-to-market-strategy-red-flag-3-no-word-of-mouth-referrals" }, { "level": 4, "text": "Red Flag #4: High Early Churn", "id": "chapter-14-go-to-market-strategy-red-flag-4-high-early-churn" }, { "level": 4, "text": "Red Flag #5: Stalled Growth", "id": "chapter-14-go-to-market-strategy-red-flag-5-stalled-growth" }, { "level": 2, "text": "Why This Matters: Mental Models & GTM Wisdom", "id": "chapter-14-go-to-market-strategy-why-this-matters-mental-models-gtm-wisdom" }, { "level": 3, "text": "Mental Models: Why GTM Strategy Works", "id": "chapter-14-go-to-market-strategy-mental-models-why-gtm-strategy-works" }, { "level": 4, "text": "1. GTM Canvas: Holistic Customer View Across Acquisition, Activation, Retention", "id": "chapter-14-go-to-market-strategy-1-gtm-canvas-holistic-customer-view-across-acquisition-activation-retention" }, { "level": 4, "text": "2. ICP Focus: Concentration of Resources on Highest-Value Customers", "id": "chapter-14-go-to-market-strategy-2-icp-focus-concentration-of-resources-on-highest-value-customers" }, { "level": 4, "text": "3. Channel Strategy: Matching Customer Behaviors to Go-to-Market Approaches", "id": "chapter-14-go-to-market-strategy-3-channel-strategy-matching-customer-behaviors-to-go-to-market-approaches" }, { "level": 4, "text": "4. Pricing Psychology: Value Perception vs. Cost Basis", "id": "chapter-14-go-to-market-strategy-4-pricing-psychology-value-perception-vs-cost-basis" }, { "level": 3, "text": "Constructed Failure Composites: Which GTM Assumptions Could Fail", "id": "chapter-14-go-to-market-strategy-constructed-failure-composites-which-gtm-assumptions-could-fail" }, { "level": 4, "text": "Composite 1: Consumer File-Sync Platform — GTM Conflict", "id": "chapter-14-go-to-market-strategy-composite-1-consumer-file-sync-platform-gtm-conflict" }, { "level": 4, "text": "Composite 2: Team Collaboration Platform — GTM Evolution", "id": "chapter-14-go-to-market-strategy-composite-2-team-collaboration-platform-gtm-evolution" }, { "level": 4, "text": "Composite 3: Enterprise Analytics Vendor — Mid-Market Mismatch", "id": "chapter-14-go-to-market-strategy-composite-3-enterprise-analytics-vendor-mid-market-mismatch" }, { "level": 3, "text": "Competing Schools: Different GTM Philosophies", "id": "chapter-14-go-to-market-strategy-competing-schools-different-gtm-philosophies" }, { "level": 4, "text": "1. Direct vs. Indirect Sales (Margin vs. Channel Scale)", "id": "chapter-14-go-to-market-strategy-1-direct-vs-indirect-sales-margin-vs-channel-scale" }, { "level": 4, "text": "2. Product-Mediated, Earned, and Paid Acquisition", "id": "chapter-14-go-to-market-strategy-2-product-mediated-earned-and-paid-acquisition" }, { "level": 4, "text": "3. Horizontal and Vertical GTM as Design Choices", "id": "chapter-14-go-to-market-strategy-3-horizontal-and-vertical-gtm-as-design-choices" }, { "level": 3, "text": "Stage-Dependent GTM Tailoring", "id": "chapter-14-go-to-market-strategy-stage-dependent-gtm-tailoring" }, { "level": 4, "text": "Earlier evidence stage", "id": "chapter-14-go-to-market-strategy-earlier-evidence-stage" }, { "level": 4, "text": "Repeatability and expansion stage", "id": "chapter-14-go-to-market-strategy-repeatability-and-expansion-stage" }, { "level": 4, "text": "Portfolio stage", "id": "chapter-14-go-to-market-strategy-portfolio-stage" }, { "level": 2, "text": "Case Example: B2B SaaS Launch", "id": "chapter-14-go-to-market-strategy-case-example-b2b-saas-launch" }, { "level": 2, "text": "Operating Manual: Your 10-Week GTM Launch", "id": "chapter-14-go-to-market-strategy-operating-manual-your-10-week-gtm-launch" }, { "level": 3, "text": "Operating-template Phase 1: GTM Strategy Development (Weeks 1-2)", "id": "chapter-14-go-to-market-strategy-operating-template-phase-1-gtm-strategy-development-weeks-1-2" }, { "level": 3, "text": "Operating-template Phase 2: ICP Deep Dive & Positioning (Weeks 3-4)", "id": "chapter-14-go-to-market-strategy-operating-template-phase-2-icp-deep-dive-positioning-weeks-3-4" }, { "level": 3, "text": "Operating-template Phase 3: Channel Selection & Pricing (Weeks 5-6)", "id": "chapter-14-go-to-market-strategy-operating-template-phase-3-channel-selection-pricing-weeks-5-6" }, { "level": 3, "text": "Operating-template Phase 4: Launch Preparation (Week 7-8)", "id": "chapter-14-go-to-market-strategy-operating-template-phase-4-launch-preparation-week-7-8" }, { "level": 3, "text": "Operating-template Phase 5: Launch & Optimization (Weeks 9-10)", "id": "chapter-14-go-to-market-strategy-operating-template-phase-5-launch-optimization-weeks-9-10" }, { "level": 3, "text": "Resource Requirements", "id": "chapter-14-go-to-market-strategy-resource-requirements" }, { "level": 3, "text": "Red Flags & Warning Signals", "id": "chapter-14-go-to-market-strategy-red-flags-warning-signals" }, { "level": 3, "text": "Contingency Triggers", "id": "chapter-14-go-to-market-strategy-contingency-triggers" }, { "level": 3, "text": "Timeline Variance", "id": "chapter-14-go-to-market-strategy-timeline-variance" }, { "level": 3, "text": "Measurement Dashboard", "id": "chapter-14-go-to-market-strategy-measurement-dashboard" }, { "level": 3, "text": "Success vs Struggling: How to Know", "id": "chapter-14-go-to-market-strategy-success-vs-struggling-how-to-know" } ], "figures": [ { "id": "chapter-14-go-to-market-strategy-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "b6790cb8c84a3c3e5cce70a2873a47eaae5cc0524225ba2fcee1264598603bed" }, { "id": "chapter-14-go-to-market-strategy-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "8fd3ff383dfaa8bd812fe44f290849054992f0d39091414571976ca839322765" }, { "id": "chapter-14-go-to-market-strategy-figure-3", "type": "mermaid", "caption": "Figure 14.3: Evidence-gated market-entry choice (constructed). This is a decision aid, not a prediction model.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "a96d4ea3006290ba4cbc7d46293b34438cddb5baca3251bee0b2114164a270f6" }, { "id": "chapter-14-go-to-market-strategy-figure-4", "type": "mermaid", "caption": "Figure 14.4: International-entry evidence and exit loop (constructed).", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "7cc47058b37683c0cfc5211b9b85527ecedd89edaa1e5c1f3fcfd57ce51a5a68" } ], "tables": [ { "id": "chapter-14-go-to-market-strategy-table-1", "caption": "Table 14.1: Constructed segment-prioritization illustration. The figures are invented teaching inputs, not market benchmarks, forecasts, or evidence of fit.", "headers": [ "Segment", "Size", "Avg Deal", "Win Rate", "LTV:CAC", "Priority" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-14-go-to-market-strategy-table-2", "caption": "Table 14.2: Constructed funnel dashboard for one sample month. Stage definitions, targets, actuals, and health labels require local cohort and data-quality rules.", "headers": [ "Stage", "Target", "Actual", "Conv Rate", "Health" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-14-go-to-market-strategy-table-3", "caption": "Table 14.3: Constructed channel-funnel comparison. Conversion values are illustrative and are not channel benchmarks.", "headers": [ "Channel", "Awareness", "Consideration", "Proposal", "Close", "Efficiency" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-14-go-to-market-strategy-table-4", "caption": "Table 14.4: Constructed channel-evaluation matrix. Volume, deal-size, cycle, margin, investment, and maturity values are hypotheses for teaching, not benchmarks.", "headers": [ "Channel", "Volume Potential", "Deal Size", "Sales Cycle", "Margin", "Investment", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-14-go-to-market-strategy-table-5", "caption": "Table 14.5: Constructed channel-economics hypothesis. The figures below illustrate a comparison method; they are not observed LTV, CAC, or channel performance.", "headers": [ "Channel", "CAC", "LTV", "LTV:CAC", "Status" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-14-go-to-market-strategy-table-6", "caption": "Table 14.6: Constructed pricing-model comparison. The dimensions are decision prompts, not universal model attributes.", "headers": [ "Model", "Predictability", "Scalability", "Customer Friction", "Enterprise", "SMB" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-14-go-to-market-strategy-table-7", "caption": "Table 14.7: Constructed partnership-evaluation illustration. Company names, revenue potential, timing, and priorities are invented teaching inputs, not forecasts.", "headers": [ "Partnership", "Revenue Potential", "Ease of Execution", "Strategic Fit", "Timeline", "Priority" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-14-go-to-market-strategy-table-8", "caption": "Table 14.8: Author-created market-entry comparison. Each row states evidence to obtain before commitment; the strategy labels do not predict success.", "headers": [ "Situation", "Candidate strategy", "Evidence required before commitment" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-14-go-to-market-strategy-table-9", "caption": "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.", "headers": [ "Decision lane", "Evidence required before commitment", "Gate or trigger" ], "sourceIds": [ "BB-C14-S09", "BB-C14-S10", "BB-C14-S11" ], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-14-go-to-market-strategy-table-10", "caption": "Table 14.10: Constructed framework-use summary. Timing is a planning aid, not a universal sequence or readiness gate.", "headers": [ "Framework", "When to Use", "Time Required" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 10 }, { "id": "chapter-14-go-to-market-strategy-table-11", "caption": "Table 14.11: Constructed channel-model comparison. Values are illustrative ranges and descriptive expectations to test locally, not natural channel properties.", "headers": [ "Channel", "Natural CAC", "Customer Expectation", "Works For" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-14-go-to-market-strategy-table-12", "caption": "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.", "headers": [ "Dimension", "Direct Sales", "Indirect Sales" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-14-go-to-market-strategy-table-13", "caption": "Table 14.13: Author-created acquisition-mechanism questions. Use the table to define evidence and guardrails; it is not a taxonomy or performance ranking.", "headers": [ "Dimension", "Questions to test" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-14-go-to-market-strategy-table-14", "caption": "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.", "headers": [ "Week", "Key Metric", "Target", "Actual", "Status" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 14 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-14-go-to-market-strategy.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-13-startup-foundations", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-13-startup-foundations", "chapter-15-fundraising-and-finance", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-21-product-management-and-product-strategy" ] }, { "id": "chapter-15-fundraising-and-finance", "slug": "chapter-15-fundraising-and-finance", "kind": "chapter", "number": 15, "title": "Fundraising and Finance", "part": "Part 3: Entrepreneurship and Innovation", "summary": "Venture fundraising, valuation, dilution, term sheets, capital planning, and investor communication.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "relatedSlugs": [ "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy" ], "sourcePath": "src/part3-entrepreneurship/15-fundraising-finance.md", "outputPath": "index.html#chapter-15-fundraising-and-finance", "markdownPath": "markdown/chapter-15-fundraising-and-finance.md", "wordCount": 32307, "checksum": "a950440e38035947eaf15b921c6c6e2d0c1c1aaa8e439df860bc290609ccf180", "sourceIds": [ "BB-C15-S06", "BB-C15-S07", "BB-C15-S14", "BB-C15-S01", "BB-C15-S02", "BB-C15-S04", "BB-C15-S05", "BB-C15-S12", "BB-C15-S16", "BB-C15-S08", "BB-C15-S09", "BB-C15-S10", "BB-C15-S11", "BB-C15-S15", "BB-C15-S03", "BB-C15-S13", "BB-C15-S18", "BB-C15-S17", "BB-C15-S19", "BB-C15-S20", "BB-C15-S21", "BB-C15-S22", "BB-C15-S23", "BB-C15-S24" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-15-fundraising-and-finance-executive-summary" }, { "level": 3, "text": "Decision Outcomes and Boundary", "id": "chapter-15-fundraising-and-finance-decision-outcomes-and-boundary" }, { "level": 2, "text": "1. Fundraising Process Timeline", "id": "chapter-15-fundraising-and-finance-1-fundraising-process-timeline" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply" }, { "level": 3, "text": "Constructed Fundraising Schedule", "id": "chapter-15-fundraising-and-finance-constructed-fundraising-schedule" }, { "level": 3, "text": "Illustrative Month 0: Preparation (example cadence)", "id": "chapter-15-fundraising-and-finance-illustrative-month-0-preparation-example-cadence" }, { "level": 3, "text": "Illustrative Month 1: Outreach (example cadence)", "id": "chapter-15-fundraising-and-finance-illustrative-month-1-outreach-example-cadence" }, { "level": 3, "text": "Illustrative Month 1-2: First Meetings (example cadence)", "id": "chapter-15-fundraising-and-finance-illustrative-month-1-2-first-meetings-example-cadence" }, { "level": 3, "text": "Illustrative Month 2-3: Due Diligence (example cadence)", "id": "chapter-15-fundraising-and-finance-illustrative-month-2-3-due-diligence-example-cadence" }, { "level": 3, "text": "Illustrative Month 3: Term Sheet & Negotiation (example cadence)", "id": "chapter-15-fundraising-and-finance-illustrative-month-3-term-sheet-negotiation-example-cadence" }, { "level": 3, "text": "Illustrative Month 4: Legal & Closing (example cadence)", "id": "chapter-15-fundraising-and-finance-illustrative-month-4-legal-closing-example-cadence" }, { "level": 3, "text": "Post-Close: Announcement (1 week)", "id": "chapter-15-fundraising-and-finance-post-close-announcement-1-week" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections" }, { "level": 2, "text": "2. Pitch Deck Structure (Slide-by-Slide Guide)", "id": "chapter-15-fundraising-and-finance-2-pitch-deck-structure-slide-by-slide-guide" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply-2" }, { "level": 3, "text": "Slide 1: Title Slide", "id": "chapter-15-fundraising-and-finance-slide-1-title-slide" }, { "level": 3, "text": "Slide 2: The Problem", "id": "chapter-15-fundraising-and-finance-slide-2-the-problem" }, { "level": 3, "text": "Slide 3: Your Solution", "id": "chapter-15-fundraising-and-finance-slide-3-your-solution" }, { "level": 3, "text": "Slide 4: Market Size (TAM)", "id": "chapter-15-fundraising-and-finance-slide-4-market-size-tam" }, { "level": 3, "text": "Slide 5: Traction / Early Results", "id": "chapter-15-fundraising-and-finance-slide-5-traction-early-results" }, { "level": 3, "text": "Slide 6: Business Model", "id": "chapter-15-fundraising-and-finance-slide-6-business-model" }, { "level": 3, "text": "Slide 7: Go-to-Market / Competitive Position", "id": "chapter-15-fundraising-and-finance-slide-7-go-to-market-competitive-position" }, { "level": 3, "text": "Slide 8: Team", "id": "chapter-15-fundraising-and-finance-slide-8-team" }, { "level": 3, "text": "Slide 9: Financial Projections (5-Year)", "id": "chapter-15-fundraising-and-finance-slide-9-financial-projections-5-year" }, { "level": 3, "text": "Slide 10: Fundraising Ask", "id": "chapter-15-fundraising-and-finance-slide-10-fundraising-ask" }, { "level": 3, "text": "Slide 11: Why Now?", "id": "chapter-15-fundraising-and-finance-slide-11-why-now" }, { "level": 3, "text": "Slide 12: Current Metrics & Milestones", "id": "chapter-15-fundraising-and-finance-slide-12-current-metrics-milestones" }, { "level": 3, "text": "Slide 13: Long-Term Vision", "id": "chapter-15-fundraising-and-finance-slide-13-long-term-vision" }, { "level": 3, "text": "Slide 14: Questions / Call to Action", "id": "chapter-15-fundraising-and-finance-slide-14-questions-call-to-action" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections-2" }, { "level": 2, "text": "3. Valuation Methods and Assumption Reconciliation", "id": "chapter-15-fundraising-and-finance-3-valuation-methods-and-assumption-reconciliation" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply-3" }, { "level": 3, "text": "Method 1: Venture-capital method", "id": "chapter-15-fundraising-and-finance-method-1-venture-capital-method" }, { "level": 3, "text": "Method 2: Comparable transactions or companies", "id": "chapter-15-fundraising-and-finance-method-2-comparable-transactions-or-companies" }, { "level": 3, "text": "Method 3: Scenario-based discounted cash flow", "id": "chapter-15-fundraising-and-finance-method-3-scenario-based-discounted-cash-flow" }, { "level": 3, "text": "Method 4: Milestone or scorecard methods", "id": "chapter-15-fundraising-and-finance-method-4-milestone-or-scorecard-methods" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections-3" }, { "level": 2, "text": "4. Term Sheet Rights and Model Matrix", "id": "chapter-15-fundraising-and-finance-4-term-sheet-rights-and-model-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply-4" }, { "level": 3, "text": "Security-by-security analysis", "id": "chapter-15-fundraising-and-finance-security-by-security-analysis" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections-4" }, { "level": 2, "text": "5. Cap Table Scenarios & Dilution", "id": "chapter-15-fundraising-and-finance-5-cap-table-scenarios-dilution" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply-5" }, { "level": 3, "text": "Capitalization and Rights Visual", "id": "chapter-15-fundraising-and-finance-capitalization-and-rights-visual" }, { "level": 3, "text": "Starting Point (Seed Stage)", "id": "chapter-15-fundraising-and-finance-starting-point-seed-stage" }, { "level": 3, "text": "After Seed Round ($500K at $2M post-money) ", "id": "chapter-15-fundraising-and-finance-after-seed-round-500k-at-2m-post-money" }, { "level": 3, "text": "After Series A Round ($5M at $25M post-money) ", "id": "chapter-15-fundraising-and-finance-after-series-a-round-5m-at-25m-post-money" }, { "level": 3, "text": "After Series B Round ($15M at $85M post-money) ", "id": "chapter-15-fundraising-and-finance-after-series-b-round-15m-at-85m-post-money" }, { "level": 3, "text": "For Investors (Series A, B, C)", "id": "chapter-15-fundraising-and-finance-for-investors-series-a-b-c" }, { "level": 3, "text": "For Employees", "id": "chapter-15-fundraising-and-finance-for-employees" }, { "level": 2, "text": "5A. Advanced Dilution Modeling: Realistic Scenarios", "id": "chapter-15-fundraising-and-finance-5a-advanced-dilution-modeling-realistic-scenarios" }, { "level": 3, "text": "Scenario 1: Option Pool Impact on Founder Dilution", "id": "chapter-15-fundraising-and-finance-scenario-1-option-pool-impact-on-founder-dilution" }, { "level": 3, "text": "Scenario 2: Down Round Dilution (Worst Case)", "id": "chapter-15-fundraising-and-finance-scenario-2-down-round-dilution-worst-case" }, { "level": 3, "text": "Scenario 3: Bridge Financing & Convertible Note Impact", "id": "chapter-15-fundraising-and-finance-scenario-3-bridge-financing-convertible-note-impact" }, { "level": 3, "text": "Scenario 4: Liquidation Preference Impact on Exit Economics", "id": "chapter-15-fundraising-and-finance-scenario-4-liquidation-preference-impact-on-exit-economics" }, { "level": 3, "text": "Scenario 5: Full Dilution Journey (Seed to IPO)", "id": "chapter-15-fundraising-and-finance-scenario-5-full-dilution-journey-seed-to-ipo" }, { "level": 3, "text": "Dilution Modeling Tool", "id": "chapter-15-fundraising-and-finance-dilution-modeling-tool" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections-5" }, { "level": 2, "text": "6. Investor Evaluation Criteria", "id": "chapter-15-fundraising-and-finance-6-investor-evaluation-criteria" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply-6" }, { "level": 3, "text": "1. Team (illustrative weighting example) ", "id": "chapter-15-fundraising-and-finance-1-team-illustrative-weighting-example" }, { "level": 3, "text": "2. Market Size / TAM (illustrative weighting example) ", "id": "chapter-15-fundraising-and-finance-2-market-size-tam-illustrative-weighting-example" }, { "level": 3, "text": "3. Traction (illustrative weighting example) ", "id": "chapter-15-fundraising-and-finance-3-traction-illustrative-weighting-example" }, { "level": 3, "text": "4. Product (illustrative weighting example) ", "id": "chapter-15-fundraising-and-finance-4-product-illustrative-weighting-example" }, { "level": 3, "text": "5. Business Model (illustrative weighting example) ", "id": "chapter-15-fundraising-and-finance-5-business-model-illustrative-weighting-example" }, { "level": 3, "text": "6. Usage and reference signals (illustrative weighting example) ", "id": "chapter-15-fundraising-and-finance-6-usage-and-reference-signals-illustrative-weighting-example" }, { "level": 2, "text": "6A. Investor-Decision Questions Beyond a Scorecard", "id": "chapter-15-fundraising-and-finance-6a-investor-decision-questions-beyond-a-scorecard" }, { "level": 3, "text": "Illustrative Investment Dimensions (to be tested against actual behavior)", "id": "chapter-15-fundraising-and-finance-illustrative-investment-dimensions-to-be-tested-against-actual-behavior" }, { "level": 4, "text": "1. Fund Economics & Portfolio Construction (illustrative weighting example) ", "id": "chapter-15-fundraising-and-finance-1-fund-economics-portfolio-construction-illustrative-weighting-example" }, { "level": 4, "text": "2. Narrative Fit with Firm's Thesis (illustrative weighting example) ", "id": "chapter-15-fundraising-and-finance-2-narrative-fit-with-firm-s-thesis-illustrative-weighting-example" }, { "level": 4, "text": "3. Founder-Investor Interpersonal Dynamics (illustrative weighting example) ", "id": "chapter-15-fundraising-and-finance-3-founder-investor-interpersonal-dynamics-illustrative-weighting-example" }, { "level": 4, "text": "4. Traction Relative to Valuation (illustrative weighting example) ", "id": "chapter-15-fundraising-and-finance-4-traction-relative-to-valuation-illustrative-weighting-example" }, { "level": 3, "text": "What Doesn't Matter (Despite What VCs Say)", "id": "chapter-15-fundraising-and-finance-what-doesn-t-matter-despite-what-vcs-say" }, { "level": 4, "text": "1. \"Passion\" and \"Mission\"", "id": "chapter-15-fundraising-and-finance-1-passion-and-mission" }, { "level": 4, "text": "2. \"Unique Technology\"", "id": "chapter-15-fundraising-and-finance-2-unique-technology" }, { "level": 4, "text": "3. \"Total Addressable Market (TAM)\"", "id": "chapter-15-fundraising-and-finance-3-total-addressable-market-tam" }, { "level": 4, "text": "4. \"Product-Market Fit\"", "id": "chapter-15-fundraising-and-finance-4-product-market-fit" }, { "level": 3, "text": "How to Navigate VC Politics", "id": "chapter-15-fundraising-and-finance-how-to-navigate-vc-politics" }, { "level": 4, "text": "Tactic 1: Coordinate a Transparent Process (without manufacturing FOMO)", "id": "chapter-15-fundraising-and-finance-tactic-1-coordinate-a-transparent-process-without-manufacturing-fomo" }, { "level": 4, "text": "Tactic 2: Leverage Partner Dynamics", "id": "chapter-15-fundraising-and-finance-tactic-2-leverage-partner-dynamics" }, { "level": 4, "text": "Tactic 3: Use Early \"No's\" to Improve Pitch", "id": "chapter-15-fundraising-and-finance-tactic-3-use-early-no-s-to-improve-pitch" }, { "level": 4, "text": "Tactic 4: Signal Insider Knowledge", "id": "chapter-15-fundraising-and-finance-tactic-4-signal-insider-knowledge" }, { "level": 3, "text": "The Unspoken Rejection Reasons", "id": "chapter-15-fundraising-and-finance-the-unspoken-rejection-reasons" }, { "level": 3, "text": "When to Walk Away from VC Money", "id": "chapter-15-fundraising-and-finance-when-to-walk-away-from-vc-money" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections-6" }, { "level": 2, "text": "7. Due Diligence Checklist (Sell-Side)", "id": "chapter-15-fundraising-and-finance-7-due-diligence-checklist-sell-side" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply-7" }, { "level": 3, "text": "Corporate / Legal", "id": "chapter-15-fundraising-and-finance-corporate-legal" }, { "level": 3, "text": "Financial", "id": "chapter-15-fundraising-and-finance-financial" }, { "level": 3, "text": "Operations", "id": "chapter-15-fundraising-and-finance-operations" }, { "level": 3, "text": "Sales & Marketing", "id": "chapter-15-fundraising-and-finance-sales-marketing" }, { "level": 3, "text": "Reference Contacts", "id": "chapter-15-fundraising-and-finance-reference-contacts" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections-7" }, { "level": 2, "text": "8. Financial Model Template (3-Statement)", "id": "chapter-15-fundraising-and-finance-8-financial-model-template-3-statement" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply-8" }, { "level": 3, "text": "Income Statement (5-Year Projection)", "id": "chapter-15-fundraising-and-finance-income-statement-5-year-projection" }, { "level": 3, "text": "Balance Sheet (Illustrative Year-End Snapshot)", "id": "chapter-15-fundraising-and-finance-balance-sheet-illustrative-year-end-snapshot" }, { "level": 3, "text": "Cash Flow Statement (Illustrative Partial-Year Slice)", "id": "chapter-15-fundraising-and-finance-cash-flow-statement-illustrative-partial-year-slice" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections-8" }, { "level": 2, "text": "9. Exit, Liquidity, and Continuation Options", "id": "chapter-15-fundraising-and-finance-9-exit-liquidity-and-continuation-options" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections-9" }, { "level": 2, "text": "10. SAFE and Convertible-Note Decision Boundary", "id": "chapter-15-fundraising-and-finance-10-safe-and-convertible-note-decision-boundary" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply-10" }, { "level": 3, "text": "Convertible note", "id": "chapter-15-fundraising-and-finance-convertible-note" }, { "level": 3, "text": "SAFE", "id": "chapter-15-fundraising-and-finance-safe" }, { "level": 3, "text": "Controlled conversion model", "id": "chapter-15-fundraising-and-finance-controlled-conversion-model" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections-10" }, { "level": 2, "text": "11. Financing and No-Raise Decision Framework", "id": "chapter-15-fundraising-and-finance-11-financing-and-no-raise-decision-framework" }, { "level": 3, "text": "Overview", "id": "chapter-15-fundraising-and-finance-overview-11" }, { "level": 3, "text": "How to Apply", "id": "chapter-15-fundraising-and-finance-how-to-apply-11" }, { "level": 3, "text": "Decision questions", "id": "chapter-15-fundraising-and-finance-decision-questions" }, { "level": 3, "text": "Scenario method", "id": "chapter-15-fundraising-and-finance-scenario-method" }, { "level": 3, "text": "So What for Managers", "id": "chapter-15-fundraising-and-finance-so-what-for-managers-11" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-15-fundraising-and-finance-limits-and-critiques-11" }, { "level": 3, "text": "Connections", "id": "chapter-15-fundraising-and-finance-connections-11" }, { "level": 2, "text": "12. Troubleshooting: When Fundraising Goes Wrong", "id": "chapter-15-fundraising-and-finance-12-troubleshooting-when-fundraising-goes-wrong" }, { "level": 3, "text": "Problem 1: No Term Sheets After a Sufficient, Responsibly Sampled Process", "id": "chapter-15-fundraising-and-finance-problem-1-no-term-sheets-after-a-sufficient-responsibly-sampled-process" }, { "level": 3, "text": "Problem 2: Lower-Price Financing or Recapitalization", "id": "chapter-15-fundraising-and-finance-problem-2-lower-price-financing-or-recapitalization" }, { "level": 3, "text": "Problem 3: Bridge Round (Emergency Financing)", "id": "chapter-15-fundraising-and-finance-problem-3-bridge-round-emergency-financing" }, { "level": 3, "text": "Problem 4: Investor Pulls Term Sheet", "id": "chapter-15-fundraising-and-finance-problem-4-investor-pulls-term-sheet" }, { "level": 3, "text": "Problem 5: Running Out of Cash (Distressed Financing)", "id": "chapter-15-fundraising-and-finance-problem-5-running-out-of-cash-distressed-financing" }, { "level": 2, "text": "13. Financing and Governance Lessons from Primary Records", "id": "chapter-15-fundraising-and-finance-13-financing-and-governance-lessons-from-primary-records" }, { "level": 3, "text": "The We Company: What the 2019 S-1 Can Support", "id": "chapter-15-fundraising-and-finance-the-we-company-what-the-2019-s-1-can-support" }, { "level": 3, "text": "Theranos: SEC Allegations and Settlement Boundary", "id": "chapter-15-fundraising-and-finance-theranos-sec-allegations-and-settlement-boundary" }, { "level": 3, "text": "FTX Debtors: Post-Bankruptcy Control Evidence", "id": "chapter-15-fundraising-and-finance-ftx-debtors-post-bankruptcy-control-evidence" }, { "level": 3, "text": "Cross-Case Decision Framework", "id": "chapter-15-fundraising-and-finance-cross-case-decision-framework" }, { "level": 2, "text": "14. Entrepreneurship Through Acquisition: Financing, Diligence, and Transition", "id": "chapter-15-fundraising-and-finance-14-entrepreneurship-through-acquisition-financing-diligence-and-transition" }, { "level": 3, "text": "Sources and uses: who funds what, and who bears which claim?", "id": "chapter-15-fundraising-and-finance-sources-and-uses-who-funds-what-and-who-bears-which-claim" }, { "level": 3, "text": "Debt service and dilution are different exposures", "id": "chapter-15-fundraising-and-finance-debt-service-and-dilution-are-different-exposures" }, { "level": 3, "text": "Quality of earnings: reconcile the claim before sizing price or debt", "id": "chapter-15-fundraising-and-finance-quality-of-earnings-reconcile-the-claim-before-sizing-price-or-debt" }, { "level": 3, "text": "Diligence and stop-gate matrix", "id": "chapter-15-fundraising-and-finance-diligence-and-stop-gate-matrix" }, { "level": 3, "text": "Governance and transition: control begins before close", "id": "chapter-15-fundraising-and-finance-governance-and-transition-control-begins-before-close" }, { "level": 3, "text": "Applied exercise — acquisition investment committee memo", "id": "chapter-15-fundraising-and-finance-applied-exercise-acquisition-investment-committee-memo" }, { "level": 2, "text": "How To Get Started: Fundraising Execution", "id": "chapter-15-fundraising-and-finance-how-to-get-started-fundraising-execution" }, { "level": 3, "text": "Illustrative Quick Version (4-6 Weeks): Pitch Development + Outreach Kickoff", "id": "chapter-15-fundraising-and-finance-illustrative-quick-version-4-6-weeks-pitch-development-outreach-kickoff" }, { "level": 4, "text": "Week 1: Pitch Deck Development", "id": "chapter-15-fundraising-and-finance-week-1-pitch-deck-development" }, { "level": 4, "text": "Week 2: Financial Model + Cap Table", "id": "chapter-15-fundraising-and-finance-week-2-financial-model-cap-table" }, { "level": 4, "text": "Week 3: Investor List Creation", "id": "chapter-15-fundraising-and-finance-week-3-investor-list-creation" }, { "level": 4, "text": "Illustrative Week 4-6: First Investor Meetings", "id": "chapter-15-fundraising-and-finance-illustrative-week-4-6-first-investor-meetings" }, { "level": 4, "text": "Quick Version Outputs", "id": "chapter-15-fundraising-and-finance-quick-version-outputs" }, { "level": 3, "text": "Illustrative Detailed Version (16-20 Weeks): Full Fundraising Cycle", "id": "chapter-15-fundraising-and-finance-illustrative-detailed-version-16-20-weeks-full-fundraising-cycle" }, { "level": 4, "text": "Phase 1: Preparation (Weeks 1-4)", "id": "chapter-15-fundraising-and-finance-phase-1-preparation-weeks-1-4" }, { "level": 4, "text": "Phase 2: Outreach (illustrative Weeks 5-8)", "id": "chapter-15-fundraising-and-finance-phase-2-outreach-illustrative-weeks-5-8" }, { "level": 4, "text": "Phase 3: First Meetings + Iteration (Weeks 9-12)", "id": "chapter-15-fundraising-and-finance-phase-3-first-meetings-iteration-weeks-9-12" }, { "level": 4, "text": "Phase 4: Due Diligence (illustrative Weeks 13-16)", "id": "chapter-15-fundraising-and-finance-phase-4-due-diligence-illustrative-weeks-13-16" }, { "level": 4, "text": "Phase 5: Term Sheet Negotiation + Closing (Weeks 17-20)", "id": "chapter-15-fundraising-and-finance-phase-5-term-sheet-negotiation-closing-weeks-17-20" }, { "level": 4, "text": "Detailed Version: Week-by-Week Metrics", "id": "chapter-15-fundraising-and-finance-detailed-version-week-by-week-metrics" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-15-fundraising-and-finance-common-pitfalls" }, { "level": 3, "text": "Measurement Framework", "id": "chapter-15-fundraising-and-finance-measurement-framework" }, { "level": 4, "text": "Outreach Metrics", "id": "chapter-15-fundraising-and-finance-outreach-metrics" }, { "level": 4, "text": "Pitch Meeting Metrics", "id": "chapter-15-fundraising-and-finance-pitch-meeting-metrics" }, { "level": 4, "text": "Due Diligence Metrics", "id": "chapter-15-fundraising-and-finance-due-diligence-metrics" }, { "level": 4, "text": "Closing Metrics", "id": "chapter-15-fundraising-and-finance-closing-metrics" }, { "level": 4, "text": "Overall Fundraise Health Dashboard", "id": "chapter-15-fundraising-and-finance-overall-fundraise-health-dashboard" }, { "level": 3, "text": "Red Flags: When Fundraising Is Stalling", "id": "chapter-15-fundraising-and-finance-red-flags-when-fundraising-is-stalling" }, { "level": 4, "text": "Outreach Red Flags", "id": "chapter-15-fundraising-and-finance-outreach-red-flags" }, { "level": 4, "text": "Pitch Meeting Red Flags", "id": "chapter-15-fundraising-and-finance-pitch-meeting-red-flags" }, { "level": 4, "text": "Due Diligence Red Flags", "id": "chapter-15-fundraising-and-finance-due-diligence-red-flags" }, { "level": 4, "text": "Closing Red Flags", "id": "chapter-15-fundraising-and-finance-closing-red-flags" }, { "level": 4, "text": "Overall Health Red Flags", "id": "chapter-15-fundraising-and-finance-overall-health-red-flags" }, { "level": 4, "text": "How to Use Red Flags", "id": "chapter-15-fundraising-and-finance-how-to-use-red-flags" }, { "level": 2, "text": "Why This Matters: Mental Models & Fundraising Wisdom", "id": "chapter-15-fundraising-and-finance-why-this-matters-mental-models-fundraising-wisdom" }, { "level": 3, "text": "Mental Models: Why Investors Value What They Value", "id": "chapter-15-fundraising-and-finance-mental-models-why-investors-value-what-they-value" }, { "level": 4, "text": "1. Momentum as One Evidence Pattern", "id": "chapter-15-fundraising-and-finance-1-momentum-as-one-evidence-pattern" }, { "level": 4, "text": "2. Unit Economics as a Scenario Model", "id": "chapter-15-fundraising-and-finance-2-unit-economics-as-a-scenario-model" }, { "level": 4, "text": "3. Narrative as a Testable Explanation", "id": "chapter-15-fundraising-and-finance-3-narrative-as-a-testable-explanation" }, { "level": 4, "text": "4. Diversified Capital: Why Multiple Funding Sources De-Risk Execution", "id": "chapter-15-fundraising-and-finance-4-diversified-capital-why-multiple-funding-sources-de-risk-execution" }, { "level": 3, "text": "Evidence-Grounded Diligence Cases", "id": "chapter-15-fundraising-and-finance-evidence-grounded-diligence-cases" }, { "level": 3, "text": "Competing Schools: Different Capital Philosophies", "id": "chapter-15-fundraising-and-finance-competing-schools-different-capital-philosophies" }, { "level": 4, "text": "1. Venture Capital vs. Strategic Investment (Growth vs. Synergy)", "id": "chapter-15-fundraising-and-finance-1-venture-capital-vs-strategic-investment-growth-vs-synergy" }, { "level": 4, "text": "2. Financing Choice as a Portfolio of Constraints and Options", "id": "chapter-15-fundraising-and-finance-2-financing-choice-as-a-portfolio-of-constraints-and-options" }, { "level": 4, "text": "3. Term-Package Effects Across Stakeholders", "id": "chapter-15-fundraising-and-finance-3-term-package-effects-across-stakeholders" }, { "level": 3, "text": "Context-Dependent Capital Strategy", "id": "chapter-15-fundraising-and-finance-context-dependent-capital-strategy" }, { "level": 2, "text": "Summary: Fundraising & Finance Frameworks", "id": "chapter-15-fundraising-and-finance-summary-fundraising-finance-frameworks" }, { "level": 2, "text": "Constructed Case: Series A Financing Decision", "id": "chapter-15-fundraising-and-finance-constructed-case-series-a-financing-decision" }, { "level": 2, "text": "Operating Manual: Your 16-Week Series A Fundraising Cycle", "id": "chapter-15-fundraising-and-finance-operating-manual-your-16-week-series-a-fundraising-cycle" }, { "level": 3, "text": "Phase 1: Preparation & Strategy (Weeks 1-4)", "id": "chapter-15-fundraising-and-finance-phase-1-preparation-strategy-weeks-1-4" }, { "level": 3, "text": "Phase 2: Outreach & Initial Meetings (Weeks 5-8)", "id": "chapter-15-fundraising-and-finance-phase-2-outreach-initial-meetings-weeks-5-8" }, { "level": 3, "text": "Phase 3: Due Diligence & Term Sheet (Weeks 9-12)", "id": "chapter-15-fundraising-and-finance-phase-3-due-diligence-term-sheet-weeks-9-12" }, { "level": 3, "text": "Phase 4: Closing & Post-Close (Weeks 13-16)", "id": "chapter-15-fundraising-and-finance-phase-4-closing-post-close-weeks-13-16" }, { "level": 3, "text": "Resource Requirements", "id": "chapter-15-fundraising-and-finance-resource-requirements" }, { "level": 3, "text": "Red Flags & Warning Signals", "id": "chapter-15-fundraising-and-finance-red-flags-warning-signals" }, { "level": 3, "text": "Contingency Triggers", "id": "chapter-15-fundraising-and-finance-contingency-triggers" }, { "level": 3, "text": "Timeline Variance", "id": "chapter-15-fundraising-and-finance-timeline-variance" }, { "level": 3, "text": "Measurement Dashboard", "id": "chapter-15-fundraising-and-finance-measurement-dashboard" }, { "level": 3, "text": "Success vs Struggling: How to Know", "id": "chapter-15-fundraising-and-finance-success-vs-struggling-how-to-know" } ], "figures": [ { "id": "chapter-15-fundraising-and-finance-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "393c2470b3266e4b0988a46e21b2d1fe12db70cf98f56bf0f27c5919223e6f80" }, { "id": "chapter-15-fundraising-and-finance-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "e7db68afb5585d9743b47007f433fe9798fd11d11842ceccccd6cef6e78aea20" }, { "id": "chapter-15-fundraising-and-finance-figure-3", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "4c799d1c8d2061ce448241d5384cdce4cb6022b3c8c27c8d74f9fb2818c13298" } ], "tables": [ { "id": "chapter-15-fundraising-and-finance-table-1", "caption": "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.", "headers": [ "Investor", "Intro Date", "1st Meeting", "Interest Level", "Feedback", "Next Step" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2 }, { "id": "chapter-15-fundraising-and-finance-table-2", "caption": "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.", "headers": [ "Method", "Decision use", "Main controls" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-15-fundraising-and-finance-table-3", "caption": "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.", "headers": [ "Provision family", "Questions to model and escalate" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 10 }, { "id": "chapter-15-fundraising-and-finance-table-4", "caption": "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.", "headers": [ "Round", "New money", "Pre-money", "Post-money", "New investor", "Founders after round" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2 }, { "id": "chapter-15-fundraising-and-finance-table-5", "caption": "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.", "headers": [ "What VC Says", "Possible interpretations to test", "What to Do" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8 }, { "id": "chapter-15-fundraising-and-finance-table-6", "caption": "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.", "headers": [ "Item", "Year 1", "Year 2", "Year 3", "Year 4", "Year 5" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 20 }, { "id": "chapter-15-fundraising-and-finance-table-7", "caption": "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.", "headers": [ "Asset", "Year 1", "Year 5" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 19 }, { "id": "chapter-15-fundraising-and-finance-table-8", "caption": "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.", "headers": [ "Month", "Jan", "Feb", "Mar", "Apr", "May", "Jun" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 14 }, { "id": "chapter-15-fundraising-and-finance-table-9", "caption": "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.", "headers": [ "Option", "Decision questions" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-15-fundraising-and-finance-table-10", "caption": "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.", "headers": [ "Question", "Convertible note", "SAFE" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-15-fundraising-and-finance-table-11", "caption": "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.", "headers": [ "Dimension", "Questions to resolve" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8 }, { "id": "chapter-15-fundraising-and-finance-table-12", "caption": "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.", "headers": [ "Observed pattern", "Competing hypotheses to test", "Possible next evidence or response" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-15-fundraising-and-finance-table-13", "caption": "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.", "headers": [ "Term", "Investor Scenario", "Founder Scenario", "Constructed Comparison Input" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-15-fundraising-and-finance-table-14", "caption": "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.", "headers": [ "Constructed uses", "Amount", "Constructed sources", "Amount" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-15-fundraising-and-finance-table-15", "caption": "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.", "headers": [ "Constructed QoE bridge", "Amount", "Evidence judgment" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-15-fundraising-and-finance-table-16", "caption": "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.", "headers": [ "Workstream", "Minimum evidence package", "Escalate, reprice, restructure, or stop when" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-15-fundraising-and-finance-table-17", "caption": "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.", "headers": [ "Stage", "Required decisions and evidence" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-15-fundraising-and-finance-table-18", "caption": "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.", "headers": [ "Investor Name", "Firm", "Stage", "Sector", "Geography", "Intro Path", "Tier", "Contact Date" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2 }, { "id": "chapter-15-fundraising-and-finance-table-19", "caption": "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.", "headers": [ "Investor", "Meeting Date", "Interest Level", "Key Feedback", "Materials Sent", "Next Step", "Timeline" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2 }, { "id": "chapter-15-fundraising-and-finance-table-20", "caption": "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.", "headers": [ "Week", "Activity", "Meetings", "Outputs" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-15-fundraising-and-finance-table-21", "caption": "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.", "headers": [ "Week", "Phase", "Key Activities", "Meetings", "Outputs" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 9 }, { "id": "chapter-15-fundraising-and-finance-table-22", "caption": "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.", "headers": [ "Theme", "Count", "Example Quote", "Action" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-15-fundraising-and-finance-table-23", "caption": "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.", "headers": [ "Source", "Cost", "Control", "Best For" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-15-fundraising-and-finance-table-24", "caption": "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.", "headers": [ "Dimension", "Venture Capital", "Strategic Investment" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-15-fundraising-and-finance-table-25", "caption": "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.", "headers": [ "Provision", "Questions to model" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-15-fundraising-and-finance-table-26", "caption": "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.", "headers": [ "Decision area", "Evidence to examine" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-15-fundraising-and-finance-table-27", "caption": "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.", "headers": [ "Framework", "When to Use", "Effort Required" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 11 }, { "id": "chapter-15-fundraising-and-finance-table-28", "caption": "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.", "headers": [ "Holder", "Pre-round", "Post-round calculation", "Post-round" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-15-fundraising-and-finance-table-29", "caption": "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.", "headers": [ "Phase", "Key Metric", "Local rule", "Actual", "Status" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 11 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-15-fundraising-and-finance.html", "outboundSlugs": [ "appendix-b-contrarian-business-perspectives", "chapter-02-business-law-governance-and-ethics", "chapter-04-financial-analysis-and-valuation", "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "chapter-02-business-law-governance-and-ethics", "chapter-04-financial-analysis-and-valuation", "chapter-13-startup-foundations" ] }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions", "slug": "chapter-16-ai-strategy-and-data-driven-decisions", "kind": "chapter", "number": 16, "title": "AI Strategy and Data-Driven Decisions", "part": "Part 4: AI and Digital Transformation", "summary": "AI strategy, data readiness, model governance, decision systems, operating models, and business-case design.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "relatedSlugs": [ "chapter-17-leading-digital-transformation", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/part4-ai-digital/16-ai-strategy-data-driven-decisions.md", "outputPath": "index.html#chapter-16-ai-strategy-and-data-driven-decisions", "markdownPath": "markdown/chapter-16-ai-strategy-and-data-driven-decisions.md", "wordCount": 22182, "checksum": "35a46c5be15e81a90640218c0b62e2df9d3539e62e438a6c56fdcd5a0db72988", "sourceIds": [ "BB-C16-S01", "BB-C16-S04", "BB-C16-S05", "BB-C16-S06", "BB-C16-S08", "BB-C16-S03", "BB-C16-S02", "BB-C16-S07", "BB-C16-S09", "BB-C16-S10", "BB-C16-S14", "BB-C16-S11", "BB-C16-S12", "BB-C16-S13" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-16-ai-strategy-and-data-driven-decisions-executive-summary" }, { "level": 3, "text": "Decision outcomes and authority boundary", "id": "chapter-16-ai-strategy-and-data-driven-decisions-decision-outcomes-and-authority-boundary" }, { "level": 2, "text": "1. AI Opportunity Assessment Matrix", "id": "chapter-16-ai-strategy-and-data-driven-decisions-1-ai-opportunity-assessment-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections" }, { "level": 2, "text": "2. Build vs. Buy vs. Partner Decision Tree", "id": "chapter-16-ai-strategy-and-data-driven-decisions-2-build-vs-buy-vs-partner-decision-tree" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections-2" }, { "level": 2, "text": "3. AI Maturity Model", "id": "chapter-16-ai-strategy-and-data-driven-decisions-3-ai-maturity-model" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-3" }, { "level": 3, "text": "Visual Representation: AI Maturity Model - Capability Diagnostic", "id": "chapter-16-ai-strategy-and-data-driven-decisions-visual-representation-ai-maturity-model-capability-diagnostic" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections-3" }, { "level": 2, "text": "4. Use Case Prioritization Framework", "id": "chapter-16-ai-strategy-and-data-driven-decisions-4-use-case-prioritization-framework" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections-4" }, { "level": 2, "text": "5. ROI Calculation for AI Projects", "id": "chapter-16-ai-strategy-and-data-driven-decisions-5-roi-calculation-for-ai-projects" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections-5" }, { "level": 2, "text": "6. Ethical AI Framework", "id": "chapter-16-ai-strategy-and-data-driven-decisions-6-ethical-ai-framework" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections-6" }, { "level": 2, "text": "7. Data Readiness Assessment", "id": "chapter-16-ai-strategy-and-data-driven-decisions-7-data-readiness-assessment" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections-7" }, { "level": 2, "text": "8. MLOps Pipeline and Change-Control Framework", "id": "chapter-16-ai-strategy-and-data-driven-decisions-8-mlops-pipeline-and-change-control-framework" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections-8" }, { "level": 2, "text": "9. Agentic AI Operating and Control Model", "id": "chapter-16-ai-strategy-and-data-driven-decisions-9-agentic-ai-operating-and-control-model" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-9" }, { "level": 3, "text": "Authority record before execution", "id": "chapter-16-ai-strategy-and-data-driven-decisions-authority-record-before-execution" }, { "level": 3, "text": "Agent execution-control loop", "id": "chapter-16-ai-strategy-and-data-driven-decisions-agent-execution-control-loop" }, { "level": 3, "text": "Applied control exercise", "id": "chapter-16-ai-strategy-and-data-driven-decisions-applied-control-exercise" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections-9" }, { "level": 2, "text": "10. AI Governance Structure", "id": "chapter-16-ai-strategy-and-data-driven-decisions-10-ai-governance-structure" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections-10" }, { "level": 2, "text": "11. Change Management for AI Adoption", "id": "chapter-16-ai-strategy-and-data-driven-decisions-11-change-management-for-ai-adoption" }, { "level": 3, "text": "Overview", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-11" }, { "level": 3, "text": "How to Apply", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-apply-11" }, { "level": 3, "text": "So What for Managers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-so-what-for-managers-11" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-16-ai-strategy-and-data-driven-decisions-limits-and-critiques-11" }, { "level": 3, "text": "Connections", "id": "chapter-16-ai-strategy-and-data-driven-decisions-connections-11" }, { "level": 2, "text": "How To Get Started", "id": "chapter-16-ai-strategy-and-data-driven-decisions-how-to-get-started" }, { "level": 3, "text": "Quick Version (3-4 Weeks; illustrative path): Rapid AI Opportunity Assessment & Pilot Selection", "id": "chapter-16-ai-strategy-and-data-driven-decisions-quick-version-3-4-weeks-illustrative-path-rapid-ai-opportunity-assessment-pilot-selection" }, { "level": 4, "text": "Week 1: AI Opportunity Assessment", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-1-ai-opportunity-assessment" }, { "level": 4, "text": "Week 2: ICP Use Case Selection", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-2-icp-use-case-selection" }, { "level": 4, "text": "Week 3: Pilot Planning", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-3-pilot-planning" }, { "level": 4, "text": "Week 4: Pilot-Readiness Handoff", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-4-pilot-readiness-handoff" }, { "level": 3, "text": "Detailed Version (12-16 Weeks; illustrative path): Strategy, Governance, and Pilot Design", "id": "chapter-16-ai-strategy-and-data-driven-decisions-detailed-version-12-16-weeks-illustrative-path-strategy-governance-and-pilot-design" }, { "level": 4, "text": "Phase 1: AI Opportunity Assessment (Weeks 1-2)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-1-ai-opportunity-assessment-weeks-1-2" }, { "level": 4, "text": "Phase 2: Use Case Prioritization & Business Case (Weeks 3-4)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-2-use-case-prioritization-business-case-weeks-3-4" }, { "level": 4, "text": "Phase 3: AI Governance & Ethics (Weeks 5-6)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-3-ai-governance-ethics-weeks-5-6" }, { "level": 4, "text": "Phase 4: First Pilot Planning (Weeks 7-8)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-4-first-pilot-planning-weeks-7-8" }, { "level": 4, "text": "Phase 5: Pilot Execution (Weeks 9-12)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-5-pilot-execution-weeks-9-12" }, { "level": 4, "text": "Phase 6: Deployment & Scaling (Weeks 13-16)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-6-deployment-scaling-weeks-13-16" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-16-ai-strategy-and-data-driven-decisions-common-pitfalls" }, { "level": 3, "text": "Measurement Framework", "id": "chapter-16-ai-strategy-and-data-driven-decisions-measurement-framework" }, { "level": 3, "text": "Red Flags: When AI Strategy Is Failing", "id": "chapter-16-ai-strategy-and-data-driven-decisions-red-flags-when-ai-strategy-is-failing" }, { "level": 2, "text": "Contrarian Reality Check: What They Don't Tell You About AI", "id": "chapter-16-ai-strategy-and-data-driven-decisions-contrarian-reality-check-what-they-don-t-tell-you-about-ai" }, { "level": 3, "text": "The Uncomfortable Truths About AI in 2026", "id": "chapter-16-ai-strategy-and-data-driven-decisions-the-uncomfortable-truths-about-ai-in-2026" }, { "level": 2, "text": "Why This Matters: Mental Models & AI Wisdom", "id": "chapter-16-ai-strategy-and-data-driven-decisions-why-this-matters-mental-models-ai-wisdom" }, { "level": 3, "text": "Mental Models: Why AI Strategy Works", "id": "chapter-16-ai-strategy-and-data-driven-decisions-mental-models-why-ai-strategy-works" }, { "level": 3, "text": "Failure Case Studies: What Happens When AI Strategy Fails", "id": "chapter-16-ai-strategy-and-data-driven-decisions-failure-case-studies-what-happens-when-ai-strategy-fails" }, { "level": 3, "text": "Competing Schools of Thought in AI Strategy", "id": "chapter-16-ai-strategy-and-data-driven-decisions-competing-schools-of-thought-in-ai-strategy" }, { "level": 3, "text": "Stage Dependency: How AI Strategy Changes with Maturity", "id": "chapter-16-ai-strategy-and-data-driven-decisions-stage-dependency-how-ai-strategy-changes-with-maturity" }, { "level": 2, "text": "Operating Manual: The Canonical Constructed 16-Week AI Use-Case Pilot", "id": "chapter-16-ai-strategy-and-data-driven-decisions-operating-manual-the-canonical-constructed-16-week-ai-use-case-pilot" }, { "level": 3, "text": "Overview: 16-Week Timeline", "id": "chapter-16-ai-strategy-and-data-driven-decisions-overview-16-week-timeline" }, { "level": 3, "text": "Phase 1: Opportunity Assessment (Weeks 1-2)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-1-opportunity-assessment-weeks-1-2" }, { "level": 4, "text": "Week 1: Use Case Brainstorming & Scoring", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-1-use-case-brainstorming-scoring" }, { "level": 4, "text": "Week 2: Detailed Use Case Assessment", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-2-detailed-use-case-assessment" }, { "level": 3, "text": "Phase 2: Business Case Development (Weeks 3-4)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-2-business-case-development-weeks-3-4" }, { "level": 4, "text": "Week 3: ROI Modeling & Resource Planning", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-3-roi-modeling-resource-planning" }, { "level": 4, "text": "Week 4: Risk Assessment & Business Case Finalization", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-4-risk-assessment-business-case-finalization" }, { "level": 3, "text": "Phase 3: Data Assessment & Governance (Weeks 5-6)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-3-data-assessment-governance-weeks-5-6" }, { "level": 4, "text": "Week 5: Data Discovery & Quality Assessment", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-5-data-discovery-quality-assessment" }, { "level": 4, "text": "Week 6: Data Governance & Compliance", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-6-data-governance-compliance" }, { "level": 3, "text": "Phase 4: Pilot Development (Weeks 7-10)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-4-pilot-development-weeks-7-10" }, { "level": 4, "text": "Weeks 7-8: Model Development Sprint 1", "id": "chapter-16-ai-strategy-and-data-driven-decisions-weeks-7-8-model-development-sprint-1" }, { "level": 4, "text": "Weeks 9-10: Model Validation & Testing", "id": "chapter-16-ai-strategy-and-data-driven-decisions-weeks-9-10-model-validation-testing" }, { "level": 3, "text": "Phase 5: Pilot Deployment (Weeks 11-14)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-5-pilot-deployment-weeks-11-14" }, { "level": 4, "text": "Week 11-12: Production Deployment", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-11-12-production-deployment" }, { "level": 4, "text": "Week 13-14: Full Rollout & Monitoring", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-13-14-full-rollout-monitoring" }, { "level": 3, "text": "Phase 6: Pilot Review & Scaling Plan (Weeks 15-16)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-phase-6-pilot-review-scaling-plan-weeks-15-16" }, { "level": 4, "text": "Week 15: Pilot Retrospective", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-15-pilot-retrospective" }, { "level": 4, "text": "Week 16: Scaling Plan", "id": "chapter-16-ai-strategy-and-data-driven-decisions-week-16-scaling-plan" }, { "level": 3, "text": "Red Flags by Week (Warning Signals)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-red-flags-by-week-warning-signals" }, { "level": 3, "text": "Resource Requirements (Detailed)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-resource-requirements-detailed" }, { "level": 3, "text": "Decision Gates (Detailed)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-decision-gates-detailed" }, { "level": 3, "text": "Contingency Triggers", "id": "chapter-16-ai-strategy-and-data-driven-decisions-contingency-triggers" }, { "level": 3, "text": "Timeline Variance (Adapt to Your Situation)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-timeline-variance-adapt-to-your-situation" }, { "level": 3, "text": "Measurement Dashboard (Track Weekly)", "id": "chapter-16-ai-strategy-and-data-driven-decisions-measurement-dashboard-track-weekly" }, { "level": 3, "text": "Success Criteria & Benchmarks", "id": "chapter-16-ai-strategy-and-data-driven-decisions-success-criteria-benchmarks" }, { "level": 2, "text": "Chapter Summary", "id": "chapter-16-ai-strategy-and-data-driven-decisions-chapter-summary" } ], "figures": [ { "id": "chapter-16-ai-strategy-and-data-driven-decisions-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C16-S01", "BB-C16-S06", "BB-C16-S08" ], "provenanceStatus": "constructed", "checksum": "c04a56020c689abb1abe6291af183bf85fa6ab7836a08101d35ed13201bc53da" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "45fda5dc723ea3a8c8f1416ce469f780ea2fb6bb7d3ecd2ae2d69e1c7d7b6f46" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C16-S09", "BB-C16-S10" ], "provenanceStatus": "constructed", "checksum": "1a9bd0ef79e8d00f248e1df089526126a2b089664cbeb248de7a1ec2db3de50b" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-figure-4", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C16-S01", "BB-C16-S04", "BB-C16-S10", "BB-C16-S14" ], "provenanceStatus": "constructed", "checksum": "c8142facdb9b86259c48eb20a08284813d7c59c5c3568aaaf3a6f3545718381a" } ], "tables": [ { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-1", "caption": "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.", "headers": [ "", "Low Feasibility", "High Feasibility" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2 }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-2", "caption": "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.", "headers": [ "Use Case", "Value", "Feasibility", "Quadrant" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-3", "caption": "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.", "headers": [ "Use Case", "Impact", "Confidence", "Ease", "Data Quality", "Score", "Priority" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-4", "caption": "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.", "headers": [ "Control", "Managerial question", "Minimum record" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8 }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-5", "caption": "Table 16.5: Constructed model-selection comparison aid (Use case | Model approach | Cost | When to use). Product names, prices, and performance are intentionally omitted because they change; validate current options and controls before procurement.", "headers": [ "Use Case", "Best Model", "Cost", "When to Use" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7 }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-6", "caption": "Table 16.6: Constructed pilot measurement dashboard (Week | Phase | Activity | Deliverable | Status | Red flags). Timing, thresholds, status values, and red flags are local planning inputs; define them against the approved use case and risk boundary.", "headers": [ "Week", "Phase", "Key Activity", "Deliverable", "Status", "Red Flags" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-16-ai-strategy-and-data-driven-decisions.html", "outboundSlugs": [ "chapter-04-financial-analysis-and-valuation", "chapter-07-organizational-behavior-and-leadership", "chapter-09-problem-structuring", "chapter-17-leading-digital-transformation", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-b-contrarian-business-perspectives", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-09-problem-structuring", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-17-leading-digital-transformation", "slug": "chapter-17-leading-digital-transformation", "kind": "chapter", "number": 17, "title": "Leading Digital Transformation", "part": "Part 4: AI and Digital Transformation", "summary": "Digital maturity, transformation leadership, architecture, operating model change, governance, and failure modes.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "relatedSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-04-financial-analysis-and-valuation", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-14-go-to-market-strategy", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/part4-ai-digital/17-leading-digital-transformation.md", "outputPath": "index.html#chapter-17-leading-digital-transformation", "markdownPath": "markdown/chapter-17-leading-digital-transformation.md", "wordCount": 21490, "checksum": "eb516d53316e020b6ebce039ca58c33fb9f37108b61e3bfdbcd6499c2e84222b", "sourceIds": [ "BB-C17-S01", "BB-C17-S06", "BB-C17-S07", "BB-C17-S02", "BB-C17-S03", "BB-C17-S04", "BB-C17-S05", "BB-C17-S08", "BB-C17-S12", "BB-C17-S13", "BB-C17-S14", "BB-C17-S21", "BB-C17-S15", "BB-C17-S17", "BB-C17-S18", "BB-C17-S16", "BB-C17-S19", "BB-C17-S20", "BB-C17-S10", "BB-C17-S11", "BB-C17-S09" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-17-leading-digital-transformation-executive-summary" }, { "level": 2, "text": "1. The Digital Transformation Lifecycle Model", "id": "chapter-17-leading-digital-transformation-1-the-digital-transformation-lifecycle-model" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview" }, { "level": 3, "text": "When to Use", "id": "chapter-17-leading-digital-transformation-when-to-use" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-17-leading-digital-transformation-key-questions-to-answer" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-17-leading-digital-transformation-data-inputs-required" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-17-leading-digital-transformation-common-pitfalls" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-17-leading-digital-transformation-digital-age-modifications" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-17-leading-digital-transformation-quick-reference-card" }, { "level": 3, "text": "Cross-Framework References", "id": "chapter-17-leading-digital-transformation-cross-framework-references" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections" }, { "level": 2, "text": "2. Vision & Strategy Canvas for Transformation", "id": "chapter-17-leading-digital-transformation-2-vision-strategy-canvas-for-transformation" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview-2" }, { "level": 3, "text": "When to Use", "id": "chapter-17-leading-digital-transformation-when-to-use-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply-2" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-17-leading-digital-transformation-key-questions-to-answer-2" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-17-leading-digital-transformation-data-inputs-required-2" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-17-leading-digital-transformation-common-pitfalls-2" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-17-leading-digital-transformation-digital-age-modifications-2" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-17-leading-digital-transformation-quick-reference-card-2" }, { "level": 3, "text": "Cross-Framework References", "id": "chapter-17-leading-digital-transformation-cross-framework-references-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections-2" }, { "level": 2, "text": "3. Kotter's 8-Step Model for Change (Digital Adaptation)", "id": "chapter-17-leading-digital-transformation-3-kotter-s-8-step-model-for-change-digital-adaptation" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview-3" }, { "level": 3, "text": "When to Use", "id": "chapter-17-leading-digital-transformation-when-to-use-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply-3" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-17-leading-digital-transformation-key-questions-to-answer-3" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-17-leading-digital-transformation-data-inputs-required-3" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-17-leading-digital-transformation-common-pitfalls-3" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-17-leading-digital-transformation-digital-age-modifications-3" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-17-leading-digital-transformation-quick-reference-card-3" }, { "level": 3, "text": "Cross-Framework References", "id": "chapter-17-leading-digital-transformation-cross-framework-references-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections-3" }, { "level": 2, "text": "4. Technology Adoption Curve & The \"Chasm\"", "id": "chapter-17-leading-digital-transformation-4-technology-adoption-curve-the-chasm" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview-4" }, { "level": 3, "text": "Visual Representation", "id": "chapter-17-leading-digital-transformation-visual-representation" }, { "level": 3, "text": "When to Use", "id": "chapter-17-leading-digital-transformation-when-to-use-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply-4" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-17-leading-digital-transformation-key-questions-to-answer-4" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-17-leading-digital-transformation-data-inputs-required-4" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-17-leading-digital-transformation-common-pitfalls-4" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-17-leading-digital-transformation-digital-age-modifications-4" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-17-leading-digital-transformation-quick-reference-card-4" }, { "level": 3, "text": "Cross-Framework References", "id": "chapter-17-leading-digital-transformation-cross-framework-references-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections-4" }, { "level": 2, "text": "5. The \"Ambidextrous Organization\" Model (Explore vs. Exploit)", "id": "chapter-17-leading-digital-transformation-5-the-ambidextrous-organization-model-explore-vs-exploit" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview-5" }, { "level": 3, "text": "When to Use", "id": "chapter-17-leading-digital-transformation-when-to-use-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply-5" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-17-leading-digital-transformation-key-questions-to-answer-5" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-17-leading-digital-transformation-data-inputs-required-5" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-17-leading-digital-transformation-common-pitfalls-5" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-17-leading-digital-transformation-digital-age-modifications-5" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-17-leading-digital-transformation-quick-reference-card-5" }, { "level": 3, "text": "Cross-Framework References", "id": "chapter-17-leading-digital-transformation-cross-framework-references-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections-5" }, { "level": 2, "text": "6. Digital Maturity Assessment Framework", "id": "chapter-17-leading-digital-transformation-6-digital-maturity-assessment-framework" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview-6" }, { "level": 3, "text": "When to Use", "id": "chapter-17-leading-digital-transformation-when-to-use-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply-6" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-17-leading-digital-transformation-key-questions-to-answer-6" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-17-leading-digital-transformation-data-inputs-required-6" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-17-leading-digital-transformation-common-pitfalls-6" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-17-leading-digital-transformation-digital-age-modifications-6" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-17-leading-digital-transformation-quick-reference-card-6" }, { "level": 3, "text": "Cross-Framework References", "id": "chapter-17-leading-digital-transformation-cross-framework-references-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections-6" }, { "level": 2, "text": "7. Business Capability Mapping for Modernization", "id": "chapter-17-leading-digital-transformation-7-business-capability-mapping-for-modernization" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview-7" }, { "level": 3, "text": "When to Use", "id": "chapter-17-leading-digital-transformation-when-to-use-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply-7" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-17-leading-digital-transformation-key-questions-to-answer-7" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-17-leading-digital-transformation-data-inputs-required-7" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-17-leading-digital-transformation-common-pitfalls-7" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-17-leading-digital-transformation-digital-age-modifications-7" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-17-leading-digital-transformation-quick-reference-card-7" }, { "level": 3, "text": "Cross-Framework References", "id": "chapter-17-leading-digital-transformation-cross-framework-references-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections-7" }, { "level": 2, "text": "8. OKRs for Transformation (Objectives & Key Results)", "id": "chapter-17-leading-digital-transformation-8-okrs-for-transformation-objectives-key-results" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview-8" }, { "level": 3, "text": "When to Use", "id": "chapter-17-leading-digital-transformation-when-to-use-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply-8" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-17-leading-digital-transformation-key-questions-to-answer-8" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-17-leading-digital-transformation-data-inputs-required-8" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-17-leading-digital-transformation-common-pitfalls-8" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-17-leading-digital-transformation-digital-age-modifications-8" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-17-leading-digital-transformation-quick-reference-card-8" }, { "level": 3, "text": "Cross-Framework References", "id": "chapter-17-leading-digital-transformation-cross-framework-references-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections-8" }, { "level": 2, "text": "9. Digital Governance & Operating Model", "id": "chapter-17-leading-digital-transformation-9-digital-governance-operating-model" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview-9" }, { "level": 3, "text": "When to Use", "id": "chapter-17-leading-digital-transformation-when-to-use-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply-9" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-17-leading-digital-transformation-key-questions-to-answer-9" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-17-leading-digital-transformation-data-inputs-required-9" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-17-leading-digital-transformation-common-pitfalls-9" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-17-leading-digital-transformation-digital-age-modifications-9" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-17-leading-digital-transformation-quick-reference-card-9" }, { "level": 3, "text": "Cross-Framework References", "id": "chapter-17-leading-digital-transformation-cross-framework-references-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections-9" }, { "level": 2, "text": "10. Storytelling & Communication Playbook for Change", "id": "chapter-17-leading-digital-transformation-10-storytelling-communication-playbook-for-change" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview-10" }, { "level": 3, "text": "When to Use", "id": "chapter-17-leading-digital-transformation-when-to-use-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply-10" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-17-leading-digital-transformation-key-questions-to-answer-10" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-17-leading-digital-transformation-data-inputs-required-10" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-17-leading-digital-transformation-common-pitfalls-10" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-17-leading-digital-transformation-digital-age-modifications-10" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-17-leading-digital-transformation-quick-reference-card-10" }, { "level": 3, "text": "Cross-Framework References", "id": "chapter-17-leading-digital-transformation-cross-framework-references-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections-10" }, { "level": 2, "text": "11. Digital and AI Sustainability System Boundary", "id": "chapter-17-leading-digital-transformation-11-digital-and-ai-sustainability-system-boundary" }, { "level": 3, "text": "Overview", "id": "chapter-17-leading-digital-transformation-overview-11" }, { "level": 3, "text": "How to Apply", "id": "chapter-17-leading-digital-transformation-how-to-apply-11" }, { "level": 3, "text": "Measure the service system, not only the data center", "id": "chapter-17-leading-digital-transformation-measure-the-service-system-not-only-the-data-center" }, { "level": 3, "text": "Keep four measurement questions separate", "id": "chapter-17-leading-digital-transformation-keep-four-measurement-questions-separate" }, { "level": 3, "text": "A seven-step measurement-to-decision workflow", "id": "chapter-17-leading-digital-transformation-a-seven-step-measurement-to-decision-workflow" }, { "level": 3, "text": "Measurement is not a marketing claim", "id": "chapter-17-leading-digital-transformation-measurement-is-not-a-marketing-claim" }, { "level": 3, "text": "System-boundary and rebound visual", "id": "chapter-17-leading-digital-transformation-system-boundary-and-rebound-visual" }, { "level": 3, "text": "Applied decision exercise — scale the AI feature, redesign it, or stop", "id": "chapter-17-leading-digital-transformation-applied-decision-exercise-scale-the-ai-feature-redesign-it-or-stop" }, { "level": 3, "text": "So What for Managers", "id": "chapter-17-leading-digital-transformation-so-what-for-managers-11" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-17-leading-digital-transformation-limits-and-critiques-11" }, { "level": 3, "text": "Connections", "id": "chapter-17-leading-digital-transformation-connections-11" }, { "level": 2, "text": "Contrarian Reality Check: What They Don't Tell You About Digital Transformation", "id": "chapter-17-leading-digital-transformation-contrarian-reality-check-what-they-don-t-tell-you-about-digital-transformation" }, { "level": 3, "text": "The Uncomfortable Truths About Digital Transformation", "id": "chapter-17-leading-digital-transformation-the-uncomfortable-truths-about-digital-transformation" }, { "level": 2, "text": "Applied Decision Exercise: Modernize, Redesign, Source, or Stop", "id": "chapter-17-leading-digital-transformation-applied-decision-exercise-modernize-redesign-source-or-stop" }, { "level": 2, "text": "Authored Connections", "id": "chapter-17-leading-digital-transformation-authored-connections" } ], "figures": [ { "id": "chapter-17-leading-digital-transformation-figure-1", "type": "mermaid", "caption": "Figure 17.1. Transformation portfolio learning loop. The diagram shows a reusable sequence for framing, testing, scaling, embedding, and re-evaluating an initiative; arrows do not imply a universal order or duration. Source basis: digital transformation leadership and maturity framing, adapted as an author planning aid. [BB-C17-S01] [BB-C17-S06]", "textEquivalent": "Text equivalent: Leaders frame a capability hypothesis, run a bounded test, scale only when business, technical, adoption, workforce, security, and governance gates are met, embed the capability in operations, and then optimize, retire, or return to a revised hypothesis.", "sourceIds": [ "BB-C17-S01", "BB-C17-S06" ], "provenanceStatus": "source-linked", "checksum": "fa2c1d05ef2fd29c2c888011a5a1ee21d30872dfd72793e4de5456e383248c02" }, { "id": "chapter-17-leading-digital-transformation-figure-2", "type": "mermaid", "caption": "Figure 17.2. Rogers adopter-category shares with Moore's chasm overlaid. Rogers's approximate ideal-type shares are shown as a sequence, while Moore's chasm is a later commercial-market interpretation between early adopters and the early majority. The overlay is a teaching synthesis, not a universal adoption trajectory. [BB-C17-S03] [BB-C17-S04]", "textEquivalent": "Text equivalent: The figure moves from innovators to early adopters, crosses a highlighted conceptual gap, and then proceeds to early majority, late majority, and laggards. The categories describe a population-level diffusion model and should not be used to stereotype individuals.", "sourceIds": [ "BB-C17-S03", "BB-C17-S04" ], "provenanceStatus": "source-linked", "checksum": "c49f1dccd637b7f7c4a0ba2ccf7a398b62a91e3af9fec7a2e37172e7b821825d" }, { "id": "chapter-17-leading-digital-transformation-figure-3", "type": "mermaid", "caption": "Figure 17.3. Evidence-to-roadmap maturity loop. The author-created loop connects dimensions, evidence-based current state, target capabilities, gaps, portfolio choices, funding, and reassessment. A score is a discussion input, not an outcome measure. Source basis: digital-maturity research. [BB-C17-S06]", "textEquivalent": "Text equivalent: Define context-specific dimensions; assess current capabilities with evidence and uncertainty; define only the target capabilities needed by strategy; identify gaps; compare initiatives and dependencies; fund a roadmap; then reassess both capability and realized value.", "sourceIds": [ "BB-C17-S06" ], "provenanceStatus": "constructed", "checksum": "a6de4d220fa1a8f1f1f0a2061125ad332f3ad5116d0c445745adb59373d310a1" }, { "id": "chapter-17-leading-digital-transformation-figure-4", "type": "mermaid", "caption": "Figure 17.4. Digital operating-model feedback system. The author-created diagram links strategy, governance forums, product teams, decision rights, delivery, outcomes, and feedback. It is a relationship map, not a prescribed organization chart. Source basis: IT-governance decision-rights research. [BB-C17-S07]", "textEquivalent": "Text equivalent: Strategy informs both governance forums and delivery teams. Governance allocates decision rights; teams deliver within those boundaries. Outcomes and control evidence feed back into strategy, funding, standards, and team design.", "sourceIds": [ "BB-C17-S07" ], "provenanceStatus": "constructed", "checksum": "15a09d84eb546587f3a5cafd95137e75c53ca55f71c1e2d09f831324427b1281" }, { "id": "chapter-17-leading-digital-transformation-figure-5", "type": "mermaid", "caption": "Figure 17.5. Digital-service lifecycle boundary, decision loop, and claims gate. This author-created visual places operational data-center impacts inside a broader system of hardware, supply chain, networks, devices, use, and end of life. It also separates an internal decision estimate from an external environmental claim and makes demand rebound visible. It is a boundary prompt, not a calculation method or verified footprint. [BB-C17-S12] [BB-C17-S13] [BB-C17-S14] [BB-C17-S17] [BB-C17-S19] [BB-C17-S20]", "textEquivalent": "Text equivalent: Define the service outcome and demand scenarios, then inventory materials and manufacturing, data-center operation, networks, end-user devices, and maintenance or end of life across operational energy, carbon, water, and material impacts. Allocate shared systems and test uncertainty. Efficiency may lower cost or latency and increase demand, so compare both intensity and absolute totals. The resulting estimate can inform a redesign, stage, cap, procure, monitor, or stop decision; any external environmental claim passes through a separate substantiation, qualification, legal, assurance, and approval gate.", "sourceIds": [ "BB-C17-S12", "BB-C17-S13", "BB-C17-S14", "BB-C17-S17", "BB-C17-S19", "BB-C17-S20", "BB-C17-S21" ], "provenanceStatus": "constructed", "checksum": "9984d399062311a2ba224b636c27b4b0acb42df2aaeb68e58ce5b3e1f3b595aa" } ], "tables": [ { "id": "chapter-17-leading-digital-transformation-table-1", "caption": "Table 17.1: Author-created framework comparison aid (Framework | Primary Use | Time Required | Complexity | Strategic Impact). Time, complexity, and impact labels are teaching inputs, not universal benchmarks; define local criteria and evidence before using them for investment decisions.", "headers": [ "Framework", "Primary Use", "Time Required", "Complexity", "Strategic Impact" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 11 }, { "id": "chapter-17-leading-digital-transformation-table-2", "caption": "Table 17.2: Author-created suitability aid (Organization Type | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against local strategy, capacity, obligations, and evidence.", "headers": [ "Organization Type", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-17-leading-digital-transformation-table-3", "caption": "Table 17.3: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; time, team, output, and update choices should be defined for the initiative rather than treated as universal requirements.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-17-leading-digital-transformation-table-4", "caption": "Table 17.4: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against local strategy, capacity, obligations, and evidence.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-17-leading-digital-transformation-table-5", "caption": "Table 17.5: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; workshop duration, team size, outputs, and update choices should be defined for the initiative.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-17-leading-digital-transformation-table-6", "caption": "Table 17.6: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against local strategy, capacity, obligations, and evidence.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-17-leading-digital-transformation-table-7", "caption": "Table 17.7: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; duration, roles, outputs, and update choices should be defined for the change context.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-17-leading-digital-transformation-table-8", "caption": "Table 17.8: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against the product, adoption, and evidence context.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-17-leading-digital-transformation-table-9", "caption": "Table 17.9: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; duration, roles, outputs, and update choices should be defined for the adoption context.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-17-leading-digital-transformation-table-10", "caption": "Table 17.10: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against local portfolio, capability, and evidence conditions.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-17-leading-digital-transformation-table-11", "caption": "Table 17.11: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; duration, roles, outputs, and update choices should be defined for the ambidexterity context.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-17-leading-digital-transformation-table-12", "caption": "Table 17.12: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against the maturity question, decision owner, and evidence available.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-17-leading-digital-transformation-table-13", "caption": "Table 17.13: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; assessment effort, roles, outputs, and update choices should be defined for the organization.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-17-leading-digital-transformation-table-14", "caption": "Table 17.14: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against the capability decision, dependencies, and evidence available.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-17-leading-digital-transformation-table-15", "caption": "Table 17.15: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; effort, roles, outputs, and update choices should be defined for the capability portfolio.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-17-leading-digital-transformation-table-16", "caption": "Table 17.16: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against the outcome definition, incentives, and evidence quality.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-17-leading-digital-transformation-table-17", "caption": "Table 17.17: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; cadence, roles, outputs, and update choices should be defined for the operating context.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-17-leading-digital-transformation-table-18", "caption": "Table 17.18: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against decision rights, controls, capacity, and evidence.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-17-leading-digital-transformation-table-19", "caption": "Table 17.19: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; roles, outputs, and update choices should be defined for the operating model in scope.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-17-leading-digital-transformation-table-20", "caption": "Table 17.20: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against audience, purpose, accessibility, privacy, and evidence conditions.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-17-leading-digital-transformation-table-21", "caption": "Table 17.21: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; communication roles, outputs, and update choices should be defined for the transformation context.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-17-leading-digital-transformation-table-22", "caption": "Table 17.22: Author-created lifecycle-boundary checklist (Lifecycle surface | What can fall inside the boundary | Managerial evidence and common boundary failure). This is a scoping aid, not a complete inventory or verified footprint; state the chosen functional unit, allocation rules, data quality, uncertainty, and exclusions.", "headers": [ "Lifecycle surface", "What can fall inside the boundary", "Managerial evidence and common boundary failure" ], "sourceIds": [ "BB-C17-S14", "BB-C17-S13", "BB-C17-S21", "BB-C17-S15", "BB-C17-S17", "BB-C17-S12", "BB-C17-S18" ], "provenanceStatus": "constructed", "rowCount": 7 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-17-leading-digital-transformation.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-04-financial-analysis-and-valuation", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-14-go-to-market-strategy", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers" ] }, { "id": "chapter-18-digital-business-models-and-platform-economics", "slug": "chapter-18-digital-business-models-and-platform-economics", "kind": "chapter", "number": 18, "title": "Digital Business Models and Platform Economics", "part": "Part 4: AI and Digital Transformation", "summary": "Platforms, network effects, ecosystems, APIs, data monetization, digital revenue models, and platform failures.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "relatedSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-14-go-to-market-strategy", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/part4-ai-digital/18-digital-business-models-platform-economics.md", "outputPath": "index.html#chapter-18-digital-business-models-and-platform-economics", "markdownPath": "markdown/chapter-18-digital-business-models-and-platform-economics.md", "wordCount": 8001, "checksum": "690ae97ff6ddfb9d3517fa546bb979ead8b4c0e999ac82b4b52ec90fd4c5dde1", "sourceIds": [ "BB-C18-S01", "BB-C18-S03", "BB-C18-S06", "BB-C18-S16", "BB-C18-S17", "BB-C18-S18", "BB-C18-S19", "BB-C18-S02", "BB-C18-S04", "BB-C18-S05", "BB-C18-S07", "BB-C18-S10", "BB-C18-S08", "BB-C18-S09", "BB-C18-S11", "BB-C18-S12", "BB-C18-S13" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-18-digital-business-models-and-platform-economics-executive-summary" }, { "level": 2, "text": "1. Platform Economy Framework", "id": "chapter-18-digital-business-models-and-platform-economics-1-platform-economy-framework" }, { "level": 3, "text": "Overview", "id": "chapter-18-digital-business-models-and-platform-economics-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-18-digital-business-models-and-platform-economics-how-to-apply" }, { "level": 3, "text": "Pipeline (Traditional) Business", "id": "chapter-18-digital-business-models-and-platform-economics-pipeline-traditional-business" }, { "level": 3, "text": "Platform or multisided business", "id": "chapter-18-digital-business-models-and-platform-economics-platform-or-multisided-business" }, { "level": 3, "text": "1. Supply Side (Producers)", "id": "chapter-18-digital-business-models-and-platform-economics-1-supply-side-producers" }, { "level": 3, "text": "2. Demand Side (Consumers)", "id": "chapter-18-digital-business-models-and-platform-economics-2-demand-side-consumers" }, { "level": 3, "text": "3. Platform Matching/Search", "id": "chapter-18-digital-business-models-and-platform-economics-3-platform-matching-search" }, { "level": 3, "text": "4. Trust/Payment System", "id": "chapter-18-digital-business-models-and-platform-economics-4-trust-payment-system" }, { "level": 3, "text": "1A. Platform Regulation and Complementor Strategy", "id": "chapter-18-digital-business-models-and-platform-economics-1a-platform-regulation-and-complementor-strategy" }, { "level": 3, "text": "Platform-regulation issue boundary", "id": "chapter-18-digital-business-models-and-platform-economics-platform-regulation-issue-boundary" }, { "level": 3, "text": "Managerial issue map", "id": "chapter-18-digital-business-models-and-platform-economics-managerial-issue-map" }, { "level": 3, "text": "Platform-regulation routing visual", "id": "chapter-18-digital-business-models-and-platform-economics-platform-regulation-routing-visual" }, { "level": 3, "text": "Constructed complementor exercise", "id": "chapter-18-digital-business-models-and-platform-economics-constructed-complementor-exercise" }, { "level": 3, "text": "So What for Managers", "id": "chapter-18-digital-business-models-and-platform-economics-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-18-digital-business-models-and-platform-economics-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-18-digital-business-models-and-platform-economics-connections" }, { "level": 2, "text": "2. Network Effects Typology", "id": "chapter-18-digital-business-models-and-platform-economics-2-network-effects-typology" }, { "level": 3, "text": "Overview", "id": "chapter-18-digital-business-models-and-platform-economics-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-18-digital-business-models-and-platform-economics-how-to-apply-2" }, { "level": 3, "text": "Type 1: Direct Network Effects", "id": "chapter-18-digital-business-models-and-platform-economics-type-1-direct-network-effects" }, { "level": 3, "text": "Type 2: Indirect Network Effects (Two-Sided)", "id": "chapter-18-digital-business-models-and-platform-economics-type-2-indirect-network-effects-two-sided" }, { "level": 3, "text": "Type 3: Data Network Effects", "id": "chapter-18-digital-business-models-and-platform-economics-type-3-data-network-effects" }, { "level": 3, "text": "Type 4: Data Exchange Effects", "id": "chapter-18-digital-business-models-and-platform-economics-type-4-data-exchange-effects" }, { "level": 3, "text": "Step 1: Identify Network Effect Type", "id": "chapter-18-digital-business-models-and-platform-economics-step-1-identify-network-effect-type" }, { "level": 3, "text": "Step 2: Start with Strongest Effect", "id": "chapter-18-digital-business-models-and-platform-economics-step-2-start-with-strongest-effect" }, { "level": 3, "text": "Step 3: Measure & Optimize", "id": "chapter-18-digital-business-models-and-platform-economics-step-3-measure-optimize" }, { "level": 3, "text": "Step 4: Scale", "id": "chapter-18-digital-business-models-and-platform-economics-step-4-scale" }, { "level": 3, "text": "So What for Managers", "id": "chapter-18-digital-business-models-and-platform-economics-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-18-digital-business-models-and-platform-economics-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-18-digital-business-models-and-platform-economics-connections-2" }, { "level": 2, "text": "3. Digital Revenue Models", "id": "chapter-18-digital-business-models-and-platform-economics-3-digital-revenue-models" }, { "level": 3, "text": "Overview", "id": "chapter-18-digital-business-models-and-platform-economics-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-18-digital-business-models-and-platform-economics-how-to-apply-3" }, { "level": 3, "text": "Model 1: Advertising", "id": "chapter-18-digital-business-models-and-platform-economics-model-1-advertising" }, { "level": 3, "text": "Model 2: Subscription (SaaS)", "id": "chapter-18-digital-business-models-and-platform-economics-model-2-subscription-saas" }, { "level": 3, "text": "Model 3: Marketplace Commission", "id": "chapter-18-digital-business-models-and-platform-economics-model-3-marketplace-commission" }, { "level": 3, "text": "Model 4: Freemium", "id": "chapter-18-digital-business-models-and-platform-economics-model-4-freemium" }, { "level": 3, "text": "Model 5: Usage-Based / Pay-as-You-Go", "id": "chapter-18-digital-business-models-and-platform-economics-model-5-usage-based-pay-as-you-go" }, { "level": 3, "text": "Model 6: Licensing / White Label", "id": "chapter-18-digital-business-models-and-platform-economics-model-6-licensing-white-label" }, { "level": 3, "text": "Model 7: Affiliate / Partnership Commission", "id": "chapter-18-digital-business-models-and-platform-economics-model-7-affiliate-partnership-commission" }, { "level": 3, "text": "Model 8: Hybrid / Tiered Pricing", "id": "chapter-18-digital-business-models-and-platform-economics-model-8-hybrid-tiered-pricing" }, { "level": 3, "text": "Model 9: Data Sales", "id": "chapter-18-digital-business-models-and-platform-economics-model-9-data-sales" }, { "level": 3, "text": "Model 10: Support / Services", "id": "chapter-18-digital-business-models-and-platform-economics-model-10-support-services" }, { "level": 3, "text": "So What for Managers", "id": "chapter-18-digital-business-models-and-platform-economics-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-18-digital-business-models-and-platform-economics-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-18-digital-business-models-and-platform-economics-connections-3" }, { "level": 2, "text": "4. API Economy & Ecosystem Value", "id": "chapter-18-digital-business-models-and-platform-economics-4-api-economy-ecosystem-value" }, { "level": 3, "text": "Overview", "id": "chapter-18-digital-business-models-and-platform-economics-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-18-digital-business-models-and-platform-economics-how-to-apply-4" }, { "level": 3, "text": "Step 1: Build Core Product", "id": "chapter-18-digital-business-models-and-platform-economics-step-1-build-core-product" }, { "level": 3, "text": "Step 2: Open APIs", "id": "chapter-18-digital-business-models-and-platform-economics-step-2-open-apis" }, { "level": 3, "text": "Step 3: Incent Developers", "id": "chapter-18-digital-business-models-and-platform-economics-step-3-incent-developers" }, { "level": 3, "text": "Step 4: Build App Marketplace", "id": "chapter-18-digital-business-models-and-platform-economics-step-4-build-app-marketplace" }, { "level": 3, "text": "So What for Managers", "id": "chapter-18-digital-business-models-and-platform-economics-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-18-digital-business-models-and-platform-economics-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-18-digital-business-models-and-platform-economics-connections-4" }, { "level": 2, "text": "5. Data Monetization and Rights-to-Value Gate", "id": "chapter-18-digital-business-models-and-platform-economics-5-data-monetization-and-rights-to-value-gate" }, { "level": 3, "text": "Overview", "id": "chapter-18-digital-business-models-and-platform-economics-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-18-digital-business-models-and-platform-economics-how-to-apply-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-18-digital-business-models-and-platform-economics-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-18-digital-business-models-and-platform-economics-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-18-digital-business-models-and-platform-economics-connections-5" }, { "level": 2, "text": "6. Digital Ecosystem Mapping", "id": "chapter-18-digital-business-models-and-platform-economics-6-digital-ecosystem-mapping" }, { "level": 3, "text": "Overview", "id": "chapter-18-digital-business-models-and-platform-economics-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-18-digital-business-models-and-platform-economics-how-to-apply-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-18-digital-business-models-and-platform-economics-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-18-digital-business-models-and-platform-economics-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-18-digital-business-models-and-platform-economics-connections-6" }, { "level": 2, "text": "7. Cybersecurity Risk Matrix", "id": "chapter-18-digital-business-models-and-platform-economics-7-cybersecurity-risk-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-18-digital-business-models-and-platform-economics-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-18-digital-business-models-and-platform-economics-how-to-apply-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-18-digital-business-models-and-platform-economics-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-18-digital-business-models-and-platform-economics-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-18-digital-business-models-and-platform-economics-connections-7" }, { "level": 2, "text": "8. Digital KPI Dashboard", "id": "chapter-18-digital-business-models-and-platform-economics-8-digital-kpi-dashboard" }, { "level": 3, "text": "Overview", "id": "chapter-18-digital-business-models-and-platform-economics-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-18-digital-business-models-and-platform-economics-how-to-apply-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-18-digital-business-models-and-platform-economics-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-18-digital-business-models-and-platform-economics-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-18-digital-business-models-and-platform-economics-connections-8" }, { "level": 2, "text": "9. Automation Opportunity Assessment", "id": "chapter-18-digital-business-models-and-platform-economics-9-automation-opportunity-assessment" }, { "level": 3, "text": "Overview", "id": "chapter-18-digital-business-models-and-platform-economics-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-18-digital-business-models-and-platform-economics-how-to-apply-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-18-digital-business-models-and-platform-economics-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-18-digital-business-models-and-platform-economics-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-18-digital-business-models-and-platform-economics-connections-9" }, { "level": 2, "text": "10. Digital Transformation Roadmap", "id": "chapter-18-digital-business-models-and-platform-economics-10-digital-transformation-roadmap" }, { "level": 3, "text": "Overview", "id": "chapter-18-digital-business-models-and-platform-economics-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-18-digital-business-models-and-platform-economics-how-to-apply-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-18-digital-business-models-and-platform-economics-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-18-digital-business-models-and-platform-economics-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-18-digital-business-models-and-platform-economics-connections-10" }, { "level": 3, "text": "Platform Design Tests, Not Universal Laws", "id": "chapter-18-digital-business-models-and-platform-economics-platform-design-tests-not-universal-laws" }, { "level": 3, "text": "Summary: Digital Business Model Frameworks", "id": "chapter-18-digital-business-models-and-platform-economics-summary-digital-business-model-frameworks" }, { "level": 3, "text": "Case Example: Digital Transformation (Retail Company)", "id": "chapter-18-digital-business-models-and-platform-economics-case-example-digital-transformation-retail-company" }, { "level": 3, "text": "Applied Decision Exercise: Design or Reject a Platform Model", "id": "chapter-18-digital-business-models-and-platform-economics-applied-decision-exercise-design-or-reject-a-platform-model" }, { "level": 3, "text": "Authored Connections", "id": "chapter-18-digital-business-models-and-platform-economics-authored-connections" } ], "figures": [ { "id": "chapter-18-digital-business-models-and-platform-economics-figure-1", "type": "mermaid", "caption": "Figure 18.1. Platform interaction and learning loop. The author-created diagram links relevant supply, matching, trusted transaction, repeat demand, and data-informed improvement. It is a hypothesis map, not a causal guarantee. Source basis: platform and multisided-market strategy. [BB-C18-S01] [BB-C18-S03] [BB-C18-S06]", "textEquivalent": "Text equivalent: Relevant supply enables discovery and matching; a trusted transaction may create repeat demand; transaction evidence can improve matching. Each link must be tested, and negative effects such as congestion, low quality, fraud, discrimination, or exit can weaken or reverse the loop.", "sourceIds": [ "BB-C18-S01", "BB-C18-S03", "BB-C18-S06" ], "provenanceStatus": "constructed", "checksum": "ec1192d03a772cdfe49b45ceb8cfa02f01fb63b50989073e695c71edd12076f2" }, { "id": "chapter-18-digital-business-models-and-platform-economics-figure-2", "type": "mermaid", "caption": "Figure 18.2. Platform-regulation and complementor decision route (constructed). The route separates scope, current legal evidence, technical/product facts, strategic consequences, and accountable approval. It does not infer that the DMA applies or prescribe a legal conclusion. [BB-C18-S16] [BB-C18-S17] [BB-C18-S18]", "textEquivalent": "Text equivalent: Define the jurisdiction, entity, role, service, and user journey. Check current legislation, designation and service decisions, compliance measures, enforcement, and appeals. Map the actual product flow and data practice to potentially relevant obligations with legal and technical owners. Model strategic and economic consequences, choose redesign, request, negotiate, launch, stage, challenge, or stop, and monitor for changes.", "sourceIds": [ "BB-C18-S16", "BB-C18-S17", "BB-C18-S18" ], "provenanceStatus": "constructed", "checksum": "4267e80254dcc32dbb3ace0d301bbdb8a1c61d52f7022dddb89d2e4ecd7b32d6" } ], "tables": [ { "id": "chapter-18-digital-business-models-and-platform-economics-table-1", "caption": "Table 18.1: Author-created platform-regulation issue map (Decision area | Questions | Evidence and owner). This is a routing aid, not a legal conclusion; current law, facts, decisions, enforcement, and qualified counsel determine the applicable analysis.", "headers": [ "Decision area", "Questions for the platform or complementor", "Evidence and owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-2", "caption": "Table 18.2: Author-created revenue-model comparison aid (Decision dimension | Evidence to compare across candidate models). The dimensions expose local assumptions; they do not rank monetization models or supply market benchmarks.", "headers": [ "Decision dimension", "Evidence to compare across candidate models" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-3", "caption": "Table 18.3: Author-created data-rights and value gate (Gate | Managerial question | Minimum evidence | Decision owner). The gate is a scoping aid, not legal advice or a complete privacy, intellectual-property, competition, employment, sector, or consumer-law analysis.", "headers": [ "Gate", "Managerial question", "Minimum evidence", "Decision owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-4", "caption": "Table 18.4: Author-created ecosystem structure map (Role | Required contribution | Dependency or bottleneck | Evidence and response). Roles and dependencies are constructed decision inputs; they are not claims about any named company or current market share.", "headers": [ "Role", "Required contribution", "Dependency or bottleneck", "Evidence and response" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-5", "caption": "Table 18.5: Author-created platform security risk matrix (Scenario | Asset or boundary | Harm to test | Evidence and response). The scenarios are constructed prompts; assess actual likelihood, impact, controls, and obligations locally with security and legal owners.", "headers": [ "Scenario", "Asset or boundary", "Harm to test", "Evidence and response" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-6", "caption": "Table 18.6: Author-created digital KPI dashboard (Hypothesis | Leading signal | Outcome measure | Guardrail | Decision rule). Metric definitions, targets, and thresholds are local inputs; none is a market benchmark.", "headers": [ "Hypothesis", "Leading signal", "Outcome measure", "Guardrail", "Decision rule" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-7", "caption": "Table 18.7: Author-created automation opportunity assessment (Workflow | Candidate change | Evidence to collect | Human and control gate). The options are constructed prompts; they do not predict job loss, productivity, ROI, or safe deployment without local evidence and affected-party review.", "headers": [ "Workflow", "Candidate change", "Evidence to collect", "Human and control gate" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-8", "caption": "Table 18.8: Author-created digital transformation roadmap (Stage | Decision question | Evidence package | Gate). Stage names and timing are local planning inputs; no fixed duration or sequence is a universal transformation recipe.", "headers": [ "Stage", "Decision question", "Evidence package", "Gate" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-9", "caption": "Table 9. Framework / When to Use / Effort Required", "headers": [ "Framework", "When to Use", "Effort Required" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 10 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-18-digital-business-models-and-platform-economics.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-14-go-to-market-strategy", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-17-leading-digital-transformation", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers", "slug": "chapter-19-cybersecurity-and-risk-management-for-managers", "kind": "chapter", "number": 19, "title": "Cybersecurity and Risk Management for Managers", "part": "Part 4: AI and Digital Transformation", "summary": "Cyber risk, controls, incident response, supply chain risk, governance, and executive-level security decisions.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "relatedSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-04-financial-analysis-and-valuation", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-20-the-ethics-of-ai-and-data", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/part4-ai-digital/19-cybersecurity-risk-management-for-managers.md", "outputPath": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers", "markdownPath": "markdown/chapter-19-cybersecurity-and-risk-management-for-managers.md", "wordCount": 14016, "checksum": "9c18276c008699e5fc711668269661cc2dda3b2527a578eead5c2f0527f1bf2a", "sourceIds": [ "BB-C19-S01", "BB-C19-S04", "BB-C19-S05", "BB-C19-S07", "BB-C19-S08", "BB-C19-S03", "BB-C19-S06" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-executive-summary" }, { "level": 2, "text": "1. The NIST Cybersecurity Framework", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-1-the-nist-cybersecurity-framework" }, { "level": 3, "text": "Overview", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-overview" }, { "level": 3, "text": "When to Use", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-when-to-use" }, { "level": 3, "text": "How to Apply", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-how-to-apply" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-key-questions-to-answer" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-data-inputs-required" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-common-pitfalls" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-digital-age-modifications" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-quick-reference-card" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-related-frameworks" }, { "level": 3, "text": "So What for Managers", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-connections" }, { "level": 2, "text": "2. Cyber Risk Quantification (FAIR Model Simplified)", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-2-cyber-risk-quantification-fair-model-simplified" }, { "level": 3, "text": "Overview", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-overview-2" }, { "level": 3, "text": "When to Use", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-when-to-use-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-how-to-apply-2" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-key-questions-to-answer-2" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-data-inputs-required-2" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-common-pitfalls-2" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-digital-age-modifications-2" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-quick-reference-card-2" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-related-frameworks-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-connections-2" }, { "level": 2, "text": "3. The \"Crown Jewels\" Analysis for Asset Protection", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-3-the-crown-jewels-analysis-for-asset-protection" }, { "level": 3, "text": "Overview", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-overview-3" }, { "level": 3, "text": "When to Use", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-when-to-use-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-how-to-apply-3" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-key-questions-to-answer-3" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-data-inputs-required-3" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-common-pitfalls-3" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-digital-age-modifications-3" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-quick-reference-card-3" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-related-frameworks-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-connections-3" }, { "level": 2, "text": "4. The Cyber Defense Matrix", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-4-the-cyber-defense-matrix" }, { "level": 3, "text": "Overview", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-overview-4" }, { "level": 3, "text": "Visual Representation", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-visual-representation" }, { "level": 3, "text": "When to Use", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-when-to-use-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-how-to-apply-4" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-key-questions-to-answer-4" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-data-inputs-required-4" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-common-pitfalls-4" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-digital-age-modifications-4" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-quick-reference-card-4" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-related-frameworks-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-connections-4" }, { "level": 2, "text": "5. Vendor & Supply Chain Risk Assessment Model", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-5-vendor-supply-chain-risk-assessment-model" }, { "level": 3, "text": "Overview", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-overview-5" }, { "level": 3, "text": "When to Use", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-when-to-use-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-how-to-apply-5" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-key-questions-to-answer-5" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-data-inputs-required-5" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-common-pitfalls-5" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-digital-age-modifications-5" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-quick-reference-card-5" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-related-frameworks-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-connections-5" }, { "level": 2, "text": "6. The \"Assume Breach\" Mindset", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-6-the-assume-breach-mindset" }, { "level": 3, "text": "Overview", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-overview-6" }, { "level": 3, "text": "When to Use", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-when-to-use-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-how-to-apply-6" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-key-questions-to-answer-6" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-data-inputs-required-6" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-common-pitfalls-6" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-digital-age-modifications-6" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-quick-reference-card-6" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-related-frameworks-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-connections-6" }, { "level": 2, "text": "7. Incident Response Plan on a Page", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-7-incident-response-plan-on-a-page" }, { "level": 3, "text": "Overview", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-overview-7" }, { "level": 3, "text": "When to Use", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-when-to-use-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-how-to-apply-7" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-key-questions-to-answer-7" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-data-inputs-required-7" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-common-pitfalls-7" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-digital-age-modifications-7" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-quick-reference-card-7" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-related-frameworks-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-connections-7" }, { "level": 2, "text": "8. Continuous Contextual Access Decisions (CARTA as a Proprietary Reference)", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-8-continuous-contextual-access-decisions-carta-as-a-proprietary-reference" }, { "level": 3, "text": "Overview", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-overview-8" }, { "level": 3, "text": "When to Use", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-when-to-use-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-how-to-apply-8" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-key-questions-to-answer-8" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-data-inputs-required-8" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-common-pitfalls-8" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-digital-age-modifications-8" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-quick-reference-card-8" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-related-frameworks-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-connections-8" }, { "level": 2, "text": "9. Ransomware Decision-Making Framework", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-9-ransomware-decision-making-framework" }, { "level": 3, "text": "Overview", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-overview-9" }, { "level": 3, "text": "When to Use", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-when-to-use-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-how-to-apply-9" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-key-questions-to-answer-9" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-data-inputs-required-9" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-common-pitfalls-9" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-digital-age-modifications-9" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-quick-reference-card-9" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-related-frameworks-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-connections-9" }, { "level": 2, "text": "10. Human-Centered Security Culture", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-10-human-centered-security-culture" }, { "level": 3, "text": "Overview", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-overview-10" }, { "level": 3, "text": "When to Use", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-when-to-use-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-how-to-apply-10" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-key-questions-to-answer-10" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-data-inputs-required-10" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-common-pitfalls-10" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-digital-age-modifications-10" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-quick-reference-card-10" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-related-frameworks-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-connections-10" }, { "level": 3, "text": "Authored Connections", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-authored-connections" } ], "figures": [ { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-figure-1", "type": "mermaid", "caption": "Figure 19.1. Classic Cyber Defense Matrix with a CSF 2.0 Govern overlay. The five operational rows preserve the source taxonomy; Govern is added as an outer layer affecting every asset and operational Function. [BB-C19-S01] [BB-C19-S06]", "textEquivalent": "Text equivalent: Devices, applications, networks, data, and users are considered across Identify, Protect, Detect, Respond, and Recover. A separate Govern layer sets context, strategy, roles, policy, oversight, and supply-chain governance for all cells. Empty cells are prompts for risk analysis, not automatic control purchases.", "sourceIds": [ "BB-C19-S01", "BB-C19-S06" ], "provenanceStatus": "source-linked", "checksum": "749b4a5dca006d84c468bd20c6e78defd33d0c343dbd022bf288293145893cc9" } ], "tables": [ { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-1", "caption": "Table 1. Framework / Primary Use / Time Required", "headers": [ "Framework", "Primary Use", "Time Required", "Complexity", "Strategic Impact" ], "sourceIds": [ "BB-C19-S01" ], "provenanceStatus": "source-linked", "rowCount": 10 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-2", "caption": "Table 2. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-3", "caption": "Table 3. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-4", "caption": "Table 4. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [ "BB-C19-S03" ], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-5", "caption": "Table 5. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-6", "caption": "Table 6. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-7", "caption": "Table 7. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-8", "caption": "Table 8. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-9", "caption": "Table 9. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-10", "caption": "Table 10. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-11", "caption": "Table 11. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-12", "caption": "Table 12. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-13", "caption": "Table 13. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-14", "caption": "Table 14. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-15", "caption": "Table 15. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-16", "caption": "Table 16. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [ "BB-C19-S01" ], "provenanceStatus": "source-linked", "rowCount": 5 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-17", "caption": "Table 17. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-18", "caption": "Table 18. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-19", "caption": "Table 19. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-20", "caption": "Table 20. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-21", "caption": "Table 21. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-19-cybersecurity-and-risk-management-for-managers.html", "outboundSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-04-financial-analysis-and-valuation", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-20-the-ethics-of-ai-and-data", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-06-operations-and-supply-chain", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy" ] }, { "id": "chapter-20-the-ethics-of-ai-and-data", "slug": "chapter-20-the-ethics-of-ai-and-data", "kind": "chapter", "number": 20, "title": "The Ethics of AI and Data", "part": "Part 4: AI and Digital Transformation", "summary": "AI ethics, bias, privacy, accountability, transparency, governance, and responsible data use.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "relatedSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-05-marketing-and-customer-analytics", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/part4-ai-digital/20-the-ethics-of-ai-and-data.md", "outputPath": "index.html#chapter-20-the-ethics-of-ai-and-data", "markdownPath": "markdown/chapter-20-the-ethics-of-ai-and-data.md", "wordCount": 15212, "checksum": "01f481f949071e068f455662ba9c5f2d11d4e9d8130af57907e746a8eee8cb74", "sourceIds": [ "BB-C20-S01", "BB-C20-S03", "BB-C20-S02", "BB-C20-S04", "BB-C20-S05", "BB-C20-S06", "BB-C20-S12", "BB-C20-S13", "BB-C20-S14", "BB-C20-S07", "BB-C20-S15" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-20-the-ethics-of-ai-and-data-executive-summary" }, { "level": 2, "text": "Ethical Reasoning Gate: Before the Checklist", "id": "chapter-20-the-ethics-of-ai-and-data-ethical-reasoning-gate-before-the-checklist" }, { "level": 2, "text": "1. The FATE (Fairness, Accountability, Transparency, Explainability) Framework", "id": "chapter-20-the-ethics-of-ai-and-data-1-the-fate-fairness-accountability-transparency-explainability-framework" }, { "level": 3, "text": "Overview", "id": "chapter-20-the-ethics-of-ai-and-data-overview" }, { "level": 3, "text": "When to Use", "id": "chapter-20-the-ethics-of-ai-and-data-when-to-use" }, { "level": 3, "text": "How to Apply", "id": "chapter-20-the-ethics-of-ai-and-data-how-to-apply" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-20-the-ethics-of-ai-and-data-key-questions-to-answer" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-20-the-ethics-of-ai-and-data-data-inputs-required" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-20-the-ethics-of-ai-and-data-common-pitfalls" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-20-the-ethics-of-ai-and-data-digital-age-modifications" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-20-the-ethics-of-ai-and-data-quick-reference-card" }, { "level": 3, "text": "So What for Managers", "id": "chapter-20-the-ethics-of-ai-and-data-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-20-the-ethics-of-ai-and-data-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-20-the-ethics-of-ai-and-data-connections" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-20-the-ethics-of-ai-and-data-related-frameworks" }, { "level": 2, "text": "2. Algorithmic Bias: Detection & Mitigation Patterns", "id": "chapter-20-the-ethics-of-ai-and-data-2-algorithmic-bias-detection-mitigation-patterns" }, { "level": 3, "text": "Overview", "id": "chapter-20-the-ethics-of-ai-and-data-overview-2" }, { "level": 3, "text": "When to Use", "id": "chapter-20-the-ethics-of-ai-and-data-when-to-use-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-20-the-ethics-of-ai-and-data-how-to-apply-2" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-20-the-ethics-of-ai-and-data-key-questions-to-answer-2" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-20-the-ethics-of-ai-and-data-data-inputs-required-2" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-20-the-ethics-of-ai-and-data-common-pitfalls-2" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-20-the-ethics-of-ai-and-data-digital-age-modifications-2" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-20-the-ethics-of-ai-and-data-quick-reference-card-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-20-the-ethics-of-ai-and-data-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-20-the-ethics-of-ai-and-data-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-20-the-ethics-of-ai-and-data-connections-2" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-20-the-ethics-of-ai-and-data-related-frameworks-2" }, { "level": 2, "text": "3. The Model Card & Datasheet for Transparency", "id": "chapter-20-the-ethics-of-ai-and-data-3-the-model-card-datasheet-for-transparency" }, { "level": 3, "text": "Overview", "id": "chapter-20-the-ethics-of-ai-and-data-overview-3" }, { "level": 3, "text": "When to Use", "id": "chapter-20-the-ethics-of-ai-and-data-when-to-use-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-20-the-ethics-of-ai-and-data-how-to-apply-3" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-20-the-ethics-of-ai-and-data-key-questions-to-answer-3" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-20-the-ethics-of-ai-and-data-data-inputs-required-3" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-20-the-ethics-of-ai-and-data-common-pitfalls-3" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-20-the-ethics-of-ai-and-data-digital-age-modifications-3" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-20-the-ethics-of-ai-and-data-quick-reference-card-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-20-the-ethics-of-ai-and-data-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-20-the-ethics-of-ai-and-data-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-20-the-ethics-of-ai-and-data-connections-3" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-20-the-ethics-of-ai-and-data-related-frameworks-3" }, { "level": 2, "text": "4. The Privacy by Design (PbD) Framework", "id": "chapter-20-the-ethics-of-ai-and-data-4-the-privacy-by-design-pbd-framework" }, { "level": 3, "text": "Overview", "id": "chapter-20-the-ethics-of-ai-and-data-overview-4" }, { "level": 3, "text": "When to Use", "id": "chapter-20-the-ethics-of-ai-and-data-when-to-use-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-20-the-ethics-of-ai-and-data-how-to-apply-4" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-20-the-ethics-of-ai-and-data-key-questions-to-answer-4" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-20-the-ethics-of-ai-and-data-data-inputs-required-4" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-20-the-ethics-of-ai-and-data-common-pitfalls-4" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-20-the-ethics-of-ai-and-data-digital-age-modifications-4" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-20-the-ethics-of-ai-and-data-quick-reference-card-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-20-the-ethics-of-ai-and-data-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-20-the-ethics-of-ai-and-data-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-20-the-ethics-of-ai-and-data-connections-4" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-20-the-ethics-of-ai-and-data-related-frameworks-4" }, { "level": 2, "text": "5. Explanation, Notice, Contestability, and Recourse Decision Tree", "id": "chapter-20-the-ethics-of-ai-and-data-5-explanation-notice-contestability-and-recourse-decision-tree" }, { "level": 3, "text": "Overview", "id": "chapter-20-the-ethics-of-ai-and-data-overview-5" }, { "level": 3, "text": "When to Use", "id": "chapter-20-the-ethics-of-ai-and-data-when-to-use-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-20-the-ethics-of-ai-and-data-how-to-apply-5" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-20-the-ethics-of-ai-and-data-key-questions-to-answer-5" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-20-the-ethics-of-ai-and-data-data-inputs-required-5" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-20-the-ethics-of-ai-and-data-common-pitfalls-5" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-20-the-ethics-of-ai-and-data-digital-age-modifications-5" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-20-the-ethics-of-ai-and-data-quick-reference-card-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-20-the-ethics-of-ai-and-data-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-20-the-ethics-of-ai-and-data-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-20-the-ethics-of-ai-and-data-connections-5" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-20-the-ethics-of-ai-and-data-related-frameworks-5" }, { "level": 2, "text": "6. Red Teaming & Adversarial Testing for AI", "id": "chapter-20-the-ethics-of-ai-and-data-6-red-teaming-adversarial-testing-for-ai" }, { "level": 3, "text": "Overview", "id": "chapter-20-the-ethics-of-ai-and-data-overview-6" }, { "level": 3, "text": "When to Use", "id": "chapter-20-the-ethics-of-ai-and-data-when-to-use-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-20-the-ethics-of-ai-and-data-how-to-apply-6" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-20-the-ethics-of-ai-and-data-key-questions-to-answer-6" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-20-the-ethics-of-ai-and-data-data-inputs-required-6" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-20-the-ethics-of-ai-and-data-common-pitfalls-6" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-20-the-ethics-of-ai-and-data-digital-age-modifications-6" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-20-the-ethics-of-ai-and-data-quick-reference-card-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-20-the-ethics-of-ai-and-data-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-20-the-ethics-of-ai-and-data-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-20-the-ethics-of-ai-and-data-connections-6" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-20-the-ethics-of-ai-and-data-related-frameworks-6" }, { "level": 2, "text": "7. The AI Ethics Committee (AEC) Charter", "id": "chapter-20-the-ethics-of-ai-and-data-7-the-ai-ethics-committee-aec-charter" }, { "level": 3, "text": "Overview", "id": "chapter-20-the-ethics-of-ai-and-data-overview-7" }, { "level": 3, "text": "When to Use", "id": "chapter-20-the-ethics-of-ai-and-data-when-to-use-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-20-the-ethics-of-ai-and-data-how-to-apply-7" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-20-the-ethics-of-ai-and-data-key-questions-to-answer-7" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-20-the-ethics-of-ai-and-data-data-inputs-required-7" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-20-the-ethics-of-ai-and-data-common-pitfalls-7" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-20-the-ethics-of-ai-and-data-digital-age-modifications-7" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-20-the-ethics-of-ai-and-data-quick-reference-card-7" }, { "level": 3, "text": "So What for Managers", "id": "chapter-20-the-ethics-of-ai-and-data-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-20-the-ethics-of-ai-and-data-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-20-the-ethics-of-ai-and-data-connections-7" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-20-the-ethics-of-ai-and-data-related-frameworks-7" }, { "level": 2, "text": "8. Stakeholder Impact Assessment for AI", "id": "chapter-20-the-ethics-of-ai-and-data-8-stakeholder-impact-assessment-for-ai" }, { "level": 3, "text": "Overview", "id": "chapter-20-the-ethics-of-ai-and-data-overview-8" }, { "level": 3, "text": "When to Use", "id": "chapter-20-the-ethics-of-ai-and-data-when-to-use-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-20-the-ethics-of-ai-and-data-how-to-apply-8" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-20-the-ethics-of-ai-and-data-key-questions-to-answer-8" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-20-the-ethics-of-ai-and-data-data-inputs-required-8" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-20-the-ethics-of-ai-and-data-common-pitfalls-8" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-20-the-ethics-of-ai-and-data-digital-age-modifications-8" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-20-the-ethics-of-ai-and-data-quick-reference-card-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-20-the-ethics-of-ai-and-data-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-20-the-ethics-of-ai-and-data-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-20-the-ethics-of-ai-and-data-connections-8" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-20-the-ethics-of-ai-and-data-related-frameworks-8" }, { "level": 2, "text": "9. The Data Ethics Canvas", "id": "chapter-20-the-ethics-of-ai-and-data-9-the-data-ethics-canvas" }, { "level": 3, "text": "Overview", "id": "chapter-20-the-ethics-of-ai-and-data-overview-9" }, { "level": 3, "text": "When to Use", "id": "chapter-20-the-ethics-of-ai-and-data-when-to-use-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-20-the-ethics-of-ai-and-data-how-to-apply-9" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-20-the-ethics-of-ai-and-data-key-questions-to-answer-9" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-20-the-ethics-of-ai-and-data-data-inputs-required-9" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-20-the-ethics-of-ai-and-data-common-pitfalls-9" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-20-the-ethics-of-ai-and-data-digital-age-modifications-9" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-20-the-ethics-of-ai-and-data-quick-reference-card-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-20-the-ethics-of-ai-and-data-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-20-the-ethics-of-ai-and-data-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-20-the-ethics-of-ai-and-data-connections-9" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-20-the-ethics-of-ai-and-data-related-frameworks-9" }, { "level": 2, "text": "10. The AI Ethics Lifecycle", "id": "chapter-20-the-ethics-of-ai-and-data-10-the-ai-ethics-lifecycle" }, { "level": 3, "text": "Overview", "id": "chapter-20-the-ethics-of-ai-and-data-overview-10" }, { "level": 3, "text": "When to Use", "id": "chapter-20-the-ethics-of-ai-and-data-when-to-use-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-20-the-ethics-of-ai-and-data-how-to-apply-10" }, { "level": 3, "text": "Key Questions to Answer", "id": "chapter-20-the-ethics-of-ai-and-data-key-questions-to-answer-10" }, { "level": 3, "text": "Data/Inputs Required", "id": "chapter-20-the-ethics-of-ai-and-data-data-inputs-required-10" }, { "level": 3, "text": "Common Pitfalls", "id": "chapter-20-the-ethics-of-ai-and-data-common-pitfalls-10" }, { "level": 3, "text": "Digital Age Modifications", "id": "chapter-20-the-ethics-of-ai-and-data-digital-age-modifications-10" }, { "level": 3, "text": "Quick Reference Card", "id": "chapter-20-the-ethics-of-ai-and-data-quick-reference-card-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-20-the-ethics-of-ai-and-data-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-20-the-ethics-of-ai-and-data-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-20-the-ethics-of-ai-and-data-connections-10" }, { "level": 3, "text": "Related Frameworks", "id": "chapter-20-the-ethics-of-ai-and-data-related-frameworks-10" }, { "level": 2, "text": "Applied Decision Exercise: Deploy, Redesign, Restrict, or Stop", "id": "chapter-20-the-ethics-of-ai-and-data-applied-decision-exercise-deploy-redesign-restrict-or-stop" }, { "level": 3, "text": "Authored Connections", "id": "chapter-20-the-ethics-of-ai-and-data-authored-connections" } ], "figures": [ { "id": "chapter-20-the-ethics-of-ai-and-data-figure-1", "type": "mermaid", "caption": "Figure 20.1. Fairness evidence and remediation loop. The author-created loop connects data review, model design, fairness evaluation, deployment, outcome audit, and renewed investigation. It does not imply that one metric, mitigation, or “no bias detected” result establishes fairness. Source basis: fairness trade-off and measurement literature. [BB-C20-S04]", "textEquivalent": "Text equivalent: Data and model choices are evaluated before deployment; real-world outcomes are audited after deployment. A material disparity or harm signal routes back to problem, data, model, threshold, workflow, and institutional review. An apparently acceptable result continues monitoring, participation, appeal, and remedy rather than closing the issue.", "sourceIds": [ "BB-C20-S04" ], "provenanceStatus": "constructed", "checksum": "c0f294d2305de3f965ce44b162d83ed354c1d065325fbecd8751aee52bc2e0b7" }, { "id": "chapter-20-the-ethics-of-ai-and-data-figure-2", "type": "mermaid", "caption": "Figure 20.2. Explanation, notice, contestability, and recourse routing. The author-created tree begins with impact and automation, then routes to current legal review, audience-appropriate information, validated explanation, correction or appeal, and monitoring. [BB-C20-S03]", "textEquivalent": "Text equivalent: For a lower-impact decision, provide proportionate transparency and monitor feedback. For a consequential or solely automated decision, qualified owners first determine applicable duties and stakeholder needs; they then validate the explanation method, provide accessible correction or appeal where required or justified, and monitor whether the process works.", "sourceIds": [ "BB-C20-S03" ], "provenanceStatus": "constructed", "checksum": "6bbb7067dd4dd7eb372d8e3c19a280ca18304279c67b76090fbc2c5919ea343c" }, { "id": "chapter-20-the-ethics-of-ai-and-data-figure-3", "type": "mermaid", "caption": "Figure 20.3. AI ethics and accountability lifecycle. The author-created diagram connects problem definition, data, model, testing, deployment, monitoring, maintenance, and retirement, with monitoring able to reopen earlier decisions. It does not imply that passage through stages establishes ethical acceptability or legal compliance. Source basis: AI risk-management and end-to-end accountability practice. [BB-C20-S01] [BB-C20-S07]", "textEquivalent": "Text equivalent: A proposed use is assessed before data and model work; evidence is tested before release; deployed systems are monitored for business, fairness, privacy, safety, security, labor, environmental, agency, complaint, appeal, and remedy signals; material findings or changes route back to the relevant earlier decision; retirement includes data, access, notice, dependency, records, and ongoing-remedy obligations.", "sourceIds": [ "BB-C20-S01", "BB-C20-S07" ], "provenanceStatus": "constructed", "checksum": "a1683f39ff2a72daf8e6398490f8ed918f81abe891e5f22039b5e85b9d93f21c" } ], "tables": [ { "id": "chapter-20-the-ethics-of-ai-and-data-table-1", "caption": "Table 1. Framework / Primary Use / Time Required", "headers": [ "Framework", "Primary Use", "Time Required", "Complexity", "Strategic Impact" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 10 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-2", "caption": "Table 2. AI Application / Key FATE Principles / Notes", "headers": [ "AI Application", "Key FATE Principles", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-3", "caption": "Table 3. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-4", "caption": "Table 4. AI Application / Key Bias Focus / Notes", "headers": [ "AI Application", "Key Bias Focus", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-5", "caption": "Table 5. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-6", "caption": "Table 6. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-7", "caption": "Table 7. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-8", "caption": "Table 8. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-9", "caption": "Table 9. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-10", "caption": "Table 10. AI Application / Explanation Focus / Notes", "headers": [ "AI Application", "Explanation Focus", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-11", "caption": "Table 11. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-12", "caption": "Table 12. AI Application / Key Testing Focus / Notes", "headers": [ "AI Application", "Key Testing Focus", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-13", "caption": "Table 13. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-14", "caption": "Table 14. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-15", "caption": "Table 15. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-16", "caption": "Table 16. AI Application / Impact Focus / Notes", "headers": [ "AI Application", "Impact Focus", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-17", "caption": "Table 17. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-18", "caption": "Table 18. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-19", "caption": "Table 19. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-20", "caption": "Table 20. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-21", "caption": "Table 21. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-20-the-ethics-of-ai-and-data.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-05-marketing-and-customer-analytics", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-b-contrarian-business-perspectives", "appendix-c-public-record-decision-cases", "chapter-02-business-law-governance-and-ethics", "chapter-05-marketing-and-customer-analytics", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-21-product-management-and-product-strategy", "slug": "chapter-21-product-management-and-product-strategy", "kind": "chapter", "number": 21, "title": "Product Management and Product Strategy", "part": "Part 3: Entrepreneurship and Innovation", "summary": "Product strategy, jobs to be done, prioritization, roadmaps, product-led growth, AI products, and product operations.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "relatedSlugs": [ "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/part3-entrepreneurship/21-product-management.md", "outputPath": "index.html#chapter-21-product-management-and-product-strategy", "markdownPath": "markdown/chapter-21-product-management-and-product-strategy.md", "wordCount": 14041, "checksum": "918d5ff753a2b62e21fb6c26ecf6ef26387c248a8859ed628f3af55ceb286a07", "sourceIds": [ "BB-C21-S01", "BB-C21-S18", "BB-C21-S03", "BB-C21-S04", "BB-C21-S05", "BB-C21-S06", "BB-C21-S07", "BB-C21-S08", "BB-C21-S09", "BB-C21-S10", "BB-C21-S19", "BB-C21-S20", "BB-C21-S21", "BB-C21-S22", "BB-C21-S23", "BB-C21-S24", "BB-C21-S25", "BB-C21-S26", "BB-C21-S27", "BB-C21-S11", "BB-C21-S16", "BB-C21-S17" ], "headings": [ { "level": 2, "text": "Manager's Orientation", "id": "chapter-21-product-management-and-product-strategy-manager-s-orientation" }, { "level": 2, "text": "Executive Summary", "id": "chapter-21-product-management-and-product-strategy-executive-summary" }, { "level": 2, "text": "1. Jobs-to-be-Done (JTBD) Framework", "id": "chapter-21-product-management-and-product-strategy-1-jobs-to-be-done-jtbd-framework" }, { "level": 3, "text": "Overview", "id": "chapter-21-product-management-and-product-strategy-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-21-product-management-and-product-strategy-how-to-apply" }, { "level": 3, "text": "Evidence-Based Contrarian Thinking: Most User Feedback Is Useless", "id": "chapter-21-product-management-and-product-strategy-evidence-based-contrarian-thinking-most-user-feedback-is-useless" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-21-product-management-and-product-strategy-input-output-interlinkages" }, { "level": 3, "text": "So What for Managers", "id": "chapter-21-product-management-and-product-strategy-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-21-product-management-and-product-strategy-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-21-product-management-and-product-strategy-connections" }, { "level": 2, "text": "2. Product Strategy Canvas", "id": "chapter-21-product-management-and-product-strategy-2-product-strategy-canvas" }, { "level": 3, "text": "Overview", "id": "chapter-21-product-management-and-product-strategy-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-21-product-management-and-product-strategy-how-to-apply-2" }, { "level": 3, "text": "Common Mistake: Confusing Strategy with Tactics", "id": "chapter-21-product-management-and-product-strategy-common-mistake-confusing-strategy-with-tactics" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-21-product-management-and-product-strategy-input-output-interlinkages-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-21-product-management-and-product-strategy-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-21-product-management-and-product-strategy-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-21-product-management-and-product-strategy-connections-2" }, { "level": 2, "text": "3. Product-Market Fit Metrics Dashboard", "id": "chapter-21-product-management-and-product-strategy-3-product-market-fit-metrics-dashboard" }, { "level": 3, "text": "Overview", "id": "chapter-21-product-management-and-product-strategy-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-21-product-management-and-product-strategy-how-to-apply-3" }, { "level": 4, "text": "1. Retention Metrics (The Most Important Signal)", "id": "chapter-21-product-management-and-product-strategy-1-retention-metrics-the-most-important-signal" }, { "level": 4, "text": "2. Engagement Metrics", "id": "chapter-21-product-management-and-product-strategy-2-engagement-metrics" }, { "level": 4, "text": "3. Growth Metrics", "id": "chapter-21-product-management-and-product-strategy-3-growth-metrics" }, { "level": 4, "text": "4. Qualitative Signals (Often More Important than Metrics)", "id": "chapter-21-product-management-and-product-strategy-4-qualitative-signals-often-more-important-than-metrics" }, { "level": 4, "text": "5. Leading Economic Indicators", "id": "chapter-21-product-management-and-product-strategy-5-leading-economic-indicators" }, { "level": 3, "text": "Evidence-Based Contrarian Thinking: PMF Is a Feeling, Not a Metric", "id": "chapter-21-product-management-and-product-strategy-evidence-based-contrarian-thinking-pmf-is-a-feeling-not-a-metric" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-21-product-management-and-product-strategy-input-output-interlinkages-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-21-product-management-and-product-strategy-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-21-product-management-and-product-strategy-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-21-product-management-and-product-strategy-connections-3" }, { "level": 2, "text": "4. Feature Prioritization (RICE)", "id": "chapter-21-product-management-and-product-strategy-4-feature-prioritization-rice" }, { "level": 3, "text": "Overview", "id": "chapter-21-product-management-and-product-strategy-overview-4" }, { "level": 3, "text": "Visual Representation", "id": "chapter-21-product-management-and-product-strategy-visual-representation" }, { "level": 3, "text": "How to Apply", "id": "chapter-21-product-management-and-product-strategy-how-to-apply-4" }, { "level": 3, "text": "Common Pitfalls and How to Avoid Them", "id": "chapter-21-product-management-and-product-strategy-common-pitfalls-and-how-to-avoid-them" }, { "level": 3, "text": "Evidence-Based Contrarian Thinking: Roadmaps Are Fiction", "id": "chapter-21-product-management-and-product-strategy-evidence-based-contrarian-thinking-roadmaps-are-fiction" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-21-product-management-and-product-strategy-input-output-interlinkages-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-21-product-management-and-product-strategy-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-21-product-management-and-product-strategy-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-21-product-management-and-product-strategy-connections-4" }, { "level": 2, "text": "5. Product Roadmapping (Now/Next/Later)", "id": "chapter-21-product-management-and-product-strategy-5-product-roadmapping-now-next-later" }, { "level": 3, "text": "Overview", "id": "chapter-21-product-management-and-product-strategy-overview-5" }, { "level": 3, "text": "Visual Representation", "id": "chapter-21-product-management-and-product-strategy-visual-representation-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-21-product-management-and-product-strategy-how-to-apply-5" }, { "level": 4, "text": "1. Now (This Quarter)", "id": "chapter-21-product-management-and-product-strategy-1-now-this-quarter" }, { "level": 4, "text": "2. Next (Next 1-2 Quarters)", "id": "chapter-21-product-management-and-product-strategy-2-next-next-1-2-quarters" }, { "level": 4, "text": "3. Later (Future, No Timeline)", "id": "chapter-21-product-management-and-product-strategy-3-later-future-no-timeline" }, { "level": 3, "text": "Why This Works", "id": "chapter-21-product-management-and-product-strategy-why-this-works" }, { "level": 3, "text": "How to Communicate to Stakeholders", "id": "chapter-21-product-management-and-product-strategy-how-to-communicate-to-stakeholders" }, { "level": 3, "text": "Evidence-Based Contrarian Thinking: Roadmaps Are Marketing Documents", "id": "chapter-21-product-management-and-product-strategy-evidence-based-contrarian-thinking-roadmaps-are-marketing-documents" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-21-product-management-and-product-strategy-input-output-interlinkages-5" }, { "level": 3, "text": "So What for Managers", "id": "chapter-21-product-management-and-product-strategy-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-21-product-management-and-product-strategy-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-21-product-management-and-product-strategy-connections-5" }, { "level": 2, "text": "6. Product Metrics Hierarchy (North Star Metric)", "id": "chapter-21-product-management-and-product-strategy-6-product-metrics-hierarchy-north-star-metric" }, { "level": 3, "text": "Overview", "id": "chapter-21-product-management-and-product-strategy-overview-6" }, { "level": 3, "text": "Visual Representation", "id": "chapter-21-product-management-and-product-strategy-visual-representation-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-21-product-management-and-product-strategy-how-to-apply-6" }, { "level": 4, "text": "Level 1: North Star Metric (The One Metric That Matters)", "id": "chapter-21-product-management-and-product-strategy-level-1-north-star-metric-the-one-metric-that-matters" }, { "level": 4, "text": "Level 2: Input Metrics (The Drivers)", "id": "chapter-21-product-management-and-product-strategy-level-2-input-metrics-the-drivers" }, { "level": 4, "text": "Level 3: Health Metrics (The Monitoring Dashboard)", "id": "chapter-21-product-management-and-product-strategy-level-3-health-metrics-the-monitoring-dashboard" }, { "level": 3, "text": "Constructed Audio-Service Metrics Hierarchy", "id": "chapter-21-product-management-and-product-strategy-constructed-audio-service-metrics-hierarchy" }, { "level": 3, "text": "Evidence-Based Contrarian Thinking: Metrics Don't Drive Decisions; Insights Do", "id": "chapter-21-product-management-and-product-strategy-evidence-based-contrarian-thinking-metrics-don-t-drive-decisions-insights-do" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-21-product-management-and-product-strategy-input-output-interlinkages-6" }, { "level": 3, "text": "So What for Managers", "id": "chapter-21-product-management-and-product-strategy-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-21-product-management-and-product-strategy-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-21-product-management-and-product-strategy-connections-6" }, { "level": 2, "text": "7. Product Discovery Process", "id": "chapter-21-product-management-and-product-strategy-7-product-discovery-process" }, { "level": 3, "text": "Overview", "id": "chapter-21-product-management-and-product-strategy-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-21-product-management-and-product-strategy-how-to-apply-7" }, { "level": 4, "text": "Stage 1: Opportunity Assessment (locally planned)", "id": "chapter-21-product-management-and-product-strategy-stage-1-opportunity-assessment-locally-planned" }, { "level": 4, "text": "Stage 2: Solution Exploration (locally planned)", "id": "chapter-21-product-management-and-product-strategy-stage-2-solution-exploration-locally-planned" }, { "level": 4, "text": "Stage 3: Validation (locally planned)", "id": "chapter-21-product-management-and-product-strategy-stage-3-validation-locally-planned" }, { "level": 4, "text": "Stage 4: Go/Redesign/Stage/Stop Decision (locally planned)", "id": "chapter-21-product-management-and-product-strategy-stage-4-go-redesign-stage-stop-decision-locally-planned" }, { "level": 3, "text": "Discovery cadence", "id": "chapter-21-product-management-and-product-strategy-discovery-cadence" }, { "level": 3, "text": "Evidence-Based Contrarian Thinking: Most Features Should Never Be Built", "id": "chapter-21-product-management-and-product-strategy-evidence-based-contrarian-thinking-most-features-should-never-be-built" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-21-product-management-and-product-strategy-input-output-interlinkages-7" }, { "level": 3, "text": "Human-Centered and Service Design Module [BB-C21-S19] [BB-C21-S20] [BB-C21-S21] [BB-C21-S22] [BB-C21-S23] [BB-C21-S24] [BB-C21-S25] [BB-C21-S26] [BB-C21-S27]", "id": "chapter-21-product-management-and-product-strategy-human-centered-and-service-design-module-bb-c21-s19-bb-c21-s20-bb-c21-s21-bb-c21-s22-bb-c21-s23-bb-c21-s24-bb-c21-s25-bb-c21-s26-bb-c21-s27" }, { "level": 4, "text": "Why This Extends Product Discovery", "id": "chapter-21-product-management-and-product-strategy-why-this-extends-product-discovery" }, { "level": 4, "text": "1. Accessibility-Led Research and Inclusive Recruitment", "id": "chapter-21-product-management-and-product-strategy-1-accessibility-led-research-and-inclusive-recruitment" }, { "level": 4, "text": "2. Research Ethics, Privacy, and Participant Safety", "id": "chapter-21-product-management-and-product-strategy-2-research-ethics-privacy-and-participant-safety" }, { "level": 4, "text": "3. Synthesize Evidence Into Needs, Not Feature Votes", "id": "chapter-21-product-management-and-product-strategy-3-synthesize-evidence-into-needs-not-feature-votes" }, { "level": 4, "text": "4. Map the Whole Service With a Blueprint", "id": "chapter-21-product-management-and-product-strategy-4-map-the-whole-service-with-a-blueprint" }, { "level": 4, "text": "5. Select Concepts Without Averaging Away Harm", "id": "chapter-21-product-management-and-product-strategy-5-select-concepts-without-averaging-away-harm" }, { "level": 4, "text": "6. Match Prototype Fidelity to the Riskiest Assumption", "id": "chapter-21-product-management-and-product-strategy-6-match-prototype-fidelity-to-the-riskiest-assumption" }, { "level": 4, "text": "7. Human-Centered Decision Gates", "id": "chapter-21-product-management-and-product-strategy-7-human-centered-decision-gates" }, { "level": 4, "text": "Applied Decision Exercise: Replace a Lost Credential", "id": "chapter-21-product-management-and-product-strategy-applied-decision-exercise-replace-a-lost-credential" }, { "level": 3, "text": "So What for Managers", "id": "chapter-21-product-management-and-product-strategy-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-21-product-management-and-product-strategy-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-21-product-management-and-product-strategy-connections-7" }, { "level": 2, "text": "8. B2B Product Management", "id": "chapter-21-product-management-and-product-strategy-8-b2b-product-management" }, { "level": 3, "text": "Overview", "id": "chapter-21-product-management-and-product-strategy-overview-8" }, { "level": 3, "text": "How B2B Differs from B2C", "id": "chapter-21-product-management-and-product-strategy-how-b2b-differs-from-b2c" }, { "level": 4, "text": "1. Buyer ≠ User", "id": "chapter-21-product-management-and-product-strategy-1-buyer-user" }, { "level": 4, "text": "2. Complex Buying Process", "id": "chapter-21-product-management-and-product-strategy-2-complex-buying-process" }, { "level": 4, "text": "3. Enterprise Requirements (Table Stakes)", "id": "chapter-21-product-management-and-product-strategy-3-enterprise-requirements-table-stakes" }, { "level": 4, "text": "4. Pricing & Packaging Strategy", "id": "chapter-21-product-management-and-product-strategy-4-pricing-packaging-strategy" }, { "level": 4, "text": "5. Product-Led Growth (PLG) vs. Sales-Led Growth", "id": "chapter-21-product-management-and-product-strategy-5-product-led-growth-plg-vs-sales-led-growth" }, { "level": 3, "text": "B2B Product Prioritization Framework", "id": "chapter-21-product-management-and-product-strategy-b2b-product-prioritization-framework" }, { "level": 3, "text": "How to Apply", "id": "chapter-21-product-management-and-product-strategy-how-to-apply-8" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-21-product-management-and-product-strategy-input-output-interlinkages-8" }, { "level": 3, "text": "So What for Managers", "id": "chapter-21-product-management-and-product-strategy-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-21-product-management-and-product-strategy-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-21-product-management-and-product-strategy-connections-8" }, { "level": 2, "text": "9. Product-Led Growth (PLG) Framework", "id": "chapter-21-product-management-and-product-strategy-9-product-led-growth-plg-framework" }, { "level": 3, "text": "Overview", "id": "chapter-21-product-management-and-product-strategy-overview-9" }, { "level": 3, "text": "How PLG Works: The Flywheel", "id": "chapter-21-product-management-and-product-strategy-how-plg-works-the-flywheel" }, { "level": 3, "text": "How to Build a PLG Product", "id": "chapter-21-product-management-and-product-strategy-how-to-build-a-plg-product" }, { "level": 4, "text": "Step 1: Design for Time-to-Value (TTV)", "id": "chapter-21-product-management-and-product-strategy-step-1-design-for-time-to-value-ttv" }, { "level": 4, "text": "Step 2: Build Viral Loops", "id": "chapter-21-product-management-and-product-strategy-step-2-build-viral-loops" }, { "level": 4, "text": "Step 3: Free-to-Paid Conversion Strategy", "id": "chapter-21-product-management-and-product-strategy-step-3-free-to-paid-conversion-strategy" }, { "level": 4, "text": "Step 4: Design for Expansion Revenue", "id": "chapter-21-product-management-and-product-strategy-step-4-design-for-expansion-revenue" }, { "level": 3, "text": "PLG Success Metrics", "id": "chapter-21-product-management-and-product-strategy-plg-success-metrics" }, { "level": 3, "text": "When PLG Works vs. Doesn't Work", "id": "chapter-21-product-management-and-product-strategy-when-plg-works-vs-doesn-t-work" }, { "level": 3, "text": "How to Apply", "id": "chapter-21-product-management-and-product-strategy-how-to-apply-9" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-21-product-management-and-product-strategy-input-output-interlinkages-9" }, { "level": 3, "text": "So What for Managers", "id": "chapter-21-product-management-and-product-strategy-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-21-product-management-and-product-strategy-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-21-product-management-and-product-strategy-connections-9" }, { "level": 2, "text": "10. AI Product Management", "id": "chapter-21-product-management-and-product-strategy-10-ai-product-management" }, { "level": 3, "text": "Overview", "id": "chapter-21-product-management-and-product-strategy-overview-10" }, { "level": 3, "text": "Key Differences: AI Products vs. Traditional Software", "id": "chapter-21-product-management-and-product-strategy-key-differences-ai-products-vs-traditional-software" }, { "level": 4, "text": "1. Deterministic and Probabilistic Components", "id": "chapter-21-product-management-and-product-strategy-1-deterministic-and-probabilistic-components" }, { "level": 4, "text": "2. Data, Model, Workflow, and Governance Shape the Product", "id": "chapter-21-product-management-and-product-strategy-2-data-model-workflow-and-governance-shape-the-product" }, { "level": 4, "text": "3. Production Performance Can Change", "id": "chapter-21-product-management-and-product-strategy-3-production-performance-can-change" }, { "level": 3, "text": "How to Build AI Products", "id": "chapter-21-product-management-and-product-strategy-how-to-build-ai-products" }, { "level": 4, "text": "Stage 1: Define the Job (Same as Non-AI Products)", "id": "chapter-21-product-management-and-product-strategy-stage-1-define-the-job-same-as-non-ai-products" }, { "level": 4, "text": "Stage 2: Establish Baseline Performance", "id": "chapter-21-product-management-and-product-strategy-stage-2-establish-baseline-performance" }, { "level": 4, "text": "Stage 3: Build, Measure, Learn (Tighter Loop than Traditional Products)", "id": "chapter-21-product-management-and-product-strategy-stage-3-build-measure-learn-tighter-loop-than-traditional-products" }, { "level": 4, "text": "Stage 4: Automation and Meaningful Human Control", "id": "chapter-21-product-management-and-product-strategy-stage-4-automation-and-meaningful-human-control" }, { "level": 4, "text": "Stage 5: Transparency & Explainability", "id": "chapter-21-product-management-and-product-strategy-stage-5-transparency-explainability" }, { "level": 3, "text": "AI Product Metrics", "id": "chapter-21-product-management-and-product-strategy-ai-product-metrics" }, { "level": 3, "text": "Common AI Product Pitfalls", "id": "chapter-21-product-management-and-product-strategy-common-ai-product-pitfalls" }, { "level": 3, "text": "When to Use AI vs. Traditional Software", "id": "chapter-21-product-management-and-product-strategy-when-to-use-ai-vs-traditional-software" }, { "level": 3, "text": "How to Apply", "id": "chapter-21-product-management-and-product-strategy-how-to-apply-10" }, { "level": 3, "text": "Input/Output Interlinkages", "id": "chapter-21-product-management-and-product-strategy-input-output-interlinkages-10" }, { "level": 3, "text": "So What for Managers", "id": "chapter-21-product-management-and-product-strategy-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-21-product-management-and-product-strategy-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-21-product-management-and-product-strategy-connections-10" }, { "level": 2, "text": "Product Economics, Responsible Product, and Lifecycle Decisions", "id": "chapter-21-product-management-and-product-strategy-product-economics-responsible-product-and-lifecycle-decisions" }, { "level": 2, "text": "Troubleshooting Guide: Product Management", "id": "chapter-21-product-management-and-product-strategy-troubleshooting-guide-product-management" }, { "level": 3, "text": "Symptom: \"We're building features no one uses. Feature adoption is weak.\"", "id": "chapter-21-product-management-and-product-strategy-symptom-we-re-building-features-no-one-uses-feature-adoption-is-weak" }, { "level": 3, "text": "Symptom: \"We're stuck in feature factory mode. Shipping features but not moving business metrics.\"", "id": "chapter-21-product-management-and-product-strategy-symptom-we-re-stuck-in-feature-factory-mode-shipping-features-but-not-moving-business-metrics" }, { "level": 3, "text": "Symptom: \"We don't know if we have product-market fit. Growth is slow.\"", "id": "chapter-21-product-management-and-product-strategy-symptom-we-don-t-know-if-we-have-product-market-fit-growth-is-slow" }, { "level": 3, "text": "Symptom: \"Sales keeps promising features we haven't built, then blames product for lost deals.\"", "id": "chapter-21-product-management-and-product-strategy-symptom-sales-keeps-promising-features-we-haven-t-built-then-blames-product-for-lost-deals" }, { "level": 3, "text": "Symptom: \"Our roadmap is a list of features with dates, and we're always late.\"", "id": "chapter-21-product-management-and-product-strategy-symptom-our-roadmap-is-a-list-of-features-with-dates-and-we-re-always-late" }, { "level": 3, "text": "Symptom: \"Engineering says every feature takes 6 months. We can't move fast.\"", "id": "chapter-21-product-management-and-product-strategy-symptom-engineering-says-every-feature-takes-6-months-we-can-t-move-fast" }, { "level": 3, "text": "Symptom: \"We have 50 metrics dashboards and no one knows what to focus on.\"", "id": "chapter-21-product-management-and-product-strategy-symptom-we-have-50-metrics-dashboards-and-no-one-knows-what-to-focus-on" }, { "level": 3, "text": "Symptom: \"Customers say they love the product (high NPS) but they churn after 6 months.\"", "id": "chapter-21-product-management-and-product-strategy-symptom-customers-say-they-love-the-product-high-nps-but-they-churn-after-6-months" }, { "level": 3, "text": "Symptom: \"The prototype is easy to use, but customers still fail to get the service outcome.\"", "id": "chapter-21-product-management-and-product-strategy-symptom-the-prototype-is-easy-to-use-but-customers-still-fail-to-get-the-service-outcome" }, { "level": 2, "text": "Operating Cadence and Case Discipline", "id": "chapter-21-product-management-and-product-strategy-operating-cadence-and-case-discipline" }, { "level": 2, "text": "Contrarian Thinking: Product Management Heresies", "id": "chapter-21-product-management-and-product-strategy-contrarian-thinking-product-management-heresies" }, { "level": 3, "text": "1. \"Most User Feedback Is Useless—Watch Behavior, Not Words\"", "id": "chapter-21-product-management-and-product-strategy-1-most-user-feedback-is-useless-watch-behavior-not-words" }, { "level": 3, "text": "2. \"Dated Roadmaps Are Commitments or Hypotheses—Make the Difference Explicit\"", "id": "chapter-21-product-management-and-product-strategy-2-dated-roadmaps-are-commitments-or-hypotheses-make-the-difference-explicit" }, { "level": 3, "text": "3. \"Data Can Support Exploitation or Exploration—Match Evidence to the Question\"", "id": "chapter-21-product-management-and-product-strategy-3-data-can-support-exploitation-or-exploration-match-evidence-to-the-question" }, { "level": 3, "text": "4. \"B2B Feature Requests Are Evidence, Not Automatic Roadmap Decisions\"", "id": "chapter-21-product-management-and-product-strategy-4-b2b-feature-requests-are-evidence-not-automatic-roadmap-decisions" }, { "level": 2, "text": "Cross-Chapter Integration", "id": "chapter-21-product-management-and-product-strategy-cross-chapter-integration" }, { "level": 3, "text": "Uses Chapter 3 (Strategy & Competitive Analysis)", "id": "chapter-21-product-management-and-product-strategy-uses-chapter-3-strategy-competitive-analysis" }, { "level": 3, "text": "Uses Chapter 4 (Financial Analysis)", "id": "chapter-21-product-management-and-product-strategy-uses-chapter-4-financial-analysis" }, { "level": 3, "text": "Uses Chapter 5 (Marketing & Segmentation)", "id": "chapter-21-product-management-and-product-strategy-uses-chapter-5-marketing-segmentation" }, { "level": 3, "text": "Uses Chapter 8 (Strategy Execution: OKRs)", "id": "chapter-21-product-management-and-product-strategy-uses-chapter-8-strategy-execution-okrs" }, { "level": 3, "text": "Uses Chapter 9 (Problem Structuring)", "id": "chapter-21-product-management-and-product-strategy-uses-chapter-9-problem-structuring" }, { "level": 3, "text": "Uses Chapter 13 (Lean Startup)", "id": "chapter-21-product-management-and-product-strategy-uses-chapter-13-lean-startup" }, { "level": 3, "text": "Uses Chapter 14 (Go-to-Market Strategy)", "id": "chapter-21-product-management-and-product-strategy-uses-chapter-14-go-to-market-strategy" }, { "level": 3, "text": "Uses Chapter 16 (AI Strategy)", "id": "chapter-21-product-management-and-product-strategy-uses-chapter-16-ai-strategy" }, { "level": 2, "text": "Applied Product Decision Exercise", "id": "chapter-21-product-management-and-product-strategy-applied-product-decision-exercise" }, { "level": 2, "text": "Authored Connections", "id": "chapter-21-product-management-and-product-strategy-authored-connections" }, { "level": 2, "text": "Chapter Summary", "id": "chapter-21-product-management-and-product-strategy-chapter-summary" } ], "figures": [ { "id": "chapter-21-product-management-and-product-strategy-figure-1", "type": "mermaid", "caption": "Figure 21.1. Product-metric hypothesis tree with value and guardrail measures. This author-created visual is a constructed teaching aid; it does not establish that any input causes the North Star outcome or that one metric hierarchy fits every product. [BB-C21-S07]", "textEquivalent": "Text equivalent: Begin with a candidate recurring customer-value outcome. Map a small set of behavioral or operational inputs that might influence it and add quality, safety, accessibility, trust, financial, and system guardrails. Test definitions, causal assumptions, segment behavior, gaming risk, and unintended effects before using the tree for decisions.", "sourceIds": [ "BB-C21-S07" ], "provenanceStatus": "constructed", "checksum": "e26066481e49d9b993f50afde91f13335d2297e8cbf85f975eeb1cc48606ccaf" }, { "id": "chapter-21-product-management-and-product-strategy-figure-2", "type": "mermaid", "caption": "Figure 21.2. Product discovery and evidence-gate loop. The author-created diagram moves from an opportunity through alternative solutions and validation to a go, pivot, or stop decision. A “go” means the evidence is sufficient for the next bounded commitment, not that the product will succeed. Source basis: continuous-discovery practice. [BB-C21-S09]", "textEquivalent": "Text equivalent: A team defines an opportunity, explores multiple solutions, tests value, usability, feasibility, viability, accessibility, ethics, safety, security, strategy, and capacity, then either moves a bounded option to delivery, returns to exploration with a revised hypothesis, or archives the learning. Post-release evidence can reopen discovery.", "sourceIds": [ "BB-C21-S09" ], "provenanceStatus": "constructed", "checksum": "bfde7a6724f5b2b92802a91c891aedcc9d37c8f1bf18b0e3ef7539f602765f8a" }, { "id": "chapter-21-product-management-and-product-strategy-figure-3", "type": "mermaid", "caption": "Figure 21.3. Accessible service blueprint for a constructed lost-credential replacement service. This author-created process visual shows evidence, user actions, visible frontstage interactions, hidden backstage work, and support capabilities across four stages. It is an illustrative teaching model, not a depiction of an actual organization or a reproduction of the cited article's figures. [BB-C21-S25]", "textEquivalent": "Text equivalent: The user finds accessible guidance, submits a replacement request, responds to any clarification, and receives an outcome with recovery options. Visible channels provide guidance, validation, status, and help. Behind the line of visibility, the service creates a case, checks records, makes and logs a decision, and handles exceptions. Content, identity, case-management, notification, accessibility, staff, and governance capabilities support every stage.", "sourceIds": [ "BB-C21-S25" ], "provenanceStatus": "constructed", "checksum": "968c1365db47adedc858a9f9d97de935522644575e9c90825bea3151e3194f29" } ], "tables": [ { "id": "chapter-21-product-management-and-product-strategy-table-1", "caption": "Table 1. Candidate / Reach per quarter / Impact", "headers": [ "Candidate", "Reach per quarter", "Impact", "Confidence", "Effort (person-months)", "RICE score" ], "sourceIds": [ "BB-C21-S05" ], "provenanceStatus": "constructed", "rowCount": 2 }, { "id": "chapter-21-product-management-and-product-strategy-table-2", "caption": "Table 2. Horizon / Decision meaning / Minimum evidence and communication", "headers": [ "Horizon", "Decision meaning", "Minimum evidence and communication" ], "sourceIds": [ "BB-C21-S06" ], "provenanceStatus": "constructed", "rowCount": 3 }, { "id": "chapter-21-product-management-and-product-strategy-table-3", "caption": "Table 3. Recruitment Dimension / Manager Question / Evidence to Record", "headers": [ "Recruitment Dimension", "Manager Question", "Evidence to Record" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-21-product-management-and-product-strategy-table-4", "caption": "Table 4. Level / Definition / Constructed Example", "headers": [ "Level", "Definition", "Constructed Example", "Traceability Test" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "chapter-21-product-management-and-product-strategy-table-5", "caption": "Table 5. Blueprint Lane / Discover and Start / Submit", "headers": [ "Blueprint Lane", "Discover and Start", "Submit", "Review and Clarify", "Outcome and Recover" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-21-product-management-and-product-strategy-table-6", "caption": "Table 6. Criterion / Evidence / Concept A", "headers": [ "Criterion", "Evidence", "Concept A", "Concept B", "Uncertainty or Disqualifier" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6 }, { "id": "chapter-21-product-management-and-product-strategy-table-7", "caption": "Table 7. Question / Lowest Useful Prototype / Evidence Produced", "headers": [ "Question", "Lowest Useful Prototype", "Evidence Produced" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "chapter-21-product-management-and-product-strategy-table-8", "caption": "Table 8. Gate / Minimum Evidence / Decision and Owner", "headers": [ "Gate", "Minimum Evidence", "Decision and Owner" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-21-product-management-and-product-strategy.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-c-public-record-decision-cases", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-05-marketing-and-customer-analytics", "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-20-the-ethics-of-ai-and-data", "chapter-22-data-analysis-and-insights" ] }, { "id": "chapter-22-data-analysis-and-insights", "slug": "chapter-22-data-analysis-and-insights", "kind": "chapter", "number": 22, "title": "Data Analysis and Insights", "part": "Part 2: Management Consulting Toolkit", "summary": "Structuring analysis, causal and statistical interpretation, visualization, KPI trees, sensitivity, simulation, and managerial decision analysis for managers.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "relatedSlugs": [ "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-13-startup-foundations", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy" ], "sourcePath": "src/part2-consulting/22-data-analysis-insights.md", "outputPath": "index.html#chapter-22-data-analysis-and-insights", "markdownPath": "markdown/chapter-22-data-analysis-and-insights.md", "wordCount": 11720, "checksum": "a4ff4e284e6f20e2389ca627294b1903b52c484f500f2f9e1728ccb0f6bd12d7", "sourceIds": [ "BB-C22-S01", "BB-C22-S02", "BB-C22-S03", "BB-C22-S04", "BB-C22-S05", "BB-C22-S06", "BB-C22-S07", "BB-C22-S08", "BB-C22-S09", "BB-C22-S10", "BB-C22-S11", "BB-C22-S12", "BB-C22-S14", "BB-C22-S13", "BB-C22-S15", "BB-C22-S16", "BB-C22-S19", "BB-C22-S17", "BB-C22-S20", "BB-C22-S18", "BB-C22-S21", "BB-C22-S22", "BB-C22-S23" ], "headings": [ { "level": 2, "text": "Executive Summary", "id": "chapter-22-data-analysis-and-insights-executive-summary" }, { "level": 2, "text": "Manager's Orientation", "id": "chapter-22-data-analysis-and-insights-manager-s-orientation" }, { "level": 3, "text": "What the reader should be able to do", "id": "chapter-22-data-analysis-and-insights-what-the-reader-should-be-able-to-do" }, { "level": 3, "text": "Data and Reproducibility Gate", "id": "chapter-22-data-analysis-and-insights-data-and-reproducibility-gate" }, { "level": 2, "text": "The Operating Principle: Decision-Grade Analysis", "id": "chapter-22-data-analysis-and-insights-the-operating-principle-decision-grade-analysis" }, { "level": 2, "text": "1. Pyramid Principle Structure", "id": "chapter-22-data-analysis-and-insights-1-pyramid-principle-structure" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply" }, { "level": 3, "text": "When To Use It", "id": "chapter-22-data-analysis-and-insights-when-to-use-it" }, { "level": 3, "text": "The Structure", "id": "chapter-22-data-analysis-and-insights-the-structure" }, { "level": 3, "text": "Practical Template", "id": "chapter-22-data-analysis-and-insights-practical-template" }, { "level": 3, "text": "Manager Checklist", "id": "chapter-22-data-analysis-and-insights-manager-checklist" }, { "level": 3, "text": "Common Failure Modes", "id": "chapter-22-data-analysis-and-insights-common-failure-modes" }, { "level": 3, "text": "Worked Mini-Example", "id": "chapter-22-data-analysis-and-insights-worked-mini-example" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections" }, { "level": 2, "text": "2. SCQ Setup and Answer Structure", "id": "chapter-22-data-analysis-and-insights-2-scq-setup-and-answer-structure" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-2" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-2" }, { "level": 3, "text": "The Four Parts", "id": "chapter-22-data-analysis-and-insights-the-four-parts" }, { "level": 3, "text": "How To Use SCQA Before Analysis", "id": "chapter-22-data-analysis-and-insights-how-to-use-scqa-before-analysis" }, { "level": 3, "text": "SCQA Diagnostic Questions", "id": "chapter-22-data-analysis-and-insights-scqa-diagnostic-questions" }, { "level": 3, "text": "Strong SCQA vs. Weak SCQA", "id": "chapter-22-data-analysis-and-insights-strong-scqa-vs-weak-scqa" }, { "level": 3, "text": "Common Failure Modes", "id": "chapter-22-data-analysis-and-insights-common-failure-modes-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-2" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-2" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-2" }, { "level": 2, "text": "3. Correlation vs. Causation Decision Tree", "id": "chapter-22-data-analysis-and-insights-3-correlation-vs-causation-decision-tree" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-3" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-3" }, { "level": 3, "text": "Required Mermaid Diagram: Decision Tree", "id": "chapter-22-data-analysis-and-insights-required-mermaid-diagram-decision-tree" }, { "level": 3, "text": "How To Use The Tree", "id": "chapter-22-data-analysis-and-insights-how-to-use-the-tree" }, { "level": 3, "text": "Methods and Ownership Boundary", "id": "chapter-22-data-analysis-and-insights-methods-and-ownership-boundary" }, { "level": 3, "text": "Decision Categories", "id": "chapter-22-data-analysis-and-insights-decision-categories" }, { "level": 3, "text": "Practical Tests For Causality", "id": "chapter-22-data-analysis-and-insights-practical-tests-for-causality" }, { "level": 3, "text": "Example", "id": "chapter-22-data-analysis-and-insights-example" }, { "level": 3, "text": "Managerial Rule", "id": "chapter-22-data-analysis-and-insights-managerial-rule" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-3" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-3" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-3" }, { "level": 2, "text": "4. Statistical Significance Interpretation For Managers", "id": "chapter-22-data-analysis-and-insights-4-statistical-significance-interpretation-for-managers" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-4" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-4" }, { "level": 3, "text": "The Three Questions To Ask", "id": "chapter-22-data-analysis-and-insights-the-three-questions-to-ask" }, { "level": 3, "text": "What A p-Value Means", "id": "chapter-22-data-analysis-and-insights-what-a-p-value-means" }, { "level": 3, "text": "What A Confidence Interval Means", "id": "chapter-22-data-analysis-and-insights-what-a-confidence-interval-means" }, { "level": 3, "text": "Statistical vs. Practical Significance", "id": "chapter-22-data-analysis-and-insights-statistical-vs-practical-significance" }, { "level": 3, "text": "Common Misuses", "id": "chapter-22-data-analysis-and-insights-common-misuses" }, { "level": 3, "text": "Worked Example", "id": "chapter-22-data-analysis-and-insights-worked-example" }, { "level": 3, "text": "Manager Checklist", "id": "chapter-22-data-analysis-and-insights-manager-checklist-2" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-4" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-4" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-4" }, { "level": 2, "text": "5. Regression Analysis Interpretation Guide", "id": "chapter-22-data-analysis-and-insights-5-regression-analysis-interpretation-guide" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-5" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-5" }, { "level": 3, "text": "The Regression Output Translation Table", "id": "chapter-22-data-analysis-and-insights-the-regression-output-translation-table" }, { "level": 3, "text": "How To Read A Coefficient", "id": "chapter-22-data-analysis-and-insights-how-to-read-a-coefficient" }, { "level": 3, "text": "The Five Manager Questions", "id": "chapter-22-data-analysis-and-insights-the-five-manager-questions" }, { "level": 3, "text": "Common Regression Traps", "id": "chapter-22-data-analysis-and-insights-common-regression-traps" }, { "level": 3, "text": "Regression Decision Memo Template", "id": "chapter-22-data-analysis-and-insights-regression-decision-memo-template" }, { "level": 3, "text": "Minimum Model Documentation", "id": "chapter-22-data-analysis-and-insights-minimum-model-documentation" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-5" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-5" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-5" }, { "level": 2, "text": "6. Data Visualization Best Practices", "id": "chapter-22-data-analysis-and-insights-6-data-visualization-best-practices" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-6" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-6" }, { "level": 3, "text": "Chart Selection Guide", "id": "chapter-22-data-analysis-and-insights-chart-selection-guide" }, { "level": 3, "text": "Visualization Rules For Managers", "id": "chapter-22-data-analysis-and-insights-visualization-rules-for-managers" }, { "level": 3, "text": "Executive Chart Template", "id": "chapter-22-data-analysis-and-insights-executive-chart-template" }, { "level": 3, "text": "Common Visualization Failure Modes", "id": "chapter-22-data-analysis-and-insights-common-visualization-failure-modes" }, { "level": 3, "text": "The \"One Chart, One Job\" Rule", "id": "chapter-22-data-analysis-and-insights-the-one-chart-one-job-rule" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-6" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-6" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-6" }, { "level": 2, "text": "7. KPI Tree Structure", "id": "chapter-22-data-analysis-and-insights-7-kpi-tree-structure" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-7" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-7" }, { "level": 3, "text": "Required Mermaid Diagram: KPI Tree", "id": "chapter-22-data-analysis-and-insights-required-mermaid-diagram-kpi-tree" }, { "level": 3, "text": "How To Build A KPI Tree", "id": "chapter-22-data-analysis-and-insights-how-to-build-a-kpi-tree" }, { "level": 3, "text": "KPI Tree Template", "id": "chapter-22-data-analysis-and-insights-kpi-tree-template" }, { "level": 3, "text": "KPI Quality Tests", "id": "chapter-22-data-analysis-and-insights-kpi-quality-tests" }, { "level": 3, "text": "Common KPI Tree Failure Modes", "id": "chapter-22-data-analysis-and-insights-common-kpi-tree-failure-modes" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-7" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-7" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-7" }, { "level": 2, "text": "8. Benchmarking Framework", "id": "chapter-22-data-analysis-and-insights-8-benchmarking-framework" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-8" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-8" }, { "level": 3, "text": "Types Of Benchmarking", "id": "chapter-22-data-analysis-and-insights-types-of-benchmarking" }, { "level": 3, "text": "The Benchmarking Process", "id": "chapter-22-data-analysis-and-insights-the-benchmarking-process" }, { "level": 3, "text": "Benchmarking Questions Managers Should Ask", "id": "chapter-22-data-analysis-and-insights-benchmarking-questions-managers-should-ask" }, { "level": 3, "text": "Common Benchmarking Traps", "id": "chapter-22-data-analysis-and-insights-common-benchmarking-traps" }, { "level": 3, "text": "Practical Output", "id": "chapter-22-data-analysis-and-insights-practical-output" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-8" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-8" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-8" }, { "level": 2, "text": "9. Sensitivity Analysis Grid", "id": "chapter-22-data-analysis-and-insights-9-sensitivity-analysis-grid" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-9" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-9" }, { "level": 3, "text": "Sensitivity Analysis Grid", "id": "chapter-22-data-analysis-and-insights-sensitivity-analysis-grid" }, { "level": 3, "text": "How To Build It", "id": "chapter-22-data-analysis-and-insights-how-to-build-it" }, { "level": 3, "text": "The Three Sensitivity Questions", "id": "chapter-22-data-analysis-and-insights-the-three-sensitivity-questions" }, { "level": 3, "text": "Tornado Logic Without The Chart", "id": "chapter-22-data-analysis-and-insights-tornado-logic-without-the-chart" }, { "level": 3, "text": "Common Failure Modes", "id": "chapter-22-data-analysis-and-insights-common-failure-modes-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-9" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-9" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-9" }, { "level": 2, "text": "10. Monte Carlo Simulation Setup", "id": "chapter-22-data-analysis-and-insights-10-monte-carlo-simulation-setup" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-10" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-10" }, { "level": 3, "text": "Mermaid Diagram: Monte Carlo Setup Flow", "id": "chapter-22-data-analysis-and-insights-mermaid-diagram-monte-carlo-setup-flow" }, { "level": 3, "text": "When To Use Monte Carlo", "id": "chapter-22-data-analysis-and-insights-when-to-use-monte-carlo" }, { "level": 3, "text": "Setup Steps", "id": "chapter-22-data-analysis-and-insights-setup-steps" }, { "level": 3, "text": "Distribution Selection For Managers", "id": "chapter-22-data-analysis-and-insights-distribution-selection-for-managers" }, { "level": 3, "text": "Monte Carlo Output Questions", "id": "chapter-22-data-analysis-and-insights-monte-carlo-output-questions" }, { "level": 3, "text": "Common Failure Modes", "id": "chapter-22-data-analysis-and-insights-common-failure-modes-4" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-10" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-10" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-10" }, { "level": 2, "text": "11. Managerial Decision Analysis Under Uncertainty", "id": "chapter-22-data-analysis-and-insights-11-managerial-decision-analysis-under-uncertainty" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-11" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-11" }, { "level": 3, "text": "Purpose and Boundary", "id": "chapter-22-data-analysis-and-insights-purpose-and-boundary" }, { "level": 3, "text": "Core Calculations", "id": "chapter-22-data-analysis-and-insights-core-calculations" }, { "level": 3, "text": "Worked Example: Test Before a Bounded AI-Support Launch", "id": "chapter-22-data-analysis-and-insights-worked-example-test-before-a-bounded-ai-support-launch" }, { "level": 3, "text": "Calculation Table", "id": "chapter-22-data-analysis-and-insights-calculation-table" }, { "level": 3, "text": "Manager Checklist", "id": "chapter-22-data-analysis-and-insights-manager-checklist-3" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-11" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-11" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-11" }, { "level": 2, "text": "12. Experimentation and Incremental Decision Evidence", "id": "chapter-22-data-analysis-and-insights-12-experimentation-and-incremental-decision-evidence" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-12" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-12" }, { "level": 3, "text": "Start With The Estimand, Not The Test", "id": "chapter-22-data-analysis-and-insights-start-with-the-estimand-not-the-test" }, { "level": 3, "text": "MDE, Power, and Sample Size", "id": "chapter-22-data-analysis-and-insights-mde-power-and-sample-size" }, { "level": 3, "text": "The Precommitted Experiment Contract", "id": "chapter-22-data-analysis-and-insights-the-precommitted-experiment-contract" }, { "level": 3, "text": "Decision Rules That Resist Result Shopping", "id": "chapter-22-data-analysis-and-insights-decision-rules-that-resist-result-shopping" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-12" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-12" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-12" }, { "level": 2, "text": "13. Optimization and Prescriptive Analytics", "id": "chapter-22-data-analysis-and-insights-13-optimization-and-prescriptive-analytics" }, { "level": 3, "text": "Overview", "id": "chapter-22-data-analysis-and-insights-overview-13" }, { "level": 3, "text": "How to Apply", "id": "chapter-22-data-analysis-and-insights-how-to-apply-13" }, { "level": 3, "text": "From Prediction To A Feasible Choice", "id": "chapter-22-data-analysis-and-insights-from-prediction-to-a-feasible-choice" }, { "level": 3, "text": "Continuous LP, Integer Models, and Scenarios", "id": "chapter-22-data-analysis-and-insights-continuous-lp-integer-models-and-scenarios" }, { "level": 3, "text": "Shadow-Price Intuition and Limits", "id": "chapter-22-data-analysis-and-insights-shadow-price-intuition-and-limits" }, { "level": 3, "text": "Optimality Is Conditional", "id": "chapter-22-data-analysis-and-insights-optimality-is-conditional" }, { "level": 3, "text": "Reproducible Two-Part Exercise", "id": "chapter-22-data-analysis-and-insights-reproducible-two-part-exercise" }, { "level": 3, "text": "So What for Managers", "id": "chapter-22-data-analysis-and-insights-so-what-for-managers-13" }, { "level": 3, "text": "Limits and Critiques", "id": "chapter-22-data-analysis-and-insights-limits-and-critiques-13" }, { "level": 3, "text": "Connections", "id": "chapter-22-data-analysis-and-insights-connections-13" }, { "level": 2, "text": "Integrating The Thirteen Frameworks", "id": "chapter-22-data-analysis-and-insights-integrating-the-thirteen-frameworks" }, { "level": 2, "text": "Decision Review Checklist", "id": "chapter-22-data-analysis-and-insights-decision-review-checklist" }, { "level": 2, "text": "How To Get Started", "id": "chapter-22-data-analysis-and-insights-how-to-get-started" }, { "level": 3, "text": "Urgent Decision Path: Decision-Grade Analysis Sprint", "id": "chapter-22-data-analysis-and-insights-urgent-decision-path-decision-grade-analysis-sprint" }, { "level": 4, "text": "Frame The Decision", "id": "chapter-22-data-analysis-and-insights-frame-the-decision" }, { "level": 4, "text": "Build The KPI Logic", "id": "chapter-22-data-analysis-and-insights-build-the-kpi-logic" }, { "level": 4, "text": "Test Evidence Quality", "id": "chapter-22-data-analysis-and-insights-test-evidence-quality" }, { "level": 4, "text": "Stress The Decision", "id": "chapter-22-data-analysis-and-insights-stress-the-decision" }, { "level": 4, "text": "Write The Recommendation", "id": "chapter-22-data-analysis-and-insights-write-the-recommendation" }, { "level": 3, "text": "Analytics Operating System Path", "id": "chapter-22-data-analysis-and-insights-analytics-operating-system-path" }, { "level": 4, "text": "Decision Inventory", "id": "chapter-22-data-analysis-and-insights-decision-inventory" }, { "level": 4, "text": "Metric Architecture", "id": "chapter-22-data-analysis-and-insights-metric-architecture" }, { "level": 4, "text": "Evidence Standards", "id": "chapter-22-data-analysis-and-insights-evidence-standards" }, { "level": 4, "text": "Visualization And Communication Standards", "id": "chapter-22-data-analysis-and-insights-visualization-and-communication-standards" }, { "level": 4, "text": "Uncertainty And Scenario Discipline", "id": "chapter-22-data-analysis-and-insights-uncertainty-and-scenario-discipline" }, { "level": 4, "text": "Governance And Review Cadence", "id": "chapter-22-data-analysis-and-insights-governance-and-review-cadence" }, { "level": 2, "text": "Troubleshooting Guide: Data Analysis And Insights", "id": "chapter-22-data-analysis-and-insights-troubleshooting-guide-data-analysis-and-insights" }, { "level": 2, "text": "Decision-Oriented Close", "id": "chapter-22-data-analysis-and-insights-decision-oriented-close" }, { "level": 2, "text": "Authored Connections", "id": "chapter-22-data-analysis-and-insights-authored-connections" }, { "level": 2, "text": "Chapter Summary", "id": "chapter-22-data-analysis-and-insights-chapter-summary" } ], "figures": [ { "id": "chapter-22-data-analysis-and-insights-figure-1", "type": "mermaid", "caption": "Figure 22.1. Routing from association to prediction or causal decision. The author-created tree distinguishes predictive use from intervention claims and routes causal questions through confounding, timing, design, testing, and explicit uncertainty. A path through the tree does not itself identify an effect. Source basis: causal-model and intervention reasoning. [BB-C22-S02]", "textEquivalent": "Text equivalent: Start with an observed relationship. If the decision is prediction only, validate the predictive model. If the decision intervenes on X to change Y, examine confounding, timing, selection, overlap, spillovers, measurement, and design. Prefer a feasible ethical randomized experiment; otherwise justify a quasi-experimental or observational design. End with act, test, hold, or redesign and a named methods owner.", "sourceIds": [ "BB-C22-S02" ], "provenanceStatus": "constructed", "checksum": "6b72c6d163671ef920772d4d0051f63a8d834a5e962f6d3b53600134001af297" }, { "id": "chapter-22-data-analysis-and-insights-figure-2", "type": "mermaid", "caption": "Figure 22.2. Constructed KPI hypothesis tree for profitable growth. The diagram links a strategic outcome to financial and operating measures. Each arrow is a proposed relationship to define, measure, and test; ownership does not make it causal. Source basis: balanced-measurement logic, adapted as author synthesis. [BB-C22-S07]", "textEquivalent": "Text equivalent: Profitable growth is decomposed into revenue growth, margin expansion, and capital efficiency. Those branches are further decomposed into acquisition, expansion, retention, margin, cost, discount, working-capital, and productivity measures. Each metric needs a definition, owner, guardrail, and evidence showing whether changing it can improve the higher-level outcome without unacceptable harm elsewhere.", "sourceIds": [ "BB-C22-S07" ], "provenanceStatus": "constructed", "checksum": "b0c0dea42981834146b0d76d451816a41b7d94df57a64b1beff97928c54785bd" }, { "id": "chapter-22-data-analysis-and-insights-figure-3", "type": "mermaid", "caption": "Figure 22.3. Monte Carlo decision-model workflow. The author-created flow moves from a deterministic decision model through uncertain inputs, distributions and dependencies, simulation, validation, outcome ranges, sensitivity, and action. Simulation outputs remain conditional on the structure and assumptions. [BB-C22-S09] [BB-C22-S10]", "textEquivalent": "Text equivalent: Define and validate the base decision model; identify uncertain inputs; choose evidence-based ranges or distributions and their dependencies; run enough simulations for stable summaries; compare results with known data or limiting cases; inspect the full outcome distribution and tail; identify decision drivers; then act, stage, hedge, redesign, or collect higher-value information.", "sourceIds": [ "BB-C22-S09", "BB-C22-S10" ], "provenanceStatus": "constructed", "checksum": "101d32d41c933827f6dd5449de41f05da7cf75ab9461343685f01b8eb960acb1" }, { "id": "chapter-22-data-analysis-and-insights-figure-4", "type": "mermaid", "caption": "Figure 22.4. Evidence-gated decision tree for a constructed AI-support decision. Decision and chance nodes are labeled in text as well as by shape. The tree compares immediate launch, testing, and deferral only after non-compensable gates pass. It is an author-created worked example based on expected-value, decision-tree, Bayesian-update, utility, information-value, and reversibility principles. [BB-C22-S11] [BB-C22-S12] [BB-C22-S13] [BB-C22-S14]", "textEquivalent": "Text equivalent: First determine whether legal, safety, rights, security, privacy, accessibility, and authority gates are satisfied. If not, redesign or stop. If they are satisfied, compare immediate launch, an evaluation followed by a later launch/defer decision, and deferral. Immediate launch faces a 45 percent high-value outcome and 55 percent low-value outcome. The evaluation passes 47 percent of the time; after a pass, the updated high-value probability is 76.6 percent and launch has a positive conditional EMV. After a fail, the updated probability is 17.0 percent and deferral dominates launch in the constructed monetary model.", "sourceIds": [ "BB-C22-S11", "BB-C22-S12", "BB-C22-S13", "BB-C22-S14" ], "provenanceStatus": "constructed", "checksum": "ab5625d537262e208a80b7b00ef932da8428731f32a4bc710772a0943eb38258" }, { "id": "chapter-22-data-analysis-and-insights-figure-5", "type": "svg", "caption": "Figure 22.5. Effect-size/sample-size curve. Author-created calculation using the stated normal approximation; deterministic data and assumptions are in docs/evidence-packets/ch22-experiment-optimization-visual-data.json . The curve is illustrative, not a universal sample-size rule. [BB-C22-S16]", "textEquivalent": "A downward-curving line shows required sample per arm falling from 1,568 at a standardized minimum detectable effect of 0.10 to 63 at 0.50, assuming a two-sided five percent error rate and eighty percent power.", "sourceIds": [ "BB-C22-S16" ], "provenanceStatus": "constructed", "checksum": "d02aeab6fb5223f4997daf72c18888d28c20aca5faafcfca6ace34794a5621f8" }, { "id": "chapter-22-data-analysis-and-insights-figure-6", "type": "svg", "caption": "Figure 22.6. Linear-program feasible region. The shaded area contains all choices satisfying the constructed constraints. The continuous objective reaches its maximum at the intersection; a whole-unit requirement moves the solution to the best feasible integer point. Data and verification inputs are in docs/evidence-packets/ch22-experiment-optimization-visual-data.json . [BB-C22-S21] [BB-C22-S22]", "textEquivalent": "A shaded polygon shows nonnegative product combinations satisfying labor and machine constraints. The continuous optimum is their intersection at about 39.67 units of X and 20.67 units of Y. A vertical scenario constraint at X equals 35 shrinks the feasible region.", "sourceIds": [ "BB-C22-S21", "BB-C22-S22" ], "provenanceStatus": "constructed", "checksum": "565181844ff963930678731bea13e3a8e3130fb11cdb1c1624ab470ab164798b" } ], "tables": [ { "id": "chapter-22-data-analysis-and-insights-table-1", "caption": "Table 1. Layer / Question / Output", "headers": [ "Layer", "Question", "Output" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "chapter-22-data-analysis-and-insights-table-2", "caption": "Table 2. Element / Purpose / Example", "headers": [ "Element", "Purpose", "Example" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "chapter-22-data-analysis-and-insights-table-3", "caption": "Table 3. Evidence Situation / Managerial Use / Decision Stance", "headers": [ "Evidence Situation", "Managerial Use", "Decision Stance" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "chapter-22-data-analysis-and-insights-table-4", "caption": "Table 4. Result / Interpretation / Decision Implication", "headers": [ "Result", "Interpretation", "Decision Implication" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "chapter-22-data-analysis-and-insights-table-5", "caption": "Table 5. Output Item / Analyst Language / Manager Translation", "headers": [ "Output Item", "Analyst Language", "Manager Translation" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 8 }, { "id": "chapter-22-data-analysis-and-insights-table-6", "caption": "Table 6. Analytical Need / Use / Avoid", "headers": [ "Analytical Need", "Use", "Avoid" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 7 }, { "id": "chapter-22-data-analysis-and-insights-table-7", "caption": "Table 7. Level / Example / Managerial Purpose", "headers": [ "Level", "Example", "Managerial Purpose" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-22-data-analysis-and-insights-table-8", "caption": "Table 8. Type / Comparison Target / Best Use", "headers": [ "Type", "Comparison Target", "Best Use" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-22-data-analysis-and-insights-table-9", "caption": "Table 9. Gap / Likely Cause / Evidence Quality", "headers": [ "Gap", "Likely Cause", "Evidence Quality", "Action", "Owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2 }, { "id": "chapter-22-data-analysis-and-insights-table-10", "caption": "Table 10. Assumption / Base Case / Downside Case", "headers": [ "Assumption", "Base Case", "Downside Case", "Upside Case", "Decision Sensitivity", "Action" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "chapter-22-data-analysis-and-insights-table-11", "caption": "Table 11. Input Type / Practical Distribution Choice / Example", "headers": [ "Input Type", "Practical Distribution Choice", "Example" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-22-data-analysis-and-insights-table-12", "caption": "Table 12. Decision question / Calculation / Result", "headers": [ "Decision question", "Calculation", "Result", "Managerial meaning" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 10 }, { "id": "chapter-22-data-analysis-and-insights-table-13", "caption": "Table 13. Estimand Element / Managerial Question / Example", "headers": [ "Estimand Element", "Managerial Question", "Example" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "chapter-22-data-analysis-and-insights-table-14", "caption": "Table 14. Standardized MDE / Required Sample Per Arm", "headers": [ "Standardized MDE", "Required Sample Per Arm" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 7 }, { "id": "chapter-22-data-analysis-and-insights-table-15", "caption": "Table 15. Element / Meaning / Product-Mix Teaching Model", "headers": [ "Element", "Meaning", "Product-Mix Teaching Model" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "chapter-22-data-analysis-and-insights-table-16", "caption": "Table 16. Feasible Vertex / Objective 40x + 30y / Interpretation", "headers": [ "Feasible Vertex", "Objective 40x + 30y", "Interpretation" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "chapter-22-data-analysis-and-insights-table-17", "caption": "Table 17. Question / Pass Standard", "headers": [ "Question", "Pass Standard" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 14 } ], "tools": [], "visibility": "public", "pagePath": "chapters/chapter-22-data-analysis-and-insights.html", "outboundSlugs": [ "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-13-startup-foundations", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-18-digital-business-models-and-platform-economics", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy" ], "backlinkSlugs": [ "appendix-a-framework-selection-decision-trees", "appendix-b-contrarian-business-perspectives", "appendix-c-public-record-decision-cases", "chapter-01-macroeconomics-for-strategic-leaders", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-14-go-to-market-strategy", "chapter-15-fundraising-and-finance", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy" ] }, { "id": "appendix-a-framework-selection-decision-trees", "slug": "appendix-a-framework-selection-decision-trees", "kind": "appendix", "number": null, "title": "Appendix A: Framework Selection Decision Trees", "part": "Appendices", "summary": "Decision trees for choosing the right framework by business problem.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [], "relatedSlugs": [], "sourcePath": "src/appendix-a-decision-trees.md", "outputPath": "index.html#appendix-a-framework-selection-decision-trees", "markdownPath": "markdown/appendix-a-framework-selection-decision-trees.md", "wordCount": 2634, "checksum": "bc355d922150a52b619239d95c9c51534d5cc1df422a2996400d349cb247a66e", "sourceIds": [], "headings": [ { "level": 2, "text": "Overview", "id": "appendix-a-framework-selection-decision-trees-overview" }, { "level": 2, "text": "Newly Added Decision Destinations", "id": "appendix-a-framework-selection-decision-trees-newly-added-decision-destinations" }, { "level": 2, "text": "Decision Tree 1: Strategic Situation Analysis", "id": "appendix-a-framework-selection-decision-trees-decision-tree-1-strategic-situation-analysis" }, { "level": 2, "text": "Decision Tree 2: Financial Analysis & Valuation", "id": "appendix-a-framework-selection-decision-trees-decision-tree-2-financial-analysis-valuation" }, { "level": 2, "text": "Decision Tree 3: Marketing & Customer Strategy", "id": "appendix-a-framework-selection-decision-trees-decision-tree-3-marketing-customer-strategy" }, { "level": 2, "text": "Decision Tree 4: Operations & Process Improvement", "id": "appendix-a-framework-selection-decision-trees-decision-tree-4-operations-process-improvement" }, { "level": 2, "text": "Decision Tree 5: Organizational & Leadership Challenges", "id": "appendix-a-framework-selection-decision-trees-decision-tree-5-organizational-leadership-challenges" }, { "level": 2, "text": "Decision Tree 6: Consulting & Problem-Solving", "id": "appendix-a-framework-selection-decision-trees-decision-tree-6-consulting-problem-solving" }, { "level": 2, "text": "Decision Tree 7: Startup & Entrepreneurship", "id": "appendix-a-framework-selection-decision-trees-decision-tree-7-startup-entrepreneurship" }, { "level": 2, "text": "Decision Tree 8: AI & Digital Strategy", "id": "appendix-a-framework-selection-decision-trees-decision-tree-8-ai-digital-strategy" }, { "level": 2, "text": "Decision Tree 9: Project Management", "id": "appendix-a-framework-selection-decision-trees-decision-tree-9-project-management" }, { "level": 2, "text": "Decision Tree 10: Launching New Business Unit", "id": "appendix-a-framework-selection-decision-trees-decision-tree-10-launching-new-business-unit" }, { "level": 2, "text": "Quick Reference: Common Business Situations", "id": "appendix-a-framework-selection-decision-trees-quick-reference-common-business-situations" }, { "level": 3, "text": "Situation 1: \"Revenue is declining\"", "id": "appendix-a-framework-selection-decision-trees-situation-1-revenue-is-declining" }, { "level": 3, "text": "Situation 2: \"Costs are too high\"", "id": "appendix-a-framework-selection-decision-trees-situation-2-costs-are-too-high" }, { "level": 3, "text": "Situation 3: \"Team not performing\"", "id": "appendix-a-framework-selection-decision-trees-situation-3-team-not-performing" }, { "level": 3, "text": "Situation 4: \"Should we enter this market?\"", "id": "appendix-a-framework-selection-decision-trees-situation-4-should-we-enter-this-market" }, { "level": 3, "text": "Situation 5: \"AI project - where to start?\"", "id": "appendix-a-framework-selection-decision-trees-situation-5-ai-project-where-to-start" }, { "level": 3, "text": "Situation 6: \"Startup - product-market fit?\"", "id": "appendix-a-framework-selection-decision-trees-situation-6-startup-product-market-fit" }, { "level": 2, "text": "Framework Combination Strategies", "id": "appendix-a-framework-selection-decision-trees-framework-combination-strategies" }, { "level": 3, "text": "Strategy 1: \"Full Strategic Planning\"", "id": "appendix-a-framework-selection-decision-trees-strategy-1-full-strategic-planning" }, { "level": 3, "text": "Strategy 2: \"Operational Excellence Program\"", "id": "appendix-a-framework-selection-decision-trees-strategy-2-operational-excellence-program" }, { "level": 3, "text": "Strategy 3: \"Digital Transformation\"", "id": "appendix-a-framework-selection-decision-trees-strategy-3-digital-transformation" }, { "level": 2, "text": "Chapter Cross-Reference Matrix", "id": "appendix-a-framework-selection-decision-trees-chapter-cross-reference-matrix" }, { "level": 2, "text": "Quick Start Guide", "id": "appendix-a-framework-selection-decision-trees-quick-start-guide" }, { "level": 3, "text": "\"I have 5 minutes...\"", "id": "appendix-a-framework-selection-decision-trees-i-have-5-minutes" }, { "level": 3, "text": "\"I have 30 minutes...\"", "id": "appendix-a-framework-selection-decision-trees-i-have-30-minutes" }, { "level": 3, "text": "\"I have 2 hours...\"", "id": "appendix-a-framework-selection-decision-trees-i-have-2-hours" }, { "level": 3, "text": "\"I have 1 day...\"", "id": "appendix-a-framework-selection-decision-trees-i-have-1-day" }, { "level": 3, "text": "\"I'm teaching/presenting...\"", "id": "appendix-a-framework-selection-decision-trees-i-m-teaching-presenting" } ], "figures": [ { "id": "appendix-a-framework-selection-decision-trees-figure-1", "type": "mermaid", "caption": "Figure A.1. Strategic-situation routing (constructed). Routes industry and internal analysis, growth choices, disruption, financial health, operational capability, and AI opportunity questions to Chapters 3, 4, 6, and 16.", "textEquivalent": "Text equivalent: Start with the decision and evidence need. Use Chapter 3 for industry, capabilities, growth, and disruption; Chapter 4 for financial health; Chapter 6 for operating capability; and Chapter 16 only after comparing AI and non-AI options.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "7d881cb30aec70402ec495f864965745c8279f7776e4edfc32378260786f05e3" }, { "id": "appendix-a-framework-selection-decision-trees-figure-2", "type": "mermaid", "caption": "Figure A.2. Financial-question routing (constructed). Separates intrinsic valuation, market and transaction evidence, operating performance, unit economics, venture finance, and cash/runway questions across Chapters 4, 15, 18, and 22.", "textEquivalent": "Text equivalent: Use Chapter 4 for financial statements, intrinsic valuation, working capital, break-even, and sensitivity, and its comparable-company and precedent-transaction workflow for market and transaction evidence; Chapter 15 for venture financing and terms; Chapter 18 for platform/cohort economics; and Chapter 22 for benchmarking and uncertainty.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "5d3726853fde2ee306893c189a3d417402eacab09a8400e247e7bd55384bce40" }, { "id": "appendix-a-framework-selection-decision-trees-figure-3", "type": "mermaid", "caption": "Figure A.3. Marketing and customer routing (constructed). Separates target/positioning, acquisition, retention, pricing, measurement, international/non-market go-to-market, accessibility-led service discovery, and experimentation across Chapters 5, 14, 21, and 22.", "textEquivalent": "Text equivalent: Use Chapter 5 for segmentation, pricing, retention, journeys, cohorts, and attribution; Chapter 14 for launch and channel, including its international and non-market GTM gate; Chapter 21 for discovery, accessibility-led research, and service blueprinting; and Chapter 22 for precommitted experimentation.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "7c5517424327cde7e7ab5674b9f1f101d614055bf13a3d74a507523d3a3a2253" }, { "id": "appendix-a-framework-selection-decision-trees-figure-4", "type": "mermaid", "caption": "Figure A.4. Operations and process routing (constructed). Routes flow, quality, cost, constraint, and supply-risk questions to Chapters 6, 9, 19, and 22; Lean operations/value-stream mapping is not the Lean Canvas.", "textEquivalent": "Text equivalent: Use Chapter 6 for flow, capacity, waste, quality, and supply chain; Chapter 9 for root-cause structure; Chapter 19 for cyber/supplier exposure; and Chapter 22 for benchmarking and evidence.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "c156cc5d390a9453b852a49443c36f7d3d7d223e1abe41daf0255e46aa4d2d21" }, { "id": "appendix-a-framework-selection-decision-trees-figure-5", "type": "mermaid", "caption": "Figure A.5. Organization and leadership routing (constructed). Routes change, team, talent, culture, negotiation, power, psychological safety, and sustainable digital transformation questions to Chapters 7, 8, 12, and 17.", "textEquivalent": "Text equivalent: Use Chapter 7 for leadership, teams, conflict, motivation, power, safety, and negotiation alternatives, range, value, power, and ethics; Chapter 8 for execution and metrics; Chapter 12 for client-specific negotiation and stakeholder engagement; and Chapter 17 for transformation and its sustainability boundary.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "eab41bad532e8a69ede5702e9eba43f78345bde36e9d6c7577fc8de161746339" }, { "id": "appendix-a-framework-selection-decision-trees-figure-6", "type": "mermaid", "caption": "Figure A.6. Consulting and problem-solving routing (constructed). Routes framing, analysis, experimentation, optimization, negotiation, recommendations, transformation, and implementation to Chapters 9, 10, 11, 12, 17, and 22.", "textEquivalent": "Text equivalent: Use Chapter 9 to frame the problem; Chapter 10 for engagement frameworks; Chapter 11 for delivery; Chapter 12 for stakeholders and negotiation; Chapter 17 for transformation; and Chapter 22 for experimentation and optimization.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "6a3b0c358e2b0a7fc1c9ae6db7a8097bb1c08a754e89fa0e97e8d0d4062f9638" }, { "id": "appendix-a-framework-selection-decision-trees-figure-7", "type": "mermaid", "caption": "Figure A.7. Startup and entrepreneurship routing (constructed). Routes discovery, product, service design, scaling, international go-to-market, acquisition entrepreneurship, economics, runway, financing, and stop decisions to Chapters 13, 14, 15, and 21.", "textEquivalent": "Text equivalent: Use Chapter 13 for venture hypotheses, MVPs, and build/search/sponsor/acquisition pathway selection; Chapter 14 for launch, channels, and international/non-market entry; Chapter 15 for financing, diligence, transition, and runway; and Chapter 21 for discovery, accessibility, service design, PMF, prioritization, and product lifecycle.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "04d33d66dcbe838f75acc73ee40aaa9139026fc31260e312117c47c41ca3c892" }, { "id": "appendix-a-framework-selection-decision-trees-figure-8", "type": "mermaid", "caption": "Figure A.8. AI and digital decision routing (constructed). Routes AI/non-AI opportunity, sourcing, data readiness, deployment, transformation sustainability, security, ethics, and governance to Chapters 16, 17, 19, 20, and 21.", "textEquivalent": "Text equivalent: Use Chapter 16 for value, sourcing, evaluation, and AI governance; Chapter 17 for capability and workforce change and its digital and AI sustainability system boundary; Chapter 19 for security; Chapter 20 for ethics and remedy; and Chapter 21 for accessible product/service discovery and lifecycle.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "5a5772d4366c97dc493926dc8a890e08f92b98b93a3019f14c08ec8c210ccda2" }, { "id": "appendix-a-framework-selection-decision-trees-figure-9", "type": "mermaid", "caption": "Figure A.9. Project delivery routing (constructed). Selects predictive, adaptive, or hybrid delivery from uncertainty, regulation, coupling, feedback, and change cost, then routes all methods to Chapter 11.", "textEquivalent": "Text equivalent: Use Chapter 11 for chartering, work breakdown, schedule, risk, change, agile, hybrid, monitoring, and closure. Choose the delivery approach from uncertainty, compliance, dependency, stakeholder-feedback, and reversibility needs rather than a methodology label alone.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "d388fa13f3409f750951f4add8a62d5e876bcfae330221924890338e7fbcea82" }, { "id": "appendix-a-framework-selection-decision-trees-figure-10", "type": "mermaid", "caption": "Figure A.10. New-business-unit decision and evidence gates (constructed). Integrates strategy, valuation evidence, legal lifecycle, negotiation, business model, international/non-market go-to-market, operations, accessible service discovery, experimentation, optimization, sustainability, scale, and transformation across the canonical chapters.", "textEquivalent": "Text equivalent: Frame and test strategic, financial, stakeholder, operating, product, legal/ethical, and risk assumptions before go/no-go. Use the Chapter 2 legal lifecycle gate, Chapter 4 market/transaction valuation evidence, Chapter 7 and 12 negotiation routes, the Chapter 14 international/non-market gate, the Chapter 17 sustainability boundary, Chapter 21 accessibility/service blueprinting, and Chapter 22 experimentation/optimization when those questions are material. Build a bounded pilot; scale only when value, economics, operations, customer, workforce, risk, and governance gates are met; otherwise pivot, redesign, or stop.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "aac9d6874370dbde75581cbb3723ff7193606f8d3fe70b2ae89e5aab7ccdbc39" } ], "tables": [ { "id": "appendix-a-framework-selection-decision-trees-table-1", "caption": "Table 1. Decision Question / Destination / Use Boundary", "headers": [ "Decision Question", "Destination", "Use Boundary" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 11 }, { "id": "appendix-a-framework-selection-decision-trees-table-2", "caption": "Table 2. Business Function / Primary Chapters / Supporting Chapters", "headers": [ "Business Function", "Primary Chapters", "Supporting Chapters" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 9 } ], "tools": [], "visibility": "public", "pagePath": "chapters/appendix-a-framework-selection-decision-trees.html", "outboundSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-13-startup-foundations", "chapter-14-go-to-market-strategy", "chapter-15-fundraising-and-finance", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-17-leading-digital-transformation", "chapter-18-digital-business-models-and-platform-economics", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [] }, { "id": "appendix-b-contrarian-business-perspectives", "slug": "appendix-b-contrarian-business-perspectives", "kind": "appendix", "number": null, "title": "Appendix B: Contrarian Business Perspectives", "part": "Appendices", "summary": "An evidence-disciplined protocol for testing default assumptions, rival explanations, boundary conditions, dissent, and reversal triggers.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "contrarian challenge", "rival hypothesis", "premortem", "boundary conditions", "decision reversal triggers" ], "relatedSlugs": [ "chapter-03-strategy-and-competitive-analysis", "chapter-09-problem-structuring", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/appendix-b-contrarian-perspectives.md", "outputPath": "index.html#appendix-b-contrarian-business-perspectives", "markdownPath": "markdown/appendix-b-contrarian-business-perspectives.md", "wordCount": 2238, "checksum": "692ba79eed5f839765f100a45418530d9a8539e3cdbb87934adf80e0a2cd80f3", "sourceIds": [ "BB-C09-S05", "BB-C22-S02", "BB-C03-S12", "BB-C03-S13", "BB-C09-S04", "BB-C03-S16", "BB-C22-S03", "BB-C10-S06" ], "headings": [ { "level": 2, "text": "Purpose: challenge a decision, not perform contrarianism", "id": "appendix-b-contrarian-business-perspectives-purpose-challenge-a-decision-not-perform-contrarianism" }, { "level": 3, "text": "Use the protocol when", "id": "appendix-b-contrarian-business-perspectives-use-the-protocol-when" }, { "level": 2, "text": "The contrarian challenge protocol", "id": "appendix-b-contrarian-business-perspectives-the-contrarian-challenge-protocol" }, { "level": 3, "text": "1. Define the decision and the default", "id": "appendix-b-contrarian-business-perspectives-1-define-the-decision-and-the-default" }, { "level": 3, "text": "2. Separate observation, inference, assumption, and unknown", "id": "appendix-b-contrarian-business-perspectives-2-separate-observation-inference-assumption-and-unknown" }, { "level": 3, "text": "3. Write the strongest credible rival", "id": "appendix-b-contrarian-business-perspectives-3-write-the-strongest-credible-rival" }, { "level": 3, "text": "4. Premortem the leading option", "id": "appendix-b-contrarian-business-perspectives-4-premortem-the-leading-option" }, { "level": 3, "text": "5. Test boundary conditions and trade-offs", "id": "appendix-b-contrarian-business-perspectives-5-test-boundary-conditions-and-trade-offs" }, { "level": 3, "text": "6. Match evidence to the disputed claim", "id": "appendix-b-contrarian-business-perspectives-6-match-evidence-to-the-disputed-claim" }, { "level": 3, "text": "7. Decide, record dissent, and set reversal triggers", "id": "appendix-b-contrarian-business-perspectives-7-decide-record-dissent-and-set-reversal-triggers" }, { "level": 2, "text": "Twenty-eight perspectives to test", "id": "appendix-b-contrarian-business-perspectives-twenty-eight-perspectives-to-test" }, { "level": 3, "text": "Strategy and competition", "id": "appendix-b-contrarian-business-perspectives-strategy-and-competition" }, { "level": 3, "text": "Finance and valuation", "id": "appendix-b-contrarian-business-perspectives-finance-and-valuation" }, { "level": 3, "text": "Marketing and customers", "id": "appendix-b-contrarian-business-perspectives-marketing-and-customers" }, { "level": 3, "text": "Organization and leadership", "id": "appendix-b-contrarian-business-perspectives-organization-and-leadership" }, { "level": 3, "text": "Entrepreneurship and innovation", "id": "appendix-b-contrarian-business-perspectives-entrepreneurship-and-innovation" }, { "level": 3, "text": "Technology, AI, and operations", "id": "appendix-b-contrarian-business-perspectives-technology-ai-and-operations" }, { "level": 3, "text": "Governance and time horizon", "id": "appendix-b-contrarian-business-perspectives-governance-and-time-horizon" }, { "level": 2, "text": "One-page challenge record", "id": "appendix-b-contrarian-business-perspectives-one-page-challenge-record" }, { "level": 2, "text": "Constructed example: geographic expansion", "id": "appendix-b-contrarian-business-perspectives-constructed-example-geographic-expansion" }, { "level": 2, "text": "Facilitation and governance guardrails", "id": "appendix-b-contrarian-business-perspectives-facilitation-and-governance-guardrails" }, { "level": 2, "text": "Related chapters", "id": "appendix-b-contrarian-business-perspectives-related-chapters" } ], "figures": [], "tables": [ { "id": "appendix-b-contrarian-business-perspectives-table-1", "caption": "Table 1. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "appendix-b-contrarian-business-perspectives-table-2", "caption": "Table 2. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5 }, { "id": "appendix-b-contrarian-business-perspectives-table-3", "caption": "Table 3. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "appendix-b-contrarian-business-perspectives-table-4", "caption": "Table 4. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "appendix-b-contrarian-business-perspectives-table-5", "caption": "Table 5. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "appendix-b-contrarian-business-perspectives-table-6", "caption": "Table 6. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "appendix-b-contrarian-business-perspectives-table-7", "caption": "Table 7. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 1 }, { "id": "appendix-b-contrarian-business-perspectives-table-8", "caption": "Table 8. Field / Record", "headers": [ "Field", "Record" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 14 } ], "tools": [], "visibility": "public", "pagePath": "chapters/appendix-b-contrarian-business-perspectives.html", "outboundSlugs": [ "appendix-c-public-record-decision-cases", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-09-problem-structuring", "chapter-10-advanced-consulting-frameworks-and-integration", "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-20-the-ethics-of-ai-and-data", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "chapter-15-fundraising-and-finance" ] }, { "id": "appendix-c-public-record-decision-cases", "slug": "appendix-c-public-record-decision-cases", "kind": "appendix", "number": null, "title": "Appendix C: Public-Record Decision Cases", "part": "Appendices", "summary": "Five original decision cases derived from public regulator, government, and SEC-filed records, with dated decision points, incomplete evidence, alternatives, compact exhibits, discussion prompts, and explicit permission and legal-reputation boundaries.", "citationStatus": "vetted", "publicationStatus": "public", "concepts": [ "public-record case method", "decision under uncertainty", "software deployment controls", "security claims governance", "operational recovery", "incentive and remediation design", "capacity and capital allocation", "hindsight bias", "source posture", "legal and reputation review" ], "relatedSlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-11-project-management-and-pmp-frameworks", "chapter-17-leading-digital-transformation", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-22-data-analysis-and-insights" ], "sourcePath": "src/appendix-c-public-record-decision-cases.md", "outputPath": "index.html#appendix-c-public-record-decision-cases", "markdownPath": "markdown/appendix-c-public-record-decision-cases.md", "wordCount": 4113, "checksum": "cd480d6a506b3d865f611002b0d37259ba65d7887d2d2fe65a816b407c9eae56", "sourceIds": [ "BB-C23-S01", "BB-C23-S02", "BB-C23-S03", "BB-C23-S04", "BB-C23-S05", "BB-C23-S06", "BB-C23-S07", "BB-C23-S08", "BB-C23-S09", "BB-C23-S10" ], "headings": [ { "level": 2, "text": "Purpose and evidence boundary", "id": "appendix-c-public-record-decision-cases-purpose-and-evidence-boundary" }, { "level": 3, "text": "How to use the cases", "id": "appendix-c-public-record-decision-cases-how-to-use-the-cases" }, { "level": 3, "text": "Case-pack map", "id": "appendix-c-public-record-decision-cases-case-pack-map" }, { "level": 2, "text": "Case 1: Knight Capital — Halt the Router or Trade Through the Opening?", "id": "appendix-c-public-record-decision-cases-case-1-knight-capital-halt-the-router-or-trade-through-the-opening" }, { "level": 3, "text": "Protagonist and decision point", "id": "appendix-c-public-record-decision-cases-protagonist-and-decision-point" }, { "level": 3, "text": "Exhibit 1A — compact incident evidence", "id": "appendix-c-public-record-decision-cases-exhibit-1a-compact-incident-evidence" }, { "level": 3, "text": "Alternatives available for evaluation", "id": "appendix-c-public-record-decision-cases-alternatives-available-for-evaluation" }, { "level": 3, "text": "Cross-chapter concepts", "id": "appendix-c-public-record-decision-cases-cross-chapter-concepts" }, { "level": 3, "text": "Discussion prompts", "id": "appendix-c-public-record-decision-cases-discussion-prompts" }, { "level": 3, "text": "Source, permission, and caution status", "id": "appendix-c-public-record-decision-cases-source-permission-and-caution-status" }, { "level": 2, "text": "Case 2: Zoom — Build to the Order, or Redesign the Trust System?", "id": "appendix-c-public-record-decision-cases-case-2-zoom-build-to-the-order-or-redesign-the-trust-system" }, { "level": 3, "text": "Protagonist and decision point", "id": "appendix-c-public-record-decision-cases-protagonist-and-decision-point-2" }, { "level": 3, "text": "Exhibit 2A — evidence and obligation map", "id": "appendix-c-public-record-decision-cases-exhibit-2a-evidence-and-obligation-map" }, { "level": 3, "text": "Alternatives available for evaluation", "id": "appendix-c-public-record-decision-cases-alternatives-available-for-evaluation-2" }, { "level": 3, "text": "Cross-chapter concepts", "id": "appendix-c-public-record-decision-cases-cross-chapter-concepts-2" }, { "level": 3, "text": "Discussion prompts", "id": "appendix-c-public-record-decision-cases-discussion-prompts-2" }, { "level": 3, "text": "Source, permission, and caution status", "id": "appendix-c-public-record-decision-cases-source-permission-and-caution-status-2" }, { "level": 2, "text": "Case 3: Southwest Airlines — Recover Incrementally or Reset the Network?", "id": "appendix-c-public-record-decision-cases-case-3-southwest-airlines-recover-incrementally-or-reset-the-network" }, { "level": 3, "text": "Protagonist and decision point", "id": "appendix-c-public-record-decision-cases-protagonist-and-decision-point-3" }, { "level": 3, "text": "Exhibit 3A — recovery system signals", "id": "appendix-c-public-record-decision-cases-exhibit-3a-recovery-system-signals" }, { "level": 3, "text": "Alternatives available for evaluation", "id": "appendix-c-public-record-decision-cases-alternatives-available-for-evaluation-3" }, { "level": 3, "text": "Cross-chapter concepts", "id": "appendix-c-public-record-decision-cases-cross-chapter-concepts-3" }, { "level": 3, "text": "Discussion prompts", "id": "appendix-c-public-record-decision-cases-discussion-prompts-3" }, { "level": 3, "text": "Source, permission, and caution status", "id": "appendix-c-public-record-decision-cases-source-permission-and-caution-status-3" }, { "level": 2, "text": "Case 4: Wells Fargo — Change the Sales Goals, or Rebuild the Control System?", "id": "appendix-c-public-record-decision-cases-case-4-wells-fargo-change-the-sales-goals-or-rebuild-the-control-system" }, { "level": 3, "text": "Protagonist and decision point", "id": "appendix-c-public-record-decision-cases-protagonist-and-decision-point-4" }, { "level": 3, "text": "Exhibit 4A — decision evidence", "id": "appendix-c-public-record-decision-cases-exhibit-4a-decision-evidence" }, { "level": 3, "text": "Alternatives available for evaluation", "id": "appendix-c-public-record-decision-cases-alternatives-available-for-evaluation-4" }, { "level": 3, "text": "Cross-chapter concepts", "id": "appendix-c-public-record-decision-cases-cross-chapter-concepts-4" }, { "level": 3, "text": "Discussion prompts", "id": "appendix-c-public-record-decision-cases-discussion-prompts-4" }, { "level": 3, "text": "Source, permission, and caution status", "id": "appendix-c-public-record-decision-cases-source-permission-and-caution-status-4" }, { "level": 2, "text": "Case 5: Intel — Commit Capacity Now, or Preserve Capital Flexibility?", "id": "appendix-c-public-record-decision-cases-case-5-intel-commit-capacity-now-or-preserve-capital-flexibility" }, { "level": 3, "text": "Protagonist and decision point", "id": "appendix-c-public-record-decision-cases-protagonist-and-decision-point-5" }, { "level": 3, "text": "Exhibit 5A — capital and capacity evidence", "id": "appendix-c-public-record-decision-cases-exhibit-5a-capital-and-capacity-evidence" }, { "level": 3, "text": "Alternatives available for evaluation", "id": "appendix-c-public-record-decision-cases-alternatives-available-for-evaluation-5" }, { "level": 3, "text": "Cross-chapter concepts", "id": "appendix-c-public-record-decision-cases-cross-chapter-concepts-5" }, { "level": 3, "text": "Discussion prompts", "id": "appendix-c-public-record-decision-cases-discussion-prompts-5" }, { "level": 3, "text": "Source, permission, and caution status", "id": "appendix-c-public-record-decision-cases-source-permission-and-caution-status-5" }, { "level": 2, "text": "Pack-level permission and release gate", "id": "appendix-c-public-record-decision-cases-pack-level-permission-and-release-gate" } ], "figures": [], "tables": [ { "id": "appendix-c-public-record-decision-cases-table-1", "caption": "Table 1. Case / Dated decision point / Primary managerial tension", "headers": [ "Case", "Dated decision point", "Primary managerial tension", "Principal chapter connections" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5 }, { "id": "appendix-c-public-record-decision-cases-table-2", "caption": "Table 2. Evidence item / What the public record supports / What remains uncertain at the decision point", "headers": [ "Evidence item", "What the public record supports", "What remains uncertain at the decision point" ], "sourceIds": [ "BB-C23-S01", "BB-C23-S02" ], "provenanceStatus": "source-linked", "rowCount": 4 }, { "id": "appendix-c-public-record-decision-cases-table-3", "caption": "Table 3. Alternative / What it preserves / What it puts at risk or leaves unresolved", "headers": [ "Alternative", "What it preserves", "What it puts at risk or leaves unresolved" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "appendix-c-public-record-decision-cases-table-4", "caption": "Table 4. Evidence or obligation / Public-record basis / Decision uncertainty", "headers": [ "Evidence or obligation", "Public-record basis", "Decision uncertainty" ], "sourceIds": [ "BB-C23-S03", "BB-C23-S04" ], "provenanceStatus": "source-linked", "rowCount": 4 }, { "id": "appendix-c-public-record-decision-cases-table-5", "caption": "Table 5. Alternative / What it emphasizes / Principal trade-offs", "headers": [ "Alternative", "What it emphasizes", "Principal trade-offs" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "appendix-c-public-record-decision-cases-table-6", "caption": "Table 6. System surface / Evidence reconstructed from the public record / Missing decision information", "headers": [ "System surface", "Evidence reconstructed from the public record", "Missing decision information" ], "sourceIds": [ "BB-C23-S06", "BB-C23-S05" ], "provenanceStatus": "constructed", "rowCount": 4 }, { "id": "appendix-c-public-record-decision-cases-table-7", "caption": "Table 7. Alternative / Potential advantage / Principal risk", "headers": [ "Alternative", "Potential advantage", "Principal risk" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "appendix-c-public-record-decision-cases-table-8", "caption": "Table 8. Evidence surface / Source-grounded signal / Important unknown", "headers": [ "Evidence surface", "Source-grounded signal", "Important unknown" ], "sourceIds": [ "BB-C23-S07", "BB-C23-S08" ], "provenanceStatus": "source-linked", "rowCount": 4 }, { "id": "appendix-c-public-record-decision-cases-table-9", "caption": "Table 9. Alternative / Potential advantage / Principal risk", "headers": [ "Alternative", "Potential advantage", "Principal risk" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 }, { "id": "appendix-c-public-record-decision-cases-table-10", "caption": "Table 10. Evidence surface / Public-record signal available by the decision point / Key uncertainty", "headers": [ "Evidence surface", "Public-record signal available by the decision point", "Key uncertainty" ], "sourceIds": [ "BB-C23-S09", "BB-C23-S10" ], "provenanceStatus": "source-linked", "rowCount": 4 }, { "id": "appendix-c-public-record-decision-cases-table-11", "caption": "Table 11. Alternative / Potential advantage / Principal risk", "headers": [ "Alternative", "Potential advantage", "Principal risk" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4 } ], "tools": [], "visibility": "public", "pagePath": "chapters/appendix-c-public-record-decision-cases.html", "outboundSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders", "chapter-02-business-law-governance-and-ethics", "chapter-03-strategy-and-competitive-analysis", "chapter-04-financial-analysis-and-valuation", "chapter-05-marketing-and-customer-analytics", "chapter-06-operations-and-supply-chain", "chapter-07-organizational-behavior-and-leadership", "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "chapter-11-project-management-and-pmp-frameworks", "chapter-12-client-management", "chapter-14-go-to-market-strategy", "chapter-17-leading-digital-transformation", "chapter-19-cybersecurity-and-risk-management-for-managers", "chapter-20-the-ethics-of-ai-and-data", "chapter-21-product-management-and-product-strategy", "chapter-22-data-analysis-and-insights" ], "backlinkSlugs": [ "appendix-b-contrarian-business-perspectives" ] } ], "concepts": [ { "name": "accessibility-led design", "id": "concept-accessibility-led-design", "entrySlugs": [ "chapter-21-product-management-and-product-strategy" ] }, { "name": "accountability", "id": "concept-accountability", "entrySlugs": [ "chapter-20-the-ethics-of-ai-and-data" ] }, { "name": "acquisition financing", "id": "concept-acquisition-financing", "entrySlugs": [ "chapter-15-fundraising-and-finance" ] }, { "name": "acquisition screening", "id": "concept-acquisition-screening", "entrySlugs": [ "chapter-13-startup-foundations" ] }, { "name": "acquisition transition", "id": "concept-acquisition-transition", "entrySlugs": [ "chapter-15-fundraising-and-finance" ] }, { "name": "AI business case", "id": "concept-ai-business-case", "entrySlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ] }, { "name": "AI ethics", "id": "concept-ai-ethics", "entrySlugs": [ "chapter-20-the-ethics-of-ai-and-data" ] }, { "name": "AI strategy", "id": "concept-ai-strategy", "entrySlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ] }, { "name": "antitrust", "id": "concept-antitrust", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics" ] }, { "name": "APIs", "id": "concept-apis", "entrySlugs": [ "chapter-18-digital-business-models-and-platform-economics" ] }, { "name": "balanced scorecard", "id": "concept-balanced-scorecard", "entrySlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ] }, { "name": "BATNA", "id": "concept-batna", "entrySlugs": [ "chapter-07-organizational-behavior-and-leadership" ] }, { "name": "Bayesian updating", "id": "concept-bayesian-updating", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "BCG Matrix", "id": "concept-bcg-matrix", "entrySlugs": [ "chapter-03-strategy-and-competitive-analysis" ] }, { "name": "bias", "id": "concept-bias", "entrySlugs": [ "chapter-20-the-ethics-of-ai-and-data" ] }, { "name": "Blue Ocean Strategy", "id": "concept-blue-ocean-strategy", "entrySlugs": [ "chapter-03-strategy-and-competitive-analysis" ] }, { "name": "boundary conditions", "id": "concept-boundary-conditions", "entrySlugs": [ "appendix-b-contrarian-business-perspectives" ] }, { "name": "brand equity", "id": "concept-brand-equity", "entrySlugs": [ "chapter-05-marketing-and-customer-analytics" ] }, { "name": "break-even probability", "id": "concept-break-even-probability", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "business cycle", "id": "concept-business-cycle", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "business model canvas", "id": "concept-business-model-canvas", "entrySlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ] }, { "name": "CAC", "id": "concept-cac", "entrySlugs": [ "chapter-05-marketing-and-customer-analytics" ] }, { "name": "capacity and capital allocation", "id": "concept-capacity-and-capital-allocation", "entrySlugs": [ "appendix-c-public-record-decision-cases" ] }, { "name": "capacity planning", "id": "concept-capacity-planning", "entrySlugs": [ "chapter-06-operations-and-supply-chain" ] }, { "name": "capital planning", "id": "concept-capital-planning", "entrySlugs": [ "chapter-15-fundraising-and-finance" ] }, { "name": "capital structure", "id": "concept-capital-structure", "entrySlugs": [ "chapter-04-financial-analysis-and-valuation" ] }, { "name": "change leadership", "id": "concept-change-leadership", "entrySlugs": [ "chapter-17-leading-digital-transformation" ] }, { "name": "change management", "id": "concept-change-management", "entrySlugs": [ "chapter-07-organizational-behavior-and-leadership" ] }, { "name": "channels", "id": "concept-channels", "entrySlugs": [ "chapter-14-go-to-market-strategy" ] }, { "name": "client negotiation", "id": "concept-client-negotiation", "entrySlugs": [ "chapter-12-client-management" ] }, { "name": "CLV", "id": "concept-clv", "entrySlugs": [ "chapter-05-marketing-and-customer-analytics" ] }, { "name": "comparable companies", "id": "concept-comparable-companies", "entrySlugs": [ "chapter-04-financial-analysis-and-valuation" ] }, { "name": "consumer protection", "id": "concept-consumer-protection", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics" ] }, { "name": "contracts", "id": "concept-contracts", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics" ] }, { "name": "contrarian challenge", "id": "concept-contrarian-challenge", "entrySlugs": [ "appendix-b-contrarian-business-perspectives" ] }, { "name": "controls", "id": "concept-controls", "entrySlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ] }, { "name": "correlation vs causation", "id": "concept-correlation-vs-causation", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "critical path", "id": "concept-critical-path", "entrySlugs": [ "chapter-11-project-management-and-pmp-frameworks" ] }, { "name": "cross-border data", "id": "concept-cross-border-data", "entrySlugs": [ "chapter-14-go-to-market-strategy" ] }, { "name": "culture", "id": "concept-culture", "entrySlugs": [ "chapter-07-organizational-behavior-and-leadership" ] }, { "name": "customer discovery", "id": "concept-customer-discovery", "entrySlugs": [ "chapter-13-startup-foundations" ] }, { "name": "customer journey", "id": "concept-customer-journey", "entrySlugs": [ "chapter-05-marketing-and-customer-analytics" ] }, { "name": "cyber risk", "id": "concept-cyber-risk", "entrySlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ] }, { "name": "data monetization", "id": "concept-data-monetization", "entrySlugs": [ "chapter-18-digital-business-models-and-platform-economics" ] }, { "name": "data readiness", "id": "concept-data-readiness", "entrySlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ] }, { "name": "DCF", "id": "concept-dcf", "entrySlugs": [ "chapter-04-financial-analysis-and-valuation" ] }, { "name": "debt service coverage ratio", "id": "concept-debt-service-coverage-ratio", "entrySlugs": [ "chapter-15-fundraising-and-finance" ] }, { "name": "decision reversal triggers", "id": "concept-decision-reversal-triggers", "entrySlugs": [ "appendix-b-contrarian-business-perspectives" ] }, { "name": "decision systems", "id": "concept-decision-systems", "entrySlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ] }, { "name": "decision trees", "id": "concept-decision-trees", "entrySlugs": [ "chapter-09-problem-structuring" ] }, { "name": "decision under uncertainty", "id": "concept-decision-under-uncertainty", "entrySlugs": [ "appendix-c-public-record-decision-cases" ] }, { "name": "digital maturity", "id": "concept-digital-maturity", "entrySlugs": [ "chapter-17-leading-digital-transformation" ] }, { "name": "digital sustainability", "id": "concept-digital-sustainability", "entrySlugs": [ "chapter-17-leading-digital-transformation" ] }, { "name": "digital transformation", "id": "concept-digital-transformation", "entrySlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ] }, { "name": "dilution", "id": "concept-dilution", "entrySlugs": [ "chapter-15-fundraising-and-finance" ] }, { "name": "earned value", "id": "concept-earned-value", "entrySlugs": [ "chapter-11-project-management-and-pmp-frameworks" ] }, { "name": "ecosystems", "id": "concept-ecosystems", "entrySlugs": [ "chapter-18-digital-business-models-and-platform-economics" ] }, { "name": "embodied emissions", "id": "concept-embodied-emissions", "entrySlugs": [ "chapter-17-leading-digital-transformation" ] }, { "name": "enterprise architecture", "id": "concept-enterprise-architecture", "entrySlugs": [ "chapter-17-leading-digital-transformation" ] }, { "name": "entity authority", "id": "concept-entity-authority", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics" ] }, { "name": "entrepreneurship through acquisition", "id": "concept-entrepreneurship-through-acquisition", "entrySlugs": [ "chapter-13-startup-foundations" ] }, { "name": "environmental claims", "id": "concept-environmental-claims", "entrySlugs": [ "chapter-17-leading-digital-transformation" ] }, { "name": "estimand", "id": "concept-estimand", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "ethics", "id": "concept-ethics", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics" ] }, { "name": "exchange rates", "id": "concept-exchange-rates", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "executive communication", "id": "concept-executive-communication", "entrySlugs": [ "chapter-12-client-management" ] }, { "name": "expected monetary value", "id": "concept-expected-monetary-value", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "expected utility", "id": "concept-expected-utility", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "experiment power", "id": "concept-experiment-power", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "feedback", "id": "concept-feedback", "entrySlugs": [ "chapter-12-client-management" ] }, { "name": "financial ratios", "id": "concept-financial-ratios", "entrySlugs": [ "chapter-04-financial-analysis-and-valuation" ] }, { "name": "fiscal policy", "id": "concept-fiscal-policy", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "flow management", "id": "concept-flow-management", "entrySlugs": [ "chapter-11-project-management-and-pmp-frameworks" ] }, { "name": "football field valuation", "id": "concept-football-field-valuation", "entrySlugs": [ "chapter-04-financial-analysis-and-valuation" ] }, { "name": "forecast accuracy", "id": "concept-forecast-accuracy", "entrySlugs": [ "chapter-06-operations-and-supply-chain" ] }, { "name": "founder choices", "id": "concept-founder-choices", "entrySlugs": [ "chapter-13-startup-foundations" ] }, { "name": "GDP", "id": "concept-gdp", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "governance", "id": "concept-governance", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics" ] }, { "name": "hindsight bias", "id": "concept-hindsight-bias", "entrySlugs": [ "appendix-c-public-record-decision-cases" ] }, { "name": "human-centered design", "id": "concept-human-centered-design", "entrySlugs": [ "chapter-21-product-management-and-product-strategy" ] }, { "name": "hypothesis pyramid", "id": "concept-hypothesis-pyramid", "entrySlugs": [ "chapter-09-problem-structuring" ] }, { "name": "ICP", "id": "concept-icp", "entrySlugs": [ "chapter-14-go-to-market-strategy" ] }, { "name": "incentive and remediation design", "id": "concept-incentive-and-remediation-design", "entrySlugs": [ "appendix-c-public-record-decision-cases" ] }, { "name": "incident response", "id": "concept-incident-response", "entrySlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ] }, { "name": "inclusive research", "id": "concept-inclusive-research", "entrySlugs": [ "chapter-21-product-management-and-product-strategy" ] }, { "name": "incrementality", "id": "concept-incrementality", "entrySlugs": [ "chapter-05-marketing-and-customer-analytics" ] }, { "name": "inflation", "id": "concept-inflation", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "insolvency", "id": "concept-insolvency", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics" ] }, { "name": "intellectual property", "id": "concept-intellectual-property", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics" ] }, { "name": "interest rates", "id": "concept-interest-rates", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "international market entry", "id": "concept-international-market-entry", "entrySlugs": [ "chapter-14-go-to-market-strategy" ] }, { "name": "issue trees", "id": "concept-issue-trees", "entrySlugs": [ "chapter-09-problem-structuring" ] }, { "name": "jobs to be done", "id": "concept-jobs-to-be-done", "entrySlugs": [ "chapter-21-product-management-and-product-strategy" ] }, { "name": "KPI trees", "id": "concept-kpi-trees", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "KPIs", "id": "concept-kpis", "entrySlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ] }, { "name": "labor markets", "id": "concept-labor-markets", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "leadership", "id": "concept-leadership", "entrySlugs": [ "chapter-07-organizational-behavior-and-leadership" ] }, { "name": "lean", "id": "concept-lean", "entrySlugs": [ "chapter-06-operations-and-supply-chain" ] }, { "name": "lean startup", "id": "concept-lean-startup", "entrySlugs": [ "chapter-13-startup-foundations" ] }, { "name": "legal and reputation review", "id": "concept-legal-and-reputation-review", "entrySlugs": [ "appendix-c-public-record-decision-cases" ] }, { "name": "lifecycle assessment", "id": "concept-lifecycle-assessment", "entrySlugs": [ "chapter-17-leading-digital-transformation" ] }, { "name": "linear programming", "id": "concept-linear-programming", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "logic trees", "id": "concept-logic-trees", "entrySlugs": [ "chapter-09-problem-structuring" ] }, { "name": "M&A diligence", "id": "concept-m-a-diligence", "entrySlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ] }, { "name": "macroeconomic indicators", "id": "concept-macroeconomic-indicators", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "marketing mix modeling", "id": "concept-marketing-mix-modeling", "entrySlugs": [ "chapter-05-marketing-and-customer-analytics" ] }, { "name": "McKinsey 7S", "id": "concept-mckinsey-7s", "entrySlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ] }, { "name": "MECE", "id": "concept-mece", "entrySlugs": [ "chapter-09-problem-structuring" ] }, { "name": "minimum detectable effect", "id": "concept-minimum-detectable-effect", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "mission", "id": "concept-mission", "entrySlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ] }, { "name": "mixed-integer optimization", "id": "concept-mixed-integer-optimization", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "model governance", "id": "concept-model-governance", "entrySlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ] }, { "name": "monetary policy", "id": "concept-monetary-policy", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "multiparty negotiation", "id": "concept-multiparty-negotiation", "entrySlugs": [ "chapter-07-organizational-behavior-and-leadership", "chapter-12-client-management" ] }, { "name": "multiple testing", "id": "concept-multiple-testing", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "MVP", "id": "concept-mvp", "entrySlugs": [ "chapter-13-startup-foundations" ] }, { "name": "network effects", "id": "concept-network-effects", "entrySlugs": [ "chapter-18-digital-business-models-and-platform-economics" ] }, { "name": "non-market strategy", "id": "concept-non-market-strategy", "entrySlugs": [ "chapter-14-go-to-market-strategy" ] }, { "name": "OKRs", "id": "concept-okrs", "entrySlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ] }, { "name": "operating model", "id": "concept-operating-model", "entrySlugs": [ "chapter-17-leading-digital-transformation" ] }, { "name": "operational recovery", "id": "concept-operational-recovery", "entrySlugs": [ "appendix-c-public-record-decision-cases" ] }, { "name": "platforms", "id": "concept-platforms", "entrySlugs": [ "chapter-18-digital-business-models-and-platform-economics" ] }, { "name": "Porter's Five Forces", "id": "concept-porter-s-five-forces", "entrySlugs": [ "chapter-03-strategy-and-competitive-analysis" ] }, { "name": "positioning", "id": "concept-positioning", "entrySlugs": [ "chapter-14-go-to-market-strategy" ] }, { "name": "post-merger integration", "id": "concept-post-merger-integration", "entrySlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ] }, { "name": "precedent transactions", "id": "concept-precedent-transactions", "entrySlugs": [ "chapter-04-financial-analysis-and-valuation" ] }, { "name": "premortem", "id": "concept-premortem", "entrySlugs": [ "appendix-b-contrarian-business-perspectives" ] }, { "name": "pricing", "id": "concept-pricing", "entrySlugs": [ "chapter-05-marketing-and-customer-analytics", "chapter-14-go-to-market-strategy" ] }, { "name": "prioritization", "id": "concept-prioritization", "entrySlugs": [ "chapter-09-problem-structuring" ] }, { "name": "privacy", "id": "concept-privacy", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics", "chapter-20-the-ethics-of-ai-and-data" ] }, { "name": "product operations", "id": "concept-product-operations", "entrySlugs": [ "chapter-21-product-management-and-product-strategy" ] }, { "name": "product strategy", "id": "concept-product-strategy", "entrySlugs": [ "chapter-21-product-management-and-product-strategy" ] }, { "name": "product-market fit", "id": "concept-product-market-fit", "entrySlugs": [ "chapter-13-startup-foundations" ] }, { "name": "project charter", "id": "concept-project-charter", "entrySlugs": [ "chapter-11-project-management-and-pmp-frameworks" ] }, { "name": "project scoping", "id": "concept-project-scoping", "entrySlugs": [ "chapter-12-client-management" ] }, { "name": "prototype fidelity", "id": "concept-prototype-fidelity", "entrySlugs": [ "chapter-21-product-management-and-product-strategy" ] }, { "name": "psychological safety", "id": "concept-psychological-safety", "entrySlugs": [ "chapter-07-organizational-behavior-and-leadership" ] }, { "name": "public-record case method", "id": "concept-public-record-case-method", "entrySlugs": [ "appendix-c-public-record-decision-cases" ] }, { "name": "pyramid principle", "id": "concept-pyramid-principle", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "quality of earnings", "id": "concept-quality-of-earnings", "entrySlugs": [ "chapter-15-fundraising-and-finance" ] }, { "name": "RACI", "id": "concept-raci", "entrySlugs": [ "chapter-12-client-management" ] }, { "name": "RAPID", "id": "concept-rapid", "entrySlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ] }, { "name": "rebound effect", "id": "concept-rebound-effect", "entrySlugs": [ "chapter-17-leading-digital-transformation" ] }, { "name": "regression interpretation", "id": "concept-regression-interpretation", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "reservation value", "id": "concept-reservation-value", "entrySlugs": [ "chapter-07-organizational-behavior-and-leadership" ] }, { "name": "responsible AI", "id": "concept-responsible-ai", "entrySlugs": [ "chapter-20-the-ethics-of-ai-and-data" ] }, { "name": "RICE", "id": "concept-rice", "entrySlugs": [ "chapter-21-product-management-and-product-strategy" ] }, { "name": "risk management", "id": "concept-risk-management", "entrySlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ] }, { "name": "rival hypothesis", "id": "concept-rival-hypothesis", "entrySlugs": [ "appendix-b-contrarian-business-perspectives" ] }, { "name": "roadmaps", "id": "concept-roadmaps", "entrySlugs": [ "chapter-21-product-management-and-product-strategy" ] }, { "name": "sales and operations planning", "id": "concept-sales-and-operations-planning", "entrySlugs": [ "chapter-06-operations-and-supply-chain" ] }, { "name": "sales funnel", "id": "concept-sales-funnel", "entrySlugs": [ "chapter-14-go-to-market-strategy" ] }, { "name": "sanctions compliance", "id": "concept-sanctions-compliance", "entrySlugs": [ "chapter-14-go-to-market-strategy" ] }, { "name": "scenario planning", "id": "concept-scenario-planning", "entrySlugs": [ "chapter-03-strategy-and-competitive-analysis" ] }, { "name": "SCQA", "id": "concept-scqa", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "search fund", "id": "concept-search-fund", "entrySlugs": [ "chapter-13-startup-foundations" ] }, { "name": "securities disclosure", "id": "concept-securities-disclosure", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics" ] }, { "name": "security claims governance", "id": "concept-security-claims-governance", "entrySlugs": [ "appendix-c-public-record-decision-cases" ] }, { "name": "segmentation", "id": "concept-segmentation", "entrySlugs": [ "chapter-05-marketing-and-customer-analytics" ] }, { "name": "sensitivity analysis", "id": "concept-sensitivity-analysis", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "sequential testing", "id": "concept-sequential-testing", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "service blueprint", "id": "concept-service-blueprint", "entrySlugs": [ "chapter-21-product-management-and-product-strategy" ] }, { "name": "shadow price", "id": "concept-shadow-price", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "Six Sigma", "id": "concept-six-sigma", "entrySlugs": [ "chapter-06-operations-and-supply-chain" ] }, { "name": "software deployment controls", "id": "concept-software-deployment-controls", "entrySlugs": [ "appendix-c-public-record-decision-cases" ] }, { "name": "source posture", "id": "concept-source-posture", "entrySlugs": [ "appendix-c-public-record-decision-cases" ] }, { "name": "sources and uses", "id": "concept-sources-and-uses", "entrySlugs": [ "chapter-15-fundraising-and-finance" ] }, { "name": "spillover effects", "id": "concept-spillover-effects", "entrySlugs": [ "chapter-22-data-analysis-and-insights" ] }, { "name": "stakeholder management", "id": "concept-stakeholder-management", "entrySlugs": [ "chapter-12-client-management" ] }, { "name": "strategy execution", "id": "concept-strategy-execution", "entrySlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ] }, { "name": "supply and demand shocks", "id": "concept-supply-and-demand-shocks", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "supply chain risk", "id": "concept-supply-chain-risk", "entrySlugs": [ "chapter-06-operations-and-supply-chain" ] }, { "name": "supply chain security", "id": "concept-supply-chain-security", "entrySlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ] }, { "name": "Taylor Rule", "id": "concept-taylor-rule", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "team dynamics", "id": "concept-team-dynamics", "entrySlugs": [ "chapter-07-organizational-behavior-and-leadership" ] }, { "name": "term sheets", "id": "concept-term-sheets", "entrySlugs": [ "chapter-15-fundraising-and-finance" ] }, { "name": "term spread", "id": "concept-term-spread", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "theory of constraints", "id": "concept-theory-of-constraints", "entrySlugs": [ "chapter-06-operations-and-supply-chain" ] }, { "name": "transformation failure", "id": "concept-transformation-failure", "entrySlugs": [ "chapter-17-leading-digital-transformation" ] }, { "name": "unit economics", "id": "concept-unit-economics", "entrySlugs": [ "chapter-04-financial-analysis-and-valuation" ] }, { "name": "valuation", "id": "concept-valuation", "entrySlugs": [ "chapter-04-financial-analysis-and-valuation", "chapter-15-fundraising-and-finance" ] }, { "name": "value chain", "id": "concept-value-chain", "entrySlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ] }, { "name": "value of information", "id": "concept-value-of-information", "entrySlugs": [ "chapter-09-problem-structuring", "chapter-22-data-analysis-and-insights" ] }, { "name": "venture capital", "id": "concept-venture-capital", "entrySlugs": [ "chapter-15-fundraising-and-finance" ] }, { "name": "VRIO", "id": "concept-vrio", "entrySlugs": [ "chapter-03-strategy-and-competitive-analysis" ] }, { "name": "WBS", "id": "concept-wbs", "entrySlugs": [ "chapter-11-project-management-and-pmp-frameworks" ] }, { "name": "worker classification", "id": "concept-worker-classification", "entrySlugs": [ "chapter-02-business-law-governance-and-ethics" ] }, { "name": "yield curve", "id": "concept-yield-curve", "entrySlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ] }, { "name": "ZOPA", "id": "concept-zopa", "entrySlugs": [ "chapter-07-organizational-behavior-and-leadership" ] } ], "frameworks": [ { "name": "GDP Growth & Business Cycle Analysis", "id": "chapter-01-macroeconomics-for-strategic-leaders-1-gdp-growth-business-cycle-analysis", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "chapterSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "aliases": [ "GDP" ], "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" ], "description": "GDP Growth & Business Cycle Analysis Macroeconomic Scenario Analysis 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 ", "sourceIds": [ "BB-C01-S13", "BB-C01-S04", "BB-C01-S14", "BB-C01-S01", "BB-C01-S02", "BB-C01-S19" ], "provenanceStatus": "source-linked", "toolIds": [ "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "chapter-01-macroeconomics-for-strategic-leaders-tool-2" ], "backlinks": [ "index.html#chapter-01-macroeconomics-for-strategic-leaders-1-gdp-growth-business-cycle-analysis" ], "url": "index.html#chapter-01-macroeconomics-for-strategic-leaders-1-gdp-growth-business-cycle-analysis" }, { "name": "Inflation & Pricing Strategy Matrix", "id": "chapter-01-macroeconomics-for-strategic-leaders-2-inflation-pricing-strategy-matrix", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "chapterSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "aliases": [], "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" ], "description": "Inflation & Pricing Strategy Matrix Margin Protection 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. 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 | | :--- | :--- | :--- | :--- | | ", "sourceIds": [ "BB-C01-S12" ], "provenanceStatus": "source-linked", "toolIds": [ "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "chapter-01-macroeconomics-for-strategic-leaders-tool-2" ], "backlinks": [ "index.html#chapter-01-macroeconomics-for-strategic-leaders-2-inflation-pricing-strategy-matrix" ], "url": "index.html#chapter-01-macroeconomics-for-strategic-leaders-2-inflation-pricing-strategy-matrix" }, { "name": "Interest Rate & Capital Investment Decision Tree", "id": "chapter-01-macroeconomics-for-strategic-leaders-3-interest-rate-capital-investment-decision-tree", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "chapterSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "aliases": [], "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" ], "description": "Interest Rate & Capital Investment Decision Tree Capital Allocation 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 di", "sourceIds": [ "BB-C01-S05" ], "provenanceStatus": "source-linked", "toolIds": [ "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "chapter-01-macroeconomics-for-strategic-leaders-tool-2" ], "backlinks": [ "index.html#chapter-01-macroeconomics-for-strategic-leaders-3-interest-rate-capital-investment-decision-tree" ], "url": "index.html#chapter-01-macroeconomics-for-strategic-leaders-3-interest-rate-capital-investment-decision-tree" }, { "name": "Unemployment & Labor Market Analysis", "id": "chapter-01-macroeconomics-for-strategic-leaders-4-unemployment-labor-market-analysis", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "chapterSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "aliases": [], "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" ], "description": "Unemployment & Labor Market Analysis Workforce Strategy 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] 1. Monitor Key Labor Market ", "sourceIds": [ "BB-C01-S10", "BB-C01-S20" ], "provenanceStatus": "source-linked", "toolIds": [ "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "chapter-01-macroeconomics-for-strategic-leaders-tool-2" ], "backlinks": [ "index.html#chapter-01-macroeconomics-for-strategic-leaders-4-unemployment-labor-market-analysis" ], "url": "index.html#chapter-01-macroeconomics-for-strategic-leaders-4-unemployment-labor-market-analysis" }, { "name": "Currency Exchange Rate & Global Strategy", "id": "chapter-01-macroeconomics-for-strategic-leaders-5-currency-exchange-rate-global-strategy", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "chapterSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "aliases": [], "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" ], "description": "Currency Exchange Rate & Global Strategy International Operations 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 outcome", "sourceIds": [ "BB-C01-S06" ], "provenanceStatus": "source-linked", "toolIds": [ "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "chapter-01-macroeconomics-for-strategic-leaders-tool-2" ], "backlinks": [ "index.html#chapter-01-macroeconomics-for-strategic-leaders-5-currency-exchange-rate-global-strategy" ], "url": "index.html#chapter-01-macroeconomics-for-strategic-leaders-5-currency-exchange-rate-global-strategy" }, { "name": "Fiscal Policy Impact Assessment", "id": "chapter-01-macroeconomics-for-strategic-leaders-6-fiscal-policy-impact-assessment", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "chapterSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "aliases": [], "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" ], "description": "Fiscal Policy Impact Assessment Government Policy Analysis 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] 1. Map Your Fiscal Policy Exposure Identify how your business is affected by government", "sourceIds": [ "BB-C01-S08" ], "provenanceStatus": "source-linked", "toolIds": [ "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "chapter-01-macroeconomics-for-strategic-leaders-tool-2" ], "backlinks": [ "index.html#chapter-01-macroeconomics-for-strategic-leaders-6-fiscal-policy-impact-assessment" ], "url": "index.html#chapter-01-macroeconomics-for-strategic-leaders-6-fiscal-policy-impact-assessment" }, { "name": "Monetary Policy Radar (Central Bank Watching)", "id": "chapter-01-macroeconomics-for-strategic-leaders-7-monetary-policy-radar-central-bank-watching", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "chapterSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "aliases": [ "Central Bank Watching" ], "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" ], "description": "Monetary Policy Radar (Central Bank Watching) Monetary-Policy Sensitivity 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] 1. Understand Your Central Bank's ", "sourceIds": [ "BB-C01-S03", "BB-C01-S07", "BB-C01-S11", "BB-C01-S17", "BB-C01-S18" ], "provenanceStatus": "source-linked", "toolIds": [ "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "chapter-01-macroeconomics-for-strategic-leaders-tool-2" ], "backlinks": [ "index.html#chapter-01-macroeconomics-for-strategic-leaders-7-monetary-policy-radar-central-bank-watching" ], "url": "index.html#chapter-01-macroeconomics-for-strategic-leaders-7-monetary-policy-radar-central-bank-watching" }, { "name": "Global Economic Indicators Dashboard", "id": "chapter-01-macroeconomics-for-strategic-leaders-8-global-economic-indicators-dashboard", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "chapterSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "aliases": [], "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" ], "description": "Global Economic Indicators Dashboard Macro Monitoring 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. | Field | Required entry | Why it matters | | :--- | :--- | :--- |", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [ "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "chapter-01-macroeconomics-for-strategic-leaders-tool-2" ], "backlinks": [ "index.html#chapter-01-macroeconomics-for-strategic-leaders-8-global-economic-indicators-dashboard" ], "url": "index.html#chapter-01-macroeconomics-for-strategic-leaders-8-global-economic-indicators-dashboard" }, { "name": "Supply & Demand Shock Analysis", "id": "chapter-01-macroeconomics-for-strategic-leaders-9-supply-demand-shock-analysis", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "chapterSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "aliases": [], "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" ], "description": "Supply & Demand Shock Analysis Crisis Management 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] 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", "sourceIds": [ "BB-C01-S09", "BB-C01-S21" ], "provenanceStatus": "source-linked", "toolIds": [ "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "chapter-01-macroeconomics-for-strategic-leaders-tool-2" ], "backlinks": [ "index.html#chapter-01-macroeconomics-for-strategic-leaders-9-supply-demand-shock-analysis" ], "url": "index.html#chapter-01-macroeconomics-for-strategic-leaders-9-supply-demand-shock-analysis" }, { "name": "Yield Curve & Recession Forecasting", "id": "chapter-01-macroeconomics-for-strategic-leaders-10-yield-curve-recession-forecasting", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "chapterSlugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "aliases": [], "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" ], "description": "Yield Curve & Recession Forecasting Recession Scenario Inputs 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 ", "sourceIds": [ "BB-C01-S02", "BB-C01-S15", "BB-C01-S16", "BB-C01-S14" ], "provenanceStatus": "source-linked", "toolIds": [ "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "chapter-01-macroeconomics-for-strategic-leaders-tool-2" ], "backlinks": [ "index.html#chapter-01-macroeconomics-for-strategic-leaders-10-yield-curve-recession-forecasting" ], "url": "index.html#chapter-01-macroeconomics-for-strategic-leaders-10-yield-curve-recession-forecasting" }, { "name": "Business-Judgment Review as a Governance Process", "id": "chapter-02-business-law-governance-and-ethics-1-business-judgment-review-as-a-governance-process", "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "chapterSlugs": [ "chapter-02-business-law-governance-and-ethics" ], "aliases": [], "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "description": "Business-Judgment Review Director Process & Decision Records 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, ex", "sourceIds": [ "BB-C02-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-02-business-law-governance-and-ethics-1-business-judgment-review-as-a-governance-process" ], "url": "index.html#chapter-02-business-law-governance-and-ethics-1-business-judgment-review-as-a-governance-process" }, { "name": "Intellectual Property (IP) Protection Matrix", "id": "chapter-02-business-law-governance-and-ethics-2-intellectual-property-ip-protection-matrix", "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "chapterSlugs": [ "chapter-02-business-law-governance-and-ethics" ], "aliases": [ "IP" ], "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "description": "Intellectual Property (IP) Protection Matrix Innovation Safeguard 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. Figure 2.1. IP issue-routing map. This author-created decision aid distinguishes t", "sourceIds": [ "BB-C02-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-02-business-law-governance-and-ethics-2-intellectual-property-ip-protection-matrix" ], "url": "index.html#chapter-02-business-law-governance-and-ethics-2-intellectual-property-ip-protection-matrix" }, { "name": "Contract Law Essentials for Managers", "id": "chapter-02-business-law-governance-and-ethics-3-contract-law-essentials-for-managers", "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "chapterSlugs": [ "chapter-02-business-law-governance-and-ethics" ], "aliases": [], "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "description": "Contract Law Essentials for Managers Risk Management 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 pro", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-02-business-law-governance-and-ethics-3-contract-law-essentials-for-managers" ], "url": "index.html#chapter-02-business-law-governance-and-ethics-3-contract-law-essentials-for-managers" }, { "name": "Corporate Governance Models (Shareholder vs. Stakeholder)", "id": "chapter-02-business-law-governance-and-ethics-4-corporate-governance-models-shareholder-vs-stakeholder", "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "chapterSlugs": [ "chapter-02-business-law-governance-and-ethics" ], "aliases": [ "Shareholder vs. Stakeholder" ], "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "description": "Corporate Governance Models Strategic Orientation 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 finan", "sourceIds": [ "BB-C02-S04", "BB-C02-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-02-business-law-governance-and-ethics-4-corporate-governance-models-shareholder-vs-stakeholder" ], "url": "index.html#chapter-02-business-law-governance-and-ethics-4-corporate-governance-models-shareholder-vs-stakeholder" }, { "name": "Agency Theory & Executive Compensation", "id": "chapter-02-business-law-governance-and-ethics-5-agency-theory-executive-compensation", "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "chapterSlugs": [ "chapter-02-business-law-governance-and-ethics" ], "aliases": [], "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "description": "Agency Theory & Executive Compensation Alignment Mechanisms 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", "sourceIds": [ "BB-C02-S02", "BB-C02-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-02-business-law-governance-and-ethics-5-agency-theory-executive-compensation" ], "url": "index.html#chapter-02-business-law-governance-and-ethics-5-agency-theory-executive-compensation" }, { "name": "The ESG (Environmental, Social, Governance) Framework", "id": "chapter-02-business-law-governance-and-ethics-6-the-esg-environmental-social-governance-framework", "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "chapterSlugs": [ "chapter-02-business-law-governance-and-ethics" ], "aliases": [ "Environmental, Social, Governance", "ESG" ], "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "description": "ESG Framework Sustainable Value Creation 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 a", "sourceIds": [ "BB-C02-S12", "BB-C02-S13", "BB-C02-S14", "BB-C02-S20" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-02-business-law-governance-and-ethics-6-the-esg-environmental-social-governance-framework" ], "url": "index.html#chapter-02-business-law-governance-and-ethics-6-the-esg-environmental-social-governance-framework" }, { "name": "Ethical Decision-Making Models", "id": "chapter-02-business-law-governance-and-ethics-7-ethical-decision-making-models", "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "chapterSlugs": [ "chapter-02-business-law-governance-and-ethics" ], "aliases": [], "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "description": "Ethical Decision-Making Models Moral Reasoning 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] Author-created decision aid: The four-step sequence ", "sourceIds": [ "BB-C02-S11" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-02-business-law-governance-and-ethics-7-ethical-decision-making-models" ], "url": "index.html#chapter-02-business-law-governance-and-ethics-7-ethical-decision-making-models" }, { "name": "Rawlsian Fairness Challenge (Author Adaptation)", "id": "chapter-02-business-law-governance-and-ethics-8-rawlsian-fairness-challenge-author-adaptation", "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "chapterSlugs": [ "chapter-02-business-law-governance-and-ethics" ], "aliases": [ "Author Adaptation" ], "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "description": "Rawlsian Fairness Challenge Fairness Evaluation 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, reprod", "sourceIds": [ "BB-C02-S15" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-02-business-law-governance-and-ethics-8-rawlsian-fairness-challenge-author-adaptation" ], "url": "index.html#chapter-02-business-law-governance-and-ethics-8-rawlsian-fairness-challenge-author-adaptation" }, { "name": "AI Ethics & Risk Assessment Matrix", "id": "chapter-02-business-law-governance-and-ethics-9-ai-ethics-risk-assessment-matrix", "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "chapterSlugs": [ "chapter-02-business-law-governance-and-ethics" ], "aliases": [ "AI" ], "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "description": "AI Ethics & Risk Assessment Matrix Responsible AI 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 applica", "sourceIds": [ "BB-C02-S08", "BB-C02-S09", "BB-C02-S06", "BB-C02-S10" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-02-business-law-governance-and-ethics-9-ai-ethics-risk-assessment-matrix" ], "url": "index.html#chapter-02-business-law-governance-and-ethics-9-ai-ethics-risk-assessment-matrix" }, { "name": "Privacy and GDPR Issue-Spotting Checklist", "id": "chapter-02-business-law-governance-and-ethics-10-privacy-and-gdpr-issue-spotting-checklist", "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "chapterSlugs": [ "chapter-02-business-law-governance-and-ethics" ], "aliases": [ "GDPR" ], "concepts": [ "governance", "ethics", "intellectual property", "contracts", "privacy", "antitrust", "worker classification", "consumer protection", "securities disclosure", "entity authority", "insolvency" ], "description": "Privacy and GDPR Issue-Spotting Checklist Privacy by Design 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, tra", "sourceIds": [ "BB-C02-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-02-business-law-governance-and-ethics-10-privacy-and-gdpr-issue-spotting-checklist" ], "url": "index.html#chapter-02-business-law-governance-and-ethics-10-privacy-and-gdpr-issue-spotting-checklist" }, { "name": "Porter's Five Forces Analysis", "id": "chapter-03-strategy-and-competitive-analysis-1-porter-s-five-forces-analysis", "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "chapterSlugs": [ "chapter-03-strategy-and-competitive-analysis" ], "aliases": [], "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "description": "Porter's Five Forces Analysis Industry Analysis 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] 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", "sourceIds": [ "BB-C03-S01", "BB-C03-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-03-strategy-and-competitive-analysis-1-porter-s-five-forces-analysis" ], "url": "index.html#chapter-03-strategy-and-competitive-analysis-1-porter-s-five-forces-analysis" }, { "name": "VRIO Framework & Dynamic Capabilities", "id": "chapter-03-strategy-and-competitive-analysis-2-vrio-framework-dynamic-capabilities", "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "chapterSlugs": [ "chapter-03-strategy-and-competitive-analysis" ], "aliases": [ "VRIO" ], "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "description": "VRIO Framework & Dynamic Capabilities Competitive Advantage Analysis 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] 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 neutral", "sourceIds": [ "BB-C03-S04", "BB-C03-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-03-strategy-and-competitive-analysis-2-vrio-framework-dynamic-capabilities" ], "url": "index.html#chapter-03-strategy-and-competitive-analysis-2-vrio-framework-dynamic-capabilities" }, { "name": "Blue Ocean Strategy Canvas", "id": "chapter-03-strategy-and-competitive-analysis-3-blue-ocean-strategy-canvas", "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "chapterSlugs": [ "chapter-03-strategy-and-competitive-analysis" ], "aliases": [], "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "description": "Blue Ocean Strategy Canvas Strategic Differentiation 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] - 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 1. Map the Current State: - Identify the key competing factors your ", "sourceIds": [ "BB-C03-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-03-strategy-and-competitive-analysis-3-blue-ocean-strategy-canvas" ], "url": "index.html#chapter-03-strategy-and-competitive-analysis-3-blue-ocean-strategy-canvas" }, { "name": "BCG Growth-Share Matrix", "id": "chapter-03-strategy-and-competitive-analysis-4-bcg-growth-share-matrix", "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "chapterSlugs": [ "chapter-03-strategy-and-competitive-analysis" ], "aliases": [ "BCG" ], "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "description": "BCG Growth-Share Matrix [BB-C03-S07] Portfolio Management 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] - 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 1. Define Your Business Units: Break your company into distinct S", "sourceIds": [ "BB-C03-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-03-strategy-and-competitive-analysis-4-bcg-growth-share-matrix" ], "url": "index.html#chapter-03-strategy-and-competitive-analysis-4-bcg-growth-share-matrix" }, { "name": "Ansoff Matrix", "id": "chapter-03-strategy-and-competitive-analysis-5-ansoff-matrix", "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "chapterSlugs": [ "chapter-03-strategy-and-competitive-analysis" ], "aliases": [], "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "description": "Ansoff Matrix (Product-Market Growth Strategy) Growth Strategy 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] - 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 1. Assess Current Positio", "sourceIds": [ "BB-C03-S08", "BB-C03-S17", "BB-C03-S18" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-03-strategy-and-competitive-analysis-5-ansoff-matrix" ], "url": "index.html#chapter-03-strategy-and-competitive-analysis-5-ansoff-matrix" }, { "name": "PESTLE Analysis", "id": "chapter-03-strategy-and-competitive-analysis-6-pestle-analysis", "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "chapterSlugs": [ "chapter-03-strategy-and-competitive-analysis" ], "aliases": [ "PESTLE" ], "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "description": "PESTLE Analysis (Macro-Environmental Scan) External Environment Analysis 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] - You're entering a new market or geography and n", "sourceIds": [ "BB-C03-S09" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-03-strategy-and-competitive-analysis-6-pestle-analysis" ], "url": "index.html#chapter-03-strategy-and-competitive-analysis-6-pestle-analysis" }, { "name": "McKinsey 7S Framework", "id": "chapter-03-strategy-and-competitive-analysis-7-mckinsey-7s-framework", "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "chapterSlugs": [ "chapter-03-strategy-and-competitive-analysis" ], "aliases": [], "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "description": "McKinsey 7S Framework [BB-C03-S10] Organizational Alignment 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] - 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 dilige", "sourceIds": [ "BB-C03-S10", "BB-C03-S19" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-03-strategy-and-competitive-analysis-7-mckinsey-7s-framework" ], "url": "index.html#chapter-03-strategy-and-competitive-analysis-7-mckinsey-7s-framework" }, { "name": "Core Competency Analysis", "id": "chapter-03-strategy-and-competitive-analysis-8-core-competency-analysis", "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "chapterSlugs": [ "chapter-03-strategy-and-competitive-analysis" ], "aliases": [], "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "description": "Core Competency Analysis Strategic Capabilities 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] - 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. outsour", "sourceIds": [ "BB-C03-S11", "BB-C03-S04", "BB-C03-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-03-strategy-and-competitive-analysis-8-core-competency-analysis" ], "url": "index.html#chapter-03-strategy-and-competitive-analysis-8-core-competency-analysis" }, { "name": "Scenario Planning Matrix", "id": "chapter-03-strategy-and-competitive-analysis-9-scenario-planning-matrix", "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "chapterSlugs": [ "chapter-03-strategy-and-competitive-analysis" ], "aliases": [], "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "description": "Scenario Planning Matrix Strategic Foresight 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] - 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 ", "sourceIds": [ "BB-C03-S12", "BB-C03-S13" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-03-strategy-and-competitive-analysis-9-scenario-planning-matrix" ], "url": "index.html#chapter-03-strategy-and-competitive-analysis-9-scenario-planning-matrix" }, { "name": "Platform Strategy Framework", "id": "chapter-03-strategy-and-competitive-analysis-10-platform-strategy-framework", "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "chapterSlugs": [ "chapter-03-strategy-and-competitive-analysis" ], "aliases": [], "concepts": [ "Porter's Five Forces", "VRIO", "Blue Ocean Strategy", "BCG Matrix", "scenario planning" ], "description": "Platform Strategy Framework Network Effects & Ecosystems 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] - 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 ", "sourceIds": [ "BB-C03-S14", "BB-C03-S15" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-03-strategy-and-competitive-analysis-10-platform-strategy-framework" ], "url": "index.html#chapter-03-strategy-and-competitive-analysis-10-platform-strategy-framework" }, { "name": "DCF (Discounted Cash Flow) Model", "id": "chapter-04-financial-analysis-and-valuation-1-dcf-discounted-cash-flow-model", "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "chapterSlugs": [ "chapter-04-financial-analysis-and-valuation" ], "aliases": [ "DCF", "Discounted Cash Flow" ], "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "description": "Discounted Cash Flow (DCF) Valuation Valuation & Investment Decisions 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] 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 ", "sourceIds": [ "BB-C04-S13" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-04-financial-analysis-and-valuation-1-dcf-discounted-cash-flow-model" ], "url": "index.html#chapter-04-financial-analysis-and-valuation-1-dcf-discounted-cash-flow-model" }, { "name": "LBO (Leveraged Buyout) Model", "id": "chapter-04-financial-analysis-and-valuation-2-lbo-leveraged-buyout-model", "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "chapterSlugs": [ "chapter-04-financial-analysis-and-valuation" ], "aliases": [ "LBO", "Leveraged Buyout" ], "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "description": "Leveraged Buyout (LBO) Model M&A Valuation 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] 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 t", "sourceIds": [ "BB-C04-S02", "BB-C04-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-04-financial-analysis-and-valuation-2-lbo-leveraged-buyout-model" ], "url": "index.html#chapter-04-financial-analysis-and-valuation-2-lbo-leveraged-buyout-model" }, { "name": "Financial Ratios & Modern Metrics", "id": "chapter-04-financial-analysis-and-valuation-3-financial-ratios-modern-metrics", "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "chapterSlugs": [ "chapter-04-financial-analysis-and-valuation" ], "aliases": [], "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "description": "Financial Ratios & Modern Metrics Performance Analysis 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. 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 hea", "sourceIds": [ "BB-C04-S04", "BB-C04-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-04-financial-analysis-and-valuation-3-financial-ratios-modern-metrics" ], "url": "index.html#chapter-04-financial-analysis-and-valuation-3-financial-ratios-modern-metrics" }, { "name": "DuPont Analysis Tree", "id": "chapter-04-financial-analysis-and-valuation-4-dupont-analysis-tree", "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "chapterSlugs": [ "chapter-04-financial-analysis-and-valuation" ], "aliases": [], "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "description": "DuPont Analysis Tree Performance Decomposition 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. 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 e", "sourceIds": [ "BB-C04-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-04-financial-analysis-and-valuation-4-dupont-analysis-tree" ], "url": "index.html#chapter-04-financial-analysis-and-valuation-4-dupont-analysis-tree" }, { "name": "Working Capital Cycle Diagram", "id": "chapter-04-financial-analysis-and-valuation-5-working-capital-cycle-diagram", "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "chapterSlugs": [ "chapter-04-financial-analysis-and-valuation" ], "aliases": [], "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "description": "Working Capital Cycle Diagram Cash Flow Optimization 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] 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): H", "sourceIds": [ "BB-C04-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-04-financial-analysis-and-valuation-5-working-capital-cycle-diagram" ], "url": "index.html#chapter-04-financial-analysis-and-valuation-5-working-capital-cycle-diagram" }, { "name": "Cap Table Evolution Chart", "id": "chapter-04-financial-analysis-and-valuation-6-cap-table-evolution-chart", "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "chapterSlugs": [ "chapter-04-financial-analysis-and-valuation" ], "aliases": [], "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "description": "Cap Table Evolution Chart Equity & Ownership 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] 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", "sourceIds": [ "BB-C04-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-04-financial-analysis-and-valuation-6-cap-table-evolution-chart" ], "url": "index.html#chapter-04-financial-analysis-and-valuation-6-cap-table-evolution-chart" }, { "name": "Unit Economics Calculator", "id": "chapter-04-financial-analysis-and-valuation-7-unit-economics-calculator", "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "chapterSlugs": [ "chapter-04-financial-analysis-and-valuation" ], "aliases": [], "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "description": "Unit Economics (LTV/CAC) Business Model Viability 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] 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", "sourceIds": [ "BB-C04-S09" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-04-financial-analysis-and-valuation-7-unit-economics-calculator" ], "url": "index.html#chapter-04-financial-analysis-and-valuation-7-unit-economics-calculator" }, { "name": "Break-Even Analysis", "id": "chapter-04-financial-analysis-and-valuation-8-break-even-analysis", "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "chapterSlugs": [ "chapter-04-financial-analysis-and-valuation" ], "aliases": [], "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "description": "Break-Even Analysis Profitability Planning 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] 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: ", "sourceIds": [ "BB-C04-S15" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-04-financial-analysis-and-valuation-8-break-even-analysis" ], "url": "index.html#chapter-04-financial-analysis-and-valuation-8-break-even-analysis" }, { "name": "Monte Carlo Simulation", "id": "chapter-04-financial-analysis-and-valuation-9-monte-carlo-simulation", "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "chapterSlugs": [ "chapter-04-financial-analysis-and-valuation" ], "aliases": [], "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "description": "Monte Carlo Simulation Risk Analysis 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] 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 ", "sourceIds": [ "BB-C04-S16" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-04-financial-analysis-and-valuation-9-monte-carlo-simulation" ], "url": "index.html#chapter-04-financial-analysis-and-valuation-9-monte-carlo-simulation" }, { "name": "Real Options Pricing", "id": "chapter-04-financial-analysis-and-valuation-10-real-options-pricing", "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "chapterSlugs": [ "chapter-04-financial-analysis-and-valuation" ], "aliases": [], "concepts": [ "DCF", "valuation", "capital structure", "unit economics", "financial ratios", "comparable companies", "precedent transactions", "football field valuation" ], "description": "Real Options Pricing Valuing Strategic Flexibility 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] 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.,", "sourceIds": [ "BB-C04-S10" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-04-financial-analysis-and-valuation-10-real-options-pricing" ], "url": "index.html#chapter-04-financial-analysis-and-valuation-10-real-options-pricing" }, { "name": "Customer Journey Mapping", "id": "chapter-05-marketing-and-customer-analytics-1-customer-journey-mapping", "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "chapterSlugs": [ "chapter-05-marketing-and-customer-analytics" ], "aliases": [], "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "description": "Customer Journey Mapping Experience Design & Diagnosis 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] 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: Outlin", "sourceIds": [ "BB-C05-S11" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-05-marketing-and-customer-analytics-1-customer-journey-mapping" ], "url": "index.html#chapter-05-marketing-and-customer-analytics-1-customer-journey-mapping" }, { "name": "Jobs-to-be-Done (JTBD)", "id": "chapter-05-marketing-and-customer-analytics-2-jobs-to-be-done-jtbd", "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "chapterSlugs": [ "chapter-05-marketing-and-customer-analytics" ], "aliases": [ "JTBD" ], "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "description": "Jobs-to-be-Done (JTBD) Understanding Customer Motivation 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] 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, al", "sourceIds": [ "BB-C05-S12", "BB-C05-S13" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-05-marketing-and-customer-analytics-2-jobs-to-be-done-jtbd" ], "url": "index.html#chapter-05-marketing-and-customer-analytics-2-jobs-to-be-done-jtbd" }, { "name": "RFM Segmentation", "id": "chapter-05-marketing-and-customer-analytics-3-rfm-segmentation", "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "chapterSlugs": [ "chapter-05-marketing-and-customer-analytics" ], "aliases": [ "RFM" ], "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "description": "RFM (Recency, Frequency, Monetary) Segmentation Customer Segmentation 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] 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. Combi", "sourceIds": [ "BB-C05-S14" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-05-marketing-and-customer-analytics-3-rfm-segmentation" ], "url": "index.html#chapter-05-marketing-and-customer-analytics-3-rfm-segmentation" }, { "name": "CLV/CAC Analysis", "id": "chapter-05-marketing-and-customer-analytics-4-clv-cac-analysis", "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "chapterSlugs": [ "chapter-05-marketing-and-customer-analytics" ], "aliases": [ "CLV/CAC" ], "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "description": "CLV/CAC Analysis Unit Economics 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] 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: ", "sourceIds": [ "BB-C05-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-05-marketing-and-customer-analytics-4-clv-cac-analysis" ], "url": "index.html#chapter-05-marketing-and-customer-analytics-4-clv-cac-analysis" }, { "name": "Marketing Attribution Models", "id": "chapter-05-marketing-and-customer-analytics-5-marketing-attribution-models", "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "chapterSlugs": [ "chapter-05-marketing-and-customer-analytics" ], "aliases": [], "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "description": "Marketing Attribution Models ROI Measurement 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] 1. Understand the Models: Last-Click: Gi", "sourceIds": [ "BB-C05-S15", "BB-C05-S16" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-05-marketing-and-customer-analytics-5-marketing-attribution-models" ], "url": "index.html#chapter-05-marketing-and-customer-analytics-5-marketing-attribution-models" }, { "name": "Pricing Strategy & Models", "id": "chapter-05-marketing-and-customer-analytics-6-pricing-strategy-models", "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "chapterSlugs": [ "chapter-05-marketing-and-customer-analytics" ], "aliases": [], "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "description": "Pricing Strategy & Models Value Capture 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] 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 gov", "sourceIds": [ "BB-C05-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-05-marketing-and-customer-analytics-6-pricing-strategy-models" ], "url": "index.html#chapter-05-marketing-and-customer-analytics-6-pricing-strategy-models" }, { "name": "Brand Architecture", "id": "chapter-05-marketing-and-customer-analytics-7-brand-architecture", "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "chapterSlugs": [ "chapter-05-marketing-and-customer-analytics" ], "aliases": [], "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "description": "Brand Architecture Portfolio & Brand Strategy 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] 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 inde", "sourceIds": [ "BB-C05-S09" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-05-marketing-and-customer-analytics-7-brand-architecture" ], "url": "index.html#chapter-05-marketing-and-customer-analytics-7-brand-architecture" }, { "name": "A/B Testing", "id": "chapter-05-marketing-and-customer-analytics-8-a-b-testing", "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "chapterSlugs": [ "chapter-05-marketing-and-customer-analytics" ], "aliases": [ "A/B" ], "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "description": "A/B Testing Experimentation & Optimization 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] 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; mon", "sourceIds": [ "BB-C05-S10" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-05-marketing-and-customer-analytics-8-a-b-testing" ], "url": "index.html#chapter-05-marketing-and-customer-analytics-8-a-b-testing" }, { "name": "NPS Driver Analysis", "id": "chapter-05-marketing-and-customer-analytics-9-nps-driver-analysis", "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "chapterSlugs": [ "chapter-05-marketing-and-customer-analytics" ], "aliases": [ "NPS" ], "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "description": "Net Promoter Score (NPS) Driver Analysis Loyalty Measurement & Diagnosis 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. 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 int", "sourceIds": [ "BB-C05-S02", "BB-C05-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-05-marketing-and-customer-analytics-9-nps-driver-analysis" ], "url": "index.html#chapter-05-marketing-and-customer-analytics-9-nps-driver-analysis" }, { "name": "Cohort Analysis", "id": "chapter-05-marketing-and-customer-analytics-10-cohort-analysis", "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "chapterSlugs": [ "chapter-05-marketing-and-customer-analytics" ], "aliases": [], "concepts": [ "segmentation", "customer journey", "CLV", "CAC", "pricing", "marketing mix modeling", "incrementality", "brand equity" ], "description": "Cohort Analysis Retention Analysis 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] 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, Mont", "sourceIds": [ "BB-C05-S17" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-05-marketing-and-customer-analytics-10-cohort-analysis" ], "url": "index.html#chapter-05-marketing-and-customer-analytics-10-cohort-analysis" }, { "name": "Process Flow Diagrams", "id": "chapter-06-operations-and-supply-chain-1-process-flow-diagrams", "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "chapterSlugs": [ "chapter-06-operations-and-supply-chain" ], "aliases": [], "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "description": "Process Flow Diagramming Process Visualization 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 equi", "sourceIds": [ "BB-C06-S11" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-06-operations-and-supply-chain-1-process-flow-diagrams" ], "url": "index.html#chapter-06-operations-and-supply-chain-1-process-flow-diagrams" }, { "name": "Lean & The 8 Wastes", "id": "chapter-06-operations-and-supply-chain-2-lean-the-8-wastes", "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "chapterSlugs": [ "chapter-06-operations-and-supply-chain" ], "aliases": [], "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "description": "Lean & The 8 Wastes (TIMWOODS) Waste Elimination 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] Table 6.1. TIMWOODS investigation prompts. These categories identify places to investigate; they do not authorize removal without customer, safety, quality, resilience, labor, acc", "sourceIds": [ "BB-C06-S01", "BB-C06-S02", "BB-C06-S05", "BB-C06-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-06-operations-and-supply-chain-2-lean-the-8-wastes" ], "url": "index.html#chapter-06-operations-and-supply-chain-2-lean-the-8-wastes" }, { "name": "Six Sigma (DMAIC Cycle)", "id": "chapter-06-operations-and-supply-chain-3-six-sigma-dmaic-cycle", "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "chapterSlugs": [ "chapter-06-operations-and-supply-chain" ], "aliases": [ "DMAIC", "DMAIC Cycle" ], "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "description": "Six Sigma (DMAIC Cycle) Data-Driven Quality Improvement 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] 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 comp", "sourceIds": [ "BB-C06-S06", "BB-C06-S09" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-06-operations-and-supply-chain-3-six-sigma-dmaic-cycle" ], "url": "index.html#chapter-06-operations-and-supply-chain-3-six-sigma-dmaic-cycle" }, { "name": "Theory of Constraints (TOC)", "id": "chapter-06-operations-and-supply-chain-4-theory-of-constraints-toc", "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "chapterSlugs": [ "chapter-06-operations-and-supply-chain" ], "aliases": [ "TOC" ], "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "description": "Theory of Constraints (TOC) Bottleneck Management 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] Figure 6.4. Constructed five-step capacity line. Under one product, one route, qualified output, ", "sourceIds": [ "BB-C06-S03", "BB-C06-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-06-operations-and-supply-chain-4-theory-of-constraints-toc" ], "url": "index.html#chapter-06-operations-and-supply-chain-4-theory-of-constraints-toc" }, { "name": "Inventory Management Models", "id": "chapter-06-operations-and-supply-chain-5-inventory-management-models", "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "chapterSlugs": [ "chapter-06-operations-and-supply-chain" ], "aliases": [], "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "description": "Inventory Management Models (EOQ vs. JIT) Stock Optimization 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. 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 equival", "sourceIds": [ "BB-C06-S01", "BB-C06-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-06-operations-and-supply-chain-5-inventory-management-models" ], "url": "index.html#chapter-06-operations-and-supply-chain-5-inventory-management-models" }, { "name": "Supply Chain Risk Matrix", "id": "chapter-06-operations-and-supply-chain-6-supply-chain-risk-matrix", "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "chapterSlugs": [ "chapter-06-operations-and-supply-chain" ], "aliases": [], "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "description": "Supply Chain Risk Matrix Resilience Planning 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-i", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-06-operations-and-supply-chain-6-supply-chain-risk-matrix" ], "url": "index.html#chapter-06-operations-and-supply-chain-6-supply-chain-risk-matrix" }, { "name": "Capacity Planning Model", "id": "chapter-06-operations-and-supply-chain-7-capacity-planning-model", "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "chapterSlugs": [ "chapter-06-operations-and-supply-chain" ], "aliases": [], "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "description": "Capacity Planning Resource Allocation 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] 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] T", "sourceIds": [ "BB-C06-S08", "BB-C06-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-06-operations-and-supply-chain-7-capacity-planning-model" ], "url": "index.html#chapter-06-operations-and-supply-chain-7-capacity-planning-model" }, { "name": "Statistical Process Control (SPC) Charts", "id": "chapter-06-operations-and-supply-chain-8-statistical-process-control-spc-charts", "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "chapterSlugs": [ "chapter-06-operations-and-supply-chain" ], "aliases": [ "SPC" ], "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "description": "Statistical Process Control (SPC) Quality Monitoring 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] 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 equivalen", "sourceIds": [ "BB-C06-S09" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-06-operations-and-supply-chain-8-statistical-process-control-spc-charts" ], "url": "index.html#chapter-06-operations-and-supply-chain-8-statistical-process-control-spc-charts" }, { "name": "Value Stream Mapping", "id": "chapter-06-operations-and-supply-chain-9-value-stream-mapping", "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "chapterSlugs": [ "chapter-06-operations-and-supply-chain" ], "aliases": [], "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "description": "Value Stream Mapping (VSM) End-to-End Process Optimization 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] 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, stat", "sourceIds": [ "BB-C06-S10", "BB-C06-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-06-operations-and-supply-chain-9-value-stream-mapping" ], "url": "index.html#chapter-06-operations-and-supply-chain-9-value-stream-mapping" }, { "name": "Digital Twin Architecture", "id": "chapter-06-operations-and-supply-chain-10-digital-twin-architecture", "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "chapterSlugs": [ "chapter-06-operations-and-supply-chain" ], "aliases": [], "concepts": [ "lean", "Six Sigma", "theory of constraints", "supply chain risk", "capacity planning", "forecast accuracy", "sales and operations planning" ], "description": "Digital Twin Architecture Simulation & Predictive Optimization 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] Figure 6.12. Constructed digital-twin component arch", "sourceIds": [ "BB-C06-S12" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-06-operations-and-supply-chain-10-digital-twin-architecture" ], "url": "index.html#chapter-06-operations-and-supply-chain-10-digital-twin-architecture" }, { "name": "Kotter's 8-Step Change Management Model", "id": "chapter-07-organizational-behavior-and-leadership-1-kotter-s-8-step-change-management-model", "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "chapterSlugs": [ "chapter-07-organizational-behavior-and-leadership" ], "aliases": [], "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "description": "Kotter's 8-Step Model for Change Leading Transformation 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] 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 wh", "sourceIds": [ "BB-C07-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-07-organizational-behavior-and-leadership-1-kotter-s-8-step-change-management-model" ], "url": "index.html#chapter-07-organizational-behavior-and-leadership-1-kotter-s-8-step-change-management-model" }, { "name": "Leadership Styles & Radical Candor", "id": "chapter-07-organizational-behavior-and-leadership-2-leadership-styles-radical-candor", "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "chapterSlugs": [ "chapter-07-organizational-behavior-and-leadership" ], "aliases": [], "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "description": "Leadership Styles & Radical Candor Effective Communication 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. 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 escala", "sourceIds": [ "BB-C07-S02", "BB-C07-S16" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-07-organizational-behavior-and-leadership-2-leadership-styles-radical-candor" ], "url": "index.html#chapter-07-organizational-behavior-and-leadership-2-leadership-styles-radical-candor" }, { "name": "Lencioni's Five Dysfunctions of a Team", "id": "chapter-07-organizational-behavior-and-leadership-3-lencioni-s-five-dysfunctions-of-a-team", "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "chapterSlugs": [ "chapter-07-organizational-behavior-and-leadership" ], "aliases": [], "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "description": "Lencioni's Five Dysfunctions of a Team Team Health Diagnostic 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] 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 eviden", "sourceIds": [ "BB-C07-S07", "BB-C07-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-07-organizational-behavior-and-leadership-3-lencioni-s-five-dysfunctions-of-a-team" ], "url": "index.html#chapter-07-organizational-behavior-and-leadership-3-lencioni-s-five-dysfunctions-of-a-team" }, { "name": "Stakeholder Mapping Grid", "id": "chapter-07-organizational-behavior-and-leadership-4-stakeholder-mapping-grid", "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "chapterSlugs": [ "chapter-07-organizational-behavior-and-leadership" ], "aliases": [], "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "description": "Stakeholder Mapping Grid Influence & Communication Strategy 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] 1. List Stakeholders: Brainstorm every individual or group affected by your project. 2. Assess Power and Interest: For each stakeholder, rate their ", "sourceIds": [ "BB-C07-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-07-organizational-behavior-and-leadership-4-stakeholder-mapping-grid" ], "url": "index.html#chapter-07-organizational-behavior-and-leadership-4-stakeholder-mapping-grid" }, { "name": "Competing Values Framework (Culture Assessment)", "id": "chapter-07-organizational-behavior-and-leadership-5-competing-values-framework-culture-assessment", "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "chapterSlugs": [ "chapter-07-organizational-behavior-and-leadership" ], "aliases": [ "Culture Assessment" ], "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "description": "Competing Values Framework (Culture) Organizational Diagnosis 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] 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 inn", "sourceIds": [ "BB-C07-S09", "BB-C07-S10" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-07-organizational-behavior-and-leadership-5-competing-values-framework-culture-assessment" ], "url": "index.html#chapter-07-organizational-behavior-and-leadership-5-competing-values-framework-culture-assessment" }, { "name": "Talent 9-Box Grid", "id": "chapter-07-organizational-behavior-and-leadership-6-talent-9-box-grid", "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "chapterSlugs": [ "chapter-07-organizational-behavior-and-leadership" ], "aliases": [], "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "description": "Talent 9-Box Grid Talent Management & Succession 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] 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 futur", "sourceIds": [ "BB-C07-S05", "BB-C07-S17" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-07-organizational-behavior-and-leadership-6-talent-9-box-grid" ], "url": "index.html#chapter-07-organizational-behavior-and-leadership-6-talent-9-box-grid" }, { "name": "Motivation Theory Comparison", "id": "chapter-07-organizational-behavior-and-leadership-7-motivation-theory-comparison", "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "chapterSlugs": [ "chapter-07-organizational-behavior-and-leadership" ], "aliases": [], "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "description": "Motivation Theories (Herzberg & Pink) Employee Engagement 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] 1. Separate Hygiene from Motivation (Herzberg): Hygiene Factors: In the theory, factors such as s", "sourceIds": [ "BB-C07-S03", "BB-C07-S18", "BB-C07-S19" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-07-organizational-behavior-and-leadership-7-motivation-theory-comparison" ], "url": "index.html#chapter-07-organizational-behavior-and-leadership-7-motivation-theory-comparison" }, { "name": "Conflict-Mode Reflection Map", "id": "chapter-07-organizational-behavior-and-leadership-8-conflict-mode-reflection-map", "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "chapterSlugs": [ "chapter-07-organizational-behavior-and-leadership" ], "aliases": [], "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "description": "Conflict-Mode Reflection Map Constructive Disagreement 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. 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 Cooperative", "sourceIds": [ "BB-C07-S20" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-07-organizational-behavior-and-leadership-8-conflict-mode-reflection-map" ], "url": "index.html#chapter-07-organizational-behavior-and-leadership-8-conflict-mode-reflection-map" }, { "name": "Organizational Design Patterns", "id": "chapter-07-organizational-behavior-and-leadership-9-organizational-design-patterns", "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "chapterSlugs": [ "chapter-07-organizational-behavior-and-leadership" ], "aliases": [], "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "description": "Organizational Design Patterns Structuring for Success 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] 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: Grou", "sourceIds": [ "BB-C07-S11", "BB-C07-S12" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-07-organizational-behavior-and-leadership-9-organizational-design-patterns" ], "url": "index.html#chapter-07-organizational-behavior-and-leadership-9-organizational-design-patterns" }, { "name": "Psychological Safety Assessment", "id": "chapter-07-organizational-behavior-and-leadership-10-psychological-safety-assessment", "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "chapterSlugs": [ "chapter-07-organizational-behavior-and-leadership" ], "aliases": [], "concepts": [ "leadership", "culture", "change management", "psychological safety", "team dynamics", "BATNA", "reservation value", "ZOPA", "multiparty negotiation" ], "description": "Psychological Safety Speaking Up, Learning, and Accountability 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] 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: St", "sourceIds": [ "BB-C07-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-07-organizational-behavior-and-leadership-10-psychological-safety-assessment" ], "url": "index.html#chapter-07-organizational-behavior-and-leadership-10-psychological-safety-assessment" }, { "name": "Mission, Vision, and Values as Strategic Inputs", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-1-mission-vision-and-values-as-strategic-inputs", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "chapterSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "aliases": [], "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "description": "Mission, Vision, and Values as Strategic Inputs Purpose and Commitments 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] 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 eve", "sourceIds": [ "BB-C08-S04", "BB-C08-S05", "BB-C08-S06", "BB-C08-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-1-mission-vision-and-values-as-strategic-inputs" ], "url": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-1-mission-vision-and-values-as-strategic-inputs" }, { "name": "Evidence-Based Goal Setting (SMART & FAST)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-2-evidence-based-goal-setting-smart-fast", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "chapterSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "aliases": [ "FAST", "SMART", "SMART & FAST" ], "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "description": "Evidence-Based Goal Setting Effective Target Definition 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 motivati", "sourceIds": [ "BB-C08-S07", "BB-C08-S09", "BB-C08-S10", "BB-C08-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-2-evidence-based-goal-setting-smart-fast" ], "url": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-2-evidence-based-goal-setting-smart-fast" }, { "name": "\"Good Strategy / Bad Strategy\" (Rumelt's Kernel)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-3-good-strategy-bad-strategy-rumelt-s-kernel", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "chapterSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "aliases": [ "Rumelt's Kernel" ], "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "description": "Good Strategy / Bad Strategy The Kernel of Strategy 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] 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 w", "sourceIds": [ "BB-C08-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-3-good-strategy-bad-strategy-rumelt-s-kernel" ], "url": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-3-good-strategy-bad-strategy-rumelt-s-kernel" }, { "name": "Objectives and Key Results (OKRs)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-4-objectives-and-key-results-okrs", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "chapterSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "aliases": [ "OKRs" ], "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "description": "Objectives and Key Results (OKRs) Agile Strategy Execution 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] 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. Result", "sourceIds": [ "BB-C08-S01", "BB-C08-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-4-objectives-and-key-results-okrs" ], "url": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-4-objectives-and-key-results-okrs" }, { "name": "Key Performance Indicators (KPIs) vs. OKRs", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-5-key-performance-indicators-kpis-vs-okrs", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "chapterSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "aliases": [ "KPIs" ], "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "description": "KPIs vs. OKRs Measurement for Clarity 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. 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", "sourceIds": [ "BB-C08-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-5-key-performance-indicators-kpis-vs-okrs" ], "url": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-5-key-performance-indicators-kpis-vs-okrs" }, { "name": "The Balanced Scorecard (BSC)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-6-the-balanced-scorecard-bsc", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "chapterSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "aliases": [ "BSC" ], "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "description": "The Balanced Scorecard (BSC) Holistic Performance Management 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] 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 o", "sourceIds": [ "BB-C08-S03", "BB-C08-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-6-the-balanced-scorecard-bsc" ], "url": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-6-the-balanced-scorecard-bsc" }, { "name": "The Hedgehog Concept (Jim Collins)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-7-the-hedgehog-concept-jim-collins", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "chapterSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "aliases": [ "Jim Collins" ], "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "description": "The Hedgehog Concept Finding Your Strategic Focus 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. The three prompts b", "sourceIds": [ "BB-C08-S11", "BB-C08-S12" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-7-the-hedgehog-concept-jim-collins" ], "url": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-7-the-hedgehog-concept-jim-collins" }, { "name": "The VSEM Framework (Vision, Strategy, Execution, Metrics)", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-8-the-vsem-framework-vision-strategy-execution-metrics", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "chapterSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "aliases": [ "Vision, Strategy, Execution, Metrics", "VSEM" ], "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "description": "The VSEM Framework Integrated Execution Model 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. 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 unintende", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-8-the-vsem-framework-vision-strategy-execution-metrics" ], "url": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-8-the-vsem-framework-vision-strategy-execution-metrics" }, { "name": "Goal Cascading & Alignment Models", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-9-goal-cascading-alignment-models", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "chapterSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "aliases": [], "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "description": "Goal Cascading & Alignment Organizational Alignment 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. 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 alignm", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-9-goal-cascading-alignment-models" ], "url": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-9-goal-cascading-alignment-models" }, { "name": "Contrarian Thinking: The Case Against Mission Statements", "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-10-contrarian-thinking-the-case-against-mission-statements", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "chapterSlugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "aliases": [], "concepts": [ "OKRs", "KPIs", "balanced scorecard", "mission", "strategy execution" ], "description": "Contrarian View: Against Mission Statements Critique & Alternative 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. 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 s", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-10-contrarian-thinking-the-case-against-mission-statements" ], "url": "index.html#chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-10-contrarian-thinking-the-case-against-mission-statements" }, { "name": "Issue Tree Templates", "id": "chapter-09-problem-structuring-1-issue-tree-templates", "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "chapterSlugs": [ "chapter-09-problem-structuring" ], "aliases": [], "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "description": "Issue Trees Problem Decomposition 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. 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 ", "sourceIds": [ "BB-C09-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-09-problem-structuring-1-issue-tree-templates" ], "url": "index.html#chapter-09-problem-structuring-1-issue-tree-templates" }, { "name": "The MECE Principle", "id": "chapter-09-problem-structuring-2-the-mece-principle", "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "chapterSlugs": [ "chapter-09-problem-structuring" ], "aliases": [ "MECE" ], "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "description": "MECE Principle Analytical Rigor 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. For any set of categories in your analysis, apply two tests: 1. The \"No Overlap\" Test (ME): Cou", "sourceIds": [ "BB-C09-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-09-problem-structuring-2-the-mece-principle" ], "url": "index.html#chapter-09-problem-structuring-2-the-mece-principle" }, { "name": "Hypothesis Pyramid Structure", "id": "chapter-09-problem-structuring-3-hypothesis-pyramid-structure", "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "chapterSlugs": [ "chapter-09-problem-structuring" ], "aliases": [], "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "description": "The Hypothesis Pyramid Building a Defensible Argument 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. 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 al", "sourceIds": [ "BB-C09-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-09-problem-structuring-3-hypothesis-pyramid-structure" ], "url": "index.html#chapter-09-problem-structuring-3-hypothesis-pyramid-structure" }, { "name": "First Principles Thinking & The 5 Whys", "id": "chapter-09-problem-structuring-4-first-principles-thinking-the-5-whys", "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "chapterSlugs": [ "chapter-09-problem-structuring" ], "aliases": [], "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "description": "First Principles & The 5 Whys Root Cause Analysis 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] 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 e", "sourceIds": [ "BB-C09-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-09-problem-structuring-4-first-principles-thinking-the-5-whys" ], "url": "index.html#chapter-09-problem-structuring-4-first-principles-thinking-the-5-whys" }, { "name": "Logic Tree Construction", "id": "chapter-09-problem-structuring-5-logic-tree-construction", "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "chapterSlugs": [ "chapter-09-problem-structuring" ], "aliases": [], "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "description": "Logic Trees Building Arguments 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. 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 R", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-09-problem-structuring-5-logic-tree-construction" ], "url": "index.html#chapter-09-problem-structuring-5-logic-tree-construction" }, { "name": "Problem Statement Canvas", "id": "chapter-09-problem-structuring-6-problem-statement-canvas", "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "chapterSlugs": [ "chapter-09-problem-structuring" ], "aliases": [], "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "description": "Problem Statement Canvas Defining the Problem 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. 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 evid", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-09-problem-structuring-6-problem-statement-canvas" ], "url": "index.html#chapter-09-problem-structuring-6-problem-statement-canvas" }, { "name": "Prioritization Matrices", "id": "chapter-09-problem-structuring-7-prioritization-matrices", "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "chapterSlugs": [ "chapter-09-problem-structuring" ], "aliases": [], "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "description": "Prioritization Matrices Deciding What to Do First 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. 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 i", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-09-problem-structuring-7-prioritization-matrices" ], "url": "index.html#chapter-09-problem-structuring-7-prioritization-matrices" }, { "name": "Risk Assessment Framework", "id": "chapter-09-problem-structuring-8-risk-assessment-framework", "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "chapterSlugs": [ "chapter-09-problem-structuring" ], "aliases": [], "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "description": "Risk Assessment Matrix Anticipating Obstacles 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 a", "sourceIds": [ "BB-C09-S06", "BB-C09-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-09-problem-structuring-8-risk-assessment-framework" ], "url": "index.html#chapter-09-problem-structuring-8-risk-assessment-framework" }, { "name": "Decision Criteria Weighting Model", "id": "chapter-09-problem-structuring-9-decision-criteria-weighting-model", "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "chapterSlugs": [ "chapter-09-problem-structuring" ], "aliases": [], "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "description": "Decision Criteria Weighting Transparent Trade-offs 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. 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-cou", "sourceIds": [ "BB-C09-S05", "BB-C22-S11", "BB-C22-S12" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-09-problem-structuring-9-decision-criteria-weighting-model" ], "url": "index.html#chapter-09-problem-structuring-9-decision-criteria-weighting-model" }, { "name": "Assumption Mapping", "id": "chapter-09-problem-structuring-10-assumption-mapping", "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "chapterSlugs": [ "chapter-09-problem-structuring" ], "aliases": [], "concepts": [ "MECE", "issue trees", "hypothesis pyramid", "logic trees", "prioritization", "decision trees", "value of information" ], "description": "Assumption Mapping Testing What You Don't Know 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. 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: ", "sourceIds": [ "BB-C09-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-09-problem-structuring-10-assumption-mapping" ], "url": "index.html#chapter-09-problem-structuring-10-assumption-mapping" }, { "name": "New Business Unit Launch Framework (Integrated)", "id": "chapter-10-advanced-consulting-frameworks-and-integration-1-new-business-unit-launch-framework-integrated", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "chapterSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "aliases": [ "Integrated" ], "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "description": "New Business Unit Launch Framework Integrated Corporate Venture Playbook 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. 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", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-10-advanced-consulting-frameworks-and-integration-1-new-business-unit-launch-framework-integrated" ], "url": "index.html#chapter-10-advanced-consulting-frameworks-and-integration-1-new-business-unit-launch-framework-integrated" }, { "name": "McKinsey 7S Framework", "id": "chapter-10-advanced-consulting-frameworks-and-integration-2-mckinsey-7s-framework", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "chapterSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "aliases": [], "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "description": "McKinsey 7S Framework Organizational Alignment Diagnostic 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. The seven elements are divided into \"Hard S's\" (easy for management to define) and \"Soft S's\" (harder to change, more cul", "sourceIds": [ "BB-C10-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-10-advanced-consulting-frameworks-and-integration-2-mckinsey-7s-framework" ], "url": "index.html#chapter-10-advanced-consulting-frameworks-and-integration-2-mckinsey-7s-framework" }, { "name": "Competitive-Advantage Context Check", "id": "chapter-10-advanced-consulting-frameworks-and-integration-3-competitive-advantage-context-check", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "chapterSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "aliases": [], "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "description": "Competitive-Advantage Context Check Competitive Environment Analysis 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. 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, requ", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-10-advanced-consulting-frameworks-and-integration-3-competitive-advantage-context-check" ], "url": "index.html#chapter-10-advanced-consulting-frameworks-and-integration-3-competitive-advantage-context-check" }, { "name": "Bain's RAPID Decision Framework", "id": "chapter-10-advanced-consulting-frameworks-and-integration-4-bain-s-rapid-decision-framework", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "chapterSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "aliases": [ "RAPID" ], "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "description": "Bain's RAPID Decision Framework Clarifying Decision Rights 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. For a defined decision, map the roles only after verifying actual authority. Some roles m", "sourceIds": [ "BB-C10-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-10-advanced-consulting-frameworks-and-integration-4-bain-s-rapid-decision-framework" ], "url": "index.html#chapter-10-advanced-consulting-frameworks-and-integration-4-bain-s-rapid-decision-framework" }, { "name": "Value Chain Analysis (Digital Version)", "id": "chapter-10-advanced-consulting-frameworks-and-integration-5-value-chain-analysis-digital-version", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "chapterSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "aliases": [ "Digital Version" ], "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "description": "Value Chain Analysis Activity-Based Advantage 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 ", "sourceIds": [ "BB-C10-S02", "BB-C10-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-10-advanced-consulting-frameworks-and-integration-5-value-chain-analysis-digital-version" ], "url": "index.html#chapter-10-advanced-consulting-frameworks-and-integration-5-value-chain-analysis-digital-version" }, { "name": "Business Model Canvas", "id": "chapter-10-advanced-consulting-frameworks-and-integration-6-business-model-canvas", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "chapterSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "aliases": [], "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "description": "Business Model Canvas Business-Model Hypothesis Map 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] 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:", "sourceIds": [ "BB-C10-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-10-advanced-consulting-frameworks-and-integration-6-business-model-canvas" ], "url": "index.html#chapter-10-advanced-consulting-frameworks-and-integration-6-business-model-canvas" }, { "name": "Capability Development Ladder (Constructed)", "id": "chapter-10-advanced-consulting-frameworks-and-integration-7-capability-development-ladder-constructed", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "chapterSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "aliases": [ "Constructed" ], "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "description": "Capability Development Ladder Organizational Development 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. 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 ", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-10-advanced-consulting-frameworks-and-integration-7-capability-development-ladder-constructed" ], "url": "index.html#chapter-10-advanced-consulting-frameworks-and-integration-7-capability-development-ladder-constructed" }, { "name": "Digital Transformation Framework", "id": "chapter-10-advanced-consulting-frameworks-and-integration-8-digital-transformation-framework", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "chapterSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "aliases": [], "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "description": "Digital Transformation Framework Enterprise Modernization 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. 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 ).", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-10-advanced-consulting-frameworks-and-integration-8-digital-transformation-framework" ], "url": "index.html#chapter-10-advanced-consulting-frameworks-and-integration-8-digital-transformation-framework" }, { "name": "M&A Due Diligence Checklist", "id": "chapter-10-advanced-consulting-frameworks-and-integration-9-m-a-due-diligence-checklist", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "chapterSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "aliases": [ "M&A" ], "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "description": "M&A Due Diligence Checklist Merger & Acquisition Analysis 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 m", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-10-advanced-consulting-frameworks-and-integration-9-m-a-due-diligence-checklist" ], "url": "index.html#chapter-10-advanced-consulting-frameworks-and-integration-9-m-a-due-diligence-checklist" }, { "name": "Post-Merger Integration (PMI) Playbook", "id": "chapter-10-advanced-consulting-frameworks-and-integration-10-post-merger-integration-pmi-playbook", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "chapterSlugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "aliases": [ "PMI" ], "concepts": [ "McKinsey 7S", "RAPID", "value chain", "business model canvas", "M&A diligence", "post-merger integration", "digital transformation" ], "description": "Post-Merger Integration (PMI) Playbook M&A Execution 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. 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. Stabilizati", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-10-advanced-consulting-frameworks-and-integration-10-post-merger-integration-pmi-playbook" ], "url": "index.html#chapter-10-advanced-consulting-frameworks-and-integration-10-post-merger-integration-pmi-playbook" }, { "name": "Predictive Project-Management Process Groups", "id": "chapter-11-project-management-and-pmp-frameworks-1-predictive-project-management-process-groups", "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "chapterSlugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "aliases": [], "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "description": "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] 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", "sourceIds": [ "BB-C11-S01", "BB-C11-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-11-project-management-and-pmp-frameworks-1-predictive-project-management-process-groups" ], "url": "index.html#chapter-11-project-management-and-pmp-frameworks-1-predictive-project-management-process-groups" }, { "name": "Work Breakdown Structure (WBS)", "id": "chapter-11-project-management-and-pmp-frameworks-2-work-breakdown-structure-wbs", "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "chapterSlugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "aliases": [ "WBS" ], "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "description": "The Work Breakdown Structure (WBS) is a hierarchical, deliverable-oriented decomposition of the defined project scope into components and work packages. [BB-C11-S02] | 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 projec", "sourceIds": [ "BB-C11-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-11-project-management-and-pmp-frameworks-2-work-breakdown-structure-wbs" ], "url": "index.html#chapter-11-project-management-and-pmp-frameworks-2-work-breakdown-structure-wbs" }, { "name": "Critical Path Method (CPM) & Gantt Charts", "id": "chapter-11-project-management-and-pmp-frameworks-3-critical-path-method-cpm-gantt-charts", "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "chapterSlugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "aliases": [ "CPM" ], "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "description": "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] 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 ta", "sourceIds": [ "BB-C11-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-11-project-management-and-pmp-frameworks-3-critical-path-method-cpm-gantt-charts" ], "url": "index.html#chapter-11-project-management-and-pmp-frameworks-3-critical-path-method-cpm-gantt-charts" }, { "name": "Earned Value Management (EVM)", "id": "chapter-11-project-management-and-pmp-frameworks-4-earned-value-management-evm", "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "chapterSlugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "aliases": [ "EVM" ], "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "description": "Earned Value Management (EVM) integrates an authorized scope, schedule, and cost baseline to measure performance and support forecasting under stated assumptions. [BB-C11-S04] 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: 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 w", "sourceIds": [ "BB-C11-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-11-project-management-and-pmp-frameworks-4-earned-value-management-evm" ], "url": "index.html#chapter-11-project-management-and-pmp-frameworks-4-earned-value-management-evm" }, { "name": "Risk Management Framework", "id": "chapter-11-project-management-and-pmp-frameworks-5-risk-management-framework", "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "chapterSlugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "aliases": [], "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "description": "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] 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, p", "sourceIds": [ "BB-C11-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-11-project-management-and-pmp-frameworks-5-risk-management-framework" ], "url": "index.html#chapter-11-project-management-and-pmp-frameworks-5-risk-management-framework" }, { "name": "Stakeholder Management (PMBOK context; constructed categories)", "id": "chapter-11-project-management-and-pmp-frameworks-6-stakeholder-management-pmbok-context-constructed-categories", "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "chapterSlugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "aliases": [ "PMBOK", "PMBOK context; constructed categories" ], "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "description": "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] 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. Stakeholder Categories: - Internal: Team members, functional managers, executives, PMO - External: Customers, suppliers, regulators, community - Upward: Sponsor, ", "sourceIds": [ "BB-C11-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-11-project-management-and-pmp-frameworks-6-stakeholder-management-pmbok-context-constructed-categories" ], "url": "index.html#chapter-11-project-management-and-pmp-frameworks-6-stakeholder-management-pmbok-context-constructed-categories" }, { "name": "Agile/Scrum Framework", "id": "chapter-11-project-management-and-pmp-frameworks-7-agile-scrum-framework", "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "chapterSlugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "aliases": [], "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "description": "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] 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 Mast", "sourceIds": [ "BB-C11-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-11-project-management-and-pmp-frameworks-7-agile-scrum-framework" ], "url": "index.html#chapter-11-project-management-and-pmp-frameworks-7-agile-scrum-framework" }, { "name": "Flow Board and WIP Policy (Constructed)", "id": "chapter-11-project-management-and-pmp-frameworks-8-flow-board-and-wip-policy-constructed", "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "chapterSlugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "aliases": [ "Constructed", "WIP" ], "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "description": "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. 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. This section is a constructed flow-management aid, not a complete or certified presentation of the Kanban Method. A formal Kanban treatment needs an in", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-11-project-management-and-pmp-frameworks-8-flow-board-and-wip-policy-constructed" ], "url": "index.html#chapter-11-project-management-and-pmp-frameworks-8-flow-board-and-wip-policy-constructed" }, { "name": "Change Control Process", "id": "chapter-11-project-management-and-pmp-frameworks-9-change-control-process", "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "chapterSlugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "aliases": [], "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "description": "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. 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 (construct", "sourceIds": [ "BB-C11-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-11-project-management-and-pmp-frameworks-9-change-control-process" ], "url": "index.html#chapter-11-project-management-and-pmp-frameworks-9-change-control-process" }, { "name": "Project Charter Template", "id": "chapter-11-project-management-and-pmp-frameworks-10-project-charter-template", "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "chapterSlugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "aliases": [], "concepts": [ "project charter", "WBS", "critical path", "earned value", "flow management" ], "description": "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. 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. 1. Project Overview - Project Name: CRM Implementation Project - Project Manager: John Doe - Sponsor: Mary Johnson (VP Sal", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-11-project-management-and-pmp-frameworks-10-project-charter-template" ], "url": "index.html#chapter-11-project-management-and-pmp-frameworks-10-project-charter-template" }, { "name": "Stakeholder Influence/Interest Matrix", "id": "chapter-12-client-management-1-stakeholder-influence-interest-matrix", "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "chapterSlugs": [ "chapter-12-client-management" ], "aliases": [], "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "description": "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] 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,", "sourceIds": [ "BB-C12-S01", "BB-C12-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-12-client-management-1-stakeholder-influence-interest-matrix" ], "url": "index.html#chapter-12-client-management-1-stakeholder-influence-interest-matrix" }, { "name": "RACI Matrix", "id": "chapter-12-client-management-2-raci-matrix", "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "chapterSlugs": [ "chapter-12-client-management" ], "aliases": [ "RACI" ], "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "description": "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] 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 (", "sourceIds": [ "BB-C12-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-12-client-management-2-raci-matrix" ], "url": "index.html#chapter-12-client-management-2-raci-matrix" }, { "name": "Executive Presentation Structure", "id": "chapter-12-client-management-3-executive-presentation-structure", "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "chapterSlugs": [ "chapter-12-client-management" ], "aliases": [], "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "description": "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] 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 s", "sourceIds": [ "BB-C12-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-12-client-management-3-executive-presentation-structure" ], "url": "index.html#chapter-12-client-management-3-executive-presentation-structure" }, { "name": "Difficult Conversation Framework", "id": "chapter-12-client-management-4-difficult-conversation-framework", "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "chapterSlugs": [ "chapter-12-client-management" ], "aliases": [], "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "description": "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] 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, sec", "sourceIds": [ "BB-C12-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-12-client-management-4-difficult-conversation-framework" ], "url": "index.html#chapter-12-client-management-4-difficult-conversation-framework" }, { "name": "Project Scoping Template", "id": "chapter-12-client-management-5-project-scoping-template", "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "chapterSlugs": [ "chapter-12-client-management" ], "aliases": [], "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "description": "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] 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 ", "sourceIds": [ "BB-C12-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-12-client-management-5-project-scoping-template" ], "url": "index.html#chapter-12-client-management-5-project-scoping-template" }, { "name": "Statement of Work (SOW) Components", "id": "chapter-12-client-management-6-statement-of-work-sow-components", "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "chapterSlugs": [ "chapter-12-client-management" ], "aliases": [ "SOW" ], "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "description": "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] 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, inc", "sourceIds": [ "BB-C12-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-12-client-management-6-statement-of-work-sow-components" ], "url": "index.html#chapter-12-client-management-6-statement-of-work-sow-components" }, { "name": "Risk Register & Mitigation", "id": "chapter-12-client-management-7-risk-register-mitigation", "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "chapterSlugs": [ "chapter-12-client-management" ], "aliases": [], "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "description": "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] 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 sco", "sourceIds": [ "BB-C12-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-12-client-management-7-risk-register-mitigation" ], "url": "index.html#chapter-12-client-management-7-risk-register-mitigation" }, { "name": "Change Request Process", "id": "chapter-12-client-management-8-change-request-process", "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "chapterSlugs": [ "chapter-12-client-management" ], "aliases": [], "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "description": "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] 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: - Who: Client stakeholder - Format: Simple form: \"What change, why needed, impact if not done?\" - Trig", "sourceIds": [ "BB-C12-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-12-client-management-8-change-request-process" ], "url": "index.html#chapter-12-client-management-8-change-request-process" }, { "name": "Feedback Collection Methods", "id": "chapter-12-client-management-9-feedback-collection-methods", "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "chapterSlugs": [ "chapter-12-client-management" ], "aliases": [], "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "description": "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. 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, ", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-12-client-management-9-feedback-collection-methods" ], "url": "index.html#chapter-12-client-management-9-feedback-collection-methods" }, { "name": "Relationship Mapping Tool", "id": "chapter-12-client-management-10-relationship-mapping-tool", "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "chapterSlugs": [ "chapter-12-client-management" ], "aliases": [], "concepts": [ "stakeholder management", "RACI", "executive communication", "project scoping", "feedback", "client negotiation", "multiparty negotiation" ], "description": "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. 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 hy", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-12-client-management-10-relationship-mapping-tool" ], "url": "index.html#chapter-12-client-management-10-relationship-mapping-tool" }, { "name": "Lean Startup Cycle", "id": "chapter-13-startup-foundations-1-lean-startup-cycle", "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "chapterSlugs": [ "chapter-13-startup-foundations" ], "aliases": [], "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "description": "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] 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 curren", "sourceIds": [ "BB-C13-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-13-startup-foundations-1-lean-startup-cycle" ], "url": "index.html#chapter-13-startup-foundations-1-lean-startup-cycle" }, { "name": "Customer Development", "id": "chapter-13-startup-foundations-2-customer-development", "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "chapterSlugs": [ "chapter-13-startup-foundations" ], "aliases": [], "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "description": "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] 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 ", "sourceIds": [ "BB-C13-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-13-startup-foundations-2-customer-development" ], "url": "index.html#chapter-13-startup-foundations-2-customer-development" }, { "name": "MVP Definition Framework", "id": "chapter-13-startup-foundations-3-mvp-definition-framework", "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "chapterSlugs": [ "chapter-13-startup-foundations" ], "aliases": [ "MVP" ], "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "description": "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] 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 m", "sourceIds": [ "BB-C13-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-13-startup-foundations-3-mvp-definition-framework" ], "url": "index.html#chapter-13-startup-foundations-3-mvp-definition-framework" }, { "name": "Product-Market Fit Metrics", "id": "chapter-13-startup-foundations-4-product-market-fit-metrics", "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "chapterSlugs": [ "chapter-13-startup-foundations" ], "aliases": [], "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "description": "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] 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]?\" - ", "sourceIds": [ "BB-C13-S08", "BB-C13-S09" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-13-startup-foundations-4-product-market-fit-metrics" ], "url": "index.html#chapter-13-startup-foundations-4-product-market-fit-metrics" }, { "name": "Founder-Governance and Agreement Issues", "id": "chapter-13-startup-foundations-5-founder-governance-and-agreement-issues", "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "chapterSlugs": [ "chapter-13-startup-foundations" ], "aliases": [], "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "description": "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] 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, securiti", "sourceIds": [ "BB-C13-S04", "BB-C13-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-13-startup-foundations-5-founder-governance-and-agreement-issues" ], "url": "index.html#chapter-13-startup-foundations-5-founder-governance-and-agreement-issues" }, { "name": "Equity Distribution Model", "id": "chapter-13-startup-foundations-6-equity-distribution-model", "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "chapterSlugs": [ "chapter-13-startup-foundations" ], "aliases": [], "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "description": "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] 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 dil", "sourceIds": [ "BB-C13-S04", "BB-C13-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-13-startup-foundations-6-equity-distribution-model" ], "url": "index.html#chapter-13-startup-foundations-6-equity-distribution-model" }, { "name": "Burn Rate Calculator", "id": "chapter-13-startup-foundations-7-burn-rate-calculator", "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "chapterSlugs": [ "chapter-13-startup-foundations" ], "aliases": [], "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "description": "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. 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, ", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-13-startup-foundations-7-burn-rate-calculator" ], "url": "index.html#chapter-13-startup-foundations-7-burn-rate-calculator" }, { "name": "Runway Planning", "id": "chapter-13-startup-foundations-8-runway-planning", "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "chapterSlugs": [ "chapter-13-startup-foundations" ], "aliases": [], "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "description": "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. 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 misleadin", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-13-startup-foundations-8-runway-planning" ], "url": "index.html#chapter-13-startup-foundations-8-runway-planning" }, { "name": "Pivot Decision Framework", "id": "chapter-13-startup-foundations-9-pivot-decision-framework", "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "chapterSlugs": [ "chapter-13-startup-foundations" ], "aliases": [], "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "description": "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] 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-", "sourceIds": [ "BB-C13-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-13-startup-foundations-9-pivot-decision-framework" ], "url": "index.html#chapter-13-startup-foundations-9-pivot-decision-framework" }, { "name": "Scale-Up Readiness Checklist", "id": "chapter-13-startup-foundations-10-scale-up-readiness-checklist", "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "chapterSlugs": [ "chapter-13-startup-foundations" ], "aliases": [], "concepts": [ "product-market fit", "MVP", "customer discovery", "lean startup", "founder choices", "entrepreneurship through acquisition", "search fund", "acquisition screening" ], "description": "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. 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, technolog", "sourceIds": [ "BB-C13-S08", "BB-C13-S09" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-13-startup-foundations-10-scale-up-readiness-checklist" ], "url": "index.html#chapter-13-startup-foundations-10-scale-up-readiness-checklist" }, { "name": "GTM Strategy Canvas", "id": "chapter-14-go-to-market-strategy-1-gtm-strategy-canvas", "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "chapterSlugs": [ "chapter-14-go-to-market-strategy" ], "aliases": [ "GTM" ], "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "description": "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] 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,", "sourceIds": [ "BB-C14-S01", "BB-C14-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-14-go-to-market-strategy-1-gtm-strategy-canvas" ], "url": "index.html#chapter-14-go-to-market-strategy-1-gtm-strategy-canvas" }, { "name": "Ideal Customer Profile (ICP) Framework", "id": "chapter-14-go-to-market-strategy-2-ideal-customer-profile-icp-framework", "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "chapterSlugs": [ "chapter-14-go-to-market-strategy" ], "aliases": [ "ICP" ], "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "description": "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] 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 o", "sourceIds": [ "BB-C14-S03", "BB-C14-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-14-go-to-market-strategy-2-ideal-customer-profile-icp-framework" ], "url": "index.html#chapter-14-go-to-market-strategy-2-ideal-customer-profile-icp-framework" }, { "name": "Sales Funnel Metrics Dashboard", "id": "chapter-14-go-to-market-strategy-3-sales-funnel-metrics-dashboard", "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "chapterSlugs": [ "chapter-14-go-to-market-strategy" ], "aliases": [], "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "description": "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] 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,", "sourceIds": [ "BB-C14-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-14-go-to-market-strategy-3-sales-funnel-metrics-dashboard" ], "url": "index.html#chapter-14-go-to-market-strategy-3-sales-funnel-metrics-dashboard" }, { "name": "Channel Strategy Matrix", "id": "chapter-14-go-to-market-strategy-4-channel-strategy-matrix", "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "chapterSlugs": [ "chapter-14-go-to-market-strategy" ], "aliases": [], "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "description": "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] 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, investm", "sourceIds": [ "BB-C14-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-14-go-to-market-strategy-4-channel-strategy-matrix" ], "url": "index.html#chapter-14-go-to-market-strategy-4-channel-strategy-matrix" }, { "name": "Pricing Model Comparison", "id": "chapter-14-go-to-market-strategy-5-pricing-model-comparison", "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "chapterSlugs": [ "chapter-14-go-to-market-strategy" ], "aliases": [], "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "description": "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] 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, willingnes", "sourceIds": [ "BB-C14-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-14-go-to-market-strategy-5-pricing-model-comparison" ], "url": "index.html#chapter-14-go-to-market-strategy-5-pricing-model-comparison" }, { "name": "Product Launch Checklist", "id": "chapter-14-go-to-market-strategy-6-product-launch-checklist", "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "chapterSlugs": [ "chapter-14-go-to-market-strategy" ], "aliases": [], "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "description": "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. 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", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-14-go-to-market-strategy-6-product-launch-checklist" ], "url": "index.html#chapter-14-go-to-market-strategy-6-product-launch-checklist" }, { "name": "Growth Experimentation Framework", "id": "chapter-14-go-to-market-strategy-7-growth-experimentation-framework", "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "chapterSlugs": [ "chapter-14-go-to-market-strategy" ], "aliases": [], "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "description": "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] 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", "sourceIds": [ "BB-C14-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-14-go-to-market-strategy-7-growth-experimentation-framework" ], "url": "index.html#chapter-14-go-to-market-strategy-7-growth-experimentation-framework" }, { "name": "Product-mediated diffusion measure", "id": "chapter-14-go-to-market-strategy-8-product-mediated-diffusion-measure", "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "chapterSlugs": [ "chapter-14-go-to-market-strategy" ], "aliases": [], "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "description": "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] 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 d", "sourceIds": [ "BB-C14-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-14-go-to-market-strategy-8-product-mediated-diffusion-measure" ], "url": "index.html#chapter-14-go-to-market-strategy-8-product-mediated-diffusion-measure" }, { "name": "Partnership Evaluation Matrix", "id": "chapter-14-go-to-market-strategy-9-partnership-evaluation-matrix", "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "chapterSlugs": [ "chapter-14-go-to-market-strategy" ], "aliases": [], "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "description": "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. 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, w", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-14-go-to-market-strategy-9-partnership-evaluation-matrix" ], "url": "index.html#chapter-14-go-to-market-strategy-9-partnership-evaluation-matrix" }, { "name": "Market Entry Strategy Decision Tree", "id": "chapter-14-go-to-market-strategy-10-market-entry-strategy-decision-tree", "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "chapterSlugs": [ "chapter-14-go-to-market-strategy" ], "aliases": [], "concepts": [ "ICP", "positioning", "channels", "pricing", "sales funnel", "international market entry", "non-market strategy", "cross-border data", "sanctions compliance" ], "description": "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. 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 substitut", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-14-go-to-market-strategy-10-market-entry-strategy-decision-tree" ], "url": "index.html#chapter-14-go-to-market-strategy-10-market-entry-strategy-decision-tree" }, { "name": "Fundraising Process Timeline", "id": "chapter-15-fundraising-and-finance-1-fundraising-process-timeline", "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "chapterSlugs": [ "chapter-15-fundraising-and-finance" ], "aliases": [], "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "description": "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] 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", "sourceIds": [ "BB-C15-S06", "BB-C15-S07", "BB-C15-S14" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-15-fundraising-and-finance-1-fundraising-process-timeline" ], "url": "index.html#chapter-15-fundraising-and-finance-1-fundraising-process-timeline" }, { "name": "Pitch Deck Structure (Slide-by-Slide Guide)", "id": "chapter-15-fundraising-and-finance-2-pitch-deck-structure-slide-by-slide-guide", "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "chapterSlugs": [ "chapter-15-fundraising-and-finance" ], "aliases": [ "Slide-by-Slide Guide" ], "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "description": "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] 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 def", "sourceIds": [ "BB-C15-S01", "BB-C15-S02", "BB-C15-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-15-fundraising-and-finance-2-pitch-deck-structure-slide-by-slide-guide" ], "url": "index.html#chapter-15-fundraising-and-finance-2-pitch-deck-structure-slide-by-slide-guide" }, { "name": "Valuation Methods and Assumption Reconciliation", "id": "chapter-15-fundraising-and-finance-3-valuation-methods-and-assumption-reconciliation", "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "chapterSlugs": [ "chapter-15-fundraising-and-finance" ], "aliases": [], "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "description": "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] 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 a", "sourceIds": [ "BB-C15-S05", "BB-C15-S12", "BB-C15-S16" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-15-fundraising-and-finance-3-valuation-methods-and-assumption-reconciliation" ], "url": "index.html#chapter-15-fundraising-and-finance-3-valuation-methods-and-assumption-reconciliation" }, { "name": "Term Sheet Rights and Model Matrix", "id": "chapter-15-fundraising-and-finance-4-term-sheet-rights-and-model-matrix", "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "chapterSlugs": [ "chapter-15-fundraising-and-finance" ], "aliases": [], "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "description": "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] 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-fina", "sourceIds": [ "BB-C15-S08", "BB-C15-S09", "BB-C15-S10", "BB-C15-S11" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-15-fundraising-and-finance-4-term-sheet-rights-and-model-matrix" ], "url": "index.html#chapter-15-fundraising-and-finance-4-term-sheet-rights-and-model-matrix" }, { "name": "Cap Table Scenarios & Dilution", "id": "chapter-15-fundraising-and-finance-5-cap-table-scenarios-dilution", "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "chapterSlugs": [ "chapter-15-fundraising-and-finance" ], "aliases": [], "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "description": "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. 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 cont", "sourceIds": [ "BB-C15-S08", "BB-C15-S09", "BB-C15-S10", "BB-C15-S11", "BB-C15-S15" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-15-fundraising-and-finance-5-cap-table-scenarios-dilution" ], "url": "index.html#chapter-15-fundraising-and-finance-5-cap-table-scenarios-dilution" }, { "name": "Investor Evaluation Criteria", "id": "chapter-15-fundraising-and-finance-6-investor-evaluation-criteria", "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "chapterSlugs": [ "chapter-15-fundraising-and-finance" ], "aliases": [], "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "description": "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] 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. Purp", "sourceIds": [ "BB-C15-S02", "BB-C15-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-15-fundraising-and-finance-6-investor-evaluation-criteria" ], "url": "index.html#chapter-15-fundraising-and-finance-6-investor-evaluation-criteria" }, { "name": "Due Diligence Checklist (Sell-Side)", "id": "chapter-15-fundraising-and-finance-7-due-diligence-checklist-sell-side", "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "chapterSlugs": [ "chapter-15-fundraising-and-finance" ], "aliases": [ "Sell-Side" ], "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "description": "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. 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 di", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-15-fundraising-and-finance-7-due-diligence-checklist-sell-side" ], "url": "index.html#chapter-15-fundraising-and-finance-7-due-diligence-checklist-sell-side" }, { "name": "Financial Model Template (3-Statement)", "id": "chapter-15-fundraising-and-finance-8-financial-model-template-3-statement", "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "chapterSlugs": [ "chapter-15-fundraising-and-finance" ], "aliases": [ "3-Statement" ], "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "description": "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. 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, balanc", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-15-fundraising-and-finance-8-financial-model-template-3-statement" ], "url": "index.html#chapter-15-fundraising-and-finance-8-financial-model-template-3-statement" }, { "name": "Exit, Liquidity, and Continuation Options", "id": "chapter-15-fundraising-and-finance-9-exit-liquidity-and-continuation-options", "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "chapterSlugs": [ "chapter-15-fundraising-and-finance" ], "aliases": [], "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "description": "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] 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, o", "sourceIds": [ "BB-C15-S11" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-15-fundraising-and-finance-9-exit-liquidity-and-continuation-options" ], "url": "index.html#chapter-15-fundraising-and-finance-9-exit-liquidity-and-continuation-options" }, { "name": "SAFE and Convertible-Note Decision Boundary", "id": "chapter-15-fundraising-and-finance-10-safe-and-convertible-note-decision-boundary", "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "chapterSlugs": [ "chapter-15-fundraising-and-finance" ], "aliases": [ "SAFE" ], "concepts": [ "venture capital", "valuation", "dilution", "term sheets", "capital planning", "acquisition financing", "quality of earnings", "debt service coverage ratio", "sources and uses", "acquisition transition" ], "description": "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] 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 instrume", "sourceIds": [ "BB-C15-S13" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-15-fundraising-and-finance-10-safe-and-convertible-note-decision-boundary" ], "url": "index.html#chapter-15-fundraising-and-finance-10-safe-and-convertible-note-decision-boundary" }, { "name": "AI Opportunity Assessment Matrix", "id": "chapter-16-ai-strategy-and-data-driven-decisions-1-ai-opportunity-assessment-matrix", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "chapterSlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "aliases": [ "AI" ], "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "description": "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. 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 sc", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-16-ai-strategy-and-data-driven-decisions-1-ai-opportunity-assessment-matrix" ], "url": "index.html#chapter-16-ai-strategy-and-data-driven-decisions-1-ai-opportunity-assessment-matrix" }, { "name": "Build vs. Buy vs. Partner Decision Tree", "id": "chapter-16-ai-strategy-and-data-driven-decisions-2-build-vs-buy-vs-partner-decision-tree", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "chapterSlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "aliases": [], "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "description": "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. 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-r", "sourceIds": [ "BB-C16-S01", "BB-C16-S06", "BB-C16-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-16-ai-strategy-and-data-driven-decisions-2-build-vs-buy-vs-partner-decision-tree" ], "url": "index.html#chapter-16-ai-strategy-and-data-driven-decisions-2-build-vs-buy-vs-partner-decision-tree" }, { "name": "AI Maturity Model", "id": "chapter-16-ai-strategy-and-data-driven-decisions-3-ai-maturity-model", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "chapterSlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "aliases": [ "AI" ], "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "description": "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. 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 sho", "sourceIds": [ "BB-C16-S03", "BB-C16-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-16-ai-strategy-and-data-driven-decisions-3-ai-maturity-model" ], "url": "index.html#chapter-16-ai-strategy-and-data-driven-decisions-3-ai-maturity-model" }, { "name": "Use Case Prioritization Framework", "id": "chapter-16-ai-strategy-and-data-driven-decisions-4-use-case-prioritization-framework", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "chapterSlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "aliases": [], "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "description": "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. 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, no", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-16-ai-strategy-and-data-driven-decisions-4-use-case-prioritization-framework" ], "url": "index.html#chapter-16-ai-strategy-and-data-driven-decisions-4-use-case-prioritization-framework" }, { "name": "ROI Calculation for AI Projects", "id": "chapter-16-ai-strategy-and-data-driven-decisions-5-roi-calculation-for-ai-projects", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "chapterSlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "aliases": [ "AI", "ROI" ], "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "description": "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. 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 organizati", "sourceIds": [ "BB-C16-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-16-ai-strategy-and-data-driven-decisions-5-roi-calculation-for-ai-projects" ], "url": "index.html#chapter-16-ai-strategy-and-data-driven-decisions-5-roi-calculation-for-ai-projects" }, { "name": "Ethical AI Framework", "id": "chapter-16-ai-strategy-and-data-driven-decisions-6-ethical-ai-framework", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "chapterSlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "aliases": [ "AI" ], "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "description": "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. 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 A", "sourceIds": [ "BB-C16-S01", "BB-C16-S02", "BB-C16-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-16-ai-strategy-and-data-driven-decisions-6-ethical-ai-framework" ], "url": "index.html#chapter-16-ai-strategy-and-data-driven-decisions-6-ethical-ai-framework" }, { "name": "Data Readiness Assessment", "id": "chapter-16-ai-strategy-and-data-driven-decisions-7-data-readiness-assessment", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "chapterSlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "aliases": [], "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "description": "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. 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 ", "sourceIds": [ "BB-C16-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-16-ai-strategy-and-data-driven-decisions-7-data-readiness-assessment" ], "url": "index.html#chapter-16-ai-strategy-and-data-driven-decisions-7-data-readiness-assessment" }, { "name": "MLOps Pipeline and Change-Control Framework", "id": "chapter-16-ai-strategy-and-data-driven-decisions-8-mlops-pipeline-and-change-control-framework", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "chapterSlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "aliases": [], "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "description": "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. 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 dat", "sourceIds": [ "BB-C16-S09", "BB-C16-S10" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-16-ai-strategy-and-data-driven-decisions-8-mlops-pipeline-and-change-control-framework" ], "url": "index.html#chapter-16-ai-strategy-and-data-driven-decisions-8-mlops-pipeline-and-change-control-framework" }, { "name": "Agentic AI Operating and Control Model", "id": "chapter-16-ai-strategy-and-data-driven-decisions-9-agentic-ai-operating-and-control-model", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "chapterSlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "aliases": [ "AI" ], "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "description": "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. 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, an", "sourceIds": [ "BB-C16-S01", "BB-C16-S04", "BB-C16-S10", "BB-C16-S14" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-16-ai-strategy-and-data-driven-decisions-9-agentic-ai-operating-and-control-model" ], "url": "index.html#chapter-16-ai-strategy-and-data-driven-decisions-9-agentic-ai-operating-and-control-model" }, { "name": "AI Governance Structure", "id": "chapter-16-ai-strategy-and-data-driven-decisions-10-ai-governance-structure", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "chapterSlugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "aliases": [ "AI" ], "concepts": [ "AI strategy", "data readiness", "model governance", "decision systems", "AI business case" ], "description": "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. 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 ris", "sourceIds": [ "BB-C16-S01", "BB-C16-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-16-ai-strategy-and-data-driven-decisions-10-ai-governance-structure" ], "url": "index.html#chapter-16-ai-strategy-and-data-driven-decisions-10-ai-governance-structure" }, { "name": "The Digital Transformation Lifecycle Model", "id": "chapter-17-leading-digital-transformation-1-the-digital-transformation-lifecycle-model", "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "chapterSlugs": [ "chapter-17-leading-digital-transformation" ], "aliases": [], "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "description": "The Digital Transformation Lifecycle Model Phased Change Approach The transformation portfolio lifecycle treats digital transformation as coordinated change in strategy, capabilities, operating model, and technology, not merely a technology installation. The author-created lifecycle below is a planning scaffold: real initiatives may loop, overlap, pause, or stop, and no fixed sequence or clock establishes success. Use it to expose hypotheses, dependencies, decision rights, learning, and value evidence. [BB-C17-S01] [BB-C17-S06] [BB-C17-S07] Decision Criteria - Use when: Initiating a significant digital transformation effort. - Use when: Assessing the progress and current challenges of an ong", "sourceIds": [ "BB-C17-S01", "BB-C17-S06", "BB-C17-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-17-leading-digital-transformation-1-the-digital-transformation-lifecycle-model" ], "url": "index.html#chapter-17-leading-digital-transformation-1-the-digital-transformation-lifecycle-model" }, { "name": "Vision & Strategy Canvas for Transformation", "id": "chapter-17-leading-digital-transformation-2-vision-strategy-canvas-for-transformation", "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "chapterSlugs": [ "chapter-17-leading-digital-transformation" ], "aliases": [], "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "description": "Vision & Strategy Canvas for Digital Transformation North Star Definition The vision and strategy canvas can help connect digital capabilities to business outcomes, but neither a canvas nor coordinated leadership guarantees transformation success. [BB-C17-S01] The canvas below is an author-created synthesis for articulating a transformation hypothesis: its why , intended customer and operating outcomes, required capabilities, evidence, risks, and decision gates. It does not ensure alignment or provide a validated roadmap. Its sections, workshop design, suitability ratings, team sizes, timings, and update cadence are illustrative defaults to adapt and test. Decision Criteria - Use when: Kicki", "sourceIds": [ "BB-C17-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-17-leading-digital-transformation-2-vision-strategy-canvas-for-transformation" ], "url": "index.html#chapter-17-leading-digital-transformation-2-vision-strategy-canvas-for-transformation" }, { "name": "Kotter's 8-Step Model for Change (Digital Adaptation)", "id": "chapter-17-leading-digital-transformation-3-kotter-s-8-step-model-for-change-digital-adaptation", "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "chapterSlugs": [ "chapter-17-leading-digital-transformation" ], "aliases": [ "Digital Adaptation" ], "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "description": "Kotter's 8-Step Model for Change (Digital Adaptation) Orchestrating People Change Kotter's eight-step model is an influential practitioner framework for organizing a change campaign. It is not a causal law or a universal sequence: participation, power, job design, institutional context, and emergent change can alter what is appropriate. The digital adaptation below is author-created and should be used as a diagnostic checklist, not proof that a transformation will succeed. [BB-C17-S02] Decision Criteria - Use when: Leading any significant organizational change, especially digital transformation. - Use when: Encountering strong resistance to new technologies or ways of working. - Use when: Ai", "sourceIds": [ "BB-C17-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-17-leading-digital-transformation-3-kotter-s-8-step-model-for-change-digital-adaptation" ], "url": "index.html#chapter-17-leading-digital-transformation-3-kotter-s-8-step-model-for-change-digital-adaptation" }, { "name": "Technology Adoption Curve & The \"Chasm\"", "id": "chapter-17-leading-digital-transformation-4-technology-adoption-curve-the-chasm", "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "chapterSlugs": [ "chapter-17-leading-digital-transformation" ], "aliases": [], "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "description": "Technology Adoption Curve & The \"Chasm\" Innovation Diffusion Strategy The adoption-curve and chasm lens uses Rogers's adopter categories and Moore's commercial \"chasm\" to ask how adoption conditions differ; it does not establish a universal employee sequence or justify labeling people by age, status, or presumed resistance. Internal adoption can be constrained by job design, accessibility, safety, privacy, workload, power, or valid control objections rather than individual attitude. [BB-C17-S03] [BB-C17-S04] Figure 17.2. Rogers adopter-category shares with Moore's chasm overlaid. Rogers's approximate ideal-type shares are shown as a sequence, while Moore's chasm is a later commercial-market ", "sourceIds": [ "BB-C17-S03", "BB-C17-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-17-leading-digital-transformation-4-technology-adoption-curve-the-chasm" ], "url": "index.html#chapter-17-leading-digital-transformation-4-technology-adoption-curve-the-chasm" }, { "name": "The \"Ambidextrous Organization\" Model (Explore vs. Exploit)", "id": "chapter-17-leading-digital-transformation-5-the-ambidextrous-organization-model-explore-vs-exploit", "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "chapterSlugs": [ "chapter-17-leading-digital-transformation" ], "aliases": [ "Explore vs. Exploit" ], "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "description": "The \"Ambidextrous Organization\" Model (Explore vs. Exploit) Balancing Innovation & Efficiency The ambidextrous organization model frames the tension between exploiting existing capabilities and exploring new ones. Structural separation is one design option, not a universal prescription: contextual, temporal, leadership, and network mechanisms may also be appropriate, and separation creates coordination and resource-allocation costs. [BB-C17-S05] Decision Criteria - Use when: Your established organization needs to innovate radically (e.g., new business models, disruptive technologies). - Use when: Your current organizational structure is stifling innovation or slow to adapt. - Use when: Strug", "sourceIds": [ "BB-C17-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-17-leading-digital-transformation-5-the-ambidextrous-organization-model-explore-vs-exploit" ], "url": "index.html#chapter-17-leading-digital-transformation-5-the-ambidextrous-organization-model-explore-vs-exploit" }, { "name": "Digital Maturity Assessment Framework", "id": "chapter-17-leading-digital-transformation-6-digital-maturity-assessment-framework", "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "chapterSlugs": [ "chapter-17-leading-digital-transformation" ], "aliases": [], "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "description": "Digital Maturity Assessment Framework Current State Analysis Before embarking on a digital transformation, organizations need an honest and comprehensive understanding of their current digital capabilities and performance. The digital maturity assessment provides a structured way to evaluate an organization across multiple dimensions—strategy, customer experience, technology, operations, and culture—to identify strengths, pinpoint critical gaps, and establish a baseline for progress. [BB-C17-S06] For leaders, this assessment informs a transformation roadmap; it does not prove which investment will have the greatest impact or ensure alignment. Decision Criteria - Use when: Initiating a digita", "sourceIds": [ "BB-C17-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-17-leading-digital-transformation-6-digital-maturity-assessment-framework" ], "url": "index.html#chapter-17-leading-digital-transformation-6-digital-maturity-assessment-framework" }, { "name": "Business Capability Mapping for Modernization", "id": "chapter-17-leading-digital-transformation-7-business-capability-mapping-for-modernization", "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "chapterSlugs": [ "chapter-17-leading-digital-transformation" ], "aliases": [], "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "description": "Business Capability Mapping for Modernization Strategic Investment Prioritization Business capability mapping represents what an organization must be able to do, separately from a particular current process, organization chart, or system. The modernization sequence below is an author-created adaptation for connecting capability hypotheses to technology and operating-model decisions. A map can expose gaps and dependencies; it does not establish which investment will produce the greatest return or ensure strategic alignment. The decomposition levels, capability counts, labels, ratings, workshop timing, and roadmap cadence are illustrative and require local evidence. Decision Criteria - Use whe", "sourceIds": [], "provenanceStatus": "constructed", "toolIds": [], "backlinks": [ "index.html#chapter-17-leading-digital-transformation-7-business-capability-mapping-for-modernization" ], "url": "index.html#chapter-17-leading-digital-transformation-7-business-capability-mapping-for-modernization" }, { "name": "OKRs for Transformation (Objectives & Key Results)", "id": "chapter-17-leading-digital-transformation-8-okrs-for-transformation-objectives-key-results", "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "chapterSlugs": [ "chapter-17-leading-digital-transformation" ], "aliases": [ "Objectives & Key Results" ], "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "description": "OKRs for Transformation (Objectives & Key Results) Outcome-Driven Measurement In the dynamic and often ambiguous world of digital transformation, traditional output-focused metrics and annual reviews can fall short. The OKR system provides a goal-setting and learning framework for setting objectives and measuring progress with defined metrics. [BB-C17-S08] OKRs can support outcome focus, alignment, transparency, and continuous improvement, but they do not ensure accountability or accelerate value by themselves. Decision Criteria - Use when: Leading a digital transformation or other significant change initiative. - Use when: Struggling with alignment across teams or clear prioritization of in", "sourceIds": [ "BB-C17-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-17-leading-digital-transformation-8-okrs-for-transformation-objectives-key-results" ], "url": "index.html#chapter-17-leading-digital-transformation-8-okrs-for-transformation-objectives-key-results" }, { "name": "Digital Governance & Operating Model", "id": "chapter-17-leading-digital-transformation-9-digital-governance-operating-model", "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "chapterSlugs": [ "chapter-17-leading-digital-transformation" ], "aliases": [], "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "description": "Digital Governance & Operating Model Structuring Digital Success The digital governance and operating model allocates decision rights, accountability, funding, standards, assurance, and escalation; the operating model describes how capabilities are delivered and run. Central, federated, product, platform, and hybrid designs are contingent on strategy, regulation, architecture, risk, scale, and talent. Governance can improve alignment and control, but no design ensures speed, value, or competitive advantage. [BB-C17-S07] Decision Criteria - Use when: Designing or refining the organizational structure for digital initiatives. - Use when: Clarifying roles, responsibilities, and decision-making ", "sourceIds": [ "BB-C17-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-17-leading-digital-transformation-9-digital-governance-operating-model" ], "url": "index.html#chapter-17-leading-digital-transformation-9-digital-governance-operating-model" }, { "name": "Storytelling & Communication Playbook for Change", "id": "chapter-17-leading-digital-transformation-10-storytelling-communication-playbook-for-change", "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "chapterSlugs": [ "chapter-17-leading-digital-transformation" ], "aliases": [], "concepts": [ "digital maturity", "operating model", "enterprise architecture", "change leadership", "transformation failure", "digital sustainability", "lifecycle assessment", "embodied emissions", "rebound effect", "environmental claims" ], "description": "Storytelling & Communication Playbook for Change Engaging Hearts & Minds The storytelling and communication playbook is one element of organized change, including Kotter's practitioner sequence, but a story does not overcome weak evidence, conflicting interests, unsafe job design, absent participation, or poor decision rights. [BB-C17-S02] The playbook below is an author-created communication aid informed by the cited storytelling literature. It can help leaders state the rationale, audience, evidence, uncertainty, choices, and feedback channels; it does not guarantee understanding, trust, adoption, or transformation success. Its sequence, channel mix, team design, timing, and examples are i", "sourceIds": [ "BB-C17-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-17-leading-digital-transformation-10-storytelling-communication-playbook-for-change" ], "url": "index.html#chapter-17-leading-digital-transformation-10-storytelling-communication-playbook-for-change" }, { "name": "Platform Economy Framework", "id": "chapter-18-digital-business-models-and-platform-economics-1-platform-economy-framework", "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "chapterSlugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "aliases": [], "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "description": "The platform economy framework treats a platform as a coordination and governance arrangement among participant groups whose choices are interdependent. It is a decision lens, not a claim that platforms are asset-free, unlimited, high-margin, or destined to dominate. [BB-C18-S01] [BB-C18-S03] Define the participant sides, jobs, value and money flows, quality floor, matching mechanism, price or subsidy structure, operating constraints, governance, data rights, and exit options before choosing a platform model. Compare platform, pipeline, reseller, managed-service, and hybrid alternatives against a non-platform baseline. Platform, pipeline, and hybrid models: - Model: Make products → Sell to c", "sourceIds": [ "BB-C18-S01", "BB-C18-S03", "BB-C18-S06", "BB-C18-S16", "BB-C18-S17", "BB-C18-S18", "BB-C18-S19" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-18-digital-business-models-and-platform-economics-1-platform-economy-framework" ], "url": "index.html#chapter-18-digital-business-models-and-platform-economics-1-platform-economy-framework" }, { "name": "Network Effects Typology", "id": "chapter-18-digital-business-models-and-platform-economics-2-network-effects-typology", "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "chapterSlugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "aliases": [], "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "description": "The network-effects typology asks how participation changes value for a defined side, segment, geography, and time window. Direct, indirect, data, and exchange effects can be positive, weak, local, congested, reversible, or negative; they are not a universal growth law. [BB-C18-S02] [BB-C18-S03] Identify the effect and counterfactual, specify the unit of value, measure participation and outcomes by side and cohort, test multi-homing and substitutes, and record a stop or redesign rule. Do not infer a global effect from aggregate users, downloads, or a single viral episode. Network Effect Definition: The value of a platform can increase as more users join. [BB-C18-S02] Constructed example: A t", "sourceIds": [ "BB-C18-S02", "BB-C18-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-18-digital-business-models-and-platform-economics-2-network-effects-typology" ], "url": "index.html#chapter-18-digital-business-models-and-platform-economics-2-network-effects-typology" }, { "name": "Digital Revenue Models", "id": "chapter-18-digital-business-models-and-platform-economics-3-digital-revenue-models", "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "chapterSlugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "aliases": [], "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "description": "The digital revenue-model framework separates value creation, value delivery, and value capture. Advertising, subscription, transaction, usage, licensing, affiliate, services, and hybrid models are choices with different payer incentives, cost drivers, risks, and control requirements—not a menu of guaranteed margins. [BB-C18-S04] [BB-C18-S05] For each alternative, name the payer, pricing basis, unit of value, variable and fixed costs, acquisition and service costs, refunds and disputes, capital needs, data and legal constraints, and the counterfactual. Model contribution cash flow by cohort and show sensitivity; do not import current price ranges or a recorded zero CAC as universal evidence.", "sourceIds": [ "BB-C18-S04", "BB-C18-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-18-digital-business-models-and-platform-economics-3-digital-revenue-models" ], "url": "index.html#chapter-18-digital-business-models-and-platform-economics-3-digital-revenue-models" }, { "name": "API Economy & Ecosystem Value", "id": "chapter-18-digital-business-models-and-platform-economics-4-api-economy-ecosystem-value", "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "chapterSlugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "aliases": [ "API" ], "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "description": "The API and ecosystem framework treats an interface as a governed dependency, not proof of a platform or network effect. Value depends on useful complementor jobs, reliability, versioning, security, data rights, support cost, bargaining power, and who captures value. [BB-C18-S06] Define the core job, authorized actors, interface contract, quality and security floor, version and deprecation policy, support model, data permissions, commercial terms, review rights, and exit path. Test a closed, partner, or open interface against the non-API alternative. API Definition: Application Programming Interface (way for programs to talk to each other) Traditional Model (No APIs): - Company A builds prod", "sourceIds": [ "BB-C18-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-18-digital-business-models-and-platform-economics-4-api-economy-ecosystem-value" ], "url": "index.html#chapter-18-digital-business-models-and-platform-economics-4-api-economy-ecosystem-value" }, { "name": "Data Monetization and Rights-to-Value Gate", "id": "chapter-18-digital-business-models-and-platform-economics-5-data-monetization-and-rights-to-value-gate", "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "chapterSlugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "aliases": [], "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "description": "The data monetization gate treats data value as conditional on authority, purpose, quality, affected-party interests, security, fairness, competition, and remedy. “Public,” “purchased,” “inferred,” or “de-identified” does not by itself establish permission, low risk, or durable value. [BB-C18-S07] [BB-C18-S10] Before choosing direct sales, a data-enhanced product, an API, or a data-enabled marketplace, document the data origin, rights and contracts, purpose, lawful basis where applicable, notice and expectations, minimization, retention, provenance, quality, re-identification risk, security, access and correction, objection/deletion, transfer, competition, affected parties, and accountable a", "sourceIds": [ "BB-C18-S07", "BB-C18-S10" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-18-digital-business-models-and-platform-economics-5-data-monetization-and-rights-to-value-gate" ], "url": "index.html#chapter-18-digital-business-models-and-platform-economics-5-data-monetization-and-rights-to-value-gate" }, { "name": "Digital Ecosystem Mapping", "id": "chapter-18-digital-business-models-and-platform-economics-6-digital-ecosystem-mapping", "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "chapterSlugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "aliases": [], "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "description": "The ecosystem-structure map makes interdependent roles, bottlenecks, dependencies, and adoption risks explicit. An ecosystem lens can clarify a strategy problem, but it is neither necessary nor sufficient for every business model. [BB-C18-S08] Map the focal customer outcome, required participants, complements, infrastructure, standards, data and money flows, dependencies, control points, substitution, bargaining power, and failure conditions. For each role, specify the contribution required, the evidence of readiness, the incentive, and the response if that participant delays, exits, or changes terms. Table 18.4: Author-created ecosystem structure map (Role | Required contribution | Dependen", "sourceIds": [ "BB-C18-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-18-digital-business-models-and-platform-economics-6-digital-ecosystem-mapping" ], "url": "index.html#chapter-18-digital-business-models-and-platform-economics-6-digital-ecosystem-mapping" }, { "name": "Cybersecurity Risk Matrix", "id": "chapter-18-digital-business-models-and-platform-economics-7-cybersecurity-risk-matrix", "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "chapterSlugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "aliases": [], "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "description": "The platform cybersecurity risk matrix translates business-model choices into security outcomes, affected assets, plausible threats, control evidence, residual risk, and accountable decisions. It is a prioritization aid, not a probability or loss benchmark. [BB-C18-S09] Start with the service, assets, data, trust boundaries, dependencies, and harm scenarios. For each scenario, record likelihood uncertainty, impact dimensions, existing controls, control evidence, recovery objective, legal/contractual obligations, owner, and an accept, reduce, transfer, redesign, or stop decision. Do not replace this analysis with a generic maturity score or a dollar figure copied from another business. Table ", "sourceIds": [ "BB-C18-S09" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-18-digital-business-models-and-platform-economics-7-cybersecurity-risk-matrix" ], "url": "index.html#chapter-18-digital-business-models-and-platform-economics-7-cybersecurity-risk-matrix" }, { "name": "Digital KPI Dashboard", "id": "chapter-18-digital-business-models-and-platform-economics-8-digital-kpi-dashboard", "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "chapterSlugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "aliases": [ "KPI" ], "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "description": "The digital KPI dashboard links a business-model hypothesis to a small set of defined leading, operating, outcome, and guardrail measures. Metrics should narrow uncertainty and trigger decisions; they should not become vanity targets or universal benchmarks. [BB-C18-S11] Define the customer or operating decision, metric numerator and denominator, unit, cohort, time window, data source, owner, uncertainty, and action threshold before collecting the number. Pair growth measures with quality, cost, safety, fairness, security, accessibility, retention, and contribution measures. Use a documented local target and review cadence. Table 18.6: Author-created digital KPI dashboard (Hypothesis | Leadi", "sourceIds": [ "BB-C18-S11" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-18-digital-business-models-and-platform-economics-8-digital-kpi-dashboard" ], "url": "index.html#chapter-18-digital-business-models-and-platform-economics-8-digital-kpi-dashboard" }, { "name": "Automation Opportunity Assessment", "id": "chapter-18-digital-business-models-and-platform-economics-9-automation-opportunity-assessment", "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "chapterSlugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "aliases": [], "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "description": "The automation opportunity assessment compares task and workflow redesign options while keeping human judgment, affected-worker effects, quality, safety, security, accessibility, and accountability visible. Digital technology can change tasks and work, but a source or tool does not predict a universal substitution path. [BB-C18-S12] Define the decision, baseline process, exception rate, quality floor, affected roles, data and control requirements, alternatives, full lifecycle cost, and evidence threshold. Compare manual improvement, conventional software, assistive automation, partial automation, outsourcing, and no-change options. Pilot with meaningful human review and measure both performa", "sourceIds": [ "BB-C18-S12" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-18-digital-business-models-and-platform-economics-9-automation-opportunity-assessment" ], "url": "index.html#chapter-18-digital-business-models-and-platform-economics-9-automation-opportunity-assessment" }, { "name": "Digital Transformation Roadmap", "id": "chapter-18-digital-business-models-and-platform-economics-10-digital-transformation-roadmap", "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "chapterSlugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "aliases": [], "concepts": [ "platforms", "network effects", "ecosystems", "APIs", "data monetization" ], "description": "The digital transformation roadmap sequences a portfolio of business, capability, operating-model, data, technology, workforce, and governance changes around evidence and decision rights. A roadmap is a coordination artifact, not a fixed timetable or guarantee of transformation success. [BB-C18-S13] Start with a customer or operating outcome and baseline. Define the capabilities, dependencies, alternatives, owners, resource and lifecycle-cost assumptions, risk boundaries, pilot evidence, scale criteria, and stop or redesign rules. Review the roadmap when evidence, law, capacity, architecture, workforce conditions, or strategy changes. Table 18.8: Author-created digital transformation roadmap", "sourceIds": [ "BB-C18-S13", "BB-C18-S02", "BB-C18-S03", "BB-C18-S06", "BB-C18-S09", "BB-C18-S10" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-18-digital-business-models-and-platform-economics-10-digital-transformation-roadmap" ], "url": "index.html#chapter-18-digital-business-models-and-platform-economics-10-digital-transformation-roadmap" }, { "name": "The NIST Cybersecurity Framework", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-1-the-nist-cybersecurity-framework", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "chapterSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "aliases": [ "NIST" ], "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "description": "The NIST Cybersecurity Framework Holistic Program Structure NIST CSF 2.0 is a voluntary, outcome-oriented framework for understanding, assessing, prioritizing, and communicating cybersecurity risk. It organizes outcomes under six concurrent Functions: Govern, Identify, Protect, Detect, Respond, and Recover . Govern establishes organizational context, risk strategy, roles, policy, oversight, and cybersecurity supply-chain risk management. CSF 2.0 does not prescribe a technology stack or by itself establish legal compliance or control effectiveness. [BB-C19-S01] Decision Criteria - Use when: Building a new cybersecurity program from scratch. - Use when: Assessing the maturity and effectiveness", "sourceIds": [ "BB-C19-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-1-the-nist-cybersecurity-framework" ], "url": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-1-the-nist-cybersecurity-framework" }, { "name": "Cyber Risk Quantification (FAIR Model Simplified)", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-2-cyber-risk-quantification-fair-model-simplified", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "chapterSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "aliases": [ "FAIR", "FAIR Model Simplified" ], "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "description": "Cyber Risk Quantification (FAIR Model Simplified) Financial Impact Assessment The FAIR-style cyber risk quantification approach translates a defined cyber scenario into frequency, loss-magnitude, control-effect, and uncertainty questions so managers can compare decisions. It can support board communication, but it does not produce a universal ROI or replace local asset, recovery, legal, safety, privacy, or mission analysis. Decision Criteria - Use when: Justifying cybersecurity budget requests to the board or executive team. - Use when: Prioritizing cybersecurity investments across multiple projects or controls. - Use when: Communicating cyber risk in business terms. - Use when: Assessing th", "sourceIds": [ "BB-C19-S03", "BB-C19-S01", "BB-C19-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-2-cyber-risk-quantification-fair-model-simplified" ], "url": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-2-cyber-risk-quantification-fair-model-simplified" }, { "name": "The \"Crown Jewels\" Analysis for Asset Protection", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-3-the-crown-jewels-analysis-for-asset-protection", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "chapterSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "aliases": [], "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "description": "The \"Crown Jewels\" Analysis for Asset Protection Prioritizing Security Efforts The crown-jewels analysis identifies critical services, data, identities, capabilities, dependencies, and recovery paths whose compromise would materially affect the organization or its mission. It focuses scarce resources without implying a fixed percentage, a complete asset inventory, or a universal ranking. Decision Criteria - Use when: Designing or refining your cybersecurity strategy. - Use when: Allocating cybersecurity budget and resources. - Use when: Identifying key assets for incident response and business continuity planning. - Use when: Communicating critical assets and associated risks to the board. -", "sourceIds": [ "BB-C19-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-3-the-crown-jewels-analysis-for-asset-protection" ], "url": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-3-the-crown-jewels-analysis-for-asset-protection" }, { "name": "The Cyber Defense Matrix", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-4-the-cyber-defense-matrix", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "chapterSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "aliases": [], "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "description": "The Cyber Defense Matrix Mapping Security Controls The classic Cyber Defense Matrix is a practitioner taxonomy created by Sounil Yu. Its five-by-five form crosses the five pre-CSF-2.0 operational Functions—Identify, Protect, Detect, Respond, Recover—with Devices, Applications, Networks, Data, and Users. [BB-C19-S06] When used with CSF 2.0, explicitly add Govern as the organizational context, strategy, policy, roles, oversight, and supply-chain layer across the matrix. This is a labeled adaptation: it does not change the registered source model or establish that a control, spend level, or product reduces loss. [BB-C19-S01] Figure 19.1. Classic Cyber Defense Matrix with a CSF 2.0 Govern overla", "sourceIds": [ "BB-C19-S06", "BB-C19-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-4-the-cyber-defense-matrix" ], "url": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-4-the-cyber-defense-matrix" }, { "name": "Vendor & Supply Chain Risk Assessment Model", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-5-vendor-supply-chain-risk-assessment-model", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "chapterSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "aliases": [], "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "description": "Vendor & Supply Chain Risk Assessment Model Third-Party Security Oversight The vendor and supply-chain risk model treats suppliers, platforms, software components, data processors, and other services as shared-control dependencies. An incident can arise from architecture, configuration, access, concentration, monitoring, contracts, recovery, a vendor, or a downstream provider. This model maps dependency paths, allocates responsibility, tests evidence, and supports reduce, transfer, accept, monitor, or exit decisions; it does not reduce a supplier to a “weakest link.” Decision Criteria - Use when: Onboarding any new third-party vendor that will access your data, systems, or network. - Use whe", "sourceIds": [ "BB-C19-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-5-vendor-supply-chain-risk-assessment-model" ], "url": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-5-vendor-supply-chain-risk-assessment-model" }, { "name": "The \"Assume Breach\" Mindset", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-6-the-assume-breach-mindset", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "chapterSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "aliases": [], "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "description": "The \"Assume Breach\" Mindset Cyber Resilience Strategy The assume-breach resilience mindset complements prevention with detection, containment, response, recovery, and learning. It asks what the organization would do if a defined scenario occurred, how quickly it could detect and contain it, how it would preserve evidence and safety, and whether it could restore critical services. It is a stress-test prompt, not a prediction that compromise is inevitable. Decision Criteria - Use when: Designing or refining your overall cybersecurity strategy. - Use when: Allocating cybersecurity budget and resources to maximize ROI. - Use when: Developing incident response and business continuity plans. - Use", "sourceIds": [ "BB-C19-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-6-the-assume-breach-mindset" ], "url": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-6-the-assume-breach-mindset" }, { "name": "Incident Response Plan on a Page", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-7-incident-response-plan-on-a-page", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "chapterSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "aliases": [], "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "description": "Incident Response Plan on a Page Crisis Playbook The incident-response one-page playbook is a concise orientation aid for authority, evidence preservation, communications, safety, containment, recovery, legal review, insurer, law-enforcement, and escalation contacts. It should point to tested technical runbooks and current legal analysis rather than pretend to replace them. Decision Criteria - Use when: A cybersecurity incident (e.g., ransomware, data breach, system outage) is actively occurring. - Use when: Training incident response teams and key stakeholders. - Use when: Communicating high-level incident response procedures to the board or executive team. - Use when: Needing a quick refer", "sourceIds": [ "BB-C19-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-7-incident-response-plan-on-a-page" ], "url": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-7-incident-response-plan-on-a-page" }, { "name": "Continuous Contextual Access Decisions (CARTA as a Proprietary Reference)", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-8-continuous-contextual-access-decisions-carta-as-a-proprietary-reference", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "chapterSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "aliases": [ "CARTA", "CARTA as a Proprietary Reference" ], "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "description": "Continuous Contextual Access Decisions Dynamic Security Decisioning The continuous contextual access decision model uses identity, device, resource, request, behavior, and other signals to make least-privilege access decisions against a defined purpose and risk boundary. It anchors architecture to NIST Zero Trust; CARTA is a separate proprietary term, not synonymous with or the operationalization of NIST architecture. Signals and automation require privacy, bias, accessibility, availability, due-process, vendor, and governance controls. [BB-C19-S01] Decision Criteria - Use when: Designing or refining your cybersecurity architecture for modern, dynamic environments (cloud, remote work, IoT). ", "sourceIds": [ "BB-C19-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-8-continuous-contextual-access-decisions-carta-as-a-proprietary-reference" ], "url": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-8-continuous-contextual-access-decisions-carta-as-a-proprietary-reference" }, { "name": "Ransomware Decision-Making Framework", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-9-ransomware-decision-making-framework", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "chapterSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "aliases": [], "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "description": "Ransomware Decision-Making Framework Crisis Response Playbook The ransomware decision-making framework is a governance checklist for a scenario-specific business-continuity, safety, data, legal, and financial risk. It is not live incident advice. During an incident, activate the approved authority matrix; preserve privilege and evidence; assess safety, operations, exfiltration, recovery, materiality, and obligations; and involve counsel, forensics, insurer, law enforcement, sanctions review, regulators, and required executives or board roles as applicable. [BB-C19-S01] [BB-C19-S05] Decision Criteria - Use when: Your organization has been impacted by a ransomware attack. - Use when: Developin", "sourceIds": [ "BB-C19-S01", "BB-C19-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-9-ransomware-decision-making-framework" ], "url": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-9-ransomware-decision-making-framework" }, { "name": "Human-Centered Security Culture", "id": "chapter-19-cybersecurity-and-risk-management-for-managers-10-human-centered-security-culture", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "chapterSlugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "aliases": [], "concepts": [ "cyber risk", "incident response", "controls", "supply chain security", "risk management" ], "description": "Human-Centered Security Culture Employee Engagement Strategy The human-centered security culture model treats people as participants in a socio-technical security system, not a firewall or the “weakest link.” Secure defaults, least privilege, usable workflows, staffing and workload, accessible reporting, identity controls, detection, containment, recovery, and accountable management determine whether an error or malicious message becomes an incident. Role-based practice and safe reporting matter, but training must not transfer the control boundary from system owners to employees. [BB-C19-S01] [BB-C19-S04] Decision Criteria - Use when: Designing or refining your overall cybersecurity program.", "sourceIds": [ "BB-C19-S01", "BB-C19-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-10-human-centered-security-culture" ], "url": "index.html#chapter-19-cybersecurity-and-risk-management-for-managers-10-human-centered-security-culture" }, { "name": "The FATE (Fairness, Accountability, Transparency, Explainability) Framework", "id": "chapter-20-the-ethics-of-ai-and-data-1-the-fate-fairness-accountability-transparency-explainability-framework", "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "chapterSlugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "aliases": [ "Fairness, Accountability, Transparency, Explainability", "FATE" ], "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "description": "The FATE (Fairness, Accountability, Transparency, Explainability) Framework Holistic Ethical Evaluation This chapter uses FATE as a mnemonic for four practical review dimensions: Fairness, Accountability, Transparency, and Explainability. These dimensions complement the trustworthy-AI and policy principles in NIST AI RMF and the OECD AI Principles. [BB-C20-S01] [BB-C20-S02] For managers, FATE provides a practical lens to assess an AI system's ethical posture, guide design choices, and communicate responsible AI practices to stakeholders. Decision Criteria - Use when: Designing, developing, or deploying any AI system with significant impact (e.g., hiring, lending, medical diagnosis, content m", "sourceIds": [ "BB-C20-S01", "BB-C20-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-20-the-ethics-of-ai-and-data-1-the-fate-fairness-accountability-transparency-explainability-framework" ], "url": "index.html#chapter-20-the-ethics-of-ai-and-data-1-the-fate-fairness-accountability-transparency-explainability-framework" }, { "name": "Algorithmic Bias: Detection & Mitigation Patterns", "id": "chapter-20-the-ethics-of-ai-and-data-2-algorithmic-bias-detection-mitigation-patterns", "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "chapterSlugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "aliases": [], "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "description": "Algorithmic Bias: Detection & Mitigation Patterns Ensuring Fair Outcomes The algorithmic bias review asks how systems can create or reproduce unjustified disparities through problem definition, data, labels, measurement, objectives, model design, thresholds, workflow, human use, or institutional context. Fairness metrics answer different normative questions and may be mutually incompatible. Qualified human owners must choose contextually and legally appropriate groups, outcomes, reference groups, metrics, thresholds, error trade-offs, and remedies; document why; test intersectional and operational effects; and provide contestability where appropriate. A favorable aggregate metric is not proo", "sourceIds": [ "BB-C20-S04", "BB-C20-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-20-the-ethics-of-ai-and-data-2-algorithmic-bias-detection-mitigation-patterns" ], "url": "index.html#chapter-20-the-ethics-of-ai-and-data-2-algorithmic-bias-detection-mitigation-patterns" }, { "name": "The Model Card & Datasheet for Transparency", "id": "chapter-20-the-ethics-of-ai-and-data-3-the-model-card-datasheet-for-transparency", "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "chapterSlugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "aliases": [], "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "description": "The Model Card & Datasheet for Transparency AI System Documentation Model Cards and Datasheets make intended use, performance, limitations, provenance, and documentation visible. A Model Card is like a nutrition label for an AI model, detailing its performance, limitations, and ethical considerations. A Datasheet for Datasets provides similar documentation for the data used to train AI. [BB-C20-S05] [BB-C20-S06] For managers, these frameworks facilitate accountable deployment and informed decision-making by clearly communicating the what, how, and why of AI systems. Decision Criteria - Use when: Developing, deploying, or acquiring any AI model. - Use when: Collecting, curating, or using data", "sourceIds": [ "BB-C20-S05", "BB-C20-S06", "BB-C20-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-20-the-ethics-of-ai-and-data-3-the-model-card-datasheet-for-transparency" ], "url": "index.html#chapter-20-the-ethics-of-ai-and-data-3-the-model-card-datasheet-for-transparency" }, { "name": "The Privacy by Design (PbD) Framework", "id": "chapter-20-the-ethics-of-ai-and-data-4-the-privacy-by-design-pbd-framework", "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "chapterSlugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "aliases": [ "PbD" ], "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "description": "The Privacy by Design (PbD) Framework Proactive Privacy Integration Privacy by Design (PbD) is presented in Ann Cavoukian's 2011 Information and Privacy Commissioner of Ontario white paper as a proactive approach that embeds privacy in the design and architecture of information systems and business practices rather than adding it after the fact. Its appendix states seven foundational principles. [BB-C20-S12] For managers, PbD is a design and governance framework, not legal advice, a certification, or a statement of current legal obligations. Determine the applicable requirements for the specific data, system, jurisdiction, and timing through qualified legal review. Application boundary: The ", "sourceIds": [ "BB-C20-S12" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-20-the-ethics-of-ai-and-data-4-the-privacy-by-design-pbd-framework" ], "url": "index.html#chapter-20-the-ethics-of-ai-and-data-4-the-privacy-by-design-pbd-framework" }, { "name": "Explanation, Notice, Contestability, and Recourse Decision Tree", "id": "chapter-20-the-ethics-of-ai-and-data-5-explanation-notice-contestability-and-recourse-decision-tree", "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "chapterSlugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "aliases": [], "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "description": "Explanation, Notice, Contestability, and Recourse Justifying AI Decisions The explanation, notice, contestability, and recourse decision tree asks what understandable information, correction, challenge, and remedy a consequential decision needs. This decision tree is an operational transparency aid, not legal advice and not a statement that one universal \"right to explanation\" applies. Specific notice, explanation, contestability, and human-review duties depend on the current requirements for the jurisdiction, use case, system role, and deployment. [BB-C20-S03] Decision Criteria - Use when: Designing or deploying AI systems that make automated decisions with legal or significant effects on i", "sourceIds": [ "BB-C20-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-20-the-ethics-of-ai-and-data-5-explanation-notice-contestability-and-recourse-decision-tree" ], "url": "index.html#chapter-20-the-ethics-of-ai-and-data-5-explanation-notice-contestability-and-recourse-decision-tree" }, { "name": "Red Teaming & Adversarial Testing for AI", "id": "chapter-20-the-ethics-of-ai-and-data-6-red-teaming-adversarial-testing-for-ai", "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "chapterSlugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "aliases": [ "AI" ], "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "description": "Red Teaming & Adversarial Testing for AI Robustness & Safety Assurance AI red teaming is a structured effort to find flaws and vulnerabilities in an AI system, often in a controlled environment and in collaboration with developers. Its AI RMF Playbook describes red teaming as adversarial testing under stress conditions and describes red-team independence as one way to support effective challenge. [BB-C20-S13] NIST's adversarial-machine-learning taxonomy separately distinguishes attack classes, lifecycle stages, attacker goals and capabilities, and predictive versus generative AI; it is a common-language resource, not a complete red-team procedure. [BB-C20-S14] Red teaming is one evaluation a", "sourceIds": [ "BB-C20-S13", "BB-C20-S14" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-20-the-ethics-of-ai-and-data-6-red-teaming-adversarial-testing-for-ai" ], "url": "index.html#chapter-20-the-ethics-of-ai-and-data-6-red-teaming-adversarial-testing-for-ai" }, { "name": "The AI Ethics Committee (AEC) Charter", "id": "chapter-20-the-ethics-of-ai-and-data-7-the-ai-ethics-committee-aec-charter", "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "chapterSlugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "aliases": [ "AEC", "AI" ], "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "description": "The AI Ethics Committee (AEC) Charter Governance & Oversight An AI ethics committee is one governance option, not a universal requirement or proof of due diligence, compliance, risk reduction, or trust. Organizations can integrate challenge and decision rights into existing product, model-risk, legal, privacy, safety, security, audit, workforce, clinical, or board structures; use a dedicated body; or combine them. The decisive questions are authority, independence, conflicts, expertise, affected-party voice, evidence access, escalation, appeal, remediation, and accountable ownership. [BB-C20-S01] [BB-C20-S07] Decision Criteria - Use when: Developing or deploying high-stakes AI systems (e.g.,", "sourceIds": [ "BB-C20-S01", "BB-C20-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-20-the-ethics-of-ai-and-data-7-the-ai-ethics-committee-aec-charter" ], "url": "index.html#chapter-20-the-ethics-of-ai-and-data-7-the-ai-ethics-committee-aec-charter" }, { "name": "Stakeholder Impact Assessment for AI", "id": "chapter-20-the-ethics-of-ai-and-data-8-stakeholder-impact-assessment-for-ai", "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "chapterSlugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "aliases": [ "AI" ], "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "description": "Stakeholder Impact Assessment for AI Broad Societal Impact Analysis A Stakeholder Impact Assessment (SIA) examines the far-reaching and often unforeseen consequences that AI systems can have beyond their immediate users. An SIA identifies, analyzes, and helps manage potential positive and negative impacts on affected individuals and groups. It moves beyond technical performance to consider the broader societal, economic, and ethical implications. For managers, an SIA can organize evidence, participation, risk decisions, and remedy; it does not guarantee trust or positive outcomes. Decision Criteria - Use when: Developing or deploying any AI system with potential broad societal, economic, or ", "sourceIds": [ "BB-C20-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-20-the-ethics-of-ai-and-data-8-stakeholder-impact-assessment-for-ai" ], "url": "index.html#chapter-20-the-ethics-of-ai-and-data-8-stakeholder-impact-assessment-for-ai" }, { "name": "The Data Ethics Canvas", "id": "chapter-20-the-ethics-of-ai-and-data-9-the-data-ethics-canvas", "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "chapterSlugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "aliases": [], "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "description": "The Data Ethics Canvas Ethical Data Strategy The Data Ethics Canvas , described by the Open Data Institute, is a tool for people who collect, share, or use data. Its purpose is to prompt reflection on ethical issues at the start of a data project and throughout it; completion does not establish that a project is ethical, lawful, fair, safe, or trustworthy. The ODI adopted a revised learning version as its standard in 2021, organized into four categories: understanding the data, exploring impact, planning engagement, and integrating decisions into processes. [BB-C20-S15] The chapter summarizes that version rather than reproducing the canvas artwork or its full text. Application and permission", "sourceIds": [ "BB-C20-S15" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-20-the-ethics-of-ai-and-data-9-the-data-ethics-canvas" ], "url": "index.html#chapter-20-the-ethics-of-ai-and-data-9-the-data-ethics-canvas" }, { "name": "The AI Ethics Lifecycle", "id": "chapter-20-the-ethics-of-ai-and-data-10-the-ai-ethics-lifecycle", "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "chapterSlugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "aliases": [ "AI" ], "concepts": [ "AI ethics", "bias", "privacy", "accountability", "responsible AI" ], "description": "The AI Ethics Lifecycle End-to-End Ethical AI Management The AI ethics lifecycle treats ethical considerations as an ongoing responsibility rather than a one-time checkpoint; they span the entire AI development and deployment process. The AI Ethics Lifecycle provides a structured, end-to-end framework for embedding ethical principles—from initial ideation and data collection to model deployment, monitoring, and eventual decommissioning. [BB-C20-S01] For managers, this lifecycle approach helps integrate ethical considerations throughout the system's lifespan. Decision Criteria - Use when: Designing an internal governance framework for AI development. - Use when: Managing complex AI projects f", "sourceIds": [ "BB-C20-S01", "BB-C20-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-20-the-ethics-of-ai-and-data-10-the-ai-ethics-lifecycle" ], "url": "index.html#chapter-20-the-ethics-of-ai-and-data-10-the-ai-ethics-lifecycle" }, { "name": "Jobs-to-be-Done (JTBD) Framework", "id": "chapter-21-product-management-and-product-strategy-1-jobs-to-be-done-jtbd-framework", "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "chapterSlugs": [ "chapter-21-product-management-and-product-strategy" ], "aliases": [ "JTBD" ], "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "description": "Jobs-to-be-Done (JTBD) Framework Customer Needs Discovery Customers don't buy products; they \"hire\" them to do a job. JTBD is a framework for understanding the fundamental progress customers are trying to make in their lives. Pioneered by Clayton Christensen and coauthors, it shifts focus from demographics and features to the underlying job. [BB-C21-S01] The Core Insight: When a customer buys a milkshake at 6am, they're not hiring it for nutrition. They're hiring it to make a boring commute more interesting and to keep them full until lunch. Understanding the job unlocks better product design than understanding the customer segment . 1. Identify the Job: What progress is the customer trying ", "sourceIds": [ "BB-C21-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-21-product-management-and-product-strategy-1-jobs-to-be-done-jtbd-framework" ], "url": "index.html#chapter-21-product-management-and-product-strategy-1-jobs-to-be-done-jtbd-framework" }, { "name": "Product Strategy Canvas", "id": "chapter-21-product-management-and-product-strategy-2-product-strategy-canvas", "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "chapterSlugs": [ "chapter-21-product-management-and-product-strategy" ], "aliases": [], "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "description": "Product Strategy Canvas Strategic Positioning A product strategy canvas connects goals and product vision to desired customer and business outcomes; it is not merely a feature plan. [BB-C21-S18] The six-part canvas below is an author-created synthesis that combines that strategy framing with jobs-to-be-done questions. [BB-C21-S01] It prompts explicit choices but does not force clarity, prove demand, or guarantee differentiation. All examples and proposed metrics below are constructed teaching prompts, not claims about named companies or universal targets. The canvas has six sections. Fill each out with brutal honesty: 1. Target Customer: Who specifically are we building for? (Not \"everyone\" ", "sourceIds": [ "BB-C21-S18", "BB-C21-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-21-product-management-and-product-strategy-2-product-strategy-canvas" ], "url": "index.html#chapter-21-product-management-and-product-strategy-2-product-strategy-canvas" }, { "name": "Product-Market Fit Metrics Dashboard", "id": "chapter-21-product-management-and-product-strategy-3-product-market-fit-metrics-dashboard", "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "chapterSlugs": [ "chapter-21-product-management-and-product-strategy" ], "aliases": [], "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "description": "Product-Market Fit Metrics Dashboard PMF Diagnosis Product-market fit (PMF) is the most critical milestone for any product. Marc Andreessen defined it as being in a good market with a product that can satisfy that market, and emphasized that the signals are often visible in demand, usage, word of mouth, sales cycles, and customer pull. [BB-C21-S03] The Reality: PMF is not binary. It's a spectrum. You can have weak PMF (slow growth, high churn) or strong PMF (demand outpacing your ability to serve it). This dashboard gives you quantitative and qualitative signals, but every numeric threshold should be calibrated against category, business model, and customer segment. Build a dashboard with th", "sourceIds": [ "BB-C21-S03", "BB-C21-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-21-product-management-and-product-strategy-3-product-market-fit-metrics-dashboard" ], "url": "index.html#chapter-21-product-management-and-product-strategy-3-product-market-fit-metrics-dashboard" }, { "name": "Feature Prioritization (RICE)", "id": "chapter-21-product-management-and-product-strategy-4-feature-prioritization-rice", "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "chapterSlugs": [ "chapter-21-product-management-and-product-strategy" ], "aliases": [ "RICE" ], "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "description": "RICE Prioritization Framework Ruthless Prioritization The RICE prioritization framework helps product managers compare feature requests from sales, customers, executives, and engineers. How do you decide what to build? RICE (Reach × Impact × Confidence ÷ Effort) is a prioritization system developed at Intercom to compare ideas through a consistent set of factors. [BB-C21-S05] RICE comparison record (constructed). Use one time horizon, population definition, impact scale, confidence convention, and effort unit across the options being compared. The score makes assumptions visible; it does not authorize shipment. [BB-C21-S05] | Candidate | Reach per quarter | Impact | Confidence | Effort (pers", "sourceIds": [ "BB-C21-S05" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-21-product-management-and-product-strategy-4-feature-prioritization-rice" ], "url": "index.html#chapter-21-product-management-and-product-strategy-4-feature-prioritization-rice" }, { "name": "Product Roadmapping (Now/Next/Later)", "id": "chapter-21-product-management-and-product-strategy-5-product-roadmapping-now-next-later", "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "chapterSlugs": [ "chapter-21-product-management-and-product-strategy" ], "aliases": [ "Now/Next/Later" ], "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "description": "Now/Next/Later Roadmapping Outcome-Focused Planning The Now/Next/Later roadmap makes uncertainty visible when dates and Gantt charts are often treated as stronger commitments than product teams can honestly make. You don't know how long every feature will take, requirements change, and priorities shift. The Now/Next/Later framework, popularized by Janna Bastow at ProdPad, replaces date-driven roadmaps with outcome-focused horizons. [BB-C21-S06] Now/Next/Later decision record (constructed). Horizons communicate evidence and commitment state, not universal calendar windows. Revisit them as learning, capacity, dependencies, obligations, or strategy change. [BB-C21-S06] | Horizon | Decision mean", "sourceIds": [ "BB-C21-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-21-product-management-and-product-strategy-5-product-roadmapping-now-next-later" ], "url": "index.html#chapter-21-product-management-and-product-strategy-5-product-roadmapping-now-next-later" }, { "name": "Product Metrics Hierarchy (North Star Metric)", "id": "chapter-21-product-management-and-product-strategy-6-product-metrics-hierarchy-north-star-metric", "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "chapterSlugs": [ "chapter-21-product-management-and-product-strategy" ], "aliases": [ "North Star Metric" ], "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "description": "Product Metrics Hierarchy (North Star Metric) Organizational Alignment The North Star approach defines one metric intended to represent delivered product value, then links it to a small set of input metrics that the team believes influence it. The resulting structure is a set of assumptions to test, not a proven causal model. [BB-C21-S07] Product-metric hypothesis tree (constructed). A North Star candidate should represent recurring customer value for a defined product and population. Input and guardrail metrics are hypotheses, not proven causal levers. [BB-C21-S07] Figure 21.1. Product-metric hypothesis tree with value and guardrail measures. This author-created visual is a constructed teac", "sourceIds": [ "BB-C21-S07", "BB-C21-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-21-product-management-and-product-strategy-6-product-metrics-hierarchy-north-star-metric" ], "url": "index.html#chapter-21-product-management-and-product-strategy-6-product-metrics-hierarchy-north-star-metric" }, { "name": "Product Discovery Process", "id": "chapter-21-product-management-and-product-strategy-7-product-discovery-process", "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "chapterSlugs": [ "chapter-21-product-management-and-product-strategy" ], "aliases": [], "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "description": "Product Discovery Process Continuous Validation Many teams spend too much time building and too little time discovering what to build. Continuous discovery reframes discovery as an ongoing product habit, not a one-off phase before delivery. [BB-C21-S09] Core Principle: Discover the right product to build, then build it right. Don't build the product, then discover it was wrong. This discovery loop makes the go, pivot, and stop decisions explicit before a solution enters the engineering backlog. Figure 21.2. Product discovery and evidence-gate loop. The author-created diagram moves from an opportunity through alternative solutions and validation to a go, pivot, or stop decision. A “go” means ", "sourceIds": [ "BB-C21-S09", "BB-C21-S10", "BB-C21-S04", "BB-C21-S19", "BB-C21-S25", "BB-C21-S20", "BB-C21-S21", "BB-C21-S22", "BB-C21-S23", "BB-C21-S24", "BB-C21-S27", "BB-C21-S26" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-21-product-management-and-product-strategy-7-product-discovery-process" ], "url": "index.html#chapter-21-product-management-and-product-strategy-7-product-discovery-process" }, { "name": "B2B Product Management", "id": "chapter-21-product-management-and-product-strategy-8-b2b-product-management", "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "chapterSlugs": [ "chapter-21-product-management-and-product-strategy" ], "aliases": [ "B2B" ], "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "description": "B2B Product Management Enterprise Considerations B2B product management differs from B2C because buying roles, workflows, contracts, service obligations, and implementation dependencies can differ. You have fewer customers, longer sales cycles, complex buying committees, and enterprise requirements (security, compliance, integrations). This framework outlines the key differences. - Problem: The person who buys your product (VP of Sales, CIO) is not the person who uses it (sales reps, engineers). - Implication: You must build for two personas: 1. Economic Buyer: Wants ROI, cost savings, scalability, vendor stability 2. End User: Wants ease of use, speed, features that make their job easier - ", "sourceIds": [ "BB-C21-S11" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-21-product-management-and-product-strategy-8-b2b-product-management" ], "url": "index.html#chapter-21-product-management-and-product-strategy-8-b2b-product-management" }, { "name": "Product-Led Growth (PLG) Framework", "id": "chapter-21-product-management-and-product-strategy-9-product-led-growth-plg-framework", "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "chapterSlugs": [ "chapter-21-product-management-and-product-strategy" ], "aliases": [ "PLG" ], "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "description": "Product-Led Growth (PLG) Framework Self-Serve SaaS Strategy Product-Led Growth (PLG) is a go-to-market strategy where the product itself drives customer acquisition, conversion, and expansion. Users discover value before talking to sales. Examples: Slack, Dropbox, Zoom, Calendly, Notion. Core Principle: The product is the primary growth driver, not the sales team or marketing campaigns. 1. Discover: User finds product (organic search, word-of-mouth, viral loop) 2. Activate: User signs up and reaches \"aha moment\" quickly (self-serve onboarding) 3. Adopt: User becomes daily/weekly active, invites teammates 4. Expand: Team grows usage, hits paywall, converts to paid 5. Advocate: Users refer new", "sourceIds": [ "BB-C21-S11" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-21-product-management-and-product-strategy-9-product-led-growth-plg-framework" ], "url": "index.html#chapter-21-product-management-and-product-strategy-9-product-led-growth-plg-framework" }, { "name": "AI Product Management", "id": "chapter-21-product-management-and-product-strategy-10-ai-product-management", "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "chapterSlugs": [ "chapter-21-product-management-and-product-strategy" ], "aliases": [ "AI" ], "concepts": [ "product strategy", "jobs to be done", "RICE", "roadmaps", "product operations", "human-centered design", "inclusive research", "service blueprint", "accessibility-led design", "prototype fidelity" ], "description": "AI Product Management AI-Native Products AI product management addresses products that add probabilistic behavior, data and model dependencies, evaluation needs, and new failure modes; they do not replace software engineering or ordinary product discipline. Test deterministic components with normal unit, integration, system, regression, performance, security, and accessibility methods, and evaluate AI behavior on versioned, representative cases with pre-specified quality, safety, fairness, privacy, security, latency, cost, and business guardrails. [BB-C21-S16] - Software components: may be deterministic or nondeterministic and still require ordinary automated and system testing. - Model beha", "sourceIds": [ "BB-C21-S16", "BB-C21-S17" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-21-product-management-and-product-strategy-10-ai-product-management" ], "url": "index.html#chapter-21-product-management-and-product-strategy-10-ai-product-management" }, { "name": "Pyramid Principle Structure", "id": "chapter-22-data-analysis-and-insights-1-pyramid-principle-structure", "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "chapterSlugs": [ "chapter-22-data-analysis-and-insights" ], "aliases": [], "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "description": "Pyramid Principle Structure Answer-First Communication The Pyramid Principle is a top-down communication structure: state the answer first, then support it with grouped arguments and evidence. Minto's work is widely used in consulting because it helps teams convert messy analysis into a logical executive argument. [BB-C22-S01] The pyramid is not a decoration for slides. It is a forcing mechanism. If you cannot state the answer at the top, the analysis is not ready for a decision. Use the Pyramid Principle when: you are presenting a recommendation to executives; the analysis has multiple workstreams; stakeholders are asking for \"the so what\"; the team is confusing evidence with argument; the ", "sourceIds": [ "BB-C22-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-22-data-analysis-and-insights-1-pyramid-principle-structure" ], "url": "index.html#chapter-22-data-analysis-and-insights-1-pyramid-principle-structure" }, { "name": "SCQ Setup and Answer Structure", "id": "chapter-22-data-analysis-and-insights-2-scq-setup-and-answer-structure", "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "chapterSlugs": [ "chapter-22-data-analysis-and-insights" ], "aliases": [ "SCQ" ], "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "description": "SCQ Setup and Answer Structure Decision Framing Minto names the setup Situation, Complication, Question (SCQ) . The communication then supplies the answer. In this chapter, SCQA is an explicit shorthand for the combined SCQ setup plus answer, not a claim that Minto gave the framework that four-part name. The sequence gives an audience shared context, the tension, the decision question, and the recommendation in a compact structure. [BB-C22-S01] | Element | Purpose | Example | | :--- | :--- | :--- | | Situation | Establish shared context | \"The company has grown revenue across several reporting periods.\" | | Complication | Introduce the tension | \"Gross margin has declined while service cost ", "sourceIds": [ "BB-C22-S01" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-22-data-analysis-and-insights-2-scq-setup-and-answer-structure" ], "url": "index.html#chapter-22-data-analysis-and-insights-2-scq-setup-and-answer-structure" }, { "name": "Correlation vs. Causation Decision Tree", "id": "chapter-22-data-analysis-and-insights-3-correlation-vs-causation-decision-tree", "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "chapterSlugs": [ "chapter-22-data-analysis-and-insights" ], "aliases": [], "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "description": "Correlation vs. Causation Decision Tree Causal Stance Correlation means two things move together. Causation means changing one thing would change another thing. Pearl's structural causal-inference work is one influential source for distinguishing association from intervention logic through explicit assumptions, causal models, confounding, and counterfactual reasoning. [BB-C22-S02] For managers, the practical question is not philosophical. It is this: can we act on the relationship, or should we only use it for prediction and monitoring? Figure 22.1. Routing from association to prediction or causal decision. The author-created tree distinguishes predictive use from intervention claims and rou", "sourceIds": [ "BB-C22-S02" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-22-data-analysis-and-insights-3-correlation-vs-causation-decision-tree" ], "url": "index.html#chapter-22-data-analysis-and-insights-3-correlation-vs-causation-decision-tree" }, { "name": "Statistical Significance Interpretation For Managers", "id": "chapter-22-data-analysis-and-insights-4-statistical-significance-interpretation-for-managers", "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "chapterSlugs": [ "chapter-22-data-analysis-and-insights" ], "aliases": [], "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "description": "Statistical Significance Interpretation for Managers Uncertainty and Practical Value Statistical significance is often misused in business settings. The ASA statement on p-values says a p-value is not the probability that the hypothesis is true, is not the probability that the result occurred by chance alone, and should not be used as a bright-line substitute for scientific or practical reasoning. [BB-C22-S03] For managers, the goal is not to become a statistician. The goal is to ask the right questions before turning a test result into a decision. 1. Is the effect real enough? Look at uncertainty and design quality. 2. Is the effect big enough? Compare effect size with the business threshol", "sourceIds": [ "BB-C22-S03" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-22-data-analysis-and-insights-4-statistical-significance-interpretation-for-managers" ], "url": "index.html#chapter-22-data-analysis-and-insights-4-statistical-significance-interpretation-for-managers" }, { "name": "Regression Analysis Interpretation Guide", "id": "chapter-22-data-analysis-and-insights-5-regression-analysis-interpretation-guide", "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "chapterSlugs": [ "chapter-22-data-analysis-and-insights" ], "aliases": [], "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "description": "Regression Analysis Interpretation Guide Model Translation Regression analysis estimates relationships between an outcome and one or more predictors. Gelman and Hill present regression as an applied modeling tool that must be interpreted with research design, model assumptions, and substantive meaning in view. [BB-C22-S04] First declare the task. A model optimized for prediction is evaluated on out-of-sample performance, calibration, leakage, decision loss, subgroup behavior, robustness, and distribution shift. A model used for coefficient inference needs a defensible sampling/design and uncertainty model. A regression used for causal estimation additionally needs an identification strategy ", "sourceIds": [ "BB-C22-S04" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-22-data-analysis-and-insights-5-regression-analysis-interpretation-guide" ], "url": "index.html#chapter-22-data-analysis-and-insights-5-regression-analysis-interpretation-guide" }, { "name": "Data Visualization Best Practices", "id": "chapter-22-data-analysis-and-insights-6-data-visualization-best-practices", "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "chapterSlugs": [ "chapter-22-data-analysis-and-insights" ], "aliases": [], "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "description": "Data Visualization Best Practices Visual Decision Support Data visualization helps people compare, diagnose, and decide. Tufte's work emphasizes graphical integrity, data density, small multiples, and avoiding visual distortion, while Few's work translates table and graph design into practical business communication. [BB-C22-S05] [BB-C22-S06] The purpose of a visualization is not to look sophisticated. The purpose is to make the comparison obvious without hiding uncertainty or context. | Analytical Need | Use | Avoid | | :--- | :--- | :--- | | Trend over time | Line chart | Pie chart | | Compare categories | Sorted bar chart | Unsorted decorative chart | | Show distribution | Histogram, box ", "sourceIds": [ "BB-C22-S05", "BB-C22-S06" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-22-data-analysis-and-insights-6-data-visualization-best-practices" ], "url": "index.html#chapter-22-data-analysis-and-insights-6-data-visualization-best-practices" }, { "name": "KPI Tree Structure", "id": "chapter-22-data-analysis-and-insights-7-kpi-tree-structure", "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "chapterSlugs": [ "chapter-22-data-analysis-and-insights" ], "aliases": [ "KPI" ], "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "description": "KPI Tree Structure Metrics and Guardrails A KPI tree is a practical author synthesis that decomposes a top-level outcome into hypothesized drivers, sub-drivers, controllable operating metrics, and guardrails. Kaplan and Norton's balanced-scorecard work supports linked, balanced measures, but the exact tree and every arrow below are hypotheses to validate rather than canonical causal structure. [BB-C22-S07] A good KPI tree does not merely display metrics. It shows how the business works. Figure 22.2. Constructed KPI hypothesis tree for profitable growth. The diagram links a strategic outcome to financial and operating measures. Each arrow is a proposed relationship to define, measure, and tes", "sourceIds": [ "BB-C22-S07" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-22-data-analysis-and-insights-7-kpi-tree-structure" ], "url": "index.html#chapter-22-data-analysis-and-insights-7-kpi-tree-structure" }, { "name": "Benchmarking Framework", "id": "chapter-22-data-analysis-and-insights-8-benchmarking-framework", "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "chapterSlugs": [ "chapter-22-data-analysis-and-insights" ], "aliases": [], "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "description": "Benchmarking Framework Comparable Performance Benchmarking compares performance, practices, or capabilities against a relevant reference group. APQC's Benchmarking Basics is a current institutional resource for launching a benchmarking initiative; it brings together materials for planning, collection, analysis, adaptation, partner selection, and data normalization. [BB-C22-S08] Benchmarking is useful when it creates a learning agenda. It is dangerous when it becomes status theater. These practical cautions are an author synthesis for decision use, not claims of an average performance benefit. [BB-C22-S08] | Type | Comparison Target | Best Use | | :--- | :--- | :--- | | Internal | Teams, regi", "sourceIds": [ "BB-C22-S08" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-22-data-analysis-and-insights-8-benchmarking-framework" ], "url": "index.html#chapter-22-data-analysis-and-insights-8-benchmarking-framework" }, { "name": "Sensitivity Analysis Grid", "id": "chapter-22-data-analysis-and-insights-9-sensitivity-analysis-grid", "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "chapterSlugs": [ "chapter-22-data-analysis-and-insights" ], "aliases": [], "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "description": "Sensitivity Analysis Grid Decision Robustness Sensitivity analysis asks how much the decision changes when key assumptions move. Saltelli and coauthors frame sensitivity analysis as a way to understand how uncertainty in model inputs affects model outputs. [BB-C22-S09] Managers should use sensitivity analysis before arguing about precision. If the decision is robust across plausible assumptions, you can move faster. If the decision flips, you need better information or a more reversible plan. | Assumption | Base Case | Downside Case | Upside Case | Decision Sensitivity | Action | | :--- | :--- | :--- | :--- | :--- | :--- | | Adoption speed | Medium | Slow | Fast | High | Pilot before scale |", "sourceIds": [ "BB-C22-S09" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-22-data-analysis-and-insights-9-sensitivity-analysis-grid" ], "url": "index.html#chapter-22-data-analysis-and-insights-9-sensitivity-analysis-grid" }, { "name": "Monte Carlo Simulation Setup", "id": "chapter-22-data-analysis-and-insights-10-monte-carlo-simulation-setup", "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "chapterSlugs": [ "chapter-22-data-analysis-and-insights" ], "aliases": [], "concepts": [ "pyramid principle", "SCQA", "correlation vs causation", "regression interpretation", "KPI trees", "sensitivity analysis", "expected monetary value", "expected utility", "Bayesian updating", "value of information", "break-even probability", "estimand", "minimum detectable effect", "experiment power", "sequential testing", "multiple testing", "spillover effects", "linear programming", "mixed-integer optimization", "shadow price" ], "description": "Monte Carlo Simulation Setup Risk Ranges and Scenarios Monte Carlo simulation models uncertainty by assigning ranges or distributions to uncertain inputs, running many simulated outcomes, and examining the resulting range of possible outputs. Hubbard's measurement work uses Monte Carlo thinking to make uncertain business cases more decision-ready, while sensitivity-analysis sources clarify how input uncertainty propagates through model outputs. [BB-C22-S10] [BB-C22-S09] Use Monte Carlo when a single base case hides too much risk. Figure 22.3. Monte Carlo decision-model workflow. The author-created flow moves from a deterministic decision model through uncertain inputs, distributions and depe", "sourceIds": [ "BB-C22-S10", "BB-C22-S09" ], "provenanceStatus": "source-linked", "toolIds": [], "backlinks": [ "index.html#chapter-22-data-analysis-and-insights-10-monte-carlo-simulation-setup" ], "url": "index.html#chapter-22-data-analysis-and-insights-10-monte-carlo-simulation-setup" } ], "figures": [ { "id": "chapter-01-macroeconomics-for-strategic-leaders-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C01-S02", "BB-C01-S04", "BB-C01-S14" ], "provenanceStatus": "constructed", "checksum": "f33c49b5827df211cde0e63ed5b1292a285352642c53d6cc051b6ad391b2f87d", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-figure-2", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C01-S05" ], "provenanceStatus": "constructed", "checksum": "0cdb496696694777e83f84e7f9ec048cf358e7ee9e6b8c6942bdc93a07acefbd", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-02-business-law-governance-and-ethics-figure-1", "type": "mermaid", "caption": "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].", "textEquivalent": "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.", "sourceIds": [ "BB-C02-S07" ], "provenanceStatus": "constructed", "checksum": "f004f7cc9a78bb57a7244c9d6696479e11c3757572483f1ccab95bbb2f65ca14", "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-02-business-law-governance-and-ethics-figure-2", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C02-S11" ], "provenanceStatus": "constructed", "checksum": "45f4fef0ac3b279cb7745296ea8fca72a978bdb076ac9d7d66443e212e2cac7f", "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-02-business-law-governance-and-ethics-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C02-S08", "BB-C02-S09" ], "provenanceStatus": "constructed", "checksum": "b904c0bd71eba1078a3054ae39d7995971c6cb08bd12731dcaacf0e13650ecb6", "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-02-business-law-governance-and-ethics-figure-4", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "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" ], "provenanceStatus": "constructed", "checksum": "20d6ef9280b14f7716d012036fd4aaa3687a3f4c4eaaa0cb2161625c8a842489", "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S06" ], "provenanceStatus": "constructed", "checksum": "00be95f36150dd80701080547e0a7cc994d6545a0c17037804f779c5d6cb731b", "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-2", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S07" ], "provenanceStatus": "constructed", "checksum": "a07ab2b2c983145d69563bd6b34e0ad2ddade7bfd68d23fe0f26d511e0edc916", "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S08" ], "provenanceStatus": "source-linked", "checksum": "a32505c251e4c1f9768b745063957b8d8dc8bec96a40f0acb80cf2f3f8d65551", "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-4", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S09" ], "provenanceStatus": "source-linked", "checksum": "389a685f92794d2edd58bba27abaac53ece2d522837abac8c09037296874b098", "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-5", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S10" ], "provenanceStatus": "constructed", "checksum": "9c0318cb62b7fb4d1c71f9ec7fc750453b08fbbf4edb9118266ad6571bd1d19e", "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-6", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S11" ], "provenanceStatus": "constructed", "checksum": "6b1e655889967b7b98409125d010fbe9613d4475e4897928e81a3964503dbf1b", "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-7", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S13" ], "provenanceStatus": "constructed", "checksum": "6a5882d0b22d8cb3ddb79fe06fbcc2d19a10a74e1ac8b60d0eb78e354ac97be7", "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-8", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S14" ], "provenanceStatus": "constructed", "checksum": "dfa6236841a1b38b946f92e77f9d7a4429a44b3f39407f45b703e14e21dc7cbd", "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-figure-9", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C03-S20", "BB-C03-S21", "BB-C03-S23", "BB-C03-S28" ], "provenanceStatus": "constructed", "checksum": "ba9e8ff3708ad0dbaee8e89994997927c68425b0fecf5c73e0a312c06fc8bf82", "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S17", "BB-C04-S18", "BB-C04-S19" ], "provenanceStatus": "constructed", "checksum": "78c394d58486df55c7ed48742028cf176517fb8182813dd7948640ed02b52536", "entrySlug": "chapter-04-financial-analysis-and-valuation" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-2", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S23" ], "provenanceStatus": "constructed", "checksum": "1d0f346d0fb594fc363773c93f9db44396609c25b3ac1530d5e9494df78ca032", "entrySlug": "chapter-04-financial-analysis-and-valuation" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S13" ], "provenanceStatus": "constructed", "checksum": "4a161065b44bbcc3b5453060947538e4faf30bec4e96572bab2b58d27b8b059d", "entrySlug": "chapter-04-financial-analysis-and-valuation" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-4", "type": "mermaid", "caption": "Figure 4.4. DuPont decomposition of return on equity. The branches are multiplicative accounting components, not a causal tree. [BB-C04-S06]", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S06" ], "provenanceStatus": "constructed", "checksum": "a6a81d9a1973acc7961b7666f2eff1226716d2a72d7db6afab391ee9b01ca673", "entrySlug": "chapter-04-financial-analysis-and-valuation" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-5", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S07" ], "provenanceStatus": "source-linked", "checksum": "c31487e8857203360925d836f0aaba1e6d95a6d2fd3863edf595bd21334606bc", "entrySlug": "chapter-04-financial-analysis-and-valuation" }, { "id": "chapter-04-financial-analysis-and-valuation-figure-6", "type": "svg", "caption": "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].", "textEquivalent": "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.", "sourceIds": [ "BB-C04-S14" ], "provenanceStatus": "constructed", "checksum": "8383750ff45d64f0c35efbd050df7da9d0ed36a64b8ee34132da413cf1b08f74", "entrySlug": "chapter-04-financial-analysis-and-valuation" }, { "id": "chapter-05-marketing-and-customer-analytics-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C05-S11" ], "provenanceStatus": "constructed", "checksum": "0f5e0ec1b0ef1a37dd2fd28e8fb2b4ca03ef7f7b5170ecc4e441e57123445a2b", "entrySlug": "chapter-05-marketing-and-customer-analytics" }, { "id": "chapter-05-marketing-and-customer-analytics-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C05-S08" ], "provenanceStatus": "constructed", "checksum": "efac505357a9d253aca5b05f9d9a697df1c041ac02c2c7b1ba142619e83fbd5e", "entrySlug": "chapter-05-marketing-and-customer-analytics" }, { "id": "chapter-05-marketing-and-customer-analytics-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C05-S10" ], "provenanceStatus": "source-linked", "checksum": "1ef1ee78f9c5cc27586300a2432d43586fcc258b28321fd1f49532db4aa6a082", "entrySlug": "chapter-05-marketing-and-customer-analytics" }, { "id": "chapter-05-marketing-and-customer-analytics-figure-4", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C05-S18", "BB-C05-S19", "BB-C05-S20", "BB-C05-S15" ], "provenanceStatus": "constructed", "checksum": "0dd59bb4885f47c5e3baf2171f5058c91d31f74ed25cbb091e4ae7b36cb9394f", "entrySlug": "chapter-05-marketing-and-customer-analytics" }, { "id": "chapter-05-marketing-and-customer-analytics-figure-5", "type": "mermaid", "caption": "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]", "textEquivalent": "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]", "sourceIds": [ "BB-C05-S22", "BB-C05-S23", "BB-C05-S24" ], "provenanceStatus": "constructed", "checksum": "41e0a451fcb19cd1476ea60bab587c2f0a55823d6b248c23f868b3c57e520f45", "entrySlug": "chapter-05-marketing-and-customer-analytics" }, { "id": "chapter-06-operations-and-supply-chain-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S11" ], "provenanceStatus": "constructed", "checksum": "64c532e4640a433fb91531b774816e494d88f257cff4311acb3c46e0c159b7d2", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S11" ], "provenanceStatus": "constructed", "checksum": "7dd703e389b15ba022eab14619939f5570a83ca2c502eb8ec52c2b06dfc44bb9", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S06" ], "provenanceStatus": "constructed", "checksum": "32411847a1f3f18c299b82e306bed8e304d723a8f8f000b72e402d9ef64aad7a", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-4", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S03", "BB-C06-S04" ], "provenanceStatus": "constructed", "checksum": "e3d77c30d5d9f81a0dcd8194f94a70ef32fda308b53ef4e479f1550264e18bb2", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-5", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S03", "BB-C06-S04" ], "provenanceStatus": "constructed", "checksum": "c691bdad9b6592d8cde63b383439ae72acdfb1fabad437c4283a0e3dcac62bff", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-6", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S03", "BB-C06-S04" ], "provenanceStatus": "constructed", "checksum": "75efe5aad7b45d7bc5a1bfc7cfef306870ac04133399240a6169a78f3dc05e57", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-7", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S01", "BB-C06-S07" ], "provenanceStatus": "constructed", "checksum": "49b2e777969bce4ba9082e314997871f9b0d80967e62bd84d2999d32efb33f44", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-8", "type": "mermaid", "caption": "Figure 6.8. Constructed supply-chain risk triage matrix. The anonymous positions are discussion prompts, not measured probabilities, expected losses, or automatic action rules.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "05946a57603fbc2c4cceffad6ffebfd5e384a206d7729465b5a3a4790c6898e7", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-9", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S08" ], "provenanceStatus": "constructed", "checksum": "9f926373d61eec354ae0600df8f27edb117dfeadb5b5244b83443acf0ad299f2", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-10", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S09" ], "provenanceStatus": "constructed", "checksum": "b819e891b4be3ac818654d78620ed2b8170d4b2c0a6c9d610e72db6fc07c33c6", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-11", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S10" ], "provenanceStatus": "constructed", "checksum": "78ea13f4a62e7f94c3b2d60b1ccc612e12b5a4ee346bea7493d3769466ea4d62", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-12", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S12" ], "provenanceStatus": "constructed", "checksum": "50c80610176fdfb511e7e2633e3194ee8c9965829bb200a228a16306c8d46377", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-13", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S12" ], "provenanceStatus": "constructed", "checksum": "3d8eadcbb18a66ea4350243ba6bb1781f75a5e8db56f2798e6f9d4fb83e1cf75", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-figure-14", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C06-S15", "BB-C06-S16" ], "provenanceStatus": "constructed", "checksum": "0554ea829b2edda0f1fcd39adae4bbfa2808b0166298c65b5e087b72d1ba9ca2", "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-07-organizational-behavior-and-leadership-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C07-S01" ], "provenanceStatus": "constructed", "checksum": "d3b6a56e2557c96bbb8482fcf577ea6cacfb824bf0c4fbfa7aaa4c3a6903a812", "entrySlug": "chapter-07-organizational-behavior-and-leadership" }, { "id": "chapter-07-organizational-behavior-and-leadership-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C07-S08" ], "provenanceStatus": "constructed", "checksum": "0056678397d0efd8a32f014139df9f3a64fe0e5bc5a24224db5a3620a9462404", "entrySlug": "chapter-07-organizational-behavior-and-leadership" }, { "id": "chapter-07-organizational-behavior-and-leadership-figure-3", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C07-S20" ], "provenanceStatus": "constructed", "checksum": "d9cfbe464aa7e9fa02a41e5edee113344b76497bfee121b9d4ab1e47141ea53f", "entrySlug": "chapter-07-organizational-behavior-and-leadership" }, { "id": "chapter-07-organizational-behavior-and-leadership-figure-4", "type": "mermaid", "caption": "Figure 7.4. Constructed evidence-gated negotiation preparation.", "textEquivalent": "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.", "sourceIds": [ "BB-C07-S13", "BB-C07-S14" ], "provenanceStatus": "constructed", "checksum": "52233a0d7e8aca81b0a23d85871eb607a41c9361089183d86829ad7b4c7ee155", "entrySlug": "chapter-07-organizational-behavior-and-leadership" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C08-S04", "BB-C08-S05", "BB-C08-S06", "BB-C08-S01" ], "provenanceStatus": "constructed", "checksum": "6d3dc2c9d99afa1b9c0364e5a9dfd6ab610388797ee4ff3571f587868e4b0837", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-figure-2", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C08-S01", "BB-C08-S06" ], "provenanceStatus": "constructed", "checksum": "d694a7c6475a887be69bbc14c0579db6eddc5709c25303a6b2703507a2d6259b", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" }, { "id": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis-figure-3", "type": "mermaid", "caption": "Figure 8.3. Balanced Scorecard strategy hypotheses. The arrows are relationships to test, not established causal chains or guaranteed financial outcomes. [BB-C08-S03]", "textEquivalent": "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.", "sourceIds": [ "BB-C08-S03" ], "provenanceStatus": "constructed", "checksum": "6ff232a86e7fc859428493859acd9731a9c5633b372488c453b985436adf3b9f", "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" }, { "id": "chapter-09-problem-structuring-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "dffaefdcf6323d4fc1181078ffcde3c1462b997dcc434bad1561913797b99344", "entrySlug": "chapter-09-problem-structuring" }, { "id": "chapter-09-problem-structuring-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C09-S01" ], "provenanceStatus": "source-linked", "checksum": "0763cef4c633a20e7e282073f2f16346aa09616f0f35506437712ea083cdafef", "entrySlug": "chapter-09-problem-structuring" }, { "id": "chapter-09-problem-structuring-figure-3", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "b9af2796790878a136d9ffcffdecdbb9cf0e5cbcaa48a8a139f76bf23146e35d", "entrySlug": "chapter-09-problem-structuring" }, { "id": "chapter-09-problem-structuring-figure-4", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C09-S05" ], "provenanceStatus": "source-linked", "checksum": "9d1a1a367dcd5c115e9de3f6319f0584d1e889012df582cbab2abc9385fc4971", "entrySlug": "chapter-09-problem-structuring" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "1225ee9e993ba6df0564c85ac5608e102569ba7976ee2d7ab75a041fe621ffe6", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-figure-2", "type": "mermaid", "caption": "Figure 10.2 — Business-model hypothesis system. The nine blocks are shown as an evidence flow rather than a copied branded-canvas layout.", "textEquivalent": "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.", "sourceIds": [ "BB-C10-S03" ], "provenanceStatus": "constructed", "checksum": "076271038c201102f38969530119f3a8b44febda6caf0528a8451545b6668882", "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration" }, { "id": "chapter-11-project-management-and-pmp-frameworks-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "50e029de68c9b82cfb71d7b52f1e2fd002d28ac38d6a007d8f1b8222edb4039c", "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-figure-2", "type": "mermaid", "caption": "Figure 11.2 — Constructed CPM dependency network. Numbers in parentheses are durations in weeks.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "d6b2ddbe023f3a0866dc35f8466b950e03fcfab122e1ae77e5aba89f30157597", "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C11-S01" ], "provenanceStatus": "constructed", "checksum": "cb72e1f44888d2ace8f678ea3d3fb4d97cae22866b4fc1dd6f1dc0244129165c", "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-figure-4", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C11-S01" ], "provenanceStatus": "constructed", "checksum": "e95fc7420359e0ccd0603003585ab1b6ac4a545a3ca73c81463ab32b8044f7a0", "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-12-client-management-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C12-S05" ], "provenanceStatus": "source-linked", "checksum": "c3638bbe285bf93bbf7bd238b2678c8a6533ff454c97f7c3efa6e176dc3d493b", "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [ "BB-C12-S03" ], "provenanceStatus": "constructed", "checksum": "44e0ac91fcfa28cdad515ca590fb9c5f7d6f95ee0e06dc6a411b7eca6ca85a5d", "entrySlug": "chapter-12-client-management" }, { "id": "chapter-13-startup-foundations-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C13-S01" ], "provenanceStatus": "source-linked", "checksum": "92f62aa7965b7e06ad46a9f06b46bfc1dce03bbe376cded44a44fe5f506a303f", "entrySlug": "chapter-13-startup-foundations" }, { "id": "chapter-13-startup-foundations-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "c4a22438bb907aa0fbba84c02fced3feaf4bb48253fa4120d7766a4d1557667f", "entrySlug": "chapter-13-startup-foundations" }, { "id": "chapter-14-go-to-market-strategy-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "b6790cb8c84a3c3e5cce70a2873a47eaae5cc0524225ba2fcee1264598603bed", "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "8fd3ff383dfaa8bd812fe44f290849054992f0d39091414571976ca839322765", "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-figure-3", "type": "mermaid", "caption": "Figure 14.3: Evidence-gated market-entry choice (constructed). This is a decision aid, not a prediction model.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "a96d4ea3006290ba4cbc7d46293b34438cddb5baca3251bee0b2114164a270f6", "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-figure-4", "type": "mermaid", "caption": "Figure 14.4: International-entry evidence and exit loop (constructed).", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "7cc47058b37683c0cfc5211b9b85527ecedd89edaa1e5c1f3fcfd57ce51a5a68", "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-15-fundraising-and-finance-figure-1", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "393c2470b3266e4b0988a46e21b2d1fe12db70cf98f56bf0f27c5919223e6f80", "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "e7db68afb5585d9743b47007f433fe9798fd11d11842ceccccd6cef6e78aea20", "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-figure-3", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "4c799d1c8d2061ce448241d5384cdce4cb6022b3c8c27c8d74f9fb2818c13298", "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-figure-1", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C16-S01", "BB-C16-S06", "BB-C16-S08" ], "provenanceStatus": "constructed", "checksum": "c04a56020c689abb1abe6291af183bf85fa6ab7836a08101d35ed13201bc53da", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-figure-2", "type": "mermaid", "caption": "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.", "textEquivalent": "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.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "45fda5dc723ea3a8c8f1416ce469f780ea2fb6bb7d3ecd2ae2d69e1c7d7b6f46", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-figure-3", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C16-S09", "BB-C16-S10" ], "provenanceStatus": "constructed", "checksum": "1a9bd0ef79e8d00f248e1df089526126a2b089664cbeb248de7a1ec2db3de50b", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-figure-4", "type": "mermaid", "caption": "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]", "textEquivalent": "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.", "sourceIds": [ "BB-C16-S01", "BB-C16-S04", "BB-C16-S10", "BB-C16-S14" ], "provenanceStatus": "constructed", "checksum": "c8142facdb9b86259c48eb20a08284813d7c59c5c3568aaaf3a6f3545718381a", "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions" }, { "id": "chapter-17-leading-digital-transformation-figure-1", "type": "mermaid", "caption": "Figure 17.1. Transformation portfolio learning loop. The diagram shows a reusable sequence for framing, testing, scaling, embedding, and re-evaluating an initiative; arrows do not imply a universal order or duration. Source basis: digital transformation leadership and maturity framing, adapted as an author planning aid. [BB-C17-S01] [BB-C17-S06]", "textEquivalent": "Text equivalent: Leaders frame a capability hypothesis, run a bounded test, scale only when business, technical, adoption, workforce, security, and governance gates are met, embed the capability in operations, and then optimize, retire, or return to a revised hypothesis.", "sourceIds": [ "BB-C17-S01", "BB-C17-S06" ], "provenanceStatus": "source-linked", "checksum": "fa2c1d05ef2fd29c2c888011a5a1ee21d30872dfd72793e4de5456e383248c02", "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-figure-2", "type": "mermaid", "caption": "Figure 17.2. Rogers adopter-category shares with Moore's chasm overlaid. Rogers's approximate ideal-type shares are shown as a sequence, while Moore's chasm is a later commercial-market interpretation between early adopters and the early majority. The overlay is a teaching synthesis, not a universal adoption trajectory. [BB-C17-S03] [BB-C17-S04]", "textEquivalent": "Text equivalent: The figure moves from innovators to early adopters, crosses a highlighted conceptual gap, and then proceeds to early majority, late majority, and laggards. The categories describe a population-level diffusion model and should not be used to stereotype individuals.", "sourceIds": [ "BB-C17-S03", "BB-C17-S04" ], "provenanceStatus": "source-linked", "checksum": "c49f1dccd637b7f7c4a0ba2ccf7a398b62a91e3af9fec7a2e37172e7b821825d", "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-figure-3", "type": "mermaid", "caption": "Figure 17.3. Evidence-to-roadmap maturity loop. The author-created loop connects dimensions, evidence-based current state, target capabilities, gaps, portfolio choices, funding, and reassessment. A score is a discussion input, not an outcome measure. Source basis: digital-maturity research. [BB-C17-S06]", "textEquivalent": "Text equivalent: Define context-specific dimensions; assess current capabilities with evidence and uncertainty; define only the target capabilities needed by strategy; identify gaps; compare initiatives and dependencies; fund a roadmap; then reassess both capability and realized value.", "sourceIds": [ "BB-C17-S06" ], "provenanceStatus": "constructed", "checksum": "a6de4d220fa1a8f1f1f0a2061125ad332f3ad5116d0c445745adb59373d310a1", "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-figure-4", "type": "mermaid", "caption": "Figure 17.4. Digital operating-model feedback system. The author-created diagram links strategy, governance forums, product teams, decision rights, delivery, outcomes, and feedback. It is a relationship map, not a prescribed organization chart. Source basis: IT-governance decision-rights research. [BB-C17-S07]", "textEquivalent": "Text equivalent: Strategy informs both governance forums and delivery teams. Governance allocates decision rights; teams deliver within those boundaries. Outcomes and control evidence feed back into strategy, funding, standards, and team design.", "sourceIds": [ "BB-C17-S07" ], "provenanceStatus": "constructed", "checksum": "15a09d84eb546587f3a5cafd95137e75c53ca55f71c1e2d09f831324427b1281", "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-figure-5", "type": "mermaid", "caption": "Figure 17.5. Digital-service lifecycle boundary, decision loop, and claims gate. This author-created visual places operational data-center impacts inside a broader system of hardware, supply chain, networks, devices, use, and end of life. It also separates an internal decision estimate from an external environmental claim and makes demand rebound visible. It is a boundary prompt, not a calculation method or verified footprint. [BB-C17-S12] [BB-C17-S13] [BB-C17-S14] [BB-C17-S17] [BB-C17-S19] [BB-C17-S20]", "textEquivalent": "Text equivalent: Define the service outcome and demand scenarios, then inventory materials and manufacturing, data-center operation, networks, end-user devices, and maintenance or end of life across operational energy, carbon, water, and material impacts. Allocate shared systems and test uncertainty. Efficiency may lower cost or latency and increase demand, so compare both intensity and absolute totals. The resulting estimate can inform a redesign, stage, cap, procure, monitor, or stop decision; any external environmental claim passes through a separate substantiation, qualification, legal, assurance, and approval gate.", "sourceIds": [ "BB-C17-S12", "BB-C17-S13", "BB-C17-S14", "BB-C17-S17", "BB-C17-S19", "BB-C17-S20", "BB-C17-S21" ], "provenanceStatus": "constructed", "checksum": "9984d399062311a2ba224b636c27b4b0acb42df2aaeb68e58ce5b3e1f3b595aa", "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-18-digital-business-models-and-platform-economics-figure-1", "type": "mermaid", "caption": "Figure 18.1. Platform interaction and learning loop. The author-created diagram links relevant supply, matching, trusted transaction, repeat demand, and data-informed improvement. It is a hypothesis map, not a causal guarantee. Source basis: platform and multisided-market strategy. [BB-C18-S01] [BB-C18-S03] [BB-C18-S06]", "textEquivalent": "Text equivalent: Relevant supply enables discovery and matching; a trusted transaction may create repeat demand; transaction evidence can improve matching. Each link must be tested, and negative effects such as congestion, low quality, fraud, discrimination, or exit can weaken or reverse the loop.", "sourceIds": [ "BB-C18-S01", "BB-C18-S03", "BB-C18-S06" ], "provenanceStatus": "constructed", "checksum": "ec1192d03a772cdfe49b45ceb8cfa02f01fb63b50989073e695c71edd12076f2", "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-18-digital-business-models-and-platform-economics-figure-2", "type": "mermaid", "caption": "Figure 18.2. Platform-regulation and complementor decision route (constructed). The route separates scope, current legal evidence, technical/product facts, strategic consequences, and accountable approval. It does not infer that the DMA applies or prescribe a legal conclusion. [BB-C18-S16] [BB-C18-S17] [BB-C18-S18]", "textEquivalent": "Text equivalent: Define the jurisdiction, entity, role, service, and user journey. Check current legislation, designation and service decisions, compliance measures, enforcement, and appeals. Map the actual product flow and data practice to potentially relevant obligations with legal and technical owners. Model strategic and economic consequences, choose redesign, request, negotiate, launch, stage, challenge, or stop, and monitor for changes.", "sourceIds": [ "BB-C18-S16", "BB-C18-S17", "BB-C18-S18" ], "provenanceStatus": "constructed", "checksum": "4267e80254dcc32dbb3ace0d301bbdb8a1c61d52f7022dddb89d2e4ecd7b32d6", "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-figure-1", "type": "mermaid", "caption": "Figure 19.1. Classic Cyber Defense Matrix with a CSF 2.0 Govern overlay. The five operational rows preserve the source taxonomy; Govern is added as an outer layer affecting every asset and operational Function. [BB-C19-S01] [BB-C19-S06]", "textEquivalent": "Text equivalent: Devices, applications, networks, data, and users are considered across Identify, Protect, Detect, Respond, and Recover. A separate Govern layer sets context, strategy, roles, policy, oversight, and supply-chain governance for all cells. Empty cells are prompts for risk analysis, not automatic control purchases.", "sourceIds": [ "BB-C19-S01", "BB-C19-S06" ], "provenanceStatus": "source-linked", "checksum": "749b4a5dca006d84c468bd20c6e78defd33d0c343dbd022bf288293145893cc9", "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-20-the-ethics-of-ai-and-data-figure-1", "type": "mermaid", "caption": "Figure 20.1. Fairness evidence and remediation loop. The author-created loop connects data review, model design, fairness evaluation, deployment, outcome audit, and renewed investigation. It does not imply that one metric, mitigation, or “no bias detected” result establishes fairness. Source basis: fairness trade-off and measurement literature. [BB-C20-S04]", "textEquivalent": "Text equivalent: Data and model choices are evaluated before deployment; real-world outcomes are audited after deployment. A material disparity or harm signal routes back to problem, data, model, threshold, workflow, and institutional review. An apparently acceptable result continues monitoring, participation, appeal, and remedy rather than closing the issue.", "sourceIds": [ "BB-C20-S04" ], "provenanceStatus": "constructed", "checksum": "c0f294d2305de3f965ce44b162d83ed354c1d065325fbecd8751aee52bc2e0b7", "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-figure-2", "type": "mermaid", "caption": "Figure 20.2. Explanation, notice, contestability, and recourse routing. The author-created tree begins with impact and automation, then routes to current legal review, audience-appropriate information, validated explanation, correction or appeal, and monitoring. [BB-C20-S03]", "textEquivalent": "Text equivalent: For a lower-impact decision, provide proportionate transparency and monitor feedback. For a consequential or solely automated decision, qualified owners first determine applicable duties and stakeholder needs; they then validate the explanation method, provide accessible correction or appeal where required or justified, and monitor whether the process works.", "sourceIds": [ "BB-C20-S03" ], "provenanceStatus": "constructed", "checksum": "6bbb7067dd4dd7eb372d8e3c19a280ca18304279c67b76090fbc2c5919ea343c", "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-figure-3", "type": "mermaid", "caption": "Figure 20.3. AI ethics and accountability lifecycle. The author-created diagram connects problem definition, data, model, testing, deployment, monitoring, maintenance, and retirement, with monitoring able to reopen earlier decisions. It does not imply that passage through stages establishes ethical acceptability or legal compliance. Source basis: AI risk-management and end-to-end accountability practice. [BB-C20-S01] [BB-C20-S07]", "textEquivalent": "Text equivalent: A proposed use is assessed before data and model work; evidence is tested before release; deployed systems are monitored for business, fairness, privacy, safety, security, labor, environmental, agency, complaint, appeal, and remedy signals; material findings or changes route back to the relevant earlier decision; retirement includes data, access, notice, dependency, records, and ongoing-remedy obligations.", "sourceIds": [ "BB-C20-S01", "BB-C20-S07" ], "provenanceStatus": "constructed", "checksum": "a1683f39ff2a72daf8e6398490f8ed918f81abe891e5f22039b5e85b9d93f21c", "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-21-product-management-and-product-strategy-figure-1", "type": "mermaid", "caption": "Figure 21.1. Product-metric hypothesis tree with value and guardrail measures. This author-created visual is a constructed teaching aid; it does not establish that any input causes the North Star outcome or that one metric hierarchy fits every product. [BB-C21-S07]", "textEquivalent": "Text equivalent: Begin with a candidate recurring customer-value outcome. Map a small set of behavioral or operational inputs that might influence it and add quality, safety, accessibility, trust, financial, and system guardrails. Test definitions, causal assumptions, segment behavior, gaming risk, and unintended effects before using the tree for decisions.", "sourceIds": [ "BB-C21-S07" ], "provenanceStatus": "constructed", "checksum": "e26066481e49d9b993f50afde91f13335d2297e8cbf85f975eeb1cc48606ccaf", "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-21-product-management-and-product-strategy-figure-2", "type": "mermaid", "caption": "Figure 21.2. Product discovery and evidence-gate loop. The author-created diagram moves from an opportunity through alternative solutions and validation to a go, pivot, or stop decision. A “go” means the evidence is sufficient for the next bounded commitment, not that the product will succeed. Source basis: continuous-discovery practice. [BB-C21-S09]", "textEquivalent": "Text equivalent: A team defines an opportunity, explores multiple solutions, tests value, usability, feasibility, viability, accessibility, ethics, safety, security, strategy, and capacity, then either moves a bounded option to delivery, returns to exploration with a revised hypothesis, or archives the learning. Post-release evidence can reopen discovery.", "sourceIds": [ "BB-C21-S09" ], "provenanceStatus": "constructed", "checksum": "bfde7a6724f5b2b92802a91c891aedcc9d37c8f1bf18b0e3ef7539f602765f8a", "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-21-product-management-and-product-strategy-figure-3", "type": "mermaid", "caption": "Figure 21.3. Accessible service blueprint for a constructed lost-credential replacement service. This author-created process visual shows evidence, user actions, visible frontstage interactions, hidden backstage work, and support capabilities across four stages. It is an illustrative teaching model, not a depiction of an actual organization or a reproduction of the cited article's figures. [BB-C21-S25]", "textEquivalent": "Text equivalent: The user finds accessible guidance, submits a replacement request, responds to any clarification, and receives an outcome with recovery options. Visible channels provide guidance, validation, status, and help. Behind the line of visibility, the service creates a case, checks records, makes and logs a decision, and handles exceptions. Content, identity, case-management, notification, accessibility, staff, and governance capabilities support every stage.", "sourceIds": [ "BB-C21-S25" ], "provenanceStatus": "constructed", "checksum": "968c1365db47adedc858a9f9d97de935522644575e9c90825bea3151e3194f29", "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-22-data-analysis-and-insights-figure-1", "type": "mermaid", "caption": "Figure 22.1. Routing from association to prediction or causal decision. The author-created tree distinguishes predictive use from intervention claims and routes causal questions through confounding, timing, design, testing, and explicit uncertainty. A path through the tree does not itself identify an effect. Source basis: causal-model and intervention reasoning. [BB-C22-S02]", "textEquivalent": "Text equivalent: Start with an observed relationship. If the decision is prediction only, validate the predictive model. If the decision intervenes on X to change Y, examine confounding, timing, selection, overlap, spillovers, measurement, and design. Prefer a feasible ethical randomized experiment; otherwise justify a quasi-experimental or observational design. End with act, test, hold, or redesign and a named methods owner.", "sourceIds": [ "BB-C22-S02" ], "provenanceStatus": "constructed", "checksum": "6b72c6d163671ef920772d4d0051f63a8d834a5e962f6d3b53600134001af297", "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-figure-2", "type": "mermaid", "caption": "Figure 22.2. Constructed KPI hypothesis tree for profitable growth. The diagram links a strategic outcome to financial and operating measures. Each arrow is a proposed relationship to define, measure, and test; ownership does not make it causal. Source basis: balanced-measurement logic, adapted as author synthesis. [BB-C22-S07]", "textEquivalent": "Text equivalent: Profitable growth is decomposed into revenue growth, margin expansion, and capital efficiency. Those branches are further decomposed into acquisition, expansion, retention, margin, cost, discount, working-capital, and productivity measures. Each metric needs a definition, owner, guardrail, and evidence showing whether changing it can improve the higher-level outcome without unacceptable harm elsewhere.", "sourceIds": [ "BB-C22-S07" ], "provenanceStatus": "constructed", "checksum": "b0c0dea42981834146b0d76d451816a41b7d94df57a64b1beff97928c54785bd", "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-figure-3", "type": "mermaid", "caption": "Figure 22.3. Monte Carlo decision-model workflow. The author-created flow moves from a deterministic decision model through uncertain inputs, distributions and dependencies, simulation, validation, outcome ranges, sensitivity, and action. Simulation outputs remain conditional on the structure and assumptions. [BB-C22-S09] [BB-C22-S10]", "textEquivalent": "Text equivalent: Define and validate the base decision model; identify uncertain inputs; choose evidence-based ranges or distributions and their dependencies; run enough simulations for stable summaries; compare results with known data or limiting cases; inspect the full outcome distribution and tail; identify decision drivers; then act, stage, hedge, redesign, or collect higher-value information.", "sourceIds": [ "BB-C22-S09", "BB-C22-S10" ], "provenanceStatus": "constructed", "checksum": "101d32d41c933827f6dd5449de41f05da7cf75ab9461343685f01b8eb960acb1", "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-figure-4", "type": "mermaid", "caption": "Figure 22.4. Evidence-gated decision tree for a constructed AI-support decision. Decision and chance nodes are labeled in text as well as by shape. The tree compares immediate launch, testing, and deferral only after non-compensable gates pass. It is an author-created worked example based on expected-value, decision-tree, Bayesian-update, utility, information-value, and reversibility principles. [BB-C22-S11] [BB-C22-S12] [BB-C22-S13] [BB-C22-S14]", "textEquivalent": "Text equivalent: First determine whether legal, safety, rights, security, privacy, accessibility, and authority gates are satisfied. If not, redesign or stop. If they are satisfied, compare immediate launch, an evaluation followed by a later launch/defer decision, and deferral. Immediate launch faces a 45 percent high-value outcome and 55 percent low-value outcome. The evaluation passes 47 percent of the time; after a pass, the updated high-value probability is 76.6 percent and launch has a positive conditional EMV. After a fail, the updated probability is 17.0 percent and deferral dominates launch in the constructed monetary model.", "sourceIds": [ "BB-C22-S11", "BB-C22-S12", "BB-C22-S13", "BB-C22-S14" ], "provenanceStatus": "constructed", "checksum": "ab5625d537262e208a80b7b00ef932da8428731f32a4bc710772a0943eb38258", "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-figure-5", "type": "svg", "caption": "Figure 22.5. Effect-size/sample-size curve. Author-created calculation using the stated normal approximation; deterministic data and assumptions are in docs/evidence-packets/ch22-experiment-optimization-visual-data.json . The curve is illustrative, not a universal sample-size rule. [BB-C22-S16]", "textEquivalent": "A downward-curving line shows required sample per arm falling from 1,568 at a standardized minimum detectable effect of 0.10 to 63 at 0.50, assuming a two-sided five percent error rate and eighty percent power.", "sourceIds": [ "BB-C22-S16" ], "provenanceStatus": "constructed", "checksum": "d02aeab6fb5223f4997daf72c18888d28c20aca5faafcfca6ace34794a5621f8", "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-figure-6", "type": "svg", "caption": "Figure 22.6. Linear-program feasible region. The shaded area contains all choices satisfying the constructed constraints. The continuous objective reaches its maximum at the intersection; a whole-unit requirement moves the solution to the best feasible integer point. Data and verification inputs are in docs/evidence-packets/ch22-experiment-optimization-visual-data.json . [BB-C22-S21] [BB-C22-S22]", "textEquivalent": "A shaded polygon shows nonnegative product combinations satisfying labor and machine constraints. The continuous optimum is their intersection at about 39.67 units of X and 20.67 units of Y. A vertical scenario constraint at X equals 35 shrinks the feasible region.", "sourceIds": [ "BB-C22-S21", "BB-C22-S22" ], "provenanceStatus": "constructed", "checksum": "565181844ff963930678731bea13e3a8e3130fb11cdb1c1624ab470ab164798b", "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "appendix-a-framework-selection-decision-trees-figure-1", "type": "mermaid", "caption": "Figure A.1. Strategic-situation routing (constructed). Routes industry and internal analysis, growth choices, disruption, financial health, operational capability, and AI opportunity questions to Chapters 3, 4, 6, and 16.", "textEquivalent": "Text equivalent: Start with the decision and evidence need. Use Chapter 3 for industry, capabilities, growth, and disruption; Chapter 4 for financial health; Chapter 6 for operating capability; and Chapter 16 only after comparing AI and non-AI options.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "7d881cb30aec70402ec495f864965745c8279f7776e4edfc32378260786f05e3", "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-a-framework-selection-decision-trees-figure-2", "type": "mermaid", "caption": "Figure A.2. Financial-question routing (constructed). Separates intrinsic valuation, market and transaction evidence, operating performance, unit economics, venture finance, and cash/runway questions across Chapters 4, 15, 18, and 22.", "textEquivalent": "Text equivalent: Use Chapter 4 for financial statements, intrinsic valuation, working capital, break-even, and sensitivity, and its comparable-company and precedent-transaction workflow for market and transaction evidence; Chapter 15 for venture financing and terms; Chapter 18 for platform/cohort economics; and Chapter 22 for benchmarking and uncertainty.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "5d3726853fde2ee306893c189a3d417402eacab09a8400e247e7bd55384bce40", "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-a-framework-selection-decision-trees-figure-3", "type": "mermaid", "caption": "Figure A.3. Marketing and customer routing (constructed). Separates target/positioning, acquisition, retention, pricing, measurement, international/non-market go-to-market, accessibility-led service discovery, and experimentation across Chapters 5, 14, 21, and 22.", "textEquivalent": "Text equivalent: Use Chapter 5 for segmentation, pricing, retention, journeys, cohorts, and attribution; Chapter 14 for launch and channel, including its international and non-market GTM gate; Chapter 21 for discovery, accessibility-led research, and service blueprinting; and Chapter 22 for precommitted experimentation.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "7c5517424327cde7e7ab5674b9f1f101d614055bf13a3d74a507523d3a3a2253", "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-a-framework-selection-decision-trees-figure-4", "type": "mermaid", "caption": "Figure A.4. Operations and process routing (constructed). Routes flow, quality, cost, constraint, and supply-risk questions to Chapters 6, 9, 19, and 22; Lean operations/value-stream mapping is not the Lean Canvas.", "textEquivalent": "Text equivalent: Use Chapter 6 for flow, capacity, waste, quality, and supply chain; Chapter 9 for root-cause structure; Chapter 19 for cyber/supplier exposure; and Chapter 22 for benchmarking and evidence.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "c156cc5d390a9453b852a49443c36f7d3d7d223e1abe41daf0255e46aa4d2d21", "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-a-framework-selection-decision-trees-figure-5", "type": "mermaid", "caption": "Figure A.5. Organization and leadership routing (constructed). Routes change, team, talent, culture, negotiation, power, psychological safety, and sustainable digital transformation questions to Chapters 7, 8, 12, and 17.", "textEquivalent": "Text equivalent: Use Chapter 7 for leadership, teams, conflict, motivation, power, safety, and negotiation alternatives, range, value, power, and ethics; Chapter 8 for execution and metrics; Chapter 12 for client-specific negotiation and stakeholder engagement; and Chapter 17 for transformation and its sustainability boundary.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "eab41bad532e8a69ede5702e9eba43f78345bde36e9d6c7577fc8de161746339", "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-a-framework-selection-decision-trees-figure-6", "type": "mermaid", "caption": "Figure A.6. Consulting and problem-solving routing (constructed). Routes framing, analysis, experimentation, optimization, negotiation, recommendations, transformation, and implementation to Chapters 9, 10, 11, 12, 17, and 22.", "textEquivalent": "Text equivalent: Use Chapter 9 to frame the problem; Chapter 10 for engagement frameworks; Chapter 11 for delivery; Chapter 12 for stakeholders and negotiation; Chapter 17 for transformation; and Chapter 22 for experimentation and optimization.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "6a3b0c358e2b0a7fc1c9ae6db7a8097bb1c08a754e89fa0e97e8d0d4062f9638", "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-a-framework-selection-decision-trees-figure-7", "type": "mermaid", "caption": "Figure A.7. Startup and entrepreneurship routing (constructed). Routes discovery, product, service design, scaling, international go-to-market, acquisition entrepreneurship, economics, runway, financing, and stop decisions to Chapters 13, 14, 15, and 21.", "textEquivalent": "Text equivalent: Use Chapter 13 for venture hypotheses, MVPs, and build/search/sponsor/acquisition pathway selection; Chapter 14 for launch, channels, and international/non-market entry; Chapter 15 for financing, diligence, transition, and runway; and Chapter 21 for discovery, accessibility, service design, PMF, prioritization, and product lifecycle.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "04d33d66dcbe838f75acc73ee40aaa9139026fc31260e312117c47c41ca3c892", "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-a-framework-selection-decision-trees-figure-8", "type": "mermaid", "caption": "Figure A.8. AI and digital decision routing (constructed). Routes AI/non-AI opportunity, sourcing, data readiness, deployment, transformation sustainability, security, ethics, and governance to Chapters 16, 17, 19, 20, and 21.", "textEquivalent": "Text equivalent: Use Chapter 16 for value, sourcing, evaluation, and AI governance; Chapter 17 for capability and workforce change and its digital and AI sustainability system boundary; Chapter 19 for security; Chapter 20 for ethics and remedy; and Chapter 21 for accessible product/service discovery and lifecycle.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "5a5772d4366c97dc493926dc8a890e08f92b98b93a3019f14c08ec8c210ccda2", "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-a-framework-selection-decision-trees-figure-9", "type": "mermaid", "caption": "Figure A.9. Project delivery routing (constructed). Selects predictive, adaptive, or hybrid delivery from uncertainty, regulation, coupling, feedback, and change cost, then routes all methods to Chapter 11.", "textEquivalent": "Text equivalent: Use Chapter 11 for chartering, work breakdown, schedule, risk, change, agile, hybrid, monitoring, and closure. Choose the delivery approach from uncertainty, compliance, dependency, stakeholder-feedback, and reversibility needs rather than a methodology label alone.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "d388fa13f3409f750951f4add8a62d5e876bcfae330221924890338e7fbcea82", "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-a-framework-selection-decision-trees-figure-10", "type": "mermaid", "caption": "Figure A.10. New-business-unit decision and evidence gates (constructed). Integrates strategy, valuation evidence, legal lifecycle, negotiation, business model, international/non-market go-to-market, operations, accessible service discovery, experimentation, optimization, sustainability, scale, and transformation across the canonical chapters.", "textEquivalent": "Text equivalent: Frame and test strategic, financial, stakeholder, operating, product, legal/ethical, and risk assumptions before go/no-go. Use the Chapter 2 legal lifecycle gate, Chapter 4 market/transaction valuation evidence, Chapter 7 and 12 negotiation routes, the Chapter 14 international/non-market gate, the Chapter 17 sustainability boundary, Chapter 21 accessibility/service blueprinting, and Chapter 22 experimentation/optimization when those questions are material. Build a bounded pilot; scale only when value, economics, operations, customer, workforce, risk, and governance gates are met; otherwise pivot, redesign, or stop.", "sourceIds": [], "provenanceStatus": "constructed", "checksum": "aac9d6874370dbde75581cbb3723ff7193606f8d3fe70b2ae89e5aab7ccdbc39", "entrySlug": "appendix-a-framework-selection-decision-trees" } ], "tables": [ { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-1", "caption": "Table 1. Working diagnosis / Evidence to collect / Options to test", "headers": [ "Working diagnosis", "Evidence to collect", "Options to test", "Stop rule / constraint" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 3, "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-2", "caption": "Table 2. Indicator / Tight Market / Balanced", "headers": [ "Indicator", "Tight Market", "Balanced", "Loose Market" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-3", "caption": "Table 3. Business Activity / Currency Exposure / Impact of Strong USD", "headers": [ "Business Activity", "Currency Exposure", "Impact of Strong USD", "Impact of Weak USD" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-4", "caption": "Table 4. Policy change / Transmission questions / Firm evidence required", "headers": [ "Policy change", "Transmission questions", "Firm evidence required" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-5", "caption": "Table 5. Signal / What to Watch / How to Interpret", "headers": [ "Signal", "What to Watch", "How to Interpret" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-6", "caption": "Table 6. Field / Required entry / Why it matters", "headers": [ "Field", "Required entry", "Why it matters" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-7", "caption": "Table 7. Observed signal / Confirm before acting / Decision test", "headers": [ "Observed signal", "Confirm before acting", "Decision test" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-table-8", "caption": "Table 8. Shock / Immediate questions / Near-term tests", "headers": [ "Shock", "Immediate questions", "Near-term tests", "Longer-term options to evaluate" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-02-business-law-governance-and-ethics-table-1", "caption": "Table 2.1. IP protection routing comparison. Author-created comparison for issue spotting; it does not determine eligibility, ownership, or enforceability.", "headers": [ "Asset Type", "Protection Method", "Key Characteristic", "Operator's Action" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-02-business-law-governance-and-ethics-table-2", "caption": "Table 2.2. Corporate-purpose and governance lenses. Author-created comparison; neither column selects a legal duty or displaces governing law.", "headers": [ "Dimension", "Shareholder Primacy", "Stakeholder Capitalism" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-02-business-law-governance-and-ethics-table-3", "caption": "Table 2.3. Illustrative compensation-plan components. Author-created diagnostic; the components and questions are not universal recommendations.", "headers": [ "Component", "Illustrative role in a plan", "Purpose", "Questions for the compensation committee" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-02-business-law-governance-and-ethics-table-4", "caption": "Table 2.4. Constructed ESG planning example. These are example metrics and target-setting prompts, not benchmarks.", "headers": [ "Pillar", "Example Metrics", "Target" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-02-business-law-governance-and-ethics-table-5", "caption": "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.", "headers": [ "Ethical Framework", "Key Question", "Strengths", "Weaknesses" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-02-business-law-governance-and-ethics-table-6", "caption": "Table 2.6. Constructed layoff/pay-cut decision lenses. The questions apply to either option; the exercise does not recommend one option.", "headers": [ "Decision lens", "Questions to test for either option" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-02-business-law-governance-and-ethics-table-7", "caption": "Table 2.7. Constructed AI risk-triage levels. The categories and examples are illustrative; legal classification requires current, context-specific analysis.", "headers": [ "Risk Level", "Criteria", "Control questions and options", "Example" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-02-business-law-governance-and-ethics-table-8", "caption": "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.", "headers": [ "Issue lane", "Selected jurisdiction anchor", "Manager-facing trigger facts", "Counsel or specialist gate before action" ], "sourceIds": [ "BB-C02-S16", "BB-C02-S17", "BB-C02-S26", "BB-C02-S18", "BB-C02-S19", "BB-C02-S20", "BB-C02-S21", "BB-C02-S22", "BB-C02-S23", "BB-C02-S24", "BB-C02-S25" ], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-02-business-law-governance-and-ethics" }, { "id": "chapter-03-strategy-and-competitive-analysis-table-1", "caption": "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.", "headers": [ "Structure", "Managerial hypothesis", "Five Forces connection", "Positioning implication" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-table-2", "caption": "Table 3.2. Information-asymmetry issue-spotting matrix. The mechanisms are candidate controls to test; they are not universal remedies or legal requirements.", "headers": [ "Information problem", "Diagnostic question", "Candidate mechanisms to test", "Failure mode" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 2, "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-table-3", "caption": "Table 3.3. Constructed two-firm response matrix for a price move. Read each cell as (Firm A, Firm B) .", "headers": [ "Firm A \\ Firm B", "Hold value-based price", "Cut price" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2, "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-03-strategy-and-competitive-analysis-table-4", "caption": "Table 3.4. Constructed strategy-kernel decision record. This author-created worksheet connects diagnosis, choice, coherent actions, scenarios, and review evidence.", "headers": [ "Element", "Required evidence", "Decision output" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-03-strategy-and-competitive-analysis" }, { "id": "chapter-04-financial-analysis-and-valuation-table-1", "caption": "Table 4.1. Earnings-quality question matrix. This author-created diagnostic organizes evidence and its limits; it is not an accounting-quality score.", "headers": [ "Quality question", "Evidence to inspect", "What the evidence does not prove" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-04-financial-analysis-and-valuation" }, { "id": "chapter-04-financial-analysis-and-valuation-table-2", "caption": "Table 4.2. Cost-of-capital input control record. The rows identify documentation and challenge questions, not a universal estimation recipe.", "headers": [ "Input", "Minimum documentation", "Challenge question" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-04-financial-analysis-and-valuation" }, { "id": "chapter-04-financial-analysis-and-valuation-table-3", "caption": "Table 4.3. Constructed valuation-range exhibit. The values are illustrative and assumption-dependent; they are not current market evidence or a recommendation.", "headers": [ "Method", "Low equity value", "High equity value", "Key constructed assumption" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-04-financial-analysis-and-valuation" }, { "id": "chapter-05-marketing-and-customer-analytics-table-1", "caption": "Table 1. Evidence stream / Strongest decision use / Required controls", "headers": [ "Evidence stream", "Strongest decision use", "Required controls", "Important limit" ], "sourceIds": [ "BB-C05-S15", "BB-C05-S18", "BB-C05-S19", "BB-C05-S20" ], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-05-marketing-and-customer-analytics" }, { "id": "chapter-06-operations-and-supply-chain-table-1", "caption": "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]", "headers": [ "Category", "Look for", "Evidence before changing the work" ], "sourceIds": [ "BB-C06-S01", "BB-C06-S02" ], "provenanceStatus": "source-linked", "rowCount": 8, "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-table-2", "caption": "Table 6.2. Constructed candidate hybrid inventory policies. The item descriptions suggest models to evaluate, not automatic assignments.", "headers": [ "Item or flow condition", "Candidate policy", "Quantify before selecting" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-table-3", "caption": "Table 6.3. Constructed inventory-policy decision matrix. The candidate policies are prompts for scenario analysis, not automatic assignments.", "headers": [ "Demand Variability", "Supply Reliability", "Candidate Strategy" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-table-4", "caption": "Table 6.4. Constructed supply-chain risk mitigation options for scenario review. The options require cost, service, recovery, safety, supplier, and residual-risk analysis.", "headers": [ "Risk Type", "Mitigation Strategy" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-table-5", "caption": "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]", "headers": [ "Chart candidate", "Data and sampling context", "Verify before use" ], "sourceIds": [ "BB-C06-S09" ], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-table-6", "caption": "Table 6.6. Constructed digital-representation scope taxonomy. Actual terminology and scope must follow the governing standard, architecture, and use case.", "headers": [ "Teaching label", "Candidate scope", "Example decision use", "Key boundary" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-table-7", "caption": "Table 6.7. Constructed S&OP decision rights and minimum outputs. The rows are a managerial synthesis, not a universal meeting design.", "headers": [ "Review", "Question", "Minimum output" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-table-8", "caption": "Table 6.8. Constructed six-period forecast-error exercise. Error definitions and values are teaching inputs; they are not a forecast-performance benchmark.", "headers": [ "Period", "Actual units", "Forecast units", "Error: actual − forecast", "Absolute error" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-table-9", "caption": "Table 6.9. Constructed constrained-plan alternatives. The contributions and service tensions are illustrative and require local cost, contract, quality, labor, and risk checks.", "headers": [ "Candidate plan", "A units", "B units", "Capacity used", "Unserved forecast", "Illustrative contribution", "Decision tension" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-06-operations-and-supply-chain-table-10", "caption": "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.", "headers": [ "Evidence stream", "Constructed input", "Question to test" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-06-operations-and-supply-chain" }, { "id": "chapter-07-organizational-behavior-and-leadership-table-1", "caption": "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]", "headers": [ "Element", "Managerial question", "Common failure" ], "sourceIds": [ "BB-C07-S13", "BB-C07-S14" ], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-07-organizational-behavior-and-leadership" }, { "id": "chapter-09-problem-structuring-table-1", "caption": "Table 1. Feature / Customer Demand / Revenue Impact", "headers": [ "Feature", "Customer Demand", "Revenue Impact", "Strategic", "Ease", "Weighted Score" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8, "entrySlug": "chapter-09-problem-structuring" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-1", "caption": "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.", "headers": [ "Framework Applied", "Key Question It Answers", "Deliverable" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-2", "caption": "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.", "headers": [ "Framework Applied", "Key Question It Answers", "Deliverable" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-3", "caption": "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.", "headers": [ "Framework Applied", "Key Question It Answers", "Deliverable" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-4", "caption": "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.", "headers": [ "Building block", "Decision question", "Illustrative evidence to gather" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 9, "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-5", "caption": "Table 5. Candidate tool / Useful questions / Do not infer", "headers": [ "Candidate tool", "Useful questions", "Do not infer" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-6", "caption": "Table 10.5. Constructed startup business-model baseline. All values are fictional teaching assumptions, not benchmarks or forecasts.", "headers": [ "Box", "Current State" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 9, "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration" }, { "id": "chapter-10-advanced-consulting-frameworks-and-integration-table-7", "caption": "Table 10.6. Constructed startup pivot hypothesis. All values are fictional teaching assumptions and require commercial, privacy, compliance, and cash evidence.", "headers": [ "Box", "Pivoted State" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 9, "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-1", "caption": "Table 1. Activity / Tool/Framework / Output", "headers": [ "Activity", "Tool/Framework", "Output" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-2", "caption": "Table 2. Level / WBS code / Illustrative element", "headers": [ "Level", "WBS code", "Illustrative element", "Parent" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 11, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-3", "caption": "Table 3. WBS / Deliverable or work package / Constructed hours", "headers": [ "WBS", "Deliverable or work package", "Constructed hours", "Parent" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-4", "caption": "Table 11.3 — Constructed CPM task register. Durations and dependencies are teaching assumptions for the worked network, not schedule benchmarks.", "headers": [ "Task", "Duration", "Predecessors" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-5", "caption": "Table 11.1 — Constructed schedule timeline. The table is the accessible timeline equivalent of the dependency network; week numbers are discrete teaching periods.", "headers": [ "Task", "Start week", "Finish week", "Duration", "Critical?", "Dependency note" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-6", "caption": "Table 6. Measure / Constructed result / Decision use", "headers": [ "Measure", "Constructed result", "Decision use" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-7", "caption": "Table 11.4 — Constructed risk register. Entries, ordinal scores, owners, and responses are teaching assumptions; define the actual method and authority locally.", "headers": [ "Risk ID", "Risk Description", "Category", "Probability (1-5)", "Impact (1-5)", "Risk Score", "Response Strategy", "Owner", "Status" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-8", "caption": "Table 8. Stakeholder / Role / Power", "headers": [ "Stakeholder", "Role", "Power", "Interest", "Influence", "Attitude", "Strategy" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-9", "caption": "Table 9. Stakeholder / Message / Frequency", "headers": [ "Stakeholder", "Message", "Frequency", "Medium", "Owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-10", "caption": "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.", "headers": [ "Backlog", "To Do", "In Progress", "Code Review", "Testing", "Done" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-11", "caption": "Table 11. Field / Description", "headers": [ "Field", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 16, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-12", "caption": "Table 11.7 — Constructed charter stakeholder register. Names, roles, and responsibilities are fictional teaching assumptions.", "headers": [ "Name", "Role", "Responsibility" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-13", "caption": "Table 11.8 — Constructed charter milestone register. Dates are fictional teaching assumptions.", "headers": [ "Milestone", "Target Date" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-14", "caption": "Table 11.9 — Constructed charter budget. Amounts and the total are fictional teaching assumptions; the line items sum to $1.2 million including the illustrative reserve.", "headers": [ "Category", "Amount" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-15", "caption": "Table 15. Dimension / Questions / Possible design response", "headers": [ "Dimension", "Questions", "Possible design response" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-16", "caption": "Table 16. Context signal / Questions for delivery design", "headers": [ "Context signal", "Questions for delivery design" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-17", "caption": "Table 17. Dimension / Questions to resolve", "headers": [ "Dimension", "Questions to resolve" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-18", "caption": "Table 18. Stakeholder Group / Frequency / Medium", "headers": [ "Stakeholder Group", "Frequency", "Medium", "Content", "Owner" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-19", "caption": "Table 19. Dimension / Predictive practice can help when... / Adaptive practice can help when...", "headers": [ "Dimension", "Predictive practice can help when...", "Adaptive practice can help when...", "Control that remains necessary" ], "sourceIds": [ "BB-C11-S01", "BB-C11-S05", "BB-C11-S06" ], "provenanceStatus": "source-linked", "rowCount": 6, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-11-project-management-and-pmp-frameworks-table-20", "caption": "Table 11.10 — Predictive and adaptive practices. Constructed comparison; select practices independently from the project's evidence and constraints.", "headers": [ "Aspect", "Waterfall", "Agile" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-11-project-management-and-pmp-frameworks" }, { "id": "chapter-12-client-management-table-1", "caption": "Table 12.2 — Constructed RACI working matrix. Confirm governing authority and required approvals before assigning local RACI labels. [BB-C12-S03]", "headers": [ "Activity or decision", "Product lead", "Engineering lead", "Design lead", "Commercial lead", "Executive authority" ], "sourceIds": [ "BB-C12-S03" ], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-2", "caption": "Table 12.6 — Constructed included-scope register. Items, descriptions, owners, and examples are fictional teaching assumptions.", "headers": [ "Item", "Description", "Owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-3", "caption": "Table 12.7 — Constructed excluded-scope register. Exclusions and alternatives are fictional teaching assumptions.", "headers": [ "Item", "Why", "Alternative" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-4", "caption": "Table 12.8 — Constructed scoping-risk register. Risks and mitigations are fictional teaching assumptions.", "headers": [ "Risk", "Mitigation" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-5", "caption": "Table 12.3 — Constructed risk register. Entries, labels, scores, responses, names, and statuses are teaching assumptions, not measured exposure.", "headers": [ "Risk", "Probability", "Impact", "Score", "Mitigation", "Owner", "Status" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-6", "caption": "Table 12.1 — Constructed relationship-map hypotheses. The arrows and labels are hypotheses to validate, not facts about motive, authority, or allegiance.", "headers": [ "From", "To", "Relationship hypothesis", "Validation and guardrail" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-7", "caption": "Table 7. Stakeholder / Role / Power", "headers": [ "Stakeholder", "Role", "Power", "Interest", "Attitude", "Key Concern" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-8", "caption": "Table 12.9 — Constructed scale-context comparison. Stakeholder counts, cadences, and governance examples are not maturity benchmarks.", "headers": [ "Dimension", "Startup", "Scale-Up", "Enterprise" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-9", "caption": "Table 9. Stakeholder Tier / Communication Frequency / Method", "headers": [ "Stakeholder Tier", "Communication Frequency", "Method" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-10", "caption": "Table 10. Stakeholder / Incentive / Preferred Outcome", "headers": [ "Stakeholder", "Incentive", "Preferred Outcome" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-11", "caption": "Table 11. Function / Input Provided / Format", "headers": [ "Function", "Input Provided", "Format" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-12", "caption": "Table 12. Function / Output Provided / Impact", "headers": [ "Function", "Output Provided", "Impact" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-13", "caption": "Table 13. Function / Input Provided / Format", "headers": [ "Function", "Input Provided", "Format" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-14", "caption": "Table 14. Function / Output Provided / Impact", "headers": [ "Function", "Output Provided", "Impact" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-15", "caption": "Table 12.5 — Constructed framework-selection aid. Time, cadence, and use examples depend on the decision, evidence, authority, and context; they are not benchmarks.", "headers": [ "Framework", "When to Use", "Time to Apply" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 10, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-12-client-management-table-16", "caption": "Table 16. Stakeholder Group / Frequency / Medium", "headers": [ "Stakeholder Group", "Frequency", "Medium", "Content", "Owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-12-client-management" }, { "id": "chapter-13-startup-foundations-table-1", "caption": "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.", "headers": [ "Stakeholder", "Shares", "%" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-13-startup-foundations" }, { "id": "chapter-13-startup-foundations-table-2", "caption": "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.", "headers": [ "Week", "Hypothesis Tested", "Validated (Y/N)", "Customer Convos", "Sign-ups/Sales", "Key Learning" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8, "entrySlug": "chapter-13-startup-foundations" }, { "id": "chapter-13-startup-foundations-table-3", "caption": "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.", "headers": [ "Path", "Primary managerial job", "Starting evidence", "Capital and ownership", "Distinct risks", "Example stop gate" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-13-startup-foundations" }, { "id": "chapter-13-startup-foundations-table-4", "caption": "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.", "headers": [ "Screen", "Evidence required before advancing", "Case signal", "Decision implication" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-13-startup-foundations" }, { "id": "chapter-13-startup-foundations-table-5", "caption": "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.", "headers": [ "Dimension", "Lean Startup", "Traditional Planning" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-13-startup-foundations" }, { "id": "chapter-13-startup-foundations-table-6", "caption": "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.", "headers": [ "Dimension", "Bootstrap", "Venture-Backed" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-13-startup-foundations" }, { "id": "chapter-13-startup-foundations-table-7", "caption": "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.", "headers": [ "Week", "Phase", "Hypothesis Tested", "Validated?", "Customer Convos", "Signups", "Paying", "Key Learning" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-13-startup-foundations" }, { "id": "chapter-14-go-to-market-strategy-table-1", "caption": "Table 14.1: Constructed segment-prioritization illustration. The figures are invented teaching inputs, not market benchmarks, forecasts, or evidence of fit.", "headers": [ "Segment", "Size", "Avg Deal", "Win Rate", "LTV:CAC", "Priority" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-2", "caption": "Table 14.2: Constructed funnel dashboard for one sample month. Stage definitions, targets, actuals, and health labels require local cohort and data-quality rules.", "headers": [ "Stage", "Target", "Actual", "Conv Rate", "Health" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-3", "caption": "Table 14.3: Constructed channel-funnel comparison. Conversion values are illustrative and are not channel benchmarks.", "headers": [ "Channel", "Awareness", "Consideration", "Proposal", "Close", "Efficiency" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-4", "caption": "Table 14.4: Constructed channel-evaluation matrix. Volume, deal-size, cycle, margin, investment, and maturity values are hypotheses for teaching, not benchmarks.", "headers": [ "Channel", "Volume Potential", "Deal Size", "Sales Cycle", "Margin", "Investment", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-5", "caption": "Table 14.5: Constructed channel-economics hypothesis. The figures below illustrate a comparison method; they are not observed LTV, CAC, or channel performance.", "headers": [ "Channel", "CAC", "LTV", "LTV:CAC", "Status" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-6", "caption": "Table 14.6: Constructed pricing-model comparison. The dimensions are decision prompts, not universal model attributes.", "headers": [ "Model", "Predictability", "Scalability", "Customer Friction", "Enterprise", "SMB" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-7", "caption": "Table 14.7: Constructed partnership-evaluation illustration. Company names, revenue potential, timing, and priorities are invented teaching inputs, not forecasts.", "headers": [ "Partnership", "Revenue Potential", "Ease of Execution", "Strategic Fit", "Timeline", "Priority" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-8", "caption": "Table 14.8: Author-created market-entry comparison. Each row states evidence to obtain before commitment; the strategy labels do not predict success.", "headers": [ "Situation", "Candidate strategy", "Evidence required before commitment" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-9", "caption": "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.", "headers": [ "Decision lane", "Evidence required before commitment", "Gate or trigger" ], "sourceIds": [ "BB-C14-S09", "BB-C14-S10", "BB-C14-S11" ], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-10", "caption": "Table 14.10: Constructed framework-use summary. Timing is a planning aid, not a universal sequence or readiness gate.", "headers": [ "Framework", "When to Use", "Time Required" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 10, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-11", "caption": "Table 14.11: Constructed channel-model comparison. Values are illustrative ranges and descriptive expectations to test locally, not natural channel properties.", "headers": [ "Channel", "Natural CAC", "Customer Expectation", "Works For" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-12", "caption": "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.", "headers": [ "Dimension", "Direct Sales", "Indirect Sales" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-13", "caption": "Table 14.13: Author-created acquisition-mechanism questions. Use the table to define evidence and guardrails; it is not a taxonomy or performance ranking.", "headers": [ "Dimension", "Questions to test" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-14-go-to-market-strategy-table-14", "caption": "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.", "headers": [ "Week", "Key Metric", "Target", "Actual", "Status" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 14, "entrySlug": "chapter-14-go-to-market-strategy" }, { "id": "chapter-15-fundraising-and-finance-table-1", "caption": "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.", "headers": [ "Investor", "Intro Date", "1st Meeting", "Interest Level", "Feedback", "Next Step" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-2", "caption": "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.", "headers": [ "Method", "Decision use", "Main controls" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-3", "caption": "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.", "headers": [ "Provision family", "Questions to model and escalate" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 10, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-4", "caption": "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.", "headers": [ "Round", "New money", "Pre-money", "Post-money", "New investor", "Founders after round" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-5", "caption": "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.", "headers": [ "What VC Says", "Possible interpretations to test", "What to Do" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-6", "caption": "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.", "headers": [ "Item", "Year 1", "Year 2", "Year 3", "Year 4", "Year 5" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 20, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-7", "caption": "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.", "headers": [ "Asset", "Year 1", "Year 5" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 19, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-8", "caption": "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.", "headers": [ "Month", "Jan", "Feb", "Mar", "Apr", "May", "Jun" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 14, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-9", "caption": "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.", "headers": [ "Option", "Decision questions" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-10", "caption": "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.", "headers": [ "Question", "Convertible note", "SAFE" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-11", "caption": "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.", "headers": [ "Dimension", "Questions to resolve" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-12", "caption": "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.", "headers": [ "Observed pattern", "Competing hypotheses to test", "Possible next evidence or response" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-13", "caption": "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.", "headers": [ "Term", "Investor Scenario", "Founder Scenario", "Constructed Comparison Input" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-14", "caption": "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.", "headers": [ "Constructed uses", "Amount", "Constructed sources", "Amount" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-15", "caption": "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.", "headers": [ "Constructed QoE bridge", "Amount", "Evidence judgment" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-16", "caption": "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.", "headers": [ "Workstream", "Minimum evidence package", "Escalate, reprice, restructure, or stop when" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-17", "caption": "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.", "headers": [ "Stage", "Required decisions and evidence" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-18", "caption": "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.", "headers": [ "Investor Name", "Firm", "Stage", "Sector", "Geography", "Intro Path", "Tier", "Contact Date" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-19", "caption": "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.", "headers": [ "Investor", "Meeting Date", "Interest Level", "Key Feedback", "Materials Sent", "Next Step", "Timeline" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-20", "caption": "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.", "headers": [ "Week", "Activity", "Meetings", "Outputs" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-21", "caption": "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.", "headers": [ "Week", "Phase", "Key Activities", "Meetings", "Outputs" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 9, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-22", "caption": "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.", "headers": [ "Theme", "Count", "Example Quote", "Action" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-23", "caption": "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.", "headers": [ "Source", "Cost", "Control", "Best For" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-24", "caption": "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.", "headers": [ "Dimension", "Venture Capital", "Strategic Investment" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-25", "caption": "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.", "headers": [ "Provision", "Questions to model" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-26", "caption": "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.", "headers": [ "Decision area", "Evidence to examine" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-27", "caption": "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.", "headers": [ "Framework", "When to Use", "Effort Required" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 11, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-28", "caption": "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.", "headers": [ "Holder", "Pre-round", "Post-round calculation", "Post-round" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-15-fundraising-and-finance-table-29", "caption": "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.", "headers": [ "Phase", "Key Metric", "Local rule", "Actual", "Status" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 11, "entrySlug": "chapter-15-fundraising-and-finance" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-1", "caption": "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.", "headers": [ "", "Low Feasibility", "High Feasibility" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2, "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-2", "caption": "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.", "headers": [ "Use Case", "Value", "Feasibility", "Quadrant" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-3", "caption": "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.", "headers": [ "Use Case", "Impact", "Confidence", "Ease", "Data Quality", "Score", "Priority" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-4", "caption": "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.", "headers": [ "Control", "Managerial question", "Minimum record" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8, "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-5", "caption": "Table 16.5: Constructed model-selection comparison aid (Use case | Model approach | Cost | When to use). Product names, prices, and performance are intentionally omitted because they change; validate current options and controls before procurement.", "headers": [ "Use Case", "Best Model", "Cost", "When to Use" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions" }, { "id": "chapter-16-ai-strategy-and-data-driven-decisions-table-6", "caption": "Table 16.6: Constructed pilot measurement dashboard (Week | Phase | Activity | Deliverable | Status | Red flags). Timing, thresholds, status values, and red flags are local planning inputs; define them against the approved use case and risk boundary.", "headers": [ "Week", "Phase", "Key Activity", "Deliverable", "Status", "Red Flags" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 8, "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions" }, { "id": "chapter-17-leading-digital-transformation-table-1", "caption": "Table 17.1: Author-created framework comparison aid (Framework | Primary Use | Time Required | Complexity | Strategic Impact). Time, complexity, and impact labels are teaching inputs, not universal benchmarks; define local criteria and evidence before using them for investment decisions.", "headers": [ "Framework", "Primary Use", "Time Required", "Complexity", "Strategic Impact" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 11, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-2", "caption": "Table 17.2: Author-created suitability aid (Organization Type | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against local strategy, capacity, obligations, and evidence.", "headers": [ "Organization Type", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-3", "caption": "Table 17.3: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; time, team, output, and update choices should be defined for the initiative rather than treated as universal requirements.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-4", "caption": "Table 17.4: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against local strategy, capacity, obligations, and evidence.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-5", "caption": "Table 17.5: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; workshop duration, team size, outputs, and update choices should be defined for the initiative.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-6", "caption": "Table 17.6: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against local strategy, capacity, obligations, and evidence.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-7", "caption": "Table 17.7: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; duration, roles, outputs, and update choices should be defined for the change context.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-8", "caption": "Table 17.8: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against the product, adoption, and evidence context.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-9", "caption": "Table 17.9: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; duration, roles, outputs, and update choices should be defined for the adoption context.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-10", "caption": "Table 17.10: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against local portfolio, capability, and evidence conditions.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-11", "caption": "Table 17.11: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; duration, roles, outputs, and update choices should be defined for the ambidexterity context.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-12", "caption": "Table 17.12: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against the maturity question, decision owner, and evidence available.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-13", "caption": "Table 17.13: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; assessment effort, roles, outputs, and update choices should be defined for the organization.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-14", "caption": "Table 17.14: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against the capability decision, dependencies, and evidence available.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-15", "caption": "Table 17.15: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; effort, roles, outputs, and update choices should be defined for the capability portfolio.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-16", "caption": "Table 17.16: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against the outcome definition, incentives, and evidence quality.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-17", "caption": "Table 17.17: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; cadence, roles, outputs, and update choices should be defined for the operating context.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-18", "caption": "Table 17.18: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against decision rights, controls, capacity, and evidence.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-19", "caption": "Table 17.19: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; roles, outputs, and update choices should be defined for the operating model in scope.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-20", "caption": "Table 17.20: Author-created suitability aid (Context | Suitability | Notes). Suitability labels are discussion inputs, not a recommendation or cross-organization benchmark; test them against audience, purpose, accessibility, privacy, and evidence conditions.", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-21", "caption": "Table 17.21: Author-created quick reference card (Element | Description). The descriptions are a local planning aid; communication roles, outputs, and update choices should be defined for the transformation context.", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-17-leading-digital-transformation-table-22", "caption": "Table 17.22: Author-created lifecycle-boundary checklist (Lifecycle surface | What can fall inside the boundary | Managerial evidence and common boundary failure). This is a scoping aid, not a complete inventory or verified footprint; state the chosen functional unit, allocation rules, data quality, uncertainty, and exclusions.", "headers": [ "Lifecycle surface", "What can fall inside the boundary", "Managerial evidence and common boundary failure" ], "sourceIds": [ "BB-C17-S14", "BB-C17-S13", "BB-C17-S21", "BB-C17-S15", "BB-C17-S17", "BB-C17-S12", "BB-C17-S18" ], "provenanceStatus": "constructed", "rowCount": 7, "entrySlug": "chapter-17-leading-digital-transformation" }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-1", "caption": "Table 18.1: Author-created platform-regulation issue map (Decision area | Questions | Evidence and owner). This is a routing aid, not a legal conclusion; current law, facts, decisions, enforcement, and qualified counsel determine the applicable analysis.", "headers": [ "Decision area", "Questions for the platform or complementor", "Evidence and owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-2", "caption": "Table 18.2: Author-created revenue-model comparison aid (Decision dimension | Evidence to compare across candidate models). The dimensions expose local assumptions; they do not rank monetization models or supply market benchmarks.", "headers": [ "Decision dimension", "Evidence to compare across candidate models" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-3", "caption": "Table 18.3: Author-created data-rights and value gate (Gate | Managerial question | Minimum evidence | Decision owner). The gate is a scoping aid, not legal advice or a complete privacy, intellectual-property, competition, employment, sector, or consumer-law analysis.", "headers": [ "Gate", "Managerial question", "Minimum evidence", "Decision owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-4", "caption": "Table 18.4: Author-created ecosystem structure map (Role | Required contribution | Dependency or bottleneck | Evidence and response). Roles and dependencies are constructed decision inputs; they are not claims about any named company or current market share.", "headers": [ "Role", "Required contribution", "Dependency or bottleneck", "Evidence and response" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-5", "caption": "Table 18.5: Author-created platform security risk matrix (Scenario | Asset or boundary | Harm to test | Evidence and response). The scenarios are constructed prompts; assess actual likelihood, impact, controls, and obligations locally with security and legal owners.", "headers": [ "Scenario", "Asset or boundary", "Harm to test", "Evidence and response" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-6", "caption": "Table 18.6: Author-created digital KPI dashboard (Hypothesis | Leading signal | Outcome measure | Guardrail | Decision rule). Metric definitions, targets, and thresholds are local inputs; none is a market benchmark.", "headers": [ "Hypothesis", "Leading signal", "Outcome measure", "Guardrail", "Decision rule" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-7", "caption": "Table 18.7: Author-created automation opportunity assessment (Workflow | Candidate change | Evidence to collect | Human and control gate). The options are constructed prompts; they do not predict job loss, productivity, ROI, or safe deployment without local evidence and affected-party review.", "headers": [ "Workflow", "Candidate change", "Evidence to collect", "Human and control gate" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-8", "caption": "Table 18.8: Author-created digital transformation roadmap (Stage | Decision question | Evidence package | Gate). Stage names and timing are local planning inputs; no fixed duration or sequence is a universal transformation recipe.", "headers": [ "Stage", "Decision question", "Evidence package", "Gate" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-18-digital-business-models-and-platform-economics-table-9", "caption": "Table 9. Framework / When to Use / Effort Required", "headers": [ "Framework", "When to Use", "Effort Required" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 10, "entrySlug": "chapter-18-digital-business-models-and-platform-economics" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-1", "caption": "Table 1. Framework / Primary Use / Time Required", "headers": [ "Framework", "Primary Use", "Time Required", "Complexity", "Strategic Impact" ], "sourceIds": [ "BB-C19-S01" ], "provenanceStatus": "source-linked", "rowCount": 10, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-2", "caption": "Table 2. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-3", "caption": "Table 3. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-4", "caption": "Table 4. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [ "BB-C19-S03" ], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-5", "caption": "Table 5. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-6", "caption": "Table 6. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-7", "caption": "Table 7. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-8", "caption": "Table 8. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-9", "caption": "Table 9. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-10", "caption": "Table 10. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-11", "caption": "Table 11. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-12", "caption": "Table 12. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-13", "caption": "Table 13. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-14", "caption": "Table 14. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-15", "caption": "Table 15. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-16", "caption": "Table 16. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [ "BB-C19-S01" ], "provenanceStatus": "source-linked", "rowCount": 5, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-17", "caption": "Table 17. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-18", "caption": "Table 18. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-19", "caption": "Table 19. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-20", "caption": "Table 20. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-19-cybersecurity-and-risk-management-for-managers-table-21", "caption": "Table 21. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-1", "caption": "Table 1. Framework / Primary Use / Time Required", "headers": [ "Framework", "Primary Use", "Time Required", "Complexity", "Strategic Impact" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 10, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-2", "caption": "Table 2. AI Application / Key FATE Principles / Notes", "headers": [ "AI Application", "Key FATE Principles", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-3", "caption": "Table 3. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-4", "caption": "Table 4. AI Application / Key Bias Focus / Notes", "headers": [ "AI Application", "Key Bias Focus", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-5", "caption": "Table 5. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-6", "caption": "Table 6. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-7", "caption": "Table 7. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-8", "caption": "Table 8. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-9", "caption": "Table 9. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-10", "caption": "Table 10. AI Application / Explanation Focus / Notes", "headers": [ "AI Application", "Explanation Focus", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-11", "caption": "Table 11. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-12", "caption": "Table 12. AI Application / Key Testing Focus / Notes", "headers": [ "AI Application", "Key Testing Focus", "Notes" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-13", "caption": "Table 13. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-14", "caption": "Table 14. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-15", "caption": "Table 15. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-16", "caption": "Table 16. AI Application / Impact Focus / Notes", "headers": [ "AI Application", "Impact Focus", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-17", "caption": "Table 17. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-18", "caption": "Table 18. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-19", "caption": "Table 19. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-20", "caption": "Table 20. Context / Suitability / Notes", "headers": [ "Context", "Suitability", "Notes" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-20-the-ethics-of-ai-and-data-table-21", "caption": "Table 21. Element / Description", "headers": [ "Element", "Description" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-20-the-ethics-of-ai-and-data" }, { "id": "chapter-21-product-management-and-product-strategy-table-1", "caption": "Table 1. Candidate / Reach per quarter / Impact", "headers": [ "Candidate", "Reach per quarter", "Impact", "Confidence", "Effort (person-months)", "RICE score" ], "sourceIds": [ "BB-C21-S05" ], "provenanceStatus": "constructed", "rowCount": 2, "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-21-product-management-and-product-strategy-table-2", "caption": "Table 2. Horizon / Decision meaning / Minimum evidence and communication", "headers": [ "Horizon", "Decision meaning", "Minimum evidence and communication" ], "sourceIds": [ "BB-C21-S06" ], "provenanceStatus": "constructed", "rowCount": 3, "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-21-product-management-and-product-strategy-table-3", "caption": "Table 3. Recruitment Dimension / Manager Question / Evidence to Record", "headers": [ "Recruitment Dimension", "Manager Question", "Evidence to Record" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-21-product-management-and-product-strategy-table-4", "caption": "Table 4. Level / Definition / Constructed Example", "headers": [ "Level", "Definition", "Constructed Example", "Traceability Test" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-21-product-management-and-product-strategy-table-5", "caption": "Table 5. Blueprint Lane / Discover and Start / Submit", "headers": [ "Blueprint Lane", "Discover and Start", "Submit", "Review and Clarify", "Outcome and Recover" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-21-product-management-and-product-strategy-table-6", "caption": "Table 6. Criterion / Evidence / Concept A", "headers": [ "Criterion", "Evidence", "Concept A", "Concept B", "Uncertainty or Disqualifier" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 6, "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-21-product-management-and-product-strategy-table-7", "caption": "Table 7. Question / Lowest Useful Prototype / Evidence Produced", "headers": [ "Question", "Lowest Useful Prototype", "Evidence Produced" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-21-product-management-and-product-strategy-table-8", "caption": "Table 8. Gate / Minimum Evidence / Decision and Owner", "headers": [ "Gate", "Minimum Evidence", "Decision and Owner" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 6, "entrySlug": "chapter-21-product-management-and-product-strategy" }, { "id": "chapter-22-data-analysis-and-insights-table-1", "caption": "Table 1. Layer / Question / Output", "headers": [ "Layer", "Question", "Output" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-2", "caption": "Table 2. Element / Purpose / Example", "headers": [ "Element", "Purpose", "Example" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-3", "caption": "Table 3. Evidence Situation / Managerial Use / Decision Stance", "headers": [ "Evidence Situation", "Managerial Use", "Decision Stance" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-4", "caption": "Table 4. Result / Interpretation / Decision Implication", "headers": [ "Result", "Interpretation", "Decision Implication" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-5", "caption": "Table 5. Output Item / Analyst Language / Manager Translation", "headers": [ "Output Item", "Analyst Language", "Manager Translation" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 8, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-6", "caption": "Table 6. Analytical Need / Use / Avoid", "headers": [ "Analytical Need", "Use", "Avoid" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 7, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-7", "caption": "Table 7. Level / Example / Managerial Purpose", "headers": [ "Level", "Example", "Managerial Purpose" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-8", "caption": "Table 8. Type / Comparison Target / Best Use", "headers": [ "Type", "Comparison Target", "Best Use" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-9", "caption": "Table 9. Gap / Likely Cause / Evidence Quality", "headers": [ "Gap", "Likely Cause", "Evidence Quality", "Action", "Owner" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 2, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-10", "caption": "Table 10. Assumption / Base Case / Downside Case", "headers": [ "Assumption", "Base Case", "Downside Case", "Upside Case", "Decision Sensitivity", "Action" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-11", "caption": "Table 11. Input Type / Practical Distribution Choice / Example", "headers": [ "Input Type", "Practical Distribution Choice", "Example" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-12", "caption": "Table 12. Decision question / Calculation / Result", "headers": [ "Decision question", "Calculation", "Result", "Managerial meaning" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 10, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-13", "caption": "Table 13. Estimand Element / Managerial Question / Example", "headers": [ "Estimand Element", "Managerial Question", "Example" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-14", "caption": "Table 14. Standardized MDE / Required Sample Per Arm", "headers": [ "Standardized MDE", "Required Sample Per Arm" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 7, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-15", "caption": "Table 15. Element / Meaning / Product-Mix Teaching Model", "headers": [ "Element", "Meaning", "Product-Mix Teaching Model" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-16", "caption": "Table 16. Feasible Vertex / Objective 40x + 30y / Interpretation", "headers": [ "Feasible Vertex", "Objective 40x + 30y", "Interpretation" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "chapter-22-data-analysis-and-insights-table-17", "caption": "Table 17. Question / Pass Standard", "headers": [ "Question", "Pass Standard" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 14, "entrySlug": "chapter-22-data-analysis-and-insights" }, { "id": "appendix-a-framework-selection-decision-trees-table-1", "caption": "Table 1. Decision Question / Destination / Use Boundary", "headers": [ "Decision Question", "Destination", "Use Boundary" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 11, "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-a-framework-selection-decision-trees-table-2", "caption": "Table 2. Business Function / Primary Chapters / Supporting Chapters", "headers": [ "Business Function", "Primary Chapters", "Supporting Chapters" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 9, "entrySlug": "appendix-a-framework-selection-decision-trees" }, { "id": "appendix-b-contrarian-business-perspectives-table-1", "caption": "Table 1. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "appendix-b-contrarian-business-perspectives" }, { "id": "appendix-b-contrarian-business-perspectives-table-2", "caption": "Table 2. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 5, "entrySlug": "appendix-b-contrarian-business-perspectives" }, { "id": "appendix-b-contrarian-business-perspectives-table-3", "caption": "Table 3. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "appendix-b-contrarian-business-perspectives" }, { "id": "appendix-b-contrarian-business-perspectives-table-4", "caption": "Table 4. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "appendix-b-contrarian-business-perspectives" }, { "id": "appendix-b-contrarian-business-perspectives-table-5", "caption": "Table 5. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "appendix-b-contrarian-business-perspectives" }, { "id": "appendix-b-contrarian-business-perspectives-table-6", "caption": "Table 6. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "appendix-b-contrarian-business-perspectives" }, { "id": "appendix-b-contrarian-business-perspectives-table-7", "caption": "Table 7. # / Default hypothesis / Rival hypothesis", "headers": [ "#", "Default hypothesis", "Rival hypothesis", "Decision evidence to seek" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 1, "entrySlug": "appendix-b-contrarian-business-perspectives" }, { "id": "appendix-b-contrarian-business-perspectives-table-8", "caption": "Table 8. Field / Record", "headers": [ "Field", "Record" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 14, "entrySlug": "appendix-b-contrarian-business-perspectives" }, { "id": "appendix-c-public-record-decision-cases-table-1", "caption": "Table 1. Case / Dated decision point / Primary managerial tension", "headers": [ "Case", "Dated decision point", "Primary managerial tension", "Principal chapter connections" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 5, "entrySlug": "appendix-c-public-record-decision-cases" }, { "id": "appendix-c-public-record-decision-cases-table-2", "caption": "Table 2. Evidence item / What the public record supports / What remains uncertain at the decision point", "headers": [ "Evidence item", "What the public record supports", "What remains uncertain at the decision point" ], "sourceIds": [ "BB-C23-S01", "BB-C23-S02" ], "provenanceStatus": "source-linked", "rowCount": 4, "entrySlug": "appendix-c-public-record-decision-cases" }, { "id": "appendix-c-public-record-decision-cases-table-3", "caption": "Table 3. Alternative / What it preserves / What it puts at risk or leaves unresolved", "headers": [ "Alternative", "What it preserves", "What it puts at risk or leaves unresolved" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "appendix-c-public-record-decision-cases" }, { "id": "appendix-c-public-record-decision-cases-table-4", "caption": "Table 4. Evidence or obligation / Public-record basis / Decision uncertainty", "headers": [ "Evidence or obligation", "Public-record basis", "Decision uncertainty" ], "sourceIds": [ "BB-C23-S03", "BB-C23-S04" ], "provenanceStatus": "source-linked", "rowCount": 4, "entrySlug": "appendix-c-public-record-decision-cases" }, { "id": "appendix-c-public-record-decision-cases-table-5", "caption": "Table 5. Alternative / What it emphasizes / Principal trade-offs", "headers": [ "Alternative", "What it emphasizes", "Principal trade-offs" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "appendix-c-public-record-decision-cases" }, { "id": "appendix-c-public-record-decision-cases-table-6", "caption": "Table 6. System surface / Evidence reconstructed from the public record / Missing decision information", "headers": [ "System surface", "Evidence reconstructed from the public record", "Missing decision information" ], "sourceIds": [ "BB-C23-S06", "BB-C23-S05" ], "provenanceStatus": "constructed", "rowCount": 4, "entrySlug": "appendix-c-public-record-decision-cases" }, { "id": "appendix-c-public-record-decision-cases-table-7", "caption": "Table 7. Alternative / Potential advantage / Principal risk", "headers": [ "Alternative", "Potential advantage", "Principal risk" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "appendix-c-public-record-decision-cases" }, { "id": "appendix-c-public-record-decision-cases-table-8", "caption": "Table 8. Evidence surface / Source-grounded signal / Important unknown", "headers": [ "Evidence surface", "Source-grounded signal", "Important unknown" ], "sourceIds": [ "BB-C23-S07", "BB-C23-S08" ], "provenanceStatus": "source-linked", "rowCount": 4, "entrySlug": "appendix-c-public-record-decision-cases" }, { "id": "appendix-c-public-record-decision-cases-table-9", "caption": "Table 9. Alternative / Potential advantage / Principal risk", "headers": [ "Alternative", "Potential advantage", "Principal risk" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "appendix-c-public-record-decision-cases" }, { "id": "appendix-c-public-record-decision-cases-table-10", "caption": "Table 10. Evidence surface / Public-record signal available by the decision point / Key uncertainty", "headers": [ "Evidence surface", "Public-record signal available by the decision point", "Key uncertainty" ], "sourceIds": [ "BB-C23-S09", "BB-C23-S10" ], "provenanceStatus": "source-linked", "rowCount": 4, "entrySlug": "appendix-c-public-record-decision-cases" }, { "id": "appendix-c-public-record-decision-cases-table-11", "caption": "Table 11. Alternative / Potential advantage / Principal risk", "headers": [ "Alternative", "Potential advantage", "Principal risk" ], "sourceIds": [], "provenanceStatus": "unlinked", "rowCount": 4, "entrySlug": "appendix-c-public-record-decision-cases" } ], "tools": [ { "id": "chapter-01-macroeconomics-for-strategic-leaders-tool-1", "label": "DCF valuation template", "target": "../../templates/04-DCF-Valuation-Model-Template.md", "sourcePath": "templates/04-DCF-Valuation-Model-Template.md", "outputPath": "downloads/chapter-01-macroeconomics-for-strategic-leaders-04-DCF-Valuation-Model-Template.md", "mediaType": "text/markdown", "checksum": "4e70a035bef88c72be33dc85e6b59ce96d0eeaa0e835757757546175bbedf6ba", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" }, { "id": "chapter-01-macroeconomics-for-strategic-leaders-tool-2", "label": "DCF workbook", "target": "../../models/04_DCF_Valuation_Model.xlsx", "sourcePath": "models/04_DCF_Valuation_Model.xlsx", "outputPath": "downloads/chapter-01-macroeconomics-for-strategic-leaders-04_DCF_Valuation_Model.xlsx", "mediaType": "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet", "checksum": "d2c5fdc418b4edf60d3f0f53d9e8cca15f5a42d93b0a09e0beffd33809a220cd", "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders" } ], "sources": [ { "source_id": "BB-C01-S01", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Business Cycle Analysis", "authors": "Kydland, F. E.; Prescott, E. C.", "year": 1990, "title": "Business Cycles: Real Facts and a Monetary Myth", "venue": "Federal Reserve Bank of Minneapolis Quarterly Review", "source_type": "academic article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.minneapolisfed.org/research/quarterly-review/business-cycles-real-facts-and-a-monetary-myth", "doi": "10.21034/qr.1421", "claim_notes": "Inspected Federal Reserve Bank of Minneapolis page; supports real-business-cycle framing and the use of observed cyclical facts in theory development, not specific firm-return claims.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "- The framework organizes scenarios; it does not establish a causal forecast of firm demand or returns. [BB-C01-S01]" ] } ] }, { "source_id": "BB-C01-S02", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Yield Curve and Recession Forecasting", "authors": "Estrella, A.; Mishkin, F. S.", "year": 1998, "title": "Predicting U.S. Recessions: Financial Variables as Leading Indicators", "venue": "Review of Economics and Statistics", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://doi.org/10.1162/003465398557320", "doi": "10.1162/003465398557320", "claim_notes": "Inspected DOI/NBER records; supports the yield curve and other financial variables as leading recession indicators over 1-8 quarter horizons. Does not support over-precise universal accuracy claims.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "- Yield Curve & Recession Forecasting (Framework 10): A well-studied financial leading indicator for recessions. [BB-C01-S02]", "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]", "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]", "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]", "- Negative spread: Increase the weight on downside scenarios only after checking forecast horizon, false positives, and firm evidence. [BB-C01-S02] [BB-C01-S16]", "- 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]" ] } ] }, { "source_id": "BB-C01-S03", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Monetary Policy and Market Response", "authors": "Bernanke, B. S.; Kuttner, K. N.", "year": 2005, "title": "What Explains the Stock Market's Reaction to Federal Reserve Policy?", "venue": "Journal of Finance", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://doi.org/10.1111/j.1540-6261.2005.00760.x", "doi": "10.1111/j.1540-6261.2005.00760.x", "claim_notes": "Inspected DOI metadata; supports market reactions to Federal Reserve policy surprises, especially equity-price sensitivity to unexpected policy changes.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "- 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]" ] } ] }, { "source_id": "BB-C01-S04", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Business Cycle Measurement", "authors": "Burns, A. F.; Mitchell, W. C.", "year": 1946, "title": "Measuring Business Cycles", "venue": "National Bureau of Economic Research", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.nber.org/books-and-chapters/measuring-business-cycles", "doi": null, "claim_notes": "Inspected NBER book page; supports business-cycle measurement, dating, and cyclical-behavior framing.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C01-S05", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Interest Rates and Investment", "authors": "Jorgenson, D. W.", "year": 1963, "title": "Capital Theory and Investment Behavior", "venue": "American Economic Review", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.jstor.org/stable/1823868", "doi": null, "claim_notes": "Inspected JSTOR record; supports neoclassical investment theory and cost-of-capital/user-cost framing, not a universal interest-rate elasticity.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C01-S06", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Currency Hedging", "authors": "Allayannis, G.; Weston, J. P.", "year": 2001, "title": "The Use of Foreign Currency Derivatives and Firm Market Value", "venue": "Review of Financial Studies", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://academic.oup.com/rfs/article-abstract/14/1/243/1588558", "doi": "10.1093/rfs/14.1.243", "claim_notes": "Inspected Oxford Academic/SSRN records; supports a positive relation between foreign-currency derivatives and firm value for exposed firms, not a generic 30-40% volatility-reduction claim.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "- The cited association between derivative use and firm value does not prove that hedging creates value for every firm. [BB-C01-S06]" ] } ] }, { "source_id": "BB-C01-S07", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Taylor Rule", "authors": "Taylor, J. B.", "year": 1993, "title": "Discretion versus Policy Rules in Practice", "venue": "Carnegie-Rochester Conference Series on Public Policy", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://web.stanford.edu/~johntayl/Onlinepaperscombinedbyyear/1993/Discretion_versus_Policy_Rules_in_Practice.pdf", "doi": "10.1016/0167-2231(93)90009-L", "claim_notes": "Inspected Stanford PDF and ScienceDirect metadata; supports policy-rule framing and federal-funds-rate response to inflation and real-income/output gaps.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "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]", "- The Taylor Rule is a sensitivity benchmark, not a promise of the next decision. [BB-C01-S07]" ] } ] }, { "source_id": "BB-C01-S08", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Fiscal Multipliers", "authors": "Ramey, V. A.", "year": 2019, "title": "Ten Years After the Financial Crisis: What Have We Learned from the Renaissance in Fiscal Research?", "venue": "Journal of Economic Perspectives", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.aeaweb.org/articles?id=10.1257/jep.33.2.89", "doi": "10.1257/jep.33.2.89", "claim_notes": "Inspected AEA/NBER records; supports that most average spending multiplier estimates cluster around 0.6 to 1 and that fiscal effects are method/context dependent.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "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]", "- Multiplier estimates vary with identification method, slack, monetary conditions, financing, timing, and the type of fiscal change. [BB-C01-S08]" ] } ] }, { "source_id": "BB-C01-S09", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Supply Chain Shock Propagation", "authors": "Carvalho, V. M.; Nirei, M.; Saito, Y. U.; Tahbaz-Salehi, A.", "year": 2021, "title": "Supply Chain Disruptions: Evidence from the Great East Japan Earthquake", "venue": "Quarterly Journal of Economics", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://academic.oup.com/qje/article/136/2/1255/6030033", "doi": "10.1093/qje/qjaa044", "claim_notes": "Inspected Oxford Academic page; supports upstream/downstream supply-chain propagation of shocks, not a generic playbook recovery-speed percentage.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "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]", "- Evidence from one disaster does not establish a universal inventory level, diversification rule, or response schedule. [BB-C01-S09]" ] } ] }, { "source_id": "BB-C01-S10", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Labor Market Indicators", "authors": "U.S. Bureau of Labor Statistics", "year": 2026, "title": "Job Openings and Labor Turnover Survey", "venue": "BLS", "source_type": "official dataset", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.bls.gov/jlt/", "doi": null, "claim_notes": "Inspected BLS JOLTS pages; supports using job openings, hires, quits, layoffs, and separations as labor-market indicators. Current values drift and should not be hard-coded.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "- Job Openings (JOLTS): Compare openings, hires, and unemployed workers while allowing for matching frictions and industry mix. [BB-C01-S10]", "- 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]" ] } ] }, { "source_id": "BB-C01-S11", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Federal Reserve Mandate", "authors": "Board of Governors of the Federal Reserve System", "year": 2025, "title": "What economic goals does the Federal Reserve seek to achieve through its monetary policy?", "venue": "Federal Reserve", "source_type": "official publication", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.federalreserve.gov/faqs/what-economic-goals-does-federal-reserve-seek-to-achieve-through-monetary-policy.htm", "doi": null, "claim_notes": "Inspected Federal Reserve FAQ; supports the U.S. dual mandate of maximum employment and stable prices.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "- Federal Reserve (U.S.): Dual mandate: maximum employment and stable prices. [BB-C01-S11]" ] } ] }, { "source_id": "BB-C01-S12", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Pricing Fairness", "authors": "Kahneman, D.; Knetsch, J. L.; Thaler, R. H.", "year": 1986, "title": "Fairness as a Constraint on Profit Seeking: Entitlements in the Market", "venue": "American Economic Review", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.jstor.org/stable/1806070", "doi": null, "claim_notes": "Inspected JSTOR/RePEc records; supports customer fairness constraints on price and wage decisions, including backlash risk when firms exploit demand shifts.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "- Perceived fairness is a design constraint, not a universal estimate of churn or profit. Test actual customer response. [BB-C01-S12]" ] } ] }, { "source_id": "BB-C01-S13", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "GDP Measurement and Data Vintages", "authors": "U.S. Bureau of Economic Analysis", "year": 2026, "title": "Gross Domestic Product", "venue": "U.S. Bureau of Economic Analysis", "source_type": "official statistical agency resource", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.bea.gov/data/gdp/gross-domestic-product", "doi": null, "claim_notes": "Inspected the current BEA GDP page. Supports GDP as the value of final goods and services produced in the United States, the distinction between real and current-dollar series, release dates, revision information, and vintage history. Current values are time-varying and are not used as fixed claims in the chapter.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "- GDP is revised, aggregates unlike sectors, and can diverge from the firm's actual markets. [BB-C01-S13]" ] } ] }, { "source_id": "BB-C01-S14", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Business Cycle Dating", "authors": "National Bureau of Economic Research Business Cycle Dating Committee", "year": 2026, "title": "Business Cycle Dating", "venue": "National Bureau of Economic Research", "source_type": "official institutional methodology", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.nber.org/research/business-cycle-dating", "doi": null, "claim_notes": "Inspected the current NBER methodology. Supports the depth, diffusion, and duration recession criteria; use of multiple real-activity indicators; and the retrospective nature of U.S. peak and trough dating. It does not support real-time phase certainty.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "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]", "- Business-cycle turning points are dated retrospectively, so this framework cannot identify the current phase with certainty. [BB-C01-S14]", "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]" ] } ] }, { "source_id": "BB-C01-S15", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Yield Curve Model Risk", "authors": "Engstrom, E. C.; Sharpe, S. A.", "year": 2022, "title": "(Don't Fear) The Yield Curve, Reprise", "venue": "FEDS Notes, Board of Governors of the Federal Reserve System", "source_type": "official central-bank research note", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.federalreserve.gov/econres/notes/feds-notes/dont-fear-the-yield-curve-reprise-20220325.html", "doi": "10.17016/2380-7172.3099", "claim_notes": "Inspected the Federal Reserve note. Supports the authors' finding that the 10-year/2-year spread added no incremental information once their near-term forward spread was monitored and their warning against treating term spreads as causal or omniscient. It is a staff research note, not official Board policy.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "- 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]", "- 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]", "- 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]" ] } ] }, { "source_id": "BB-C01-S16", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Current Recession-Risk Evidence", "authors": "Ahn, H. J.; Eo, Y.; Moyon, L.", "year": 2026, "title": "Assessing Recession Risks with State-Level Data", "venue": "FEDS Notes, Board of Governors of the Federal Reserve System", "source_type": "official central-bank research note", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.federalreserve.gov/econres/notes/feds-notes/assessing-recession-risks-with-state-level-data-20260107.html", "doi": "10.17016/2380-7172.3992", "claim_notes": "Inspected the Federal Reserve note. Supports the bounded current observation that the 10-year/3-month spread was negative in 2023 and 2024 but a U.S. recession did not materialize in those years. It is a staff research note and does not invalidate all yield-curve models.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "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]", "- Negative spread: Increase the weight on downside scenarios only after checking forecast horizon, false positives, and firm evidence. [BB-C01-S02] [BB-C01-S16]", "- 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]", "- 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]" ] } ] }, { "source_id": "BB-C01-S17", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "European Central Bank Mandate", "authors": "European Central Bank", "year": 2026, "title": "Introduction to Monetary Policy", "venue": "European Central Bank", "source_type": "official central-bank publication", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.ecb.europa.eu/mopo/intro/html/index.en.html", "doi": null, "claim_notes": "Inspected the current ECB page. Supports price stability as the primary monetary-policy objective, a 2 percent medium-term inflation aim, and subordinate support for broader EU policies without prejudice to price stability.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "- 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]" ] } ] }, { "source_id": "BB-C01-S18", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Bank of England Mandate", "authors": "Bank of England", "year": 2026, "title": "Monetary Policy", "venue": "Bank of England", "source_type": "official central-bank publication", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.bankofengland.co.uk/monetary-policy", "doi": null, "claim_notes": "Inspected the current Bank of England page. Supports low and stable inflation as the primary objective, the government-set 2 percent medium-term target, and support for strong, sustainable, balanced growth subject to the primary objective. Time-varying current rates are not hard-coded in the chapter.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "- 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]" ] } ] }, { "source_id": "BB-C01-S19", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Growth Accounting", "authors": "Solow, R. M.", "year": 2001, "title": "After \"Technical Progress and the Aggregate Production Function\"", "venue": "New Developments in Productivity Analysis (University of Chicago Press / NBER)", "source_type": "author retrospective book chapter", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.nber.org/system/files/chapters/c10126/c10126.pdf", "doi": null, "claim_notes": "Full seven-page NBER-hosted chapter inspected. Solow retrospectively describes the continuing effort to assign parts of the growth-accounting residual to measured inputs or output adjustments and identifies measurement, conceptual, modeling, and aggregate-production-function limitations. Supports a bounded discussion of the residual and model assumptions; it does not make the residual a pure technology measure or a firm-level causal estimator.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C01-S20", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Beveridge Curve", "authors": "Federal Reserve Bank of St. Louis", "year": 2025, "title": "The Unusual Shape of the Beveridge Curve", "venue": "FRED Blog", "source_type": "official central-bank data explainer", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://fredblog.stlouisfed.org/2025/01/the-unusual-shape-of-the-beveridge-curve/", "doi": null, "claim_notes": "Inspected the St. Louis Fed explanation. Supports the unemployment/job-openings relationship and the observation that the post-pandemic curve shifted, motivating caution about a fixed mapping. The blog is an official explainer, not a causal labor-policy evaluation.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "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]", "- 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]", "- The Beveridge curve can shift, so it should not be treated as a fixed hiring rule. [BB-C01-S20]" ] } ] }, { "source_id": "BB-C01-S21", "chapter_slugs": [ "chapter-01-macroeconomics-for-strategic-leaders" ], "framework": "Aggregate Demand and Aggregate Supply", "authors": "Greenlaw, S. A.; Shapiro, D.; MacDonald, D.", "year": 2022, "title": "Introduction to the Aggregate Supply-Aggregate Demand Model", "venue": "OpenStax Principles of Economics 3e", "source_type": "open educational textbook", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://openstax.org/books/principles-economics-3e/pages/24-introduction-to-the-aggregate-supply-aggregate-demand-model", "doi": null, "claim_notes": "Inspected the OpenStax chapter and attribution information. Supports the aggregate demand/supply model as a framework for short-run price/output tradeoffs. The manuscript paraphrases basic directional effects and does not reproduce OpenStax figures or text.", "uses": [ { "entrySlug": "chapter-01-macroeconomics-for-strategic-leaders", "entryTitle": "Macroeconomics for Strategic Leaders", "excerpts": [ "- 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]", "- 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]", "- The aggregate supply-and-demand model holds other conditions constant and can obscure simultaneous demand, supply, financial, and policy shocks. [BB-C01-S21]" ] } ] }, { "source_id": "BB-C16-S01", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "AI Risk Management", "authors": "National Institute of Standards and Technology", "year": 2023, "title": "Artificial Intelligence Risk Management Framework (AI RMF 1.0)", "venue": "NIST", "source_type": "official framework", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10", "doi": "10.6028/NIST.AI.100-1", "claim_notes": "Inspected NIST publication record and AI RMF materials; supports Govern/Map/Measure/Manage risk functions and trustworthy-AI characteristics. Does not support hard ROI, deployment-rate, or maturity-percentage claims.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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]", "- Governance implication: treat value realization as an operating discipline: use-case selection, data readiness, risk controls, product ownership, deployment, and change management. [BB-C16-S01] [BB-C16-S06]", "The Reality: Buying or partnering may reduce time and delivery risk for a mature capability; building may be justified when proprietary data, workflow control, product differentiation, security, or economics materially change the decision. Compare the options on the same lifecycle, risk, and strategic assumptions. [BB-C16-S01] [BB-C16-S06]", "Governance introduced only after deployment may discover design, data, authority, or control problems late. Earlier risk work can reduce exposure and improve detectability, but it cannot guarantee that bias, harm, regulatory breach, or operational failure will not occur. [BB-C16-S01] [BB-C16-S04] [BB-C16-S06]", "The mental model: AI governance is an accountable risk-management system, not an insurance policy or legal safe harbor. Risk review, testing, documentation, oversight, incident response, and ownership can reduce risk and improve decisions; residual risk remains and requires human acceptance by the appropriate authority. [BB-C16-S01] [BB-C16-S06]" ] } ] }, { "source_id": "BB-C16-S02", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "Responsible AI Principles", "authors": "OECD", "year": 2024, "title": "OECD AI Principles", "venue": "OECD.AI Policy Observatory", "source_type": "official policy framework", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.oecd.org/en/topics/sub-issues/ai-principles.html", "doi": null, "claim_notes": "Inspected OECD principles page; supports the 2019 principles updated in 2024, including inclusive growth, human rights, transparency, robustness, accountability, investment, ecosystem, policy, skills, and cooperation themes.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C16-S03", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "AI Adoption and Capability Trends", "authors": "Stanford Institute for Human-Centered Artificial Intelligence", "year": 2026, "title": "AI Index Report 2026", "venue": "Stanford HAI", "source_type": "research report", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://hai.stanford.edu/ai-index/2026-ai-index-report", "doi": null, "claim_notes": "Inspected Stanford HAI 2026 report page; supports broad AI adoption and capability-trend context, including reported high organizational adoption. Do not use for unsupported project-failure-rate claims.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]", "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]", "Most AI strategy guides assume your project will succeed. This section starts from a more useful premise: broad AI adoption does not automatically translate into measurable business value. Current public reports show widespread adoption alongside uneven value capture, so understanding why projects stall is more valuable than copying success stories. [BB-C16-S03] [BB-C16-S08]", "An organization can adopt AI tools, announce a strategy, and run pilots without demonstrating attributable business value. Public surveys document broad adoption and uneven value capture, but they do not establish the motives of any executive, team, or adviser. Diagnose the operating evidence instead: ownership, baselines, controls, adoption, and measured outcomes. [BB-C16-S03] [BB-C16-S08]", "- Stanford AI Index: AI adoption is widespread, but the report should be used for trend context rather than as proof that any specific project will succeed. [BB-C16-S03]", "- Generative AI is now part of mainstream enterprise experimentation and product design. [BB-C16-S03] [BB-C16-S04]", "- Multimodal models enable text, image, audio, and structured-data workflows. [BB-C16-S03]" ] } ] }, { "source_id": "BB-C16-S04", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "Generative AI Risk Management", "authors": "National Institute of Standards and Technology", "year": 2024, "title": "Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile", "venue": "NIST", "source_type": "official profile", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence", "doi": "10.6028/NIST.AI.600-1", "claim_notes": "Inspected NIST publication record; supports generative-AI-specific risk management as a companion profile to AI RMF 1.0.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]", "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]", "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]", "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]", "- Reality: LLMs are powerful tools for specific use cases, but they need evaluation, retrieval, security, monitoring, and fallback design for production use. [BB-C16-S04] [BB-C16-S10]", "Governance introduced only after deployment may discover design, data, authority, or control problems late. Earlier risk work can reduce exposure and improve detectability, but it cannot guarantee that bias, harm, regulatory breach, or operational failure will not occur. [BB-C16-S01] [BB-C16-S04] [BB-C16-S06]", "- Generative AI is now part of mainstream enterprise experimentation and product design. [BB-C16-S03] [BB-C16-S04]" ] } ] }, { "source_id": "BB-C16-S05", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "AI Regulation", "authors": "European Commission", "year": 2024, "title": "AI Act", "venue": "European Commission Digital Strategy", "source_type": "official policy page", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai", "doi": null, "claim_notes": "Inspected European Commission AI Act page; supports risk-based EU AI Act framing, entry into force on August 1, 2024, and phased/full applicability dates.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]", "- Regulation and governance increasingly require risk-based controls, documentation, and accountable ownership. [BB-C16-S05] [BB-C16-S06]" ] } ] }, { "source_id": "BB-C16-S06", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "AI Management System", "authors": "International Organization for Standardization", "year": 2023, "title": "ISO/IEC 42001:2023 Artificial intelligence - Management system", "venue": "ISO", "source_type": "international standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.iso.org/standard/42001", "doi": null, "claim_notes": "Inspected ISO standard page; supports AI management-system framing for organizational governance, risk, opportunities, ethics, transparency, and continuous learning.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]", "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]", "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]", "- Governance implication: treat value realization as an operating discipline: use-case selection, data readiness, risk controls, product ownership, deployment, and change management. [BB-C16-S01] [BB-C16-S06]", "The Reality: Buying or partnering may reduce time and delivery risk for a mature capability; building may be justified when proprietary data, workflow control, product differentiation, security, or economics materially change the decision. Compare the options on the same lifecycle, risk, and strategic assumptions. [BB-C16-S01] [BB-C16-S06]", "Governance introduced only after deployment may discover design, data, authority, or control problems late. Earlier risk work can reduce exposure and improve detectability, but it cannot guarantee that bias, harm, regulatory breach, or operational failure will not occur. [BB-C16-S01] [BB-C16-S04] [BB-C16-S06]", "The mental model: AI governance is an accountable risk-management system, not an insurance policy or legal safe harbor. Risk review, testing, documentation, oversight, incident response, and ownership can reduce risk and improve decisions; residual risk remains and requires human acceptance by the appropriate authority. [BB-C16-S01] [BB-C16-S06]", "- Regulation and governance increasingly require risk-based controls, documentation, and accountable ownership. [BB-C16-S05] [BB-C16-S06]" ] } ] }, { "source_id": "BB-C16-S07", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "Data Quality for Analytics and Machine Learning", "authors": "International Electrotechnical Commission", "year": 2024, "title": "ISO/IEC 5259-4:2024 Artificial intelligence - Data quality for analytics and machine learning - Part 4: Data quality process framework", "venue": "IEC Webstore", "source_type": "international standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://webstore.iec.ch/en/publication/98263", "doi": null, "claim_notes": "Inspected IEC/ISO records; supports using a data-quality process framework for analytics and machine learning rather than universal sample-size or missingness thresholds.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]", "One common reason AI projects fail is bad data. You can't reliably fix a data problem with a better model. [BB-C16-S07]" ] } ] }, { "source_id": "BB-C16-S08", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "Enterprise Generative AI Value Realization", "authors": "Singla, A.; Sukharevsky, A.; Yee, L.; Chui, M.; Hall, B.", "year": 2025, "title": "The state of AI: How organizations are rewiring to capture value", "venue": "McKinsey QuantumBlack", "source_type": "industry survey report", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai-how-organizations-are-rewiring-to-capture-value", "doi": null, "claim_notes": "Official 26-page March 2025 McKinsey report inspected in full. It discloses a McKinsey Global Survey of 1,491 participants at all organizational levels conducted July 16-31, 2024. Supports respondent-reported widespread AI/gen-AI use, uneven scaling practices, and the finding that more than 80 percent of respondents reported no tangible enterprise-level EBIT impact from gen AI. Results are self-reported, survey-specific associations; they do not establish audited financial impact, causal effects, universal rates, project failure, or motives.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]", "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]", "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]", "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]", "Most AI strategy guides assume your project will succeed. This section starts from a more useful premise: broad AI adoption does not automatically translate into measurable business value. Current public reports show widespread adoption alongside uneven value capture, so understanding why projects stall is more valuable than copying success stories. [BB-C16-S03] [BB-C16-S08]", "An organization can adopt AI tools, announce a strategy, and run pilots without demonstrating attributable business value. Public surveys document broad adoption and uneven value capture, but they do not establish the motives of any executive, team, or adviser. Diagnose the operating evidence instead: ownership, baselines, controls, adoption, and measured outcomes. [BB-C16-S03] [BB-C16-S08]", "- McKinsey State of AI: many organizations report AI use, but measurable EBIT impact is more limited and context-dependent. [BB-C16-S08]", "The Problem: Model deployment, tool usage, or accuracy does not by itself establish attributable business impact. In McKinsey's July 2024 respondent survey, reported gen-AI use was widespread while most respondents reported no tangible enterprise-level EBIT impact; the result is self-reported and survey-specific, not a causal estimate or universal rate. [BB-C16-S08]" ] } ] }, { "source_id": "BB-C16-S09", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "MLOps and ML Pipeline Automation", "authors": "Google Cloud", "year": 2024, "title": "MLOps: Continuous delivery and automation pipelines in machine learning", "venue": "Google Cloud Architecture Center", "source_type": "technical architecture guide", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://docs.cloud.google.com/architecture/mlops-continuous-delivery-and-automation-pipelines-in-machine-learning", "doi": null, "claim_notes": "Inspected Google Cloud architecture guide; supports CI/CD/continuous-training framing for ML pipelines, primarily predictive ML systems.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C16-S10", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "Secure AI Model Development", "authors": "National Institute of Standards and Technology", "year": 2024, "title": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models", "venue": "NIST Special Publication 800-218A", "source_type": "official guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.nist.gov/publications/secure-software-development-practices-generative-ai-and-dual-use-foundation-models-ssdf", "doi": null, "claim_notes": "Inspected NIST SP 800-218A publication/news pages; supports secure-development practices for AI model development across the software development lifecycle.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]", "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]", "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]", "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]", "- Reality: LLMs are powerful tools for specific use cases, but they need evaluation, retrieval, security, monitoring, and fallback design for production use. [BB-C16-S04] [BB-C16-S10]", "- AI agents require stronger evaluation, monitoring, and secure-development controls before production use. [BB-C16-S10]" ] } ] }, { "source_id": "BB-C16-S11", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions", "chapter-20-the-ethics-of-ai-and-data" ], "framework": "AI Recruiting Bias Case", "authors": "Dastin, J.", "year": 2018, "title": "Amazon scraps secret AI recruiting tool that showed bias against women", "venue": "Reuters via OpenCasebook", "source_type": "news report", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://opencasebook.org/casebooks/1539-regulating-digital-technology-hls-1l-reading-group-fall-2020/resources/4.2-jeffrey-dastin-amazon-scraps-secret-ai-recruiting-tool-that-showed-bias-against-women-reuters-october-10-2018/", "doi": null, "claim_notes": "Inspected Reuters-linked OpenCasebook record; supports the Amazon recruiting-tool bias case as a cautionary example. Treat as case evidence, not general AI-bias prevalence evidence.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "Case Study 1: Amazon's Biased Hiring AI (2014-2018) [BB-C16-S11]", "Reuters reported that Amazon worked on an AI recruiting tool that was ultimately scrapped after it showed bias against women. The case is useful because it shows how historical hiring data can encode historical bias. [BB-C16-S11]" ] } ] }, { "source_id": "BB-C16-S12", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "Clinical AI Deployment Case", "authors": "Ruamviboonsuk, P.; et al.", "year": 2022, "title": "Real-time diabetic retinopathy screening by deep learning in a multisite national screening programme", "venue": "The Lancet Digital Health", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://pubmed.ncbi.nlm.nih.gov/35272972/", "doi": "10.1016/S2589-7500(22)00017-6", "claim_notes": "Inspected PubMed/Lancet records; supports real-time diabetic-retinopathy screening in Thai primary-care sites and the importance of workflow deployment context.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "Case Study 2: Google's Diabetic Retinopathy Screening Deployment Lesson [BB-C16-S12]", "Google Research and collaborators evaluated deep-learning diabetic retinopathy screening in Thailand's national screening program. The peer-reviewed case is best read as a deployment and workflow lesson: real-time AI can perform well, but field use still depends on image quality, clinical workflow, staffing, and escalation design. [BB-C16-S12]" ] } ] }, { "source_id": "BB-C16-S13", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "AI Healthcare Commercialization Case", "authors": "IBM", "year": 2022, "title": "Francisco Partners to Acquire IBM's Healthcare Data and Analytics Assets", "venue": "IBM Newsroom", "source_type": "company announcement", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://newsroom.ibm.com/2022-01-21-Francisco-Partners-to-Acquire-IBMs-Healthcare-Data-and-Analytics-Assets", "doi": null, "claim_notes": "Inspected IBM announcement; supports the sale of IBM healthcare data and analytics assets. Does not support unsourced Watson Health valuation, loss, or medical-performance claims.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "Case Study 3: IBM Healthcare Data and Analytics Asset Sale: Commercialization Checklist [BB-C16-S13]", "IBM announced in January 2022 that Francisco Partners would acquire its healthcare data and analytics assets, including Health Insights, MarketScan, Clinical Development, Social Program Management, Micromedex, and imaging software assets. [BB-C16-S13]" ] } ] }, { "source_id": "BB-C16-S14", "chapter_slugs": [ "chapter-16-ai-strategy-and-data-driven-decisions" ], "framework": "Agentic AI Identity and Authority", "authors": "National Institute of Standards and Technology; National Cybersecurity Center of Excellence", "year": 2026, "title": "New Concept Paper on Identity and Authority of Software Agents", "venue": "NIST", "source_type": "emerging official guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.nist.gov/news-events/news/2026/02/new-concept-paper-identity-and-authority-software-agents", "doi": null, "claim_notes": "Official NIST page inspected in full on 2026-07-11. It describes a February 2026 NCCoE concept paper for a potential project on applying identity standards and best practices to software and AI agents, and explicitly identifies identification, authorization, auditing, non-repudiation, and prompt-injection mitigation as open control questions. It is emerging work, not a final standard, certification, safe harbor, or complete agent-control framework.", "uses": [ { "entrySlug": "chapter-16-ai-strategy-and-data-driven-decisions", "entryTitle": "AI Strategy and Data-Driven Decisions", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C21-S01", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Jobs to Be Done", "authors": "Christensen, C. M.; Hall, T.; Dillon, K.; Duncan, D. S.", "year": 2016, "title": "Know Your Customers' Jobs to Be Done", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://hbr.org/2016/09/know-your-customers-jobs-to-be-done", "doi": null, "claim_notes": "Inspected HBR article page; supports JTBD framing, customer-job language, and the warning that customer profiles/correlations alone do not explain purchase choice.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Customers don't buy products; they \"hire\" them to do a job. JTBD is a framework for understanding the fundamental progress customers are trying to make in their lives. Pioneered by Clayton Christensen and coauthors, it shifts focus from demographics and features to the underlying job. [BB-C21-S01]", "Source-grounded view: Christensen, Hall, Dillon, and Duncan argue that innovation teams over-rely on customer profiles and correlation data when they should understand the job customers are trying to get done. Treat customer requests as clues about the job, not as finished product requirements. [BB-C21-S01]", "A product strategy canvas connects goals and product vision to desired customer and business outcomes; it is not merely a feature plan. [BB-C21-S18] The six-part canvas below is an author-created synthesis that combines that strategy framing with jobs-to-be-done questions. [BB-C21-S01] It prompts explicit choices but does not force clarity, prove demand, or guarantee differentiation. All examples and proposed metrics below are constructed teaching prompts, not claims about named companies or universal targets.", "- The Jobs-to-be-Done framing argues that customers struggle to articulate solutions, but can describe the progress they are trying to make in a situation. [BB-C21-S01]", "- Use interviews to understand the job, current workarounds, switching triggers, and constraints rather than to harvest a feature list. [BB-C21-S01]" ] } ] }, { "source_id": "BB-C21-S03", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Product-Market Fit", "authors": "Andreessen, M.", "year": 2007, "title": "The Only Thing That Matters", "venue": "Pmarca archive", "source_type": "practitioner essay", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://pmarchive.com/guide_to_startups_part4.html", "doi": null, "claim_notes": "Inspected archive; supports Andreessen's qualitative product/market fit definition and observable demand signals.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Product-market fit (PMF) is the most critical milestone for any product. Marc Andreessen defined it as being in a good market with a product that can satisfy that market, and emphasized that the signals are often visible in demand, usage, word of mouth, sales cycles, and customer pull. [BB-C21-S03]", "Despite this dashboard, the most important PMF signal is qualitative: Are users desperate for your product? Andreessen's PMF framing is intentionally qualitative: when PMF is weak, customers are not getting value, word of mouth is weak, and sales cycles drag; when PMF is strong, customers pull the product from the company. [BB-C21-S03]", "Remedy: Build the PMF Metrics Dashboard (Framework 3) . If relevant cohort retention trends toward zero, treat it as a signal to investigate before scaling. Go back to Product Discovery (Framework 7) and find the real customer job. [BB-C21-S03]" ] } ] }, { "source_id": "BB-C21-S04", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Product-Market Fit Survey", "authors": "Ellis, S.", "year": 2017, "title": "Using Product/Market Fit to Drive Sustainable Growth", "venue": "GrowthHackers", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://medium.com/growthhackers/using-product-market-fit-to-drive-sustainable-growth-58e9124ee8db", "doi": null, "claim_notes": "Inspected article; supports the 'very disappointed' survey question and Ellis's example of improving must-have responses to 40%.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "- User Desperation: Would users be \"very disappointed\" if product went away? Use the Sean Ellis survey as a directional PMF signal, with the 40% response level treated as a useful but not universal benchmark. [BB-C21-S04]", "Source-grounded view: Use metrics to diagnose health, but do not treat any single threshold as proof. Sean Ellis's \"very disappointed\" survey is useful because it combines a simple quantitative readout with follow-up questions about why users consider the product a must-have. [BB-C21-S04]", "- Evidence criteria: pre-specify the relevant value, usability, feasibility, viability, accessibility, risk, and strategy questions, sample, uncertainty, guardrails, and decision rule. A survey or small usability test answers a bounded question, not the entire product decision. [BB-C21-S04] [BB-C21-S10]" ] } ] }, { "source_id": "BB-C21-S05", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "RICE Prioritization", "authors": "McBride, S.", "year": 2016, "title": "RICE: Simple Prioritization for Product Managers", "venue": "Intercom", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/", "doi": null, "claim_notes": "Inspected Intercom article; supports RICE factors, formula, and guidance to use real measurements where possible.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "The RICE prioritization framework helps product managers compare feature requests from sales, customers, executives, and engineers. How do you decide what to build? RICE (Reach × Impact × Confidence ÷ Effort) is a prioritization system developed at Intercom to compare ideas through a consistent set of factors. [BB-C21-S05]", "RICE comparison record (constructed). Use one time horizon, population definition, impact scale, confidence convention, and effort unit across the options being compared. The score makes assumptions visible; it does not authorize shipment. [BB-C21-S05]", "3. Confidence: How confident are you in these estimates? Intercom's RICE method uses confidence to discount work where the evidence is weak. [BB-C21-S05]", "Tip: If confidence is low, gather more data before committing. [BB-C21-S05]", "Rank comparable ideas, inspect the underlying assumptions, and test sensitivity. RICE is a comparison aid, not an objective ranking: strategic coherence, dependencies, capacity, portfolio interaction, accessibility, legal/safety obligations, risk, and opportunity cost can override numerical order. [BB-C21-S05]", "Most roadmaps are wish lists, not commitments. RICE helps you say \"no\" to lower-confidence requests by making assumptions visible. [BB-C21-S05]", "Source-grounded view: Intercom presents RICE as a way to compare ideas consistently by estimating reach, impact, confidence, and effort. Treat the score as a decision aid, not a substitute for judgment: the quality of the ranking depends on the quality of the assumptions. [BB-C21-S05]" ] } ] }, { "source_id": "BB-C21-S06", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Now/Next/Later Roadmapping", "authors": "Bastow, J.", "year": 2022, "title": "Why I Invented the Now-Next-Later Roadmap", "venue": "ProdPad", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.prodpad.com/blog/invented-now-next-later-roadmap/", "doi": null, "claim_notes": "ProdPad article inspected. Supports Bastow's origin attribution, three flexible horizons, reduced false date certainty, and linking priorities to problems and objectives. The unsupported fixed quarterly-update marker was removed; local cadence and sharing rules are not attributed to the source.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "The Now/Next/Later roadmap makes uncertainty visible when dates and Gantt charts are often treated as stronger commitments than product teams can honestly make. You don't know how long every feature will take, requirements change, and priorities shift. The Now/Next/Later framework, popularized by Janna Bastow at ProdPad, replaces date-driven roadmaps with outcome-focused horizons. [BB-C21-S06]", "Now/Next/Later decision record (constructed). Horizons communicate evidence and commitment state, not universal calendar windows. Revisit them as learning, capacity, dependencies, obligations, or strategy change. [BB-C21-S06]" ] } ] }, { "source_id": "BB-C21-S07", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "North Star Metric", "authors": "Cutler, J.; Scherschligt, J.", "year": 2019, "title": "The North Star Playbook: The Guide to Discovering Your Product's North Star", "venue": "Amplitude", "source_type": "practitioner playbook", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://info.amplitude.com/rs/138-CDN-550/images/Amplitude-The-North-Star-Playbook.pdf", "doi": null, "claim_notes": "Official Amplitude playbook inspected; the co-author documents first-edition publication in 2019. Supports one value-representing North Star and a small set of influential inputs treated as assumptions to field-test. Direct-causal-driver, separate universal health-layer, and overbroad alignment wording were corrected. The current official PDF is a living undated revision; 2019 is the first-edition year, not a verified revision date.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "The North Star approach defines one metric intended to represent delivered product value, then links it to a small set of input metrics that the team believes influence it. The resulting structure is a set of assumptions to test, not a proven causal model. [BB-C21-S07]", "Product-metric hypothesis tree (constructed). A North Star candidate should represent recurring customer value for a defined product and population. Input and guardrail metrics are hypotheses, not proven causal levers. [BB-C21-S07]", "Figure 21.1. Product-metric hypothesis tree with value and guardrail measures. This author-created visual is a constructed teaching aid; it does not establish that any input causes the North Star outcome or that one metric hierarchy fits every product. [BB-C21-S07]", "- Definition: A small set of metrics hypothesized to influence the North Star; the relationships should be field-tested rather than treated as direct causal drivers. [BB-C21-S07]" ] } ] }, { "source_id": "BB-C21-S08", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Goodhart's Law", "authors": "Strathern, M.; Goodhart, C. A. E.", "year": 1997, "title": "Improving Ratings: Audit in the British University System", "venue": "European Review", "source_type": "academic article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://jgme.kglmeridian.com/view/journals/jgme/13/1/article-p2.xml", "doi": "10.4300/JGME-D-21-00103.1", "claim_notes": "Secondary academic article inspected via search; supports the common Strathern formulation and Goodhart origin for metric-target caution.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Source-grounded view: Goodhart's Law is the warning that a measure can lose its value when people are rewarded for optimizing the measure itself. In product work, this means a North Star should guide diagnosis and tradeoffs, not become a target that teams manipulate at the expense of customer value. [BB-C21-S08]", "- Metrics are diagnostic tools; Goodhart's Law warns that a measure can stop being useful when it becomes the target. [BB-C21-S08]" ] } ] }, { "source_id": "BB-C21-S09", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Product Discovery", "authors": "Torres, T.", "year": 2023, "title": "Everyone Can Do Continuous Discovery: Here's How", "venue": "Product Talk", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.producttalk.org/getting-started-with-discovery/", "doi": null, "claim_notes": "Inspected Product Talk article; supports continuous discovery definition as weekly customer touchpoints by the team building the product.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Many teams spend too much time building and too little time discovering what to build. Continuous discovery reframes discovery as an ongoing product habit, not a one-off phase before delivery. [BB-C21-S09]", "Figure 21.2. Product discovery and evidence-gate loop. The author-created diagram moves from an opportunity through alternative solutions and validation to a go, pivot, or stop decision. A “go” means the evidence is sufficient for the next bounded commitment, not that the product will succeed. Source basis: continuous-discovery practice. [BB-C21-S09]", "Continuous-discovery sources may recommend weekly customer touchpoints as a practice pattern, but cadence is not evidence quality. Set it from decision frequency, risk, access to participants, product change rate, research ethics, team capacity, and the cost of delay; increase rigor and sample size when the decision requires quantitative or subgroup confidence. [BB-C21-S09] [BB-C21-S10]", "Strong product managers kill more ideas than they ship. Continuous discovery is valuable precisely because it creates cheap ways to reject weak opportunities before engineering commits to them. [BB-C21-S09]", "For operators: Track how many ideas are changed, merged, deferred, or killed during discovery. If almost every idea ships unchanged, you are probably using discovery as theater rather than as a decision filter. [BB-C21-S09]", "- Use quantitative data to detect patterns and qualitative discovery to understand the customer context behind those patterns. [BB-C21-S09]" ] } ] }, { "source_id": "BB-C21-S10", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Usability Testing", "authors": "Nielsen, J.", "year": 2000, "title": "Why You Only Need to Test with 5 Users", "venue": "Nielsen Norman Group", "source_type": "practitioner research article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/", "doi": null, "claim_notes": "Inspected NN/g article; supports qualitative five-user usability testing guidance and its assumptions.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "1. Usability Testing: Can users complete the task? Nielsen Norman Group argues that small qualitative usability tests can surface many major issues quickly; use larger samples when you need quantitative confidence. [BB-C21-S10]", "- Evidence criteria: pre-specify the relevant value, usability, feasibility, viability, accessibility, risk, and strategy questions, sample, uncertainty, guardrails, and decision rule. A survey or small usability test answers a bounded question, not the entire product decision. [BB-C21-S04] [BB-C21-S10]", "Continuous-discovery sources may recommend weekly customer touchpoints as a practice pattern, but cadence is not evidence quality. Set it from decision frequency, risk, access to participants, product change rate, research ethics, team capacity, and the cost of delay; increase rigor and sample size when the decision requires quantitative or subgroup confidence. [BB-C21-S09] [BB-C21-S10]" ] } ] }, { "source_id": "BB-C21-S11", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Product-Led Growth Benchmarks", "authors": "Poyar, K.; Richard, S.; OpenView; Amplitude", "year": 2022, "title": "Your Guide to Product-Led Growth Benchmarks", "venue": "OpenView Partners", "source_type": "industry benchmark report", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://openviewpartners.com/blog/your-guide-to-product-led-growth-benchmarks/", "doi": null, "claim_notes": "Inspected benchmark article; supports PLG funnel stages and selected activation/free-to-paid benchmark ranges from 450+ software companies.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Best Practice: Use tiers to segment market. Optimize for retention and expansion revenue instead of treating the first contract as the whole account value. [BB-C21-S11]", "Goal: Strong net revenue retention. In PLG companies, expansion from successful teams is often as important as the initial conversion. [BB-C21-S11]", "- Target: Set from your product's historical cohort data; generic activation benchmarks vary by category. [BB-C21-S11]", "- Target: OpenView's benchmark work reports different conversion patterns for freemium and free-trial motions; compare against your model, not against a single universal target. [BB-C21-S11]", "- Target: Track whether expansion revenue reliably offsets contraction and churn. [BB-C21-S11]" ] } ] }, { "source_id": "BB-C21-S16", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "AI Product Risk Management", "authors": "National Institute of Standards and Technology", "year": 2023, "title": "Artificial Intelligence Risk Management Framework (AI RMF 1.0)", "venue": "NIST", "source_type": "official standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://www.nist.gov/itl/ai-risk-management-framework", "doi": "10.6028/NIST.AI.100-1", "claim_notes": "Inspected NIST page; supports AI risk, trustworthiness, and design/development/use/evaluation risk-management language for AI products.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "AI product management addresses products that add probabilistic behavior, data and model dependencies, evaluation needs, and new failure modes; they do not replace software engineering or ordinary product discipline. Test deterministic components with normal unit, integration, system, regression, performance, security, and accessibility methods, and evaluate AI behavior on versioned, representative cases with pre-specified quality, safety, fairness, privacy, security, latency, cost, and business guardrails. [BB-C21-S16]", "- A drift alert triggers diagnosis, not automatic or calendar-based retraining. Retrain, recalibrate, replace, change the workflow, restrict use, or stop only when evidence supports it; preserve versions and evidence, validate, approve, stage, monitor, and retain rollback. [BB-C21-S16]", "Key Insight: Many AI product failures come from weak data, measurement, and monitoring rather than from the model architecture alone. Treat data quality as a product requirement, not a back-office task. [BB-C21-S16]", "- Solution: Be transparent about limitations. Use AI to augment, not replace. [BB-C21-S16]", "For an AI feature, add a versioned evaluation set, non-AI baseline, data/model/vendor dependency map, meaningful-human-control decision, change-control approvals, incident path, and rollback evidence. [BB-C21-S16]" ] } ] }, { "source_id": "BB-C21-S17", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "AI Product Regulation", "authors": "European Parliament and Council of the European Union", "year": 2024, "title": "Regulation (EU) 2024/1689: Artificial Intelligence Act", "venue": "Official Journal of the European Union", "source_type": "official regulation", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://eur-lex.europa.eu/eli/reg/2024/1689/oj/eng", "doi": null, "claim_notes": "Inspected EUR-Lex official text; supports EU AI Act high-level purpose and harmonized AI-system obligations.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Regulatory note: the EU AI Act and other regimes are role-, system-, use-, jurisdiction-, and effective-date-specific. Map current applicable obligations through official sources and qualified legal review; no chapter checklist establishes compliance. [BB-C21-S17]" ] } ] }, { "source_id": "BB-C21-S18", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Product Strategy", "authors": "Perri, M.", "year": 2016, "title": "What Is Good Product Strategy?", "venue": "MelissaPerri.com", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-03", "url": "https://melissaperri.com/blog/2016/07/14/what-is-good-product-strategy", "doi": null, "claim_notes": "Inspected article; supports product strategy as goals and visions aligned to desirable business and customer outcomes, not a feature plan.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "A product strategy canvas connects goals and product vision to desired customer and business outcomes; it is not merely a feature plan. [BB-C21-S18] The six-part canvas below is an author-created synthesis that combines that strategy framing with jobs-to-be-done questions. [BB-C21-S01] It prompts explicit choices but does not force clarity, prove demand, or guarantee differentiation. All examples and proposed metrics below are constructed teaching prompts, not claims about named companies or universal targets." ] } ] }, { "source_id": "BB-C03-S01", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Porter's Five Forces", "authors": "Porter, M. E.", "year": 1979, "title": "How Competitive Forces Shape Strategy", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=10692", "doi": null, "claim_notes": "Canonical Five Forces source. Supports industry-structure and force-analysis framing; does not independently support hard profitability-variance percentages. Verified on 2026-07-05 against the HBS faculty publication record and HBR article page; citation matches Porter, 1979, Harvard Business Review.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]", "- Porter, M. E. (1979). How Competitive Forces Shape Strategy. Harvard Business Review , 57(2), 137-145. [BB-C03-S01]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S02", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Competitive Strategy", "authors": "Porter, M. E.", "year": 1980, "title": "Competitive Strategy: Techniques for Analyzing Industries and Competitors", "venue": "Free Press", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=195", "doi": null, "claim_notes": "Canonical strategy book for industry analysis, generic strategies, and competitive positioning. Verified on 2026-07-05 against the HBS faculty book record; citation matches Porter, 1980, Free Press.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S03", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Strategic Positioning", "authors": "Porter, M. E.", "year": 1996, "title": "What Is Strategy?", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://hbr.org/1996/11/what-is-strategy", "doi": null, "claim_notes": "Canonical source for trade-offs, fit among activities, and strategy as distinct positioning. Verified on 2026-07-05 against HBR and HBS records; citation matches Porter, 1996, Harvard Business Review.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]", "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]", "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]", "6. Choose a guiding policy, reject incompatible options, and specify mutually reinforcing actions with owners and resources. [BB-C03-S03] [BB-C03-S16]" ] } ] }, { "source_id": "BB-C03-S04", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Resource-Based View and VRIO", "authors": "Barney, J. B.", "year": 1991, "title": "Firm Resources and Sustained Competitive Advantage", "venue": "Journal of Management", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://journals.sagepub.com/doi/10.1177/014920639101700108", "doi": "10.1177/014920639101700108", "claim_notes": "Foundational resource-based view source. Supports valuable, rare, hard-to-imitate resource logic; local productivity or performance percentages require separate evidence. Verified on 2026-07-05 against the Sage journal record; DOI, author, title, year, and venue match.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S05", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Dynamic Capabilities", "authors": "Teece, D. J.; Pisano, G.; Shuen, A.", "year": 1997, "title": "Dynamic Capabilities and Strategic Management", "venue": "Strategic Management Journal", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://sms.onlinelibrary.wiley.com/doi/abs/10.1002/%28SICI%291097-0266%28199708%2918%3A7%3C509%3A%3AAID-SMJ882%3E3.0.CO%3B2-Z", "doi": "10.1002/(SICI)1097-0266(199708)18:7<509::AID-SMJ882>3.0.CO;2-Z", "claim_notes": "Supports sense/seize/reconfigure framing and the limits of static resource analysis in changing environments. Verified on 2026-07-05 against the Wiley Strategic Management Journal record; DOI and bibliographic fields match.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "- 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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S06", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Blue Ocean Strategy", "authors": "Kim, W. C.; Mauborgne, R.", "year": 2025, "title": "Blue Ocean Tools and Frameworks: Blue Ocean Toolkit 2025", "venue": "Blue Ocean Strategy", "source_type": "official author toolkit", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.blueoceanstrategy.com/wp-content/uploads/2025/06/Blue-Ocean-Toolkit-2025.pdf", "doi": null, "claim_notes": "Full 20-page toolkit published by the framework authors was inspected. It defines the strategy canvas and value curve and states the eliminate-reduce-raise-create questions in the Four Actions Framework. It presents market creation and demand claims as the authors' framework, not controlled evidence of causal performance or a promise that competition disappears.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "- Kim, W. C., & Mauborgne, R. (2025). Blue Ocean Tools and Frameworks: Blue Ocean Toolkit 2025 . Blue Ocean Strategy. [BB-C03-S06]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S07", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "BCG Growth-Share Matrix", "authors": "Henderson, B. D.", "year": 1970, "title": "The Product Portfolio", "venue": "Boston Consulting Group Perspectives", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.bcg.com/publications/1970/strategy-the-product-portfolio", "doi": null, "claim_notes": "Canonical source for the growth-share matrix and experience-curve portfolio logic. Verified on 2026-07-05 against BCG publication page; citation matches Bruce Henderson, The Product Portfolio, 1970.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "BCG Growth-Share Matrix [BB-C03-S07]", "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]", "- 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]", "Mermaid Diagram: BCG Growth-Share Matrix [BB-C03-S07]", "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]", "Limits of the BCG Matrix [BB-C03-S07]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S08", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Ansoff Matrix", "authors": "Ferguson, J.; Zamudio, C.", "year": 2026, "title": "Chapter 5: Strategic Planning", "venue": "Marketing Principles From The River City (Virginia Commonwealth University Libraries)", "source_type": "open educational textbook chapter", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://pressbooks.library.vcu.edu/marketingprinciples/chapter/chapter-5-strategic-planning/", "doi": null, "claim_notes": "Full openly licensed VCU Libraries textbook chapter inspected. It defines market penetration as existing products/existing markets, product development as new products/existing markets, market development as existing products/new markets, and diversification as new products/new markets. It also cautions against growth as an end in itself and discusses capability and risk demands. The source does not establish a universal ordinal risk ranking, causal performance effect, or guaranteed value creation.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "- Ferguson, J., & Zamudio, C. (2026). Ch. 5: Strategic Planning. Marketing Principles From The River City . Virginia Commonwealth University Libraries. [BB-C03-S08]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S09", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Environmental Scanning and PESTLE", "authors": "Choo, C. W.", "year": 2001, "title": "Environmental Scanning as Information Seeking and Organizational Learning", "venue": "Information Research, 7(1), paper 112", "source_type": "scholarly open-access article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://informationr.net/ir/7-1/paper112.html", "doi": null, "claim_notes": "Full 14-page text uploaded by the author was inspected. Choo defines environmental scanning as acquiring and using information about external events, trends, and relationships and analyzes multiple viewing, searching, sensemaking, learning, and decision-use modes. The article cites Aguilar but does not validate PESTLE's six labels as a causal model, forecast, or completeness guarantee.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "- Choo, C. W. (2001). Environmental scanning as information seeking and organizational learning. Information Research , 7(1), paper 112. [BB-C03-S09]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S10", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Seven-Element Organizational Alignment Model", "authors": "Waterman, R. H.; Peters, T. J.; Phillips, J. R.", "year": 1980, "title": "Structure Is Not Organization", "venue": "Business Horizons", "source_type": "peer-reviewed practitioner article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.sciencedirect.com/science/article/pii/0007681380900270", "doi": "10.1016/0007-6813(80)90027-0", "claim_notes": "Canonical published source for the seven-element organizational model. Supports using strategy, structure, systems, shared values, style, staff, and skills as interdependent diagnostic categories; it does not establish a universal execution-success rate or prove that alignment causes performance. Metadata and DOI rechecked against ScienceDirect on 2026-07-10.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "McKinsey 7S Framework [BB-C03-S10]", "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]", "- Waterman, R. H., Peters, T. J., & Phillips, J. R. (1980). “Structure Is Not Organization.” Business Horizons , 23(3), 14–26. [BB-C03-S10]", "Mermaid Diagram: McKinsey 7S Framework [BB-C03-S10]", "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]" ] } ] }, { "source_id": "BB-C03-S11", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Core Competence", "authors": "Prahalad, C. K.; Hamel, G.", "year": 1990, "title": "The Core Competence of the Corporation", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://hbr.org/1990/05/the-core-competence-of-the-corporation", "doi": null, "claim_notes": "Canonical source for core competencies as cross-business capabilities that create customer value and are difficult to imitate. Verified on 2026-07-05 against the HBR article page; citation matches Prahalad and Hamel, 1990, Harvard Business Review.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "- 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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S12", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis", "appendix-b-contrarian-business-perspectives" ], "framework": "Scenario Planning", "authors": "Wack, P.", "year": 1985, "title": "Scenarios: Uncharted Waters Ahead", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://hbr.org/1985/09/scenarios-uncharted-waters-ahead", "doi": null, "claim_notes": "Canonical Shell scenario-planning source; supports mental-model and uncertainty-planning framing. Verified on 2026-07-05 against the HBR article page; citation matches Wack, 1985, Harvard Business Review.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "- 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]", "8. Stress-test critical uncertainties with scenarios, signposts, staged commitments, competitor responses, and stop conditions. [BB-C03-S12] [BB-C03-S13] [BB-C03-S29]" ] }, { "entrySlug": "appendix-b-contrarian-business-perspectives", "entryTitle": "Appendix B: Contrarian Business Perspectives", "excerpts": [ "Construct a rival explanation or scenario that a well-informed decision-maker could reasonably hold. Scenario planning can expose uncertainties and mental models, but scenarios are not forecasts and should not be assigned false precision. [BB-C03-S12] [BB-C03-S13]" ] } ] }, { "source_id": "BB-C03-S13", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis", "appendix-b-contrarian-business-perspectives" ], "framework": "Scenario Planning", "authors": "Schoemaker, P. J. H.", "year": 1995, "title": "Scenario Planning: A Tool for Strategic Thinking", "venue": "Sloan Management Review", "source_type": "academic/practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-09", "url": "https://shop.sloanreview.mit.edu/store/scenario-planning-a-tool-for-strategic-thinking", "doi": null, "claim_notes": "Supports scenario planning as a tool for strategic thinking: identifying trends and uncertainties, constructing scenarios, and countering overconfidence and tunnel vision. Verified on 2026-07-09 against the MIT Sloan Management Review store record; the record identifies Paul J. H. Schoemaker, the 1995 publication date, and the article's scenario-construction focus.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "- Schoemaker, P. J. H. (1995). Scenario Planning: A Tool for Strategic Thinking. Sloan Management Review , 36(2), 25-40. [BB-C03-S13]", "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]", "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]", "8. Stress-test critical uncertainties with scenarios, signposts, staged commitments, competitor responses, and stop conditions. [BB-C03-S12] [BB-C03-S13] [BB-C03-S29]" ] }, { "entrySlug": "appendix-b-contrarian-business-perspectives", "entryTitle": "Appendix B: Contrarian Business Perspectives", "excerpts": [ "Construct a rival explanation or scenario that a well-informed decision-maker could reasonably hold. Scenario planning can expose uncertainties and mental models, but scenarios are not forecasts and should not be assigned false precision. [BB-C03-S12] [BB-C03-S13]" ] } ] }, { "source_id": "BB-C03-S14", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Platform Strategy and Two-Sided Markets", "authors": "Eisenmann, T.; Parker, G.; Van Alstyne, M.", "year": 2006, "title": "Strategies for Two-Sided Markets", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://hbr.org/2006/10/strategies-for-two-sided-markets", "doi": null, "claim_notes": "Supports two-sided-market economics, pricing, chicken-and-egg sequencing, network effects, and multi-homing discussion. Verified on 2026-07-05 against HBR and HBS records; citation matches Eisenmann, Parker, and Van Alstyne, 2006, Harvard Business Review.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "- 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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S15", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Platform Strategy", "authors": "Parker, G. G.; Van Alstyne, M. W.; Choudary, S. P.", "year": 2016, "title": "Platform Revolution: How Networked Markets Are Transforming the Economy and How to Make Them Work for You", "venue": "W. W. Norton", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://wwnorton.com/books/Platform-Revolution/", "doi": null, "claim_notes": "Supports platform business-model and network-market management framing; hard market-cap rankings should be checked before publication. Verified on 2026-07-05 against the W. W. Norton book page; authors, title, publisher, and ISBN match the 2016 book.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "- Parker, G. G., Van Alstyne, M. W., & Choudary, S. P. (2016). Platform Revolution . New York: W.W. Norton. [BB-C03-S15]", "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]" ] } ] }, { "source_id": "BB-C03-S16", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis", "appendix-b-contrarian-business-perspectives" ], "framework": "Strategy Diagnosis and Coherent Action", "authors": "Rumelt, R. P.", "year": 2011, "title": "Good Strategy/Bad Strategy: The Difference and Why It Matters", "venue": "Crown Business", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.penguinrandomhouse.com/books/208668/good-strategy-bad-strategy-by-richard-rumelt/", "doi": null, "claim_notes": "Supports the chapter's pragmatic strategy-diagnosis, trade-off, and coherent-action framing. Verified on 2026-07-05 against the Penguin Random House book page; citation matches Rumelt, 2011, Crown Business.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]", "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]", "6. Choose a guiding policy, reject incompatible options, and specify mutually reinforcing actions with owners and resources. [BB-C03-S03] [BB-C03-S16]" ] }, { "entrySlug": "appendix-b-contrarian-business-perspectives", "entryTitle": "Appendix B: Contrarian Business Perspectives", "excerpts": [ "Specify where each view might hold, where it might fail, and which stakeholders bear the costs. A useful strategy diagnosis connects the central challenge to explicit trade-offs and coherent action rather than a collection of aspirations. [BB-C03-S16]" ] } ] }, { "source_id": "BB-C03-S17", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Diversification Discount", "authors": "Berger, P. G.; Ofek, E.", "year": 1995, "title": "Diversification's Effect on Firm Value", "venue": "Journal of Financial Economics", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.sciencedirect.com/science/article/pii/0304405X94007986", "doi": "10.1016/0304-405X(94)00798-6", "claim_notes": "Official ScienceDirect record and abstract inspected. The study estimates a 13% to 15% average value loss from diversification for its 1986–1991 sample, using imputed stand-alone segment values, and reports smaller losses for related segments plus contributions from overinvestment and cross-subsidization. Chapter 3 uses the finding only as conditional average evidence and explicitly rejects universal firm-level inference.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C03-S18", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Corporate Strategy and Diversification", "authors": "Porter, M. E.", "year": 1987, "title": "From Competitive Advantage to Corporate Strategy", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://hbr.org/1987/05/from-competitive-advantage-to-corporate-strategy", "doi": null, "claim_notes": "Supports corporate-strategy and diversification caution. Exact divestiture percentages should be verified before being restored. Verified on 2026-07-05 against HBR and HBS records; citation matches Porter, 1987, Harvard Business Review.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C03-S19", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Strategic Alignment", "authors": "Kaplan, R. S.; Norton, D. P.", "year": 2006, "title": "Alignment: Using the Balanced Scorecard to Create Corporate Synergies", "venue": "Harvard Business School Press", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=21112", "doi": null, "claim_notes": "Supports strategic alignment and management-system linkage. Do not use for unverified universal execution-success percentages. Verified on 2026-07-05 against the HBS faculty book record; citation matches Kaplan and Norton, 2006, Harvard Business School Press.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C03-S20", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Price Elasticity of Demand", "authors": "Greenlaw, S. A.; Shapiro, D.; MacDonald, D.", "year": 2022, "title": "5.3 Elasticity and Pricing", "venue": "Principles of Economics 3e (OpenStax, Rice University)", "source_type": "open educational textbook section", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://openstax.org/books/principles-economics-3e/pages/5-3-elasticity-and-pricing", "doi": null, "claim_notes": "Full OpenStax section inspected. It defines the relation between price elasticity, price changes, quantity response, and total revenue and discusses cost pass-through. Chapter 3 uses it for bounded managerial interpretation and explicitly warns that elasticity alone does not establish profit, causality, or a permanent firm-level parameter.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S21", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Marginal Cost and Economies of Scale", "authors": "Greenlaw, S. A.; Shapiro, D.; MacDonald, D.", "year": 2022, "title": "Chapter 7 Key Concepts and Summary: Cost and Industry Structure", "venue": "Principles of Economics 3e (OpenStax, Rice University)", "source_type": "open educational textbook section", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://openstax.org/books/principles-economics-3e/pages/7-key-concepts-and-summary", "doi": null, "claim_notes": "Full OpenStax chapter summary inspected. It distinguishes fixed, variable, marginal, average, and sunk costs; explains short-run versus long-run choice; and defines economies, constant returns, and diseconomies of scale through long-run average cost. Chapter 3 does not treat scale as an automatic advantage.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S22", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Marginal Revenue and Market Power", "authors": "Shapiro, D.; MacDonald, D.; Greenlaw, S. A.", "year": 2022, "title": "9.2 How a Profit-Maximizing Monopoly Chooses Output and Price", "venue": "Principles of Microeconomics 3e (OpenStax, Rice University)", "source_type": "open educational textbook section", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://openstax.org/books/principles-microeconomics-3e/pages/9-2-how-a-profit-maximizing-monopoly-chooses-output-and-price", "doi": null, "claim_notes": "Full OpenStax section inspected. It demonstrates comparing marginal revenue and marginal cost, selecting output before reading price from demand, and distinguishing a price-taking firm from a monopolist. Chapter 3 uses the marginal rule as a decision heuristic and does not assume that any focal firm is a literal monopolist.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C03-S23", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Relevant Market and Market Power", "authors": "United States Department of Justice; United States Federal Trade Commission", "year": 2023, "title": "2023 Merger Guidelines, Section 4.3: Market Definition", "venue": "United States Department of Justice and Federal Trade Commission", "source_type": "official regulator guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.justice.gov/atr/merger-guidelines/tools/market-definition", "doi": null, "claim_notes": "Official DOJ/FTC guidance inspected. Section 4.3 defines a relevant antitrust market as an area of effective competition with product and geographic elements and describes evidence including substitution, observed competition, market power, practical indicia, and the hypothetical-monopolist test. Chapter 3 distinguishes this legal-regulatory analysis from a managerial Five Forces boundary and provides no legal conclusion.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C03-S24", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Price Discrimination and Pricing Ethics", "authors": "Albrecht, M. G.; Green, M.; Hoffman, L.", "year": 2023, "title": "12.6 Ethical Considerations in Pricing", "venue": "Principles of Marketing (OpenStax, Rice University)", "source_type": "open educational textbook section", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://openstax.org/books/principles-marketing/pages/12-6-ethical-considerations-in-pricing", "doi": null, "claim_notes": "Full OpenStax section inspected for its marketing definition of price discrimination and warnings about trust, ethics, and legal context. Chapter 3 narrows the use to an economic/managerial description, explicitly states that the economic label is broader than any statute, and directs managers to fact-specific legal review.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C03-S25", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Bundling and Information-Goods Pricing", "authors": "Bakos, Y.; Brynjolfsson, E.", "year": 1999, "title": "Bundling Information Goods: Pricing, Profits, and Efficiency", "venue": "Management Science, 45(12), 1613-1630", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://oz.stern.nyu.edu/phd04/big.pdf", "doi": "10.1287/mnsc.45.12.1613", "claim_notes": "Full author-hosted article and official INFORMS metadata inspected. The model explains how bundling many information goods can make aggregate valuations more predictable and interact with segmentation, while identifying limits involving marginal costs, correlated valuations, heterogeneous segments, and cognitive or search costs. Chapter 3 does not generalize the model to all bundles.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C03-S26", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Adverse Selection and the Market for Lemons", "authors": "Akerlof, G. A.", "year": 1970, "title": "The Market for 'Lemons': Quality Uncertainty and the Market Mechanism", "venue": "The Quarterly Journal of Economics, 84(3), 488-500", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://academic.oup.com/qje/article-abstract/84/3/488/1896241", "doi": "10.2307/1879431", "claim_notes": "Official Oxford Academic metadata and a full university-hosted preserved copy were inspected. The paper develops the automobiles quality-uncertainty model, additional applications, and counteracting institutions. Chapter 3 uses it as the seminal adverse-selection model and explicitly avoids claiming that every secondhand or quality-uncertain market collapses.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C03-S27", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Uncertainty, Insurance, and Moral Hazard", "authors": "Arrow, K. J.", "year": 1963, "title": "Uncertainty and the Welfare Economics of Medical Care", "venue": "American Economic Review, 53(5), 941-973", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://assets.aeaweb.org/asset-server/files/9442.pdf", "doi": null, "claim_notes": "Full article from the American Economic Association asset server inspected. Arrow analyzes uncertainty, information, insurance, professional institutions, and departures from the competitive model in medical care. Chapter 3 treats it as seminal information-economics context and applies moral-hazard logic cautiously beyond health care without attributing a universal remedy.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C03-S28", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Operational Responses to Asymmetric Information", "authors": "Greenlaw, S. A.; Shapiro, D.; MacDonald, D.", "year": 2022, "title": "16.1 The Problem of Imperfect Information and Asymmetric Information; 16.2 Insurance and Imperfect Information", "venue": "Principles of Economics 3e (OpenStax, Rice University)", "source_type": "open educational textbook sections", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://openstax.org/books/principles-economics-3e/pages/16-1-the-problem-of-imperfect-information-and-asymmetric-information", "doi": null, "claim_notes": "Both full OpenStax sections were inspected. They distinguish imperfect from asymmetric information, adverse selection from moral hazard, and give bounded examples of reputation, guarantees, warranties, screening, collateral, monitoring, and shared exposure. Chapter 3 adds cautions about error, exclusion, burden, privacy, appeal, and governance rather than treating any response as universally optimal.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C03-S29", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Oligopoly and Payoff Matrices", "authors": "Greenlaw, S. A.; Shapiro, D.; MacDonald, D.", "year": 2022, "title": "10.2 Oligopoly", "venue": "Principles of Economics 3e (OpenStax, Rice University)", "source_type": "open educational textbook section", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://openstax.org/books/principles-economics-3e/pages/10-2-oligopoly", "doi": null, "claim_notes": "Full OpenStax section inspected. It explains oligopoly as strategic interdependence, shows prisoner-dilemma payoff matrices, and distinguishes dominant-strategy incentives from the jointly better outcome. Chapter 3 uses an original price-response matrix and explicitly rejects competitor coordination as a managerial recommendation.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]", "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]", "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]", "8. Stress-test critical uncertainties with scenarios, signposts, staged commitments, competitor responses, and stop conditions. [BB-C03-S12] [BB-C03-S13] [BB-C03-S29]" ] } ] }, { "source_id": "BB-C03-S30", "chapter_slugs": [ "chapter-03-strategy-and-competitive-analysis" ], "framework": "Non-Cooperative Game Theory and Nash Equilibrium", "authors": "Nash, J.", "year": 1951, "title": "Non-Cooperative Games", "venue": "Annals of Mathematics, 54(2), 286-295", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.jstor.org/stable/1969529", "doi": "10.2307/1969529", "claim_notes": "Official journal/JSTOR metadata and a full preserved copy were inspected. Nash develops non-cooperative games and equilibrium points; Chapter 3 cites it only for the seminal equilibrium concept and warns that a stylized equilibrium does not itself predict behavior under incomplete information, bounded rationality, repeated interaction, or institutional constraints.", "uses": [ { "entrySlug": "chapter-03-strategy-and-competitive-analysis", "entryTitle": "Strategy and Competitive Analysis", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C09-S01", "chapter_slugs": [ "chapter-09-problem-structuring" ], "framework": "Issue Trees and Hypothesis-Driven Problem Solving", "authors": "Garrette, B.; Phelps, C.; Sibony, O.", "year": 2018, "title": "Structure the Problem: Pyramids and Trees", "venue": "Cracked it! (Palgrave Macmillan)", "source_type": "academic book chapter", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Inspected the Springer chapter record and publisher-displayed abstract. It directly supports hypothesis pyramids, confronting a hypothesis with evidence, issue-tree decomposition into issues and sub-issues, MECE decomposition, and confirmation risk. Chapter 9 cites it only for bounded decomposition and evidence-investigation statements; framing and stakeholder-coverage limits are author cautions.", "url": "https://link.springer.com/chapter/10.1007/978-3-319-89375-4_5", "doi": "10.1007/978-3-319-89375-4_5", "uses": [ { "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "excerpts": [ "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.", "Source note: Author synthesis informed by an academic account of issue decomposition and hypothesis-driven analysis. [BB-C09-S01]" ] } ] }, { "source_id": "BB-C09-S02", "chapter_slugs": [ "chapter-09-problem-structuring" ], "framework": "MECE and Pyramid Logic", "authors": "McKinsey & Company; Minto, B.", "year": 2018, "title": "Barbara Minto: ‘MECE: I invented it, so I get to say how to pronounce it’", "venue": "McKinsey & Company Alumni News", "source_type": "official interview", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Inspected McKinsey's first-party interview with Barbara Minto. It directly defines MECE as mutually exclusive and collectively exhaustive and states that a pyramid's point above summarizes logically similar, logically ordered ideas below. Chapter 9 cites only those bounded definition and grouping claims; completeness, validity, and decision-quality guarantees are not attributed to it.", "url": "https://www.mckinsey.com/alumni/news-and-events/global-news/alumni-news/barbara-minto-mece-i-invented-it-so-i-get-to-say-how-to-pronounce-it", "doi": null, "uses": [ { "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "excerpts": [ "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.", "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.", "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]", "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." ] } ] }, { "source_id": "BB-C09-S03", "chapter_slugs": [ "chapter-09-problem-structuring" ], "framework": "5 Whys and Toyota Production System", "authors": "Ohno, T.", "year": 1988, "title": "Toyota Production System: Beyond Large-Scale Production", "venue": "Productivity Press", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Routledge metadata and the Lean Enterprise Institute’s attributed Ohno page-17 example support repeated 5 Whys questioning beyond symptoms. The manuscript treats it as a Toyota-associated inquiry routine and explicitly does not claim that repeated questioning proves causality.", "url": "https://www.routledge.com/Toyota-Production-System-Beyond-Large-Scale-Production/Ohno/p/book/9780915299140", "uses": [ { "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C09-S04", "chapter_slugs": [ "chapter-09-problem-structuring", "appendix-b-contrarian-business-perspectives" ], "framework": "Premortem Analysis", "authors": "Klein, G.", "year": 2007, "title": "Performing a Project Premortem", "venue": "Harvard Business Review; official Bain & Company republication", "source_type": "official practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Gary Klein’s HBR article was inspected and supports assuming a project has failed, then independently generating plausible reasons as prospective risk identification. It does not establish event probabilities or guarantee better outcomes; the manuscript makes neither claim.", "url": "https://hbr.org/2007/09/performing-a-project-premortem", "uses": [ { "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "excerpts": [ "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." ] }, { "entrySlug": "appendix-b-contrarian-business-perspectives", "entryTitle": "Appendix B: Contrarian Business Perspectives", "excerpts": [ "Assume the leading option has failed and independently generate plausible reasons. A premortem is a prospective risk-identification exercise; it does not establish probabilities or prove that failure will occur. [BB-C09-S04]" ] } ] }, { "source_id": "BB-C09-S05", "chapter_slugs": [ "chapter-09-problem-structuring", "appendix-b-contrarian-business-perspectives" ], "framework": "Structured Decision Making", "authors": "Robinson, K. F.; Fuller, A. K.", "year": 2016, "title": "Participatory Modeling and Structured Decision Making", "venue": "Environmental Modeling with Stakeholders; Springer", "source_type": "academic book chapter", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Inspected the official USGS publication record and full abstract. It directly identifies a transparent, defensible, replicable structured-decision-making process covering problem and decision context, objectives, alternatives, consequences, trade-offs, implementation, stakeholder values, science, and uncertainty. The chapter's weighting matrix and assumption-routing quadrants remain explicitly author-created and are not attributed to this source.", "url": "https://www.usgs.gov/publications/participatory-modeling-and-structured-decision-making", "doi": "10.1007/978-3-319-25053-3_5", "uses": [ { "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "excerpts": [ "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.", "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]" ] }, { "entrySlug": "appendix-b-contrarian-business-perspectives", "entryTitle": "Appendix B: Contrarian Business Perspectives", "excerpts": [ "Structured decision making separates context, objectives, alternatives, consequences, trade-offs, implementation, stakeholder values, evidence, and uncertainty. This appendix adapts those elements into a compact challenge record; it does not claim that the protocol guarantees a better outcome. [BB-C09-S05]" ] } ] }, { "source_id": "BB-C09-S06", "chapter_slugs": [ "chapter-09-problem-structuring" ], "framework": "Likelihood-Impact Risk Assessment", "authors": "Joint Task Force Transformation Initiative", "year": 2012, "title": "Guide for Conducting Risk Assessments", "venue": "NIST Special Publication 800-30 Revision 1", "source_type": "official government guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://csrc.nist.gov/pubs/sp/800/30/r1/final", "doi": "10.6028/NIST.SP.800-30r1", "claim_notes": "Inspected the official NIST landing page and full PDF. NIST uses likelihood and impact scales in federal information-security risk determination, embeds assessment in a broader process, permits tailoring, and cautions that assessments are often imprecise and depend on method limits, data subjectivity and quality, interpretation, and assessor expertise. The chapter's cross-domain color matrix is explicitly a constructed adaptation, not a NIST-prescribed general business matrix.", "uses": [ { "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "excerpts": [ "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]", "- 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]." ] } ] }, { "source_id": "BB-C09-S07", "chapter_slugs": [ "chapter-09-problem-structuring" ], "framework": "Risk-Matrix Limitations", "authors": "Cox, L. A., Jr.", "year": 2008, "title": "What's Wrong with Risk Matrices?", "venue": "Risk Analysis", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://ideas.repec.org/a/wly/riskan/v28y2008i2p497-512.html", "doi": "10.1111/j.1539-6924.2008.01030.x", "claim_notes": "Inspected the IDEAS/RePEc metadata, publisher-linked DOI, and complete abstract. It supports cautions about poor resolution, range compression, ranking errors, suboptimal resource allocation, ambiguous or subjective inputs and outputs, and the need to explain embedded judgments. The chapter does not reproduce the article's quantitative examples.", "uses": [ { "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "excerpts": [ "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]", "- 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]." ] } ] }, { "source_id": "BB-C10-S01", "chapter_slugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "framework": "McKinsey 7S Framework", "authors": "Waterman, R. H.; Peters, T. J.; Phillips, J. R.", "year": 1980, "title": "Structure Is Not Organization", "venue": "Business Horizons", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "ScienceDirect metadata and the author-hosted original article were inspected. Supports structure, strategy, systems, style, skills, staff, and superordinate goals/shared values as interacting organizational elements. Chapter use is diagnostic and does not claim causal performance proof.", "url": "https://www.sciencedirect.com/science/article/pii/0007681380900270", "doi": "10.1016/0007-6813(80)90027-0", "uses": [ { "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "excerpts": [ "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.", "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]", "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]", "7. McKinsey 7S (Framework 2): Which organizational relationships and capability hypotheses require testing before execution? [BB-C10-S01]" ] } ] }, { "source_id": "BB-C10-S02", "chapter_slugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "framework": "Value Chain Analysis", "authors": "Porter, M. E.", "year": 1985, "title": "Competitive Advantage: Creating and Sustaining Superior Performance", "venue": "Free Press; official framework summary at Harvard Business School Institute for Strategy and Competitiveness", "source_type": "academic book and official institutional summary", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.isc.hbs.edu/strategy/business-strategy/Pages/the-value-chain.aspx", "doi": null, "claim_notes": "Reactivated with replacement evidence. Inspected the official HBS Institute page, which attributes the value chain to Porter and directly supports disaggregating strategically relevant activities, higher-price/lower-cost advantage, the upstream/downstream value system, activities as units of advantage, and strategy as choices about activity configuration and linkages. The official institutional framework page is the claim carrier; the chapter's familiar activity labels and digital prompts are explicitly author adaptations.", "uses": [ { "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C10-S03", "chapter_slugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "framework": "Business Model Canvas", "authors": "Osterwalder, A.; Pigneur, Y.", "year": 2010, "title": "Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers", "venue": "John Wiley & Sons", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Wiley metadata and official Strategyzer materials support the Business Model Canvas and its nine building blocks. The chapter uses the canvas to make business-model hypotheses visible and explicitly does not treat a completed canvas as validation.", "url": "https://www.wiley.com/en-us/Business%2BModel%2BGeneration%3A%2BA%2BHandbook%2Bfor%2BVisionaries%2C%2BGame%2BChangers%2C%2Band%2BChallengers-p-9780470876411", "uses": [ { "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "excerpts": [ "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.", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C10-S04", "chapter_slugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "framework": "RAPID Decision Framework", "authors": "Rogers, P.; Blenko, M.", "year": 2006, "title": "Who Has the D? How Clear Decision Roles Enhance Organizational Performance", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Inspected Bain's official page, which identifies Rogers and Blenko, the January 1, 2006 publication date, ambiguity over decision accountability, and all five RAPID roles: Recommend, Agree, Perform, Input, and Decide. The chapter separately states that the framework cannot replace actual legal, governance, contractual, professional, labor, or emergency authority. RAPID is a registered Bain mark and remains subject to permissions review.", "url": "https://www.bain.com/insights/who-has-d-how-clear-decision-roles-enhance-organizational-performance/", "doi": null, "uses": [ { "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "excerpts": [ "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.", "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." ] } ] }, { "source_id": "BB-C10-S06", "chapter_slugs": [ "chapter-10-advanced-consulting-frameworks-and-integration", "appendix-b-contrarian-business-perspectives" ], "framework": "Psychological Safety", "authors": "Edmondson, A.", "year": 1999, "title": "Psychological Safety and Learning Behavior in Work Teams", "venue": "Administrative Science Quarterly", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "SAGE metadata and the MIT-hosted full article were inspected. The 51-team field study defines team psychological safety and reports its association with learning behavior. Chapter use treats it as one possible explanation for inhibited candor, not a diagnosis or universal effect.", "url": "https://journals.sagepub.com/doi/10.2307/2666999", "doi": "10.2307/2666999", "uses": [ { "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "excerpts": [ "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]" ] }, { "entrySlug": "appendix-b-contrarian-business-perspectives", "entryTitle": "Appendix B: Contrarian Business Perspectives", "excerpts": [ "- Protect good-faith dissent and record unresolved disagreement. Psychological safety can support learning behavior, but this protocol does not diagnose a team or promise candor. [BB-C10-S06]" ] } ] }, { "source_id": "BB-C10-S07", "chapter_slugs": [ "chapter-10-advanced-consulting-frameworks-and-integration" ], "framework": "Value Configurations", "authors": "Stabell, C. B.; Fjeldstad, Ø. D.", "year": 1998, "title": "Configuring Value for Competitive Advantage: On Chains, Shops, and Networks", "venue": "Strategic Management Journal", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://sms.onlinelibrary.wiley.com/doi/10.1002/%28SICI%291097-0266%28199805%2919%3A5%3C413%3A%3AAID-SMJ946%3E3.0.CO%3B2-C", "doi": "10.1002/(SICI)1097-0266(199805)19:5<413::AID-SMJ946>3.0.CO;2-C", "claim_notes": "Inspected Wiley's indexed metadata, DOI, and abstract. It directly distinguishes value chains for long-linked transformation, value shops for intensive problem solving, and value networks for mediated exchange. It supports bounding linear-chain applicability; the chapter's digital-platform activity labels are not attributed to the article.", "uses": [ { "entrySlug": "chapter-10-advanced-consulting-frameworks-and-integration", "entryTitle": "Advanced Consulting Frameworks and Integration", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C12-S01", "chapter_slugs": [ "chapter-12-client-management" ], "framework": "Stakeholder Theory", "authors": "Freeman, R. E.; McVea, J.", "year": 2001, "title": "A Stakeholder Approach to Strategic Management", "venue": "Darden School of Business Working Paper Series / SSRN", "source_type": "academic working paper", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Inspected the Darden-author metadata, SSRN record, abstract, and author-posted paper. It supports stakeholder-oriented strategic management through active attention to stakeholder relationships and interests. Chapter 12 separately treats legal rights, expertise, representation, vulnerability, and harm exposure as author safeguards rather than source-derived stakeholder-theory claims.", "url": "https://papers.ssrn.com/sol3/papers.cfm?abstract_id=263511", "doi": "10.2139/ssrn.263511", "uses": [ { "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "excerpts": [ "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]", "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." ] } ] }, { "source_id": "BB-C12-S02", "chapter_slugs": [ "chapter-12-client-management" ], "framework": "Stakeholder Salience", "authors": "Mitchell, R. K.; Agle, B. R.; Wood, D. J.", "year": 1997, "title": "Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of Who and What Really Counts", "venue": "Academy of Management Review", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Academy of Management Review metadata and abstract were inspected and directly identify stakeholder power, legitimacy, and urgency. Supports the chapter’s three-attribute salience framing, not separate legal-rights or harm analysis.", "url": "https://www.jstor.org/stable/259247", "doi": "10.2307/259247", "uses": [ { "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "excerpts": [ "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]", "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." ] } ] }, { "source_id": "BB-C12-S03", "chapter_slugs": [ "chapter-12-client-management" ], "framework": "Project Scope and Responsibility Management", "authors": "Project Management Institute", "year": 2026, "title": "PMI Lexicon of Project Management Terms, Version 5.0", "venue": "Project Management Institute", "source_type": "professional standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Inspected PMI Lexicon v5.0, last updated January 2026. It defines the RACI and responsibility-assignment matrices; project scope statements; statements of work; risk registers, owners, responses, and mitigation; change control, requests, boards, and systems; formal baselines; and related risk terminology. Chapter 12 uses those definitions narrowly. Its expanded scoping, SOW, risk-register, contract, delegated-authority, capacity, acceptance, and ordinal-scoring fields are author additions rather than PMI-prescribed templates. Citation does not authorize reproduction of PMI content; permissions review remains required for any adapted PMI expression or visual.", "url": "https://www.pmi.org/-/media/pmi/documents/registered/pdf/pmbok-standards/pmi-lexicon-pm-terms.pdf?rev=447328d841c249af985d14177ddd5f95", "doi": null, "uses": [ { "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "excerpts": [ "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]", "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.", "Table 12.2 — Constructed RACI working matrix. Confirm governing authority and required approvals before assigning local RACI labels. [BB-C12-S03]", "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]", "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]", "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]", "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.", "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]", "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.", "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]", "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.", "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." ] } ] }, { "source_id": "BB-C12-S04", "chapter_slugs": [ "chapter-12-client-management" ], "framework": "Executive Communication", "authors": "McKinsey & Company; Minto, B.", "year": 2018, "title": "Barbara Minto: ‘MECE: I invented it, so I get to say how to pronounce it’", "venue": "McKinsey & Company Alumni News", "source_type": "official interview", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Inspected McKinsey's first-party interview with Barbara Minto. It directly supports a governing summary above logically similar, logically ordered supporting ideas. Chapter 12 identifies the question, evidence, implications, uncertainty, ask, alternatives, dissent, and risk fields as an author-created decision-brief adaptation rather than attributing them to Minto.", "url": "https://www.mckinsey.com/alumni/news-and-events/global-news/alumni-news/barbara-minto-mece-i-invented-it-so-i-get-to-say-how-to-pronounce-it", "doi": null, "uses": [ { "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "excerpts": [ "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]", "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." ] } ] }, { "source_id": "BB-C12-S05", "chapter_slugs": [ "chapter-12-client-management" ], "framework": "Difficult Conversations", "authors": "Stone, D.; Patton, B.; Heen, S.", "year": 2010, "title": "Difficult Conversations: How to Discuss What Matters Most", "venue": "Penguin Books", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Google Books description and exposed contents support separating what happened from interpretation/intent, hearing the other perspective, and moving toward a problem-solving conversation. Formal HR, legal, and safety escalation guidance is explicitly separate from this source.", "url": "https://www.penguinrandomhouse.com/books/722989/difficult-conversations-by-douglas-stone-bruce-patton-and-sheila-heen-foreword-by-roger-fisher/", "uses": [ { "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "excerpts": [ "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]", "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.", "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]" ] } ] }, { "source_id": "BB-C12-S06", "chapter_slugs": [ "chapter-12-client-management" ], "framework": "Professional Services Management", "authors": "Maister, D. H.", "year": 1993, "title": "Managing the Professional Service Firm", "venue": "Free Press", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Official Simon & Schuster excerpt and the author’s chapter inventory support balancing client service, professional careers, and firm economics. Stronger portfolio-selection attribution was removed; the source does not provide a universal client-exit rule.", "url": "https://www.simonandschuster.co.uk/books/Managing-The-Professional-Service-Firm/David-H-Maister/9780743231565", "uses": [ { "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C13-S01", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "Lean Startup Cycle", "authors": "Ries, E.", "year": 2011, "title": "The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses", "venue": "Crown Business", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Penguin Random House metadata plus Eric Ries’s official principles and book outline support Build-Measure-Learn, MVP, and pivot/persevere. The chapter’s safety, evidence-quality, cash, pause, and stop gates are labeled author adaptations.", "url": "https://www.penguinrandomhouse.com/books/210088/the-lean-startup-by-eric-ries/", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]", "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]", "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]", "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]", "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." ] } ] }, { "source_id": "BB-C13-S02", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "Customer Development", "authors": "Blank, S.", "year": 2005, "title": "The Four Steps to the Epiphany: Successful Strategies for Products that Win", "venue": "K&S Ranch", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Canonical source for Customer Discovery, Customer Validation, Customer Creation, and Company Building. Use for framework structure, not unsupported interview-count statistics. Verified 2026-07-05: Wiley page confirms The Four Steps to the Epiphany title and states the book was originally published by K&S Ranch; 2005 K&S Ranch edition retained, no DOI found.", "url": "https://www.wiley.com/en-us/The%2BFour%2BSteps%2Bto%2Bthe%2BEpiphany%3A%2BSuccessful%2BStrategies%2Bfor%2BProducts%2Bthat%2BWin-p-9781119690351", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]", "Steve Blank's four Customer Development steps: [BB-C13-S02]" ] } ] }, { "source_id": "BB-C13-S04", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "Founder Equity and Founder's Dilemmas", "authors": "Wasserman, N.", "year": 2012, "title": "The Founder's Dilemmas: Anticipating and Avoiding the Pitfalls That Can Sink a Startup", "venue": "Princeton University Press", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Google Books preview exposes the book’s treatment of founding teams, roles, equity splits, control, and founder conflict. The legal/tax/entity checklist marker was removed; remaining use is limited to founder-equity and control questions.", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=42425", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]", "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.", "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]", "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]" ] } ] }, { "source_id": "BB-C13-S05", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "Founder Equity Allocation", "authors": "Hellmann, T.; Wasserman, N.", "year": 2017, "title": "The First Deal: The Division of Founder Equity in New Ventures", "venue": "Management Science", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Supports evidence-oriented discussion of founder-equity allocation. DOI omitted until verified. Verified 2026-07-05: INFORMS page confirms Hellmann and Wasserman, The First Deal, Management Science 63(8), DOI, and publication record; registry year retained for issue-year citation.", "url": "https://pubsonline.informs.org/doi/10.1287/mnsc.2016.2474", "doi": "10.1287/mnsc.2016.2474", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]", "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.", "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]", "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]" ] } ] }, { "source_id": "BB-C13-S06", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "Startup Failure Reasons", "authors": "CB Insights", "year": 2026, "title": "The Top 9 Reasons Startups Fail", "venue": "CB Insights", "source_type": "practitioner report", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-09", "url": "https://www.cbinsights.com/research/report/startup-failure-reasons-top/", "doi": null, "claim_notes": "Supports current startup-failure post-mortem themes and a multi-causal interpretation of shutdowns. The official 2026 report analyzes 431 VC-backed companies that shut down since 2023; it must not be used as a universal startup failure-rate estimate or retroactively attributed to the 2021 Top 12 report.", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C13-S07", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "Business Survival Data", "authors": "U.S. Bureau of Labor Statistics", "year": 2024, "title": "Business Employment Dynamics: Entrepreneurship and the U.S. Economy", "venue": "U.S. Bureau of Labor Statistics", "source_type": "official publication", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Appropriate source family for business survival or failure-rate claims if those claims are restored. Current chapter wording avoids hard startup failure-rate statistics. Verified 2026-07-05: BLS Business Employment Dynamics page confirms the official Entrepreneurship and the U.S. Economy source family and BLS venue; no DOI found for this web resource.", "url": "https://www.bls.gov/bdm/entrepreneurship/entrepreneurship.htm", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C13-S08", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "Product-Market-Fit Survey Heuristic", "authors": "Ellis, S.", "year": 2009, "title": "The Startup Pyramid", "venue": "Startup Marketing Blog", "source_type": "primary practitioner blog", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.startup-marketing.com/category/productmarket-fit/", "doi": null, "claim_notes": "Inspected Sean Ellis's original February 2009 post on his site. It directly exposes the no-longer-use question, the 40-percent very-disappointed heuristic, the comparison across nearly 100 startups, the statement that the threshold is arbitrary, and the need for a sufficiently large target market. It does not provide representative sampling, causal validation, or a universal PMF threshold.", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]", "- 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]", "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]", "- [ ] PMF evidence triangulates survey, retention, use, paid behavior, referrals, alternatives, and segment-specific needs. [BB-C13-S08] [BB-C13-S09]", "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]" ] } ] }, { "source_id": "BB-C13-S09", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "Product-User Fit and Market Breadth", "authors": "Lauten, P.; Ulevitch, D.", "year": 2019, "title": "Product-User Fit Comes Before Product-Market Fit", "venue": "Andreessen Horowitz", "source_type": "institutional practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://a16z.com/product-user-fit-comes-before-product-market-fit/", "doi": null, "claim_notes": "Inspected the a16z article. It directly distinguishes strong fit with early power users from evidence of a broader market and warns against declaring product-market fit when broader demand remains unknown. It is practitioner reasoning, not independent empirical validation of retention, survey, NPS, or unit-economics cutoffs.", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]", "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.", "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]", "- [ ] PMF evidence triangulates survey, retention, use, paid behavior, referrals, alternatives, and segment-specific needs. [BB-C13-S08] [BB-C13-S09]", "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]" ] } ] }, { "source_id": "BB-C14-S01", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "Value Proposition Design", "authors": "Osterwalder, A.; Pigneur, Y.; Bernarda, G.; Smith, A.", "year": 2014, "title": "Value Proposition Design: How to Create Products and Services Customers Want", "venue": "Wiley", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Canonical source for value proposition, customer profile, and fit framing used in GTM canvas material. Verified 2026-07-05: Wiley page confirms Osterwalder, Pigneur, Bernarda, and Smith, 2014, Value Proposition Design title, and Wiley publication; no DOI found for the book.", "url": "https://www.wiley.com/en-gb/Value%2BProposition%2BDesign%3A%2BHow%2Bto%2BCreate%2BProducts%2Band%2BServices%2BCustomers%2BWant-p-9781118968055", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C14-S02", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "Market Entry and Chasm Crossing", "authors": "Moore, G. A.", "year": 2014, "title": "Crossing the Chasm, 3rd Edition: Marketing and Selling Disruptive Products to Mainstream Customers", "venue": "HarperBusiness", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "HarperCollins and Geoffrey Moore’s official book page support the early-market/mainstream, beachhead, reference-customer, and adoption-barrier framing. The chapter presents it as a bounded practitioner lens, not a universal adoption sequence.", "url": "https://www.harpercollins.com/products/crossing-the-chasm-3rd-edition-geoffrey-a-moore", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C14-S03", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "Jobs to Be Done", "authors": "Christensen, C. M.; Hall, T.; Dillon, K.; Duncan, D. S.", "year": 2016, "title": "Know Your Customers' 'Jobs to Be Done'", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Supports customer-problem and jobs-to-be-done framing for ICP and segmentation. Verified 2026-07-05: Harvard Business Review/HBS faculty pages confirm Christensen, Hall, Dillon, and Duncan, September 2016, HBR venue, and exact title styling; title corrected to include the inner quoted phrase.", "url": "https://hbr.org/2016/09/know-your-customers-jobs-to-be-done", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C14-S04", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "Bullseye Framework", "authors": "Weinberg, G.; Khan, O.", "year": 2015, "title": "The Bullseye Framework for Startup Traction", "venue": "The SaaS Podcast, Episode 34; SaaS Club", "source_type": "primary practitioner interview", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Inspected the full primary interview transcript with Traction coauthor Gabriel Weinberg. He describes Bullseye as brainstorming across 19 acquisition channels, ranking candidates, running inexpensive tests in parallel, focusing on the channel that produces evidence, and repeating the process when it plateaus. The chapter does not attribute universal conversion, budget, speed, or causal benchmarks to this source; its matrices and legal safeguards are explicitly author-created.", "url": "https://saasclub.io/podcast/gabriel-weinberg-duckduckgo-2/", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "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]", "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]", "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]", "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]", "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.", "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.", "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]" ] } ] }, { "source_id": "BB-C14-S05", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "Pricing Strategy", "authors": "Nagle, T. T.; Hogan, J.; Zale, J.", "year": 2016, "title": "The Strategy and Tactics of Pricing: A Guide to Growing More Profitably, New International Edition", "venue": "Routledge", "source_type": "academic/practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Routledge DOI metadata and the exact-edition Google Books preview support value creation/communication, price setting, price sensitivity, cost, competition, and willingness-to-pay evidence. Wording now retains cost, capacity, risk, competition, and required-return constraints.", "url": "https://www.taylorfrancis.com/books/mono/10.4324/9781315266220/strategy-tactics-pricing-thomas-nagle-john-hogan-joseph-zale", "doi": "10.4324/9781315266220", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "- Percentage of transaction: Marketplace fee; determine the basis and rate from value, cost, risk, competition, contract, and willingness-to-pay evidence. [BB-C14-S05]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C14-S06", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "Viral Marketing", "authors": "Leskovec, J.; Adamic, L. A.; Huberman, B. A.", "year": 2007, "title": "The Dynamics of Viral Marketing", "venue": "ACM Transactions on the Web", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Supports viral marketing dynamics and network-based diffusion. DOI omitted until verified. Verified 2026-07-05: ACM Digital Library confirms Leskovec, Adamic, and Huberman, 2007, ACM Transactions on the Web article, and DOI.", "url": "https://dl.acm.org/doi/10.1145/1232722.1232727", "doi": "10.1145/1232722.1232727", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C15-S01", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Pitch Deck Structure", "authors": "Kawasaki, G.", "year": 2015, "title": "The Art of the Start 2.0: The Time-Tested, Battle-Hardened Guide for Anyone Starting Anything", "venue": "Portfolio", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.penguinrandomhouse.com/books/318082/the-art-of-the-start-20-by-guy-kawasaki/", "doi": null, "claim_notes": "Supports practitioner pitch-deck structure and startup presentation guidance; use for deck framing, not empirical conversion rates. Verified 2026-07-05: Penguin Random House page confirms Kawasaki, The Art of the Start 2.0, 2015 Portfolio publication, and ISBN; no DOI found.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C15-S02", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Founder Experience and Venture Funding", "authors": "Hsu, D. H.", "year": 2007, "title": "Experienced Entrepreneurial Founders, Organizational Capital, and Venture Capital Funding", "venue": "Research Policy", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.sciencedirect.com/science/article/abs/pii/S0048733307000716", "doi": "10.1016/j.respol.2007.02.022", "claim_notes": "Supports the relevance of founder experience and organizational capital in venture funding decisions. Verified 2026-07-05: ScienceDirect/Research Policy page confirms Hsu, 2007, title, volume 36 issue 5 pages 722-741, and DOI.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C15-S03", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Venture Selection Criteria", "authors": "Baum, J. A.; Silverman, B. S.", "year": 2004, "title": "Picking Winners or Building Them? Alliance, Intellectual, and Human Capital as Selection Criteria in Venture Financing and Performance of Biotechnology Startups", "venue": "Journal of Business Venturing", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.sciencedirect.com/science/article/abs/pii/S0883902603000387", "doi": "10.1016/S0883-9026(03)00038-7", "claim_notes": "Supports investor screening criteria related to alliances, intellectual capital, and human capital. Verified 2026-07-05: ScienceDirect/Journal of Business Venturing page confirms Baum and Silverman, 2004, full title/subtitle, pages 411-436, and DOI; title expanded to the complete publication title.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C15-S04", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Pitch Presentation", "authors": "Clark, C.", "year": 2008, "title": "The Impact of Entrepreneurs' Oral 'Pitch' Presentation Skills on Business Angels' Initial Screening Investment Decisions", "venue": "Venture Capital", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.tandfonline.com/doi/abs/10.1080/13691060802151945", "doi": "10.1080/13691060802151945", "claim_notes": "Supports the idea that pitch presentation quality can affect early investor screening. Verified 2026-07-05: Taylor & Francis page confirms Clark, 2008, Venture Capital article title, and DOI.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C15-S05", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Venture Capital Method", "authors": "Sahlman, W. A.; Scherlis, D. R.", "year": 2009, "title": "A Method for Valuing High-Risk, Long-Term Investments: The Venture Capital Method", "venue": "Harvard Business School Background Note", "source_type": "teaching note", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=6515", "doi": null, "claim_notes": "Supports the backward-looking venture capital valuation method used in startup finance teaching. Verified 2026-07-05: Harvard Business School faculty record confirms the venture capital method background note record and HBS venue; no DOI found for the teaching note.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C15-S06", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "VC Decision-Making", "authors": "Gompers, P. A.; Gornall, W.; Kaplan, S. N.; Strebulaev, I. A.", "year": 2020, "title": "How Do Venture Capitalists Make Decisions?", "venue": "Journal of Financial Economics", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.sciencedirect.com/science/article/pii/S0304405X19301680", "doi": "10.1016/j.jfineco.2019.06.011", "claim_notes": "Supports VC decision-making practices across sourcing, selection, valuation, deal structure, monitoring, and exits. Verified 2026-07-05: ScienceDirect/RePEc records confirm Gompers, Gornall, Kaplan, and Strebulaev, Journal of Financial Economics 135(1), 2020, and DOI.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C15-S07", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Entrepreneurial Experimentation", "authors": "Kerr, W. R.; Nanda, R.; Rhodes-Kropf, M.", "year": 2014, "title": "Entrepreneurship as Experimentation", "venue": "Journal of Economic Perspectives", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.aeaweb.org/articles?id=10.1257/jep.28.3.25", "doi": "10.1257/jep.28.3.25", "claim_notes": "Supports startup uncertainty, experimentation, and financing under uncertain entrepreneurial outcomes. Verified 2026-07-05: American Economic Association page confirms Kerr, Nanda, and Rhodes-Kropf, Journal of Economic Perspectives 28(3), 2014, pages 25-48, and DOI.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C15-S08", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Venture Financing Model Documents", "authors": "National Venture Capital Association", "year": 2026, "title": "NVCA Model Legal Documents", "venue": "National Venture Capital Association", "source_type": "official model legal documents", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://nvca.org/model-legal-documents/", "doi": null, "claim_notes": "Official NVCA landing page and the directly downloadable current model Certificate of Incorporation (October 2025), Investors' Rights Agreement (October 2025), Voting Agreement (June 2026), and Right of First Refusal and Co-Sale Agreement (April 2026) were inspected in full. They support alternative provisions for liquidation preference, conversion, anti-dilution, dividends, protective and voting rights, board composition, information and future-financing rights, drag-along, first-refusal, co-sale, and transfer restrictions. NVCA states the documents are starting points requiring tailoring and are not legal advice; they do not establish universal, current-market, founder-friendly, or investor-friendly terms.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "- 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]", "“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]", "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]", "- 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]" ] } ] }, { "source_id": "BB-C15-S09", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "VC Contracting", "authors": "Kaplan, S. N.; Stromberg, P.", "year": 2003, "title": "Financial Contracting Theory Meets the Real World: An Empirical Analysis of Venture Capital Contracts", "venue": "Review of Economic Studies", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://academic.oup.com/restud/article-abstract/70/2/281/1586768", "doi": "10.1111/1467-937X.00245", "claim_notes": "Supports the use of cash-flow rights, board rights, voting rights, liquidation rights, and other control rights in VC contracts. Verified 2026-07-05: Oxford Academic page confirms Kaplan and Stromberg, Review of Economic Studies 70(2), pages 281-315, and DOI.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "- 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]", "“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]", "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]", "- 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]" ] } ] }, { "source_id": "BB-C15-S10", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Investor Abilities and Contracting", "authors": "Bengtsson, O.; Sensoy, B. A.", "year": 2011, "title": "Investor Abilities and Financial Contracting: Evidence from Venture Capital", "venue": "Journal of Financial Intermediation", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.sciencedirect.com/science/article/abs/pii/S1042957311000076", "doi": "10.1016/j.jfi.2011.02.001", "claim_notes": "Supports variation in venture contracting terms and investor-related contracting differences. Verified 2026-07-05: ScienceDirect/Journal of Financial Intermediation page confirms Bengtsson and Sensoy, 2011, volume 20 issue 4 pages 477-502, and DOI.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]", "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]", "“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]" ] } ] }, { "source_id": "BB-C15-S11", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Contracts and Exits", "authors": "Cumming, D. J.", "year": 2008, "title": "Contracts and Exits in Venture Capital Finance", "venue": "Review of Financial Studies", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://academic.oup.com/rfs/article-abstract/21/5/1947/1571470", "doi": "10.1093/rfs/hhn072", "claim_notes": "Supports the relationship between VC contract terms and exit outcomes. Verified 2026-07-05: JSTOR/RePEc/Oxford records confirm Cumming, Review of Financial Studies 21(5), 2008, pages 1947-1982, and DOI.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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]", "“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]" ] } ] }, { "source_id": "BB-C15-S12", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Startup Valuation", "authors": "Damodaran, A.", "year": 2009, "title": "Valuing Young, Start-up and Growth Companies: Estimation Issues and Valuation Challenges", "venue": "NYU Stern School of Business", "source_type": "working paper", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://pages.stern.nyu.edu/~adamodar/pdfiles/papers/younggrowth.pdf", "doi": null, "claim_notes": "Supports valuation challenges for young companies, including limited operating history, survival risk, and use of forecasts and discount rates. Verified 2026-07-05: NYU Stern PDF confirms Damodaran, May 2009, title, and Stern School of Business venue; no DOI found.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C15-S13", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "SAFE Financing", "authors": "Y Combinator", "year": 2023, "title": "Post-Money SAFE User Guide", "venue": "Y Combinator", "source_type": "model document guide", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://bookface-static.ycombinator.com/assets/ycdc/Website%20User%20Guide%20Feb%202023%20-%20final-28acf9a3b938e643cc270b7da514194d5c271359be25b631b025605673fa9f95.pdf", "doi": null, "claim_notes": "Supports post-money SAFE mechanics and conversion examples; use for SAFE structure, not broad market statistics. Verified 2026-07-05: Y Combinator official PDF confirms the Post-Money SAFE User Guide and February 2023 document; no DOI found.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C15-S14", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "VC Market Context", "authors": "National Venture Capital Association; PitchBook", "year": 2026, "title": "NVCA 2026 Yearbook", "venue": "National Venture Capital Association", "source_type": "industry report", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://nvca.org/2026-nvca-yearbook/", "doi": null, "claim_notes": "Supports current U.S. venture capital market context and aggregate activity; do not use for generic founder success-rate claims without claim-level inspection. Verified 2026-07-05: NVCA page confirms the 2026 NVCA Yearbook with data provided by PitchBook and links to the official report/public data pack; no DOI found.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C15-S15", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Entrepreneurial Risk", "authors": "Hall, R. E.; Woodward, S. E.", "year": 2010, "title": "The Burden of the Nondiversifiable Risk of Entrepreneurship", "venue": "American Economic Review", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.aeaweb.org/articles?id=10.1257/aer.100.3.1163", "doi": "10.1257/aer.100.3.1163", "claim_notes": "Supports the high-risk, nondiversified economics of entrepreneurship and founder payoff uncertainty. Verified 2026-07-05: American Economic Association page confirms Hall and Woodward, American Economic Review 100(3), 2010, title, and DOI.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C15-S16", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Portfolio Company Valuation", "authors": "AICPA", "year": 2019, "title": "Valuation of Portfolio Company Investments of Venture Capital and Private Equity Funds and Other Investment Companies", "venue": "AICPA Accounting and Valuation Guide", "source_type": "professional guide", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.aicpa-cima.com/cpe-learning/publication/valuation-of-portfolio-company-investments-of-venture-capital-and-private-equity-funds-and-other-investment-companies-accounting-and-valuation-guide-OPL", "doi": null, "claim_notes": "Supports professional valuation considerations for venture capital and private equity portfolio company investments. Verified 2026-07-05: AICPA-CIMA page confirms the accounting and valuation guide title, scope, and AICPA source family; no DOI found.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C15-S17", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Theranos Failure Case", "authors": "U.S. Securities and Exchange Commission", "year": 2018, "title": "Theranos, CEO Holmes, and Former President Balwani Charged With Massive Fraud", "venue": "SEC Press Release", "source_type": "regulator publication", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.sec.gov/newsroom/press-releases/2018-41", "doi": null, "claim_notes": "Official SEC release inspected at claim level. Supports that the SEC charged Theranos, Elizabeth Holmes, and Ramesh Balwani; alleged false or exaggerated statements; reported more than $700 million raised from investors; and described specified settlements without admission or denial. Chapter language preserves the distinction between allegations, charges, and settlements and does not treat the release as an adjudication.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C15-S18", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "WeWork Failure Case", "authors": "The We Company", "year": 2019, "title": "Form S-1 Registration Statement", "venue": "U.S. Securities and Exchange Commission EDGAR", "source_type": "securities filing", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.sec.gov/Archives/edgar/data/1533523/000119312519220499/d781982ds1.htm", "doi": null, "claim_notes": "Full SEC-hosted Form S-1 inspected through lawful Exa retrieval after the ordinary page fetch failed. Supports the bounded chapter statement that the issuer disclosed revenue, losses, lease obligations and risk factors, related-party transactions, and governance/control structure as of the filing. The chapter identifies it as issuer disclosure, not adjudicated fact, and makes no later-outcome or motive claim from this source.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C15-S19", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "FTX Failure Case", "authors": "Ray, J. J. III", "year": 2022, "title": "Testimony of Mr. John J. Ray III CEO, FTX Debtors", "venue": "U.S. House Committee on Financial Services", "source_type": "congressional testimony", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://democrats-financialservices.house.gov/uploadedfiles/hhrg-117-ba00-wstate-rayj-20221213.pdf", "doi": null, "claim_notes": "Full U.S. House testimony inspected at claim level. Supports John J. Ray III's bounded witness account, as CEO of the FTX debtors after the bankruptcy filings, of control, governance, recordkeeping, security, and asset-management failures. The chapter identifies it as testimony and does not present it as adjudicated fact or a complete transaction history.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C18-S01", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Platform Economy Framework", "authors": "Parker, G. G.; Van Alstyne, M. W.; Choudary, S. P.", "year": 2016, "title": "Platform Revolution: How Networked Markets Are Transforming the Economy and How to Make Them Work for You", "venue": "W. W. Norton & Company", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://wwnorton.com/books/platform-revolution", "doi": null, "claim_notes": "Google Books preview and the same authors’ HBR article support the pipeline-versus-platform distinction and producer/consumer interaction and matching logic. The chapter labels its diagram as a hypothesis map and makes no asset-free, unlimited-growth, margin, or causal guarantee.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The platform economy framework treats a platform as a coordination and governance arrangement among participant groups whose choices are interdependent. It is a decision lens, not a claim that platforms are asset-free, unlimited, high-margin, or destined to dominate. [BB-C18-S01] [BB-C18-S03]", "Many firms combine pipeline and platform activities, own or control important assets, and bear inventory-like obligations. “Platform” is not equivalent to asset-free, unlimited, or high margin. [BB-C18-S01] [BB-C18-S03]", "Figure 18.1. Platform interaction and learning loop. The author-created diagram links relevant supply, matching, trusted transaction, repeat demand, and data-informed improvement. It is a hypothesis map, not a causal guarantee. Source basis: platform and multisided-market strategy. [BB-C18-S01] [BB-C18-S03] [BB-C18-S06]" ] } ] }, { "source_id": "BB-C18-S02", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Network Effects Typology", "authors": "Katz, M. L.; Shapiro, C.", "year": 1985, "title": "Network Externalities, Competition, and Compatibility", "venue": "American Economic Review", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.jstor.org/stable/1814809", "doi": "10.2307/1814809", "claim_notes": "Full 17-page American Economic Review article inspected through the public full text uploaded by coauthor Carl Shapiro; bibliographic details cross-checked against AER/RePEc. Supports positive consumption externalities arising through direct physical network effects, indirect complementary-product effects, and service-network effects; the scope of the relevant network; consumer expectations; compatibility; and competition. It does not support modern platform taxonomy labels, viral coefficients, growth thresholds, universal positive effects, or guaranteed platform outcomes.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The network-effects typology asks how participation changes value for a defined side, segment, geography, and time window. Direct, indirect, data, and exchange effects can be positive, weak, local, congested, reversible, or negative; they are not a universal growth law. [BB-C18-S02] [BB-C18-S03]", "Network Effect Definition: The value of a platform can increase as more users join. [BB-C18-S02]", "Constructed example: A telephone network with one subscriber cannot support a call within the network; with two, a call becomes possible. As reachable participants grow, the set of possible connections grows, but realized value depends on usage, quality, congestion, and alternatives. [BB-C18-S02]", "Contingent comparison: Do not rank network-effect labels in the abstract. Compare effect direction and magnitude for the relevant side, segment, geography, time, quality level, and price structure; then test multi-homing, congestion, interoperability, governance, cost, and decay. [BB-C18-S02] [BB-C18-S03]", "For each proposed model, test: (1) local density and matching quality; (2) cohort contribution and cash needs before and during growth; (3) trust, safety, quality, fraud, moderation, dispute, appeal, and remedy; (4) which side, if any, should be subsidized and for how long; (5) multi-homing, disintermediation, interoperability, congestion, bargaining power, and competition; and (6) data rights, security, privacy, accessibility, labor, consumer, and regulatory obligations from the first design. No result is universal, and no threshold guarantees success. [BB-C18-S02] [BB-C18-S03] [BB-C18-S06] [BB-C18-S09] [BB-C18-S10]" ] } ] }, { "source_id": "BB-C18-S03", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Two-Sided Platform Strategy", "authors": "Eisenmann, T.; Parker, G.; Van Alstyne, M. W.", "year": 2006, "title": "Strategies for Two-Sided Markets", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=22459", "doi": null, "claim_notes": "Supports two-sided market strategy, cross-side network effects, and subsidizing one side of a platform. Use as practitioner support rather than empirical benchmark support. Verified 2026-07-05 against Harvard Business School faculty record for Eisenmann, Parker, and Van Alstyne, Harvard Business Review 84(10), October 2006; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The platform economy framework treats a platform as a coordination and governance arrangement among participant groups whose choices are interdependent. It is a decision lens, not a claim that platforms are asset-free, unlimited, high-margin, or destined to dominate. [BB-C18-S01] [BB-C18-S03]", "Many firms combine pipeline and platform activities, own or control important assets, and bear inventory-like obligations. “Platform” is not equivalent to asset-free, unlimited, or high margin. [BB-C18-S01] [BB-C18-S03]", "Figure 18.1. Platform interaction and learning loop. The author-created diagram links relevant supply, matching, trusted transaction, repeat demand, and data-informed improvement. It is a hypothesis map, not a causal guarantee. Source basis: platform and multisided-market strategy. [BB-C18-S01] [BB-C18-S03] [BB-C18-S06]", "The network-effects typology asks how participation changes value for a defined side, segment, geography, and time window. Direct, indirect, data, and exchange effects can be positive, weak, local, congested, reversible, or negative; they are not a universal growth law. [BB-C18-S02] [BB-C18-S03]", "Contingent comparison: Do not rank network-effect labels in the abstract. Compare effect direction and magnitude for the relevant side, segment, geography, time, quality level, and price structure; then test multi-homing, congestion, interoperability, governance, cost, and decay. [BB-C18-S02] [BB-C18-S03]", "For each proposed model, test: (1) local density and matching quality; (2) cohort contribution and cash needs before and during growth; (3) trust, safety, quality, fraud, moderation, dispute, appeal, and remedy; (4) which side, if any, should be subsidized and for how long; (5) multi-homing, disintermediation, interoperability, congestion, bargaining power, and competition; and (6) data rights, security, privacy, accessibility, labor, consumer, and regulatory obligations from the first design. No result is universal, and no threshold guarantees success. [BB-C18-S02] [BB-C18-S03] [BB-C18-S06] [BB-C18-S09] [BB-C18-S10]" ] } ] }, { "source_id": "BB-C18-S04", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Digital Revenue Models", "authors": "Teece, D. J.", "year": 2010, "title": "Business Models, Business Strategy and Innovation", "venue": "Long Range Planning", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.sciencedirect.com/science/article/pii/S002463010900051X", "doi": "10.1016/j.lrp.2009.07.003", "claim_notes": "Supports the concept of business models as value creation, delivery, and capture architecture. Does not validate the chapter's illustrative pricing ranges. Verified 2026-07-05 against ScienceDirect DOI record for Long Range Planning 43(2-3), 2010.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The digital revenue-model framework separates value creation, value delivery, and value capture. Advertising, subscription, transaction, usage, licensing, affiliate, services, and hybrid models are choices with different payer incentives, cost drivers, risks, and control requirements—not a menu of guaranteed margins. [BB-C18-S04] [BB-C18-S05]" ] } ] }, { "source_id": "BB-C18-S05", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "E-Business Value Creation", "authors": "Amit, R.; Zott, C.", "year": 2001, "title": "Value Creation in E-Business", "venue": "Strategic Management Journal", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://sms.onlinelibrary.wiley.com/doi/10.1002/smj.187", "doi": "10.1002/smj.187", "claim_notes": "Supports value creation mechanisms in e-business. Use for conceptual revenue-model framing, not for SaaS or marketplace benchmark statistics. Verified 2026-07-05 against Wiley Strategic Management Journal DOI record for Amit and Zott, 2001.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The digital revenue-model framework separates value creation, value delivery, and value capture. Advertising, subscription, transaction, usage, licensing, affiliate, services, and hybrid models are choices with different payer incentives, cost drivers, risks, and control requirements—not a menu of guaranteed margins. [BB-C18-S04] [BB-C18-S05]" ] } ] }, { "source_id": "BB-C18-S06", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "API Economy and Ecosystem Value", "authors": "Boudreau, K. J.; Hagiu, A.", "year": 2009, "title": "Platform Rules: Multi-Sided Platforms as Regulators", "venue": "Platforms, Markets and Innovation", "source_type": "academic book chapter", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=35339", "doi": null, "claim_notes": "Supports platform governance, access rules, and non-price instruments in multi-sided platforms. Does not validate current API marketplace counts. Verified 2026-07-05 against Harvard Business School faculty record for the 2009 Platforms, Markets and Innovation chapter; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "Figure 18.1. Platform interaction and learning loop. The author-created diagram links relevant supply, matching, trusted transaction, repeat demand, and data-informed improvement. It is a hypothesis map, not a causal guarantee. Source basis: platform and multisided-market strategy. [BB-C18-S01] [BB-C18-S03] [BB-C18-S06]", "The API and ecosystem framework treats an interface as a governed dependency, not proof of a platform or network effect. Value depends on useful complementor jobs, reliability, versioning, security, data rights, support cost, bargaining power, and who captures value. [BB-C18-S06]", "Constructed API transition: A standalone workflow tool may expose a governed API so authorized complementors can exchange events or extend a task. The team must test whether integrations improve customer outcomes after security, privacy, reliability, support, versioning, review, bargaining-power, and ecosystem-governance costs; an API count does not establish platform value. [BB-C18-S06]", "Constructed partner-ecosystem hypothesis: A core service opens governed interfaces; complementors build relevant extensions; customer outcomes and complementor economics may improve; the core service may gain qualified demand or retention. Test each link, full cost, counterfactual, concentration, incidents, governance, and who captures value. [BB-C18-S06]", "For each proposed model, test: (1) local density and matching quality; (2) cohort contribution and cash needs before and during growth; (3) trust, safety, quality, fraud, moderation, dispute, appeal, and remedy; (4) which side, if any, should be subsidized and for how long; (5) multi-homing, disintermediation, interoperability, congestion, bargaining power, and competition; and (6) data rights, security, privacy, accessibility, labor, consumer, and regulatory obligations from the first design. No result is universal, and no threshold guarantees success. [BB-C18-S02] [BB-C18-S03] [BB-C18-S06] [BB-C18-S09] [BB-C18-S10]" ] } ] }, { "source_id": "BB-C18-S07", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Data Monetization Models", "authors": "Hartmann, P. M.; Zaki, M.; Feldmann, N.; Neely, A.", "year": 2016, "title": "Capturing Value from Big Data - A Taxonomy of Data-Driven Business Models Used by Start-Up Firms", "venue": "International Journal of Operations & Production Management", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.emerald.com/ijopm/article/36/10/1382/303563/Capturing-value-from-big-data-a-taxonomy-of-data", "doi": "10.1108/IJOPM-02-2014-0098", "claim_notes": "Supports data-driven business model taxonomy and data as a value-capture resource. Does not support unsupported margin or price examples. Verified 2026-07-05 against Emerald publisher record for International Journal of Operations & Production Management 36(10), 2016.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The data monetization gate treats data value as conditional on authority, purpose, quality, affected-party interests, security, fairness, competition, and remedy. “Public,” “purchased,” “inferred,” or “de-identified” does not by itself establish permission, low risk, or durable value. [BB-C18-S07] [BB-C18-S10]" ] } ] }, { "source_id": "BB-C18-S08", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Digital Ecosystem Mapping", "authors": "Adner, R.", "year": 2017, "title": "Ecosystem as Structure: An Actionable Construct for Strategy", "venue": "Journal of Management", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-12", "url": "https://journals.sagepub.com/doi/10.1177/0149206316678451", "doi": "10.1177/0149206316678451", "claim_notes": "Primary journal record inspected 2026-07-12. Supports an ecosystem-as-structure lens, role and interdependence mapping, and the warning that an ecosystem perspective is neither necessary nor sufficient for every strategy problem. It does not support universal platform dominance, company-specific pricing, or current market claims.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The ecosystem-structure map makes interdependent roles, bottlenecks, dependencies, and adoption risks explicit. An ecosystem lens can clarify a strategy problem, but it is neither necessary nor sufficient for every business model. [BB-C18-S08]" ] } ] }, { "source_id": "BB-C18-S09", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Cybersecurity Risk Matrix", "authors": "National Institute of Standards and Technology", "year": 2024, "title": "The NIST Cybersecurity Framework (CSF) 2.0", "venue": "NIST CSWP 29", "source_type": "government standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.nist.gov/publications/nist-cybersecurity-framework-csf-20", "doi": "10.6028/NIST.CSWP.29", "claim_notes": "Supports use of cybersecurity outcomes and risk-management categories. Does not support dollar-loss examples or budget ranges. Verified 2026-07-05 against NIST publication page and DOI for CSWP 29, February 26, 2024.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The platform cybersecurity risk matrix translates business-model choices into security outcomes, affected assets, plausible threats, control evidence, residual risk, and accountable decisions. It is a prioritization aid, not a probability or loss benchmark. [BB-C18-S09]", "For each proposed model, test: (1) local density and matching quality; (2) cohort contribution and cash needs before and during growth; (3) trust, safety, quality, fraud, moderation, dispute, appeal, and remedy; (4) which side, if any, should be subsidized and for how long; (5) multi-homing, disintermediation, interoperability, congestion, bargaining power, and competition; and (6) data rights, security, privacy, accessibility, labor, consumer, and regulatory obligations from the first design. No result is universal, and no threshold guarantees success. [BB-C18-S02] [BB-C18-S03] [BB-C18-S06] [BB-C18-S09] [BB-C18-S10]" ] } ] }, { "source_id": "BB-C18-S10", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Privacy Regulation and Platform Risk", "authors": "European Parliament; Council of the European Union", "year": 2016, "title": "Regulation (EU) 2016/679, Article 83: General Conditions for Imposing Administrative Fines", "venue": "General Data Protection Regulation", "source_type": "regulation", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng", "doi": null, "claim_notes": "Supports the GDPR administrative fine ceiling of 20 million euros or 4 percent of worldwide annual turnover for higher-tier infringements. Verified 2026-07-05 against EUR-Lex official GDPR record and Article 83 fine provisions; no DOI applies.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The data monetization gate treats data value as conditional on authority, purpose, quality, affected-party interests, security, fairness, competition, and remedy. “Public,” “purchased,” “inferred,” or “de-identified” does not by itself establish permission, low risk, or durable value. [BB-C18-S07] [BB-C18-S10]", "For each proposed model, test: (1) local density and matching quality; (2) cohort contribution and cash needs before and during growth; (3) trust, safety, quality, fraud, moderation, dispute, appeal, and remedy; (4) which side, if any, should be subsidized and for how long; (5) multi-homing, disintermediation, interoperability, congestion, bargaining power, and competition; and (6) data rights, security, privacy, accessibility, labor, consumer, and regulatory obligations from the first design. No result is universal, and no threshold guarantees success. [BB-C18-S02] [BB-C18-S03] [BB-C18-S06] [BB-C18-S09] [BB-C18-S10]" ] } ] }, { "source_id": "BB-C18-S11", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Digital KPI Dashboard", "authors": "Croll, A.; Yoskovitz, B.", "year": 2013, "title": "Lean Analytics: Use Data to Build a Better Startup Faster", "venue": "O'Reilly Media", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-12", "url": "https://www.oreilly.com/library/view/lean-analytics/9781449335687/", "doi": null, "claim_notes": "Publisher record inspected 2026-07-12. Supports metric selection by business model, cohort and stage thinking, leading versus lagging measures, and data-informed rather than purely data-driven decisions. Chapter targets remain constructed local inputs, not external benchmarks.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The digital KPI dashboard links a business-model hypothesis to a small set of defined leading, operating, outcome, and guardrail measures. Metrics should narrow uncertainty and trigger decisions; they should not become vanity targets or universal benchmarks. [BB-C18-S11]" ] } ] }, { "source_id": "BB-C18-S12", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Automation Opportunity Assessment", "authors": "Brynjolfsson, E.; McAfee, A.", "year": 2014, "title": "The Second Machine Age: Work, Progress, and Prosperity in a Time of Brilliant Technologies", "venue": "W. W. Norton & Company", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-12", "url": "https://wwnorton.com/books/the-second-machine-age/", "doi": null, "claim_notes": "Publisher record inspected 2026-07-12. Supports the broad managerial framing that digital technologies can reshape tasks, work, and human-machine collaboration. It does not validate automation ROI percentages, labor-outcome predictions, or a universal substitution path.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The automation opportunity assessment compares task and workflow redesign options while keeping human judgment, affected-worker effects, quality, safety, security, accessibility, and accountability visible. Digital technology can change tasks and work, but a source or tool does not predict a universal substitution path. [BB-C18-S12]" ] } ] }, { "source_id": "BB-C18-S13", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Digital Transformation Roadmap", "authors": "Westerman, G.; Bonnet, D.; McAfee, A.", "year": 2014, "title": "Leading Digital: Turning Technology into Business Transformation", "venue": "Harvard Business Review Press", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-12", "url": "https://store.hbr.org/product/leading-digital-turning-technology-into-business-transformation/17039", "doi": null, "claim_notes": "Publisher record and author/title record inspected 2026-07-12. Supports the broad digital-transformation leadership and capability-roadmap framing. It does not support the chapter's fictional retail metrics, fixed timelines, or guaranteed transformation outcomes.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The digital transformation roadmap sequences a portfolio of business, capability, operating-model, data, technology, workforce, and governance changes around evidence and decision rights. A roadmap is a coordination artifact, not a fixed timetable or guarantee of transformation success. [BB-C18-S13]" ] } ] }, { "source_id": "BB-C18-S16", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Digital Markets Act Legislation and Gatekeeper Scope", "authors": "European Parliament; Council of the European Union; European Commission", "year": 2022, "title": "Digital Markets Act (DMA) Legislation", "venue": "European Commission", "source_type": "primary legislation portal", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://digital-markets-act.ec.europa.eu/about-dma/legislation_en", "doi": null, "claim_notes": "Official European Commission legislation page inspected on 2026-07-11. It identifies Regulation (EU) 2022/1925 and the procedural implementing regulation and states that the DMA contains the main designation rules and obligations/prohibitions for gatekeepers. It supports issue spotting only; current coverage, service scope, legal effect, and remedies require the legislation, decisions, appeals, facts, and qualified counsel.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "This is a managerial issue-spotting tool, not legal advice. Designation, service scope, obligations, compliance measures, decisions, appeals, and enforcement can change; confirm the current official record with qualified counsel. [BB-C18-S16] [BB-C18-S17]", "The EU Digital Markets Act (DMA) is an ex-ante regulatory regime for designated gatekeepers providing specified core platform services. It complements rather than replaces EU competition law. Its obligations and prohibitions are not a generic code for every platform, and a firm's product label alone does not determine coverage. [BB-C18-S16] [BB-C18-S17]", "Figure 18.2. Platform-regulation and complementor decision route (constructed). The route separates scope, current legal evidence, technical/product facts, strategic consequences, and accountable approval. It does not infer that the DMA applies or prescribe a legal conclusion. [BB-C18-S16] [BB-C18-S17] [BB-C18-S18]" ] } ] }, { "source_id": "BB-C18-S17", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Digital Markets Act Managerial Context", "authors": "European Commission", "year": 2026, "title": "About the Digital Markets Act", "venue": "European Commission", "source_type": "official institutional guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://digital-markets-act.ec.europa.eu/about-dma_en", "doi": null, "claim_notes": "Official European Commission overview inspected on 2026-07-11. It supports the ex-ante gatekeeper framing, core-platform-service context, complementarity with EU competition law, and examples of obligations and prohibitions. It does not determine coverage or legal outcomes for a particular firm, service, or feature.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "This is a managerial issue-spotting tool, not legal advice. Designation, service scope, obligations, compliance measures, decisions, appeals, and enforcement can change; confirm the current official record with qualified counsel. [BB-C18-S16] [BB-C18-S17]", "The EU Digital Markets Act (DMA) is an ex-ante regulatory regime for designated gatekeepers providing specified core platform services. It complements rather than replaces EU competition law. Its obligations and prohibitions are not a generic code for every platform, and a firm's product label alone does not determine coverage. [BB-C18-S16] [BB-C18-S17]", "Figure 18.2. Platform-regulation and complementor decision route (constructed). The route separates scope, current legal evidence, technical/product facts, strategic consequences, and accountable approval. It does not infer that the DMA applies or prescribe a legal conclusion. [BB-C18-S16] [BB-C18-S17] [BB-C18-S18]" ] } ] }, { "source_id": "BB-C18-S18", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "DMA Complementor and Developer Resources", "authors": "European Commission", "year": 2026, "title": "Digital Markets Act Developer Portal", "venue": "European Commission", "source_type": "official developer guidance portal", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://digital-markets-act.ec.europa.eu/developer-portal_en", "doi": null, "claim_notes": "Official European Commission developer portal inspected on 2026-07-11. It organizes practical business resources for interoperability, data portability, data access, and app distribution and provides channels for raising concerns. It is a starting point for current evidence, not legal advice, a guarantee of access, or evidence of commercial success.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The Commission's developer portal currently organizes practical resources around topics including interoperability, data portability, data access, and app distribution. Treat those resources as starting points for current evidence, not as a substitute for the legislation, designation decisions, enforcement record, product-specific analysis, or counsel. [BB-C18-S18]", "Figure 18.2. Platform-regulation and complementor decision route (constructed). The route separates scope, current legal evidence, technical/product facts, strategic consequences, and accountable approval. It does not infer that the DMA applies or prescribe a legal conclusion. [BB-C18-S16] [BB-C18-S17] [BB-C18-S18]" ] } ] }, { "source_id": "BB-C18-S19", "chapter_slugs": [ "chapter-18-digital-business-models-and-platform-economics" ], "framework": "Digital Markets Act Review and Change Monitoring", "authors": "European Commission", "year": 2026, "title": "DMA Review Q&A", "venue": "European Commission", "source_type": "official institutional review", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://digital-markets-act.ec.europa.eu/about-dma/dma-review-qa_en", "doi": null, "claim_notes": "Official European Commission 2026 review Q&A inspected on 2026-07-11. It describes the Article 53 review scope, including core-platform services, Articles 5-7 obligations, enforcement, business-user and user effects, and potential modification. It reports early implementation changes and continuing concerns about enforcement, transparency, circumvention, and technical access. These are Commission review statements, not proof of coverage, compliance, causality, or a particular firm's commercial outcome.", "uses": [ { "entrySlug": "chapter-18-digital-business-models-and-platform-economics", "entryTitle": "Digital Business Models and Platform Economics", "excerpts": [ "The Commission's 2026 review Q&A describes the formal review scope and reports both early implementation changes and continuing stakeholder concerns about enforcement, transparency, circumvention, and technical access. Treat this as the Commission's dated review position, not proof of causality, compliance, coverage, or commercial benefit for a particular firm. [BB-C18-S19]" ] } ] }, { "source_id": "BB-C19-S01", "chapter_slugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "framework": "NIST Cybersecurity Framework", "authors": "National Institute of Standards and Technology", "year": 2024, "title": "The NIST Cybersecurity Framework (CSF) 2.0", "venue": "NIST CSWP 29", "source_type": "official framework", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.nist.gov/publications/nist-cybersecurity-framework-csf-20", "doi": "10.6028/NIST.CSWP.29", "claim_notes": "Supports governance and cybersecurity risk management functions. Chapter text should use the CSF 2.0 function set when updated fully. Verified 2026-07-05 against NIST publication page and DOI; corrected venue from generic NIST to NIST CSWP 29.", "uses": [ { "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "excerpts": [ "1. NIST Cybersecurity Framework 2.0 (Govern, Identify, Protect, Detect, Respond, Recover) [BB-C19-S01]", "8. Continuous Contextual Access Decisions (with CARTA clearly labeled as a proprietary Gartner concept) [BB-C19-S01]", "1. use all six concurrent NIST CSF 2.0 Functions and explain the central role of Govern; [BB-C19-S01]", "Current-evidence boundary. Threat reports, exploited-vulnerability catalogs, laws, regulator rules, product capabilities, incident facts, and loss estimates change. Record an as-of date and primary source for operational use, and recheck before publication. Every duration, star rating, score, cadence, cost, loss, confidence range, threshold, and case scenario in this chapter is an author planning assumption unless a claim-level source states otherwise. [BB-C19-S01] [BB-C19-S04] [BB-C19-S05] [BB-C19-S07] [BB-C19-S08]", "| NIST Framework | Holistic cyber program structure | Locally planned | Context-dependent | Core organizing framework [BB-C19-S01] |", "NIST CSF 2.0 is a voluntary, outcome-oriented framework for understanding, assessing, prioritizing, and communicating cybersecurity risk. It organizes outcomes under six concurrent Functions: Govern, Identify, Protect, Detect, Respond, and Recover . Govern establishes organizational context, risk strategy, roles, policy, oversight, and cybersecurity supply-chain risk management. CSF 2.0 does not prescribe a technology stack or by itself establish legal compliance or control effectiveness. [BB-C19-S01]", "Step-by-Step Process: Implementing the NIST Framework [BB-C19-S01]", "The six Functions are concurrent and should be connected through a Current Profile, Target Profile, and risk-informed improvement plan. [BB-C19-S01]", "Are our employees adequately trained to recognize and report cybersecurity threats? [BB-C19-S01]", "- Supply-chain cybersecurity: govern concentration, provenance, access, fourth parties, contractual rights, monitoring, incident coordination, continuity, and exit; a supplier relationship is not reducible to a “weakest link” slogan [BB-C19-S01].", "- Cyber Risk Quantification - Provides financial metrics for risk identified by NIST [BB-C19-S01].", "Constructed example: \"We estimate a local frequency range for this specific database breach scenario.\" The range, evidence, and calibration method must be documented before use. [BB-C19-S01]", "Presenting Single-Point Estimates: Using \"the breach will cost exactly $5M\" instead of a documented local range with explicit uncertainty and a defensible confidence method. [BB-C19-S01]", "- NIST Cybersecurity Framework - Quantifies risks identified in the \"Identify\" function [BB-C19-S01].", "Based on the ranking, identify the services, data, identities, capabilities, dependencies, and recovery paths whose compromise would create material impact; do not use a universal percentage. [BB-C19-S01]", "- NIST Cybersecurity Framework - Informs the \"Identify\" function's asset management [BB-C19-S01].", "The classic Cyber Defense Matrix is a practitioner taxonomy created by Sounil Yu. Its five-by-five form crosses the five pre-CSF-2.0 operational Functions—Identify, Protect, Detect, Respond, Recover—with Devices, Applications, Networks, Data, and Users. [BB-C19-S06] When used with CSF 2.0, explicitly add Govern as the organizational context, strategy, policy, roles, oversight, and supply-chain layer across the matrix. This is a labeled adaptation: it does not change the registered source model or establish that a control, spend level, or product reduces loss. [BB-C19-S01]", "Figure 19.1. Classic Cyber Defense Matrix with a CSF 2.0 Govern overlay. The five operational rows preserve the source taxonomy; Govern is added as an outer layer affecting every asset and operational Function. [BB-C19-S01] [BB-C19-S06]", "| Compliance Audits | Moderate (author aid) | Demonstrates alignment of controls to NIST functions. | [BB-C19-S01]", "1. Draw and version the matrix: preserve the classic five-by-five source grid and add a clearly labeled CSF 2.0 Govern overlay. Record the matrix and CSF versions rather than implying the classic grid is the complete current CSF. [BB-C19-S01] [BB-C19-S06]", "- NIST Cybersecurity Framework - Provides the row (function) dimension of the matrix [BB-C19-S01].", "Output: A risk assessment report for each critical vendor, identifying gaps and vulnerabilities. [BB-C19-S01]", "- NIST Cybersecurity Framework - Informs the \"Protect\" and \"Identify\" functions for third-party assets [BB-C19-S01].", "Balanced resilience: Prevention remains important, but no control strategy guarantees prevention; pair it with detection, response, recovery, and learning. [BB-C19-S01]", "- NIST Cybersecurity Framework - Focuses on strengthening the Detect, Respond, and Recover functions [BB-C19-S01].", "- NIST Cybersecurity Framework - Guides the \"Respond\" and \"Recover\" functions [BB-C19-S01].", "The continuous contextual access decision model uses identity, device, resource, request, behavior, and other signals to make least-privilege access decisions against a defined purpose and risk boundary. It anchors architecture to NIST Zero Trust; CARTA is a separate proprietary term, not synonymous with or the operationalization of NIST architecture. Signals and automation require privacy, bias, accessibility, availability, due-process, vendor, and governance controls. [BB-C19-S01]", "| Zero Trust Architecture | Context-dependent | Use NIST's architecture as the authoritative anchor; CARTA is a separate proprietary concept. [BB-C19-S01] |", "- NIST Cybersecurity Framework - contextual access can contribute to outcomes across all six Functions when governed appropriately [BB-C19-S01].", "The ransomware decision-making framework is a governance checklist for a scenario-specific business-continuity, safety, data, legal, and financial risk. It is not live incident advice. During an incident, activate the approved authority matrix; preserve privilege and evidence; assess safety, operations, exfiltration, recovery, materiality, and obligations; and involve counsel, forensics, insurer, law enforcement, sanctions review, regulators, and required executives or board roles as applicable. [BB-C19-S01] [BB-C19-S05]" ] } ] }, { "source_id": "BB-C19-S03", "chapter_slugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "framework": "FAIR Cyber Risk Quantification", "authors": "Freund, J.; Jones, J.", "year": 2015, "title": "Measuring and Managing Information Risk: A FAIR Approach", "venue": "Butterworth-Heinemann", "source_type": "business/technical book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.sciencedirect.com/book/monograph/9780124202313/measuring-and-managing-information-risk", "doi": null, "claim_notes": "Supports FAIR-style scenario analysis, frequency, loss magnitude, and annualized loss exposure. Does not support universal control ROI percentages. Verified 2026-07-05 against ScienceDirect/Elsevier monograph record; corrected year to publisher-listed 2015; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "excerpts": [ "| Cybersecurity Budgeting | High (author aid) | Supports scenario-specific investment decisions; it does not produce a universal ROI. [BB-C19-S03] |", "Estimate Reduction: Estimate how much the control could reduce likelihood or impact, and express the estimate as a range with assumptions. [BB-C19-S03]", "Example: If MFA costs $100k/year, model the expected reduction in annualized loss exposure as a range and compare the expected loss reduction to the annual control cost. [BB-C19-S03]" ] } ] }, { "source_id": "BB-C19-S04", "chapter_slugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "framework": "Breach Pattern Evidence", "authors": "Verizon", "year": 2023, "title": "2023 Data Breach Investigations Report", "venue": "Verizon", "source_type": "annual industry report", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.verizon.com/business/resources/reports/2023-data-breach-investigations-report-dbir.pdf", "doi": null, "claim_notes": "Named annual report for breach-pattern context. Exact percentages must be verified against the report before use. Verified 2026-07-05 against Verizon official 2023 DBIR PDF; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "excerpts": [ "Current-evidence boundary. Threat reports, exploited-vulnerability catalogs, laws, regulator rules, product capabilities, incident facts, and loss estimates change. Record an as-of date and primary source for operational use, and recheck before publication. Every duration, star rating, score, cadence, cost, loss, confidence range, threshold, and case scenario in this chapter is an author planning assumption unless a claim-level source states otherwise. [BB-C19-S01] [BB-C19-S04] [BB-C19-S05] [BB-C19-S07] [BB-C19-S08]", "The human-centered security culture model treats people as participants in a socio-technical security system, not a firewall or the “weakest link.” Secure defaults, least privilege, usable workflows, staffing and workload, accessible reporting, identity controls, detection, containment, recovery, and accountable management determine whether an error or malicious message becomes an incident. Role-based practice and safe reporting matter, but training must not transfer the control boundary from system owners to employees. [BB-C19-S01] [BB-C19-S04]", "Provide a clear, visible \"report phishing\" button in email clients. Reassure employees that there are no negative consequences for false alarms. [BB-C19-S04]" ] } ] }, { "source_id": "BB-C19-S05", "chapter_slugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "framework": "Cyber Threat Landscape", "authors": "European Union Agency for Cybersecurity", "year": 2024, "title": "ENISA Threat Landscape 2024", "venue": "ENISA", "source_type": "official annual report", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.enisa.europa.eu/publications/enisa-threat-landscape-2024", "doi": null, "claim_notes": "Named annual threat landscape source for ransomware, supply-chain, and threat-trend context. Exact rankings and statistics require claim-level verification. Verified 2026-07-05 against ENISA official publication page for Threat Landscape 2024; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "excerpts": [ "Current-evidence boundary. Threat reports, exploited-vulnerability catalogs, laws, regulator rules, product capabilities, incident facts, and loss estimates change. Record an as-of date and primary source for operational use, and recheck before publication. Every duration, star rating, score, cadence, cost, loss, confidence range, threshold, and case scenario in this chapter is an author planning assumption unless a claim-level source states otherwise. [BB-C19-S01] [BB-C19-S04] [BB-C19-S05] [BB-C19-S07] [BB-C19-S08]", "The ransomware decision-making framework is a governance checklist for a scenario-specific business-continuity, safety, data, legal, and financial risk. It is not live incident advice. During an incident, activate the approved authority matrix; preserve privilege and evidence; assess safety, operations, exfiltration, recovery, materiality, and obligations; and involve counsel, forensics, insurer, law enforcement, sanctions review, regulators, and required executives or board roles as applicable. [BB-C19-S01] [BB-C19-S05]" ] } ] }, { "source_id": "BB-C19-S06", "chapter_slugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "framework": "Cyber Defense Matrix", "authors": "Yu, Sounil", "year": 2016, "title": "The Cyber Defense Matrix", "venue": "Cyber Defense Matrix", "source_type": "author-maintained practitioner framework", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-09", "url": "https://cyberdefensematrix.com/", "doi": null, "claim_notes": "Supports a five-by-five taxonomy crossing the five NIST functions with Devices, Applications, Networks, Data, and Users, plus portfolio-gap discussion. The 2016 origin is corroborated by the official RSAC 2019 record at https://www.rsaconference.com/Library/presentation/USA/2019/cyber-defense-matrix-reloaded-3-3-4. It does not establish control efficacy, loss reduction, product selection, or ROI. Rechecked 2026-07-09 under the cybersecurity current-information rule.", "uses": [ { "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "excerpts": [ "The classic Cyber Defense Matrix is a practitioner taxonomy created by Sounil Yu. Its five-by-five form crosses the five pre-CSF-2.0 operational Functions—Identify, Protect, Detect, Respond, Recover—with Devices, Applications, Networks, Data, and Users. [BB-C19-S06] When used with CSF 2.0, explicitly add Govern as the organizational context, strategy, policy, roles, oversight, and supply-chain layer across the matrix. This is a labeled adaptation: it does not change the registered source model or establish that a control, spend level, or product reduces loss. [BB-C19-S01]", "Figure 19.1. Classic Cyber Defense Matrix with a CSF 2.0 Govern overlay. The five operational rows preserve the source taxonomy; Govern is added as an outer layer affecting every asset and operational Function. [BB-C19-S01] [BB-C19-S06]", "1. Draw and version the matrix: preserve the classic five-by-five source grid and add a clearly labeled CSF 2.0 Govern overlay. Record the matrix and CSF versions rather than implying the classic grid is the complete current CSF. [BB-C19-S01] [BB-C19-S06]" ] } ] }, { "source_id": "BB-C19-S07", "chapter_slugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "framework": "Known Exploited Vulnerabilities", "authors": "Cybersecurity and Infrastructure Security Agency", "year": 2024, "title": "Known Exploited Vulnerabilities Catalog", "venue": "CISA", "source_type": "official dataset", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog", "doi": null, "claim_notes": "Supports prioritizing known-exploited vulnerabilities and patch accountability. Current catalog entries drift and should not be hard-coded. Verified 2026-07-05 against CISA official Known Exploited Vulnerabilities Catalog; no DOI applies and catalog contents drift over time.", "uses": [ { "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "excerpts": [ "Current-evidence boundary. Threat reports, exploited-vulnerability catalogs, laws, regulator rules, product capabilities, incident facts, and loss estimates change. Record an as-of date and primary source for operational use, and recheck before publication. Every duration, star rating, score, cadence, cost, loss, confidence range, threshold, and case scenario in this chapter is an author planning assumption unless a claim-level source states otherwise. [BB-C19-S01] [BB-C19-S04] [BB-C19-S05] [BB-C19-S07] [BB-C19-S08]" ] } ] }, { "source_id": "BB-C19-S08", "chapter_slugs": [ "chapter-19-cybersecurity-and-risk-management-for-managers" ], "framework": "Breach Cost Inputs", "authors": "IBM; Ponemon Institute", "year": 2025, "title": "Cost of a Data Breach Report 2025", "venue": "IBM", "source_type": "annual industry report", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-09", "url": "https://www.ibm.com/reports/data-breach", "doi": null, "claim_notes": "Supports contextual external cost inputs for a scenario-based breach estimate. IBM identifies it as global research with Ponemon Institute; report-level averages are not company-specific loss, control-effect, or universal ROI estimates. Rechecked 2026-07-09; recheck before 2027-07-09 and before public posting under the cybersecurity current-information rule.", "uses": [ { "entrySlug": "chapter-19-cybersecurity-and-risk-management-for-managers", "entryTitle": "Cybersecurity and Risk Management for Managers", "excerpts": [ "Current-evidence boundary. Threat reports, exploited-vulnerability catalogs, laws, regulator rules, product capabilities, incident facts, and loss estimates change. Record an as-of date and primary source for operational use, and recheck before publication. Every duration, star rating, score, cadence, cost, loss, confidence range, threshold, and case scenario in this chapter is an author planning assumption unless a claim-level source states otherwise. [BB-C19-S01] [BB-C19-S04] [BB-C19-S05] [BB-C19-S07] [BB-C19-S08]", "Data Sources: Use internal incident and cost data, legal counsel estimates, insurance inputs, and named annual breach reports as contextual external inputs. IBM's 2025 report is a global study; its averages are not a company-specific loss estimate. [BB-C19-S08]", "Lack of Historical Data: Do not rely purely on intuition. Treat industry figures as contextual ranges, then calibrate them with organization- and scenario-specific inputs. [BB-C19-S08]" ] } ] }, { "source_id": "BB-C02-S01", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Business Judgment Rule", "authors": "Supreme Court of Delaware", "year": 1985, "title": "Smith v. Van Gorkom, 488 A.2d 858", "venue": "Delaware Supreme Court", "source_type": "case law", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Canonical Delaware duty-of-care case supporting the bounded discussion of an inadequately informed board sale process. It is not used as a complete statement of the business-judgment rule or as a promise of director or officer protection. Opinion and citation rechecked 2026-07-10.", "url": "https://law.justia.com/cases/delaware/supreme-court/1985/488-a-2d-858-4.html", "doi": null, "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C02-S02", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Agency Theory", "authors": "Jensen, M. C.; Meckling, W. H.", "year": 1976, "title": "Theory of the Firm: Managerial Behavior, Agency Costs and Ownership Structure", "venue": "Journal of Financial Economics", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Foundational source for agency-cost framing and incentive alignment. Does not by itself support precise executive-compensation mix percentages. Verified on 2026-07-05 against ScienceDirect; DOI and bibliographic fields match Jensen and Meckling, 1976, Journal of Financial Economics.", "url": "https://www.sciencedirect.com/science/article/pii/0304405X7690026X", "doi": "10.1016/0304-405X(76)90026-X", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C02-S03", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Executive Compensation", "authors": "Bebchuk, L. A.; Fried, J. M.", "year": 2003, "title": "Executive Compensation as an Agency Problem", "venue": "Journal of Economic Perspectives, 17(3), 71-92", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Full NBER working-paper text and the final American Economic Association article record were inspected. The authors analyze compensation both as a potential response to agency problems and as a possible product of managerial influence, including weak or perverse incentives. The source does not establish one universally optimal compensation mix.", "url": "https://www.nber.org/system/files/working_papers/w9813/w9813.pdf", "doi": "10.1257/089533003769204362", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C02-S04", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Stakeholder Governance", "authors": "Business Roundtable", "year": 2019, "title": "Statement on the Purpose of a Corporation", "venue": "Business Roundtable", "source_type": "industry statement", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Canonical practitioner statement for stakeholder-oriented corporate-purpose framing. Not evidence for performance outperformance by itself. Verified on 2026-07-05 against Business Roundtable official release; citation matches the 2019 Statement on the Purpose of a Corporation.", "url": "https://www.businessroundtable.org/business-roundtable-redefines-the-purpose-of-a-corporation-to-promote-an-economy-that-serves-all-americans", "doi": null, "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C02-S05", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Stakeholder Performance Evidence", "authors": "Edmans, A.", "year": 2011, "title": "Does the Stock Market Fully Value Intangibles? Employee Satisfaction and Equity Prices", "venue": "Journal of Financial Economics", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Supports evidence-oriented discussion of employee satisfaction and long-run equity performance. Check exact window and return estimates before using hard numbers. Verified on 2026-07-05 against ScienceDirect; DOI and bibliographic fields match Edmans, 2011, Journal of Financial Economics.", "url": "https://www.sciencedirect.com/science/article/abs/pii/S0304405X11000869", "doi": "10.1016/j.jfineco.2011.03.021", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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]", "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." ] } ] }, { "source_id": "BB-C02-S06", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Data Privacy and GDPR", "authors": "European Parliament and Council", "year": 2016, "title": "Regulation (EU) 2016/679 (General Data Protection Regulation)", "venue": "Official Journal of the European Union", "source_type": "official regulation", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Primary legal source inspected at Articles 3, 5, 6, 12-14, 25, 28, 30, 32-34, 37, 44-49, and 83 for Chapter 2's bounded scope, principles, lawful bases, notice, design, vendor, records, risk-based security, breach, DPO, transfer, and fine-ceiling statements. Official EUR-Lex text rechecked 2026-07-10; current counsel must still determine application to specific facts.", "url": "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng", "doi": null, "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "- 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]", "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]", "- 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]", "- [ ] Document what personal data you collect (name, email, location, behavior, etc.). [BB-C02-S06]", "- [ ] 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]", "- [ ] Apply the age and parental-consent rules in the applicable jurisdiction. [BB-C02-S06]", "- [ ] 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]", "- [ ] 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]", "- [ ] 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]", "- [ ] 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]", "- [ ] 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]", "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]", "- Privacy requirements should be built into design rather than treated as an after-the-fact task [BB-C02-S06]" ] } ] }, { "source_id": "BB-C02-S07", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Patent Application Publication", "authors": "United States Patent and Trademark Office", "year": 2022, "title": "MPEP Section 1120: Eighteen-Month Publication of Patent Applications", "venue": "Manual of Patent Examining Procedure", "source_type": "official guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Official USPTO guidance inspected for the qualified statement that most U.S. nonprovisional utility and plant applications are published after 18 months from the earliest claimed filing date, subject to statutory exceptions and nonpublication rules. It does not support claims about grant timing, obsolescence, or commercial strategy.", "url": "https://www.uspto.gov/web/offices/pac/mpep/s1120.html", "doi": null, "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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].", "Source note: Author-created routing synthesis. [BB-C02-S07] supports only the later patent-publication timing statement.", "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." ] } ] }, { "source_id": "BB-C02-S08", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "AI Risk Management Framework", "authors": "Tabassi, E.", "year": 2023, "title": "Artificial Intelligence Risk Management Framework (AI RMF 1.0)", "venue": "National Institute of Standards and Technology", "source_type": "official framework", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Official NIST publication inspected for the voluntary, rights-preserving, non-sector-specific, use-case-agnostic framework and Govern-Map-Measure-Manage functions. NIST states that AI RMF 1.0 is being revised; the source does not create legal compliance or universal numeric thresholds.", "url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10", "doi": "10.6028/NIST.AI.100-1", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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.", "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]", "- 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]", "- 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]", "- 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]", "- 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]", "- 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]", "- 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]", "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]", "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.", "- 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]" ] } ] }, { "source_id": "BB-C02-S09", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "European Union Artificial Intelligence Act", "authors": "European Parliament and Council", "year": 2024, "title": "Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence", "venue": "Official Journal of the European Union", "source_type": "official regulation", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Official EUR-Lex record inspected for the enacted regulation's identity and risk-based legal structure. Chapter 2 explicitly reserves role, scope, category, exclusion, and phased-application analysis for current counsel and does not treat its illustrative matrix as an EU AI Act classification.", "url": "https://eur-lex.europa.eu/eli/reg/2024/1689/oj?locale=en", "doi": null, "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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.", "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]", "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]", "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.", "- 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]" ] } ] }, { "source_id": "BB-C02-S10", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Applied AI Governance Enforcement Case", "authors": "United States Federal Trade Commission", "year": 2023, "title": "Rite Aid Banned from Using AI Facial Recognition After FTC Says Retailer Deployed Technology without Reasonable Safeguards", "venue": "Federal Trade Commission", "source_type": "official regulator release and proposed order", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "FTC release and linked proposed stipulated order inspected for the attributed allegations, proposed five-year prohibition, safeguards, and then-pending court and bankruptcy approvals. Chapter 2 distinguishes allegations and proposal status from adjudicated findings.", "url": "https://search.ftc.gov/news-events/news/press-releases/2023/12/rite-aid-banned-using-ai-facial-recognition-after-ftc-says-retailer-deployed-technology-without", "doi": null, "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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." ] } ] }, { "source_id": "BB-C02-S11", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Behavioral Ethics in Organizations", "authors": "Treviño, L. K.; Weaver, G. R.; Reynolds, S. J.", "year": 2006, "title": "Behavioral Ethics in Organizations: A Review", "venue": "Journal of Management", "source_type": "peer-reviewed review article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Peer-reviewed review inspected for the existence of individual, group, and organizational influences on ethical behavior and limits in the evidence base. Supports Chapter 2's use of a multi-lens, documented deliberation process; it does not prove that the original four-step synthesis yields an ethically correct decision or performance outcome.", "url": "https://journals.sagepub.com/doi/10.1177/0149206306294258", "doi": "10.1177/0149206306294258", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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]", "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]", "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]", "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.", "- Ethical processes can clarify expectations, conflicts, escalation, dissent, and accountability, but they do not mechanically produce one correct answer. [BB-C02-S11]" ] } ] }, { "source_id": "BB-C04-S02", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Leveraged Buyouts", "authors": "Kaplan, S. N.; Strömberg, P.", "year": 2009, "title": "Leveraged Buyouts and Private Equity", "venue": "Journal of Economic Perspectives", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.aeaweb.org/articles?id=10.1257%2Fjep.23.1.121", "doi": "10.1257/jep.23.1.121", "claim_notes": "Supports LBO value-creation mechanisms and private-equity return framing. Exact benchmarks require claim-level verification. Verified on 2026-07-05 against AEA record; DOI and bibliographic fields match Kaplan and Stromberg, 2009, Journal of Economic Perspectives.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C04-S03", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Leveraged Buyouts", "authors": "Axelson, U.; Jenkinson, T.; Strömberg, P.; Weisbach, M. S.", "year": 2013, "title": "Borrow Cheap, Buy High? The Determinants of Leverage and Pricing in Buyouts", "venue": "Journal of Finance", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://onlinelibrary.wiley.com/doi/abs/10.1111/jofi.12082", "doi": "10.1111/jofi.12082", "claim_notes": "Supports the claim that buyout leverage and pricing vary with credit-market conditions. Exact sample and return figures require verification. Verified on 2026-07-05 against Wiley Journal of Finance record; DOI and bibliographic fields match.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C04-S04", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Financial Ratio Analysis", "authors": "Lev, B.; Thiagarajan, S. R.", "year": 1993, "title": "Fundamental Information Analysis", "venue": "Journal of Accounting Research", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://ideas.repec.org/a/bla/joares/v31y1993i2p190-215.html", "doi": "10.2307/2491270", "claim_notes": "Supports use of fundamental financial signals in earnings analysis. Does not support universal excess-return claims without inspection. Verified on 2026-07-05 against RePEc/JAR DOI-indexed record; citation matches Lev and Thiagarajan, 1993.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C04-S05", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Financial Ratio Analysis", "authors": "Piotroski, J. D.", "year": 2000, "title": "Value Investing: The Use of Historical Financial Statement Information to Separate Winners from Losers", "venue": "Journal of Accounting Research", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.jstor.org/stable/2672906", "doi": "10.2307/2672906", "claim_notes": "Supports F-Score-style systematic financial-statement analysis within value stocks. Exact return statistics require verification. Verified on 2026-07-05 against JSTOR/RePEc records; DOI and citation match Piotroski, 2000, Journal of Accounting Research.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C04-S06", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "DuPont Analysis", "authors": "Soliman, M. T.", "year": 2008, "title": "The Use of DuPont Analysis by Market Participants", "venue": "The Accounting Review", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://openurl.ebsco.com/c/zag3po/openurl?date=20080501&doi=10.2308%2Faccr.2008.83.3.823&epage=853&genre=article&issn=0001-4826&issue=3&prompt=true&sid=Primo&spage=823&title=The+accounting+review.&volume=83", "doi": "10.2308/accr.2008.83.3.823", "claim_notes": "Supports decomposing ROE into margin, turnover, and leverage components for performance interpretation. Verified on 2026-07-05 against EBSCO/Accounting Review metadata; DOI and citation match Soliman, 2008.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]", "Source note: Original redraw of the three-step DuPont identity; empirical interpretation is bounded by the active DuPont source record. [BB-C04-S06]" ] } ] }, { "source_id": "BB-C04-S07", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Working Capital Management", "authors": "Deloof, M.", "year": 2003, "title": "Does Working Capital Management Affect Profitability of Belgian Firms?", "venue": "Journal of Business Finance & Accounting, 30(3-4), 573-588", "source_type": "peer-reviewed article; author manuscript", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://medialibrary.uantwerpen.be/oldcontent/container1244/files/TEW%20-%20Onderzoek/Working%20Papers/RPS/2001/RPS-2001-027.pdf", "doi": "10.1111/1468-5957.00008", "claim_notes": "Full University of Antwerp author manuscript for the published article was inspected. It defines the cash conversion cycle as receivables days plus inventory days minus payables days and analyzes 5,045 firm-year observations for 1,009 large Belgian non-financial firms from 1992-1996. Reported relationships are observational and differ across measures and specifications; the paper also discusses benefits and costs of inventory, trade credit, and delayed payment. It does not establish a universal causal instruction to minimize the cycle.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]", "Source note: Original timeline based on the cash-conversion-cycle relationship; the adjacent evidence supports association, not a universal causal instruction. [BB-C04-S07]" ] } ] }, { "source_id": "BB-C04-S08", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Cap Table and Venture Governance", "authors": "Sahlman, W. A.", "year": 1990, "title": "The Structure and Governance of Venture-Capital Organizations", "venue": "Journal of Financial Economics", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.sciencedirect.com/science/article/pii/0304405X90900658", "doi": "10.1016/0304-405X(90)90065-8", "claim_notes": "Supports staged venture financing, governance, and incentive alignment. Does not support universal founder-ownership thresholds without inspection. Verified on 2026-07-05 against ScienceDirect; DOI and bibliographic fields match Sahlman, 1990, Journal of Financial Economics.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C04-S09", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Customer Lifetime Value", "authors": "Gupta, S.; Lehmann, D. R.; Stuart, J. A.", "year": 2004, "title": "Valuing Customers", "venue": "Journal of Marketing Research", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://journals.sagepub.com/doi/10.1509/jmkr.41.1.7.25084", "doi": "10.1509/jmkr.41.1.7.25084", "claim_notes": "Supports customer lifetime value as a management and valuation lens. Exact profitability comparisons require verification. Verified on 2026-07-05 against Sage Journal of Marketing Research record; DOI and bibliographic fields match.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C04-S10", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Real Options and Investment Under Uncertainty", "authors": "Dixit, A. K.; Pindyck, R. S.", "year": 1994, "title": "Investment Under Uncertainty", "venue": "Princeton University Press", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.jstor.org/stable/j.ctt7sncv", "doi": "10.1515/9781400830176", "claim_notes": "Supports option value of waiting and investment flexibility under uncertainty. Verified on 2026-07-05 against JSTOR and DOI-indexed book records; citation matches Dixit and Pindyck, Princeton University Press, 1994.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C04-S11", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "WeWork Valuation Failure", "authors": "The We Company", "year": 2019, "title": "Form S-1 Registration Statement", "venue": "U.S. Securities and Exchange Commission", "source_type": "regulatory filing", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.sec.gov/Archives/edgar/data/1533523/000119312519220499/d781982ds1.htm", "doi": null, "claim_notes": "Supports public-filing evidence of WeWork losses, lease obligations, and business-model risk. Private valuation figure needs independent confirmation. Verified on 2026-07-05 against the SEC EDGAR Form S-1 filing for The We Company, 2019.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C04-S12", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Financial Crisis Valuation Failure", "authors": "Financial Crisis Inquiry Commission", "year": 2011, "title": "The Financial Crisis Inquiry Report", "venue": "U.S. Government Printing Office", "source_type": "government report", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.govinfo.gov/app/details/GPO-FCIC", "doi": null, "claim_notes": "Supports mortgage-asset valuation and systemic risk context for the 2008 financial crisis. Verified on 2026-07-05 against GovInfo official record; citation matches The Financial Crisis Inquiry Report, 2011.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C05-S02", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Net Promoter Score", "authors": "Reichheld, F. F.", "year": 2003, "title": "The One Number You Need to Grow", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Original practitioner article for NPS framing. Should be paired with critical empirical sources for predictive-validity claims. Verified on 2026-07-05 against HBR article page; citation matches Reichheld, 2003, Harvard Business Review.", "url": "https://hbr.org/2003/12/the-one-number-you-need-to-grow", "doi": null, "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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.", "- 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]" ] } ] }, { "source_id": "BB-C05-S03", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "NPS Predictive Validity", "authors": "Keiningham, T. L.; Cooil, B.; Andreassen, T. W.; Aksoy, L.", "year": 2007, "title": "A Longitudinal Examination of Net Promoter and Firm Revenue Growth", "venue": "Journal of Marketing", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Full article inspected. In longitudinal firm/industry analyses, the authors did not replicate NPS's claimed clear superiority or status as the single most reliable indicator of firm revenue growth. The article does not test cohort analysis or individual future behavior; manuscript uses were narrowed accordingly.", "url": "https://journals.sagepub.com/doi/10.1509/jmkg.71.3.039", "doi": "10.1509/jmkg.71.3.039", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "- 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]" ] } ] }, { "source_id": "BB-C05-S04", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Customer-Centricity", "authors": "Fader, P.", "year": 2012, "title": "Customer Centricity: Focus on the Right Customers for Strategic Advantage", "venue": "Wharton Digital Press", "source_type": "academic/practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Official Wharton Chapter 4 excerpt inspected. Supports CLV as the present value of expected customer net cash flows, customer heterogeneity, and explicit limits of homogeneous point estimates. Does not validate a CLV/CAC threshold or identify a company’s principal constraint; manuscript uses were narrowed accordingly.", "url": "https://executiveeducation.wharton.upenn.edu/wp-content/uploads/2019/01/Customer-Centricity-Excerpt-2019.pdf", "doi": null, "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C06-S01", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Toyota Production System and Lean", "authors": "Ohno, T.", "year": 1988, "title": "Toyota Production System: Beyond Large-Scale Production", "venue": "Productivity Press", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.routledge.com/Toyota-Production-System-Beyond-Large-Scale-Production/Ohno/p/book/9780915299140", "doi": null, "claim_notes": "Canonical source for Toyota Production System principles, just-in-time, and waste elimination. Exact operational benchmarks require verification. Verified on 2026-07-05 against Routledge/Productivity Press book page; citation matches Ohno, English edition, 1988.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C06-S02", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Lean Thinking", "authors": "Womack, J. P.", "year": 2006, "title": "Lean Thinking: A Look Back and a Look Forward", "venue": "Lean Enterprise Institute", "source_type": "author retrospective practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.lean.org/the-lean-post/articles/lean-thinking-a-look-back-and-a-look-forward/", "doi": null, "claim_notes": "Full first-person retrospective by James Womack on the Lean Enterprise Institute site was inspected. It traces the production-system lineage through Ford and Toyota and states the five principles of customer value, value stream, flow, pull, and perfection. The prior Wiremold case claim was retired because the cited book was not available for page-level inspection; this replacement does not support Wiremold metrics or universal performance effects.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C06-S03", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Theory of Constraints", "authors": "Goldratt, E. M.; Cox, J.", "year": 2004, "title": "The Goal: A Process of Ongoing Improvement", "venue": "North River Press", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://northriverpress.com/the-goal-a-process-of-ongoing-improvement/", "doi": null, "claim_notes": "Canonical source for Theory of Constraints operating logic and focusing attention on the system constraint. Verified on 2026-07-05 against North River Press and Google Books records; citation matches The Goal revised edition lineage.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "- 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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C06-S04", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Theory of Constraints", "authors": "Goldratt, E. M.", "year": 1990, "title": "What is this Thing Called Theory of Constraints and how Should it be Implemented?", "venue": "North River Press", "source_type": "book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://books.google.com/books/about/What_is_this_Thing_Called_Theory_of_Cons.html?id=FA8KAQAAMAAJ", "doi": null, "claim_notes": "Supports the conceptual claim that non-constraint optimization does not necessarily raise system throughput. Corrected on 2026-07-05: web verification did not support a 1990 Journal of Cost Management article titled Theory of Constraints; replaced with Goldratt's real 1990 North River Press book.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "- 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]", "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]", "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]", "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]", "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]", "- 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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C06-S05", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Lean Healthcare", "authors": "Kenney, C.", "year": 2011, "title": "Transforming Health Care: Virginia Mason Medical Center's Pursuit of the Perfect Patient Experience", "venue": "Productivity Press", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.routledge.com/Transforming-Health-Care-Virginia-Mason-Medical-Centers-Pursuit-of-the-Perfect-Patient-Experience/Kenney/p/book/9781563273759", "doi": "10.1201/b10359", "claim_notes": "Official publisher preview inspected. The book states that Virginia Mason based its production system on Toyota's, adapted the approach to health care, and treated it as an evolving continuous-improvement journey. Supports practice context only; exact safety, waiting-time, satisfaction, savings, and outcome effects require separate primary and study-design evidence.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C06-S06", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Six Sigma", "authors": "Pande, P. S.; Neuman, R. P.; Cavanagh, R. R.", "year": 2000, "title": "The Six Sigma Way", "venue": "McGraw-Hill", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.mheducation.com/highered/mhp/product/six-sigma-way-how-ge-motorola-other-top-companies-honing-their-performance.html", "doi": null, "claim_notes": "Supports common Six Sigma performance target and DMAIC management framing. Exact Motorola and GE savings require separate verification. Verified on 2026-07-05 against McGraw Hill product page; citation matches Pande, Neuman, and Cavanagh, 2000.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C06-S07", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Capacity Planning and Queueing", "authors": "Hopp, W. J.; Spearman, M. L.", "year": 2008, "title": "Factory Physics", "venue": "Waveland Press", "source_type": "academic/practitioner book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.waveland.com/browse.php?t=587", "doi": null, "claim_notes": "Supports queueing-based warning that high utilization increases waiting time and reduces operational buffer. Verified on 2026-07-05 against Waveland Press product page; citation matches Hopp and Spearman, Factory Physics, 2008.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]", "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]", "Queueing logic warns against planning at full utilization because variability causes waiting time to rise sharply as utilization approaches full load. [BB-C06-S07]" ] } ] }, { "source_id": "BB-C06-S08", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Capacity Expansion", "authors": "Luss, H.", "year": 1982, "title": "Operations Research and Capacity Expansion Problems: A Survey", "venue": "Operations Research", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://pubsonline.informs.org/toc/opre/30/5", "doi": "10.1287/opre.30.5.907", "claim_notes": "Supports capacity expansion planning literature. Exact strategy examples require separate verification. Verified on 2026-07-05 against INFORMS Operations Research issue page; DOI and bibliographic fields match Luss, 1982.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C06-S09", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Statistical Process Control", "authors": "Montgomery, D. C.", "year": 2009, "title": "Introduction to Statistical Quality Control", "venue": "John Wiley & Sons", "source_type": "textbook", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.amazon.com/Introduction-Statistical-Quality-Control-Montgomery/dp/0470169923", "doi": null, "claim_notes": "Supports statistical-process-control limits and interpretation. Exact normal-distribution explanations should be verified against the text. Verified on 2026-07-05 against book records for the 6th edition; citation matches Montgomery, Wiley, 2009.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "- 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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C06-S10", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Value Stream Mapping", "authors": "Rother, Mike; Shook, John", "year": 2018, "title": "Learning to See", "venue": "Lean Enterprise Institute", "source_type": "practitioner guide", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-09", "url": "https://www.lean.org/store/book/learning-to-see/", "doi": null, "claim_notes": "Supports value-stream mapping as a representation of material and information flow, including value-creating and non-value-creating activity, and as a tool for current-state, future-state, and implementation planning. It does not support generic percentage-savings claims. Verified on 2026-07-09 against the Lean Enterprise Institute's official workbook record.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]", "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]", "- 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]", "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]", "- 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]" ] } ] }, { "source_id": "BB-C07-S01", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Change Management", "authors": "Kotter, J. P.", "year": 1995, "title": "Leading Change: Why Transformation Efforts Fail", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Canonical source for Kotter's change-management framing. Treat the common 70 percent failure claim as needing exact inspection before restoration. Verified on 2026-07-05 against HBR article page; citation matches Kotter, 1995, Harvard Business Review.", "url": "https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2", "doi": null, "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]", "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]", "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]", "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]", "Source note: Original redraw of Kotter's practitioner sequence with an explicit iterative-review edge. [BB-C07-S01]" ] } ] }, { "source_id": "BB-C07-S02", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Emotional Intelligence and Leadership", "authors": "Goleman, D.", "year": 2000, "title": "Leadership That Gets Results", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Official HBR article and product records confirm Goleman's six styles and situational use of a leadership-style repertoire. Supports the taxonomy and adaptive-use framing; does not support the chapter's separate Radical Candor material or universal performance effects.", "url": "https://hbr.org/2000/03/leadership-that-gets-results", "doi": null, "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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." ] } ] }, { "source_id": "BB-C07-S03", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Motivation Theory", "authors": "Herzberg, F.", "year": 1968, "title": "One More Time: How Do You Motivate Employees?", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Canonical article for hygiene factors and motivators. Pair with original empirical work if moving motivation claims to vetted status. Verified on 2026-07-05 against HBR reprint page and secondary records for the original 1968 article.", "url": "https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees", "doi": null, "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C07-S04", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Psychological Safety", "authors": "Edmondson, A. C.", "year": 1999, "title": "Psychological Safety and Learning Behavior in Work Teams", "venue": "Administrative Science Quarterly", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Full article inspected. Supports Edmondson's definition, the 51-team study in one manufacturing company, association with learning behavior, and the seven-item team psychological-safety scale. Unsupported Lencioni, broad innovation/change, and intervention-marker uses were removed or narrowed.", "url": "https://journals.sagepub.com/doi/10.2307/2666999", "doi": "10.2307/2666999", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]", "- 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].", "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]" ] } ] }, { "source_id": "BB-C07-S05", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Cognitive Bias and Judgment", "authors": "Kahneman, D.", "year": 2011, "title": "Thinking, Fast and Slow", "venue": "Farrar, Straus and Giroux", "source_type": "academic/practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Official Macmillan book page and excerpt inspected. Supports the bounded claim that judgment is vulnerable to systematic error, including availability and halo effects. It does not validate the 9-box grid, diagnose an individual employee, or establish any employment outcome; broader anchoring, similarity, and confirmation-bias wording was removed from the cited lines.", "url": "https://us.macmillan.com/books/9780374533557/thinkingfastandslow/", "doi": null, "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C07-S06", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Group Development", "authors": "Tuckman, B. W.", "year": 1965, "title": "Developmental Sequence in Small Groups", "venue": "Psychological Bulletin", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Full 1965 review inspected. It reviews 50 articles and proposes forming, storming, norming, and performing while explicitly noting imperfect fit and setting-dependent variation. Supports the manuscript’s bounded team-development lens, not fixed universal stages or performance claims.", "url": "https://pubmed.ncbi.nlm.nih.gov/14314073/", "doi": "10.1037/h0022100", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "- Team-development stages are hypotheses that vary by setting; the group-development literature does not establish fixed stages or performance effects [BB-C07-S06]." ] } ] }, { "source_id": "BB-C08-S01", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "OKRs", "authors": "Doerr, J.", "year": 2018, "title": "Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs", "venue": "Portfolio/Penguin", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Publisher record, limited preview, official author material, and a direct Doerr interview support Intel-to-Google OKR history, Objective/Key Result structure, committed versus stretch practice, Google's early adoption, and the Chrome adoption-oriented Key Result. Cadence, scoring, alignment, and incentive treatment remain practitioner conventions, not validated universal thresholds.", "url": "https://www.penguinrandomhouse.com/books/546304/measure-what-matters-by-john-doerr-foreword-by-larry-page/", "doi": null, "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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.", "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]", "Doerr describes Google's early use of OKRs and uses a browser example to illustrate an adoption-oriented Key Result. [BB-C08-S01]" ] } ] }, { "source_id": "BB-C08-S03", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "Balanced Scorecard", "authors": "Kaplan, R. S.; Norton, D. P.", "year": 1992, "title": "The Balanced Scorecard: Measures That Drive Performance", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Original HBR article for Balanced Scorecard perspectives and performance-measurement framing. Verified on 2026-07-05 against HBR and HBS records; citation matches Kaplan and Norton, 1992, Harvard Business Review.", "url": "https://hbr.org/1992/01/the-balanced-scorecard-measures-that-drive-performance-2", "doi": null, "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "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]", "Figure 8.3. Balanced Scorecard strategy hypotheses. The arrows are relationships to test, not established causal chains or guaranteed financial outcomes. [BB-C08-S03]", "Source note: Original redraw of the four Balanced Scorecard perspectives; strategy-map arrows are hypotheses. [BB-C08-S03]", "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]", "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]" ] } ] }, { "source_id": "BB-C08-S04", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "Vision and Mission", "authors": "Collins, J. C.; Porras, J. I.", "year": 1996, "title": "Building Your Company's Vision", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Canonical source for core ideology, envisioned future, mission, and values framing. Verified on 2026-07-05 against HBR article page; citation matches Collins and Porras, 1996, Harvard Business Review.", "url": "https://hbr.org/1996/09/building-your-companys-vision", "doi": null, "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C08-S05", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "Good Strategy", "authors": "Rumelt, R.", "year": 2011, "title": "Good Strategy Bad Strategy: The Difference and Why It Matters", "venue": "Crown Business", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "claim_notes": "Publisher-authorized sample inspected. Rumelt explicitly defines the strategy kernel as diagnosis, guiding policy, and coherent action; coherent actions include coordinated policies, resource commitments, and actions carrying out the policy. Supports distinguishing strategy from aspiration lists, not one universal process or outcome effect.", "url": "https://www.penguinrandomhouse.com/books/208668/good-strategy-bad-strategy-by-richard-rumelt/", "doi": null, "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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." ] } ] }, { "source_id": "BB-C08-S06", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "Incentives and Metrics", "authors": "Kerr, S.", "year": 1995, "title": "On the Folly of Rewarding A, While Hoping for B", "venue": "Academy of Management Executive", "source_type": "peer-reviewed/practitioner article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "claim_notes": "Classic source for misaligned rewards and metric dysfunction. Does not support GE-specific historical claims without additional source inspection. Verified on 2026-07-05 against Academy of Management journal record; DOI and citation match Kerr, 1995, Academy of Management Executive.", "url": "https://journals.aom.org/doi/abs/10.5465/255378", "doi": "10.5465/255378", "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "The following composite teaching scenario illustrates the risk Kerr identifies when rewards and desired outcomes are misaligned. [BB-C08-S06]", "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]" ] } ] }, { "source_id": "BB-C08-S07", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "SMART Goals", "authors": "Farnsworth, D.; Clark, J. L.; Cothran, H.; Wysocki, A.", "year": 2019, "title": "Developing SMART Goals for Your Organization", "venue": "University of Florida IFAS Extension", "source_type": "official academic extension publication", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://ask.ifas.ufl.edu/publication/FE577/pdf", "doi": null, "claim_notes": "Inspected the official UF/IFAS PDF, revised July 2019 and reviewed January 2024. It presents Specific, Measurable, Attainable, Relevant, and Time-bound and attributes SMART to Doran's 1981 Management Review article while noting that wording has evolved. Doran's original article was not directly inspected; the chapter therefore describes this as UF/IFAS's attribution and uses Achievable as a common variant, not as the uniquely canonical wording.", "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "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." ] } ] }, { "source_id": "BB-C08-S08", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "FAST Goals", "authors": "Sull, D.; Sull, C.", "year": 2018, "title": "With Goals, FAST Beats SMART", "venue": "MIT Sloan Management Review", "source_type": "official practitioner article summary", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://shop.sloanreview.mit.edu/store/with-goals-fast-beats-smart", "doi": null, "claim_notes": "Inspected the official MIT Sloan Management Review storefront. The exposed summary directly defines FAST as embedded in Frequent discussions, Ambitious in scope, measured by Specific metrics, and Transparent. The paid article was not accessed; the chapter cites only this exposed definition and treats cadence, safeguards, and disclosure constraints as author additions.", "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "dynamic environments; Sull and Sull define it as Frequent discussions, Ambitious scope, Specific metrics, and Transparency. [BB-C08-S08]" ] } ] }, { "source_id": "BB-C08-S09", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "Goal-Setting Theory", "authors": "Locke, E. A.; Latham, G. P.", "year": 2002, "title": "Building a Practically Useful Theory of Goal Setting and Task Motivation: A 35-Year Odyssey", "venue": "American Psychologist", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://pubmed.ncbi.nlm.nih.gov/12237980/", "doi": "10.1037/0003-066X.57.9.705", "claim_notes": "Inspected the PubMed record and abstract. It is a 35-year empirical synthesis covering core findings, mechanisms, moderators, incentive mediation, practical significance, and limitations of goal-setting theory. The chapter uses it to reject a universal mnemonic-only account, not to claim that any SMART or FAST implementation improves performance.", "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "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." ] } ] }, { "source_id": "BB-C08-S10", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "Goal-Setting Side Effects", "authors": "Ordóñez, L. D.; Schweitzer, M. E.; Galinsky, A. D.; Bazerman, M. H.", "year": 2009, "title": "Goals Gone Wild: The Systematic Side Effects of Over-Prescribing Goal Setting", "venue": "Harvard Business School Working Paper 09-083", "source_type": "academic working paper", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.hbs.edu/ris/download.aspx?name=09-083.pdf", "doi": null, "claim_notes": "Inspected the author-hosted HBS working paper. It supports cautions about narrow focus, unethical behavior, distorted risk preferences, organizational-culture effects, reduced intrinsic motivation, calibration, task complexity, and close monitoring. The chapter does not present these effects as inevitable for every goal system.", "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "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." ] } ] }, { "source_id": "BB-C08-S11", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "Hedgehog Concept", "authors": "Collins, J.", "year": 2001, "title": "The Hedgehog Concept", "venue": "Jim Collins official author site; concept developed in Good to Great", "source_type": "official author source", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.jimcollins.com/concepts/the-hedgehog-concept.html", "doi": null, "claim_notes": "Inspected Collins's official concept page. It directly defines the intersection of passion, potential to be best in the world, and the economic or resource engine and identifies Good to Great as the source. The chapter separates this practitioner model from causal claims and labels its feasibility, customer, risk, and externality prompts as author adaptations.", "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "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." ] } ] }, { "source_id": "BB-C08-S12", "chapter_slugs": [ "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis" ], "framework": "Survivor-Sample Bias in Management Research", "authors": "Denrell, J.", "year": 2003, "title": "Vicarious Learning, Undersampling of Failure, and the Myths of Management", "venue": "Organization Science", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://pubsonline.informs.org/doi/10.1287/orsc.14.2.227.15164", "doi": "10.1287/orsc.14.2.227.15164", "claim_notes": "Inspected the INFORMS metadata and abstract. It directly explains how survivor samples, successful-organization focus, and undersampling failure can create misleading beliefs about the determinants of performance. It supports the methodological limit placed beside the Hedgehog Concept, not a framework-specific empirical refutation.", "uses": [ { "entrySlug": "chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis", "entryTitle": "Strategy Execution: Mission, Vision, Values, OKRs, and KPIs", "excerpts": [ "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." ] } ] }, { "source_id": "BB-C11-S01", "chapter_slugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "framework": "Project Management Body of Knowledge", "authors": "Project Management Institute", "year": 2021, "title": "A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition and The Standard for Project Management", "venue": "Project Management Institute", "source_type": "professional standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://pmi.bookstore.ipgbook.com/a-guide-to-the-project-management-body-of-knowledge--pmbok---guide------seventh-edition-and-the-standard-for-project-management--english--products-9781628256642.php", "doi": null, "claim_notes": "Canonical project-management reference for project principles, performance domains, tailoring, planning, stakeholder engagement, delivery, measurement, and uncertainty. Use for framework structure, not for unsupported universal percentage thresholds. Verified 2026-07-05: PMI/IPG bookstore page confirms the 2021 Seventh Edition and The Standard for Project Management; title corrected to the complete edition title.", "uses": [ { "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "excerpts": [ "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]", "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]", "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]", "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]", "- Use monitoring and controlling to update plans, risks, baselines, stakeholders, and decisions rather than merely report status. [BB-C11-S01]", "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]", "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]", "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]", "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.", "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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C11-S02", "chapter_slugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "framework": "Work Breakdown Structure", "authors": "Project Management Institute", "year": 2019, "title": "Practice Standard for Work Breakdown Structures - Third Edition", "venue": "Project Management Institute", "source_type": "professional standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.pmi.org/standards/work-breakdown-structures-third-edition", "doi": null, "claim_notes": "Supports WBS decomposition, deliverable orientation, the 100 percent rule, and WBS dictionary usage. Local hour ranges and acceptance thresholds remain illustrative unless separately sourced. Verified 2026-07-05: PMI page confirms Practice Standard for Work Breakdown Structures - Third Edition, July 2019 publication date, and PMI standard type; edition added to title.", "uses": [ { "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "excerpts": [ "The Work Breakdown Structure (WBS) is a hierarchical, deliverable-oriented decomposition of the defined project scope into components and work packages. [BB-C11-S02]", "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]", "- 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]", "- 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]" ] } ] }, { "source_id": "BB-C11-S03", "chapter_slugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "framework": "Critical Path Method", "authors": "Kelley, J. E.; Walker, M. R.", "year": 1959, "title": "Critical-Path Planning and Scheduling", "venue": "Proceedings of the Eastern Joint IRE-AIEE-ACM Computer Conference", "source_type": "conference paper", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.computer.org/csdl/proceedings-article/afips/1959/50550160/12OmNym2c66", "doi": "10.1109/AFIPS.1959.79", "claim_notes": "Foundational source for CPM logic and schedule-network analysis. Does not validate chapter-specific schedule examples or crash-cost assumptions. Verified 2026-07-05: IEEE Computer Society page confirms Kelley and Walker, 1959, Critical-Path Planning and Scheduling, conference proceedings, and DOI; venue normalized to the fuller conference name.", "uses": [ { "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C11-S04", "chapter_slugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "framework": "Earned Value Management", "authors": "Fleming, Q. W.; Koppelman, J. M.", "year": 2010, "title": "Earned Value Project Management - Fourth Edition", "venue": "Project Management Institute", "source_type": "professional book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.pmi.org/shop/p-/book/earned-value-project-management---fourth-edition/00101230901", "doi": null, "claim_notes": "Supports EVM concepts, including planned value, earned value, actual cost, variance, performance indices, and forecasting. Worked dollar examples are illustrative. Verified 2026-07-05: PMI shop page confirms Fleming and Koppelman, Earned Value Project Management - Fourth Edition, 2010, PMI publisher, and ISBN; edition added to title.", "uses": [ { "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "excerpts": [ "Earned Value Management (EVM) integrates an authorized scope, schedule, and cost baseline to measure performance and support forecasting under stated assumptions. [BB-C11-S04]", "The definitions and formulas are supported by the EVM source; all amounts and results in this example are constructed. [BB-C11-S04]" ] } ] }, { "source_id": "BB-C11-S05", "chapter_slugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "framework": "Scrum Framework", "authors": "Schwaber, K.; Sutherland, J.", "year": 2020, "title": "The Scrum Guide: The Definitive Guide to Scrum: The Rules of the Game", "venue": "Scrum.org", "source_type": "framework guide", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf", "doi": null, "claim_notes": "Canonical Scrum source for roles/accountabilities, events, artifacts, increments, and sprint cadence. Does not support local velocity, defect, or adoption thresholds. Verified 2026-07-05: Official Scrum Guides PDF confirms Schwaber and Sutherland, November 2020, The Scrum Guide subtitle and Scrum Guide venue; no DOI found.", "uses": [ { "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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]", "- Developers: Accountable for creating a usable Increment each Sprint; required skills can span engineering, design, testing, analysis, or other work. [BB-C11-S05]", "- Sprint cadence: Choose a fixed cadence that fits the product and the team's ability to inspect and adapt. [BB-C11-S05]", "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]" ] } ] }, { "source_id": "BB-C11-S06", "chapter_slugs": [ "chapter-11-project-management-and-pmp-frameworks" ], "framework": "Agile Principles", "authors": "Beck, K.; Beedle, M.; van Bennekum, A.; Cockburn, A.; Cunningham, W.; Fowler, M.; Grenning, J.; Highsmith, J.; Hunt, A.; Jeffries, R.; Kern, J.; Marick, B.; Martin, R. C.; Mellor, S.; Schwaber, K.; Sutherland, J.; Thomas, D.", "year": 2001, "title": "Manifesto for Agile Software Development", "venue": "Agile Alliance", "source_type": "principles statement", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://agilemanifesto.org/", "doi": null, "claim_notes": "Supports agile values around iterative delivery, customer collaboration, responding to change, and working software. Does not validate percentage-based project-success claims. Verified 2026-07-05: Official Agile Manifesto site confirms the 2001 Manifesto for Agile Software Development and the listed signatories; no DOI applies.", "uses": [ { "entrySlug": "chapter-11-project-management-and-pmp-frameworks", "entryTitle": "Project Management and PMP Frameworks", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C17-S01", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Transformation Leadership", "authors": "Westerman, G.; Bonnet, D.; McAfee, A.", "year": 2014, "title": "Leading Digital: Turning Technology into Business Transformation", "venue": "Harvard Business Review Press", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://store.hbr.org/product/leading-digital-turning-technology-into-business-transformation/17039", "doi": null, "claim_notes": "Canonical practitioner source for digital transformation leadership, digital capabilities, leadership capabilities, and coordinated transformation. Does not validate universal failure-rate claims. Verified 2026-07-05 against Harvard Business Review Press store record for Westerman, Bonnet, and McAfee, 2014; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "Chapter-wide evidence boundary. The lifecycle, maturity levels, star ratings, scores, durations, cadences, thresholds, organization designs, and monetary examples in this chapter are author-constructed teaching aids unless a source marker states otherwise. They are not industry benchmarks. Transformation choices should be calibrated to strategy, regulation, architecture, capacity, affected people, and evidence. [BB-C17-S01] [BB-C17-S06] [BB-C17-S07]", "The transformation portfolio lifecycle treats digital transformation as coordinated change in strategy, capabilities, operating model, and technology, not merely a technology installation. The author-created lifecycle below is a planning scaffold: real initiatives may loop, overlap, pause, or stop, and no fixed sequence or clock establishes success. Use it to expose hypotheses, dependencies, decision rights, learning, and value evidence. [BB-C17-S01] [BB-C17-S06] [BB-C17-S07]", "Figure 17.1. Transformation portfolio learning loop. The diagram shows a reusable sequence for framing, testing, scaling, embedding, and re-evaluating an initiative; arrows do not imply a universal order or duration. Source basis: digital transformation leadership and maturity framing, adapted as an author planning aid. [BB-C17-S01] [BB-C17-S06]", "The vision and strategy canvas can help connect digital capabilities to business outcomes, but neither a canvas nor coordinated leadership guarantees transformation success. [BB-C17-S01] The canvas below is an author-created synthesis for articulating a transformation hypothesis: its why , intended customer and operating outcomes, required capabilities, evidence, risks, and decision gates. It does not ensure alignment or provide a validated roadmap. Its sections, workshop design, suitability ratings, team sizes, timings, and update cadence are illustrative defaults to adapt and test." ] } ] }, { "source_id": "BB-C17-S02", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Change Leadership", "authors": "Kotter, J. P.", "year": 1996, "title": "Leading Change", "venue": "Harvard Business School Press", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=137", "doi": null, "claim_notes": "Canonical source for the eight-step change model. Supports the structure of change-leadership guidance, not the chapter's illustrative KPI examples. Verified 2026-07-05 against Harvard Business School faculty record for Kotter, Leading Change, 1996; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "Kotter's eight-step model is an influential practitioner framework for organizing a change campaign. It is not a causal law or a universal sequence: participation, power, job design, institutional context, and emergent change can alter what is appropriate. The digital adaptation below is author-created and should be used as a diagnostic checklist, not proof that a transformation will succeed. [BB-C17-S02]", "The storytelling and communication playbook is one element of organized change, including Kotter's practitioner sequence, but a story does not overcome weak evidence, conflicting interests, unsafe job design, absent participation, or poor decision rights. [BB-C17-S02] The playbook below is an author-created communication aid informed by the cited storytelling literature. It can help leaders state the rationale, audience, evidence, uncertainty, choices, and feedback channels; it does not guarantee understanding, trust, adoption, or transformation success. Its sequence, channel mix, team design, timing, and examples are illustrative." ] } ] }, { "source_id": "BB-C17-S03", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Diffusion of Innovations", "authors": "Rogers, E. M.", "year": 2003, "title": "Diffusion of Innovations", "venue": "Free Press", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.simonandschuster.com/books/Diffusion-of-Innovations-5th-Edition/Everett-M-Rogers/9780743222099", "doi": null, "claim_notes": "Canonical source for adopter categories and approximate shares: innovators, early adopters, early majority, late majority, and laggards. Verified 2026-07-05 against Simon & Schuster official fifth-edition page for Rogers, 2003; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "The adoption-curve and chasm lens uses Rogers's adopter categories and Moore's commercial \"chasm\" to ask how adoption conditions differ; it does not establish a universal employee sequence or justify labeling people by age, status, or presumed resistance. Internal adoption can be constrained by job design, accessibility, safety, privacy, workload, power, or valid control objections rather than individual attitude. [BB-C17-S03] [BB-C17-S04]", "Figure 17.2. Rogers adopter-category shares with Moore's chasm overlaid. Rogers's approximate ideal-type shares are shown as a sequence, while Moore's chasm is a later commercial-market interpretation between early adopters and the early majority. The overlay is a teaching synthesis, not a universal adoption trajectory. [BB-C17-S03] [BB-C17-S04]", "Innovators (2.5%): a population-level ideal type associated with early experimentation; do not treat the label as a personality, age, tenure, or competence judgment. [BB-C17-S03]", "Early Adopters (13.5%): a population-level ideal type associated with earlier experimentation and strategic interest; test the actual conditions in the target population. [BB-C17-S03]", "Early Majority (34%): a population-level ideal type associated with adoption after evidence, integration, support, and reliability improve. [BB-C17-S03]", "Late Majority (34%): a population-level ideal type associated with later adoption after uncertainty and supporting infrastructure improve. [BB-C17-S03]", "Laggards (16%): a population-level ideal type associated with latest adoption or non-adoption; do not map it mechanically to worker age, tenure, or competence. [BB-C17-S03]" ] } ] }, { "source_id": "BB-C17-S04", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Crossing the Chasm", "authors": "Moore, G. A.", "year": 2014, "title": "Crossing the Chasm: Marketing and Selling Disruptive Products to Mainstream Customers", "venue": "HarperBusiness", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.harpercollins.com/products/crossing-the-chasm-3rd-edition-geoffrey-a-moore", "doi": null, "claim_notes": "Supports the chasm framing between early adopters and mainstream customers. Does not support internal adoption-rate benchmarks by itself. Verified 2026-07-05 against HarperCollins official third-edition page for Moore, 2014; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "The adoption-curve and chasm lens uses Rogers's adopter categories and Moore's commercial \"chasm\" to ask how adoption conditions differ; it does not establish a universal employee sequence or justify labeling people by age, status, or presumed resistance. Internal adoption can be constrained by job design, accessibility, safety, privacy, workload, power, or valid control objections rather than individual attitude. [BB-C17-S03] [BB-C17-S04]", "Figure 17.2. Rogers adopter-category shares with Moore's chasm overlaid. Rogers's approximate ideal-type shares are shown as a sequence, while Moore's chasm is a later commercial-market interpretation between early adopters and the early majority. The overlay is a teaching synthesis, not a universal adoption trajectory. [BB-C17-S03] [BB-C17-S04]", "2. Understand the \"Chasm\": This is the critical gap between Early Adopters (who seek a strategic leap) and the Early Majority (who seek a proven, complete solution). Early adopters will tolerate imperfect products; the early majority demand reliability, support, and integration. [BB-C17-S04]" ] } ] }, { "source_id": "BB-C17-S05", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Organizational Ambidexterity", "authors": "O'Reilly, C. A., III; Tushman, M. L.", "year": 2004, "title": "The Ambidextrous Organization", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=16932", "doi": null, "claim_notes": "Supports explore/exploit and ambidextrous-organization framing. Does not validate company-specific transformation outcomes. Verified 2026-07-05 against Harvard Business School faculty record; corrected author name to include Charles A. OReilly III; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "The ambidextrous organization model frames the tension between exploiting existing capabilities and exploring new ones. Structural separation is one design option, not a universal prescription: contextual, temporal, leadership, and network mechanisms may also be appropriate, and separation creates coordination and resource-allocation costs. [BB-C17-S05]" ] } ] }, { "source_id": "BB-C17-S06", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Maturity", "authors": "Kane, G. C.; Palmer, D.; Phillips, A. N.; Kiron, D.; Buckley, N.", "year": 2017, "title": "Achieving Digital Maturity: Adapting Your Company to a Changing World", "venue": "MIT Sloan Management Review and Deloitte University Press", "source_type": "research report", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.deloitte.com/us/en/insights/topics/digital-transformation/digital-mindset-mit-smr-report.html", "doi": null, "claim_notes": "MIT SMR/Deloitte official report inspected after Exa located the official report route; independent QA confirmed the Deloitte full report. Supports a 3,500-plus respondent survey and 15 interviews, a self-rated 1-to-10 digital-maturity measure grouped early/developing/maturing, and broad strategy, capability, workforce, culture, technology, structure, innovation, and talent framing. Author-designed triangulation advice is no longer attributed to this source.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "Chapter-wide evidence boundary. The lifecycle, maturity levels, star ratings, scores, durations, cadences, thresholds, organization designs, and monetary examples in this chapter are author-constructed teaching aids unless a source marker states otherwise. They are not industry benchmarks. Transformation choices should be calibrated to strategy, regulation, architecture, capacity, affected people, and evidence. [BB-C17-S01] [BB-C17-S06] [BB-C17-S07]", "The transformation portfolio lifecycle treats digital transformation as coordinated change in strategy, capabilities, operating model, and technology, not merely a technology installation. The author-created lifecycle below is a planning scaffold: real initiatives may loop, overlap, pause, or stop, and no fixed sequence or clock establishes success. Use it to expose hypotheses, dependencies, decision rights, learning, and value evidence. [BB-C17-S01] [BB-C17-S06] [BB-C17-S07]", "Figure 17.1. Transformation portfolio learning loop. The diagram shows a reusable sequence for framing, testing, scaling, embedding, and re-evaluating an initiative; arrows do not imply a universal order or duration. Source basis: digital transformation leadership and maturity framing, adapted as an author planning aid. [BB-C17-S01] [BB-C17-S06]", "Before embarking on a digital transformation, organizations need an honest and comprehensive understanding of their current digital capabilities and performance. The digital maturity assessment provides a structured way to evaluate an organization across multiple dimensions—strategy, customer experience, technology, operations, and culture—to identify strengths, pinpoint critical gaps, and establish a baseline for progress. [BB-C17-S06] For leaders, this assessment informs a transformation roadmap; it does not prove which investment will have the greatest impact or ensure alignment.", "Digital maturity models commonly use ordered levels across several dimensions, but the number, labels, scores, and target state below are author-created examples. Maturity is multidimensional and context-specific; a higher score does not by itself prove superior business outcomes. [BB-C17-S06]", "Figure 17.3. Evidence-to-roadmap maturity loop. The author-created loop connects dimensions, evidence-based current state, target capabilities, gaps, portfolio choices, funding, and reassessment. A score is a discussion input, not an outcome measure. Source basis: digital-maturity research. [BB-C17-S06]" ] } ] }, { "source_id": "BB-C17-S07", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "IT Governance", "authors": "Weill, P.; Ross, J. W.", "year": 2004, "title": "IT Governance: How Top Performers Manage IT Decision Rights for Superior Results", "venue": "Harvard Business School Press", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://store.hbr.org/product/it-governance-how-top-performers-manage-it-decision-rights-for-superior-results/2535", "doi": null, "claim_notes": "Supports governance, decision-rights, and accountability framing for digital operating models. Verified 2026-07-05 against Harvard Business Review Press store record for Weill and Ross; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "Chapter-wide evidence boundary. The lifecycle, maturity levels, star ratings, scores, durations, cadences, thresholds, organization designs, and monetary examples in this chapter are author-constructed teaching aids unless a source marker states otherwise. They are not industry benchmarks. Transformation choices should be calibrated to strategy, regulation, architecture, capacity, affected people, and evidence. [BB-C17-S01] [BB-C17-S06] [BB-C17-S07]", "The transformation portfolio lifecycle treats digital transformation as coordinated change in strategy, capabilities, operating model, and technology, not merely a technology installation. The author-created lifecycle below is a planning scaffold: real initiatives may loop, overlap, pause, or stop, and no fixed sequence or clock establishes success. Use it to expose hypotheses, dependencies, decision rights, learning, and value evidence. [BB-C17-S01] [BB-C17-S06] [BB-C17-S07]", "The digital governance and operating model allocates decision rights, accountability, funding, standards, assurance, and escalation; the operating model describes how capabilities are delivered and run. Central, federated, product, platform, and hybrid designs are contingent on strategy, regulation, architecture, risk, scale, and talent. Governance can improve alignment and control, but no design ensures speed, value, or competitive advantage. [BB-C17-S07]", "Figure 17.4. Digital operating-model feedback system. The author-created diagram links strategy, governance forums, product teams, decision rights, delivery, outcomes, and feedback. It is a relationship map, not a prescribed organization chart. Source basis: IT-governance decision-rights research. [BB-C17-S07]" ] } ] }, { "source_id": "BB-C17-S08", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Objectives and Key Results", "authors": "Doerr, J.", "year": 2018, "title": "Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs", "venue": "Portfolio/Penguin", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.penguinrandomhouse.com/books/546304/measure-what-matters-by-john-doerr-foreword-by-larry-page/", "doi": null, "claim_notes": "Supports OKR structure, stretch goals, transparency, and outcome-oriented measurement. Local KPI targets remain illustrative. Verified 2026-07-05 against Penguin Random House official page for Doerr, 2018; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "In the dynamic and often ambiguous world of digital transformation, traditional output-focused metrics and annual reviews can fall short. The OKR system provides a goal-setting and learning framework for setting objectives and measuring progress with defined metrics. [BB-C17-S08] OKRs can support outcome focus, alignment, transparency, and continuous improvement, but they do not ensure accountability or accelerate value by themselves.", "Ambitious: Challenging but achievable; set a locally appropriate confidence threshold rather than treating 70% as universal. [BB-C17-S08]", "A possible design is more bottom-up than top-down: teams propose their OKRs, which are then reviewed and aligned with leadership. [BB-C17-S08]", "\"Stretch Goals\": OKRs can be ambitious; define success criteria with the team rather than treating any fixed attainment rate as universal. [BB-C17-S08]" ] } ] }, { "source_id": "BB-C17-S09", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Disruptive Innovation and Incumbent Response", "authors": "Christensen, C. M.", "year": 1997, "title": "The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail", "venue": "Harvard Business School Press", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=46", "doi": null, "claim_notes": "Supports incumbent-resource-allocation and disruptive-innovation framing used in Kodak-style discussions. Does not validate exact Kodak revenue or margin figures. Verified 2026-07-05 against Harvard Business School faculty record for Christensen, 1997; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "Previously drafted case narratives contained precise financial, personnel, motive, counterfactual, and causal claims without claim-level primary support. Those narratives were removed. A defensible case should distinguish dated facts from interpretation, compare rival explanations, avoid claiming what a company \"should\" have done as fact, and disclose hindsight and survivorship bias. Disruptive-innovation theory can organize questions about resource allocation; it does not prove a single cause. [BB-C17-S09]" ] } ] }, { "source_id": "BB-C17-S10", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Transformation Success Factors", "authors": "McKinsey & Company", "year": 2018, "title": "Unlocking success in digital transformations", "venue": "McKinsey & Company", "source_type": "industry research article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/unlocking-success-in-digital-transformations", "doi": null, "claim_notes": "Complete official McKinsey survey page inspected. Supports a low respondent-defined digital-transformation success rate and discloses its 1,793-participant survey, eligible subsample, weighting, success definition, and method. Use only as directional practitioner evidence; it is not a universal failure rate or causal estimate.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "Most digital transformation frameworks assume your transformation will succeed. This section starts from a more cautious premise: large transformations often miss some intended objectives. Practitioner studies should be read as directional evidence because results vary with the sample, definition of success, and time horizon. [BB-C17-S10] [BB-C17-S11]", "Large transformations can change titles, technology, or activity measures without changing customer outcomes, operating performance, risk, or capability. Practitioner evidence suggests transformation is difficult, but it does not establish that a majority of programs are cosmetic or reveal the motives of executives, employees, boards, or advisers. Evaluate evidence and decision rights rather than intent. [BB-C17-S10] [BB-C17-S11]", "- Practitioner studies from McKinsey and BCG frame large transformation programs as difficult to sustain, but the exact result depends on the sample, definition of success, and time horizon. [BB-C17-S10] [BB-C17-S11]" ] } ] }, { "source_id": "BB-C17-S11", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Transformation Success Factors", "authors": "Forth, P.; Reichert, T.; de Laubier, R.; Chakraborty, S.", "year": 2020, "title": "Flipping the Odds of Digital Transformation Success", "venue": "BCG", "source_type": "industry research article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.bcg.com/publications/2020/increasing-odds-of-success-in-digital-transformation", "doi": null, "claim_notes": "Complete official BCG report inspected. It reports a proprietary study using experience with 70 companies and a survey of 825 executives, defines success, and states that 70% fell short of objectives. Chapter use is deliberately directional and does not generalize the rate universally or infer participant motives.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "Most digital transformation frameworks assume your transformation will succeed. This section starts from a more cautious premise: large transformations often miss some intended objectives. Practitioner studies should be read as directional evidence because results vary with the sample, definition of success, and time horizon. [BB-C17-S10] [BB-C17-S11]", "Large transformations can change titles, technology, or activity measures without changing customer outcomes, operating performance, risk, or capability. Practitioner evidence suggests transformation is difficult, but it does not establish that a majority of programs are cosmetic or reveal the motives of executives, employees, boards, or advisers. Evaluate evidence and decision rights rather than intent. [BB-C17-S10] [BB-C17-S11]", "- Practitioner studies from McKinsey and BCG frame large transformation programs as difficult to sustain, but the exact result depends on the sample, definition of success, and time horizon. [BB-C17-S10] [BB-C17-S11]" ] } ] }, { "source_id": "BB-C20-S01", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "AI Risk Management", "authors": "National Institute of Standards and Technology", "year": 2023, "title": "Artificial Intelligence Risk Management Framework (AI RMF 1.0)", "venue": "NIST", "source_type": "government framework/publication", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10", "doi": "10.6028/NIST.AI.100-1", "claim_notes": "Official 48-page NIST AI RMF 1.0 PDF inspected. Supports the voluntary and use-case-agnostic status, trustworthy-AI characteristics, GOVERN/MAP/MEASURE/MANAGE functions, lifecycle and TEVV framing, cross-cutting governance, contextual risk tolerance, and integration with enterprise risk management. Does not itself establish legal compliance.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "Current-authority note: NIST AI RMF 1.0 is a voluntary risk-management framework, and official materials, standards, and laws may change. EU AI Act and other duties are role-, system-, use-, jurisdiction-, and effective-date-specific. Recheck official primary sources before publication and implementation. [BB-C20-S01] [BB-C20-S03]", "This chapter uses FATE as a mnemonic for four practical review dimensions: Fairness, Accountability, Transparency, and Explainability. These dimensions complement the trustworthy-AI and policy principles in NIST AI RMF and the OECD AI Principles. [BB-C20-S01] [BB-C20-S02] For managers, FATE provides a practical lens to assess an AI system's ethical posture, guide design choices, and communicate responsible AI practices to stakeholders.", "An AI ethics committee is one governance option, not a universal requirement or proof of due diligence, compliance, risk reduction, or trust. Organizations can integrate challenge and decision rights into existing product, model-risk, legal, privacy, safety, security, audit, workforce, clinical, or board structures; use a dedicated body; or combine them. The decisive questions are authority, independence, conflicts, expertise, affected-party voice, evidence access, escalation, appeal, remediation, and accountable ownership. [BB-C20-S01] [BB-C20-S07]", "The AI ethics lifecycle treats ethical considerations as an ongoing responsibility rather than a one-time checkpoint; they span the entire AI development and deployment process. The AI Ethics Lifecycle provides a structured, end-to-end framework for embedding ethical principles—from initial ideation and data collection to model deployment, monitoring, and eventual decommissioning. [BB-C20-S01] For managers, this lifecycle approach helps integrate ethical considerations throughout the system's lifespan.", "Figure 20.3. AI ethics and accountability lifecycle. The author-created diagram connects problem definition, data, model, testing, deployment, monitoring, maintenance, and retirement, with monitoring able to reopen earlier decisions. It does not imply that passage through stages establishes ethical acceptability or legal compliance. Source basis: AI risk-management and end-to-end accountability practice. [BB-C20-S01] [BB-C20-S07]" ] } ] }, { "source_id": "BB-C20-S02", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "AI Policy Principles", "authors": "Organisation for Economic Co-operation and Development", "year": 2019, "title": "OECD Principles on Artificial Intelligence", "venue": "OECD", "source_type": "official policy principles", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://oecd.ai/en/ai-principles", "doi": null, "claim_notes": "Supports policy-level AI principles including inclusive growth, human-centered values, transparency, robustness, and accountability. Verified 2026-07-05 against OECD AI Principles official page and OECD legal instrument record; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "This chapter uses FATE as a mnemonic for four practical review dimensions: Fairness, Accountability, Transparency, and Explainability. These dimensions complement the trustworthy-AI and policy principles in NIST AI RMF and the OECD AI Principles. [BB-C20-S01] [BB-C20-S02] For managers, FATE provides a practical lens to assess an AI system's ethical posture, guide design choices, and communicate responsible AI practices to stakeholders." ] } ] }, { "source_id": "BB-C20-S03", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "AI Regulation", "authors": "European Parliament; Council of the European Union", "year": 2024, "title": "Regulation (EU) 2024/1689: Artificial Intelligence Act", "venue": "Official Journal of the European Union", "source_type": "official regulation", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://eur-lex.europa.eu/eli/reg/2024/1689/oj/eng", "doi": null, "claim_notes": "Supports risk-based regulatory framing for AI systems. Current applicability and obligations should be verified before public posting. Verified 2026-07-05 against EUR-Lex official Regulation (EU) 2024/1689 record; no DOI applies.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "Current-authority note: NIST AI RMF 1.0 is a voluntary risk-management framework, and official materials, standards, and laws may change. EU AI Act and other duties are role-, system-, use-, jurisdiction-, and effective-date-specific. Recheck official primary sources before publication and implementation. [BB-C20-S01] [BB-C20-S03]", "- Regulatory review: This is a governance prompt, not legal advice. Use current official sources and qualified legal review to determine whether, when, and how an AI regime applies to the specific system, deployment, jurisdiction, and date [BB-C20-S03].", "- Applicable-law review: This checklist is not legal advice. Adapt documentation only after qualified legal review confirms the current scope, phase-in, and applicability of relevant requirements for the system, deployment, jurisdiction, and date [BB-C20-S03].", "The explanation, notice, contestability, and recourse decision tree asks what understandable information, correction, challenge, and remedy a consequential decision needs. This decision tree is an operational transparency aid, not legal advice and not a statement that one universal \"right to explanation\" applies. Specific notice, explanation, contestability, and human-review duties depend on the current requirements for the jurisdiction, use case, system role, and deployment. [BB-C20-S03]", "Figure 20.2. Explanation, notice, contestability, and recourse routing. The author-created tree begins with impact and automation, then routes to current legal review, audience-appropriate information, validated explanation, correction or appeal, and monitoring. [BB-C20-S03]", "- Regulatory mapping: This is not legal advice. For systems that may fall within the EU AI Act or another AI regime, use current official sources and qualified legal review to map only the requirements that apply to the specific system, deployment, jurisdiction, and effective date before public posting [BB-C20-S03]." ] } ] }, { "source_id": "BB-C20-S04", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "Fairness in Machine Learning", "authors": "Barocas, S.; Hardt, M.; Narayanan, A.", "year": 2023, "title": "Fairness and Machine Learning: Limitations and Opportunities", "venue": "MIT Press", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://mitpress.mit.edu/9780262048613/fairness-and-machine-learning/", "doi": null, "claim_notes": "Supports fairness tradeoffs, measurement limits, and algorithmic bias concepts. Exact metric thresholds require contextual legal and technical review. Verified 2026-07-05 against MIT Press and fairmlbook records; corrected publication year and venue from 2019/fairmlbook.org to 2023/MIT Press; no DOI confirmed.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "The algorithmic bias review asks how systems can create or reproduce unjustified disparities through problem definition, data, labels, measurement, objectives, model design, thresholds, workflow, human use, or institutional context. Fairness metrics answer different normative questions and may be mutually incompatible. Qualified human owners must choose contextually and legally appropriate groups, outcomes, reference groups, metrics, thresholds, error trade-offs, and remedies; document why; test intersectional and operational effects; and provide contestability where appropriate. A favorable aggregate metric is not proof that a system is fair. [BB-C20-S04]", "Figure 20.1. Fairness evidence and remediation loop. The author-created loop connects data review, model design, fairness evaluation, deployment, outcome audit, and renewed investigation. It does not imply that one metric, mitigation, or “no bias detected” result establishes fairness. Source basis: fairness trade-off and measurement literature. [BB-C20-S04]" ] } ] }, { "source_id": "BB-C20-S05", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "Model Cards", "authors": "Mitchell, M.; Wu, S.; Zaldivar, A.; Barnes, P.; Vasserman, L.; Hutchinson, B.; Spitzer, E.; Raji, I. D.; Gebru, T.", "year": 2019, "title": "Model Cards for Model Reporting", "venue": "Proceedings of the Conference on Fairness, Accountability, and Transparency", "source_type": "peer-reviewed conference paper", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://dl.acm.org/doi/10.1145/3287560.3287596", "doi": "10.1145/3287560.3287596", "claim_notes": "Supports model card documentation for transparency, intended use, performance, and limitations. Verified 2026-07-05 against ACM Digital Library DOI record for FAT* 2019.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "Model Cards and Datasheets make intended use, performance, limitations, provenance, and documentation visible. A Model Card is like a nutrition label for an AI model, detailing its performance, limitations, and ethical considerations. A Datasheet for Datasets provides similar documentation for the data used to train AI. [BB-C20-S05] [BB-C20-S06] For managers, these frameworks facilitate accountable deployment and informed decision-making by clearly communicating the what, how, and why of AI systems." ] } ] }, { "source_id": "BB-C20-S06", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "Datasheets for Datasets", "authors": "Gebru, T.; Morgenstern, J.; Vecchione, B.; Vaughan, J. W.; Wallach, H.; Daumé III, H.; Crawford, K.", "year": 2021, "title": "Datasheets for Datasets", "venue": "Communications of the ACM", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://dl.acm.org/doi/10.1145/3458723", "doi": "10.1145/3458723", "claim_notes": "Supports dataset documentation, provenance, composition, collection process, and recommended use transparency. Verified 2026-07-05 against ACM Digital Library DOI record for Communications of the ACM, 2021.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "Model Cards and Datasheets make intended use, performance, limitations, provenance, and documentation visible. A Model Card is like a nutrition label for an AI model, detailing its performance, limitations, and ethical considerations. A Datasheet for Datasets provides similar documentation for the data used to train AI. [BB-C20-S05] [BB-C20-S06] For managers, these frameworks facilitate accountable deployment and informed decision-making by clearly communicating the what, how, and why of AI systems." ] } ] }, { "source_id": "BB-C20-S07", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "AI Ethics Guidelines", "authors": "Hagendorff, T.", "year": 2020, "title": "The Ethics of AI Ethics: An Evaluation of Guidelines", "venue": "Minds and Machines", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-05", "url": "https://link.springer.com/article/10.1007/s11023-020-09517-8", "doi": "10.1007/s11023-020-09517-8", "claim_notes": "Supports caution that AI ethics guidelines can be weak without implementation, enforcement, and institutional change. Verified 2026-07-05 against Springer Minds and Machines DOI record for Hagendorff, 2020.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "An AI ethics committee is one governance option, not a universal requirement or proof of due diligence, compliance, risk reduction, or trust. Organizations can integrate challenge and decision rights into existing product, model-risk, legal, privacy, safety, security, audit, workforce, clinical, or board structures; use a dedicated body; or combine them. The decisive questions are authority, independence, conflicts, expertise, affected-party voice, evidence access, escalation, appeal, remediation, and accountable ownership. [BB-C20-S01] [BB-C20-S07]", "Figure 20.3. AI ethics and accountability lifecycle. The author-created diagram connects problem definition, data, model, testing, deployment, monitoring, maintenance, and retirement, with monitoring able to reopen earlier decisions. It does not imply that passage through stages establishes ethical acceptability or legal compliance. Source basis: AI risk-management and end-to-end accountability practice. [BB-C20-S01] [BB-C20-S07]" ] } ] }, { "source_id": "BB-C22-S01", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Pyramid Principle Structure and SCQA Framework", "authors": "Minto, B.", "year": 2009, "title": "The Pyramid Principle: Logic in Writing and Thinking", "venue": "Financial Times Prentice Hall", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://books.google.com/books/about/The_Pyramid_Principle.html?id=VseP7-7hCNYC", "doi": null, "claim_notes": "Google Books confirms the 2009 Financial Times Prentice Hall edition. Barbara Minto’s official site supports organizing ideas as a pyramid under one point and names the Situation-Complication-Question (SCQ) framework. The manuscript now labels SCQA as its own shorthand for the SCQ setup followed by the answer, not Minto’s name for the framework.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "The Pyramid Principle is a top-down communication structure: state the answer first, then support it with grouped arguments and evidence. Minto's work is widely used in consulting because it helps teams convert messy analysis into a logical executive argument. [BB-C22-S01]", "Minto names the setup Situation, Complication, Question (SCQ) . The communication then supplies the answer. In this chapter, SCQA is an explicit shorthand for the combined SCQ setup plus answer, not a claim that Minto gave the framework that four-part name. The sequence gives an audience shared context, the tension, the decision question, and the recommendation in a compact structure. [BB-C22-S01]" ] } ] }, { "source_id": "BB-C22-S02", "chapter_slugs": [ "chapter-22-data-analysis-and-insights", "appendix-b-contrarian-business-perspectives" ], "framework": "Correlation vs. Causation Decision Tree", "authors": "Pearl, J.", "year": 2010, "title": "An Introduction to Causal Inference", "venue": "The International Journal of Biostatistics", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://escholarship.org/uc/item/5wk4j60p", "doi": "10.2202/1557-4679.1203", "claim_notes": "Full 59-page peer-reviewed article inspected through the University of California eScholarship repository; DOI and publication details cross-checked against the journal and PubMed Central record. Supports the shift from associational statistics to assumption-explicit causal analysis, structural causal models, interventions, identification, confounding, counterfactuals, and mediation. It does not make the chapter's author-created decision tree a validated universal workflow or imply that observational data identify causal effects without assumptions.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Correlation means two things move together. Causation means changing one thing would change another thing. Pearl's structural causal-inference work is one influential source for distinguishing association from intervention logic through explicit assumptions, causal models, confounding, and counterfactual reasoning. [BB-C22-S02]", "Figure 22.1. Routing from association to prediction or causal decision. The author-created tree distinguishes predictive use from intervention claims and routes causal questions through confounding, timing, design, testing, and explicit uncertainty. A path through the tree does not itself identify an effect. Source basis: causal-model and intervention reasoning. [BB-C22-S02]", "The data shows that customers attending onboarding sessions have higher renewal rates. That relationship may be useful for predicting renewal risk, but it does not prove onboarding caused renewal. Customers who attend may already be more motivated, better staffed, or larger. The decision is not \"onboarding works\"; the decision is \"should we invest in an onboarding intervention, and what design would prove incremental value?\" [BB-C22-S02]" ] }, { "entrySlug": "appendix-b-contrarian-business-perspectives", "entryTitle": "Appendix B: Contrarian Business Perspectives", "excerpts": [ "List what was directly observed, what a source reports, what the team inferred, what the plan assumes, and what remains unknown. If the recommendation depends on causality, state the causal assumptions explicitly; association alone does not identify an intervention effect. [BB-C22-S02]" ] } ] }, { "source_id": "BB-C22-S03", "chapter_slugs": [ "chapter-22-data-analysis-and-insights", "appendix-b-contrarian-business-perspectives" ], "framework": "Statistical Significance Interpretation for Managers", "authors": "Wasserstein, R. L.; Lazar, N. A.", "year": 2016, "title": "The ASA's Statement on p-Values: Context, Process, and Purpose", "venue": "The American Statistician", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.amstat.org/asa/files/pdfs/p-valuestatement.pdf", "doi": "10.1080/00031305.2016.1154108", "claim_notes": "Official ASA statement inspected. It says p-values address incompatibility with a specified model, do not measure hypothesis truth or random chance, should not be used as a threshold-only decision rule, and do not measure effect size or importance. Chapter warnings track these principles.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Statistical significance is often misused in business settings. The ASA statement on p-values says a p-value is not the probability that the hypothesis is true, is not the probability that the result occurred by chance alone, and should not be used as a bright-line substitute for scientific or practical reasoning. [BB-C22-S03]", "A p-value is a statement about the compatibility of the observed data with a specified statistical model and null hypothesis. It is not a direct measure of business importance. [BB-C22-S03]", "No. A threshold does not prove truth, causality, or business value. The ASA statement specifically warns against using p-values as a mechanical decision rule. [BB-C22-S03]" ] }, { "entrySlug": "appendix-b-contrarian-business-perspectives", "entryTitle": "Appendix B: Contrarian Business Perspectives", "excerpts": [ "Define the minimum evidence that would distinguish the default from the rival. Record source quality, population, setting, date, uncertainty, and applicability. A p-value does not measure the probability that a hypothesis is true, the importance of an effect, or the quality of a decision. [BB-C22-S03]" ] } ] }, { "source_id": "BB-C22-S04", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Regression Analysis Interpretation Guide", "authors": "Gelman, A.; Hill, J.", "year": 2007, "title": "Data Analysis Using Regression and Multilevel/Hierarchical Models", "venue": "Cambridge University Press", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.cambridge.org/highereducation/books/data-analysis-using-regression-and-multilevel-hierarchical-models/32A29531C7FD730C3A68951A17C9D983", "doi": "10.1017/CBO9780511790942", "claim_notes": "Cambridge and Andrew Gelman’s official book pages were inspected. They support applied regression, model building and evaluation, research-design orientation, causal inference, and careful interpretation. Chapter use is broad and contains no page-specific numeric claim.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Regression analysis estimates relationships between an outcome and one or more predictors. Gelman and Hill present regression as an applied modeling tool that must be interpreted with research design, model assumptions, and substantive meaning in view. [BB-C22-S04]" ] } ] }, { "source_id": "BB-C22-S05", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Data Visualization Best Practices", "authors": "Tufte, E. R.", "year": 2001, "title": "The Visual Display of Quantitative Information", "venue": "Graphics Press", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.edwardtufte.com/book/the-visual-display-of-quantitative-information/", "doi": null, "claim_notes": "Edward Tufte’s official book page explicitly lists graphical integrity, data density, small multiples, data-ink ratio, and detection of graphical deception. These are the exact concepts attributed in the chapter.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Data visualization helps people compare, diagnose, and decide. Tufte's work emphasizes graphical integrity, data density, small multiples, and avoiding visual distortion, while Few's work translates table and graph design into practical business communication. [BB-C22-S05] [BB-C22-S06]" ] } ] }, { "source_id": "BB-C22-S06", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Data Visualization Best Practices", "authors": "Few, S.", "year": 2012, "title": "Show Me the Numbers: Designing Tables and Graphs to Enlighten", "venue": "Analytics Press", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.perceptualedge.com/library.php", "doi": null, "claim_notes": "Stephen Few’s official Perceptual Edge page confirms the 2012 second edition and describes it as a practical guide to designing tables and graphs for effective and efficient quantitative communication. Chapter use is limited to that bounded practitioner guidance.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Data visualization helps people compare, diagnose, and decide. Tufte's work emphasizes graphical integrity, data density, small multiples, and avoiding visual distortion, while Few's work translates table and graph design into practical business communication. [BB-C22-S05] [BB-C22-S06]" ] } ] }, { "source_id": "BB-C22-S07", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "KPI Tree Structure", "authors": "Kaplan, R. S.; Norton, D. P.", "year": 1992, "title": "The Balanced Scorecard: Measures that Drive Performance", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.hbs.edu/faculty/Pages/item.aspx?num=9161", "doi": null, "claim_notes": "HBS metadata confirms the 1992 Kaplan and Norton article. Claim support was independently inspected in Kaplan’s later first-party HBS exposition, which states the four financial/nonfinancial perspectives and their strategy linkage. The chapter labels its KPI tree as author synthesis and does not imply page inspection of the 1992 article for every tree element.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "A KPI tree is a practical author synthesis that decomposes a top-level outcome into hypothesized drivers, sub-drivers, controllable operating metrics, and guardrails. Kaplan and Norton's balanced-scorecard work supports linked, balanced measures, but the exact tree and every arrow below are hypotheses to validate rather than canonical causal structure. [BB-C22-S07]", "Figure 22.2. Constructed KPI hypothesis tree for profitable growth. The diagram links a strategic outcome to financial and operating measures. Each arrow is a proposed relationship to define, measure, and test; ownership does not make it causal. Source basis: balanced-measurement logic, adapted as author synthesis. [BB-C22-S07]", "Financial outcomes matter, but they often lag operational drivers. Balanced-scorecard logic asks managers to connect financial, customer, process, and learning dimensions. [BB-C22-S07]" ] } ] }, { "source_id": "BB-C22-S08", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Benchmarking Framework", "authors": "APQC", "year": 2026, "title": "Benchmarking Basics", "venue": "APQC", "source_type": "institutional practitioner resource", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-09", "url": "https://www.apqc.org/resource-library/resource-collection/benchmarking-basics", "doi": null, "claim_notes": "Replacement for the weakly documented Camp 1989 record. Supports materials for planning, collection, analysis, adaptation, partner selection, and data normalization in a benchmarking initiative. It does not establish a universal benchmark, identify a universally best peer, or prove that transferring a practice will improve performance.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Benchmarking compares performance, practices, or capabilities against a relevant reference group. APQC's Benchmarking Basics is a current institutional resource for launching a benchmarking initiative; it brings together materials for planning, collection, analysis, adaptation, partner selection, and data normalization. [BB-C22-S08]", "Benchmarking is useful when it creates a learning agenda. It is dangerous when it becomes status theater. These practical cautions are an author synthesis for decision use, not claims of an average performance benefit. [BB-C22-S08]", "This classification is an author synthesis to help choose a reference group; it does not label any external peer as universally best-performing. [BB-C22-S08]", "APQC groups its methodology materials around plan, collect, analyze, and adapt. The seven-step manager workflow below translates those phases into a decision-oriented sequence; it does not demonstrate that a transferred practice will succeed. [BB-C22-S08]", "8. Benchmarking Framework - Compare performance carefully and convert gaps into action. [BB-C22-S08]" ] } ] }, { "source_id": "BB-C22-S09", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Sensitivity Analysis Grid", "authors": "Saltelli, A.; Ratto, M.; Andres, T.; Campolongo, F.; Cariboni, J.; Gatelli, D.; Saisana, M.; Tarantola, S.", "year": 2007, "title": "Global Sensitivity Analysis: The Primer", "venue": "Wiley", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://catalogimages.wiley.com/images/db/pdf/9780470059975.excerpt.pdf", "doi": "10.1002/9780470725184", "claim_notes": "Wiley’s official 52-page Chapter 1 excerpt inspected. It defines sensitivity analysis as studying how uncertainty in model output is apportioned to uncertainty sources in model input and discusses input ranges, factor prioritization, decision-relevant inference, and Monte Carlo-based methods.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Sensitivity analysis asks how much the decision changes when key assumptions move. Saltelli and coauthors frame sensitivity analysis as a way to understand how uncertainty in model inputs affects model outputs. [BB-C22-S09]", "Monte Carlo simulation models uncertainty by assigning ranges or distributions to uncertain inputs, running many simulated outcomes, and examining the resulting range of possible outputs. Hubbard's measurement work uses Monte Carlo thinking to make uncertain business cases more decision-ready, while sensitivity-analysis sources clarify how input uncertainty propagates through model outputs. [BB-C22-S10] [BB-C22-S09]", "Figure 22.3. Monte Carlo decision-model workflow. The author-created flow moves from a deterministic decision model through uncertain inputs, distributions and dependencies, simulation, validation, outcome ranges, sensitivity, and action. Simulation outputs remain conditional on the structure and assumptions. [BB-C22-S09] [BB-C22-S10]" ] } ] }, { "source_id": "BB-C22-S10", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Monte Carlo Simulation Setup", "authors": "Hubbard, D. W.", "year": 2014, "title": "How to Measure Anything: Finding the Value of Intangibles in Business", "venue": "Wiley", "source_type": "business book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.wiley.com/en-ca/How%2Bto%2BMeasure%2BAnything%3A%2BFinding%2Bthe%2BValue%2Bof%2BIntangibles%2Bin%2BBusiness%2C%2B3rd%2BEdition-p-9781118539279", "doi": null, "claim_notes": "Wiley metadata confirms Hubbard’s 2014 third edition. Claim support was inspected in Hubbard Decision Research’s first-party study guide and training material, which explicitly cover Monte Carlo simulation, probabilistic modeling, uncertainty, risk, and value of information. This does not imply page-level inspection of the 2014 book.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Monte Carlo simulation models uncertainty by assigning ranges or distributions to uncertain inputs, running many simulated outcomes, and examining the resulting range of possible outputs. Hubbard's measurement work uses Monte Carlo thinking to make uncertain business cases more decision-ready, while sensitivity-analysis sources clarify how input uncertainty propagates through model outputs. [BB-C22-S10] [BB-C22-S09]", "Figure 22.3. Monte Carlo decision-model workflow. The author-created flow moves from a deterministic decision model through uncertain inputs, distributions and dependencies, simulation, validation, outcome ranges, sensitivity, and action. Simulation outputs remain conditional on the structure and assumptions. [BB-C22-S09] [BB-C22-S10]" ] } ] }, { "source_id": "BB-C04-S13", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Discounted Cash Flow and Firm-to-Equity Valuation", "authors": "Damodaran, A.", "year": 2002, "title": "Investment Valuation, 2nd ed., Chapter 15: Firm Valuation: Cost of Capital and APV Approaches", "venue": "Wiley / NYU Stern author-hosted chapter", "source_type": "academic book chapter", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://pages.stern.nyu.edu/~adamodar/pdfiles/valn2ed/ch15.pdf", "doi": null, "claim_notes": "Complete author-hosted chapter inspected. Supports FCFF construction, WACC-based firm/operating-asset valuation, addition of non-operating assets, non-equity claims, and the firm-to-equity bridge. Supports the bounded Chapter 4 DCF text and original diagram; it does not make a model output an observed fact or investment recommendation.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C04-S14", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Relative Valuation and Comparable Firms", "authors": "Damodaran, A.", "year": 2002, "title": "Investment Valuation, 2nd ed., Chapter 17: Fundamental Principles of Relative Valuation", "venue": "Wiley / NYU Stern author-hosted chapter", "source_type": "academic book chapter", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://pages.stern.nyu.edu/~adamodar/pdfiles/valn2ed/ch17.pdf", "doi": null, "claim_notes": "Complete author-hosted chapter inspected. Supports deriving relative value from standardized market prices and controlling for peer differences in risk, growth, and cash-flow potential. It also documents market-mood, peer-selection, and implicit-assumption limitations.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]", "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]", "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].", "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]" ] } ] }, { "source_id": "BB-C05-S07", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Segmentation, Targeting, and Positioning", "authors": "Albrecht, M. G.; Green, M.; Hoffman, L.", "year": 2023, "title": "Principles of Marketing, Sections 5.1, 5.5, and 5.6", "venue": "OpenStax, Rice University", "source_type": "open academic textbook", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://openstax.org/books/principles-marketing/pages/5-6-product-positioning", "doi": null, "claim_notes": "Complete OpenStax Sections 5.1, 5.5, and 5.6 inspected. Supports defining market segments, selecting target markets, and the STP sequence culminating in product positioning. Does not prove that one segmentation or position improves outcomes without local evidence. Related inspected URLs are recorded in the chapter footnote.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C05-S08", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Pricing Decision Context", "authors": "Albrecht, M. G.; Green, M.; Hoffman, L.", "year": 2023, "title": "Principles of Marketing, Sections 12.1 and 12.2", "venue": "OpenStax, Rice University", "source_type": "open academic textbook", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://openstax.org/books/principles-marketing/pages/12-1-pricing-and-its-role-in-the-marketing-mix", "doi": null, "claim_notes": "Complete OpenStax Sections 12.1 and 12.2 inspected. Supports pricing as a marketing-mix decision involving customer value, costs, competition, channels, and compatibility with positioning/other marketing choices. Does not validate one universal pricing method or the chapter's illustrative matrix coordinates.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "Source note: Original teaching matrix informed by open marketing-principles material; positions and labels are illustrative rather than empirical. [BB-C05-S08]" ] } ] }, { "source_id": "BB-C05-S09", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Brand Architecture and Brand Relationships", "authors": "Aaker, D. A.; Joachimsthaler, E.", "year": 2000, "title": "The Brand Relationship Spectrum: The Key to the Brand Architecture Challenge", "venue": "California Management Review", "source_type": "peer-reviewed/practitioner research article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://cmr.berkeley.edu/2000/08/42-4-the-brand-relationship-spectrum-the-key-to-the-brand-architecture-challenge/", "doi": "10.1177/000812560004200401", "claim_notes": "Official UC Berkeley/CMR record and abstract inspected. Supports brand architecture as an organizing structure specifying portfolio roles and relationships and identifies sub-brand and endorsed-brand alternatives. The manuscript does not attribute guaranteed efficiency, cross-selling, or equity outcomes to it.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C05-S10", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Trustworthy Online Controlled Experiments", "authors": "Kohavi, R.; Tang, D.; Xu, Y.", "year": 2020, "title": "Trustworthy Online Controlled Experiments: A Practical Guide to A/B Testing", "venue": "Cambridge University Press", "source_type": "academic/practitioner methods book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.cambridge.org/core/books/trustworthy-online-controlled-experiments/D97B26382EB0EB2DC2019A7A7B518F59", "doi": "10.1017/9781108653985", "claim_notes": "Official Cambridge book and relevant chapter records inspected, including the available ramping chapter. Supports controlled-experiment hypothesis testing, trustworthy analysis, treatment-effect interpretation, guardrail metrics, practical decision pitfalls, and staged exposure. Does not support the chapter's separate attribution or quasi-experimental guidance.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "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]", "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]", "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]", "- Stage a supported change and monitor durability; ship, reject, redesign, or declare inconclusive according to the pre-specified decision rule. [BB-C05-S10]" ] } ] }, { "source_id": "BB-C20-S12", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "Privacy by Design", "authors": "Cavoukian, A.", "year": 2011, "title": "Privacy by Design in Law, Policy and Practice: A White Paper for Regulators, Decision-makers and Policy-makers", "venue": "Information and Privacy Commissioner of Ontario", "source_type": "official privacy regulator white paper", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.ipc.on.ca/en/media/1779/download?attachment=", "doi": null, "claim_notes": "Official 36-page Information and Privacy Commissioner of Ontario white paper inspected, including title page and Appendix A. Supports Cavoukian's August 2011 PbD framing and the seven foundational principles: proactive/preventative action, privacy as default, privacy embedded in design, positive-sum functionality, end-to-end lifecycle protection, visibility/transparency, and respect for user privacy. Does not establish current legal compliance, certification, implementation effectiveness, or fixed operating prescriptions.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "Privacy by Design (PbD) is presented in Ann Cavoukian's 2011 Information and Privacy Commissioner of Ontario white paper as a proactive approach that embeds privacy in the design and architecture of information systems and business practices rather than adding it after the fact. Its appendix states seven foundational principles. [BB-C20-S12] For managers, PbD is a design and governance framework, not legal advice, a certification, or a statement of current legal obligations. Determine the applicable requirements for the specific data, system, jurisdiction, and timing through qualified legal review." ] } ] }, { "source_id": "BB-C20-S13", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "AI Red Teaming", "authors": "National Institute of Standards and Technology", "year": 2023, "title": "NIST AI Risk Management Framework Playbook: Govern", "venue": "NIST AI Resource Center", "source_type": "government framework playbook", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://airc.nist.gov/airmf-resources/playbook/govern/", "doi": null, "claim_notes": "Current official NIST AI RMF Playbook Govern page inspected with the official Playbook release history. Supports red teaming as adversarial stress testing to seek AI failure modes or vulnerabilities and describes independent external experts or personnel as an effective-challenge design. The Playbook is voluntary, living, non-exhaustive, and not a one-size-fits-all checklist; it does not prescribe universal team composition, engagement duration, annual cadence, effectiveness, or legal compliance.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "AI red teaming is a structured effort to find flaws and vulnerabilities in an AI system, often in a controlled environment and in collaboration with developers. Its AI RMF Playbook describes red teaming as adversarial testing under stress conditions and describes red-team independence as one way to support effective challenge. [BB-C20-S13] NIST's adversarial-machine-learning taxonomy separately distinguishes attack classes, lifecycle stages, attacker goals and capabilities, and predictive versus generative AI; it is a common-language resource, not a complete red-team procedure. [BB-C20-S14] Red teaming is one evaluation and risk-management method. It does not replace ordinary quality assurance, domain validation, privacy/fairness/safety evaluation, security engineering, incident response, legal review, or post-deployment monitoring.", "Effective challenge: Establish enough independence from the people whose work is being tested to surface conflicts and blind spots, while creating safe collaboration with developers and accountable owners. [BB-C20-S13]" ] } ] }, { "source_id": "BB-C20-S14", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "Adversarial Machine Learning Taxonomy", "authors": "Vassilev, A.; Oprea, A.; Fordyce, A.; Anderson, H.; Davies, X.; Hamin, M.", "year": 2025, "title": "Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations", "venue": "NIST Trustworthy and Responsible AI", "source_type": "government technical report", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://csrc.nist.gov/pubs/ai/100/2/e2025/final", "doi": "10.6028/NIST.AI.100-2e2025", "claim_notes": "Official 127-page NIST AI 100-2e2025 report and publication record inspected. Supports attack classification by AI-system type, lifecycle stage, attacker goals, capabilities, access, and knowledge; predictive-AI evasion, poisoning, privacy, and model-extraction concepts; generative-AI poisoning, prompt attacks, privacy compromise, misuse, and connected-resource risks; and mitigation limitations. It is voluntary common-language guidance, not an exhaustive taxonomy, complete red-team procedure, risk-tolerance rule, or legal requirement.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "AI red teaming is a structured effort to find flaws and vulnerabilities in an AI system, often in a controlled environment and in collaboration with developers. Its AI RMF Playbook describes red teaming as adversarial testing under stress conditions and describes red-team independence as one way to support effective challenge. [BB-C20-S13] NIST's adversarial-machine-learning taxonomy separately distinguishes attack classes, lifecycle stages, attacker goals and capabilities, and predictive versus generative AI; it is a common-language resource, not a complete red-team procedure. [BB-C20-S14] Red teaming is one evaluation and risk-management method. It does not replace ordinary quality assurance, domain validation, privacy/fairness/safety evaluation, security engineering, incident response, legal review, or post-deployment monitoring.", "Privacy Attacks: Testing for reconstruction, membership or property inference, model extraction, prompt extraction, or leakage where relevant to the system. [BB-C20-S14]" ] } ] }, { "source_id": "BB-C20-S15", "chapter_slugs": [ "chapter-20-the-ethics-of-ai-and-data" ], "framework": "Data Ethics Canvas", "authors": "Open Data Institute", "year": 2021, "title": "The Data Ethics Canvas", "venue": "Open Data Institute Toolkit", "source_type": "official organizational toolkit", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://theodi.org/insights/tools/the-data-ethics-canvas-2021/", "doi": null, "claim_notes": "Official ODI 2021 landing page, standard-version announcement, and May 2021 canvas PDF inspected. Supports use by people who collect, share, or use data; reflection at project outset and throughout; and the standard four-category version covering data understanding, impact, engagement, and process integration. The PDF identifies its text as licensed under Creative Commons Attribution-ShareAlike 4.0 International. Does not establish project ethicality, legal compliance, effectiveness, fixed workshop duration, team composition, or review cadence.", "uses": [ { "entrySlug": "chapter-20-the-ethics-of-ai-and-data", "entryTitle": "The Ethics of AI and Data", "excerpts": [ "The Data Ethics Canvas , described by the Open Data Institute, is a tool for people who collect, share, or use data. Its purpose is to prompt reflection on ethical issues at the start of a data project and throughout it; completion does not establish that a project is ethical, lawful, fair, safe, or trustworthy. The ODI adopted a revised learning version as its standard in 2021, organized into four categories: understanding the data, exploring impact, planning engagement, and integrating decisions into processes. [BB-C20-S15] The chapter summarizes that version rather than reproducing the canvas artwork or its full text." ] } ] }, { "source_id": "BB-C02-S12", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "ESG Framework", "authors": "Knoepfel, I.; Hagart, G.", "year": 2009, "title": "Future Proof? Embedding Environmental, Social and Governance Issues in Investment Markets: Outcomes of the Who Cares Wins Initiative 2004–2008", "venue": "Who Cares Wins / United Nations Digital Library", "source_type": "official initiative report", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://digitallibrary.un.org/record/681662/files/who_cares_wins.pdf", "doi": null, "claim_notes": "Complete UN-hosted report inspected. Supports the 2004 launch of Who Cares Wins, its investment-market purpose, and the environmental, social, and governance issue grouping. It does not establish one universal ESG measurement or legal regime, and its advocacy claims are not treated as causal evidence of financial performance.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C02-S13", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "ESG Framework", "authors": "International Sustainability Standards Board", "year": 2023, "title": "IFRS S1 General Requirements for Disclosure of Sustainability-related Financial Information", "venue": "IFRS Foundation", "source_type": "official sustainability disclosure standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.ifrs.org/issued-standards/ifrs-sustainability-standards-navigator/ifrs-s1-general-requirements/", "doi": null, "claim_notes": "Official IFRS Foundation standard page inspected. Supports investor-focused disclosure of sustainability-related risks and opportunities and the governance, strategy, risk-management, metrics, and targets content areas. It does not support a universal ESG taxonomy, impact-materiality rule, or claim that compliance causes superior performance.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "- Material ESG issues should be assessed against the firm's strategy and operating context. [BB-C02-S13] [BB-C02-S14]" ] } ] }, { "source_id": "BB-C02-S14", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "ESG Framework", "authors": "European Commission, Directorate-General for Financial Stability, Financial Services and Capital Markets Union", "year": 2026, "title": "Corporate Sustainability Reporting", "venue": "European Commission", "source_type": "official regulatory overview", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://finance.ec.europa.eu/financial-markets/company-reporting-and-auditing/company-reporting/corporate-sustainability-reporting_en", "doi": null, "claim_notes": "Current European Commission overview inspected. Supports that EU sustainability reporting addresses both sustainability-related risks and opportunities and company impacts on people and the environment, and that in-scope companies report under ESRS. The page is current-state regulatory guidance; applicability and effective requirements still require date- and entity-specific legal review.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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]", "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]", "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]", "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]", "- Material ESG issues should be assessed against the firm's strategy and operating context. [BB-C02-S13] [BB-C02-S14]" ] } ] }, { "source_id": "BB-C02-S15", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Veil of Ignorance Test", "authors": "Freeman, S.", "year": 2023, "title": "Original Position", "venue": "Stanford Encyclopedia of Philosophy", "source_type": "academic reference entry", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://plato.stanford.edu/entries/original-position/", "doi": null, "claim_notes": "Complete 2023 substantive revision inspected. Supports Rawls's original position, the veil of ignorance as a restriction on knowledge intended to represent impartiality and equality, and its status as a device of representation or thought experiment. It does not validate the chapter's employment-policy examples, produce a unique managerial answer, or establish legality.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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." ] } ] }, { "source_id": "BB-C04-S15", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Break-Even Analysis", "authors": "Franklin, M.; Graybeal, P.; Cooper, D.", "year": 2019, "title": "Principles of Accounting, Volume 2: Managerial Accounting, Section 3.2: Calculate a Break-Even Point in Units and Dollars", "venue": "OpenStax, Rice University", "source_type": "open academic textbook", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://openstax.org/books/principles-managerial-accounting/pages/3-2-calculate-a-break-even-point-in-units-and-dollars", "doi": null, "claim_notes": "Complete OpenStax section inspected. Supports contribution margin and break-even calculations in units and sales dollars and states the operating assumptions required for cost-volume-profit analysis. It does not support treating cost behavior, price, mix, or capacity as invariant outside the defined relevant range.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C04-S16", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Monte Carlo Simulation", "authors": "Thomas, D.", "year": 2025, "title": "Monte Carlo Tool", "venue": "National Institute of Standards and Technology", "source_type": "official technical tool documentation", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.nist.gov/services-resources/software/monte-carlo-tool", "doi": null, "claim_notes": "Official NIST page inspected. Supports probabilistic sensitivity analysis through model sampling, specification of simulated variables and their distributions, random sampling, and selection of an iteration count. It does not prescribe 10,000 runs, independent normal inputs, a universal capital-budgeting model, or statistically calibrated confidence intervals.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C05-S11", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Customer Journey Mapping", "authors": "Lemon, K. N.; Verhoef, P. C.", "year": 2016, "title": "Understanding Customer Experience Throughout the Customer Journey", "venue": "Journal of Marketing / University of Groningen Research Portal", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://research.rug.nl/en/publications/understanding-customer-experience-throughout-the-customer-journey/", "doi": "10.1509/jm.15.0420", "claim_notes": "Institutional repository record and lawful full-text version inspected. Supports customer experience and journeys over time, multiple touchpoints across channels and media, and the need to integrate functions and external partners. It does not validate the chapter's illustrative stage sequence or diagram and does not make a journey map causal evidence.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C05-S12", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Jobs-to-be-Done", "authors": "Christensen, C. M.; Hall, T.; Dillon, K.; Duncan, D. S.", "year": 2016, "title": "Know Your Customers' Jobs to Be Done", "venue": "Harvard Business Review", "source_type": "practitioner article", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://hbr.org/2016/09/know-your-customers-jobs-to-be-done", "doi": null, "claim_notes": "Official HBR record and article text inspected. Supports the Christensen and collaborators practitioner framing around understanding why customers make choices and the progress sought in a circumstance. It does not by itself support every later JTBD interview variant, job-statement syntax, four-forces model, or a universal innovation-performance claim.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C05-S13", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Jobs-to-be-Done", "authors": "Moesta, B.; Spiek, C.", "year": 2026, "title": "What Is Jobs-to-be-Done? A Plain-English Guide", "venue": "Jobs-to-be-Done / The Re-Wired Group", "source_type": "official practitioner guide", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://jobstobedone.org/learn/", "doi": null, "claim_notes": "Current model-owner guide inspected. Supports the Moesta-Spiek practitioner variant focused on progress in a specific situation, switch interviews, the struggling moment, and the four Forces of Progress: push, pull, anxiety, and habit. It is practitioner guidance, not evidence that retrospective interviews reveal a single true motive or that the framework causes product success.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "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]", "3. Map one practitioner variant—the Forces of Progress: Moesta and Spiek describe four forces in a switching decision: [BB-C05-S13]" ] } ] }, { "source_id": "BB-C05-S14", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "RFM Segmentation", "authors": "Fader, P. S.; Hardie, B. G. S.; Lee, K. L.", "year": 2005, "title": "RFM and CLV: Using Iso-value Curves for Customer Base Analysis", "venue": "Journal of Marketing Research / author-hosted manuscript", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.brucehardie.com/papers/rfm_clv_2005-02-16.pdf", "doi": "10.1509/jmkr.2005.42.4.415", "claim_notes": "Complete author-hosted manuscript inspected. Supports recency, frequency, and monetary value as the RFM paradigm and develops a formal model connecting RFM inputs to CLV. It does not support equating simple percentile scores or descriptive segments with CLV, loyalty, churn risk, or incremental treatment response.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "- 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]" ] } ] }, { "source_id": "BB-C05-S15", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Marketing Attribution", "authors": "Li, H. A.; Kannan, P. K.", "year": 2014, "title": "Attributing Conversions in a Multichannel Online Marketing Environment: An Empirical Model and a Field Experiment", "venue": "Journal of Marketing Research / SSRN", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2621304", "doi": "10.1509/jmr.13.0050", "claim_notes": "Article abstract and accessible manuscript record inspected. Supports multichannel touchpoint attribution, carryover and spillover modeling, and a field validation conducted by pausing paid search for one week at one hospitality firm. It does not validate arbitrary first-click, linear, or position-based weights or universal causal budget effects.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "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]", "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]", "| 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] |", "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]" ] } ] }, { "source_id": "BB-C05-S16", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Marketing Attribution", "authors": "Dalessandro, B.; Stitelman, O.; Perlich, C.; Provost, F.", "year": 2012, "title": "Causally Motivated Attribution for Online Advertising", "venue": "Proceedings of the Sixth International Workshop on Data Mining for Online Advertising and Internet Economy", "source_type": "peer-reviewed conference paper", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://fosterprovost.com/wp-content/uploads/2019/07/CAUSALLY-MOTIVATED-ATTRIBUTION.pdf", "doi": "10.1145/2351356.2351363", "claim_notes": "Complete author-hosted paper inspected. Supports defining attribution as conversion-credit assignment, framing causal attribution as an estimation problem, and interpreting approximations as variable-importance measures when causal assumptions fail. It does not make observed path association equivalent to incremental effect.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C05-S17", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Cohort Analysis", "authors": "Amplitude, Inc.", "year": 2026, "title": "Cohort Analysis: Types, Examples, and How to Reduce Churn", "venue": "Amplitude", "source_type": "official practitioner guide", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://amplitude.com/explore/analytics/cohort-analysis", "doi": null, "claim_notes": "Current official guide inspected. Supports grouping users by a defined shared characteristic, tracking cohorts over time, reading retention tables by cohort age, and selecting an observation window. It explicitly warns that cohort analysis reveals associations rather than causes and recommends experiments for causal validation. It is not used for vendor benchmark claims.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "- Cohorts can be small, immature, selected, or unlike the target population; report uncertainty and avoid universal retention benchmarks. [BB-C05-S17]" ] } ] }, { "source_id": "BB-C06-S11", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Process Flow Diagrams", "authors": "American Society for Quality", "year": 2025, "title": "What Is a Flowchart? Process Flow Diagrams and Maps", "venue": "ASQ Quality Resources", "source_type": "professional-body practitioner guide", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://asq.org/quality-resources/flowchart", "doi": null, "claim_notes": "Complete ASQ guide, reviewed June 2025, inspected. Supports process boundaries, sequential steps, inputs and outputs, decisions, delays, rework, handoffs, cycle time, review with process participants, and the basic rectangle, diamond, arrow, input-output, and start-end symbol meanings. The chapter does not reproduce ASQ graphics or claim its small symbol subset is a complete notation standard.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C06-S12", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Digital Twin Architecture", "authors": "International Organization for Standardization", "year": 2021, "title": "ISO 23247-1:2021 Automation Systems and Integration — Digital Twin Framework for Manufacturing — Part 1: Overview and General Principles", "venue": "ISO", "source_type": "international standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.iso.org/standard/75066.html", "doi": null, "claim_notes": "Official ISO record inspected. Supports that ISO 23247-1 provides terms, definitions, overview, general principles, and requirements for a manufacturing digital-twin framework. The paywalled standard text was not used to support definitions beyond the public record, and the chapter's architecture, governance loop, and scope taxonomy remain author-created rather than ISO reference diagrams.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C07-S07", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Lencioni's Five Dysfunctions", "authors": "Lencioni, P. M.; The Table Group", "year": 2026, "title": "The Five Dysfunctions of a Team", "venue": "The Table Group", "source_type": "model-owner practitioner guide", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://www.tablegroup.com/topics-and-resources/teamwork-5-dysfunctions/", "doi": null, "claim_notes": "Current model-owner page inspected. Supports the five named dysfunctions—absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results—and their published sequence. It does not establish causal validity, universal performance effects, or permission to reproduce the branded pyramid or assessment.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C07-S08", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Stakeholder Mapping Grid", "authors": "UK Government Analysis Function", "year": 2024, "title": "Stakeholder Mapping", "venue": "Government Analysis Function", "source_type": "official practitioner guidance", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://analysisfunction.civilservice.gov.uk/policy-store/stakeholder-mapping/", "doi": null, "claim_notes": "Complete government guide inspected. Supports mapping stakeholders by power or influence and interest, using four engagement categories, documenting scores and reasons, providing an accessible list, and reviewing positions as power and interest change. It does not support treating low-power stakeholders as unimportant or allowing quadrant position to override rights, harms, legitimacy, or legal duties.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C07-S09", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Competing Values Framework", "authors": "Quinn, R. E.; Rohrbaugh, J.", "year": 1983, "title": "A Spatial Model of Effectiveness Criteria: Towards a Competing Values Approach to Organizational Analysis", "venue": "Management Science", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://pubsonline.informs.org/doi/10.1287/mnsc.29.3.363", "doi": "10.1287/mnsc.29.3.363", "claim_notes": "Official INFORMS article record and abstract inspected. Supports the empirically derived effectiveness-criteria framework and the control-flexibility, internal-external, and means-ends dimensions. It does not by itself support the later four-culture OCAI packaging or a claim that one quadrant is the best culture.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C07-S10", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Competing Values Framework", "authors": "Cameron, K. S.; Quinn, R. E.", "year": 1999, "title": "Diagnosing and Changing Organizational Culture Based on the Competing Values Framework", "venue": "Prentice Hall / University of Michigan author-hosted chapter", "source_type": "academic book chapter", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://webuser.bus.umich.edu/cameronk/PDFs/Organizational%20Culture/CULTURE%20BOOK-CHAPTER%201.pdf", "doi": null, "claim_notes": "Author-hosted chapter inspected. Supports the Competing Values Framework's culture application, the hierarchy, market, clan, and adhocracy types, and current-versus-preferred culture profiling. The chapter does not reproduce or score the OCAI instrument, infer one true culture, or claim that one target quadrant causes performance.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]", "Market (Compete): External focus and stability, emphasizing goals, competition, and results. [BB-C07-S10]" ] } ] }, { "source_id": "BB-C07-S11", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Organizational Design Patterns", "authors": "Black, J. S.; Bright, D. S.", "year": 2019, "title": "Organizational Behavior, Section 15.3: Organizational Designs and Structures", "venue": "OpenStax, Rice University", "source_type": "open academic textbook", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://openstax.org/books/organizational-behavior/pages/15-3-organizational-designs-and-structures", "doi": null, "claim_notes": "Complete OpenStax section inspected. Supports functional, divisional, and matrix structures, dual reporting in a matrix, contextual fit, and tradeoffs including specialization, silos, coordination, flexibility, and conflict. It does not establish that one design is universally agile or superior.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C07-S12", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Organizational Design Patterns", "authors": "Kniberg, H.; Ivarsson, A.", "year": 2012, "title": "Scaling Agile at Spotify with Tribes, Squads, Chapters and Guilds", "venue": "Crisp / Spotify", "source_type": "primary practitioner white paper", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-10", "url": "https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf", "doi": null, "claim_notes": "Complete primary white paper inspected. Supports the 2012 descriptions of squads, tribes, chapters, and guilds. The authors explicitly call the paper a fast-changing snapshot and journey in progress, not an invented, finished, universal model; it does not establish superiority or transferability to another organization.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "Chapters & Guilds: Mechanisms for people with related skills or interests to coordinate and share knowledge across squads. [BB-C07-S12]" ] } ] }, { "source_id": "BB-C04-S17", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Financial Statement Linkage", "authors": "U.S. Securities and Exchange Commission, Office of Investor Education and Advocacy", "year": 2007, "title": "Beginners' Guide to Financial Statements", "venue": "U.S. Securities and Exchange Commission", "source_type": "official investor education guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/about/reports-publications/investorpubsbegfinstmtguide", "doi": null, "claim_notes": "Complete SEC guide inspected. Supports the purposes of the balance sheet, income statement, cash flow statement, and statement of shareholders' equity; the accounting equation; operating, investing, and financing cash-flow categories; reconciliation from net income to operating cash flow; footnote review; and the principle that the statements are related and no single statement tells the complete story. It is introductory education, not authoritative GAAP or accounting advice.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C04-S18", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Accrual Accounting and Recognition", "authors": "Financial Accounting Standards Board", "year": 2021, "title": "Statement of Financial Accounting Concepts No. 8, Chapter 1: The Objective of General Purpose Financial Reporting (As Amended)", "venue": "Financial Accounting Standards Board", "source_type": "official conceptual framework", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://storage.fasb.org/Concepts%20Statement%208%E2%80%94Chapter%201%20%28As%20Amended%29.pdf", "doi": null, "claim_notes": "Complete official PDF inspected. Paragraphs 12-23 and OB17-OB20 support accrual, deferral, allocation, the timing difference between recognition and cash, and the usefulness of accrual performance information. The document expressly states that Concepts Statements are nonauthoritative and do not establish or amend GAAP; the chapter preserves that limitation.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C04-S19", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Cash Flow and Earnings Quality", "authors": "Munter, P.", "year": 2023, "title": "The Statement of Cash Flows: Improving the Quality of Cash Flow Information Provided to Investors", "venue": "U.S. Securities and Exchange Commission, Office of the Chief Accountant", "source_type": "official staff statement", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/newsroom/speeches-statements/munter-statement-cash-flows-120423", "doi": null, "claim_notes": "Complete SEC Chief Accountant statement inspected. Supports cash-flow reporting as part of a complete set of financial statements; investigation of differences between net income and cash receipts and payments; cash flow as a commonly used proxy for earnings quality; reconciliation to income-statement activity and balance-sheet changes; and the importance of classification, noncash disclosure, controls, and audit. The statement says it is staff guidance without legal force and not a Commission rule.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C04-S20", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Normalization and Non-GAAP Measures", "authors": "U.S. Securities and Exchange Commission, Division of Corporation Finance", "year": 2022, "title": "Non-GAAP Financial Measures: Compliance and Disclosure Interpretations", "venue": "U.S. Securities and Exchange Commission", "source_type": "official regulatory staff guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/rules-regulations/staff-guidance/corporation-finance-interpretations/non-gaap-financial-measures", "doi": null, "claim_notes": "Current SEC page inspected, including Questions 100.01-100.06 and 102.03. Supports cautions about excluding normal recurring cash operating expenses, inconsistent or asymmetric adjustments, misleading labels, calling recurring items nonrecurring, and individually tailored measures that change GAAP recognition or measurement, including accrual-to-cash changes. Applicability depends on U.S. securities-law context; the chapter uses it as a normalization control, not universal global law.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C04-S21", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Cost Behavior", "authors": "Franklin, M.; Graybeal, P.; Cooper, D.", "year": 2019, "title": "Principles of Accounting, Volume 2: Managerial Accounting, Section 2.2: Identify and Apply Basic Cost Behavior Patterns", "venue": "OpenStax, Rice University", "source_type": "open academic textbook", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://openstax.org/books/principles-managerial-accounting/pages/2-2-identify-and-apply-basic-cost-behavior-patterns", "doi": null, "claim_notes": "Complete open textbook section inspected. Supports decision-dependent cost classification, fixed, variable, and mixed behavior, cost drivers, per-unit versus total fixed-cost behavior, and the relevant-range boundary. It does not establish that every cost is linear, avoidable, or correctly classified without local evidence.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C04-S22", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Overhead Allocation and Activity-Based Costing", "authors": "Franklin, M.; Graybeal, P.; Cooper, D.", "year": 2019, "title": "Principles of Accounting, Volume 2: Managerial Accounting, Section 6.4: Compare and Contrast Traditional and Activity-Based Costing Systems", "venue": "OpenStax, Rice University", "source_type": "open academic textbook", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://openstax.org/books/principles-managerial-accounting/pages/6-4-compare-and-contrast-traditional-and-activity-based-costing-systems", "doi": null, "claim_notes": "Complete open textbook section inspected. Supports single-driver traditional allocation, multiple-driver activity-based costing, allocation accuracy and data-cost tradeoffs, and the distinction between supplemental ABC information and external financial-reporting product cost. It does not prove that ABC is always more decision-useful or that an allocation equals an incremental cost.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C04-S23", "chapter_slugs": [ "chapter-04-financial-analysis-and-valuation" ], "framework": "Risk, Return, and Cost of Capital", "authors": "Damodaran, A.", "year": 2016, "title": "The Cost of Capital: The Swiss Army Knife of Finance", "venue": "NYU Stern author-hosted paper", "source_type": "academic practitioner paper", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://pages.stern.nyu.edu/~adamodar/pdfiles/papers/costofcapital.pdf", "doi": null, "claim_notes": "Complete author-hosted paper inspected. Supports cost of capital as an equivalent-risk opportunity cost, financing cost, hurdle rate, and FCFF discount rate; different rates for businesses with different risk; current and currency-consistent cost of debt; cash-flow/rate currency and inflation consistency; tax-capacity limits; market-value financing weights; hybrid and changing-leverage complications; and warnings against one company-wide rate for dissimilar projects or a project-specific debt-heavy ratio. It also supports keeping discrete failure risks in cash-flow scenarios rather than arbitrary rate premiums and treating cost of capital as estimated and frequently misused.", "uses": [ { "entrySlug": "chapter-04-financial-analysis-and-valuation", "entryTitle": "Financial Analysis and Valuation", "excerpts": [ "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]", "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]", "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]", "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]", "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]", "- Small changes in the discount rate can matter, but cash-flow and terminal-value errors often dominate. Allocate review effort accordingly. [BB-C04-S23]" ] } ] }, { "source_id": "BB-C22-S11", "chapter_slugs": [ "chapter-09-problem-structuring", "chapter-22-data-analysis-and-insights" ], "framework": "Managerial Decision Analysis Under Uncertainty", "authors": "HM Treasury", "year": 2026, "title": "The Green Book: UK Government Guidance on Appraisal", "venue": "GOV.UK", "source_type": "government guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://assets.publishing.service.gov.uk/media/6984ac702df808759a7bd740/The_Green_Book_2026.pdf", "doi": null, "claim_notes": "Official 2026 PDF inspected at sections 5.6 and 6.68-6.77. Supports probability-weighted expected-value calculation, decision trees for sequential and difficult-to-reverse choices, real-options flexibility as information emerges, explicit probability-estimation limits, and treating legal, ethical, and other requirements as critical success factors or constraints. It is UK public-appraisal guidance, not a universal legal rule, private-company valuation standard, or authorization to monetize non-compensable harms.", "uses": [ { "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "excerpts": [ "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]", "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." ] }, { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Decision analysis separates what an owner can choose from what remains uncertain. A decision node contains feasible actions; a chance node contains mutually exclusive uncertain outcomes with probabilities that sum to one; a terminal branch contains the consequence of that action-outcome path. HM Treasury's 2026 appraisal guidance uses probability-weighted expected values and decision trees for complex, sequential, or difficult-to-reverse choices. [BB-C22-S11]", "5. Reversibility: model later decision points explicitly. A staged choice may preserve an option to expand, revise, or stop as evidence arrives, but only if rollback, obligations, affected parties, and path-dependent costs make that flexibility real. [BB-C22-S11]", "Figure 22.4. Evidence-gated decision tree for a constructed AI-support decision. Decision and chance nodes are labeled in text as well as by shape. The tree compares immediate launch, testing, and deferral only after non-compensable gates pass. It is an author-created worked example based on expected-value, decision-tree, Bayesian-update, utility, information-value, and reversibility principles. [BB-C22-S11] [BB-C22-S12] [BB-C22-S13] [BB-C22-S14]" ] } ] }, { "source_id": "BB-C22-S12", "chapter_slugs": [ "chapter-09-problem-structuring", "chapter-22-data-analysis-and-insights" ], "framework": "Expected Utility and Non-Compensable Decision Gates", "authors": "Government Analysis Function", "year": 2024, "title": "An Introductory Guide to Multi-Criteria Decision Analysis", "venue": "UK Government Analysis Function", "source_type": "government analytical guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://analysisfunction.civilservice.gov.uk/policy-store/an-introductory-guide-to-mcda/", "doi": null, "claim_notes": "Complete official HTML guidance inspected, especially lines 58-93 and 636-666. Supports the warning that compensatory scores allow strong performance to offset weak performance, use of absolute minima to eliminate unsuitable options before scoring, expected utility for preferences under uncertainty and risk attitude, and sensitivity review. It does not establish which legal, safety, rights, or ethical minima apply to a specific private decision.", "uses": [ { "entrySlug": "chapter-09-problem-structuring", "entryTitle": "Problem Structuring", "excerpts": [ "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]" ] }, { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Apply non-compensable gates before ranking options. If an option fails an applicable legal requirement, safety limit, rights obligation, ethical standard, or other authorized minimum, remove or redesign it rather than allowing favorable money or a weighted score to offset the failure. Official UK analytical guidance warns that compensatory models permit good performance on one criterion to offset poor performance on another and describes absolute minima for eliminating unsuitable options before scoring. [BB-C22-S12]", "Expected monetary value is a risk-neutral comparison, not a promise, forecast, or complete decision rule. Use expected utility when an authorized decision maker's risk preference or the severity and distribution of consequences could change the ranking. Utility must be elicited and sensitivity-tested; it must not be invented to rationalize a preferred answer. [BB-C22-S12]", "Figure 22.4. Evidence-gated decision tree for a constructed AI-support decision. Decision and chance nodes are labeled in text as well as by shape. The tree compares immediate launch, testing, and deferral only after non-compensable gates pass. It is an author-created worked example based on expected-value, decision-tree, Bayesian-update, utility, information-value, and reversibility principles. [BB-C22-S11] [BB-C22-S12] [BB-C22-S13] [BB-C22-S14]" ] } ] }, { "source_id": "BB-C22-S13", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Bayesian Decision Trees and Value of Information", "authors": "Pindilli, E.; Chiavacci, S. J.; Straub, C. L.", "year": 2023, "title": "The Value of Scientific Information—An Overview", "venue": "U.S. Geological Survey Open-File Report 2023-1011", "source_type": "government research report", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://pubs.usgs.gov/publication/ofr20231011/full", "doi": "10.3133/ofr20231011", "claim_notes": "Complete official USGS HTML report inspected. Supports value of information as the difference in decision outcomes with versus without additional information relative to the next-best information, Bayesian decision-tree representation, and applied examples in which information changes decisions and consequences. The BusinessBook example, monetary values, test properties, and EVSI calculation are author-constructed and not USGS findings.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "4. Value of information (VOI): compare the expected value of the best action after observing information with the expected value of the best action now. Subtract testing, delay, implementation, privacy, safety, and other information-acquisition costs. Information has decision value only when it can change an action or improve its timing, targeting, safeguards, or consequence. USGS illustrates this logic with Bayesian decision trees comparing decisions with and without new scientific information. [BB-C22-S13]", "Figure 22.4. Evidence-gated decision tree for a constructed AI-support decision. Decision and chance nodes are labeled in text as well as by shape. The tree compares immediate launch, testing, and deferral only after non-compensable gates pass. It is an author-created worked example based on expected-value, decision-tree, Bayesian-update, utility, information-value, and reversibility principles. [BB-C22-S11] [BB-C22-S12] [BB-C22-S13] [BB-C22-S14]" ] } ] }, { "source_id": "BB-C22-S14", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Bayesian Base-Rate Updating", "authors": "Pennsylvania State University Department of Statistics", "year": "n.d.", "title": "STAT 414 Lesson 6: Bayes' Theorem", "venue": "Penn State Eberly College of Science", "source_type": "open academic course", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://online.stat.psu.edu/stat414/Lesson06", "doi": null, "claim_notes": "Complete open lesson inspected. It derives Bayes' theorem from conditional probability, distinguishes prior from posterior probabilities, and demonstrates how a low base rate can keep a posterior probability modest even after a positive result. It supports the formula and base-rate update, not the constructed AI-support probabilities or business recommendation.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "3. Bayesian update: begin with the relevant base rate or prior probability, then update it with evidence: P(H|E) = P(E|H) x P(H) / P(E) . Penn State's open probability lesson derives this conditional-probability relationship. [BB-C22-S14]", "Figure 22.4. Evidence-gated decision tree for a constructed AI-support decision. Decision and chance nodes are labeled in text as well as by shape. The tree compares immediate launch, testing, and deferral only after non-compensable gates pass. It is an author-created worked example based on expected-value, decision-tree, Bayesian-update, utility, information-value, and reversibility principles. [BB-C22-S11] [BB-C22-S12] [BB-C22-S13] [BB-C22-S14]" ] } ] }, { "source_id": "BB-C07-S13", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership", "chapter-12-client-management" ], "framework": "Principled Negotiation and BATNA", "authors": "Fisher, R.; Ury, W. L.; Patton, B.", "year": 2011, "title": "Getting to Yes: Negotiating Agreement Without Giving In", "venue": "Penguin Books, third edition", "source_type": "academic-practitioner book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.penguinrandomhouse.com/books/324551/getting-to-yes-by-roger-fisher-and-william-ury/", "doi": null, "claim_notes": "Official publisher page inspected. It confirms the 2011 third-edition authorship and the Harvard Negotiation Project framing, including separating people from the problem, focusing on interests rather than positions, generating options, and using objective criteria. The BATNA definition is treated as the canonical book concept; the BusinessBook's authority, rights, risk, and implementation gates are author-added cautions.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]", "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]", "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]" ] }, { "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C07-S14", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership", "chapter-12-client-management" ], "framework": "Creating and Claiming Value in Managerial Negotiation", "authors": "Lax, D. A.; Sebenius, J. K.", "year": 1986, "title": "Manager as Negotiator: Bargaining for Cooperation and Competitive Gain", "venue": "Free Press / Simon & Schuster", "source_type": "academic book", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.simonandschuster.com/books/Manager-as-Negotiator/David-A-Lax/9781451636499", "doi": null, "claim_notes": "Official publisher page and excerpt inspected; Google Books publication details cross-checked. Supports the manager-as-negotiator framing and the book's analysis of alternatives, reservation values, bargaining ranges, cooperation, competitive gain, and the tension between creating and claiming value. It does not support deception, coercion, or treating every managerial interaction as negotiable.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]", "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]", "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]" ] }, { "entrySlug": "chapter-12-client-management", "entryTitle": "Client Management", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C07-S15", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Negotiation Ethics and Truthfulness Boundary", "authors": "American Bar Association", "year": 2019, "title": "Model Rule 4.1: Truthfulness in Statements to Others", "venue": "ABA Model Rules of Professional Conduct", "source_type": "professional model rule", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/rule_4_1_truthfulness_in_statements_to_others/", "doi": null, "claim_notes": "Official ABA rule and comment inspected. Supports only the narrow example that the model rule addresses knowingly false statements of material fact or law by lawyers dealing with third persons and certain disclosures needed to avoid assisting crime or fraud. The chapter expressly states that professional duties and applicability vary by jurisdiction and role and require counsel.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C07-S16", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Radical Candor", "authors": "Scott, K.", "year": 2017, "title": "Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity", "venue": "St. Martin's Press / Radical Candor", "source_type": "model-owner practitioner framework", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-12", "url": "https://www.radicalcandor.com/our-approach", "doi": null, "claim_notes": "Canonical model-owner page inspected. Supports the bounded practitioner framing of Caring Personally and Challenging Directly and the four feedback quadrants. It does not establish a validated leadership ranking, universal performance effect, or permission to reproduce the trademarked visual or assessment materials.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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." ] } ] }, { "source_id": "BB-C07-S17", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Talent Potential Assessment", "authors": "Silzer, R.; Church, A. H.", "year": 2009, "title": "The Pearls and Perils of Identifying Potential", "venue": "Industrial and Organizational Psychology", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-12", "url": "https://doi.org/10.1111/j.1754-9434.2009.01163.x", "doi": "10.1111/j.1754-9434.2009.01163.x", "claim_notes": "Wiley article record inspected. Supports the bounded claim that organizations use varied approaches to identifying potential and that talent-potential judgments require conceptual and methodological care. It does not validate the 9-box grid, predict an individual employee's future, or establish employment outcomes.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C07-S18", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Self-Determination Theory", "authors": "Deci, E. L.; Ryan, R. M.", "year": 2000, "title": "The ‘What’ and ‘Why’ of Goal Pursuits: Human Needs and the Self-Determination of Behavior", "venue": "Psychological Inquiry", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-12", "url": "https://doi.org/10.1207/S15327965PLI1104_01", "doi": "10.1207/S15327965PLI1104_01", "claim_notes": "Publisher abstract and author-hosted full text inspected. Supports self-determination theory's account of the psychological needs for autonomy, competence, and relatedness. It does not establish Pink's exact practitioner model, a universal workplace intervention, or guaranteed performance or retention effects.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C07-S19", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Motivation Theory", "authors": "Pink, D. H.", "year": 2009, "title": "Drive: The Surprising Truth About What Motivates Us", "venue": "Riverhead Books / Penguin Random House", "source_type": "practitioner book", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-12", "url": "https://www.danpink.com/books/drive/", "doi": null, "claim_notes": "Author and publisher records inspected. Supports the bounded practitioner framing of autonomy, mastery, and purpose in Drive. It does not establish a universal motivation mechanism, guarantee workplace performance or retention, or replace the distinct self-determination-theory evidence base.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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]", "For modern knowledge work, Daniel Pink's practitioner model uses three prompts: autonomy, mastery, and purpose. [BB-C07-S19]" ] } ] }, { "source_id": "BB-C07-S20", "chapter_slugs": [ "chapter-07-organizational-behavior-and-leadership" ], "framework": "Conflict-Mode Reflection Map", "authors": "Thomas, K. W.; Kilmann, R. H.; CPP, Inc.", "year": 1974, "title": "Thomas-Kilmann Conflict Mode Instrument", "venue": "CPP, Inc.", "source_type": "model-owner practitioner instrument", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-12", "url": "https://shop.cpp.com/Pdfs/TKI-GRP-tech-brief.pdf", "doi": null, "claim_notes": "Model-owner technical brief and product material inspected. Supports the named five conflict modes and the assertiveness/cooperativeness dimensions. The manuscript's figure is an author-created illustrative redraw; the licensed instrument, assessment items, scoring, and trademarked materials are not reproduced.", "uses": [ { "entrySlug": "chapter-07-organizational-behavior-and-leadership", "entryTitle": "Organizational Behavior and Leadership", "excerpts": [ "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.", "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]" ] } ] }, { "source_id": "BB-C02-S16", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - U.S. Antitrust and Competition", "authors": "Federal Trade Commission", "year": "n.d.", "title": "Anticompetitive Practices", "venue": "Federal Trade Commission", "source_type": "official regulator guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.ftc.gov/enforcement/anticompetitive-practices", "doi": null, "claim_notes": "Official FTC page inspected 2026-07-11. Supports the distinction between unreasonable horizontal restraints and exclusionary single-firm conduct and the examples of price fixing, market division, and bid rigging as conduct described by the FTC as almost always illegal. It does not determine the legality of a particular collaboration, information exchange, vertical restraint, platform practice, or transaction.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "| 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. |", "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." ] } ] }, { "source_id": "BB-C02-S17", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - EU Competition", "authors": "European Commission", "year": "n.d.", "title": "Competition Law Treaty Articles", "venue": "European Commission, Directorate-General for Competition", "source_type": "primary treaty text", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://competition-policy.ec.europa.eu/antitrust-and-cartels/legislation/competition-law-treaty-articles_en", "doi": null, "claim_notes": "Official European Commission reproduction of TFEU competition provisions inspected 2026-07-11. Supports the high-level Article 101 categories for agreements, decisions, and concerted practices and Article 102's abuse-of-dominance category. It does not establish applicability, an effect on trade, restriction, exemption, relevant market, dominance, abuse, procedure, or outcome for a particular matter.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "| 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. |", "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." ] } ] }, { "source_id": "BB-C02-S18", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - U.S. Worker Classification Rulemaking", "authors": "U.S. Department of Labor, Wage and Hour Division", "year": 2026, "title": "Final Rule: Employee or Independent Contractor Classification Under the Fair Labor Standards Act, RIN 1235-AA43", "venue": "U.S. Department of Labor", "source_type": "official regulator rulemaking page", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.dol.gov/agencies/whd/flsa/misclassification/rulemaking", "doi": null, "claim_notes": "Official DOL page inspected 2026-07-11. Supports that the 2024 FLSA classification rule became effective March 11, 2024 and that DOL announced a proposed replacement rule on February 26, 2026. The source does not resolve worker status under the FLSA, state law, tax, benefits, immigration, or any other regime. Current rulemaking status must be rechecked before publication or use.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "| 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. |", "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." ] } ] }, { "source_id": "BB-C02-S19", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - U.S. Worker Classification Enforcement", "authors": "U.S. Department of Labor, Wage and Hour Division", "year": 2025, "title": "Field Assistance Bulletin No. 2025-1: FLSA Independent Contractor Misclassification Enforcement Guidance", "venue": "U.S. Department of Labor", "source_type": "official enforcement guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.dol.gov/sites/dolgov/files/WHD/fab/fab2025-1.pdf", "doi": null, "claim_notes": "Official three-page DOL bulletin inspected 2026-07-11. Supports that, from May 1, 2025, Wage and Hour Division investigations no longer applied the 2024 rule's analysis and instead used specified earlier guidance, while the 2024 rule remained in effect for private litigation. It is enforcement guidance, not a status determination or a source for non-FLSA regimes, and may be superseded.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "| 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. |", "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." ] } ] }, { "source_id": "BB-C02-S20", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - U.S. Advertising Claims", "authors": "Federal Trade Commission", "year": 1984, "title": "FTC Policy Statement Regarding Advertising Substantiation", "venue": "Federal Trade Commission", "source_type": "official regulator policy statement", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.ftc.gov/legal-library/browse/ftc-policy-statement-regarding-advertising-substantiation", "doi": null, "claim_notes": "Official FTC policy statement dated November 23, 1984 and inspected 2026-07-11. Supports the prior reasonable-basis requirement for objective express and implied advertising claims and the source's context-dependent substantiation factors. It is not a safe harbor, a finding about a particular claim, or a universal scientific-evidence prescription for every product.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "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]", "| 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. |", "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." ] } ] }, { "source_id": "BB-C02-S21", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - U.S. Consumer Product Reporting", "authors": "U.S. Consumer Product Safety Commission", "year": "n.d.", "title": "Duty to Report to CPSC: Rights and Responsibilities of Businesses", "venue": "U.S. Consumer Product Safety Commission", "source_type": "official regulator guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.cpsc.gov/Business--Manufacturing/Recall-Guidance/Duty-to-Report-to-CPSC-Rights-and-Responsibilities-of-Businesses", "doi": null, "claim_notes": "Official CPSC guidance inspected 2026-07-11. Supports immediate escalation of potentially reportable product information, the stated 24-hour reporting expectation after obtaining reportable information, the limited period for a reasonable investigation when genuinely uncertain, and the distinction between reporting and a recall determination. Applicability depends on the product, entity role, facts, statute, and current law; the page itself disclaims legal advice.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "| 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. |", "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." ] } ] }, { "source_id": "BB-C02-S22", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - U.S. Current Reporting", "authors": "U.S. Securities and Exchange Commission", "year": 2025, "title": "Form 8-K: Current Report Pursuant to Section 13 or 15(d) of the Securities Exchange Act of 1934", "venue": "U.S. Securities and Exchange Commission", "source_type": "official regulator form", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/files/form8-k.pdf", "doi": null, "claim_notes": "Official SEC Form 8-K edition SEC 873 (02-25) inspected 2026-07-11. Supports the description of Form 8-K as a current-report form and its enumerated event categories. It does not establish that a specific issuer is covered, an event is material, a filing is required, or a particular deadline or disclosure is sufficient.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "| 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. |", "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." ] } ] }, { "source_id": "BB-C02-S23", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - U.S. Selective Disclosure and Insider Trading", "authors": "U.S. Securities and Exchange Commission", "year": 2000, "title": "Selective Disclosure and Insider Trading", "venue": "Securities Act Release No. 33-7881; Exchange Act Release No. 34-43154", "source_type": "official regulation and adopting release", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/rules-regulations/2000/08/selective-disclosure-insider-trading", "doi": null, "claim_notes": "Official SEC Regulation FD and insider-trading adopting release inspected 2026-07-11. Supports the high-level selective-disclosure and material-nonpublic-information issue categories for covered issuers and persons. Scope, exclusions, materiality, public-disclosure timing, trading liability, and any response to a specific communication require securities counsel.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "| 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. |", "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." ] } ] }, { "source_id": "BB-C02-S24", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - Delaware Corporate Authority", "authors": "State of Delaware", "year": "n.d.", "title": "Delaware Code, Title 8, Chapter 1, Subchapter IV: Directors and Officers, Sections 141 and 142", "venue": "Delaware Code Online", "source_type": "primary legislation", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://delcode.delaware.gov/title8/c001/sc04/", "doi": null, "claim_notes": "Current official Delaware Code page inspected 2026-07-11. Supports the general Section 141 board-management rule and Section 142's linkage of officer titles and duties to bylaws or board resolutions. It does not prove actual, apparent, delegated, or statutory authority for a particular person or transaction and does not apply to every entity or jurisdiction.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "| 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. |", "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." ] } ] }, { "source_id": "BB-C02-S25", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - U.S. Distress and Reorganization", "authors": "Administrative Office of the U.S. Courts", "year": "n.d.", "title": "Chapter 11 - Bankruptcy Basics", "venue": "United States Courts", "source_type": "official court educational guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.uscourts.gov/court-programs/bankruptcy/bankruptcy-basics/chapter-11-bankruptcy-basics", "doi": null, "claim_notes": "Official U.S. Courts educational page inspected 2026-07-11. Supports the high-level description of Chapter 11 reorganization, debtor-in-possession operation, court approval for some actions, and U.S.-trustee monitoring. The page states that it is not legal authority, filing guidance, or a substitute for competent legal, accounting, or financial advice.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "| 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. |", "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." ] } ] }, { "source_id": "BB-C02-S26", "chapter_slugs": [ "chapter-02-business-law-governance-and-ethics" ], "framework": "Legal Lifecycle Risk Gate - U.S. Labor-Market Competition", "authors": "U.S. Department of Justice, Antitrust Division; Federal Trade Commission", "year": 2025, "title": "Antitrust Guidelines for Business Activities Affecting Workers", "venue": "U.S. Department of Justice and Federal Trade Commission", "source_type": "official joint-agency guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.justice.gov/atr/media/1384596/dl?inline=", "doi": null, "claim_notes": "Official DOJ-FTC guidelines revised January 2025 and inspected 2026-07-11. Supports issue-spotting for wage-fixing, no-poach, exchange of compensation or other competitively sensitive employment information, worker-mobility restrictions, and other labor-market conduct. The guidelines explain agency assessment and explicitly state that listed activities may or may not violate antitrust law; they are not a determination for a particular practice or a substitute for counsel.", "uses": [ { "entrySlug": "chapter-02-business-law-governance-and-ethics", "entryTitle": "Business Law, Governance, and Ethics", "excerpts": [ "| 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. |", "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." ] } ] }, { "source_id": "BB-C22-S15", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Estimands and Sensitivity Analysis", "authors": "International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use", "year": 2021, "title": "E9(R1) Statistical Principles for Clinical Trials: Addendum: Estimands and Sensitivity Analysis in Clinical Trials", "venue": "U.S. Food and Drug Administration Guidance for Industry", "source_type": "official guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.fda.gov/media/148473/download", "doi": null, "claim_notes": "Supports defining the treatment effect of interest through a structured estimand before choosing design and analysis, including population, treatment condition, variable or endpoint, intercurrent-event strategy, and population-level summary. The chapter generalizes the discipline to business experiments and does not imply that pharmaceutical regulatory rules govern every business test.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "An experiment should estimate a decision-relevant effect, not merely produce a p-value. Before assignment begins, write the estimand : the precise effect the analysis is intended to estimate. The ICH E9(R1) framework defines this discipline through the treatment conditions, population, outcome variable, handling of events after assignment that complicate interpretation, and population-level summary. The structure transfers usefully to business experiments even though business tests are not clinical trials. [BB-C22-S15]" ] } ] }, { "source_id": "BB-C22-S16", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Experiment Design, Power, Multiplicity, and Interim Analysis", "authors": "International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use", "year": 1998, "title": "E9 Statistical Principles for Clinical Trials", "venue": "U.S. Food and Drug Administration Guidance for Industry", "source_type": "official guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.fda.gov/media/71336/download", "doi": null, "claim_notes": "Supports pre-specification, sample-size justification, type I and type II error, multiplicity, interim analysis, missing-data attention, and cautious subgroup interpretation. The chapter adapts these general statistical disciplines to managerial experimentation rather than presenting clinical-trial compliance advice.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "The minimum detectable effect (MDE) is the smallest effect the design is intended to detect with its specified power and error rate. It is not the smallest effect that matters. The team should first set a minimum practically important effect from economics, customer value, risk, or capacity; then size the experiment so a result near that threshold is informative. ICH E9 requires sample-size justification tied to the primary objective, type I error, power, and assumptions. [BB-C22-S16]", "Figure 22.5. Effect-size/sample-size curve. Author-created calculation using the stated normal approximation; deterministic data and assumptions are in docs/evidence-packets/ch22-experiment-optimization-visual-data.json . The curve is illustrative, not a universal sample-size rule. [BB-C22-S16]", "6. Multiplicity: the family of outcomes, variants, looks, and confirmatory subgroups to be protected; the error-control method; and which analyses are exploratory. More tests create more opportunities for chance findings. [BB-C22-S16] [BB-C22-S17]", "10. Subgroups: a small number of theory-backed, pre-specified hypotheses with interaction tests. Do not infer that subgroups differ merely because one is statistically significant and another is not; label post-hoc segment mining exploratory. [BB-C22-S16] [BB-C22-S20]" ] } ] }, { "source_id": "BB-C22-S17", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Sequential A/B Testing", "authors": "Johari, R.; Koomen, P.; Pekelis, L.; Walsh, D.", "year": 2022, "title": "Always Valid Inference: Continuous Monitoring of A/B Tests", "venue": "Operations Research, 70(3), 1806-1821", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://pubsonline.informs.org/doi/10.1287/opre.2021.2135", "doi": "10.1287/opre.2021.2135", "claim_notes": "Supports the warning that ordinary fixed-horizon p-values and confidence intervals are unreliable when sample size is chosen through continuous monitoring, and supports always-valid inference as one principled sequential-testing approach with sequential multiplicity control.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "5. Timing and stopping: fixed horizon or a valid group-sequential/always-valid design; planned looks; efficacy, futility, safety, and operational stop rules. Repeatedly checking ordinary fixed-horizon p-values and stopping when one crosses a threshold invalidates their usual interpretation. [BB-C22-S17]", "6. Multiplicity: the family of outcomes, variants, looks, and confirmatory subgroups to be protected; the error-control method; and which analyses are exploratory. More tests create more opportunities for chance findings. [BB-C22-S16] [BB-C22-S17]", "Action: Treat the result as exploratory; rerun under a precommitted fixed-horizon or valid sequential design with explicit multiplicity control. [BB-C22-S17]" ] } ] }, { "source_id": "BB-C22-S18", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Causal Inference With Interference", "authors": "Hudgens, M. G.; Halloran, M. E.", "year": 2008, "title": "Toward Causal Inference With Interference", "venue": "Journal of the American Statistical Association, 103(482), 832-842", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC2600548/", "doi": "10.1198/016214508000000292", "claim_notes": "Supports distinguishing direct, indirect or spillover, total, and overall effects when one unit's treatment can affect another unit's outcome. It supports redesigning assignment and estimands when no-interference assumptions are implausible.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "8. Interference and spillovers: whether one unit's treatment can change another unit's outcome through teams, households, networks, inventory, pricing, or shared capacity. If so, redefine the estimand and consider cluster, geographic, network, or two-stage assignment; direct and spillover effects are distinct causal quantities. [BB-C22-S18]", "Action: Do not average the harm away. Inspect data quality, direct and spillover effects, pre-specified interactions, and the approved guardrail threshold before adoption. [BB-C22-S18] [BB-C22-S19] [BB-C22-S20]" ] } ] }, { "source_id": "BB-C22-S19", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Trustworthy Online Experimentation", "authors": "Microsoft Experimentation Platform", "year": 2020, "title": "Patterns of Trustworthy Experimentation: During-Experiment Stage", "venue": "Microsoft Research", "source_type": "official practitioner guidance", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.microsoft.com/en-us/research/group/experimentation-platform-exp/articles/patterns-of-trustworthy-experimentation-during-experiment-stage/", "doi": null, "claim_notes": "Supports the operational distinction among data-quality, overall evaluation, diagnostic, and guardrail metrics; warns that repeated measurement requires suitable statistical handling; and identifies declining effects across date segments as a possible novelty effect. Microsoft-specific cadence examples are not treated as universal benchmarks.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "4. Metric hierarchy: one primary outcome or a pre-defined primary family; diagnostic metrics; data-quality checks; and guardrails with explicit non-inferiority or harm limits. Microsoft distinguishes overall-evaluation, diagnostic, data-quality, and guardrail metrics in its experimentation practice. [BB-C22-S19]", "9. Novelty and duration: whether initial curiosity, learning, fatigue, seasonality, or survivorship could make the early effect differ from the steady-state effect; pre-plan time-segment checks or a longer holdout. A changing effect across date segments may indicate novelty, but the pattern is a diagnostic rather than proof. [BB-C22-S19]", "Action: Do not average the harm away. Inspect data quality, direct and spillover effects, pre-specified interactions, and the approved guardrail threshold before adoption. [BB-C22-S18] [BB-C22-S19] [BB-C22-S20]" ] } ] }, { "source_id": "BB-C22-S20", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Transparent Experiment Reporting", "authors": "Moher, D.; Hopewell, S.; Schulz, K. F.; Montori, V.; Gotzsche, P. C.; Devereaux, P. J.; Elbourne, D.; Egger, M.; Altman, D. G.", "year": 2010, "title": "CONSORT 2010 Explanation and Elaboration: Updated Guidelines for Reporting Parallel Group Randomised Trials", "venue": "BMJ, 340, c869", "source_type": "peer-reviewed reporting guideline", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.bmj.com/content/340/bmj.c869", "doi": "10.1136/bmj.c869", "claim_notes": "Supports transparent participant flow and attrition reporting, pre-specified subgroup analyses and interaction tests, and disclosure of interim analyses and stopping rules. The chapter adapts these transparency principles to business experiments.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "7. Attrition and missingness: expected loss, reasons, participant or unit flow, differential loss by arm, telemetry failure, analysis handling, and sensitivity analysis. Transparent flow and loss reporting is necessary because post-assignment exclusions can change the comparison. [BB-C22-S20]", "10. Subgroups: a small number of theory-backed, pre-specified hypotheses with interaction tests. Do not infer that subgroups differ merely because one is statistically significant and another is not; label post-hoc segment mining exploratory. [BB-C22-S16] [BB-C22-S20]", "Action: Do not average the harm away. Inspect data quality, direct and spillover effects, pre-specified interactions, and the approved guardrail threshold before adoption. [BB-C22-S18] [BB-C22-S19] [BB-C22-S20]" ] } ] }, { "source_id": "BB-C22-S21", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Linear Optimization", "authors": "Google OR-Tools Team", "year": 2025, "title": "Solving an LP Problem", "venue": "Google for Developers: OR-Tools Documentation", "source_type": "official technical documentation", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://developers.google.com/optimization/lp/lp_example", "doi": null, "claim_notes": "Supports the standard linear-programming model structure: decision variables, linear constraints, an objective function, solver status, and an optimal solution conditional on the model. The chapter's product-mix model and numbers are author-created teaching assumptions.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Google OR-Tools' official examples use the same variable-constraint-objective-solve structure. A solver's “optimal” status means optimal for the mathematical model provided; it does not prove that the objective, data, constraints, or omitted consequences represent the real decision. [BB-C22-S21]", "Figure 22.6. Linear-program feasible region. The shaded area contains all choices satisfying the constructed constraints. The continuous objective reaches its maximum at the intersection; a whole-unit requirement moves the solution to the best feasible integer point. Data and verification inputs are in docs/evidence-packets/ch22-experiment-optimization-visual-data.json . [BB-C22-S21] [BB-C22-S22]", "Action: Repair and validate the model, add integer or logical restrictions where needed, rerun scenarios, and document the changed feasible region. [BB-C22-S21] [BB-C22-S22]" ] } ] }, { "source_id": "BB-C22-S22", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Mixed-Integer Optimization", "authors": "Google OR-Tools Team", "year": 2025, "title": "Mixed-Integer Programming", "venue": "Google for Developers: OR-Tools Documentation", "source_type": "official technical documentation", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://developers.google.com/optimization/mip", "doi": null, "claim_notes": "Supports distinguishing mixed-integer programs from continuous linear programs when some variables must take integer values and notes that solver choice depends on model structure.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "Figure 22.6. Linear-program feasible region. The shaded area contains all choices satisfying the constructed constraints. The continuous objective reaches its maximum at the intersection; a whole-unit requirement moves the solution to the best feasible integer point. Data and verification inputs are in docs/evidence-packets/ch22-experiment-optimization-visual-data.json . [BB-C22-S21] [BB-C22-S22]", "Use a continuous linear program when fractional decisions are meaningful: tons, hours, budget shares, or flow. Use an integer or mixed-integer model when choices are indivisible or logical: facilities, people, trucks, production batches, open-or-close decisions, or yes/no assignments. Integer restrictions can create an integrality gap between the relaxed continuous solution and the best implementable whole-number choice, and they generally require different solution methods. [BB-C22-S22]", "Action: Repair and validate the model, add integer or logical restrictions where needed, rerun scenarios, and document the changed feasible region. [BB-C22-S21] [BB-C22-S22]" ] } ] }, { "source_id": "BB-C22-S23", "chapter_slugs": [ "chapter-22-data-analysis-and-insights" ], "framework": "Optimization Sensitivity and Shadow Prices", "authors": "Gershwin, S. B.", "year": 2016, "title": "Optimization", "venue": "MIT OpenCourseWare, Introduction to Manufacturing Systems", "source_type": "official university course material", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://ocw.mit.edu/courses/2-854-introduction-to-manufacturing-systems-fall-2016/resources/283796c9f0729a97f410a65ca4b70471_MIT2_854F16_Optimization.pdf", "doi": null, "claim_notes": "Supports linear-programming sensitivity analysis and shadow-price intuition. The chapter limits shadow-price interpretation to the local range over which the active solution structure remains unchanged.", "uses": [ { "entrySlug": "chapter-22-data-analysis-and-insights", "entryTitle": "Data Analysis and Insights", "excerpts": [ "A shadow price is the local improvement in the optimal objective from relaxing a binding constraint by one unit, while the relevant solution structure remains unchanged. In this example, local dual values are approximately 16.67 per additional labor unit and 6.67 per additional machine unit. That makes the first extra labor unit more valuable in the model, but it does not mean the organization should pay any price indefinitely. Shadow prices can change when a constraint stops binding, a different corner becomes optimal, integrality matters, or the model changes. [BB-C22-S23]" ] } ] }, { "source_id": "BB-C14-S07", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "Country and Institutional Screening", "authors": "World Bank", "year": 2025, "title": "Worldwide Governance Indicators: 2025 Revision", "venue": "World Bank Group", "source_type": "official international dataset and methodology", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.worldbank.org/en/publication/worldwide-governance-indicators", "doi": null, "claim_notes": "Official project page and 2025 methodology documentation inspected. Supports the six governance dimensions, coverage through 2024, uncertainty reporting, and the explicit usage caution that aggregate country indicators are too coarse for specific institutional or reform decisions. The chapter uses the dataset only as a screening input and requires country-, sector-, and transaction-specific evidence.", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C14-S08", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "Country-Specific Market Entry Research", "authors": "U.S. International Trade Administration", "year": "n.d.", "title": "Country Commercial Guides", "venue": "U.S. Department of Commerce", "source_type": "official government market guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.trade.gov/country-commercial-guides", "doi": null, "claim_notes": "Official guide index inspected. Supports using embassy and trade-specialist country guides as starting points for market conditions, political and economic context, selling channels, trade rules, standards, business customs, and entry considerations across more than 125 countries. The chapter states that these guides are neither legal opinions nor proof of market attractiveness.", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C14-S09", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "International Personal-Data Transfers", "authors": "European Commission", "year": "n.d.", "title": "What Rules Apply if My Organisation Transfers Data Outside the EU?", "venue": "European Commission", "source_type": "official regulatory guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://commission.europa.eu/law/law-topic/data-protection/rules-business-and-organisations/obligations/what-rules-apply-if-my-organisation-transfers-data-outside-eu_en", "doi": null, "claim_notes": "Official European Commission guidance inspected. Supports the narrow statement that GDPR protection continues to apply to qualifying personal-data transfers outside the EU and that transfers require an applicable mechanism or condition, including adequacy or appropriate safeguards. Specific applicability and transfer design remain matters for qualified privacy and legal owners.", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "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]", "| 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] |" ] } ] }, { "source_id": "BB-C14-S10", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "Sanctions Compliance Risk Management", "authors": "U.S. Department of the Treasury, Office of Foreign Assets Control", "year": 2019, "title": "A Framework for OFAC Compliance Commitments", "venue": "Office of Foreign Assets Control", "source_type": "official regulator compliance framework", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://ofac.treasury.gov/media/16331/download", "doi": null, "claim_notes": "Official OFAC framework inspected. Supports a risk-based sanctions compliance program involving management commitment, risk assessment, internal controls, testing or audit, and training, including attention to clients, suppliers, business partners, and counterparties. It does not determine whether a particular transaction is prohibited or authorized.", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "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]", "| 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] |" ] } ] }, { "source_id": "BB-C14-S11", "chapter_slugs": [ "chapter-14-go-to-market-strategy" ], "framework": "Responsible Business Conduct Due Diligence", "authors": "Organisation for Economic Co-operation and Development", "year": 2018, "title": "OECD Due Diligence Guidance for Responsible Business Conduct", "venue": "OECD Publishing", "source_type": "official international guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.oecd.org/en/topics/sub-issues/due-diligence-guidance-for-responsible-business-conduct.html", "doi": null, "claim_notes": "Official OECD guidance page inspected. Supports risk-based, ongoing due diligence for actual and potential adverse impacts across operations, supply chains, and business relationships, including labor rights, human rights, environment, bribery, and consumer interests. The chapter does not treat certification or partner status as a substitute for the firm's own due diligence.", "uses": [ { "entrySlug": "chapter-14-go-to-market-strategy", "entryTitle": "Go-to-Market Strategy", "excerpts": [ "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]", "| 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] |" ] } ] }, { "source_id": "BB-C05-S18", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Advertising Incrementality and Observational Measurement", "authors": "Gordon, B. R.; Zettelmeyer, F.; Bhargava, N.; Chapsky, D.", "year": 2019, "title": "A Comparison of Approaches to Advertising Measurement: Evidence from Big Field Experiments at Facebook", "venue": "Marketing Science, 38(2), 193-225", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://pubsonline.informs.org/doi/abs/10.1287/mksc.2018.1135", "doi": "10.1287/mksc.2018.1135", "claim_notes": "Official INFORMS record and full abstract inspected. The study compares multiple observational approaches with 15 randomized U.S. Facebook advertising experiments and finds that the observational methods often did not recover the experimental effects despite extensive covariates. Chapter 5 limits the inference to the studied setting and does not claim that all observational measurement always fails.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "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]", "| 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] |", "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]" ] } ] }, { "source_id": "BB-C05-S19", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Advertising Experiment Power and ROI Uncertainty", "authors": "Lewis, R. A.; Rao, J. M.", "year": 2015, "title": "The Unfavorable Economics of Measuring the Returns to Advertising", "venue": "The Quarterly Journal of Economics, 130(4), 1941-1973", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://academic.oup.com/qje/article-abstract/130/4/1941/1914592", "doi": "10.1093/qje/qjv023", "claim_notes": "Official Oxford Academic record and full abstract inspected. Twenty-five large field experiments show that volatile individual sales and small advertising effects can make precise advertising ROI estimation costly or infeasible. Chapter 5 does not generalize the study's numeric confidence intervals or sample requirements into a universal rule.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "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]", "| 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] |" ] } ] }, { "source_id": "BB-C05-S20", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Marketing Mix Modeling and Experimental Calibration", "authors": "Google Meridian Team", "year": 2026, "title": "An Introduction to Meridian and Model Configuration", "venue": "Google for Developers", "source_type": "official open-source method documentation", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://developers.google.com/meridian/docs/basics/meridian-introduction", "doi": null, "claim_notes": "Current official documentation inspected for KPI, media and control inputs; lag and saturation assumptions; posterior uncertainty; response curves; ROI and marginal ROI; scenario optimization; and experiment-informed calibration. Chapter 5 states that implementation and calibration features do not independently validate causal assumptions or a focal model.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "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]", "| 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] |", "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]" ] } ] }, { "source_id": "BB-C05-S22", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Customer-Based Brand Equity", "authors": "Keller, K. L.", "year": 1993, "title": "Conceptualizing, Measuring, and Managing Customer-Based Brand Equity", "venue": "Journal of Marketing, 57(1), 1-22", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://journals.sagepub.com/doi/abs/10.1177/002224299305700101", "doi": "10.1177/002224299305700101", "claim_notes": "Official journal record and abstract inspected. Keller defines customer-based brand equity through differential customer response to marketing and conceptualizes brand knowledge through awareness and image or associations. Chapter 5 does not equate a survey score with financial value.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "- 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]" ] } ] }, { "source_id": "BB-C05-S23", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Revenue Premium as a Brand-Equity Outcome", "authors": "Ailawadi, K. L.; Lehmann, D. R.; Neslin, S. A.", "year": 2003, "title": "Revenue Premium as an Outcome Measure of Brand Equity", "venue": "Journal of Marketing, 67(4), 1-17", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://business.columbia.edu/sites/default/files-efs/pubfiles/537/revenue%20premium.pdf", "doi": "10.1509/jmkg.67.4.1.18688", "claim_notes": "Full author-institution-hosted article inspected. The authors propose and empirically test revenue premium relative to private label as a product-market brand-equity measure in packaged-goods categories. Chapter 5 requires a justified comparator and does not assume transferability to every category or business model.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "- 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]" ] } ] }, { "source_id": "BB-C05-S24", "chapter_slugs": [ "chapter-05-marketing-and-customer-analytics" ], "framework": "Market-Based Assets and Shareholder Value", "authors": "Srivastava, R. K.; Shervani, T. A.; Fahey, L.", "year": 1998, "title": "Market-Based Assets and Shareholder Value: A Framework for Analysis", "venue": "Journal of Marketing, 62(1), 2-18", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://journals.sagepub.com/doi/10.1177/002224299806200102", "doi": "10.1177/002224299806200102", "claim_notes": "Official metadata and article framework inspected. The paper connects market-based assets with cash-flow acceleration, level, vulnerability and volatility, and residual value. Chapter 5 presents those links as a falsifiable evidence chain and not a direct brand-valuation formula.", "uses": [ { "entrySlug": "chapter-05-marketing-and-customer-analytics", "entryTitle": "Marketing and Customer Analytics", "excerpts": [ "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]", "- 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]" ] } ] }, { "source_id": "BB-C06-S13", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Forecast Evaluation and Time-Series Cross-Validation", "authors": "Hyndman, R. J.; Athanasopoulos, G.", "year": 2021, "title": "Forecasting: Principles and Practice, 3rd edition", "venue": "OTexts", "source_type": "open authoritative methods textbook", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://otexts.com/fpp3/accuracy.html", "doi": null, "claim_notes": "Full open sections on point accuracy and time-series cross-validation inspected. They distinguish forecast errors from residuals, define MAE, RMSE, MAPE and scaled errors, warn about percentage errors near zero, and use rolling forecast origins without future leakage. Chapter 6 labels WAPE as a constructed exercise metric rather than attributing it to this source.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]" ] } ] }, { "source_id": "BB-C06-S14", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "M4 Forecasting Competition", "authors": "Makridakis, S.; Spiliotis, E.; Assimakopoulos, V.", "year": 2020, "title": "The M4 Competition: 100,000 Time Series and 61 Forecasting Methods", "venue": "International Journal of Forecasting, 36(1), 54-74", "source_type": "peer-reviewed open-access article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sciencedirect.com/science/article/pii/S0169207019301128", "doi": "10.1016/j.ijforecast.2019.04.014", "claim_notes": "Official open-access article record and abstract inspected. M4 compares 61 methods across 100,000 series and evaluates point and prediction-interval forecasts. Chapter 6 uses it to support large-scale out-of-sample benchmarking, not a universal winning model for the focal company.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C06-S15", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "S&OP Coordination Mechanisms", "authors": "Tuomikangas, N.; Kaipia, R.", "year": 2014, "title": "A Coordination Framework for Sales and Operations Planning (S&OP): Synthesis from the Literature", "venue": "International Journal of Production Economics, 154, 243-262", "source_type": "peer-reviewed systematic literature synthesis", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://research.aalto.fi/en/publications/a-coordination-framework-for-sales-and-operations-planning-sampop/", "doi": "10.1016/j.ijpe.2014.04.026", "claim_notes": "Official Aalto research record and bibliographic metadata inspected. The article synthesizes S&OP as a coordination framework using multiple mechanisms. Chapter 6's exact closed-loop stages, decision rights, and outputs are explicitly an original managerial synthesis.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C06-S16", "chapter_slugs": [ "chapter-06-operations-and-supply-chain" ], "framework": "Sales and Operations Planning", "authors": "APICS", "year": 2014, "title": "APICS Introduction to Sales and Operations Planning (S&OP)", "venue": "APICS educational handout", "source_type": "official practitioner guidance", "quality_tier": "tier_2", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://wc.ascm.org/images/downloads/PDM_s/apics_introduction_to_s_op_handout.pdf", "doi": null, "claim_notes": "Full two-page APICS handout inspected. It defines S&OP as integrating customer-focused marketing and new/existing product plans with sales, development, manufacturing, sourcing, supply-chain and financial plans; it also identifies deviation reporting, resource checks, executive trade-off resolution, and continuous updates. Chapter 6 does not claim that running the process guarantees performance.", "uses": [ { "entrySlug": "chapter-06-operations-and-supply-chain", "entryTitle": "Operations and Supply Chain", "excerpts": [ "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]", "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]", "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]" ] } ] }, { "source_id": "BB-C17-S12", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Sustainability Boundary - Product Lifecycle Accounting", "authors": "World Resources Institute; World Business Council for Sustainable Development", "year": 2011, "title": "Product Life Cycle Accounting and Reporting Standard", "venue": "Greenhouse Gas Protocol", "source_type": "official product lifecycle accounting standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://ghgprotocol.org/sites/default/files/standards/Product-Life-Cycle-Accounting-Reporting-Standard_041613.pdf", "doi": null, "claim_notes": "Official GHG Protocol standard inspected 2026-07-11. Supports product lifecycle goal and scope, functional unit, boundary, inventory, allocation, data-quality, uncertainty, reporting, and reduction-accounting concepts. It does not provide a verified footprint for a digital service, cover every environmental impact, or approve a marketing claim.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "The digital-service system boundary has no single, context-free environmental footprint. Its measured result depends on the decision question, functional unit, geography, time period, service demand, system boundary, allocation method, electricity and water conditions, asset lifetime, data quality, and counterfactual. The GHG Protocol Product Standard uses a product-lifecycle approach, while ITU-T L.1410 provides an ICT-specific methodology for goods, networks, and services. These are measurement frameworks, not proof that one architecture, vendor, model, or transformation is “sustainable.” [BB-C17-S12] [BB-C17-S13]", "Start with a functional unit that describes the service delivered—for example, one completed customer transaction at an agreed quality level, one active user-month, or one model-supported decision under defined performance conditions. Report the organization's absolute impact as well as an intensity per functional unit. An intensity improvement can coexist with rising total energy, water, emissions, material demand, or waste when service volume grows. [BB-C17-S12] [BB-C17-S13]", "| Supply chain and logistics | Raw-material extraction and processing, semiconductor and equipment suppliers, construction, transport, purchased services, cloud and colocation providers, and upstream electricity and water. | Map material suppliers and service providers, geography, contractual data rights, emission factors, water context, allocation, and missing tiers. A provider's operational dashboard rarely represents the customer's full lifecycle or value-chain boundary. [BB-C17-S12] [BB-C17-S17] |", "3. Draw the boundary. Mark included lifecycle stages, organizational and supplier roles, data centers, networks, end-user devices, shared assets, excluded processes, and cut-off rules. The boundary should be reproducible, not optimized after seeing the result. [BB-C17-S12] [BB-C17-S13]", "Figure 17.5. Digital-service lifecycle boundary, decision loop, and claims gate. This author-created visual places operational data-center impacts inside a broader system of hardware, supply chain, networks, devices, use, and end of life. It also separates an internal decision estimate from an external environmental claim and makes demand rebound visible. It is a boundary prompt, not a calculation method or verified footprint. [BB-C17-S12] [BB-C17-S13] [BB-C17-S14] [BB-C17-S17] [BB-C17-S19] [BB-C17-S20]", "Source note: Author-created synthesis of lifecycle, value-chain, ICT-boundary, energy-scenario, rebound, and environmental-claims concepts from [BB-C17-S12] through [BB-C17-S20]. ITU-T L.1450 [BB-C17-S21] additionally supports treating operational energy and embodied lifecycle emissions within an ICT-sector boundary. No external quantitative data are plotted." ] } ] }, { "source_id": "BB-C17-S13", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Sustainability Boundary - ICT Goods, Networks, and Services", "authors": "International Telecommunication Union", "year": 2024, "title": "Recommendation ITU-T L.1410 (11/2024): Methodology for Environmental Life Cycle Assessments of Information and Communication Technology Goods, Networks and Services", "venue": "ITU Telecommunication Standardization Sector", "source_type": "international technical standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.itu.int/rec/t-rec-l.1410", "doi": null, "claim_notes": "Official current ITU recommendation record inspected 2026-07-11. Supports an ICT-specific lifecycle boundary spanning goods, networks, and services, with goal, scope, allocation, use-profile, data, and reporting choices. It is a methodology, not a universal impact number or a conclusion about a particular architecture, vendor, or service.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "The digital-service system boundary has no single, context-free environmental footprint. Its measured result depends on the decision question, functional unit, geography, time period, service demand, system boundary, allocation method, electricity and water conditions, asset lifetime, data quality, and counterfactual. The GHG Protocol Product Standard uses a product-lifecycle approach, while ITU-T L.1410 provides an ICT-specific methodology for goods, networks, and services. These are measurement frameworks, not proof that one architecture, vendor, model, or transformation is “sustainable.” [BB-C17-S12] [BB-C17-S13]", "Start with a functional unit that describes the service delivered—for example, one completed customer transaction at an agreed quality level, one active user-month, or one model-supported decision under defined performance conditions. Report the organization's absolute impact as well as an intensity per functional unit. An intensity improvement can coexist with rising total energy, water, emissions, material demand, or waste when service volume grows. [BB-C17-S12] [BB-C17-S13]", "| Materials, components, and manufacturing | Chips, servers, storage, network equipment, cooling and power equipment, buildings, batteries, displays, user devices, packaging, and manufacturing yield. These are commonly described as embodied or capital-goods impacts because they occur before or around operation rather than only at the point of electricity use. | Obtain supplier product, bill-of-material, manufacturing, lifetime, repairability, and chain-of-custody data where decision-useful. Allocate shared equipment transparently and test lifetime and utilization assumptions. ITU methods explicitly treat lifecycle impacts and embodied emissions as part of ICT assessment. [BB-C17-S13] [BB-C17-S21] |", "| Networks and data transfer | Access, metro, core, content-delivery, enterprise, mobile or fixed networks, routing, retransmission, and shared network equipment. | Define data volume, distance or topology if material, access technology, allocation basis, utilization, equipment lifetime, and uncertainty. Do not assume network impact is zero because a cloud invoice omits it. ITU-T L.1410 includes ICT networks as well as goods and services. [BB-C17-S13] |", "3. Draw the boundary. Mark included lifecycle stages, organizational and supplier roles, data centers, networks, end-user devices, shared assets, excluded processes, and cut-off rules. The boundary should be reproducible, not optimized after seeing the result. [BB-C17-S12] [BB-C17-S13]", "Figure 17.5. Digital-service lifecycle boundary, decision loop, and claims gate. This author-created visual places operational data-center impacts inside a broader system of hardware, supply chain, networks, devices, use, and end of life. It also separates an internal decision estimate from an external environmental claim and makes demand rebound visible. It is a boundary prompt, not a calculation method or verified footprint. [BB-C17-S12] [BB-C17-S13] [BB-C17-S14] [BB-C17-S17] [BB-C17-S19] [BB-C17-S20]" ] } ] }, { "source_id": "BB-C17-S14", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Sustainability Boundary - AI and Data-Center Electricity Scenarios", "authors": "International Energy Agency", "year": 2025, "title": "Energy and AI", "venue": "International Energy Agency", "source_type": "official intergovernmental analysis", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.iea.org/reports/energy-and-ai", "doi": null, "claim_notes": "Official IEA report and scenario pages inspected 2026-07-11. Supports scenario-based treatment of AI and data-center electricity demand, accelerated and conventional servers, other IT equipment, cooling and infrastructure, efficiency, geography, adoption, and uncertainty. It does not supply a universal per-query, per-model, site, company, or future-demand factor.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "| Service demand and software | User journeys, model training or adaptation, inference, storage, data movement, redundancy, testing, idle capacity, quality and latency requirements, and workload growth. | Record transactions, tokens or compute units where relevant, data retained and moved, utilization, quality targets, and forecast demand. Do not use one query or training estimate as a universal impact number; architectures, workloads, locations, and utilization differ. IEA scenarios also show that efficiency and adoption assumptions materially change projected data-center demand. [BB-C17-S14] |", "Figure 17.5. Digital-service lifecycle boundary, decision loop, and claims gate. This author-created visual places operational data-center impacts inside a broader system of hardware, supply chain, networks, devices, use, and end of life. It also separates an internal decision estimate from an external environmental claim and makes demand rebound visible. It is a boundary prompt, not a calculation method or verified footprint. [BB-C17-S12] [BB-C17-S13] [BB-C17-S14] [BB-C17-S17] [BB-C17-S19] [BB-C17-S20]" ] } ] }, { "source_id": "BB-C17-S15", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Sustainability Boundary - U.S. Data-Center Energy and Water", "authors": "Shehabi, A.; Smith, S. J.; Hubbard, A.; Newkirk, A.; Lei, N.; Siddik, M. A. B.; Holecek, B.; Koomey, J. G.; Masanet, E. R.; Sartor, D. A.", "year": 2024, "title": "2024 United States Data Center Energy Usage Report", "venue": "Lawrence Berkeley National Laboratory", "source_type": "government research report", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://eta-publications.lbl.gov/publications/2024-lbnl-data-center-energy-usage-report", "doi": "10.71468/P1WC7Q", "claim_notes": "Official LBNL record and report inspected 2026-07-11. Supports the need for facility, equipment, electricity, cooling, power-source, direct and electricity-related water, scenario, and limitations data in U.S. data-center analysis. Its U.S. historical and scenario estimates are not universal workload, query, provider, site, water, carbon, or future-demand factors.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "| Data-center operation | IT electricity, cooling, power conversion and distribution, backup systems, facility overhead, refrigerants where relevant, direct water, and water associated with electricity generation. | Collect facility, workload, power, cooling, water-withdrawal and water-consumption, grid, backup, and equipment data at the location and interval needed for the decision. Berkeley Lab's U.S. report demonstrates why energy and water estimates require scenarios, infrastructure characteristics, and explicit limitations; its U.S. aggregate estimates are not a universal factor for a workload or site. [BB-C17-S15] |" ] } ] }, { "source_id": "BB-C17-S16", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Sustainability Boundary - Purchased Electricity Accounting", "authors": "World Resources Institute; World Business Council for Sustainable Development", "year": 2015, "title": "GHG Protocol Scope 2 Guidance: An Amendment to the GHG Protocol Corporate Standard", "venue": "Greenhouse Gas Protocol", "source_type": "official greenhouse-gas accounting guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://ghgprotocol.org/sites/default/files/standards/Scope%202%20Guidance_Final_Sept26.pdf", "doi": null, "claim_notes": "Official Scope 2 Guidance and current FAQ inspected 2026-07-11. Supports distinct location-based and market-based methods, data hierarchies, quality criteria, and labeled dual reporting where applicable. GHG Protocol is revising Scope 2 guidance, so current requirements must be rechecked; neither method alone describes every physical, contractual, or consequential electricity effect.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "2. Greenhouse gases: State whether the inventory is organizational, product/service lifecycle, or project/consequential. For purchased electricity, location-based and market-based Scope 2 results answer different questions and may both be required under the selected reporting framework; contractual instruments do not erase the physical grid context. [BB-C17-S16]", "5. Calculate more than one view. Report absolute totals and functional-unit intensities; operational and embodied components; direct and value-chain components; and, where applicable, both location-based and market-based electricity emissions. Keep avoided or enabled emissions separate from the footprint inventory and disclose the counterfactual. [BB-C17-S16] [BB-C17-S17]" ] } ] }, { "source_id": "BB-C17-S17", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Sustainability Boundary - Corporate Value Chain", "authors": "World Resources Institute; World Business Council for Sustainable Development", "year": 2011, "title": "Corporate Value Chain (Scope 3) Accounting and Reporting Standard", "venue": "Greenhouse Gas Protocol", "source_type": "official value-chain accounting standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://ghgprotocol.org/corporate-value-chain-scope-3-standard", "doi": null, "claim_notes": "Official GHG Protocol standard page and standard inspected 2026-07-11. Supports upstream and downstream value-chain categories, including purchased goods and services, capital goods, use of sold products, and end-of-life treatment, plus inventory boundaries and data-quality needs. It does not make all Scope 3 categories material for every decision, and avoided emissions are reported separately from the inventory.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "| End-user devices and use | Device manufacture, charging, display and processor use, local computation, peripherals, replacement, repair, and accessibility or quality settings needed to use the service. | Define supported device mix, active time, energy modes, useful lifetime, ownership boundary, and whether user electricity and device production are included. GHG Protocol value-chain guidance includes downstream use and end-of-life categories; exclusions still require disclosure. [BB-C17-S17] |", "| Supply chain and logistics | Raw-material extraction and processing, semiconductor and equipment suppliers, construction, transport, purchased services, cloud and colocation providers, and upstream electricity and water. | Map material suppliers and service providers, geography, contractual data rights, emission factors, water context, allocation, and missing tiers. A provider's operational dashboard rarely represents the customer's full lifecycle or value-chain boundary. [BB-C17-S12] [BB-C17-S17] |", "5. Calculate more than one view. Report absolute totals and functional-unit intensities; operational and embodied components; direct and value-chain components; and, where applicable, both location-based and market-based electricity emissions. Keep avoided or enabled emissions separate from the footprint inventory and disclose the counterfactual. [BB-C17-S16] [BB-C17-S17]", "Figure 17.5. Digital-service lifecycle boundary, decision loop, and claims gate. This author-created visual places operational data-center impacts inside a broader system of hardware, supply chain, networks, devices, use, and end of life. It also separates an internal decision estimate from an external environmental claim and makes demand rebound visible. It is a boundary prompt, not a calculation method or verified footprint. [BB-C17-S12] [BB-C17-S13] [BB-C17-S14] [BB-C17-S17] [BB-C17-S19] [BB-C17-S20]" ] } ] }, { "source_id": "BB-C17-S18", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Sustainability Boundary - Hardware End of Life and E-waste", "authors": "International Telecommunication Union; United Nations Institute for Training and Research", "year": 2024, "title": "The Global E-waste Monitor 2024", "venue": "International Telecommunication Union and UNITAR", "source_type": "official intergovernmental report", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.itu.int/pub/D-GEN-E_WASTE.01", "doi": null, "claim_notes": "Official ITU publication record and report inspected 2026-07-11. Supports treating discarded electrical and electronic equipment as a distinct and changing material stream and the need for generation, collection, recycling, material-recovery, policy, and data tracking. It is not a device-, supplier-, company-, or project-specific impact factor.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "| Maintenance, reuse, and end of life | Spares, repair, refurbishment, resale, redeployment, secure data destruction, take-back, recycling, hazardous handling, and disposal. | Record age, failure and replacement rates, repair constraints, residual value, destination, custody, certified processing, and recovered material. The Global E-waste Monitor treats discarded electrical and electronic equipment as a distinct, rapidly changing material stream and emphasizes data, collection, recycling, and policy gaps. [BB-C17-S18] |" ] } ] }, { "source_id": "BB-C17-S19", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Sustainability Boundary - Rebound Effects", "authors": "UK Department for Energy Security and Net Zero", "year": 2026, "title": "Industrial Energy and Resource Efficiency Rebound Effects", "venue": "GOV.UK, Ref. RAF011/2425", "source_type": "official government research report", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.gov.uk/government/publications/industrial-energy-and-resource-efficiency-rebound-effects", "doi": null, "claim_notes": "Complete 118-page official report inspected 2026-07-11. Supports rebound as the possibility that expected efficiency-based savings are partly or wholly offset through induced consumption and shows why the magnitude depends on boundary, sector, mechanism, and evidence. It does not provide a universal rebound percentage for digital or AI services; the chapter therefore requires demand scenarios and empirical review rather than assuming backfire.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "6. Test sensitivity, scale, and rebound. Vary demand, utilization, asset life, grid mix, water conditions, model or workload size, hardware replacement, allocation, and supplier factors. Efficiency can lower cost or latency and stimulate more use, partially offsetting expected savings. Rebound is an empirical possibility, not a presumption that all efficiency gains disappear; the official UK DESNZ review supports treating the magnitude and mechanisms as context-dependent rather than using a universal percentage. [BB-C17-S19]", "Figure 17.5. Digital-service lifecycle boundary, decision loop, and claims gate. This author-created visual places operational data-center impacts inside a broader system of hardware, supply chain, networks, devices, use, and end of life. It also separates an internal decision estimate from an external environmental claim and makes demand rebound visible. It is a boundary prompt, not a calculation method or verified footprint. [BB-C17-S12] [BB-C17-S13] [BB-C17-S14] [BB-C17-S17] [BB-C17-S19] [BB-C17-S20]" ] } ] }, { "source_id": "BB-C17-S20", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Sustainability Boundary - Environmental Claims Gate", "authors": "Federal Trade Commission", "year": 2012, "title": "Guides for the Use of Environmental Marketing Claims (Green Guides), 16 CFR Part 260", "venue": "Federal Trade Commission", "source_type": "official regulator guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.ftc.gov/legal-library/browse/rules/green-guides", "doi": null, "claim_notes": "Official FTC Green Guides page, rule text, and business summary inspected 2026-07-11. Supports caution against broad, unqualified general environmental-benefit claims in the United States and the need for competent, reliable evidence and clear qualifications for covered claims. The guides do not certify a claim, cover every jurisdiction, or replace current legal review.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "In the United States, the FTC Green Guides caution against broad, unqualified general environmental-benefit claims; other jurisdictions and sector rules differ and change. The guides do not certify a claim, and a completed footprint does not itself establish that the words, comparison, disclosure, or implied message are lawful or non-misleading. [BB-C17-S20] Connect the claims gate to Chapter 14 and the governance and legal boundaries in Chapter 2.", "Figure 17.5. Digital-service lifecycle boundary, decision loop, and claims gate. This author-created visual places operational data-center impacts inside a broader system of hardware, supply chain, networks, devices, use, and end of life. It also separates an internal decision estimate from an external environmental claim and makes demand rebound visible. It is a boundary prompt, not a calculation method or verified footprint. [BB-C17-S12] [BB-C17-S13] [BB-C17-S14] [BB-C17-S17] [BB-C17-S19] [BB-C17-S20]", "Source note: Author-created synthesis of lifecycle, value-chain, ICT-boundary, energy-scenario, rebound, and environmental-claims concepts from [BB-C17-S12] through [BB-C17-S20]. ITU-T L.1450 [BB-C17-S21] additionally supports treating operational energy and embodied lifecycle emissions within an ICT-sector boundary. No external quantitative data are plotted." ] } ] }, { "source_id": "BB-C17-S21", "chapter_slugs": [ "chapter-17-leading-digital-transformation" ], "framework": "Digital Sustainability Boundary - Current ICT Sector Lifecycle Method", "authors": "International Telecommunication Union", "year": 2025, "title": "Recommendation ITU-T L.1450 (12/2025): Methodologies for the Assessment of the Environmental Impact of the Information and Communication Technology Sector", "venue": "ITU Telecommunication Standardization Sector", "source_type": "international technical standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.itu.int/epublications/publication/itu-t-l-1450-2025-12-methodologies-for-the-assessment-of-the-environmental-impact-of-the-information-and-communication-technology-sector", "doi": null, "claim_notes": "Official current ITU recommendation inspected 2026-07-11. Supports ICT-sector lifecycle assessment that includes operational energy and embodied lifecycle emissions, goal and scope, goods/networks/services perspectives, boundaries, data quality, cut-offs, and absolute and relative footprints. It does not establish a company or service footprint or justify the report's illustrative sector percentage as a universal current value.", "uses": [ { "entrySlug": "chapter-17-leading-digital-transformation", "entryTitle": "Leading Digital Transformation", "excerpts": [ "| Materials, components, and manufacturing | Chips, servers, storage, network equipment, cooling and power equipment, buildings, batteries, displays, user devices, packaging, and manufacturing yield. These are commonly described as embodied or capital-goods impacts because they occur before or around operation rather than only at the point of electricity use. | Obtain supplier product, bill-of-material, manufacturing, lifetime, repairability, and chain-of-custody data where decision-useful. Allocate shared equipment transparently and test lifetime and utilization assumptions. ITU methods explicitly treat lifecycle impacts and embodied emissions as part of ICT assessment. [BB-C17-S13] [BB-C17-S21] |", "Source note: Author-created synthesis of lifecycle, value-chain, ICT-boundary, energy-scenario, rebound, and environmental-claims concepts from [BB-C17-S12] through [BB-C17-S20]. ITU-T L.1450 [BB-C17-S21] additionally supports treating operational energy and embodied lifecycle emissions within an ICT-sector boundary. No external quantitative data are plotted." ] } ] }, { "source_id": "BB-C21-S19", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Human-Centred Design", "authors": "International Organization for Standardization", "year": 2019, "title": "ISO 9241-210:2019 Ergonomics of Human-System Interaction — Part 210: Human-Centred Design for Interactive Systems", "venue": "ISO International Standard", "source_type": "official standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.iso.org/standard/77520.html", "doi": null, "claim_notes": "Official ISO public record inspected 2026-07-11. It confirms the current 2019 second edition, reconfirmed in 2025, and its high-level scope: requirements and recommendations for human-centred design principles and activities throughout the life cycle of interactive systems. The chapter uses no paywalled clause text and makes no claim of ISO conformance.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Human-Centered and Service Design Module [BB-C21-S19] [BB-C21-S20] [BB-C21-S21] [BB-C21-S22] [BB-C21-S23] [BB-C21-S24] [BB-C21-S25] [BB-C21-S26] [BB-C21-S27]", "An interface is only one part of a service. A customer outcome can also depend on guidance, identity checks, staff judgment, queues, handoffs, notifications, support, records, vendors, and recovery when something goes wrong. Human-centered design keeps design grounded in people and their context across the system life cycle; service design makes the visible and hidden delivery system inspectable. ISO 9241-210:2019 provides the current high-level standard for managing human-centered design of interactive systems, while service-blueprinting research provides a customer-grounded way to visualize dynamic service processes. [BB-C21-S19] [BB-C21-S25]" ] } ] }, { "source_id": "BB-C21-S20", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Accessibility-Led User Involvement", "authors": "World Wide Web Consortium Web Accessibility Initiative", "year": 2010, "title": "Involving Users in Web Projects for Better, Easier Accessibility", "venue": "W3C Web Accessibility Initiative", "source_type": "official web guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.w3.org/WAI/planning/involving-users/", "doi": null, "claim_notes": "Supports involving people with disabilities and older people early and throughout design, obtaining a range of perspectives, and combining user involvement with accessibility standards. It does not support treating user testing as a substitute for standards evaluation or legal review.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Human-Centered and Service Design Module [BB-C21-S19] [BB-C21-S20] [BB-C21-S21] [BB-C21-S22] [BB-C21-S23] [BB-C21-S24] [BB-C21-S25] [BB-C21-S26] [BB-C21-S27]", "Accessibility-led research starts before a prototype exists. Involve people with disabilities and older people with accessibility needs early and throughout the work, and combine their experience with technical standards and expert evaluation. User involvement can reveal real-world barriers, but it is not a substitute for standards testing or legal review. [BB-C21-S20]", "Remedy 1: Use the Human-Centered and Service Design module to widen recruitment and link observations to needs rather than feature votes. [BB-C21-S20] [BB-C21-S21] [BB-C21-S24]" ] } ] }, { "source_id": "BB-C21-S21", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Inclusive Research Recruitment", "authors": "UK Government Digital Service User Research Community", "year": 2020, "title": "Finding Participants for User Research", "venue": "GOV.UK Service Manual", "source_type": "official practitioner guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.gov.uk/service-manual/user-research/find-user-research-participants", "doi": null, "claim_notes": "Supports recruiting actual or likely users across relevant access needs, digital skills, literacy, and other characteristics; using varied recruitment routes; arranging accommodations; obtaining permission for invitations; minimizing participant data; and reducing recruitment bias. Government-specific examples and participant-count suggestions are not presented as universal requirements.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Human-Centered and Service Design Module [BB-C21-S19] [BB-C21-S20] [BB-C21-S21] [BB-C21-S22] [BB-C21-S23] [BB-C21-S24] [BB-C21-S25] [BB-C21-S26] [BB-C21-S27]", "Use several recruitment routes where one channel would systematically omit people. Ask participants how they want to be contacted, what accommodations or formats they need, whether they prefer their own assistive technology, and whether location or remote setup creates barriers. Do not repeatedly burden the same convenient participants or use employees as a proxy for external users without a justified research question. GOV.UK's official research guidance supports recruiting actual or likely users, disabled participants, people with limited digital skills or literacy, and people who may need help, while recognizing that recruitment method itself can introduce bias. [BB-C21-S21]", "Do not turn one vivid quote into a universal persona, count repeated comments as if convenience research were a representative survey, or erase differences among access needs. A decision-grade synthesis links every proposed need to evidence and every roadmap item back to a need or authorized non-user requirement. [BB-C21-S21] [BB-C21-S24] [BB-C21-S27]", "Remedy 1: Use the Human-Centered and Service Design module to widen recruitment and link observations to needs rather than feature votes. [BB-C21-S20] [BB-C21-S21] [BB-C21-S24]" ] } ] }, { "source_id": "BB-C21-S22", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Research Ethics", "authors": "National Commission for the Protection of Human Subjects of Biomedical and Behavioral Research", "year": 1979, "title": "The Belmont Report: Ethical Principles and Guidelines for the Protection of Human Subjects of Research", "venue": "U.S. Department of Health and Human Services, Office for Human Research Protections", "source_type": "official ethics report", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.hhs.gov/ohrp/regulations-and-policy/belmont-report/read-the-belmont-report/index.html", "doi": null, "claim_notes": "Supports respect for persons, beneficence, justice, informed consent, risk-benefit assessment, and fair subject selection for human-subjects research. The chapter explicitly states that not every product-research activity is regulated human-subjects research and requires the organization's qualified ethics, legal, and privacy owners to determine applicable review.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Human-Centered and Service Design Module [BB-C21-S19] [BB-C21-S20] [BB-C21-S21] [BB-C21-S22] [BB-C21-S23] [BB-C21-S24] [BB-C21-S25] [BB-C21-S26] [BB-C21-S27]", "Before recruiting, obtain an explicit determination from the authorized owner about whether the activity is regulated research, requires an institutional ethics review, or triggers sector, employment, education, health, child, biometric, recording, cross-border, or other rules. The Belmont Report's principles—respect for persons, beneficence, and justice—support informed consent, risk-benefit assessment, and fair participant selection in human-subjects research; they are an ethical floor for reflection, not a substitute for applicable review. [BB-C21-S22]" ] } ] }, { "source_id": "BB-C21-S23", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Privacy Risk Management", "authors": "National Institute of Standards and Technology", "year": 2020, "title": "NIST Privacy Framework: A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "venue": "NIST Cybersecurity White Paper", "source_type": "official framework", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.nist.gov/document/nist-privacy-frameworkv10pdf", "doi": "10.6028/NIST.CSWP.01162020", "claim_notes": "Supports managing privacy risks arising from data processing through Identify-P, Govern-P, Control-P, Communicate-P, and Protect-P and considering impacts on directly or indirectly affected individuals. It is a flexible risk-management tool, not a universal legal-compliance certificate.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Human-Centered and Service Design Module [BB-C21-S19] [BB-C21-S20] [BB-C21-S21] [BB-C21-S22] [BB-C21-S23] [BB-C21-S24] [BB-C21-S25] [BB-C21-S26] [BB-C21-S27]", "Do not promise anonymity when voices, video, rare attributes, or contextual details can identify someone. NIST's Privacy Framework supports managing privacy risk arising from data processing through Identify-P, Govern-P, Control-P, Communicate-P, and Protect-P and considering impacts on people directly or indirectly affected. It is a flexible risk-management framework, not a universal certificate of legal compliance. [BB-C21-S23]" ] } ] }, { "source_id": "BB-C21-S24", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Research Synthesis", "authors": "UK Government Digital Service User Research Community", "year": 2016, "title": "Analyse a Research Session", "venue": "GOV.UK Service Manual", "source_type": "official practitioner guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.gov.uk/service-manual/user-research/analyse-a-research-session", "doi": null, "claim_notes": "Supports extracting observations, grouping them, determining findings, involving observers to reduce individual bias, connecting findings to next actions or research, and sharing the synthesis. The chapter's observation-to-decision chain is an author-created traceability structure.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Human-Centered and Service Design Module [BB-C21-S19] [BB-C21-S20] [BB-C21-S21] [BB-C21-S22] [BB-C21-S23] [BB-C21-S24] [BB-C21-S25] [BB-C21-S26] [BB-C21-S27]", "Analyse soon after research, include observers and cross-functional owners, retain contradictory and negative cases, and distinguish prevalence from salience. GOV.UK guidance recommends extracting observations, grouping them, determining findings, deciding actions, and sharing the synthesis; its user-needs guidance emphasizes evidence-based needs framed around the user's problem rather than a preferred solution. [BB-C21-S24] [BB-C21-S27]", "Do not turn one vivid quote into a universal persona, count repeated comments as if convenience research were a representative survey, or erase differences among access needs. A decision-grade synthesis links every proposed need to evidence and every roadmap item back to a need or authorized non-user requirement. [BB-C21-S21] [BB-C21-S24] [BB-C21-S27]", "Remedy 1: Use the Human-Centered and Service Design module to widen recruitment and link observations to needs rather than feature votes. [BB-C21-S20] [BB-C21-S21] [BB-C21-S24]" ] } ] }, { "source_id": "BB-C21-S25", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Service Blueprinting", "authors": "Bitner, M. J.; Ostrom, A. L.; Morgan, F. N.", "year": 2008, "title": "Service Blueprinting: A Practical Technique for Service Innovation", "venue": "California Management Review, 50(3), 66-94", "source_type": "peer-reviewed article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://asu.elsevierpure.com/en/publications/service-blueprinting-a-practical-technique-for-service-innovation/", "doi": "10.2307/41166446", "claim_notes": "Supports service blueprinting as a customer-grounded visualization of dynamic service processes and documents its service-innovation use. Figure 21.2 is a new author-created teaching example; it does not reproduce the article's proprietary diagrams or imply permission beyond citation.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Human-Centered and Service Design Module [BB-C21-S19] [BB-C21-S20] [BB-C21-S21] [BB-C21-S22] [BB-C21-S23] [BB-C21-S24] [BB-C21-S25] [BB-C21-S26] [BB-C21-S27]", "An interface is only one part of a service. A customer outcome can also depend on guidance, identity checks, staff judgment, queues, handoffs, notifications, support, records, vendors, and recovery when something goes wrong. Human-centered design keeps design grounded in people and their context across the system life cycle; service design makes the visible and hidden delivery system inspectable. ISO 9241-210:2019 provides the current high-level standard for managing human-centered design of interactive systems, while service-blueprinting research provides a customer-grounded way to visualize dynamic service processes. [BB-C21-S19] [BB-C21-S25]", "A service blueprint aligns the customer journey with visible service interactions, hidden operational work, supporting systems or partners, and the physical or digital evidence users encounter. The line of visibility separates frontstage activity that a user can perceive from backstage activity; the line of internal interaction separates backstage delivery from supporting capabilities. Bitner, Ostrom, and Morgan describe blueprinting as a customer-grounded visualization technique for dynamic service processes and service innovation. [BB-C21-S25]", "Figure 21.3. Accessible service blueprint for a constructed lost-credential replacement service. This author-created process visual shows evidence, user actions, visible frontstage interactions, hidden backstage work, and support capabilities across four stages. It is an illustrative teaching model, not a depiction of an actual organization or a reproduction of the cited article's figures. [BB-C21-S25]", "Remedy 2: Blueprint the whole service, rehearse frontstage and backstage interactions, and assign every failure and recovery path to an owner. [BB-C21-S25]" ] } ] }, { "source_id": "BB-C21-S26", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Service Prototyping", "authors": "UK Government Digital Service Design Community", "year": 2016, "title": "Making Prototypes", "venue": "GOV.UK Service Manual", "source_type": "official practitioner guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.gov.uk/service-manual/design/making-prototypes", "doi": null, "claim_notes": "Supports using prototypes to explore, share, test, and discard design approaches before production commitment; choosing fidelity to fit the question; securing published prototypes; and not treating prototype code as production-ready, secure, or scalable.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Human-Centered and Service Design Module [BB-C21-S19] [BB-C21-S20] [BB-C21-S21] [BB-C21-S22] [BB-C21-S23] [BB-C21-S24] [BB-C21-S25] [BB-C21-S26] [BB-C21-S27]", "GOV.UK guidance supports using prototypes to explore and test alternatives before production commitment and warns that prototype code may lack the security and performance required for a live service. Protect access to realistic prototypes, do not use live personal data without explicit authority and safeguards, and never promote prototype code merely because the interface tested well. [BB-C21-S26]" ] } ] }, { "source_id": "BB-C21-S27", "chapter_slugs": [ "chapter-21-product-management-and-product-strategy" ], "framework": "Evidence-Based User Needs", "authors": "UK Government Digital Service User Research Community", "year": 2017, "title": "Learning About Users and Their Needs", "venue": "GOV.UK Service Manual", "source_type": "official practitioner guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs", "doi": null, "claim_notes": "Supports grounding user needs in research rather than stakeholder assumptions, framing needs around the user's problem rather than a preferred solution, considering service and support staff, validating needs over time, and maintaining traceability from needs to delivery artifacts.", "uses": [ { "entrySlug": "chapter-21-product-management-and-product-strategy", "entryTitle": "Product Management and Product Strategy", "excerpts": [ "Human-Centered and Service Design Module [BB-C21-S19] [BB-C21-S20] [BB-C21-S21] [BB-C21-S22] [BB-C21-S23] [BB-C21-S24] [BB-C21-S25] [BB-C21-S26] [BB-C21-S27]", "Analyse soon after research, include observers and cross-functional owners, retain contradictory and negative cases, and distinguish prevalence from salience. GOV.UK guidance recommends extracting observations, grouping them, determining findings, deciding actions, and sharing the synthesis; its user-needs guidance emphasizes evidence-based needs framed around the user's problem rather than a preferred solution. [BB-C21-S24] [BB-C21-S27]", "Do not turn one vivid quote into a universal persona, count repeated comments as if convenience research were a representative survey, or erase differences among access needs. A decision-grade synthesis links every proposed need to evidence and every roadmap item back to a need or authorized non-user requirement. [BB-C21-S21] [BB-C21-S24] [BB-C21-S27]" ] } ] }, { "source_id": "BB-C13-S10", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "Traditional Search Fund Cohort Evidence", "authors": "Kelly, P.; Heston, S.", "year": 2024, "title": "2024 Search Fund Study", "venue": "Stanford Graduate School of Business, Case E870", "source_type": "institutional cohort study", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.gsb.stanford.edu/faculty-research/case-studies/2024-search-fund-study", "doi": null, "claim_notes": "Official Stanford GSB record inspected. It states that the 27-page study reports financial returns and key qualities of U.S. and Canadian search funds formed since 1984 and updates the 2022 study with data through December 31, 2023. Chapter 13 uses it only as bounded cohort evidence and does not reproduce return estimates or infer outcomes for a new searcher, self-funded search, sponsor-backed deal, corporate acquisition, or geography outside the study scope. The study's definitions, population, reporting, vintage mix, and outcome availability must be examined before any quantitative use.", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C13-S11", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "Entrepreneurship Through Acquisition", "authors": "Hunt, R. A.; Fund, B. R.", "year": 2012, "title": "Reassessing the Practical and Theoretical Influence of Entrepreneurship Through Acquisition", "venue": "Journal of Entrepreneurial Finance, 16(1), 29-56", "source_type": "peer-reviewed conceptual and empirical article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://digitalcommons.pepperdine.edu/jef/vol16/iss1/2/", "doi": "10.57229/2373-1761.1005", "claim_notes": "Full official Pepperdine journal record inspected. The article argues that ETA should not be reduced to a small-company leveraged buyout and develops entrepreneurship propositions using search-fund data. Chapter 13 uses it to support ETA as a distinct entrepreneurial pathway with entrepreneurial intent and financing features, not to claim universal performance, prevalence, financing terms, or causal effects.", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C13-S12", "chapter_slugs": [ "chapter-13-startup-foundations" ], "framework": "ETA Forms and Evidence Boundary", "authors": "Hoffmann, A.; Kanbach, D. K.; Stubner, S.", "year": 2024, "title": "Entrepreneurship through acquisition: a scoping review", "venue": "Management Review Quarterly, 74, 1981-2012", "source_type": "peer-reviewed scoping review", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://link.springer.com/article/10.1007/s11301-023-00352-6", "doi": "10.1007/s11301-023-00352-6", "claim_notes": "Full open article inspected. It maps ETA-related work across management buy-ins, management buy-outs, search funds, business takeover, and entry-mode research and states that ETA scholarship remains limited. The authors also report English-language, interpretive, and no-quality-assessment limitations. Chapter 13 uses the review for form distinctions and the evidence boundary, not as proof that a particular path, screen, or outcome is superior.", "uses": [ { "entrySlug": "chapter-13-startup-foundations", "entryTitle": "Startup Foundations", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C15-S20", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Leveraged Acquisition Financing and Governance", "authors": "Kaplan, S. N.; Stromberg, P.", "year": 2009, "title": "Leveraged Buyouts and Private Equity", "venue": "Journal of Economic Perspectives, 23(1), 121-146", "source_type": "peer-reviewed review article", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.aeaweb.org/articles?id=10.1257/jep.23.1.121", "doi": "10.1257/jep.23.1.121", "claim_notes": "Official AEA record and complimentary article metadata inspected. The article defines leveraged buyouts as acquisitions by specialized investment firms using a relatively small equity portion and relatively large outside debt portion and reviews industry and transaction evidence. Chapter 15 uses that high-level distinction only; it does not treat 2009 evidence as a current leverage benchmark, a small-business ETA prescription, or proof of transaction outcomes.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C15-S21", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "U.S. SBA 7(a) Change-of-Ownership Financing", "authors": "U.S. Small Business Administration", "year": "n.d.", "title": "7(a) loans", "venue": "U.S. Small Business Administration", "source_type": "official current program guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sba.gov/funding-programs/loans/7a-loans", "doi": null, "claim_notes": "Current official SBA page inspected. It lists complete or partial changes of ownership among permitted 7(a) uses and identifies eligibility and reasonable repayment ability requirements. Chapter 15 does not state a universal loan amount, rate, equity injection, collateral rule, guarantee rule, term, approval probability, or transaction eligibility. Current SBA rules, lender requirements, transaction facts, and later notices must be checked at underwriting and closing.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C15-S22", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "SBA Lender and Development Company Operating Requirements", "authors": "U.S. Small Business Administration", "year": 2025, "title": "Standard Operating Procedure 50 10: Lender and Development Company Loan Programs, Version 8", "venue": "U.S. Small Business Administration", "source_type": "official operating procedure", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sba.gov/document/sop-50-10-lender-development-company-loan-programs", "doi": null, "claim_notes": "Official SBA document page inspected. It identifies SOP 50 10 Version 8 as effective June 1, 2025 and provides core, 7(a), and 504 program requirements. The page also presents related notices and updates. Chapter 15 uses the source only to require version- and notice-aware underwriting and closing review; it does not claim borrower entitlement, approval, or the applicability or satisfaction of a particular requirement.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C15-S23", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Adjusted Earnings Definition and Reconciliation Discipline", "authors": "U.S. Securities and Exchange Commission, Division of Corporation Finance", "year": "n.d.", "title": "Compliance and Disclosure Interpretations: Non-GAAP Financial Measures", "venue": "U.S. Securities and Exchange Commission", "source_type": "official regulator staff guidance", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/rules-regulations/staff-guidance/corporation-finance-interpretations/non-gaap-financial-measures", "doi": null, "claim_notes": "Current official SEC staff-guidance page inspected. It supports disciplined definition and reconciliation of non-GAAP measures and cautions that some adjustments or individually tailored recognition and measurement methods can be misleading in covered disclosures. Chapter 15 uses this only by analogy for a conservative private-transaction adjustment discipline and expressly does not claim that SEC non-GAAP rules govern every private ETA presentation or that a QoE review is an audit, GAAP opinion, fraud assurance, valuation, tax opinion, or forecast.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C15-S24", "chapter_slugs": [ "chapter-15-fundraising-and-finance" ], "framework": "Acquisition Governance and Board Oversight", "authors": "Organisation for Economic Co-operation and Development", "year": 2023, "title": "G20/OECD Principles of Corporate Governance 2023", "venue": "OECD Publishing", "source_type": "official international governance standard", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.oecd.org/content/dam/oecd/en/publications/reports/2023/09/g20-oecd-principles-of-corporate-governance-2023_60836fcb/ed750b30-en.pdf", "doi": "10.1787/ed750b30-en", "claim_notes": "Full official OECD publication inspected, especially disclosure and transparency, board responsibilities, risk and control systems, conflicts, independent judgment, and oversight of major acquisitions. Chapter 15 uses the principles as broad governance orientation, not as binding entity law, a jurisdiction-specific fiduciary standard, or a universal small-company board design. Actual law, documents, lender rights, and authorized governing bodies control.", "uses": [ { "entrySlug": "chapter-15-fundraising-and-finance", "entryTitle": "Fundraising and Finance", "excerpts": [ "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]" ] } ] }, { "source_id": "BB-C23-S01", "chapter_slugs": [ "appendix-c-public-record-decision-cases" ], "framework": "Public-Record Decision Case - Knight Capital Controls", "authors": "U.S. Securities and Exchange Commission", "year": 2013, "title": "In the Matter of Knight Capital Americas LLC, Exchange Act Release No. 70694", "venue": "SEC Administrative Proceeding File No. 3-15570", "source_type": "official regulator consent order", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/files/litigation/admin/2013/34-70694.pdf", "doi": null, "claim_notes": "Official SEC order inspected 2026-07-11. Supports the deployment, dormant-code, server inconsistency, pre-open message, control, and incident chronology. Knight consented without admitting or denying most findings; the order does not establish what every employee knew or intended.", "uses": [ { "entrySlug": "appendix-c-public-record-decision-cases", "entryTitle": "Appendix C: Public-Record Decision Cases", "excerpts": [ "The SEC later found, in an order entered with Knight's consent without admission or denial of most findings, that new code had not been deployed consistently across all eight servers, that dormant code could be triggered, that pre-open internal messages referenced the router error, and that Knight lacked specified automated controls and sufficiently documented deployment procedures. Those later findings reconstruct the control environment; they are not a transcript of what every decision-maker knew before the opening. [BB-C23-S01]", "| Deployment consistency | The SEC order states that the new code was deployed to seven of eight servers and that the eighth retained older code. [BB-C23-S01] | Whether the on-call leaders had a reliable server-by-server attestation before opening. |", "| Error signal | The SEC states that an internal system generated 97 messages referencing the router before the market opened; it also notes that these messages were not designed as formal system alerts. [BB-C23-S01] | Whether the messages indicated a contained defect, a false positive, or a market-wide exposure. |", "| Control design | The SEC order describes gaps in automated pre-trade controls, deployment procedures, testing, and incident response. [BB-C23-S01] | Which manual controls or fallback routes were immediately operable. |" ] } ] }, { "source_id": "BB-C23-S02", "chapter_slugs": [ "appendix-c-public-record-decision-cases" ], "framework": "Public-Record Decision Case - Knight Capital Company Disclosure", "authors": "Knight Capital Group, Inc.", "year": 2012, "title": "Form 8-K Exhibit 99.1: Update Regarding August 1 Disruption to Routing in NYSE-Listed Securities", "venue": "U.S. Securities and Exchange Commission EDGAR", "source_type": "company primary source filed with regulator", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/Archives/edgar/data/1060749/000119312512332176/d391111dex991.htm", "doi": null, "claim_notes": "Official SEC-filed company exhibit inspected 2026-07-11. Supports Knight's public description of the software installation issue and its initial loss estimate. It is a company disclosure made after the decision point, not evidence available before the market opened.", "uses": [ { "entrySlug": "appendix-c-public-record-decision-cases", "entryTitle": "Appendix C: Public-Record Decision Cases", "excerpts": [ "| Exposure | Knight's SEC-filed post-incident disclosure attributed a large trading loss to the August 1 software issue. [BB-C23-S02] | The size and direction of exposure before the market opens; the case does not disclose the later loss to the protagonist. |" ] } ] }, { "source_id": "BB-C23-S03", "chapter_slugs": [ "appendix-c-public-record-decision-cases" ], "framework": "Public-Record Decision Case - Zoom Security and Claims", "authors": "Federal Trade Commission", "year": 2021, "title": "FTC Gives Final Approval to Settlement with Zoom over Allegations the Company Misled Consumers about Its Data Security Practices", "venue": "Federal Trade Commission", "source_type": "official regulator release and final order package", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.ftc.gov/news-events/news/press-releases/2021/02/ftc-gives-final-approval-settlement-zoom-over-allegations-company-misled-consumers-about-its-data", "doi": null, "claim_notes": "Official FTC final-approval page and linked complaint/order inspected 2026-07-11. Supports attributed allegations and prospective order requirements, including a comprehensive security program, release review, independent assessments, and restrictions on misrepresentation. Allegations are not recast as adjudicated findings.", "uses": [ { "entrySlug": "appendix-c-public-record-decision-cases", "entryTitle": "Appendix C: Public-Record Decision Cases", "excerpts": [ "Decision point: February 2, 2021 , the day after the FTC announced final approval of its consent order. The order requires a comprehensive security program, security review of software updates, independent assessments, and restrictions on privacy and security misrepresentations. The committee must choose how broadly to redesign product governance, claims review, release assurance, and customer communication while supporting a platform that had experienced unprecedented pandemic-era usage. [BB-C23-S03] [BB-C23-S04]", "The FTC complaint contains allegations; the final order creates prospective obligations without converting every allegation into an adjudicated factual finding. The case therefore separates “the FTC alleged” from “the order requires.” [BB-C23-S03]", "| Security representations | The FTC alleged misrepresentations about encryption, cloud-recording security, and a Mac software component. [BB-C23-S03] | Which historical and current customer-facing statements require correction, qualification, or withdrawal across channels and jurisdictions. |", "| Program requirements | The final order requires a comprehensive security program, release-security review, independent assessment, and compliance reporting. [BB-C23-S03] | Whether minimum compliance will address product architecture, trust, and customer-segment needs. |", "| Governance | The order assigns formal program and assessment duties. [BB-C23-S03] | Where product, security, legal, and claims approval should sit and how dissent reaches the board. |", "This original case uses FTC complaint/order materials and an SEC-filed Zoom quarterly report. It paraphrases the official record and includes the allegation-versus-order distinction; no proprietary case narrative or technical design is copied. Security details are intentionally limited to facts already made public by the FTC. Do not infer present-day Zoom practices from a 2020 complaint or 2021 order. [BB-C23-S03] [BB-C23-S04] Status: citation fragment prepared; current legal, security, technical, reputation, and permissions review required before release." ] } ] }, { "source_id": "BB-C23-S04", "chapter_slugs": [ "appendix-c-public-record-decision-cases" ], "framework": "Public-Record Decision Case - Zoom Operating Scale", "authors": "Zoom Video Communications, Inc.", "year": 2020, "title": "Quarterly Report on Form 10-Q for the Quarter Ended October 31, 2020", "venue": "U.S. Securities and Exchange Commission EDGAR", "source_type": "company regulatory filing", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/Archives/edgar/data/1585521/000158552120000299/zm-20201031.htm", "doi": null, "claim_notes": "Official SEC filing inspected 2026-07-11. Supports Zoom's disclosure of unprecedented pandemic-era platform usage and operating-scale context. It does not prove that growth caused the FTC-alleged practices or establish a security-control conclusion.", "uses": [ { "entrySlug": "appendix-c-public-record-decision-cases", "entryTitle": "Appendix C: Public-Record Decision Cases", "excerpts": [ "Decision point: February 2, 2021 , the day after the FTC announced final approval of its consent order. The order requires a comprehensive security program, security review of software updates, independent assessments, and restrictions on privacy and security misrepresentations. The committee must choose how broadly to redesign product governance, claims review, release assurance, and customer communication while supporting a platform that had experienced unprecedented pandemic-era usage. [BB-C23-S03] [BB-C23-S04]", "| Scale and demand | Zoom's SEC filing described unprecedented use beginning in the quarter ended April 30, 2020 and rapid growth in cash, receivables, and operating scale. [BB-C23-S04] | Future demand, capacity, threat exposure, customer sensitivity, and the cost of slowing releases. |", "This original case uses FTC complaint/order materials and an SEC-filed Zoom quarterly report. It paraphrases the official record and includes the allegation-versus-order distinction; no proprietary case narrative or technical design is copied. Security details are intentionally limited to facts already made public by the FTC. Do not infer present-day Zoom practices from a 2020 complaint or 2021 order. [BB-C23-S03] [BB-C23-S04] Status: citation fragment prepared; current legal, security, technical, reputation, and permissions review required before release." ] } ] }, { "source_id": "BB-C23-S05", "chapter_slugs": [ "appendix-c-public-record-decision-cases" ], "framework": "Public-Record Decision Case - Southwest Operational Recovery", "authors": "U.S. Department of Transportation", "year": 2023, "title": "Southwest Airlines Consent Order 2023-12-11", "venue": "Office of Aviation Consumer Protection", "source_type": "official regulator consent order", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.transportation.gov/airconsumer/southwest-order-2023-12-11", "doi": null, "claim_notes": "Official DOT order inspected 2026-07-11. Supports later reconstruction of customer-service, notification, refund, reimbursement, and disruption conditions and the order's findings and relief. It postdates the protagonist's decision and is not treated as contemporaneous knowledge.", "uses": [ { "entrySlug": "appendix-c-public-record-decision-cases", "entryTitle": "Appendix C: Public-Record Decision Cases", "excerpts": [ "The 2023 DOT consent order and Southwest's 2022 Form 10-K were produced after this decision point. They reconstruct the scale, customer-service failures, refund and notification problems, cancellations, and financial effects with hindsight. The learner may use the operational symptoms in Exhibit 3A but should not assume the protagonist knew the later aggregate totals or enforcement outcome. [BB-C23-S05] [BB-C23-S06]", "| Customer contact | DOT later found that call-center queues, flight-status notifications, and customer assistance failed at scale. [BB-C23-S05] | Overflow capacity, channel accuracy, accessibility needs, and which communications can be automated safely. |", "| Refunds and care | The DOT order addresses prompt refunds, reimbursements, and customer-service commitments. [BB-C23-S05] | Volume and value of current obligations, processing capacity, error rate, and cash timing. |", "This original case derives compact exhibits from a DOT consent order and an SEC-filed annual report. It does not reproduce a proprietary airline-operations case. The DOT order reflects an enforcement settlement and must be attributed; the company filing reflects management's public disclosure. Later totals are withheld from the protagonist to reduce hindsight bias. The case does not allocate blame to individual employees or determine private rights. [BB-C23-S05] [BB-C23-S06] Status: citation fragment prepared; aviation operations, consumer-law, labor, accessibility, reputation, and permissions review required before release." ] } ] }, { "source_id": "BB-C23-S06", "chapter_slugs": [ "appendix-c-public-record-decision-cases" ], "framework": "Public-Record Decision Case - Southwest Company Disclosure", "authors": "Southwest Airlines Co.", "year": 2023, "title": "Annual Report on Form 10-K for the Year Ended December 31, 2022", "venue": "U.S. Securities and Exchange Commission EDGAR", "source_type": "company regulatory filing", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/Archives/edgar/data/92380/000009238023000010/luv-20221231.htm", "doi": null, "claim_notes": "Official SEC filing inspected 2026-07-11. Supports Southwest's later disclosure of crew, schedule, fleet, cancellation, and financial effects. Aggregate outcomes are withheld from the protagonist to reduce hindsight bias.", "uses": [ { "entrySlug": "appendix-c-public-record-decision-cases", "entryTitle": "Appendix C: Public-Record Decision Cases", "excerpts": [ "The 2023 DOT consent order and Southwest's 2022 Form 10-K were produced after this decision point. They reconstruct the scale, customer-service failures, refund and notification problems, cancellations, and financial effects with hindsight. The learner may use the operational symptoms in Exhibit 3A but should not assume the protagonist knew the later aggregate totals or enforcement outcome. [BB-C23-S05] [BB-C23-S06]", "| Network and crew alignment | Southwest later disclosed difficulty realigning crews, schedules, and aircraft after the storm. [BB-C23-S06] | Current verified location and duty status for every crew and aircraft; time to restore a reliable schedule. |", "| Financial and operational exposure | Southwest later disclosed more than 16,700 cancellations from December 21 through 31 and a material fourth-quarter effect. [BB-C23-S06] | The incremental exposure of each recovery option as of December 27; these later totals are withheld from the protagonist. |", "This original case derives compact exhibits from a DOT consent order and an SEC-filed annual report. It does not reproduce a proprietary airline-operations case. The DOT order reflects an enforcement settlement and must be attributed; the company filing reflects management's public disclosure. Later totals are withheld from the protagonist to reduce hindsight bias. The case does not allocate blame to individual employees or determine private rights. [BB-C23-S05] [BB-C23-S06] Status: citation fragment prepared; aviation operations, consumer-law, labor, accessibility, reputation, and permissions review required before release." ] } ] }, { "source_id": "BB-C23-S07", "chapter_slugs": [ "appendix-c-public-record-decision-cases" ], "framework": "Public-Record Decision Case - Wells Fargo Consumer Practices", "authors": "Consumer Financial Protection Bureau", "year": 2016, "title": "In the Matter of Wells Fargo Bank, N.A., Consent Order 2016-CFPB-0015", "venue": "Consumer Financial Protection Bureau", "source_type": "official regulator consent order", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://files.consumerfinance.gov/f/documents/092016_cfpb_WFBconsentorder.pdf", "doi": null, "claim_notes": "Official CFPB consent order inspected 2026-07-11. Supports attributed Bureau determinations, incentive and target context, covered account practices, restitution, penalties, and required relief. It does not establish identical conduct or intent for every account or employee.", "uses": [ { "entrySlug": "appendix-c-public-record-decision-cases", "entryTitle": "Appendix C: Public-Record Decision Cases", "excerpts": [ "The CFPB consent order states the Bureau's determinations and required relief. The OCC described the sales practices as unsafe or unsound and required an enterprise-wide sales-practices risk-management and oversight program. These records support the institutional control problem; they do not prove that every account, employee, manager, or customer experience was the same. [BB-C23-S07] [BB-C23-S08]", "| Customer authorization | The CFPB order addresses unauthorized deposit, credit-card, online-banking, and debit-card activity and customer restitution. [BB-C23-S07] | Complete affected population, non-fee harms, downstream credit or tax effects, and remediation preferences. |", "| Incentives and targets | The CFPB linked the practices it described to sales targets and compensation incentives. [BB-C23-S07] | Which product, branch, manager, or metric designs produced pressure; which legitimate sales activity would be impaired by abrupt change. |", "| Accountability and due process | Coordinated orders require restitution, penalties, and corrective action. [BB-C23-S07] [BB-C23-S08] | Individual knowledge, proportional accountability, employment obligations, preservation of evidence, and protection from retaliation. |" ] } ] }, { "source_id": "BB-C23-S08", "chapter_slugs": [ "appendix-c-public-record-decision-cases" ], "framework": "Public-Record Decision Case - Wells Fargo Enterprise Risk", "authors": "Office of the Comptroller of the Currency", "year": 2016, "title": "OCC Assesses Penalty Against Wells Fargo, Orders Restitution for Unsafe or Unsound Sales Practices", "venue": "Office of the Comptroller of the Currency", "source_type": "official regulator enforcement record", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.occ.gov/news-issuances/news-releases/2016/nr-occ-2016-106.html", "doi": null, "claim_notes": "Official OCC enforcement page and linked orders inspected 2026-07-11. Supports the unsafe-or-unsound sales-practice characterization, restitution, penalty, and enterprise-wide risk-management requirement. It does not allocate individual knowledge, intent, or liability.", "uses": [ { "entrySlug": "appendix-c-public-record-decision-cases", "entryTitle": "Appendix C: Public-Record Decision Cases", "excerpts": [ "The CFPB consent order states the Bureau's determinations and required relief. The OCC described the sales practices as unsafe or unsound and required an enterprise-wide sales-practices risk-management and oversight program. These records support the institutional control problem; they do not prove that every account, employee, manager, or customer experience was the same. [BB-C23-S07] [BB-C23-S08]", "| Enterprise risk management | The OCC cited failure to develop and implement an effective program to detect and prevent the unsafe or unsound practices. [BB-C23-S08] | Data quality, escalation history, control independence, employee-reporting experience, and board visibility. |", "| Accountability and due process | Coordinated orders require restitution, penalties, and corrective action. [BB-C23-S07] [BB-C23-S08] | Individual knowledge, proportional accountability, employment obligations, preservation of evidence, and protection from retaliation. |" ] } ] }, { "source_id": "BB-C23-S09", "chapter_slugs": [ "appendix-c-public-record-decision-cases" ], "framework": "Public-Record Decision Case - Intel CHIPS Preliminary Terms", "authors": "U.S. Department of Commerce", "year": 2024, "title": "Preliminary Terms with Intel to Support Investment in U.S. Semiconductor Technology Leadership", "venue": "U.S. Department of Commerce", "source_type": "official government preliminary-terms announcement", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.commerce.gov/news/press-releases/2024/03/biden-harris-administration-announces-preliminary-terms-intel-support", "doi": null, "claim_notes": "Official Commerce announcement inspected 2026-07-11. Supports the March 20, 2024 non-binding preliminary terms, proposed funding and loans, sites, stated investment expectations, due diligence, milestones, conditionality, and warning that final terms could differ. It does not support a guaranteed award, investment, job, capacity, or technology outcome.", "uses": [ { "entrySlug": "appendix-c-public-record-decision-cases", "entryTitle": "Appendix C: Public-Record Decision Cases", "excerpts": [ "Decision point: March 21, 2024 , one day after the U.S. Department of Commerce announced a non-binding preliminary memorandum of terms with Intel under the CHIPS and Science Act. Intel must decide how to pace proposed U.S. manufacturing and advanced-packaging investments across Arizona, New Mexico, Ohio, and Oregon while process readiness, external foundry demand, customer commitments, construction sequencing, incentives, and capital-market conditions remain uncertain. [BB-C23-S09]", "Commerce stated that final terms could differ, that funding remained subject to due diligence, negotiation, milestones, and availability, and that the preliminary terms contemplated direct funding and possible loans. Intel's 2023 Form 10-K described a “Smart Capital” approach using shell capacity, milestones, government incentives, customer commitments, co-investment, and external foundry use; it also disclosed that incentive arrangements can carry long-lived conditions and recapture or termination risk. [BB-C23-S09] [BB-C23-S10]", "| Preliminary public support | Commerce announced non-binding preliminary terms for up to $8.5 billion in direct funding and potential access to up to $11 billion in loans, subject to further process and conditions. [BB-C23-S09] | Final award, timing, project-specific milestones, disbursement, covenants, and recapture exposure. |", "| Investment scope | Commerce associated the preliminary terms with projects in four states and Intel described U.S. proposals exceeding $100 billion over five years. [BB-C23-S09] [BB-C23-S10] | Construction cost, permitting, workforce, tool timing, demand, process yield, and ramp coordination. |", "This original case derives its exhibit from a Department of Commerce announcement and Intel's SEC-filed 2023 annual report. Public statements about jobs, investment, technology, capacity, and incentives are presented as agency or company expectations, not guaranteed outcomes. The case deliberately stops at the non-binding preliminary terms and excludes later award changes and company developments. It does not provide investment advice or evaluate current Intel securities. [BB-C23-S09] [BB-C23-S10] Status: citation fragment prepared; securities, government-contracting, financial, technical, labor, environmental, reputation, and permissions review required before release." ] } ] }, { "source_id": "BB-C23-S10", "chapter_slugs": [ "appendix-c-public-record-decision-cases" ], "framework": "Public-Record Decision Case - Intel Capital and Capacity", "authors": "Intel Corporation", "year": 2024, "title": "Annual Report on Form 10-K for the Year Ended December 30, 2023", "venue": "U.S. Securities and Exchange Commission EDGAR", "source_type": "company regulatory filing", "quality_tier": "tier_1", "verification_status": "vetted", "verified_at": "2026-07-11", "url": "https://www.sec.gov/Archives/edgar/data/50863/000005086324000010/intc-20231230.htm", "doi": null, "claim_notes": "Official SEC filing inspected 2026-07-11. Supports Intel's Smart Capital, shell-capacity, milestone, government-incentive, co-investment, customer-commitment, external-foundry, and incentive-condition disclosures available before the March 2024 decision point. It does not establish that the strategy or proposed investments would succeed.", "uses": [ { "entrySlug": "appendix-c-public-record-decision-cases", "entryTitle": "Appendix C: Public-Record Decision Cases", "excerpts": [ "Commerce stated that final terms could differ, that funding remained subject to due diligence, negotiation, milestones, and availability, and that the preliminary terms contemplated direct funding and possible loans. Intel's 2023 Form 10-K described a “Smart Capital” approach using shell capacity, milestones, government incentives, customer commitments, co-investment, and external foundry use; it also disclosed that incentive arrangements can carry long-lived conditions and recapture or termination risk. [BB-C23-S09] [BB-C23-S10]", "| Investment scope | Commerce associated the preliminary terms with projects in four states and Intel described U.S. proposals exceeding $100 billion over five years. [BB-C23-S09] [BB-C23-S10] | Construction cost, permitting, workforce, tool timing, demand, process yield, and ramp coordination. |", "| Flexibility design | Intel's filing described building shell space and using readiness, market, and customer milestones before bringing capacity online. [BB-C23-S10] | Whether shells preserve valuable options or create carrying cost and commitment escalation. |", "| Capital partners and conditions | Intel described government incentives, co-investment, customer commitments, and external foundry use as capital levers; it also disclosed compliance and recapture conditions. [BB-C23-S10] | Partner appetite, customer concentration, control, economics, and whether external commitments arrive before irreversible tool spending. |", "This original case derives its exhibit from a Department of Commerce announcement and Intel's SEC-filed 2023 annual report. Public statements about jobs, investment, technology, capacity, and incentives are presented as agency or company expectations, not guaranteed outcomes. The case deliberately stops at the non-binding preliminary terms and excludes later award changes and company developments. It does not provide investment advice or evaluate current Intel securities. [BB-C23-S09] [BB-C23-S10] Status: citation fragment prepared; securities, government-contracting, financial, technical, labor, environmental, reputation, and permissions review required before release." ] } ] } ], "files": { "landingHtml": "index.html", "singleFileHtml": null, "chapterPages": [ "chapters/chapter-01-macroeconomics-for-strategic-leaders.html", "chapters/chapter-02-business-law-governance-and-ethics.html", "chapters/chapter-03-strategy-and-competitive-analysis.html", "chapters/chapter-04-financial-analysis-and-valuation.html", "chapters/chapter-05-marketing-and-customer-analytics.html", "chapters/chapter-06-operations-and-supply-chain.html", "chapters/chapter-07-organizational-behavior-and-leadership.html", "chapters/chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis.html", "chapters/chapter-09-problem-structuring.html", "chapters/chapter-10-advanced-consulting-frameworks-and-integration.html", "chapters/chapter-11-project-management-and-pmp-frameworks.html", "chapters/chapter-12-client-management.html", "chapters/chapter-13-startup-foundations.html", "chapters/chapter-14-go-to-market-strategy.html", "chapters/chapter-15-fundraising-and-finance.html", "chapters/chapter-16-ai-strategy-and-data-driven-decisions.html", "chapters/chapter-17-leading-digital-transformation.html", "chapters/chapter-18-digital-business-models-and-platform-economics.html", "chapters/chapter-19-cybersecurity-and-risk-management-for-managers.html", "chapters/chapter-20-the-ethics-of-ai-and-data.html", "chapters/chapter-21-product-management-and-product-strategy.html", "chapters/chapter-22-data-analysis-and-insights.html", "chapters/appendix-a-framework-selection-decision-trees.html", "chapters/appendix-b-contrarian-business-perspectives.html", "chapters/appendix-c-public-record-decision-cases.html" ], "markdownMirrors": [ "markdown/chapter-01-macroeconomics-for-strategic-leaders.md", "markdown/chapter-02-business-law-governance-and-ethics.md", "markdown/chapter-03-strategy-and-competitive-analysis.md", "markdown/chapter-04-financial-analysis-and-valuation.md", "markdown/chapter-05-marketing-and-customer-analytics.md", "markdown/chapter-06-operations-and-supply-chain.md", "markdown/chapter-07-organizational-behavior-and-leadership.md", "markdown/chapter-08-strategy-execution-mission-vision-values-okrs-and-kpis.md", "markdown/chapter-09-problem-structuring.md", "markdown/chapter-10-advanced-consulting-frameworks-and-integration.md", "markdown/chapter-11-project-management-and-pmp-frameworks.md", "markdown/chapter-12-client-management.md", "markdown/chapter-13-startup-foundations.md", "markdown/chapter-14-go-to-market-strategy.md", "markdown/chapter-15-fundraising-and-finance.md", "markdown/chapter-16-ai-strategy-and-data-driven-decisions.md", "markdown/chapter-17-leading-digital-transformation.md", "markdown/chapter-18-digital-business-models-and-platform-economics.md", "markdown/chapter-19-cybersecurity-and-risk-management-for-managers.md", "markdown/chapter-20-the-ethics-of-ai-and-data.md", "markdown/chapter-21-product-management-and-product-strategy.md", "markdown/chapter-22-data-analysis-and-insights.md", "markdown/appendix-a-framework-selection-decision-trees.md", "markdown/appendix-b-contrarian-business-perspectives.md", "markdown/appendix-c-public-record-decision-cases.md" ], "searchIndex": "search-index.json", "citationIndex": "citations.json", "downloads": [ "downloads/chapter-01-macroeconomics-for-strategic-leaders-04-DCF-Valuation-Model-Template.md", "downloads/chapter-01-macroeconomics-for-strategic-leaders-04_DCF_Valuation_Model.xlsx" ] } }