Hands-On Leadership & the Pendulum

Deliberately moving between leading and delivering across a career — technical depth as the entry ticket that keeps leadership grounded, with real identity grief in the transition.

Also known as: pendle (verb) / pendel (noun), pendle, Engineer-Manager Pendulum, inngangsbillett (entry ticket), inngangsbillett, lederhatten / brette opp armene, sorgprosess (developer-to-leader), joggeskoene på (put your running shoes on)

How authors use it

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

Documents (13)

• Alex Ewerlöf's Post Alex Ewerlöf · 2026-10-08 source ↗ Reader 🖥️
  On the Y-shaped career ladder, Staff Engineers — unlike Engineering Managers, who spend their discretionary time on people-admin — should put their extra time into deepening technical skill and staying hands-on in code and architecture, because the alternative is sliding into an 'Ivory Tower Architect': elevated pay, voice, and autonomy without the grounding that earns it, which working engineers quietly route around.
• 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.
• The Power of Strategic Centering Harvard Business Review · 2026-07-01 source ↗ Reader 🖥️
  In a 'dematerializing' economy where corporate value has shifted decisively from physical assets to intangibles, executives should replace industry-position-based strategy frameworks with a single, deliberately chosen 'strategic center' (mission, customer, technology, ecosystem, or friction erasure) that the whole organization orients its resource allocation, opportunity selection, and identity around — because a clear center bounds the opportunity set without closing it, resolves capital-allocation conflicts, and licenses fast 'permissionless' action without requiring hierarchical approval.
• The engineering manager role is splitting in two Stephane Moreau · 2026-06-09 source ↗ Reader 🖥️
  The engineering-manager role is fracturing into two divergent futures — the code-adjacent tech lead manager and the non-technical multi-team EM — and because AI-shrunk teams are driving the split as an unplanned byproduct of flattening, engineers on the management path must diagnose which future their company is building and prepare accordingly rather than aiming at a single 'EM' destination.
• 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.
• Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) Kent Beck — Still Burning Podcast · 2026-05-20 Reader 🖥️
  We are not in another technology hype wave but in a step-function transformation: the marginal cost of producing software is collapsing toward zero, large incumbents are adopting AI faster than any prior shift, and the whole ecosystem — not just the AI labs — is accelerating; in this 'Red Queen' regime, profit and productivity may not visibly improve because every competitor is running at the new tempo, so the only sane response is to paddle straight into the wave by sustaining the maker's compulsion (the 'itchy brain'), reshaping engineering leadership toward hands-on impact, and accepting that software engineering as a profession will resemble medicine or law more than the unique 2010s template that minted six-figure undergrads.
• How to Build a Superteam That Keeps Getting Better Harvard Business Review · 2026-05-01 source ↗ Reader 🖥️
  In periods of rapid change, teams win not because they start with the best plans or the most talent but because their leaders build a continuous-improvement culture — one that makes experimentation, curiosity, early problem-surfacing, hands-on involvement, non-threatening feedback, and growth-oriented investment in people the daily default — so the team's rate of learning, not its starting position, determines whether it becomes a 'superteam.'
• 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.
• 12) Greger Teigre Wedel: Når sjefen har svaret, tier resten Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-03-01 source ↗ Reader 🖥️
  When the boss already has the answer (and shows it), other voices fall silent — so a hands-on technical leader's most important discipline is choosing, situationally, when to suppress their own answer and create space for the team to find one.
• 3) Christin Gorman leder uten tittel Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2025-10-27 source ↗ Reader 🖥️
  Title-less leadership is influence through clear, accountable public voice — anchored in actually delivering working software and a financial freedom that lets you keep telling the truth — and it is one legitimate, complementary mode of leadership in a tech industry that needs many such modes, even though it has real costs (intimidation effects, defensive listeners, and an asymmetry where formal leaders take credit when title-less leaders' ideas do get adopted).
• 1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2025-10-13 source ↗ Reader 🖥️
  What warrants the Steve Jobs analogy in Larsen's case is not product taste in a consumer sense but the disciplined construction of a 'strategic narrative' so concrete and personally believed that it can pull a large bureaucracy through a paradigm shift — and this only works when paired with a complementary engineering apparatus (reverse Conway architecture, cross-functional value streams, common components discovered rather than designed, a 'golden-path' platform that makes the right thing the easy thing) operated by a leader who keeps an 'inngangsbillett' to the technical conversation so that the narrative remains connected to what is actually happening on the floor.
• 0) Velkommen til Heis Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2025-10-10 source ↗ Reader 🖥️
  Heis is a podcast about technology leadership across the different organizational floors of a company — riding the elevator up and down to talk with leaders at every level — built on the conviction that autonomous teams still need leadership, that traditional management does not fit the team model, and that the leaders modern technology companies need are people with hands-on experience from working in teams and with technology.
