Find which corner of functions, people and operations breaks first

1. Why hiring alone does not add capacity

A lot of people believe that more people means more capacity. A founder feels stretched and hires. For 60 days that feels good: there is some momentum, and everyone notices the new faces. Then the new hire turns up with 47 questions, repeats work someone else is already doing, and nobody is sure who owns what. Six months on, two outcomes are given: more headcount and the same capacity, or twice the team and the same revenue. This is said to happen all the time. The figures belong to an illustration.

The pattern. The problem, in this reading, is not people but a lack of structure. Stretched thin, you take someone on. They arrive capable, driven and eager to contribute, and still they are missing:

• a sense of what the job is beyond the loose description they were given;
• a picture of where their work meets the rest of the team's;
• a clear idea of who handles which questions;
• knowledge of the way decisions are reached;
• the company's unwritten norms, which appear in only one of two lists.

So they come to you, constantly. You had one bottleneck, yourself; now you have that same bottleneck and a person who relies on it. What you have added is dependency, not capacity. Some of you, it is expected, already feel that new people lean on you the moment they arrive, to the point that you would rather not hire more. The work on this page aims at the opposite: people who multiply what the business can do instead of depending on you.

2. The three corners

Every business that is scaling, in this model, needs three things working together, drawn as the corners of a triangle with growth at its center. When all three are in place, growth follows. Let one corner go weak and growth stops, or, in a second reading, starts to stall.

Corner	What it covers
Functions	What work has to happen. Settle it before you hire: most founders skip this step and take on "a marketing person" without deciding what marketing results they need. Functions differ from one kind of business to another: e-commerce, B2B, software sold as a service, AI, a service business, a gym
People	Who carries out the work: people suited to their roles and skilled for them. You cannot judge who is suitable until the functions are defined, because you cannot choose people for work you have not described
Operations	How work passes between people: how they communicate and how decisions are made. It is called the connective tissue

Where founders look. Most founders, it is said, fix their attention on people and leave functions and operations unattended. They bring strong people into roles nobody has defined, with weak operations or no working rhythm at all, then wonder why nothing works and conclude that the people are bad. The answer here is to go back to the triangle and ask whether the fault lies in a function, in a person or in an operation.

A diagnostic. The triangle serves here as a diagnostic: stalled growth means a corner has failed, and your job is to work out which one.

Starting from what the company is trying to achieve, and only then asking whom it needs, is also how workforce planning begins in section 2 of SOP 179 — Plan the workforce and map responsibility.

3. Where companies break as they grow

Chaos, in this view, is predictable rather than random. Each stage of growth has a failure you can expect, and that failure tells you what to build next.

People	Stage	What breaks	What to build
0 to 10	Startup	Clarity about roles	Scorecards naming results, not duties
10 to 50	Scale-up	Communication	Meeting rhythms and frameworks for making decisions
50 to 100	Professionalization	Accountability	KPIs, OKRs and ownership charts
100 and up	Enterprise	Leadership depth	The short layer of leaders: middle managers, executives or both

Up to ten people. Everybody does everything, and no one knows their lane. Often, role clarity is the trouble at this size, and the fix is usually job scorecards (section 4). In a team of one to ten, this is typically the broken part. With everyone doing a bit of everything, you shy away from telling people what they are really responsible for; getting people that clarity is what takes you out of this stage and into the next.

Ten to fifty. Information stops moving. One person has no idea what another is doing, and you become the hub of every conversation. The fix is a set cadence: structured meetings such as weekly stand-ups, clear channels for communication, and frameworks for decisions that people can use without depending on you.

Fifty to a hundred. This is where accountability gives way. Roles are clear, people communicate and there are ways to decide, but nobody is held to account, so work slips through the cracks and nobody feels they own it. Put KPIs and OKRs in place and draw ownership charts for each department, so each result belongs to a single named person rather than to a committee.

A hundred and up. Typically, there are not enough leaders. Often you have something like 20 people reporting straight to you, and everything moves slowly, because there is too little accountability and decision making has not been handed out. The fix is to build whichever layer of leaders you lack. That might mean executives, it might mean a middle management layer, made by hiring or growing people able to run a team of anywhere from 5 to 20, or maybe both layers are short of people.

Mostly not a people problem. Looking across these stages, which is where many companies break as they scale, only the last is about having too few people; the others lean more on functions and operations than on people. A lot of people blame their people when the fault is really in a function or an operation. The business is already telling you what to fix, if you pay attention.

Think it through yourself. When growth stalls, ask which corner is breaking. Take the time to think about it yourself, rather than handing the question to an AI chat tool.

A different cut. SOP 183 divides growth into narrower headcount stages and names, at each, the one constraint holding the whole business back. The bands here name what breaks in how the people, functions and operations are organized.

A matrix of who does, answers for, is consulted on and is told about each task, built one team at a time, is section 6 of SOP 179. How to grade a team's communication and lift its weakest part is SOP 136 — Grade a team's communication and raise its weakest part.

4. Write each role as outcomes

A job scorecard names what a person is responsible for achieving, not a list of tasks. To show the difference, set an outcome beside a task: owning customer retention above 90 percent, rather than answering support tickets.

How one company does it. Every job description in one company carries a short section that sets the role out under these headings:

