I Have a Question for You—Do You Have Any for Me?
[Cartoon courtesy of Grantland Cartoons]
If your company's employees are lucky, their bosses are all-purpose solution centers—similar to an IT help desk except understandable and efficient. That's not to say the bosses, who are doing duty as these one-stop-shop question catch-alls also are lucky. I guess they're pretty unlucky to be saddled with so many questions, come to think of it.
But regardless of whether bosses are able to provide solutions, that's how employees view them, and that's why there's usually a line waiting outside their door or in their cue of unanswered e-mail. For that reason, companies that want their managers to operate at their best—and most profitable—should teach them in leadership classes not only which questions to answer and not to answer, but which questions to ask. Most of the time, if not all the time, employee questions should generate equally provocative questions from managers.
For example, say a sad employee wants to know whether they'll be raises and promotions this year (a common question during a recession). Instead of the boss simply giving him the party line from the company's human resources department about the hiring and salary freeze, the manager might want to ask a few questions of her own. "Are you feeling under-appreciated?" she should ask. "Because if you are, you should know that's definitely not the case. I've noticed all the great work you've been doing, and as soon as I'm able to, I'll push for you to be recognized by the company in the form of a raise and promotion." Or another good one might be: "Are you feeling overwhelmed by the workload? Things are tough now, but I think if we can pull through this hard time, there may be rewards down the line. Let me know of any ideas you have to reorganize your work flow. Maybe there's a way we can jigger your commitments so they're more manageable."
Questions regarding the organization hierarchy also should inspire questions. How about when an employee consults with the boss because she isn't sure who to send a customer request to? Maybe that confusion signals a departmental structure that isn't working. "Would it help if that work function (let's say product development specialist) had a point person designated for our division? Let me see if I can do something about that. I'll at least float the idea during the next managerial meeting, and you never know, we might get our wish." Another question that should spring from questions about organization structure involves the extraneous. "So, you don't know what Tommy does? That's interesting. I wonder how many other people don't know what he does? What are you hearing? Maybe we need to meet with him to review the responsibilities he's taken on."
Queries from customers are especially question-inducing-worthy. How about the times when an employee visits one of your managers' offices to tell him he doesn't know how to answer a customer's question. "When did you last receive training on the Giant Panda Retractor?" the manager should ask. "Maybe it's time for an update on that. Why don't you round up Sally and Henry, and next week, we'll sit down to go over the Giant Panda's capabilities and troubleshooting techniques, and how it differs from White Tiger Two, so you'll be able to up-sell better." Sometimes the questions employees bring managers can be passed on as questions from the manager to the product and services department. "Why do you think that customer didn't like Sea Turtle Adapter Version 2.0 and wants to revert to Great Dane Navigator? Maybe I should ask the product development team to incorporate the characteristics of Great Dane into the next version of Sea Turtle we release. Or maybe we could ask them to teach us a quick-fix you could give customers over the phone so they don't have to wait. What do you think of that?"
The worst is when the manager gets angry that an employee doesn't know something. Partly it's bad because in the future the employee won't bother to ask, and then will likely give wrong information to a co-worker or customer, or deliver a service to a customer that has flaws in it. Plus it's bad because it says something about the manager himself—it says that he's not open to trial and error, or rather, he's open to "trial" but not the inevitable "error" that occurs when new ways of doing business are explored. I bring up "error" because it's common for questions brought to managers to be about how to fix a mistake. It might be that a new idea for the Website ended up crashing the site or a new way of inviting business partners to a meeting didn't work and now those business partners are confused and annoyed. Yes, it's aggravating for mistakes to occur, but there also are a lot of great questions that mistakes bring to the fore. "So, the new E-Invite technology is harder than we thought it would be? What are some of your thoughts on how we can fix it so this doesn't happen again? How can we make it even better so business partners in the future not only know about our events and are able to respond, but are given added help in booking flights and hotel rooms?" the savvy manager asks rather than openly fuming.
Then there are the boss questions involving needs for extra time off. "Oh, that's a shame. Is it hard for you to both put in a full day and pick up little Timmy from soccer practice? Would a flex-schedule on Tuesdays and Thursdays work for you better?" the solicitous boss might ask. Or how about the peach of a manager who's worried about a worker having enough time for himself (irregardless of the presence of a child in his life): "Why don't you pick one day a month to work from home and catch up on your own life for a change?"
The best part is asking all, or any (or anything similar to), the above posed questions may negate the worst question of all: "Why are you leaving us?"
How good are your managers at asking astute questions in response to queries from employees and customers? And how good are you at teaching them this skill?