• Update on Software Engineering Career Ladder jamesshore.com · 2024-08-20 source ↗ Reader 🖥️
  OpenSesame's redesigned career ladder deliberately shifts the organization's definition of engineering seniority away from individual ownership and self-promotion toward teamwork, peer leadership, and manager-verified skill fluency -- trading the old system's clarity and perceived fairness for reduced self-promotion/tenure bias, at the real cost of a heavier, judgment-intensive evaluation burden that falls unevenly on managers depending on how well they already know their people.

Propositions touching this concept (3)

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

2025-10

• explicitMaintaining inngangsbillett to technical conversation is non-negotiable for a leader who wants to attract good engineers, develop grounded strategic narrative and keep the floor-to-strategy translation working.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p9
• explicitHe is not afraid to hire people smarter than himself, but staying relevant to those people requires holding the inngangsbillett — both for the sales pitch (you sell a future) and for the ongoing dialogue.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p25
• implicitHe could feel exactly when Larsen hit his technical competence wall in conversation — and Larsen's capacity to stretch the inngangsbillett far beyond that wall is itself the load-bearing skill.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p26

Open gaps (56)

• incompleteThe two-way split erases the technical-track / IC-leadership ladder. The article scopes itself to 'the management path,' and even its code-adjacent option, the TLM, is defined by managerial load (1:1s, career conversations, project coordination) — i.e., it is still a manager. The staff → principal → distinguished ladder, where one leads through technical judgment and influence with no personnel responsibility ('leadership, not management'), is collapsed into 'management' or left out. For a reader on exactly that ladder, the dichotomy is a false binary: there is a third future — the technical leader who is neither a people-manager nor a coder-with-reports.
  The engineering manager role is splitting in two — read next: Read against 'Developing Your Leadership Skills toward Principal Engineering' (the whole IC-leadership-ladder case), heis-12 (a principal engineer orchestrating ~40 architects with no personnel authority, forced into a non-coercive leadership style), and 'kill your org chart' (staff/principal engineers holding project leadership) — all of which name the technical-leadership track this piece omits.
• incompleteThe TLM-viability claim rests on managerial load scaling down cleanly with team size, which is untested. Career conversations, performance management, hiring, and conflict do not obviously shrink linearly with headcount — a three-person team can still generate a full-time person-problem — so the attention-split Larson warned about may not actually become manageable just because the team is small.
  The engineering manager role is splitting in two — read next: Seek span-of-control research on the composition (not just the count) of managerial load, and practitioner accounts of small-team TLMs, to test whether load really tracks headcount.
• incompleteEvery named company example is one whose centering choice is, so far, associated with a good outcome (Novartis, Fujifilm, TSMC, Samsung, Toss, DBS, Nvidia, Shopify, early Amazon). Kodak and Southwest appear only as foils establishing other companies' successes, not as tested instances of 'had a clear, deliberately chosen single center and it still failed.' No company that centered and underperformed is discussed, so the base rate of centering's success is unknowable from the article alone.
  The Power of Strategic Centering — read next: Survivorship-bias literature (Mlodinow's 'The Drunkard's Walk', Taleb) on retrospective success narratives fitted to winners; Rosenzweig's 'The Halo Effect' critique of the 'In Search of Excellence' genre of business writing, which has essentially the same evidentiary structure as this article.
• uninformedNo attempt is made to separate the causal contribution of 'centering' from contemporaneous confounds: Novartis's radioligand bet coincided with a broadly hot oncology/precision-medicine investment cycle; TSMC's and Samsung's ecosystem success is explicitly bound up with decades of targeted state industrial policy (named in the text itself), yet the article still credits 'centering' as the operative variable rather than state support; Fujifilm's successful diversification depended on pre-existing chemical/materials-science IP whose availability to Kodak is never assessed.
  The Power of Strategic Centering — read next: Regression-to-the-mean and confound-control literature in strategy research; comparative case-study methodology critiques (e.g., Geoffrey Jones or business-history methodology essays) on isolating a single explanatory variable from multi-causal corporate histories.
