PRODUCT 02 / AI READINESS SPRINT

Find the first move.
Before you fund the wrong one.

Fifteen working days to examine one manufacturing workflow, separate the symptoms from the cause and leave with a decision your team can act on.

You are buying a diagnosis. The recommendation can be an AI pilot, better records, a simpler process or a reason to pause. Implementation is scoped separately.

READINESS SPRINT / WORKFLOW 01 EXAMPLE DIAGNOSIS
15WORKING DAYS

One workflow. One sponsor. One decision worth enabling.

Process visibility68
Data reliability42
Team ownership81
Pilot feasibility57
NEXT DECISIONFix the information hand-off before automating it.
ONE TARGET WORKFLOW15 WORKING DAYSDIAGNOSIS BEFORE AITEAM READY TO OWN IT

Five moves.
One useful decision.

Each phase answers a practical question. The sprint ends with a recommendation, a named owner, evidence to collect and the next decision to make.

  1. 01

    Prepare

    Agree the sponsor, target workflow, access, and the decision the sprint must enable.

  2. 02

    Discover

    Walk the process with experienced and newer team members. Inspect available data and the exceptions each person handles.

  3. 03

    Diagnose

    Separate the root cause from the symptoms and rank possible fixes by value, feasibility, and speed.

  4. 04

    Draft

    Design the first practical solution: better data, a simpler workflow or a bounded AI pilot.

  5. 05

    Handover

    Walk the owner through the recommendation, evidence, success measure and next checkpoint.

Evidence your team
can act on.

OUTPUT 01

Current-state diagnosis

A documented view of how the workflow actually runs, including bottlenecks, dependencies, and data gaps.

OUTPUT 02

Ranked opportunities

A short list prioritised by business value, feasibility, readiness, and time to visible evidence.

OUTPUT 03

A first move ready to scope

A practical design, success measure, named owner and next decision. Dependencies and open questions stay visible.

AI is an option.
Not the answer by default.

A useful sprint distinguishes three paths: build a bounded AI pilot, repair the underlying workflow first, or stop because the value is not there yet.

BUILD THE PILOTFIX THE FOUNDATIONSTOP FOR NOWTHE
EVIDENCE
DECIDES

Bring one workflow
that should work better.