1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs

Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · podcast · 2025-10-13 source ↗ Reader 🖥️

mixed · narrative-argumentative — long-form interview in which the guest's autobiographical arc (systemutvikler → Tandberg/Cisco strategist → NAV IT-direktør → Telenor teknologi-leder) carries an argumentative spine about strategic narrative, organisational design and the discovery of common components — Hosts Truls Jørgensen and Audun Fauchald Strand interview Torbjørn Larsen — the first real interview after the welcome episode. The conversation is intimate: Truls explicitly worked for Larsen at NAV ('da vi jobbet sammen i den perioden i NAV. 2018-2019') and asks teacher-student questions ('Hvordan får du til den inngangsbilletten?'). Hosts ask short questions; Larsen answers at length. Tone is collegial-reverent — the hosts call his storytelling 'the closest we come to Steve Jobs' and Larsen accepts the framing rather than disclaiming it. The conversation moves through four arcs: (1) becoming a leader and the discovery of strategic narrative as a leadership tool, (2) bridge–engine-room disconnect and the inngangsbillett, (3) organising for continuous value creation (value streams, matrix, reverse Conway, common components as discovery), (4) opportunity-driven strategy execution at Telenor and the project-mindset trap.

Structure

Key terms

• strategisk narrativ (strategic narrative) Strategy & Direction-Setting
  A concrete, evolving story about what the organisation is trying to become — including organisational form, architecture and value-creation thesis — that is personally believed by the leader and used both to orient daily decisions and to attract followers via indre motivasjon. Not a fasit; develops as you learn. Must avoid the failure mode of 'ulle generelle ambisjoner som kunne passet inn i en visningsmappe'.
• reality distortion field Strategy & Direction-Setting
  Used by Truls (not Larsen) to characterise Larsen's storytelling effect: the ability to create a perceptual state in an audience where the future being described becomes vivid enough to draw tears and goosebumps. Larsen accepts the framing and reframes it as the construction of strategic narrative he personally needs and that demonstrably works on others.
• toppdivisjon av ledelse (top-division leadership)
  Larsen's ranking of leadership techniques: the lowest divisions are intimidation ('det berømte balltre') and authority ('det står i den boka der'); the top division is mobilising people through what they want to be part of — indre motivasjon. 'Lite som slår indre motivasjonen'.
• indre motivasjon (intrinsic motivation) Intrinsic Motivation & Making
  The only durable basis for getting people to follow durable change; ranked above all other 'leadership techniques'. Recurs at the platform-governance level: NAIS was made attractive enough that using it became intrinsically motivated, not mandated.
• bro og maskinrom (bridge and engine room) Technology Leadership (Heis)
  The two organisational floors that have come apart in many virksomheter: ledermøter and strategy processes (bridge) versus what is actually happening on the daily delivery floor (engine room). The diagnosis-pattern Larsen sees across industries.
• heis (the elevator) Technology Leadership (Heis)
  Reflected here as the host's own framing — Truls explicitly names the show's hypothesis: the koblingen mellom bro og maskinrom requires people who can move between floors. Larsen accepts this and reframes it as leading 'from the middle of the organisation, not from the top'.
• inngangsbillett (entry ticket) Hands-On Leadership & the Pendulum
  Enough technical depth in a fagdomene to be relevant in the conversation — not the smartest in the room, but credible enough that experts engage. Acquired by the hermeneutic-circle method: key terms, structure of the field, recurring engagement. Necessary for any leader who wants to (a) attract good engineers, (b) develop strategic narrative grounded in reality, (c) keep the bridge–engine-room translation working.
• hermeneutisk sirkel (hermeneutic circle)
  From pedagogy: the way one learns a field by acquiring key terms and structure, which then makes deeper reading productive, which in turn refines the terms — a self-reinforcing loop. Larsen uses it to describe how a leader maintains 'inngangsbillett' across many technical domains without becoming a specialist in any.
• organisasjonen som lærende, tilpasningsdyktig organisme
  Senge-derived framing that recurs in all of Larsen's narrativer as the first of three common denominators. The opposition is the Weberian / military hierarchy that was good for sikker og stabil drift but 'jævla vanskelig å endre på'.
• verdistrøm (value stream) Value Streams & Verticals
  The unit of organisational design at Telenor — cross-functional teams sitting in shared problem-spaces, target-set on outcomes for an identifiable målgruppe. Vertikale verdistrømmer are market-facing; horisontale exist only to accelerate verticals. Telenor: ~150 teams in 17-18 verdistrømmer.
