A practical starting guide

You do not need a solution worked out.

Start with one problem that keeps coming back. A few observations from a normal working week are more useful than a list of tools to buy.

Write down one problem.

  1. What happens today?For example: quotes wait days for a price check and a manager’s approval.
  2. Who is involved, and how often?Note the people or teams, roughly how often it happens, and where it slows down or goes wrong.
  3. What would better look like?Faster approvals, fewer errors, or a clear view of what is waiting. Choose something you can observe.

Example to bring to a conversation: “Website enquiries arrive in a shared inbox. Nobody owns follow-up, so some wait days for a reply.”

Choose the help you need.

Understand a complex problem

If several teams or systems are involved, or the cause isn’t clear, business analysis maps the work and tests the causes before anything is bought.

About business analysis

Fix a clear, bounded task

If information needs to move between systems or a repeatable step needs automating, a scoped build may fit. We first check the inputs, exceptions and cost.

About AI solutions

Help people do the work

If someone needs to draft, summarise or interpret information, training may be a useful start. A person reviews the work and decides what to do.

Explore training

Not sure which?

The free snapshot suggests a route from your answers in a few minutes, including when a simple change is enough.

Get your free snapshot

Still unsure? WhatsApp Justin about a business problem or system, or WhatsApp Marvin about training. You do not need to buy anything to ask which route to explore.

Sometimes the useful answer is a simpler process.

A clearer template, a shared checklist, or a change in responsibility may solve the problem without buying anything. The free snapshot will say when that looks likely.