Speaking the Language of Capital Allocation

The practice of translating a proposal into the vocabulary the capital-allocation decision-maker actually uses to evaluate any investment — cash flow, risk, and return — rather than the proposer's own domain language (e.g. a CSO's impact/materiality/disclosure vocabulary), while being disciplined about which impacts are credibly quantifiable versus directional upside or an explicit bet.

Also known as: business case fluency, investment language, cash-flow, risk, return framing, de-averaging vs aggregation, value pathways, quantify what you can, treat the rest as upside or bet

How authors use it

Oldest first (extraction date when no publication date is known).

Documents (2)

• TBM 437: Tokens, Hours, Points, and Other Curious Proxies John Cutler · 2026-08-17 Reader 🖥️
  Tokens are the latest in a lineage of seductive measurement proxies -- hours, story points, flow metrics -- that organizations mistake for a theory of value because they happen to be unusually easy to measure, and the fix is not a better proxy but making the underlying causal model of value explicit (treating the team as the cost unit, funding durable lanes, stating falsifiable hypotheses) so that ROI becomes the *output* of that model rather than a number computed directly from an easy-to-meter input.
• Make the Business Case for Your Sustainability Initiative Laura Bryce · 2026-07-07 source ↗ Reader 🖥️
  Sustainability proposals stall not for lack of merit but because they are pitched in the CSO's vocabulary (impact, materiality, disclosure) instead of the vocabulary capital allocators actually evaluate against (cash flow, risk, return); CSOs should therefore build their case like any other investment case — naming which of four value pathways (cost reduction, cost avoidance, new revenue, revenue protection) drives the ask, stating the causal business story before modeling numbers, and explicitly separating what can be credibly quantified from what must be labeled upside or a strategic bet.

Open gaps (4)

• incompleteThe article's reciprocity claim is asymmetric in substance: CSOs are asked to do concrete, effortful work (learn financial fluency, build cash-flow models, partner with finance/tax), while CFOs are only asked for an attitudinal shift ('give up the reflex,' 'commit to patiently run through the value pathways') with no accountability mechanism specified if they don't. The piece never asks what recourse a CSO has, or what changes on the CFO/process side, if a well-built, correctly-framed case still gets the same silent non-commitment as the opening vignette.
  Make the Business Case for Your Sustainability Initiative — read next: Literature on cross-functional influence without formal authority, and on how other historically 'soft' functions (HR analytics, DEI) fared when they adopted the finance function's own language — did translation alone move decisions, or did it also require process/accountability changes on the receiving side?
• incompleteThe 'quantify what you can, treat the rest as upside or bet' rule has no safeguard against motivated classification: nothing in the framework stops a CSO (wanting funding) or a skeptical CFO (wanting to kill a proposal) from strategically choosing which impacts count as 'credibly quantifiable' versus 'directional' to steer toward a predetermined conclusion. The article presents the rule as if the quantifiable/directional line were self-evident, when in practice it is exactly the kind of judgment call prone to motivated reasoning.
  Make the Business Case for Your Sustainability Initiative — read next: Forecasting and estimation literature on motivated reasoning and strategic misrepresentation in business-case modeling — e.g. Bent Flyvbjerg's work on systematic cost-benefit gaming in megaprojects, or reference-class forecasting as a corrective.
• uninformedThe framework treats 'impact/materiality/disclosure' language and 'cash-flow/risk/return' language as two dialects describing the same underlying value, fully translatable if the CSO just tries hard enough. It does not engage the more skeptical possibility that some sustainability value is a genuine externality — a cost or benefit that does not show up in the firm's own cash flows at all, absent regulation or carbon pricing forcing internalization. If so, no amount of business-story or pathway-mapping skill converts that value into a defensible project-level cash flow; the CSO would be pushed to overstate captured value or quietly drop genuinely important-but-uninternalized impacts to fit the framework.
  Make the Business Case for Your Sustainability Initiative — read next: Environmental economics on externality internalization (Pigouvian taxation, the theory of market failure), and corporate-finance critiques of ESG 'materiality' as a category that elides the difference between financial materiality to the firm and materiality to the world.
• incompleteCutler never specifies who is supposed to build, own, and adjudicate disputes about the 'theory of the system' / causal model he proposes -- finance, engineering leadership, product, or some new function. Without a named owner and a process for contesting a causal narrative's validity, 'make your theory of the system explicit' risks becoming just as rhetorically gameable as the proxies it replaces: a leader can write a confident-sounding, well-formatted causal story without it being falsifiable in practice, and nothing in the piece specifies who would catch that.
  TBM 437: Tokens, Hours, Points, and Other Curious Proxies — read next: Organizational-design and FinOps-style AI-cost-governance literature on who owns cross-functional investment decisions; DORA's Capabilities Model research on how measurement gets operationalized organizationally rather than just prescribed.