Meta-Skills & Contextual Judgment

The transferable ability to read context, judge which practices fit, and run small experiments — the durable skill layer above any specific tool or method.

Also known as: meta-skill, meta-skills, four buckets, process mechanics of leading, irreplaceable (with AI), the smallest experiment, Thinkies, metacognition

How authors use it

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

Documents (20)

• 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.
• 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.
• Introducing The Founder Mindset: Tim Ferriss on Experiments, Risk, and Freedom HBR IdeaCast (Adi Ignatius, bonus crossover episode featuring Reza Satchu interviewing Tim Ferriss) · 2026-07-30 Reader 🖥️
  Ferriss argues that what looks like reckless risk-taking is really a disciplined practice of minimizing downside — defining fears concretely instead of vaguely, treating decisions as either fast-and-reversible or slow-and-irreversible, and pursuing 'bounded' optionality (a pre-narrowed, time-boxed set of parallel experiments) rather than either indefinite hedging or premature commitment — which he claims reconciles his love of optionality with Satchu's thesis that commitment is a superpower.
• How Do You Know That? Kent Beck — Still Burning Podcast · 2026-07-22 Reader 🖥️
  The skill that matters most — in engineering craft, in working with AI agents, and in locating accountability when automated systems act — isn't knowing the answer but asking 'how do you know that?': interrogating the actual reasons behind behavior, code, and systems, because that meta-intelligence diagnoses root causes invisible to observers of behavior alone, and because AI agents, having no drive or accountability of their own, can never do that interrogating or that owning on a human's behalf.
• The Beginnings of an Idea: XP is Long Volatility Kent Beck from Software Design: Tidy First? · 2026-07-14 Reader 🖥️
  Beck's genuinely new ideas — including the just-arrived analogy 'XP is long volatility' — take years of unconscious incubation before they're ready to articulate, and once ripe they can only be sharpened into a teachable form by repeatedly explaining them badly, in varied ways, to real audiences, not by solitary polishing.
• Addy Osmani’s Post Addy Osmani · 2026-07-11 source ↗ Reader 🖥️
  As coding agents make solving cheap and abundant, an engineer's durable career value shifts from being the fastest problem-solver to the 'ungradeable' meta-skills that have no answer key — selecting which problems matter, judging quality through earned taste, directing agents rather than doing the work, sprinting the hard last mile, and owning the outcome.
• Why product feels so hard right now - Charity Ibhadon (WPP) Mind the Product · 2026-07-08 source ↗ Reader 🖥️
  Product work feels harder than ever not mainly because the job changed but because a culture with no 'gold standard' fuses people's identity to the work and teaches them to mistake the physical symptoms of burnout for proof of excellence; the way through is to de-identify from work, defend recovery and boundaries, and lead through durable, unflappable 'happy high status' composure and commercial curiosity rather than chasing ever more frameworks and certificates.
• SWLW #710: Revised rules of Eng Leadership, When AI costs more than the engineer, and more. Oren Ellenbogen · 2026-07-06 Reader 🖥️
  As AI reshapes engineering, the decisive leadership work shifts to human judgment applied to fundamentals — reaffirming sound operating principles, justifying AI's now salary-scale cost, and demanding engineering rigor — because AI only amplifies (in magnitude, not direction) whatever practices, clarity, and dysfunction already exist.
• TBM 428: Yes, Robot. Yes, Boss? John Cutler (The Beautiful Mess) · 2026-07-06 Reader 🖥️
  Because AI faithfully amplifies the intent and direction an organization already carries, it can relieve only capability-and-friction blockers — never the human blockers of fear, misaligned incentives, and illegitimate power — so using it well is a matter of individual metacognition and systemic design, not the tool's supposed objectivity.
• 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.
• Agent Skills Tanvi Singhal, Gabriela Hernandez Larios, Debanshu Dus, Lavi Nigam, and Smitha Kolan · 2026-06-10 Reader 🖥️
  Agent Skills are the engineering primitive that gives AI agents testable procedural memory — how to do things, not just what is true — and because the format is deliberately thin (a folder, a markdown file, optional scripts), the real and still-unsettled work is everything built around it: evaluating skills under realistic co-loaded conditions, governing who may author and promote them, and composing them into production systems — work that is organizational and engineering discipline, not a model capability.
