# Turn an outcome into an initiative

Taiga Learning · Worksheet
https://taiga.training/en/lessons/taiga-initiatives/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Write an outcome, reason, and bounded scope for an initiative.
- Explain the difference between Backlog, Todo, Queue, and Build.
- Recognize the authority implied by queue order and plan approval.

## Exercise
For the fictional equipment service, request employee self-service. Write the end state, why it matters, scope, exclusions, and acceptance evidence. Identify any required identity change before placing it in Queue.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
An initiative describes the outcome. Its plan describes implementation. Queue placement is a decision to start work in the order you specify.

## Sources
- [Taiga docs: Initiatives](https://docs.tai.ga/deliver/initiatives/)
- [Taiga docs: Write intake agents can act on](https://docs.tai.ga/agents/write-intake-agents-can-act-on/)

This worksheet supports learning. Completing it does not itself authorize a production change.