# Customer milestone evidence choice

Illustrative planning brief; no automatic product import.

Illustrative case: A customer marks orientation attended as implementation complete.

## Decision

Separate attendance from demonstrated operational readiness.

## Owned work

- Inspect milestone wording
  - Owner role: Onboarding coordinator
  - Acceptance evidence: Attendance and readiness are distinguished.
- Define a practical demonstration
  - Owner role: Customer enablement contributor
  - Acceptance evidence: The customer completes one representative workflow.
- Agree the completion label
  - Owner role: Customer readiness reviewer
  - Acceptance evidence: Both contacts accept the milestone meaning.

## Workflow

1. Replace the ambiguous implementation-complete label with separate orientation and operating-readiness milestones.
2. Ask the customer to complete one representative synthetic workflow and retain the observed result and remaining support needs.
3. Have both contacts agree the milestone meaning; record a hold when the required demonstration has not occurred.

## Judgment

Do not equate a meeting with a customer outcome.


## Filled illustrative planning example

Synthetic milestone record: orientation attended, yes; sample report workflow demonstrated, no; operating readiness, pending. The next action is a supervised demonstration, not a blanket implementation-complete label.


## Working artifact

- Orientation attended / Customer confirms the session and its limited purpose. / Keep attendance pending; do not substitute a calendar invitation.
- Operating workflow demonstrated / Customer completes the representative sample with the agreed result. / Record the missing step and arrange support; readiness stays pending.
- Milestone meaning agreed / Both contacts confirm which result the completion label denotes. / Clarify the label before reporting implementation complete.


## Workflow questions

### Is attendance worthless?

No, it proves participation rather than operational readiness

### Can the milestone be renamed?

Yes, preserve the old meaning in the transition note

## 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.