How to Make a Big Ask of Your Boss and Actually Get a Yes

Your boss wants to say yes more than you think. That's the core finding of a new management column by organizational psychologist Art Markman, who argues that most employees dramatically overestimate the risk of making a significant request of their supervisor. Good bosses, he writes, see supporting their direct reports as an implicit part of the job description — not as an imposition.

The column completes a trilogy of workplace-advice pieces on making big requests, following earlier installments on asking colleagues and on how bosses should approach requests from their own direct reports. This week's lesson flips the perspective: what should you do when the resource you need sits in your manager's hands?

Why you're more worried than you should be

Markman makes two calming points before getting to tactics. First, taking care of the team is a core — if often unstated — supervisory duty. If your request is reasonable, your boss is inclined to grant it.

Second, perspective matters. "Your boss is likely to be asked to do things all the time from people across the organization," Markman writes. "Another request isn't going to be as big a deal to them as it is to you." Even when the answer is no, he adds, managers are unlikely to resent you simply for asking.

What does the cost-benefit analysis involve?

Every request you make of your boss draws on a resource at their disposal. Markman breaks those resources into four categories:

• Time — the hours your manager spends on your issue instead of something else
• Political capital — their willingness to back something you want to see done
• Finances — budget dollars directed to your project
• Human resources — other people assigned to help you

Every one of those carries a cost, and it's usually an opportunity cost: whatever goes to your request can't go anywhere else. The benefit side can accrue to you directly (a job reference, a spot on a project), to the team, or to the organization's future.

Markman's advice is to map both sides before you knock on the door. "You don't want to put in the request until you're fairly certain you understand what would be entailed for your boss to agree," he writes. That may mean asking around first — would fulfilling your request require financial support, or other people's time?

The endgame is arithmetic. "You want to shift the cost-benefit calculation in your favor as much as possible," Markman writes. Anything that lowers the cost or widens the benefit improves your odds.

How do you lower the costs?

The cost list isn't fixed. Markman recommends engineering it down deliberately.

His example: if you want a recommendation letter, hand your boss everything they need without making them hunt for it. In some cases, that means drafting the letter yourself. More often, it means supplying a list of key points to include, plus full context on the purpose of the recommendation.

The more sophisticated tool is tiering. Markman suggests building three versions of your ask — "Silver," "Gold," and "Platinum." Silver is the bare-bones option: minimum cost, smallest benefit. Platinum is the full package with the highest cost and biggest payoff. Gold sits in the middle.

He cites three advantages to this framing:

1. Your boss sees you've priced out the full range of costs, which signals preparation.
2. It gives your manager a template for modifying your request — they can see which elements are "nice to have" and which are "need to have."
3. Decision-makers gravitate toward compromise. Citing published research on the appeal of the middle option, Markman notes that offering a middle way "often gives them a reason to select one of your options."

Whose problem are you actually solving?

The benefit side of the ledger usually gets framed wrong. Employees naturally list benefits from their own perspective — the problem they're trying to solve, the outcome they want.

That's a mistake, Markman argues. Managers field a steady stream of requests, and they part with valuable resources only when the outcome holds some worth to them. The cost-benefit analysis, he says, should be run from the boss's perspective: what problem of theirs does your request actually solve?

"The best way to get what you want is to help your boss see that supporting your request helps them accomplish something that matters to them," Markman writes.

That doesn't mean hiding your own motives. It means doing the work to understand the broader organizational context behind your ask — which, he notes, doubles as career development. Taking an organizational perspective when planning is a critical skill for future leaders, so every well-framed request is also rehearsal for a management role of your own.

The takeaway for anyone gearing up for a difficult conversation: don't walk in with a wish. Walk in with a priced menu of options, each one cheaper for your boss and more useful to them than you assumed.