Most AI projects stall because they start with the tool. Start with the decision or the process you want to improve instead.

Most leadership teams now feel they should be "doing something with AI". The usual first step is a tool: a chatbot pilot, a set of licences, a proof of concept from a vendor. A few months later the pilot is still a pilot, and nobody can say what it changed.

The problem is rarely the technology. It is that the work started with the answer instead of the question.

Start with a process, not a product

A better starting point is a short list of business processes where time, cost or quality matters most. For each one, ask three things:

  • How much time or money does this process use today?
  • Where are the delays, errors or repeated manual steps?
  • What would a 20 to 30 percent improvement be worth?

This list is usually more ordinary than people expect: proposal writing, customer support, invoice handling, reporting, internal search. That is fine. Ordinary processes with real volume are where AI pays back first.

Check the data before the model

Many AI ideas fail on data, not on the model. Before committing budget, check whether the information the process needs is available, reasonably clean and allowed to be used. A use case that needs six months of data clean-up is a data project first, and should be planned and priced that way.

Run pilots that can actually scale

A good pilot has a named business owner, a clear measure of success, a fixed time limit and a decision at the end: scale, change or stop. It also runs on real work with real users. A pilot that only ever runs in a sandbox tells you very little about what will happen in production.

Set simple rules early

Teams will use AI tools whether there is a policy or not. A short, practical set of rules on what data can be shared, which tools are approved and who reviews outputs reduces risk far more than a long policy nobody reads.

The questions to ask this quarter

If you are deciding where to start, three questions cover most of it. Which two or three processes would benefit most? Is the data for them ready? And who in the business will own the result? If you can answer those clearly, the choice of tool becomes the easy part.