A Hero’s Journey

Standard

I spoke with my team this week about the hero’s journey, or Joseph Campbell’s monomyth. This was brought up in a leadership program at Mozilla as a tool we could use to understand the different types of journeys we take as leaders and what phase we might be in.

Hero's Journey

There are a few things I wanted to emphasize with the group:

  • Put things in perspective. “The Pit” or “The Abyss” can seem pretty daunting and when you’re in the middle of it, things can seem pretty bleak. However, once you conquer a few, you build confidence and recognition that what you’re facing isn’t the end of the world — that you’ll find a way to work your way through it and make a breakthrough.
  • You need faith. Belief in yourself, your abilities or your cause can sustain you through otherwise dark periods. There’s a reason why you answered “The Call” — just like Luke left Tatooine in Star Wars without really thinking about it. It’s because deep down, even if you are frustrated or tired, you know you can accomplish great things and overcome this challenge.
  • You will need allies. There is no Luke Skywalker without Yoda or Obiwan. Likewise, you won’t be able to move mountains without help from others. Could be your mentor, your god, your friends or your spouse. Either way, it’s important to realize that to make true breakthroughs you need to open up enough to let people help you get to where you need to go. Help can come as feedback, support, listening or many other ways. Remember to look for it and seek it.

Not very useful, but I found it pretty entertaining to deconstruct movies from the 1980s and see how they fit in with (or butchered) the formula. It’s interesting to see how they used montages to breeze through parts of a hero’s journey just because of budgeting or time constraints. You have to admit, though: the training montage from Rocky IV is pretty epic.

Anyway, just wanted to share some of those thoughts.

Take care of the little things

Standard

My grandmother told me two things when she dropped me off at school:

  • Be good
  • Do your best

Simple, right?

In most systems, especially those that deal with people, this simplicity is something you have to claw and scratch for. It doesn’t come free. If you’re a manager it’s usually at your expense and it’s a part of your job.

Learning what makes people happy or sad is an important part of achieving this simple success. Getting the best out of your people, and having folks do things the right way — for the right reasons — requires some basic knowledge about what motivates or demotivates people.

Unfortunately, this takes some time. You’re not going to know everyone inside-out after a few days; not even after a few months. So where do you start? You start simple. You start with the small things:

  • Be polite. Wait your turn. Hold the door. Say thank you. Clean up after yourself. Say sorry and mean it. Offer other people gum.
  • Listen to people. Make eye contact. Let them finish talking. If you don’t know what they said, ask them so you can understand. Empathize with them.
  • Be on time. Show up when you say you will. Let people know if you can’t. Reschedule promptly if you have to. Don’t waste people’s time.
  • Random acts of kindness. Notes saying “thank you!” or “you’re awesome!” mean a lot. Cards on birthdays, holidays, new babies. Gifts: trophies, action figures, mugs, gift cards, scotch, etc.
  • Go out of your way for them. Stay late. Reschedule a meeting if they aren’t done yet. Put off your dinner plans to be there with them during a launch. Reply to their late email. Give them a ride home when it’s raining.

If you find yourself in a corner because you don’t know everyone on your team, relax. The best part about these small things is they are universal motivators. They build trust and relationships at work, home or elsewhere.

Over time, you’ll get to know your team and build on what you’ve started. Until then, do the small things — and keep doing them. Eventually, your team will be good and do their best because you did the same first.

More reading:

Engineers and other anomalies

Standard

In cased you missed it, Nicholas C. Zakas wrote a great post about the care and feeding of engineers and why they’re so grumpy.

If you have worked with engineers, this should either resonate with you, leading you to recognize your past misunderstandings and want to bear-hug engineers tomorrow OR you won’t read the whole thing and pass it off as another passive-aggressive rant from the techno-elite. Seriously, though, please at least read it.

If you are an engineer with some decent experience, you’ll likely grab a box of tissues and nod along like you’re seeing Shawshank Redemption for the umpteenth time. Near the part where he talks about engineers as creators, you’ll get the same feeling you got when Red said, introspectively:

“But still, the place you live in is that much more drab and empty that they’re gone. I guess I just miss my friend.”

So. Beautiful.

But wait! Put down the tissues. Before you start emailing your non-technical colleagues or tattooing this article on your chest backwards so you can read it in the mirror, there are some points I want to cover:

Mental fatigue and the culture of NO

