The most common advice for getting the project or the promotion you want fits on a sticky note. Advocate for yourself. Be confident. Speak up. It sounds like a plan right up until you’re sitting across from your manager and realize nobody ever told you the actual sentence to say.
Confidence isn’t the thing standing between you and the ask. The words are. Most people don’t stall because they doubt they’ve earned it. They stall because they’re improvising a high-stakes conversation in real time with no draft, and the draft is the whole game.
So this guide skips the pep talk. You get three scripts you can adapt and say out loud: one for the stretch project, one for the promotion case, and one for claiming the visible assignment before it goes to someone else. First, though, this ask lands harder on some people than others, and the reason isn’t a confidence gap you can pep-talk your way out of. That’s what this is about: how to ask for what you want at work in the specific moments that decide it. If moving work forward without a title is most of your week, the individual contributor playbook is the wider context. This is the asking chapter.
Why asking for what you want at work is harder than it should be
The ask lands harder on some people because two structural patterns are working against them before they open their mouth. Neither one has anything to do with how brave or how deserving they are.
The first is office housework. Linda Babcock and her co-authors gave it a sharper name: non-promotable tasks. These are the jobs that keep an organization running but almost never show up in a promotion case. Taking the notes. Organizing the offsite. Onboarding the new hire. Sitting on the committee nobody volunteers for. Someone has to do them, and the research Babcock’s team published in the American Economic Review found the asks aren’t handed out evenly. Women are more likely to be asked to take these tasks on, more likely to say yes when asked, and more likely to end up with a week full of work that keeps them busy and invisible at the same time. Babcock’s team laid the same finding out for a general audience in Harvard Business Review.
Stack that up over a year and you get a quiet trap. You’re the reliable one, always contributing, never quite building the visible track record a promotion actually runs on. So when you finally ask for the stretch project, there’s no obvious block of promotable work with your name on it, because your calendar has been full of the other kind.
The second pattern is the gap between mentorship and sponsorship. A mentor talks to you. A sponsor talks about you, in the meetings where headcount and promotions and the good assignments get decided, the rooms you never sit in. Herminia Ibarra, Nancy Carter, and Christine Silva found that women tend to be over-mentored and under-sponsored: long on advice, short on someone willing to spend their own credibility to move them up. As Sylvia Ann Hewlett has argued, it’s sponsorship, not mentorship, that actually pushes a career forward.
This is where it hits your ask. If nobody is advocating for you when you’re out of the room, the conversation you have with your manager carries more weight, because it might be the only advocacy happening at all. That raises the stakes, and it’s exactly why the vague advice fails. “Be confident” does nothing about a workload stuffed with non-promotable tasks or a sponsor who isn’t there. What helps is seeing the structure you’re operating inside, then walking in with words precise enough to do some of the job a sponsor would otherwise do for you.
Script 1: asking for the stretch project
The most reliable way to ask for a stretch project is to frame it around a problem the business already has rather than around your own growth. Managers approve work that solves something they’re worried about. Your development is a nice side effect. The problem is the pitch.
Try this, adjusted to your situation:
“I’ve been watching [specific problem] slip, and I think I can own it. I’d like to take the lead on [project]. I’ve already sketched how I’d approach the first thirty days, and I can bring a full plan to our next one-on-one. Can I run it by you?”
Three things are doing the work there. You’ve tied the ask to a real problem, so it reads as help. You’ve named the specific thing you want instead of hinting around it. And you’ve offered a concrete next step, which makes it easy to say yes to a small commitment now.
If your plate is already full, say what you’ll hand off. “To do this properly I’d want to pass the onboarding rotation to someone else for a quarter.” That signals you take the stretch seriously, and it quietly moves a non-promotable task off your desk in the same breath.
Sometimes the project needs a yes from someone who isn’t your manager. When you’re winning over a peer or a partner team with no power to assign them anything, the levers are different, and influence without authority walks through the ones that work.
When your manager says “let me think about it”
A “let me think about it” is an unfinished conversation. The mistake is to treat it as a soft no, say “sure, no rush,” and walk out, because then it can drift forever. Pin the next step before you leave the room instead:
“Makes sense. Can I send you the thirty-day plan by Friday so you’ve got something concrete to react to? And would early next week work to give me a yes or no?”
You’ve just turned a vague maybe into a scheduled decision with a deadline attached. That single move closes more stretch-project asks than any amount of confidence does.
Script 2: making the promotion case
A promotion conversation is won on evidence. Enthusiasm on its own won’t carry it. The strongest version sounds less like a request and more like a summary of a decision your work has already made obvious: you’ve been doing the job at the next level for a while, and now you’re asking your manager to make it official.
Open with the ask, then move straight to proof:
“I’d like to make the case for moving to [title]. For the last [timeframe] I’ve been operating at that level, and I’ve pulled the specifics together. Can we set aside time to go through them and agree on what a yes would need?”
A promotion case is a negotiation, and like any negotiation it goes better when you walk in prepared than when you hope to improvise.
What to bring into the room:
- Two or three examples of work you already did at the next level, each tied to a business outcome: revenue moved, hours saved, a risk headed off, a launch that shipped.
- The scope you own now versus when you started, in plain numbers (headcount influenced, budget touched, systems owned).
- Something a peer or a partner team said about your work that you can quote, so the advocacy in the room isn’t coming only from you.
- A concrete timeline, so the decision can’t quietly drift.
That third item matters more than it looks. If you have no sponsor speaking for you elsewhere, quoting a partner team’s feedback imports an outside voice into the room and does a piece of what a sponsor would. You’re borrowing advocacy you don’t structurally have.
The timeline matters too. “I’d like to aim for a decision by the next review cycle in [month]” gives both of you a date to work against, which beats an open-ended “someday” that resets every quarter.
One trap to sidestep: a bare list of activities reads like a job description and invites a shrug. Attach an outcome to each one. “I did X, which cut Y by a third” reads like impact, and impact is what a level change is supposed to reward.
Script 3: claiming the visible, high-stakes assignment
The fastest way to change what your promotion case looks like next year is to claim promotable work now, before the visible assignment gets handed to someone else and the office housework drifts back to you by default. The moment a high-stakes project gets announced is the moment to speak up, well before the roles get quietly assigned.
Raise your hand in the room:
“I’d like to take the client presentation. It’s exactly the kind of high-visibility work I’m trying to do more of, and I’m ready for it. Can I own it?”
Or set it up in advance with your manager:
“When [big project] kicks off, I want to be considered to lead a workstream. Keep me in mind, and tell me now if there’s a gap I should close first.”
Saying out loud that you want the visible work does two useful things at once. It puts you on the shortlist, and it makes it a little harder for the promotable work to default to whoever always gets it. Reputations form fast. If you only ever say yes to the notes and the onboarding, that becomes the thing you’re known for, and it’s a hard reputation to outrun once it sets.
There’s an honest limit here. You can’t grab every shiny assignment, and the colleague who hoards visible work while dodging all the glue work becomes the one nobody wants to staff. You don’t have to stop doing the invisible tasks. You do have to make sure they aren’t the only thing on your plate. Start declining a few of them so you have room for the one assignment that counts, and treat claiming that work as part of building a reputation as a leader before anyone hands you the title. That fuller idea is worth its own read: leadership without a title.
Handling the “not yet” (or a flat no) without losing ground
A “not yet” is only useful if you leave the room knowing exactly what would turn it into a yes. Most people accept the soft no, say thanks, and walk out with nothing to act on. That wastes the whole conversation.
When you hear “not yet,” ask for the specifics before you leave:
“I appreciate the straight answer. Can you tell me the two or three specific things that would need to be true for this to be a yes? I want to work on the right things instead of guessing.”
Then lock the follow-up on the spot:
“Let’s put a check-in on the calendar for six weeks out to see where I’ve landed against those. Does that work for you?”
You’ve just converted a vague no into a definition of done and a date. Now you have a plan and a deadline to work toward, which beats walking out stung with nothing to do. When the check-in comes and you’ve hit the marks, the next conversation starts from a different place.
Sometimes it’s a real no, and the skill is reading which kind. A timing no (“not this cycle”) means revisit with new context later. A no that isn’t your manager’s to give means you ask who does own the decision. A no about a genuine gap means you get the gap named precisely so you can close it. A clean question sorts them: “Is this a not-right-now, or a not-with-your-current-scope? Either way, I’d like to know what to do next.”
Whatever kind it is, don’t argue it in the moment. Restate what you heard, get the follow-up date, and leave clean, because arguing a no in real time is how one decision hardens into a reputation. If the real blocker is that nobody’s advocating for you upstairs, the most useful thing you can ask is simple: “Who else should know I’m interested in this?” You’re asking your manager to sponsor you, or to point you to someone who will.
Rehearse the ask before it counts
The distance between knowing the script and actually saying it well is closed by reps, not by reading it one more time. The words look easy on the page. Under real pressure, with your manager glancing at the clock, most people default to hedging, over-explaining, or shrinking the ask until it’s small enough to feel safe and forgettable.
That’s the part rehearsal fixes. Merlin, our AI coach, lives natively in Slack and Microsoft Teams, so you can run the promotion case out loud before the real meeting. Hand Merlin a weak, apologetic version of your ask and get honest pushback on it. Tighten the wording until it sounds like you at your most direct. You can even practice the part everyone skips, holding your ground on a “not yet” without folding into “no worries, forget I asked.”
Pick the conversation you’ve been putting off. Draft the ask, then rehearse it with Merlin until the words come out clean. The script only works if you can say it when it counts.