Learning Culture & Slack

Deliberately protected time, reflection and experimentation that make software development function as structured learning — the thing AI acceleration most threatens.

Also known as: læringskultur, learning culture, learning loops, laeringssleyfer (learning loops), double-loop learning, Double-loop learning, enkelt- og dobbelkrekklæring (single- and double-loop learning), single-loop learning, slakk, slack, Slow development, bruke tid for å spare tid, outsource the learning (du kan ikke outsource læringen), outsource the learning, læringsprosess vs produksjonsprosess (learning process vs production process), learning in the flow of work, ildsjel, speed of learning

How authors use it

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

Documents (36)

• Nils Brede Moe's Post Nils Brede Moe · 2026-09-23 Reader 🖥️
  Teams that genuinely pursue value from AI-assisted coding may work slower at first, because AI shortens code-writing but does not shorten the harder, team-level work of learning to specify tasks, verify quality, and build a shared practice — so the real productivity gain comes not from AI writing code faster but from the team developing a new, common way of working.
• The More Accessible Information Is, the Less Employees Remember Esther Kang · 2026-09-22 Reader 🖥️
  Because greater connectivity to people, platforms, and AI assistants makes employees measurably better at knowing who or what holds information and measurably worse at retaining the information itself -- even among their highest-capacity people -- leaders must stop treating findability as a proxy for learning and instead deliberately engineer work (explaining, applying, debating, teaching) that forces genuine internalization.
• Podcast: How Will We Train Developers If AI Does the Routine Work: A Conversation with Scott Hanselman Michael Stiefel (host) with Scott Hanselman (guest, VP, Microsoft/GitHub) · 2026-09-14 Reader 🖥️
  The software industry must institutionalize a formal, metriced 'preceptor' role -- modeled on nursing's dedicated teaching-nurse system -- whose explicit job is to grow junior engineers into seniors, because AI has absorbed the routine, low-stakes toil junior developers used to learn from, and without deliberate, funded intervention the industry's short-term hyper-optimization will hollow out the senior-engineer pipeline within a generation.
• Agentic Skill Decay AddyOsmani.com · 2026-08-31 source ↗ Reader 🖥️
  Agentic coding collapses the loop from problem to working patch so fast that it strips out the incidental struggle (debugging, reading diffs, forming and testing hypotheses) that used to build engineering expertise as a side effect of the work itself — so practitioners must now deliberately reinsert that practice, because the very expertise agents make optional is what increasingly determines whether you can verify and direct what an agent produces.
• Pascal BORNET's Post Pascal BORNET · 2026-08-01 Reader 🖥️
  Organizations mistake a team's ability to keep performing despite a broken system (endurance, sustained by workarounds and quiet compensation from strong employees and loyal managers) for evidence that the system itself is healthy, and leaders should instead treat the places demanding the most resilience as the places most in need of structural redesign.
• 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.
• Teaching Coding When AI Can Write the Code Eric Freeman · 2026-07-28 Reader 🖥️
  Because AI has severed the link between a finished piece of code and evidence of the student's understanding, coding education must shift its center of gravity from grading the finished artifact to making the process of thinking — explained, revised, and performed in public — the thing that is observed and assessed.
• Model the Transformation You Expect Employees to Deliver Antonio Nieto-Rodriguez · 2026-07-22 source ↗ Reader 🖥️
  Organizational transformations succeed or fail not because employees resist change but because senior leaders either do or do not visibly perform, in their own calendars and decisions, the same risk-taking, uncertainty-tolerance, and willingness-to-reverse-course they are asking employees to adopt.
• Det skal være vanskelig Erik Børve Rasmussen · 2026-07-10 source ↗ Reader 🖥️
  Difficulty is the mechanism of learning, not a defect in it, so AI — a machine for removing difficulty — destroys learning wherever the process rather than the product was the whole point (school, unlike work); the remedy is therefore to redesign AI and assessment as skill-forcing 'simulators' rather than to ban them.
• The Office Amenity That Actually Improves Teamwork Harvard Business Review · 2026-07-09 source ↗ Reader 🖥️
  The strongest driver of team effectiveness is not perks, office design, or where people work, but whether the team protects uninterrupted focused work, because effective collaboration depends first on enabling deep, independent thinking.
• Are We Entering a New Age of Creativity with the Help of AI? Harvard Business Review · 2026-07-07 source ↗ Reader 🖥️
  Laurene Powell Jobs's Atlantic-OpenAI content-licensing deal exemplifies the correct strategic response to generative AI for creative institutions: treat AI licensing as a short-term revenue and access play while doubling down on human-curated 'meaning' and top-tier creative talent, because genuine creativity — unlike AI's pattern recognition — remains scarce and is what audiences will still pay for.
• Notes from FOSE Europe Giles Edwards-Alexander · 2026-07-07 source ↗ Reader 🖥️
  Five months into the agentic era the value of agentic engineering is now settled ('the evidence is in'), so the live frontier of the debate has moved from the tools themselves to the socio-organisational questions they raise — how to design your organisation (Optimiser vs Learner), where engineering rigour and human judgement now live, and how to coordinate agentic work across teams and enterprises — none of which is yet resolved.
• Ordinary Engineers, Not Heroic Inventors Tim O'Reilly · 2026-07-07 source ↗ Reader 🖥️
  Technological and economic leadership — for nations and companies alike — is won not by inventing or dominating the 'leading sector' of a new technology but by diffusing a general-purpose technology like AI more broadly and patiently than rivals across ordinary, unglamorous work, a slow organizational (not technical) process that depends on skill infrastructure and on incentives that reward the 'ordinary engineers' who actually do the diffusing.
• This Is How To Overcome Burnout: 5 Secrets From Philosophy Eric Barker · 2026-07 Reader 🖥️
  To overcome burnout you must stop reflexively obeying the internalized 'achievement society' — notice and interrupt its demands, refuse compulsive busyness, and reclaim rest, boredom, and endings as intrinsically valuable rather than as instruments for future productivity.
• Research: Why Some Junior Employees Work Well with AI—and Others Don’t Ashish Agarwal, Anitesh Barua, Anu Puvvada, Fangchen Song, Wen Wen · 2026-07 source ↗ Reader 🖥️
  What separates early-career employees who create value beyond an AI baseline from those who merely match or fall below it is not their foundational skills (critical thinking, domain knowledge, AI literacy) but how they behave while working with AI — orchestrating, interrogating, and refining its output — so organizations should redesign entry-level training and performance assessment around that interaction behavior rather than around screening or upskilling foundational skills alone.
• DORA Community Discussion - Operationalizing DORA within a large organization DORA (speaker: Julia Jakubiec, ABN AMRO; host: Nathan Harvey) · 2026-06-26 source ↗ Reader 🖥️
  Operationalizing DORA at enterprise scale is fundamentally a change-management problem — solved by running Kotter's 8 steps to institutionalize a durable continuous-improvement culture — not by the metrics themselves, which serve only as a recognizable survey instrument, authority brand, and benchmarking catalyst.
• AI coding creates two kinds of debt. You're only measuring one Antonija Bilić Arar · 2026-06-18 source ↗ Reader 🖥️
  AI-generated code creates a second, largely invisible kind of debt — cognitive debt, the erosion of shared team understanding of what a system does and why, distinct from ordinary technical debt in the code itself — and it is a genuine measurement blind spot: satisfaction scores, NPS and mentor ratings can hold steady or rise while it accumulates, so organizations must replace satisfaction-based signals with trajectory-based skill measurement and deliberate team-level questions to catch it before it becomes irreversible.
