Skip to content

Meeting Inflation

The organizational pathology in which coordination meetings multiply until they consume more capacity than the work they coordinate — driven by coordination cost scaling super-linearly with dependency density while each scheduler prices a meeting linearly.

Core Idea

Meeting inflation is the organizational pathology in which a coordination mechanism — recurring syncs, standups, status reviews, steering committees — multiplies until meetings collectively consume more productive capacity than the work they were introduced to coordinate, and additional coordination meetings are then added to manage the increasingly disjoint state of work that the original meeting load has produced, accelerating the inversion. Each individual meeting remains locally defensible: the participants are genuinely involved, the agenda addresses a real coordination need, the calendar entry was justified when created. The pathology is aggregate and recursive: the sum of individually-reasonable meeting commitments crowds out the deep work time the meetings presuppose, degrading the work's progress, which generates fresh coordination needs, which are addressed with more meetings.

The structural mechanism is a mismatch between how meeting load scales and how it is priced. Coordination requirements in a team grow with the square (or higher power) of dependency density — every new dependency between sub-teams adds pairwise and higher-order coordination needs — but individual schedulers price each meeting as a local addition to one calendar: n invitees × t hours of time, with no accounting for calendar fragmentation (the split of deep-work blocks into sub-threshold intervals between meetings), the multiplier across all invitees, or the downstream coordination the meeting's absence of decision-making creates. This mispricing enables runaway growth because the system-level cost is invisible to the individual who schedules the next meeting. The growth has three distinguishable components that require different interventions: genuine coordination-need growth with team size (addressed by async communication channels that decouple coordination from real-time attendance), defensive scheduling driven by information-exclusion anxiety (addressed by decision-rights frameworks that clarify who must be informed versus who must decide), and coordination-of-coordination proliferation in which meta-meetings arise to triage the object-meeting load (the recursive self-compounding phase, addressed only by a deliberate calendar audit that cuts from the root).

Structural Signature

Sig role-phrases:

  • the coordination mechanism — recurring syncs, standups, status reviews, and steering committees introduced to coordinate the work
  • the deep-work capacity it presupposes — the productive time the meetings exist to serve, fragmented into sub-threshold gaps as meetings multiply
  • the dependency density — the pairwise and higher-order links between sub-teams whose growth drives coordination need super-linearly
  • the scaling-versus-pricing mismatch — coordination cost growing with the square (or higher) of dependency density while each scheduler prices a meeting linearly (n invitees × t hours on one calendar), blind to the across-attendee multiplier and deep-work fragmentation
  • the local defensibility — each meeting individually justified (real attendees, real agenda), so per-meeting audits find nothing to cut
  • the three growth components — genuine coordination-need growth, defensive scheduling (insuring against exclusion from decisions), and coordination-of-coordination (meta-meetings triaging the object-meeting load)
  • the recursive inversion — meeting load crowding out deep work, degrading progress, generating fresh coordination needs met with still more meetings, the meta-meeting phase marking self-compounding runaway

What It Is Not

  • Not individual meetings being wasteful or badly run. Each meeting is locally defensible — real attendees, a real agenda, a justified calendar entry — so a per-meeting audit finds nothing to cut. The pathology is aggregate and recursive: the sum of individually-reasonable commitments crowds out the deep work the meetings presuppose. Improving any single meeting does not touch the inversion.
  • Not a calendar-management problem. The reflexive "schedule better, decline more" targets the individual when the fault is aggregate. Because every meeting survives one-at-a-time scrutiny, the failure lives in the sum and its feedback loop, not in lax personal scheduling; treating it as a discipline issue dead-ends in a calendar that is merely "full."
  • Not curable by deleting meetings. Deletion attacks only one of three growth dynamics and backfires on the others: defensive scheduling regenerates the meeting unless decision-rights are clarified, and the coordination-of-coordination recursion needs a root-cutting audit, not marginal trimming. The cure must match which dynamic put the meeting on the calendar.
  • Not Parkinson's law restated. Parkinson's "work expands to fill the time available" has the inverse character. Here the coordination mechanism expands to consume time the work actually needed — meetings crowding out execution — rather than a task lazily stretching to fill its slot. The direction of the encroachment is opposite.
  • Not priced by the meeting's own hours. The locally visible cost — n invitees times t hours on one calendar — is exactly the mispricing that drives the runaway. The true system-level cost is the multiplier across all attendees plus the fragmentation of deep-work blocks into sub-threshold gaps, neither of which the individual scheduler sees. Reading the cost as just "my hour" is what lets each next meeting be booked.

