Skip to content

Flow & Routing

← Back to Mechanisms by Solution Family

Solutions that direct material, information, demand, work, or traffic through paths and stages to improve movement and avoid congestion.

146 mechanisms across 17 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.

Bottleneck Identification and Relief

Find the stage, resource, role, queue, or transition that limits whole-system throughput, then relieve, protect, redesign, or prioritize around it.

10 mechanisms · View full solution archetype

  • Automation of Bottleneck Stage — Relieves the binding stage by replacing its manual work with machine or software execution — changing the kind of capacity at the constraint, not just the amount.
  • Bottleneck Analysis Workshop — A facilitated cross-functional session that builds one shared flow map and reconciles the competing local views of different teams into a single, agreed system constraint.
  • Bottleneck Buffer — A deliberately maintained reserve of ready work staged just before the constraint, so upstream variability never leaves the binding stage idle.
  • Bottleneck Priority Rule — A prioritization policy that decides, when demand exceeds the constraint's capacity, which work the scarce stage takes first — aligned to the system objective, not to whoever shouts loudest.
  • Capacity Expansion — Relieves the constraint by investing in more of the same binding capacity — additional units, hours, machines, or licensed throughput at the stage that limits the whole.
  • Input Quality Check — Screens incoming work at the door of the constraint, admitting only complete, correct, and relevant items so scarce capacity is never spent on avoidable clarification or rework.
  • Queue Analysis — Reads queue length, wait time, and service rate across a flow to locate the binding station and size how far work is backing up behind it.
  • Staffing Relief / Cross-Training — Widens the constraint by adding people or cross-skilling existing ones, so more qualified hands can serve the bottleneck when it binds and flex away when it moves.
  • Theory of Constraints Cycle — Runs Goldratt's five focusing steps as a loop — define system throughput, find the constraint, exploit it, subordinate everything else, elevate it, then repeat because the constraint moves.
  • Work-in-Progress Limit — Caps how many items may be in a stage or flow at once, so upstream work can't flood the constraint and cycle time stays short.

Bounded Random-Walk Navigation

Let randomness move, but govern the walk: define step rules, boundaries, checkpoints, reset conditions, and drift tests so cumulative wandering stays useful and safe.

10 mechanisms · View full solution archetype

  • Absorbing-State Trigger — Names the states a walk must never re-emerge from and fires an irreversible halt the instant the trajectory enters one.
  • Cumulative Displacement Dashboard — Tracks how far a live process has drifted from its origin and plots it against the expected-spread band, so ordinary wandering and genuine excursions are told apart at a glance.
  • Drift vs. Noise Test — Applies a formal significance test to a stretch of the path, refusing to call it a trend, streak, or skill until its displacement exceeds what a pure random walk would routinely throw up.
  • Exploration Capture Protocol — Recognizes when aimless wandering has stumbled onto something valuable and banks that state as a new reference before the walk drifts on and loses it.
  • Path-Trace Audit — Reconstructs a completed walk from its recorded log to see which boundaries it touched and whether its path was actually governed — or merely lucky.
  • Random-Restart Schedule — Teleports a stalled or trapped walk back to a fresh random starting point on a set schedule, so no single dead-end region can hold the search forever.
  • Random-Walk Simulation — Runs many synthetic copies of the walk forward from an assumed step rule to forecast how far it typically wanders, how fast, and how often it reaches the edges — before a single real step is taken.
  • Reflecting-Boundary Rule — Turns a limit into a wall that bounces the walk back inward instead of ending it, keeping the trajectory inside a safe zone while letting it keep wandering.
  • Step-Size Throttle — Governs how large each increment may be — widening steps to explore, shrinking them to settle — on a schedule tied to progress.
  • Walk-Budget Review — Periodically checks how much of the exploration budget the wandering has burned and rules on whether continued drift is still buying enough discovery to justify its cost.

Endpoint Fan-Out Fulfillment

Design the deconsolidation, local staging, routing, service-mode, access, evidence, and recovery layer that turns efficient trunk flow into verified endpoint completion.