• Brain Food: Answers Without Effort Shane Parrish (FS) · 2026-06-14 source ↗ Reader 🖥️
  Understanding — and the confidence, success and clutch performance that stand alongside it — cannot be borrowed or shortcut; all are earned only through whole-hearted, sustained effort, so an answer you obtain without effort is hollow because it never becomes understanding you actually own.
• Trust Factory Kent Beck (Software Design: Tidy First?) · 2026-06-02 Reader 🖥️
  Extreme Programming was a 'trust factory' — its practices, principles, and values all produced trust as a byproduct of producing software — and AI-augmented ('genie') development is breaking this because it accumulates code far faster than it accumulates trust; the remedy is to deliberately slow augmented development so it manufactures trust the way XP did.
• 17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-05-18 source ↗ Reader 🖥️
  Large sociotechnical transformations — whether NAV's digital transformation a decade ago or the current AI shift — work by accumulating slow flywheel momentum that then snaps into a sudden S-curve climb through a high-friction liminal phase, and the leaders who guide organizations through such transitions are those who can 'take the elevator' across organizational floors and disciplines, translating between domain, technology and executive language while staying close enough to the craft that their advice is grounded in something real.
• SWLW #701: Gazing at the misty AI Frontier, From Vibe Coding to Agentic Engineering, and more. Oren Ellenbogen · 2026-05-18 Reader 🖥️
  In the agentic era, software leaders win by raising their ceiling — investing in fundamentals, original thinking, and emotionally-attuned leadership — rather than letting AI flatten everyone to the same elevated floor.
• TBM 421: Minimally Viable Consistency (Part 3) John Cutler · 2026-05-09 Reader 🖥️
  Organizational consistency is not a single lever but a portfolio of three distinct strategies — sharp consistency (opinionated uniformity), flexible consistency (shared intent with local adaptation), and legible variety (named, visible differences) — and choosing the right mix at each point is the central design problem, one that AI can help with by translating between frames and scaling coaching, but only if the sensemaking friction it removes was overhead and not a learning mechanism.
• How Fast-Growing Companies Can Make Better Decisions Tatiana Sandino · 2026-05-07 source ↗ Reader 🖥️
  Fast-growing companies that frame decision-making as a binary choice between centralization and decentralization fall into predictable failure modes; a third path — structured empowerment, which combines curated decision options with outcome-based accountability — lets organizations scale while preserving both consistency and local adaptability.
• New Skills to Navigate Continuous Change HBR.org (Nilofer Merchant conversation) · 2026-05-05 source ↗ Reader 🖥️
  The biggest barrier to organizational change is not resistance but inherited norms — especially the privileging of confidence over competence and control over co-creation — and leaders who replace those norms with collaborative ownership, curiosity, and tolerance for discomfort will unlock the innovation their organizations already contain.
• Forskning på digitalisering 2026 uke 19 Leif Knutsen · 2026-05-04 source ↗ Reader 🖥️
  Current software engineering research highlights a recurring tension: agile transformation, measurement, and AI-assisted code analysis all require structured, disciplined approaches that seem to contradict the flexibility they aim to enable — and these paradoxes are not yet resolved.
• How to Build a Superteam That Keeps Getting Better Harvard Business Review · 2026-05-01 source ↗ Reader 🖥️
  In periods of rapid change, teams win not because they start with the best plans or the most talent but because their leaders build a continuous-improvement culture — one that makes experimentation, curiosity, early problem-surfacing, hands-on involvement, non-threatening feedback, and growth-oriented investment in people the daily default — so the team's rate of learning, not its starting position, determines whether it becomes a 'superteam.'
• Supporting Your Employees' Career Growth When Everyone Is Overwhelmed Rebecca Knight · 2026-05 source ↗ Reader 🖥️
  When workloads and AI/economic uncertainty crowd out career thinking, managers should reframe development away from long-horizon ladder-climbing toward near-term, broad, learning embedded inside the existing flow of work — and lead it by visibly doing it themselves.
• Presentation: Engineering at AI Speed: Lessons from the First Agentically Accelerated Software Project Adam Wolff · 2026-04-20 source ↗ Reader 🖥️
  When AI drives implementation cost to near zero, the competitive advantage shifts from planning and coding speed to the speed of your feedback loop — how fast you can ship, learn from users, and reverse course — making experimentation, not upfront design, the right engineering strategy.
• SMOC.AI's Post — 5 Minutter: AI og utviklere Kristoffer Kvam · 2026-04-10 source ↗ Reader 🖥️
  AI amplifies senior developers' effectiveness but breaks the traditional junior developer training pipeline, because the simple tasks that served as the learning on-ramp are being automated away — and juniors guiding AI-juniors compound weaknesses rather than building competence.
• 11) AI-spesial med Vilde Opsal og Anders Sveen Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-02-16 source ↗ Reader 🖥️
  AI-assisted development is a real step up in abstraction that pays off only when teams pair it with judgment, structure and active learning — speed gains come from agentic tooling, but durable value comes from evals, information architecture and refusing to outsource learning to the model.
• 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."}
• 9) Nils Brede Moe om AI-paradokset, autonomi, læringskultur og fremtidens team Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-01-19 source ↗ Reader 🖥️
  The promised productivity gains from AI in software development will not materialize at the organizational level unless teams deliberately slow down — investing in psychological safety, structured reflection, and joint experimentation — because software development is fundamentally a learning process and AI threatens the learning even as it accelerates the output.
• How AI will change software engineering – with Martin Fowler The Pragmatic Engineer · 2025-11-19 source ↗ Reader 🖥️
  AI's defining change to software engineering is not primarily a jump in abstraction level but a shift from deterministic to non-deterministic systems — and the disciplines that make software durable and legible to teams over time (small reviewable steps, tests, refactoring, shared vocabulary, mentorship) matter more, not less, as a result, even as the field has not yet worked out how teams — as opposed to individuals — should operate with AI.
• 5) Vidar Moe: Det eneste Vidar vil er å ha det lett Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2025-11-17 source ↗ Reader 🖥️
  Vidar Moe's core engineering-leadership philosophy is 'gjøre det lett og rett' (make it easy and right) — a Toyota-Way-inflected craft and leadership stance in which you lead an organization most powerfully not by exhortation but by patiently building the tooling, frameworks, fagtid, hiring filters, fixed-term leadership rotation, and shared decision arenas that make the right thing the path of least resistance; the episode's ironic title ('the only thing Vidar wants is to have it easy') inverts this — Moe wants the work to be easy precisely because he is willing to do the very hard, decade-long, mostly invisible work of removing friction from doing the right thing, and his current concern with AI agents is the natural next chapter of the same project.
• Tiny Experiments Anne-Laure Le Cunff · 2025-01-29 Reader 🖥️
  As reconstructed from the subtitle ('How to Live Freely in a Goal-Obsessed World') and the glossary's evaluative terms, Le Cunff's claim is that fixed, linear goals and a single overarching 'purpose' constrain rather than serve people navigating an uncertain world, and that small, time-bound, curiosity-driven 'personal experiments' (Pacts), evaluated by what was learned rather than by whether a predetermined outcome was hit, are the better vehicle for growth — but this document itself only supplies the vocabulary and self-reflection prompts for that thesis, not the argument or evidence for it.
• Mob programming: From avant-garde experimentation to established practice Daniel Ståhl, Torvald Mårtensson · 2021-07-29 Reader 🖥️
  Mob programming is a genuinely emergent but still immature practice whose effects — on productivity, learning, exhaustion, and team social dynamics — vary so much by individual and by task type that no universal claim about its efficacy holds; what the published literature treats as settled benefits are, on direct interview evidence from committed practitioners, ambiguous, individually contingent, and in urgent need of quantitative (not just anecdotal) research.

Propositions touching this concept (6)

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

2026-01

