Have you ever thought about the weight of your requests? As a leader, you want your requests followed through, but sometimes that same instinct works against the team. A question you meant as curiosity can land as a command, and the work that was supposed to get done first slides down the list.
Howard Miller, Chief Information Officer at UCLA Anderson School of Management, puts it simply: leaders carry a certain gravitas. Ask someone for something, and people will often stop what they’re doing and jump on it because they assume the request is urgent. “That’s not always the case either,” he says. The distance between what a leader means and what a team hears is where this problem begins.
Why a “Quick Question” Is Never Quick
Think about the phrases leaders use every day:
“Can you quickly look into this?”
“I’d love to see some numbers on this.”
“Maybe we should explore this idea.”
To the leader, these are exploratory. To the employee, they often sound like “stop what you’re doing and work on this now.” The higher your position, the less your requests sound optional, and research on leadership and power points the same way: employees adjust their behavior simply because a request comes from someone with formal authority.
The message also changes as it travels. It is the telephone game: you say something, one person hears it a certain way, and they pass it down in their own words. The further it goes, the further it can drift from your original intent. He adds that you can say the same thing to eight different direct reports and get eight different results.
The Chain Reaction Behind One Request
Once a request is interpreted as urgent, a chain reaction starts. The employee pauses current work, and the priorities they set aside get delayed. Other teams get pulled in, meetings get scheduled, and the leader’s latest request ends up outranking work that was genuinely urgent. Organizational focus slips without anyone deciding it should.
Our expert in the topic, CIO Howard Miller, describes the same dynamic from the inside. When he asks someone on Team A to help Team B, Team B succeeds, but Team A may not reach what they had planned. Each decision a leader makes affects the decisions that follow, and every ask comes at the expense of something else.
The cost goes beyond the schedule. Research on interruptions consistently shows that switching attention away from a task carries real productivity costs, and returning to the original work takes effort.
Studies by Gloria Mark (Department of Informatics at the University of California) and her colleagues found that interrupted employees often compensate by working faster, but at the price of higher stress, frustration, and workload pressure. This means that responsiveness can look like productivity from the outside while the team is paying for it in focus and energy.
There is a human factor too. Strong performers often struggle to say no because they don’t want to disappoint. They take on the leader’s request, commit to it, and over-promise. Then they under-deliver across the board, because the work was never given room in the first place. They also rarely ask for help with prioritization, so leaders may not see the pressure building.
How to Make a Request Without Reorganizing Someone’s Week
The good news is that small changes in how you ask can prevent most of this. Here are practical ways to do it:
Separate curiosity from priority. If you’re only curious, say so. Try: “I’m curious about this. Please don’t change your priorities. If this requires trade-offs, let’s discuss them first.”
Give every request a priority level. Without one, people assume the highest. A simple scale works: stop what you’re doing, important this week, when capacity allows, or exploratory.
Ask what gets pushed back. “If we take this on, what will stop getting done?” makes the trade-off visible before work starts.
Let people choose the timing. Research on interruptions suggests that negotiated interruptions are less costly than immediate ones. Ask, “When would be a good time for you to take this on?”
Give explicit permission to push back. Authority makes it hard to challenge a leader. Say, “If this conflicts with higher priorities, tell me.”
It also helps to estimate the size of the ripple before you send the message. A single question from a CEO to one manager can trigger analyst work, manager reviews, cross-functional meetings, and an executive presentation. Ask yourself how many hours of organizational effort your request could generate.
Accountability starts with intention. You can’t assume that something you asked for will get done in the way you pictured, and the burden of being clear belongs to the person who asks.
The most expensive words in an organization are often the leader’s casual ones. Authority amplifies intent, so suggestions turn into priorities, priorities into urgencies, and urgencies into mandates. A leader who treats attention as one of the scarcest resources in the company will ask more clearly, and the team will protect what actually matters.