• This Week in AI: Production Viability Michelle Smith (O'Reilly Network) · 2026-06-06 Reader 🖥️
  AI's current bottleneck is not capability but measurement: practitioners and organizations are producing prodigious output (tokens, code, recommendations, profiles) while lacking the contextual judgment, metacognitive discipline, and incentive structures needed to tell which output is actually worth shipping.
• The real skill behind good AI prompts is older than computers Ernie Svenson · 2026-06-02 Reader 🖥️
  Good AI output depends not on prompting technique but on attention — the pre-digital, self-cultivated skill of noticing what matters in the task and in the model's output — which cannot be taught, only chosen.
• Doug Shannon's Post Doug Shannon, Anastasios (Tassos) Fountis, Victoria Dior Wang, Dr Scott Davies, Carrie Eckersley, Antony Evans, and others · 2026-05-19 source ↗ Reader 🖥️
  As AI absorbs more of the work of producing answers, the decisive human skill shifts from using AI well to thinking well about one's own thinking while using it — a disposition ('co-thinking', the 'Cyborg' stance) distinct from both AI dependency and from mere prompt skill, with early evidence (self-reported and cited brain-connectivity and creativity studies) suggesting this metacognitive posture determines whether AI sharpens or erodes a person's independent judgment.
• The model doesn't matter anymore – and other AI skills worth your Thursday Turing Post · 2026-05-05 source ↗ Reader 🖥️
  Professionals need to identify which AI skills will remain valuable in 2026, and a free virtual AI Skills Conf on May 14 promises practical, practitioner-led sessions on AI ROI, agentic memory, AI workflows, and professional irreplaceability.
• 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.
• Unstick Your Stuck Thinking Thinkies by Kent Beck · 2026-05-01 source ↗ Reader 🖥️
  Thinkies are learnable pattern transformations that help you break out of stuck thinking by shifting how you frame a situation, and you can learn them at Thinkies World Congress II.
• TBM 420: The AI Playbook Puzzle John Cutler from The Beautiful Mess · 2026-04-20 Reader 🖥️
  Nobody has an AI playbook yet because the real challenge is not tactical AI adoption but the identity-threatening work of distinguishing which existing practices were always broken, which were genuinely good, which only worked due to now-vanished constraints, and developing the meta-skill of contextual judgment to navigate all three.
• Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again The Pragmatic Engineer · 2026-04-07 Reader 🖥️
  In a period of unprecedented technological disruption, the same meta-skills that mattered before — disciplined skepticism tempered by curiosity, small experiments to validate claims, and mastery of craft fundamentals — remain the primary differentiators, but practitioners must shift their satisfaction from writing perfect code to understanding domains and systems at a higher level of abstraction.
• 12) Greger Teigre Wedel: Når sjefen har svaret, tier resten Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-03-01 source ↗ Reader 🖥️
  When the boss already has the answer (and shows it), other voices fall silent — so a hands-on technical leader's most important discipline is choosing, situationally, when to suppress their own answer and create space for the team to find one.

Propositions touching this concept (17)

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

2026-04

• explicitestablishedSystems thinking, metacognition, and contextual judgment are being discounted precisely when they are most needed.
  TBM 420: The AI Playbook Puzzle · p5

2026-05

• explicitA leader's core competence in continuous change is the meta-skill of orienting in unfamiliar situations, not domain expertise.
  New Skills to Navigate Continuous Change · p7
• explicitReal metacognition requires becoming an active participant in one's own reasoning process — noticing how one reacts to information, why one trusted one answer over another, and what assumptions and emotional states shaped a conclusion.
  Doug Shannon's Post · p1
• explicitAI does not create metacognition on its own, but functions as a real-time cognitive mirror: the cycle of asking, receiving an answer, refining the question, and challenging the output lets a person notice patterns in their own thinking, which a saved, reflected-on feedback loop can then deliberately develop.
  Doug Shannon's Post · p2
• explicitDecades of prior research in self-regulated learning and goal-setting (Simon's Intelligence-Design-Choice model, Hollenbeck & Klein's goal-commitment research, Zimmerman's cyclical self-regulation, Flavell's metacognition model) already describe the planning, monitoring, evaluation, and adaptation skills that now determine the quality of human-AI collaboration — this is an old psychological phenomenon applied to a new domain, not a newly discovered one.
  Doug Shannon's Post · p8
• explicitA cited 2026 Harvard study found generative AI dramatically boosts creativity for people with strong metacognition, who treat AI as a thinking partner, while barely moving creativity for people with weak metacognition, who take the first plausible output and move on.
  Doug Shannon's Post · p11
