The first question is often how to use AI to do an existing task faster. I want teams to ask another question as well: if we designed this work today, what would we do differently?
Experience in enterprise architecture and transformation is useful here. It helps explain why the current process exists and which constraints still matter. Building with AI adds a different perspective on what the solution could be.
Give people room to question the brief
A request for a faster report may conceal a need for an earlier decision. A drafting task may be better approached as a structured review of the evidence. Let the team examine the outcome before committing to the current format.
This takes leadership support. People need permission to remove steps, test a smaller solution and show that an attractive idea does not work. They also need clear boundaries around data and decisions.
Learn on work that matters
Choose a real task with someone who understands what good looks like. Build alongside them. Compare the result with the current method, including the time spent checking and correcting it. Look at whether the outcome is more useful as well as whether it is faster.
That experience gives people a basis for judging the next opportunity. A general training session can introduce the tools, but the working habits develop through repeated use and feedback.
Make the better method available to others
Save the instructions, examples and quality checks that made the solution useful. Give them an owner. Let colleagues reuse and improve them through the approved delivery path.
A reusable AI skill is one part of this. Equally important is the habit of explaining the task clearly, challenging assumptions and checking the output against evidence. Those habits help the business make use of new tools as they develop.
Measure the change in the work
Look for better turnaround, less rework and more consistent results. Ask where released capacity has gone. These measures give leaders a clearer view of progress than usage counts alone.
An AI-first culture becomes tangible when a team can explain what it changed, why the new approach is better and how the next team can use it.