Will Larson

The Story

The Slack channels were a constant torrent, a digital equivalent of a leaky faucet that never stopped. Every ping was an emergency, every direct message a plea for intervention. Will Larson, then a seasoned engineering leader, sat at his desk, watching the real-time chaos unfold across multiple teams. It was late, but the clock seemed irrelevant in the face of the perpetual crisis mode. A critical migration was stalled, two teams were at loggerheads over API ownership, and a recent hire had just announced their departure, citing a "lack of clarity" and "constant firefighting."

This wasn’t a unique day. It was every day, or at least, a recurring pattern that had become frustratingly familiar. He’d seen it across different companies, different scales, but the symptoms were always the same: brilliant engineers burning out, projects slipping, and a pervasive sense of overwhelm. People were working harder than ever, yet the output felt like a fraction of their potential. The collective energy was spent reacting, not building.

Will had started his career as a hands-on engineer, revelling in the logic and structure of code. Debugging a complex system, finding the elegant solution, that was his natural element. But as he ascended into leadership roles, the systems he was debugging became human. The logic was messier, the solutions less obvious, and the "bugs" often manifested as emotional friction or organizational gridlock. He found himself spending less time writing code and more time in "triage mode," a human router directing traffic and mediating disputes. This wasn't sustainable, for him or for the organization.

He remembered a particularly intense period during a critical product launch. The timeline was aggressive, the technical challenges immense, and the team was stretched thin. He watched his engineers, usually vibrant and engaged, grow increasingly withdrawn, their screens glowing late into the night. One morning, he walked in to find a whiteboard filled not with architecture diagrams, but with a desperate, half-erased list of "who owns what?" and "what's next?" The clarity that should have been inherent in the project plan had evaporated under pressure. People were working hard, but they lacked a shared, accessible system for understanding the larger picture, for coordinating efforts, and for capturing the decisions made in hurried hallway conversations. Every new challenge felt like starting from scratch, every decision a potential landmine because its context was buried in individual memories.

That experience, and many others like it, planted a seed. Will began to see the chaos not as a failure of individuals, but as a failure of systems. Just as well-architected software could handle complexity, so too could well-structured organizational processes. The problem wasn't a lack of discipline in effort, but a lack of discipline in designing the environment for effort. He began to observe, meticulously. He noted which meetings were productive and why. He tracked how decisions were made – or failed to be made. He cataloged common points of friction: unclear roles, opaque career paths, inconsistent feedback, the "bus factor" of critical knowledge residing in a single person's head.

He started small, introducing habits that felt almost trivial at first. A shared document for meeting notes, rigorously updated and easily searchable. A weekly "wins and learnings" email to create a sense of shared progress and reflection. Standardized templates for project proposals that forced teams to articulate goals, risks, and dependencies upfront. These weren’t revolutionary ideas, but their consistent application was. He had to be disciplined in enforcing these habits, sometimes gently, sometimes firmly, against the natural human tendency towards ad-hoc solutions and "quick fixes." He often felt like a broken record, repeating the same principles, reminding people to consult the documentation, to update the status, to think a step ahead. It was exhausting, thankless work at times, battling the inertia of existing habits and the allure of perceived shortcuts.

One of the biggest struggles was convincing people that these "overhead" activities were not distractions from "real work" but foundational to it. He learned to frame them not as rules, but as tools. "This isn't about bureaucracy," he'd explain, "it's about building a shared map so we don't get lost, and so new people can quickly find their way." He pushed for blameless post-mortems after incidents, not to assign fault, but to identify systemic weaknesses and learn. This required a huge amount of psychological safety, a discipline in itself to cultivate.

His personal life began to mirror this philosophy. He realized that the same principles applied to his own growth and productivity. The constant stream of information, the endless to-do list, the feeling of being pulled in a million directions – these were personal symptoms of the same systemic issues he saw at work. He started applying the discipline of structured thinking to himself. He meticulously tracked his own goals, breaking them down into small, actionable habits. He reserved specific blocks of time for "deep work," shutting out distractions, just as he advocated for focused project time for his teams. He built systems for learning, for capturing ideas, for reflecting on his progress. He started writing a personal blog, 'Lethain', not initially with the intention of it becoming a resource for others, but as a disciplined practice to synthesize his thoughts, to document his observations, and to make sense of the complex world of engineering leadership.