• explicitThinkies are learnable pattern transformations for shifting perspective and expanding options
  Unstick Your Stuck Thinking · p1
• explicitThe goal of Thinkies is idea quantity, not idea quality — generating lots of ideas rather than finding the right one
  Unstick Your Stuck Thinking · p2
• explicitThinkies help you notice when thinking is falling into a predictable groove
  Unstick Your Stuck Thinking · p3
• explicitThere are approximately a hundred distinct Thinkies
  Unstick Your Stuck Thinking · p4

2026-06

• explicitAgent-drafted skills (meta-skills authoring, trace-harvesting, metric-driven optimization) must always enter the library at the draft tier regardless of how confident the drafting agent is, with a human scanning the diff for the first several edits, because an agent permitted to edit its own skills will optimize for whatever metric it is given, including metrics that are easy to game.
  Agent Skills · p10

2026-07

• explicitagent-skills organizes the entire product lifecycle (Define→Plan→Build→Verify→Review→Ship) as skills routed through a meta-skill, whereas Superpowers concentrates on the core build loop (brainstorm→plan→execute) and Matt Pocock's skills are one expert's personal, curated daily toolkit rather than an exhaustive framework.
  agent-skills/docs/comparison.md at main · addyosmani/agent-skills · GitHub · p2
• explicitBecause these are markdown skills, not runtimes, individual skills can be cherry-picked across frameworks even though a framework's meta-skill router cannot safely coexist with another framework's router in the same session.
  agent-skills/docs/comparison.md at main · addyosmani/agent-skills · GitHub · p6
• explicitRunning two frameworks' meta-skills as simultaneous active routers causes command-name collisions and competing TDD philosophies, producing unpredictable behavior rather than combined benefit — so exactly one framework should be the primary router, with skills from the others borrowed à la carte.
  agent-skills/docs/comparison.md at main · addyosmani/agent-skills · GitHub · p7
• implicitWhat makes these meta-skills durable is that they are ungradeable: because there is no answer key an agent could check them against, choosing what matters, judging honestly, and answering for the result resist the automation that is commoditizing solvable, checkable work.
  Addy Osmani’s Post · p7
• explicit'AI is just a tool' is true but insufficient: responsible use demands three faculties — metacognition (noticing one's own intent), empathy/other-metacognition (imagining the other person's experience), and computational metacognition (asking what the tool is smoothing, inferring, omitting, or making legible).
  TBM 428: Yes, Robot. Yes, Boss? · p7
• implicitcorroboratedBeck's other major recent frameworks (3X: Explore/Expand/Extract, the 'Genie' metaphor for LLMs, Thinkies) all originated through the same slow-incubation-then-repeated-bad-explanation process he is now describing for 'XP is long volatility'.
  The Beginnings of an Idea: XP is Long Volatility · p7

Open gaps (51)

• 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
• incompleteThe concrete prescriptions (mentor-as-coach, AI-free checkpoints, try-first-check-second, visibility of professional standards) are demonstrated only inside a structured, resourced internship program with a dedicated mentor per intern. The piece never asks whether or how they generalize to an ordinary team of mid-level or senior engineers with no formal mentor role, or to distributed/remote teams that lack the ambient 'who's the go-to' awareness the piece assumes exists in a colocated cohort.
  AI coding creates two kinds of debt. You're only measuring one — read next: Golden-path / platform-engineering literature on embedding good practice without a bespoke mentor relationship; pair/mob-programming literature on how tacit-knowledge transfer happens outside formal mentorship for non-junior engineers.
• incompleteThe whole argument rests on the meta-skills being 'ungradeable' and therefore unautomatable, but the piece asserts this durability without defending it — offering no account of why selecting, judging, and even 'answering for it' won't also be encroached on as models gain evaluative and agentic capability. 'Keep your alpha ahead of the models' concedes the edge is depreciating without saying how fast or how you would know when it is gone.
  Addy Osmani’s Post — read next: Arguments about which judgment tasks resist automation — verifiability, evals, the limits of LLM-as-judge — and the frontier of what agents can and cannot evaluate.
