Experience · Growing business

Illustrative pattern Growing business

What worked at ten people failed at fifty

An all-in-one system felt like the cure for growth pressure. The real operating system had become exceptions and tribal knowledge - invisible until scale made it expensive.

What the organization believed
We need an all-in-one system now.
Why that belief made sense
Spreadsheet-driven operations under growth pressure. Leaders wanted one place for the truth.
What contradicted it
Exceptions and tribal knowledge had become the operating system - unwritten, uneven, and hard to transfer.
What decision became clearer
Stabilize work, ownership, and exceptions first - then commit to a system that can hold them.

At ten people, informal coordination works. Everyone knows who to ask. Spreadsheets and side channels feel fast. At fifty, the same habits become a tax: work depends on who remembers the exception, not on a shared design.

The belief in an all-in-one system is understandable under that pressure. The contradiction is that software cannot invent ownership or decision rights that do not exist. Automating tribal knowledge without naming it usually freezes the mess into a more expensive form.

The clearer decision is order: which work is core, who owns each exception path, and what must be true every week - then select systems that reinforce that design rather than replace the need for it.