How to approach failures as a leader?


Hey friend,

In this week's deep dive, we're flipping the script on failure.

In our journey as leaders or developers, we inevitably encounter failure either through bugs or challenges while tackling difficult problems or, rather, problems in general.

But what if we viewed these moments not just as setbacks, but as valuable lessons?

Do you prefer reading on the web? Here's a link for you


Today, let's learn from Mark Rober (former Nasa Engineer πŸš€ and Youtuber).

Mark Rober conducted an experiment with 2 groups of all age groups, teaching them to learn to code. He wanted to prove that anyone from any background could learn to code, so he challenged them to get through the maze.

The reality? This maze was impossible to solve and no one could solve it.

😲 50,000 of them took the challenge.

Mark's intriguing experiment sheds light on how people react to failure.

Participants were tasked with coding a robot πŸ€– to navigate a maze - a setup designed for failure.

  • Group 1 received a neutral message upon failing: ​
    "⚠️ You have failed, please try again."
  • Group 2 received a message emphasizing loss: ​
    "⚠️ You have failed, you have lost 5 points, you now have 195 points, please try again."

The result? 😲

Group 2 made fewer attempts than Group 1 because they were scared to fail. Isn't that interesting?

Why do we let the fear of failure hold us back?

πŸ”– This highlights 3 crucial points:

  • The framing of failure can significantly impact our willingness to persist and try again.
  • A fear of failure holds you back about feeling good about the thing.
  • Those who were not discouraged by failures made more attempts to solve the puzzle, leading to more success and learning.

There are 3 takeaways here - Act like a Scientist would πŸ§ͺ

πŸ–ΌοΈ Perception of Failure

If we start viewing each failure as an experiment, it becomes a hypothesis tested, not a verdict on our abilities.

As leads, we must foster an environment where failures are seen as steps in the scientific method of success.

πŸ”„ Encouraging Persistence

Just like in a lab, repeated trials are essential.

By removing the stigma around failure, we encourage the team to try different approaches, learn, adapt, and innovate. Just like it was emphasized in Mark's experiment with Group 2.

πŸ›‘οΈ Creating a Safe Space for Trial and Error

Every experiment brings us closer to understanding what works and what doesn't.

Let's emphasize that each attempt, each 'failed' experiment, is a precious opportunity for learning, leading to better solutions and personal growth.


Here's a Homework for you 🧠

Next time a project goes differently than planned, analyze the outcome. What can be learned? How can this new knowledge be applied in the future?

How do you handle setbacks in your team? Have you ever had a failure that turned into a success story? Please just hit reply and share your experiences.

I'm all ears, and your story could be the highlight of our next issue!


🧰 The Engineering Leader's Toolbox

  • πŸ§ͺ For a Master class in Learning from Failure, check out Mark Rober's experiment. It's a powerful illustration of the impact our perception of failure has on our actions. πŸ‘€ Watch the experiment ↗️.
    ​
  • πŸ’― Redefining Success using Pathless Path, the book is now free, so check it out here ↗️. Should we move away from a conventional emphasis on academic excellence, career success, and achievement at the expense of our true passions?

Do you think this was useful?

With your feedback, I can improve future emails. Click on a link to vote:

​πŸ”₯ 😐 πŸ‘Žβ€‹

​​​

Thanks for reading! Reply any time.

When you're ready, here's how I can help you:

  1. πŸš€ Turn into a Successful Engineering Leader - Learn the essential skills to Become an Engineering Leader Course
    ​
  2. πŸ“™ Get an E-book on Taking control of your First 90 days as a Leader - An Ebook: The Engineering Leader's Playbook: The First 90 Days
    ​
  3. ☎️ Book a 1:1 Coaching call with me

Ankita Kulkarni

Join 9200+ subscribers reading by weekly personalized Newsletter that helps developers level up their skills through weekly Frontend and Leadership Snacks. You get a deep dive into a Tech topic, Actionable tips to excel in your career and a toolbox!

Read more from Ankita Kulkarni
A terminal interface displays commands for a tool called next-browser, designed for AI agents to analyze and monitor Next.js applications.

Hey Reader, This week, Next.js 16.2 gave AI agents something they never had "a browser". Your agent can now see your app, find the problem, and fix it without asking you. This along with GPT-5.4 mini & nano (2 small models), TanStack Start going 5x faster, why you should ban useEffect, and more. Let's dive in. 🍿 Our Weekly Snack: Your AI agent can finally see what your users see (Next.js 16.2 is here) Next.js 16.2 dropped yesterday (deep dive here) and it just gave AI agents a browser. It's...

next.js proxy

Hey Reader, Middleware got renamed to Proxy in Next.js 16. Same functionality. Better name. What is Proxy? Every request to your app has to go somewhere - a page, an API route, a file. Proxy gets to look at it first and decide what happens: send the user somewhere else, serve different content silently, or just let it through as-is. Think of it as a traffic controller 🚦 sitting in front of your routes. So, why you should stop putting auth in Proxy? It feels like the perfect place but it...

You’re Suspending the Wrong Component

Hey Reader, There are thousands of you going through Modern Full Stack Next.js Course so wanted to be grateful here for your support. Just as a thank you, there is something big dropping for you. It will only last 24 hours ⏰ so keep an eye out for my email next week. Let's dive in! PRESENTED BY CLERK Instead of your coding agent guessing how auth works, you can now install specialized Clerk knowledge directly into it. Introducing Clerk Skills One simple command $ npx skills add clerk/skills...