How to define roles and responsibilities in a small team

Every growing company runs on the same sentence for a while: everyone helps where it hurts. It works, right up to the point where two people are doing the same job, one outcome has no owner, and the founder is the only person who can decide anything.

That is not a people problem. It is a missing sentence per role: what this seat owns, what it decides alone, and where it stops.

Why "everyone helps where it hurts" stops working

Up to about ten people, overlap is cheap: everyone sees the whole business, so gaps get filled by whoever notices them. After the first managers join, the same behaviour becomes expensive. Each manager fills gaps on their own side, the founder fills the ones in between, and priorities start to disagree.

The result is rarely a dramatic failure. It is quieter than that:

• Work that two people consider theirs gets done twice, badly.
• Work that nobody considers theirs does not get done at all.
• Decisions arrive at the founder because nobody was told where their authority ends.
• Reviews become arguments, because nobody can say what the role was supposed to deliver.

The four lines every role needs

A role definition is not a job description. It has four parts, and none of them is a list of tasks:

1. Outcomes — the two or three results this role owns for the next two quarters, in plain words.
2. Decision rights — what the person can decide alone, and what comes to the manager first.
3. Boundaries — what this role explicitly does not own. This is the line that prevents overlap with the founder's work.
4. Cadence — when the role gets looked at again: quarterly for most roles, more often while the work is changing.

How to define roles and responsibilities in a small team, step by step

Start with the work, not the title. Ask what would be visibly missing if this person stopped for a month. That answer is the role.

Write it with the person, not about them. Twenty minutes at a table beats a document handed down. The person usually knows where the role ends better than the manager does.

Write three outcomes for the next two quarters. If you can write ten, the role is really two roles, or you are describing tasks.

Name the decision rights out loud. Money, scope, hiring, exceptions — say which ones the person handles alone and which ones come to you. Ambiguity here is what puts the founder back into every decision.

Draw the boundary. One line, plainly: this role does not own pricing, hiring or the roadmap. It feels blunt written down, which is exactly why it works.

Get the manager's approval and share it. A role that only the founder has seen is not a standard, it is a private opinion.

A worked example: the founder and the delivery lead

A twelve-person agency. The founder writes the scopes, delivers the work and answers client questions. A delivery lead is hired to take the projects. For three months both of them own delivery, and clients hear two answers.

Written down, it takes one page:

• Outcomes: projects delivered inside scope and margin; a delivery calendar clients trust; no project stalled for more than two working days.
• Decision rights: can move timelines inside an agreed scope, can reassign people between projects, must bring anything that changes price or contract to the founder.
• Boundaries: does not own pricing, contracts or new business conversations.
• Cadence: reviewed every quarter, and the week the work changes.

The argument does not disappear because the two of them suddenly agree more. It disappears because the next time a client asks for something out of scope, there is one answer and one owner.

Role clarity for teams: the five-minute test

Pick any role on your team and ask five questions. Every hesitation is where the overlap lives.

• Can you name the three outcomes in plain words?
• Can the person say them back to you without reading them?
• Can they name one decision they make alone?
• Can they name one thing the role does not own?
• When was this last looked at, and did it still match the work of the last month?

Keep it alive

A role definition describes a job that no longer exists the moment the work changes, and a person judged against an old definition has a fair complaint. The rule we use: when responsibilities shift, change the line that same week. It is a five-minute edit, not a project.

These four fields are the ones we use for employee role scorecards in the product — outcomes, decision rights, boundaries, reviewed on a cadence. Written down, they are the difference between a team that argues about ownership and a team that gets on with the work.

If you are already reviewing people against those roles, the companion piece is how to run performance reviews in a small business.