Public-Sector Digitalization

Technology transformation inside public institutions — societal mandates, procurement gates, transparency obligations and the leadership work of making bureaucracies digital.

Also known as: samfunnsoppdrag (societal mission), samfunnsoppdrag, societal mission, NAV, uforløst teknologibedrift (an unredeemed/unrealised technology company), KS1 / KS2, open source (in NHS context)

How authors use it

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

Documents (13)

• Forsvaret med egen data-grunnlov Silje Rognsvåg · 2026-08-18 Reader 🖥️
  The Norwegian Armed Forces are building a 'data constitution' (FDSA) that makes data — not the technology or vendor processing it — the stable core of digital infrastructure, so that suppliers can be swapped without disruption; Norway's Digitalization Minister argues this same data-centric logic should extend to the rest of the public sector.
• 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.
• How governments and organizations are leveraging Google's AI breakthroughs for crisis resilience Yossi Matias · 2026-07-07 source ↗ Reader 🖥️
  Google's decade of AI investment in forecasting, alerting, and satellite-imagery analysis is now translating, through partnerships with the UN, national governments, and humanitarian organizations, into measurable improvements across the full disaster life-cycle — and Google intends to keep expanding this role.
• 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.
• NHS England rushes to hide software over AI hacking fears New Scientist · 2026-05-18 Reader 🖥️
  NHS England has reversed its long-standing 'open by default' policy for publicly funded code, citing fears that Anthropic's code-analysis AI 'Mythos' could be used to find exploitable flaws — a move that security experts and former civil servants characterize as evidence-light, counterproductive, and harmful to the transparency on which public-sector accountability depends.
• 16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-05-04 source ↗ Reader 🖥️
  Norway's understanding of AI has been hijacked by the chatbot — both as the dominant interface and as the dominant mental model — and this collapses our maturation path: we substitute buying foreign LLM products for the slower, harder work of in-house machine-learning, problem framing, and explainability, even though the technical theory (data manifolds, approximation, neurosymbolic combinations) and the geopolitics both demand that we develop our own capability rather than outsource our problem-solving.
• Backlash builds over NHS plan to hide source code from AI hacking risk New Scientist · 2026-04-20 Reader 🖥️
  NHS England's decision to withdraw publicly funded open-source code from public access — motivated by fear of AI-powered vulnerability discovery tools like Mythos — is counterproductive because it removes the security benefits of open scrutiny while doing nothing to stop determined attackers, and it betrays the transparency obligations owed to taxpayers.
• Entur AS' innlegg — KI-løypa: Slik vurderer og innfører vi KI-verktøy i Entur Entur AS · 2026-04-16 Reader 🖥️
  Entur has developed a structured five-stage governance process ('KI-løypa') for evaluating, piloting, and managing AI tools responsibly, balancing the pursuit of efficiency gains against privacy, security, regulatory compliance, and ethical obligations inherent in their public-sector mandate.
• 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.
• 7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2025-12-15 source ↗ Reader 🖥️
  Insourcing, retning, and strategi-på-en-ølbrikke are three faces of one leadership move: pulling the locus of decision-making in-house and then compressing direction tightly enough that a distributed organisation can actually act on it — insourcing repatriates the people who must own the work, oppdragsbasert ledelse and sirkler av autonomi give those people a clear mission with explicit frihetsgrenser, and the ølbrikke forces utviklingsstrategi down to the few hovedområder a development organisation can actually carry, with OKRs underneath and an explicit business case underneath that.
• 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."}
• 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).
• 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.

Propositions touching this concept (2)

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

2025-12

• descriptiveSuccessful digitalization is not a technology problem — it is the leader's act of sewing together many parallel streams (regelverk, sikkerhet, penger, samfunnsoppdrag, kriminalitetsbildet, teknologi) into a totalbilde that lets people understand what is prioritized.
  6) Catherine Janson og Kjerstin Wester: The power of two! · p13

2026-04

