Hierarchy & Org Charts

Hierarchy as structurally inevitable in groups — flat-structure ideology merely hides the operating hierarchy — and the political gap between aspirational org charts and how work actually flows.

Also known as: hierarki, hierarchy, org chart, flat struktur, flat structure, selvbedrag (flat struktur som), kunnskapshierarki, wide span of control, Undiscussables, undiscussable, organized hypocrisy, frames, frame, museum of boxes, Empire of headcount

How authors use it

Oldest first (extraction date when no publication date is known).

Documents (27)

• Dare to Be Bad at Something (From Fixable) Fixable (TED Audio Collective / Pushkin Industries), hosts Anne Morriss and Frances Frei; syndicated via the HBR Podcast Network / Cold Call feed · 2026-09-23 Reader 🖥️
  To excel where it matters most, individuals and organizations must deliberately choose — guided by a strict, customer-derived ranking of what matters — not only what to stop doing, but what to keep doing while doing it badly, and leaders must have (and visibly model) the emotional courage to sustain that choice under pressure.
• TBM 440: The Problem With Putting People in Boxes John Cutler · 2026-09-19 Reader 🖥️
  Putting people in boxes — typing them by personality, strengths, or 'culture fit' — is a category error at work because behavior is not a stable, context-free trait but a function of the person interacting with situational incentives, norms, power dynamics, and constraints, so the operative question should be 'under what conditions do you/they behave differently' rather than 'what type are you.'
• Pim de Morree's Post Pim de Morree · 2026-09-12 Reader 🖥️
  Bayer shows that when an organization is already mid-transformation, the better path is to fold AI into that existing change effort rather than launch AI as its own parallel initiative with separate leadership, budget, and governance.
• TBM 438: Am I the Only Weirdo in This Company? John Cutler from The Beautiful Mess · 2026-09-05 Reader 🖥️
  Organizations look far more uniform in belief than they actually are because what you observe is a compound of three layered things — power-weighted norms, individual adaptation to those norms, and the actual diverse beliefs of the people underneath — and we systematically mistake the middle layer (visible adaptation) for the bottom layer (real belief) while underweighting the top layer (power) that is actually driving what gets displayed.
• TBM 433: The Border Collie Faustian Bargain John Cutler · 2026-07-29 Reader 🖥️
  In an organization performing a strategy that its experienced members already know isn't one, people sort by whether they can see the incoherence and whether they can tolerate it -- and the people who can see it but can't fully stomach it (the 'Border Collies') face a Faustian bargain: trade the right to challenge the fiction for more influence over it, a trade that starts as reasonable-sounding local accommodations and ends with the Border Collie having become responsible for producing and defending the very ambiguity it once found intolerable.
• Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework Daniel Curtis · 2026-07-28 source ↗ Reader 🖥️
  Remix 3's beta preview is a ground-up architectural break from Remix 2 — dropping the React runtime for a forked, imperative Preact, rebuilding routing on raw Fetch/Response objects, and introducing server-driven 'frames' and a bundler-less 'unbundling' model — a deliberate bet that web-standards conformance beats framework abstraction, one so disruptive that it forces every existing Remix app into a full rewrite and has split developer commentary between praise for its explicit simplicity and skepticism toward a team already known for reinventing itself.
• Managers Are Not Overhead: They Are Infrastructure David Michelson · 2026-07-22 source ↗ Reader 🖥️
  Organizations flattening management layers on the assumption that AI has absorbed most of what managers used to do are making an unsupported productivity bet, because converging survey evidence shows managers have become the critical infrastructure layer that translates AI investment into realized team-level value, not a layer of overhead AI is now positioned to eliminate.
• What 60 Years of Data Reveals About How Men and Women Experience Leadership Harvard Business Review · 2026-07-10 source ↗ Reader 🖥️
  Over 60 years overt bias against women leaders has receded but reorganized into harder-to-see structural forms (informal sponsorship, subjectively interpreted merit, unequal access to P&L roles), and men and women now sharply diverge on whether the system is fair — progress on the surface, deterioration underneath.
• When Nothing Happens Fish Food for Thought · 2026-07-08 source ↗ Reader 🖥️
  Whether a leader's harsh behavior is judged as abuse or as excellence turns almost entirely on whether the numbers are good rather than on the behavior itself, so tolerating a high performer's bad conduct is not a moral judgment about their character but an unadmitted bet on their continued performance — a bet that reverses the moment results fade, not when the behavior escalates — and leaders should name and confront that bet today instead of letting it become the scandal they must later explain.
• Every Organization Has Two Realities Harvard Business Review (Gretchen Gavett, The Insider newsletter) · 2026-07-06 source ↗ Reader 🖥️
  Organizations run on a gap between the version leaders formally present, govern, and are accountable for (board decks, compliance categories, regulatory structure) and the version that is actually lived, worked, and enforced day to day (employee experience, well-intentioned deviation, political reality) — and leaders who fail to actively surface and reconcile that gap accumulate risk (talent loss, misjudged misconduct, blindsided strategy) that a more legible, presented reality obscures.
• TBM 426: The Trouble With Mirrors John Cutler from The Beautiful Mess · 2026-06-16 source ↗ Reader 🖥️
  Visualizing how an organization works and 'embracing transparency' cannot by themselves improve it, because organizational truth is never a single neutral reflection but is positional, framed, and continuously negotiated among parties who each have something at stake in what gets seen — so the real need is not to be shown the mirror but to be mirrored: to have one's perspective recognized and held with care.
• What is the harder human-capital problem beneath token capital? Turing Post · 2026-06-15 Reader 🖥️
  Beneath Nadella's visible 'token capital vs. human capital' story lies a harder problem — the human capital big firms manufacture best (senior, politically-fluent ladder-climbers) is exactly the kind that wastes token capital, while the frontier-moving talent that would use it well is what corporate structure selects against — so the scarcest capital in the AI age is neither human nor machine but an organizational structure porous enough to hold uncorporate talent and corporate-scale compute together without flattening either.
• The engineering manager role is splitting in two Stephane Moreau · 2026-06-09 source ↗ Reader 🖥️
  The engineering-manager role is fracturing into two divergent futures — the code-adjacent tech lead manager and the non-technical multi-team EM — and because AI-shrunk teams are driving the split as an unplanned byproduct of flattening, engineers on the management path must diagnose which future their company is building and prepare accordingly rather than aiming at a single 'EM' destination.
• Your AI strategy has a trust problem, not a tooling problem Elena Verna (cross-posted by Lenny Rachitsky) · 2026-06-05 Reader 🖥️
  AI tooling produces no velocity unless companies first dismantle the title-gated access, decision-bottlenecking, and middle-management telephone-game that signal distrust of employees — the real unlock is employee agency, not AI agents.
• 4) Morten Eikeland: Det finnes alltid et hierarki Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-06-01 source ↗ Reader 🖥️
  Hierarchy is not optional in any group of more than a few people — it arises structurally from division-of-labour pressure plus external groups' need for a single point of contact — and the agile/teknologi/flat-struktur ideology that pretends otherwise does not eliminate hierarchy, it only makes the actual operating hierarchy invisible, unspoken, and harder to challenge; therefore the work of leading well is not to flatten but to operate at the correct abstraction level for the role one is in, to recognise the role-vs-person distinction, and (for a developer becoming a leader) to walk a real sorgprosess of identity loss before gaining a different kind of relevance.
• AI Won't Save the Kingdoms We Built John Cutler · 2026-05-25 source ↗ Reader 🖥️
  AI will only dissolve the organizational fiefdoms of the ZIRP era if leaders are honest that those fiefdoms were structural responses to coordination, autonomy, and accountability problems — otherwise AI will simply reproduce the same coordination burden in a new, async, agent-mediated shape.
• TBM 423: Why Defining Teams Is So Hard John Cutler · 2026-05-21 source ↗ Reader 🖥️
  Defining teams in product/tech orgs is hard not because the analytic skill is rare, but because honestly naming the gap between the aspirational org chart and how work actually flows threatens existing power, incentives, and narratives — so the work is political and emotional, not technical, and the goal should be to hold both views at once and act on the gap rather than collapse it.
• TBM 423: Why Defining Teams Is So Hard John Cutler from The Beautiful Mess · 2026-05-21 Reader 🖥️
  Honestly describing how teams actually work in product-and-technology organizations is cognitively easy but politically expensive, because the gap between the legible aspirational org chart and the lived collaboration reality is sustained by asymmetric incentives (cheap for product to redefine, costly for engineering to absorb, invisible to design) rather than by any lack of skill or insight — so the real organizational competence is the willingness to hold both views at once and work with the gap.
• Your Work Team Is Now a 'Pod' and Your Co-Workers Are AI Agents Isabelle Bousquette · 2026-05-18 source ↗ Reader 🖥️
  AI agents now do enough of the actual software-development work (coding, testing) that engineering organizations are restructuring around much smaller, cross-functional 'pods' of one to eight humans plus agents, carrying the decades-long trend toward smaller teams further than headcount-only shrinkage ever could.