20 mechanisms · View full solution archetype

  • Address or Endpoint Validation — Checks each endpoint's identity, location, eligibility, connectivity, and access prerequisites before anything is dispatched, so effort is only spent on endpoints that can actually be served.
  • Community Access Point — Stands up a trusted local place — staffed with people who know the community — where endpoints can get assisted pickup, connectivity, identity help, or translation to complete a service they couldn't finish alone.
  • Demand Aggregation Window — Briefly holds compatible low-density requests until enough accumulate to serve them together as one efficient cluster, instead of dispatching each sparse request on its own.
  • Dynamic Route Optimization — Continuously recomputes routes and assignments from live demand, capacity, traffic, priority, and failure signals, so the fan-out adapts to conditions on the ground instead of following a fixed plan.
  • Endpoint Completion Dashboard — Puts verified endpoint completion — not trunk throughput or dispatch — at the center of the view, exposing the gap between what was sent and what actually arrived, sliced by segment.
  • Endpoint Cost-to-Serve Analysis — Estimates the full cost of successfully completing service at each class of endpoint — including the last-mile share that trunk-level accounting hides — so the true economics of the edge become visible.
  • Exception Queue — Pulls the endpoint cases that don't fit the standard flow into a dedicated queue with its own capacity and clock, so the main line keeps moving and the oddballs still get resolved.
  • Failed-Attempt Recovery Workflow — Turns a failed endpoint attempt into a classified, routed recovery — diagnosing why it failed and sending it to correction, an alternate mode, a reschedule, or escalation — so one miss doesn't become a permanent non-completion.
  • Geospatial Service-Area Mapping — Turns endpoint locations, travel times, terrain barriers, and service deserts into one spatial picture that shows where the fan-out is hard and where local staging could sit.
  • Local Dispatch or Field Team — Standing local operational capacity — people who know the ground — assigned to work the last leg, clear on-site obstacles, and close the exceptions no ticket can specify.
  • Local Inventory or Edge Cache — A forward-placed buffer of the frequently-needed goods, data, or capability held close to endpoints, so the common request is served locally — fast, and still served when the trunk is slow or down.
  • Local Partner or Agent Network — Delegates endpoint completion to trained third-party local actors under an explicit contract that defines what 'done' means and where the system's responsibility hands off to theirs.
  • Micro-Hub or Pickup-Point Network — Local nodes where consolidated trunk flow is broken down and staged for short final legs or self-collection — relocating the handoff off the doorstep to a dense, efficient point.
  • Mobile Service Unit — A self-contained unit that travels to sparse or hard-to-reach endpoint clusters, bringing the goods, equipment, or expertise to recipients instead of requiring them to come to a fixed point.
  • Multimodal Delivery Switching — Maintains a portfolio of delivery modes and moves an endpoint from one to another — home, pickup, mobile, partner, assisted, remote — when its conditions, cost, or repeated failures change which mode fits.
  • Proof-of-Completion Capture — Captures just enough verifiable evidence that an endpoint was actually served — a signature, photo, scan, or confirmation — proportionate to the stakes, so completion is provable without over-collecting.
  • Route Clustering and Territory Design — Groups scattered endpoints into service clusters and territories that lift route density and balance workload, while protecting latency limits, capacity, equity, and the sparse tail that clustering tends to strand.
  • Scheduled Service Window — Carves out protected, recurring time to repair, patch, replace, and clean up endpoints so upkeep never has to fight live demand for the same capacity.
  • Targeted Outreach Campaign — Goes out and finds the specific endpoints that are stuck — missing information, blocked by an access barrier — and proactively removes the blocker so they can complete, instead of waiting for them to come to the system.
  • Transparent Cross-Subsidy Schedule — An explicit, reviewable rule that funds high-cost or essential endpoints out of pooled system revenue, making the who-pays-for-whom of universal service visible instead of hidden.

Fast/Slow Path Routing

Route routine cases through a cheap, safe fast path while sending exceptional, ambiguous, risky, or high-value cases to a deliberately resourced slow path.

8 mechanisms · View full solution archetype

Flow Channelization

Confine diffuse or chaotic flow into defined channels so it can be directed, measured, protected, or governed.

