Strategy & Direction-Setting

Strategy as deliberate deselection plus a concrete, personally believed narrative — compressed enough that a distributed organization can act on it.

Also known as: strategisk narrativ (strategic narrative), strategic narrative, Retning, retning, Strategi på en ølbrikke, Velge bort, velge bort, Must-win battles, Tydelig, Skråsikker, company bets, reality distortion field, Henge sammen / få det til å henge sammen, Forankring

How authors use it

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

Documents (18)

• Dare to Be Bad at Something (From Fixable) Fixable (TED Audio Collective / Pushkin Industries), hosts Anne Morriss and Frances Frei; syndicated via the HBR Podcast Network / Cold Call feed · 2026-09-23 Reader 🖥️
  To excel where it matters most, individuals and organizations must deliberately choose — guided by a strict, customer-derived ranking of what matters — not only what to stop doing, but what to keep doing while doing it badly, and leaders must have (and visibly model) the emotional courage to sustain that choice under pressure.
• What New CEOs Get Wrong About the Job HBR IdeaCast (hosts Alison Beard, Adi Ignatius; guest Nitin Nohria) · 2026-09-22 source ↗ Reader 🖥️
  New executives systematically misjudge the CEO role because it inverts the very competencies that got them promoted — operating, knowing, and being obeyed — and succeeding requires deliberately relearning the job as one of creating conditions (for a team to run the company, for the truth to reach you, for the board to trust you, for the organization to move without you in the room) rather than exercising direct control.
• John Cutler's Post John Cutler · 2026-09-12 source ↗ Reader 🖥️
  Shifting from outputs to outcomes fails not because the idea is wrong but because teams adopt the language of outcomes while keeping the psychology of outputs — chasing certainty, easy measurement, and reputational credit instead of committing to the qualitative judgment, tolerance for ambiguity, and honest attribution that outcome-orientation actually demands.
• Is Your Strategic Plan Too Ambitious? Or Not Ambitious Enough? Rebecca Knight · 2026-09-10 source ↗ Reader 🖥️
  How ambitious a strategic plan should be is not an intrinsic property of the target number but something you calibrate by systematically examining the underlying problem, your available resources and talent, your tolerance for uncertainty, your measurement time horizon, and your competitive position — a deliberate exercise most organizations skip, defaulting instead to timid, business-as-usual plans.
• Strategy Making Gets an AI Boost Gretchen Gavett · 2026-08-18 Reader 🖥️
  As curator of The Insider, Gavett presents two arguments that senior leaders should trade fixed, precomputed plans for continuous option-generation under protected human judgment: AI dissolves the bounded-rationality limits that forced strategy-making into static frameworks like SWOT and Porter's five forces (per Felipe Csaszar), and longer, less predictable careers require small low-stakes experiments plus deliberately protected reflection time rather than a single career plan (per Lynda Gratton).
• 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.
• John Cutler's Post John Cutler · 2026-07-31 Reader 🖥️
  In an environment where every competitor has access to the same AI technology, durable advantage comes not from adopting AI fastest but from building — through problem-first, hypothesis-driven experimentation and a genuine social contract of trust — a team practice that learns faster than the surrounding hype cycle.
• TBM 433: The Border Collie Faustian Bargain John Cutler · 2026-07-29 Reader 🖥️
  In an organization performing a strategy that its experienced members already know isn't one, people sort by whether they can see the incoherence and whether they can tolerate it -- and the people who can see it but can't fully stomach it (the 'Border Collies') face a Faustian bargain: trade the right to challenge the fiction for more influence over it, a trade that starts as reasonable-sounding local accommodations and ends with the Border Collie having become responsible for producing and defending the very ambiguity it once found intolerable.
• Adam Mosseri: AI is a tailwind for authenticity Adam Mosseri (guest); Lenny Rachitsky (host) · 2026-07-11 Reader 🖥️
  Because AI makes creation nearly free and floods the world with synthetic content, the scarce and durable human advantages become taste, judgment and authenticity — which Mosseri argues is a tailwind rather than a headwind for Instagram (audiences will seek out real people and creators, not less), and which in turn reshapes how work is organized: teams compress into small generalist 'pods' led by a new 'product staff' role, while hiring rewards curiosity, grit and a willingness to try over deep specialization.
• The Power of Strategic Centering Harvard Business Review · 2026-07-01 source ↗ Reader 🖥️
  In a 'dematerializing' economy where corporate value has shifted decisively from physical assets to intangibles, executives should replace industry-position-based strategy frameworks with a single, deliberately chosen 'strategic center' (mission, customer, technology, ecosystem, or friction erasure) that the whole organization orients its resource allocation, opportunity selection, and identity around — because a clear center bounds the opportunity set without closing it, resolves capital-allocation conflicts, and licenses fast 'permissionless' action without requiring hierarchical approval.