Scope of Application

Meeting inflation lives across the knowledge-work and management subfields where recurring coordination meetings compete with deep work; its reach is within that calendar-and-deep-work substrate, with a soft edge beyond it (construction a fair analogue, manufacturing weaker), since the substrate-neutral scaling story is carried by coordination + transaction_costs + diseconomies_of_scale, and the recursive scaffolding-becomes-the-load story by the separate coordination_overhead_inversion pattern.

  • Software delivery — standups, syncs, design reviews, and executive cadences multiplying across sub-teams until deep work fragments and output falls despite added headcount.
  • Consulting — engagement, internal, and practice-coordination meetings crowding out billable delivery time.
  • Research-program management — committee and review-board proliferation, with meta-committees arising to triage the object-committee load.
  • Policy implementation — interagency coordination-meeting overload as dependency density across agencies grows super-linearly.
  • Construction (toolbox-talk multiplication) — the fair analogue at the edge of the substrate, safety and coordination briefings multiplying past the work they coordinate.

Clarity

Naming meeting inflation sharpens the familiar lament — "I have no time to do my work" — into a specific structural inversion: the coordination mechanism has begun consuming more capacity than the work it was meant to coordinate. That reframe is what makes the problem tractable, because it relocates the fault from the individual to the aggregate. Each meeting is locally defensible — real attendees, a real agenda, a justified calendar entry — so any audit that interrogates meetings one at a time finds nothing to cut and concludes the schedule is merely full. The concept directs attention instead to the sum and its recursion: individually-reasonable commitments crowd out the deep-work time the meetings presuppose, degrade the work, generate fresh coordination needs, and draw in still more meetings. The question shifts from a calendar-management one ("schedule better," "decline more") to a design one ("which coordination needs are actually being met, and at what system-level cost?").

It also resolves the growth into three components that get blurred together and that demand different cures. Genuine coordination-need growth tracks team size and dependency density, and is met by async channels that decouple coordination from real-time attendance. Defensive scheduling — meetings booked to insure against being left out of decisions — is met not by deleting meetings but by decision-rights clarity that separates who must be informed from who must decide. Coordination-of-coordination, the meta-meetings that arise to triage the object-meeting load, is the self-compounding phase, curable only by a root-cutting calendar audit. The concept also names the mispricing that drives all three: coordination cost scales with the square of dependency density while each scheduler prices a meeting linearly, as n invitees times t hours on one calendar, blind to the multiplier across attendees and to the fragmentation of deep-work blocks into sub-threshold gaps. The sharper question becomes not "is this meeting worth my hour?" but "what is this meeting's true system-level cost, and which of the three growth dynamics is putting it on the calendar?"

Manages Complexity

A manager confronting a calendar that has swallowed the workweek faces a problem that resists the obvious audit, because every meeting on it is individually defensible — real attendees, a real agenda, a justified entry — so interrogating meetings one at a time finds nothing to cut and concludes only that the schedule is full. Meeting inflation compresses that dead-ended, case-by-case search into one structural diagnosis governed by a single mispricing: coordination requirements grow with the square (or higher power) of dependency density, while each scheduler prices a meeting linearly, as n invitees times t hours on one calendar, blind to the multiplier across attendees and to the fragmentation of deep-work blocks into sub-threshold gaps. That mismatch between how meeting load scales and how it is priced is the whole engine, and once it is named the runaway and its recursion (degraded work generating fresh coordination needs that draw in more meetings) follow as consequences rather than mysteries. The unanswerable "why do I have no time?" collapses to a quantity the analyst can actually reason about: the gap between quadratic coordination cost and linear local pricing.

