When a business owner asks me to fix everything at once, my answer is usually to start with one job. Not one app, not one department. One piece of work, followed from the moment it arrives to the moment it is paid.
Why not everything at once
The temptation is understandable. An owner who has lived with six disconnected apps for years wants all six gone by next month. But a system that tries to replace everything on day one has to guess at how the business works, and the guesses are where it breaks.
Following one job is different. You watch where it is written down first, where it gets copied, who has to ask whom what happens next, and where it waits. That path tells you more about how the business really runs than any list of software ever will.
What one job shows
The job card on a workshop floor is a good example of the kind of thing this turns up. The work is done well. The trouble is that the job lives on a card and the invoice lives somewhere else, so somebody has to carry it across by hand. Every step where work is carried across by hand is a step where it can be lost.
You do not find that by asking which apps a business uses. You find it by following the work.
Why this is how the Business OS starts
So the Business Operating System starts with one agreed operating journey, with named steps and a clear owner for each. Once that journey runs on one record, from the first capture to the invoice, the team trusts it, and the next journey joins onto it rather than sitting beside it.
It can feel slower at the start than a big launch would. The point is what happens after: the owner stops being the person who carries the handovers, because the handovers are part of the system.
If you want to see which of your own journeys leaks the most time, the free Business Autopsy is where that starts, and the Business Operating System is what it is built on.
Frequently Asked Questions
What is an operating journey?
One repeatable piece of work followed end to end, for example a job from booking in to the paid invoice. It names each step, who owns it and what happens next, so nothing is carried across by hand.
Why not replace every app at once?
Because a system built in one go has to guess how the business works. Starting with one journey shows the real path of the work, and every later journey joins onto a record the team already trusts.
Does starting small mean it takes longer?
The first journey takes careful work, because it sets the record everything else builds on. After that, each new journey connects to what is already running instead of starting again from nothing.