I returned to work last week from a short vacation.
​
When I logged back in, I quickly saw there had been some problems while I was away. Some code that processes authentication requests was running extremely slow.
​
As I read through the thread, I realized this was code I had worked on😳
​
And for the rest of the week, even though my team had solved the problem quickly and prevented an outage, I kept apologizing over and over. I was casting blame on myself.
​
This week's article dives into the differences between taking responsibility vs. blaming ourselves for errors (big and small).
​

Team-Building Exercise

This week's Team-Building Exercise is about helping your team avoid the trap of self-blame. Look for ways to encourage someone out of a "blame spiral" where, like me, they apologize profusely and ignore the progress or learnings that came from the error.
​
Navigating the different emotions and factors that come into play when recognizing a failure can be difficult. You can't just say, "Don't worry about it." You have to acknowledge the failure and address it while moving beyond it.
​
One way I've found to help redirect attention away from the person and toward the learning is to reframe things in light of the team and not one person.
​
When they say, "I broke XYZ," I remind them that the code went through a code review and, therefore, other engineers missed the same bug during the review.
​
I remind them that our code has automated tests that didn't catch the bug either.
​
I remind them that we tend to prefer shipping quickly in some cases rather than having perfect code, and there is accepted risk when we do.
​
Then, we have to keep the focus on learning. What can we improve to avoid this bug (and ones like it) in the future? What tests do we need to write? What could we have done differently?
​
In either case, creating a culture of encouragement and a focus on continual improvement is the basis for creating a safe and blameless culture.
​
Find a teammate to encourage in either a failure or a job well done this week.

Here are some more resources from me to help you build better teams!​

Other Creators I Recommend

Hi! I make things for creators. by Thomas McGee I’m a web developer by trade, but I’m a creator at heart. As such, I constantly find myself making, designing, and coding new things to make life easier for creators of all kinds. Whether it be Radarist for managing your projects and tasks or Tubelinks for showcasing your best work—I’m here to make it easier for anyone to earn online. Subscribe​

Nerd Notes | Power-up your freelancing By Chris Hufnagel Every Tuesday, creative freelancers (like you) learn from my 12+ years out on my own. Pricing, productivity, mindset, and everything in between. Subscribe​

​

113 Cherry St #92768, Seattle, WA 98104
​Unsubscribe · Preferences​

​

​