• incompleteEach of the five centering types is given a named risk (mission drift, goal conflict, technological narcissism, geopolitical dependency, scope creep), but no instance is given of a company whose centering failed because that risk actually materialized. Without an observed failure case per risk, the framework offers no falsification criterion — it cannot currently be distinguished from 'successful companies, described after the fact, can always be shown to have had a coherent internal logic.'
  The Power of Strategic Centering — read next: Popper on falsifiability as a demarcation criterion; compare against how the 'resource-based view' and 'core competence' literatures the article dismisses were themselves originally supported by anecdote before later empirical scrutiny — is this critique specific to strategic centering, or standard for the strategy-framework genre at its introduction?
• misinformedThe load-bearing statistic — 'roughly 83% of Fortune 500 assets were tangible in 1975 versus ~90% intangible today' — is presented as a clean, uncontested fact via a single secondary citation, without stating measurement methodology. The widely-circulated version of this figure (traceable to the Ocean Tomo 'Intangible Asset Market Value' study) proxies 'intangible value' as market-cap-minus-book-value, which is sensitive to speculative multiple expansion and stock-market bubbles, not purely to genuine changes in asset composition — a methodological caveat the article does not mention despite resting its entire historical premise on the number.
  The Power of Strategic Centering — read next: Methodological critiques of the Ocean Tomo intangible-asset study specifically; broader critiques of using market-cap-minus-book-value as an 'intangibles' proxy in accounting/finance literature.
• uninformedCitations are underspecified throughout: the Journal of Organizational Behavior study on manager involvement gives no sample size, effect size, or definition of 'manage from a distance'; the Frontiers in Psychology moonlighting study names a sample size (324) but no effect size or engagement instrument; every leader-behavior percentage (33%, 43%, 53%, 56%, 59%, 90%+) is reported without a confidence interval, base rate, or description of how 'average team' leaders were sampled.
  How to Build a Superteam That Keeps Getting Better — read next: The original Journal of Organizational Behavior and Frontiers in Psychology papers directly; Ron Friedman's book 'Superteams' (Simon & Schuster, 2026), from which this article is adapted, for full survey methodology.
• illogicalSurvivorship bias in case selection: every illustrative organization (Thunder, Meta, Netflix, Amazon, Spotify, LinkedIn, Microsoft, Airbnb, Adobe, Estée Lauder, HubSpot, Keap, Basecamp, Haberman) is a documented success story for the practice it illustrates. No case of a team that experimented boldly and failed, admitted uncertainty and lost credibility, or had a hands-on leader who tipped into micromanagement is discussed, so each practice's downside risk and failure rate are invisible by construction.
  How to Build a Superteam That Keeps Getting Better — read next: Base-rate and survivorship-bias literature (e.g., Mlodinow, Taleb) applied to management case studies; accounts of experimentation cultures or hands-on leadership that did not pay off.
• incompleteThe involvement-vs-micromanagement line ('comes down to intent and impact') is asserted as the safeguard against practice 4 curdling into harmful over-involvement, but no behavioral test, warning sign, or transition point is given for a leader (or reader) to self-diagnose which side of the line they are on — precisely the ambiguity that makes 'Founder Mode' controversial elsewhere.
  How to Build a Superteam That Keeps Getting Better — read next: Situational-leadership and delegation literature (Hersey-Blanchard) for readiness-based criteria; critiques of 'Founder Mode' that specify when hands-on involvement curdles into harmful control.
• incompleteThe thesis that traditional leadership doesn't work with autonomous teams is stated as observed fact ('vi så i NAV') but never specified. Which behaviors of old-style leadership failed? What were the visible symptoms? Without examples, the claim functions as a slogan rather than an argument — appropriate for a welcome episode, but the show will need to deliver the substance.
  0) Velkommen til Heis
• incompleteThe argument that this kind of leadership requires experience 'from working in teams and with technology' is asserted but not defended. It excludes by implication leaders from non-engineering backgrounds; whether and why that exclusion is justified is not addressed.
  0) Velkommen til Heis
