# Customer parallel onboarding tracks

Illustrative planning brief; no automatic product import.

Illustrative case: Two customer groups need different introductory sessions but share one readiness reviewer.

## Decision

Run separate learning tracks with one explicit review queue.

## Owned work

- Separate track requirements
  - Owner role: Onboarding coordinator
  - Acceptance evidence: Each group has a distinct first exercise.
- Reserve reviewer windows
  - Owner role: Customer enablement contributor
  - Acceptance evidence: The shared reviewer confirms feasible slots.
- Accept track outcomes independently
  - Owner role: Customer readiness reviewer
  - Acceptance evidence: Each group receives its own readiness decision.

## Workflow

1. Define the first sample exercise for each customer group and the evidence each must provide.
2. Reserve feasible review slots with the shared reviewer and communicate which track enters each slot.
3. Issue separate readiness decisions and keep any blocked track open without delaying an already accepted independent outcome.

## Judgment

A shared reviewer creates a scheduling dependency rather than identical training needs.


## Filled illustrative planning example

Synthetic queue: group A reviews a daily summary at 10:00; group B reviews exception classification at 11:00. The shared reviewer accepts A but asks B for one more example. A is ready; B remains pending.


## Workflow questions

### Must both groups finish together?

No, unless the agreed operating outcome requires it

### How is reviewer overload avoided?

By confirming distinct review windows before scheduling

## Product connection

Adapt the stage tasks, owner roles and acceptance evidence to your TeamBoost planning workflow. The example does not create customer records or import an onboarding plan.

Confirm account availability before adopting this manual outline.