Technology Leadership (Heis)

Leadership that moves fluently between organizational floors — executive bridge and delivery engine room — translating between domains while staying credibly connected to the craft.

Also known as: teknologiledelse (technology leadership), teknologiledelse, Heis, heis (the elevator), kunsten å ta heis (the art of taking the elevator), heis-fører (elevator operator), ulike etasjer (different floors), bro og maskinrom (bridge and engine room), T-ledelse (T-leadership), teammodellen (the team model)

How authors use it

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

Documents (10)

• 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.
• Strategi som regi i møte med teknologi: En samtale med Walter Qvam Verdistrategipodden (Tale Skjølsvik interviewing Walter Qvam) · 2026-08-01 Reader 🖥️
  Strategy is best understood not as a detailed analytical plan but as an ambition or aspiration compressed into a believed, narratable direction that a leader — acting as a director/orchestra-conductor rather than a soloist — uses to make an organization's culture willing and able to execute; and because plans now have a shorter shelf life than ever, strategic success increasingly depends on combining proactive bet-making with the honesty and speed to detect weak signals and respond to the unforeseen (robustness), rather than treating proactive and reactive strategy as opposites.
• 18) Vipps: Fra app til verb til nordisk infrastruktur Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-06-01 source ↗ Reader 🖥️
  Vipps's evolution — from a 2015 DNB-internal P2P app built under an IT freeze, through three successive mergers (MCash 2017, BankAxept 2018-ish, MobilePay 2023), three markets, and a near-decade of platform rewrites — shows that becoming Nordic critical infrastructure is less about visionary architecture than about repeatedly choosing momentum over perfection: small monoliths first, big-bang cut-overs when integration matters more than iteration, and a relentless willingness to throw away technology, organisation and product features that no longer serve the next size of company.
• 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.
• 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.
• 13) Tobias K. Torrissen om kodekvalitet, konferanser og AI Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-03-16 source ↗ Reader 🖥️
  In the age of LLM-generated code, the durable value of an engineering leader is not in writing code but in cultivating the engineering practices, explicit design discipline, and craft community that determine whether a long-lived system can be understood, maintained, and adapted — and code quality, understood as 'obvious over clever,' matters more in this era, not less.
• 6) Catherine Janson og Kjerstin Wester: The power of two! Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2025-12-01 source ↗ Reader 🖥️
  {'english': "Two-person leadership — 'the power of two' — is not a designed pairing or a formal structure but an emergent, trust-based working relationship between leaders whose strengths are complementary and whose explicit rule is 'if something feels off, say it once'; when it works it produces psychological safety, faster organizational metabolism (one leader pulls long-arc direction while the other lands structure and detail in real time), and a refusal of the leader-as-individual-hero default. The conditions that make it possible are not personality alone but a culture of explicit non-competition, mutual fremsnakk (talking each other up in their absence), and willingness to operate fluidly across hierarchical configurations — over, under, sideways — without the relationship breaking. The episode is also, by demonstration, an argument that this dyadic leadership is itself a competence layered on top of conventional leadership skills (listening to technologists, translating across disciplines, setting OKR-style direction, accepting that mistakes will happen) — and that you discover the pairing rather than plan it.", 'norwegian': "Toleder-relasjonen — 'the power of two' — er ikke et planlagt par eller en formell struktur, men et fremvokst, tillitsbasert arbeidsforhold mellom ledere med komplementære styrker, hvor den eneste eksplisitte regelen er 'sier vi det én gang hvis noe skurrer'; når det fungerer, gir det psykologisk trygghet, raskere organisatorisk metabolisme (én leder drar de lange linjene mens den andre lander struktur og detalj i sanntid), og et avhopp fra forestillingen om leder-som-ensom-helt. Forutsetningene er ikke bare personlighet, men en kultur for eksplisitt ikke-konkurranse, gjensidig fremsnakk og evnen til å bevege seg fritt mellom hierarkiske konfigurasjoner — over, under, sideordnet — uten at relasjonen knekker. Episoden er også, ved demonstrasjon, et argument for at toleder-praksis er en kompetanse på toppen av vanlig lederkompetanse (lytte til teknologer, oversette mellom fag, sette OKR-retning, akseptere at det vil skje feil) — og at par-forholdet oppdages, det planlegges ikke."}
