Operations

The Operations view is where your team tracks the things that can derail delivery: risks that need monitoring, decisions that need to be preserved, and dependencies that cross project boundaries.

Before you start

• All project members can view Operations records.
• To create or update records, you need at least a Member role.
• Risks, decisions, and dependencies can also be created automatically when a ritual session is completed with outcome records (see /docs/guides/run-a-ceremony).

Steps

View the operations health summary

1. Open your project and click Operations in the project sidebar.
2. Three health cards at the top summarise the current state:
   • Open risks — risks not yet closed, needing mitigation or monitoring.
   • Pending decisions — proposals awaiting a final decision.
   • Active dependencies — dependencies across work and projects that are not yet resolved.

Record a risk

1. Make sure the Risks tab is active (it is the default).
2. Click New risk in the top-right area.
3. In the "New risk" modal, fill in:
   • Title — a concise description of what could prevent delivery.
   • Context — background information (Markdown supported).
   • Probability — Low, Medium, or High.
   • Impact — Low, Medium, or High.
   • Mitigation — the plan to reduce or monitor this risk.
4. Click Create.
5. In the risk list, use the Status dropdown on each row to advance the risk through: Open, Monitoring, Mitigated, or Closed.

Record a decision

1. Click the Decisions tab.
2. Click New decision in the top-right area.
3. Fill in:
   • Title — the choice that needs durable context.
   • Context — why this decision arose.
   • Options considered — the alternatives that were evaluated.
   • Proposed decision — the chosen direction.
4. Click Create.
5. In the decision list, use the Status dropdown to move the decision from Proposed → Decided → Superseded.

Record a dependency

1. Click the Dependencies tab.
2. Click New dependency in the top-right area.
3. Fill in:
   • Title — what work is blocked or blocking.
   • Source work — choose a work item from this project, or leave as "Project-level".
   • Target project — the project this dependency links to.
   • Relationship — blocks, depends on, or relates.
   • Notes — any additional context.
4. Click Create.
5. In the dependency list, use the Status dropdown to set: Open, At risk, or Resolved.

Discuss a record

1. Click the discussion button (the comment icon) on any risk, decision, or dependency row to open the collaboration panel. Add comments, @mention teammates, and subscribe to digest notifications.

Result

Risks are tracked with probability and impact ratings and advance through mitigation. Decisions are preserved with context so the team does not re-litigate settled choices. Dependencies are visible so blockers surface during planning rather than at release.