• #35 Lessons learned from a 2x Unicorn Founder (Uri Levine) Perspective — The Scandinavian Product Podcast / Afonso Franco · 2026-05-09 Reader 🖥️
  Startup success is maximized by falling in love with a real, large problem — not a solution — and then relentlessly iterating through failures with speed, focus, and the courage to make hard decisions about people and direction.
• #36 Thinking big from day 1 to Unicorn | Pål Næss (Gelato, a Norwegian Unicorn) Afonso Franco · 2026-04-20 Reader 🖥️
  Building a globally significant company requires setting outsized ambitions from day one, staying hands-on through every stage of growth, and treating every operational constraint as a future competitive advantage — and the Norwegian ecosystem, despite its strengths, needs better role models and policy reform to produce more such companies.
• 15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-04-20 source ↗ Reader 🖥️
  Strategy is the disciplined act of choosing what NOT to do, justified by a credible read of where the world is going; doing it well requires leaders who are clear (tydelig) about direction without being dogmatic (skråsikker) about what they cannot yet know, and who keep the chosen direction connected, top and bottom, to what the organization is actually capable of and willing to move on.
• 10) Una Aamodt Mathisen om å lede når du ikke har fasiten Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-02-02 source ↗ Reader 🖥️
  {'english': "Leading complex cross-functional product work means accepting that the leader does not hold the answer key (fasiten) — the leader's job is to set direction and create the conditions in which a multidisciplinary team can find the answer together, not to supply it; competence at this looks like detective-work listening on arrival, hypothesis-shaped direction-setting ('we're going to that mountain, but route and gear we figure out together'), tight/loose discipline that closes the loop on learning, and tolerance for the friction and uncertainty that comes with not pretending to know.", 'norwegian': "Å lede tverrfaglige produkt-team på tvers av forretning, teknologi og fag betyr å anerkjenne at lederen ikke sitter på fasiten — lederens oppgave er å sette retning og legge til rette for at teamet finner løsningen, ikke å levere svaret selv; god utøvelse ser ut som lytte-detektivarbeid i starten, hypotese-formet retning ('vi skal på det fjellet, men rute og bagasje finner vi ut av sammen'), tight/loose-disiplin som lukker læringssløyfen, og toleranse for friksjonen og usikkerheten det skaper å ikke late som om man kan svaret."}
• 8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-01-04 source ↗ Reader 🖥️
  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.
• 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.
• 1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2025-10-13 source ↗ Reader 🖥️
  What warrants the Steve Jobs analogy in Larsen's case is not product taste in a consumer sense but the disciplined construction of a 'strategic narrative' so concrete and personally believed that it can pull a large bureaucracy through a paradigm shift — and this only works when paired with a complementary engineering apparatus (reverse Conway architecture, cross-functional value streams, common components discovered rather than designed, a 'golden-path' platform that makes the right thing the easy thing) operated by a leader who keeps an 'inngangsbillett' to the technical conversation so that the narrative remains connected to what is actually happening on the floor.
• Architecture Modernization: Aligning software, strategy, and structure • Nick Tune • CodeCrafts 2024 SQUER Solutions · 2024-06-11 source ↗ Reader 🖥️
  Successful architecture modernization is primarily an organizational and narrative problem, not a technology-upgrade problem: it succeeds when architects treat the value stream (business domain + outcomes + team autonomy + deployability) as the real unit of design, triage the system as a portfolio rather than rebuild it wholesale, and use social tools (listening, impact mapping, event storming, enabling teams, early visible wins) to earn and sustain the organizational permission that technical skill alone cannot secure.

Propositions touching this concept (9)

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

2025-10

• explicitcorroboratedReal lifestyle-change in an organisation requires a strong strategic narrative — not because storytelling is stylistically nice but because narrative is the only tool that mobilises people through what they want to be part of, which is the only durable form of follow-through.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p1
• explicitThe strategic narrative is dels something the leader personally needs — leadership is not survivable on work that does not feel important, valuable and value-creating to the leader herself.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p2
• explicitMaintaining inngangsbillett to technical conversation is non-negotiable for a leader who wants to attract good engineers, develop grounded strategic narrative and keep the floor-to-strategy translation working.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p9
• explicitThe strategic narrative is not a fasit but a developing object — innsikten avler mer innsikt — and the right metaphor is the hermeneutic circle from pedagogy.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p24

2025-12

