Chapter 21: Asking for Something Real

Last week was about giving without an ask attached. This week, you're going to make a legitimate ask when you actually need something, real headcount, real budget, real scope, and you're going to do it without pretending you don't need it.

That distinction matters more than it might seem. A lot of people, once they've internalized "don't be transactional," start avoiding legitimate asks altogether, worried that wanting something makes the whole relationship look fake in hindsight. It doesn't. The two chapters aren't in tension. Last week built trust when nothing was on the line. This week spends some of that trust on something that actually matters, which is exactly what trust is for.

Here's the pattern that usually goes wrong with resourcing asks. Someone needs more budget, or another person on their team, or more time to do something properly. They frame the ask around their own experience of the problem. "I'm stretched too thin." "This would really help my team." "I've been asking for this for months." All of that might be completely true, and none of it is what actually moves a resourcing decision, because the person deciding isn't measured on your comfort. They're measured on something else entirely, and your ask needs to speak that language, not yours.

Frame it around what they're actually measured on

Before you ask for anything, get specific about what the decision-maker is actually accountable for. This connects directly back to the leader-profiling work from chapter eleven. A Metrics Hawk wants the number your ask protects or improves. A Guardian wants to know what risk this prevents. A Visionary wants to know how this connects to where things are headed. Whatever their pattern, your ask needs to be translated into their terms, not yours.

Here's the shift in practice. Instead of, "I need another analyst because my team is overloaded," try, "Without another analyst, we're at risk of missing the Q3 reporting deadline that leadership is tracking, and the gap is specifically in data validation, not analysis itself." Same underlying need. Completely different framing. One is about you. The other is about an organizational outcome the other person already cares about.