Ownership Isn't Something You Hand Out
Jonathan Raymond5 min read
You've probably done this. You give someone a project. You explain what needs to happen, how you'd approach it, and when you need it done. You tell them it's theirs now. You mean it.
Two weeks later, they're back in your office asking what to do next. Or the project has stalled, and when you ask why, the answer is some version of "I wasn't sure how you wanted it."
And you think: why won't anyone on this team just own something?
Here's a version I hear all the time. The CEO of a 250-person distribution company asks her director of operations to fix their order fulfillment process, which has been causing late shipments for months. She walks him through the problem, tells him which system she thinks they should switch to, and sketches out how she'd reorganize the warehouse teams. Then she tells him it's his project.
Three weeks later, he's in her office asking which supervisors should run which shifts. She's frustrated. She handed him the job. What she didn't realize was that she'd kept all the thinking.
I asked myself the same question she did for a long time. I blamed hiring. I blamed motivation. I even blamed the generation.
It took me an embarrassingly long time to look at what I was actually doing in those handoff conversations. I was the one doing all the thinking. And thinking is where ownership lives.
You can delegate a task. You can't delegate ownership.
A task is something you can hand over. Here's what needs doing, here's the deadline, go.
Ownership is different. It's the feeling that this is mine: my decision, my call, my result. And nobody gets that feeling from being told what to do, no matter how clearly you say "this is yours now."
Think about it from their side. If you walk in with the plan already figured out, what's left for them? They can execute your plan. They can check with you when something doesn't fit your plan. But it's still your plan. When it goes sideways, it's your problem to solve, because it was your idea in the first place.
If you walk in with the answer, they walk out with your answer. And it stays yours.
That's not a character flaw on their part. It's a completely rational response. Why would anyone take ownership of something they had no hand in shaping?
Leave room in the conversation
People take ownership when the conversation leaves room for them to. That's the whole trick. And it's harder than it sounds, because most of us got promoted for having answers.
Leaving room means walking into the conversation with questions instead of a plan. It means being willing to sit through a few seconds of silence while someone thinks. It means letting them land on an approach that's a little different from the one you'd pick, as long as it gets the job done.
That last part is the hardest. You'll watch someone choose a path you know is slower, or clunkier, or just not how you'd do it. Every instinct will tell you to step in and fix it.
Ask yourself one question first: is this wrong, or just different? If it's genuinely going to cause a problem, say so. If it's just not your way, let it go. The small cost of a less-than-perfect approach is nothing compared to the cost of a team that never thinks for itself.
You still set the direction. You still say what success looks like and what can't be compromised. But the how? That's where you leave room.
What leaving room sounds like
Here's the difference in practice.
Handing off a project: Instead of "Here's the plan. Call the supplier, get three quotes, and have it to me by Friday," try "We need a new supplier for this by end of month. What do you think the right approach is?"
When someone brings you a problem: Instead of "Okay, here's what you do," try "What have you thought about so far? What would you do if I weren't around?"
When their plan isn't how you'd do it: Instead of "I'd do it differently. Let's go with my way," try "Walk me through why you landed there." (And then, more often than not, let them run with it.)
When it's done: Instead of "Thanks, I'll take it from here," try "How do you think it went? What would you change next time?"
Notice what all of these have in common. They put the thinking back where it belongs, with the person doing the work. And once someone has done the thinking, the result really is theirs.
Building a team that thinks for itself
Asking instead of telling sounds simple. In practice, it goes against years of habit. When you're busy and you already know the answer, giving it is just faster.
That's part of why we built Ren. Ren is an AI agent that takes the overhead out of leading people, so your leaders can focus on what matters most. Before a handoff or a one-on-one, a manager can talk it through with Ren: what outcome they need, what questions to ask, and where to step back and let the other person lead. And it works the other way too. Anyone on the team can use Ren to think through their own approach before they bring it to the boss, so they show up with ideas instead of questions.
But you can start without any of that. Pick one conversation this week where you'd normally hand someone the answer. Ask a question instead. Then wait.
It'll feel slower at first. It is slower at first. But a few months from now, you'll notice fewer things boomeranging back to your desk, and a team that doesn't need you to have every answer. That's what ownership looks like. It's not something you hand out. It's something you make room for.
Is there a conversation you’ve been putting off?
Ren helps you find the first sentence. Try it free, with 100 Ren credits.