8 mechanisms · View full solution archetype

  • Channel Monitoring Dashboard — Puts a channel's health — volume, load against capacity, and leakage — on one live surface, so overload is seen and acted on rather than discovered at failure.
  • Data Conduit — Moves information through one defined stream that validates what enters and confirms what is delivered, replacing untracked point-to-point scripts with a governed, observable path.
  • Drainage Channel — Confines diffuse runoff inside bounded banks and directs it along a rated path to a safe discharge, so it flows where intended instead of spreading into vulnerable ground.
  • Intake Queue — Holds admitted work in an ordered, priority-ranked line with explicit rules for who advances, who may legitimately jump, and what 'done' means, so nothing waits invisibly or forever.
  • Overflow Lane or Spillway — A normally-dormant surge path that opens only when the primary channel exceeds its capacity, carrying the excess along a planned route instead of letting it back up or spill.
  • Service Channel Portal — One official front door that consolidates scattered requests behind a single governed intake, with defined submission requirements and an accessible alternate for those the standard path would exclude.
  • Traffic Lane — Separates incompatible flow classes into their own bounded routes, admitting only eligible traffic and granting priority classes a dedicated lane, so faster and slower movement stop colliding.
  • Workflow Swimlane — A design diagram that assigns each strand of work to its own responsibility lane and exposes exactly where flow crosses a boundary or leaks between owners.

Flow Diversion / Rerouting

Redirect flow through an alternate viable path when the current route becomes blocked, overloaded, or harmful, rather than stopping the flow.

0 mechanisms · View full solution archetype

No mechanism currently instantiates this archetype as its primary archetype.

Gestalt Continuation and Grouping Activation

When a viewer must infer a path, group, sequence, or motion from static or partial cues, arrange the field so perception completes the intended route rather than inventing a misleading one.

7 mechanisms · View full solution archetype

  • Attention Gradient Following — Builds a smooth gradient of visual weight so attention slides from the most prominent element down to the least in a predictable order, without a drawn path.
  • Closure-Based Completion — Leaves a single form or sequence deliberately incomplete so the viewer's perception supplies the missing piece and sees a whole that was never drawn.
  • False-Continuation Interruption — Deliberately breaks a continuation or grouping cue at a boundary so the eye stops instead of wrongly connecting unrelated elements into one path or set.
  • Good-Continuation Routing — Aligns and smoothly curves elements into a single unbroken line so the eye follows the intended route from a chosen anchor to a chosen destination without any label.
  • Grouping by Shared Cue — Gives related elements one shared visual attribute — proximity, similarity, or a common region — so the eye reads them as a single group without a label saying so.
  • Implied Motion from Orientation — Uses static orientation cues — motion streaks, elongation, repeated posture — to make a still image read as if its subject is moving in a direction, with nothing actually animating.
  • Rhythmic Scan Cadence — Repeats evenly spaced units to set a scanning tempo, giving the eye a steady beat of stops as it moves through a field from a downbeat entry.

Gradient Flattening

Reduce harmful disparities, pressure differences, or intensity gradients that drive instability, exploitation, unfairness, or destructive flow.

10 mechanisms · View full solution archetype

  • Access Equalization Policy — Reduces differences in access by standardizing minimum service, expanding reach, removing discriminatory barriers, or providing targeted support.
  • Banded Floor and Ceiling Rule — Uses allowed ranges, minimums, maximums, or ratios to keep variation from becoming destabilizing or unfair.
  • Buffer Pool or Reserve — Absorbs surges or deficits while longer-term structural flattening takes effect.
  • Gradient Dashboard — Makes the spread visible over time so actors can detect steepening, evaluate flattening, and spot displaced pressure.
  • Load Equalization — Compresses a workload, traffic, or demand gradient by moving work, adding support, smoothing peaks, or temporarily protecting overloaded regions.
  • Pressure Equalization — Reduces dangerous pressure differences through valves, vents, regulators, reserves, bypasses, or controlled release paths.
  • Price or Friction Compression — Reduces incentive gradients that drive arbitrage, extraction, panic movement, or avoidance behavior.
  • Progressive Redistribution — Moves more support toward low-resource or high-burden regions, or asks more from high-capacity regions, to compress harmful gaps.
  • Service Floor Upgrade — Raises baseline service in low-access or high-need regions so the gap narrows without necessarily reducing service quality elsewhere.
  • Subsidy or Equalization Fund — Creates a shared pool that raises the low side of an access, capacity, or service gradient without requiring each local actor to self-fund the correction.