• implicitAI governance in a public-sector organization must account for 'samfunnsoppdrag' (societal mission) in addition to standard business considerations.
  Entur AS' innlegg — KI-løypa: Slik vurderer og innfører vi KI-verktøy i Entur · p8

Open gaps (58)

• incompleteThe argument is pinned to Norwegian policy specifics (the government's ban, the Malthe-Sørenssen committee) while advancing a domain-general claim about how minds learn; it does not test whether its prescriptions travel beyond the Norwegian school/university system, nor engage equity between schools that can and cannot build 'simulators.'
  Det skal være vanskelig — read next: Comparative ed-tech policy; UNESCO 2023 'Technology in education: A tool on whose terms?'; equity-of-access critiques of school AI infrastructure.
• incompleteNo specific evaluation criteria or decision rubrics are shared for any of the five stages. The post describes the process structure but not how decisions are actually made, leaving the most operationally important details absent.
  Entur AS' innlegg — KI-løypa: Slik vurderer og innfører vi KI-verktøy i Entur — read next: Internal governance documentation from similar public-sector organizations; AI governance frameworks from NIST, ISO 42001, or Datatilsynet's AI guidelines.
• incompleteNo evidence of outcomes: how many AI tools have entered KI-løypa, how many were rejected at each stage, and what value the adopted tools have delivered. Without this, the framework's effectiveness is unsubstantiated.
  Entur AS' innlegg — KI-løypa: Slik vurderer og innfører vi KI-verktøy i Entur — read next: Case studies from organizations that have published AI governance outcomes and metrics.
• incompleteThe role of employees and end users in the governance process is limited to submitting proposals in Stage 1. There is no mention of how employee experience, feedback from piloting, or end-user impact assessments factor into decisions at later stages.
  Entur AS' innlegg — KI-løypa: Slik vurderer og innfører vi KI-verktøy i Entur — read next: Human-centered AI governance frameworks; participatory technology assessment literature.
• incompleteThe article never states the geopolitical/beredskap driver explicitly — NATO and NSM involvement gesture at it, but the reader is left to infer whether this is driven by the war in Ukraine, concern about foreign (especially US) tech-vendor dependency, cloud-sovereignty debates, or purely internal efficiency goals. This is a sharper version of the same gap the corpus flagged for a finance-sector parallel (beredskap and geopolitisk lock-in as explicit drivers of exit-strategy work).
  Forsvaret med egen data-grunnlov — read next: Read NSM/PST/E-tjenesten public risk assessments on tech-vendor dependency in critical infrastructure, or follow-up Kode24/Digital Norway coverage of the October 5 leverandørkonferanse, for the strategic rationale FDSA's public unveiling doesn't spell out.
• incompleteMinister Tung's claim that the Dataforvaltningsloven shares FDSA's 'logic' is asserted via a single sentence, not demonstrated — the article doesn't explain what the law actually requires or how closely it maps onto data-centric architecture principles (standardized interfaces, data-attached security rules, vendor exchangeability), leaving the reader unable to judge whether this is a genuine policy convergence or a rhetorical bridge built for the Arendalsuka panel debate.
  Forsvaret med egen data-grunnlov — read next: Read the Dataforvaltningsloven text or Digitaliseringsdirektoratet's guidance on it to assess actual overlap with FDSA's principles.
• incompleteThe post treats 'reach' (alerts appearing in Search, Maps, Android notifications) as equivalent to protection, without acknowledging that Public Alerts, Android Earthquake Alerts, and smartphone-based forecasting all assume Android/smartphone penetration and reliable internet or cellular connectivity — both of which vary enormously across the governments and communities the piece claims to serve.
  How governments and organizations are leveraging Google's AI breakthroughs for crisis resilience — read next: Read on disaster-alert equity gaps and the digital divide in low-connectivity or low-smartphone-penetration regions, especially in the same countries named here (Nigeria, Venezuela).
• incompleteThe piece names only successes. It presents no false positives, no missed events, no cost figures, and no account of what happens when a forecast is wrong or an alert fails to arrive in time — a familiar pattern across other Google-authored posts in this corpus (see extract-google-educators-ai-learning, which similarly reports only positive outcomes for a Google AI program).
  How governments and organizations are leveraging Google's AI breakthroughs for crisis resilience — read next: Seek failure-case studies or post-mortems of AI-based early-warning systems, and independent error-rate analyses of hurricane/flood AI forecasting versus traditional numerical weather prediction.
• illogicalThe post cites the WMO/national-agency local-data pilot study's finding ('local data significantly improves forecasts') as an established result, while explicitly noting in the same paragraph that the results are 'to be published in the coming weeks' — i.e., not yet peer-reviewed or public at the time of writing.
  How governments and organizations are leveraging Google's AI breakthroughs for crisis resilience — read next: Check whether the study was subsequently published and whether its published findings match the pre-announced framing.
• 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
• 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?
• incompleteHaugseth's account is built on insourcing successes (Mattilsynet, NAV). There is no narrative of an insourcing that failed or backfired — no analysis of when insourcing produced worse outcomes than the status quo. The closest is the NAIS-reflection (where she would have stayed less ambitious about own platform), but that is presented as 'should have piggybacked,' not 'insourcing failed.' The asymmetry shapes what is visible: insourcing's hazards (talent risk, two-year ramp where the org loses access to specialists, capability concentration in a few key hires who then leave) are absent from the framing.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke — read next: Susanne Justesen / John Cutler on the cost of capability concentration; the Norwegian NAV 'Optimizing for Fast Flow' article (already in the user's library) for a parallel account that emphasises the work-system rather than the ownership question; Capacity Planning literature on staffing as a long-cycle bet; failure-case writing on insourced platform teams that lost their flywheel (Stripe / Etsy public postmortems are useful counterpoints).
• incompleteThe business-case for insourcing is asserted but not specified. 'Either konsulentene get ny oppdrag andre steder, OR rådgiver-hverdagen improves enough to boost inntekt' is a frame, not an analysis. What kind of measurement? Over what horizon? Who validates the case 24 months in? The hard version of the case — that some insourcing pays for itself only in scenarios that don't materialise — is not engaged.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke — read next: Roger Martin on the strategy-stack from where-to-play to how-to-win; cost-of-delay literature; Dan North on staffing-as-bet.
• incompleteThe ølbrikke method is presented as a virtuous compression artifact, but the failure mode — that radical compression elides important trade-offs and lets every reader project their preferred reading onto the three hovedområder — is not addressed. Olrud Moen (ep 15) discusses the strategy-as-PowerPoint failure mode explicitly; Haugseth's ølbrikke could fall into a sibling failure mode (the strategy-as-slogan trap).
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke — read next: Olrud Moen Heis ep 15 (recently extracted) — direct counterpoint on strategy compression; John Cutler's TBM on 'making the trade-off visible'; Roger Martin on integrative thinking; Donald Sull on 'simple rules.'
• incompleteThe sponsor-group mechanism is described in the abstract; what happens when the two sponsors disagree, or when a sponsor leaves konsernledelsen mid-oppdrag, or when sponsor priorities conflict with what the team's konsernledelse-wide one-pager actually says, is not analysed.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke — read next: Marty Cagan / SVPG on product strategy governance; Cutler on accountability culture and DRIs (directly responsible individuals).
• incompleteHaugseth's epistemic update on skye is offered as an instance of changing her mind, but the underlying mental model that drove her earlier full-pro-cloud stance is not interrogated. What other current convictions might be in the same epistemic position now? The 'how does a leader earn forankring on the world' question (same as the Olrud Moen ep 15 gap) is unaddressed.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke — read next: Annie Duke 'Thinking in Bets' (already in user's library) on calibration and the cost of being skråsikker about probabilistic claims; Philip Tetlock on superforecasting; Donella Meadows on systemic leverage points.
• incompletePower and political economy are visible at the edges (the consultant houses' motstand to Mattilsynet cancellations; the 'kjipe' work of handling underperformance) but never named as power. The political cost paid by the consultant houses, by the developers whose subkulturer were dismantled, and by the avdelingsledere who had to take on accountability for cross-team samhandling is not analysed.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke — read next: Cutler 'Power and Space' (TBM 413, already in user's library); Pfeffer 'Power' on organisational politics; Hamel/Birkinshaw on managerial innovation and its political cost.
• incompleteThe 'privilegium ikke identitet' frame is named but not connected back to the operating-model questions earlier in the conversation. A leader who treats the role as borrowed time presumably should design the operating model so it survives their departure — i.e., the ølbrikke and the sponsor-group should ideally outlast the leader. That implication is not drawn.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke — read next: Cutler on operating systems as artefacts that survive their author; Olrud Moen ep 15 on 'strategy as the few sharp trade-offs that nobody else has the authority to set' — and the corollary question of what the leader leaves behind.
• 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.
• incompleteThe 'outsourcet problemløsning' framing is sharp but Strümke does not develop the policy mechanics: what counts as 'building it yourself' on a continuum? OSS-finetuned-from-an-open-base, Norway-hosted closed-weight, fully in-house from scratch — the framing presupposes a binary that procurement policy would have to operationalize.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: Cuijpers / EU AI Act interpretation on capability sovereignty; Anu Bradford on Brussels effect; OpenEuroLLM / Silo AI literature on sovereign-capability tiers; recent NSM/Nkom positions on cloud sovereignty thresholds.
• incompleteThe data-manifold frame is presented as Strümke's primary lens but she explicitly says 'we don't have access to either manifold' — so the entire empirical apparatus that would let us know how close approximation has gotten remains undeveloped in the conversation. The host doesn't push on what an operational proxy would even look like.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: Yamins & DiCarlo on neural-net-vs-cortex representational geometry; Bengio on the manifold hypothesis as ML's organizing assumption; recent interpretability work (Anthropic's circuit-tracing, sparse autoencoders) as one empirical handle on the model side of the question.
• incompleteStrümke argues for neurosymbolic AI and points at Claude Code's regex as proof, but doesn't address the harder question: where does the symbolic boundary go? Claude Code's choice is for a single literal token; the production design pattern (when LLM, when regex, when AST, when proof) is unexplored.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: Gary Marcus's neurosymbolic writings; DeepMind's AlphaProof/AlphaGeometry as advanced symbolic-neural hybrids; the harness-engineering literature already in the user's library (Anthropic, Boris Cherny) for production-design patterns.
• incompleteThe conversation reaches the 'cover your ass' diagnosis of Norwegian public-sector risk-aversion but does not investigate the structural causes — why has the last ~10 years been 'feigere'? Datatilsynet stance is named, the Nikolai Tangen episode is named, but the institutional feedback loop producing the pattern is not unpacked.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: John Cutler on institutional overload and accountability culture (already in the user's reading); recent NSM/Nkom assessments on resilience; Norwegian public-administration literature (NIBR / NIFU) on risk-distribution between politikere and direktorater; Annie Duke / Daniel Kahneman on outcome-bias driving risk-aversion.
• incompleteStrümke names two interesting categories — 'avklaringsspørsmål' (we have the methods, we just need agreement) and 'forskningsspørsmål' (genuinely open) — but doesn't extend the taxonomy. The third missing category is presumably 'capability-building-spørsmål' (we know what we need to build but lack the people / infra to build it) — which is arguably the dominant Norwegian bottleneck.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: Donella Meadows on system leverage points (where in this taxonomy is the highest leverage); KI Norge mandate documents from Digdir; recent NTNU/SimulaMet hiring and capacity reports.
• uninformedStrümke is open about her own production-coding skepticism ('jeg merker når jeg sitter og koder med agentene, så er sånn tulleprosjektet'), and the hosts (Audun from NAV) push back gently with the more developed practitioner view that high-stakes work warrants Vim while front-end can be agent-led. Strümke's reading of agentic coding may underweight what's currently possible with proper harness, evals, and sandboxing — though she does flag the macOS sandbox feature.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: User's existing thread on harness engineering (Anthropic videos, Boris Cherny, Bockeler/Fowler static sensors); Beane on Precision Proactivity; the user's earlier Heis Anders Sveen / Vilde Opsal extractions; Greger Wedel; concrete production-engineering reports from Builder.io, Cursor, and Claude Code teams.
• incompleteThe closing 'undetectable backdoors' research preview is fascinating but isolated from the rest of the conversation. If undetectable backdoors are plantable, the entire 'outsource problem-solving to Copilot' diagnosis acquires a much sharper national-security dimension that the conversation does not draw.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: Goldwasser et al. on undetectable backdoors (the foundational paper); recent NeurIPS / ICML papers on neural-net backdoor detection; supply-chain security literature (SLSA, sigstore) extended to ML model artifacts.
• incompleteThe flywheel/S-curve/liminal frame is used to describe both the NAV transformation (which succeeded) and the AI shift (in progress). The conversation never names a transformation that failed at the liminal phase and asks why — so the framework is at risk of being unfalsifiable on its own terms.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Read failed transformations through the same frame — e.g., government-IT projects that died in their liminal phase, large agile adoptions that reverted. Cutler's overload work and the 'people who tried Spotify model' literature would expose where the frame breaks. The Geoffrey Moore 'Crossing the Chasm' tradition has more developed accounts of curves that stall.
• incompleteThe 'learning vs production' rule is stated as a personal heuristic but not connected to any educational theory or empirical evidence. For a leader of consultants asked to scale this practice, there is no model for how the two modes should be partitioned, whether across days, projects, or moods.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Donald Schön's reflection-in-action; deliberate-practice literature (Ericsson); Beck's 'tidy first?' framing of preparatory vs delivery work — the tidy/messy split echoes the learning/production split structurally. Worth syntopical pass against Beck's recent 'Starving Genies' work on AI-assisted craft.
• incompleteThe elevator metaphor is generalised from Jonas's own career and from the show's animating premise. The conversation does not seriously consider organisations where vertical traversal is structurally suppressed (military, regulated finance with information walls, classified environments). The implicit premise that elevators are always available may not hold.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Read about organisations with designed information barriers — security classifications, MAR-walled investment banking, healthcare compartmentalisation. James C Scott's 'Seeing Like a State' on legibility. Where the elevator is locked, what substitutes?
• incompleteThe introvert-leader claim rests on one practitioner's experience and one rhetorical contrast (scale removes small-talk tax). Jonas notes that some colleagues found it hard to distinguish his opinions from his decisions — a cost that may be specifically introvert-shaped (lower social-cue density) but is not investigated.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Susan Cain on introvert leadership; the Cutler thread on 'signals that look like decisions' in leadership communication. The implicit problem of 'low-cue leadership at scale' is worth its own extraction.
• incompleteThe tractor and car analogies argue for slow structural change, but neither is examined for disanalogies. AI compresses learning loops in a way physical machinery cannot. The argument relies on the assumption that adoption is gated by humans, not by capability — which is plausible but not defended.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: The general-purpose-technology economics literature (Bresnahan & Trajtenberg); David Autor on labour-market restructuring time. Counter-cases: dial-up to broadband transitions, mobile phones — both moved faster than tractors. What predicts speed?
• uninformedThe Gukesh anecdote is reported confidently ('the only one of the young players not allowed a computer before age 12') but is not actually verified in the conversation. Whether true or apocryphal, it is doing argumentative work it has not earned.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Quick fact-check; more importantly, treat the underlying claim about protected early craft as a hypothesis and look at the actual evidence on AI use in early-career learning — programming pedagogy research will move on this in 2026-2028.
• incompleteThe claim that NAV's success was driven by capability investments is asserted from inside the case by the very people who made those investments. There is no counterfactual — no comparable agency that did not invest similarly and failed similarly. Some of the 'flywheel' may be storytelling.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Compare cross-country COVID welfare-IT responses (Germany, Denmark, UK), and Norwegian agencies of similar size that did not transform similarly. The Skatteetaten and Helsedirektoratet experiences would be a natural comparison.
• illogicalJonas argues both that we are early on the AI S-curve (so 10% gains are not the story) and that complexity will push back on productivity gains as they accumulate. These are compatible but in tension: if the curve climbs steeply because of intent-level abstraction, the complexity ceiling should appear later; if complexity bites soon, the curve is shallower than claimed. The argument is not adjudicated.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: The Brooks / Mythical Man Month tradition on accidental vs essential complexity; Ousterhout on system design; recent measurements on long-running agent harnesses (Anthropic harness design work) which directly test the complexity-ceiling claim.
• incompleteThe article quotes no cybersecurity expert who supports the NHS decision, even conditionally. A one-sided expert roster makes the argument persuasive but analytically weak — we don't hear the steelman of the NHS position.
  Backlash builds over NHS plan to hide source code from AI hacking risk — read next: NCSC or NHS Digital cybersecurity strategy documents; any published rationale from the NHS decision-makers.
• uninformedThe article does not distinguish between different types of NHS code — some repositories may contain infrastructure configurations, deployment scripts, or internal tooling where the security calculus differs from application code.
  Backlash builds over NHS plan to hide source code from AI hacking risk — read next: NHS England's GitHub repositories; analysis of what categories of code were actually published.
• incompleteThe broader policy question — how should governments respond when AI dramatically lowers the cost of finding vulnerabilities in public infrastructure code — is raised implicitly but not addressed. This is arguably the most important question the article touches.
  Backlash builds over NHS plan to hide source code from AI hacking risk — read next: CISA guidance on AI and software security; EU Cyber Resilience Act provisions; academic work on the security economics of open-source critical infrastructure.
• incompleteThe article does not identify who within NHS England drove the decision, what threat-modeling process was used, or what alternatives were considered. Without that, the 'panic' reading remains plausible but unproven; it could equally be a political-blame-avoidance maneuver dressed in security language.
  NHS England rushes to hide software over AI hacking fears — read next: FOI requests or follow-up reporting; literature on institutional risk aversion (e.g., Wildavsky on risk and culture; Power's 'Risk Management of Everything')
• incompleteThe Mythos capability claim is reported via prior coverage rather than reassessed; the article leans on AISI's summary without unpacking the evaluation methodology or scope.
  NHS England rushes to hide software over AI hacking fears — read next: The AISI blog post linked in the article; Anthropic's own model cards and red-team disclosures; broader work on cyber-offensive AI capability evaluation
• incompleteNo quantification of what's lost: how many repos, how much downstream reuse, what value to other organisations. The cost side of the cost-benefit framing is asserted rather than measured.
  NHS England rushes to hide software over AI hacking fears — read next: GDS impact assessments of public-sector open source; UK GovTech case studies; academic work on the economic value of open-source code
• incompleteNo engagement with intermediate options between fully open and fully closed — selective redaction, embargoed releases, signed binaries with private build pipelines, hash-based attestations. The frame is binary, which makes the criticism easier but flattens the design space.
  NHS England rushes to hide software over AI hacking fears — read next: Threat-model literature; the OpenSSF and CNCF supply-chain security playbooks
• incompleteThe article implies but does not develop a structural claim: that frontier-AI hype is producing a class of institutional decisions that withdraw from civic transparency commitments. The NHS case may be one of many; without comparable cases the claim is anecdote rather than pattern.
  NHS England rushes to hide software over AI hacking fears — read next: Survey other public-sector responses (national libraries, statistical offices, parliamentary IT) to AI scraping/ingestion; broader literature on 'AI moral panics' and their institutional consequences