AI Adoption & Implementation Lead

AI works when the workflow changes.

I turn operational constraints into AI-supported ways of working that people can validate, own and use.

I work between delivery, product and engineering.

I spent 14 years in software delivery before focusing on the gap between AI deployment and real adoption. I shape the intervention with the people who own the work, then test whether the evidence supports scaling it.

Two workflows.
Human decisions.

The graphic below shows what enters each workflow, where AI is used, who validates the output and what changed.

Open the case summary
Source material Context enters a governed workflow

Product delivery

From conversations to a decision the Product Manager can act on.

  1. InputMeeting transcripts
  2. AI useAnswers grounded in source material
  3. Human decisionProduct Manager validates the answer
  4. OutputInitiatives and epics prepared for manual entry
40+ people use the meeting knowledge assistant

Engineering

From repository changes to technical context people can trust.

  1. InputRepository changes
  2. AI useDocumentation drafted from the code
  3. Human decisionEngineers review and rework the draft
  4. OutputDocumentation approved and aligned with code
3 to 30 microservices 30+ engineers using the workflow

Building is one decision.
Stopping is another.

Scale

The workflow has value, evidence and an owner.

Then implementation can move forward with named controls and a measurable next decision.

Stop

Validation costs more than the expected value.

I stopped a separate initiative before adding more technology to a weak value case.

Read why it stopped

Start where the work is stuck.

What would you like to know?

Ask about my work, the evidence behind it, my services or professional background.