• The Agentic P&L: Beyond the Empire of Headcount Shreshta Shyamsundar and Anmol Jain · 2026-05 source ↗ Reader 🖥️
  Headcount is obsolete as the unit of corporate value; in an agentic enterprise, leverage must be measured and rewarded along three new axes — contextual density (potential energy of knowledge enclaves), agentic throughput at a managed cost per cognitive outcome (kinetic energy), and revenue productivity per person — organized in '3+N' squads governed by decision-provenance 'mirrors'.
• Introduction johnpcutler.github.io · 2026-04-10 source ↗ Reader 🖥️
  Organizations suffer because the words, categories, and representations they use to describe product development work systematically flatten, filter, and distort reality as information moves across levels -- and the solution requires treating operational language as information architecture and ontology design rather than simple labeling.
• The founder of Postman says you have to kill your existing org chart Ivan Burazin · 2026-04-10 Reader 🖥️
  Traditional organizational hierarchies must be dismantled in favor of flat, builder-centric structures where everyone — including PMs and designers — ships directly, and management exists to cultivate judgment rather than coordinate through layers.
• TBM 414: Legibility and Legitimacy John Cutler from The Beautiful Mess · 2026-04-04 source ↗ Reader 🖥️
  AI-powered organizational 'legibility' is being sold as efficiency and liberation, but without the harder question of legitimacy — whether the resulting control is accepted as justified by those subjected to it — it amounts to a power grab concealed by technology's rhetorical authority.
• Optimizing teams: A dual perspective on Team Topologies Elias Lieberich · 2024-09-26 source ↗ Reader 🖥️
  Team Topologies' four-type model is a useful starting vocabulary, but both authors argue that applying it well requires practical, product-aware judgment calls it doesn't itself supply — Lieberich's engineering-facing checklist (well-defined scope, disambiguated boundaries, minimal dependencies) and Wille's product-facing one (small teams, end-to-end ownership of a user journey, splitting by product/user-group/value-moment/funnel-stage rather than by technology) — because the book's own categories never fully resonated with a product-management, rather than engineering, view of where team boundaries should fall.
• Thriving with complexity using open sociotechnical systems design Trond Hjorteland · 2022-01-05 source ↗ Reader 🖥️
  Software organizations should undergo a radical, participatively-designed structural transition from DP1 (bureaucratic, redundancy-of-parts, externally-coordinated) to DP2 (self-managing, redundancy-of-functions, internally-coordinated) sociotechnical design — the empirically-grounded Open Systems Theory tradition that agile, product, and 'team-first' movements have been independently and incompletely rediscovering — because only DP2 generates the variety needed to thrive in today's turbulent technical and social environment, and because that change must be structural and self-designed, not a culture or values campaign layered on top of unchanged structure.
• Scaling the Practice of Architecture, Conversationally Andrew Harmel-Law · 2021-11-30 source ↗ Reader 🖥️
  Architecture should be practiced as a decentralized, conversational discipline — anyone can make an architectural decision as long as they first seek out and record advice from those meaningfully affected and those with relevant expertise (the 'Advice Process') — supported by four lightweight tools (Architecture Decision Records, a recurring Architecture Advisory Forum, team-sourced architectural principles, and a technology radar) that let architecture scale with team autonomy instead of being bottlenecked on a small group of designated architects.
• Software Engineering at Google Fergus Henderson · 2019-02-19 source ↗ Reader 🖥️
  Google sustains software velocity and quality at extreme scale (2+ billion lines, one repository, thousands of engineers) not through any single tool or policy but through a mutually reinforcing system of technical infrastructure (a single trunk-based monorepo, hermetic reproducible builds, and mandatory same-day code review) and organizational design (separated engineer/manager career tracks, OKRs deliberately decoupled from pay, 20% time, and periodic full rewrites) that together manufacture trust, ownership, and continuous renewal.

Propositions touching this concept (49)

By publication month, oldest first (extraction month when no publication date is known).

2019-02

• explicitSomewhat frequent corporate reorganization is a necessary cost of a large technology-driven organization, used (among other things) to counteract the 'shipping the org chart' failure mode where software architecture passively mirrors reporting structure rather than being designed.
  Software Engineering at Google · p15

2024-04

• explicitOrganizations that explicitly and intentionally fix how they learn and work together (values, ways of working) as the one deliberately stable structure gain the ability to treat almost everything else -- org chart, software architecture -- as fluid and re-imaginable; organizations that instead fix their org chart in stone are left with reinventing or rebuilding the architecture as their only real lever for change.
  Software Development As Collective Learning With Hazel Weakly · p9

2024-09

• explicitDesigning product teams to mirror the existing organizational reporting structure ('shipping your org chart') leads to inefficiency and silos.
  Optimizing teams: A dual perspective on Team Topologies · p10

2025-10

• explicitThe Weberian / military-derived functionally specialised hierarchy is well-suited to sikker og stabil drift in stable environments but unfit for dynamic and unpredictable conditions; the choice between machine and organism organisation is forced by environment, not preference.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p10

2025-11

• implicitFlat structure is impossible above ~5 people; the right response is not to pretend it is flat but to design the social arenas (tech-møtet, fagavdelinger, åremål, distributed personalledelse) so that the inevitable hierarchy is humane and productive.
  5) Vidar Moe: Det eneste Vidar vil er å ha det lett · p9

2026-02

• implicitThe widespread practice of onboarding a coding agent like a new human hire (office tour, org chart, architecture walkthrough) misapplies a model of discovery cost that doesn't hold for agents, which can grep an entire codebase before a human finishes typing a prompt.
  Stop Using /init for AGENTS.md · p13

2026-04

• explicitdevelopedThe traditional developer experience design paradigm (progressive disclosure, visual hierarchy, interactive examples) is partially obsolete for agent consumers.
  Agentic Engine Optimization (AEO) · p7
• explicitcorroboratedLLM non-determinism can be sufficiently tamed for production coding workflows by wrapping AI in a strict hierarchy: hard-coded hooks/scripts first, specialized narrow agents second, project rules/memory third
  Accelerating Delivery: How AI Agents Can Own the Initial Code Draft · p3
• explicitdevelopedBurnout manifests differently depending on one's position in the organizational hierarchy, shaped by control, clarity, and moral alignment rather than workload alone.
  Burnout Looks Different Across the Org Chart. Watch for These Signs. · p2
• implicitThe factory/manufacturing mental model is the default frame most organizations bring to product development operations, and it is the wrong frame.
  Introduction · p8
• explicitThe modern org chart requires wide span of control, direct work with ICs, and a binary of building or selling.
  The founder of Postman says you have to kill your existing org chart · p2
• implicitPRDs and Figma-only workflows are symptoms of the old hierarchy, not intrinsically valuable activities.
  The founder of Postman says you have to kill your existing org chart · p8
• explicitDorsey's 'Hierarchy vs. Intelligence' repackages control as freedom — it increases legibility while assuming legitimacy
  TBM 414: Legibility and Legitimacy · p3
• prescriptive claimObservability should follow a linked hierarchy (something is broken -> where -> why), paired with declarative, idempotent tooling that enables a first-rotation on-call engineer to resolve incidents as effectively as a ten-year veteran.
  Three Pillars of Platform Engineering: A Virtuous Cycle · p6

2026-05

• implicitRegulators, boards, and auditors will accept a structured 'mirror' log as a substitute for the human accountability previously provided by named individuals in a hierarchy.
  The Agentic P&L: Beyond the Empire of Headcount · p12
• explicitThese task-level gains attenuate sharply moving up the production hierarchy: the 180% cumulative commit effect falls to roughly 50% for the number of projects and to about 30% for actual releases; for sync agents specifically, a 741% increase in lines of code translates into only a 65% increase in pull requests and just a 20% increase in releases.
  Writing Code vs. Shipping Code: Productivity Effects Across Generations of AI Coding Tools · p2
• implicitBy making 'shipped and used' software the terminal measure of value, the paper's own hierarchy implicitly defines productivity around throughput-to-release rather than around other candidate outcomes (defect rates, maintainability, user-reported value) that this corpus's other sources treat as co-equal or more important consequences of the same AI-driven volume increase.
  Writing Code vs. Shipping Code: Productivity Effects Across Generations of AI Coding Tools · p13
• implicitdevelopedMost organizational systems (org charts, taxonomies, planning tools) are structurally incapable of holding more than one frame at a time; they flatten multi-frame reality into a single canonical view.
  TBM 423: Why Defining Teams Is So Hard · p13
• explicitdevelopedThe gap between aspirational and actual org models may be functional, not pathological — Brunsson's 'organized hypocrisy' lets contradictory stakeholders be satisfied simultaneously.
  TBM 423: Why Defining Teams Is So Hard · p8
• explicitBoth the enterprise architecture community ('museum of boxes') and the product framework community ('market-tecture') fail in symmetric ways when they treat their categories as mutually exclusive and collectively exhaustive.
  TBM 423: Why Defining Teams Is So Hard · p12

2026-06

• explicitdevelopedProductivity gains attenuate sharply as work climbs the organizational hierarchy: a 741% increase in lines of code written translates to only a 65% increase in pull requests and just a 20% increase in actual software releases.
  AI isn't making developers more productive – it's making them busier · p2
• explicitHierarki finnes uansett — in any group of more than one person there is always some operating hierarchy, even if the formal one is absent.
  4) Morten Eikeland: Det finnes alltid et hierarki · p1
