Grow Into Your Britches

Small businesses often wait too long to design for growth.

The explanation sounds practical: “We’ll document that when we’re bigger.” “We don’t need formal ownership yet.” “Everyone knows what to do.” The current team is close, communication is fast, and the founder can still reach every decision personally.

Then growth arrives and exposes the bill.

The new employee learns by interruption. The same title means three different things. Customers receive different answers depending on who picks up the phone. The founder becomes the approval path for everything important and plenty that isn’t. The company has more people but less clarity.

The mistake was not staying informal while the business was small. The mistake was building a system that could only remain small.

One of my favorite Kyleisms is: Develop for greatness and grow into your britches.

That doesn’t mean hiring a corporate hierarchy before revenue supports it. It means defining the work before you have a separate person for every function.

In a five-person company, the owner may carry business development, finance, service leadership, and technology decisions. That’s normal. What matters is whether leaders recognize them as distinct responsibilities with clear outcomes. One person may wear four hats today. If you define the hats, you can hand one to a new person tomorrow without inventing the role during onboarding.

This is the difference between designing for scale and pretending to be large. Designing for scale is practical. It asks:

• What function is this person performing?
• What outcome should it produce?
• Who owns it today?
• What decisions belong to that owner?
• What knowledge must survive when the hat changes heads?

The exercise is useful even if no hiring is planned. It reveals conflicts hidden by personality. It also shows where the founder is doing work that prevents the founder from leading.

The strongest small companies I’ve seen don’t bury themselves in policy. They make ownership visible. They document the work most likely to be repeated, delegated, regulated, or interrupted. They choose tools that can support the next stage instead of forcing a system replacement every time headcount changes.

They also avoid building fantasy infrastructure. Growth-ready does not mean complicated. If a process requires more administrative effort than the risk or value justifies, simplify it. A system earns its place by making execution clearer, more reliable, or more transferable.

Here’s a useful test: imagine doubling revenue without doubling headcount. Which part of your operation breaks first? Now imagine the person who owns that area gives two weeks’ notice. What knowledge leaves with them?

Those answers identify the britches the business hasn’t grown into yet.

Build the role. Define the handoff. Document the standard. Then, when growth comes, you can add capacity without adding confusion.