Navigate Complexity, Get Simple
The best leaders I have worked with share one trait that has nothing to do with how much they know. They ask questions. Not as a technique, and not because they were told to delegate more. For them, the question is the actual work. The answer is almost beside the point — it is the asking that drives improvement, and the first questions are usually the simplest ones.
That is a strange thing to say about leaders running complex organizations. Complexity is supposed to call for complex tools: frameworks, dashboards, governance structures, change management methodologies. And those have their place. But underneath most of them sits a small set of questions a curious eight-year-old could ask. Why do we do it this way? How come? So what? Prove it. Organizations spend a great deal of effort building sophisticated answers to problems they have not actually diagnosed, because somewhere along the way, people stopped asking the simple questions that would have surfaced the real one.
The questions we were trained out of
Children ask why on a loop, sometimes to the point of exhaustion, because they have not yet learned that asking can cost something. Somewhere between childhood and a first performance review, most people learn that lesson. Research on workplace curiosity has consistently found that the barrier is not a lack of curious people. It is an environment that makes curiosity expensive.
Harvard Business School's Francesca Gino has studied this gap directly. Her research found that although most leaders say they value inquisitive minds, in practice they often discourage curiosity because they fear it will slow things down or introduce risk. The irony is that the fear runs in the wrong direction. Gino's work also found that curiosity reduces conflict, because people who question their colleagues end up understanding them better, and that understanding makes it easier to manage the uncertainty that complex organizations are full of.
The fear of asking is not evenly distributed, either. Research led by Mark Bolino and Phillip Thompson found that curious employees are sometimes perceived by their managers as insubordinate and less likable, while employees who pair curiosity with political skill tend to avoid that perception entirely. The same question, asked two different ways, lands as defiance from one person and competence from another. But the researchers are careful not to lay that entirely at the employee's feet. They are explicit that managers and employees share responsibility for curiosity being received as well-intentioned, and that managers should not mistake curiosity for insubordination in the first place. A leader who has not done the work of building trust is the one most likely to hear a question as a threat, regardless of how carefully it was asked.
Edgar Schein spent more than fifty years studying interpersonal dynamics in organizations, and his work on humble inquiry offers the clearest explanation for why the same question can land so differently depending on who is asking it and why. Schein defined humble inquiry as the art of drawing someone out by asking questions you genuinely do not know the answer to, from a posture of curiosity and interest in the other person rather than from authority. The distinction matters because not all questions are humble ones. A question asked to learn something is a different act than a question asked to expose something, even when the words are identical. Schein was direct about this: even a confrontational question can function as genuine inquiry if the motive behind it is to help and if the relationship carries enough trust for the other person to feel helped rather than cornered. Remove either of those conditions — the honest motive or the established trust — and the same question becomes an accusation. Leaders who ask questions to catch people out, whether they realize it or not, teach their teams that questions are weapons. Once that lesson is learned, it is very hard to unlearn.
That disposition — genuine curiosity, honest motive, a relationship with enough trust for questions to land as help rather than threat — is precisely what Nelson Repenning and Donald Kieffer build into the structural design of how leaders should engage with their teams. In There's Got to Be a Better Way, their dynamic work design framework begins with a deceptively simple instruction: go and see how the work actually happens. Their first principle, solve the right problem, exists because so much organizational effort goes into solving problems that were never properly diagnosed in the first place. Leaders fix the fire in front of them and miss the design flaw that keeps lighting new ones. Repenning has put it plainly: too many executives cannot describe how the work in their own organization actually gets done.
That same instinct — go and see, rather than assume and direct — is the entire premise of the gemba walk, a practice with deep roots in the Toyota Production System. Toyota's longtime chairman Fujio Cho described its purpose in three words: go see, ask why, show respect. Those three are not separate steps. The going and the asking are how the respect gets shown. A leader who walks the floor and observes before concluding is telling the people doing the work that their reality matters more than the leader's assumptions about it. That is alignment in its most literal form — the gap between what leadership believes is happening and what is actually happening, closed by direct observation and a simple why.
Why the third-grade questions are harder
If why is the kindergarten question, so what and prove it belong to a slightly older grade. These are not requests for information. They are challenges, and challenges land differently than questions do. Asking why something is done a certain way is curious. Asking someone to prove their plan will work is something else entirely, and in many organizations it gets treated as something else: a threat to authority, a vote of no confidence, a problem to be managed rather than a contribution to be welcomed.
Amy Edmondson's research on psychological safety offers the clearest explanation for why this distinction matters so much. Her foundational study set out to test a straightforward hypothesis: that better-performing hospital nursing teams would make fewer medication errors. The data ran the opposite direction. The better teams reported more errors, not fewer. That counterintuitive result reshaped her entire research program, because it revealed that the teams were not actually making more mistakes. They were the only ones willing to say so out loud. Edmondson's subsequent work formalized the mechanism: psychological safety does not predict comfort, it predicts learning behavior, and learning behavior is what predicts performance. Teams that report errors, ask for help, and challenge an approach are not behaving riskily. They are the only teams actually generating the information that lets an organization improve.
This is the piece that gets missed when curiosity is treated as a personality trait rather than a structural condition. Some people will ask the hard question regardless of the room they are in. Most will not, and the cost of building an organization that depends on the few who will is that you only ever hear from the few who will. The prove it and so what questions only become routine practice when leaders have made it unmistakably clear that asking them will not be read as insubordination. That clarity has to come from leadership, repeatedly and visibly, because the people closest to the work are the ones taking the actual risk every time they ask.
What this looks like from a leader
Liz Wiseman's research on Multipliers offers the most direct behavioral answer to how a leader builds that clarity. Her studies of leadership style found that the single most practical shift a leader can make is to stop explaining and start asking. It sounds almost too simple to be a strategy, but it inverts the leader's role entirely. A leader who explains is the source of the answer. A leader who asks is signaling that the answer is not yet known, and that finding it is a shared task. Wiseman's research found that leaders operating this way unlock far more of their team's actual capability than leaders who default to directing, even when the directing leader has good intentions and real expertise.
Put together, the research points toward a leader who does a few specific things, consistently, rather than one big cultural overhaul. They go to where the work happens instead of relying on what gets reported up. They ask why before they propose a fix, and they ask it of the people doing the work, not about them. They treat a so what or a prove it from a team member as a sign the team is paying attention, not a sign the team is pushing back. And they keep doing this when things are going well, not only when something has broken — because the gemba walk and the dynamic work design discipline are not crisis tools. They are how a leader stays oriented to what is actually true, on a normal Tuesday, before the complexity has had a chance to compound.
None of this requires a framework leaders do not already have access to. It requires the willingness to keep asking the simple question even after the meeting has moved on, even when the answer might complicate the plan already in motion. The leaders worth working for are the ones who never quite stop doing that.
Bearing Check
When was the last time you asked your team a question you genuinely did not know the answer to, and let the conversation go where it went? If that is rare, what would it take to make asking — not just answering — a normal part of how your team works?