• vertikal / horisontal verdistrøm Value Streams & Verticals
  Vertikale are the customer/market-facing streams (internet at home, entertainment-where-you-are, safe-and-secure-family) — where revenue and feedback live. Horisontale are platforms / shared capabilities. The discipline: 'no horisontal can exist unless it accelerates the vertical verdiskaping in the market'.
• kompetansekling / people-and-competence
  The second matrix dimension at Telenor — competence-aligned groupings (software/data/platform engineering, network engineering, marketing/sales) that own personalansvar, rekruttering, faglig og karriereutvikling. Designed to address the standard objection to cross-functional org: career path and faglig fellesskap.
• felleskomponenter oppdages, ikke designes (common components are discovered, not designed) Platform Engineering
  The episode's most quotable thesis. Solve problems in verticals close to customers; let the patterns that turn out to be genuinely shared 'gravitate down into a platform'. The opposing pattern — designing ambitious common components up front — produces shadow solutions and bottlenecks because the contexts are more different than assumed (NAV fakturering: et velskapt barn vs en terminal kreftpasient).
• religionskrig (religious war)
  The internal NAV-era conflict over whether common components should be designed or discovered. Larsen aligns himself firmly with the discovery side; the term acknowledges that this is contested terrain inside large engineering organisations.
• reverse Conway Sociotechnical Architecture
  Design the architecture first, then place the organisation on top of the architecture you want. The exercise's purpose: 'å ta bort koordineringsbehov i så stor grad som mulig'.
• golden path / kul-luxverk Golden Path
  Larsen's NAV-era pattern: never mandate platform use; instead build the platform so good that going elsewhere is costlier and slower. Adoption then runs on indre motivasjon. Recognises 'edge cases' where teams should be allowed to solve outside the platform — and that this constrains the platform from absorbing them as 'must-haves'.
• Solan Gunnerud-måten ('hva skal jeg transformere i dag?')
  Self-deprecating allusion to the Caprino character — Larsen knows he can be misread as someone who thinks every situation needs transformation. He explicitly disclaims this even while acknowledging that 'grunnverslag, selvsagt er det det'.
• opportunity (efficiency / growth / risk-and-compliance)
  Telenor's strategy-execution unit. ~100-150 business opportunities classified into three types: efficiency, growth (new revenue / innovation), risk/compliance. Owned by value streams; some owned by people-and-competence. The conscious move away from project mindset toward outcome-based target-setting.
• order takers vs læringsarenaer
  The unresolved transformation problem at Telenor: moving teams (and value streams) from receiving requirements ('order takers') to becoming learning arenas where priorities are set by what they discover in tett dialog with target groups. Larsen names this as the current hardest organisational problem.
• NAIS Platform Engineering
  NAV's developer platform (not named with full expansion in the transcript but clearly NAIS — 'NAV Application Infrastructure Service'). The reference case for the golden-path / indre-motivasjon pattern in platform governance.
• NOVA
  Telenor's internal platform — multi-hyperscaler, supporting private cloud — running '200-400 deploys per month to prod'. Used by Larsen as the proof-point that the operating-model design produces real change rate.
• joggeskoene på (put your running shoes on) Hands-On Leadership & the Pendulum
  Idiomatic call for ledere to get out of meetings and into the organisation. Cannot fix the bridge–engine-room disconnect 'ved å sende ut dekreter'. Borrowed by Larsen 'fra dere' (from the hosts).

Propositions

• explicitcorroboratedReal lifestyle-change in an organisation requires a strong strategic narrative — not because storytelling is stylistically nice but because narrative is the only tool that mobilises people through what they want to be part of, which is the only durable form of follow-through.conf: high
  supports ←Strategi som regi i møte med teknologi: En samtale med Walter Qvam · p14 — Both claim narrative/storytelling, not analysis, is the mechanism that actually mobilizes an organization behind a strategy.
• explicitThe strategic narrative is dels something the leader personally needs — leadership is not survivable on work that does not feel important, valuable and value-creating to the leader herself.conf: high
• explicitLeadership is context-dependent, not all situations require transformation; many ledergrupper would benefit from an early conversation about whether they actually have an appetite for the kind of change they are claiming to undertake.conf: high
• explicitcorroboratedThe toppdivisjon of leadership is mobilising people through intrinsic motivation; threats (the famous balltre) and formal authority are lower divisions that work less durably.conf: high
  supports ←Strategi som regi i møte med teknologi: En samtale med Walter Qvam · p17 — Qvam's 'getting people to want to do it' as the real starting point matches Larsen's claim that the 'top division' of leadership is mobilizing through intrinsic motivation rather than threats/authority.
