Skip to content

Allocation & Prioritization

← Back to Mechanisms by Solution Family

Solutions that distribute scarce attention, effort, money, capacity, or opportunity among competing claims and make the order of service explicit.

106 mechanisms across 9 solution archetypes in this solution family. A mechanism inherits the primary family of the archetype it instantiates; family is about the move the solution makes, not the domain where it originated.

Cost-Asymmetric Preference Revelation Design

Reveal held preferences without forcing dangerous exposure by mapping expression costs, protecting low-risk signal channels, and translating aggregate private information into safer public choice and norm updates.

10 mechanisms · View full solution archetype

Decisive-Point Concentration

Create local superiority at the decisive point by massing finite effort there and deliberately accepting bounded weakness elsewhere.

12 mechanisms · View full solution archetype

  • 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.

Layer-Appropriate Capability Placement

Place a capability in the layer that can express and govern it well, then let narrower embedded layers delegate through explicit contracts instead of rebuilding miniature host platforms.

15 mechanisms · View full solution archetype

  • Adapter Layer — A thin translation layer that maps a host's calls, data, and conventions onto the interface the subsystem expects — so the subsystem can consume host capability, and later swap which host provides it, without its own code changing.
  • API Versioning — Exposes a host capability as explicitly versioned interfaces that coexist, so consumers migrate on their own schedule and a change to the host never becomes a forced, simultaneous break for everyone downstream.
  • Architecture Decision Record — Records why a complexity-adding placement choice was accepted — the criterion applied, the host-dependency it commits to, and the conditions that would reopen it — so the decision is revisited on evidence, not relitigated from memory.
  • Capability Catalog — A discoverable directory of what the host and shared layers already provide, who owns each capability, and how to consume it — so teams delegate to an existing facility instead of rebuilding it because they couldn't find it.
  • Capability-Promotion Review — A recurring review that spots the same capability being rebuilt locally across teams and decides whether it should be promoted into a supported host or shared layer — turning repeated duplication into an owned, escalated decision.
  • Compatibility Bridge or Shim — A deliberately temporary layer that makes old local callers keep working against a newly promoted host capability during a migration — carrying them across so the duplicate facility can be retired, then expiring itself.
  • Extension-Request Workflow — Routes a recurring need the embedded layer can't support up to the host owner for triage and disposition, so a real requirement is escalated rather than quietly rebuilt locally.
  • Host-Dependency Fallback Drill — Rehearses host failure — degraded, disconnected, incompatible, or withdrawn — before the dependency is load-bearing, so the subsystem's graceful-degradation rules are proven rather than assumed.
  • Host-Service API Delegation — Forwards a subsystem's capability request to the authoritative host service across a bounded, versioned API, so the host stays the single source of truth instead of being cloned locally.
  • Interface Contract Test — Turns the promises a delegated host interface makes — permissions, isolation, error and capacity behavior, and what happens when the host is unavailable — into automated pass/fail checks, so delegation is verified rather than assumed.
  • Layer-Placement Fitness Check — Scores each candidate layer against the requirement it would have to own — variety, expressiveness, security, lifecycle cost, governance — and names the layer that can carry the capability well.
  • Privileged Host Escape Hatch — Grants time-bounded, least-privilege access to a host capability that sits outside the ordinary embedded surface, so a rare genuine need is met without permanently widening the interface.
  • Service Layer or API Facade — A single stable interface that upper layers call instead of reaching into host services directly — presenting one curated contract and hiding the lower-level detail, so what sits behind it can change without the callers noticing.
  • Shadow-Platform Audit — Inspects embedded systems for host-like facilities, duplicate authoritative state, and unbounded local extension growth, and registers each shadow platform it finds.
  • Temporary Local Shim with Expiry — Permits a narrow local stand-in for a missing host capability, but only with an explicit scope and a hard expiry date, so the stopgap can't quietly harden into a permanent shadow platform.

Net-Additive Contribution Intake

Accept, reshape, redirect, defer, or decline well-intended contributions according to their full net value, available sponsorship, and effect on protected primary work.

