---
name: "playbook-fractional-leader-onboard"
type: playbook
description: The prescribed sequence for embedding a fractional design leader into a client team and keeping the engagement moving — fix the role and remit, secure access across the technical, strategic, culture and interpersonal dimensions, and agree the cadence and the client's response terms before delivery starts. Read and followed, not run. Use it while scoping a fractional or advisory engagement and again with the client team once the contract is agreed, so access and response times are an agreement rather than something discovered after signature. Sits after playbook-client-onboard, which scaffolds the engagement, and beside playbook-engagement-kickoff, which runs the diagnostic; this one governs the working relationship those two assume.
license: CC BY-NC-SA 4.0
status: proposed
---

# Embedded fractional leader onboarding

The working agreement between a client team and a fractional design leader embedded in it: what the leader is for, what the team owes them, and how fast. It is **read and followed, not run** — it composes governance and judgement and calls no behaviour of its own (`core-operating-model`, Layer 5).

It exists because the terms it fixes are currently re-derived per engagement and only tested after signature, when the cost of a slow answer lands on the leader's weeks rather than the client's.

## Where it sits

Three playbooks cover one engagement and do not overlap:

- `playbook-client-onboard` — the **scaffold**: project, decision log, milestone spine, first ticket, dependency gate. Run it first; it is A1's setup sequence and this playbook does not restate any of it.
- **This playbook** — the **working relationship**: role, remit, access, cadence, response terms. It is the thing the other two assume and neither states.
- `playbook-engagement-kickoff` — the **diagnostic**: Sonar's Finding → Theme → Opportunity → Initiative sequence once the leader is working. Run it inside the cadence this playbook fixes.

## When to use

Any engagement where the leader works **inside** the client's team rather than delivering to it from outside — a fractional design lead, a design director on retainer, an embedded advisory seat. Not for a fixed-deliverable build, where the contract is the agreement and this adds nothing.

Use it twice: **while scoping**, as the terms being asked for; and **at kickoff**, read through with the client team.

## 1. Fix the role and remit

Write it down before the first working session, in three parts, in the engagement's decision log (`convention-decision-log`):

- **What the leader decides.** The design decisions that do not come back to the client for approval — direction, craft, sequence within an agreed scope. State it as a positive grant, not an exclusion list.
- **What the leader recommends.** Where the leader produces the recommendation and the client rules — spend, hiring, roadmap commitments, anything with a cost the client carries.
- **What the leader does not own.** Line management, delivery capacity, and anything the client's own leads hold. An embedded seat that is read as a hire is the common failure; naming the boundary once is cheaper than correcting it per meeting.

Name the client-side **counterpart** — one person who can unblock access and answer a scope question — and say what happens when they are unavailable.

## 2. Secure access, across four dimensions

Access is the engagement's rate limiter and it has four faces, not one. Each gets a named owner and a date, opened as gate leaves on the board in the shape `playbook-client-onboard` step 5 already prescribes (`convention-ticket`, *Obligations belong in structure, not prose*; APP-1443). A dimension with no named owner is the finding.

- **Technical** — repositories, design files, the analytics and data the work is judged against, environments, and whatever single sign-on gates them. Nothing here is a favour; it is the instrument.
- **Strategic** — the goals the work serves, the commercial constraints, the roadmap as it actually stands, and prior work that has already been tried and rejected. A leader without this re-proposes what the team discarded last quarter.
- **Culture** — how the team already works: its rituals, its decision forums, where work is reviewed, and what it is proud of. The leader joins an existing operating rhythm or competes with it.
- **Interpersonal** — who the leader needs a direct line to, who is sceptical of the engagement and why, and who is affected by it without being in the room.

State the **office and email position** explicitly. An embedded leader on an external address, outside the team's channels, is a visitor; say which systems the leader is inside and which they are not, and treat each exclusion as a named constraint on what can be delivered.

## 3. Agree the cadence

The cadence is the engagement's spine and is agreed, not drifted into:

- **Onsite presence** — a stated minimum, in days per week, with the days named. Where onsite is not possible, name the synchronous substitute and its length; "as needed" is not a cadence.
- **Check-ins** — a short standing session with the counterpart, for unblocking rather than reporting.
- **Planning sessions** — the recurring session where the leader and the team's leads set the next period's work.
- **Roadmap review** — the longer-horizon session where direction is revisited against the goals from step 1.

Each gets an owner, a length and a frequency. A session nobody owns is not scheduled.

## 4. Agree the response terms

The terms that make the cadence survive contact. These are the part most often left unsaid and the part that decides the engagement's pace:

- **Turnaround on feedback** — the working days within which the client responds to a shared recommendation, route or design.
- **Turnaround on access** — the working days within which a named access request is granted or refused.
- **Rescheduling** — what happens when a session is pushed: rebooked within the same week, or the dependent work slips and is recorded as slipping.
- **The consequence of silence.** State what the leader does when a term is missed: proceed on a stated assumption and log it, or stop and record the engagement as blocked. Pick one per class of decision. A term with no consequence is a preference.

Record a missed term against the engagement's dependency gate the day it is missed, not at the review. An engagement discovers its own pace only if the misses are written down while they are cheap.

## 5. Review the terms with the team, not only the signatory

The contract is agreed with one person; the terms are honoured by a team. Read sections 1 to 4 through with the people who will actually supply the access and the feedback, and amend what they say is unrealistic before it is signed off rather than after. A term the team has not heard is not an agreement.

## Guardrails

- **Agree before delivery, not during.** The terms are scoping material. Negotiating access in week three is the failure this playbook exists to prevent.
- **Compose, don't duplicate.** Gate shape comes from `convention-ticket`, the log from `convention-decision-log`, the engagement scaffold from `playbook-client-onboard`. This playbook points at them and does not restate their rules.
- **Name the constraint, don't absorb it.** Where the client declines a term, record it as a named constraint on delivery rather than quietly working around it.
- **Client-facing materials are not canon.** Any deck, checklist or leave-behind built from this playbook is a downstream rendering and delivery work in its own right; this artefact is the source and is edited here (APP-2719).
- **Proposed.** A first draft against one live engagement; confirm the shape before treating it as adopted.

## Tone

Calm, precise, sentence case, British spelling, no exclamation marks, outcome before adjective. (cos.tov.)
