Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

Built for Now

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.

Built for Now
93
built-for-now

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.

How it shows up

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 scene

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.

Where it lands

  • In you: you often make decisions on numbers you aren’t sure of, and you ask for reports that take days to build by hand.
  • In your team: people tend to copy information from one system to another, keep their own spreadsheets because the shared system can’t give them what they need, and spend real time reconciling.
  • In your organization: each team typically has its own tools, the same fact lives in several places, and the systems slow down or break at the busiest moments, which is when growth tests them.

Questions to ponder

Think of the last number two of our systems disagreed on, and ask:

  • Where does the most time go: moving information, fixing it, or rebuilding reports?
  • Which questions do leaders ask that no system can answer without hand work?
  • Who owns each core system on the business side, and when did they last plan for its next stage?
  • How many tools do we pay for that do overlapping jobs?
  • Are we using most of what our current systems can do, or a small part of it?

Questions to discuss

With the week of notes on the table:

  • Where do we copy information by hand, and what would we do with that time back? The notes usually point to one or two systems.
  • Which number do we argue about because two systems disagree? The argument usually points to a fact with no agreed home.
  • How could we change the way we work together so that each of us helps the others get a number they can trust, and one system holds each fact for all of us? Name one fact each of your teams will read from the agreed system rather than from its own copy, and what you need from the owner of that system.

Try this week

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.

Keep reading with a free account

  • Three versions of this challenge, from hours lost moving information between systems to tools you already own and use only a small part of
  • Why the spreadsheet people keep by hand is often an exact description of what a system is missing
  • Why each core system needs a business owner as well as a technical one, and the question to put to that owner once or twice a year
  • How to replace a system in stages, one team or one region first, and why copying today’s setup into new software brings the old limits along
  • The research behind it, and books to read next
  • The toolkit: questions to ponder, questions to discuss, things to subtract, actions to take
  • The kit, as downloads: the full Field Guide, a Leader’s Guide, and slides for the team conversation
Create a free account

Free, no card.

Open the field guide >>

About the author

Mark D. Benson
Mark D. Benson
Founder of Resonant Vector™
Resonant Vector
Full profile →

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.