17 mechanisms · View full solution archetype

  • Automated Classification and Routing — Reads each standardized offer and mechanically sends it to the right destination — review queue, self-service path, alternate recipient, or decline — applying triage rules at volume without staff touching every one.
  • Batch Volunteer Onboarding — Onboards a wave of similar accepted volunteers together — shared orientation and access setup in one pass — so a surge of willing help is absorbed without a linear pile-up of per-person coordination.
  • Bounded Contribution Pilot — Admits an uncertain contribution into a small, reversible sandbox with pre-set success, stop, and handoff criteria, so its real net value is observed before any full commitment.
  • Clean Rejection Notice — Closes an unsuitable offer with a plain, final disposition and no ambiguous 'maybe later,' so the contributor gets a real answer and the system carries no hidden obligation.
  • Contribution Net-Value Review — Weighs a contribution's expected benefit against its full lifetime coordination cost to judge whether it is genuinely net-additive — and recommends accept, reshape, redirect, defer, or decline.
  • Contribution Onboarding Packet — The written working agreement handed to an accepted contributor — scope, ownership, support, credit, and exit terms — so the relationship runs on stated expectations rather than assumed ones.
  • Intake Pause — A pre-authorized stop that halts all new intake when protected work, sponsor bandwidth, or maintenance capacity is at risk — trading incoming help for the primary work already underway.
  • Intake Portal — Gives every well-intended offer a single standard front door, so nothing reaches the team by side channel and the total volume of incoming help becomes visible in one place.
  • Material Donation Acceptance List — A published specification of exactly which physical goods can be accepted — item types, condition, quantity, packaging, timing, storage, liability, and disposal — so unusable donations are screened out before they arrive.
  • Overflow Redirection — Sends offers the system can't absorb right now to a later window, a partner program, or an external recipient — so surplus help is placed rather than dropped or hoarded.
  • Post-Integration Contribution Review — A scheduled look-back that compares a contribution's promised value against what it actually delivered — hidden coordination cost, work displaced, upkeep incurred — and feeds the verdict back into intake criteria.
  • Pre-Screening Form — A short structured form contributors fill in themselves — fit, provenance, restrictions, support offered, timing, risk — so an offer arrives as comparable data before any staff time is spent on it.
  • Refusal Script — Reusable, respectful language for saying no or not-yet — grounded in a legitimate right to refuse — so front-line people can decline without negotiating, over-apologizing, or damaging the relationship.
  • Requested Contribution Menu — Publishes a current, bounded list of the contributions the system actually needs — with specifications, timing, and exclusions — so willing contributors can self-serve toward net-additive help.
  • Side-Channel Redirect Notice — A reusable, face-saving message that moves an informally-offered contribution back onto the common intake path — without making the person who received it personally responsible for evaluating it.
  • Sponsor-Required Acceptance Protocol — Blocks acceptance of a contribution until a named owner commits the coordination budget to carry it, converting a free-looking offer into an obligation someone has agreed to hold.
  • Support Ticket Router — Turns each accepted offer into a tracked work item with an owner and a handoff, so contribution work flows through the same visible queue as everything else instead of landing on someone's desk untracked.

Public Goods Provision

Create funding, contribution, or governance mechanisms for resources whose benefits are shared and hard to exclude.

13 mechanisms · View full solution archetype

  • Assurance Contract — Collects conditional pledges that bind only once enough others also commit, so no one has to pay first for a good that needs a crowd.
  • Collective Procurement — Pools the demand of many actors who each can't justify a shared service alone, then buys and governs it once on behalf of all of them.
  • Cooperative Ownership — Vests ownership and governance of the shared good in its beneficiaries, so the people who rely on it also decide, fund, and answer for it.
  • Crowdfunding or Pledge Drive — Mobilizes many small voluntary contributions toward a visible funding goal, using momentum and a public target to turn diffuse goodwill into a pool.
  • Grant or Subsidy Program — Funds a good that private incentives would underprovide by paying an external provider against defined outcomes, then measuring whether the public value actually appeared.
  • Maintenance Endowment or Reserve — Sets aside a standing fund whose income pays for ongoing upkeep, so the good's maintenance is funded in advance rather than begged for each year.
  • Mandatory Contribution Scheme — Compels a defined class of beneficiaries or responsible parties to contribute, on the authority of a rule rather than their willingness, when voluntary funding repeatedly fails.
  • Matching Fund — Uses one committed contribution to unlock others by promising to match what the crowd gives, making each contributor's gift feel larger and more decisive.
  • Membership Dues or Assessments — Funds a shared good for a bounded group by charging recurring dues tied to membership, where paying in and the right to use the good are the same status.
  • Open-Source Sponsorship — Channels funding from downstream beneficiaries to the maintainers of shared digital infrastructure, paying for the upkeep that keeps a widely-used common resource alive.
  • Public Funding or Taxation — Funds a broad civic good from a whole population through compulsory, legitimacy-backed contribution, for benefits so widely shared that excluding non-payers makes no sense.
  • Public–Private or Multi-Stakeholder Partnership — Provides a good no single actor can legitimately or affordably create alone by blending funding, authority, and capability across sectors under a shared governance structure.
  • Volunteer Contribution Rota — Sustains a shared good through scheduled in-kind labor, assigning named people to named turns so upkeep is contributed as time and effort rather than money.

Resource Rationing

Govern unavoidable scarcity through explicit, legitimate, reviewable, and temporary limits on access.

