Twitter/X

Ask any teammate why the team chose its current pricing model and you’ll likely…

2026-05-11 · 15:57 UTC ·@aakashgupta ·2 min read

Brief

Aakash Gupta argues teams stop losing critical decisions by building a shared 'Team OS' — a repo where every function checks in PRDs, customer-call summaries, decision logs, and analytics queries. He reports studying four implementations (Hannah Stulberg at DoorDash, Dave Killeen at Pendo, Gabor Meyer at Google, and Carl Vellotti) and describes a three‑phase rollout: Phase 1 (one week) moves foundational docs into the repo and designs for context engineering; Phase 2 brings analysts, engineers, and nontechnical contributors into regular PR workflows; Phase 3 lets the system compound so it answers questions nobody individually remembers. Gupta cites concrete metrics — three months to make a decision unrecoverable, new hires take 6–7 months to settle, 47% of companies flag institutional knowledge loss as their top offboarding issue, and routine context questions can cost 8+ hours/week — and gives an example where a new engineer retrieved a three‑month‑old decision in 15 seconds. A downloadable guide (six assets) and a one‑command skill promise to convert personal PM OSes into team OSes without leaking personal context.

Why it matters

Ask any teammate why the team chose its current pricing model and you’ll likely hear “I wasn't here for that” or “let me dig up the deck”; Aakash Gupta says three months is enough for a real decision to become unrecoverable.

Key details

  • Gupta studied implementations at DoorDash, Pendo, and Google (Hannah Stulberg, Dave Killeen, Gabor Meyer) plus a solo build by Carl Vellotti; all converged on a shared-repo 'Team OS' that stores PRDs, customer call summaries, decision logs, and analytics queries.
  • The Team OS rolls out in three phases: Phase 1 (foundation) — PMs move PRDs and customer calls into the repo and onboard core team (one week); Phase 2 — analysts check in queries, engineers add investigation templates, non‑technical contributors open PRs; Phase 3 — the repo compounds and answers questions no single teammate remembers.
  • Quantified impacts and examples: new hires typically take 6–7 months to settle; 47% of companies name institutional knowledge loss their top offboarding problem; 10 context questions/day at ~10 minutes each costs ~8+ hours/week; one new engineer retrieved a three‑month‑old decision rationale from the repo in 15 seconds, freeing the PM from being a bottleneck.
Source evidence

Try this on your team Monday. Ask any teammate why your team chose its current pricing model. The answer will either be "I wasn't here for that" or "let me dig up the deck." Both mean the decision is functionally lost.

The PM who ran the call is on parental leave. The customer interviews that anchored the architecture pivot are in someone's personal notes. The churn query is on the laptop of an engineer who rotated teams in March.

Three months. That's all it takes for a real decision to become unrecoverable.

The teams I studied at DoorDash, Pendo, and Google all built the same fix: a shared repo where every team function checks in PRDs, customer calls, decision logs, and analytics queries. Hannah Stulberg calls it a Team OS.

It comes online over three phases.

Phase 1, the foundation. PM moves PRDs and customer calls into the repo. Architecture designed for context engineering. Core team in from day one. One week.

Phase 2, the team builds together. Analyst checks in query skills. Engineers contribute investigation templates. Non-technical contributors open their first PRs.

Phase 3, the system compounds. The repo starts answering questions nobody on the team individually remembers anymore. New hires onboard from the repo instead of from a three-week Slack archaeology dig.

47% of companies call institutional knowledge loss their top offboarding problem. Phase 3 is where that statistic stops applying to your team.

Aakash Gupta (@aakashgupta)

Hannah Stulberg, a PM at DoorDash, built a shared repo where her team checks in every customer call summary, decision log, and analytics query.

Last week a new engineer needed context on a customer decision from three months ago.

Instead of pinging Hannah and waiting, the engineer opened the repo, asked in natural language, and got the full reasoning in 15 seconds.

Hannah wasn't involved. She wasn't even online.

Every PM book tells you to make yourself indispensable. Hannah did the opposite. She freed herself from being the bottleneck and the team treated her as more valuable.

OpenAI made the same point in their February harness engineering post. That Slack discussion where your team aligned on an architectural pattern? If it isn't discoverable to the agent, it's illegible the same way it would be to a new hire joining three months later.

The numbers back it up. New hires take 6 to 7 months to feel settled. 47% of companies call institutional knowledge loss their top offboarding challenge. 10 context questions a day at 10 minutes each is 8+ hours of productive time gone every week.

I spent the last week studying four implementations: Hannah at DoorDash, Dave Killeen at Pendo, Gabor Meyer at Google, and Carl Vellotti building solo.

Four people, four companies, four different levels of complexity. They all converged on the same three-layer architecture.

Full guide is up with 6 downloadables, including a one-command skill that converts your personal PM OS into a team OS without leaking your personal context.

A personal OS compounds for you. A team OS compounds for everyone.

news.aakashg.com/p/team-os-c…

— https://nitter.net/aakashgupta/status/2052966308225142901#m