How to write a risk or issue
A risk is something that might hurt delivery. An issue is something that is hurting delivery right now. The RAID log is where both live.
Why it matters
Most teams keep risks in a leader's head. The Tenhaw Way puts them in the system, scored, owned, and reviewed quarterly. AI also auto-detects risks from delivery patterns (off-track epics, declining team health, value-at-risk), those land beside the human-raised ones.
Step by step
- Pick the type. Risk (potential), Issue (active), Assumption, Dependency.
- Title: the bad thing you're trying to avoid. "Auth provider rate-limit may block 800+ DAU launch."
- Description: probability + impact + window. "60% likely in next 4 weeks; would block launch by 2-3 days."
- Severity. High / medium / low, based on impact × likelihood.
- Owner. One named human accountable for tracking it.
- Mitigation plan. What you'll do to reduce probability or impact.
- Category. Outcome / delivery / people, drives where it shows up in dashboards.
- Status. Open → In progress → Mitigated → Closed (with reason).
What good looks like
- Probability + impact + time-window stated
- One owner
- Concrete mitigation plan
- Reviewed quarterly minimum
- Closed with a reason, not just deleted
How Tenhaw runs this
AI auto-detects risks from delivery patterns (off-track epics, value-at-risk, declining team health) and opens RAID rows alongside human-raised ones. Open high-severity risks surface in the Outcome Coach's weekly briefing as the leader's "decision needed". They don't quietly stale.
- Tenhaw RAID Logs
- Tenhaw AI risk detector
- Tenhaw outcome rollup
- Tenhaw Outcome Coach
In Tenhaw → RAID Logs. AI-detected risks appear with an "ai_detected" source tag and need human triage to confirm.
Run this in your team
The Tenhaw product enforces every rule in this playbook so it doesn't sit on a wiki gathering dust. Try Tenhaw or book a working session with the founder.