Organizational Abstraction Levels

Treating organizations as stacked abstraction layers and leading at the level appropriate to one's role — a software metaphor applied to management.

Also known as: abstraksjonslag, lede på riktig nivå, å lede på riktig nivå, abstraction layers, altitude (of review), presisjon i abstraksjonen / å treffe på riktig abstraksjonsnivå, retenking av abstraksjonsnivå (rethinking the abstraction level)

How authors use it

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

Documents (9)

• TBM 437: AI and the Recontextualization Tax John Cutler · 2026-09-03 Reader 🖥️
  Organizations pay a real, often-hidden cost -- the 'recontextualization tax' -- every time people flatten a working reality into a simplified version to suit whoever has the most power, the least appetite for detail, or the least time, and AI is newly good at absorbing that translation labor because it can render one underlying, accurate context into many audience-tailored formats without forcing teams to first standardize how they actually work.
• Leder du fra sidelinjen – eller ute på banen? Mats Kristensen · 2026-08-01 source ↗ Reader 🖥️
  Good leadership is range, not a fixed position: leaders should deliberately move between an outside, strategic vantage point ('sidelinjen') and direct, hands-on involvement ('banen'), because each position sees something real the other cannot, and staying too long in either one — never stepping back to reflect, or never staying close enough to feel what is actually happening — degrades leadership.
• 🧠 Community Wisdom: How AI is changing product operating models, tracking work stress with Whoop, whether you nee… Lenny's Newsletter · 2026-07-07 Reader 🖥️
  A weekly subscriber-community digest surveying current practitioner consensus across four threads of product work — tracking work stress with wearables, status-reporting as a manager of managers, go-to-market for tiny AI-augmented teams, and re-organizing the product operating model around AI — where the advice threads share a recurring move: redirecting the question from tools, tactics, and headcount back to the underlying outcome or system.
• 4) Morten Eikeland: Det finnes alltid et hierarki Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-06-01 source ↗ Reader 🖥️
  Hierarchy is not optional in any group of more than a few people — it arises structurally from division-of-labour pressure plus external groups' need for a single point of contact — and the agile/teknologi/flat-struktur ideology that pretends otherwise does not eliminate hierarchy, it only makes the actual operating hierarchy invisible, unspoken, and harder to challenge; therefore the work of leading well is not to flatten but to operate at the correct abstraction level for the role one is in, to recognise the role-vs-person distinction, and (for a developer becoming a leader) to walk a real sorgprosess of identity loss before gaining a different kind of relevance.
• 17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-05-18 source ↗ Reader 🖥️
  Large sociotechnical transformations — whether NAV's digital transformation a decade ago or the current AI shift — work by accumulating slow flywheel momentum that then snaps into a sudden S-curve climb through a high-friction liminal phase, and the leaders who guide organizations through such transitions are those who can 'take the elevator' across organizational floors and disciplines, translating between domain, technology and executive language while staying close enough to the craft that their advice is grounded in something real.
• Managers Are Struggling to Keep Up with the AI Productivity Boom Mollie West Duffy (with Liz at Atlassian) · 2026-05 Reader 🖥️
  As AI accelerates individual execution, managers become the new bottleneck; their role must shift from editor-in-chief (policing the work) to strategic guide (clearing the path) via five behavioral changes — focus on where not what, make managing up a core skill, deploy AI as an EQ coach, use AI to filter rather than flatten, and restructure check-in cadence.
• 15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-04-20 source ↗ Reader 🖥️
  Strategy is the disciplined act of choosing what NOT to do, justified by a credible read of where the world is going; doing it well requires leaders who are clear (tydelig) about direction without being dogmatic (skråsikker) about what they cannot yet know, and who keep the chosen direction connected, top and bottom, to what the organization is actually capable of and willing to move on.
• 14) Øystein Ulseth pendler mellom å lede og levere Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-04-07 source ↗ Reader 🖥️
  The best technology leaders pendle (commute) deliberately between leading and delivering — driven not by career ambition but by the joy of building at the right level of abstraction — because crossing that boundary in both directions is what makes you precise: a hands-on background gives leaders pragmatism about complexity and trade-offs, while a leadership background gives builders the holistic, risk-aware perspective that lets them choose what to build.
