A mixed team around a table, writing on sticky notes and documents together.

The Many Hands Toolkit

A toolkit for every hand in the team.

These aren’t documents you buy. Your teams build them, around their own roles, paths and AI tools. The Many Hands framework gives them the structure: how to work together, how each person gets the most from AI as their role changes, and how to measure that outcomes improve.

What I offer, and what your teams build

The framework (what I bring)

  • A structure for shared governance
  • Role paths for each role
  • Facilitated team sessions
  • Starter templates
  • The measurement model (baseline → follow-up, five KPIs)

The toolkit (what your teams build)

  • Their own guidelines and examples
  • Review checklists for their products
  • Their team agreement
  • Override and gap logs
  • Guidance for their own AI tools

The framework stays the same across the company. Each team’s toolkit is its own.

How the toolkit grows

How the toolkit grows Many Hands framework Structure · role paths · team sessions · starter templates · measures What I bring same structure Built by each team Team A Their toolkit Team B Their toolkit Team C Their toolkit Their products and AI tools Reviewed, owned and corrected by the people who do the work. Gaps and good practice flow back into the shared core How the toolkit grows What I bring Many Hands framework Structure · role paths · team sessions starter templates · measures same structure Built by each team Team A Their toolkit Team B Their toolkit Team C Their toolkit Their products and AI tools Reviewed, owned and corrected by the people who do the work. Gaps and good practice flow back into the shared core

Same framework everywhere. Each team’s toolkit is its own.

Read the diagram as a list

  1. Many Hands framework. What I bring. Structure, role paths, team sessions, starter templates, measures.
  2. The same structure reaches Team A, Team B and Team C. Built by each team.
  3. Each team holds its four roles and its own toolkit.
  4. Their products and AI tools. Reviewed, owned and corrected by the people who do the work.
  5. Gaps and good practice flow back into the shared core.

Governed by the people who do the work

Governance isn’t a separate team checking from the outside. It’s the people doing the work, acting as they agreed they would.

  1. A mixed group sits in a circle and talks. Agree In the team session, each role agrees what it checks, when it steps in and who it hands to.
  2. A woman at a desk talks on the phone and writes notes. Act When an AI output is wrong or a case doesn’t fit, people react the way they agreed: pause, override, escalate, fix.
  3. A team smiles together in front of a whiteboard. Recognise Teams see the benefit: fewer errors, faster fixes, less blame. And they update their toolkit with what they learned.

The agreement improves every time

Example: Sabine, the caseworker, sees a wrong AI answer. She overrides it and records why, exactly as her team agreed. The team reviews the log, sees the same issue three times, and changes the rule.

See it in: The Case That Doesn't Fit →

People follow rules they wrote themselves.

What teams build with the framework

  • Shared core library

    Built by the team

    Guidelines your teams write and share, the same core for everyone.

  • Role paths

    Built by the team

    Each role shapes its path from its own work.

  • Scenario quizzes

    Built by the team

    Built from the team’s real cases. They diagnose, not grade.

  • Team agreement template

    Built by the team Starter template

    Who checks, decides, escalates and fixes. See an example →

  • Product review checklist

    Built by the team Starter template

    The questions your team asks before an AI change ships.

  • Override and gap log

    Built by the team Starter template

    Where people stepped in, and where guidance was unclear.

Your AI tools are part of it

Copilots, agents and assistants aren’t separate from this. Each team decides how its AI tools fit each role: what the agent does, what people check, what people own. That decision goes into the toolkit too.

Your agentic self →

Better outcomes, measured

  • For each person

    Confidence and capability as their role changes.

  • For the team

    Clear owners, fewer gaps between roles.

  • For the people they serve

    Fewer errors, and a person to reach when something goes wrong.

How the pilot measures it →

Built on established guidance

How the Many Hands Toolkit relates to Microsoft HAX and Google’s People + AI Guidebook.
Microsoft HAX (external site) Google People + AI Guidebook (external site) Many Hands Toolkit
Focus How an AI product should behave towards people Designing human-centred AI products A framework teams use to build their own toolkit, around their roles, paths and AI tools, governed by the people who do the work.
Format 18 guidelines, patterns, workbook, playbook 23 patterns, 6 chapters with worksheets, case studies, workshop kit Core library, role paths, team agreement, review checklist
Who it’s for Product teams UX and product teams Every role, including frontline staff
What it covers The product’s behaviour with people Human-centred product design Review, ownership and correction across the team
What it adds — — Ownership, rehearsal and the right to stop

HAX and PAIR help teams design better AI products. The Many Hands Toolkit helps the whole team use that guidance together, with clear owners for every step.

Want to build your team’s toolkit?

Get in touch