• 2) Hans Christian Holte dusjer i informasjon Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2025-10-20 source ↗ Reader 🖥️
  What senior public-sector leadership at NAV's scale actually consists of is the disciplined acceptance that you cannot retain most of the information that washes over you — that you must filter to a few central themes, lean heavily on competent people around you, deliberately ride the elevator between strategic altitude and the work itself ('T-ledelse'), and treat technology development not as a domain you keep up with personally but as the most potent strategic lever you must integrate with legal, professional, and user-experience perspectives to bring the whole organization, not just the directorate, forward.
• 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.

Propositions touching this concept (4)

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

2025-10

• explicitTechnology leadership exists at every organizational level, and a podcast about it should move between those levels rather than focus on a single one.
  0) Velkommen til Heis · p1
• implicitThe hosts' lived experience at NAV (and now Entur/private sector) qualifies them to discuss technology leadership.
  0) Velkommen til Heis · p9
• 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'.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p7

2026-05

• explicitAcross many leader interviews on Heis, the strongest pattern is not technique but epistemic posture — the leaders worth listening to are 'wondering and questioning', rarely doctrinaire.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis · p19

Open gaps (48)

• 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 cost side of the information shower is not addressed. Every person who 'prepares and wants to land maximum points in their slot' is paying a cost: compressing their best case, choosing what to leave out, presumably also accepting that most of their points will be among those that 'rinse down the drain.' A senior-leader-centric view of information overload treats it as a load problem on the receiver; a system view would ask what happens to the people producing the information for the shower and what the aggregate organizational effect is when many serious efforts produce one-slot compressions that the receiver does not retain. Holte's metaphor invites this question and the conversation does not pick it up.
  2) Hans Christian Holte dusjer i informasjon
• incompleteThe criteria for which 'few central themes' Holte holds are not made explicit. He mentions specific filters: digital representation as a near-term must-solve at NAV offices; the NAV-office counsellor as a long-term focus; user experience as his current energise-zone. But how those particular bets emerged from the shower — what got filtered out, by what test — is not described. This is the operationally most interesting question and the most strategically sensitive; an answer might also be politically costly to give.
  2) Hans Christian Holte dusjer i informasjon
• unaddressedThe piece does not address what happens when Holte's filtering is wrong — when a theme that should have made it through the filter did not. The arbeidsavklaringspenger case is named as a failure of broad-enough thinking, but the role of his own information processing in that failure is not interrogated. A self-aware leader could productively unpack the failure mode of accepted forgetting: the information you accept losing may include exactly the information you should have kept.
  2) Hans Christian Holte dusjer i informasjon
• incompletePublic-sector context shapes what Holte can say. As sitting NAV director he must be careful about politically loaded territory (the stat/kommune split at NAV offices, decisions about digital identity, the politics around the user-experience unit). The conversation rides these edges and signals them ('certain politicians are squinting at us') but cannot fully unpack them. This is a structural feature of the format, not a flaw — but it limits how much of Holte's actual filtering criteria can surface.
  2) Hans Christian Holte dusjer i informasjon
• incompleteThe 'T-ledelse' reframe of the hosts' heis-fører concept is elegant, but the question of where T-ledelse fits in a 22,000-person organisation with multiple levels — and whether T-ledelse from the very top can substitute for translation roles at the middle — is not resolved. The hosts' own concept (heis-fører at middle levels) and Holte's reframe (T-ledelse from the top) may not be alternatives at all; the conversation does not address whether both are needed.
  2) Hans Christian Holte dusjer i informasjon
• irrelevantThe episode does not address the dusjer-i-informasjon dynamic outside the senior-leader context — at lower organisational levels (where 'preparation by counterparties' looks very different), or in private sector (where Holte has no recent experience). The framing is specific to Holte's altitude in Norwegian public-sector leadership, and the conversation honours that specificity rather than over-generalising — which is appropriate for the form, though a syntopical reading across episodes might generalise it.
  2) Hans Christian Holte dusjer i informasjon
