# Make task ownership explicit

Illustrative planning brief; no automatic product import.

Illustrative case: an onboarding email update involves a designer, an engineer and a support lead. Everyone assumes someone else will close the task.

## Decision

Name the engineer as delivery owner and the support lead as acceptance reviewer; confirm both assignments.

## Owned work

- Delivery responsibility
  - Owner role: Engineer
  - Acceptance evidence: Confirms coordination of implementation and a next update date.
- Contributor handoff
  - Owner role: Designer
  - Acceptance evidence: Provides approved copy and explains any wording constraint before implementation.
- Acceptance responsibility
  - Owner role: Support lead
  - Acceptance evidence: Reviews the final email against approved copy and records the decision.

## Workflow

1. Ask who will move the task forward when a contributor is unavailable.
2. Record who may accept the result separately from who implements it.
3. Review the ownership agreement when scope or availability changes.

## Judgment

Do not assign accountability to an absent colleague. This example uses roles; obtain agreement from actual people.


## Illustrative ownership agreement

Outcome: publish the revised onboarding email using approved copy.
Delivery owner: engineer, pending personal confirmation.
Contributor: designer supplies the final copy before implementation.
Acceptance reviewer: support lead checks the rendered email against that copy.
Next check: confirm delivery and reviewer availability before scheduling.
If copy changes: reopen the scope discussion; do not silently update the acceptance boundary.


## Workflow questions

### Can two people own the task?

They can collaborate, but name one person to coordinate delivery and updates. Otherwise unresolved decisions often fall between them.

### Does the delivery owner approve the result?

Only when the team explicitly agrees. A separate acceptance reviewer is useful when another function depends on the outcome.

## Product connection

Confirm who moves the task forward and who approves it before recording responsibility in TeamBoostAI.

Confirm account availability before adopting this manual outline.