RAID Log — Personal Training OS
Artifact: 1.1 (Phase 1 — Planning) · Owner: Delivery Manager (Primary User)
Version: v1.0 · Date: 2026-07-04 · Cadence: living — reviewed each work session
RAID = Risks (might happen), Assumptions (taken as true, unverified), Issues
(already happening), Dependencies (needs from/to others). It's the PM's radar. In industry
this is typically a spreadsheet; here it's versioned Markdown.
Scoring: L/I = Low/Med/High. Priority = L×I.
Risks
| ID |
Risk |
L |
I |
Pri |
Owner |
Mitigation / response |
| R1 |
★ Won't actually use it → OS goes stale |
M |
H |
High |
Primary User |
Automated/low-effort capture (SC2); MVP usable by race week for early value; track >7-day staleness |
| R2 |
★ Automations aren't compatible with Notion |
M |
H |
High |
Primary User |
Automation-ready design; spike a thin slice early; integrations gated separately |
| R3 |
★ A desired sync source is paywalled |
M |
M |
Med |
Primary User |
Per-source cost/access assessment; manual/CSV fallback; no hard dependency on one paid source |
| R4 |
★ "Design never ends" (scope creep) |
H |
H |
High |
Primary User |
Bounded v1 (Charter §5); time-box to race week; change control; MoSCoW discipline |
| R5 |
★ Notion is the wrong UI |
L |
H |
Med |
Primary User |
Early mobile usability check in Build; data API-portable (exit path) |
| R6 |
Data loss — no backup of health/training data |
M |
H |
High |
Primary User |
Backup/recovery plan (6.3); scheduled Notion export before go-live |
| R7 |
Privacy — 2 people's health data (+ future integrations) |
L |
M |
Low |
Primary User |
Privacy note (3.4); least-data; review Notion share settings |
| R8 |
Notion formulas/rollups can't express required logic (hockey counts, shoe mileage) |
M |
M |
Med |
Team |
Validate the key formulas first in Build (proof spike) before building around them |
Assumptions
| ID |
Assumption |
Impact if false |
Validate by |
| A1 |
Notion Business plan with 2 seats is acquired |
No 2-person use (SC3 fails) |
Phase 1 |
| A2 |
Notion connector authorized so Claude can build |
Build blocked |
✅ VALIDATED 2026-07-04 (workspace verified) |
| A3 |
Secondary User participates as a tracked user |
SC3 (multi-person) fails |
Phase 1 |
| A4 |
Calendar source is API-accessible |
Calendar-import feature (CAL) fails |
Phase 4 |
| A5 |
Notion can express the required rollup/formula logic |
Rework of design |
Phase 4 spike (see R8) |
Issues (open now)
| ID |
Issue |
Sev |
Owner |
Action |
| ~~I1~~ |
CLOSED (invalid) 2026-07-04 — "connector not authorized" was an unvalidated assumption, not a real issue. Verified live: workspace "Almond Street Notion" ([email protected]). Build unblocked. |
— |
Primary User |
Lesson: validate before logging as an Issue |
Dependencies
| ID |
Dependency |
Blocks |
Links |
| D1 |
Notion connector authorization |
Phase 4 Build |
✅ MET — verified 2026-07-04 |
| D2 |
Notion Business plan purchase (2 seats) |
Multi-person use |
A1 |
| D3 |
Calendar API access |
Calendar-import feature |
A4 |
| D4 |
Each integration source's API / cost / access |
That source's future phase |
R3 |
| D5 |
Requirements + design baseline complete |
Build start |
✅ met |