We scan new podcasts and send you the top 5 insights daily.
To scale beyond being a bottleneck, leaders must let their team make small mistakes. Allowing for minor, recoverable errors ("fender benders") builds decision-making skills and autonomy, which prevents the catastrophic failures ("train wrecks") that occur when a team is overly dependent on its leader.
The instinct for a hands-on leader is to fix every problem themselves, which doesn't scale. Growing requires developing the intuition to distinguish between critical issues (glass balls) and less important ones (rubber balls) that can temporarily fail, freeing up time for higher-leverage tasks.
Effective long-term leadership isn't static; it's an 'accordion' that flexes between deep involvement and granting autonomy. This adaptive approach is key for different company seasons, knowing when to lean into details and when to empower the team to make 'foot fault' mistakes and learn.
A great tech lead provides a safety net without micromanaging. The analogy is a driving instructor who starts with their hands near a second steering wheel, ready to intervene, but gradually backs off as trust builds with the student. This approach gives engineers freedom to grow while ensuring the project stays on track.
To accelerate growth for talented individuals, give them responsibility where their failure rate is between one-third and two-thirds. Most corporate roles are over-scaffolded with a near-zero chance of failure, which stifles learning. High potential for failure is a feature, not a bug.
Giving teams total freedom can be terrifying and counterproductive. Leaders must provide enough structure ('guardrails') to prevent chaos, but not so much that it kills creativity. This balance is the key to fostering productive autonomy.
To foster a culture of risk-taking and speed, leaders must accept that their role is not to prevent all errors. Instead, they should focus on creating an environment where mistakes are surfaced quickly and corrected without punishment, which is a key artifact of empowerment.
To foster growth and create a self-sufficient organization, leaders should grant designers extreme ownership rather than directing their work. This forces them to make hard decisions, which is the fastest way to become a better designer.
When your team disagrees with your direction, don't force your way. Let them execute their plan. If they fail, you build immense credibility and buy-in for future decisions without being a micromanager. If they succeed, the company wins. It's a double-win scenario.
When transitioning leadership, you must allow your successors to make mistakes. True learning comes from fixing failures, not just replicating successes. As the founder, your instinct is to prevent errors, but you must permit 'fuck ups' for the next generation to truly develop their own capabilities and own the business.
A leader's role is to teach their team, not just provide answers. Even if you can build a solution faster (like an AI agent), doing it for your team deprives them of a critical learning opportunity. The best approach is demonstrating what's possible, then empowering them to build it themselves.