Elon Musk's management playbook is built on a few core principles: only engineers truly matter, the CEO must violate the chain of command to talk directly to line engineers, and the CEO's job is to parachute in weekly to fix the single biggest bottleneck by working alongside them.

The act of writing forces clarity. Jeff Bezos mandates written narratives over slideshows at Amazon because the process exposes fuzzy thinking. While a clear thinker isn't always a great writer, a clear writer is invariably a clear thinker. This makes writing a critical leadership skill, not just a marketing tactic.

At Tesla, critical priorities weren't chosen from a list of options; they were dictated by existential threats. The focus became whatever problem would cause bankruptcy if left unsolved. This creates an intense, survival-driven roadmap that forces clarity and action.

Musk doesn't broadly delegate. He abdicates most operations but intensely focuses on the single greatest bottleneck across his entire enterprise, 'nano-managing' it until it's resolved before moving to the next one, like the Eye of Sauron.

Investor Thomas Laffont, inspired by Steven Spielberg, mandates that every great investment story be pitched in three sentences. This constraint forces a deep, first-principles understanding of a business's core drivers. It ensures the financial model is a simple reflection of the core thesis, not an overly complex spreadsheet.

Speed is a mindset that compounds efficiency. Responding to an email in one minute requires just two words. A day's delay demands a paragraph, and a week necessitates a full page. Acting with speed drastically reduces the cumulative effort required for communication and tasks.

To ensure clarity and impact, mandate that any explanation of the platform team's work to non-technical stakeholders must be understandable in under three minutes. This forces the team to distill their message to its core value, cutting through technical jargon.

Bupa's Head of Product Teresa Wang requires her team to explain their work and its value to non-technical people within three minutes. This forces clarity, brevity, and a focus on the 'why' and 'so what' rather than the technical 'how,' ensuring stakeholders immediately grasp the concept and its importance.

Arvind Jain insists on receiving written thoughts before discussions. It's partly for his own processing style (he absorbs information better by reading). More importantly, he believes the act of writing is the most effective way for anyone to structure their thoughts coherently and make better strategic decisions.