• 8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-01-04 source ↗ Reader 🖥️
  Becoming Nordic-aligned (not pan-European, not purely national) is the right level at which to consolidate digital marketplaces, and getting there requires leading at the right abstraction layer — setting direction and 'why' from the top while delegating the 'how' to distributed cross-Nordic vertical teams — because the previous failure of pan-European centralisation taught Printzell Halvorsen that scale only works when the people whose work is being reorganised are kept, respected, and reassembled around problem verticals rather than dispossessed by a new hub.

Propositions touching this concept (1)

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

2026-01

• explicitA developer's discipline of moving between abstraction layers transfers to leadership: organisations are nested abstraction layers (individual → team → område → divisjon → selskap) and the leader must reason at the right one.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet · p8

Open gaps (46)

• incompleteSame system-shift-framed-as-practice-tweak pattern recurring across the user's recent extractions (Cutler, Osmani, Reed, HBR Career-Growth-Overwhelmed). Duffy diagnoses a structural failure of the manager layer to keep pace, then prescribes individual behavior changes that leave organizational architecture, role boundaries, decision rights, and compensation untouched.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: Pair with Cutler 'AI Won't Save the Kingdoms We Built' and Osmani 'Orchestration Tax is You' for the syntopical thread. The unanswered question: when is the manager role itself the bottleneck-design, and what would an AI-era org chart actually look like?
• incompleteTreats manager decision-rights over AI-produced output as unproblematic — but if AI generates faster, broader, and (with verification) better output than the manager's review can keep up with, the manager's authority is conventional, not epistemic. The piece never asks whose judgment is actually load-bearing.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: Cathy O'Neil on algorithmic accountability; Bainbridge 'Ironies of Automation' for what happens to operator authority when automation outpaces oversight (Paul Reed extract).
• incompleteThe AI-as-EQ-coach example is presented as a clever augmentation, but if managers cannot find time for warm communication, that's an org-design failure being masked by a tool. The article never asks whether normalized DM-auditing by AI changes the implicit contract between manager and report.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: Surveillance/trust literature; HBR 'On Managing Yourself' for the older norm being replaced.
• illogical'Increase frequency to course-correct faster' (daily syncs) is offered as a remedy for manager overload, but adding meetings to an already overloaded manager is the textbook overload-amplifier. Osmani's orchestration-tax argument applies to managers too.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: Cutler TBM on institutionalized overload; Osmani 'Orchestration Tax is You'.
• incomplete'89% of leaders agree AI has accelerated work' — but the article assumes that acceleration is sustained throughput rather than a transient burst as teams adopt new tooling. No engagement with the possibility that the 'AI productivity boom' is a one-time S-curve, not the new steady state.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: DORA reports on AI's effect on engineering throughput; longitudinal AI-adoption studies.
• incompleteThe thesis 'det finnes alltid et hierarki' is rescued from triviality by Eikeland's broad definition (formell + uformell + kunnskaps- + framing-makt), but the same breadth makes the claim nearly unfalsifiable. Every conceivable group has some asymmetry of influence on some dimension; calling that 'hierarki' wins the argument by definition. The conversation does not engage the harder question of when the unit of analysis is wrong — when treating a temporary, context-dependent, weak asymmetry as a 'hierarchy' obscures more than it reveals.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Compare to network-and-influence literature (Cross/Parker on organisational networks, Vedres/Stark on structural folds) where the alternative unit is the network of weak ties rather than the layered hierarchy. Also Heath/Sunstein on consensus-driven decision-making to test where 'hierarchy' really is the operating frame.
• incompleteThe claim that flat-org rhetoric is selvbedrag is supported by Eikeland's clinical observation and the innvandrer vignette but not by counter-evidence from organisations that have made the rhetoric operationally real (or that have failed in distinctively non-Eikeland ways). The conversation does not engage Holacracy, Buurtzorg, sociocratic governance, or the long literature of self-managing teams. The result is a strong descriptive claim resting on a single vantage point.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Read Laloux Reinventing Organizations, Buurtzorg case studies, Robertson's Holacracy critically — both for examples of self-organisation that genuinely changes which hierarchy operates and for documented failures that Eikeland's frame would explain well. Pair with Lee/Edmondson's typology of self-managing organisations.
• incompleteThe role-vs-person distinction is presented as universal but it conflicts with a strong current of contemporary leadership literature (authentic leadership, bring-your-whole-self-to-work, vulnerability-based trust à la Lencioni/Brown) that holds that role-thick depersonalised leadership is itself the failure mode in knowledge work. The conversation does not engage these counter-positions; it treats them only implicitly via the Trump example, which is a one-sided foil.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Read Brené Brown on Dare to Lead, Goffee/Jones 'Why Should Anyone Be Led by You?', Lencioni on vulnerability-based trust against Eikeland's role-thick line. The most interesting test case is: are there role-domains where role-thickness is right (dommer, kirurg, politi) and other domains where it is wrong (product-team leadership, R&D leadership)?
• incompleteEikeland's developer-to-leader sorgprosess prescription is rich on the loss side but thin on the gain side. The transition presumably brings new sources of meaning (impact through others, system-level effect, mentoring, organisational design), but the conversation barely names them. The risk for the listener is to internalise the loss-frame and miss the path through.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Camille Fournier's Manager's Path; Will Larson's Staff Engineer/An Elegant Puzzle on the IC-vs-manager fork; Lara Hogan on growing engineering leaders. Pair with Olga Khazan or Lori Gottlieb on the psychology of mid-career identity transitions.
• incompleteThe illusion-of-explanatory-depth intervention (ask for mekanismer not meninger) is presented as reliably productive but Eikeland admits it provokes forbannelse and ejection from rooms. The conversation does not address how to make the intervention land without burning the relationship — i.e., the practice question of how to descend into mekanisme safely. This matters because the intervention has weight only if it can be sustained inside an ongoing leader relationship.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Edgar Schein on humble inquiry; Marshall Goldsmith on stakeholder-centred coaching; Patterson et al. Crucial Conversations. The Heis-internal pairing is with Brede Moe (ep 9) on psykologisk trygghet as the precondition for being usable as a diagnostic outsider.
• uninformedThe argument that teknologene have gained makt at the expense of 'litt enklere selgere' is named as a flagged trade-off but not analysed. The conversation does not engage the broader political-economy story of which professions rise and fall with each kunnskapshierarki shift, or the consequences for democratic and labour-market dynamics when one type of fag becomes dominant. Eikeland's clinical vantage is not designed for this question; the gap is honest but real.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Read Daniel Markovits The Meritocracy Trap, Michael Sandel The Tyranny of Merit on the consequences of credentialist hierarchies. For the Norwegian case specifically, NAV's own reports on labour-market polarisation.
• incompleteEikeland insists hierarchies are inevitable but does not develop how to design good hierarchies versus bad ones. Hierarchy as a design object — its arity (span of control), its time-horizons per level, its dual lines (formal/uformell), its rotation, its accountability — receives no operational attention. The descriptive claim therefore stops short of a constructive prescription beyond 'operate at the right abstraksjonslag and recognise rolle vs person.'
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Elliott Jaques on requisite organisation and time horizons per level; Stafford Beer's Viable System Model; James Mwangi on adaptive governance. Pair with Printzell Halvorsen (ep 8) on the Vend operating model as a worked example of an explicit, designed hierarchy that honours these structural pressures.
• incompleteThe claim that ledelse-as-coordination kicks in around eight people is asserted as 'avhenger litt av hvor mye interaksjon du trenger' but not defended against the broader social-science literature on group size, span of control, and self-organisation thresholds. The number is plausible but the conversation does not engage why eight rather than five or twelve, what happens in distributed/asynchronous groups, or how the threshold shifts with technology.
  4) Morten Eikeland: Det finnes alltid et hierarki — read next: Robin Dunbar's hierarchies of group size (5, 15, 50, 150); Christopher Allen's optimal group sizes; Tuckman's small-group dynamics. For the distributed case, GitLab's all-remote handbook on team sizing and the post-COVID literature on async coordination.