• incompleteTorrissen's frame is largely Norwegian consultancy and public-sector. The 30-year-lifespan argument is anchored in NAV/Skatt/politi; he gestures at differential quality bars for low-stakes consumer apps but does not engage with product-company contexts (startup, scaleup, SaaS) where the relevant time horizon is 3-5 years and the relevant readers are 5-10 engineers, not 70 forvaltere.
  13) Tobias K. Torrissen om kodekvalitet, konferanser og AI — read next: Read this against the Pocock workshop extraction (product-company AI workflow) and Vidar Moe (Heis), to see how product-company engineers calibrate quality differently.
• incompleteThe 'engineering practices matter more under AI' claim rests on one cited Telenor talk. Strong intuition, weak evidence. A serious version needs DORA-style measurement of practice maturity × AI uplift.
  13) Tobias K. Torrissen om kodekvalitet, konferanser og AI — read next: DORA 2025 (already in user's library); the Entur AI adoption piece; Addy Osmani's agent patterns; any rigorous productivity studies.
• incompleteThe 'obvious over clever' principle is presented as inheritance from NAV's tekniske retning but the tradeoff against domain-modelling power, type-system expressiveness, and idiomatic language use is not explored. A 'maximally obvious' codebase in a functional language with strong types may look obscure to a Java-trained 70-forvalter pool.
  13) Tobias K. Torrissen om kodekvalitet, konferanser og AI — read next: Greg Young / Vlad Khononov on domain modelling; Ousterhout's 'A Philosophy of Software Design'; Rich Hickey's 'Simple Made Easy' (vs. 'easy ≠ obvious').
• incompleteTorrissen acknowledges he's about to participate in a recursive case (reviewing code that was itself generated agentically) and only jokes. The methodology gap — how does code review change when the developer's intent is partially encoded in prompts, ADRs, and context files rather than commit history — is left for next time.
  13) Tobias K. Torrissen om kodekvalitet, konferanser og AI — read next: Anthropic 'harness design' talk and the Pocock workshop already in this corpus.
• incompleteThe advice to juniors assumes the fundamentals taught today are the right ones; doesn't engage with the possibility that fundamentals themselves need re-curation for a world where LLMs are the second author. What does TDD even mean when test generation is also automated?
  13) Tobias K. Torrissen om kodekvalitet, konferanser og AI — read next: Kent Beck's recent 'Tidy First?' work on AI and design; 'starving genies' series; DORA on AI testing practices.
• uninformedTorrissen disclaims familiarity with the formal 'distribution law' he invokes (Parnas/Helland-style). He gets the spirit right but doesn't engage with the literature on when distribution is forced (latency, regulatory, fault isolation).
  13) Tobias K. Torrissen om kodekvalitet, konferanser og AI — read next: Pat Helland's papers; Parnas on module boundaries; Vlad Khononov directly.
• incompleteCode quality discussion is silent on data and persistence design — arguably the longest-lived and hardest-to-change layer in 30-year systems. The whole conversation is about behavioural code.
  13) Tobias K. Torrissen om kodekvalitet, konferanser og AI — read next: Stripe-style schema evolution practice; Martin Kleppmann's data engineering work; event-sourcing reflections from CQRS practitioners.
• 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 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.
• incompleteVendor positioning is conspicuous: the story is told entirely from the survivors' chair. MobilePay engineers are quoted only as having insisted their tech was 'objectively better', MCash veterans get one similar line, and no failures are attributed to Vipps leadership specifically. The MCash 2017 carve-out is treated as smoothly inevitable; the operational chaos is named ('brannslukningsarbeid') but never traced to a decision.
  18) Vipps: Fra app til verb til nordisk infrastruktur — read next: MobilePay engineering blog posts from 2023–2024; the Danish fintech press's coverage of the merger; Kristian Pinsel Halvorsen interviews (his name is dropped as the host's 'old boss' from FINN, suggesting a counter-perspective on big-bang migrations in Schibsted/FINN territory)
