I’ve been thinking a lot lately about how we hand things over as leaders, and honestly, I think one of our most well-meaning habits is quietly holding people back.
When someone takes on something new, our instinct is to announce it. A nice post, under our own name, letting everyone know who owns what now and where to send questions. It feels supportive, and it comes from a good place. The reality is, though, that the message people actually hear is “the manager decided this”. The authority is still sitting with us. We’ve just lent a bit of it out.
Tasks vs authority
This is the distinction I keep coming back to.
Handing over a task means someone else does the work. That’s useful, and it’s the part most of us are pretty good at.
Handing over authority is different. It’s the right to decide what the work actually is: what’s in, what’s out, what changes and who people should go to. And the thing about authority is that it only really exists when other people see it and recognise it.
So when I spell out someone’s new responsibilities for them, I’m still the one defining it. They’ve got the work, but I’ve kept the authority, and it can take months for everyone, them included, to figure that out.
A slightly rough post in their own voice builds far more credibility than a polished one in mine.
Why letting them say it works
The alternative is simple, even if it doesn’t always feel comfortable. The person taking ownership writes up their own new role and shares it themselves, under their own name. My job is to back it, visibly, underneath.
I love how many things this changes at once.
People see them as the owner, because they’re the one speaking for it. In a remote, async team, the first written version of something tends to become the version, so whoever writes it really does own the story.
Questions go to the right person from day one. When I write the post, the replies come to me, because I look like the person who knows. When they write it, people go straight to them, and there’s no habit of checking with the manager to unlearn later.
It builds their confidence too. Putting your role into your own words means committing to it: drawing the edges, saying what you’ll change and asking for what you need. Once it’s out there, they have something real to stand behind, and accountability starts with their words, not mine.
And my role changes in a really helpful way. I stop being the spokesperson and become the backer. A short “fully behind this” under their post says I trust them far more than any announcement I could write.
What it costs me
I’ll be honest, this isn’t always easy.
I give up some control. It won’t be worded exactly the way I’d word it, and the scope might be a little narrower or bolder than I’d have chosen.
I give up some polish. Mine might be tighter. Theirs might be longer, more careful or a bit rough around the edges.
And I give up some speed. Asking someone to write and share what they now own takes longer than dashing off a post myself, especially the first time.
I can happily say it’s worth it. A slightly rough post in their own voice builds far more credibility than a polished one in mine. The time it takes up front saves a lot of questions drifting back up to me later.
What I try to keep in mind
Let them speak first. Whoever owns the area shares it first. My voice comes second, as support, not as the introduction.
Fix things privately, back them publicly. If something important is missing, I tell them directly and let them update it. Correcting them in the comments would take back the very thing I’ve just handed over.
Point people back to them. Questions will still find their way to me, and that’s ok. I send them on to the owner, even when I know the answer, because every one I answer quietly tells people I’m still in charge.
None of this needs a new process. It just needs us to be comfortable being the second voice instead of the first.
So next time someone on your team takes something on, hand them the mic, not just the work!


