How do you give a junior real ownership?


Not by handing over a project and waiting. When that happens, the project often stops moving or the manager takes it back. Ownership is learned in steps, and full delegation is the last one.
Small teams can't hire many senior people, so juniors get real responsibility early. That's often a good thing. The plan usually sounds like this: give them ownership, and they'll grow into it.
What tends to happen is different. The junior waits for permission they don't know they have. Or they guess, get corrected, and guess less next time. They don't ask many questions, because asking feels like admitting they can't cope. After a few weeks the manager decides they're "not ready" and takes the project back. Both sides conclude that ownership didn't work.
The problem is that it was handed over with nothing around it.
Situational leadership, a model from management research, describes four ways to lead: telling, coaching, supporting and delegating [4]. The right one depends on how ready a person is for a specific task. Someone can be experienced in general and still be a beginner at the thing you just gave them.
The point for juniors is that full delegation comes last. Before that comes telling, coaching and supporting, and a junior often needs all three when a task is new to them.
Someone can be experienced in general and still be a beginner at the thing you just gave them.
David Marquet, a former submarine commander, built his approach to leadership around one change in language [2]. Instead of asking for permission, people say what they intend to do: “I intend to ship this on Thursday.” The difference, in his words, is that “with intent, the default is action absent a veto whereas with permission the default is stasis absent approval”.
That gives you a ladder you can make explicit. For small, reversible decisions: "Do it and tell me after." For bigger ones: "Tell me what you intend to do, and go ahead unless I object by tomorrow." For the few that really matter: "Bring me two options and what you'd pick." Write down which level applies to each kind of decision, and give the person more freedom on a kind of decision once they’ve handled it well a few times.
None of this works if the junior hides problems until they’re too big to hide. Amy Edmondson’s research on psychological safety describes the belief that you can take interpersonal risks, like asking a basic question or admitting a mistake, without being shamed for it [3]. It’s one of the most studied conditions in research on how teams learn.
Juniors watch how their manager reacts to bad news. If a junior gets a sigh the first time they say they’re stuck, they’ll wait much longer before they say it again. One large analysis of more than 11,000 work teams estimated that at least 70% of the difference in engagement between teams comes down to the manager [1]. Engagement here means how involved and committed people are in their work. In other words, whether a team cares about its work depends a lot on who manages it.
If a junior gets a sigh the first time they say they’re stuck, they’ll wait much longer before they say it again.
This is what I’d put in place before handing a project to a junior:
Explain why the work matters. Who the work is for, what problem it solves and what good looks like. People can only make decisions if they know what the decisions are for.
Agree which decisions are theirs. Use the ladder: what they decide alone, what they announce, what they bring to you.
Check in often at first, then less. A short weekly conversation in the first month, every two weeks after that, then only when they ask.
Talk through the decisions behind the work. When a piece of work is done, ask which options they looked at, why they picked the one they did, and what they’d change next time. That’s how they learn to make the next decision without you.
Let them present their own work. If the manager always explains the project to others, everyone, including the junior, assumes it’s still the manager’s project.
Say when you'll step back. "After this release, the next one is yours from start to finish." A date makes the handover real.
Done this way, ownership takes a few months to build. It also tends to last.
Sources
Gallup (n.d.). Why Great Managers Are So Rare
Marquet, D. (n.d.). What is Intent-Based Leadership?
Wikipedia (n.d.). Psychological safety
Wikipedia (n.d.). Situational leadership theory

Edita Dermontaité
Hands-on CPO and product leader who still builds (with AI)
I’ve often been the first: the first product hire at Leadcamp and Bizzy, where I led product as CPO for five years, and the first user researcher at Lighthouse, where I spent two years building the research function.
For the past year I’ve worked as a fractional CPO and hands-on product leader, helping B2B SaaS teams between traction and scale connect what engineering builds to what brings in revenue.
I started out as a graphic designer, so I still design and test things myself, these days mostly with AI: in Claude and Lovable, or straight in code with Cursor.
Book a free 30-minute call, or a coffee in Ghent. We’ll look at what’s slowing your product down and what to do about it. I work with teams fractionally or hands-on as an embedded product leader, 2–5 days a week, depending on your needs and my availability.
Product leadership for B2B SaaS between traction and scale, from a hands-on CPO and product leader who still builds (with AI). I take product decisions off the founder’s shoulders and get product, engineering and sales moving in one direction: revenue.

New North BV
BE 1025.547.940
9050 Ghent
Belgium