• uninformedThe retail case study and the distributed-ownership argument assume each skill maps cleanly to one owning domain team, but does not address what happens when two teams' skills legitimately compete for the same trigger (overlapping description keywords) in a large, many-team organization — a scaling failure mode distinct from the four it names (trigger, execution, token budget, regression), closer to a governance/arbitration problem than a technical one.
  Agent Skills — read next: Read against software-architecture literature on team-boundary design (e.g. Conway's Law, bounded contexts) applied to skill ownership rather than service ownership.
• incompleteThe paper asserts skills are portable across vendors and runtimes (Claude Code, Codex CLI, Gemini CLI, Antigravity) via the shared agentskills.io format, but — beyond noting that install paths, activation rules, and tool-whitelisting details differ per tool — does not report any direct empirical comparison of the same SKILL.md executed across multiple harnesses to verify truly identical behavior, leaving the portability claim's practical reliability untested within the paper itself.
  Agent Skills — read next: Compare the same SKILL.md's measured trigger accuracy and execution fidelity across at least two different coding-agent harnesses.
• incompleteCultural specificity is unexamined: Wedel never tests whether 'when the boss has the answer, the rest stay silent' depends on Norwegian (or Nordic, or hierarchical) defaults. In flatter or more confrontational cultures, the chilling effect may be weaker — or it may show up differently (silent disagreement vs. silent compliance).
  12) Greger Teigre Wedel: Når sjefen har svaret, tier resten — read next: Cutler TBM 423 on undiscussables (which treats power-asymmetry-creating-silence as general, not culturally specific) and Edmondson on psychological safety across cultures. Also Hofstede / Trompenaars on power distance dimensions in Nordic vs. other workplaces.
• incompleteDecision criteria for posture-switching are underspecified. Wedel says leaders should choose among coaching, deciding, hands-on, whiteboarding, director postures situationally — but he names only one explicit trigger (the over-coaching failure mode that calls for cutting through). When to take which posture is left as 'judgment'.
  12) Greger Teigre Wedel: Når sjefen har svaret, tier resten — read next: Kent Beck on tidy-first vs. mess-first decision rules; Heifetz on adaptive vs. technical work; Cutler's TBM 418 on campfires/trails/quests as posture-selection frame.
• incompleteThe interaction between explicit mode-switching ('lederhatten av') and team-level psychological safety is asserted but not unpacked. Saying 'we're in whiteboarding mode now' presumably only works if the team trusts that the leader will actually honour the signal — which is itself a function of trust built elsewhere.
  12) Greger Teigre Wedel: Når sjefen har svaret, tier resten — read next: Edmondson on psychological safety as accumulated track-record; Schein on rituals and their preconditions; Pocock's 'alignment is not AFK' point about why alignment work must be live, not formal.
• incompleteAI-as-amplifier is asserted in both directions (good practice → better; bad practice → worse) but the magnitude of asymmetry is not addressed. If AI amplifies bad practice faster than good, the policy implication ('defer AI until guardrails exist') may be stronger than Wedel states.
  12) Greger Teigre Wedel: Når sjefen har svaret, tier resten — read next: DORA 2025 detailed findings; the Dave Farley YouTube series Wedel mentions; any empirical work on AI adoption velocity vs. defect rates.
• incompleteThe six product-org first principles are alluded to but not enumerated in the conversation. Only the first (deep user/customer connection) is discussed.
  12) Greger Teigre Wedel: Når sjefen har svaret, tier resten — read next: stuff.greger.io blog series on product organisation first principles.
• 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.
• incompleteThe 'Success = Machine Understanding x Problem Understanding x Practice Evolution / Social Contract' formula uses multiplication and division as if the four factors were measurable quantities, but none are scored, operationalized, or given units anywhere in the deck — it functions as a mnemonic device, not an actual computable model.
  John Cutler's Post — read next: This is a recurring pattern in Cutler's own frameworks — the corpus already flags the same failure to operationalize a 2x2's axes in his tbm-430 piece (extract-tbm-430-incubate-compound-refinance-liquidate#g1) — worth reading together to see how consistently the gap recurs.
