{"handle":"business-frameworks/decision/effort@1.6.1","path":"decision/effort","version":"1.6.1","title":"Effort: match the analysis to the stakes","layer":2,"free":true,"tokens":520,"tokens_terse":101,"budget":520,"price_usd":0,"children":["business-frameworks/decision/effort/initiatives@1.6.1","business-frameworks/decision/effort/test@1.6.1"],"related":["business-frameworks/decision@1.6.1","business-frameworks/decision/extension@1.6.1","business-frameworks/cash-flow/decide/runway@1.6.1","business-frameworks/growth/decide/adjacency@1.6.1","business-frameworks/cash-flow/pro-forma@1.6.1","business-frameworks/value/decide/reinvest-or-distribute@1.6.1","business-frameworks/decision/parameters@1.6.1"],"cites":["Sirkin, Keenan and Jackson (2005), Harvard Business Review","Ruback, R. S. and Yudkoff, R., HBR Guide to Buying a Small Business, Harvard Business Review Press, 2017","Harvard Business Review, HBR Guide to Data Analytics Basics for Managers, 2018","Harvard Business Review, HBR Guide to AI Basics for Managers, 2023"],"shape":null,"text":"Match the analysis to what a wrong answer would cost and how easily it could be undone. A decision that is small, reversible or repeated every month takes the rule with its defaults and no more; one that is large, irreversible or rare — an acquisition, a plant, a change of ownership — earns the full method: the forecast, the pro forma, a calibrated r, a parameter adjusted for the project. Most decisions are the first kind; spend the effort saved on the few that are the second.\n\nThree signs that a decision was under-analyzed: the realized return misses the plan twice in a row (the check in `value/decide/reinvest-or-distribute`); every candidate passes the screen (`decision/parameters`); or a large, irreversible choice was made on a spoken summary of a document nobody read. Two signs of over-analysis: the forecast is still being refined after the answer stopped changing, or the analysis costs more than the decision is worth. Where others must change their work, approval is not execution; involving them is effort, and so is reporting the result. For work others carry out over months, set the gap between reviews at the start: that gap tells more about the outcome than the total length. A decision copied into many units, or locked in by a design freeze or a tooling order, is large even when it costs little itself; \"repeated\" means decided again with a check between. Over many candidates, stage the effort: a quick screen rejects most, a deeper one most of the rest, and the full method goes to the few left. Getting and preparing the data is part of the effort: check what already exists before collecting more. Where the evidence is only that two things move together, take the action whose downside is small and hold the costly or hard-to-undo one until the cause is understood. For a system that will act in the work, a working pilot is not the decision: size the effort on running and maintaining it, start it on a few simple tasks, and widen its authority in stages where service holds, pausing where it is falling.\n\nAnalysis has a cost in time and tokens, and its value falls fast once the direction of the answer is settled; the 80/20 split in `decision` is a budget for it, not a ceiling on care. The check in every decision node is what lets a short analysis be safe: an error shows up at the next check, where it is cheap to correct. A reversible decision in doubt gets the cheapest test that could change it, not more analysis.","variants":{"terse":"the lede alone","full":"lede, conditions and reasoning","agent":"the same accepted text as fields (served with ?variant=agent): scope, inputs, rule, action, check, reasoning, units, example, apply, recheck, recheck_note, closing_citation; the same price"},"versions":["1.6.1","1.6","1.5","1.4","1.3","1.2"],"variant":"full","levels":{"lede":"Match the analysis to what a wrong answer would cost and how easily it could be undone. A decision that is small, reversible or repeated every month takes the rule with its defaults and no more; one that is large, irreversible or rare — an acquisition, a plant, a change of ownership — earns the full method: the forecast, the pro forma, a calibrated r, a parameter adjusted for the project. Most decisions are the first kind; spend the effort saved on the few that are the second.","conditions":"Three signs that a decision was under-analyzed: the realized return misses the plan twice in a row (the check in `value/decide/reinvest-or-distribute`); every candidate passes the screen (`decision/parameters`); or a large, irreversible choice was made on a spoken summary of a document nobody read. Two signs of over-analysis: the forecast is still being refined after the answer stopped changing, or the analysis costs more than the decision is worth. Where others must change their work, approval is not execution; involving them is effort, and so is reporting the result. For work others carry out over months, set the gap between reviews at the start: that gap tells more about the outcome than the total length. A decision copied into many units, or locked in by a design freeze or a tooling order, is large even when it costs little itself; \"repeated\" means decided again with a check between. Over many candidates, stage the effort: a quick screen rejects most, a deeper one most of the rest, and the full method goes to the few left. Getting and preparing the data is part of the effort: check what already exists before collecting more. Where the evidence is only that two things move together, take the action whose downside is small and hold the costly or hard-to-undo one until the cause is understood. For a system that will act in the work, a working pilot is not the decision: size the effort on running and maintaining it, start it on a few simple tasks, and widen its authority in stages where service holds, pausing where it is falling.","reasoning":"Analysis has a cost in time and tokens, and its value falls fast once the direction of the answer is settled; the 80/20 split in `decision` is a budget for it, not a ceiling on care. The check in every decision node is what lets a short analysis be safe: an error shows up at the next check, where it is cheap to correct. A reversible decision in doubt gets the cheapest test that could change it, not more analysis."},"url":"https://business-frameworks.matryoshka-paradigms.workers.dev/node/decision/effort","children_urls":["https://business-frameworks.matryoshka-paradigms.workers.dev/node/decision/effort/initiatives","https://business-frameworks.matryoshka-paradigms.workers.dev/node/decision/effort/test"],"related_urls":["https://business-frameworks.matryoshka-paradigms.workers.dev/node/decision","https://business-frameworks.matryoshka-paradigms.workers.dev/node/decision/extension","https://business-frameworks.matryoshka-paradigms.workers.dev/node/cash-flow/decide/runway","https://business-frameworks.matryoshka-paradigms.workers.dev/node/growth/decide/adjacency","https://business-frameworks.matryoshka-paradigms.workers.dev/node/cash-flow/pro-forma","https://business-frameworks.matryoshka-paradigms.workers.dev/node/value/decide/reinvest-or-distribute","https://business-frameworks.matryoshka-paradigms.workers.dev/node/decision/parameters"],"cite_as":"McHenry, J. (2026). Business Frameworks, version 1.6.1, business-frameworks/decision/effort@1.6.1."}