Skip to main content

Navigating from 0 → 1with AI teammates

One lead navigator — design, delivery, and AI inside the work from day one.

One lead. One line. Sprint velocity.

Continuity

Discovery → Beta, one lead throughout

The same lead stays with the programme from the first research conversation through to a Beta that can be assured.

Line

Policy to pixel, one line

Business requirements, policy intent, and the interface that ships stay on a single line — no handoff fog between strategy and craft.

Velocity

AI-augmented sprint velocity

Synthesis, patterns, and documentation move at sprint pace because AI specialists sit in the workflow, not in a side tool.

Programme experience

Delivered across government and regulated-sector programmes, from Discovery through Beta.

  • GOV.UK
  • Foreign, Commonwealth & Development Office
  • UK Export Finance
  • Department for Energy Security and Net Zero
  • Home Office
  • HM Revenue & Customs
  • Ofgem
  • NHS
  • Avis
  • Canon Medical Systems
  • Velux
  • BMW
  • Nationwide
  • Vodafone
  • Virgin Media O2
  • Travelex
  • Pay by Bank
  • British Airways
  • Scottish Government
  • Fiserv

The problem it's built to fix

Programmes stall when leadership and craft are split — and when AI is an accessory.

Most programmes lose momentum in one of two ways: a lead too far from the work to unblock it, or a maker too deep in the pixels to steer the programme.

AI tooling gets purchased and parked beside the process, so the double diamond still waits on handoffs. Research sits in a deck. Design waits for a brief. Delivery guesses at intent.

ucdpilot is built to close both gaps at once: a pilot that is in the work and above it, running an operating model where AI teammates carry the repetitive synthesis so the programme keeps moving.

The method

The double diamond, piloted

Each stage is held three ways at once: the UCD activity, the leadership work that keeps the programme moving, and the AI teammate embedded in that loop.

Discover

Find the evidence.

UCD
Field research, interviews, contextual inquiry, and the evidence base that frames the problem.
Leadership
Hold the policy or business question, align sponsors, and set what the programme is actually asking.
AI teammate
Transcript synthesis, theme clustering, and evidence tagging so findings surface in days, not weeks.

Define

Name the problem.

UCD
Synthesis, problem framing, opportunity definition, and the maps that make the problem shareable.
Leadership
Prioritise the problem space, lock the outcome, and brief the next diamond with a decision, not a wish list.
AI teammate
Pattern extraction, journey clustering, and option comparison against the evidence already in hand.

Develop

Make and test the response.

UCD
Journeys, prototypes, critique, and iterative testing against real users and real constraints.
Leadership
Sequence the work, unblock the team, and keep every artefact tied back to the policy or commercial intent.
AI teammate
Pattern-library support, documentation drafts, and variant exploration that the team can judge, not rubber-stamp.

Deliver

Ship a Beta that can be stood behind.

UCD
Interface specification, content, accessibility, and the Beta artefacts that can stand up to assurance.
Leadership
Walk stakeholders through the line, close the gaps, and get the programme Beta-ready.
AI teammate
Spec drafting, checklist generation, and change logs that keep the evidence trail intact at ship speed.

How the pilot shows up

The role is leadership plus velocity — not a catalogue of isolated crafts. Each card is a way the pilot holds the programme, not a service sold off a menu.

Discovery & policy framing

Start with the real question.

Turn a policy need or business brief into a researchable problem. Frame what must be true before anyone opens a file.

Service design & journey mapping

See the whole service, not the screen.

Map the journeys, handoffs, and failure points so the programme designs the service — not just the next interface.

Design leadership & team embedding

In the work and above it.

Set direction, raise the bar in critique, and stay close enough to unblock delivery without becoming a bottleneck.

AI-augmented delivery pipelines

Teammates in the loop, not a bolt-on.

Put AI specialists into research, synthesis, pattern work, and documentation so the diamond keeps turning.

Also within scope: Design ops & pattern governance · Stakeholder & programme navigation · Beta-readiness & assurance · Coaching AI-fluent design teams

The differentiator

An AI-first operating model inside the double diamond — not beside it.

ucdpilot treats AI teammates as embedded specialists in the research, synthesis, pattern, and documentation loop. They draft, cluster, extract, and prepare. The lead judges, frames, and decides.

That split is the point. Velocity comes from removing the wait between a session and a usable finding, between a journey and a shareable map, between a decision and the spec that follows it. Rigour stays with the human who owns the line.

The tools are described by function, not by product name: copilots for synthesis, pattern extraction, journey support, and the paper trail a programme needs when it is asked to show its working.

A programme cadence, not a personal diary

The week is a loop the programme can see — brief, make, show, steer. Stakeholders get a visible outcome; the team gets a decision, not another status meeting.

Brief

Open the week with a question.

A framed problem, a named audience, and the decision the week is meant to unlock.

Make

Craft and leadership in the same week.

Research, synthesis, design, and the stakeholder work that keeps the line intact — with AI teammates carrying the repetitive pass.

Show

Put something in front of the room.

A journey, a prototype, a finding, a recommendation. Evidence the programme can react to, not a slide about activity.

Steer

Close with a decision.

Lock the next question, drop what is not earning its place, and brief the following week before momentum leaks.

Tools & practice

Categories the pilot works in — not a personal kit list.

Design tooling

Interface, systems, and the files a team can inherit without a guided tour.

Prototyping kit

Fidelity matched to the question: from paper-fast to something a user can actually try.

GOV.UK-standard frameworks

Service-standard thinking, accessibility, and content patterns that stand up in regulated programmes.

AI copilots

Synthesis, clustering, pattern extraction, and documentation support sitting inside the week, not after it.

Brief the pilot

Hiring managers and recruiters — send the opportunity as it stands: the role, the stage, and the outcome you need. DM us on 𝕏 to start the conversation.