What the manager then tracks reduces to sorting the meeting load into three growth components, each with a distinct cure, so the intervention reads off the diagnosis instead of requiring a meeting-by-meeting verdict. Genuine coordination-need growth scales with team size and dependency density and is met by async channels that decouple coordination from real-time attendance. Defensive scheduling — meetings booked to insure against being left out of decisions — is met not by deleting meetings but by decision-rights clarity separating who must be informed from who must decide. Coordination-of-coordination — the meta-meetings that arise to triage the object-meeting load — is the self-compounding phase, curable only by a root-cutting calendar audit. The branch structure is clean: classify a meeting by which of the three dynamics put it on the calendar, and the remedy is determined — async tooling, decision framework, or audit-from-the-root — rather than left to taste. And the cost question is reframed from the locally unanswerable "is this meeting worth my hour?" to the system-level "what is its true cost (the across-attendee multiplier plus the deep-work fragmentation it imposes), and which growth dynamic is generating it?" A bewildering full calendar that defeats one-at-a-time pruning becomes a single scaling-versus-pricing mismatch feeding a three-way classification with matched cures, letting the practitioner locate the runaway's source and apply the one intervention that cuts it rather than rescheduling at the margin.

Abstract Reasoning

Meeting inflation licenses reasoning moves built on its core mechanism — coordination cost scaling super-linearly with dependency density while each scheduler prices a meeting linearly — and on the three-way classification of what is generating the load.

Diagnostic (infer the aggregate pathology from a signature that the per-meeting audit misses): the defining move is to refuse the one-at-a-time interrogation and reason at the aggregate. When a calendar has swallowed the workweek yet every meeting is individually defensible — real attendees, real agenda, justified entry — the analyst infers from that very local defensibility to an aggregate, recursive inversion: the failure cannot be any single meeting because each survives scrutiny, so it must live in the sum and its feedback. The signature is a coordination mechanism consuming more capacity than the work it coordinates, with output declining despite increased headcount — a pattern that points at the scaling-versus-pricing mismatch rather than at lazy scheduling. A second diagnostic classifies each meeting by which of three dynamics put it on the calendar: coordination-need growth (tracks team size and dependency density), defensive scheduling (booked to insure against exclusion from decisions), or coordination-of-coordination (meta-meetings triaging the object-meeting load). Reasoning from the meeting's function to its type tells the analyst which engine is running — and the presence of meta-meetings specifically is the diagnostic that the self-compounding recursive phase has begun.

Interventionist (name the cure, predicted to differ by type): the classification is prescriptive because the three dynamics have non-overlapping cures, and applying the wrong one is predicted to fail. Genuine coordination-need growth is met by async channels that decouple coordination from real-time attendance — predicted to absorb the load without consuming synchronous deep-work time. Defensive scheduling is met not by deleting meetings but by decision-rights frameworks (who must be informed versus who must decide) — predicted to dissolve the exclusion anxiety that books the meeting, where deletion alone would just regenerate it. Coordination-of-coordination is curable only by a root-cutting calendar audit — predicted to require cutting from the source because trimming at the margin leaves the recursion intact. The deeper interventionist claim is about pricing: because the runaway is driven by system-level cost being invisible to the individual scheduler, the predicted-effective structural fix is to cost each meeting at the system level (across-attendee multiplier plus deep-work fragmentation), making the next scheduler confront the true cost before booking — the move that attacks the mispricing engine rather than its symptoms.

Boundary-drawing (when the diagnosis applies, what is and is not the pathology): the concept draws a sharp line against the reflexive calendar-management framing — "schedule better," "decline more" — which targets the individual when the fault is aggregate, and it bounds the problem to regimes where coordination cost genuinely scales super-linearly (high dependency density between sub-teams) so that linear local pricing diverges from real cost. It also distinguishes the three growth components so that effort is not wasted: deleting meetings attacks only one of the three and is predicted to backfire on defensive scheduling, while async tooling does nothing for the meta-meeting recursion. The regime in which the full diagnosis bites is a team whose dependency density has grown enough that quadratic coordination cost has outrun the linear pricing each scheduler applies.

