What I've learned

AI makes a good process faster. It makes a bad process faster too.

The teams who get real value from AI aren't the ones with the most tools. They're the ones who fixed the process first, then let AI remove the repeatable parts of what was left.

Connect with Clare
Follow the thread to see where the work starts, what changes, and how the evidence becomes useful.

How service improves, in four stages:

01 Notice02 Connect03 Change04 Prove

What I've learned

If a process is confused, automation doesn't fix the confusion — it just moves it faster. I've seen AI initiatives struggle not because the technology was weak, but because it was pointed at a process nobody had actually agreed on yet.

Common mistakes

Automating the exception-handling instead of the repeatable work. Good uses of AI include summarising notes, spotting repeated themes, drafting clear updates, and routing common requests — not replacing the judgement calls that need a person who understands the customer.

Practical approaches

Start with what's repeated: updates, checks, triage, reports, reminders, handovers. Keep people in charge where empathy, context, or trust matters. Then measure honestly — are customers getting clearer help, and are teams actually spending less time on repeat work, or just looking busier?

See the evidence behind this thinking
Try the calculator

See what recurring IT issues are really costing you.

Enter monthly tickets and average resolution time for each issue type to see a ranked breakdown — useful evidence for prioritising the IT roadmap.

Open the IT lost time calculator
Selected Briefings

Read the thinking behind the work.

Explore every Briefing ↗
Connect with Clare

Continue the service conversation.

For senior leadership opportunities, transformation programmes, industry collaboration, and conversations about improving service.

hi@clarelangley.com