Last week was about Lies of P and expecting difficulties.  This week is about boss fights and the importance of understanding the situation before sprinting forward. 

I had made it through the first few bosses without much trouble and then I ran into Fuoco, the King’s Flame.  It was a giant incinerator like puppet (robot).  I went all in and was super aggressive for my first attempt.  It didn’t go well.  He quickly killed me.  After that, I switched up my approach.  I started playing more cautiously and slowly for a few rounds.  My kids saw this, thought it was weird, and asked why I wasn’t rushing in aggressively again to win.  I explained to them that I wasn’t trying to win the fight right now.  Right now, I was trying to better understand what I was up against.  I was spending time learning his moves and finding his weak spots.  I knew that after I had a better understanding of the fight, I would be able to be successful.  Sure enough, when I finally went all in, I was able to get him down to about 10% of his health before he ever hit me the first time.  My kids were amazed at how I was virtually flawless in the battle. (I’m virtually flawless in life too, so they shouldn’t have been surprised 😉)

What does this have to do with anything?  In the above story, I quickly failed because I didn’t know what I was up against.  If I would have kept charging in super aggressively then it would have taken me a long time before I was able to win that battle.  I would have kept failing over and over again, because in my rush to move fast I would not have been learning the critical things about the boss fight to be successful.  Investing time in approaching the situation more slowly, so I could understand it, ultimately enabled me to move faster toward success.

Now let’s look at the parallels with work.  Have you ever had a project or assignment where you just went blindly barging in full steam ahead?  How did that turn out for you?  I’ve done that and it never works out particularly well.  When I just rush in, I often fail to understand the true problem or miss important bits of information, and both lead to failure.  Throughout my career, I’ve had to learn that the most important thing I can do for any project is understand what we are trying to accomplish, why, with whom, and how the deliverable is going to be used.  I’ve learned that if I invest the time to slow down to understand those things, then I will be able to be faster and more successful in the future.

The challenge: Will you be willing to take your time to understand the situation before trying to charge forward?

Have a jolly good day,

Andrew Embry