Predictive / order-of-events: the framing predicts a characteristic escalation sequence — object meetings multiply with dependency density, the resulting calendar fragmentation degrades deep work, degraded work generates fresh coordination needs, those needs are met with still more meetings, and eventually meta-meetings appear to triage the object-meeting load, marking the self-compounding phase. Reasoning along that loop, the analyst predicts that without a structural pricing or decision-rights change the load will not self-limit, that the inversion accelerates rather than plateaus, and that the appearance of coordination-of-coordination is the late-stage marker indicating a root-cutting audit is now required rather than marginal pruning.

Knowledge Transfer

Within knowledge work the meeting-inflation frame transfers as mechanism, because its engine (super-linear coordination cost against linear local pricing), its three-way classification (coordination-need growth, defensive scheduling, coordination-of-coordination), and its matched cures are stated in terms any meeting-heavy organization exposes. They carry intact across software delivery, consulting, research-program management (committee proliferation), and policy implementation (interagency coordination-meeting overload), and the practical triad — async update channels, decision-rights frameworks (RACI / DACI / RAPID), and meeting-free focus blocks — transfers across all of them, as does the diagnostic that the appearance of meta-meetings marks the self-compounding phase. The reach has a soft edge the seed flags honestly: construction (toolbox-talk multiplication) is a fair analogue, but manufacturing and engineering extensions are weaker, because those domains have their own coordination-overhead patterns (changeover time, batch handoff) better captured by other concepts — so the meeting-inflation frame ports cleanly across knowledge-work substrates and only loosely beyond them. These are instances of one coordination pathology on the knowledge-work substrate, with the calendar-and-deep-work structure shared throughout.

Beyond knowledge work the honest reading is shared abstract mechanism, at two levels (case B). At the shallower level, the substrate-neutral content — coordination overhead that scales non-linearly until it dominates the activity it was meant to coordinate — is already carried jointly by parent primes: coordination, transaction_costs, diseconomies_of_scale, and coordination_problem_and_equilibrium_selection. Stripped of meeting vocabulary, that is what remains, and it is those primes that should carry any cross-domain lesson about coordination cost outrunning its activity. At the deeper level there is a sharper, genuinely recurring pattern that meeting inflation is one instance of — a mechanism introduced to support an activity grows until it consumes more capacity than the activity itself, whereupon meta-mechanisms are added to manage the proliferation (the scaffolding-becomes-the-load recursion). That pattern reappears as real co-instances across distinct substrates: bureaucratic overhead, audit-of-audit regimes, governance-of-governance committees, and documentation-of-documentation. It is being tracked as a separate emergent candidate (coordination_overhead_inversion) precisely because it travels in its own right, more abstractly than meetings. So the cross-domain lesson should carry one of those parents — the coordination-cost primes for the scaling story, or the overhead-inversion pattern for the recursive self-compounding story — not "meeting inflation," whose home-bound cargo (calendars and deep-work fragmentation, meeting culture, async-versus-sync tooling, decision-rights frameworks, the calendar audit) stays in knowledge-work management. The cleanest disposition is the seed's: keep meeting inflation as the organizational-management instance that points up to those substrate-independent parents. (Note also that meeting inflation is not Parkinson's law restated: Parkinson's "work expands to fill the time available" is the inverse character — here the coordination mechanism expands to consume time the work needed.)

Examples

Canonical

The defining instance is the scaling software organization. A ten-person startup coordinates in the hallway; grown to a hundred people across a dozen sub-teams, it acquires a daily standup per team, a weekly cross-team sync, sprint planning and retro, design reviews, a program-status meeting, and an all-hands. Every one of these is defensible in isolation — the attendees are genuinely involved and each agenda names a real dependency — yet an engineer can find their week reduced to hour-long gaps between calendar entries, too short for deep work. As shipping slows, the response is to add a coordination meeting to unblock the slippage, and eventually a weekly "meeting to triage our meetings." Output falls even as headcount rises.