• explicitStructured, scheduled learning practices (Friday reflection meetings, workshops, dedicated Slack channels) outperform reliance on individual champions (ildsjeler) because champions burn out without supporting culture.
  9) Nils Brede Moe om AI-paradokset, autonomi, læringskultur og fremtidens team · p13

2026-02

• prescriptiveWhen you observe team behavior that signals defense or distrust (e.g., being kicked out of a Slack channel), exercise restraint — do not 'arrest' people for it; treat it as data about leadership scar tissue, not an offense.
  10) Una Aamodt Mathisen om å lede når du ikke har fasiten · p7
• explicitOrganizations should refuse to let any individual 'outsource the learning' — every level (developers, principals, CFOs, summer interns) must touch the tools themselves rather than wait for best practices.
  11) AI-spesial med Vilde Opsal og Anders Sveen · p12
• explicitcorroboratedAn organization-scale adoption pattern that works: deliberately surface an *ordinary* team that succeeded (not just star individuals), run Slack channels (a 'fast' frontier one and a 'safe' learning one), workshops, internal blog summaries, and 'no opt-out' learning culture — supported by access to best-in-class tools.
  11) AI-spesial med Vilde Opsal og Anders Sveen · p20

2026-04

• explicitcorroboratedWhen implementation cost approaches zero, the speed of learning becomes the only competitive advantage
  Presentation: Engineering at AI Speed: Lessons from the First Agentically Accelerated Software Project · p1

2026-05

• prescriptiveStructured empowerment requires two enabling conditions: formal double-loop learning systems and an empowering culture (purpose, adaptability, candor/psychological safety).
  How Fast-Growing Companies Can Make Better Decisions · p8

Tensions

Open gaps (89)