• explicitBeing easy to read — including being a bad liar — is itself a leadership asset, because authentic legibility makes the leader easier to orient to.conf: high
• explicitThe recurring pathology across the industries he has consulted in is a disconnect between bro (ledermøter / strategy processes) and maskinrom (the floor) — strategy that does not capture what must happen on the floor and floor work that does not connect to strategic ambition.conf: high
• explicitClosing the bridge–engine-room gap requires specific people who can function at many levels of the organisation — the hypothesis behind calling the show 'Heis'.conf: high
• explicitModern leadership happens 'from the middle of the organisation, not from the top' — mobilising delivery is positional, not just communicative.conf: high
• 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.conf: high
• explicitThe Weberian / military-derived functionally specialised hierarchy is well-suited to sikker og stabil drift in stable environments but unfit for dynamic and unpredictable conditions; the choice between machine and organism organisation is forced by environment, not preference.conf: high
• explicitWhat used to require a gigantic moon-landing project with a couple of hundred consultants is now needed daily — value streams of cross-functional teams replace projects as the organisational form for continuous change.conf: high
• explicitThe reality test for value-stream design: a customer or partner brought into the organisation should recognise where their needs are produced; if they only see the divisions, the design is wrong.conf: high
• explicitHorisontale verdistrømmer / platforms can only exist if they accelerate verdiskaping in vertikale (market-facing) verdistrømmer — measured through leading indicators of innovation speed, time-to-market and time-to-value in the verticals they serve.conf: high
• explicitGood common components are discovered, not invented — solve problems in verticals close to customers, then let patterns that turn out to be genuinely shared gravitate down into a platform.conf: high
• explicitThe idea of an ultimate kostnadseffektiv felleskomponent fails because the contexts inside a large organisation are more different than assumed — NAV's fakturering had to handle both a family with a newborn and a terminal cancer patient, and the difference matters.conf: high
• explicitdevelopedReverse Conway — design the architecture first, then place the organisation on top of the architecture you want — is the right sequencing because the exercise's purpose is to remove coordination need.conf: high
  extends ←Beyond Autonomous Teams in Software Product Development · p10 — Extends reverse-Conway sequencing (design architecture first, then place organization on top) with a networked/nested alternative topology for coordination without hierarchy traversal.
