Transition & Nemawashi
Synced from Asana (20 Jul 2026): Nemawashi & Transition Report, Team Transition & Readiness Programme, AI operating parameters. Door-opener view — not a live readiness tracker.
Nemawashi means prepare people before change
The funded product must prove staff, partners and young-person continuity are ready with evidence — not just that training was sent. This page explains the rules so demos can talk about adoption honestly. The prototype itself is not a go-live gate.
Ten Nemawashi principles
Understand why, what changes, what stays the same, and how support works — before go-live.
Stakeholders influence the design while change is still possible.
Concerns and practical knowledge are heard before final calls.
Silence is not agreement. Objections stay visible until addressed or formally accepted.
Everyone who contributes is told what happened to their input.
No interrupted support, ownerless Needs, weaker safeguarding, or forced re-telling of stories.
Not ready → training, tools, time, coaching — not shame.
Ready means demonstrated understanding and practice — not “they were sent a slide deck”.
AI may help assess readiness; people approve transition.
Every transition improves the Blueprint for the next programme.
Readiness areas (assess before go-live)
Each area gets a status: Ready · Ready with conditions · Not ready · Not assessed · Not applicable. Gaps that block transition stay visible — not buried in a backlog.
| Area | What “ready” means |
|---|---|
| People readiness | Staff understand roles, decisions, escalations and new ways of working. |
| Young-person readiness | Continuity of support; communication plan; no ownerless Needs. |
| Partner readiness | Referral partners know how to hand off and get updates. |
| Process readiness | Lifecycle, forms, RACI and exception routes are practised. |
| Technology & data readiness | Systems, access, data quality and fallback routes work. |
| AI Specialist readiness | Boundaries, labels, handover and suspension tested. |
| Safeguarding & compliance | Risk routes, DPIA/retention rules, coverage at go-live. |
| Governance readiness | Sponsors, approvals, reporting and change control clear. |
Team transition programme (what staff get)
- Why the OS is changing — and what stays the same
- Role-based pathways (not one generic briefing for everyone)
- Practice: handovers, escalations, exceptions — before go-live
- How to work with technology, automation and AI Specialists
- Where to get help during transition and early operation
- Individual/team readiness sign-off with extra support if not ready
Protect young people: transition must never leave a Need without an owner or weaken safeguarding coverage.
AI operating parameters (control layer)
From Asana: every AI Specialist is a controlled capability. If any of the questions below is unclear, it is not ready for configuration or release.
An AI Specialist may not expand its own role, grab extra data, or act outside its approved purpose without formal change control.
Each AI is restricted to approved Need Lifecycle stages — not “anything on the same person”.
Outputs are labelled e.g. AI recommendation, risk indicator, quality finding — never as a final authorised decision.
Stop and hand over on risk of harm, prohibited decisions, uncertainty, conflicting evidence, or when a human is requested.
Any AI can be immediately suspended if boundaries fail, audit is missing, or safety requires it.
Every AI must be able to answer
- What is my approved purpose?
- Who am I serving?
- What capability am I providing?
- What information may I use?
- What actions may I take?
- What decisions may I recommend?
- What decisions am I prohibited from making?
- When must I stop?
- Who must take over?
- What record must I create?
- Who remains accountable?
- How will my work be reviewed?
Release statuses
See 18 AI Specialists in the directory → · Young person interaction rules →
How this links to the door-opener demo
- The app shows the operating model (Needs, specialists, processes).
- Nemawashi / readiness is the people plan for when (if) a funded implementation goes live — not something this prototype tracks for real staff.
- In a pitch: “We designed how people are prepared — not just the screens.”