The act of writing, in particular, became a profound act of discipline. It forced him to clarify his thinking, to articulate abstract concepts into concrete advice. There were days he felt he had nothing new to say, days when the words wouldn’t come, days when he was exhausted from his day job. But he committed to it, treating it like a habit. Even short posts, even rough drafts, added up. He wrote about everything from career ladders to incident response, from managing technical debt to fostering psychological safety. Each post was a small brick in a larger edifice of understanding.

The impact of these consistent, systematic efforts started to show. Teams under his purview became more autonomous. Incidents became less frequent, and when they did occur, the recovery was faster because the documentation and communication processes were in place. Engineers started to understand their career paths more clearly, reducing anxiety and increasing retention. The "leaky faucet" of Slack didn’t stop entirely, but the urgent, chaotic pings lessened, replaced by more structured conversations and clear information flows.

Will Larson’s journey became a testament to the power of quiet, persistent discipline. It wasn't about heroic sprints or grand, sweeping changes, but about the relentless, iterative refinement of systems – both organizational and personal. He demonstrated that true leadership isn't just about making big decisions, but about creating the conditions, the habits, and the structures where consistent excellence can thrive. He showed that the most impactful transformations often begin with the painstaking, disciplined work of bringing order to chaos, one documented process, one clear expectation, one consistent habit at a time. The result was not just better software, but better-functioning teams and, ultimately, a clearer path for individual growth.

What to take from it

• Systemize for Scale, Personally and Professionally: Larson understood that relying on individual heroics leads to burnout and fragility. By consistently investing in clear processes, documentation, and shared understanding, he built robust systems that allowed teams and individuals to grow and perform consistently, even under pressure. This approach minimizes chaos and maximizes efficiency.
• Documentation as a Discipline, Not a Chore: Many see documentation as an afterthought, but Larson championed it as a fundamental discipline. Regular, clear, and accessible documentation acts as a collective memory, a training tool, and a foundational element for informed decision-making, significantly reducing friction and accelerating learning.
• The Power of Gradual, Consistent Improvement: Major transformations rarely happen overnight. Larson's success stemmed from the disciplined, incremental refinement of processes and habits. Small, consistent tweaks to how teams communicate, plan, and learn accumulate into profound positive changes over time, proving that steady effort beats sporadic intensity.
• Clarity Reduces Chaos and Builds Trust: Ambiguity is a breeding ground for stress and inefficiency. By consistently working to define roles, expectations, and feedback mechanisms, Larson fostered environments where people understood their contributions and felt psychologically safe. This clarity is a direct output of disciplined communication habits and builds a strong foundation of trust.
• Apply Systems Thinking to Personal Growth: The same principles that govern effective organizations apply to individual development. Larson's disciplined approach to writing, learning, and managing his own energy demonstrates that building personal systems and habits is crucial for sustained growth, clarity, and impact in any field.

Today's Growth Point

Identify one recurring personal or professional task that feels chaotic or wastes time. Commit to spending 10 minutes today outlining a simple, repeatable process or checklist for it.

The one thing to remember

True mastery isn't about heroic effort, but the consistent, quiet discipline of building and refining your systems.

Try this today

Spend 10 minutes documenting the steps for a recurring task you often do from memory (e.g., preparing for a weekly meeting, submitting an expense report, or even your morning routine). Write it down clearly. This isn't just for others; it's to clarify your own process and identify potential improvements.

Sit with this

What unstructured area in your life or work causes you the most repeated friction, and what simple system or habit could you introduce to bring order to it?

Send this to someone

Your friend who's always talking about how overwhelmed they are, or who's trying to get a project off the ground. Hey, came across this piece on Will Larson and it really resonated with me – especially the idea that mastery is about building small, consistent systems, not just heroic effort. Thought you might like it!

Sources

1. https://lethain.com/: Will Larson's personal blog, which serves as a rich archive of his insights and frameworks on engineering management, organizational design, and personal effectiveness, often detailing the disciplined approach he advocates.
2. https://fs.blog/knowledge-project/will-larson-staff-engineer/: A comprehensive interview with Will Larson on 'The Knowledge Project' podcast, where he discusses his philosophy on systems thinking, career growth in engineering, and the importance of structured approaches.
3. https://queue.acm.org/detail.cfm?id=3477114: An article in ACM Queue, a reputable computing magazine, discussing the themes and impact of Larson's book "Staff Engineer," highlighting his systematic approach to defining complex roles and fostering growth within technical organizations.

This is a dramatized editorial narrative created for personal inspiration, drawn from publicly available sources listed above. It is not a biography, does not claim to represent the subject's exact views or experiences, and is not affiliated with or endorsed by the person or their estate. For a fuller picture, we recommend exploring the sources linked above.

Rate 1-5 when you like.