Mapped back: The proliferating standups and syncs are the coordination mechanism; the fragmented engineer's week is the deep-work capacity it presupposes being consumed. Growth from ten to a hundred across sub-teams is rising dependency density driving need super-linearly, while each organizer books "just an hour" — the scaling-versus-pricing mismatch. Every meeting's local defensibility is why per-meeting pruning fails, and the triage-our-meetings meeting is the coordination-of-coordination marker of the recursive inversion.

Applied / In Practice

Shopify's 2023 "meeting purge" is a documented corporate intervention against exactly this pathology. The company cancelled all recurring meetings with three or more people (thousands of events), reinstating them only if they proved necessary, and declared meeting-free periods to protect focus time. Notably, it also built a meeting "cost calculator" into its systems that estimated the dollar cost of a proposed meeting from the number and seniority of attendees, surfacing that figure to whoever tried to schedule it.

Mapped back: The blanket cancellation of recurring 3+-person meetings is the root-cutting calendar audit the concept prescribes for the coordination-of-coordination phase — cutting from the source rather than trimming at the margin. Most pointedly, the cost calculator attacks the scaling-versus-pricing mismatch directly: by pricing each meeting at the across-attendee, system level and showing it to the scheduler before booking, it makes the individual confront the true cost the linear "n invitees × t hours" framing hides — the concept's central interventionist move made operational.

Structural Tensions

T1: Aggregate diagnosis versus an ownerless fix (no meeting is at fault, so no one cuts). Relocating the fault from the individual meeting to the aggregate is the concept's central insight — it correctly explains why a per-meeting audit finds nothing to cut, since each entry is locally defensible. But that same move leaves the correction without an owner. If no single meeting is the problem and the pathology lives in the sum, then no individual scheduler has both the standing and the incentive to cut: each rationally books their own defensible meeting, and only a top-down structural act — a blanket purge like Shopify's — can override every local defense at once. The diagnosis that exonerates each scheduler also removes the leverage any of them has to fix it, so the concept demands an authority willing to act against the aggregate that its own analysis says no participant caused. Diagnostic: Is there an actor with the authority and incentive to cut against the aggregate here, or does "no single meeting is at fault" leave the inversion with a correct diagnosis and no one able to act on it?

T2: System-level pricing versus the unpriceable half of the cost. The concept's deepest interventionist claim is to make the scheduler confront a meeting's true system-level cost — the across-attendee multiplier plus deep-work fragmentation — and Shopify's calculator operationalizes it. But it prices only the tractable half: salary × attendees × hours. The fragmentation cost — the splitting of each attendee's day into sub-threshold gaps too short for deep work — is the half the concept identifies as the real engine, and it is nearly impossible to price, depending on every attendee's other commitments, task type, and switching cost, none visible to the scheduler. A dollar figure that captures only the salary-hours can manufacture false precision, legitimizing any meeting whose "cost" is affordable while ignoring the fragmentation harm that actually drives the inversion. The pricing cure risks mispricing by measuring what is easy and omitting what matters. Diagnostic: Does the meeting's priced cost include the fragmentation it imposes on each attendee's deep-work blocks, or only the salary-hours — and is the affordable-looking number hiding the harm that matters?

T3: A clean three-way classification versus meetings that are blends. The three growth components — coordination-need growth, defensive scheduling, coordination-of-coordination — are prescriptive because each has a non-overlapping cure and applying the wrong one is predicted to backfire (deleting a defensively-booked meeting just regenerates it). But that logic presupposes meetings come in pure types, and real ones are usually blends: a recurring status sync is partly genuine coordination, partly defensive attendance by people insuring against exclusion, partly a meta-meeting triaging other work. Classifying by "which dynamic put it on the calendar" requires reading intents the attendees themselves may not know, and a misclassification triggers exactly the cure the concept says will fail. The matched-cure precision is only as good as a type-assignment that the mixed reality of a single meeting resists. Diagnostic: Is this meeting cleanly one of the three types, or a blend whose dominant dynamic is contested — so the "matched cure" may be aimed at the wrong component?

