Operating Systems & Operating-Model Design
13 tier-5 · 6 tier-4
Cutler's core project: treating "how the company works" as itself a product — an operating system built from the fewest consistent concepts that still let an org function, modeled as a mesh of meaning-carrying relationships rather than a containment cascade. Across these pieces he names the materials (context, intent, collaboration, investment; possibility/action/control), the design competencies and principles, the failure modes (zombie processes, mission drift, overloaded words, model-market-fit), and the political reality that OS design is a real skill leaders rarely own. This is the durable spine of TBM and the cluster with the heaviest tier-5 concentration.
TIER 5
2024-07-15
A comprehensive framework treating operations and enablement as two sides of the same coin, both viewed as internal products/platforms applied to 'the company as the product.' Cutler builds out the full model: operationalize-vs-leave-bespoke, functional/value/general domains, a capability-based unifying view with maturation stages (Exploration/Expansion/Excellence) and differentiator/basic/performance classification, plus a long list of governing principles (trust formula, safe-to-fail experiments, think-big-work-small). A landmark reference piece on org design and internal platform thinking.
operationsenablementcapabilitiesorg designproduct operating model
TIER 5
2024-08-08
Cutler argues multi-level goal cascades are usually just 'org-chart cascades' with no underlying causal model, leading to optics-driven box-checking where teams reverse-engineer goals from work already committed. He reframes goals around stable core metrics plus ephemeral bet metrics, noting that only front-line teams can actually action anything (everything above is a downstream lagging effect), so you really need only two levels of goals plus team-level models. A definitive statement of his persistent-models-over-cascades thesis and a high-value reference for goal-setting design.
goal cascadesOKRsmetricscore vs bet metricsstrategy
TIER 5
2024-09-08
Cutler explains why theoretically simple practices like OKRs become 'zombie processes' that everyone performs but no one believes in: at scale they get institutionalized, decoupled from reality, tied to performance reviews, and worked around, creating a growing chasm between the 'official' and 'real' worlds. He frames the cure as fighting Selznick's 'mission drift' (revisit original purpose, allow local adaptation, invite challenge) and reframes the issue from a training problem to one of feedback, incentives, and trust (via Dirksen's behavior-change factors). A durable, mechanism-rich account of how good practices rot.
OKRszombie processesmission driftinstitutionalizationbehavior change
TIER 5
2025-01-26
A 32-principle reference compendium for designing a company's product operating system, treating it as an internally-built product owned by senior leadership. Principles include consistent interfaces over consistent processes, enabling vs. limiting constraints, anchor documents, examples over templates, fight premature convergence, subtract first, scaffolding, and 'simple not simplistic.' Densely cross-linked to prior TBMs — a canonical, lasting reference for product-ops practitioners.
product-operating-systemdesign-principlesenabling-constraintsritualsorg-design
TIER 4
2025-02-04
Answers what skills a company needs to intentionally design a product operating system: leadership/influence, domain experience, systems thinking, and general operations/tooling. Walks through the failure mode when any one is missing (e.g., systems thinking without leadership yields brilliant designs no one follows) and observes that intentional companies usually had leaders who wrote things down and pushed back on cargo-cult practices. A clean competency framework for the product-ops function.
product-operationscompetenciessystems-thinkingleadershiporg-design
TIER 5
2025-03-04
Introduces an original five-block model of any 'operating system' — Possibility, Intent, Action, Context, and Control & Integration — woven as a mesh rather than a cascade, and shows how each block degrades under growth/scale. Adds a rich sub-framework on 'intent types' across four dimensions (short/long, procedural/outcome, concrete/abstract, linear/high-leverage) to replace the blunt strategy-planning-execution cascade. A foundational, reference-grade synthesis of how to design rituals, artifacts, and cycles.
operating-modelframeworksintentorg-designscaling
TIER 4
2025-03-18
Argues that PMs should pick a small set of slow-changing 'drivers' (a stable model / shared language) for their product area and repeat them relentlessly with stakeholders, rather than churning frameworks every quarter. The model itself is interchangeable and strategy-agnostic; its value is the durable vocabulary it gives partners to think outcome-oriented and long-term. Includes a worked example (integration team's five drivers) plus a self-coaching question set.
mental-modelsshared-languagestakeholder-managementproduct-strategylong-term-thinking
TIER 5
2025-03-23
Answers a reader's question about why leaders treat operating-system design as mere 'process' nobody owns, diagnosing it across many angles: the false process-vs-leadership binary that leaves OS design unnameable, OS design being a distinct skill great managers often lack, leaders having no time and 'process allergy,' general management not translating from local to global scale, doomed middle-out pushes, and chiefs of staff inventing operating systems in a day (the root of 'Zombie Process'). Offers seven concrete tips (intentional≠explicit, lead with relatable stories, anchor on behaviors, keep your own private doc, respect inertia). A standout, practical essay on the organizational politics of ways-of-working.
operating system designleadershipprocess allergychiefs of staffchange tactics
TIER 5
2025-04-11
A diagram-rich tour of why wrangling product work is so hard, walking from project DAGs vs. causal chains, through experimentation-driven bet graphs, to the 'wrong but useful' insights→opportunities→options→bets→work→release→impact flow, and contrasting a tidy top-down tree (Company A) with a fractal, mesh-like nested intent graph (Company B). Lands on minimally viable consistency, the irreplaceable richness of physical kanban boards over tools, and Scott's legibility-vs-Mētis tension, closing with eight pieces of advice (start with rituals, resist cascade thinking, product work isn't factory work). A landmark synthesis of how product operating systems actually behave.
operating modelgraphslegibilityroadmapsminimally viable consistency
TIER 4
2025-04-23
Proposes that an operating system can be boiled down to how intentionally a company creates conditions for the right conversations to happen with the right people at the right time, then layers three lenses: a (self-critiqued) conversation-maturity model, a scale dimension (local excellence vs. vertical/horizontal reach), and an implicit-vs-explicit formalization 9-box. Stresses 'minimally viable global consistency,' warns that high-autonomy ZIRP-era companies lacked any OS for org-wide coordination, and reframes bad conversations as often a system/trust issue, not a skills gap. Substantive multi-model analysis, still labeled V0.1.
conversationsmaturity modelsscaleformalizationoperating model
TIER 4
2025-06-06
Introduces a four-entity framework (Context = what is; Intent = what we want for the future; Collaboration = human structures; Investment = models for allocating time/capital/focus) to replace muddy distinctions like 'strategy vs. execution.' Argues orgs over-invest in a narrow slice of near-term Intent (this quarter's goals) while neglecting durable, 'sticky' context and investment/collaboration models, illustrated by 20 teams whose business cases summed to a physically impossible 500% metric gain. Useful as a vocabulary for diagnosing why teams feel like they're chasing their tails.
operating modelframeworksintent vs contextinvestmentNorth Star
TIER 4
2025-06-30
A video-with-outline critiquing the Pillars→Priorities→Initiatives→Epics→Tasks pyramid: it assumes one-way top-down flow, hides outcomes, ignores time-to-impact variability, pushes teams into execution roles, and misrepresents work. Cutler proposes work behaves like a fabric/network needing multiple lenses (outcome, work, finance, structure) and three artifact types (Anchor, Intent, Context) reinforced by rituals. The thinking is substantive and original even though the post is largely a bullet outline of the video.
value hierarchystrategy cascadeoperating modelartifactsoutcomes
TIER 5
2025-08-26
Introduces 'minimally viable consistency' (MVC): the fewest shared concepts, terms, and norms an operating system needs to function in its specific context — no more, no less. Cutler shows the viability tension (overloaded words like 'initiatives' lose meaning; launch-tiering schemes may not match internal reality) and argues people wrongly copy the surface simplicity of other companies' systems without the underlying forces that make it possible. An original, named framework with lasting reference value for designing company operating systems.
operating modelconsistencyshared languageframeworkstandardization
TIER 5
2025-11-23
Debunks the belief that accounting/governance standards require projects, programs, and false-precision cost reporting, project/program codes are governance constructs, not GAAP/IFRS requirements, and frameworks (OECD, ISO 38500, NIST) demand accountability and traceability, not project structures. Distinguishes procedural from substantive legitimacy and lays out twelve principle-based ways to govern durable products, platforms, and capabilities. A landmark, deeply argued reference on product/platform investment governance.
governanceproduct-operating-modelinvestmentcapitalizationplatform-funding
TIER 5
2025-12-07
Argues that company operating systems should be modeled as concept maps / lightweight ontologies where edges carry meaning, not as containment hierarchies (project -> deliverable -> story). Shows four different goal-initiative relationship models, contrasts containment vs. bet-based strategy-to-execution, sketches Amazon as a mechanism-rich network, and uses SAFe's scaling logic to demonstrate that most team practices are not scale-free once distance, politics, and translation enter. A durable, original mental-model piece with lasting reference value.
operating-modelsontologyorg-designscaling-agilegoal-cascades
TIER 5
2025-12-14
A deep essay on organizational semantics arguing that disagreement over words like 'initiative' or 'BAU' isn't always confusion: it can be levels of abstraction, harmless polysemy, or dangerous ontological conflict where incompatible definitions collide and drive real funding and layoff decisions (via Scott's legibility, Juarrero's enabling constraints, and DDD/event storming). It contrasts the pragmatic VP (hacking practice) with the Trojan Horse Expert (hacking models) and delivers seven actionable tactics: anchor on events, polymorphism, utilitarian definitions, fractal objects, name-the-exception, fractal artifacts/rituals, and design for many frames. A landmark, heavily-theorized reference piece on naming, reification, and meaning in sociotechnical systems.
semanticsontologyreificationdomain-driven designenabling constraints
TIER 5
2026-01-19
A five-act narrative of how organizations evolve from delivery-predictability and WIP-reduction, through tacked-on goals, to goals-first, to contested emerging value models, to converged value models where org chart, goals, architecture, and work align around value, explicitly framed as a non-linear stumbling-forward rather than a maturity model. It surfaces Dotwork's 'four graphs' (Intent, Context, Collaboration, Investment) and the cycle by which concepts get introduced, overburdened, bifurcated, and fade. A landmark synthesis of years of transformation thinking that names the dominant/competing mental models at each stage.
product operating modeltransformationvalue modelsorg designmental models
TIER 4
2026-03-04
A continuation essay on designing a company operating system with the fewest consistent concepts that still let you operate, introducing 'Model Market Fit' (you can't predict which framework will take hold) and warnings about strategic-vs-structure lag, the myth of the standard framework (OKRs vary wildly under one name), roll-up pyramids, and consistency-as-scaffold that should carry an expiration date. It closes with a sharp six-question test for whether a consistency requirement is worth imposing. Useful org-design craft, though it explicitly leans on its Part 1 for the core model.
operating modelconsistencyOKRsorg designframeworks
TIER 5
2026-05-09
Extends the Minimally Viable Consistency series with a three-strategy framework, sharp consistency (opinionated uniformity), flexible consistency (shared intent, local form), and legible variety (a consistent way to describe difference), each mapped to a CS analogy (strict schema, interface/protocol, tagged union). It then applies the model to where AI helps or harms (translation, concurrent frames, coaching) and the risk that removing translation friction also removes sensemaking. A precise, original org-design framework.
org designconsistencystandardizationAIframeworks
Prioritization, Capacity & Investment Allocation
10 tier-5 · 10 tier-4
The most practitioner-facing cluster, and the home of several of Cutler's signature reframes. Prioritization is not one job but four (efficiency, leverage, alignment, funding) and is supposed to be hard; time allocation is not capacity allocation; allocation percentages are an output of strategy, not its driver; and the dream of clean roll-ups, story points, and time tracking borrows the authority of accounting without being accounting. Running through it all: protect capacity, learn cheaply, treat confidence as costly, and obsess over the return side of ROI rather than the investment side.
TIER 4
2024-03-08
Cutler offers a mental model of team effectiveness as a distribution of time/energy across leverage (ROI) levels, showing how two teams with superficially similar distributions can differ hugely—one with 5x the high-leverage work and far less negative-ROI drag. The point is that many small disadvantages (worse data, more tech debt, extra dependencies, lower psychological safety, premature convergence) compound into outsized gaps via virtuous vs wicked loops, which is why productivity/efficiency debates miss the mark. A clean, portable model on marginal gains and compounding effects.
leverage/ROIteam effectivenessmarginal gainsreinforcing loopsmental models
TIER 4
2024-05-02
Cutler diagnoses a common anti-pattern: leadership sets a few equally-weighted, non-comparable priority pillars (revenue vs satisfaction vs cost), leaving shared/enabling teams stuck arbitrating apples-to-oranges demands. He lays out a clear taxonomy of survival strategies for shared teams (Ruinous Pragmatism, Go Rogue, Cage Match, Partnership & Global Priorities) with pros/cons, arguing Partnership is ideal but Cage Match is the realistic move in a defensive layoff climate where you must protect capacity and preserve flow. A practical, well-framed model for anyone running a dependency-serving team.
prioritizationshared teamsdependenciescapacity allocationorg design
TIER 5
2024-05-30
Introduces the 'failure threshold': a point where the share of cross-team/cross-codebase work grows past which the coordination problem becomes mathematically (not skill-wise) unsolvable by brute-force planning and Tetris. Argues teams must switch from static optimization to heuristic-based dynamic optimization (WIP limits, force-ranking, weighted-shortest-job-first), and explains why managers resist because 'doing less' feels like cheating. An original, durable mental model linking architecture/dependencies to the limits of planning.
dependenciesWIP limitsheuristicscomplexityprioritization
TIER 4
2024-07-18
Cutler reverses his long-held view that strategy should be expressed as % allocations across investment buckets, arguing allocations are an output of priorities/strategy/risk-heuristics, not the driver. He pairs this with a five-bucket value/urgency model (mission-critical, dilemma, optimizers, future seeds, slack-mop-up) each with its own work-style heuristic, showing how two companies' resulting allocations diverge from the same prioritization logic. Useful reframe for anyone treating allocation spreadsheets as the controlling mechanism of strategy.
prioritizationcapacity allocationstrategymental modelsvalue/urgency
TIER 4
2024-11-20
Cutler introduces 'work shape mix' — distinguishing large complex cross-team projects, independent product work, and zero-to-one efforts (each with different funding, ROI, and risk profiles) — and traces how the mix shifts as companies scale, with critical 'fire' inflection points where leaders must choose between formalizing a new reality or tolerating friction. The durable takeaway is to deliberately name 3-5 real work shapes in your org to get an honest view of dynamics and spot the narrow window before drift hardens into a heavy transformation.
org designwork typesfunding modelsscalingoperating model
TIER 5
2025-01-19
Argues that reducing team capacity to engineers x hours is a dangerous illusion; using a layered factory analogy, it shows current capacity is the cumulative output of investments in people, teams, structure, codebase, tools, trust, and culture — much of it intangible. The real risk is failing to invest in future capacity while obsessing over time-allocation reports, and teams fret over 20% vs 30% refactoring while suffering 40-70% drag. A landmark reframe of how to answer 'where did our salaries go?'
capacitycapital-allocationtime-trackingtechnical-debtmetrics
TIER 4
2025-01-22
Replaces spreadsheet/ticket/percent-allocation dependency haggling with a lightweight model: each team gets three focus slots (primary >50% bandwidth, secondary, ad hoc), and Team Topologies interaction modes (Collaboration, Facilitating, X-as-a-Service) drive heuristics for which slot a dependency consumes. Argues the collaboration pattern matters far more than fine-grained estimates, and conservative focus plus pebble-filling beats peanut-spreading. A practical, original coordination mechanism.
dependenciesteam-topologiesWIP-limitscapacity-allocationcoordination
TIER 4
2025-02-16
A focused practitioner playbook for a platform team drowning under ad hoc requests while losing ground on its roadmap. Ten concrete tips — keep the platform promise front and center, stop optimizing for being underwater, go big on enabling constraints, keep transparent queues and receipts, work tiny slices, get both manager groups in a room — frame the situation as 'fixing the train while it barrels down the tracks.' High practical value for the specific platform-team turnaround scenario.
platform-teamsenabling-constraintsprioritizationWIP-limitsteam-turnaround
TIER 5
2025-04-15
Cutler's signature insight that 'prioritization' jams together four distinct jobs — Efficiency (reduce WIP/context-switching), Leverage & effectiveness (right mix of bets), Alignment & autonomy (shared context for local decisions), and Support/funding/commitment (structural backing) — and that conflating them is why prioritization talks deadlock. Shows worked examples (a struggling platform team, above/below-the-line games) and argues there's no single correct sequence — clearing the pipes can itself be the strategy. A foundational, frequently-cited framework that names what was previously implicit.
prioritizationWIPleveragefundingdecision rights
TIER 5
2025-04-20
A deep 'context safari' arguing that growing companies can't fund and plan every team the same way, building a rich toolkit: four funding archetypes (Company-In-A-Company, Service Team, Blurry Team, Adhoc Project), team-stage models tied to hill-climbing, effort-value curves and work shapes, and the product-is-the-product vs. tech-enables-the-product distinction. Catalogs anti-patterns (one-size-fits-all, pure ad hoc, false precision, and the most damaging — having no theory of investment/value for a team at all) and lays out a four-step path to a legible-but-not-mono-process model. A landmark reference essay on funding and planning in context.
fundingplanningteam topologiesinvestment theorywork shapes
TIER 4
2025-08-03
Via a thought experiment (no one complains about dependencies on a company-saving initiative), Cutler argues dependencies aren't the real problem — the lack of shared priorities and incentives to overcommit are. Elaborate dependency-tracking systems become scheduling Tetris that turns cells green without ever calculating the value gap between competing priorities; the fix is to shift from 'managing dependencies' to maximizing value throughput. A sharp reframe of a common org pain, lightly undercut by product-pitch framing.
dependenciesprioritizationplatform teamscapacity allocationvalue throughput
TIER 5
2025-08-24
Defines urgency as 'the degree to which a delay reduces the long-term value of a decision or action' and distinguishes regrettable/reactive urgency from proactive urgency, arguing that timing and tempo control are central to strategy yet absent from popular prioritization frameworks (RICE, ICE, MoSCoW, Kano, WSJF). The key reframe: weaving time-and-value decay into prioritization conversations shifts them from value-haggling toward genuine strategy. A landmark conceptual contribution that exposes a real gap in the prioritization canon.
strategyurgencyprioritization frameworkstimingcost of delay
TIER 5
2025-09-05
Cutler draws a hard conceptual distinction: time allocation is just where hours went, while capacity allocation is a systemic property shaped by past investments, tooling, codebase health, rework, dependencies, and team composition. He argues companies waste money and do real damage by treating salary-hour tracking as capacity, and that the only fix is to decouple the two terms so honest conversations about impact and efficiency can begin. A durable mental-model piece grounded in lean/theory-of-constraints with a useful 14-category taxonomy of where time actually goes.
capacity allocationleaninvestmentmetricsmental-model
TIER 4
2025-09-12
Cutler argues that selling enabling constraints (WIP limits, force-ranked prioritization, single roadmap) is rarely a logic problem and almost always a psychology problem rooted in loss aversion, optimism bias, comfort with abstraction, and threats to autonomy. He offers a practical, audience-segmented playbook for pitching constraints differently to concrete thinkers, abstract thinkers, autonomy-driven leaders, veterans, and 'why-not-both' maximizers. Useful because it reframes a recurring PM frustration as a persuasion-and-personality challenge with concrete tactics.
constraintspersuasionWIP limitsdecision-makingprioritization
TIER 4
2025-09-30
Argues prioritization is supposed to be hard, and reframes it as the interplay of three frames: prioritizing ambitions/strategy (#1), allocating fixed capacity for maximum leverage (#2), and deciding net-new investment to shift capacity (#3). Maps the anti-patterns produced by over-focusing on any one or two, and contends the productive tension between ambition, capital, and capacity is the game, which frameworks and quick fixes wrongly try to replace. A sharp, useful prioritization model.
prioritizationcapacity-allocationinvestmentanti-patternstension
TIER 5
2025-10-21
Builds a layered chain from business basics to prioritization: four benefit types (increase/protect revenue, decrease/protect costs), their drivers, downward pressure and decay, leverage, Helmer's 7 Powers and the lifecycle of advantage (discover, grow, extract, resist erosion), then shows how real prioritization flows from this strategic foundation rather than vague-or-numeric 'value.' A comprehensive, original synthesis tying strategy directly to prioritization.
prioritizationstrategy7-powersleverage-and-decayWardley-mapping
TIER 4
2026-01-01
A catalog of ten named prioritization anti-patterns (Burning Down the House, Too Much Time on My Hands, Everybody Wants to Rule the World, Just Enough Is Never Enough, Running on Empty, Dreamer, Slow Ride, Someday Never Comes, The Logical Song, Takin' Care of Business), each with a representative quote and a concrete 'Do This Now' action. The throughline is doing 'good enough' marginally better decisions and protecting capacity, learning cheaply, and treating confidence as costly. A useful, actionable diagnostic checklist rather than an original framework.
prioritizationanti-patternscapacity allocationcost of delaydiagnostics
TIER 5
2026-01-09
Cutler imports liquidity and fungibility from finance to explain why Strategic Portfolio Management feels awkward in software: software products are low-fungibility, low-liquidity socio-technical systems where stopping work rarely frees capacity cleanly, so the portfolio metaphor overstates how easily bets can be rebalanced. He traces SPM's two lineages (centralized IT and consumer-goods brands), shows where Lean Portfolio Management moves fungibility from people to flow but flow isn't liquid either, and concludes that in product-centric firms portfolio management IS leadership, expressed through org design rather than a separate buffer layer. An original, high-leverage reframe with a strong question set.
portfolio managementliquidity and fungibilityproduct-centricityorg designstrategy
TIER 5
2026-01-27
A Socratic executive-dialogue essay dismantling the dream of clean work roll-ups, story points, and time tracking, arguing they borrow the authority of accounting without being accounting and that enforcing roll-ups makes teams invent work just to have something to roll up to. Cutler distinguishes time allocation from emergent capacity (via Stafford Beer's requisite variety and Hubbard's How to Measure Anything) and reframes the fix as obsessing over the return side of ROI and system-health signals rather than the investment side. A landmark, frequently-referenced argument against faux-accounting in product measurement.
roll-upsstory pointstime trackingmeasurementcapacity
TIER 5
2026-02-16
An original framework distinguishing three modes of doing many things at once: strategic juggling (intentional optionality with pruning), lazy juggling (undisciplined drift), and survival juggling (forced, back-against-the-wall triage), plus the parallel strategic/lazy/survival focus modes for a 2x3, and the virtuous/vicious loops that move teams between them. The key insight is that the strategic-vs-lazy border is often subjective and hinges on an unknowable assumption, so teams rationalize drift as optionality. A durable, reusable mental model for diagnosing focus and portfolio discipline.
strategyoptionalityfocusprioritizationmental model
Org Design, Team Topology & Coupling
7 tier-5 · 11 tier-4
How structure actually forms and why it hurts. Cutler treats org design as the deepest expression of leadership — naming what a "team" is, sizing a team-of-teams by who can still challenge its own assumptions, diagnosing why orgs grow too tall, and classifying teams by their distance from impact and their funding archetype. The recurring move is to expose the political and historical forces ("Game of Thrones," "It Just Happened," implicit bureaucracy) behind structures that present themselves as rational, and to design for when things go wrong rather than for the happy path.
TIER 4
2024-04-28
A podcast with Hazel Weakly reframing software work as collective learning rather than individual force-multiplication, with the key insight that a change agent's presence (not their outputs) is the real multiplier, so the goal is building systems where local decisions are globally coherent. Rich on migrations-as-migratory-pattern, the 'done / done-done / done-done-done' levels of doneness (Stripe's TS migration), architecture as a catalyst for coherent autonomy, and why leaders with multi-year feedback loops must deliberately introspect rather than wait for outcomes. Strong durable craft material on developer thriving and emergence.
collective learningmigrationsdeveloper productivityarchitectureleadership feedback loops
TIER 5
2024-05-12
A deep podcast conversation with Gene Kim built around his 'Wiring the Winning Organization' framing: the couch metaphor for coherence and coupling, 'independence of action' as something worth paying a lot for (analogized to option value), and 'Layer 3 wiring' as the organizational design that lets functional specialties integrate without crippling coordination. The standout argument is that the same problem-solving applies orthogonally to product, process, and organization/architecture, illustrated with rich case studies (Walmart, Amazon Prime Video monolith, Adidas platforms, SAP role-engineering teardown). High reference value for org-design and sociotechnical thinking.
sociotechnical systemsGene Kimcoupling/coherenceDevOpsplatform teams
TIER 4
2024-05-14
Using an Indeed layoff quote as a springboard, Cutler argues that org bloat (layers, duplicate teams, dependencies) is a predictable 'organizational physics' of rapid growth, and that the harder question is how to sense and respond to incoherence early instead of over-correcting via violent pendulum swings. He proposes the Lean Gemba Walk and the Toyota 'Shusa'/Chief Engineer role as undervalued mechanisms for leaders to see frontline reality, while acknowledging Silicon Valley's empowered-team model resists collectivist responses. It matters because it reframes layoffs as a failure to act on early signals and challenges the assumption that empowered/independent teams are universally optimal.
org designlayoffslean/gembapendulum swingsempowered teams
TIER 5
2024-09-01
Cutler asks why software orgs, despite their freedom, are worse than manufacturing at blameless problem-solving and challenging system assumptions, attributing it to software's high contextuality, low visibility (no physical gemba), murky cause-and-effect, mythologized hero-team independence, and immaturity as a discipline. He proposes the 'Boundary of Safely Challenged Assumptions': size a team-of-teams (roughly 30-50, not 150) by the largest group that can still challenge its own assumptions under bad conditions, not ideal ones. A landmark org-design principle that designs structure for when things go wrong.
org designmission commandteam of teamsblameless retrossoftware vs manufacturing
TIER 5
2024-10-31
A comprehensive diagnostic of why organizations accumulate excessive management layers, organized around two root causes (the team got too big, or it struggled to get 'wider' via spans of control) and then an exhaustive catalog of contributing factors: manager experience, board optics, WIP, reactive interrupts, frequent reprioritization, turnover, role ambiguity, layer buffering, departmental symmetry, remote/hybrid habits, and trust/delegation culture. The argument that flattening efforts fail when leaders fixate on a narrow set of causes makes this a durable reference for anyone diagnosing org height.
org designspans of controlmanagement layersflatteningorg structure
TIER 4
2024-11-03
Notes from an internal talk on dampening the harsh organizational pendulum swings between team independence and centralized coordination, arguing the balance point constantly shifts with macro conditions and that inertia makes swings violent unless counteracted. Cutler frames the 'adaptive capability to monitor and respond' as a legitimate, buildable competence — via scaffolding with expiration dates, normalizing restructuring, aligning incentives to adaptability, and genuine sensemaking — a substantive org-design argument against premature convergence and the illusions of independence and necessity.
org designinertiaaligned autonomyadaptive capabilityscaffolding
TIER 4
2024-12-06
Cutler contrasts rapid-growth adhocracies with enterprise bureaucracies and surfaces a durable insight: in the quest for 'minimal bureaucracy,' fast-growth companies accumulate implicit bureaucracy — unspoken constraints offloaded onto integrative glue/platform roles to preserve a facade of team independence — which leaders then attack via whack-a-mole until collapse forces drastic measures. Using Westrum's typologies, he distinguishes the Silicon Valley scaling challenge from the enterprise 'de-scale the train' transformation, with practical takeaways on scaffolding and lightweight working agreements.
org designbureaucracyadhocracyglue rolestransformation
TIER 4
2025-01-14
Proposes three graph models — path/linear, directed acyclic (DAG), and network — as lenses for understanding how a sociotechnical organization actually operates, and argues all companies run on overlapping mixes of the three. Uses a 2022-to-2025 scale-up example to show why Lean ideas land differently depending on where the 'weight' of the problem sits, and why rapid-growth firms resist portfolio Kanban even when it would help. An original conceptual framework for contextualizing Lean and org models.
leangraph-theoryorg-modelssystems-thinkingdependencies
TIER 5
2025-02-02
Uses the Garbage Can model (Cohen, March, Olsen) plus a pirate-ship contrast to explain why organizational conflict festers: business systems leave just enough room to avoid both the conflict and the discomfort of resolving it, with costs diffused as inefficiency and turnover. Argues 'wartime' efficiency drives often create the very conditions that prevent conflict resolution. A theory-grounded, durable explanation of organizational dysfunction with a strong review-question set.
garbage-can-modelconflict-resolutionorganizational-theoryculturedecision-making
TIER 4
2025-02-13
Presents a six-archetype taxonomy of teams (close-to-impact, everything-and-nothing, focused-multiple-hops, journey team, startup-mode, spreadsheet/project-factory) and maps each onto three axes: close vs. far from impact, independent vs. dependent, stable vs. temporary. Uses the taxonomy to explain why funding/ROI conversations break down and how enterprises adopting the product operating model strand teams two hops from revenue. A useful org-design and capital-allocation classifier.
team-topologyfundingROIproduct-operating-modeldependencies
TIER 4
2025-06-27
Three composite team self-descriptions — Aligned/Outcome-Driven, Parallel-Tracks/Local-Progress, and Strategically-Unsettled/Dependency-Tangled — illustrate how a team's mode is instantly legible from how members describe their work. Cutler unpacks how each feels (flow, pushing-rocks-uphill, navigating fog), notes that culture can lock a team into a mode, that Team 2 is sometimes correct, and that the same surface 'vibe' can have very different causes. A useful, vivid diagnostic vocabulary for team states delivered without stigma.
team dynamicsteam modesdiagnosisoutcomesdependencies
TIER 4
2025-07-12
Names a recurring organizational cycle: execs demand a simplified 'big picture,' teams over-filter, doubt builds, a P0 list emerges, reality is hidden until a ball drops, blame is exchanged, the view is repackaged, and it all repeats. Cutler connects this to personal productivity loops (only broken by an accountability coach) and lays out three responses — idealized discipline, lightweight enabling constraints, and the reactive spiral — recommending a mix of high discipline plus well-designed constraints. A perceptive how-it-actually-works essay on visibility, accountability, and intentionality.
visibilityaccountabilityoperating modelenabling constraintsleadership
TIER 4
2025-09-02
A nine-pattern typology of how companies actually arrive at their org design — Game of Thrones, Buzzwords 'n' Decks, It Just Happened, Roller Coasters, Re-orgs as BAU, Founder Centric, Founder Philosopher, Disciplined Steady Hand, and Thoughtful Transformation — each rendered as a composite leader quote with survive/thrive/hack moves. A genuinely useful diagnostic vocabulary for naming the political and historical forces behind org structure, though it's more catalog than deep argument.
org designtypologycompany patternsfoundersre-orgs
TIER 4
2025-09-19
Shares a 2x2 of vertical vs. horizontal org coupling (Federated Islands, Hands-Off Gridlock, Locked Grid, Command Towers) and works through why perspectives differ across levels, why 'at what cost' matters more than coupling level itself, and the ZIRP-era drift cycle between quadrants. Ties in cohesion/coupling trade-offs and argues no box is universally bad given inertia and direction. A useful org-design model, lighter and more exploratory than a landmark piece.
org-designcouplingdependenciesteam-topology2x2
TIER 5
2025-10-08
Explains why 'projects to products' and product-operating-model slogans fall flat in large non-digital-product enterprises, building from proximity/feedback loops and confidence horizons through the define-build-run legacy, agile's failure to change funding, the project-to-product 'translation layer,' and flow's local maximum. Argues the real opportunity is embracing a networked, multi-lens, multi-motion operating model rather than simplifying. A durable, distinctive analysis of product transformation in complex orgs.
product-centricityproduct-operating-modelfeedback-loopsfunding-teamsenterprise-complexity
TIER 4
2026-03-27
Argues organizational overload has been so normalized that people ground their professional identity in juggling noise and even defend the chaos as the engine of innovation, with AI amplifying the pattern while feeling like it tames it. Cutler draws on Simon ('a wealth of information creates a poverty of attention'), Argyris's defensive routines, and Byung-Chul Han's self-exploiting achievement subject to argue that resisting context expansion is itself the work. A concise, sharp critique of AI-era overload.
overloadattentionAIidentityburnout
TIER 5
2026-05-16
Introduces a triad model of management motions, Exception-based, Presence-based, and Delegation-based, that form a virtuous loop together and produce predictable anti-patterns when any leg is missing. Cutler maps the triad onto Mintzberg's configurations and contrasts Mulally (presence as scaffolding for the other two), Chesky's founder mode (presence replacing them), and Jensen Huang (systems over involvement), then uses it to explain why AI-era orgs feel heavier. An original, highly reusable leadership framework.
leadershipmanagement by exceptiondelegationfounder modeMintzberg
TIER 5
2026-05-21
A deep org-design essay explaining why naming what a 'team' is stays hard not because of skill but because describing reality is an Argyris 'undiscussable' that threatens incentives and power. It maps the competing product/design/tech/collaboration frames, the asymmetric costs (product names cheaply, eng carries headcount, design absorbs incoherence), triad fractals breaking at the manager layer, and Brunsson's 'organized hypocrisy.' Landmark synthesis of team topology, Conway, DDD, and organizational politics.
team designorg structureConway's lawundiscussablesorganized hypocrisy
Legibility, Truth & Sensemaking in Organizations
5 tier-5 · 5 tier-4
Cutler's most theory-rich strand, anchored by James C. Scott's legibility-vs-metis distinction. The throughline: organizational "truth" is negotiated, never neutral, and the systems we build to surface it (sources of truth, roll-up views, dashboards, transparency drives) routinely capture little of what matters. Trust is the precondition for observing reality at all; compression always excludes and mirrors power; and the gap between the official process and how work really happens is the central object of study. These are the durable lenses behind much of the rest of TBM.
TIER 5
2024-06-27
Argues that in low-trust, dysfunctional environments you cannot engineer a metric or process that 'surfaces reality'—reality only emerges alongside efforts to rebuild trust, and pursuing crude objective metrics (like PRs) is itself a byproduct of distrust that makes things worse. Closes with the original 'Cutler Variation of Goodhart's Law': in high-trust environments a measure can remain good as a target because missing it is treated as signal, not failure. A landmark argument on metrics, trust, and observability.
trustmetricsGoodhart's lawpsychological safetydysfunction
TIER 4
2024-07-05
Uses Cutler's lapsed cycling-data discipline as analogy for how teams/orgs lose touch with their own decline and 'forget.' The actionable core is an engineering org's eight-year practice of tracking lead times by reference feature type plus colorful journal entries, giving a reference point to detect and explain when things that used to be easy got hard. Argues for lightweight longitudinal logging/time-capsules as a catalyst for sensemaking as people and context churn.
organizational memorylead timemetricsretrospectivessensemaking
TIER 5
2024-07-26
Cutler introduces a five-part model of organizational reality: A (the official process), B (how work really happens), C (the costly effort to translate B into A), D (an optics-driven idealization that everything is fine), and E (a well-meaning improvement direction). He warns companies vastly underestimate the translation burden (C), play 'D games' that deny team reality, and dangerously confuse D with E when reforming. A compact, original, highly reusable lens for diagnosing the gap between stated and actual ways of working.
mental modelsofficial vs realorganizational realityprocesstranslation burden
TIER 5
2025-03-30
Five mini-essays on how information moves (or doesn't) in orgs: Cascade Flattening (stop building five-level goal trees you never interact with), Volume/Filters/Interfaces (a four-scenario analysis showing structure beats volume, and the hierarchical telephone game is a distortion engine while Amazon-style WBRs work via shared interfaces and rituals), No View To Rule Them All (views must be coupled to a task, like air-traffic-control displays), The Seduction of Loops (real loops spin at different speeds and aren't neatly nested), and Model Traps (compression always excludes, mirroring power dynamics; Team Topologies invites depth, MoSCoW flattens it). A dense, reference-grade treatment of legibility and information flow at scale.
information flowlegibilitygoal cascadesweekly business reviewmodel compression
TIER 4
2025-07-27
Argues that 'source of truth' problems are rarely about data modeling and mostly about whether people actually want the truth, can agree on what truth they seek, and will do the work to forge coherence across versions. Using a richly detailed example of initiatives/releases/launches/epics relationships, Cutler shows that fully modeling product complexity yields 20-30 entities no one will maintain, and that companies squash reality for reasons ranging from inexperience to dependency pressure to narrative-of-control. A thoughtful piece on the politics of data and operational complexity.
source of truthdata modelingoperational complexitytoolingorganizational politics
TIER 5
2026-02-07
A reflective essay using James C. Scott's legibility-vs-metis distinction to explain why 'systems of record' and roll-up tools capture little real truth, and why AI intensifies the polarity to 11: it can either expand shared metis across larger groups (the humanist hope) or supercharge top-down legibility and control (the techno-authoritarian fear). Cutler names the tension explicitly, citing research that AI increased collaboration and made expertise more valuable, alongside the darker centralizing strands in tech. Durable for its conceptual frame and its honest both-optimistic-and-pessimistic stance on AI's organizational effects.
legibilitymetisAIcontrolsensemaking
TIER 5
2026-02-13
Cutler challenges the AI-era assumption that context is a transferable package that can be pooled and synthesized for clarity and control, arguing instead (via Shannon-Weaver vs. 4E cognition) that context is produced through interaction, not transmitted. The landmark reframe: 'context engineering is interaction design,' and therefore leaders are interaction designers who refine intent through dialogue, backbriefs, and scenario exploration rather than broadcasting. It matters because it cuts against the dominant context-firehose narrative with a grounded theory of how shared understanding actually forms.
AIcontext engineeringinteraction designcommander's intentsensemaking
TIER 4
2026-03-17
Documents the observed pattern of high-performing teams using freeform, frequently-migrated 'messy docs' (ad hoc tags, links everywhere, strikethroughs, copy-forward snapshots) as a shared scratchpad that externalizes working memory and resists the 'simplicity fetish.' Cutler considers survivorship bias and resolves the messy-reality vs. organizational-legibility tension with three views, settling on designing 'intentional interfaces' rather than crushing the emergence. A practical, well-grounded product-craft essay.
product workdocumentationlegibilitysensemakingteam practices
TIER 4
2026-04-04
Draws a sharp conceptual distinction between legibility (what can be seen/controlled, never neutral per James C. Scott) and legitimacy (whether that control is accepted as justified), then critiques Jack Dorsey's 'Hierarchy vs. Intelligence' for repackaging AI-driven control as freedom while skipping the question of who holds power. Contrasts Haier's value philosophy with Dorsey's efficiency optimizations. A pointed conceptual essay on AI, power, and org flattening.
legibilitylegitimacypowerAIorg flattening
TIER 4
2026-06-16
Cutler distinguishes 'mirrors' (showing teams the objective truth of how they work) from 'mirroring' (helping people feel seen and heard), arguing the transparency-will-fix-it belief is positional, naive, and ignores that organizational truth is negotiated, weaponizable, and frame-dependent. Drawing on Nagel, Rao's Gervais Principle, and Peter Block, he reframes the goal from surfacing reality to drawing the map side by side. A thoughtful reflective essay on why organizational honesty so often fails to land.
organizational truthtransparencypsychological safetychange agencymental models
Strategy
5 tier-5 · 5 tier-4
Cutler's strategy writing is relentlessly anti-cargo-cult. Strategy frameworks are interchangeable along four axes and feel that way for a reason; "we have no strategy" usually means a diagnosable failure in one of three pillars, or that strategy lives unwritten in someone's head, or that it's a negotiated narrative with winners and losers. He argues against romanticizing bold decisiveness (good strategy is often deliberately indecisive), and names the archetypes — maximizers vs. focusers — whose dispositional clash drives most strategy conflict.
TIER 4
2024-02-25
Cutler and Tom Kerwin make the usually-vague 'soft skills' of leading in complexity explicit by enumerating ~20 named capabilities (e.g. Patient Divergence, Coherence vs. Alignment, Both/And, Plant Seeds, Power of the Present), each with an 'ability to...' definition and a sample interview question. The frame draws on complexity/Cynefin thinking, treating these as properties of groups-in-context rather than individual traits. It matters as a reusable diagnostic and hiring vocabulary for the otherwise illegible craft of navigating ambiguity.
leadershipcomplexitysoft-skillshiringmental-models
TIER 5
2024-03-01
Cutler reframes the perennial 'why doesn't my company have a real strategy?' complaint with eight provocative explanations: companies don't have strategies, individuals do; what's communicated is a negotiated narrative; strategy itself is a negotiation with winners and losers; the neutral 6/10 option often suffices; real strategy lives unwritten in intuitive strategists' heads; the big bet may already be in motion; famous strategies are often post-hoc rationalizations of emergent activity; and sometimes things work too well to inspire one. A landmark, frequently-referenced corrective to naive 'good strategy' worship, with a pragmatic close on advancing strategy through the decisions you must make.
strategyorganizational politicsemergent strategynegotiationdecision making
TIER 4
2024-04-04
Cutler argues most companies aren't competing with the celebrated 1% of product orgs, so obsessing over their public practices is a distraction; instead, ways of working are an underrated, buildable differentiator against your actual nearest competitors. Via a vignette of a leader who knew competitors deal-by-deal but nothing about how they work, he urges concrete competitive analysis of practices (discovery, shipping cadence, experimentation) and warns against handwavy 'be Agile' binaries and copy-pasted me-too metrics like NPS. A focused, actionable reframe on competitive advantage through capability.
ways of workingcompetitive analysisdifferentiationincremental improvementproduct capability
TIER 5
2024-10-13
Cutler names and dissects 'self-sealing arguments' — Catch-22 framings (you're defensive because you can't handle criticism; you lack high agency; you make things too complex) that cannot be refuted because any response confirms the premise, a common form of gaslighting and ideological entrapment. He maps the four instinctive losing responses (attack the frame, defend, outlast/game, acquiesce) and offers pre-trap moves (reframe to goals, ask curious questions, slow the conversation), making this a high-value, broadly transferable mental model for navigating power-laden arguments at work.
mental modelscommunicationgaslightingargumentationpower dynamics
TIER 4
2025-01-03
Challenges the romantic equation of strategy with bold decisiveness, arguing a sound strategy often means being deliberately indecisive — hedging, keeping optionality, and being 'reasonably OK at many things.' Distinguishes everyday decisiveness from inspiring strategy, warns that manufactured convergence can be as wrong as it is satisfying, and offers a front-line trade-off exercise for spotting the few areas that genuinely need a strategic POV. A substantive, anti-cargo-cult reframe of strategy.
strategydecisivenessoptionalityprioritizationfocus
TIER 5
2025-01-09
Offers a meta-framework: every strategy framework reduces to four things — which questions to answer and when, tools to answer them, a way to organize/visualize answers, and (sometimes) deployment guidance. Decomposes Zone to Win, Wardley Mapping, Rumelt's kernel, Gibson Biddle's acronyms, and more along these axes, showing why frameworks feel interchangeable yet suit different thinkers and contexts. Argues strategy is hard not because of frameworks but because of the messy human contexts in which they're applied. A durable, reference-grade synthesis.
strategymeta-frameworkwardley-mappingrumeltframeworks
TIER 5
2025-08-10
A diagnostic framework that splits 'we have no strategy' into three pillars — Information & Insights (situational awareness), The Game & Options (shared understanding of the game being played, including cynical real-world games like the Big Flip and Lock-In), and Now What? (commitment despite incomplete information) — each with strong/weak markers. Cutler's core insight is that strategic paralysis often stems from a logjam where no option is good, not from incompetence, and that you must diagnose which pillar is failing. A high-value, reusable diagnostic with lasting reference value.
strategydiagnosisframeworksensemakingdecision-making
TIER 5
2025-08-17
A long, talk-derived catalog of the observable behaviors of product-centric teams — weaving in context, delaying convergence, crisp problem framing, balancing output/outcome talk, returning to stable foundations, moving beyond Tetris, shipping, bidirectional strategy, seeking leverage, questioning priors, real customer-centricity, diverse bets, treating ways-of-working as product, and conviction held loosely. Valuable as a comprehensive, reflection-prompting reference for diagnosing and improving product culture through concrete behaviors rather than abstractions.
product cultureteam behaviorsoutcomesleverageproduct craft
TIER 4
2025-10-10
Names two archetypes that talk past each other: maximizers (speed, breadth, optionality, parallel bets, 'why not both?') and focusers (depth, coherence, constraints, doing less for more), arguing focusers can't counter maximizers with logic because the difference is dispositional, not skill. Layers in strategy to form four conflicting personas and argues healthy orgs keep all of them in tension rather than eliminating any. A useful, memorable mental model for strategy conflicts.
maximizers-vs-focusersarchetypesfocusstrategy-conflictdecision-styles
TIER 4
2026-04-15
Reframes 'what's the ROI of our engineering investment?' as a continuous habit of stewardship and thriftiness rather than a calculation you can cold-start, invoking the Lucas Critique to explain why feature-factory-era data won't carry into a fiscal-discipline regime. Cutler frames it as Bayesian updating (narrowing uncertainty quarter by quarter) and prescribes leading indicators, a business model, hiring discipline, and honest finance conversations. A strong, practical product/finance essay.
engineering ROIinvestmentLucas CritiqueBayesian updatingstewardship
Change Agency, Helping & Influence
3 tier-5 · 7 tier-4
The most personal cluster: a field guide to being an internal change agent or "systems over-thinker" without burning out. Cutler draws on Schein's paradox of helping, Peter Block's emergent model, and his own self-sabotage to argue sincerity isn't enough — change lands or fails on timing, framing, messenger, and the ego toll someone must pay. Recurring tools: the impulses and hats a helper can wear, the moves that preserve identity while shifting status, and the discipline of hacking power structures rather than fighting them.
TIER 5
2024-05-19
Extended commentary on Cutler's widely-shared 20-point list for systems thinkers / informal change agents: pace your delivery, don't show all your work, default problem descriptions feel threatening, do deep thinking with co-conspirators (not those you're influencing), informal influence goes unrecognized, hack power structures rather than fight them, and don't confuse seeing system dynamics with controlling them. A landmark, highly transferable field guide to operating as an internal influencer without burning out or over-identifying with change.
systems thinkinginfluencechange agentsmental modelsself-management
TIER 4
2025-02-21
Offers the 'ego toll' as an explanatory lens for why obvious, low-hanging improvements stay undone: someone must lose status, admit they were wrong, or surrender an identity-defining story. The corollary is that long-lingering 'easy' fixes are actually very hard, and change agents are not immune. Closes with five reframing moves (preserve identity, make it temporary, shift not remove status, make it about the team, tie to a bigger picture) — a memorable, reusable mental model.
change-managementorganizational-resistanceidentitystatusincentives
TIER 4
2025-02-26
A first-person cautionary tale: Cutler's systems-oriented 'skeptoptimist' framing of a problem as collective opportunity landed as personal blame to colleagues who attribute gaps to individual competency. The lesson — meet people where they are, always frame in collective terms, drop the helper identity, and recognize optimism mixed with pessimism is heard as pessimism — is a durable how-change-actually-lands piece with a concrete behavioral checklist for advocates.
change-agencyhelpingfeedbackpsychological-safetyself-awareness
TIER 4
2025-05-10
A catalog of ~16 mindsets people hold about organizational change and improvement, each captured in a first-person quote ('It's not that I don't want things to get better — I've just seen how this usually goes') with its strength and risk. Presented as a non-judgmental continuum rather than right/wrong, it's a self-diagnostic mirror for recognizing which stance you (and colleagues) default to. Valuable as a reflective taxonomy, though it's a list of archetypes rather than a tight causal model.
change mindsetsself-reflectionimprovementarchetypescontext
TIER 5
2025-05-16
Explains why Marty Cagan/SVPG's 'Transformed' succeeds at scale — it nudges change in an executive-friendly, identity-affirming way ('no one gets fired for recommending Transformed') by keeping the aspirational version clean so leaders stay the hero, deliberately omitting the political mess that would let people disengage. Cutler then extracts durable lessons for internal change agents (the messenger matters more than the message; surf timing and framing; transformation is structural constraint-smashing, not just a competency gap) and notes product management lacks any real theory of organizational change. A landmark, widely-shared piece on the social mechanics of change adoption.
change managementSVPGMarty Caganproduct operating modelconstraints
TIER 4
2025-06-14
Cutler contrasts two consulting paradigms — the dominant gap-diagnosis-expert-roadmap model (politically viable, low-risk, identity-affirming for execs) versus Peter Block's emergent, relational model where people realize they ARE the context and change grows from within. He names six-plus 'hats' a change agent can wear (pragmatist, purist, integrator, advocate, expert, etc.) and argues the real move is becoming conscious of which view you carry, closing with an unusually personal reflection on self-sabotage. Matters because it gives change agents a frame for the dissonance between believing in emergence while working in gap-thinking orgs.
consulting modelschange agencyPeter Blockcontextself-awareness
TIER 4
2025-09-28
Connects attractor states (systems revert to patterns unless something external changes) with the narrative fallacy and Plato's 'noble lie' to explain why companies pour money into narratively pleasing fixes (hire an expert, reduce WIP) and end up back where they started. Counsels complexity-aware thinkers to co-author a better narrative that fills the human need for an action-effect story, illustrated by a leader reframing 'predictability' for her boss and her team. A practical change-management piece.
change-managementnarrative-fallacyattractor-statescomplexityleadership
TIER 4
2026-04-26
Distinguishes outcome optimism ('we'll get there', protects momentum) from capability optimism ('we can figure this out', protects plan quality), arguing organizations structurally punish the latter while critical thinkers can hide behind 'just asking questions.' Using Norem's defensive pessimists, Hill's creative abrasion, and a climbing/base-camp metaphor, Cutler says teams should sequence the two modes explicitly rather than resolve them. A useful explainer on productive conflict and the politics of dissent.
optimismconflictcritical thinkingteam dynamicspsychological safety
TIER 5
2026-05-31
An original framework for change agents and helpers built on Four Impulses (way-driven, tension-absorbing, mission-driven, agency-building), each with its own gift, trap, and 'kryptonite' that triggers others, layered with identity and power dynamics. Cutler uses Schein's paradox of helping to argue sincerity is not enough and frames self-care as staying in the right relationship with one's own urge to help. A durable, reusable mental model for anyone doing improvement or facilitation work.
change agentshelpingself-carepower dynamicsidentity
TIER 4
2026-06-07
An argument that AI-adoption mandates strip employees of the very agency, trust, and dignity that genuine adoption requires, treating rational skepticism as a mindset failing. Using Bandura, Franklin/Illich (prescriptive vs. convivial tools), and Self-Determination Theory, Cutler shows how mandates damage autonomy, competence, and relatedness, then offers diagnostic questions for leaders. A pointed take on the cultural failure mode of corporate AI pushes.
AI adoptionagencyself-determination theoryleadershipmotivation
Goals, Metrics & Measurement
3 tier-5 · 7 tier-4
OKRs are just one interface onto the forever-hard problem of goal-setting, and most measurement pathologies come from treating product work like accounting. Cutler builds reusable taxonomies of goal types, exposes the goal-cascade as an org-chart in disguise, and repeatedly attacks measurement-led productivity narratives by arguing the real blocker is the cultural inability to talk about problems amid fear and blame.
TIER 4
2024-06-13
A diagnostic two-column inventory of where more product-mature teams spend more time and energy (direct customer contact, synthesizing research as a team, healthy debate, real shipping, removing features) versus less (estimating for timeboxes, triaging internal requests, dependency Tetris, premature specs, navigating proxies). Built on the premise that behaviors don't lie while labels like 'empowered' are squishy. A useful, concrete self-assessment checklist for product maturity.
product teamsmaturitytime allocationdiagnosticsdiscovery
TIER 4
2024-07-13
A sharp linguistic-reframe essay on the difference between labeling a person ('Lia is an underperformer') versus labeling performance-in-context ('Lia's performance here at Acme is...'). The context frame acknowledges both individual and environment while the person frame denies the environment exists, which managers resist because owning the environment is an ego threat. Short but a durable mental model for performance conversations and avoiding self-limiting boxes.
performance managementpeople managementframingcontextego
TIER 4
2024-08-01
Reacting to an Atlassian/DX study claiming developers lose a full day a week to inefficiencies, Cutler asks why, unlike roofers or Cirque performers, software teams tolerate this without mutiny, attributing it to invisible/async pain, expensive fixes, and acclimating to 'degraded mode.' He argues the real problem was never lack of awareness (people have long given this feedback) but the cultural inability to talk about it amid fear, blame, and apathy, so retros and better measurement alone won't fix it. A sharp, well-argued critique of measurement-led productivity narratives.
developer productivityinefficiencymetrics critiqueorganizational culturedeveloper experience
TIER 5
2024-09-15
Cutler distinguishes three model types for cross-functional product work, capability trees (enduring language), customer journeys (the lived experience), and flywheels/growth loops (the core growth hypothesis), and shows the strengths and blind spots of each. The 'functional model trap' is when each function (architect, designer, PM) is fluent only in one model and they don't link to a shared language, leaving the business to fall back on revenue and NPS. A landmark, reference-grade synthesis arguing teams should use all three models in ubiquitous, interlinked language.
mental modelscapability treescustomer journeysgrowth loopscross-functional alignment
TIER 5
2024-11-10
Cutler argues that vague product concepts (empowerment, data-driven, customer-focused) fail because teams can't translate them into observable behaviors, and lays out a full method to fix this: define the goal, articulate specific behaviors ('what would I see more/less of'), diagnose gaps with Julie Dirksen's COM-B model (Capability, Opportunity, Motivation), then prioritize Behavior Change Techniques. With a worked 'data-driven' example spanning behaviors, conditions, and interventions, it's a landmark, immediately applicable framework that reframes culture and improvement as behavior change rather than slogans.
behavior changeCOM-Bcultureoutcomesframeworks
TIER 4
2024-11-21
Ten practical principles for buying, adopting, and customizing roadmapping/goal/strategy-deployment tools, treating internal tools as products needing research, low-fi prototyping, and iteration rather than big-bang rollouts. Key heuristics — make tools work for you, question calls for consistency, distinguish 'scaling what works' from 'figuring out what works,' avoid oversimplified cascade models, bias to front-line needs, document-first as a test, and be willing to declare tool bankruptcy — make it a useful operating checklist against zombie process.
toolingprocessroadmappingadoptionconsistency
TIER 4
2024-11-27
A reference catalog of ~14 goal types — overarching/primary, target, anti-goals (NOKRs), continuous/progress, milestone, process, guardrail/counterbalancing, leading/lagging, maintenance, project, adaptive, exploratory/learning, decision-based, and capability-building — each defined with paired health and beekeeping examples. The thesis is that teams default to homogeneous target goals when mixing and matching goal types better fits the work, making this a durable, reusable goal-setting toolkit.
goalsOKRsmetricsgoal-settingframeworks
TIER 5
2025-12-18
Cutler presents a six-layer model for engaging a problem that is explicitly not a root-cause model: the customer's own words (Layer 1), other actors' perspectives (2), system forces/incentives/power (3), integrated 'real problem' plus why prior fixes failed (4), how your product could intersect those dynamics (5), and what you can realistically influence today (6). Each layer is grounded in named methods (Appreciative Inquiry, COM-B, Garbage Can Theory, Theory of Change, etc.). A reusable, reference-grade framework for problem framing that pairs directly with the later 'Dancing With Problems' essay.
problem definitionframingdiscoverysystems thinkingframework
TIER 4
2026-02-03
Answering a reader question, Cutler argues it's reasonable to know why each team exists, their value-chain fit, metrics, release calendars, and what shipped to production, but not to force a common work tracker; epics and initiatives can be largely throwaway if context is shared through goals, value models, and charters. He maps the wicked cycle where low trust drives more oversight and non-value-add consistency, and notes the exception: when 30-40%+ of work spans boundaries you're effectively one big team that benefits from temporary consistency. A practical, well-argued take on tooling consistency and the trust-scrutiny dynamic.
toolingtrackersconsistencytrustgovernance
TIER 4
2026-04-09
Argues you can't meaningfully discuss discovery, capacity, or 'good' without first understanding a team's demand mix (what fills the funnel and how it's shaped) and mandate levels, contrasting a disciplined 'efficient feature factory' with a dysfunctional 'empowered' org. The key claim: AI doesn't fix the funnel, it reveals and amplifies whichever version you already run, intensifying scarcity-negotiation or accelerating learning. A solid framework piece on intake, prioritization, and context.
demand mixdiscoveryprioritizationoperating modelsAI
Transformation & How Organizations Evolve
2 tier-5 · 4 tier-4
Why "product transformations" fail, and what they actually are. Cutler's consistent claim: transformation is not a finite project but a continuous-improvement muscle, structural constraint-smashing capped by architecture and the business model around 50-60% — "institutionalized incoherence" — and it fails when leaders treat it as a competency gap, copy-paste frameworks, devalue the present, or ignore dependencies. The cluster pairs his North Star metric for transformation with the definitive failure-mode catalog and the genealogy of how orgs stumble forward toward product-centricity.
TIER 4
2024-03-17
Cutler argues that resistance to product ways-of-working is usually not bad mindset or intent but simply a lack of firsthand experience, then catalogs twelve experiences (a flat launch, a team persevering past dead ends, strong PMF, organic adoption, a feature factory's slow collapse, quality increasing speed, healthy low-dependency teams, etc.) that make product concepts finally 'click.' The actionable implication is to stop trying to persuade people abstractly and instead invite them into the process for direct exposure, even to failures. A memorable, reusable lens on conviction and how product knowledge is actually acquired.
firsthand experienceproduct mindsetPMFbuy-inlearning by doing
TIER 5
2024-06-05
A definitive enumerated catalog of transformation failure modes: treating it as a finite project, devaluing the present, not letting the team lead, putting 'the best' on a pedestal, neglecting the continuous-improvement muscle, refusing to let go (subtractive change), losing sight of customers, copy/pasting frameworks, and—the biggest real-world blocker—ignoring architecture and dependencies. Stresses you need top-down air cover plus bottom-up empowerment and working examples. A landmark, frequently-referenceable piece on org transformation.
product transformationchange managementarchitecturecontinuous improvementframeworks
TIER 4
2024-06-21
Characterizes healthy teams by their habit of closing loops, integrating often, limiting open threads, and using forcing functions—then traces how teams 'drift' not from laziness but because doing the right thing progressively gets harder (raising concerns stops being rewarded, getting answers gets costly). Borrows bullet-journal 'migration' to frame loop-closing, and warns that excessive frequency/magnitude of change burns out formerly great teams. Ends with reflective diagnostic questions for spotting and resisting drift.
team healthforcing functionsdriftshared understandingcontinuous improvement
TIER 5
2024-08-18
Cutler argues tech's idealized 'mission command' operating model (empowered teams, apolitical meritocracy, free-flowing ground truth) only works while a social contract of legitimacy and coherence holds, and breaks down under distrust, layoffs, and divided narratives, much as armies disintegrated when their soldiers lost faith. Drawing on Morgan's Images of Organization, he urges challenging default frames and taking the political and legitimacy lenses seriously rather than dismissing them. A landmark reframing of why product operating models fail that names the missing variable: legitimacy.
mission commandlegitimacyorganizational politicsmental frameslayoffs
TIER 4
2025-04-07
Proposes a single transformation metric: the % of product teams that can operate fairly independently with a clear line of impact from daily work to customer/business value (plus actionable leading indicators, low-friction customer access, think-big-work-small coherence, and context-matched funding). Argues structural issues (architecture, business model, legacy inertia) usually cap this around 50-60% — what he calls 'institutionalized incoherence' — and that the instinct to blame individuals when the number is low makes things worse. A useful diagnostic lens framed as a weekend thought rather than a fully built model.
transformationNorth Star metricempowered teamsstructural constraintsself-assessment
TIER 4
2026-01-16
A first-person essay on a career-defining leader who ran the team via 3-5 owned 'lanes' with weekly cadence out of a single manually-copied-forward doc, distilling the 'work small, think big' practice and why the manual friction and collective sensemaking were the point. Cutler argues most frameworks flirt with these core principles but pretend work is more stable and repeatable than it is, and closes with an eight-step practical guide to running lanes. Valuable both as a how-it-actually-works reflection and an actionable operating practice.
lanescadenceteam operating rhythmownershipleadership
Constraints, Frameworks & the Tools That Carry Them
2 tier-5 · 4 tier-4
Enabling constraints are a learnable superpower, and frameworks are tools hired for a job — misapplying the job is the source of most framework conflict. This cluster gathers the practical craft of constraint design (dissecting Shape Up), the four-jobs lens for frameworks, the deep/broad context traps that distort how experts and generalists reason, and the segmentation lens for ways-of-working products.
TIER 4
2024-06-06
Argues many teams should use static low-tech docs and manual repetition over specialized tracking tools, building the case on bullet journaling's 'migration' (hand-copying forces you to question whether each item is worth keeping) and on 'state history' that digital tools erase by only showing current state. Reframes the say/do ratio into Say→Try→Did→Understood and shows how state history exposes information asymmetries and roadmap-vs-track-record gaps. The friction is a feature: forcing functions inspire thoughtfulness.
toolsdocumentationforcing functionsbullet journalingsay/do ratio
TIER 4
2024-10-07
Using London's 'Great Stink' as an analogy, Cutler argues that scaling growth inevitably introduces incoherence and that organizations only act once problems become viscerally undeniable. He proposes a set of concrete 'enabling constraints' (hiring gates, WIP limits, health-metric thresholds, mandatory vetting for large initiatives) that act as easy-to-follow early-warning mechanisms catching incoherence before it 'wafts into parliament.' Matters because it offers a proactive, structural alternative to the violent oversimplified resets that usually follow runaway scale.
enabling constraintsorg designscalingsense-makingWIP limits
TIER 4
2024-12-18
Drawing on his new head-of-product role at Dotwork, Cutler argues that for 'ways of working' products, simplistic firmographic ICPs (size, industry) fail and should be replaced by organizational psychographics across four dimensions: awareness (implicit/explicit/unintelligible ways of working), centralization/consistency context, rate and direction of change (inertia), and perceived effectiveness. He walks through clustering design partners on these axes, giving a concrete, transferable segmentation framework for products sensitive to a company's operating environment.
ICPcustomer segmentationproduct strategyorg psychographicsGTM
TIER 4
2024-12-26
A compact mental model contrasting two contextual-experience traps: deep-but-narrow experts overgeneralize their playbook to similar-looking contexts (missing the environment that actually made it work), while shallow-but-broad generalists fool themselves into 'first principles' that are really pattern-matching. Cutler offers seven self-interrogation exercises to catch overgeneralization, making it a useful short reflective explainer despite the holiday-post brevity.
mental modelsexpertisecontextfirst principlesself-awareness
TIER 5
2025-04-27
Argues the real problem with the glut of product frameworks isn't the number but failing to agree on the 'job' a framework is hired for, then names four distinct jobs: scaffold/practice environment (for building judgment), local interface (for experienced people to align fast), federated interface (lossy abstraction for cross-team coordination), and quality aid/checklist. Misapplying a job-X framework to job-Y — e.g., operationalizing Teresa Torres's Opportunity Solution Tree as a rigid process when it's a thinking tool — surfaces hidden assumptions about experience and creates conflict. An original, durable model with broad reference value.
frameworksscaffoldingshared languageOpportunity Solution Treecoordination
TIER 5
2025-11-03
Treats constraint design as a learnable superpower, using Basecamp's Shape Up (six-week cycles, appetite, fixed time/variable scope, betting table, circuit breaker, cool-down, etc.) to dissect each constraint's intent, risks of overdoing it, and how they counterbalance one another. Extracts what makes constraints enabling (clarity plus depth, full-loop integration, active engagement, cultural fit) and six principles for making them work in your own context. A landmark essay on enabling constraints.
enabling-constraintsshape-upframeworksteam-processcontextual-fit
AI & the Future of Product Work
1 tier-5 · 7 tier-4
Cutler's anti-cargo-cult lens applied to the AI moment. The recurring thesis: AI is a dysfunction multiplier, not a fix — it amplifies whichever org you already are, supercharges either shared metis or top-down control, and exposes (then often destroys) the invisible glue work that made artifacts matter. He resists the firehose-context narrative ("context engineering is interaction design"), warns against firing glue people on a friction heuristic that doesn't hold when the real barrier is capability or motivation, and frames AI adoption as an identity journey, not a tactical recipe.
TIER 4
2024-05-10
Cutler names the 'narrative soup' of 2024 tech: everyone authors fragile narrative fallacies ('post-ZIRP PMs', 'product theater', 'bad management') to explain organizational dysfunction, and these clashing stories (pre/post-pandemic joiners, CFO vs CPO, ICs vs VPs) actively divide people because real livelihoods and identities are at stake. He argues the antidote is personal reflection plus seeking like-minded support and diverse perspectives in safe settings, since fallacies break on contact with reality unless backed by power. A useful mental-model essay on epistemics and the social dynamics of org dysfunction.
narrative fallaciestech cultureepistemicslayoffssensemaking
TIER 4
2024-08-12
Cutler diagnoses the current tech malaise as six interlocking problems, work-around-the-work, demands to 'get into the details', fear that prevents anyone calling it out, the slow time meaningful change requires, naturally hectic priority churn, and accumulated multi-year fatigue, then offers his fixes (remove things, force-rank priorities, create tempo) before crowdsourcing many practitioners' diverse takes. The reader contributions converge on limiting WIP, restoring cadence, and fixing the top of the org. A strong systemic diagnosis of the doom-loop dynamics in 2024 tech, enriched by a chorus of perspectives.
tech industrywork around workWIP limitslayoffsorganizational dysfunction
TIER 4
2024-08-28
A compilation of 15 Wardley-style dialogues with a composite 'X' executive, dramatizing recurring product-org tensions: consistent sprint lengths and bird's-eye views, open-ended priorities, 'when will it be done', tech-debt denial, big meetings, accountability theater, developer-productivity metrics, span of control, and 150 in-progress projects. Amalgamated from real conversations, it is a sharp, recognizable catalog of dysfunctional reasoning and how to gently surface the deeper problem. Valuable as a reusable mirror for the 'you're not crazy' frustrations of practitioners.
dialoguesexecutive dynamicsprioritizationmetricsWIP
TIER 4
2025-11-27
Reframes many 'alignment' conflicts as a clash of cognitive styles, abstract/problem-first thinkers versus concrete/solution-first thinkers, rather than power, autonomy, or empowerment failures. Uses trip-planning, workshop participation, and a personal story of being asked for solutions to argue teams share intent but speak different cognitive languages, and that bridging those styles (especially under stress) is the real opportunity. A substantive, reflective people/collaboration essay.
cognitive-stylesalignmentcollaborationabstract-vs-concretefacilitation
TIER 4
2025-12-01
Introduces a framework grounding tool value in the current state of a target behavior: seven behavior states (aspirational, weakly realized, inconsistent, friction-filled, stable, suppressed, contested) crossed with COM-B (Capability, Opportunity, Motivation) to determine which intervention a tool should provide. The state-dependent lens also reframes where AI helps. A useful, transferable explainer despite being a short video post with AI-generated show notes.
toolsbehavior-designCOM-BadoptionAI
TIER 5
2026-04-16
A passionate, rigorous argument that the heuristic 'use AI to do what you should do but don't' only holds when the barrier is friction/cost, and breaks when the real barrier is capability, social opportunity, or motivation, applied via COM-B. The core warning: replacing 'glue people' with AI keeps the visible 20% artifact while losing the invisible 80% (judgment, legitimacy, timing, social navigation) that made it matter, with damage surfacing months later. A landmark piece on AI, invisible work, and constraint shifts.
glue workAI replacementCOM-Binvisible labororg capability
TIER 4
2026-04-22
Makes the case for 'multiplayer' AI use over solo prompting, using the cognitive-science 4Es (embodied, embedded, enacted, extended) to show what's lost when one person curates context alone. Cutler introduces a campfires/trails/quests model (conversations, accumulated traces via stigmergy, and purposeful work) and argues AI should enrich the loop between them rather than replace any phase. A vivid, original mental model for collaborative AI work.
AI collaboration4Es cognitionstigmergyshared contextteamwork
TIER 4
2026-04-30
Argues the AI 'playbook' resolves into four buckets, bad ideas AI makes worse, good instincts AI supercharges, genuinely new practices we haven't imagined, and the meta-skill of reading context, with identity threat as the biggest obstacle. Cutler diagnoses three traps (amplify-bad, identity-threat, avoidance) using a COM-B lens and frames the work as an emotional identity journey rather than a tactical recipe. A substantive anti-cargo-cult take on AI and product practice.
AIproduct practiceidentity threatCOM-Bcontext
Leadership, Management & the Limits of Empowerment
0 tier-5 · 5 tier-4
Cutler's most sustained critique of "empowerment" rhetoric: tech borrows the language of mission command (autonomy, intent, ground truth) without the hard infrastructure of trust, shared doctrine, and penalty-free escalation that makes it work. The cluster traces the implicit delivery-only bargain teams actually get, why staying close to frontline reality stopped reading as a leadership duty, and the conflated meanings of "complexity" and "reducing it."
TIER 4
2024-04-18
Cutler introduces the 'justers vs butters' polarity: 'just' is context-free, action-biased, and convergent ('we just need to ___'), while 'but' is context-heavy, questioning, and divergent ('but what about ___'). The reusable insight is that healthy teams need both in balance with mutual trust (justers ship fast, butters prevent the fatal edge case), and that experience teaches when to apply each as an effort moves from divergence to convergence. A tidy, memorable original mental model with self-reflection prompts; lighter than his deep essays but genuinely portable.
mental modelsdecision makingteam dynamicsdivergence/convergencecommunication
TIER 4
2024-11-14
Through a vivid scene of an exasperated executive declaring a project 'too complex,' Cutler distinguishes three things conflated under 'complexity': product work is inherently complex, the company is a complex adaptive system, and what executives actually feel is high cognitive load from drag, too many priorities, and fragmented information. The reframe — leadership's job isn't to reduce complexity but to create conditions where people can work effectively with it (bounded bubbles of complexity, simple interfaces, less drag) — is a sharp, memorable correction to a common executive instinct.
complexitycognitive loadleadershipcomplex adaptive systemsdrag
TIER 4
2024-12-29
Two near-identical 'common sense' team-turnaround playbooks (assess people, narrow focus, time-out, set guardrails, reintroduce work) succeed for some managers while others fail with the same approach — and a third story shows why: optics pressure, a guarded toxic veteran, post-layoff low trust, and a swamped partner stymie even experienced operators. Cutler reframes the 'we just need stronger managers' lament as a question of whether the environment lets common sense work, arguing leaders should build conditions where ordinary competent managers can execute rather than hunting for chaos-navigating superheroes.
managementteam turnaroundorg environmenttrustplaybooks
TIER 4
2025-07-08
Exposes the implicit bargain in most tech orgs: teams get autonomy for delivery, but managers are accountable for keeping the edges clean, and boundary-spanning is rewarded for execution while dissent must route up the official chain. Drawing on military mission command, Cutler argues tech borrows the language of empowerment without the hard infrastructure of trust, shared context, and penalty-free escalation, then offers four responses (accept it, carve a bastion and code-switch, stay disappointed, find better). A clear-eyed essay on the limits of 'empowerment' rhetoric.
empowermentautonomymission commanddissentmanagement
TIER 4
2025-12-28
Sparked by a CPO whose request for direct biweekly team updates drew 'micromanagement' pushback, Cutler asks when staying close to frontline reality stopped being a leadership duty, contrasting Drucker's original MBO (intent, decentralization, judgment) and military mission command against degraded MBO where targets become contracts and escalation feels unsafe. He argues tech's individualistic 'empowerment' lacks the shared doctrine and safe-escalation mechanisms that make direct visibility healthy, so the pushback is warranted given missing conditions. A thoughtful org-culture analysis of trust, exposure, and doctrine.
micromanagementMBOmission commandempowermentleadership
Product Craft, Discovery & Problem Definition
0 tier-5 · 4 tier-4
The hands-on practice of product work: how to frame a problem (a navigable space across layers and elevations, not a single root-cause moment), how to structure a learn-build-measure quarter, how to practice real product management even inside a feature factory, and the multi-lens sensemaking that no single model captures. Discovery here is collective, multi-elevation diagnosis rather than a tidy linear funnel.
TIER 4
2024-03-21
A 10-point practical guide for practicing real product management even inside an irreformable feature factory: instrument what you ship, talk to actual customers, learn how the business makes money, set usage/adoption goals nobody asked for, present from an outcome frame, and use strategic language hacks. The unifying thesis is 'it's all about the reps'—quietly do the work correctly within the constraint that someone else chose what to build, which builds skill, may open eyes, and prepares you for your next move. Durably useful career/craft advice, plus a candid note on coining 'feature factory.'
feature factoryproduct craftcareer developmentoutcomesmetrics/instrumentation
TIER 4
2024-03-28
A concrete experiment for structuring a quarter as 2 weeks research/discovery, 6 weeks ship something real to customers, 4 weeks iterate (weekly updates), and 1 week tie up loose ends, designed to force a full learn-build-measure cycle and avoid the end-of-quarter mad rush. Cutler couples it with strong operating discipline (make it the only OKR, clear the decks of reactive work below 15-20%, protect ~6 hours of daily focus time, normalize slack) and frames it explicitly as a disposable, roll-your-own experiment. Practical and immediately runnable, valuable as a how-to playbook.
cadence/rhythmdiscoverytimeboxingfocus timeteam operating model
TIER 4
2025-11-12
Uses a single workshop diagram to catalog nine overlapping analytical lenses (customer journey, persona, Wardley axes and movement, team boundaries and interactions, opportunities/options, execution kanban) and the 20+ directional relationships between them, showing why one lens is never enough for product work. Closes with the operational question of who decides which lenses matter and when. A useful, concrete explainer of multi-lens sensemaking.
lensessensemakingWardley-mappingteam-topologiesvisualization
TIER 4
2026-03-11
Cutler argues there is no perfect articulation of a problem; problem definition is a space you navigate by 'dancing' up and down layers (exploratory, definitional, contextual, descriptive, explanatory, strategic, generative, evaluative) and across mandate levels for different audiences. The leader's job isn't to define the problem and hand it off, but to create conditions where people can engage the situation from multiple elevations and converge on the crux. It matters because it reframes diagnosis (Rumelt's 'crux') as collective, multi-layer sensemaking rather than a single decisive moment.
problem definitiondiagnosisproduct leadershipshared understandingmental models