Business practice
Department structure.
Roles grew around the people who happened to be there. You reach a structure where responsibility is clear, decisions have an owner, and nothing important sits between two job titles.
Your structure was not designed. It accumulated, one good hire at a time.
That is not a criticism. It is how most organizations of your size got here. Somebody capable took on the thing nobody else was doing, then took on the next thing, and the job title never caught up. It works until that person is stretched, or leaves, and the work turns out to have no other home.
What we build is a structure people can act on: who owns what, written down and agreed out loud, where each recurring decision sits, and the gaps and overlaps surfaced before they cost you. It is a working document about responsibility, not a chart to hang on a wall.
The approach
Three words we work by.
Name.
Every meaningful area of work gets an owner by name, and every owner sees the list before it is final. Written ownership that has not been said out loud in the room is not ownership, it is a document. The conversation where two people discover they both thought they owned something is the useful part.
Decide.
Decisions are mapped separately from tasks, because that is where the queue forms. For each recurring decision: who makes it, who has to be consulted, and what threshold sends it up. Most of what waits on a leader turns out to be something somebody else could have settled.
Close.
Gaps and overlaps get surfaced and closed while they are still cheap. The work sitting between two job titles, the approval two people both believe they give, the responsibility everyone assumed belonged to the person who left. Each one gets a name or an explicit decision to leave it open.
The work
Four workstreams, in sequence.
Ownership map
Every recurring area of work listed against a named owner, built from what people actually do rather than from job titles. The draft goes back to the people named on it, because ownership somebody has not agreed to is a wish.
Decision rights
The recurring decisions in your organization written down with who decides, who is consulted, and what threshold escalates. This is normally where the queue behind one calendar comes from, and it is the fastest thing to fix.
Gaps and overlaps
The work with no owner and the work with two, listed plainly. Each item gets resolved in the room or gets an explicit note saying it stays open and why, so nothing quietly returns to being nobody's job.
Structure on paper
The agreed structure written down in a form your team can use and change: owners, decision rights, escalation, and a review date. Handed over with the disagreements that were settled noted, so the next change starts from a record rather than from memory.
Related reading.
All insights
Operations
The two-person dependency test
Pick any critical workflow and ask one question. If these two specific people were both unreachable for a week, what happens. If the honest answer is that things quietly stop, you have found the real risk register of your firm, and it does not appear in
Retention
The six questions that find churn before it finds you
Every firm that has lost a client it did not expect to lose has the evidence sitting somewhere in an inbox. The six questions below take about an hour to work through and they will surface the pattern, but only if you are willing to run them against
Questions
Asked before, answered plainly.
Usually not. Most of what we find is fixed by naming an owner and moving a decision down a level, with nobody changing seats. If the structure genuinely needs to change we will say so and show you why, but that is the less common outcome.
That is not what this is for. The question we answer is where responsibility is unclear, not who is surplus. If the work says you are short of a person somewhere, we will say that too, and headcount planning is the piece that answers it properly.
By telling them what it is before it starts and by showing them their own section before it is final. The exercise is about work, not performance, and every person named on the map sees it and can argue with it.
The smaller you are, the more decisions tend to queue behind one or two people, so the value often shows up faster. It does not have to be a framework. For most organizations of your size it is a single page listing the decisions that actually recur.
Then you have found one of the more expensive items on the list, and it is better found here than during an incident. Somebody with the authority to settle it needs to be in the room, which is why we ask for that person up front.