Skip to content
UCD Bots
Lead

UCD Lead

Orchestrates discovery → live across ten specialist teammates. Briefs by remit and phase (GDS team shape + RACI-style routing). You approve every gate; specialists keep the craft.

Open in GrokSave bot card

Third-party UCDOps template on Grok Bot — not created or endorsed by xAI.

Works in

Lead

Status

Available on Grok Bot

What it does

UCD Lead is the pipeline orchestrator for User Centred Design. It briefs ten specialist teammates by remit and phase (GDS team shape + RACI-style routing), assembles evidence trails and exit packs, and pauses for your approval at every gate.

  • Pipeline orchestration across discovery, alpha, beta, and live
  • Briefs the right specialists with the goal, evidence, constraints, and success criteria
  • Synthesises teammate outputs into one evidence trail
  • Holds evidence trails across specialists — data → findings → insights → recommendations → decision — and labels breakage risk when adoption is unknown
  • Draft artefacts stay labelled draft until a person approves them: research plans, problem statements, journeys, hypotheses, stories, content drafts, prototype briefs, phase exit packs, assessment packs, and Listen / continuous-improvement outlines
  • Proposes phase RACI and routing tables — always labelled draft pending human approval
  • Stages artefacts for human approval without shipping them

What it does not own

  • Does not own specialist craft judgement — that sits with User Researcher, UX Planner, UX Designer, Interaction Designer, UI Designer, Content Writer, Business Analyst, Product Designer, Prototype Designer, and Accessibility Expert
  • Does not own final sign-off, spend, or service assessments
  • Does not own policy or legal authority
  • Does not ship or publish without human approval
  • Does not declare a service ready for live or finished without the service owner’s decision
  • Does not assign by availability instead of remit
  • Does not invent findings, prototype without a UX Planner handoff, or present a fixed organisation-wide RACI as GDS guidance

Role boundaries follow NN/g · GDS · DDaT.

How you work together

Inputs

  • A decision to inform
  • Existing evidence, if any
  • Known constraints and success criteria
  • Which specialists are in the workspace (or consent to add them)

Outputs

  • A staged orchestration of the pipeline
  • Remit- and phase-based specialist briefs and synthesised stage packs
  • Draft artefacts, always labelled draft
  • Evidence trails linking claims to sources
  • Proposed phase RACI and routing tables, labelled draft pending human approval

Human gate

Every stage pauses for you, including: discovery goal and problem definition; research ethics and sampling; discovery exit (proceed, stop, or reframe); alpha assumptions and prototypes; alpha exit (proceed to beta, stop, or repeat); private beta invite criteria and ethics; private to public beta (including accessibility fixes before open); accessibility audit and statement publication; assessment readiness; beta to live; material live changes with exclusion risk; continuous-improvement staffing or metric choices that change user-facing behaviour; external publication; and retirement or reshape when need or cost-effectiveness collapses.

How the lead uses teammates

  1. Name the decision or craft job (not the person).
  2. Brief the remit owner first — one lead per craft job.
  3. Consult adjacent specialists only when the phase or evidence needs them (GDS phase team guidance + NN/g Consulted/Informed).
  4. Wait for craft output → synthesise into the pipeline pack → pause for the human gate.
  5. Fan out in parallel only when you ask or the stage genuinely needs it.

Phase hint (from GDS, summarised): discovery leans research + service design + product skill; alpha adds content, designers, accessibility lead, and must appoint a service owner; beta and live scale designers, content, and ops-adjacent skills as the service hardens.

Ten-specialist family (product roles, not people): research, planning, UX, interaction, UI, content, BA, product, prototype, accessibility.

Need the full pipeline?

UCD Lead orchestrates; the ten specialists keep the craft.

Public install index: https://www.ucdbots.com/bots (also https://ucdbots.com/bots).

Install each specialist from its page with Open in Grok, then accept third-party terms on x.ai.

Where it sits

UCD Lead orchestrates; each specialist owns their craft. You keep the approval.

In the family

Routes work by remit — one craft lead per job.

Get UCD Lead

Open in GrokSave bot card
Third-party UCDOps template on Grok Bot — not created or endorsed by xAI.

These teammates are third-party Grok Bot templates, built and operated by UCDOps — not created or endorsed by xAI. Once added, a bot may act on your behalf. Adding it means accepting Grok Bot's third-party bot-sharing terms on x.ai. That consent step happens on x.ai after you click through.