• incompleteThe 'every company is a technology company' claim is delivered as a closer without supporting argument. It is a common premise in contemporary tech-leadership discourse but the episode does not engage with the well-known counter-readings (that 'tech company' loses meaning when applied universally; that technology intensity is a spectrum, not a binary).
  0) Velkommen til Heis
• incompleteThe elevator metaphor implies vertical movement between hierarchical levels, but the show's stated commitment is to a team-model world where hierarchical levels are deliberately flattened. There is a latent tension between 'visit leaders on every floor' (which implies floors exist as distinct strata) and 'leadership that plays on the team' (which implies the strata are less salient). The episode does not address this tension.
  0) Velkommen til Heis
• incompleteThe Jobs analogy is named but not fully cashed out against its disanalogies. Jobs's reality distortion field was famously paired with cruelty, factional purges and product taste applied to consumer aesthetics. Larsen's framing is the opposite — toppdivisjon-ledelse runs on indre motivasjon, not fear; authenticity / easy-to-read-ness is the asset; the product is a public-sector welfare system. The conversation does not name these disanalogies, so the analogy carries more rhetorical work than it earns.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Read Walter Isaacson's Jobs alongside Tracy Kidder's Soul of a New Machine and Marc Andreessen-tradition writing on charismatic founder leadership to surface the disanalogies; for the NAV case specifically, read Cutler on 'institutionalized overload' to see what indre-motivasjon-based mobilisation can hide. Connects to the gap in the Skjærpe ep 17 extract on transformations that fail in the liminal phase.
• incompleteThe NAV transformation is described entirely from the inside by one of its architects. There is no counterfactual: comparable Norwegian agencies that did not transform similarly, post-Larsen reversion at NAV, what failed within NAV and why. The 'hagiography risk' the hosts flagged is real and unexamined.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Compare Skatteetaten, Statens Pensjonskasse, Helsedirektoratet trajectories during the same period; read the NAV-flow article in the user's library (Optimizing for Fast Flow in NAV) for the inside-but-different-author view; read the Skjærpe ep 17 extract for the immediate-successor's view from inside the system. Look for what the NAV transformation displaced or made impossible (e.g. casualties among legacy fagsystemer staff).
• incompleteThe 'common components are discovered, not designed' thesis is asserted with the NAV fakturering case as the load-bearing example, but the inverse failure mode (premature divergence — many verticals each solving the same problem badly because no one promoted the pattern to the platform) is acknowledged in passing ('we have capabilities in the platforms that strictly speaking are only needed one or two places ... it is a little behagelig that it got fixed over there') without being theorised. The position is one-sided.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Read the Wardley Mapping / pioneers-settlers-town-planners tradition for an explicit account of when components should be designed up front (the 'industrialised' part of the map). Read Cutler on 'horizontal team accountability' for how teams refuse to own platform-like problems they should own. The Vipps ep 18 extract may have a relevant view from the perspective of an organisation that did design infrastructure up front.
• incompleteThe 'easy to read' / authentic-leadership claim collides with the strategic-narrative claim. Strong strategic narrative is itself a construction; sustained reality-distortion presupposes some performance discipline. The conversation treats easy-to-read-ness and disciplined narrative as compatible without examining the tension. When does the constructed narrative cross into managed-impression territory, and what is the leader's check on that?
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Erving Goffman's Presentation of Self; Edgar Schein on the discrepancy between espoused theory and theory-in-use; Bent Flyvbjerg on narrative in megaprojects (where the same person both believes and constructs the future). The Cutler 'signals that look like decisions' thread is also relevant — for an easy-to-read leader, even contemplative musings can be read as commitments.
• incompleteThe inngangsbillett method is a personal description, not a teachable account. Larsen says he spends 'many hours a day' on craft and uses the hermeneutic-circle approach, but does not name which key terms, which structural maps, which sources, or how to know when the inngangsbillett is sufficient for a given fagdomene. The 'Fred George reads no books, he talks to authors' punchline gestures at one upper-bound technique but leaves the floor undefined.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Hubert Dreyfus's five-stage skill model (novice → expert) for a more precise grammar of 'how much do I need to know'; Cal Newport's deep work / deliberate practice tradition; the recent harness-engineering and AI-coding research extracted in this repo on what 'understanding a system' actually requires before AI can help you scale that understanding.
• uninformedThe conversation invokes Peter Senge's learning organisation as one of the three common denominators of Larsen's narrativer but does not interrogate how durably the organism-organisation framing has held up under real conditions over the 30 years since Fifth Discipline. There is a tradition of critique (e.g. Mintzberg on the messiness of organisational learning; recent operations-research literature on actual learning loops in software organisations) that the conversation does not engage with.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Mintzberg's Rise and Fall of Strategic Planning; Argyris on double-loop learning vs Senge's framing; the more recent DORA / Accelerate research on what kinds of learning actually correlate with performance — and what kinds (e.g. 'just keep adapting') do not.
• incompleteThe episode ends on Larsen's most quotable problem — moving from project mindset to outcome-driven verdistrøm-mindset — but does not specify what makes this so hard at Telenor specifically. Is it inherited governance? Board reporting cadence? Career incentives for people who have always shipped to scope? The hosts move on. This is the single most actionable place the conversation could have gone deeper.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Cutler on outcome-orientation and operating-system design; Marty Cagan's 'product team vs feature team' distinction; the Una Aamodt-Mathisen ep 10 extract (lede uten fasit) likely has direct material on the same problem at a different scale. The Vidar Moe ep 5 ('det eneste Vidar vil er å ha det lett') may have a relevant view on operating-model simplification.
• incompleteThe hagiography risk is structural: Truls worked for Larsen, Audun met him at a formative moment, both are visibly inspired. The format does not include any adversarial pressure. The episode is therefore best read as Larsen's self-presentation lightly facilitated by admirers — strong as primary source, weak as evaluation.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: For an evaluation lens, read external accounts of NAV's transformation (audit reports, Riksrevisjonen, Aftenposten / NRK coverage of NAV IT projects during the Larsen era), and look for counter-narratives in the Norwegian public-sector tech community. Compare to Holte ep 2 (the senior public-sector counterpart) for a different view of the same period.
• incompleteThe episode does not address whose work is *invisible* without a title — those without platform, conference speaker credibility, financial cushion, or social safety to speak controversially. Gorman names her own preconditions (cheap living in Drammen, ability to return to retail work) but does not extend the analysis to those whose preconditions do not hold. Title-less leadership in her account is universally legitimated but materially restricted.
  3) Christin Gorman leder uten tittel — read next: Read against Cutler on institutional overload and 'who gets to think' / power and space (TBM 413); against work on visibility and credit allocation in tech (especially gendered patterns); and against critiques of 'thought leadership' as a privilege economy. The Bekk/Kodemaker consulting ecosystem also deserves examination as the platform infrastructure that makes Gorman's mode possible at all.