T4: The cures versus their own inflation (the scaffolding recursion applies to the fixes too). Async channels, decision-rights frameworks, and meeting-free blocks are prescribed as clean absorbers of the load — but each is itself a coordination mechanism subject to the same pathology. Async channels proliferate into notification overload and endless threads, message inflation replacing meeting inflation in a different medium; RACI/DACI matrices become governance artifacts that require their own upkeep and, eventually, meetings to maintain; focus-time policies spawn the meta-work of scheduling and defending them. The very recursion the concept names — a mechanism introduced to support work growing until it consumes the work, whereupon meta-mechanisms manage the proliferation — applies to the remedies, so the cure can relocate the overhead rather than dissolve it. Fixing meeting inflation by adding coordination infrastructure can seed the next inversion. Diagnostic: Does the proposed cure actually reduce total coordination overhead, or relocate it into channels, frameworks, and policies that will inflate in turn?

T5: Autonomy versus reduction (an organizational pathology or the coordination-cost and overhead-inversion parents). Meeting inflation is a specific, well-drawn management concept — calendars and deep-work fragmentation, meeting culture, async-versus-sync tooling, decision-rights frameworks, the root-cutting audit — and within knowledge work it transfers as mechanism across software, consulting, research, and policy. But the entry is explicit that it reduces at two levels: the substrate-neutral scaling story (coordination overhead growing non-linearly until it dominates the activity) is carried by coordination, transaction_costs, and diseconomies_of_scale, and the recursive scaffolding-becomes-the-load story by the separate coordination_overhead_inversion pattern that also covers bureaucracy, audit-of-audit, and governance-of-governance. It is pointedly not Parkinson's law (that has the inverse character). Diagnostic: Resolve toward the coordination-cost primes for the scaling lesson, and toward coordination_overhead_inversion for the recursive self-compounding lesson, when leaving knowledge work; toward the named pathology only where calendars, meetings, and deep-work fragmentation are literally in play.

Structural–Framed Character

Meeting inflation sits at the framed-leaning end of the spectrum. It does not convict a person the way a fallacy does, but it lands on the framed side because it is a normatively-charged organizational pathology constituted by a specific human work practice. Its evaluative_weight is real: "inflation" and "pathology" name a dysfunction — a runaway to be diagnosed and cured — so the term marks its object as undesirable in a way a neutral mechanism-word does not; naming meeting inflation is already half a call to intervene. It is thoroughly human_practice_bound: the substrate is calendars, meetings, and deep work in a knowledge-work organization, and the concept dissolves without that practice — there is no "meeting," no "deep-work block fragmented into sub-threshold gaps," and no "defensive scheduling" except relative to human coordinators and their calendars. Its institutional_origin is pronounced: it is a management/work-design construct, its cures (async channels, RACI/DACI/RAPID decision-rights frameworks, meeting-free focus blocks, the root-cutting calendar audit) and its three-way growth taxonomy all drawn inside the organizational-management tradition rather than read off nature. On vocab_travels it scores low — standup, steering committee, deep-work capacity, coordination-of-coordination, meeting-free block are pinned to the calendar-and-knowledge-work substrate — and on import_vs_recognize it patterns as import-by-analogy for the named concept: it ports cleanly only across knowledge-work substrates, weakens already at construction and manufacturing, and the genuine cross-domain lesson rides the coordination-cost primes (or the separate overhead-inversion pattern), not "meeting inflation" recognized as itself.

