ai transformation lead
Builds the architecture of the processes — the structure that keeps the programme organised instead of chaotic.
people
Users become builders — first their own assistants, then power users building for others.
processes
The shared view — bottlenecks everyone knew but never formalised, finally on one map. The conversation about fixing them starts.
context
Richer than SOPs — the how and the why of every process, captured with AI while mapping. The layer that makes every later move cheaper.
capabilities
Assistants multiply — and the layers prove themselves: ECM starts moving from ChatGPT to Claude, quickly, because the context and data are its own.
friction
Where the biggest value hides — problems unsolvable before: too complex, too expensive, too labour-intensive.
data
Mapped bit by bit, process by process — what flows in, what flows out, where it lives. Inefficiencies surface; the first data packs form.
field notes — learned at ecm
slow — and speeding up
Process mapping takes time. The good news: AI is far better at it now — whatever feels slow today will be faster tomorrow.
went wrong — the board's patience
Six months in, the board was losing patience — and when the board loses patience, people lose motivation: "my boss will be mad I spent time on this."
not everything wants automating
People keep the work they love — and there, AI's value is quality, not replacement. That's the offer checker.
less stress, not less work
Nobody ended up with less work — there's always more. But higher quality meant visibly less stress.
wanting ≠ needing
The fleet app was never used — small fleet, Excel was fine. Not wasted, though: it's how the future lead learned to build apps.