Gradient-Guided Intervention

Use a gradient of stress, value, risk, need, or opportunity to decide where intervention should move, intensify, taper, or concentrate.

8 mechanisms · View full solution archetype

  • Gradient Descent or Ascent Search — Reads the local slope of an objective surface and takes a step in the improving direction, repeating until the ground goes flat, to walk toward a better point without mapping the whole field.
  • Heat Map — Renders a field's uneven intensity as a color-graded surface, so that where a variable runs hot or cold becomes legible at a glance.
  • Hotspot Response Plan — Concentrates a surge of action in the spatial, temporal, or network regions where incidents cluster, with built-in guardrails against displacing the problem or over-burdening the place.
  • Opportunity Scoring Model — Estimates, for every case in a field at once, the expected marginal benefit of acting on it, producing a comparable score so effort flows to where the upside is greatest.
  • Risk-Band Treatment Matrix — Cuts a continuous gradient into a small set of named bands and assigns each band a fixed, predefined treatment, turning a slope into a lookup table anyone can apply.
  • Risk-Based Inspection Schedule — Sets how often each asset is inspected in proportion to its failure risk, so high-risk items are checked frequently while a regulatory floor keeps low-risk ones from vanishing entirely.
  • Sentinel Indicator Dashboard — Tracks a small set of leading indicators that reveal where a gradient is moving before lagging outcomes confirm it, so attention arrives ahead of the problem.
  • Triaged Maintenance Route — Orders a crew's work into a ranked route through a fleet of assets by failure risk and consequence, so the highest-stakes items are reached first within the cycle's capacity.

Handoff Standardization

Standardize transitions between stages or actors so flow does not lose context, quality, state, or accountability at handoff points.

9 mechanisms · View full solution archetype

  • Case Transfer Dossier — Bundles a continuing matter's history, obligations, deadlines, and next actions into one package so a new owner can carry it forward without reconstructing it.
  • Chain-of-Custody Form — Records an unbroken, signed sequence of who held an item, when, and with what integrity check, so the transfer chain itself can be proven later.
  • Deployment Release Handoff — Transfers a shipped software release from the team that built it to the team that will operate it, under an explicit contract of rollback, monitoring, and on-call ownership.
  • Handoff Note Template — A reusable fixed-field form the sender fills at every handoff, so the same critical items are captured in the same shape every time.
  • Incident Escalation Note — Packages a live incident's severity, timeline, attempted fixes, and current hypotheses with a specific ask, so a higher tier can take over the decision without re-triaging.
  • Manufacturing Station Handoff — Passes a part and its state to the next workstation only after an inline check confirms the station's work is complete and within spec.
  • Shift-Change Briefing — A scheduled, face-to-face turnover where outgoing and incoming crews talk through live state and confirm understanding by read-back before responsibility changes hands.
  • Structured Handoff Checklist — A prompt list both parties run at handoff to confirm every must-transfer item was actually covered before the transfer is signed off.
  • Support Ticket Escalation — Moves a support case across a queue or tier boundary to a better-equipped owner while carrying its context, with defined paths to reroute or bounce back a mis-sent case.

Inversion of Control

Shift initiative or control from the usual actor to another layer, framework, recipient, or environment to reduce coupling, improve fit to context, or coordinate action more cleanly.

8 mechanisms · View full solution archetype

  • Callback Function — Allows one part of a system to provide behavior that another part invokes later when a lifecycle event, completion condition, or external signal occurs.
  • Dependency Injection Framework — Implements software inversion by letting a framework supply dependencies or call application behavior through configured interfaces instead of having application code directly construct or control everything.
  • Event Listener or Webhook — Lets external events or remote systems initiate behavior through a registered interface rather than requiring continuous polling or upstream push.
  • Just-in-Time Replenishment Rule — Triggers production or replenishment from actual downstream demand or threshold signals rather than forecast push alone.
  • Kanban Pull System — Uses downstream readiness or consumption to authorize upstream work, turning a push process into a governed pull process.
  • Learner-Led Inquiry Protocol — Lets learners initiate questions, projects, or evidence-seeking activity while instructors provide constraints, scaffolds, and feedback.
  • Participant Agenda Setting — Lets affected participants initiate topics, decisions, or priorities within a governed forum instead of only receiving a centrally defined agenda.
  • Recipient-Triggered Support Channel — Lets the person or unit experiencing need activate support when conditions are met rather than waiting for a provider-driven schedule.

