The Myth of the Fast Yes
You've been in the meeting where someone says they need a quick yes on this and the conversation goes nowhere for twenty minutes. You've watched the approver sit there, nodding, saying let me think about it, and the request sits in a queue for three weeks. You've probably blamed the approver. Called them slow. Called them political. Called them a bottleneck. In the operations I've run across industries, the pattern was never the person. It was the request. A quick yes that takes fourteen days to get answered is almost never a fourteen-day approval. It's a fourteen-day clarification. The approver is doing the thinking you should have done before you walked into the room. The myth is that speed lives in the approver's personality, and the reality is that speed lives in the specificity of the ask.
The approver is doing your job
The approver who thinks about it for two weeks isn't stalling. They're reverse-engineering what you didn't say. They're asking themselves what the risk is, what the scope is, what happens if they say yes and this balloons. You handed them a question and expected an answer. They got a problem and started solving it. I've sat on the other side of that table. I've had requests come in that read like approve the thing with no context, no numbers, no fallback. And I've watched the same approver turn around a four-hundred-dollar purchase in four minutes when the requester came in with the vendor name, the delivery date, the budget line, and what happens if it doesn't arrive by Friday. Same person. Same day. Different request.
What actually separates the two
The distinction that matters: a specific request is a decision, and a vague request is a project. When you walk in with the vendor, the quantity, the deadline, the budget, and the penalty for missing it, you are handing someone a yes or a no. When you walk in with I need your approval on the procurement thing, you are handing someone a research assignment. The person who gets the fast yes isn't luckier. They're not friendlier. They did the work of making the decision small enough to be decided. They removed the ambiguity that made it feel big. And that's not a personality trait. That's a choice you make in the twenty minutes before the meeting.
The part nobody talks about
Here's where it gets uncomfortable. Sometimes the request is specific and the answer is still no. And sometimes it's specific and the answer is I need to talk to Finance first, and that's not a delay. That's the system working. The myth of the fast yes isn't just that people are slow. It's that we've built a culture where asking vaguely is polite and asking specifically is aggressive. Where I just need a general sense is the socially safe entry point and here's the exact decision I need by four or we lose the window sounds like a threat. The edge case I keep coming back to: what happens when the specificity is right, the decision is clear, and the approver still can't say yes because the authority to say yes isn't actually theirs? You've done everything right. The request is crisp. The constraint is named. The fallback is set. And the person in the chair still has to go ask someone else. At that point, the problem wasn't the request. It was the org chart. And no amount of specificity fixes a misrouted decision.