• incompleteWhen is the formal title load-bearing? Gorman gestures at the answer (taking unpopular fights, decisive 'I'm not paying for that' moves) but does not theorize when title-less voice strictly cannot substitute. The carpenter renovation analogy works because the homeowners had authority — Gorman in a team without it cannot replicate that pattern.
  3) Christin Gorman leder uten tittel — read next: Read Morten Eikeland (Heis ep 4) 'det finnes alltid et hierarki' as the explicit counter-claim. Also read Una Aamodt Mathisen (Heis ep 10) 'lede uten fasit' as a complementary refusal-of-answer-key mode. The cross-cutting question: which leadership functions can be unbundled from title and which cannot?
• incompleteThe asymmetry of credit ('formal leaders take recognition when title-less leaders' ideas land') is named as a price Gorman is willing to pay, but not analyzed as a systemic problem. Who benefits from this asymmetry? It serves the formal leadership class — both the leaders who take credit, and the system that does not have to compensate the title-less.
  3) Christin Gorman leder uten tittel — read next: Read on credit assignment in collaborative work, on academic citation/recognition norms, on the labor economics of 'thought leadership' (Substack, conferences). Connects to Cutler on 'directly responsible individuals' from the recognition side.
• incompleteThe framing of public-sector dysfunction as 'budget growth instead of value delivery' is a strong claim presented anecdotally. The implicit comparison to private sector ('we are on the same team') under-acknowledges that private-sector alignment is also engineered and partial — shareholder vs. employee interests, sales vs. engineering, short- vs. long-term.
  3) Christin Gorman leder uten tittel — read next: Read Nils Brede Moe (Heis ep 9) on the AI-paradox and learning culture; read public-sector reform literature (NAV's 'optimizing for fast flow' is on the user's list). Also read industrial-organization work on aligned vs. misaligned incentives across sectors.