• incompleteThe case for 'lokalt forankret, nordisk samlet' rests heavily on the three favourable conditions (small cultural distance, similar maturity, no hub story) that Printzell Halvorsen names. The conversation does not seriously interrogate what happens in cases where one or more of those conditions does not hold — e.g. a Nordic group with one dominant and three start-up markets, or a public-sector federation where national differences (legal, fiscal) are large. The model may be narrower than its rhetorical appeal suggests.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — read next: Compare to Nordic banking (Nordea), Nordic telecom (Telia/Telenor), and Nordic public-sector federations to see where the conditions hold and where they don't. Read Geert Hofstede / Erin Meyer on the actual measured cultural distances within the Nordics.
• incompletePrivileged-Schibsted-vantage shapes what's visible vs. invisible. The lessons are drawn from a Schibsted-internal lineage of marketplaces with strong brands, a developer-heavy talent pool, and a long maturation as commercial businesses. The conversation is silent on: public-sector contexts, non-media startups, B2B enterprise software, government-mandated platform consolidations, and platforms where brand-in-consumers'-heads is not the load-bearing asset. The framework is presented as broadly applicable without owning these scope conditions.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — read next: Read public-sector platform consolidation case studies (NAV, Skatteetaten, NHS Digital, Estonian e-government); read B2B platform consolidation studies (Salesforce-MuleSoft, Adobe-Figma). The presence/absence of the Vend pattern in those contexts would map the model's actual reach.
• incompleteThe methodological claim that big-bang beats phased for integration projects with a known target state is grounded in three Vend cases and asserted as a general lesson. The conversation does not consider failure cases (industry has many) or the boundary conditions (rehearsal infrastructure, rollback capability, cohesion of the cut team). Listeners may over-apply.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — read next: Read post-mortems on famous failed big-bang migrations (UK NHS NPfIT, TSB Bank 2018, Hertz/Accenture) to identify what made Vend's big-bangs work that those did not have.
• incompleteBob the Builder is presented as low-code AI tooling that produces useful prototypes and personal-productivity solutions but is firewalled from product production code. The conversation does not address how outputs ever cross that firewall — what happens when a marketing team's Bob the Builder solution becomes load-bearing and needs the engineering quality bar.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — read next: Read low-code/citizen-developer governance literature (Gartner's 'fusion teams,' Microsoft Power Platform CoE patterns) for how organisations handle the citizen-to-production handoff.
• incompletePrintzell Halvorsen names the senior/junior asymmetry of technology fluency implicitly (his own developer past as anchor; CFO going through Bob the Builder to stay relevant) but never engages the question of how Vend develops the next generation of leaders without a developer past. The transferability of the abstraksjonslag instinct to non-technical leaders is left open.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — read next: Read Beane on apprenticeship in mixed-expertise contexts; read deliberate-practice literature on developing abstraction skill without a code substrate.
• incompleteThe destination-vs.-chat scenario framing is treated as binary. The conversation does not engage the third possibility — that marketplaces become specialised APIs feeding many fronts (chat, AR shopping, voice assistants), with the consumer-facing brand decoupled from the consumer-facing surface. That would require a different bet on data infrastructure and brand strategy.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — read next: Read literature on platform economics under generative AI distribution (Anu Hariharan, a16z's recent marketplaces writing); Matthew Prince's own writing at Cloudflare on the AI-content-economy collapse and 'pay-per-crawl' proposals (which Printzell Halvorsen alludes to when citing him).
• uninformedThe conversation does not engage with the consumer-welfare or competition-policy implications of Nordic consolidation. Consolidating into Vend reduces marketplace competition within each vertical at a Nordic level. The hosts do not raise this; Printzell Halvorsen does not address it.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — read next: Read EU competition decisions on Adevinta/eBay Classifieds, Schibsted's spin-off rationale, and Nordic competition authorities' marketplace cases for the regulatory frame the conversation omits.
• incompleteThe autobiographical-prescriptive proposition ('do a good job where you are; opportunities follow; developer → product → business is the natural path') is presented without engaging the question of how much of Printzell Halvorsen's trajectory is reproducible vs. how much depends on McKinsey-as-accelerator, Norway's small leadership pool, and the specific historical moment of FINN. The advice may be more biographically contingent than it sounds.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — read next: Read against the Cutler thread on what conditions enable senior individual-contributor-to-leader transitions inside specific organisations, and against literature on path-dependence in executive careers.
• incompleteScale dependence of pendling. The whole career story plays out inside two large Norwegian financial-services organisations (Storebrand, Fremtind) that recognise technical depth as legitimate seniority. The conversation never tests whether pendling is feasible — or how it changes shape — in small startups (no role to come back to), pure consultancies (the IC vs. leader frame may not apply), public-sector hierarchies (rigid grade structures), or US-style stock-comp tracks where stepping back is also stepping out financially.
  14) Øystein Ulseth pendler mellom å lede og levere — read next: Pair with Charity Majors' 'Engineer-Manager Pendulum' original essay to see her conditions for it working; pair with Will Larson on staff-engineer archetypes for the IC-track question; pair with Norwegian-public-sector accounts (NAV optimising for fast flow) for the bureaucracy edge case.