• explicitBelieving one operates in a flat team while a strong kunnskapshierarki is in fact present is selvbedrag — not lying, but a collective self-deception that hides the operating hierarchy.
  4) Morten Eikeland: Det finnes alltid et hierarki · p3
• explicitcontestedSuppressing the visible signals of hierarchy (no separate offices, no penere bil for the sjef) does not abolish hierarchy; it makes it harder to read, especially for newcomers from høy-hierarki cultures, who are then destabilised by the diffuseness.
  4) Morten Eikeland: Det finnes alltid et hierarki · p4
• explicitPeople with power do not want hierarchy interrogated; this explains the structural avoidance of the topic in organisational discourse.
  4) Morten Eikeland: Det finnes alltid et hierarki · p5
• explicitWhichever profession plukker opp et element and successfully imposes its begrepsapparat on it controls the framing of organisational problems — making kunnskapshierarki the operating hierarchy in knowledge-intensive orgs.
  4) Morten Eikeland: Det finnes alltid et hierarki · p6
• explicitFINN's drift from a sales organisation to a teknologi-organisasjon is itself a hierarchy change — teknologene fikk mer makt, selgerne mindre.
  4) Morten Eikeland: Det finnes alltid et hierarki · p7
• explicitOrganisations are samfunnsspørsmål, not vitenskapelige problemer; the teknologisk-tenkning urge to find rotårsak and solve is the wrong methodological frame.
  4) Morten Eikeland: Det finnes alltid et hierarki · p8
• explicitRepetitive use of a generalised begrep makes us recognise but not understand it; gjenkjenne ≠ forstå. This is why digitalisering, AI, hierarki etc. drift into shared-label / un-shared-meaning failures.
  4) Morten Eikeland: Det finnes alltid et hierarki · p16
• explicitTwo structural mechanisms force hierarchy: (a) the internal coordination need that grows superlinearly with group size, and (b) the external need for one talsperson because outsiders cannot keep track of every gruppemedlem.
  4) Morten Eikeland: Det finnes alltid et hierarki · p20
• explicitOffice layout is a quiet hierarchy lever: teknologer sitting next to selgere produces cross-empathy; teknologer concentrated on their own etasje produces stronger in-group identity and decayed empathy for andre fag.
  4) Morten Eikeland: Det finnes alltid et hierarki · p21
• explicitTeknologi gave introverte, ofte sosialt-angste nerds a place where their fag created sosial status and gode penger; 30 years ago they would have been på NAV and slitt som et uver. This was a net good — but partly på bekostning av enklere selgere who lost makt as the dominant kunnskapshierarki shifted.
  4) Morten Eikeland: Det finnes alltid et hierarki · p23
• explicitCredibility signals form a hierarchy: demonstrated proof of work is strongest, a personal referral is powerful but risky because you spend someone else's reputation, and institutional affiliation is weakest because it only proves you once cleared a filter.
  How to ask for help from people who don't know you · p5
• explicitThe human capital a large firm manufactures best — the senior, reliable, politically-fluent veteran who can move a proposal through six committees — is almost exactly the kind that wastes token capital, because that person optimizes the org chart, not the loss curve.
  What is the harder human-capital problem beneath token capital? · p4
• explicitMirrors are not neutral — every mirror has a frame, and the frame is a choice; someone decides what gets reflected and how.
  TBM 426: The Trouble With Mirrors · p2
• implicitReality in organizations is socially constructed and multi-perspectival rather than singular and objective — the 'real world' invoked to foreclose alternatives is itself just one negotiated frame among others.
  TBM 426: The Trouble With Mirrors · p14

2026-07

• explicitdevelopedA software factory is many harnessed agentic loops running at once, fed by a queue of work and drained through a review gate into production, with humans owning the whole system from above — an org chart made of loops, not a bigger single agent.
  Software Factories, Light and Dark · p1
• explicitcontestedAI's coding-activity gains attenuate as work moves through the delivery hierarchy (lines of code -> files -> commits -> PRs -> repos -> releases): commit increases of +40% (autocomplete) to +180% (autonomous agents) top out at only ~+30% more releases shipped.
  Five studies that are changing how I think about AI in software engineering · p4
• explicitIt is rational to delegate to AI only the tasks at the bottom of one's goal hierarchy — tedious, low-learning-curve chores — while continuing to invest personal effort and attention where learning and expertise-building actually matter.
  Leadership Summit 2026: Inspiring Grit and Growth Amid Unprecedented Change · p9
• explicitGrit is not fixed; it changes across the lifespan, and on average people become grittier with age and experience, meaning grit can be deliberately built once its underlying goal-hierarchy structure is understood.
  Leadership Summit 2026: Inspiring Grit and Growth Amid Unprecedented Change · p15
• explicitRemix 3's server-driven UI mechanism ('frames' — independently loading/reloading server-rendered fragments) resembles HTMX's approach closely enough that multiple outside observers have made the comparison.
  Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework · p5
• explicitIn an analysis of 22,000 of his own agent conversations, a hierarchy where a small model owns the work and asks a big model for advice performs poorly (fidelity is lost passing context 'up'), while having the big model plan, decide, and check output while a small model only executes works cleanly.
  Stranded in the Slow Zone · p8

2026-08

• explicitMaking the facilitator and decision-maker roles explicit — independent of organizational hierarchy — prevents conversations from drifting toward decisions no one has authority to make, or from being derailed by an undisclosed veto.
  How the Best Leaders Shape Conversations · p4
