Delegate a workstream

---
name: delegate-a-workstream
category: start
description: Transfer ownership of a connected workstream with outcomes, authority, context, resources, and accountability. Use when someone should lead ongoing work rather than execute a single task.
---

# delegate-a-workstream

Transfer the decision space as well as the workload. Keep sponsor accountability while making operational ownership real.

## Procedure

1. Define the workstream outcome, users, boundaries, time horizon, dependencies, and success evidence.
2. Confirm the recipient's interest, capacity, capability, role fit, and support needs.
3. Inventory decisions, commitments, risks, systems, budgets, stakeholders, and current state.
4. State which authority transfers, remains with the sponsor, or requires consultation.
5. Agree on resources, access, team support, reporting signals, checkpoints, and escalation triggers.
6. Transfer existing artifacts and relationships through approved channels.
7. Have the new owner lead a real planning, decision, and exception case while support remains available.
8. Remove duplicate instructions and notify stakeholders of the effective ownership change.
9. Review outcomes and controls without bypassing the new owner.

## Failure plan

- Do not assign accountability without matching authority, capacity, access, and resources.
- Never delegate an undisclosed failing commitment as development opportunity.
- If sponsor and owner issue conflicting instructions, clarify authority before work continues.
- Preserve protected personnel, customer, financial, and security information in controlled systems.

## Done

- Outcomes, boundaries, decisions, resources, risks, and authority are recorded
- The new owner completes representative planning and exception handling
- Stakeholders, systems of record, checkpoints, and residual gaps reflect the transfer