8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet

Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · podcast · 2026-01-04 source ↗ Reader 🖥️

Non-Engineers Building Organizational Abstraction Levels Strategy & Direction-Setting Team Autonomy Value Streams & Verticals

Becoming Nordic-aligned (not pan-European, not purely national) is the right level at which to consolidate digital marketplaces, and getting there requires leading at the right abstraction layer — setting direction and 'why' from the top while delegating the 'how' to distributed cross-Nordic vertical teams — because the previous failure of pan-European centralisation taught Printzell Halvorsen that scale only works when the people whose work is being reorganised are kept, respected, and reassembled around problem verticals rather than dispossessed by a new hub.

practical · narrative-expository — a leadership case interview built around three intertwined arcs: Printzell Halvorsen's biographical arc (developer to topplsjef), the Schibsted/Vend organisational arc (Norwegian autonomy → failed pan-European centralisation → successful tvernordisk verticalisation), and the current AI/platform forward-look. Hosts ask short questions; guest answers at length. Argumentative in places (why the Nordic attempt succeeded where the European one failed); narrative in places (the Barcelona failure, the Blocket cut-over); expository on operating mechanics (vertical organisation, distributed teams, Department of AI, Bob the Builder). — Truls Jørgensen and Christian Printzell Halvorsen have prior history (Truls worked at FINN under him; explicit references to 'jeg jobbet med Finn frem til 2017' and the 'gamle dager' at FINN). The conversational warmth and shorthand reflect that. Audun is the relative outsider asking framing questions.

Structure