• incompleteThe essay is entirely first-person and anecdotal (one senior practitioner's account, backed by two cited studies), and never addresses whether "deliberate reps" can be operationalized for an entire junior cohort at an organizational level, versus remaining an individual discipline mainly available to practitioners who already have the author's level of self-directed rigor.
  Agentic Skill Decay — read next: Organizational or pedagogical research on structuring deliberate practice for junior engineers at scale, rather than individual habit-formation advice.
• illogicalThe author asserts "the return on expertise is going up" with near-certainty, then two paragraphs later states "I don't know how long code-level expertise will remain as valuable as it is today. Models are improving too quickly for much certainty." These two claims sit in tension without being reconciled — the confident framing needs a time-horizon qualifier the piece never supplies.
  Agentic Skill Decay
• incompleteThis is a 1-minute LinkedIn teaser for deeper SINTEF empirical research; no methodology, sample size, or data are given for either the specification/verification time-shift claim or the individual-to-shared-practice claim. The post only links onward to a kode24 article and gestures at a JavaZone talk.
  Nils Brede Moe's Post — read next: Read the linked kode24 article (https://lnkd.in/eKhzYCCt) covering the JavaZone talk, and cross-reference the fuller SINTEF findings already captured in this corpus at extract-heis-09-nils-brede-moe-ai-paradokset-autonomi-laringskultur.json — same researcher, same 'AI-paradokset' framing, with sourced propositions, arguments, and narratives (including the 9-of-10-vs-95% MIT figure and the car-factory study) that this short post compresses away.
• incompleteAttention and orchestrator cognitive-load concerns are absent. The document moves employees from 'producing' to 'reviewing and judgement', as if review is purely value-additive. But review fatigue, automation complacency, deskilling of junior staff who never learn to draft from scratch — these are real failure modes the document does not engage. This is the hidden-layer concern (Bailey, Stolen Focus, Cutler on overload) the reader carries.
  Building AI Agents For The Enterprise — read next: Cutler TBM on institutionalised overload + AI; Bailey on attention infrastructure; deskilling literature; Heis ep 9 Brede Moe on autonomy/learning culture in AI-augmented organisations.
• incompleteAll three case studies come from a single team (Claude Code at Anthropic) building a CLI tool with unusually tight dogfooding loops. The argument that experimentation should replace upfront design is not tested against contexts with higher costs of failure (healthcare, infrastructure, finance), longer feedback cycles, or larger teams where coordination costs dominate.
  Presentation: Engineering at AI Speed: Lessons from the First Agentically Accelerated Software Project — read next: Literature on high-reliability organizations (e.g., Normal Accidents by Perrow); experiences of AI adoption in safety-critical domains
• incompleteThe talk assumes a small, highly skilled team that can make and evaluate architectural decisions rapidly. No discussion of how these practices scale to larger organizations where most engineers are not senior architects.
  Presentation: Engineering at AI Speed: Lessons from the First Agentically Accelerated Software Project — read next: Team Topologies (Skelton & Pais); research on scaling agile and continuous deployment in large organizations
• uninformedThe SQLite analysis conflates SQLite's limitations with the specific way it was deployed (npm native dependency distribution, Better-SQLite3 binding). SQLite-via-WASM (e.g., sql.js) would have avoided the native dependency problem entirely. The multiprocess locking concern is real but standard WAL mode mitigates it significantly.
  Presentation: Engineering at AI Speed: Lessons from the First Agentically Accelerated Software Project — read next: SQLite documentation on WAL mode; sql.js and other WASM-based SQLite distributions
• incompleteNo engagement with whether agile transformation frameworks actually work — the Italian study is summarized but its evidence base is not examined
  Forskning på digitalisering 2026 uke 19
• incompleteThe measurement section invokes Deming but does not specify which concrete metrics would satisfy the learning-over-control criterion in modern agile contexts
  Forskning på digitalisering 2026 uke 19
• incompleteNo discussion of how LLM-generated code interacts with the measurement problem — if LLMs generate code, what does 'developer productivity' even mean?
  Forskning på digitalisering 2026 uke 19
• incompleteThe bonus items (frontline leadership, sustainability micro-foundations, airport effects) are too thinly described to extract any propositions
  Forskning på digitalisering 2026 uke 19
• incompleteThe three practices are validated only by the author's own uncontrolled classroom observation — no comparison group, no measured learning-outcome data, and no discussion of cost/scale requirements (small classes, an arts-department studio culture, custom-built chatbot avatars, TA availability for public critique) that make the approach hard to generalize to large, non-arts-adjacent CS programs.
  Teaching Coding When AI Can Write the Code — read next: Look for controlled or larger-N studies of process-based/performative assessment in programming education, and for follow-on evaluations of teachable-agent-as-assessor systems (extending Betty's Brain-style research to the assessor role rather than the tutee role).
• incompleteNo engagement with organizations that lack Microsoft's scale, cash, or executive sponsorship -- a resource-constrained startup, a non-tech company's small engineering team, or a highly outsourced/offshore engineering org has no obvious path to implementing preceptorship as described (400-500 person 'shards,' formal cohorts, explicit executive buy-in).
  Podcast: How Will We Train Developers If AI Does the Routine Work: A Conversation with Scott Hanselman
• incompleteThe 'third place' collapse and anthropomorphization-of-AI risks are raised as real sociological costs, but Hanselman offers no organizational remedy beyond his own personal practice (periodic travel to Seattle); there is no discussion of what fully distributed, no-office companies could do instead, nor any engagement with whether his prescription (in-person contact) is feasible for organizations that chose remote-first specifically to access geographically dispersed talent.
  Podcast: How Will We Train Developers If AI Does the Routine Work: A Conversation with Scott Hanselman
• incompleteThe five experiments used simulated online communities and freshly presented, lab-constructed material with freshly formed connections -- not real workplace knowledge or the long-standing, trust-laden, expertise-asymmetric relationships that exist in actual organizations. The article does not address whether the tradeoff holds, strengthens, or weakens once relationships are established and repeatedly relied upon over years, as opposed to a single lab session.
  The More Accessible Information Is, the Less Employees Remember — read next: Look for field or longitudinal studies of transactive memory systems in real teams (the classical Wegner transactive-memory literature, or organizational studies of how expertise-location knowledge develops and is used over a team's lifespan).
• incompleteThe piece frames the connectivity tradeoff as a problem to be corrected, but never establishes that it is bad for team- or organization-level outcomes -- only that it changes what individuals remember. If knowledge is efficiently distributed and reliably retrievable through trusted people, that may be a feature of well-functioning distributed cognition rather than a deficit; no group- or organization-level performance comparison (only individual recall) is offered to settle this.
  The More Accessible Information Is, the Less Employees Remember — read next: Look for group-cognition or distributed-cognition research comparing team performance under high- versus low-connectivity/high- versus low-individual-retention conditions, not just individual memory outcomes.
• incompleteTreats overload as a permanent atmospheric condition rather than a designed outcome. The article tells overwhelmed managers how to coach overwhelmed reports about growth, but never asks why aggregate work has expanded or whether it should be cut. The one-sentence 'lighten their load' is the closest it comes — it is not developed and not staffed with examples.
  Supporting Your Employees' Career Growth When Everyone Is Overwhelmed — read next: John Cutler's 'institutionalized overload' (TBM 412 and related) treats overload as a systems problem with feedback loops and organizational levers — read this against Knight's piece to see what's missing when the manager is the only actor in the frame.
• incompleteThe organization as a unit of analysis is absent. No discussion of role architecture, promotion criteria, learning budgets, internal mobility programs, or HR systems. The implicit model is: each manager improvises a development culture inside their span of control, regardless of structure.
  Supporting Your Employees' Career Growth When Everyone Is Overwhelmed — read next: Org-design literature on internal labor markets and skill architectures (e.g., Cappelli on talent on demand) — or Cutler on org operating systems — would supply the missing layer.
• incompleteRisk and accountability are silently transferred to the individual. Career uncertainty caused by employer decisions (layoffs, restructurings, AI deployment) becomes a personal learnability problem. There is no symmetric obligation on the employer.
  Supporting Your Employees' Career Growth When Everyone Is Overwhelmed — read next: Critical management scholarship on the 'enterprising self' and responsibilization (e.g., du Gay, Fleming) — and any HBR-adjacent counterpoint arguing for employer-side commitments.
• illogical'Show your own work' is positioned as the bridge between asking impossible things and maintaining credibility. But if the targets are genuinely impossible (Bidwell's own framing), no amount of leader transparency repairs that; transparency without target reduction is theater. The argument elides the difference.
  Supporting Your Employees' Career Growth When Everyone Is Overwhelmed — read next: Anything on psychological safety as a precondition for honest upward escalation (Edmondson) — to see what 'showing your own work' would need to do to actually change the work, not just narrate it.
• uninformedNo acknowledgment that 'permission to learn' presumes a manager with real slack and political cover to grant time for non-job-essential study. In overloaded, deliverable-tracked teams, that permission is often not in the manager's actual gift — the article assumes managerial discretion that may not exist.
  Supporting Your Employees' Career Growth When Everyone Is Overwhelmed — read next: Cutler on power and space in organizations; flow accounting / slack theory (Tom DeMarco).
• illogicalThe central 'meaning cannot be commodified out' argument rests on one negative case (Buzzfeed's failure) and one still-unresolved positive case (the Atlantic, whose own outcome Elkins repeatedly disclaims — 'we'll see where it goes... I have no crystal ball'). No comparative base rate of publisher-AI licensing deals succeeding versus failing is offered, so the argument's generalizability is asserted rather than demonstrated.
  Are We Entering a New Age of Creativity with the Help of AI? — read next: Longitudinal tracking of publisher-AI deal outcomes (traffic, revenue, subscriber retention) as more of the '70+' deals mature past their first year or two.
• incompleteSame self-report / common-method-bias structure as this corpus's sibling superteam pieces: 'superteam' status is defined entirely by members' own 10/10 rating, and all seven behavioral differentiators (experimentation, curiosity, surfacing problems, involvement, feedback quality, growth support, meaning) are ALSO self-reported by those same members. The correlation could be a halo effect (teams that feel good about themselves report more positive everything on every dimension) rather than evidence that these specific leader behaviors cause learning or performance.
  How to Build a Superteam That Keeps Getting Better — read next: Objective or third-party performance measures paired with longitudinal or experimental designs; this corpus's own critique of the identical design flaw in the companion HBR pieces on connection and on protected focus, both drawn from the same or a sibling 6,000-worker survey.
• uninformedCitations are underspecified throughout: the Journal of Organizational Behavior study on manager involvement gives no sample size, effect size, or definition of 'manage from a distance'; the Frontiers in Psychology moonlighting study names a sample size (324) but no effect size or engagement instrument; every leader-behavior percentage (33%, 43%, 53%, 56%, 59%, 90%+) is reported without a confidence interval, base rate, or description of how 'average team' leaders were sampled.
  How to Build a Superteam That Keeps Getting Better — read next: The original Journal of Organizational Behavior and Frontiers in Psychology papers directly; Ron Friedman's book 'Superteams' (Simon & Schuster, 2026), from which this article is adapted, for full survey methodology.
• illogicalSurvivorship bias in case selection: every illustrative organization (Thunder, Meta, Netflix, Amazon, Spotify, LinkedIn, Microsoft, Airbnb, Adobe, Estée Lauder, HubSpot, Keap, Basecamp, Haberman) is a documented success story for the practice it illustrates. No case of a team that experimented boldly and failed, admitted uncertainty and lost credibility, or had a hands-on leader who tipped into micromanagement is discussed, so each practice's downside risk and failure rate are invisible by construction.
  How to Build a Superteam That Keeps Getting Better — read next: Base-rate and survivorship-bias literature (e.g., Mlodinow, Taleb) applied to management case studies; accounts of experimentation cultures or hands-on leadership that did not pay off.
• incompleteThe article repackages well-established learning-organization and psychological-safety research (Edmondson's psychological safety construct, Senge's learning organizations, Argyris's work on defensive routines and double-loop learning) under the 'superteam'/'continuous improvement' brand, adding survey percentages and a sports narrative, without citing any of these lineages by name or engaging what, if anything, is mechanistically new versus a repackaging with fresh statistics.
  How to Build a Superteam That Keeps Getting Better — read next: Edmondson's 'The Fearless Organization'; Senge's 'The Fifth Discipline'; Argyris on double-loop learning and defensive routines — the clear intellectual ancestors of practices 2, 3, and 5 that this piece never names.
• 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 framing of public-sector dysfunction as 'budget growth instead of value delivery' is a strong claim presented anecdotally. The implicit comparison to private sector ('we are on the same team') under-acknowledges that private-sector alignment is also engineered and partial — shareholder vs. employee interests, sales vs. engineering, short- vs. long-term.
  3) Christin Gorman leder uten tittel — read next: Read Nils Brede Moe (Heis ep 9) on the AI-paradox and learning culture; read public-sector reform literature (NAV's 'optimizing for fast flow' is on the user's list). Also read industrial-organization work on aligned vs. misaligned incentives across sectors.
• incompleteThe episode systematically tells the success-side of the story. Crisis → response → improvement is the recurring arc, but failed experiments, dead-end framework choices, or instances where 'gjøre det lett og rett' produced unintended organisational uniformity are absent. Moe's stated regret is only directional (could have done more, faster, in more places), not structural (e.g. 'this particular default we engineered was wrong'). The hosts twice surface the hierarchy-is-inevitable point but do not press on whether the framework-team's 'easy and right' becomes a hidden orthodoxy.
  5) Vidar Moe: Det eneste Vidar vil er å ha det lett — read next: Pair with Allen Holub's #NoAccountability strand (already in the user's persona) and with anything on the costs of platform-engineering paved roads (e.g. Charity Majors / Honeycomb on the limits of golden paths). The user's existing extraction on Cutler's institutionalised overload is a strong complement here — Cutler's frame would ask what the second-order costs of the SpareBank 1 system look like.
• incompleteMoe's persistent 'vi' is itself a load-bearing rhetorical pattern that the hosts notice in closing but do not unpack. The episode is a portrait of a person who declines to be individuated — he says 'vi' even when narrating decisions whose intellectual origin clearly lies with him personally. This is consistent with the leadership-through-defaults thesis (the work is the structure, not the speaker) but it also obscures the part of the story that does depend on a specific senior practitioner persistently present in the system for 14 years. The question 'how transferrable is this without Moe (and Stian)?' is not engaged.
  5) Vidar Moe: Det eneste Vidar vil er å ha det lett — read next: Read in tension with the previous Heis episode on hierarchy (Eikeland, ep 4, alluded to: 'forrige podcast-episoden snakket om... det er sjelden helt flat struktur') and with the leadership-presence strand in the user's library (Cutler on power and space, TBM 413). Beck's writing on senior individuals' role in evolutionary design is a direct anglophone parallel.
• incompleteThe 'organisatorisk gjeld' coinage at the close is the most pregnant unfinished idea in the episode. Moe gestures at the next direction of 'lett og rett' — engineering golden paths for product development itself, with good practices baked into roadmap tooling — but does not work it out. This is exactly the territory where the AI question reconnects: an agentic product-development assistant that encoded the right defaults could be the next instance of 'lett og rett', and would be a Moe-shaped answer to the alienation worry from his essay.
  5) Vidar Moe: Det eneste Vidar vil er å ha det lett — read next: Pair with the user's existing extractions on harness engineering for AI coding agents and on 'Agents Don't Know What Good Looks Like'. The Backstage / Internal Developer Platforms tradition (Spotify) is the obvious anglophone analogue. Team Topologies (Skelton & Pais) and DORA's recent platform engineering findings are the natural canon. Truls's closing observation that Toyota → DORA → Team Topologies is one lineage is exactly the bridge.