Pipeline Staging

Divide a complex flow into ordered stages so each stage can specialize, coordinate handoffs, and preserve throughput, quality, and accountability.

8 mechanisms · View full solution archetype

  • Assembly Line Workflow — Implements pipeline staging by arranging repeated physical or service transformations into specialized stations with defined movement between them.
  • CI/CD Pipeline — Implements pipeline staging in software delivery by moving changes through build, test, review, deployment, and release stages with automated handoffs.
  • Clinical Care Pathway — Implements pipeline staging in care delivery by sequencing intake, triage, diagnosis, treatment, monitoring, discharge, and follow-up while preserving patient state.
  • Editorial Workflow — Implements pipeline staging for text or media by separating drafting, editing, fact-checking, approval, production, and publication responsibilities.
  • ETL or Data Processing Pipeline — Implements pipeline staging for data by moving records through extraction, validation, cleansing, enrichment, and loading stages while quarantining records that fail and preserving lineage.
  • Legal Procedure Sequence — Implements pipeline staging by ordering filings, disclosures, hearings, judgments, and appeals so process rights and evidentiary state are preserved.
  • Onboarding Workflow — Implements pipeline staging by sequencing orientation, account setup, training, practice, verification, and handoff into regular participation.
  • Research Review Pipeline — Implements pipeline staging by moving proposals, manuscripts, or evidence through screening, review, revision, decision, and archival stages.

Queue Partitioning

Split a shared queue into governed lanes so different classes of waiting work receive appropriate service without blocking or distorting one another.

9 mechanisms · View full solution archetype

  • Dedicated Worker Pool — Reserves a fixed block of servers, staff, or processors to a partition so its capacity is guaranteed — with borrowing rules and periodic resizing so the reservation doesn't strand idle capacity.
  • Express Lane — Splits off quick, simple items into a fast lane so they aren't stuck behind long ones — with a guardrail against gaming the 'simple' criterion and against stranding the complex work left behind.
  • Multi-Class Queue — Replaces one shared line with several durable class-keyed lanes under a single governing structure — fixing how many lanes exist, what class each holds, and how each lane's backlog stays visible.
  • Overflow Lane — Spills items or capacity across a lane boundary when a partition breaches its backlog or wait threshold, then merges back once the surge passes — so rigid lanes don't buckle under a spike.
  • Priority Lane — Carves out a fast lane for urgent, high-risk, or time-sensitive work — and governs the privilege so the fast path is a defensible service fit, not a favor.
  • Service-Type Queue — Splits waiting work by the kind of service it needs — billing, technical, security — so each lane can be bound to the staff, tools, and service standard that fit that kind of work.
  • Specialist Queue — Routes work that needs a distinct skill, authorization, or piece of equipment into its own lane with a named owner, so specialist cases stop bouncing through generalist queues.
  • Tenant or Segment Queue — Gives each tenant, account, or population segment its own lane so contractual promises are honored and one heavy actor can't crowd out the others — under an anti-discrimination rail.
  • Triage Router — Classifies each incoming item and directs it to the correct lane before it joins the wrong line — and corrects misroutes fast, so lane membership stays accurate.

Slot-Template Design

Define a stable template with variable slots so interchangeable elements can be substituted while preserving coherence, purpose, and compatibility.

9 mechanisms · View full solution archetype

  • Curriculum Template — A learning design scaffold with variable example, activity, assessment, and pacing slots.
  • Design System Component Slot — A design-system component exposes named content or behavior slots with allowed component types.
  • Document Template — A reusable document scaffold with fixed sections and variable fields or clauses.
  • Modular Form Schema — A structured form schema with fields, conditional sections, validation rules, and stored responses.
  • Plugin Slot Registration — A host system exposes extension points that approved plugins can fill through a defined interface.
  • Policy Template with Local Options — A shared policy scaffold with bounded fields for local parameters, approved exceptions, and implementation choices.
  • Product Configuration Matrix — A table or ruleset listing product option slots, allowed fills, dependencies, and invalid combinations.
  • Recipe Pattern — A culinary scaffold with functional ingredient or process slots that support valid substitutions.
  • Style Guide or Pattern Library — A curated collection of reusable patterns, allowed variants, and usage rules.

