Organizational Coherence
The contingent alignment among an organization's genuinely separate structures (goals, teaming, ownership, technology, incentives) that must be continually re-established as the organization changes — distinct from legibility (visibility) and organizational debt (accumulated liability); a property to measure and maintain rather than architect once.
Also known as: coherence, organizational coherence, spacetime crystal, spacetime crystals, coherence ceiling, business gardening, structural coherence, API coherence
How authors use it
Oldest first (extraction date when no publication date is known).
| Author | Their term | Their meaning |
|---|---|---|
| TBM 423: Why Defining Teams Is So Hard John Cutler · 2026-05-21 | Coherence (and misalignment) | The degree to which the product view and the technology org naturally line up. A spectrum, not a binary; most teams sit somewhere between high coherence and deep misalignment. |
| TBM 423: Why Defining Teams Is So Hard John Cutler from The Beautiful Mess · 2026-05-21 | coherence | The degree to which the product view and the technology org naturally align. Teams sit on a spectrum from high coherence to deep misalignment; achieving coherence is constrained by existing architecture, not just by intent. |
| Coherence, Connections, and… Spacetime Crystals Art Anthony · 2026-09-09 | Coherence | The property of an API estate and the organization above it holding consistent decisions about ownership, capabilities, standards, and business objectives, such that the structure does not fracture as the organization changes — distinct from, and prior to, individual API performance. |
| Coherence, Connections, and… Spacetime Crystals Art Anthony · 2026-09-09 | Spacetime crystal | A physics analogy (a phase of matter with a repeating pattern at regular time intervals, like a self-sustaining clock) used to describe an organizational/API structure whose underlying logic repeats/holds consistently across time (i.e., survives organizational change) rather than only across space (i.e., being internally tidy at a single moment). |
| Coherence, Connections, and… Spacetime Crystals Art Anthony · 2026-09-09 | Business gardening | The ongoing practice of tending an organization: continually mapping how goals connect to work, which long-lived products exist, and how they relate to each other — explicitly not a one-time exercise. |
| Coherence, Connections, and… Spacetime Crystals Art Anthony · 2026-09-09 | Coherence ceiling | The limit an incoherent higher-level organizational structure imposes on a lower-level, internally-coherent product or team — however coherent a single product is made, it cannot 'fix' the incoherence of the organizational goals above it. |
Documents (4)
- Beyond Autonomous Teams in Software Product Development Ben Linders · 2026-09-10 source ↗ Reader 🖥️
Because a team's contribution in a complex organization is really a share of an ever-shifting web of value dependencies rather than a discrete 'product,' organizations should replace 'autonomous product team' thinking with 'value center' thinking, in which every unit at every level (person, team, team-of-teams, org) answers the same five recursive questions and trades off autonomy against coherence according to the shape of the value it carries, not according to ideology. - Coherence, Connections, and… Spacetime Crystals Art Anthony · 2026-09-09 source ↗ Reader 🖥️
A technically well-performing API is close to worthless if it isn't coherent with the organization's goals, ownership, and structure — and because organizations and their APIs change constantly, that coherence has to be continuously mapped and re-established rather than achieved once and assumed to hold. - 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.
Propositions touching this concept (13)
By publication month, oldest first (extraction month when no publication date is known).
2026-05
- explicitChange agents should not try to close the gap personally; they should find pockets of coherence and work there.
- explicitGoogle may lack the organizational coherence to run both the consumer product track and the Hassabis frontier-science track simultaneously.
2026-08
- explicit⚡ disputed & corroboratedPerfect organizational coherence is not a desirable goal — it would require either stasis or an organization so tightly constrained that it could not adapt.
2026-09
- explicitThe shape of an organization's value (its web of dependencies) determines and constrains what organizational structures are possible, including the achievable trade-off between team autonomy and organizational coherence.
- explicitcontestedBecause today's environment contains substantially more disorder than order, managers should lean toward preferring coherence even though they are more comfortable dealing with order.
- explicitThe core problem behind API duplication, overlapping capabilities, competing standards, and unclear ownership is coherence, not performance.
- explicitA coherent API/organizational structure functions like a spacetime crystal: the API landscape (space) must absorb organizational change (time) without the underlying organizational logic fragmenting into disorder (sprawl).
- explicitMapping — determining why things are the way they are, how goals connect to work, and how products relate to each other — is a necessary first step before an organization can meaningfully improve coherence.
- explicitdevelopedAn individual product or set of APIs can be highly coherent internally while still being constrained by the 'coherence ceiling' imposed by incoherent organizational goals above it.
- explicitCoherence is not a one-time achievement: because organizations and APIs change constantly, maps and measurements of coherence must be continually updated ('business gardening'), not produced once and relied on later.
- explicitPerfect, 100% organizational coherence is unattainable; the realistic goal is understanding how much different parts of an organization make sense together, not eliminating change or difference.
- implicitCoherence should be evaluated holistically, treating an API as a long-lived 'product' nested within the wider organization, rather than assessed only through the API's own technical metrics.
- explicitAs AI agents become more autonomous consumers of APIs, human-oriented coherence needs do not disappear — coherence work is not purely an optimization for machine consumers, because humans still need to understand and navigate the same systems.
Open gaps (17)
- incompleteThe claim that the five questions apply unchanged 'at all levels: team, team-of-teams, department, whole organisation' is asserted but only ever demonstrated with a single team-level worked example (Scrum backlog, sprint goal); no worked example is given at the team-of-teams, department, or whole-organization level, so the universality/recursiveness claim is untested within the piece itself.
- incompleteRohrer's 'prefer coherence, because there's a lot more disorder than order' reads as an argument for maximizing coherence, but elsewhere in this reader's corpus the same coherence concept is explicitly qualified: perfect/maximal organizational coherence is not a desirable goal because it would require stasis or over-constraint. The piece doesn't engage this diminishing-returns or over-coupling risk of coherence-seeking.Beyond Autonomous Teams in Software Product Development — read next: extract-tbm-434-how-maps-can-hide-problems#p9 (perfect organizational coherence is undesirable — requires stasis) and extract-nordic-apis-coherence-spacetime-crystals#p10 (perfect coherence is unattainable; the realistic goal is understanding degree of fit, not maximizing)
- incompleteThe article asserts that AI systems 'reinforce' incoherence they ingest, and quotes Faull's SSRN claim that such failures are 'structural rather than algorithmic,' but provides no worked example of an AI-driven decision that was actually corrupted by upstream organizational incoherence — the mechanism is asserted, not demonstrated within this piece.Coherence, Connections, and… Spacetime Crystals — read next: Read Faull's underlying SSRN paper directly for the mechanism and evidence. This is the same gap already flagged in the corpus for a structurally identical claim by a different author — see extract-tbm-434-how-maps-can-hide-problems#g3.
- incompleteNo criterion or method is given for prioritizing which coherence gaps are 'consequential' enough to fix versus tolerable, despite the piece explicitly conceding perfect coherence is unattainable and undesirable — the actual triage decision is left unaddressed.Coherence, Connections, and… Spacetime Crystals — read next: Same open gap already in the corpus (extract-tbm-434-how-maps-can-hide-problems#g1); worth pairing with Meadows on leverage points for a prioritization heuristic.
- incompleteThe proposed measurement method (product tree: map an API's goals/jobs/work-items, then map organizational goals above it) is described only in the abstract as 'a first pass' — no worked example, metric, or threshold is given, and Faull's own open-source coherence-measurement framework is explicitly not yet released.Coherence, Connections, and… Spacetime Crystals — read next: Track the eventual release of Faull's open-source framework and his Nordic APIs Summit 2026 talk for the operationalized version of this method.
- incompleteThe article never discusses failure modes of the mapping/gardening practice itself — e.g. the coping-mechanisms-substitute-for-repair pattern already identified in the corpus, where organizations build translators, dashboards, or maps that make incoherence bearable without ever fixing it. Faull's proposed coherence dashboard/framework risks becoming exactly this kind of coping mechanism rather than a forcing function for repair.Coherence, Connections, and… Spacetime Crystals — read next: See extract-tbm-434-how-maps-can-hide-problems#p5 and #p6 for the coping-substitutes-for-repair pattern this document doesn't engage.
- 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.