• incompletePair programming is named as the most effective form of knowledge sharing and as the substrate that the rest of the infrastructure exists to support, but the cost question (developer preference, time investment, neurodiversity, hybrid/remote context) is not engaged. Moe acknowledges that change in this direction is 'ordentlig seig' — really tough/slow — but does not ask why even at SpareBank 1, with all the structure in place, pair programming is not yet universal. The same gap exists in his essay's TDD-with-the-agent prescription.
  5) Vidar Moe: Det eneste Vidar vil er å ha det lett — read next: Read Birgitta Böckeler's recent work on remote pair programming, and the user's already-extracted Beck material on TCR (which functions as a half-step toward pair-discipline). The 'AI Joy Gap Developers' extraction the user already has — which treats reconnection-of-developers as needing organisational structure — is a direct complement.
• incompleteThe Norwegian / Lean-Norwegian context is implicit but not theorised. The åremål concept comes from Norwegian political and academic life and is being repurposed for engineering leadership. The fagtid concept has roots in Norwegian work-culture autonomy ideas. The DORA / Lean / Toyota convergence Truls names at the end is itself partially a Nordic management-culture convergence. There is a comparative essay latent here that the episode does not write.
  5) Vidar Moe: Det eneste Vidar vil er å ha det lett — read next: Read in parallel with NAV's 'optimizing for fast flow' piece (already in the user's queue), with Norwegian Self-Determination Theory–inflected management writing (autonomi, mestring, mening), and with the wider tradition of Nordic engineering culture vs. anglophone agile-at-scale. The user's coding-agents corpus already includes Nils Brede Moe (no relation? — but a Nordic empirical-software-engineering voice in the same neighbourhood, including the upcoming Heis episode 9).
• incompleteThe MIT '95% of AI projects show no return' figure is asserted as foundational but never sourced, methodologically interrogated, or compared to base rates for non-AI IT projects (where failure rates are also famously high). The framing relies heavily on this number.
  9) Nils Brede Moe om AI-paradokset, autonomi, læringskultur og fremtidens team — read next: Pursue the MIT study directly (likely the MIT NANDA / Sloan AI 'GenAI Divide' report from 2025) and compare against Standish CHAOS-style baselines for IT project failure to establish whether AI is failing more than other IT initiatives, or merely the same.
• incompleteThe framing is almost entirely about knowledge-work software teams in professional services / large org settings. The argument is silent on: solo developers, small startups without team infrastructure, contracting/outsourcing relationships, non-developer roles where AI is also disrupting work, and contexts where 'team' is not the unit of production.
  9) Nils Brede Moe om AI-paradokset, autonomi, læringskultur og fremtidens team — read next: Read Tabarrok / Acemoglu on AI and labor markets in non-team-shaped work; and Beane's Skill Code on apprenticeship in mixed expert/AI environments outside software, to test how portable Brede Moe's prescriptions are.
• incompleteThe conversation treats AI tooling as relatively homogeneous — Copilot, ChatGPT, Cursor, Claude Code are mentioned as a cluster. But the team-level practices likely differ between chat-based assistants, autonomous agents, and in-IDE pair tools. Brede Moe gestures at this with 'augmented teams' but doesn't yet differentiate.
  9) Nils Brede Moe om AI-paradokset, autonomi, læringskultur og fremtidens team — read next: Empirical studies of differential effects by tool class — DORA's 2025 AI findings, Microsoft / GitHub research on Copilot effects, ongoing studies of agentic coding tools.
• incompleteThe car-factory study (cited as 15-20 years old) is the central empirical anchor for the slow-down-to-speed-up claim, but it is cited without source — the listener cannot evaluate the comparison. Similarly the 9-of-10 figure.
  9) Nils Brede Moe om AI-paradokset, autonomi, læringskultur og fremtidens team — read next: Source the original study; even if accurate, ask whether software development resembles auto-manufacturing learning curves enough for the lesson to transfer.
• incompleteThe argument assumes that team autonomy and team learning are the right units of analysis. It does not engage with alternative views — e.g. that AI might shift the unit back to the individual contractor or fragment work into smaller, more decomposable tasks, in which case the team-level prescription is the wrong response to the wrong question.
  9) Nils Brede Moe om AI-paradokset, autonomi, læringskultur og fremtidens team — read next: Read agentic-work literature (Eric Ries, Naval-style 'agency leverage' arguments, Yegge's vibe-coding manifesto) for the opposing view.
• incompleteThe conversation explicitly opens but does not close the team-augmentation question — what does multi-agent + multi-human team coordination look like in practice? Vilde admits FINN/Vend has not cracked it.
  11) AI-spesial med Vilde Opsal og Anders Sveen — read next: Nils Brede Moe (Heis ep 9) on AI paradox + autonomy + learning culture; Pocock workshop on harness design for long-running agent teams; emerging literature on multi-agent code review and orchestration.
• incompleteNorwegian/Nordic constraints (persondata, public-sector compliance, sovereignty, DPA-with-Anthropic) are mentioned repeatedly but never developed into a coherent picture of how the Norwegian stack will diverge from the US default agent stack.
  11) AI-spesial med Vilde Opsal og Anders Sveen — read next: Smidigposten / Norwegian agile community pieces on public-sector AI; sovereign-AI / data residency discussions; Vipps/DNB/NAV-specific writeups.
