Tool Stack Design: Building Your Personal Work System
Tool stack principles: one tool per function avoiding overlap, tools should integrate with data flowing between, start minimal adding when needed.
What was corrected
Article included an anecdote about Sahil Lavingia's personal tool stack and an Okta statistic about medium-sized enterprises and app-switching frequency that could not be verified, cited a researcher, 'Dr. Stefan Mayer (HEC Paris),' who could not be verified to exist in any faculty directory, referenced a Notion study of 50,000 teams that could not be verified, and included specific internal statistics for Basecamp, Automattic, Superhuman, USDS, and Stripe that could not be verified (including an Automattic revenue-per-employee figure inconsistent with public data, and a reference to Basecamp's HEY email service in a 2018 context, though HEY did not launch until 2020).
Removed the Lavingia anecdote and Okta misattribution, replacing them with an accurately hedged description of Lavingia's real minimalist-tooling approach and correctly attributed Okta enterprise figures. Removed the Stefan Mayer study reference and the Notion study entirely. Rewrote the Basecamp, Automattic, Superhuman, USDS, and Stripe sections to describe their real, documented approaches and public statements without the unverifiable statistics, and removed the chronologically inconsistent reference to HEY in a 2018 context.
Why this is better
Verified via web search against primary sources: Okta's published Businesses at Work reports, Sahil Lavingia's public commentary (Lenny's Newsletter), HEC Paris and Cambridge faculty directories (no record of a Stefan Mayer), Automattic's public revenue and headcount figures, and the absence of any corroborating source for the studies cited at Notion, Basecamp, Superhuman, USDS, or Stripe.
More by Emir Baycan in Productivity Tools
- Correction Workflow Apps for Knowledge Workers
- Correction Top Tools for Knowledge Work and Their Uses