• incompleteThe people who can't pendle. Ulseth's account is sympathetic to both directions but assumes the listener has the option of swinging both ways. It does not address those who are only-leaders (lost technical currency) or only-deliverers (no taste for organisational complexity) — and whether they should be coached, paired, or left in their lane. There is a real possibility that pendling is a personality privilege as much as an organisational one.
  14) Øystein Ulseth pendler mellom å lede og levere — read next: Camille Fournier on technical-leadership transitions; Cutler on the costs of forcing technical contributors into managerial roles; Allen Holub on accountability and the limits of role-fluidity.
• incompleteThe architect's function is never defined. The talk asserts that architecture has not changed in its core function, only in practice — but it does not say what the function is. The closest thing to a definition is 'enabling speed and flow via loose coupling and high cohesion', which is more a goal than a function and which collapses architecture into platform engineering in some readings.
  14) Øystein Ulseth pendler mellom å lede og levere — read next: Vlad Khononov on coupling in distributed systems; Ruth Malan on architecture as 'the design decisions that are hardest to change'; Team Topologies for the sociotechnical framing Ulseth invokes.
• incompleteBredde/dybde sounds clean but is operationally underspecified. How does a sjefsarkitekt choose which initiatives to take as 'mine'? Ulseth nods that they should be 'both important and interesting' and that the two usually overlap — but the harder cases (important-but-boring, interesting-but-marginal) are not discussed. This is the place where pendling-by-design either works or quietly collapses into one side.
  14) Øystein Ulseth pendler mellom å lede og levere — read next: Cutler on how leaders allocate attention; deep-dive into 'staff-plus' patterns where senior ICs balance technical and political work.