• descriptiveTydelig retning at scale has a ceiling — beyond a few hundred employees, 'alle marsjerer i takt' is unattainable and probably undesirable; one year of intense OKR work at PIT did not move the medarbeiderundersøkelse scores on retning/strategi, and that is partly because the bar was unrealistic.
  6) Catherine Janson og Kjerstin Wester: The power of two! · p15

2026-02

• descriptivecorroboratedDirection-setting (retning) and team autonomy are not opposites; they are mutually constitutive — autonomy without shared direction produces drift, direction without autonomy produces literal compliance.
  10) Una Aamodt Mathisen om å lede når du ikke har fasiten · p4

2026-04

• explicitBeing tydelig (clear) is a virtue; being skråsikker (dogmatically certain) without grounding is its failure mode.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker · p3
• explicitStrong, clear leadership only helps if it is pointed in the right direction; otherwise sterk og tydelig accelerates the wrong outcome.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker · p7
• explicitTop-down 'company bets' (Spotify's term, introduced by the host) are a legitimate but scarce instrument — used too often, they erode the legitimacy of bottom-up work.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker · p11

Open gaps (62)

• incompleteSurvivorship bias is unaddressed. The entire argument for audacious goals, founder mode, and hands-on leadership is drawn from Gelato and the Stenbeck lineage — all successful cases. No discussion of companies that thought big from day one and failed, or founders who stayed hands-on and burned out.
  #36 Thinking big from day 1 to Unicorn | Pål Næss (Gelato, a Norwegian Unicorn) — read next: Ben Horowitz 'The Hard Thing About Hard Things' for failure narratives; research on stretch goals that backfire (e.g., Sitkin et al. on when stretch goals harm performance)
• incompleteThe role-model transmission theory lacks mechanism. Why does proximity to Stenbeck produce great founders but proximity to, say, Statoil or DNB does not? Næss even wishes Jotun would engage with startups — suggesting the mechanism is not automatic. What specifically must a role model do?
  #36 Thinking big from day 1 to Unicorn | Pål Næss (Gelato, a Norwegian Unicorn) — read next: Research on entrepreneurial ecosystems (Endeavor's work on mentor density); Saxenian 'Regional Advantage' on Silicon Valley vs. Route 128
• incompleteThe 'perfectly understaffed' philosophy is presented without its failure modes. When does deliberate understaffing lead to burnout, quality failures, or missed market windows? The US launch was pulled back as a positive example, but no negative consequences of understaffing are explored.
  #36 Thinking big from day 1 to Unicorn | Pål Næss (Gelato, a Norwegian Unicorn) — read next: Literature on organizational slack (Cyert & March); counterargument in Blitzscaling (Hoffman) that sometimes overstaffing is the correct move to capture winner-take-all markets
• incompleteThe conversation does not address how Gelato's insights apply to software-only or digital-native companies. Much of the discussion (local production, VAT complexity, physical delivery) is specific to companies with physical operations. The transferability of lessons to SaaS founders is assumed but not examined.
  #36 Thinking big from day 1 to Unicorn | Pål Næss (Gelato, a Norwegian Unicorn) — read next: Contrast with pure-software internationalization stories — e.g., Notion, Linear, or other companies that went global without physical operations
• incompleteThe episode never explains how to resolve conflicts between different customer segments' orderings of value (e.g. budget vs. business travelers on an airline), nor how 'the customer' is even defined when an organization serves multiple distinct populations with different priority orders.
  Dare to Be Bad at Something (From Fixable) — read next: Multi-sided-market and stakeholder-prioritization literature; product-market segmentation frameworks for reconciling conflicting customer rankings.
• incompleteNo account of how long a strategic trade-off should hold once made — when does a settled trade-off (no CD-ROM, no baggage transfer) become stale as customer expectations, competitors, or technology shift? Trade-offs are presented as durable and settled, never as something to periodically re-rank.
  Dare to Be Bad at Something (From Fixable) — read next: Strategy-renewal / dynamic-capabilities literature on when and how to revisit a prior strategic trade-off.
• illogicalThe 'defy gravity' claim — that trade-off physics apply identically in services as in physical products — is asserted by analogy ('the same physics applies') rather than demonstrated; the hosts never specify the underlying constrained resource (attention? budget? headcount? culture bandwidth?) the way weight/materials constrain a laptop.
  Dare to Be Bad at Something (From Fixable) — read next: Operations-management literature on service-quality trade-off mechanisms (queuing theory, capacity-utilization trade-offs) that would ground the metaphor mechanistically rather than rhetorically.
• incompleteThe rule 'don't run the company yourself' is stated as near-absolute, but real CEOs face moments (a safety incident, a fraud discovery, an active M&A crisis) where direct, hands-on intervention is clearly expected and appropriate. Nohria gives no criteria for distinguishing legitimate crisis intervention from the pathological over-involvement he warns against.
  What New CEOs Get Wrong About the Job — read next: Contingency-theory leadership literature on when centralized command is warranted vs. harmful (crisis management, high-reliability organizations).
• incompleteThe claim that CEOs get fired because they 'mistook politeness for support' is Nohria's own retrospective pattern-read of anecdotal workshop conversations with already-fired CEOs. There's no base rate offered, and no comparison group — CEOs who did read the board accurately and were fired anyway, or CEOs who ignored this advice and survived — so the causal weight of 'board-reading skill' versus underlying company performance is left unclear.
  What New CEOs Get Wrong About the Job — read next: Empirical CEO-succession/dismissal research (e.g., studies correlating board engagement practices with tenure and forced-turnover rates) that isolates board-reading skill from performance as a predictor.
• incompleteThe claim that '80% of the CEO job hasn't changed in 30 years, 20% is external' is asserted from Nohria's own workshop observation, with no operational definition of what's actually being measured — time allocation, topics discussed in the workshop, or skill demands are three different things that could each yield a different ratio. As stated, the 80/20 split is a memorable number but not a falsifiable claim.
  What New CEOs Get Wrong About the Job — read next: None specific — this is a call for the underlying workshop data (if it exists) to be operationalized and published rather than asserted as a round number.
• illogicalThe article asserts that 'centering is not the same as purpose' (illustrated with a single contrast example — a theater company's vague purpose statement) yet one of the five listed centering types is literally 'mission centering,' and the Novartis exemplar of mission-centering ('innovative medicines that truly help patients') reads as a purpose statement in all but name. No testable criterion is given for distinguishing a properly narrow, decision-useful 'center' from a properly narrow 'mission' or an properly narrow 'purpose' — the taxonomy's own first category partially collapses the distinction the article just drew.
  The Power of Strategic Centering — read next: Rumelt's 'Good Strategy/Bad Strategy' on distinguishing real strategy from restated goals; critiques of construct proliferation in strategy vocabulary (purpose, mission, vision, core values, North Star) as under-differentiated executive-speak.
• incompleteEvery named company example is one whose centering choice is, so far, associated with a good outcome (Novartis, Fujifilm, TSMC, Samsung, Toss, DBS, Nvidia, Shopify, early Amazon). Kodak and Southwest appear only as foils establishing other companies' successes, not as tested instances of 'had a clear, deliberately chosen single center and it still failed.' No company that centered and underperformed is discussed, so the base rate of centering's success is unknowable from the article alone.
  The Power of Strategic Centering — read next: Survivorship-bias literature (Mlodinow's 'The Drunkard's Walk', Taleb) on retrospective success narratives fitted to winners; Rosenzweig's 'The Halo Effect' critique of the 'In Search of Excellence' genre of business writing, which has essentially the same evidentiary structure as this article.
• uninformedNo attempt is made to separate the causal contribution of 'centering' from contemporaneous confounds: Novartis's radioligand bet coincided with a broadly hot oncology/precision-medicine investment cycle; TSMC's and Samsung's ecosystem success is explicitly bound up with decades of targeted state industrial policy (named in the text itself), yet the article still credits 'centering' as the operative variable rather than state support; Fujifilm's successful diversification depended on pre-existing chemical/materials-science IP whose availability to Kodak is never assessed.
  The Power of Strategic Centering — read next: Regression-to-the-mean and confound-control literature in strategy research; comparative case-study methodology critiques (e.g., Geoffrey Jones or business-history methodology essays) on isolating a single explanatory variable from multi-causal corporate histories.
• incompleteEach of the five centering types is given a named risk (mission drift, goal conflict, technological narcissism, geopolitical dependency, scope creep), but no instance is given of a company whose centering failed because that risk actually materialized. Without an observed failure case per risk, the framework offers no falsification criterion — it cannot currently be distinguished from 'successful companies, described after the fact, can always be shown to have had a coherent internal logic.'
  The Power of Strategic Centering — read next: Popper on falsifiability as a demarcation criterion; compare against how the 'resource-based view' and 'core competence' literatures the article dismisses were themselves originally supported by anecdote before later empirical scrutiny — is this critique specific to strategic centering, or standard for the strategy-framework genre at its introduction?
• misinformedThe load-bearing statistic — 'roughly 83% of Fortune 500 assets were tangible in 1975 versus ~90% intangible today' — is presented as a clean, uncontested fact via a single secondary citation, without stating measurement methodology. The widely-circulated version of this figure (traceable to the Ocean Tomo 'Intangible Asset Market Value' study) proxies 'intangible value' as market-cap-minus-book-value, which is sensitive to speculative multiple expansion and stock-market bubbles, not purely to genuine changes in asset composition — a methodological caveat the article does not mention despite resting its entire historical premise on the number.
  The Power of Strategic Centering — read next: Methodological critiques of the Ocean Tomo intangible-asset study specifically; broader critiques of using market-cap-minus-book-value as an 'intangibles' proxy in accounting/finance literature.
• incompleteThe Jobs analogy is named but not fully cashed out against its disanalogies. Jobs's reality distortion field was famously paired with cruelty, factional purges and product taste applied to consumer aesthetics. Larsen's framing is the opposite — toppdivisjon-ledelse runs on indre motivasjon, not fear; authenticity / easy-to-read-ness is the asset; the product is a public-sector welfare system. The conversation does not name these disanalogies, so the analogy carries more rhetorical work than it earns.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Read Walter Isaacson's Jobs alongside Tracy Kidder's Soul of a New Machine and Marc Andreessen-tradition writing on charismatic founder leadership to surface the disanalogies; for the NAV case specifically, read Cutler on 'institutionalized overload' to see what indre-motivasjon-based mobilisation can hide. Connects to the gap in the Skjærpe ep 17 extract on transformations that fail in the liminal phase.
• incompleteThe NAV transformation is described entirely from the inside by one of its architects. There is no counterfactual: comparable Norwegian agencies that did not transform similarly, post-Larsen reversion at NAV, what failed within NAV and why. The 'hagiography risk' the hosts flagged is real and unexamined.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Compare Skatteetaten, Statens Pensjonskasse, Helsedirektoratet trajectories during the same period; read the NAV-flow article in the user's library (Optimizing for Fast Flow in NAV) for the inside-but-different-author view; read the Skjærpe ep 17 extract for the immediate-successor's view from inside the system. Look for what the NAV transformation displaced or made impossible (e.g. casualties among legacy fagsystemer staff).
• incompleteThe 'common components are discovered, not designed' thesis is asserted with the NAV fakturering case as the load-bearing example, but the inverse failure mode (premature divergence — many verticals each solving the same problem badly because no one promoted the pattern to the platform) is acknowledged in passing ('we have capabilities in the platforms that strictly speaking are only needed one or two places ... it is a little behagelig that it got fixed over there') without being theorised. The position is one-sided.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Read the Wardley Mapping / pioneers-settlers-town-planners tradition for an explicit account of when components should be designed up front (the 'industrialised' part of the map). Read Cutler on 'horizontal team accountability' for how teams refuse to own platform-like problems they should own. The Vipps ep 18 extract may have a relevant view from the perspective of an organisation that did design infrastructure up front.
• incompleteThe 'easy to read' / authentic-leadership claim collides with the strategic-narrative claim. Strong strategic narrative is itself a construction; sustained reality-distortion presupposes some performance discipline. The conversation treats easy-to-read-ness and disciplined narrative as compatible without examining the tension. When does the constructed narrative cross into managed-impression territory, and what is the leader's check on that?
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Erving Goffman's Presentation of Self; Edgar Schein on the discrepancy between espoused theory and theory-in-use; Bent Flyvbjerg on narrative in megaprojects (where the same person both believes and constructs the future). The Cutler 'signals that look like decisions' thread is also relevant — for an easy-to-read leader, even contemplative musings can be read as commitments.
• incompleteThe inngangsbillett method is a personal description, not a teachable account. Larsen says he spends 'many hours a day' on craft and uses the hermeneutic-circle approach, but does not name which key terms, which structural maps, which sources, or how to know when the inngangsbillett is sufficient for a given fagdomene. The 'Fred George reads no books, he talks to authors' punchline gestures at one upper-bound technique but leaves the floor undefined.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Hubert Dreyfus's five-stage skill model (novice → expert) for a more precise grammar of 'how much do I need to know'; Cal Newport's deep work / deliberate practice tradition; the recent harness-engineering and AI-coding research extracted in this repo on what 'understanding a system' actually requires before AI can help you scale that understanding.
• uninformedThe conversation invokes Peter Senge's learning organisation as one of the three common denominators of Larsen's narrativer but does not interrogate how durably the organism-organisation framing has held up under real conditions over the 30 years since Fifth Discipline. There is a tradition of critique (e.g. Mintzberg on the messiness of organisational learning; recent operations-research literature on actual learning loops in software organisations) that the conversation does not engage with.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Mintzberg's Rise and Fall of Strategic Planning; Argyris on double-loop learning vs Senge's framing; the more recent DORA / Accelerate research on what kinds of learning actually correlate with performance — and what kinds (e.g. 'just keep adapting') do not.
• incompleteThe episode ends on Larsen's most quotable problem — moving from project mindset to outcome-driven verdistrøm-mindset — but does not specify what makes this so hard at Telenor specifically. Is it inherited governance? Board reporting cadence? Career incentives for people who have always shipped to scope? The hosts move on. This is the single most actionable place the conversation could have gone deeper.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: Cutler on outcome-orientation and operating-system design; Marty Cagan's 'product team vs feature team' distinction; the Una Aamodt-Mathisen ep 10 extract (lede uten fasit) likely has direct material on the same problem at a different scale. The Vidar Moe ep 5 ('det eneste Vidar vil er å ha det lett') may have a relevant view on operating-model simplification.
• incompleteThe hagiography risk is structural: Truls worked for Larsen, Audun met him at a formative moment, both are visibly inspired. The format does not include any adversarial pressure. The episode is therefore best read as Larsen's self-presentation lightly facilitated by admirers — strong as primary source, weak as evaluation.
  1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs — read next: For an evaluation lens, read external accounts of NAV's transformation (audit reports, Riksrevisjonen, Aftenposten / NRK coverage of NAV IT projects during the Larsen era), and look for counter-narratives in the Norwegian public-sector tech community. Compare to Holte ep 2 (the senior public-sector counterpart) for a different view of the same period.
• 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 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.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — 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.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — 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.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — 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.
• 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.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — 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.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — 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.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — 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.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — 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.
  8) Christian Printzell Halvorsen om å lede på riktig nivå: Lokalt forankret, nordisk samlet — 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.
• incompleteThe criterion that distinguishes strategic deselection from defensive or pathological deselection is named (the climate example) but not developed. When the urgent legitimately overrides the important and when it doesn't is left unanalyzed.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: John Cutler on institutional overload (TBM 412) and the cost of context collapse; Hamilton Helmer's 7 Powers for a more analytical theory of when narrowing is value-creating vs. value-destroying; Roger Martin's 'Playing to Win' for the 'winning aspiration → where to play → how to win' chain that forces the warrant question explicitly.
• incompleteThe people on the wrong side of deselection ('det er noen folk bak') are acknowledged but their experience and what leaders owe them is not analyzed. The 'kjipe oppgavene' frame keeps it at the level of leader-discomfort rather than treating the human cost as its own analytical object.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: Annie Duke's 'Quit' for the ethics and cognition of stopping; Cutler on accountability culture vs. blame; literature on layoffs/restructuring as legitimacy work.
• incompleteThe HOW-sharpening proposal (be sharp on tempo vs. error-tolerance, not on implementation) is offered as a resolution but not tested against the failure modes of values-as-strategy (where 'speed over perfection' becomes a slogan everyone reinterprets locally).
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: Cutler on operating systems and 'making the trade-off visible'; DORA/Accelerate on what concrete operating principles actually correlate with outcomes; Beck's Tidy First? framing for how small-scale design decisions encode strategic posture.
• incompleteThe relationship between 'kompani-bets' and the legitimacy economy of an autonomous team-of-teams organization is sketched but not modeled. How many bets per year? Who funds them? How does the organization recover from a bet that fails publicly?
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: Spotify's own writings on the post-bets era and what replaced it; Marty Cagan / SVPG on product strategy at scale; Cutler on directly-responsible-individuals and accountability when top-down moves intrude.
• incompletePublic-sector strategy is dismissed as 'mer taktikk' but the conversation does not return to it. Whether public-sector leaders can do something like deselection (and what its political constraints look like) is a productive missing thread for a podcast whose hosts work in NAV-adjacent contexts.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: Mark Moore on public value; Mariana Mazzucato on mission-led public strategy; specific Norwegian writing on NAV and Statens forvaltningsapparat strategy work.
• incompleteStrategy as power is gently visible (who gets the IT-køen priority that Vips got) but not analyzed as power. The political economy of must-win-battles inside a large organization — who loses access to resources, and through what mechanism — is left implicit.
  15) Kari Olrud Moen om strategi, kunsten å velge bort og forskjellen på å være tydelig og skråsikker — read next: Cutler on power and space (TBM 413, recently in user's library); Pfeffer on power in organizations; Helmer/Porter for the strategic value of being explicit about who-loses-what.
• incompleteThe role of DNB through the entire history is underexamined. Vipps was DNB's first public-cloud workload, DNB's CEO drove the founding, MCash brought the other Norwegian banks in, and yet the bank-shareholder governance — including how decisions like 'use Vipps's platform, not MobilePay's' actually get taken — is essentially a black box.
  18) Vipps: Fra app til verb til nordisk infrastruktur — read next: Norwegian financial press on Vipps AS ownership changes; Rune Bjerke's memoir/interviews; the prior Heis episode with Kari Olrud Moen (ep 15, 'strategi tydelig og skråsikker') — Moen is Vipps's CEO context
