Knowledge Center: Don’t Solve Problems If You Want To Be A Great Manager

Saturday, March 30, 2019

Don’t Solve Problems If You Want To Be A Great Manager

What Makes A Great Manager Isn't The Problems They Solve, But The Questions They Ask. Start With These 16 Questions Here.

An employee comes to you and says, "I have a problem." If you're trying to be a great manager, what do you do?

Your initial instinct might be to roll up your sleeves. "Time to be the boss," you think to yourself. You're ready to step in, solve the problem and save the day.

Or something like that. You just want to be helpful.

In reality, your instinct is the opposite of helpful. Startlingly, when you jump in to solve a problem as a manager, it's one of the biggest leadership mistakes you can make.

I was reminded of this counterintuitive concept when chatting with Wade Foster, CEO of Zapier, on our Heartbeat podcast. Though his company today is thriving with over 200 employees and over 2 million users, Wade admitted how he struggled in the early days as a CEO when an employee would come to him with a problem:

"When you [jump in and try to solve the problem yourself] you're actually mistaking your roles. You've hired this person to solve problems. And if they're unable to solve the problem, you've probably hired the wrong person."

In other words, your role as a manager is not to solve problems. It's to help others solve problems, themselves. Leadership is stewardship. It's navigating your team through treacherous waters, around jagged rocks, to the desired destination, and making sure folks feel nourished and rested along the way. But you can't be a good steward if you're scampering around trying to paddle all the oars faster, yourself. To take the boat analogy one step further, a great manager is a coxswain, not a rower.

This confusion of roles leads to a highly undesired outcome: You prevent your team from learning how to solve the problem. A dangerous reliance develops that hinges on your expertise, your "final word." Your team never gets to fuss, flail, and figure out how to crack a nut with their own hands. When you're the one thinking through all the problems, you're teaching your team members to not think for themselves.

You also inadvertently slow your team down. Every problem – especially the "hard ones" – are re-routed to you. So what happens if you're out of the office that week? Or, what if your plate is full? Well, that problem will just have to wait. And wait it does. You become a bottleneck, the inhibitor of your team. You funnel your team into single mode of dependency that's difficult to undo.

The best leaders know this, and are keen to avoid this pitfall – so they do something else. They become the team's accelerator. They help team members think for themselves.

How? By asking questions. Wade of Zapier adopted this practice as a CEO, describing it as a "more Socratic way" to helping his team solve problems. Ultimately, it leads to better results.

Ask questions and a team member can come to the answer themselves. Ask questions and the problem they're facing becomes more lucid, less daunting. Ask questions and your team member might even come up with a better answer than you would have.

To be a great manager, here are 16 questions you can start with instead of jumping in to solve the problem yourself:

What do you see as the underlying root cause of the problem?
What are the options, potential solutions, and courses of action you're considering?
What are the advantages and disadvantages to each course of action?
How would you define success in this scenario?
How do you know you will have been successful?
What would the worst possible case outcome be?
What's the most likely outcome?
Which part of the issue or scenario seems most uncertain, befuddling, and difficult to predict?
What have you already tried?
What is your initial inclination for the path you should take?
Is there another solution that isn't immediately apparent?
What's at stake here, in this decision?
Is there an easier way to do what you suggested?
What would happen if you didn't do anything at all?
Is this an either/or choice, or is there something you're missing?
Is there anything you might be explaining away too quickly?

What you'll notice when you ask these questions is that most employees already have an answer (or several answers!) to a given problem. But they were uncomfortable with it, or they were worried about getting it "wrong."

Part of asking the questions isn't just to help them think through the problem more clearly, but also to help them realize they know more than they think, they're more capable than they think, and that they've mitigated the risks better than anticipated.

Your job as a leader isn't to just help clarify thought process – but to give confidence in their thinking.

As Wade says, "You're trying to just help them get to that realization that, 'You know what to do.'"

After all, a great manager is centered on building the capabilities of their team, not their own capabilities

Don't solve the problem, yourself.

Thanks to Claire Lew / KnowYourTeam
https://knowyourteam.com/blog/2019/03/06/dont-solve-problems-if-you-want-to-be-a-great-manager/?utm_source=kytnewsletter

Please Extend Your Patronage...

Kindly Like, Comment, Share, Following:-

"Knowledge Center" For Latest Updates ... Facebook.com/KnowledgeCenter3579

"Knowledge Center" For Latest Updates ... https://ZiaullahKhan.blogspot.com

To Support Facebook "Knowledge Center" & Blog "Knowledge Center" Contents, Please Use This Link: - PayPal.me/ZiaullahKhan1

Or Use this Email Address for PayPal (To Support Knowledge Center Channel):-KnowledgeCenter3579@gmail.com

Amazon USA :- https://amzn.to/2GjhTaB