An order gets followed less often than the question that replaces it

Two weeks before the holidays, Talia's small print shop landed the biggest order in its five-year history, a run of custom packaging for a regional grocery chain. The problem was the deadline. Her floor manager took one look at the schedule and told her flatly it couldn't be done, not with the machines already booked for existing clients.

Talia had two instinctive options. She could push the deadline through by order, telling her staff to make it work and dealing with the resentment later. Or she could walk away from the order and protect the schedule she already had. Instead, she called the whole floor together, explained honestly what the order would mean for the shop if they landed it, and then asked a simple question: is there any way we could make this work, and if so, how?

She expected silence. Instead, one of her press operators suggested running two smaller existing jobs back-to-back overnight instead of during the day, freeing up daytime hours for the new order. Someone else offered to shift a personal day. A third employee pointed out that one of the existing clients had actually asked for a later delivery the week before and might not mind a short delay if someone simply called to ask.

None of those ideas were things Talia would have thought of on her own, because she wasn't the one running the presses every day. The order shipped on time, and more importantly, her staff had ownership over exactly how it happened, because they'd built the solution themselves.

This is the difference between commanding and asking that shows up again and again in accounts of people who've turned around struggling teams: a naval captain who interviewed every sailor on his ship before changing anything, a manufacturing manager who asked his floor what do you think more than he told them what to do. Orders get obeyed. Questions get people invested, because a solution someone helped build is a solution they defend.

The next time you're tempted to hand someone a directive, try describing the problem honestly instead and asking what they think should be done about it. Before a review or a difficult conversation, give the other person questions to sit with beforehand, so they walk in with their own honest thinking already done. Direct your questions first to the people closest to the actual work, not just to the people managing it from a distance, because they usually see details you can't. And when someone gives you a real answer, act on it visibly, so people learn that answering you honestly actually changes what happens. Do this consistently, and you'll find people solving problems for you that you never got around to assigning.