• incompleteThe claim that AI raises the incentive to live good engineering culture is asserted but not mechanised. Continuous delivery has been well-described for 20 years and only patchily adopted. Why will AI succeed in changing this where the prior decade's tooling, DORA reports, and platform engineering did not? A causal story is missing.
  14) Øystein Ulseth pendler mellom å lede og levere — read next: DORA 2025/2026 specifically on AI's interaction with delivery practices; Birgitta Böckeler and Martin Fowler on AI-coding feedback loops; Kent Beck's TCR work as the practice end of the same idea.
• incompleteNo data on whether pendling actually produces better outcomes. The argument is largely 'I felt better and have heard I do better.' The episode lacks any reference to organisational research on whether engineer-manager pendulum careers correlate with better team or product outcomes — and whether the benefits go to the individual, the team, or the organisation.
  14) Øystein Ulseth pendler mellom å lede og levere — read next: Pragmatic Engineer / Newcomer on staff-plus role outcomes; LeadDev surveys on engineer-manager transitions; academic work on bidirectional career mobility in knowledge work.
• uninformedUlseth notes he has not yet seen conversational architecture practiced and that sociotechnical architecture is a new acquaintance — yet these are the frameworks he is now bringing into Fremtind's IT strategy. The talk does not engage seriously with the published critiques of these models (e.g. that Team Topologies under-specifies platform-team funding, or that Harmel-Law's model assumes a maturity teams may not have).
  14) Øystein Ulseth pendler mellom å lede og levere — read next: Andrew Harmel-Law's own book and the Architecture Decision Records literature; critical reviews of Team Topologies (Manuel Pais et al.).
