Skip to content
All journal entries

Process · The ODEG method

From founder-led ops to a real operating model.

By Daniel Blatchford6 min read

When you start a business, it makes sense for most things to go through you. You know the customers, the prices and why things are done a particular way. As the business grows, keeping all of that in your head becomes difficult for everyone.

You can see it in the small interruptions. Someone needs a price approved. Someone else wants to know whether an order can go out. A customer is waiting for an answer only you seem to have. These may each take a minute, but together they can fill the day.

What an operating model is, in practice.

I’d start with a few practical questions:

  • Where does work begin, and where does it end?
  • Who owns each handover?
  • Which decisions can the team make without asking you?
  • What happens automatically, and what relies on someone remembering?
  • Where can people find the information they regularly need?

Clear answers let people get on with their work. They also show you where a process needs documenting, where someone needs more authority and where a system could take on a routine task.

Why AI changes the maths.

Small businesses have to be selective about what they build and buy. A process that is irritating for ten minutes a week may not justify much investment. Something that occupies a person for several hours a day deserves a closer look.

AI and automation can make some of that work easier to tackle: extracting information from documents, drafting follow-ups or moving data between systems. The right approach depends on the task, the cost of an error and how much human review is needed.

How ODEG runs this.

The scope depends on the business, but this is the approach I work through with clients:

  • Audit: follow the work with your team and identify the problems worth solving.
  • Roadmap: agree priorities, costs and what a useful result looks like.
  • Build: configure the tools, connect the systems and develop the workflows you need.
  • Implement: test with the team, handle exceptions and make sure everyone knows how it works.
  • Improve: review the results and adjust the parts that need more work.

If this sounds familiar, tell me which parts of the business still depend on you. We can work out where to start and what it would take to hand them over properly.

FounderOperating modelMethod
Reply to this