Part	Role
Opening: the cohort of brands (Finn / Blocket / DBA-Bilbasen / Tori-Oikotie) and the question 'how do you build a shared Nordic identity without erasing the cultures that made each brand work locally?'	Frames the entire conversation around the central tension named in the episode title
Biographical arc: Commodore 64 developer → McKinsey → FINN 2007 → Schibsted/Vend topplsjef	Establishes the guest's hybrid technical/strategic identity and signals that the path was unplanned — a series of opportunities seized after doing good work where he was
Defending technology-literate leadership: how it shapes strategy, where it overcorrects, how he maintains it (own AI coding, not as expert but as enough to reason)	Establishes a stance on the right depth of leader engagement with the underlying craft — neither a CTO-in-disguise nor a buzzword consumer
Tverrfaglig (cross-functional) coordination inside FINN: salg vs. tech, different motivations, suksess måles i markedet	Establishes a baseline picture of leading a multi-disciplinary organisation where the unifying frame is value to customers, not internal alignment
The pivot to Vend: from country-organised autonomous units to vertical (bil/eiendom/jobb/torget) organisation across the Nordics, motivated by customers' more specialised needs	Names the central organisational move — verticalisation, not centralisation
The Blocket migration: 60-70 tech teams + ~30-40 non-tech teams, big-bang cut-over, ahead of schedule	Concrete proof-of-concept of the new operating model and a stark contrast to public-sector megaproject delivery (Audun's NAV reference)
The Barcelona failure (Schibsted's 'One Company' 2015-2017): the prior attempt at pan-European centralisation, why it failed (people, not technology; central hub vs. local org friction), and Printzell Halvorsen's personal reckoning with it	Central counterexample and source of the lessons baked into the Nordic attempt
What was different this time: smaller cultural distance within the Nordics; similar maturity across all four marketplaces; never used the word 'sentralisering'; brought the same people, reorganised by vertical instead of by country; deliberate work on new shared values and leadership principles for Vend	Names the specific design choices that operationalise 'lokalt forankret, nordisk samlet'
Distributed teams across countries: how they collocate per vertical (bil, eiendom, jobb, torget), tidszone-aligned, minor cultural differences (danes direct, swedes konsensus, nordmenn på hytta)	Shows the operating texture beneath the model
AI: Department of AI (30-40 people) as enablement (not monopoly) on tooling, productivity, and product integration; Bob the Builder program for non-engineers; AI-based annonsinnlegging on torget; natural-language search; CFO joining Bob the Builder	Shows where current organisational energy is going and how the new platform creates leverage for AI rollout across countries
AI futures: the two-scenario picture (marketplaces persist as destinations vs. chat as the new front door); Vend bets on the first	Reveals the strategic posture under genuine uncertainty
Closing reflection: abstraksjonslag — leadership as moving up and down abstraction levels, like a developer; deference to a prior guest (Morten Eikeland) on the same point	Names the operational meaning of 'å lede på riktig nivå' — the conversation's title concept

Key terms

lokalt forankret, nordisk samlet
An organising principle for a Nordic group of national marketplaces: stay rooted in (and proud of) each strong local brand (Finn, Blocket, DBA, Bilbasen, Tori, Oikotie) because the brands live in consumers' heads, while sharing technology, platform, problem-framing and people across the four countries — organised by vertical (bil/eiendom/jobb/torget), not by country. Operationalised by: refusing the word 'sentralisering'; keeping the same people and reassembling them by problem domain instead of by geography; building new shared values and leadership principles for the merged company while preserving consumer-facing brand integrity.
å lede på riktig nivå Organizational Abstraction Levels
Operationally explained near the end of the conversation: an organisation is a stack of abstraction layers (individual → team → område → divisjon → selskap), analogous to abstraction layers in software. A topplsjef must operate at the highest layer — setting direction and the 'why' — and must resist the urge to direct work at lower layers. Stay curious about every level (nysgjerrig) without intervening in detail. Printzell Halvorsen explicitly endorses Morten Eikeland's framing on this point: leadership is not detail-focus but higher-abstraction focus.
vertikal Value Streams & Verticals
The unit of organisation that replaced 'country' as the slicing axis. The four verticals are bil (car), eiendom (real estate), jobb (jobs), torget (general goods). Each vertical is staffed by the same talent that previously sat under the country org, distributed across the four Nordic countries, and is expected to go deeper into its specific customer journey (kjøpe bil ≠ kjøpe bolig). Verticals are 'sett fri' so they can innovate without breaking each other — loosely coupled by design.
One Company
Schibsted's 2015-2017 attempt to put all 30+ global marketplaces (Europe and beyond) on a common technology platform, with central hubs in Barcelona and London. Failed because of friction between the central hubs and the local organisations; the friction grew until the effort had to be rolled back. Printzell Halvorsen had moved to Barcelona to lead the Barcelona hub; he counts this as a personal failure as a leader and reflected extensively on what went wrong.
Vend
The corporate name of the Nordic marketplaces group separated from Schibsted, comprising Finn (NO), Blocket (SE), DBA + Bilbasen (DK), Tori + Oikotie (FI). Deliberately a new brand at the parent level because the constituent marketplaces retain their consumer brands. 'Rentyrket markedsplass' — pure-play marketplace company — is the strategic identity, focused on four verticals and on positions that are or can be leading.
abstraksjonslag Organizational Abstraction Levels
Borrowed from software: organisations are made of nested abstraction layers (individual, team, område, divisjon, selskap). The skill a developer learns of moving between abstraction levels translates to leadership — at each level you reason at the right granularity and resist pulling detail from below. Used to give 'lede på riktig nivå' a technically literate meaning rather than a managerial one.
Department of AI
An organisational unit of 30-40 AI experts inside Vend that explicitly does not 'own' AI innovation — it is an enablement organisation. Three workstreams: (1) tooling and upskilling (ChatGPT Enterprise, AI-based sales tools, developer tools), (2) internal productivity, (3) supporting product teams in shipping AI features (with the vertical product team — e.g. jobb — as owner of features like natural-language search).
Bob the Builder Non-Engineers Building
A Vend program that enables non-engineers to build AI solutions with access to data sources and the ability to deploy in some form (described carefully as 'not yet in production product' but used to support people's own jobs and to prototype). Piloted with 10 employees pre-summer; now running cohort of 80. Vend's CFO joined cohort 2 to explore how to use AI to automate finance processes and to 'stay relevant' as a CFO.
rentyrket markedsplass
Pure-play marketplace — the strategic identity Vend chose after separating from Schibsted. Implies: focus on the four verticals (bil/eiendom/jobb/torget) where Vend has leading positions or a path to one, and divest from adjacent services that do not have a path to market leadership. Cited concrete consequences: shut down the Finnish job board (#2-3 in market), de-prioritised Nordic expansion of Finn Reise.
big bang launch
Cutover style preferred for platform migrations once you know where you are going. After a phased 1%-then-10% rollout in Finland (Tori) proved 'mye mer komplisert' and produced delays, the DBA migration used a big-bang cutover and was 'mye enklere og mye tryggere faktisk' and on time. Blocket — the highest-stakes site — also used big-bang and ran ahead of schedule. Implicit methodological claim: in integration projects with a known target state, big-bang beats incremental.
linjeorganisasjonen (using the line org)
Vend deliberately ran the Blocket migration through the existing line organisation — not through external consultants and not as a parallel project — combined with a clear cross-konsern priority signal from the top. Implicitly contrasted with public-sector megaproject patterns (Audun's NAV reference) where consulting-led parallel projects with detailed multi-year plans are the norm.
tvernordisk Value Streams & Verticals
Cross-Nordic — Printzell Halvorsen coins/emphasises it as a structural property distinct from 'multi-Nordic' (each country separately). The teams are tvernordisk in the same way they used to be tverrfaglig: members from different countries collaborating routinely. Tidszone-aligned and culturally close enough that distance is manageable.

Propositions

explicitThe right level of consolidation for the four Nordic marketplaces is Nordic-and-vertical, not country-by-country and not pan-European.conf: high
explicitCustomer needs are becoming more vertical-specific (selling a t-shirt is not selling a house), which is what justifies organising by vertical rather than by country.conf: high
explicitLocal consumer brands (Finn, Blocket, DBA, Bilbasen, Tori, Oikotie) must be preserved because they live in consumers' heads — but the organisation behind them should be tvernordisk.conf: high
explicitWhen the prior pan-European 'One Company' attempt failed, the cause was people-and-organisation friction between central hubs (Barcelona, London) and local marketplace organisations — not technology.conf: high
explicitThree conditions made the Nordic attempt succeed where the pan-European attempt failed: smaller cultural distance among Nordic countries; similar maturity across all four marketplaces; and reaching everywhere from a clean start with no hub vs. periphery framing.conf: high
explicitThe word 'sentralisering' was deliberately not used in the Nordic restructuring; instead, the framing was 'same talented people, organised differently — by vertical rather than by country.'conf: high
explicitLeading at the right level means operating at the top abstraction layer and resisting the urge to direct work at lower layers — staying curious about every level without intervening.conf: high
explicitA developer's discipline of moving between abstraction layers transfers to leadership: organisations are nested abstraction layers (individual → team → område → divisjon → selskap) and the leader must reason at the right one.conf: high
explicitIn platform-integration projects with a known target state, big-bang cutover is methodologically superior to phased rollout.conf: high
explicitLarge cross-Nordic delivery (Blocket migration: 60-70 tech teams + 30-40 non-tech teams) requires giving teams autonomy on the how, while the centre owns clarity on the why and the priority.conf: high
explicitA radically simple status-reporting mechanism — each team self-reports its probability of hitting a milestone — produces better intervention targeting than detailed top-down plans, because leadership can support the 30% who are struggling instead of managing the totality.conf: high
explicitcorroboratedThe simple status mechanism requires psychological safety: teams must be safe to report that they don't think they'll make it, and must know that admitting trouble brings help rather than punishment.conf: high
supports ←Don't Let AI Make Bad Analytics Worse · p9 — Both propositions argue that honest reporting (of trouble, or of disconfirming analytics findings) requires an organizational guarantee that admitting bad news brings help/correction rather than blame or persuasion pressure.
explicitVend's large delivery used the existing line organisation, not consultants on a parallel project — implicitly contrasted with the public-sector megaproject pattern.conf: high
explicitCultural differences within the Nordics are real but manageable (Danes more direct, Swedes more konsensus-oriented, Norwegians want to leave for the cabin on Fridays), and the tidszone alignment removes a significant source of friction that complicated the earlier Barcelona-led setup.conf: high
explicitTechnology-fluent leadership matters: a leader who understands enough of the technology to reason about it (without being the deepest expert) makes better strategic choices and knows what is and isn't possible.conf: high
explicitTechnology fluency has a downside: the organisation may report that the leader over-focuses on tech and under-focuses on sales or other functions; balance and tverrfaglighet are required.conf: high
explicitSuksess måles i markedet — internal alignment matters less than what is delivered to consumers and professional customers — and this framing makes tverrfaglig friction (e.g. salg vs. tech) easier to dissolve.conf: high
explicitAI capability should be organised as enablement (a Department of AI of 30-40 AI experts supporting the verticals' product teams) rather than as a monopoly on AI innovation.conf: high
explicitcorroboratedAI literacy must reach non-engineering functions; Bob the Builder is the mechanism (pilot of 10, now cohort of 80), and even the CFO is going through it to learn how to automate finance processes.conf: high
supports ←Lawyers are quietly becoming builders · p7 — The claim that every lawyer must at least get good at the tools and cannot ignore AI supports the broader thesis that AI literacy must reach non-engineering functions.
explicitcorroboratedAI prototypes built in Bob the Builder are not yet running in production-grade product code; they support people's jobs and enable rapid prototyping by product people without consuming engineering team capacity.conf: high
supports ←Lawyers are quietly becoming builders · p2 — Lawyers testing ideas in their own practice with no budget and no outside developer is the same phenomenon as non-engineers doing rapid prototyping without consuming engineering-team capacity.
explicitOn AI's effect on marketplaces, Vend bets on the 'destinations persist' scenario — fin.no, blokket, etc. as the best place to buy/sell — and on using AI to enhance that experience, leveraging brand trust and accumulated consumer-behaviour data.conf: high
explicitConcrete AI features rolling out: AI-guided ad creation on torget (photo/text guidance); natural-language search across torget and jobb. Jobb is a particularly good fit because verbal description of jobs is more naturally fluffy than filterable.conf: high
explicitStrategic focus (rentyrket markedsplass on four verticals with leading positions) implies discontinuing adjacent services that have no path to market leadership — the Finnish job board (#2-3) was shut down, and Finn Reise is being kept Norway-only despite host enthusiasm for its quality.conf: high
implicitA leader who has become a buzzword-consumer ('AI is what matters now') without underlying technical understanding loses credibility with engineers; the antidote is genuine first-hand engagement (coding AI examples, not just reading Gartner reports) plus ongoing dialogue with the organisation.conf: medium
explicitAutobiographical: career progress comes from doing a good job where you are and seizing opportunities when they appear, not from planning. The natural progression for a developer with a CEO-shaped ambition is developer → product/produktutvikling → business.conf: high

Arguments

Nordic-and-vertical consolidation is the right level — neither country-by-country autonomy nor pan-European centralisation — for Vend's marketplaces. strength: high

Explicit premises:

Customer needs are becoming more vertical-specific.
Nordic cultural distance is small enough that cross-country teamwork is viable.
All four marketplaces are at similar maturity, removing the start-up vs. mature asymmetry that complicated One Company.
Centralised hub-and-spoke models produce friction that destroyed One Company.
Verticalisation captures scale around customer journeys without taking ownership away from any single country.

Implicit premises:

Brand presence in consumer minds is locally rooted and must be preserved as a separate asset from operational structure.
There is a goldilocks zone of cultural and operational distance: pan-European is too far, country-only is too narrow.
Operating-organisation scope and consumer-brand scope can and should be decoupled.

Inferences:

Other Nordic consolidations facing similar conditions (similar maturity, cultural proximity, no hub story) should consider verticalisation instead of centralisation.
Public-sector or pan-European efforts should not draw the analogy lightly; the success conditions are specific.

Word choice matters in organisational change — specifically, refusing 'sentralisering' as a frame was a load-bearing design choice. strength: medium

Explicit premises:

In One Company, central hubs were a structural reality and the language reflected it; this produced friction.
In Vend, the framing is 'same people, organised differently by vertical instead of by country' — and the word 'sentralisering' is never used.
The actual movement of work was less centralising than One Company; the verticals are distributed across countries.

Implicit premises:

Language shapes how the affected people interpret their position and risk.
Identity loss (rather than work change per se) is what produces transformational friction.
Reorganising by problem domain is less identity-disrupting than relocating to a hub.

Inferences:

Leaders running similar transformations should audit their language for terms that signal dispossession ('central', 'hub', 'sentralisering') and replace them with terms that signal rearrangement of existing capacity.

Leading at the right abstraction level — clear 'why' at the top, autonomous 'how' at the team level, with very lightweight transparent self-reporting — is what made the Blocket cutover deliver ahead of schedule. strength: high

Explicit premises:

The total scope (60-70 tech teams + 30-40 non-tech teams) cannot be planned from the top.
Direction and priority were set unambiguously from the top.
Teams were given autonomy on the how plus a simple self-report on probability of hitting milestones.
Transparent rollup (50%, then 70%) let leadership target struggling teams rather than manage the totality.
Psychological safety made the self-reporting honest enough to be useful.
The line organisation, not consultants on a parallel project, did the work.

Implicit premises:

Detailed top-down planning loses at this scale.
Status reporting is bidirectional: it requires honesty downward and helpfulness upward.
Existing line organisation has the necessary capacity if priority is signalled clearly.

Inferences:

Public-sector megaprojects bound to multi-year tollgate plans and external consultant delivery are running the wrong operating model for projects of this complexity (Audun's NAV comment).
The Vend operating model is portable in principle, but depends on having a leadership culture that can hold the line on the 'why' and refrain from intervening on the 'how'.

Methodologically, big-bang cutover beats phased rollout in platform integration projects with a known target state. strength: high

Explicit premises:

Tori's 1%/10% phased rollout was 'mye mer komplisert' and produced delays.
DBA's big-bang rollout was simpler, safer, and on time.
Blocket's big-bang rollout (the highest-stakes site) ran ahead of schedule.

Implicit premises:

Integration is a different mode of work from greenfield product development; iterative/agile mental models apply less.
Confidence in the target state, plus rehearsal infrastructure, makes one-shot cutover dominate.

Inferences:

Default-iterative methodology should not be applied uncritically to integration projects.

AI capability should be organised as enablement, not as a monopoly — vertical product teams own AI features; the central Department of AI tools and upskills them. strength: medium

Explicit premises:

Vertical product teams own their domain (e.g., jobb owns natural-language search).
Department of AI's three workstreams are tooling/upskilling, internal productivity, and embedded support for product teams.
AI literacy must reach all functions (CFO in Bob the Builder).

Implicit premises:

The verticalisation principle (vertical owns the customer journey) extends naturally to AI capability.
Centralised AI feature ownership would recreate the hub vs. local friction of One Company in a new form.

Inferences:

Organisations centralising AI both for capability and for feature delivery should expect the same friction patterns Printzell Halvorsen experienced with One Company.

Vend should bet on marketplaces persisting as destinations and not on chat-as-front-door, while taking AI seriously inside the marketplaces. strength: low

Explicit premises:

Two extreme scenarios are plausible: destinations persist, or chat becomes the front door.
The future is probably between them but closer to the first.
Vend's strongest assets are brand trust and accumulated consumer-behaviour data — both of which favour the destinations scenario.
Concrete AI features (ad creation, natural-language search) leverage those assets.

Implicit premises:

Brand trust does not transfer cleanly into a third-party chat layer.
Strategy under deep uncertainty should be defined by the assets you can compound, not by the scenario you find most stylistically modern.

Inferences:

Marketplaces with the same asset structure (data + brand trust) should make the same bet.
Marketplaces without those assets should consider the second scenario more seriously.

A developer's instinct for moving between abstraction levels is one of the most underrated leadership capabilities and is the operational meaning of 'å lede på riktig nivå.' strength: medium

Explicit premises:

Developers continuously work across abstraction layers.
Organisations are nested abstraction layers (individual → team → område → divisjon → selskap).
A topplsjef who reaches down to direct work at low layers gets it wrong — like a developer reasoning at the wrong layer.
A leader must stay curious about all levels without intervening.

Implicit premises:

Leadership errors of intervention are analogous to leakage between abstraction levels in software.
Technical training transfers a useful structural intuition to leadership work.

Inferences:

Developer-to-leader transitions should be encouraged and the abstraction-level skill should be named explicitly as transferable.
Non-technical leaders may need a different scaffolding to develop the same instinct.

Narratives

Printzell Halvorsen's biographical arc: first code on a Commodore 64 as a child; trained in datateknikk; started as developer; recruited 'tilfeldigvis' by McKinsey building up their technology pillar; joined FINN in 2007 because the company felt 'det nærmeste du kunne komme Silicon Valley, men faktisk i Norge'; worked at FINN through 2017; later moved to Barcelona to build the Schibsted technology hub; came back, eventually became topplsjef of Vend.
→ Frames the unplanned, opportunity-seizing career model he later prescribes; also signals the developer identity that grounds the abstraksjonslag argument.
The Barcelona / One Company failure (2015-2017): Printzell Halvorsen moved to Barcelona to build the central technology hub for Schibsted's 30+ global marketplaces; the effort failed because of friction between the central hub (Barcelona + London + others) and the local marketplace organisations; the friction grew so large the rollback was ordered; Printzell Halvorsen left Schibsted in the wake of it, reflected extensively, and 'lov til meg selv at jeg skal aldri sette i gang noe sånt igjen.'
→ The negative template against which everything in the Nordic transformation is defined; also the credentialing scar that makes Printzell Halvorsen credible as the leader of the new attempt.
Audun's parallel anecdote: leading a One Company-era team distributed across Oslo, Stockholm, and Barcelona — same timezone, but the lunch culture differences (Spanish late eating) meant only a narrow window (~10:30-11:00) when the whole team could be assumed to be present and not eating.
→ Concrete vignette of the pan-European coordination problem the Nordic scope avoids; reinforces the cultural-proximity premise.
The Blocket migration as a 100-team big-bang: 60-70 tech teams + ~30-40 non-tech teams (marketing, sales, finance, customer service), distributed across countries, migrating Sweden's largest marketplace onto the same platform as Finn — ran ahead of schedule, using the line organisation, with teams self-reporting probability of hitting milestones, allowing leadership to support the struggling 30-50% rather than micromanage the whole.
→ Central empirical anchor for the operating-model argument; presented as a contrast to the public-sector megaproject model Audun raises.
Sequence of three platform migrations as a learning organisation: Tori (Finland) first, with 1% and 10% phased rollout — succeeded but 'mye mer komplisert' and delayed; DBA (Denmark) next, learned from Tori, used big-bang cutover, simpler and on time; Blocket (Sweden) last and highest-stakes, used big-bang and ran ahead of schedule. Site sequencing was deliberate — easiest and lowest-value site first.
→ Illustrates Vend's learning culture and grounds the big-bang methodological claim in a controlled progression.
Vend's vertical pattern: teams distributed across all four countries by vertical (bil teams in Norway, Sweden, Denmark; eiendom, jobb, torget similarly), some colocated, some distributed within the team itself across borders.
→ Shows the operating texture of tvernordisk: it is not 'central team in one country serves all four' — it is genuinely distributed across all four.
Bob the Builder pilot to scale: pre-summer pilot of 10 employees from across the organisation produced concrete AI solutions relevant to their own work; cohort 2 now has 80 participants; the CFO joined cohort 2 to learn how to use AI to automate finance processes and 'stay relevant.'
→ Concrete demonstration of AI literacy diffusion across functions; also signals Vend's leadership norm of senior people being students.
Truls's Finn Reise lament: he and others who worked on Finn Reise had a 'pakt' that when it finally went global they would all come back to take it further — but it never went global, and now everyone has moved on. Printzell Halvorsen explains that Finn Reise is being kept Norway-only because travel is a competitive market without a viable path to leadership outside Norway.
→ Concretises the rentyrket-markedsplass focus principle and shows what it costs (loyalty and quality both genuine, but neither sufficient to justify capital allocation).
Closing reflection on the developer-to-leader transition: Printzell Halvorsen did not decide to become a leader; it just happened. The one thing he names as transferable is the abstraksjonslag intuition, and he attributes the formulation to Morten Eikeland from an earlier Heis conversation.
→ Names the operational meaning of the episode title and explicitly threads it into the Heis canon.

Questions addressed

✅ How do you build a shared Nordic identity for these marketplaces without erasing the cultures that made each brand work locally?
Preserve the consumer brands (Finn, Blocket, DBA, Bilbasen, Tori, Oikotie) as identity-bearing local artefacts while reorganising the operating company by vertical (bil/eiendom/jobb/torget) distributed across all four countries. Never use the word 'sentralisering'; bring the same people across, reassemble by problem domain; invest deliberately in new shared values and leadership principles to bridge the residual cultural differences.
✅ Why did the Nordic attempt succeed where Schibsted's pan-European One Company effort failed?
Three differences: smaller cultural distance; similar maturity across all four marketplaces; and the deliberate avoidance of a hub vs. local frame in language and structure. Plus the lessons from the failure were baked into the Nordic design.
✅ What does 'å lede på riktig nivå' mean operationally?
Treat the organisation as nested abstraction layers; operate at the top layer (direction, why, priority); resist directing work below; remain curious about every layer without intervening. The analogy is to a developer moving between abstraction levels in software.
✅ How do you deliver a 100-team cross-Nordic platform migration ahead of schedule?
Clear top-level why-story and priority; use the line organisation, not consultants on a parallel project; give teams autonomy on the how; require only a very simple self-report on probability of hitting each milestone; use the transparent rollup to support struggling teams instead of managing the totality; cultivate the psychological safety required for honest self-reporting; prefer big-bang cutover over phased rollout when the target state is known.
⭕ Should marketplaces bet on persisting as destinations or on chat-as-front-door?
Both scenarios are plausible; the future is probably between them. Vend bets closer to 'destinations persist' because brand trust and accumulated data favour that scenario, and is using AI to enhance the destination experience. Acknowledged as a bet, not a prediction.
✅ How should AI capability be organised in a Nordic group of vertical product teams?
Central Department of AI as enablement (tooling, upskilling, embedded support); vertical product teams own AI features; Bob the Builder program brings AI literacy to non-engineers including the CFO.
✅ What career advice do you give a developer with a topplsjef in their belly?
Do a good job where you are; opportunities will follow; the natural progression is developer → product/produktutvikling → business. McKinsey was a coincidence; he does not endorse it as a path.
✅ How does a technology-fluent leader avoid becoming the buzzword-consumer 'AI is what matters now' caricature?
Genuine first-hand engagement (Printzell Halvorsen has coded AI examples himself, not to become an expert but to reason about possibility), plus ongoing dialogue with the people and the organisation that calibrates his understanding.
✅ What about the Schibsted/FINN engineering culture (you-build-it-you-run-it, devops, code quality) under a low-code AI tool like Bob the Builder?
Bob the Builder outputs are not in product production code (yet); they support people's own jobs and rapid prototyping. Implicitly preserves the engineering culture's quality bar for production code while opening a wider pipeline for prototypes and personal-productivity tooling.

Gaps

incompleteThe case for 'lokalt forankret, nordisk samlet' rests heavily on the three favourable conditions (small cultural distance, similar maturity, no hub story) that Printzell Halvorsen names. The conversation does not seriously interrogate what happens in cases where one or more of those conditions does not hold — e.g. a Nordic group with one dominant and three start-up markets, or a public-sector federation where national differences (legal, fiscal) are large. The model may be narrower than its rhetorical appeal suggests.
Read next: Compare to Nordic banking (Nordea), Nordic telecom (Telia/Telenor), and Nordic public-sector federations to see where the conditions hold and where they don't. Read Geert Hofstede / Erin Meyer on the actual measured cultural distances within the Nordics.
incompletePrivileged-Schibsted-vantage shapes what's visible vs. invisible. The lessons are drawn from a Schibsted-internal lineage of marketplaces with strong brands, a developer-heavy talent pool, and a long maturation as commercial businesses. The conversation is silent on: public-sector contexts, non-media startups, B2B enterprise software, government-mandated platform consolidations, and platforms where brand-in-consumers'-heads is not the load-bearing asset. The framework is presented as broadly applicable without owning these scope conditions.
Read next: Read public-sector platform consolidation case studies (NAV, Skatteetaten, NHS Digital, Estonian e-government); read B2B platform consolidation studies (Salesforce-MuleSoft, Adobe-Figma). The presence/absence of the Vend pattern in those contexts would map the model's actual reach.
incompleteThe methodological claim that big-bang beats phased for integration projects with a known target state is grounded in three Vend cases and asserted as a general lesson. The conversation does not consider failure cases (industry has many) or the boundary conditions (rehearsal infrastructure, rollback capability, cohesion of the cut team). Listeners may over-apply.
Read next: Read post-mortems on famous failed big-bang migrations (UK NHS NPfIT, TSB Bank 2018, Hertz/Accenture) to identify what made Vend's big-bangs work that those did not have.
incompleteThe simple 'how confident are you?' status mechanism is presented as a powerful tool but with one premise — psychological safety — given a single sentence. Building that safety at the scale of 100 teams across four countries is non-trivial and the conversation does not explore how Vend actually did it (or whether it was already present from inheritance).
Read next: Brede Moe ep 9 (already extracted) directly addresses the operational construction of psychological safety in teams; pairing his prescriptions with Printzell Halvorsen's claim that the self-reporting honesty held would test whether Vend's safety conditions are explicit or implicit. Also Edmondson on hybrid/distributed safety.
closed by9) Nils Brede Moe om AI-paradokset, autonomi, læringskultur og fremtidens team — Operationalizes the psychological-safety premise behind Vend's self-reported status mechanism: safety is collective, requires deliberate investment in shared practice, and is built through structured learning rituals and peer-agreed working agreements.
incompleteBob the Builder is presented as low-code AI tooling that produces useful prototypes and personal-productivity solutions but is firewalled from product production code. The conversation does not address how outputs ever cross that firewall — what happens when a marketing team's Bob the Builder solution becomes load-bearing and needs the engineering quality bar.
Read next: Read low-code/citizen-developer governance literature (Gartner's 'fusion teams,' Microsoft Power Platform CoE patterns) for how organisations handle the citizen-to-production handoff.
incompletePrintzell Halvorsen names the senior/junior asymmetry of technology fluency implicitly (his own developer past as anchor; CFO going through Bob the Builder to stay relevant) but never engages the question of how Vend develops the next generation of leaders without a developer past. The transferability of the abstraksjonslag instinct to non-technical leaders is left open.
Read next: Read Beane on apprenticeship in mixed-expertise contexts; read deliberate-practice literature on developing abstraction skill without a code substrate.
incompleteThe destination-vs.-chat scenario framing is treated as binary. The conversation does not engage the third possibility — that marketplaces become specialised APIs feeding many fronts (chat, AR shopping, voice assistants), with the consumer-facing brand decoupled from the consumer-facing surface. That would require a different bet on data infrastructure and brand strategy.
Read next: Read literature on platform economics under generative AI distribution (Anu Hariharan, a16z's recent marketplaces writing); Matthew Prince's own writing at Cloudflare on the AI-content-economy collapse and 'pay-per-crawl' proposals (which Printzell Halvorsen alludes to when citing him).
uninformedThe conversation does not engage with the consumer-welfare or competition-policy implications of Nordic consolidation. Consolidating into Vend reduces marketplace competition within each vertical at a Nordic level. The hosts do not raise this; Printzell Halvorsen does not address it.
Read next: Read EU competition decisions on Adevinta/eBay Classifieds, Schibsted's spin-off rationale, and Nordic competition authorities' marketplace cases for the regulatory frame the conversation omits.
incompleteThe autobiographical-prescriptive proposition ('do a good job where you are; opportunities follow; developer → product → business is the natural path') is presented without engaging the question of how much of Printzell Halvorsen's trajectory is reproducible vs. how much depends on McKinsey-as-accelerator, Norway's small leadership pool, and the specific historical moment of FINN. The advice may be more biographically contingent than it sounds.
Read next: Read against the Cutler thread on what conditions enable senior individual-contributor-to-leader transitions inside specific organisations, and against literature on path-dependence in executive careers.

8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet

Structure

Key terms

Propositions

Arguments

Narratives

Questions addressed

Gaps

Related documents