Wednesday, May 20, 2026
MSFT · AAPL
Productivity · Opinion · Field Notes

The new productivity stack: how operators ship 10× faster.

I've spent six months watching the operators who actually ship. None of them are using what your CTO thinks they're using. The stack that wins, broken down.

A desk workspace arranged around a paper calendar and work tools.

Photo · Pexels · The highest-output operators design the week before they touch the work.

The TL;DR
  • Operators who ship fast are not using more tools — they are using fewer tools, more deliberately. Median stack: four primary surfaces.
  • The four: Linear (what), Cursor (how), Claude (think), Granola (memory). Everything else is noise.
  • The biggest predictor of velocity is not the stack — it's whether the operator protects four hours of unbroken time per day.
  • Most "productivity" software actually fragments attention. The 10× operator's first move is usually deleting half their tools.

The observation.

I spent six months observing twelve operators — three founders, four engineering leads, two product managers, three independents — who, by every available metric, ship faster than anyone around them. I expected to find an elaborate stack. I found the opposite.

The median number of primary work surfaces these operators used was four. The mean number of work surfaces their less-productive colleagues used was eleven. The 10× operator is not adding tools. They are stripping them away.

The stack.

Across all twelve, the same four surfaces showed up:

  • Linear for what to do. One source of truth on tasks. Everything not in Linear gets ignored — including Slack pings, emails, and meeting action items, all of which must be triaged into Linear or they evaporate.
  • Cursor for how to do it. The IDE is the surface where most actual work happens. Multi-file context, Claude routing, agent mode for the boring parts.
  • Claude for thinking out loud. Not for "AI" — for the reflection that used to happen on legal pads. Operators run an open Claude window the way a writer runs an open notebook.
  • Granola for memory. Meeting transcripts auto-summarized, decisions extracted, automatically routed into Linear as tasks. The "what was decided" problem disappears.

Notably absent: Notion (the operators use it but it is not a primary surface), Slack (they read it once daily, in a 20-minute block), email (twice daily, same pattern), Figma (only the designers), Zoom (replaced by async voice notes in Granola for any meeting under 30 minutes).

The discipline.

The bigger predictor of velocity was not the stack — it was a single shared behavior. Eleven of twelve operators protected at least four hours of unbroken time per day, usually in the morning. No meetings, no Slack, no email. Linear and Cursor only.

The tools are an enabler. The discipline is the cause. Operators who have the discipline ship fast with almost any stack. Operators who lack it cannot be saved by software.

I deleted Slack from my phone in January. My output doubled in February. — Engineering lead, Series C startup

If I had to pick one move for a reader who wants to be a 10× operator: turn off every notification on your phone today. Then delete the Slack app entirely. Most velocity is reclaimed attention.

Frequently asked.

Based on six months of observation across twelve high-output operators, the median stack is four surfaces: Linear (task management), Cursor (IDE and execution), Claude (reflection and analysis), and Granola (meeting memory). Everything else is secondary, including Slack and email — which are checked once or twice daily, not continuously.
No. The stack is a pattern, not a prescription. The bigger driver of velocity is discipline — specifically, protecting four hours of unbroken work time per day. Operators with that discipline ship fast with almost any tools. Operators without it cannot be saved by better software.
Turn off every notification on your phone, then delete the Slack mobile app. Most lost velocity is fragmented attention. Reclaim the attention first; tool choices come second.

Camille Beaumont

Editor-at-large · Productivity & Luxury

Camille covers productivity, attention, and luxury at the operator level. Former editor at Monocle. Based in Paris.

164 articlesCited in HBR, FT Magazine