• explicitPlatform governance at NAV / NAIS worked because NAIS was never mandated; the team built a 'kul-luxverk' so good that going outside cost more and was slower, so teams chose it through indre motivasjon.conf: high
• explicitValue-stream organisations need duplicate solutions tolerated as the cost of doing business; the discipline is in the culture and handlingsrom to refactor over time, not in preventing the duplication.conf: high
• explicitTelenor's matrix separates leveranseoptimalisering (value streams, with verdistrømsleder + lead architect + lead product lead but no personalansvar in principle) from kompetanseutvikling (people-and-competence dimension, where personalansvar, rekruttering and karriereutvikling sit).conf: high
• explicitThe current hardest organisational problem is moving from project mindset to outcome-driven verdistrøm-mindset — making verdistrømmer (and the teams within) into læringsarenaer and innovasjonsarenaer rather than order takers.conf: high
• explicitThe biggest obstacle to omstilling in most virksomheter is not technology but 'legacy leadership og mindset' — leaders who have not constructed a new leader-identity for adding value in cross-functional, outcome-driven settings.conf: high
• explicitCommunication and collaboration are increasingly load-bearing soft skills because the spaces where humans still add value are precisely the cross-cutting ones machines do not yet inhabit — repetitive work is migrating to machines.conf: high
• explicitWithout a forestilling about where you want to be in 3-4 years, you cannot know which step to take tomorrow — vision is the precondition for tactics, not their decoration.conf: high
• explicitThe strategic narrative is not a fasit but a developing object — innsikten avler mer innsikt — and the right metaphor is the hermeneutic circle from pedagogy.conf: high
• 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.conf: high
• 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.conf: medium
• explicitHe is grunnverslag (in his basic disposition) someone who reaches for transformation — the Solan-Gunnerud joke is on himself — and this can be misread as naïve belief that the strategic endgame is reachable tomorrow.conf: high
• explicitBig career outcomes have a luck component he is comfortable admitting — choosing Oracle over Google on the 2003 MIT Silicon Valley trip is his canonical self-deprecation about taste.conf: high
• explicitThe phenomenon being analysed (Larsen's reality distortion) is real from the receiving side — the same effect Audun felt over coffee at Supreme in 2014.conf: high

Arguments

Narratives

• Telenor as 180-year engineering tradition: Telegrafverket grunnlagt i 1885 (Larsen rounder til 'snart 180 år'), Televerket → Telenor 1994. Larsen frames himself as coming home to build strong ingeniørmiljøer after a period when many organisations underweighted deep technical understanding ('the balance between having peiling and buying peiling').
  → Sets the engineering-craft identity that frames the entire conversation; Larsen is positioned not as outsider executive but as someone returning to a craft tradition.
• Telenor Mobil in the early 2000s: Truls remembers Daniel, the smartest engineer on the entire ruite, who would try to explain string theory to the others and later left to become a rocket scientist.
  → Confirms Telenor as historically an environment that attracted craft-deep engineers; functions as a token of shared culture between hosts and Larsen.
• Becoming a leader: starts as systemutvikler in Forskningsparken in the early 90s (after some years in Forsvaret); team-lead, then leads a small utviklingsmiljø in a produktselskap. Goes into consulting. Late-30s: leads strategy + IT-operasjon at Tandberg through hypergrowth 2005-2009, scaling 30 offices in 20 countries to 60-70 offices in 40-50 countries, ending in Cisco's acquisition for ~$3B (largest Oslo Børs transaction at that point). 'Came in as the strategist, drew the maps, worked with the people' and was then invited to lead — 'a small leap of faith'.
  → Establishes Larsen's leader-as-strategist origin; the late and craft-derived path matters because it explains why the strategic-narrative-as-personal-need framing reads as authentic.
• Father was a tailor (skredder). Larsen has 'always carried that image' of software engineering as a håndverk, a fag — you make something people become glad i.
  → Roots the craft framing in personal biography; explains why the craft / inngangsbillett discipline is constitutive of his identity rather than instrumental.
• Ringen Kino, NAV era: Larsen, relatively new IT-direktør, presents his vision for where NAV is going and how to get there. People in the audience get tears in their eyes and goosebumps. Truls explicitly compares the moment to Steve Jobs's reality distortion field.
  → The canonical moment that triggers the Jobs analogy and frames the rest of the episode's analysis of narrative as load-bearing.
• Supreme coffee 2014: Audun and Larsen meet for coffee; Audun's øyne 'glitret' afterwards. Later (2018-2019) Truls is working closely with Larsen at NAV — 'sporadic but tight communication', 'flinke på å la inn oss mot samme ting', 'almost intuitive understanding of who was going to do what'.
  → Anchors the conversation in lived working relationships; the hosts are not interviewing from outside the case but from inside it. Justifies the analytical confidence elsewhere in the episode.
• Fakturering ved NAV: the agency learned the harde veien that paying out money to a family with a newborn vs to a terminal cancer patient are very different contexts — even the ostensibly identical 'fakturering' use case has irreducibly different shape.
  → Concrete case for the 'discovered, not designed' thesis. The example is striking enough to do real argumentative work without explicit elaboration.
• Religionskrig in NAV-tiden over felleskomponenter: the question of whether common components should be designed or discovered became contested terrain. Larsen aligned firmly with the discovery side and stands by it now.
  → Acknowledges that the position has costs; this is not the painless org-design answer it might appear.
• NAIS golden path: at NAV / NAIS they never said 'you must use NAIS'. Instead they 'walked up the path' and built kul-luxverk — capabilities so good that going outside was costlier and slower. The result was adoption through indre motivasjon, not mandate.
  → The foundational anecdote that connects the toppdivisjon-of-leadership claim (indre motivasjon) to platform governance. Most quotable operating principle in the episode.
• NOVA platform at Telenor: more complex setup than NAIS (multi-hyperscaler, supporting private cloud), '200-400 deploys per month to prod', every config / policy / code change counted. Develops in dialogue with developers and product teams.
  → Quantitative proof that Telenor's value-stream + reverse-Conway design produces real change rate. Bridges from NAV-era claims to current practice.
• Posten phone call: Petter Børre, leder of Posten, called Larsen 5-6 years ago to learn from the reise Larsen had been on at NAV. Larsen notes the felles nendere with what they later did at Telenor.
  → Establishes that NAV's transformation became reference architecture for at least one other major Norwegian transformation; supports the transferability claim.
• Hva er du til for? Larsen says: 'I was not at NAV, and I'm not at Telenor, to drive IT. We are here to deliver on verdiskaping in IT, and continually better verdiskaping.' Verdiskaping is a function of need-understanding, verdiforslag, tjenester, leveransepraksiser and tools — not technology alone.
  → Restates the operating principle that prevents the IT organisation from existing for itself; supports the leading-indicator discipline for platforms.
• Joggeskoene-på: Larsen acknowledges the host's framing — leaders need to take the running shoes on, get out into the organisation. 'Det utfordrer veldig mange ledere'.
  → Names the practical / embodied discipline of leading from the middle; bridges from abstract claim to concrete leadership behaviour.
• Solan Gunnerud joke on himself: 'Hva skal jeg transformere i dag?' Larsen knows he can be misread as someone who thinks every situation needs transformation; he disclaims this even while admitting it is his basic grunnverslag.
  → Self-aware acknowledgement of the failure mode of the storytelling-as-superpower framing; protects the rest of his argument from accusations of universalism.
• Fred George reads no books, he talks to the authors: Larsen's punchline at the end of his hermeneutic-circle discussion of how he keeps up.
  → Names the upper limit of his inngangsbillett method — at some point the right move is direct access to the source-thinkers — and signals shared community membership with Truls (Fred George being a well-known XP / programmer-anarchist figure in the Norwegian agile community).
• MIT Sloan Silicon Valley study trip, winter 2003/04: stayed near Harvard Square ('omtrent oppfunnet av Facebook'), visited a series of companies. Forced to choose between visiting an unknown 100-person garasjefirma with a weird name ('Google was rett og slett ikke så veldig forlokkende') or a really cool place that had moved into a new headquarters that looked like a database server. Chose Oracle. 'Ikke et så fett valg i ettertid.'
  → The episode's closing self-deprecation. Restores epistemic humility for the leader credited with NAV's digital transformation; lets him close on a beat that re-grounds the reality-distortion framing.

Questions addressed

• ✅ What specifically warrants comparing Larsen's leadership to Steve Jobs?
  Not consumer-product taste but the construction of strategic narrative so concrete and personally believed that it produces a reality-distortion effect in audiences — visible at Ringen Kino during NAV and at coffee at Supreme. Larsen reframes this as a teachable discipline (narrativer with three structural common-denominators) rather than charisma.
• ✅ Why call the show 'Heis'?
  Truls names the hypothesis explicitly: the koblingen mellom bro og maskinrom requires people who can move between organisational floors. Larsen accepts and adds the positional refinement: modern leadership happens from the middle, not from the top.
• ✅ How does a leader stay technically credible without becoming the specialist?
  Through the hermeneutic-circle method: master key terms and structure of a field, sustain daily engagement with podcasts and articles, accept that specialists will run circles around you on Kubernetes but you can still hang on the corners and occasionally challenge. The goal is the inngangsbillett, not dominance.
• ✅ How should a large organisation be organised for continuous transformation?
  Value streams (cross-functional, market-facing where possible) as the primary leverage, with a matrix where people-and-competence owns career/personalansvar; verticals are market-facing, horisontals exist only to accelerate verticals; reverse Conway sequences architecture before organisation; common components are discovered, not designed; platforms work via golden paths.
• ✅ When is a transformation appropriate?
  Not always — leaders should have an early conversation with their team about whether this is a two-degree course correction or something larger, and whether the team has the appetite. Calling everything a transformation is a known failure mode (the Solan-Gunnerud trap Larsen flags on himself).
• ✅ How do platforms / common components actually work without becoming bottlenecks?
  Solve in verticals first (close to customers, fast feedback). Tolerate duplicates and refactor over time. Promote to platform only when the pattern is genuinely shared, and govern with leading indicators that show the platform accelerates the verticals. Never mandate — build a golden path.
• ✅ What is Telenor's strategy execution unit?
  Business opportunities (~100-150 of them, classified into efficiency / growth / risk-and-compliance), owned by value streams. The goal: outcome-driven target-setting rather than to-do-list-driven project execution.
• ✅ Does the value-stream model need tech leadership at higher levels?
  Yes — every value stream has a verdistrømsleder, a lead architect and a lead product lead. Some have more leader profiles than they probably need (a legacy from divisions/hierarchies). Personalansvar in principle lives in the people-and-competence dimension, not in the value streams.
• ✅ What is the largest obstacle to omstilling in most virksomheter?
  Legacy leadership and mindset — leaders who have not constructed a new lederidentitet for adding value in cross-functional, outcome-driven settings. Secondary: difficulty of cross-fag collaboration.
• ⭕ Can the conditions of value-stream learning ('læringsarenaer, ikke order takers') be engineered, or do they have to emerge?
  Larsen names this as the current hardest unsolved problem at Telenor — the move from project mindset to outcome-driven verdistrøm-mindset. He does not claim to have solved it; describes ongoing target-setting work and the difficulty of giving board-level updates while not bootstrapping the teams into commitment-mode.
• ✅ What does Larsen think of the 'closest to Steve Jobs' framing — is he embarrassed?
  He is past being embarrassed by it. He accepts the framing and immediately reframes it: leadership is context-dependent, and the storytelling capability is a tool for transformation contexts specifically — not all situations need it.
• ⭕ How does Larsen actually develop these narratives — does he write, rehearse?
  He treats it as a developing object (hermeneutic circle) and emphasises concrete structural elements rather than writing/rehearsal mechanics. The hosts ask explicitly about technique and Larsen redirects to substance ('det høres ut som om det er noe litt sånn bibelskoginerisk' — he disclaims the bibelsk framing and pivots to the structural-narrative components). The question of his actual writing/rehearsal practice is not answered.
• ⭕ What about the costs / casualties / failures of the NAV transformation?
  Not addressed. The episode is hagiographic about NAV — the only failure mentioned is the religionskrig over felleskomponenter, framed as a position Larsen won. Cost to displaced legacy staff, alternatives not chosen, what-could-have-been-cheaper are not in the conversation.

Gaps

• 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.
  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.
  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.
  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?
  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.
  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.
  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.
  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.
• illogicalLarsen holds two positions that are in tension: (a) modern leadership happens from the middle, not the top, and (b) the leader must construct a strategic narrative that pulls the organisation toward a 3-4 year endgame. If leadership is from the middle, where exactly is the strategic narrative being constructed and projected from? The conversation treats these as compatible — the strategic leader rides the elevator down from a not-quite-top position — but the geometry is not specified.
  Read next: Henry Mintzberg's 'crafting strategy' for an account of emergent strategy from the middle; Roger L Martin's 'play to win' for a counter-position arguing strategy has to be top-set. Worth a syntopical pass against ep 15 (Kari Olrud Moen on strategi tydelig og skråsikker), which from its title suggests the opposite position.
  closed byStrategi som regi i møte med teknologi: En samtale med Walter Qvam — Qvam's leader-as-'regissør'/orchestra-conductor framing offers a compatible way to hold Larsen's two positions together: the leader authors and holds the strategic narrative (top-driven authorship) while deliberately keeping delivery power with 'the orchestra' — the organization/middle. This is a partial, vocabulary-level resolution rather than a direct engagement with Larsen's claim, so it should be read as reconciling rather than definitively settling the tension.
• 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.
  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.

Related documents

• DevOps Topologies
  Platform Engineering Sociotechnical Architecture Team Topologies Value Streams & Verticals
• 14) Øystein Ulseth pendler mellom å lede og levere
  Hands-On Leadership & the Pendulum Intrinsic Motivation & Making Sociotechnical Architecture Technology Leadership (Heis)
• How Platform Engineering Using Golden Bricks Can Enable Fast and Smooth Delivery
  Golden Path Platform Engineering Sociotechnical Architecture Team Topologies
• Architecture Modernization: Aligning software, strategy, and structure • Nick Tune • CodeCrafts 2024
  Sociotechnical Architecture Strategy & Direction-Setting Team Topologies Value Streams & Verticals
• Beyond Autonomous Teams in Software Product Development
  Sociotechnical Architecture Team Topologies Value Streams & Verticals
• Sociotechnical Architecture as Enabler of Product Thinking
  Sociotechnical Architecture Team Topologies Value Streams & Verticals
• Optimizing teams: A dual perspective on Team Topologies
  Sociotechnical Architecture Team Topologies Value Streams & Verticals
• Strategi som regi i møte med teknologi: En samtale med Walter Qvam
  Intrinsic Motivation & Making Strategy & Direction-Setting Technology Leadership (Heis)
• TBM 390: Governance by Principle, Not by Template
  Platform Engineering Sociotechnical Architecture Team Topologies
• Team Topologies: Organizing Business and Technology Teams for Fast Flow
  Platform Engineering Sociotechnical Architecture Team Topologies