• uninformed (in a time-stamped sense)The episode is explicitly dated end of January 2026 and pre-DeepSick announcement; the participants flag this themselves.
  11) AI-spesial med Vilde Opsal og Anders Sveen — read next: Re-listen after major model releases; compare against follow-up Heis special when produced.
• incompleteThe flywheel/S-curve/liminal frame is used to describe both the NAV transformation (which succeeded) and the AI shift (in progress). The conversation never names a transformation that failed at the liminal phase and asks why — so the framework is at risk of being unfalsifiable on its own terms.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Read failed transformations through the same frame — e.g., government-IT projects that died in their liminal phase, large agile adoptions that reverted. Cutler's overload work and the 'people who tried Spotify model' literature would expose where the frame breaks. The Geoffrey Moore 'Crossing the Chasm' tradition has more developed accounts of curves that stall.
• incompleteThe 'learning vs production' rule is stated as a personal heuristic but not connected to any educational theory or empirical evidence. For a leader of consultants asked to scale this practice, there is no model for how the two modes should be partitioned, whether across days, projects, or moods.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Donald Schön's reflection-in-action; deliberate-practice literature (Ericsson); Beck's 'tidy first?' framing of preparatory vs delivery work — the tidy/messy split echoes the learning/production split structurally. Worth syntopical pass against Beck's recent 'Starving Genies' work on AI-assisted craft.
• incompleteThe elevator metaphor is generalised from Jonas's own career and from the show's animating premise. The conversation does not seriously consider organisations where vertical traversal is structurally suppressed (military, regulated finance with information walls, classified environments). The implicit premise that elevators are always available may not hold.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Read about organisations with designed information barriers — security classifications, MAR-walled investment banking, healthcare compartmentalisation. James C Scott's 'Seeing Like a State' on legibility. Where the elevator is locked, what substitutes?
• incompleteThe introvert-leader claim rests on one practitioner's experience and one rhetorical contrast (scale removes small-talk tax). Jonas notes that some colleagues found it hard to distinguish his opinions from his decisions — a cost that may be specifically introvert-shaped (lower social-cue density) but is not investigated.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Susan Cain on introvert leadership; the Cutler thread on 'signals that look like decisions' in leadership communication. The implicit problem of 'low-cue leadership at scale' is worth its own extraction.
• incompleteThe tractor and car analogies argue for slow structural change, but neither is examined for disanalogies. AI compresses learning loops in a way physical machinery cannot. The argument relies on the assumption that adoption is gated by humans, not by capability — which is plausible but not defended.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: The general-purpose-technology economics literature (Bresnahan & Trajtenberg); David Autor on labour-market restructuring time. Counter-cases: dial-up to broadband transitions, mobile phones — both moved faster than tractors. What predicts speed?
• uninformedThe Gukesh anecdote is reported confidently ('the only one of the young players not allowed a computer before age 12') but is not actually verified in the conversation. Whether true or apocryphal, it is doing argumentative work it has not earned.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Quick fact-check; more importantly, treat the underlying claim about protected early craft as a hypothesis and look at the actual evidence on AI use in early-career learning — programming pedagogy research will move on this in 2026-2028.
• incompleteThe claim that NAV's success was driven by capability investments is asserted from inside the case by the very people who made those investments. There is no counterfactual — no comparable agency that did not invest similarly and failed similarly. Some of the 'flywheel' may be storytelling.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Compare cross-country COVID welfare-IT responses (Germany, Denmark, UK), and Norwegian agencies of similar size that did not transform similarly. The Skatteetaten and Helsedirektoratet experiences would be a natural comparison.
• illogicalJonas argues both that we are early on the AI S-curve (so 10% gains are not the story) and that complexity will push back on productivity gains as they accumulate. These are compatible but in tension: if the curve climbs steeply because of intent-level abstraction, the complexity ceiling should appear later; if complexity bites soon, the curve is shallower than claimed. The argument is not adjudicated.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: The Brooks / Mythical Man Month tradition on accidental vs essential complexity; Ousterhout on system design; recent measurements on long-running agent harnesses (Anthropic harness design work) which directly test the complexity-ceiling claim.
• incompleteThe 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.
• incompleteEvery case in the article — Gupta, Horta-Osório, the unnamed industrial-company CEO, the energy-company CEO, the pharma CFO, the retail-bank CEO — sits at CEO, chairman, or C-suite level. The article's own opening claim ('the bottleneck is at the top') is never tested against a case where the bottleneck is one level below the top: a business-unit leader or VP whose own boss is not modeling the transformation. It is left unaddressed whether visible modeling by a sub-CEO leader can still move their own team's behavior, or whether the effect requires the very top of the hierarchy to model it.
  Model the Transformation You Expect Employees to Deliver — read next: Read alongside middle-management- or informal-leadership-focused accounts of change agency operating without top-level air cover, to test whether 'modeling' works bottom-up/mid-up or only top-down.
• incompleteThe McKinsey and Prosci statistics (5.3x more likely to succeed; 79% vs 27%) are presented as if the causal arrow runs cleanly from leader modeling to transformation success. The article does not consider or rule out reverse causation (transformations that are already succeeding for other structural reasons — better resourcing, less internal politics, a healthier starting culture — may simply free leaders to model behavior visibly, rather than the modeling causing the success) or confounding (leaders confident and secure enough to visibly take personal risk may be systematically different, and more effective for unrelated reasons, from leaders who are not).
  Model the Transformation You Expect Employees to Deliver — read next: Read alongside the original McKinsey and Prosci methodology write-ups to check whether either study attempts to control for confounds or establish direction of causality, or is purely correlational self-reported benchmarking.
