Economy Of Force¶
Core Idea¶
Economy of force is the structural pattern in which, when resources are finite and one or a few efforts are decisive for the outcome, the secondary efforts receive the minimum sufficient allocation — enough to hold their position, preserve optionality, deny the opponent advantage there, or maintain function, and no more — so that the freed mass can be concentrated at the decisive point. The discipline is not "do less elsewhere" in a vague sense; it is "do the least that still works elsewhere, on purpose, so that the decisive effort has the resources it requires." Economy of force is deliberate under-resourcing of the non-decisive in service of mass at the decisive. It is the complement of concentration: concentration names the massing at the decisive point, economy of force names what is done everywhere else to make that massing possible.
The structure decomposes into a finite resource budget; a set of efforts over which the resource must be allocated; a decisiveness gradient — a small number of efforts whose marginal returns to resource are large, and many efforts with small marginal returns; a minimum-viable function for each non-decisive effort, the threshold below which that effort fails or imposes costs exceeding the savings; an allocation rule that drives non-decisive efforts to their minimum-viable level and concentrates the freed resource at the decisive ones; and a reserve hedging against being wrong about which effort is decisive. Two structural commitments are easy to miss and load-bearing. The first is that "minimum viable" is harder than it looks: each non-decisive effort has an owner who will argue for more, and the minimum is set by threshold — what the effort must produce to not cause harm downstream — not by desire. The second is the distinction between neglect and deliberate minimum allocation: the former is failure, the latter is design, and the whole value of the prime rests on keeping them apart.
How would you explain it like I'm…
Just Enough Elsewhere
Least That Still Works
Deliberate Minimum, Not Neglect
Structural Signature¶
the finite resource budget — the set of efforts to allocate over — the decisiveness gradient — the minimum-viable threshold per non-decisive effort — the concentrate-the-freed-mass allocation rule — the reserve hedging the decisive-point judgement
A situation exhibits the economy-of-force pattern when each of the following holds:
- A finite resource budget. A fixed quantity of resource — troops, capital, attention, engineering effort — must be distributed and cannot fund every effort to its preferred level.
- A set of competing efforts. Multiple efforts claim the resource, each with an owner inclined to argue for more.
- A decisiveness gradient. A small number of efforts have large marginal returns to resource (decisive), and many have small marginal returns (non-decisive); the outcome turns on the decisive few.
- A minimum-viable threshold. Each non-decisive effort has a floor — what it must produce to not cause harm downstream — set by threshold, not by desire; below it the effort fails or imposes costs exceeding the savings.
- A concentrate-the-freed-mass rule. The allocation rule deliberately drives non-decisive efforts to their minimum-viable level and concentrates the freed resource at the decisive point. This is deliberate under-resourcing by design, sharply distinct from neglect (failure) and from prioritisation (ranking without the cut).
- A reserve. Capacity is held back proportional to the uncertainty about which effort is decisive, hedging the catastrophic risk of misidentifying the decisive point; non-decisive efforts also ratchet back toward preferred levels over time, requiring periodic recalibration.
The components compose a two-pile discipline — decisive versus non-decisive — that replaces N-way optimisation with threshold-setting plus concentration, with the reserve as built-in safeguard. The military vocabulary tinges the surface, but the allocation rule travels cleanly.
What It Is Not¶
- Not prioritisation.
prioritizationrank-orders efforts cognitively; economy of force is the cut-and-concentrate move that must follow the ranking — actually starving the lower ranks to their minimum so the decisive can be massed. Ranking without the cut is the common, expensive failure economy of force names. - Not concentration alone. Concentration names the massing at the decisive point; economy of force names what is done everywhere else (deliberate minimum allocation) to make that massing possible.[1] They are complements — economy of force is the under-resourcing half.
- Not neglect. Neglect is failure of attention; economy of force is deliberate minimum allocation to a defined threshold in service of concentration. The two look identical from the outcome but differ in pedigree — a threshold defined before the cut, and the freed resource actually concentrated.
- Not a decision.
decision(the nearest neighbour) is a single choice; economy of force is a standing allocation discipline with a reserve and periodic recalibration against ratchet drift, not a one-time selection.[1] - Not held capacity for its own sake.
reserveis one component of economy of force (the hedge against decisive-point error); the prime is the whole allocation rule, not just the held-back portion. - Common misclassification. Laundering neglect as strategy after the fact, or stopping at prioritisation. If no threshold was defined before the cut and the freed resource was not actually concentrated at a decisive point, what happened was neglect; and a priority list that no budget reflects is ranking without economy of force.
Broad Use¶
In the military, the home substrate, economy of force is one of the classical principles of war: hold a wide front with the minimum required force so that the main attack can be concentrated.[1] In portfolio and capital allocation, it is betting on the few convictions while holding benchmark or minimum-position exposures everywhere else to preserve optionality and minimise tracking error, freeing capital for high-conviction positions.[2] In operating budgets, it is keeping cost-of-doing-business functions at minimum-viable run rate and concentrating investment on the few strategic priorities. In attention and personal effectiveness, it is minimum-viable engagement with the inbox, meetings, and chores so that deep work gets uninterrupted blocks — most productivity systems are economy of force on attention.[3] In engineering reliability, it is minimum-viable error handling on cold code paths so hot paths receive the engineering attention, with gold-plating the rarely-hit branches as the anti-pattern.[4] In sales, it is minimum-viable coverage of low-tier accounts to defend share while concentrating on high-value accounts.[5] In public policy, it is minimum-viable enforcement on low-impact violations to maintain norm legitimacy while concentrating enforcement on high-impact ones.[6] And in software architecture, it is minimum-viable handling of edge cases so the common-case code stays small, simple, and well-tuned.[4]
Clarity¶
The frame's first clarifying act is to separate neglect from deliberate minimum allocation. The former is a failure of attention; the latter is a designed choice, and conflating them is the most common error the prime guards against. By naming the difference, the frame converts "we under-resourced that and it suffered" from an admission of failure into a description of strategy — provided the under-resourcing was deliberate, to a defined threshold, in service of a decisive concentration. It forces the explicit question "what is the minimum function this effort must deliver, and what is the smallest allocation that achieves it?" — a sharply different question from "what would be ideal here?"
The frame's second clarifying act is to separate prioritisation from economy of force. Prioritisation rank-orders efforts; economy of force is the discipline of cutting allocation to the lower-ranked efforts to the minimum sufficient. The two are routinely confused, with expensive consequences: prioritisation without economy of force produces lists that everyone agrees with and no one's allocation reflects, because ranking is cognitive while reallocation is a resource move that requires actually starving the lower ranks. Clarity here means recognising that agreeing on what matters most is not the same as freeing the mass to fund it, and that the second step — the deliberate cut — is the one that usually fails to happen.
Manages Complexity¶
Resource-allocation problems become tractable when reframed from "how do I optimally distribute across N efforts?" to "which one or two are decisive, what is the minimum sufficient elsewhere, and how much can I concentrate at the decisive point?" Two-pile sorting — decisive versus non-decisive — beats N-way optimisation, which is a dramatic reduction in the dimensionality of the decision. The practitioner no longer needs to weigh every effort against every other; they need only identify the decisive few, set thresholds for the rest, and concentrate the difference.
The cost of this compression is being wrong about which point is decisive, which is a serious risk, and the prime manages it structurally through the reserve: economy of force without a reserve is brittle, because a misidentified decisive point with no hedge is catastrophic, so the right reserve level depends on the uncertainty about which effort is decisive. The compression therefore comes with its own built-in safeguard. The frame also bounds an otherwise open question — how much to spend where — by tying it to thresholds and a decisiveness gradient rather than to negotiation among effort-owners, which is what makes allocation tractable in the face of political pressure to fund everything adequately. The minimum-viable threshold, honestly set, is the device that converts an unbounded bargaining problem into a bounded structural one.
Abstract Reasoning¶
The structural shape supports several inferences. The binding question is identify the decisive point, because a wrong answer is catastrophic, and the prime makes this the first and most consequential reasoning move. It supports the inference that non-decisive efforts have minimum-viable thresholds set by what they must produce to not cause harm downstream, not by their owners' preferences, which redirects the allocation argument from desire to threshold. It supports the reserve inference: hold back capacity proportional to the uncertainty about which effort is decisive, because the whole scheme is brittle without it. And it supports a ratchet-drift inference: non-decisive efforts tend to grow back toward their preferred allocation over time, so periodic recalibration against creep is required.
The reasoning generalises because it is stated in terms of decisiveness, threshold, concentration, and reserve rather than in terms of troops or capital. A general reasoning about which front is decisive, an investor reasoning about which positions carry conviction, and an engineer reasoning about which code paths are hot are all reasoning about the same gradient and applying the same allocation rule. The prime's distinctive reasoning contribution is disciplinary: it does not tell the reasoner what to build, but what not to spend on in order to spend on what matters — a discipline that is recurringly under-practised across substrates precisely because the felt pressure is always to fund every effort adequately.
Knowledge Transfer¶
The portable procedure is to identify the decisive point, define minimum-viable thresholds for the non-decisive efforts, reallocate the freed resource visibly to the decisive ones, maintain a reserve hedging the decisive-point judgement, and audit for ratchet drift. The same intervention pattern recurs across capital allocation, military campaigns, engineering attention, regulatory enforcement, and sales coverage, because each fills the same slots with its own resources.
The transfer's core moves carry directly. Identify the decisive point is the binding question everywhere, and a wrong answer is catastrophic in every substrate. Define minimum-viable thresholds, explicitly measured and defended against ratcheting upward, applies whether the effort is a code path, a low-tier account, or a quiet front. Reallocate the freed resource visibly to the decisive effort, rather than letting it be absorbed in slack, is the step that distinguishes economy of force from mere cost-cutting. Maintain a reserve against being wrong about decisiveness hedges the central risk in every domain. And communicate the discipline, because non-decisive owners feel starved and the cut must be made legitimate as a strategic choice rather than a snub — a social transfer requirement that is identical across military planning, budget setting, and engineering triage.
The transfer is genuine but the prime grades as mixed-structural, because its military-doctrine origin tinges the vocabulary — "mass," "decisive point," "force" — even though the underlying allocation rule travels cleanly. What ports is the rule itself: deliberately under-resource the non-decisive to the minimum sufficient so the decisive can be concentrated, hedged by a reserve and protected against ratchet drift. The substrate is mostly resource-and-strategy, which is why the structural skeleton survives translation to finance, operations, attention, and policy without strain. The most valuable thing the prime carries between domains is the licence — and the discipline — to deliberately starve the secondary right things, which is a different and harder move than starving the wrong things, and one that no single domain teaches reliably on its own. Its nearest neighbour, prioritisation, is the ranking move; economy of force is the cut-and-concentrate move that must follow it for the ranking to mean anything.
Examples¶
Formal/abstract¶
A classical breakthrough offensive is the prime's home instance, and it instantiates every slot. The finite resource budget is the total force available to the attacker — fixed, unable to fund every sector to its preferred strength. The set of competing efforts is the frontage: a wide line of sectors, each with a local commander inclined to argue for more troops. The decisiveness gradient is sharp: one narrow sector chosen for the breakthrough has enormous marginal returns to additional force (concentration there decides the battle), while the rest of the front has small marginal returns (holding them merely denies the enemy advantage). The minimum-viable threshold for each non-decisive sector is the floor below which it would collapse and let the enemy through to threaten the main effort from the flank — set by what the sector must produce to not cause harm downstream, not by its commander's desire. The concentrate-the-freed-mass rule is the discipline itself: deliberately thin the quiet sectors to their minimum-viable level and mass the freed force at the breakthrough point. The reserve is held back proportional to the uncertainty about whether the chosen sector is truly the decisive one — economy of force without a reserve is brittle, because a misidentified decisive point with no hedge is catastrophic. The prime's two load-bearing distinctions are both visible: deliberately thinning a quiet sector to its minimum (design) is sharply distinct from neglecting it (failure), and from merely ranking sectors by importance without actually cutting their allocation (prioritisation without the cut). The ratchet-drift discipline applies too — quiet-sector commanders lobby their strength back up over time, requiring periodic recalibration against creep.
Mapped back: The breakthrough offensive instantiates every commitment — finite budget, competing efforts, decisiveness gradient, minimum-viable thresholds, concentrate-the-freed-mass rule, reserve — and shows the prime's core discipline: deliberately starve the secondary to its floor so the decisive point can be massed, hedged by a reserve.
Applied/industry¶
The identical allocation rule, with its military vocabulary shed, governs concentrated investment and engineering reliability — two domains where the structure ports cleanly to a resource-and-strategy substrate. In a high-conviction investment portfolio, the budget is the fund's capital; the competing efforts are the candidate positions; the decisiveness gradient separates a few high-conviction theses (large marginal return on capital) from many low-conviction holdings. The minimum-viable threshold for the non-decisive positions is the benchmark or minimum exposure that preserves optionality and limits tracking error — the floor below which the portfolio incurs costs (regret risk, mandate breach) exceeding the savings — and the concentrate-the-freed-mass rule reallocates the difference into the high-conviction bets.[2] The reserve is the cash or liquidity held against being wrong about which theses are decisive, the structural hedge against the central risk. The prime's distinction between economy of force and mere cost-cutting is exact here: the freed capital must be visibly reallocated to the decisive positions, not absorbed in slack, which is what makes it concentration rather than just trimming. Engineering reliability is the same skeleton in a software substrate: the budget is finite engineering attention; the efforts are the code paths; the decisiveness gradient separates hot paths (hit constantly, where attention has large marginal return on reliability and performance) from cold paths (rarely executed). The minimum-viable threshold for a cold path is enough error handling that a rare failure does not corrupt state or cascade downstream — set by threshold, not by the perfectionist impulse — and the anti-pattern the prime names is gold-plating the rarely-hit branches, lavishing attention on cold code at the expense of the hot paths that determine the system's actual behaviour.[4] The freed attention concentrates on the hot paths, with a reserve of slack capacity for the genuine surprise. In both, the social transfer requirement is identical: the starved owners (low-conviction position holders, cold-path maintainers) feel snubbed, so the cut must be communicated as a deliberate strategic choice rather than neglect.
Mapped back: Concentrated investing and reliability triage are economy of force in financial and engineering substrates: deliberately under-resource the non-decisive to its minimum-viable floor so the decisive few can be massed, hedged by a reserve and protected against ratchet drift — the allocation rule travelling cleanly once the military vocabulary is dropped.
Structural Tensions¶
T1 — Deliberate Minimum versus Neglect (sign/direction). The whole value of the prime rests on a distinction that is invisible from the outcome: a starved non-decisive effort looks identical whether it was under-resourced by design (to a defined threshold, in service of concentration) or simply neglected (a failure of attention). The failure mode is laundering neglect as strategy after the fact, or conversely flinching from a sound deliberate cut because it resembles negligence. Diagnostic: ask whether a threshold was defined before the cut and whether the freed resource was actually concentrated at a decisive point; deliberate minimum allocation has both, neglect has neither, and only the outcome's pedigree tells them apart.
T2 — Prioritisation versus the Actual Cut (scopal). Ranking efforts is cognitive and cheap; cutting allocation to the lower ranks is a resource move and politically expensive — and the prime insists the second is what makes the first mean anything. The failure mode is prioritisation theatre: everyone agrees on the ranked list, no one's allocation changes, and the decisive effort stays unfunded because the freed mass was never actually freed. Diagnostic: ask whether the lower-ranked efforts have had resource removed, not merely been labelled lower priority; a priority ordering that no budget reflects is ranking without economy of force, and the decisive concentration it was meant to enable never happens.
T3 — Minimum-Viable Threshold versus Owner Desire (measurement). Each non-decisive effort's floor is set by what it must produce to not cause harm downstream — a threshold — not by what its owner wants, yet the owner is the one arguing for the number. The failure mode runs both ways: setting the floor too high (capitulating to owner desire, so nothing is freed) or too low (cutting below genuine viability, so the effort fails and imposes downstream costs exceeding the savings). Diagnostic: derive the threshold from downstream harm, independently of the owner's preference; the minimum is what the effort must deliver for the system, and confusing "what would be ideal here" with "what must not break" is how the cut either fails to happen or goes too far.
T4 — Concentration versus Decisive-Point Error (scalar, the central risk). The prime replaces N-way optimisation with a two-pile bet on which efforts are decisive — and the entire scheme is catastrophic if that bet is wrong, because mass was stripped from everything else to fund it. Concentration and robustness pull against each other. The failure mode is over-concentration on a misidentified decisive point with no hedge, so a single judgement error loses everything at once. Diagnostic: size the reserve to the uncertainty about which effort is decisive, not to a fixed convention; the more confident the decisive-point judgement, the more concentration is licensed, and economy of force without a reserve proportional to that uncertainty is brittle by construction.
T5 — Static Allocation versus Ratchet Drift (temporal). A correct allocation is not self-maintaining: non-decisive owners lobby their resource back toward preferred levels over time, so the disciplined cut silently erodes. The failure mode is treating economy of force as a one-time decision rather than a standing discipline, so that months later the freed mass has been quietly reabsorbed into the secondary efforts and the decisive concentration has dissolved. Diagnostic: audit allocations periodically against the original thresholds; drift back toward preferred levels is the default, and without recalibration against creep the concentration achieved at decision time decays back into the even spread it was meant to replace.
T6 — Allocation Frame versus Inseparable Efforts (scopal). The prime presumes efforts are separable enough to fund independently and rank on a decisiveness gradient — but some efforts are coupled, and starving a "non-decisive" one can disable the decisive effort it secretly supports. The failure mode is cutting a low-marginal-return effort whose output the decisive effort silently depends on, so the concentration fails not from misjudging decisiveness but from misjudging independence. Diagnostic: before cutting a non-decisive effort to its floor, ask what the decisive effort draws from it; the two-pile discipline assumes the piles are separable, and where efforts are tightly coupled the minimum-viable threshold of a secondary effort is set partly by what the decisive effort requires of it, not by its own standalone function.
Structural–Framed Character¶
Economy of force sits on the structural side of the middle of the structural–framed spectrum, with a mixed-structural aggregate of 0.4. The underlying rule is a genuine, substrate-neutral allocation principle: deliberately under-resource the non-decisive efforts to their minimum-viable floor so the freed mass can be concentrated at the decisive point, hedged by a reserve and protected against ratchet drift. That rule — decisiveness gradient, minimum-viable threshold, concentrate-the-freed-mass, reserve — recurs without strain in capital allocation, operating budgets, attention management, engineering reliability, sales coverage, and regulatory enforcement, which keeps the grade below the middle.
Two diagnostics read 0.0 and anchor the structural core. Evaluative weight is zero: the allocation rule is value-neutral — deliberately starving a secondary effort is neither good nor bad in itself, and the prime's whole point is to distinguish deliberate minimum allocation (design) from neglect (failure), which is a pedigree distinction, not a valence one. The remaining diagnostics read 0.5 and lift the aggregate to 0.4. Institutional origin is 0.5: the prime is one of the classical principles of war, born of military doctrine, and that lineage tinges it. Vocabulary travels halfway: the military lexicon — "mass," "decisive point," "force," "reserve" — follows the allocation rule into finance and engineering rather than each substrate naming the cut-and-concentrate move natively. Human-practice binding is 0.5: the discipline leans on a deciding agent who must set thresholds against effort-owners' lobbying and communicate the cut as legitimate, yet the bare allocation rule (finite budget, decisiveness gradient, concentration) is a resource-and-strategy structure that holds wherever a fixed budget meets uneven marginal returns, which keeps the binding partial. And import-versus-recognize is 0.5, because invoking the prime brings some operational-art framing along even as it recognises a genuine concentration-versus-spread allocation already in play. The honest reading, which the entry states, is that the military-doctrine origin tinges the vocabulary while the underlying allocation rule travels cleanly — exactly a mixed-structural 0.4, and the prose label matches the frontmatter.
Substrate Independence¶
Economy of Force is a strongly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. The principle — deliberately under-resource non-decisive efforts in order to mass strength at the decisive point — is a genuine cross-domain allocation structure (structural abstraction 4). It recurs across military strategy, finance (concentrating capital where edge is real), operations (staffing the bottleneck and starving the rest), attention management, engineering (spending effort only where it moves the outcome), and policy prioritization (domain breadth 4). What holds it a notch lower is the transfer evidence: while the allocation logic clearly recurs, its cross-domain carry is more often stated as a maxim than instantiated in a shared formal model, so the documented transfer is solid but not dense (transfer evidence 3). The clean abstraction and real breadth place it firmly in the strong band just below the top.
- Composite substrate independence — 4 / 5
- Domain breadth — 4 / 5
- Structural abstraction — 4 / 5
- Transfer evidence — 3 / 5
Relationships to Other Abstractions¶
Current abstraction Economy Of Force Prime
Parents (1) — more general patterns this builds on
-
Economy Of Force is a kind of Allocation Prime
Economy of force is a specialized allocation rule: drive non-decisive efforts to their minimum-viable floor so freed mass concentrates at the decisive point.It is allocation (assign limited supply across competing claimants) plus a decisiveness gradient + minimum-viable threshold + reserve.
Children (1) — more specific cases that build on this
-
Reserve Prime decompose Economy Of Force
The reserve is one named component of economy of force — the hedge against decisive-point misidentification.'reserve is one component of economy of force, not the prime.'. After the engineering_design frame is stripped away, the retained structural roles are those of Economy Of Force: Deliberate minimum-sufficient under-resourcing of non-decisive efforts so that mass can be concentrated at the decisive point. Reserve adds the local frame and commitments expressed in its identity: Deliberately maintained surplus held beyond expected need so the system can absorb variation, uncertainty, or shock without failing. The parent pattern remains recognizable without that vocabulary, while the child is the framed realization of it. That preservation test establishes decomposition rather than taxonomic subsumption.
Hierarchy path (1) — routes to 1 parentless root
- Economy Of Force → Allocation → Scarcity → Constraint
Neighborhood in Abstraction Space¶
Economy Of Force sits in a sparse region of abstraction space (68th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.
Family — Unclustered & Miscellaneous (424 primes)
Nearest neighbors
- Mass — 0.76
- Concentration — 0.71
- Opportunity Cost — 0.70
- Non-Zero-Sum Game — 0.69
- Sacrifice Periphery To Defend Core — 0.69
Computed from structural-signature embeddings · 2026-09-10
Not to Be Confused With¶
The most consequential confusion is with prioritization, because the two are routinely treated as the same move and the conflation is exactly what makes resource strategy fail. Prioritisation is the cognitive ranking of efforts — deciding which matters most, producing an ordered list everyone can agree on. Economy of force is the resource move that must follow the ranking: deliberately cutting allocation to the lower-ranked efforts down to their minimum-viable level so the freed mass can be concentrated at the decisive point. The distinction is that ranking is cheap and cognitive while reallocation is expensive and political — and the prime's whole point is that the second step, the actual cut, is the one that usually fails to happen. "Prioritisation theatre" is the signature pathology: everyone agrees on the ranked list, no one's allocation changes, and the decisive effort stays unfunded because the freed mass was never actually freed. Economy of force insists that a priority ordering which no budget reflects is not economy of force at all — it is ranking without the cut, and the decisive concentration it was meant to enable never happens. The confusion is dangerous precisely because prioritisation feels like the hard part (the debate over what matters), when the genuinely hard part is the politically costly act of starving the lower ranks. A practitioner who stops at prioritisation has done the cognitive work and skipped the resource work; economy of force is the discipline that ranking means something only when allocation is actually removed from the lower ranks.
A second genuine confusion is with concentration (the massing at the decisive point), of which economy of force is the complement, not a synonym. Concentration names the visible, celebrated move — bringing overwhelming force to bear at the decisive point. Economy of force names the invisible, disciplined move that makes concentration possible — the deliberate under-resourcing of everything else to its minimum-viable floor, so that there is freed mass to concentrate. They are two halves of one allocation: you cannot concentrate at the decisive point without economy of force everywhere else, because the mass has to come from somewhere. The confusion matters because attention naturally goes to concentration (the breakthrough, the big bet, the deep-work block) while the harder discipline is the starving of the secondary — and a reasoner who thinks only in terms of concentration asks "where do I mass?" without asking "what do I deliberately starve to its floor to free that mass?" Economy of force's distinctive and under-practised contribution is the licence to deliberately starve the secondary right things — a different and harder move than starving the wrong things — which the concentration framing alone does not supply.
For the practitioner the distinctions are a sequence, and the failure is stopping early. Prioritisation ranks (necessary but cheap). Economy of force cuts the lower ranks to their minimum-viable floor (the politically costly step that ranking is meaningless without). Concentration masses the freed resource at the decisive point (the visible payoff). The reserve hedges the decisive-point judgement. Skipping the cut — mistaking prioritisation for the whole job, or focusing on concentration without the disciplined starving that funds it — leaves the decisive effort unfunded while everyone agrees it matters most.
Solution Archetypes¶
Solution archetypes in the catalog that build on this prime — directly (this prime is a source ingredient) or as a related prime.
Built directly on this prime (3)
- Central Reserve Redeployment: Hold a mobile shared reserve where paths to several fronts are short, then shift and concentrate it fast enough to create local advantage before dispersed alternatives can coordinate.▸ Mechanisms (18)
- Capacity-Aware Dispatch Optimizer — Recommends which reserve unit to commit to which competing front by scoring front priority, response windows, route time, compatibility, local-cover floors, and turnaround into a ranked deployment — while leaving the commit to a human.
- Dispatch Center — A staffed coordinating hub that holds the one live picture of every front, turns a front's request into an assembled deployment of the reserve, and coordinates the handoff — while hardening itself against becoming the single point of failure.
- Dynamic Staffing Schedule — Continuously reassigns a shared pool of people to the fronts that need them, floating only those eligible to move and never stripping any front below its protected coverage floor.
- Incident Command Structure — Stands up a temporary chain of command that names who stewards the central reserve and who is pre-authorized to release it, so the shared pool can be committed to a front in minutes instead of meetings.
- Logistics Routing Plan — The standing plan that decides which front the reserve flows to first and in what feasible sequence, encoding an explicit front-priority ranking against a map of the network's capacities and constraints.
- Multi-Front Dispatch Board — A live shared display of competing front requests, current reserve positions, route state, and arrival estimates — with unresolved allocation conflicts flagged — so the reserve is committed against one common picture rather than scattered reports.
- Mutual-Aid Dispatch Board — A shared board where every front posts its need and every unit its lendable capacity, matching the two on one live map while locking each committed resource so it can't be promised to two fronts at once.
- Network Capacity Dashboard — A live topological view of a flow network that shows where capacity is saturated, where it sits idle, and where the binding bottleneck has moved.
- Prepositioned Resource Cache — Places a curated slice of the reserve forward, near the fronts, so its final deployment time is already spent — while what to stock and how to refill it stay under central control.
- Rapid Status Broadcast and Stop Signal — Keeps every front synchronized on current status and, when a risk signal fires, pushes an immediate authoritative halt or recall over a direct channel that still reaches everyone when the normal path is down.
- Recall and Reconstitution Protocol — The procedure that brings a committed reserve back, reconciles its state and authority, replenishes what it spent, and restores it to ready — so the same reserve can answer the next front instead of being used up by the last one.
- Reserve Readiness Rotation — A standing rota that cycles people or assets through ready, deployed, recovering, maintenance, and unavailable states so a protected floor of capacity is always ready at the hub without exhausting the pool.
- Reserve Release Playbook — The documented rulebook for spending the reserve without destroying it — bounding each drawdown against a protected floor and binding every release to a duty to refill.
- Sequential Concentration Drill — A live rehearsal that moves the same reserve through more than one front in sequence — setup, handoff, recall, reconstitution between commitments — to prove the central position really delivers concentration in time, and to re-check that it still does.
- Simultaneous-Front Stress Test — An adversarial test of whether correlated demands, route failures, and false alarms can exhaust the reserve or force it below minimum local cover — setting the guardrail on how much simultaneous draw the pool can safely absorb.
- Standby Transport Corridor — Keeps a pre-qualified alternate route between the reserve and the fronts continuously ready and health-checked, so a redeployment can still complete inside its window when the primary path fails.
- Strategic Reserve — Constitutes a protected, centrally-held pool of mobile capacity — with defined membership and a single accountable steward — that can be committed across ordinary boundaries to wherever it is needed most.
- Travel-Time Matrix — Tabulates the full response time from each candidate reserve location to each front under normal, degraded, and surge conditions, turning 'centrally positioned' from a claim on a map into a checkable number.
- Decisive-Point Concentration: Create local superiority at the decisive point by massing finite effort there and deliberately accepting bounded weakness elsewhere.▸ Mechanisms (12)
- After-Action Concentration Review — After a concentration episode, reconstructs whether massing at the chosen point actually paid off, updates the model of how return scales with concentration, and feeds the lesson into the next decision.
- Focus Block Schedule — Reserves recurring, defended blocks of time for the one task that decides the most, and batches or sheds everything shallow into the margins.
- Incident-Command Resource Staging — Puts the whole resource pool under one commander, masses it at the point of main effort, holds a reserve to reinforce success, and plans the orderly stand-down.
- Main-Effort Statement — Names one main effort as the decisive point, says who owns it, and states plainly what the organization accepts giving up everywhere else.
- Minimum-Service-Floor Dashboard — Watches the deliberately-starved areas against pre-set minimum floors and fires a reallocation trigger the moment economizing there begins to cause real harm.
- Pivotal Segment Campaign — Pours a disproportionate share of go-to-market effort into the one customer segment that unlocks the rest, driving it past a decisive share threshold within a single window while other segments run on a maintenance baseline.
- Priority Budget Reallocation — Concentrates a divisible budget on the decisive few line items by deliberately cutting the many toward a defined floor, and books the opportunity cost as an authorized decision rather than a quiet trim.
- Reserve Release Gate — Holds a reserve uncommitted against the pull to spend it piecemeal, and defines the threshold conditions under which it is released all at once to reinforce success at the decisive point.
- Schwerpunkt Directive — A commander's order that fixes the point of main effort as binding intent, gives its owner priority of support, and masks the choice behind feints — subordinating the whole force to one decisive point.
- Surge Staffing Roster — Names exactly who moves to the decisive point, from which teams and for how long, and specifies the backfill the drained sources keep and the rest the surged crew is owed.
- Time-Boxed Focus Sprint — Concentrates a team's whole effort on one objective inside a hard, short, non-renewable time box — shielded from interruption, checked at the end, and deliberately followed by recovery rather than renewed into permanent crunch.
- Triage Priority List — Ranks competing demands by where effort changes the outcome and draws a hard cutoff, massing scarce capacity above the line while the deferred tail is set aside openly and re-checked as conditions shift.
- Sequential Local Superiority: When the whole opposition is too strong, make the contest local, sequential, and non-recombining until each part can be resolved with concentrated capacity.▸ Mechanisms (10)
- After-Action Sequence Update — Turns what each resolved segment taught into a revised field map and a re-ordered sequence for the segments still ahead.
- Economy of Force Allocation Sheet — Apportions force across fronts — minimum-safe coverage on the non-decisive, concentration on the decisive, a named reserve held back — as one explicit ledger.
- Local Overmatch Ratio Dashboard — Continuously compares committed capacity against a chosen segment's resolution threshold so focus is never mistaken for genuine local superiority.
- Phase-Gate Resolution Review — A go/no-go gate that refuses to advance the sequence until the current segment is stably resolved and the next segment is still the right next segment.
- Recombination Risk Register — Tracks the leading signs that separated segments are beginning to reconnect, coordinate, or regenerate — before they combine faster than the sequence can resolve them.
- Reintegration Checkpoint — Verifies that a resolved segment holds when it is folded back into the wider system, and plans the handoff that keeps it from regenerating.
- Reserve Release Trigger — A pre-committed rule that releases held-back reserve capacity the moment a segment's local overmatch slips below its safety margin.
- Safe-Stop and De-escalation Trigger — A pre-set rule that halts and unwinds the sequence when ethical, legal, or collateral harm rises past the justification for continuing.
- Scope Control Order — States what is inside the current engagement and what is deliberately deferred, and closes the channels through which the wider field could aggregate against it.
- Segment Priority Matrix — Ranks candidate segments by separability, capacity fit, recombination delay, and strategic payoff, then fixes the order in which they are engaged.
Also a related prime in 2 archetypes
- Position-Based Leverage Design: Gain leverage by changing where the actor, resource, interface, signal, or option sits in the field rather than by increasing force at the current location.
- Shared-Input Variety Platform Design: Produce varied outputs more cheaply by sharing the inputs they can truly hold in common while protecting the differences that still matter.
References¶
[1] U.S. Army. ADP 3-0: Operations. Washington, DC: Headquarters, Department of the Army, 2017. States economy of force among the principles of war: allocate minimum essential combat power to secondary efforts so mass can be concentrated at the decisive point. registry ↩a ↩b ↩c
[2] Swensen, David F. Pioneering Portfolio Management: An Unconventional Approach to Institutional Investment. Rev. ed. New York: Free Press, 2009. Argues for concentrating capital in high-conviction positions while holding minimal exposure elsewhere to preserve optionality and limit tracking error. registry ↩a ↩b
[3] Drucker, Peter F. The Effective Executive. New York: Harper & Row, 1967. Advances concentration of effort on the few results that matter and minimum engagement with low-value demands on attention. registry ↩
[4] McConnell, Steve. Code Complete: A Practical Handbook of Software Construction. 2nd ed. Redmond, WA: Microsoft Press, 2004. Treats matching engineering effort to code-path importance and warns against gold-plating rarely-executed branches. registry ↩a ↩b ↩c
[5] Zoltners, Andris A., Prabhakant Sinha, and Sally E. Lorimer. Building a Winning Sales Force. New York: AMACOM, 2009. Discusses concentrating sales coverage on high-value accounts while maintaining minimum-viable coverage of low-tier accounts to defend share. registry ↩
[6] Sparrow, Malcolm K. The Regulatory Craft: Controlling Risks, Solving Problems, and Managing Compliance. Washington, DC: Brookings Institution Press, 2000. Argues for concentrating enforcement on high-impact violations while maintaining minimum-viable enforcement to sustain norm legitimacy. registry ↩