• incompleteThe role of DNB through the entire history is underexamined. Vipps was DNB's first public-cloud workload, DNB's CEO drove the founding, MCash brought the other Norwegian banks in, and yet the bank-shareholder governance — including how decisions like 'use Vipps's platform, not MobilePay's' actually get taken — is essentially a black box.
  18) Vipps: Fra app til verb til nordisk infrastruktur — read next: Norwegian financial press on Vipps AS ownership changes; Rune Bjerke's memoir/interviews; the prior Heis episode with Kari Olrud Moen (ep 15, 'strategi tydelig og skråsikker') — Moen is Vipps's CEO context
• incompleteTap to Pay is celebrated as a success, but the speakers stop short of explaining what economic margin Vipps captures from international card schemes vs. domestic BankAxept on in-store transactions. Given that the entire European sovereignty argument hinges on dependency on American card schemes, the cost/risk picture matters strategically.
  18) Vipps: Fra app til verb til nordisk infrastruktur — read next: Norwegian card-scheme regulator (Finanstilsynet) cost analyses; EU Digital Markets Act / Payment Services Directive 3 documentation; ECB reports on European payments sovereignty
• incompleteThe 'verb-status' achievement is mentioned but not problematised. Mobilepay is also a verb in Danish; both verbs are now inside one company. What happens to brand neutrality and to user expectations when a Norwegian verb is owned by a Nordic company that wants to be European? The speakers laugh it off ('det tror jeg ikke vi skal prøve å spørre' about Finnish usage).
  18) Vipps: Fra app til verb til nordisk infrastruktur — read next: Sociolinguistics of brand-verb status; comparable post-merger brand consolidations in payments (Klarna, Wise); MobilePay marketing material from the merger announcement
• incompleteAI in regulated production code is left as an open problem. The 'humanize ser på koden' (humans review code) regulatory expectation is named, but the speakers don't engage with how Norwegian Finanstilsynet, the EU AI Act, or DORA-style governance frameworks will actually treat AI-generated code in financial production.
  18) Vipps: Fra app til verb til nordisk infrastruktur — read next: Finanstilsynet guidance on AI in financial services; EU AI Act high-risk system requirements for payments; DORA 2025 findings on AI-assisted development in regulated industries
• incompleteArchitecture is described as never planned ('aldri hatt et stort arkitekturprosjekt') but the result is a mature multi-cloud, multi-region, regulated platform with 35 product teams and 170+ engineers. The gap between 'we never planned it' and 'we ended up here' is unexamined — what is the actual feedback mechanism that lets a no-architecture-project culture not drift into mush?
  18) Vipps: Fra app til verb til nordisk infrastruktur — read next: Cutler's writing on emergent architecture and operating-system design; Beck's Tidy First essays on iterative architecture; the prior Heis episode with Greger Teigre Wedel (ep 12, 'når sjefen har svaret') for a Norwegian counter-perspective on top-down architecture
• incompleteThe speakers describe weekly releases and trunk-based-ish development for the app, but back-end deploy cadence and the cross-team coordination model when 35 product teams plus a payments backbone plus an AI platform team all ship at different speeds is not described in detail.
  18) Vipps: Fra app til verb til nordisk infrastruktur — read next: DORA 2024–2025 reports on deploy frequency and change-failure rate in financial services; NAV's 'fast flow' writeup that Kjetil has already saved (per persona)
• incompleteThe Digital Norway and Kongsberg Remote Weapon Station stories are told entirely from Qvam's own vantage point as the architect/CEO who initiated them, with no counterfactual (a comparable Norwegian coalition or product pivot that failed) and no adversarial pressure from the host — the same hagiography-risk pattern already flagged elsewhere in this corpus for founder/leader-narrated case studies.
  Strategi som regi i møte med teknologi: En samtale med Walter Qvam — read next: extract-heis-01-torbjorn-larsen-naermeste-vi-kommer-steve-jobs#g9 (same pattern, same corpus) and independent accounts of Digital Norway's or Kongsberg's development.