You’re micromanaging. And you hate it. Don’t beat yourself up. Set yourself up for success.

Perhaps you have found yourself reviewing minor communications and attending unnecessary meetings. Or jumping in and completing project work because you think that you can do it faster, and with fewer errors.

I can relate. I remember staying in the office late on a Friday evening to complete an assignment for a team member, so that she could leave early for vacation. I was pretty proud of myself. I was a cool and supportive project manager. Then our director walked by. He asked why I was in the office so late. I told him and then waited for him to tell me that I was amazing. Instead, he called me an idiot, and as he walked away, he said, “Will you do my work for me too?” Ouch. He was right. I was failing at delegation and team member accountability. I wish I had known better from the start, and I wish that I had known about these three frameworks:

Framework One: Assign Outcomes, Not Tasks

Stop telling people how to do something. Tell them what needs to exist when they’re done and why it matters.

Instead of this: “Create a risk register using this template, with high/medium/low ratings, owner assignments, and deliver by Friday.”

Try this: “We need the steering committee to understand what could derail us and feel confident we’re managing those risks. You have complete freedom on format—give me what you think will actually get them engaged.”

Caveat: If your organization has a standardized risk register, then of course, make this clear.

This tiny shift signals: “Your judgment matters. Your expertise matters. I trust you.” It unleashes creativity and accountability simultaneously. Your team member becomes the expert on execution; you provide context and outcomes.

Framework Two: Define Success Before Work Starts

The most toxic phrase in delegation is “I’ll know it when I see it.” Your team member delivers something that doesn’t match unstated expectations you never articulated.

I once worked for a manager who asked me to create a spreadsheet of some specific data. He did not give me any guidance. I created the spreadsheet, and then he started making corrections. Out of frustration, I said to him, “Why didn’t you just tell me what you wanted from the beginning?” His reply, “Oh. I needed to see something in order to figure out what I wanted.”

If I had known I was creating a prototype, I would not have spent so much time on it.

A better approach is to have a clear conversation about success before your team member starts the work. Create specific measurable success criteria together. Discuss the work and the outcome. This allows your team member to work independently, while keeping the success criteria in mind.

Framework Three: Checkpoints That Feel Like Partnership

Create checkpoints that are supportive, not surveillance. Consider this structure for your checkpoints:

1. Acknowledge progress (be specific)
2. Understand where they stand
3. Identify obstacles they’re hitting
4. Problem-solve together
5. Clarify next steps and reconnection timing

Your checkpoint is not about looking for errors; it is about ensuring your team member has what is needed to meet your established success criteria.

This is a collaboration.

For work that is a shorter duration, you might have one checkpoint at completion. For longer assignments, consider weekly or biweekly checkpoints.

You also want your team member to be able to request a checkpoint anytime they feel stuck or uncertain.

Imagine if I had:

1. Given my team member the desired outcome of completing some specific work before she left for vacation.
2. Agreed upon what it meant to complete that work.
3. Held a checkpoint as she prepared to complete the work, and definitely before she left for vacation.

Then maybe my director would have had a higher opinion of me. Nobody wants to be the office idiot.

Try these three frameworks and experience freedom from delegation distress!

Margaret Meloni

pmStudent

5318 East Second Street #413, Long Beach, CA 90803
​Unsubscribe · Preferences​