The portable structure here is genuinely two skeletons, because the entry is explicit that the concept reduces at two levels. The first is non-linearly-scaling coordination overhead that comes to dominate the activity it serves — coordination cost growing super-linearly with dependency density while each local decision prices it linearly, so overhead outruns the work — carried by coordination, transaction_costs, and diseconomies_of_scale. The second is the recursive scaffolding-becomes-the-load pattern — a mechanism introduced to support an activity grows until it consumes more capacity than the activity, whereupon meta-mechanisms are added to manage the proliferation — carried by the separate coordination_overhead_inversion pattern (which also covers bureaucracy, audit-of-audit, and governance-of-governance). Naming both is warranted, not padding, because the entry assigns the scaling story and the self-compounding recursion to different parents. And that is the point: both skeletons are what meeting inflation instantiates from those umbrella primes, not what makes "meeting inflation" itself travel — the cross-domain reach belongs to the coordination-cost primes and the overhead-inversion pattern, while the domain-accented specifics (calendars, meeting culture, async-versus-sync tooling, decision-rights frameworks, the mispricing of "n invitees × t hours") stay home. Its character: a practice-constituted, normatively-charged organizational pathology — structural only in the non-linear-coordination-overhead and scaffolding-inversion skeletons it borrows from its umbrella primes and dresses in the irreducibly knowledge-work vocabulary of meetings and fragmented calendars.

Structural Core vs. Domain Accent

This section decides why meeting inflation is a domain-specific abstraction and not a prime, and it carries the case for its domain-specificity — there is no separate section for that.

What is skeletal (could lift toward a cross-domain prime) — and here the skeleton is genuinely doubled, because the concept reduces at two levels. Strip the calendars and a first thin structure survives: coordination overhead scales super-linearly with dependency density while each local decision prices it linearly, so the overhead comes to dominate the very activity it was introduced to serve. Its portable pieces are abstract — a set of interdependent units whose pairwise (and higher-order) links grow the coordination requirement faster than linearly, a local pricing blind to the aggregate, and a divergence between them. That skeleton is carried by coordination, transaction_costs, diseconomies_of_scale, and coordination_problem_and_equilibrium_selection. A second, sharper structure also survives: a mechanism introduced to support an activity grows until it consumes more capacity than the activity itself, whereupon meta-mechanisms are added to manage the proliferation — the scaffolding-becomes-the-load recursion, carried by the separate coordination_overhead_inversion pattern (which also covers bureaucracy, audit-of-audit, and governance-of-governance). Naming both is warranted, not padding, because the entry assigns the scaling story and the self-compounding recursion to different parents. Both are genuinely substrate-portable — but both are the core meeting inflation shares with those parents, not what makes it distinctive.