• explicitcontestedExecutive teams have historically relied on simplifying strategy tools (SWOT, growth-share matrices, Porter's five forces) because of bounded rationality — finite human attention, memory, and processing power — but AI removes this constraint by generating and screening thousands of strategic alternatives, building continuously updated dynamic models of markets/customers/competitors, and testing ideas through simulated deliberation without the groupthink, hierarchy, and time pressure that distort real strategy meetings.
  Strategy Making Gets an AI Boost · p3

2026-09

• explicitOrganizations should shift from autonomous product teams to a nested and networked structure, in which value can be delivered without needing to traverse the formal hierarchy.
  Beyond Autonomous Teams in Software Product Development · p10
• implicitNetworked, hierarchy-bypassing coordination is implicitly assumed to have lower or comparable coordination cost than hierarchical coordination, since the piece presents 'not needing to traverse the hierarchy' as an unqualified benefit.
  Beyond Autonomous Teams in Software Product Development · p13
• explicitA software development team should be defined functionally as everyone and everything required for the individual to be successful, regardless of the org chart — including the running software itself, its infrastructure, and its tooling.
  Collective problem solving in music, art, science, and software · p3
• implicitCommunication media form an implicit cost/overhead hierarchy — document, infodeck, interactive web app, recording, live presentation, in ascending order of production and audience-attendance cost — and the rational choice is the cheapest rung that still achieves the communicative goal.
  Do you even need a presentation? · p9
• explicitEach of the five capability layers (ML, deep learning, generative AI, AI agents, agentic AI) is built on the one directly below it, forming a strict prerequisite hierarchy.
  Jimmy Acton's Post · p1

Open gaps (84)

• incompleteThe mechanism for change is under-specified. The article names the tools for redesign (predefined criteria, structured documentation, P&L pipelines, actionable feedback) and asserts the missing ingredient is 'willingness,' but does not operationalize how organizations actually adopt them or how to interrupt the self-reinforcing glass-cliff/savior cycle — the 'why diversity programs fail' problem it diagnoses is left as the reader's.
  What 60 Years of Data Reveals About How Men and Women Experience Leadership — read next: Change-adoption and implementation research (Kotter; 'Fearless Change' patterns), the organizational-behavior literature on de-biasing structured decisions, and HBR's own 'Why Diversity Programs Fail.'
• incompleteThe sample is 193 U.S. senior executives across unspecified industries plus a few qualitative interviews. Generalizability to other geographies (e.g., Nordic/European labor markets with different parental-leave and board-quota regimes), to organizational levels below the C-suite, and to non-corporate sectors is unaddressed.
  What 60 Years of Data Reveals About How Men and Women Experience Leadership — read next: Cross-national comparative and multi-level studies of leadership advancement, and the interaction of national policy (quotas, leave) with the underground-bias mechanism.
• incompleteHeadcount-as-political-capital is not reckoned with. The authors treat headcount purely as a productivity input that has been superseded. But in real enterprises, headcount is the currency of influence in budget negotiations, executive succession, real-estate claims, and cross-functional bargaining. A VP with 500 reports has structural leverage that a 3+N squad lead with equivalent cost per cognitive outcome simply does not have, because the negotiating game inside the firm is still played in headcount units. The article's 'reframing that works' assumes prestige and political capital will rebase on the new metrics; it does not argue for it.
  The Agentic P&L: Beyond the Empire of Headcount — read next: John Cutler on operating-system design and 'institutionalized overload' (TBM 411–413); Jeffrey Pfeffer 'Managing With Power' on resource-based political capital inside firms; Henry Mintzberg on the politics of organization; recent work on 'middle manager hollowing' under AI
• incompleteThe implicit theory of compensation and prestige re-anchoring is unargued. If pay and status currently track span-of-control, what is the mechanism by which they migrate to enclave density, RPP, and cost per cognitive outcome? Boards, peer benchmarking firms (e.g. Mercer, Korn Ferry), proxy advisors, and executive labor markets all currently price seniority partly on people-managed. The article needs an account of how this rebasing happens — or admits that early adopters will lose talent to firms still paying for empires.
  The Agentic P&L: Beyond the Empire of Headcount — read next: Compensation literature on equity comparators (Bebchuk, Fried); Korn Ferry and Mercer methodology papers; the 'platform company' compensation case studies (Stripe, Shopify) where small teams produce outsized revenue
• incompleteAccountability and liability allocation in the 3+N model is hand-waved. The 'human-as-rubberstamp' joke acknowledges the failure mode but the article does not specify who is on the hook when an agentic compliance decision causes a regulatory breach: the strategic architect? The policy-and-ethics lead? The vendor of the foundation model? The CFO who signed off on the cost-per-outcome budget? Without an answer, regulators are unlikely to treat the mirror as substantively equivalent to a named accountable individual.
  The Agentic P&L: Beyond the Empire of Headcount — read next: EU AI Act allocation of responsibility; the FCA / PRA senior managers regime in UK financial services; recent Bank of England consultation papers on AI in regulated firms
• incompletePower dynamics between the 3+N squad and the rest of the enterprise are unaddressed. If most of the cognitive work has shifted into squads, who allocates budget to them, who chooses what gyms to build, and who controls promotion across them? The article specifies the three internal human roles (architect, policy lead, orchestrator) but is silent on the governance layer above and the inter-squad coordination layer between.
  The Agentic P&L: Beyond the Empire of Headcount — read next: Spotify squad-tribe-chapter critiques (Henrik Kniberg's later writings, Marty Cagan); team-of-teams literature (Stanley McChrystal); Cutler on cross-team operating models
• incompleteThe argument frames career value purely through financial discounting, but late-career workers often report that meaning, legacy, mentorship, and intrinsic motivation become more important, not less. A late-career worker may rationally accept a long-dated equity grant because it locks them into a community of practice they enjoy. Beck's frame leaves no room for non-financial utility — which is striking given his own continued public writing and teaching, which are themselves long-dated, non-monetary investments.
  Extreme Time Value of Money: Late-stage Career Planning — read next: Erik Erikson's stage theory (generativity vs. stagnation); Arthur Brooks 'From Strength to Strength' on second-half careers; Robert Atchley's continuity theory of aging
• illogicalThe closing claim that networking lets teams 'deliver value without needing to traverse the hierarchy' risks conflating informal lateral coordination with actual decision rights, budget authority, and accountability, which typically remain hierarchical even when day-to-day coordination becomes networked. The piece treats bypassing hierarchy as an unqualified good without engaging the possibility that hierarchy persists for reasons (accountability, resource allocation) that a purely networked value-delivery model doesn't replace.
  Beyond Autonomous Teams in Software Product Development — read next: the corpus's hierarchy concept, esp. framing of hierarchy as structurally inevitable in groups rather than an artifact that networking simply dissolves
• incompleteCutler treats fiefdoms as cultural-political artifacts produced by unwilling leaders and self-interested fief-heads. He does not engage with the genuine structural pressures that may force fiefdom-like structures: capital-allocation cycles, headcount accounting, regulatory accountability, the way investors and boards read org charts, the difficulty of cross-fiefdom budgeting in a quarterly cadence. If those structural pressures are real, the 'hard choices' framing is too voluntarist.
  AI Won't Save the Kingdoms We Built — read next: Read management-accounting and capital-allocation critiques (e.g., Beyond Budgeting Round Table — Bjarte Bogsnes; Robert Simons on accountability systems; Niels Pflaeging on cell-structure designs). Also: Henry Mintzberg on configurations as responses to environmental contingency, not pathology.
• incompleteThe essay names 'coordination theater' but offers no test to distinguish it from real coordination in flight. Without a diagnostic, the concept risks becoming a rhetorical move rather than an operational lens.
  AI Won't Save the Kingdoms We Built — read next: Pair with Cutler's own prior work on operating systems / TBM 412 (institutional overload), and with explicit decision-rights frameworks (RAPID, DACI) that surface where decisions actually get made vs. where they are documented.
• incompleteThe 'people with a bias toward working alone' characterization is psychological, not structural. It does not interrogate why an organization rewards or selects for that bias — which is itself a fiefdom-era artifact (individual P&L-style accountability, individual performance ratings, etc.).
  AI Won't Save the Kingdoms We Built — read next: Allen Holub on accountability culture; Edmondson on psychological safety; Cutler's own earlier writing on directly-responsible-individuals and accountability culture.
• incompleteThe essay addresses leaders and the front lines but is silent on the middle layer — the fief-leaders themselves as actors who must decide whether to dissolve their own kingdoms. Their incentive structure is sketched (self-interest) but not engaged as a design problem.
  AI Won't Save the Kingdoms We Built — read next: Schein on organizational culture and middle-management as load-bearing; classic literature on 'turkey voting for Thanksgiving' problems in restructurings.
• empiricalNo evidence is offered for the claim that product development is categorically different from manufacturing operations. The introduction relies entirely on the reader's experiential recognition. Later chapters may supply theoretical grounding (endurant/perdurant, Scott's legibility) but the introduction treats the distinction as self-evident.
  Introduction — read next: Read chapters on endurant vs. perdurant and metis vs. legibility for the theoretical backing.
• scopeThe guide targets 'product development operations' but never defines where the boundary of that domain lies. Many of the same representation problems exist in policy, healthcare operations, and other complex domains. The introduction does not address whether the framework generalizes.
  Introduction — read next: Consider applying the ontology lens to adjacent complex domains to test generalizability.
• implicit_premiseThe argument assumes that the manufacturing mental model is the dominant frame organizations bring to product operations. This is plausible but unstated and undefended. Some organizations may already operate with complexity-aware models and still suffer the same visibility problems for structural or political reasons unrelated to ontology.
  Introduction — read next: Look for whether later chapters address political and power-dynamic causes of information distortion alongside representational causes.
• tensionThe introduction implicitly promises that better ontology design can resolve the visibility problem, but also acknowledges that 'words alone will rarely sink the ship.' This creates tension about how much explanatory weight ontology can actually bear versus organizational politics, incentives, and culture.
  Introduction — read next: Track how the guide handles the relationship between naming/representation and the social/political dynamics of organizations.
• incompleteThe two-way split erases the technical-track / IC-leadership ladder. The article scopes itself to 'the management path,' and even its code-adjacent option, the TLM, is defined by managerial load (1:1s, career conversations, project coordination) — i.e., it is still a manager. The staff → principal → distinguished ladder, where one leads through technical judgment and influence with no personnel responsibility ('leadership, not management'), is collapsed into 'management' or left out. For a reader on exactly that ladder, the dichotomy is a false binary: there is a third future — the technical leader who is neither a people-manager nor a coder-with-reports.
  The engineering manager role is splitting in two — read next: Read against 'Developing Your Leadership Skills toward Principal Engineering' (the whole IC-leadership-ladder case), heis-12 (a principal engineer orchestrating ~40 architects with no personnel authority, forced into a non-coercive leadership style), and 'kill your org chart' (staff/principal engineers holding project leadership) — all of which name the technical-leadership track this piece omits.
• incompleteThe binary is asserted, not shown to be exhaustive. The citations (Meta, Amazon, Gartner, Faros) establish that flattening is happening, not that it resolves into exactly these two EM archetypes rather than a spectrum, durable hybrids, or outright role dissolution. No evidence is offered that organizations must pick one; the intermediate case (a TLM who also carries some cross-team scope) is excluded by construction rather than by argument.
  The engineering manager role is splitting in two — read next: Read against 'AI Won't Save the Kingdoms We Built' (flattening as politics and cost, with coordination burden re-emerging in a new shape rather than vanishing) and 'Your AI strategy has a trust problem' (flat high-autonomy pods as a third structural option), which suggest the fork is one framing among several.
• incompleteThe article never addresses the organizational/political reasons teams keep defaulting to live meetings and slide decks despite the overhead the author identifies (status signaling, visibility, habit, hierarchy expectations) — it treats the choice as a purely rational medium-fit decision, ignoring why the 'irrational' default persists.
  Do you even need a presentation? — read next: Read into organizational-change or meeting-culture literature (e.g. work on meeting overload, status theatre, or Cutler-style institutional-overload framing) for why the rational choice the author recommends is hard to adopt in practice.
• unstated assumptionFowler's curation implicitly assumes that the discipline-vs-tarpit tension is the defining axis of AI-assisted development, but economic and organizational dimensions (team structure, hiring, skill deskilling) are largely absent from the fragments selected.
  Fragments: May 5 — read next: Cross-reference with pieces on how AI changes team composition and organizational design (e.g., the 'kill your org chart' literature).
• uninformedNo mention of model-level defenses (instruction hierarchy, input sanitization at the model layer) as a complementary security layer. The architecture is entirely infrastructure-level, treating the model as a black box.
  How GitHub Is Securing Agentic Workflows in Modern CI CD Systems — read next: Research on instruction hierarchy in LLMs; OpenAI and Anthropic publications on model-level prompt injection defenses.
• incompleteThe digest asserts that 'the best CEOs' ask quarterly where the reported and lived organizations diverge, but gives no mechanism for how that inquiry is actually conducted, who is consulted, how the findings avoid being filtered back into a curated 'reported' answer, or how findings are acted on. Without a described mechanism, the practice risks becoming another reported-organization artifact (a 'we discussed culture at the offsite' checkbox) rather than a genuine channel to the lived organization.
  Every Organization Has Two Realities — read next: extract-hbr-frontline-workers-solve-problems' six-step confidential-listening process is a concrete mechanism for exactly this gap — it operationalizes how to extract lived-organization signal without it being filtered by the reporting hierarchy.
• incompleteThe digest frames organizational truth as binary — a 'reported' account and a 'lived' account, both simply 'true' — without engaging the more general problem that there is no single lived organization either: different employees, teams, and levels each hold partial, interested, negotiated views of what's really happening. The two-organizations frame may itself be a simplification that a curious CEO could act on too literally (assume there are exactly two truths to reconcile, rather than many).
  Every Organization Has Two Realities — read next: extract-tbm-426-trouble-with-mirrors argues organizational truth is not hidden-but-discoverable, it is continuously negotiated among many partial, interested viewpoints — directly complicates the two-organizations frame's implicit assumption that the lived organization is a single, findable ground truth.
• illogicalThe 'defy gravity' claim — that trade-off physics apply identically in services as in physical products — is asserted by analogy ('the same physics applies') rather than demonstrated; the hosts never specify the underlying constrained resource (attention? budget? headcount? culture bandwidth?) the way weight/materials constrain a laptop.
  Dare to Be Bad at Something (From Fixable) — read next: Operations-management literature on service-quality trade-off mechanisms (queuing theory, capacity-utilization trade-offs) that would ground the metaphor mechanistically rather than rhetorically.
• incompleteThe piece gives no treatment of incentives or political economy: why would senior partners, rainmakers, or otherwise entrenched leaders willingly submit to peer-enforced standards and give up autonomy? No discussion of resistance, power, or what happens to leaders who refuse to comply appears anywhere, including in the case study, where the two-day forum and board-governance reset are described as succeeding without any account of who resisted or what it cost them.
  How to Turn Individual Talent into Organizational Excellence — read next: extract-cutler-ai-wont-save-kingdoms directly engages the political-economy angle this piece elides — fiefdoms persisted 'despite visible pain' because leaders were unwilling to prioritize across them and fief-leaders had self-interest in preservation; the 'real' fiefdom problem is political-economic, not informational.
• incompleteNone of the tips address feedback across power or identity asymmetries — feedback from a junior employee to a senior manager, cross-cultural feedback norms, or feedback where the recipient has structurally less power to push back or seek recourse if the giver's guardrails fail. The bias-auditing prescription in Tip 1 is the closest the piece comes, but it addresses giver bias, not the receiver's structural vulnerability.
  Our Favorite Management Tips on Giving Feedback — read next: Research on upward feedback, psychological safety across hierarchy, and cross-cultural management (e.g., Erin Meyer's work on feedback norms across cultures) would fill this.
• incompleteSame system-shift-framed-as-practice-tweak pattern recurring across the user's recent extractions (Cutler, Osmani, Reed, HBR Career-Growth-Overwhelmed). Duffy diagnoses a structural failure of the manager layer to keep pace, then prescribes individual behavior changes that leave organizational architecture, role boundaries, decision rights, and compensation untouched.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: Pair with Cutler 'AI Won't Save the Kingdoms We Built' and Osmani 'Orchestration Tax is You' for the syntopical thread. The unanswered question: when is the manager role itself the bottleneck-design, and what would an AI-era org chart actually look like?
• incompleteThe thesis 'det finnes alltid et hierarki' is rescued from triviality by Eikeland's broad definition (formell + uformell + kunnskaps- + framing-makt), but the same breadth makes the claim nearly unfalsifiable. Every conceivable group has some asymmetry of influence on some dimension; calling that 'hierarki' wins the argument by definition. The conversation does not engage the harder question of when the unit of analysis is wrong — when treating a temporary, context-dependent, weak asymmetry as a 'hierarchy' obscures more than it reveals.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Compare to network-and-influence literature (Cross/Parker on organisational networks, Vedres/Stark on structural folds) where the alternative unit is the network of weak ties rather than the layered hierarchy. Also Heath/Sunstein on consensus-driven decision-making to test where 'hierarchy' really is the operating frame.
• incompleteThe claim that flat-org rhetoric is selvbedrag is supported by Eikeland's clinical observation and the innvandrer vignette but not by counter-evidence from organisations that have made the rhetoric operationally real (or that have failed in distinctively non-Eikeland ways). The conversation does not engage Holacracy, Buurtzorg, sociocratic governance, or the long literature of self-managing teams. The result is a strong descriptive claim resting on a single vantage point.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Read Laloux Reinventing Organizations, Buurtzorg case studies, Robertson's Holacracy critically — both for examples of self-organisation that genuinely changes which hierarchy operates and for documented failures that Eikeland's frame would explain well. Pair with Lee/Edmondson's typology of self-managing organisations.
• incompleteThe role-vs-person distinction is presented as universal but it conflicts with a strong current of contemporary leadership literature (authentic leadership, bring-your-whole-self-to-work, vulnerability-based trust à la Lencioni/Brown) that holds that role-thick depersonalised leadership is itself the failure mode in knowledge work. The conversation does not engage these counter-positions; it treats them only implicitly via the Trump example, which is a one-sided foil.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Read Brené Brown on Dare to Lead, Goffee/Jones 'Why Should Anyone Be Led by You?', Lencioni on vulnerability-based trust against Eikeland's role-thick line. The most interesting test case is: are there role-domains where role-thickness is right (dommer, kirurg, politi) and other domains where it is wrong (product-team leadership, R&D leadership)?
• incompleteEikeland's developer-to-leader sorgprosess prescription is rich on the loss side but thin on the gain side. The transition presumably brings new sources of meaning (impact through others, system-level effect, mentoring, organisational design), but the conversation barely names them. The risk for the listener is to internalise the loss-frame and miss the path through.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Camille Fournier's Manager's Path; Will Larson's Staff Engineer/An Elegant Puzzle on the IC-vs-manager fork; Lara Hogan on growing engineering leaders. Pair with Olga Khazan or Lori Gottlieb on the psychology of mid-career identity transitions.
• incompleteThe illusion-of-explanatory-depth intervention (ask for mekanismer not meninger) is presented as reliably productive but Eikeland admits it provokes forbannelse and ejection from rooms. The conversation does not address how to make the intervention land without burning the relationship — i.e., the practice question of how to descend into mekanisme safely. This matters because the intervention has weight only if it can be sustained inside an ongoing leader relationship.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Edgar Schein on humble inquiry; Marshall Goldsmith on stakeholder-centred coaching; Patterson et al. Crucial Conversations. The Heis-internal pairing is with Brede Moe (ep 9) on psykologisk trygghet as the precondition for being usable as a diagnostic outsider.
• uninformedThe argument that teknologene have gained makt at the expense of 'litt enklere selgere' is named as a flagged trade-off but not analysed. The conversation does not engage the broader political-economy story of which professions rise and fall with each kunnskapshierarki shift, or the consequences for democratic and labour-market dynamics when one type of fag becomes dominant. Eikeland's clinical vantage is not designed for this question; the gap is honest but real.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Read Daniel Markovits The Meritocracy Trap, Michael Sandel The Tyranny of Merit on the consequences of credentialist hierarchies. For the Norwegian case specifically, NAV's own reports on labour-market polarisation.
• incompleteEikeland insists hierarchies are inevitable but does not develop how to design good hierarchies versus bad ones. Hierarchy as a design object — its arity (span of control), its time-horizons per level, its dual lines (formal/uformell), its rotation, its accountability — receives no operational attention. The descriptive claim therefore stops short of a constructive prescription beyond 'operate at the right abstraksjonslag and recognise rolle vs person.'
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Elliott Jaques on requisite organisation and time horizons per level; Stafford Beer's Viable System Model; James Mwangi on adaptive governance. Pair with Printzell Halvorsen (ep 8) on the Vend operating model as a worked example of an explicit, designed hierarchy that honours these structural pressures.
• incompleteThe claim that ledelse-as-coordination kicks in around eight people is asserted as 'avhenger litt av hvor mye interaksjon du trenger' but not defended against the broader social-science literature on group size, span of control, and self-organisation thresholds. The number is plausible but the conversation does not engage why eight rather than five or twelve, what happens in distributed/asynchronous groups, or how the threshold shifts with technology.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Robin Dunbar's hierarchies of group size (5, 15, 50, 150); Christopher Allen's optimal group sizes; Tuckman's small-group dynamics. For the distributed case, GitLab's all-remote handbook on team sizing and the post-COVID literature on async coordination.
• incompleteThe episode systematically tells the success-side of the story. Crisis → response → improvement is the recurring arc, but failed experiments, dead-end framework choices, or instances where 'gjøre det lett og rett' produced unintended organisational uniformity are absent. Moe's stated regret is only directional (could have done more, faster, in more places), not structural (e.g. 'this particular default we engineered was wrong'). The hosts twice surface the hierarchy-is-inevitable point but do not press on whether the framework-team's 'easy and right' becomes a hidden orthodoxy.
  5) Vidar Moe: Det eneste Vidar vil er å ha det lett — read next: Pair with Allen Holub's #NoAccountability strand (already in the user's persona) and with anything on the costs of platform-engineering paved roads (e.g. Charity Majors / Honeycomb on the limits of golden paths). The user's existing extraction on Cutler's institutionalised overload is a strong complement here — Cutler's frame would ask what the second-order costs of the SpareBank 1 system look like.