• uninformedAll supporting evidence is qualitative and anecdotal (two expert interviews, the Bezos/Amazon anecdote, one Burberry case) with no data on the relative frequency or cost of the two failure modes — plans that were too timid vs. plans that were too ambitious — so a reader cannot tell which error is more common or more costly in practice.
  Is Your Strategic Plan Too Ambitious? Or Not Ambitious Enough? — read next: Empirical strategy-execution research on goal-setting outcomes (e.g., academic stretch-goal research, or large-sample studies of strategic-plan success/failure rates).
• illogicalThe piece treats 'start small while aiming high' (the Bezos narrative) and '10x goals can't be achieved incrementally' (Sull's funding argument) as compatible, but doesn't reconcile that starting with books was itself an incremental first step — the article never clearly distinguishes incremental execution in service of a big vision from incremental ambition-setting, even though only the latter is framed as the failure mode to avoid.
  Is Your Strategic Plan Too Ambitious? Or Not Ambitious Enough? — read next: Real-options theory or staged-investment strategy models that formalize the distinction between a small, reversible first step and a capped level of ambition.
• incompleteNo mention of psychological safety or incentive/reward-system design, even though several failure modes (#4 credit-seeking, #9 cherry-picking around promo time, #11 fabricating causal stories) are natural responses to a reward system that punishes honest reporting of ambiguity, setbacks, or unattributable work. The post diagnoses the symptom (behavior) without naming the likely structural cause (what gets rewarded).
  John Cutler's Post
• incompleteThe deck compresses three detailed organizational case studies (build-trap escape, code migration, OKR alignment) into a handful of two-to-four-word bullets per box ('Portfolio approach', 'Layer HIL validation', 'Domain slicing', 'Back briefing'), with no operational detail on how these practices were actually implemented step by step, who owned the change, or how long it took to land.
  John Cutler's Post — read next: Cutler's longer TBM newsletter essays (already in this corpus, e.g. extract-tbm-430-incubate-compound-refinance-liquidate, extract-tbm-432-bundling-unbundling-capabilities) or a recording/write-up of the underlying live Dotwork client presentation would likely supply the missing mechanism.
• incompleteAll three case stories are presented as success narratives — the pivot worked in every case. The deck gives no counter-example of a team that adopted the same problem-first, hypothesis-driven, trust-first practice and still failed, nor any base rate for how often the 'before' pattern actually resolves the way these stories describe. Survivorship bias in the anecdotes is unaddressed.
  John Cutler's Post — read next: Practitioner retrospectives or failure-mode write-ups of AI-adoption playbooks would help test whether the practice generalizes beyond hand-picked success cases.
• incompleteThis LinkedIn post is a by-product of a live client talk ('Presenting to some of the biggest companies... I have a bad habit of creating new presentations and never doing the same one twice. So might as well share!'). The verbal narration, audience Q&A, and worked-exercise detail that would have accompanied these slides in the room are not captured here — only the static slide text and imagery survive as a 34-image carousel, so the connective reasoning between slides is partly inferred rather than stated.
  John Cutler's Post — read next: A recording or write-up of one of the actual Dotwork client sessions, if it surfaces, would fill in the missing connective tissue.
• incompleteThe talk asserts platform purpose 'can change' but never describes who has authority to change it, what triggers a re-evaluation, or how a changed purpose is communicated and re-legitimized to the stakeholders who bought into the original one — a real gap given the talk's own claim that platform failure often stems from purpose never having been (re)negotiated in the first place.
  Presentation: Platform Engineering for Everyone - Success Can’t Be Coded — read next: Corpus material on strategy-and-direction (compressed, personally-believed narratives) and on organizational governance of changing strategic commitments without losing team trust.
• incompleteLevine's framework is entirely drawn from consumer-facing, network-effect products (Waze, Moovit, Uber, Google). He does not address how his principles (especially 'fail fast with an embarrassing product' and 'retention is the only PMF metric') apply to B2B, enterprise, or deep-tech startups where shipping an embarrassing product may permanently damage trust.
  #35 Lessons learned from a 2x Unicorn Founder (Uri Levine) — read next: Ben Horowitz 'The Hard Thing About Hard Things' for enterprise context; or April Dunford 'Obviously Awesome' for B2B positioning nuances
• incompleteThe 'less than 5% of value in the first decade' claim is presented as fact without sourcing. It conflates market capitalization with value creation — early-stage value creation (technology, team, IP) is real but not captured by stock price.
  #35 Lessons learned from a 2x Unicorn Founder (Uri Levine) — read next: Janeway 'Doing Capitalism in the Innovation Economy' for a more nuanced account of when and how value accrues
• incompleteCrossing the chasm from early adopters to early majority is identified as critical (simplicity wins) but Levine provides no mechanism or case study for how to actually make that transition. Geoffrey Moore's framework is conspicuously absent.
  #35 Lessons learned from a 2x Unicorn Founder (Uri Levine) — read next: Geoffrey Moore 'Crossing the Chasm' — the canonical treatment of this exact problem
• incompleteThe firing advice assumes a US-style at-will employment context. The host raises Scandinavian legal constraints and cultural norms, but Levine dismisses them with 'you need to face the legal challenges' without engaging with how employment law changes the calculus.
  #35 Lessons learned from a 2x Unicorn Founder (Uri Levine) — read next: European employment law perspectives on startup team management; Scandinavian HR practices for scale-ups
• uninformedLevine claims 'only 64 people have built two unicorns.' This figure is likely outdated or sourced from a specific list; the actual number fluctuates and depends on definition (co-founder vs sole founder, SPAC unicorns, etc.).
  #35 Lessons learned from a 2x Unicorn Founder (Uri Levine) — read next: N/A — minor factual claim
• illogicalQvam argues culture and strategy are 'Siamese twins,' not opposed — yet his own land-based-wind-power example, where legitimate local/cultural opposition has blocked an outcome he himself calls rationally necessary, is a case where culture (in the broad sense of stakeholder values) directly defeats strategic execution. He never reconciles the tension between 'culture and strategy align when done right' and his own clearest example of when they don't.
  Strategi som regi i møte med teknologi: En samtale med Walter Qvam — read next: Cases of legitimate, non-pathological stakeholder resistance defeating a leadership-endorsed strategy (e.g., siting/NIMBY literature, or corpus material on change management's limits).
• incompleteThe Digital Norway and Kongsberg Remote Weapon Station stories are told entirely from Qvam's own vantage point as the architect/CEO who initiated them, with no counterfactual (a comparable Norwegian coalition or product pivot that failed) and no adversarial pressure from the host — the same hagiography-risk pattern already flagged elsewhere in this corpus for founder/leader-narrated case studies.
  Strategi som regi i møte med teknologi: En samtale med Walter Qvam — read next: extract-heis-01-torbjorn-larsen-naermeste-vi-kommer-steve-jobs#g9 (same pattern, same corpus) and independent accounts of Digital Norway's or Kongsberg's development.
• incompleteThe conversation never resolves who or what is actually doing the strategic work: is organizational success driven by the individual leader's skill as 'regissør' (director), or by structural conditions (ownership type, regulation, external shocks) that Qvam names as equally decisive elsewhere in the same conversation? Both framings are asserted side by side with no account of how they interact or which dominates when they conflict — arguably the conversation's central unexamined premise.
  Strategi som regi i møte med teknologi: En samtale med Walter Qvam — read next: Structure-vs-agency literature in leadership/strategy studies; corpus material on ownership and governance as strategic determinants.
• incompleteThe newsletter conveys Csaszar's core claim and recommendations but doesn't address how an AI-widened set of strategic options actually gets evaluated without hitting the same bounded-rationality constraint AI was meant to solve on the generation side — it asserts the conversation becomes 'sharper' without explaining the mechanism. The full underlying article, 'AI Is Revolutionizing Strategic Decision-Making' (hbr.org/2026/09/ai-is-revolutionizing-strategic-decision-making — not flagged Executive-only in a raw-HTML check; full-page/client-side access not verified since it was never saved), likely addresses this and is the natural next read.
  Strategy Making Gets an AI Boost — read next: Extract hbr.org/2026/09/ai-is-revolutionizing-strategic-decision-making directly.
• incompleteThe talk never reconciles its two first-slice funding postures: deliver visible value within 3-6 months to earn continued investment, versus the risk that an ambitious, high-value first slice (his own example: a committed six-month deadline blown by a year of cloud/on-prem networking and security issues) can derail the whole initiative. No decision rule is offered beyond 'map the options and be clear about tradeoffs.'
  Architecture Modernization: Aligning software, strategy, and structure • Nick Tune • CodeCrafts 2024 — read next: extract-hard-stop-rule-hcm-monoliths-microservices's pull-based migration model, which answers this by removing the separate-budget, separate-first-slice decision point entirely — migration becomes a side effect of ordinary roadmap work instead of a funded initiative that needs an early win.