Q4 Platform Launch · Fault Lines

Program length: 41 days
Critical path: 9 of 35 tasks
Flagged at risk: 2 tasks
Heaviest downstream load: Engineering · 85 downstream

Tap a task to inspect it · drag to move itScroll to zoom · drag a task to move it · drag the canvas to pan

No task selected

Select a task in the graph to see its owner, what depends on it, and how much delay it can absorb.

Delay simulator

Select a task to simulate a slip

010 days

Select a task, then drag the slider to see how far a slip travels and which teams it lands on.

Risk briefing

The biggest risk in this program is Vendor data feed contracts (Ops). It's blocked, it's on the critical path, and 15 tasks across 5 teams can't start until it's done.

Sample text (no API key)

T05 · Ops
The ingestion pipeline and data validation can't start until this contract is signed, and a lot of the program sits behind those. There's no spare time here, so every day it stays blocked pushes the launch back a day.
Do this: Ask legal to fast-track the contract review this week. In parallel, have Ops line up a backup data source so Engineering isn't waiting on one vendor.
T07 · Engineering
It's 40% done and four other pieces of work are waiting on it: audit logging, the dashboard front-end, analytics tagging and the security pen test.
Do this: Move one engineer from the accessibility review (T29), which isn't urgent yet, onto the reporting API for the next week.
T01 · Engineering
This is already done. It's on the list because everything else builds on it, so a gap found here late would mean the most rework.
Do this: Nothing to do now. If a new requirement comes up, handle it as a change request rather than reopening T01.

If Vendor data feed contracts slips another 3 days, the program finishes on day 44 instead of day 41. The delay reaches Compliance, Data, Engineering, Marketing and Ops.

Select any task in the graph for a briefing on that task alone.