• incompleteMoe's persistent 'vi' is itself a load-bearing rhetorical pattern that the hosts notice in closing but do not unpack. The episode is a portrait of a person who declines to be individuated — he says 'vi' even when narrating decisions whose intellectual origin clearly lies with him personally. This is consistent with the leadership-through-defaults thesis (the work is the structure, not the speaker) but it also obscures the part of the story that does depend on a specific senior practitioner persistently present in the system for 14 years. The question 'how transferrable is this without Moe (and Stian)?' is not engaged.
  5) Vidar Moe: Det eneste Vidar vil er å ha det lett — read next: Read in tension with the previous Heis episode on hierarchy (Eikeland, ep 4, alluded to: 'forrige podcast-episoden snakket om... det er sjelden helt flat struktur') and with the leadership-presence strand in the user's library (Cutler on power and space, TBM 413). Beck's writing on senior individuals' role in evolutionary design is a direct anglophone parallel.
• incompleteHenderson presents the engineer/manager dual-ladder as simply working, with no acknowledgment that a later cost-driven flattening trend (fewer managers, broader spans, informal TLM blending) might erode exactly the separation his argument depends on.
  Software Engineering at Google — read next: See extract-engineering-manager-role-splitting-in-two for the 2020s-era pressure toward recombining tech-lead and manager duties, and whether Larson's 'TLM is unstable' critique applies once team sizes shrink.