Adopting NOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!! as your default response to things usually doesn’t work. Here are situations where it won’t work:

  • When U.S. customs asks you for your passport
  • When your grandma asks you to pass the mashed potatoes
  • When a cop asks you for your driver’s license and registration
  • When your best friend asks you to babysit their dog

Why smart and talented people would adopt this as their default reaction to questions is beyond me. The motivation behind the response is pure — focus on shipping, no time, reluctance to context-switch, etc. — but the reaction is entirely predictable in almost every case:

  • Jail
  • Dad punches you
  • Jail
  • (# of friends you have) – 1

All I’m saying is you get a chance to apply some creativity here. When that doesn’t work, at least apply restraint and say two magic words: “Yes, but…” Still confused? Here are some examples:

  • Yes, but it’s buried in my bag. Just a second, sir.
  • Yes, but my hands are terribly swollen and I have to use the bathroom. Ask Dad.
  • Yes, but my glove compartment is locked. It will take me some time to gather my legal documents.
  • Yes, but my house is getting fumigated and I’m flying to Peru that day.

Take the mental leap and apply it to work situations. If you can’t, your manager should be able to help. If they can’t, quit now.

Stop fixing stuff and take time to celebrate

An engineer’s obsession with creating is a great, wondrous thing. In my experience, it’s not unlike an addiction. It’s almost instinctive for an engineer to stay up late, whittling way at an impossible problem, fighting for that extra inch of performance, elegance or security. They can become immersed in fixing every bug, every issue in their project — but what about the positive parts? Where is there time for celebrating, recognition, reward and reflection?

Nicholas stated it well:

The software is our baby, and we like to care for it as such.

But as with most addictions, there isn’t much room for anything else. That baby can consume you, robbing you of some basic necessities like food, sleep, companionship, paying your taxes, personal hygiene and fashion sense. Bad baby!

I often remind engineers to spend equal time on the positives. In a culture so focused on finding creative ways to solve problems, we forget to recognize some basic things:

  • how much work went into the whole thing (a ton)
  • how much we learned from the project
  • what actually went well (a lot)
  • how cool the final result was

Don’t be selfless and obsessed. It makes you grumpy. Take time to appreciate what you’ve done together with your team (which includes designers, product managers, etc.) and take time to stop worrying about bugs. It’s not just about being positive — it’s about being human and letting yourself feel good about what you did.

Sometimes you’re just an asshole

There are those times where engineers are assholes. Yes, I know this may come as a shock to many, but engineers are also capable of being unjustifiable assholes. Over time, life will help you identify when you’re doing this, but if you need help read The No Asshole Rule by Bob Sutton.

If you’re an engineer and you engage in asshole behavior, it’s not justified by a silent frustration caused by other people. In those cases, it’s way easier to say, “Wow. I was an asshole yesterday and I’m sorry.”

Don’t go down the road of asshole justification. It’s a messy road, filled with bullshit. It’s often public, humiliating, and irreversible. Just say sorry and learn how to get your point across without alienating the people you will need to work with tomorrow. It actually feels great to talk it out with the team, the person you had issues with and regain your footing.

Stop digging a hole, put the shovel down and apologize.

Congrats, you made it this far!

Those were just some side comments to accompany a thorough post by Nicholas. Hopefully it helps and you spent the time to read and understand what I was saying. But if not, well…

He’s flippant, but is he right?

Standard

Criticizing tone instead of having rich discussion is a waste of time. In most cases, the time it takes to criticize tone and delivery can be spent arguing the issue at hand.

In a case where someone has the courage to raise their voice and question things publicly:

  • Try not to discourage them from speaking up in the future
  • Focus on what they said, not how they said it
  • Address the issue in your response, always

In Paul Graham’s post about how to disagree, he states:

“So if the worst thing you can say about something is to criticize its tone, you’re not saying much. Is the author flippant, but correct? Better that than grave and wrong. And if the author is incorrect somewhere, say where.”

While it’s not constructive to react and submit knee-jerk comments, it’s just as counter-productive to criticize tone and delivery instead of offering solid reasoning as to why you disagree.

Of course, we can frame things initially in order to not invoke a predictable response to our snarky comments. But outside of insults or out-of-bounds comments (which are usually best ignored), I usually prefer to focus my energy on the problem, not examining words and etiquette.

Be wary of criticizing tone. It’s not as productive as it might feel and won’t do anything to change the end result.