12 mechanisms · View full solution archetype

  • Anti-Hoarding and Diversion Control — Detects duplicate claims, stockpiling, privileged diversion, resale, and coordinated circumvention using proportional controls and an explicit boundary for legitimate sharing.
  • Claims Adjudication and Rapid Appeal Panel — Reviews contested, urgent, or exception claims with sufficient independence, time limits, recorded reasons, accessibility support, and authority to correct decisions.
  • Criterion-Version and Decision Audit Log — Links each rationing decision to the active criterion version, evidence, authority, reason, appeal outcome, and later correction without making sensitive data broadly visible.
  • Distributional Denial and Burden Dashboard — Surfaces grant, denial, delay, appeal, burden, and harm rates by relevant population and geography while enforcing privacy and small-cell protections.
  • Independent Rationing Equity Audit — Tests whether stated criteria, actual decisions, enforcement, and appeal outcomes align, including disparate burdens, proxy discrimination, privileged bypass, and missing claimant populations.
  • Priority Classification and Tie-Break Protocol — Applies published eligibility and priority criteria, then resolves equivalent claims through a declared queue, rotation, lottery, equal-share, or other tie procedure.
  • Protected Minimum and Accommodation Override — Prevents ordinary ration ceilings or priority scores from violating rights floors, disability accommodations, essential survival minima, or non-discrimination duties.
  • Provisional Grant Pending Verification — Provides temporary access when urgency is high and evidence cannot reasonably be completed before harm, followed by proportionate verification and non-punitive correction.
  • Ration Card, Token, or Allowance Ledger — Issues and reconciles claimant-specific or class-specific access allowances while preventing duplicate redemption and preserving accessible non-digital routes.
  • Rationing Relaxation and Sunset Protocol — Reduces restrictions or terminates the regime when recovery thresholds are met, removes emergency data and controls, settles outstanding claims, and records the after-action review.
  • Scarcity Declaration and Activation Protocol — Verifies shortage evidence, identifies the accountable declaring authority, publishes scope and duration, activates the criterion version, and starts mandatory review clocks.
  • Unmet-Need Supply Escalation Packet — Aggregates residual essential need and recurring denial patterns into accountable requests for procurement, capacity expansion, substitution, mutual aid, or policy relief.

Role-Expectation Conflict Reconciliation

Make incompatible role expectations visible and govern which duty controls, what must be redesigned, and when a person needs recusal, substitution, support, sequencing, or release.

6 mechanisms · View full solution archetype

Role-Scoped Disclosure Minimization

Release only the role- and purpose-justified subset of a richer record, removing surplus at the producer boundary before it can propagate.

12 mechanisms · View full solution archetype

  • API Response Projection — Shapes the outgoing response at the producer, composing it from an allow-list of only the fields a given consumer's role and purpose justify, so surplus data is never serialized and never leaves the source.
  • Attribute-Based Access Policy — Computes at request time what a consumer may receive by evaluating attributes of the actor, resource, purpose, and context against per-field necessity rules — so the disclosed view narrows or widens with the situation instead of being a fixed grant.
  • Break-Glass Disclosure Workflow — Grants a normally-forbidden disclosure in a genuine emergency through a deliberate, high-friction override that time-boxes the access and notifies the data's steward — so the exception stays available but never quiet, routine, or free.
  • Claim Certificate or Verifiable Credential — Packages a single attested fact — 'over 21', 'currently licensed', 'in good standing' — as a portable, cryptographically-verifiable credential the holder presents in place of the underlying record, and that can expire or be revoked.
  • Data Loss Prevention Policy — Watches data in motion at the egress boundary, classifying content by sensitivity and flagging or blocking transfers where surplus — or an aggregation of individually-innocuous fields — is leaving for a context it shouldn't.
  • Derived Eligibility or Status Answer — Answers the consumer's actual question with a computed predicate or status — 'meets the income threshold: yes' — returned live in place of the underlying record, so the source releases a conclusion instead of the data behind it.
  • Disclosure Audit Log — Records every disclosure — who received which fields, when, and under what justification — as an append-only trail that answers 'who saw this?' after the fact and drives subject notification.
  • Field-Level Redaction — Removes or blacks out the specific fields flagged sensitive or surplus from an outgoing record, at the producer, so what leaves carries only what the recipient may see.
  • Privacy Impact Review — A pre-release assessment that maps what a source record actually contains and what a recipient could infer or re-identify from a proposed disclosure, before the disclosure is designed.
  • Purpose-Based Access Request — Makes a consumer declare, before any data flows, the specific purpose and the task-justified fields it needs — so access is granted against a stated need rather than a standing entitlement.
  • Role-Based View — Gives each role a standing, pre-shaped window onto the source record that exposes only the fields that role's work requires, so the surplus is never in the view to leak.
  • Tokenization or Masking — Replaces each sensitive value with a surrogate token or masked form, so downstream systems can still key, join, and display records without ever holding the raw value.

Satiation-Aware Allocation

Allocate resources according to marginal need or utility, recognizing that additional units matter less after partial satisfaction.

9 mechanisms · View full solution archetype