How to Ask Your Manager for More Responsibility

Asking for more responsibility is a different conversation from asking for a promotion. It doesn't need a title change, a budget, or a review cycle. It needs a specific scope, a reason you're ready for it, and a manager willing to say yes to something small enough to actually approve on the spot.

The conversation

Read it once before you go in, then use it as a guide rather than a script to read word for word. The order matters more than the exact phrasing - get the structure right and your own words will carry it.

1. Pick the specific scope, not "more" in general

   "I want more responsibility" is hard to act on. "I want to own the migration project end to end" is a decision your manager can actually make.

   • Name a specific project, area, or decision you want ownership of.
   • Have a reason ready for why this particular scope, not just any scope.
   • Think through what you'd need from your manager to actually take it on.

2. Name what you want and why you're ready

   • You: I'd like to take on ownership of the onboarding redesign - I've been supporting similar projects and I think I'm ready to lead one.
   • Them: What makes you feel ready for that specifically?
   • You: I ran point on the last two smaller features end to end, including the rollout.

3. Handle "let's revisit next cycle"

   • Them: Let's think about this for the next planning cycle.
   • You: That's fine - what would need to be true between now and then for this to be a yes?
   • Them: Honestly, seeing you run something at that scope first would help.

4. Offer to prove it on a trial basis

   • You: Could I take on a smaller piece of it now, as a trial, and we revisit the full scope after that?
   • Them: That could work - let's define what that piece looks like.
   • You: I'll put together a proposal for what that trial scope would be.

5. Ask what would need to be true for a yes

   • You: If I deliver that well, is the full scope something we can commit to, or is there something else in the way?
   • Them: If it goes well, I don't see why not.
   • You: Good - let's put a date on when we'll check back in on it.

6. What to avoid saying

   • Don't frame the ask as being bored or under-challenged - it puts your manager on the defensive rather than making the case for you.
   • Don't compare your scope to a specific peer's. It makes the conversation about fairness between two people instead of your own readiness.
   • Don't leave without a specific ask. "I'd like to grow" is a feeling, not a request your manager can act on.

7. After the conversation

   Whatever the answer, the follow-through is what actually moves this forward.

   • Send a short written summary of what was agreed, including any trial scope or date.
   • Start logging the work as evidence from day one - Perform Review's Achievement Log is built for exactly this kind of running record.
   • Calendar the agreed check-in date yourself rather than waiting for it to come up.

That's the whole conversation

Every real version of this conversation goes slightly differently. What is above is the shape that holds regardless of how they react - what to actually say in the moment is still yours to find.