Clarifying responsibilities in a growing company
Fuzziness costs more than complexity. And it can be fixed easily.
In a growing company, blurred responsibilities cost more than complexity itself. When every important topic lacks a clearly identified owner, decisions drag, efforts get duplicated, and tension settles at the borders between teams. The good news is that this fuzziness is one of the simplest problems to fix, provided you tackle it at the right level.
Clarifying responsibilities isn't about producing a more detailed org chart. It's about answering, topic by topic, a question that growth makes unavoidable: who carries this decision, and who contributes without carrying it? This page goes deeper into one of the five pillars sketched out in Structuring your company to stay agile.
Why blurred responsibilities cost so much
When a company is small, the absence of formal responsibilities isn't a problem, because everyone sees everyone else's work and adjustments happen on the fly. A topic with no designated owner naturally finds someone to take care of it. This self-regulation has a limit: it assumes each person keeps a wide enough view of the whole to fill the gaps.
The moment that view is lost, fuzziness becomes costly. A topic with no owner stops moving, or moves in fits and starts, because no one feels entitled to decide. Conversely, a topic that several people believe they own generates duplication and turf conflicts. In both cases, the organization spends energy not on doing the work, but on figuring out who should be doing it. That is exactly the kind of cost that clarity makes disappear. This fuzziness is more widespread than people think: Gallup finds that fewer than half of employees clearly know what is expected of them at work, which gives a sense of how much ground clarity has to win back.
One ultimate owner per topic
The most structuring principle is also the simplest: every important topic must have a single ultimate owner. Not the person who does all the work, but the one who answers for progress and decides when a decision is needed. This idea lines up with what the OKR vocabulary calls accountability and single-threaded ownership: a clear thread of responsibility that doesn't dissolve into the collective.
Singleness matters as much as responsibility. A responsibility shared among several people with no clear hierarchy often amounts to a responsibility no one truly exercises, because each assumes the other has it. Naming an ultimate owner takes nothing away from the contributors; it simply provides a point of decision and a single point of contact, which speeds up everything else.
Evolving scopes, not just titles
A difficulty specific to growth is that responsibilities age. A role that made sense at twelve people can become too broad, too central, or too vague at forty-five, simply because the context has changed. The person has done nothing wrong; it's the scope that failed to keep pace with the business.
Clarifying responsibilities therefore means revisiting the actual scopes on a regular basis, not just the job titles. The real question isn't "what is this role called," but "what does it cover today, and is that still coherent." The same title can hide very different realities depending on the size of the company, and it's by looking at the content of responsibilities, not their label, that you spot what needs to be re-cut.
Telling owner, contributor, and consulted apart
To get out of the fuzziness without adding weight, it's often enough to distinguish three positions on a given topic: who owns it, who contributes to it, and who needs to be consulted. The owner carries the decision. Contributors bring the work. Those consulted offer input that informs the decision without commanding it. This simple distinction dissolves most turf conflicts, because it names what was being left implicit.
You do have to resist the temptation to formalize everything, though. An exhaustive responsibility matrix applied to every micro-decision re-creates the very heaviness you were trying to escape. The aim isn't to map the organization in detail, but to remove ambiguity on the topics that matter. Useful clarity is the kind that helps you decide faster, not the kind that produces one more document.
Common traps
The first trap is the overly broad role, which aggregates so many responsibilities that none is truly held. It holds up as long as the person is exceptional, then becomes a point of fragility the moment they saturate or leave. The second is the overly central role, which concentrates decisions to the point of turning its holder into a bottleneck, reproducing at the scale of a single role the very problem you were trying to solve.
The third trap is the opposite: over-structuring. In trying to clarify everything, you multiply roles, sign-offs, and layers, and you smother an organization that mostly needed a few clean lines. Clarity is not the same as administrative density. A well-clarified company isn't the one with the most procedures, but the one where everyone knows, without hesitating, what they answer for.
Revisiting responsibilities at each step
Because scopes age, clarification isn't a one-off act but a periodic review. At each step of growth, it's worth taking the important topics again and checking that they still have an identified ultimate owner, that scopes don't overlap, and that no role has become unworkable. This re-examination beats a late overhaul forced by a crisis.
This discipline has a valuable side effect: it makes the organization less dependent on individuals. When responsibilities are clear and kept up to date, a person leaving stops being a threat, because what they carried is legible and transferable. Clarifying responsibilities, in the end, is what makes a company able to carry on without resting on the memory and heroics of a few.
Blurred responsibilities are often among the first symptoms of an organization growing too fast. Once responsibilities are clear, two natural extensions present themselves: tying those responsibilities to shared objectives, and giving them a space for regular follow-up.
OKRs give those responsibilities a measurable direction, and the manager-report 1:1 gives them the place where they are followed and adjusted over time.