• incompleteImplicit premise about authority and self-correction ('I trust my own thinking only because I have to argue for it') is asserted as autobiographical but generalized. The argument that formal authority degrades judgment by removing resistance deserves more scrutiny — many formal leaders maintain rigorous self-criticism, and many title-less voices ossify.
  3) Christin Gorman leder uten tittel — read next: Read on epistemic humility and authority (Annie Duke on 'Thinking in Bets' framing of belief-updating; Greger Teigre Wedel (Heis ep 12) 'når sjefen har svaret' on the inverse problem). Also Beck on Tidy First / TDD as institutionalized self-correction independent of authority.
• uninformedThe episode does not engage with how AI coding agents change the picture of who counts as a 'delivery-grounded' practitioner. Gorman's 'basis' criterion is rooted in writing code yourself — but what counts as that basis when much code is now generated and curated? The 'AI replaces ticket-converters' framing is correct but stops short of asking what the basis becomes.
  3) Christin Gorman leder uten tittel — read next: Read Heis ep 11 (Vilde Opsal / Anders Sveen AI special) and ep 13 (Tobias Torrissen on code quality + AI); read the user's Kent Beck Tidy First and Claude Code material — what is the 'basis' equivalent when the medium shifts?
• 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.
• incompleteCultural specificity is unexamined: Wedel never tests whether 'when the boss has the answer, the rest stay silent' depends on Norwegian (or Nordic, or hierarchical) defaults. In flatter or more confrontational cultures, the chilling effect may be weaker — or it may show up differently (silent disagreement vs. silent compliance).
  12) Greger Teigre Wedel: Når sjefen har svaret, tier resten — read next: Cutler TBM 423 on undiscussables (which treats power-asymmetry-creating-silence as general, not culturally specific) and Edmondson on psychological safety across cultures. Also Hofstede / Trompenaars on power distance dimensions in Nordic vs. other workplaces.
• incompleteDecision criteria for posture-switching are underspecified. Wedel says leaders should choose among coaching, deciding, hands-on, whiteboarding, director postures situationally — but he names only one explicit trigger (the over-coaching failure mode that calls for cutting through). When to take which posture is left as 'judgment'.
  12) Greger Teigre Wedel: Når sjefen har svaret, tier resten — read next: Kent Beck on tidy-first vs. mess-first decision rules; Heifetz on adaptive vs. technical work; Cutler's TBM 418 on campfires/trails/quests as posture-selection frame.
• incompleteThe interaction between explicit mode-switching ('lederhatten av') and team-level psychological safety is asserted but not unpacked. Saying 'we're in whiteboarding mode now' presumably only works if the team trusts that the leader will actually honour the signal — which is itself a function of trust built elsewhere.
  12) Greger Teigre Wedel: Når sjefen har svaret, tier resten — read next: Edmondson on psychological safety as accumulated track-record; Schein on rituals and their preconditions; Pocock's 'alignment is not AFK' point about why alignment work must be live, not formal.
• incompleteAI-as-amplifier is asserted in both directions (good practice → better; bad practice → worse) but the magnitude of asymmetry is not addressed. If AI amplifies bad practice faster than good, the policy implication ('defer AI until guardrails exist') may be stronger than Wedel states.
  12) Greger Teigre Wedel: Når sjefen har svaret, tier resten — read next: DORA 2025 detailed findings; the Dave Farley YouTube series Wedel mentions; any empirical work on AI adoption velocity vs. defect rates.
• incompleteThe six product-org first principles are alluded to but not enumerated in the conversation. Only the first (deep user/customer connection) is discussed.
  12) Greger Teigre Wedel: Når sjefen har svaret, tier resten — read next: stuff.greger.io blog series on product organisation first principles.
