
Playbook
Tasteful Skills
“Tasteful Skills” argues that the best agent skills are not documentation or best-practice lists.
Brian Armstrong tied Coinbase’s 700 layoffs to both crypto and AI — the memo says a 14% workforce cut reflects a crypto downturn and a deeper shift where engineers now ship in days and non-technical teams can push production code with AI.
The hosts reject the 'AI washing or bad business' binary — their core point is that both can be true at once: Coinbase may have overhired or be in a weak market, and AI can still be genuinely changing how companies should operate.
Armstrong’s org chart vision is aggressively AI-native — he wants no more than five layers below the CEO/COO, leaders with 15+ direct reports, 'player-coach' managers, and teams built around people who can run fleets of agents.
Pure management is the job category under direct attack — Paul Roetzer says the direction feels right because companies should want fewer layers, faster decisions, and managers who still build rather than just supervise.
This memo matters beyond Coinbase because it gives other leaders cover — Roetzer argues PE- and VC-backed companies likely passed this around immediately, and many will use AI-driven efficiency claims to justify 10–20% cuts in legacy orgs.
The real question isn’t whether this round of layoffs is fully about AI — it’s whether AI changes how organizations must function, and the hosts say if your answer is yes, then this memo is an early signal of where structures, hiring, and team design are headed.
The episode opens on Coinbase CEO Brian Armstrong’s email announcing a roughly 14% cut — about 700 jobs — while arguing two things are happening at once: crypto is in a downturn, and AI is changing the company’s operating model. The memorable line is that Coinbase is rebuilding as an “intelligence with humans around the edge aligning it,” which gives the whole discussion a much more structural feel than a standard cost-cutting memo.
Armstrong’s case is concrete, not abstract: engineers are using AI to “ship in days” what used to take teams weeks, and even non-technical employees are now shipping production code. He pairs that with a hard-edged organizational vision — flatter structures, more direct reports, fewer layers, and experiments with one-person teams blending engineering, design, and product.
Mike tees up the comment-section argument everyone knows by now: is this really AI, or just cover for overhiring and a bad market? Paul’s answer is basically, stop forcing it into extremes — Coinbase can have macro problems and still be directionally right about AI changing work. He even says, fine, “let’s assume you’re right” that some of it is AI washing, then walks through why the memo’s underlying claims still hold.
Paul goes point by point and says the strategic logic stands on its own: companies should be leaner, faster, and more AI-native; orgs should be flatter; and “pure managers are out.” He’s especially animated about the “player-coach” idea, arguing there’s no reason to pay managers who aren’t also builders, orchestrators, or domain experts doing real work.
The section that most excites them is Armstrong’s focus on “AI native talent” — people who can manage fleets of agents and operate in very small pods, even solo. The hosts frame this as the real signal inside the memo: not just layoffs, but a hiring and organizational model centered on builders who can architect, execute, and coordinate AI systems themselves.
Paul says this wasn’t just a Coinbase internal note — in his view, it was probably dropped into Slack channels across VC-funded companies immediately. His prediction is blunt: even if AI wasn’t the full cause here, memos like this provide cover for many firms to make 10–20% cuts on the assumption that AI can absorb that much legacy inefficiency.
By the end, Mike says the AI-washing debate “misses the forest for the trees.” The more important yes-or-no question is whether AI changes how organizations have to operate; if you think it does, then leaders should be pulling ideas from memos like this, even if they reject half of them. Their closing note is almost generous: nobody has the full answer, but it matters when someone is willing to put a model out in public so others can test what fits their company.
Share
Keep Reading
The Weekly Echo. The inbox-shaped summary of what mattered.
New editorials announced here.

Playbook
“Tasteful Skills” argues that the best agent skills are not documentation or best-practice lists.

Playbook
Learn how tasteful prompting helps you move beyond generic AI output by shaping context, style, and judgment from the start.

Playbook
OpenAI shipped /goal for the Codex CLI. It turns a prompt into a persisted, self-continuing contract.