How I make inexperienced and unconfident decisions
The Marketing Manager gently closes the door behind him, explains it’s been a pleasure working with the team, but he’s been offered a position he can’t refuse and is moving on to new adventures. This position was critical for the company and we needed to find a replacement that could kick big goals.
The Marketing Manager gently closes the door behind him, explains it’s been a pleasure working with the team, but he’s been offered a position he can’t refuse and is moving on to new adventures. This position was critical for the company and we needed to find a replacement that could kick big goals. It was one of those decisions where I felt immense pressure to get it right first time.
After the news got around, one of our Project Managers put his hand up for the position, but he had no marketing qualifications and no marketing experience. However he was an amazing Project Manager, seriously productive and a huge contributor to the team.
My big fear was if I let him take the Marketing Manager position and he was no good, then things could go pear shaped and we might also end up losing a great Project Manager. If I didn’t give him an opportunity I may risk losing him. I’m fortunate that I have a great peer group that I regularly turn to for advice but there are often unique circumstances such as the people involved that ultimately bring the decision back home.
The traditional approach to management decisions where you’re not sure or inexperienced is to:
- Act confident, be decisive and announce a decision; or
- Delay the decision until you’re more confident of the outcome.
I feel uncomfortable acting confident because the underlying message is that “I know what I’m doing and I have certainty in the outcome”. But when it’s an act, you don’t. I also dislike the follow-on pressure that the decision ‘has to be right’. So option 1 was out for me.
When decisions are delayed in pursuit of more certainty, I’ve learnt that it’s easy to fall into a trap of analysis paralysis, lots of time can tick past while resources are consumed trying to predict an outcome. I didn’t think option 2 was going to be effective either — no matter how much time we applied to more research, we would never achieve a confident prediction.
Our answer was to collectively agree that none of us knew how this would unfold, we would give him a go as Marketing Manager, assess the situation after 3 months and label the whole thing as an ‘experiment’. If either party thought it hadn’t worked then we would go back to how we were with no hard feelings.
I’ve found this approach to be incredibly effective on many occasions when I’ve been faced with a decision where I’m unsure or lack confidence in what the outcome might be. I’ve applied it to bonus schemes, staff positions, marketing campaigns etc. The key point is this approach requires a manager to throw away any ego or a self-imposed perception of needing to be ‘all-knowing and confident’ in every outcome. There is agreement that nobody knows how it will unfold.
The simple act of labeling a decision as an experiment carries a message that “this may or may not work, and that’s ok”. It must be communicated to the broader team so everyone is aware of the experiment. This creates a safe environment with an escape route for all parties to comfortably return to how things were, without a fear of failure. And most importantly it allows you to take risks that you wouldn’t take if you always have to be right.
And as for the Project Manager, well it was one of the best experiments ever…. for us both. Christophe was an AMAZING Marketing Manager, he really did kick big goals and a couple of years later went on to work with Atlassian where he became Head of Product Marketing.
Originally published on hrmonline