Every project needs one name next to it


A project that belongs to “the team” usually belongs to nobody: the more people who could act, the less likely each one is to do it. One accountable name per project fixes most of this, but only if that person also has the right to decide. Here’s what that looks like in a small team.
Shared ownership sounds like good teamwork. Three people care about the project, everyone chips in, nobody plays the boss.
In practice it looks like this. Each of the three assumes one of the others is chasing the open questions. Decisions wait for the next meeting where everyone is in the room. When the project runs late, nobody is surprised, and nobody thinks it was their job to notice. Shared ownership mostly means nobody decides.
Psychologists have a name for this: diffusion of responsibility [1]. In a classic experiment, participants heard someone over an intercom who seemed to be having a seizure. 85% went to help when they thought they were the only one listening. With one other listener, 62% did. With four others, 31%. Same emergency, same kind of people. The only thing that changed was how many others could have stepped in.
A second effect is about effort. Agricultural engineer Maximilien Ringelmann found that people pulling a rope together each pulled less hard than when they pulled alone, and that effort per person kept dropping as the group grew [3]. Later studies put one real participant in a group of actors who only pretended to pull, and the real participant still pulled less hard. People put in less effort when nobody can see their part.
The fixes the research points to are practical ones: make each person's contribution visible, keep groups small, and set clear goals.
Shared ownership mostly means nobody decides.
Project management has had an answer to this for a long time. In a RACI chart (short for responsible, accountable, consulted and informed), many people can be responsible for doing the work, but there should be only one person accountable for each task or deliverable [2].
The owner isn't the person who does all the work. The owner makes sure decisions get made, chases the open questions, says when it's done and is the person everyone else goes to with questions. Other people still build, review and advise.
For that to work, the owner needs three things: the right to decide within agreed limits, a clear list of who they should consult, and a date.
These are the most common mistakes when a project gets one owner:
Co-owners. Two names on a project behave like no name. Each waits for the other, or both decide different things.
The most senior person owns everything by default. In small companies this is often the founder, and then every project waits for their decision.
Ownership without authority. The name is on the project, but every real decision still goes up to someone else.
Owning an area with no end point. "Owns the frontend" never ends. "Owns the new sign-up flow, live by the end of the month" does.
Two names on a project behave like no name.
None of this needs a new tool or a process document. Five steps are enough:
Put one name on every project. In the place where the team tracks work, where everyone can see it.
Write one sentence on what "done" means. If the owner and the team describe it differently, agree on that first.
Hold a short kickoff. Who's involved, what has to be decided first, what could block it. Thirty minutes is usually enough.
Set dated milestones. Two or three points where you’ll know whether it’s on track are enough.
Let the owner close it. The owner says when it’s done, and says it out loud, so everyone knows the people on it are free for the next project.
Go through your current projects and write the owner’s name next to each one. If you can’t think of a name, or you end up writing two, that project needs an owner first.
Sources
Wikipedia (n.d.). Diffusion of responsibility
Wikipedia (n.d.). Responsibility assignment matrix
Wikipedia (n.d.). Ringelmann effect

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