A field guide for an organization whose way of working has not kept up: read the strain early, and build for the business you're becoming.

Why tools chosen for a smaller company strain as it grows, how to read the strain before it breaks something, and how to build systems for the business you are becoming.
How things get done
The challenge: Our systems haven’t kept up with our growth
Systems are chosen for the company that existed at the time, and growth keeps changing that company. Tools strain before they break, and the first sign is the work done around them: copying between systems, reconciling numbers, rebuilding reports by hand. Adding another tool spreads the same fact across more places, and a replacement that copies today’s setup carries the old limits forward. The guide helps you see that strain early, decide where each important fact lives, and choose systems for the stage the business is growing into.
Who it’s for: Leaders of a growing company or function: a chief executive, a chief operating officer, a finance or sales leader who makes decisions on numbers the systems should agree on. Read it on your own first, then take the conversation in part three to your team.
Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.
The leadership meeting opens with two numbers for last quarter’s revenue. The sales leader has one, from the customer system. The finance leader has another, from the accounting software and a spreadsheet that has gained a new tab each quarter for several years. Both are right by their own sources, and the next twenty minutes go to working out why they differ. It isn’t the first time. The customer system was set up when the sales team fit around one table. Support runs out of a shared inbox. Each team has bought a tool or two of its own, and the information that matters most, who the customers are and what they pay, now lives in several places that don’t agree. The people in the room know something needs replacing. They also remember the last replacement, which took twice as long as planned and fixed less than promised, so the room is slow to propose the next one.
Think of the last number two of our systems disagreed on, and ask:
With the week of notes on the table:
For one week, ask your team to keep a short note each time they copy information by hand from one system to another, rebuild a number a system should have given them, or keep a spreadsheet because the shared tool can’t do the job. Ask them to note roughly how long it took. At the end of the week, read the notes together. The pattern usually points to one or two systems, and to the questions those systems can’t answer. That is a clearer starting point than a list of tools to buy, because it starts from the work the systems are failing to support rather than from what the market is selling.
Free, no card.
Mark D. Benson is the founder and principal writer of Resonant Vector, the home of Pressure Intelligence, and the host of Pressure Rising™. He is a product and systems leader who has spent his career running global teams, complex platforms, and consequential decisions under real constraint.
His career sits where strategy, technology and large human systems meet, in places where high stakes are the norm.
Resonant Vector is his commitment to learning in public and sharing what helps leaders and teams perform under pressure.
More about Mark can be found at markdbenson.com.