Work, Reconsidered: Questions Aren't Threats. They're Invitations to Think.
I ask “why” a lot. Actually… that’s probably underselling it.
But here’s the thing... I don’t ask every question that enters my brain. That would be exhausting for everyone, including me. Some questions can be answered by paying attention. Some require research. Some need to wait for the right conversation. Some aren’t important enough to ask at all.
The ones I do ask usually begin in the same place... I’m trying to understand what we’re solving, why we’re solving it this way, and whether the process is giving us the result we intended.
Asking questions at work can still be interpreted as resistance, criticism, or an unwillingness to follow direction. Sometimes it is. People absolutely use questions to disguise opinions they’ve already formed. But thoughtful questions can also uncover information, prevent expensive mistakes, clarify expectations, and help a team make a better decision.
The difference is not whether someone asks why. The difference is what they do before, during, and after they ask it.
Curiosity Helps Us Find the Real Problem
One of the things I’ve learned over years in recruiting is that the visible problem is rarely the whole problem.
A role that’s been open for six months might look like a sourcing problem until you realize the compensation doesn’t match the market. A hiring manager who keeps rejecting candidates might look impossibly picky until you discover nobody ever calibrated what “good” looks like. A process with four interviews might have started with reasonable intentions until years of people adding “just one more conversation” turned it into an assignment and seven interviews.
You don’t discover any of that by treating the first explanation as the final answer. You discover it by getting curious.
That curiosity is one of the most consistent things I bring to my work. Give me the difficult search. The messy process. The workflow everyone complains about but nobody has had time to fix. Give me the hiring manager who knows they need someone but can’t quite articulate who. I’m going to want to understand what is happening underneath what we’re seeing.
Questions are part of that. So are data, observation, listening, and knowing enough to recognize what I don’t know.
Maybe there’s a legal requirement I haven’t encountered. Maybe the customer needs something that isn’t obvious from where I’m sitting. Maybe someone tried the seemingly obvious solution three years ago and discovered a problem I haven’t considered. Maybe there’s organizational history I wasn’t there to experience.
Tell me. Now I know something I didn’t know before.
But sometimes the answer is, “I’m not sure.” Sometimes it’s, “That’s how we’ve always done it.” And every once in a while, someone gets halfway through explaining why something has to be done a particular way, stops, and says, “Huh. That’s actually a really good question.”
Those are some of my favorite moments at work. That’s where things can get better.
I’ve watched recruiting processes retain steps nobody could clearly explain. I’ve seen job descriptions inherit requirements until nobody could remember why candidates needed them. I’ve watched approvals take so long that the candidate accepted another job while everyone was still discussing whether they were allowed to hire them.
None of those things happened because someone intentionally designed a bad process. Organizations accumulate things. Another interview. Another approval. Another field in the ATS. Another meeting. Another rule created to solve a problem that may not even exist anymore. Eventually, “the way we do things” can become completely disconnected from why we started doing them.
Someone has to notice. Sometimes someone also has to ask.
Not Every Question Needs a Microphone
Curiosity shouldn’t be a disguise for ego. “Why are we doing this?” can be a genuine request for context or a passive-aggressive way of saying, “This is stupid and I could do it better.” People can usually tell the difference. The key to this is USUALLY. For me, usually isn't enough to blatantly disregard anyone's question(s).
I don’t want to walk into a new organization and immediately start explaining everything it should change. I want to understand what I’m walking into first. What’s working? What have we tried? Where are the constraints? What does the data tell us? What do the people closest to the work know that I don’t?
I also don’t believe every observation needs a meeting, a Slack thread, and a six-person working group.
Some questions answer themselves if I spend ten minutes looking at the information already available. Some belong in a one-on-one conversation rather than the middle of a team meeting. Some can wait until we have enough information to do something useful with the answer. And some are preferences dressed up like problems. Those can stay with me.
When I do raise something, I want to bring more than “this doesn’t work.” What am I seeing? Why does it matter? Who or what is being affected? What might happen if we leave it alone? What options could we consider?
Sometimes I recommend a change. Sometimes I ask for context. Sometimes the answer explains something I hadn’t understood, and I move forward with better information. Sometimes I change my mind. I would much rather change my mind because I learned something than protect an opinion just because it started as mine.
The question is not the contribution. What we learn and do because someone asked it is where the value lives.
Clarity Is Part of the Work
Sometimes a question isn’t about challenging a decision. Sometimes I’m just trying to figure out what the decision actually is.
Leaders often roll out a process or give an instruction believing they’ve been perfectly clear. From their perspective, they probably have been. They know the earlier conversations, the context surrounding the announcement, and the problem they’re trying to solve.
The people receiving the information may not know any of that. They hear the words that were actually said, and sometimes those words could reasonably mean several different things.
“We need to move faster.”
Where? What are we willing to change to make that happen? What aren’t we willing to sacrifice?
“Take ownership.”
Of the outcome, the process, or the decision? Do I have the information and authority required to own it?
Those aren’t attempts to be difficult. They’re the questions that turn an idea into something people can actually execute.
I’d much rather ask the extra question at the beginning than confidently execute the wrong interpretation for three weeks and discover afterward that we were working toward two different outcomes.
In recruiting, that matters tremendously. A vague statement from a hiring manager can become the wrong sourcing strategy. An unclear requirement can eliminate candidates who should have been considered. An ambiguous change to an interview process can create a completely different candidate experience depending on which recruiter or interviewer happens to be running it. This can pertain any role... not just recruiting.
Clarity isn’t a nice-to-have when people are expected to execute. It’s part of the work.
Silence Is Expensive
When people believe questions will automatically be interpreted as criticism, they start calculating whether speaking up is worth the risk. Eventually, many decide it isn’t.
They still notice the broken process. They see the unnecessary meeting. They know the new workflow created three problems while solving one. They may have information the rest of the team needs. They just stop saying it out loud.
That’s an incredibly expensive kind of silence.
Psychological safety at work doesn’t mean every idea gets adopted or every decision remains open for debate forever. It means people can share relevant information, ask for clarity, acknowledge a mistake, or raise a concern without becoming the problem for doing it.
The strongest teams I’ve worked with haven’t agreed about everything. That sounds terrible anyway. They made room for thoughtful disagreement, honest questions, and new information. Then they made decisions and moved on them, as a team.
There are times when I ask a question and learn something that changes my perspective. There are times when the team adjusts its approach. There are times when neither happens, but we understand the issue better because we discussed it. And there are times when the decision has been made, the reasoning is sufficient, and my responsibility is to execute it well.
Collaboration isn’t everyone agreeing with me. It is contributing what I know, listening to what other people know, and helping the work move forward.
Curiosity Should Lead Somewhere
Recruiting has never been just about finding people for me. It’s about systems, behavior, decisions, communication, expectations, and the hundred small choices organizations make before a candidate ever receives an offer.
It’s why I notice when candidates keep dropping out at the same stage. It’s why I care whether interviewers are evaluating the same things. It’s why I question a requirement when the market repeatedly tells us it doesn’t make sense. And it’s why I don’t want to stop at identifying what’s wrong. I want to help build what works better.
I will probably find the weird process everyone stopped noticing six months ago and wonder why it takes eleven steps. But I’ll also investigate before assuming, listen to the answer, change my mind when the information changes, and help solve the problem I’m raising. For me, it's not about being right. It's about doing the right thing.
If there’s a good reason we’re doing something exactly the way we’re doing it, great. Now I understand the why. Once I understand the why, I’m very good at figuring out the how.
The value I bring isn’t simply that I ask questions. It’s that I know how to connect a question to evidence, business impact, and possible solutions without losing sight of the people affected by it or the outcome the organization needs.
Thoughtful questions can expose a risk, clarify an expectation, prevent wasted work, improve a candidate experience, or help a team see an option it hadn’t considered. They can also confirm that the current approach is the right one.
Questions don’t automatically signal resistance. Sometimes they signal engagement. Sometimes they signal someone thinking three steps ahead. Sometimes they come from the person who cares enough about the work to notice that the result and the intention no longer match.
Curiosity doesn’t have to create friction. Paired with context, timing, judgment, and a willingness to help, it creates understanding. And sometimes it creates something even better than the way we’ve always done it.
Questions aren’t threats. They’re invitations to think.
Comments