• Role.
• Responsibility.
• Result: the results the person is responsible for delivering. This is said to be what most people leave out.
• Requirement: the prerequisites.

That is a description of one company's practice. The instruction is the one in section 3: at the smallest size, give people clarity about the outcome they own.

Writing the job description as an ad that draws applicants is section 8 of SOP 148, on recruiting while the business is still very small.

5. The test of time away

Picture yourself gone for 30 days: you leave tomorrow for a month and do not look at the team chat. Which corner collapses first?

Corner	What you would see
Functions	Work stalls, since nobody is clear on their role
People	Without you, the team is unable to reach a decision
Operations	People stop talking to each other, and the pieces no longer fit together

Write your answer down. That is where to focus next: the place to get into the detail. As you answer, think about what is going wrong right now. A second framing asks what would break if you left for about a month, and settles on a month because it feels harder.

Be honest with yourself. What breaks while you are away is, in this view, a systems problem and not a people problem, and a systems problem can be fixed.

6. Why systems feel slow

Putting systems in place feels like easing off, and easing off feels like losing ground. Process can seem like bureaucracy, like braking while you are moving fast. The reply here is that speed without structure is not growth but chaos at a larger size.

Without systems. A strong hire asks you how something is done, and you tell them. Two weeks on, the same question comes back and you answer it a second time; then they get it wrong and you put it right. Repeat that for 20 people and what grows is a reliance on you, not a business. A lot of you are in that place now, with everyone depending on you.

With systems. You hire someone great, hand over the playbook and tell them their place on the scale of ownership (SOP 266). They do the work and make decisions, bringing you only the 5 percent of unusual cases that fall outside the playbook; in a second reading, they may come to you for only about 5 percent. Those questions are welcome, in this view: that is what the founder is there for.

No shortcut. There is no magic software and no magic formula for this, in this view. It takes conversation after conversation, and the expectations are yours to set.

Bad systems and good ones. A bad system adds friction exactly where you do not want it: momentum drops, work slows down and feels harder, and it feels like bureaucracy. Good systems build momentum. Maybe there is a cost in the short run, but over the long run it gets the ball rolling. Systems free you up instead of slowing you down, and turn people who keep asking questions into people who make decisions.

A way to hand one of your own advertising jobs to someone else, by writing it down, showing it and then watching them do it, is SOP 43 — Document, demonstrate, duplicate. Writing the playbook itself as actions someone can be seen doing is SOP 279, section 4.

7. How strong corners feed one another

When all three corners are strong, each one strengthens the next. One reading gives the order below; the last step, stronger functions, is placed from a diagram of the loop and from a second reading:

• Clear functions. Knowing precisely what the business needs lets you hire for results instead of tasks.
• Well-placed people. Each person sits in a role that suits them, so the work happens without you, and people can work at level four or five of the scale of ownership (SOP 266).
• Operations that link them. Information moves, decisions come quickly, and people are held to account as a matter of course.
• Better results. Revenue rises, the culture grows stronger and execution gets better.
• Better people drawn in. Top performers want to work inside systems that function well, and they hate working reactively.
• Stronger functions. With better people, you can take on bigger problems.

And round it goes again. In the second reading the loop closes with better people creating stronger functions, and those creating clear functions.

Most founders, in this view, are on a hamster wheel, working hard and going nowhere, because one of the pieces is missing. Getting all three corners right is what makes the hard work pay off.

8. A build list

• Audit the triangle. Which corner is weakest? Ask whether you understand what functions the business has, whether operations connect those functions, and whether you have people in their seats.
• Check your breaking point. For the size you are now, check that you are fixing whatever is most likely to be breaking (section 3). This list speaks of revenue size, though the stages in section 3 are counted in people.
• Define the levels of ownership, and where each person should be working (SOP 266).
• Build the connective tissue around them: the operations that have to surround each of these.

Circle where you are weakest right now. You will not solve it all at once, or all at the same time; you work through it, because it is a system.

9. What this page does not decide for you

• Size by people or by revenue. The stages in section 3 are counted in people, while the build list near the end asks you to look at your revenue size. This page does not settle which reading is right.
• The edges of each stage. The ranges share their end points (ten and fifty, for example), so a team of exactly that size fits two stages. Not established on this page.
• How long before a hire adds capacity. The 60 days and six months belong to the illustration in section 1. This page gives no figure for how long a new hire takes to add capacity.

10. The checklist

Step	What to do
1	Before you hire, define the work that has to happen and the results you need from it
2	When growth stalls, work out which of the three corners is failing
3	Find your size in the table in section 3 and check that you are building what that size typically lacks
4	Write each role as the outcomes it owns, not a list of tasks
5	Imagine a month away and write down the corner that would collapse first
6	Give each hire the playbook and their level of ownership, so they bring you only the edge cases
7	Audit the triangle, check the breaking point for your size, then set levels of ownership and the operations around them

11. What this page does not cover

Setting the level of ownership for each role, and training people up it, is SOP 266 — Set each role's level of ownership and train people up the dial. Bringing in people to fill the roles is SOP 267, on a hiring funnel built like a customer funnel, and the interview is SOP 268 — Gate each interview step, then sell at the close.

The management practices themselves, cadence among them, are SOP 271 — Score your management system and fix its weakest practices.