Insourcing & In-House Capability

Repatriating the people, decisions and problem-solving capability an organization depends on — because using a vendor's AI is not the same as having the capability.

Also known as: Insourcing (hjemtaking), insourcing, hjemtaking, Hjemtaking av jurister, outsourcet problemløsning, in-house capability, innovation sovereignty, modningsreise (maturation journey), modningsreise, Business case for insourcing, capability mismatch, hollowed out

How authors use it

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

Documents (3)

• How Chinese Firms Are Saving Western Brands Shameen Prashantham · 2026-06 Reader 🖥️
  Western firms whose brand strength has outrun their in-house manufacturing, design, and digital capabilities should consider deliberate divestment — often to Chinese acquirers whose vertically integrated, patient, light-touch playbook can revive the brand — because clinging to ownership without the underlying capabilities is now the greater strategic risk.
• 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.
• 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.

Propositions touching this concept (9)

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

2025-12

• explicitInsourcing is the right move for software competence specifically — you save money AND you couple the developers tightly to the organisation.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke · p1
• explicitInsourcing's window depends on contract structure — when consultant contracts allow cancellation only twice a year, leaders must seize the window even with thin runway.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke · p2
• explicitInsourcing snowballs once it has started — flinke folk attract flinke folk, so the early hires are disproportionately load-bearing.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke · p3
• explicitInsourcing should not be done for its own sake — there must be an underliggende business case (redeployment of consultants, productivity gain that boosts revenue).
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke · p4
• explicitInsourcing should extend beyond developers — colocating jurists with developers collapses inter-organisational loops and is itself an insourcing move.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke · p5
• explicitThe right insourcing depth depends on context — SpareBank 1 Østlandet keeps most software at the shared SpareBank 1 Utvikling and only insources for what is genuinely Østlandet-differentiating.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke · p6
• explicitPublic-sector insourcing is no harder than private-sector insourcing — what differs is the utløsende hendelse (e.g., a KPMG-rapport, an administrerende leaving) that creates mandate width.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke · p7
• explicitTech leaders must understand technology well enough to recruit and to insource — without that competence, insourcing produces a 'veldig rart miljø' that ends up dependent on external consultants again.
  7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke · p16

2026-06

• explicitDecades of outsourcing have hollowed out the in-house manufacturing, design, and (eventually) R&D capabilities of many Western brand-owners, eroding the brand premium itself.
  How Chinese Firms Are Saving Western Brands · p2

Open gaps (22)

• incompleteGeopolitical and regulatory friction is mentioned only as a tailwind for vertical integration; the article does not engage with the very real possibility that Western governments will increasingly block exactly the deals it recommends (CFIUS, EU FDI screening, Five Eyes pressure). The strategic-choice menu assumes a deal-friendly environment that may not exist.
  How Chinese Firms Are Saving Western Brands — read next: Recent CFIUS/EU FDI screening case data; analyses of the Newport Wafer Fab, MagnaChip, or Nexperia interventions; Henry Farrell & Abraham Newman on weaponized interdependence.
• incompleteSurvivor bias: every named case is a success. No accounting of failed Chinese acquisitions of Western brands, base rates, or selection effects (e.g., Ding's board roles at H&H and JS Global, disclosed, may shape the case mix). Without a denominator, the playbook may be retrofitted to winners.
  How Chinese Firms Are Saving Western Brands — read next: M&A failure-rate literature on Chinese outbound deals (e.g., Lenovo-Motorola, HNA, Anbang); academic work by Peter Williamson, Eden Yin.
• incompleteOrganizational mechanism inside the acquirer is treated as a black box — 'they bring digital marketing acumen' is asserted, not decomposed. For a reader interested in capability transfer, the actual operating model (governance, talent flows between Hangzhou and Boston, decision rights) is the most interesting question and is unaddressed.
  How Chinese Firms Are Saving Western Brands — read next: Cutler-style organizational systems writing applied to cross-border M&A; case studies of JS Global's actual governance of SharkNinja; literature on ambidextrous organizations.
• incompleteThe article reframes outsourcing as the original sin but does not engage why the smiling-curve strategy made sense at the time or what changed (capital costs, supplier learning rates, geopolitics). Without that, the prescription to re-vertically-integrate is unsupported by the same kind of analysis the diagnosis received.
  How Chinese Firms Are Saving Western Brands — read next: Suzanne Berger 'Making in America'; recent reshoring economics; semiconductor industrial-policy literature.
• incompleteNo treatment of the data, IP, and software dimension — i.e., what happens to customer data, embedded software, OTA update infrastructure, and AI/ML models when a connected-product brand changes hands. For 2026 consumer-electronics deals this is arguably the central question.
  How Chinese Firms Are Saving Western Brands — read next: Recent DeepSeek / Chinese AI capability reporting; smart-device data sovereignty frameworks; literature on connected-product M&A.
• illogicalConflates two distinct claims under the 'rewiring the smiling curve' phrase: (1) the acquirer creates value at all three nodes, and (2) value at the middle (manufacturing) is no longer low-margin. Only the first is argued; the second is suggested rhetorically.
  How Chinese Firms Are Saving Western Brands — read next: Stan Shih's original smiling-curve papers; recent revisions by Mudambi on geography of value.
• 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.
• 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.
• incompleteNo engagement with the counter-thesis that agentic specification is itself a learnable new craft with its own first principles, rather than a hollow shell around an absent practice. Moe treats 'specifying' as essentially less than 'building' — the alienation premise depends on this. But it is at least defensible to argue that designing the specification surface, the test contract, the architectural guardrails, and the review protocol for an agent is a real engineering act that has its own depth. The essay would be stronger if it engaged this counter-position rather than implicitly dismissing it.
  KI, utvikling og følelser — read next: Steve Yegge's vibe coding manifesto (which the user is tracking) and Gene Kim's vibe coding series are explicit attempts to defend specification as craft. Read Moe in tension with them, not just alongside. Beck's evolutionary design tradition is also relevant: is the agent a new kind of pair-programmer that requires a new design discipline, or is it the thing that hollowed out the discipline?
• incompleteInsourcing is never weighed as the deeper remedy. The article accepts outsourced AI as the default and manages its risk downstream, but never considers building and owning the capability (or the data/eval/governance layer) as an alternative that would dissolve several exposures at once — opacity, customization-liability ambiguity and lock-in all shrink when the enterprise, not a vendor, owns the model or the surrounding stack.
  You Outsourced the AI—but You Still Own the Risk — read next: Insourcing vs. buy-and-govern trade-offs; owned AI capability (token capital) as a hedge; when repatriating capability beats contracting around a vendor's risk.