Stage-Gate Progression

Move work, people, decisions, or artifacts through stages only after explicit criteria are met, preventing premature progression and preserving quality, safety, readiness, or legitimacy.

6 mechanisms · View full solution archetype

  • Clinical Clearance Protocol — Implements guarded transition by requiring clinical criteria, review, or sign-off before a patient moves to discharge, transfer, surgery, or a new treatment state.
  • Compliance Signoff — Certifies on the record that legal, regulatory, safety, or policy criteria have been met — with a named signer and any deviations logged — before work is allowed to proceed.
  • Educational Mastery Assessment — Requires a learner to demonstrate prerequisite competence, not seat-time, before advancing — and routes those who fall short into targeted remediation rather than forward.
  • Go / No-Go Review — Convenes a single synchronized decision event where designated authorities poll launch criteria and render one committing verdict — go, hold, or no-go — before a high-exposure action.
  • Manufacturing Inspection Point — An inline checkpoint that measures a part against tolerance and routes it to proceed, rework, or scrap, so defects are caught before they are built into a larger assembly.
  • Release Readiness Review — Aggregates readiness evidence across tests, monitoring, rollback, security, and support before a release, permitting a staged or conditional rollout rather than an all-or-nothing ship.

Stratified Treatment

Apply different interventions to different strata when a uniform treatment would be ineffective, unfair, or unsafe.

8 mechanisms · View full solution archetype

  • Case Management Tiers — Assigns cases to light, standard, intensive, or specialist management tracks according to need, risk, or complexity.
  • Clinical Risk Banding — Uses clinical indicators to separate patients into bands that receive different screening, follow-up, treatment intensity, or safety precautions.
  • Fairness Audit by Stratum — Checks whether differential treatment is producing intended fit without unacceptable disparate harm, exclusion, or hidden under-service.
  • Risk Stratification Protocol — Implements the archetype by assigning cases to risk bands and linking each band to monitoring, protection, escalation, or support rules.
  • Segmented Customer Treatment Rules — Operationalizes different response scripts, service levels, retention offers, or escalation paths for different customer or case segments.
  • Stratum-Specific Threshold Schedule — Lists different eligibility, review, escalation, inspection, or intervention thresholds for each stratum.
  • Tiered Service Catalog — Documents the service levels, response times, supports, thresholds, and responsibilities associated with each stratum.
  • Vulnerability-Based Support Workflow — Directs additional protection, outreach, simplification, or case management toward strata with lower capacity or higher exposure to harm.

Tiered Escalation

Handle issues at the lowest competent level and escalate only when scope, authority, risk, complexity, or capacity requires higher-level intervention.

8 mechanisms · View full solution archetype

  • Appeal Process — Gives an affected party a defined route to move a contested decision up to a higher review tier empowered to affirm, reverse, or remand it.
  • Approval Matrix — Maps each class of decision to the authority tier that must approve it, so spending, risk, and exceptions route to the right approver.
  • Clinical Referral Pathway — Routes a patient from generalist to specialist to acute care on clinical need, then hands them back to primary care with responsibility for the patient never dropped.
  • Emergency Command Levels — Activates progressively larger tiers of command as an incident outgrows local response, expanding coordination span and resource authority at each level.
  • Incident Severity Matrix — Combines impact, urgency, scope, and reversibility to route an incident into a response regime.
  • Management Escalation Review — A recurring forum that pulls unresolved, cross-boundary, or authority-sensitive issues up to a management tier with the standing and decision rights to close them.
  • On-Call Runbook Escalation — Pre-writes the page, transfer, and notify steps an on-call responder follows so escalation stays fast and safe under time pressure.
  • Support Tier Model — Arranges support into competence tiers where a case starts at the lowest tier that can resolve it and rises only when that tier is genuinely out of depth.