Published September 14, 2026 · Altvina Insights · 6 min read

The Article Is Right, and It Stops One Step Short

Inc's August 31 piece argues that growth-stage teams feel less sharp because they are running habits built for three people, not because they lost their hunger. We agree, and we add the three-question audit the article does not hand you.

On August 31, Inc published a piece whose headline does most of the arguing by itself: "Your Growth Company Hasn't Lost Its Startup Hunger, It's Running on Habits Built for 3 People."

We think it is right. We also think it stops one step short of anything a founder can act on this week.

Where the article is right

The article takes a story founders usually tell about morale and turns it into a story about design.

At three or five people, coordination is free. Everyone hears everything because everyone sits in the same conversation. Nobody writes down who owns what, because nobody needs to. Skipping that step is the correct call at that size, not sloppiness.

At fifteen, the same habits start charging rent. The conversation splits. Two people hedge on the same task because neither is sure it belongs to them. Work still gets done, and it gets done at a cost nobody is measuring.

From the outside, that reads as a team that lost its edge. The article's point is that the edge is fine and the habits are stale, which is a far more fixable diagnosis.

What we would add, from what we keep meeting inside service firms: the clearest signal is rarely someone slacking. Count the small workarounds that quietly became the process. A colleague rechecking work just in case. A client question that routes through three people before it reaches the one who can answer it. Each workaround was invented by someone reasonable solving a real problem, and none of them were ever meant to be permanent.

Where it stops

An accurate diagnosis is not the same as knowing the diagnosis is yours.

Plenty of pieces in this genre will describe your business well enough that you nod along. Nodding is not evidence. And no founder should start reassigning role ownership on the strength of a headline that landed well on a Monday morning.

So here is a check you can run alone, in about forty minutes, with a notebook and no meeting. Three questions. The rule: answer each one with something you can point at, not with what you believe to be true.

The three questions

1. Are the five or six roles that carry the business written down anywhere?

Not job titles, and not the org chart. The functions that, if nobody did them for two weeks, would cost you money or cost you a client. Our expectation, offered as opinion rather than data: the list runs five or six items, and it comes out shorter than you would guess.

Write them out. Beside each one, write the person. Then, beside the person, write where that assignment exists in writing: a document, a message, an onboarding note, a contract.

Point at nothing, and that role is currently held by whoever noticed first. That has worked so far. It also breaks quietly when the person who usually notices is on vacation, in a client meeting, or new.

2. Does a new hire's first month depend on someone's memory or on something they can read?

Pick the newest person on the team, whether that is someone who joined this year or the last contractor you brought in. Then pick one task they do every week.

Ask them to send you the instructions for it.

Whatever arrives, or does not arrive, is your answer. A link to something readable is a good sign. A reply along the lines of "I just ask whoever has been here longest" means a person is your documentation, and that person already has a day job.

3. Would the business run the same way for a month without you checking in?

Not "would it survive." It would survive. The same way: same quality, same speed, same decisions getting made rather than stacking up until you are back.

Skip yes or no. Write down the list of decisions that would wait for you. Pricing exceptions, scope disputes, who covers a sick colleague's client, whether to take the awkward job in week three.

The length of that list is the finding. Our own judgment, offered as judgment: the decisions that would wait tell you more than the tasks that would wait. Tasks get covered. Decisions sit, and the sitting is what a team experiences as the business feeling slower than it used to.

What the answers mean

Three document-shaped answers, and this genre of article is not about you. Close the tab and go solve whatever your actual constraint is, which might be demand, pricing, or delivery capacity.

A mix is the common case, and a mix is not an emergency.

Three memory-shaped answers, and the Inc piece is describing your firm accurately. The first move is almost never a new tool or a new hire. Writing down the five or six roles and who holds them costs an afternoon. Telling the team costs ten minutes and is the part that gets skipped.

The temptation at this point is a project management tool or an operations hire. Both can be right later. Neither substitutes for a sentence naming who owns the thing, because a tool with ambiguous ownership just relocates the ambiguity into a nicer interface.

Growth exposes gaps, it rarely creates them

This mechanism is not unique to role design, which is part of why the Inc framing travels so well.

Look at a different domain entirely. Bain's survey of US companies found that 75% of companies say scaling their AI use exposes a shortage of in-house expertise across critical functions. Different subject, same shape: the gap existed at small scale, and scale made it visible and expensive at the same time.

Fifteen people does the same thing to habits built for three. Growth does not manufacture the problem. Growth stops letting you absorb it personally.

Ruling it out counts as a result

The honest case for running this audit: it works in both directions. Either it finds something you can fix without spending money, or it tells you role clarity is not your bottleneck and you can stop wondering about it.

One last thing about the human side. Ambiguous ownership is tiring in a way that heavy workload is not. People can carry a lot of work when they know the work is theirs. What wears them down is the low background uncertainty about whether someone else was supposed to handle it, and whether raising it will sound like complaining.

Putting it in writing is not bureaucracy. Read from the inside, it lands closer to a kindness you can hand over on a Tuesday.

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.