Why Small Teams Still Win
Small teams still have an edge, but only if they stop copying the coordination habits of larger companies.
Read the introductionFor founders, managers, and operators in teams of 2 to 20
Scale your impact, not your headcount.
Practical systems and AI workflows for small teams (2–20 people) who want to stay lean, profitable, and focused without building a noisier company.
If you are new here, start with these three foundational essays. After that, move into the latest practical guides for small teams.
Written from a data scientist's perspective, grounded in patterns found across millions of accounting and employee records and in hands-on operating experience.
Read First
If you are new here, begin with these.
These articles explain the core point of view before you dig into narrower operating systems and templates.
Why Small Teams Should Optimize for Calm, Not Speed
Calm is not the opposite of ambition. For a small team, it is usually the condition that makes real progress possible.
Meetings Are Overhead, Not Progress
Meetings can be useful, but small teams lose far too much time when they confuse conversation with movement.
Latest
The newest practical essays.
After the introductions, this is the best place to keep reading.
Respond, Don't React: Setting Internal SLAs for a Calm Team
Internal SLAs provide the certainty teams need to stop obsessive Slack checking and move back to deep, meaningful work.
Dashboards Over Documents: How to Visualize Progress in a Small Team
Stop forcing your team to read long status reports. Using visual dashboards creates a passive pulse that keeps everyone aligned without a single meeting.
How to Build a High-Performance Async Culture in a Small Team
Pseudo-async is worse than meetings. To win as a small team, you need a cultural shift in how you value time and focus.
The Complexity Tax: Why Scaling Your Team Can Kill Your Profit
Most founders think hiring more people is the only way to grow. But for small teams, headcount growth often increases complexity faster than output, eating into margins.
The Minimalist First Week
In a small team, the first week isn't about knowing where all the documents are. It's about knowing what's urgent and how fast to reply.
If Your Team Isn't Reading Your Docs, Fix the First View
Before blaming your small team for ignoring the playbook, make sure the document does not look like a wall of text.
How to Start Projects With a Written Kickoff Instead of a Meeting
Stop wasting your team's most productive hours on kickoff meetings. Use a written kickoff document instead.
How to Write a One-Page Kickoff Doc for a Small Team
A short kickoff doc is often enough to align a small team before work starts, but only if it is concrete enough to guide execution.
Browse by Topic
Five focused tracks. No generic catch-all bucket.
Pick a topic if you already know what kind of operating problem you want to solve.
10 articles
Calm Operations
How to run a small team without constant urgency, interruptions, or communication sprawl.
Latest article
How to Build a High-Performance Async Culture in a Small Team
7 articles
Small-Team Execution
Practical systems for deciding, planning, and finishing meaningful work with a small team.
Latest article
Dashboards Over Documents: How to Visualize Progress in a Small Team
10 articles
Async Communication
Practical async communication for small teams: replace status meetings and chat churn with written updates, decision docs, and clear documentation.
Latest article
Respond, Don't React: Setting Internal SLAs for a Calm Team
3 articles
Profitable Simplicity
Advice for protecting margin, reducing tool sprawl, and keeping a company simple on purpose.
Latest article
The Complexity Tax: Why Scaling Your Team Can Kill Your Profit
3 articles
AI Without Chaos
How to use AI to reduce friction without flooding a small team with more noise and review work.
Latest article
AI Should Remove Work, Not Create More of It