Start with friction
Ask teams where time disappears: repeated document handling, searching for information, reconciling reports, or coordinating the same steps across several tools. Name the process and the person responsible for its outcome before discussing a solution.
Separate possibility from priority
For each opportunity, consider the frequency of the work, the cost of delays or errors, the availability of data, and the consequences of a wrong output. A frequent, bounded workflow with accessible information is often a better starting point than a broad assistant expected to do everything.
Define the baseline
Record how the work happens today. Agree on what you want to improve, how you will measure it, and what must remain under human control. Estimate value using your own operating data and make uncertainty explicit.
Choose a small, complete first step
Your first initiative should be narrow enough to deliver and complete enough to use. Plan for the integration, owner, review process, and ongoing operation alongside the model. The goal is a useful part of the business, not another isolated demonstration.