How to ask for more work without sounding desperate

A common early-career moment: you’ve finished everything on your plate, you’re sitting idle, and you’re two minutes from sending the “hey, anything I can help with?” Slack.

Don’t. That message is how you end up reformatting someone’s deck at 4:47 p.m.

Asking for more work is a good instinct. The execution is where people lose.

Why the default Slack doesn’t work

“Anything I can help with?” puts the cognitive load on your manager. They have to stop their actual work, scan their mental list of tasks, find something vaguely juniorable, and type it out. Most won’t bother — they’ll send you whatever’s easiest to describe in a sentence. Usually admin.

You want real scope. That requires you to do the framing.

The three ingredients

Context. Why you’re asking now. (“I wrapped X earlier than planned” — not “I’m bored.”)

Options. Two or three things you’ve already noticed could use help, specific enough that your manager doesn’t have to think hard.

A default. What you’ll do if they say nothing. Makes it safe to decline.

The Slack message

“Hey — I finished [X] earlier than expected and have about 1.5 days of capacity before [next thing] starts. Three things I’ve noticed I could pick up:

1. [Specific thing you saw], which would free up [person / time]. 2. [Another specific thing], which would unblock [something]. 3. [A third, if you have one].

Option 1 is my default unless you’d rather I take 2 or 3. Happy to do something else entirely if there’s something more useful.”

That message does four things at once: shows you’re paying attention to the team’s actual work, makes it trivial for your manager to say yes, gives them an easy way to redirect you, and proves you can run with ambiguity.

Where to find the three options

If you’re stuck on what to propose, walk the team’s docs and Jira channels for 20 minutes and look for:

• A doc or process everyone complains is out of date
• A recurring task your senior does manually that could be templated
• A meeting series with no notetaker
• A ticket on the backlog that’s been there for over a month
• An onboarding gap (you just lived through it — fix one thing)
• A metric nobody’s owning
• A half-finished automation someone started but never wrapped

Almost every team has at least three of those lying around.

Timing

Don’t send this Monday morning. Your manager is drowning.

The sweet spots:

• Mid-week, early afternoon (Tue–Thu, 1–3 p.m.) — they’ve dealt with their inbox, they haven’t hit late-afternoon crunch.
• The day after you ship something visible. “I wrapped X. What’s next?” is a question a manager is mentally ready to answer when X just landed.
• Before your 1:1, not in it. Send the Slack 24 hours ahead so the 1:1 conversation is about which of the options, not whether to take one.

How to make sure you get real scope, not busywork

Two rules.

Never take unscoped work. If your manager says “Can you help with the Q2 launch?” — great. But before you say yes, ask: “Happy to. What’s the specific thing you’d want me to own — a piece end-to-end, or support on a workstream? Who should I coordinate with?” If they can’t answer, the work isn’t ready for you. Offer to come back when it is.

Close the loop hard on whatever you pick up. Visible ship → short update → “what’s next.” That’s how the next ask becomes a bigger piece of work. Managers give scope to people who make small scope look handled.

What not to do

Don’t ask every day. Asking once a week signals capacity. Asking every day signals anxiety.

Don’t volunteer for everyone else’s leftovers. The first couple of times, it builds goodwill. Past that, you become the person who absorbs crap work, and the ceiling of your role gets lower without anyone noticing.

Don’t lead with “I’m bored.” Boredom is your problem, not theirs. Lead with capacity.

Don’t ask a skip-level. Don’t route around your manager for scope. That’s a relationship-damaging move even when well-intentioned.

The harder version: you’re genuinely under-utilized

If you’ve done the structured Slack three or four times over a month and you’re still sitting on two days of capacity a week, that’s a 1:1 conversation, not a Slack message.

“I’ve had extra capacity for the last few weeks and I’ve been picking up smaller things. I want to flag it because I don’t want to be the person who’s coasting without anyone noticing. Is there a larger scope I could be ramping onto? I’d rather stretch than fill.”

Two things can happen. Either your manager gives you a stretch, or they don’t, and the “is this role actually growing” question becomes legitimate. Useful either way.

—

I’ve watched first-years with extra capacity do every variation of the wrong thing — sit silent and read Twitter, panic-DM their manager hourly, volunteer for everyone’s worst tickets — and the correct move is honestly the simplest one: walk the team’s docs once, write down three things, send the Slack. The whole exercise takes thirty minutes and saves you from a week of being the new grad nobody trusts with anything good.

For the status rhythm that turns every piece of pickup work into visible progress, use the Status update template. For the meeting where this ask lands best, see the Manager 1:1 agenda.