The truth is that most people are afraid to ask questions—whether from years of conditioning within a company or plain old human nature. Whatever natural curiosity they had as children tends to get discouraged in most large organizations. Leaders assume following the status quo is the right way to go and are not interested in trying to challenge anything, especially if it seems on the surface to be going along just fine. And the lower-level employees just try to do what’s asked of them and stay out of trouble, believing that people who ask questions may be sticking their neck out.
Obviously, getting people to start asking questions — getting them to use fresh eyes and act on that new perspective — requires effort and energy. It means changing what may have been part of a process for years. Change is very hard. It actually means choosing the path of resistance, instead of the path of least resistance. But when people get into the habit, and know they won’t get their head chopped off for asking questions, that in fact their questions will be welcomed, everything gets better.
The best way to teach is by example. Buddha and every other great leader throughout history taught by showing or doing, not by telling. When your people see you, the leader, asking questions (i.e., questions about how and why things are done, not questions regarding people’s individual intentions and/or productivity), they will begin to feel comfortable answering your questions, and they will start asking similar questions with their folks. And those folks, in turn, will start to realize that challenging things and offering information about what is really going on in their department is something that is encouraged. When you are willing to admit in front of everybody that you don’t know a particular answer, and you are the boss, then that makes others understand that they also can admit they don’t know. This enables free flowing information, which is essential to the health and productivity of your organization.
This sounds pretty simple doesn’t it? So why does this reticence, this reluctance to ask questions, occur so often? Why is it so hard for leaders to know what’s going on at the lower levels of their companies? The main reason is that leaders are fundamentally not interacting well with their employees.
Obviously most leaders don’t promote a closed-door policy or a bad environment. They just don’t actively promote the opposite. But the absence of a positive message is still a message, just as making no decision is actually making an important decision — a decision to do nothing. The process of questioning is actually hard — -and it is a process. There are no simple approaches here to reset what has been years in the making. https://www.linkedin.com/in/denispicard
When I interviewed Denis Picard, a managing director who specializes in technology and operations at Alvarez & Marsal’s Business Performance Improvement in New York, he told me a story that illustrates what can happen when people don’t ask questions.
“We had a client in Boston,” said Picard, “a communications technology manufacturer, rapidly growing, who needed to put in a new ERP [enterprise resource planning] system. As I’m sure you know, ERP systems have a high risk of failure, and if you don’t have senior management support you cannot succeed.
“This Boston client had picked a system, configured the system, converted the data, and they were ready to go. Then the CFO, who is a friend of mine, called me and asked me if I would come take a look. He said they were supposed to go live, but he wasn’t feeling good about what was happening.
“So I spent some time looking into it and found out that the implementation has stalled. They were supposed to go live maybe in a month or two, but things were at a standstill. I had a conversation with the CIO, who was the project leader, and I asked him what the problem was.
“’We lack senior management support,’ he told me. ‘Wow,’ I said. ‘That sounds pretty serious. Why do you say that?’” ‘Because the CFO won’t help us,’ was his answer. And I thought, That’s interesting because the CFO was the one who asked me to check into this. What’s he doing wrong?
“So we kept talking about this,” said Picard, “and it turns out they couldn’t complete the final test and go live unless they bought a special printer—because they had to do some kind of labels that go on circuit boards or something like that—but in any case it was a very special printer, and it was going to cost $12,000.”
Article Continues Below
When I asked Picard what the CFO has said when the CIO informed him of this, he told me the CIO had hesitated and then replied, “Well we haven’t really asked him.”
“Why not?” Picard had wanted to know. “Why wouldn’t you have asked him?”
“He’s going to say no,” the CIO said. “Because it’s very expensive. I can’t ask him; it would be really bad for my career.”
Picard went to the CFO to report back and told him, tongue in cheek, “Well, I found out that you are the problem.”
The CFO looked at him kind of quizzically and said “What are you talking about?”
“My understanding,” said Picard, “is that you will not approve a $12,000 printer that you don’t know anything about, and that’s going to cause the project to be delayed.” The CFO was nonplussed. Absurdly enough, the project was costing about $5 million, and a $12,000 printer was holding it hostage. Of course in the end they bought the printer and finished the project.
If you engage your employees, they will not be afraid to come to you and tell you what is really happening. Their natural curiosity will come back, and they will start questioning things. However, this is a process that requires constant fine-tuning.