Start with the workflow that repeatedly holds up other work. Compare how often the problem occurs, who is waiting and the smallest useful change you can test. Agree the first phase before committing to a wider system.

Find the work that keeps stopping

A growing business can feel caught in a loop: it needs systems to handle more work, but investing in systems depends on the business growing. A smaller, well-chosen first step can make the decision easier to assess.

Follow one real workflow. A question becomes a quote, the customer pays, then an order is processed. Note where work waits, who needs to act and which information is missing.

Compare the effect on work

A large request may not affect daily operations. A small gap, such as an unclear owner for follow-up, may affect many customer enquiries.

Review the choices with the people doing the work. Use real examples to explain why one improvement comes first. That makes the trade-off clearer without dismissing the needs of other teams.

  • How often does this problem occur?
  • Who else is waiting because of it?
  • Would a clearer rule solve part of it?
  • What is the smallest useful change to test?

Give the first phase a clear job

Agree what the first phase should improve, who will use it and what remains outside its scope. Decide how you will review it after the team starts using it.

For customer enquiries, you might check whether each enquiry has a next action. For payments, you might check whether staff can identify orders ready to process. Choose a measure that fits the problem.

Leave room for the next step

Starting small should not mean starting over later. Discuss the records you need to keep, how to export your data, who maintains the system and which connections may be needed next.

Then learn from actual use. Some needs will become clearer. Others may change. Use that evidence to decide the next phase, rather than treating the original plan as fixed.

A phased approach helps organise scope and decisions. Costs, dependencies and the right sequence still need to be worked out for each project.

See how we review a workflow