What is domain-bound. Almost all of the content is organizational-management furniture, and none of it survives extraction intact: the coordination mechanism as recurring syncs, standups, status reviews, and steering committees; the deep-work capacity fragmented into sub-threshold calendar gaps; the three growth components (coordination-need growth, defensive scheduling, coordination-of-coordination) and their matched cures (async channels, RACI/DACI/RAPID decision-rights frameworks, the root-cutting calendar audit); and the concrete mispricing of "n invitees × t hours on one calendar." These are the worked vocabulary, the diagnostic instruments, and the empirical cases (the scaling software org, Shopify's meeting purge and cost calculator). There is also a domain accent in the term's normative charge: "inflation" and "pathology" mark the object as a dysfunction to be cured, texture a neutral word like "coordination" does not carry. The decisive test: remove the human calendars, meetings, and deep-work practice and there is no "meeting," no "fragmented block," and no "defensive scheduling" — only the bare non-linear-overhead and scaffolding-inversion structures, at which point one is using coordination/transaction_costs/coordination_overhead_inversion, not meeting inflation.

Why this does not clear the prime bar. A prime is a relational structure whose vocabulary travels and whose cross-domain transfer is recognition of the same mechanism, not analogy. Meeting inflation's transfer is bimodal with a soft edge. Within knowledge work the mechanism travels intact — the scaling-versus-pricing engine, the three-way classification with matched cures, and the meta-meeting late-stage marker carry without translation across software delivery, consulting, research-program management, and policy implementation, all one calendar-and-deep-work substrate (with construction a fair analogue at the edge, manufacturing already weaker). Beyond knowledge work it travels only by analogy: the calendar-and-meeting vocabulary loses its referents, and manufacturing or engineering coordination overhead is better captured by those fields' own patterns (changeover time, batch handoff), not by importing "meeting inflation." And when the bare structural lesson is needed cross-domain, it is already supplied in more general form by the primes meeting inflation instantiates: the scaling story rides coordination, transaction_costs, and diseconomies_of_scale; the recursive self-compounding story rides coordination_overhead_inversion (which independently covers bureaucracy, audit-of-audit, and governance-of-governance as co-instances). The cross-domain reach belongs to those parents; "meeting inflation," as named, is the knowledge-work management instance — its calendars, meeting culture, async-versus-sync tooling, and decision-rights frameworks stay home and should not travel.

Relationships to Other Abstractions

Local relationship map for Meeting InflationParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Meeting InflationDOMAINPrime abstraction: Coordination-Overhead Inversion — is a kind ofCoordination-Ov…PRIME

Current abstraction Meeting Inflation Domain-specific

Parents (1) — more general patterns this builds on

  • Meeting Inflation is a kind of Coordination-Overhead Inversion Prime

    Meeting Inflation is coordination-overhead inversion specialized to recurring knowledge-work meetings whose aggregate calendar load crowds out the work they coordinate.

Hierarchy paths (3) — routes to 3 parentless roots

Not to Be Confused With

  • Parkinson's law. The adage that "work expands to fill the time available." Meeting inflation has the inverse character: the coordination mechanism expands to consume time the work actually needed, meetings crowding out execution rather than a task lazily stretching to fill its slot. Tell: is a task stretching to fill its allotted time (Parkinson), or is a coordination overhead multiplying until it eats the capacity for real work (meeting inflation)?

  • Individually wasteful or badly-run meetings. The complaint that particular meetings have no agenda, run long, or invite the wrong people. Meeting inflation is aggregate and recursive: each meeting is locally defensible, so per-meeting audits find nothing to cut; the pathology lives in the sum and its feedback loop. Tell: would fixing or deleting this one meeting solve it (a bad-meeting problem), or does every meeting survive one-at-a-time scrutiny while the total has inverted (meeting inflation)?

  • A calendar-management / personal-discipline problem. The reflexive "schedule better, decline more" framing that targets the individual. Because every meeting passes individual scrutiny, the fault is in the aggregate and its scaling-versus-pricing mismatch, not in lax personal scheduling. Tell: is the remedy better individual calendar hygiene (a discipline framing), or a structural change to pricing and decision-rights that no single scheduler can enact (meeting inflation)?

  • Bureaucratic bloat / red tape. The proliferation of rules, forms, and approval layers that outgrow the work they govern. This is a co-instance of the same scaffolding-becomes-the-load recursion in a different substrate (procedures rather than calendars), not meeting inflation itself. Tell: is the overhead made of rules and approval steps (bureaucratic bloat), or of recurring meetings fragmenting deep-work time (meeting inflation) — both instances of coordination_overhead_inversion?

  • coordination_overhead_inversion (the recursive parent pattern). The substrate-neutral pattern — a support mechanism grows until it consumes more than the activity it serves, whereupon meta-mechanisms manage the proliferation — that also covers audit-of-audit and governance-of-governance. Meeting inflation is its knowledge-work instance; the self-compounding lesson travels via this pattern, not the meeting label. Tell: is the point the general scaffolding-becomes-load recursion across substrates (the pattern), or specifically meetings and fragmented calendars (meeting inflation)? (Treated more fully in an earlier section.)

  • coordination / transaction_costs / diseconomies_of_scale (the scaling parents). The substrate-neutral primes carrying the scaling story — coordination overhead growing non-linearly until it dominates the activity. Meeting inflation instantiates these with a super-linear-cost/linear-pricing mismatch; the scaling lesson rides these parents. Tell: is the claim the general non-linear coordination-cost growth (the parents), or specifically the meeting-load-versus-deep-work inversion (meeting inflation)? (Treated more fully in an earlier section.)

Neighborhood in Abstraction Space

Meeting Inflation sits in a sparse region of the domain-specific corpus (64th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Organizational Power & Coordination Drift (9 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12