• uninformedThe article treats the Credit Suisse collapse as if the modeling failure were the decisive cause ('at its heart is Horta-Osório's failure to embody and model the transformation'), while its own text names the Greensill and Archegos losses (the latter alone costing about $5.5 billion) as having already 'laid bare' the cultural problem before Horta-Osório's appointment. It does not engage with the possibility that Credit Suisse's fate was already largely sealed by those prior losses and the resulting collapse in market and counterparty confidence, independent of whether the chairman personally modeled accountability afterward.
  Model the Transformation You Expect Employees to Deliver — read next: Read banking-sector post-mortems on Credit Suisse's collapse (regulatory reports, the Swiss FINMA assessment) that weigh governance/risk-control failures against leadership/cultural factors, to establish whether the modeling-failure framing is proportionate to its actual causal weight.
• incompleteMerchant assumes co-decided ownership always produces better outcomes than directed change but never addresses contexts where it might fail — e.g., crisis situations requiring speed, organizations with deep expertise asymmetries, or cases where employees genuinely lack the context to contribute to strategic decisions. The ownership model may have boundary conditions she does not explore.
  New Skills to Navigate Continuous Change — read next: Gary Klein's work on naturalistic decision-making; research on when participatory vs. directive leadership outperforms.
• incompleteThe AI argument is instrumentally deployed to support her pre-existing thesis but is not seriously engaged. She uses a single data point (19% error rate) and does not consider how the argument changes as AI capabilities improve. The claim that question-formulation is uniquely human is asserted without defense.
  New Skills to Navigate Continuous Change — read next: Ethan Mollick's work on AI and organizational productivity; Karim Lakhani's full research (which Merchant cites but only partially).
• incompleteNo measurement framework for the intangible qualities she advocates (curiosity, creativity, collaboration). She identifies the measurement gap but does not close it. Leaders who want to implement her advice have no way to know if it is working.
  New Skills to Navigate Continuous Change — read next: Amy Edmondson's psychological safety measurement instruments; Teresa Amabile's research on measuring creativity in organizations.
• incompleteThe burnout question is acknowledged but not adequately addressed. In a world of continuous change where leaders must constantly tolerate discomfort, the sustainability question is critical. Merchant's answer (signal that rest matters) is necessary but clearly insufficient.
  New Skills to Navigate Continuous Change — read next: Christina Maslach's burnout research; Cal Newport on sustainable productivity.
• illogicalMerchant claims strategy arcs have shrunk to near-zero (citing Rita McGrath) while also claiming collaborative co-creation of strategy (which takes weeks) is the answer. There is a tension between 'the world moves too fast for long-term strategy' and 'we should slow down to co-decide.' She resolves this through the 'go slow to go fast' aphorism but does not seriously address the timing tension.
  New Skills to Navigate Continuous Change — read next: Rita McGrath's 'The End of Competitive Advantage' for the full argument on transient advantage and its implications for decision speed.
• incompleteThin evidence for the durability claim itself. 'Make it stick' is asserted (OKRs, report-of-the-year four years running) but four years of sustained report engagement is not the same as a proven, self-sustaining continuous-improvement culture that would persist if the driving team were removed.
  DORA Community Discussion - Operationalizing DORA within a large organization — read next: Longitudinal studies of change persistence after a champion or program team departs; measures of institutionalization beyond engagement metrics.
• incompleteThe article pairs a structural diagnosis (burnout is produced by the achievement society) with an almost entirely individual remedy (defuse the thought, say no, schedule boredom), and never addresses who can actually afford to opt out. The person with precarious work, caregiving load, or a genuinely external boss cannot simply reclaim 'sovereignty' by delaying an email. The locus of the disease (social structure) and the locus of the cure (private attitude) are mismatched.
  This Is How To Overcome Burnout: 5 Secrets From Philosophy — read next: Read alongside extract-burnout-across-org-chart (burnout as an organizational design failure that varies by one's power, control, and moral load) and John Cutler on institutionalized overload — the systems-and-power dimension this piece brackets.
• incompleteEmpirical support is a single mind-wandering citation doing very heavy lifting. The leap from 'the idle brain does useful work' to 'scheduled boredom cures burnout' is asserted, not evidenced, and the piece substitutes theoretical authority (Han) for a mechanism. Pop-philosophy framing skips the empirical rigor its confident prescriptions would require.
  This Is How To Overcome Burnout: 5 Secrets From Philosophy — read next: Recovery-science literature — Sonnentag on psychological detachment, Maslach's exhaustion/cynicism/inefficacy model — and the attention research the persona already tracks (Stolen Focus, Hyperfocus) to test the boredom-and-rest claims against data.
• incompleteCognitive defusion is offered as the answer but compressed to a slogan. The article concedes that ambition and conscientiousness are 'good' yet 'can get out of hand', but gives the reader no criteria for distinguishing the healthy version from the pathological 'invisible boss' — i.e., when to obey the thought and when to defuse it. Without that boundary, 'says who?' risks becoming a license to defuse any inconvenient obligation.
  This Is How To Overcome Burnout: 5 Secrets From Philosophy — read next: ACT clinical literature (Steven Hayes) on defusion and its limits, and CBT on separating adaptive from maladaptive cognitions — the diagnostic criteria the essay omits.
• incompleteNo treatment of why leaders might rationally choose not to redesign even after correctly spotting the pattern — cost, disruption risk, uncertain payoff, or the political capital required to dismantle a structure that loyal managers are actively protecting. The post implies redesign is the obvious next step once identified, but doesn't engage with the asymmetry that makes the symptomatic fix (workaround) persistently cheaper than the fundamental fix (redesign) — the same asymmetry the 'Shifting the Burden' systems archetype describes.
  Pascal BORNET's Post — read next: Systems-thinking literature on the Shifting-the-Burden archetype (Senge) and on why symptomatic solutions crowd out fundamental ones.
• incompleteThe post never distinguishes this 'bad' resilience (workaround-masking) from legitimate resilience — a system's genuine, healthy capacity to absorb shocks without needing structural change. As written, 'resilience' is used almost entirely pejoratively, which risks reading as an argument against slack/buffer capacity generally rather than against dysfunction specifically.
  Pascal BORNET's Post — read next: Resilience-engineering tradition (Hollnagel, Woods, Dekker) treats resilience as the adaptive capacity of a sociotechnical system — a largely positive framing this post never engages with or reconciles its own usage against.
• incompleteFowler explicitly names 'how do we best operate with AI in the team environment' as an open question his own organization is 'still trying to figure out' — but the entire conversation's concrete advice (vibe-coding boundaries, PR-style review of AI output, building a shared vocabulary, thin specs) is framed at the level of one developer and one LLM. No team-level operating model (shared context across team members, division of review labor, how a team maintains a common mental model of a codebase that multiple AI-assisted people are editing) is even sketched.
  How AI will change software engineering – with Martin Fowler — read next: Look for emerging practitioner accounts of team-scale (not individual-scale) AI coding workflows: shared harness/context conventions across a team, how code review scales when every team member is AI-accelerated, and how a team keeps a common mental model of a codebase multiple people are editing with AI assistance.
• uninformedFowler attributes the current software-industry downturn and job losses primarily to the end of zero-interest-rate financing rather than AI, but does not engage with the counter-evidence elsewhere in the discourse that some of the layoff wave is genuine AI-driven restructuring (not merely macroeconomic or a cover story) — he states his view confidently without weighing the split causation other commentators report.
  How AI will change software engineering – with Martin Fowler — read next: Compare against corpus accounts that split the layoff wave into AI-washing/cover-story and genuinely AI-driven restructuring components.
• incompleteThe article asserts that behavior-focused, workflow-embedded training builds 'amplifier' behaviors, citing KPMG's own program as a test case, but reports no before/after outcome data, control group, or effect size — only "early results suggest." The load-bearing premise underneath every prescription (that these behaviors are teachable and that training measurably shifts people between profiles) is asserted, not demonstrated.
  Research: Why Some Junior Employees Work Well with AI—and Others Don’t — read next: Longitudinal or intervention studies testing whether AI-collaboration training changes an individual's performance-profile classification over time; a follow-up KPMG/UT Austin publication with pre/post data.
• illogicalThe 'AI as junior developer' metaphor contains a self-defeating dynamic the author doesn't notice: if AI eliminates junior training, and seniors are needed to guide AI, then the pipeline that produces seniors is broken. The metaphor predicts its own obsolescence — eventually there are no seniors left to guide the AI-junior. This is the most consequential implication of the post and it goes entirely unaddressed.
  SMOC.AI's Post — 5 Minutter: AI og utviklere — read next: Systems thinking (Meadows) on stocks and flows — the senior developer pool is a stock that requires inflow from the junior pipeline; cutting the inflow depletes the stock over time
• incompleteThe claim that AI code quality is 'often low' is stated but not analyzed. Low in what dimension? Maintainability? Correctness? Performance? Architecture? Different quality dimensions have different implications for when and how AI should be supervised.
  SMOC.AI's Post — 5 Minutter: AI og utviklere — read next: DORA 2025 findings on AI and code quality; empirical studies on AI-generated code defect rates
• illogicalThe paper treats 'evening out' individual performance as a possibly controversial but basically technical question (does the team lose value from suppressing star performers?) without considering that this is also an ethical/motivational question — whether star performers themselves experience mobbing as a demotion of their contribution, which could predict attrition independent of raw output effects.
  Mob programming: From avant-garde experimentation to established practice — read next: Read against retention/motivation literature on high performers in flattened, collectivized work structures.
• evidentiaryAll supporting evidence comes from retail, service, hospitality, and franchise contexts; the author acknowledges seeing 'similar principles' in other sectors but provides no cases outside these domains, leaving the framework's generalizability to knowledge-work, tech, or manufacturing undemonstrated.
  How Fast-Growing Companies Can Make Better Decisions
• methodologicalThe case studies are observational and retrospective; no controlled comparison or counterfactual analysis is presented. OXXO's tripling of stores and doubling of profitability is attributed to structured empowerment, but confounding factors (market growth, competitor dynamics, macroeconomic conditions) are not addressed.
  How Fast-Growing Companies Can Make Better Decisions
• conceptualThe boundary between 'structured empowerment' and well-designed delegation with guardrails is under-theorized. Many mature organizations already provide decision playbooks and measure outcomes; the article does not clearly distinguish where existing management practice ends and structured empowerment begins.
  How Fast-Growing Companies Can Make Better Decisions
• incompleteThe 'raise the floor but not the ceiling' claim is repeated approvingly but never operationalized. How does a leader, in practice, recognize ceiling-extending original work as opposed to confidently-presented model-mediated work? Without a heuristic, the framing becomes a flattering self-description rather than a usable filter.
  SWLW #701: Gazing at the misty AI Frontier, From Vibe Coding to Agentic Engineering, and more. — read next: Read Cedric Chin on tacit knowledge or Tyler Cowen on 'what counts as taste in an AI era' for concrete diagnostics; also Karpathy's full talk for his hiring criteria as a partial answer
• incompleteTwo of the curator's headline framings — 'AI raises the floor' and 'AI eats closed loops first' — are pulled toward each other but not reconciled. If AI raises the floor on closed-loop work, the implication is that closed-loop expertise becomes commodity labor while open-loop / relational / ethical work becomes the new premium. The newsletter implies this but does not state it, leaving leaders without an explicit instruction.
  SWLW #701: Gazing at the misty AI Frontier, From Vibe Coding to Agentic Engineering, and more. — read next: Elad Gil's full 'Misty AI Frontier' piece + a careful read of Yue Zhao's leadership argument against Christensen's disruption framing — the synthesis is more useful than either alone
• incompleteThe newsletter implicitly equates 'agentic engineering' (a craft skill) with 'agentic leadership' (a hiring/strategy task) but never separates them. Whether the same person should both code with agents and lead teams that code with agents — and whether the screening criteria are the same — is left ambiguous.
  SWLW #701: Gazing at the misty AI Frontier, From Vibe Coding to Agentic Engineering, and more. — read next: Bruno Fernandez-Ruiz's 'Engineering in the Compiler Age' slides (referenced here, worth a focused extraction) and Karpathy's actual hiring section to see how he separates IC craft from leadership selection
• incompleteThe 'Anthropic AI-resistant evaluation' story is treated as a positive exemplar, but the newsletter does not engage with the obvious tension: a long-horizon take-home where AI is permitted requires significant unpaid candidate time, which is a known equity problem. The curator endorses the design pattern without acknowledging its cost.
  SWLW #701: Gazing at the misty AI Frontier, From Vibe Coding to Agentic Engineering, and more. — read next: The original Anthropic write-up, plus any of the recent compensated-interview / pair-programming-screen literature, for a more honest cost-benefit picture
• illogicalThe endorsement of 'gut over head' (SahilBloom tweet) sits uneasily next to the endorsement of 'shared design concept before you code' (Pocock). The first valorizes unjustified judgment; the second valorizes explicit-and-shared rationalization before action. The newsletter treats both as obviously correct without noting that they pull in opposite directions for a leader deciding which to lean on in a given situation.
  SWLW #701: Gazing at the misty AI Frontier, From Vibe Coding to Agentic Engineering, and more. — read next: Daniel Kahneman on when intuition is trustworthy (closed environments with rapid feedback — i.e., precisely the closed loops AI is eating); Gary Klein's recognition-primed decision research for the conditions under which gut beats analysis
• incompleteThe essay provides no method for diagnosing which strategy to apply where — the questions at the end are reflective prompts, not a decision framework. How do you determine whether a given consistency point should be sharp, flexible, or legible variety?
  TBM 421: Minimally Viable Consistency (Part 3)
• incompleteJob 3 is missing from the AI section (jumps from Job 2 to Job 4) — either an editing artifact or a deliberate omission, but it is unexplained.
  TBM 421: Minimally Viable Consistency (Part 3)
• incompleteThe taxonomy is presented as exhaustive (three strategies) but no argument is given for why these three are sufficient. Could there be a fourth strategy (e.g., emergent consistency that arises from shared tooling without explicit design)?
  TBM 421: Minimally Viable Consistency (Part 3)
• incompleteThe AI risk analysis identifies that friction can be a learning mechanism but offers no heuristic for distinguishing productive friction from pure overhead — the central practical question for anyone applying the framework to AI adoption.
  TBM 421: Minimally Viable Consistency (Part 3)
• incompleteAdler's four gap forms (uninformed/misinformed/illogical/incomplete) presuppose an argument to evaluate, but this excerpt supplies none — it is a toolkit table, a set of reflection prompts, a glossary, and acknowledgments. The evidence, worked examples, and inferential support for claims like 'quality of experience beats efficiency' or 'intentional imperfection produces better long-term outcomes' live in the book's main chapters, which were not captured in this Reader save. Nothing here can be assessed as backed by real mechanism or research versus inspirational framing, because no mechanism or research is presented at all — only vocabulary and prompts.
  Tiny Experiments — read next: Read the book's actual chapters (not this back-matter excerpt) to evaluate whether the experimental-mindset thesis is supported by cited research or worked case studies, or is asserted by authority and narrative alone.
• incompleteTrust is treated as one undifferentiated resource. Trust between paired programmers, trust from the rest of the team, trust from the customer, trust in the system (observability) — Beck collapses these. But they have different production functions, different decay rates, and may not be substitutable. A skeptic might point out that customer trust is far more about delivered value than pairing rituals, while pair-trust is largely independent of customer outcomes.
  Trust Factory — read next: Janson + Wester on pair-trust (Heis ep 6 — 'if something feels off, say it once'); Printzell Halvorsen on Nordic societal trust enabling distributed teams (Heis ep 8); Onora O'Neill on the trust-trustworthiness distinction and on different kinds of trust requiring different verification structures.
• incompleteThe 'trust factory' metaphor is endorsed without examining what it concedes. 'Factory' implies trust is manufactured by repeating standardized processes — but a major tradition (cultural, philosophical, theological) treats trust as precisely the kind of thing that cannot be manufactured. Beck does not engage this objection. The metaphor's industrial framing also obscures that XP practices may have worked because they instantiated values the practitioners already held — not because the practices produced the values.
  Trust Factory — read next: Cutler on operating-system design vs cultural pre-conditions (TBM series); Diego Gambetta on trust as a non-manufacturable resource; the 'culture eats process for breakfast' literature.
• incompleteThe four 'slow development' prescriptions are stated but not operationalized for the augmented case. How exactly do you 'slow development to encourage frequent person-to-person interaction' when the genie is so seductive? What are the equivalent of XP practices for the augmented era? Beck explicitly defers this ('not yet settled') but a reader looking for action is left with a principle, not a practice.
  Trust Factory — read next: Beck's own subsequent essays (the 'XPAI' thread he's hinting at); Birgitta Böckeler on harness engineering; Garg on reducing friction in AI development (both already in the user's extracted corpus); Bockeler/Anthropic harness writing.
• incompleteThe cultural specificity of trust is not addressed. XP emerged in a high-trust professional subculture (Chrysler C3, early agilists). Whether the trust factory works in low-trust organizational contexts — or only metabolizes pre-existing trust — is left untested. Same question applies to whether trust factories scale across cultural and national boundaries.
  Trust Factory — read next: Printzell Halvorsen on Nordic high-trust societies enabling distributed teams (Heis ep 8); Fukuyama on high-trust vs low-trust societies; cross-cultural management literature.