Field guide / primary domain

Leadership

25

sources in this field

Updated July 16, 2026

Current thesis

The shortest path to orientation.

Leadership in the AI era spans people management, AI-augmented executive workflows, investor communication, and emerging AI governance. Keith Rabois's talent framework (expand scope until breaks, test small problems first, monitor desk traffic) applies equally to human and AI team management. CPO role predicted to vanish within five years as AI-native companies replace PM/design/engineering with "product builder" archetype spanning all three. CEOs use Claude Code as AI Chief of Staff doubling productivity: unifying inboxes, managing overnight todos, enriching contacts from transcripts, receiving strategic pushback. AI dissolves time barriers degrading leadership discipline—Friday reviews compress from hours to 12 minutes, 1:1 prep from hours to 5 minutes, removing procrastination excuses skipping high-leverage reflection. Hannah Stulberg (DoorDash) built shared repo where teams check call summaries, decision logs, analytics queries enabling 15-second natural-language queries returning full reasoning without pulling humans off work. Four independent implementations (DoorDash, Pendo, Google, solo) converged on same three-layer team-knowledge architecture—pattern is structurally robust, not idiosyncratic. One-command skill converts personal PM OS into team OS without leaking context, turning individual gains into team-wide compounding. Rippling PMs fix own copy errors rather than relying separate teams—ownership reduces coordination overhead. AI-native companies replacing standalone PM role with full-stack product builder (product+design+engineering IC) because standalone CPO creates coordination tax when ICs already blending. Career implication: PMs should develop fluency across product, design, engineering, analytics to become full-stack product builders; standalone specialization becomes overhead. AI-native company structures propagate to non-AI companies within 5 years. Agent governance should follow constitutional design: AI systems with distinct invested values (transparency, equity, due process) checking/balancing other AI systems; single concentration of intelligence should not self-regulate. SEC example illustrates gap: business school graduates with Excel combating AI-augmented trading is structurally inadequate—governments need AI-powered oversight matching AI-powered actors. Dorsey's four-layer AI-native org: Capabilities (hardware/models), World Model (unified vector DB company memory), Intelligence Layer (agent fleet deciding), Surfaces (human interaction)—any company can map this. DRI system applied to agents: temporary teams around specific 90-day goals, agents return to pool after, learnings absorbed into organizational brain. Agency/consulting new model: internal AI implementation becomes product—months compounded data and operational learnings become differentiation. Five moats surviving AI: compounding proprietary data (living, not static), network effects, regulatory permission, capital at scale ($20B chip fabs, $10B nuclear plants), physical infrastructure—all bottlenecked by time unparallelizable. Capital at scale underweighted moat—when bottleneck shifts software to atoms, financing/deployment at massive scale plus institutional trust becomes defining. Open question: does trust become moat when AI does more work? Institution bearing liability when things fail might become MORE valuable. Marek Siliski's clipboard trick (printed team photos with note space per person) lets exec ramp faster than any new peer seen, converting relationship-building into deliberate practice with checkpoints. Premortem prompt (Kahneman's most-valued decision technique, Google, Goldman Sachs, P&G; turned Claude pattern: "it's 6 months from now and this is dead") flips training-induced optimism because premise says already failed. Proper premortem returns: most likely failure, most dangerous failure, single biggest hidden assumption (often most valuable), revised plan closing gaps—counters confirmation bias on high-stakes decisions.

Evidence board

Claims worth carrying forward
01

A 5-minute AI prep routine before 1:1s—running 5 structured prompts—replaces ad-hoc agenda glancing and produces noticeably sharper conversations. The pattern: prepare prompts in advance, run them consistently before every session, not just high-stakes ones.

02

The post references 5 specific prompts run before every 1:1 but does not disclose them in this excerpt—the substantive content (the actual prompts) is missing. The value claim (5 min, consistent improvement) is present; the reusable artifact is not.

03

A shared repo where team members check in call summaries, decision logs, and analytics queries—queryable via Claude Code in natural language—let a DoorDash engineer retrieve 3-month-old decision reasoning in 15 seconds without pinging the responsible PM.

04

OpenAI's harness engineering post (Feb 2026) frames the legibility problem precisely: a Slack discussion that aligned the team on an architecture is illegible to an AI agent exactly as it would be to a new hire three months later—if it isn't discoverable, it doesn't exist.

05

10 context questions/day × 10 minutes of total productive time lost each = 8+ hours of lost productivity per week per knowledge worker. Most teams interviewed reported higher rates, making context retrieval a primary leverage point.

06

New hires take 6–7 months to feel settled; only 12% of employees say their company does onboarding well; 47% of companies cite institutional knowledge loss as their top offboarding challenge—three compounding data points for why a searchable team OS has outsized ROI.

07

Four independent implementations (Hannah Stulberg/DoorDash, Dave Killeen/Pendo, Gabor Meyer/Google, Carl Vellotti/solo) all converged on the same 3-layer architecture for a Team OS—convergent independent discovery is strong signal the pattern is robust.

08

The Team OS architecture is tool-agnostic: because it's just Markdown files, it can be ported to Codex, Cursor, or GitHub Copilot. Claude Code is the current implementation because it's most popular with AI-native PMs, not because of hard coupling.

Adjacent fields

Key voices

Latest evidence

Recent additions

All synthesized insights →

Aakash Gupta

Team OS in Claude Code: Shared Repo Architecture for Institutional Knowledge

Hannah Stulberg (DoorDash PM) built a shared git repo where every team function checks in context—call summaries, decision logs, analytics queries—queryable in natural language via Claude Code. Four independent implementations (DoorDash, Pendo, Google, solo) converged on the same 3-layer architecture, suggesting a generalizable pattern for solving institutional knowledge loss.

Vijay Iyengar

When 1:1s Are Worth It: An Opt-In Management Framework

Vijay Iyengar argues the default weekly 1:1 is structurally flawed because its fixed cadence decouples meetings from actual need. He proposes replacing most 1:1s with public-channel work, real-time escalation, written decision communication, ambient connection, and work-oriented feedback—while preserving 1:1s for onboarding (daily for 2-3 weeks), early-career reports, remote teams, on-demand requests, and peer-manager alignment.

Josh Wolfe

Lux Capital Q1 2026 LP Letter (PDF)

The post links to the Lux Capital Q1 2026 LP letter as a downloadable PDF. The actual document content is not accessible — only the Google Drive file metadata is available.

Leadership Needs context

Josh Wolfe

Lux Capital Q1 2026 LP Letter PDF Release

> 10/ Full 🔗link to downloadable PDF 📄of Lux LP letter here 👇 > https://t.co/FY6uzYWzEv - Josh Wolfe shared Lux Capital's Q1 2026 LP letter as a downloadable PDF via Google Drive link — relates to [[leadership]]