• 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 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.
• incompleteThe entire generalization from football to the workplace rests on a single anecdotal pair (Solbakken/Ødegaard) plus the author's own unsupported claim to have observed 'begge ledertypene og begge lederfellene' in professional life. No data, case study, or even a second concrete workplace example is offered. The football analogy is evocative but N=1, and football coaching (a role with a hard, external rule against playing) may transfer only weakly to workplace leadership, where the boundary the author is trying to recreate voluntarily does not exist by default.
  Leder du fra sidelinjen – eller ute på banen? — read next: Empirical work on leader involvement/distance and team outcomes — e.g. the Journal of Organizational Behavior finding cited in extract-hbr-superteam (leaders who work alongside their teams report more energy and effectiveness than those managing from a distance) — to see whether 'range' or 'proximity' is actually the better-supported prescription.
• incompleteThe article asserts that taking back delegated work 'can look effective short-term but creates dependency long-term' as a near-universal rule, without ever addressing the cases where a leader stepping back in genuinely is correct — a team member in over their head, a safety-critical error in progress, a crisis requiring the leader's specific expertise. It offers no way to distinguish harmful takeover from warranted intervention, leaving a real tension with the corpus's other position (extract-pincus-hidden-pattern-successful-products#p22-p23) that the best leaders stay maximally close to execution and treat routine 'micromanagement' as the correct default until it becomes physically impossible.
  Leder du fra sidelinjen – eller ute på banen? — read next: extract-hbr-superteam#p6 for a sharper version of the same distinction (involvement builds capacity vs. micromanagement creates dependency — the difference being intent and impact); extract-pincus-hidden-pattern-successful-products for the opposing view that proximity/'micromanagement' is usually the right default for founders and product leaders.
• incompleteVendor incentive distortion in the 'whole ecosystem is accelerating' claim
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: DORA 2025 and the Stanford/Microsoft developer-productivity studies on AI's actual code-quality effects; Gergely Orosz on enterprise sales-cycle compression; Marc Andreessen's classic 'why software is eating the world' for the prior pattern. For the contrarian counterweight: Gary Marcus and Ed Zitron on whether the AI productivity story is being narrated by the people selling it.
• incompleteThe marginal-cost claim is accounting-incomplete (Beck flags it; Grinich doesn't return)
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Anything in your Kent Beck file on TCR and scope-of-done (this is exactly the conversation about plausible deniability and shrinking scope); Lorin Hochstein on operational complexity; the Böckeler harness-engineering extraction in this repo (the 'gap between running system and trusted system' is the harness-engineering surface). The Adam Tooze / Brad DeLong line on 'productivity gains that don't show up in the statistics' is the macroeconomic complement.
• incompleteThe 'descaling of software' counter-trend is named by Beck and left hanging
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Steve Yegge on vibe coding; Gene Kim's vibe coding series; Simon Willison on the 'no-coder using LLMs to build real software' phenomenon; the Schoening agency-over-skills extraction in this repo (the agency thesis is the descaling-friendly side of this tug of war). Honest framing: Beck's craft instincts and Grinich's institutional instincts pull in opposite directions; you may have to choose.
• incompleteGrinich's 'industrialization phase' analogy launders externalities
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Tooze on energy transitions; the IEA's compute-electricity projections; the literature on whether the late-19th-century industrialization actually 'cleaned up' or just exported externalities. For Kjetil specifically: this is the systems-thinking lens — feedback loops, stocks/flows, who absorbs what — applied to the rhetoric of inevitability.
• incompleteWhat changes about Beck specifically — the craft thinker in this regime
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Beck's own recent Substack posts (Tidy First, the 'starving genies' piece, 'forest thinning'); your highlights on Beck for where he reframes craft for the agentic era; Hickey's 'Simple Made Easy' as the substrate craft argument; Ousterhout's complexity work. The persona-relevant cross-thread: this is where Kjetil's 'fragility of ideas' hidden layer touches the AI transition — if the craft of attentive code-reading is the protected attention surface, what protects it now?
• incompleteWhat does the 'itchy brain' protect against, exactly?
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Pressfield on Resistance; Cal Newport on deep work degradation under tool proliferation; the David Whyte/Maria Popova line on the difference between making and consuming; the persona's Bailey/Hyperfocus annotations on what attention needs in order to do anything. This is where the persona's hidden layer (fragility of ideas) and the episode's title concept (itchy brain) collide — and it is the most productive question the episode opens.