What to Delegate (And What You Should Never Let Go Of)

Avery Quinn on Delegation, Control, and Creative Ownership

 

Avery didn’t rush into delegation.

That had been the advice from the beginning.

“Just hire.”

“Just trust your team.”

“Just get out of the way.”

Simple.

Too simple.

Because Avery had already tried that.

And something didn’t sit right.

Not because the team wasn’t capable.

They were.

The work still moved.

Deadlines were met.

Clients were satisfied.

But something inside the work—

felt thinner than it used to.

Harder to recognize.

“I thought this would feel like relief,” Avery said quietly, closing a project review.

A pause.

“…but it feels like I’m losing something.”

The Assumption Behind Delegation

Delegation is usually framed as a release.

Less work.

Less pressure.

More space.

And on the surface—

that’s true.

But there’s something underneath it that rarely gets addressed.

Delegation doesn’t just remove responsibility.

It redistributes authorship.

That’s the part Avery hadn’t fully seen yet.

Because when you hand something off—

you’re not just transferring execution.

You’re transferring influence.

And if you don’t define where that influence should stay—

it disappears faster than you expect.

The First Adjustment: Stop Delegating by Task

At first, Avery tried to organize delegation the obvious way.

Tasks.

What can I hand off?

What can someone else do faster?

What doesn’t need me?

It made sense.

And it didn’t work.

Because tasks don’t define the work.

They just move it forward.

A project could be perfectly delegated at the task level—

and still drift at the outcome level.

That’s what Avery kept running into.

“Everything’s getting done,” Avery said during one review.

A pause.

“…but it’s not landing the way it should.”

That was the moment the shift started.

The Second Adjustment: See the Work Differently

Instead of asking what to delegate—

Avery started looking at the work itself.

Not as a checklist.

But as something that took shape over time.

There were points where everything was still flexible.

And there were points where the direction became fixed.

Where the work either held—

or drifted.

Once that became visible—

it changed everything.

Because not all parts of a project carried the same weight.

Some moments could move freely.

Others couldn’t.

The Third Adjustment: Stay Close at the Beginning

Avery started experimenting.

Instead of stepping back early—

they stayed closer at the start.

Not to manage.

To shape.

Early conversations became more intentional.

Less about gathering requirements—

more about defining perspective.

“What are we actually trying to say here?” Avery would ask.

Not just what the client wanted—

but what the work needed to become.

These weren’t longer meetings.

They were sharper ones.

More focused.

And something shifted because of it.

Projects that used to drift—

started aligning earlier.

Fewer corrections later.

Less rework.

“I’m not fixing things at the end anymore,” Avery noticed.

A pause.

“I’m setting them up properly at the beginning.”

The Fourth Adjustment: Make the Standard Visible

There was another gap Avery hadn’t seen before.

The team wasn’t missing skill.

They were missing clarity.

Not about what to do—

but about what good actually meant.

So Avery started doing something subtle—

but different.

Instead of reviewing work only after it was done—

they began defining the standard before it started.

Not in documents.

In conversation.

“This needs to feel intentional,” Avery would say.

“Not just clean—clear.”

Or:

“If we stripped everything back—would this still hold?”

At first, it felt vague.

But over time—

it created alignment.

Because the team wasn’t just executing tasks anymore.

They were working toward something shared.

The Fifth Adjustment: Step Out Earlier

This was the hardest part.

Knowing when to leave.

Because once the direction was clear—

once the standard was set—

once the intent was understood—

Avery had to step back.

Earlier than instinct suggested.

“Are you sure you don’t want to review this round?” someone asked.

Avery paused.

Then shook their head.

“No. It’s already where it needs to be.”

That wasn’t about trust alone.

It was about structure.

Because once the foundation was strong—

staying longer didn’t improve the work.

It diluted ownership.

And slowed momentum.

What Actually Stayed

Avery didn’t hold onto everything.

Just the parts that defined the work:

The framing of the problem.

The direction of the idea.

The standard it needed to meet.

And the final decision—

that determined whether it held.

Everything else—

moved.

What Actually Changed

The workload didn’t disappear.

But the pressure shifted.

Fewer late-stage fixes.

Less second-guessing.

More alignment—

before the work even began.

Because instead of reacting to problems—

Avery was shaping where problems could exist.

And where they couldn’t.

The Line That Becomes Clear

There’s a point where delegation stops being about capacity—

and becomes about identity.

What stays with you—

defines the work.

What you release—

defines how the work moves.

Both matter.

But they are not interchangeable.

If You’re in This Phase

There’s a moment where you realize:

You can’t stay inside everything.

But you also can’t step away from everything.

That tension doesn’t go away.

But it becomes clearer.

Not everything requires you.

But some things always will.

And the more precisely you define that line—

the easier everything else becomes.

Because once you know:

Where you must be present—

and where you don’t need to be—

delegation stops feeling like a risk.

And starts feeling like design.