A lot of organizations hold off on continuous improvement software for the same reason: "We're not ready. Our culture needs work first." This is a reasonable instinct, but it gets the sequence backward. Culture gets built by using the tools, not before adding them. To see how that plays out in practice, meet Doug. Watch the video or read below...

Doug is a practical guy. Frugal, too. He wants to get faster, so he does what practical people do: he reads. A lot. Books on running, training plans, the physiology of endurance. He sets a goal, builds his theoretical knowledge, writes out a plan. On paper, Doug is now an expert. Goal, check. Knowledge, check. Plan, check.

There's just one thing Doug skipped. He figured he didn't need to buy running shoes until he'd proven he could actually run. Why invest in gear for a thing you haven't committed to yet? So when race day comes, Doug laces up the shoes he already owns. Dress shoes. He's glad he already has them. No new purchase required.

You can see where this is going. Nobody runs a marathon in dress shoes. Sure, they weren't made for it -- but that's exactly the point. Doug didn't choose the wrong shoes out of ignorance. He chose them because he was waiting until he'd "succeeded" before equipping himself to succeed. The logic eats its own tail. You don't need the tools until you've already done the thing, and you can't do the thing without the tools.

You already have an improvement system. It's just terrible.

Here's where Doug stops being about running.

Most organizations that say they're "not ready" for improvement software already have an improvement system. It's just a bad one. They're trying to spread continuous improvement with spreadsheets, bulletin boards, and email. Those are the dress shoes. Not chosen because anyone thinks they're the right equipment for the job, but because they're already on the shelf and they feel free.

They are not free. They're the most expensive option you have, and the bill comes due slowly enough that nobody connects the cost to the cause.

Think about what spreading improvement on those tools actually requires. Someone in one department has a good idea. They put it in a spreadsheet, or pin it to a board, or send an email. And then what? There's no mechanism to route it, no way to track whether anyone acted on it, no visibility for the three other departments wrestling with the identical problem. The idea sits. The person who raised it hears nothing. They learn, correctly, that raising ideas is a waste of breath. Ethan Burris's research at UT Austin found that this sense of futility silences people just as reliably as fear does -- not "I'm scared to speak up" but "why bother, nothing happens." Email and spreadsheets are futility machines. They are built, structurally, to make sure nothing happens.

This is the marathon in dress shoes. You can technically do it. Organizations run improvement programs on spreadsheets every day. They're just slow, it hurts the whole way, and most of them don't finish -- they plateau somewhere around year two and quietly call it change fatigue.

The part that sounds backward

So here's the claim that makes people uncomfortable, and I'm going to defend it rather than hedge it: you don't get the tool when your culture is right. The tool is what makes your culture right.

The instinct to fix culture first treats culture as a thing you complete before you equip people, the way Doug treated running as a thing he'd master before buying shoes. But a culture of improvement is not a precondition you satisfy and then graduate from. It is the accumulated residue of thousands of small daily acts -- someone surfaces a problem, someone tests a change, someone sees a result, someone gets recognized for it.  Culture is what those acts leave behind. No acts, no residue, no culture.

And every one of those acts depends on the thing the spreadsheet cannot do. People keep surfacing problems only if surfacing a problem reliably produces a response. They keep testing changes only if the results become visible to someone who cares. They keep participating only if participating is acknowledged. Cue, behavior, reward -- that's the loop that turns a one-time effort into a habit, and habit is what culture is made of. The tool is what supplies the loop at scale. It captures the idea, routes it, triggers the response, shows the result, and closes the gap between "I said something" and "something changed." Do that a few hundred times, and you have not installed a culture -- you have run the machinery that grows one.

That's why the sequence in the objection is wrong. Waiting for the culture to be ready before you add the system is waiting for an output before you'll allow the input. The behaviors build the culture. The tool is what lets the behaviors happen often enough, visibly enough, and reliably enough to compound into something that deserves the name. Take the tool away, and you're not protecting a fragile culture. You're starving it of the one thing it needs to form.

This is not "buy software and a culture appears on its own." Software left unused is just a digital bulletin board, and a digital bulletin board left unused is no better than a cork one. Leaders still have to go see the work, respond to ideas with curiosity rather than defensiveness, and visibly pursue their own improvement. The point is narrower and harder to argue with: those leadership behaviors cannot survive contact with scale on spreadsheets and email. A leader can respond to every idea from one team by hand. Across forty teams, by hand, they cannot, no matter how committed they are. The system is what lets good leadership behavior reach more than one room. That's the mechanism. That's why the tool comes first.

What Doug should have done

Doug's mistake wasn't reading. The reading was fine. His mistake was deciding that equipment is a reward you earn after success rather than the thing that makes success possible. He had the goal, the knowledge, and the plan -- everything except the one purchase that would have let any of it matter -- and he talked himself out of that purchase precisely because he was being careful.

If you're holding off on a system until your culture feels ready, you're making Doug's decision. You have the goal. You probably have people who'd improve their work if the path of doing so didn't dead-end in a spreadsheet nobody reads. What you're missing is the equipment that turns all of that into motion. And you're missing it on purpose, for the most reasonable-sounding reason in the world: you want to be sure before you invest.

Do yourself a favor. Get the tool you need before you start the race, not after. The race is what builds the culture, and you can't run it in dress shoes.

KaiNexus helps organizations start, spread, and sustain continuous improvement -- connecting strategy to frontline work so leadership can see what's actually happening. See KaiNexus in action.