• incompleteThe lab-vs-enterprise conflation. The argument is strongest for frontier labs that BUILD token capital (models, evals, loops require irreverent frontier-movers) and weakest for the telco, bank or typical enterprise that BUYS and absorbs it. A firm that consumes AI rather than pushing the frontier may not need 'permission-averse, loudly-wrong' talent at all — for it the binding constraint is more likely absorption, integration and process legibility than porousness for mavericks. The essay treats the two as one problem and never tests whether its prescription even applies to the majority of the 54% of employment it invokes.
  What is the harder human-capital problem beneath token capital? — read next: Read against the enterprise-AI-adoption literature that separates building vs. buying/absorbing AI capability (e.g. forward-deployed-engineer and readiness models): does a token-capital consumer need frontier-mover porousness, or is its real obstacle organizational absorption, and would importing 'uncorporate' talent even help?
• incomplete'Porous structure' is named as the answer but never operationalized. The essay supplies no mechanism, org-design pattern, incentive structure, or worked example of what porousness looks like, nor how a firm hands 'corporate-scale compute + responsibility' to uncorporate people without recreating the committees and procurement logic that sand them down. The prescription is a direction, not a design.
  What is the harder human-capital problem beneath token capital? — read next: Read toward concrete structural patterns that could fill the mechanism — small-teams/tiny-core bets, autonomous-team designs, skunkworks and lab-within-a-company structures — and test which actually preserve irreverence at corporate scale.
• illogicalThe essay's own evidence strains against its thesis. Demis Hassabis built Gemini INSIDE Google, a corporate giant — 'in spite of' it, yes, but still inside it and still winning — which shows rigid incumbents CAN produce frontier results, cutting against the flat claim that structure 'selects frontier talent out.' By naming only the winning obsessives (Hassabis, Dean, Liang Wenfeng) it also survivorship-selects, saying nothing about the uncorporate people who were in fact crushed. So 'structure selects them out' is asserted more strongly than the evidence, which really shows 'structure taxes them, but some still win.'
  What is the harder human-capital problem beneath token capital? — read next: Read comparatively for cases where incumbents DID retain and productively hold frontier talent, to separate the strong claim ('structure filters them out') from the weaker, better-supported one ('structure imposes a heavy tax they sometimes overcome').