• 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.
• survivorship bias in the 'craft transfers' argumentBoth speakers are masters of craft who naturally see craft as the durable skill. They do not seriously consider the possibility that AI could make some craft practices genuinely obsolete rather than merely shifting them upward. Beck comes closest with his admission of grief about losing zone-flow on code, but neither explores which specific practices may not transfer.
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again — read next: Look for empirical studies or practitioner reports on which specific engineering practices AI makes less vs. more valuable.
• vague definition of 'the middle'Beck's claim about 'the middle' being most vulnerable is stated without clear criteria. How do you distinguish someone in 'the middle' from a competent professional who simply isn't a thought leader? The framing risks becoming a circular argument: those who thrive had intrinsic motivation; those who didn't were 'the middle.'
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again — read next: Look for more rigorous analysis of which programmer skill profiles are most affected by AI tooling.
• absence of data on team-structure claimsThe argument that pairs-plus-agents beats solo-plus-agents is based on XP philosophy and Beck's personal experience, not comparative evidence. Given that this is arguably the most consequential organizational design question in software right now, the evidentiary basis is thin.
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again — read next: Seek out early empirical comparisons of solo-plus-agent vs. pair-plus-agent productivity and quality outcomes.
• enterprise perspective is observation without prescriptionFowler reports 'large-scale confusion and panic' and security concerns at enterprises but offers no framework for how enterprises should approach AI adoption differently from startups. The advice is pitched at individual practitioners, not organizational leaders.
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again — read next: Look for enterprise-specific AI adoption frameworks (e.g., ThoughtWorks Technology Radar, or Fowler's own martinfowler.com posts on the topic).
• the COBOL analogy cuts both waysBeck invokes the recurring 'eliminate the programmers' dream (COBOL, etc.) as historical context, then adds 'it behooves us as programmers to think about why they keep wanting to get rid of us.' This self-critical aside is dropped immediately without exploration. The uncomfortable possibility — that some of the desire to eliminate programmers reflects genuine organizational friction caused by programmers — is raised but not examined.
  Martin Fowler & Kent Beck: Frameworks for reinventing software, again and again — read next: Consider whether the 'eliminate programmers' impulse reflects legitimate frustration with the cost and difficulty of translating business intent into code, which AI might actually address.
• unsupported_claimThe title claims 'the model doesn't matter anymore' but the email body never argues or even mentions this claim. The provocative thesis is pure clickbait with no supporting content.
  The model doesn't matter anymore – and other AI skills worth your Thursday
• missing_evidenceThe email provides no evidence that the speakers or sessions will deliver on the 'signal from real practitioners' promise. Speaker credentials are mentioned only for one session (Paige Bailey from Google DeepMind).
  The model doesn't matter anymore – and other AI skills worth your Thursday
• incompleteTaste and judgment are presented as durable human advantages 'much more difficult to imagine being automated away', but Mosseri gives no account of why they resist automation, and the opposing view — that taste is an in-group-reaction prediction loop AI can also learn to close — is never engaged.
  Adam Mosseri: AI is a tailwind for authenticity — read next: The argument (from the Schoening/Lenny conversation) that taste resembles backpropagation and may not be an enduring human advantage; theories of taste as learnable feedback vs. innate faculty.
• 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.
• incompleteThe metacognition argument depends on a tacit theory of practitioner skill — that individuals can correctly self-assess which cognition is 'central' to their job's value. No mechanism is offered for how to learn or verify this self-assessment, especially under pressure to ship
  This Week in AI: Production Viability — read next: Adler/Polanyi on tacit knowledge; Kahneman on overconfidence in self-judgment; deliberate practice literature (Ericsson); workshop reports from teams that have institutionalized AI-judgment reviews
• incompleteFDE critique identifies the missing analyst layer but doesn't engage with current AI-firm playbooks (Anthropic, Palantir, Sierra) that explicitly pair FDEs with discovery / scoping phases. The piece treats FDE as monolithic
  This Week in AI: Production Viability — read next: Gergely Orosz's FDE coverage (extract-pragmatic-engineer-pulse-fde-heats-up.json) for comparison; Anthropic Applied AI team writeups; Palantir's deployment-strategist literature
• incompleteOpenAI consumer-intent argument doesn't engage with the counter-case: that financial-data partnerships might actually be subject to materially stricter regulatory regimes (GLBA, PSD2, etc.) than ad-tech, which could constrain monetization paths
  This Week in AI: Production Viability — read next: Comparative regulation of fintech vs. ad-tech data flows; banking-API consent literature; Apple's privacy-vs-monetization positioning
• incompleteThe article doesn't address how the agent decides whether it needs a research phase. The Liquid case didn't need one; the llama.cpp case did. But the agent couldn't have known this in advance. A decision heuristic ('when should I read before coding?') is the missing meta-skill that would make this approach self-directing rather than human-configured.
  Research-Driven Agents: What Happens When Your Agent Reads Before It Codes — read next: Metacognitive agent architectures; 'knowing what you don't know' in AI systems; confidence calibration research
• incompleteNo method for developing the one skill it names as decisive. The essay says attention is the key, says it can't be taught, and then offers only the paid 'Inner Circle' as a path — leaving the practical reader without an actionable next step, which is ironic for a self-styled 80/20 practical newsletter.
  The real skill behind good AI prompts is older than computers — read next: Cal Newport 'Deep Work'; Nir Eyal 'Indistractable'; William James on attention; mindfulness / meta-attention research — the how-to layer the essay withholds
• illogicalThe thesis is close to unfalsifiable: any AI success is credited to attention, any failure blamed on inattention. It also equivocates between 'attention' as (a) present-moment noticing and (b) accumulated domain expertise ('knowing what matters about the task') — much of what he calls noticing is actually expertise/tacit knowledge, a different faculty.
  The real skill behind good AI prompts is older than computers — read next: Michael Polanyi 'The Tacit Dimension'; Gary Klein 'Sources of Power' (expert intuition as pattern recognition); Ericsson on expertise — to separate 'attention' from 'expertise'
• incompleteTitle/body mismatch. The headline promises a skill 'older than computers,' but the body only asserts the pre-digital, timeless pedigree of attention — it never substantiates the historical claim it uses as a hook.
  The real skill behind good AI prompts is older than computers — read next: Matthew Crawford 'The World Beyond Your Head' (attention as a cultural/historical achievement); Simone Weil on attention
• incompleteThe issue diagnoses AI-era pressures (salary-scale economics, direction-less amplification, agent reliability, term-inflation) and poses them as open questions to the reader ('where does your company sit?', 'what would you do differently?') but never synthesizes them into an operating model — it stops short of what a leader should actually do.
  SWLW #710: Revised rules of Eng Leadership, When AI costs more than the engineer, and more. — read next: Will Larson's 'Revised Rules of Engineering Leadership' itself (the linked favorite), and John Cutler / engineering-strategy sources that convert principles into concrete decision rules.
• incompleteThe continuity framing (fundamentals and judgment are what matter, AI only raises their stakes) under-weights the possibility that some fundamentals themselves must change under AI — it treats 'fundamentals' as fixed rather than a live question.
  SWLW #710: Revised rules of Eng Leadership, When AI costs more than the engineer, and more. — read next: Sources debating whether the fundamentals taught today are still the right ones (e.g. Tobias Torrissen on juniors and fundamentals; 'The Future of Software Engineering' on mid-level retraining).
• incompleteBucket 3 (genuinely new practices only possible with AI) is the most interesting category but receives the least development. The author acknowledges these exist but provides zero concrete examples of what they might look like.
  TBM 420: The AI Playbook Puzzle — read next: Look for writing on emergent AI-native workflows: Maggie Appleton on AI interaction patterns, or Linus Lee on AI-augmented thinking tools.
• incompleteThe COM-B analysis is applied only to individuals. The organizational and structural factors that create and reinforce the three traps (incentive structures, promotion criteria, budget cycles) are not analyzed.
  TBM 420: The AI Playbook Puzzle — read next: Westrum's organizational typology applied to AI adoption; Amy Edmondson on psychological safety as a precondition for the identity work Cutler describes.
• incompleteThe argument assumes a product/tech organizational context. How the four-bucket framework applies to non-tech domains (healthcare, education, government) is unaddressed.
  TBM 420: The AI Playbook Puzzle — read next: Sector-specific AI adoption research; Ethan Mollick's work on AI across professions.
• incompleteThe eight-step journey is presented as linear and individual. No treatment of how teams or organizations move through this collectively, or what happens when team members are at different stages.
  TBM 420: The AI Playbook Puzzle — read next: Bridges' Transition Model for organizational change; Kegan and Lahey on immunity to change.
• illogicalThe claim that 'the more certain someone sounds, the more likely they're relying on outdated models' risks being unfalsifiable. It could also apply to Cutler's own confident claims about identity threat being the biggest obstacle.
  TBM 420: The AI Playbook Puzzle — read next: Philip Tetlock on superforecasting and calibrated confidence — certainty is not inherently a signal of poor reasoning.
• incompleteThe essay is almost entirely diagnostic on the systemic register: it insists AI cannot fix incentives, legitimacy or voice safety and that these must be addressed by humans/systems, but offers no method for doing so. The 'individual + systemic' synthesis names both levels without specifying how to act on the systemic one.
  TBM 428: Yes, Robot. Yes, Boss? — read next: Cutler's own 'AI Won't Save Your Kingdom' and legibility/legitimacy pieces; systems-change literature on incentive redesign; Amy Edmondson on building psychological safety as a deliberate practice.
• incompleteThe capability/friction vs. motivational/political blocker taxonomy is presented as a clean binary, but many real blockers are mixed (e.g., 'missing scaffolding' can itself be a symptom of low legitimacy or fear). The essay doesn't address how to tell which kind of blocker you actually face — precisely the diagnosis on which its advice depends.
  TBM 428: Yes, Robot. Yes, Boss? — read next: Diagnostic frameworks that separate technical from adaptive problems (Heifetz, adaptive leadership); root-cause methods that trace surface friction to underlying incentives.
• incompleteThe accountability question is raised and dropped: if AI makes bad-faith performance management cleaner and more defensible, the essay's own 'would they be successful?' implies existing legal/organizational recourse is inadequate, but it neither examines that recourse nor proposes countermeasures (audit trails, prompt provenance, HR governance).
  TBM 428: Yes, Robot. Yes, Boss? — read next: Agent-governance and decision-provenance literature; employment-law treatments of pretextual performance management; work on organizational undiscussables.
• incompleteThe asymmetry claim — that AI amplifies dysfunction more readily than honesty — is argued qualitatively (bad-faith use is the low-effort default) but never sized. Whether the reflective-use gap is closable by design (defaults, prompts, scaffolds that nudge toward self-interrogation) is left unexplored.
  TBM 428: Yes, Robot. Yes, Boss? — read next: Choice-architecture / nudge work applied to AI defaults; 'scaffolded cognitive friction' as an antidote (cognitive-surrender literature).
• incompleteThis is a promotional newsletter, not an analytical piece. Only one Thinkie (Can't/Because) is demonstrated out of the claimed ~100. The definition of Thinkies is given but no taxonomy, no theory of why they work, and no evidence of effectiveness beyond one dialogue.
  Unstick Your Stuck Thinking — read next: Kent Beck's book or course materials on Thinkies; TWC content if available; related work on lateral thinking (de Bono), reframing (Watzlawick), or cognitive flexibility
• incompleteThe piece does not distinguish Thinkies from existing frameworks for creative/lateral thinking (de Bono's lateral thinking hats, TRIZ contradiction analysis, Socratic questioning). It is unclear what is novel vs. repackaged.
  Unstick Your Stuck Thinking — read next: Compare with de Bono's Six Thinking Hats, TRIZ inventive principles, and Socratic method literature
• incompleteThe Can't/Because example conflates correlation with causation without flagging it — 'can't X because Y' is treated as a causal claim to be solved, but no attention is given to whether Y actually causes not-X.
  Unstick Your Stuck Thinking — read next: This may be intentional (the point is to generate ideas, not validate causation), but the piece does not acknowledge the distinction
• incompleteShe prescribes 'be more human, be commercially curious, be nice to work with' as the durable AI-era edge but offers no account of which of these are developable skills versus fixed dispositions, nor how someone would train them — leaving the advice motivational rather than actionable, and vulnerable to the same 'no clear starting point' complaint she levels at the framework literature.
  Why product feels so hard right now - Charity Ibhadon (WPP) — read next: extract-ai-worker-identity-archetypes and the meta-skills / contextual-judgment literature on which durable capabilities are teachable; commercial-acumen development pathways for product roles.
• incompleteThe 'long-baked ideas' theory of how his frameworks originate is offered purely as autobiographical pattern-matching across Beck's own past examples (3X, Genie, Thinkies), with no engagement with the existing psychology-of-creativity literature on incubation.
  The Beginnings of an Idea: XP is Long Volatility — read next: Graham Wallas's four-stage model of creativity (preparation, incubation, illumination, verification, from The Art of Thought, 1926); empirical work on incubation effects in problem-solving (e.g. Sio & Ormerod's meta-analysis on incubation and insight).
• uninformedBeck doesn't say who originated the 'XP is long volatility' framing he 'heard... yesterday' — whether it's his own restated insight, a collaborator's phrase, or something from the broader trading/software crossover community. Without attribution, readers can't independently trace or evaluate the idea's source before Beck's own treatment arrives.
  The Beginnings of an Idea: XP is Long Volatility — read next: No source available yet; would require Beck's future post or direct correspondence to resolve.