Decision exercise · 10 MIN
Practice a Taiga workflow
Make six decisions for an internal expense app. Learn when to add context, check assumptions, and require human approval.
The situation
You are enabling Taiga for a fictional internal expense app. The walkthrough gives you six decisions, from supplying context to resolving blocked work. Each screen explains the relevant Taiga concept. No Taiga account is needed.
What to do
- Read the situation and choose the next action. Select Check decision to see the reason.
- If needed, change your answer. Continue when the decision is correct. Complete all six decisions to finish.
This exercise teaches Taiga decisions with fictional situations. Your choices affect only this exercise. Use the documentation links below to find the actual Taiga screens.
1 / 6 · Context
Start with shared information
You will build an internal expense service. The organization has a security policy and an approved technology list.
Discovery uses available knowledge and instructions. Shared rules belong at a shared level. Record an undecided question explicitly.
2 / 6 · Conversation
Review the specification before publication
The draft specification says that every employee can view every expense claim. This does not match the requirement.
Downstream documents use the published version. Correct material errors first. An updated specification can mark previously generated documents as Outdated.
3 / 6 · Documents
Check generated assumptions
All eight required documents are published. The data flow includes an external recipient that nobody recognizes.
Publication does not prove that assumptions are correct. Finish Discovery locks the documents. You can reopen Discovery later, but early correction limits the error’s consequences.
4 / 6 · Initiatives
Set the work order
Discovery is complete. The repository is connected and an environment is defined. You want one limited export feature.
Queue starts work when its turn arrives. Taiga handles one initiative at a time per product. Check dependencies: queuing overrides the wait for unfinished dependencies.
5 / 6 · Autonomy
Choose when to review the plan
The team needs to review each plan before building starts. Automatic building is currently enabled.
The Autonomy setting can make a completed plan wait for Approve or Reject. An initiative can override the default. PR approval is separate.
6 / 6 · Needs you
Resolve the cause of an interruption
A build stops because a required permission is missing. The plan remains correct. Some work is already committed.
Resume build continues from the first incomplete step and retains commits. Start over executes the current plan on a fresh branch. Select the action for the actual cause.
Exercise complete
You completed six decisions from Context to a build interruption. In a real product, check its current state, your permissions, and the action’s consequences.
Product behavior sources: Your first product · Discovery · Initiatives
TO FINISH
What does the human still need to decide when Taiga can implement a change?
Compare your answer with the explanation
The human must clarify the intended behavior, verify data handling, and set the allowed autonomy. Published documents still need review. Blocked work still needs the specific missing permission or information. These decisions connect the requested outcome to controlled delivery.
Use this at work
Before enabling Taiga for a product, prepare its intended users, data boundaries, and decisions that require a person.
Choose another exercise