• unstated assumptionThe argument assumes that coordination, alignment, and context-sharing across teams are either unnecessary or automatically handled in flat structures. Large-scale organizations face coordination problems that are not solely caused by hierarchy but by the inherent complexity of distributed work.
  The founder of Postman says you have to kill your existing org chart — read next: Literature on coordination costs in flat organizations (e.g., Galbraith's information-processing theory of organization design); case studies of flat-org failures at scale.
• missing evidenceNo evidence is provided that PMs building APIs or designers shipping PRs produces better outcomes than the prior division of labor. The implicit claim is that directness equals quality, but this conflates shipping speed with product quality.
  The founder of Postman says you have to kill your existing org chart — read next: Research on specialization vs. generalization in knowledge work; outcomes data from companies that have adopted these structures.
• selection biasThe argument is attributed to the founder of Postman — a developer-tools company where engineering culture is dominant. The prescription may not transfer to organizations where the core work is not software (healthcare, logistics, manufacturing).
  The founder of Postman says you have to kill your existing org chart — read next: Compare with AI-era org design thinking in non-tech industries.
• unacknowledged tensionThe binary 'either you're building, or you're selling' erases important organizational functions: strategy, research, compliance, people development, customer success. These are neither building nor selling but may be essential.
  The founder of Postman says you have to kill your existing org chart — read next: Consider which organizational functions are genuinely automatable vs. which are being rhetorically dismissed.
• incompleteTreats trust as a leadership-behavior problem (leaders should give trust, employees should accept accountability) rather than an org-design or contract/incentive problem. There is no mechanism design — no discussion of decision rights documents, RACI alternatives, equity/comp restructuring, escalation policies, or measurement systems that would make agency stick when individual managers regress to control. Pattern-matches to the HBR Managers AI Productivity Boom piece: name a structural problem, prescribe individual remedies.
  Your AI strategy has a trust problem, not a tooling problem — read next: Reinertsen, 'The Principles of Product Development Flow' (decision rights and queue economics); Hamel & Zanini, 'Humanocracy' (post-bureaucratic org design with explicit mechanisms); Laloux, 'Reinventing Organizations' (advice process as a contract for distributed decisions); Spotify's matrix history and post-mortems; works on internal markets for decision rights.
• incompleteThe accountability-and-comp argument is named but not operationalized. If ICs newly carry decision accountability, what is the manager premium for? She gestures at the tension and moves on. Without a comp/perf-review redesign, the agency upgrade is unilateral risk transfer.
  Your AI strategy has a trust problem, not a tooling problem — read next: Buurtzorg's flat-pay model; literature on profit-sharing and gainsharing; recent work on equity-as-accountability-comp in startups.
• illogicalThere is a quiet tension between 'centralize information' (named as a benefit reducing the need for middle managers to coordinate) and 'distribute decisions' (the agency thesis). Centralized information typically implies central gatekeeping; distributed decisions imply distributed access. The piece doesn't say what mechanism resolves the tension at scale — 'parented agents' is gestured at but not specified.
  Your AI strategy has a trust problem, not a tooling problem — read next: Conway's Law literature; works on platform engineering as context distribution; Team Topologies (Skelton & Pais).
• incompleteNo engagement with the failure modes of the prescription: pilot pods that become innovation theater; flat pods that recreate informal hierarchies; high-velocity decision-making that produces irreversible decisions before reflection (e.g. customer trust violations). The closing trust-based-growth move actually heightens this risk — fast public action with low oversight.
  Your AI strategy has a trust problem, not a tooling problem — read next: Failure-mode analyses of holacracy at Zappos; post-mortems on flat orgs (Valve, GitHub pre-2014); Karen Ho 'Liquidated' on what happens when decision velocity outruns institutional memory.
• incompleteThe essay never reconciles the tension its own evidence walks into: the LeadDev data it cites to show managers 'doing more' (more scope, more reports, more communication) is, elsewhere in this corpus, flagged as an unresolved structural contradiction — manager quality/attention is the single biggest lever on wellbeing, yet spans of control keep widening. If managers are stretched across more reports and more scope, their capacity to perform the very behaviors credited with driving AI value (individualized modeling, psychological safety, quality-standard setting) may itself erode, an inference the essay never draws.
  Managers Are Not Overhead: They Are Infrastructure — read next: Reads as a partial answer to the reconciliation gap named in extract-lenny-noam-segal-tech-worker-ai-sentiment-2026#g2 and extract-tech-workers-2026-workforce-splitting-in-two#g4 (orgs flattening while manager quality is the biggest wellbeing lever) and extract-postman-engineering-leadership-report-2026#g5 (the same report's own reassurance-vs-accelerating-flattening tension) — but it only asserts a side (invest in/preserve managers) rather than explaining how broader spans and deeper manager investment can coexist.
• unaddressedThe essay rebuts the 'AI replaces manager tasks so cut managers' narrative in general terms ('managers are infrastructure') but never engages the sharper, competing claim already in circulation that AI eliminates specifically the *coordination* function managers historically performed (not managerial value generally) by letting ICs and PMs ship directly — a claim that argues for redefining, not simply preserving, the role.
  Managers Are Not Overhead: They Are Infrastructure — read next: Read against extract-kill-your-org-chart-for-ai (management's purpose becomes developing judgment, not coordination) and extract-engineering-manager-role-splitting-in-two (the TLM/multi-team-EM fork) for competing accounts of which manager functions AI actually obsoletes versus elevates.
• incompleteEvery case in the article — Gupta, Horta-Osório, the unnamed industrial-company CEO, the energy-company CEO, the pharma CFO, the retail-bank CEO — sits at CEO, chairman, or C-suite level. The article's own opening claim ('the bottleneck is at the top') is never tested against a case where the bottleneck is one level below the top: a business-unit leader or VP whose own boss is not modeling the transformation. It is left unaddressed whether visible modeling by a sub-CEO leader can still move their own team's behavior, or whether the effect requires the very top of the hierarchy to model it.
  Model the Transformation You Expect Employees to Deliver — read next: Read alongside middle-management- or informal-leadership-focused accounts of change agency operating without top-level air cover, to test whether 'modeling' works bottom-up/mid-up or only top-down.
• incompleteParrish offers no operational test for distinguishing wisdom from intelligence. If wisdom is choosing the right goals, then choosing well is itself a kind of getting-what-you-want — meta-getting. The distinction risks collapsing into 'intelligence applied to first-order goals' vs. 'intelligence applied to goal-selection' — i.e., into a hierarchy of intelligence rather than a separate faculty. Without a test (e.g., regret-rate, time-horizon of evaluation, second-order satisfaction), the aphorism is a vibe, not a tool.
  Brain Food: Intelligence vs. Wisdom — read next: Annie Duke, *Thinking in Bets* and *Quit* (separating decision quality from outcome quality; resulting; expected value of changing course). Russ Roberts, *Wild Problems* (decisions whose value cannot be precomputed — the closest contemporary treatment of 'what's worth wanting'). Aristotle's *Nicomachean Ethics* on phronesis (practical wisdom) vs. sophia and techne. Harry Frankfurt on second-order desires ('Freedom of the Will and the Concept of a Person').
• incompleteThe post withholds the one concrete example it invokes as proof of stakes ("gets into something much bigger than AI") — the actual mechanics of how Bayer folded AI into its 90-day-cycle model are entirely absent, deferred to a separate Thursday newsletter. As written, this is a teaser for an argument rather than the argument itself.
  Pim de Morree's Post — read next: Read the referenced Thursday newsletter (linked via https://lnkd.in/emN_R95n) for the actual case detail and the fixed-jobs argument.
• incompleteThe article never explains what 'unbundling' concretely means for build tooling in practice — how source maps, tree-shaking, code-splitting, or third-party bundler-dependent tooling are handled once 'the runtime rather than a bundler is the source of truth' — so readers cannot assess the real tradeoffs of dropping the bundler model.
  Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework — read next: Remix 3's own documentation/source once the beta stabilizes; comparisons with other runtime-first, no-bundler approaches (e.g., Deno's native TypeScript execution, import maps) to see what unbundling typically costs or saves.
• incompleteThe article reports that a forked Preact replaces the React runtime but never quantifies the performance, bundle-size, or ecosystem-compatibility implications (e.g., React DevTools, existing React component libraries) of forking Preact rather than adopting it unmodified or retaining React.
  Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework — read next: Benchmarks and compatibility write-ups once Remix 3 ships stable; the fork's own diff/changelog against upstream Preact.
• illogicalThe article asserts Remix 3 is 'the boldest bet yet on web standards over framework abstractions' against Next.js, SolidStart, and SvelteKit, but never tests whether Remix 3's claimed full-stack breadth (auth, uploads, data/database management, theming) is actually delivered with comparable maturity to those competitors — the comparison is asserted, not demonstrated.
  Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework — read next: A hands-on feature-parity comparison across Remix 3, SvelteKit, and SolidStart on the specific claimed full-stack capabilities.
• uninformedThe article does not explain why the team chose to keep JSX as authoring syntax while dropping React's virtual-DOM/reconciliation model entirely — a design tension between 'web standards' purism and retaining a React-shaped authoring surface that is never addressed or justified.
  Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework — read next: The team's own 'Wake Up, Remix' rationale post; any interviews with Michael Jackson explaining the JSX-retention decision.
• incompleteCutler identifies the problem (legitimacy is skipped) and gives the Haier counter-example, but doesn't describe what legitimacy-grounded AI organizational design would actually entail. The essay points at the question but doesn't begin to answer it.
  TBM 414: Legibility and Legitimacy — read next: James C. Scott's 'Seeing Like a State' (the source of the legibility/power argument); democratic workplace theory; platform cooperativism literature
• incompleteThe critique targets Dorsey specifically but the pattern Cutler describes (efficiency metrics as value substitutes, decentralization rhetoric concealing control) applies to most AI organizational proposals. The essay doesn't synthesize the critique into generalizable criteria.
  TBM 414: Legibility and Legitimacy — read next: Literature on algorithmic management: 'The Platform Society' (van Dijck et al.); Nick Srnicek's 'Platform Capitalism'; Cutler's own TBM work on operating systems and accountability
• illogicalThe coda ('AI is a catalyst for whatever you already believe') slightly undermines the specificity of the critique. If AI just amplifies existing values, then the problem is Dorsey's pre-existing values — not a rhetorical trick specific to AI. This is a different and stronger argument than Cutler develops.
  TBM 414: Legibility and Legitimacy — read next: Winner's 'Do Artifacts Have Politics?' — the more rigorous version of this claim
• uninformedCutler doesn't engage with the existing literature on algorithmic management (gig worker surveillance, scoring systems in platform companies like Uber/Amazon warehouses). These are the live cases where the legibility/legitimacy conflict has already played out, with empirical data.
  TBM 414: Legibility and Legitimacy — read next: Alexandrea Ravenelle's 'Hustle and Gig'; Alex Rosenblat's 'Uberland'; Shoshana Zuboff's 'The Age of Surveillance Capitalism'
• incompleteCutler's prescription is essentially individual ('surf the tension', 'find pockets'). He gestures at — but does not develop — what institutional design would look like for an organization that natively holds two views. The flattening tendency of org systems is named but not redesigned.
  TBM 423: Why Defining Teams Is So Hard — read next: Stafford Beer's Viable System Model and Espejo on organizational cybernetics (which explicitly model multiple recursive views of the same system); Wardley mapping for multi-frame strategy; Niels Pflaeging's beta-codex / 'org physics' (cells vs. functions). Also Cutler's own earlier writing on 'operating systems' for product orgs.
• incompleteDesign is positioned as the 'truth-telling' frame because designers see the seams, but design's own blind spots and the cost of giving design more structural power are not examined. The essay grants design moral authority without scrutinizing it.
  TBM 423: Why Defining Teams Is So Hard — read next: Jared Spool and Don Norman critiques of design's overreach; service design literature on the limits of journey-mapping; Tony Ulwick / jobs-to-be-done as a competitor frame that disputes design's own narrative.
• incompleteThe essay focuses on the product/design/tech axis inside a single org. It does not address how this dynamic changes in regulated, public-sector, or critical-infrastructure orgs where 'teams' are also legal/audit/governance entities — a context particularly relevant to Norwegian public-sector tech (NAV, Entur, public services).
  TBM 423: Why Defining Teams Is So Hard — read next: Pia Andrews / GovTech writing on public-sector team design; Mark Schwartz ('A Seat at the Table', 'War and Peace and IT') on bureaucracy and IT leadership; Mariana Mazzucato on mission-led public organizations. For the Nordic context: Skatteetaten/NAV/Entur case studies on team topologies in regulated environments.
• incompleteThe 'pendulum' framing is descriptively useful but normatively underspecified. Cutler observes the swing between 'everything is a product' and 'three products only' but doesn't propose what the stable middle looks like — what's the unit of organization that resists both inflation and deflation of the product label?
  TBM 423: Why Defining Teams Is So Hard — read next: Team Topologies (Skelton & Pais) explicitly types teams (stream-aligned, platform, enabling, complicated-subsystem) as a possible answer; Sriram Narayan on agile organization design; Marty Cagan's 'empowered product teams' framing as a competitor.
• incompleteAI/agent-assisted development is conspicuously absent from an essay published in 2025/2026 about how teams are defined. If a meaningful share of engineering work is mediated by agents, the definition of 'team', headcount-as-cost, and the engineering manager's role all shift. Cutler doesn't touch this, though it is plausibly the next pendulum swing.
  TBM 423: Why Defining Teams Is So Hard — read next: DORA AI capabilities report; Kent Beck on AI-assisted design ('Tidy First?' series); Addy Osmani / Steve Yegge on agentic engineering; Cutler's own TBM pieces on institutional overload and AI (TBM 412).
• incompleteCutler's prescription ('surf the tension', 'find pockets') leaves the change agent without a diagnostic for distinguishing a real pocket of opportunity from a temporary opening that will close, or from a trap that consumes effort without producing change. The post advises a posture but not a method.
  TBM 423: Why Defining Teams Is So Hard — read next: Donella Meadows' 'Places to Intervene in a System' (leverage points hierarchy) supplies the missing taxonomy of where intervention has high leverage. Fearless Change (Manns & Rising) — which Kjetil's persona shows he highlights heavily — supplies pattern-level guidance for what to do once a pocket is identified.
• incompleteThe post diagnoses the asymmetric cost geometry but never asks whether the asymmetry could itself be redesigned. Could product be held accountable for operational consequences? Could design have budget authority? Cutler treats the geometry as a given and prescribes only how to live within it.
  TBM 423: Why Defining Teams Is So Hard — read next: Allen Holub's #NoAccountability work and the broader DRI (Directly Responsible Individual) literature — which Kjetil already engages with — would supply the missing accountability-redesign frame. Henrik Kniberg's writing on Spotify-era squad accountability is another natural extension.
• incompleteThe post is silent on AI tooling, despite Cutler's recent series on AI and organizational design. This is a striking absence — if AI is changing how work is coordinated (skills, agents, asynchronous artifacts), does it also change the cost asymmetry that this post identifies as the root cause?
  TBM 423: Why Defining Teams Is So Hard — read next: Re-read TBM 412 (institutionalized overload + AI) and TBM 418 (campfires, trails, quests) against this post. Test whether AI-mediated artifacts could shift the cost asymmetry — does cheap AI-generated documentation make tech's 'I have to live with it' position cheaper or more expensive?
• incompleteThe post barely engages with what 'aspirational' actually looks like — there is no example of a North-Star map that is being incrementally closed versus one that is permanent theater. Without exemplars, the distinction is rhetorical rather than operational.
  TBM 423: Why Defining Teams Is So Hard — read next: Team Topologies (Skelton & Pais) — their stream-aligned/platform/enabling/complicated-subsystem taxonomy is the closest thing to an operational aspirational map; useful to read it through Cutler's lens to see whether it survives the 'permanent theater' test.
• illogicalCutler argues both (a) describing reality is cognitively easy and (b) organizational history is load-bearing and rarely documented. If the historical context is missing, then describing reality is not actually easy — it is partial in ways the workshop participants cannot fully see. The post does not reconcile these two claims.
  TBM 423: Why Defining Teams Is So Hard — read next: Engage with Edgar Schein on organizational culture as historically embedded — the surface-level description that workshops surface may be necessary but not sufficient, and the post understates how much remains invisible even after the political cost has been paid.
• incompleteThe C-suite is named (via Dame's quote — 'cross-functional with complete oversight') but never analyzed as itself a structural location with its own incentive geometry. If the fractal breaks at middle management, what is the corresponding pathology at the top?
  TBM 423: Why Defining Teams Is So Hard — read next: Henry Mintzberg on structure in fives; Russ Ackoff on idealized design — both supply tools for analyzing the C-suite as an organizational location rather than a moral category. Camille Fournier on engineering leadership ladders is closer to home.
• incompleteCutler shows that mirrors alone don't produce change and pivots to 'mirroring', but never shows how mirroring actually surfaces and resolves the hard, uncomfortable realities (the coin-flip odds, the org-chart vestiges) that mirrors were meant to confront. Without that, 'helping people feel seen' risks becoming a sophisticated way to avoid the elephants — comfort substituting for change, and the resolution quietly undermining the very problem it set out to solve.
  TBM 426: The Trouble With Mirrors — read next: Read Amy Edmondson on psychological safety as enabling candor (not merely comfort); Kegan & Lahey, Immunity to Change, on how meaning-making translates into action; and Peter Block's Community in full, alongside Cutler's own operating-systems / legibility work (TBM 414, the visibility guide) for the mechanism from being-seen to actually confronting the hard things.
• incompleteThe relationship between mirroring and accountability is left unresolved. Cutler insists surfaced truth must be met with 'stewardship' and asks 'who is accountable for what happens next', yet the mirroring resolution emphasizes feeling seen and NOT being 'held against' people — potentially in tension with the accountability that acting on uncomfortable truths requires.
  TBM 426: The Trouble With Mirrors — read next: Read on accountability cultures (Allen Holub) and the distinction between blame and accountability; Cutler's own writing on directly-responsible individuals; and restorative-vs-punitive framings of organizational feedback.
• incompleteThe cynical, power-analytic read of transparency advocates ('actually about power'; candor is cheap for the already-won) is asserted without evidence and, as Cutler half-concedes ('I realize all of this sounds negative'), risks proving too much: by the same logic his own mirroring prescription is equally positional and equally a bid to define what good relating looks like.
  TBM 426: The Trouble With Mirrors — read next: Read Langdon Winner, 'Do Artifacts Have Politics?', and critical-management studies for the rigorous version of the power-in-ideals claim, and test whether the argument self-undermines when turned on the author's own prescription.
• incompleteNo account of mechanism or scale. Cutler's clearest example of mirroring is a two-party coaching dyad (you, the coach, the scale), but his own solo-vs-collective distinction makes the collective the hard case. How a leader practically moves a whole team or organization from mirrors to mirroring — how many people 'draw the map side by side' at once — is not addressed.
  TBM 426: The Trouble With Mirrors — read next: Read facilitation and large-group-intervention literature (Open Space, liberating structures) and Peter Block's Community for community-scale practices that operationalize joint meaning-making beyond the dyad.
• incompleteThe entire taxonomy is conditioned on the stipulated premise that experienced people already share common knowledge the strategy is fake -- but real organizations often feature leaders who are themselves genuinely uncertain, divided, or self-deceived about their strategy's coherence. The piece never revisits or relaxes this stipulation, so it says nothing about the (plausibly more common) case where the incoherence is not common knowledge at all, only suspected.
  TBM 433: The Border Collie Faustian Bargain — read next: extract-tbm-426-trouble-with-mirrors' argument that organizational truth is multi-party and negotiated (not simply known-but-hidden) supplies the more general case this piece brackets away by assumption.
• incompleteThe claim that visible behavior badly undercounts true belief-diversity rests almost entirely on one personal anecdote (the conference-vs-work contrast) plus a plausible-sounding three-layer decomposition — no survey data, case study, or reference to the adjacent, already-named social-science literature on exactly this phenomenon (pluralistic ignorance, preference falsification, spiral of silence, Asch-style conformity) is cited to establish that the adaptation/belief gap is large rather than modest.
  TBM 438: Am I the Only Weirdo in This Company? — read next: Timur Kuran, Private Truths, Public Lies; the pluralistic-ignorance literature in social psychology; Elisabeth Noelle-Neumann's spiral of silence.
• incompleteCutler concedes at the outset that typologies 'became fodder for some fun discussions and had that occasional wow, how right! horoscope vibe,' but never weighs this genuine value (shared vocabulary for self-reflection, low-stakes team bonding, an entry point into talking about difference at all) against the costs he documents. The piece critiques typologies' insufficiency for the hard work of teamwork without arguing they are net-harmful, leaving open whether a more modest, supplementary use of typing survives the critique.
  TBM 440: The Problem With Putting People in Boxes — read next: None in this corpus yet directly weighs the self-reflection/vocabulary value of typologies against their organizational misuse — a genuine open question for a future read on personality-assessment validity research.
• incompleteThe three academic traditions cited (institutionalization: Berger, Luckmann, Zucker; organizational culture: Schein, Martin; social dominance: Sidanius, Pratto) are named but not engaged with — no specific finding, mechanism, or quotation from any of them appears in the piece. They function as authority gestures that lend the argument credibility rather than as evidence a reader could verify or follow up on directly from this text.
  TBM 440: The Problem With Putting People in Boxes — read next: Read Berger & Luckmann's 'The Social Construction of Reality' and Sidanius & Pratto's social dominance theory directly to check how closely Cutler's depersonalization-of-norms argument tracks their actual claims versus using them as a plausibility gesture.
• uninformedThe claim that underrepresented people bear a disproportionate adaptation burden is asserted as established via named literature (social dominance theory) but no data, case study, or even a paraphrased finding is offered within this piece to substantiate the specific magnitude or mechanism of that burden in a workplace setting — it is plausible and consistent with the field, but not evidenced here.
  TBM 440: The Problem With Putting People in Boxes — read next: Empirical organizational-behavior research on code-switching, executive-presence coaching, and promotion-rate disparities by demographic group, to see what evidence actually exists behind the claim as applied to workplaces specifically (versus the broader social-dominance literature Cutler gestures at).
• incompleteSelection and survivorship bias in the evidence: all three cases are famous winners who eventually lost, so the pattern is fitted to confirming instances. The essay never examines high performers whose harsh behavior was checked WHILE they were still winning, or abusers who failed early and were never prosecuted — so the claim that results are effectively the only variable is illustrated, not tested against disconfirming cases or base rates.
  When Nothing Happens — read next: Comparative and base-rate evidence on when abusive-but-successful leaders are and are not sanctioned; cases of accountability arriving during a winning streak.
• incompleteThe article never asks who actually absorbs the coordination, mentorship, code-review-depth, and on-call/incident work that a larger team used to distribute across more people — it treats headcount reduction as a clean efficiency gain (less time 'talking to each other') without examining whether that work still needs doing and now concentrates on fewer, more exposed individuals. This is exactly the team/org durability question a pod-based reorg raises once the novelty wears off.
  Your Work Team Is Now a 'Pod' and Your Co-Workers Are AI Agents — read next: extract-hbr-new-rules-enterprise-leader.json (p12: psychological safety and trust as the precondition without which small teams and human-AI hybrids don't actually work) and material on apprenticeship/mentorship pipelines inside very small teams.