• incompleteThe criterion that distinguishes strategic deselection from defensive or pathological deselection is named (the climate example) but not developed. When the urgent legitimately overrides the important and when it doesn't is left unanalyzed.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: John Cutler on institutional overload (TBM 412) and the cost of context collapse; Hamilton Helmer's 7 Powers for a more analytical theory of when narrowing is value-creating vs. value-destroying; Roger Martin's 'Playing to Win' for the 'winning aspiration → where to play → how to win' chain that forces the warrant question explicitly.
• incompleteThe people on the wrong side of deselection ('det er noen folk bak') are acknowledged but their experience and what leaders owe them is not analyzed. The 'kjipe oppgavene' frame keeps it at the level of leader-discomfort rather than treating the human cost as its own analytical object.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: Annie Duke's 'Quit' for the ethics and cognition of stopping; Cutler on accountability culture vs. blame; literature on layoffs/restructuring as legitimacy work.
• incompleteThe HOW-sharpening proposal (be sharp on tempo vs. error-tolerance, not on implementation) is offered as a resolution but not tested against the failure modes of values-as-strategy (where 'speed over perfection' becomes a slogan everyone reinterprets locally).
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: Cutler on operating systems and 'making the trade-off visible'; DORA/Accelerate on what concrete operating principles actually correlate with outcomes; Beck's Tidy First? framing for how small-scale design decisions encode strategic posture.
• incompleteThe relationship between 'kompani-bets' and the legitimacy economy of an autonomous team-of-teams organization is sketched but not modeled. How many bets per year? Who funds them? How does the organization recover from a bet that fails publicly?
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: Spotify's own writings on the post-bets era and what replaced it; Marty Cagan / SVPG on product strategy at scale; Cutler on directly-responsible-individuals and accountability when top-down moves intrude.
• incompletePublic-sector strategy is dismissed as 'mer taktikk' but the conversation does not return to it. Whether public-sector leaders can do something like deselection (and what its political constraints look like) is a productive missing thread for a podcast whose hosts work in NAV-adjacent contexts.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: Mark Moore on public value; Mariana Mazzucato on mission-led public strategy; specific Norwegian writing on NAV and Statens forvaltningsapparat strategy work.
• incompleteStrategy as power is gently visible (who gets the IT-køen priority that Vips got) but not analyzed as power. The political economy of must-win-battles inside a large organization — who loses access to resources, and through what mechanism — is left implicit.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: Cutler on power and space (TBM 413, recently in user's library); Pfeffer on power in organizations; Helmer/Porter for the strategic value of being explicit about who-loses-what.
• incompleteThe flywheel/S-curve/liminal frame is used to describe both the NAV transformation (which succeeded) and the AI shift (in progress). The conversation never names a transformation that failed at the liminal phase and asks why — so the framework is at risk of being unfalsifiable on its own terms.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Read failed transformations through the same frame — e.g., government-IT projects that died in their liminal phase, large agile adoptions that reverted. Cutler's overload work and the 'people who tried Spotify model' literature would expose where the frame breaks. The Geoffrey Moore 'Crossing the Chasm' tradition has more developed accounts of curves that stall.
• incompleteThe 'learning vs production' rule is stated as a personal heuristic but not connected to any educational theory or empirical evidence. For a leader of consultants asked to scale this practice, there is no model for how the two modes should be partitioned, whether across days, projects, or moods.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Donald Schön's reflection-in-action; deliberate-practice literature (Ericsson); Beck's 'tidy first?' framing of preparatory vs delivery work — the tidy/messy split echoes the learning/production split structurally. Worth syntopical pass against Beck's recent 'Starving Genies' work on AI-assisted craft.
• incompleteThe elevator metaphor is generalised from Jonas's own career and from the show's animating premise. The conversation does not seriously consider organisations where vertical traversal is structurally suppressed (military, regulated finance with information walls, classified environments). The implicit premise that elevators are always available may not hold.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Read about organisations with designed information barriers — security classifications, MAR-walled investment banking, healthcare compartmentalisation. James C Scott's 'Seeing Like a State' on legibility. Where the elevator is locked, what substitutes?
• incompleteThe introvert-leader claim rests on one practitioner's experience and one rhetorical contrast (scale removes small-talk tax). Jonas notes that some colleagues found it hard to distinguish his opinions from his decisions — a cost that may be specifically introvert-shaped (lower social-cue density) but is not investigated.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Susan Cain on introvert leadership; the Cutler thread on 'signals that look like decisions' in leadership communication. The implicit problem of 'low-cue leadership at scale' is worth its own extraction.
• incompleteThe tractor and car analogies argue for slow structural change, but neither is examined for disanalogies. AI compresses learning loops in a way physical machinery cannot. The argument relies on the assumption that adoption is gated by humans, not by capability — which is plausible but not defended.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: The general-purpose-technology economics literature (Bresnahan & Trajtenberg); David Autor on labour-market restructuring time. Counter-cases: dial-up to broadband transitions, mobile phones — both moved faster than tractors. What predicts speed?
• uninformedThe Gukesh anecdote is reported confidently ('the only one of the young players not allowed a computer before age 12') but is not actually verified in the conversation. Whether true or apocryphal, it is doing argumentative work it has not earned.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Quick fact-check; more importantly, treat the underlying claim about protected early craft as a hypothesis and look at the actual evidence on AI use in early-career learning — programming pedagogy research will move on this in 2026-2028.
• incompleteThe claim that NAV's success was driven by capability investments is asserted from inside the case by the very people who made those investments. There is no counterfactual — no comparable agency that did not invest similarly and failed similarly. Some of the 'flywheel' may be storytelling.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Compare cross-country COVID welfare-IT responses (Germany, Denmark, UK), and Norwegian agencies of similar size that did not transform similarly. The Skatteetaten and Helsedirektoratet experiences would be a natural comparison.
• illogicalJonas argues both that we are early on the AI S-curve (so 10% gains are not the story) and that complexity will push back on productivity gains as they accumulate. These are compatible but in tension: if the curve climbs steeply because of intent-level abstraction, the complexity ceiling should appear later; if complexity bites soon, the curve is shallower than claimed. The argument is not adjudicated.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: The Brooks / Mythical Man Month tradition on accidental vs essential complexity; Ousterhout on system design; recent measurements on long-running agent harnesses (Anthropic harness design work) which directly test the complexity-ceiling claim.
• incompleteThe piece never converts 'spennvidde' into an actionable, falsifiable decision rule — it does not say how a reader should decide, in a given week or situation, whether to be on the sideline or on the pitch. It stays at the level of a compelling metaphor and a values statement ('leadership is about range') rather than cashing that out into a specific, testable claim or a diagnostic the reader could apply to themselves. This matches the reader's known skepticism toward pieces that don't get past the metaphor to a concrete, falsifiable claim.
  Leder du fra sidelinjen – eller ute på banen? — read next: Charity Majors' original 'Engineer-Manager Pendulum' essay, or the corpus's own extract-heis-14-oystein-ulseth-pendler-lede-levere, for a more concrete treatment of when and how to switch operating modes; Heifetz's actual adaptive-leadership work (not just the borrowed metaphor) for a real decision framework for when technical/operational engagement is warranted versus when the problem is adaptive and requires distance.
• incompleteMulti-cloud or hybrid strategies are not discussed — the entire framework assumes AWS as the sole provider. The fungibility argument could extend to cross-provider flexibility but this is unexplored.
  Presentation: How Netflix Shapes our Fleet for Efficiency and Reliability — read next: Look for writing on multi-cloud capacity strategy, or provider-abstraction layers at scale
• incompleteCutler names one precondition for AI paying the tax well -- 'it has the raw context and that context is reasonably up to date' -- but never explores what happens when that precondition fails: stale, partial, or politically curated context would presumably make AI-generated translations confidently wrong rather than usefully simplified, and the essay gives no signal for how to detect that failure mode.
  TBM 437: AI and the Recontextualization Tax — read next: Compare with Cutler's own tbm-434 (extract-tbm-434-how-maps-can-hide-problems), where he argues AI cannot reconcile genuinely incoherent organizational structures and, if it smooths over contradictions rather than exposing them, can 'exacerbate the underlying tensions while producing a false appearance of alignment' -- the same smoothing mechanism praised here as a feature is treated there as a serious risk. The two pieces would benefit from being read together to see whether Cutler distinguishes 'translating a coherent reality for different audiences' from 'smoothing over an incoherent one,' since from outside his own framing the difference may not always be legible in practice.
• incompleteThe essay treats the recontextualization tax purely as a cost to be minimized/automated away, without asking whether the act of flattening/translating reality for a powerful audience ever serves an epistemically or organizationally valuable function beyond accommodation -- e.g. forcing someone to compress a complex reality into a one-page summary can itself surface what actually matters, a benefit lost if AI does the compression silently on the recipient's behalf.
  TBM 437: AI and the Recontextualization Tax — read next: Cross-reference tbm-414's treatment of legibility and power (extract-tbm-414-legibility-and-legitimacy#p1: 'making systems legible requires selective simplification that enables control over those being simplified') -- if flattening is partly about control, not just cognitive load, then having AI perform the flattening doesn't remove the power dynamic, it just launders who is doing the (potentially distorting) selection.