Project Manager + RAID
Project status and execution management: Up-level is the only path.
The Project Manager surface is where execution happens, and where most enterprise tools get it wrong. They build surfaces for reporting, not for acting. The core insight that shaped this design: in a healthy project, the only information flow is upward. Status moves up the chain; decisions come back down. The design should make "up-level" the single, obvious action, reachable from wherever a PM happens to be, not buried three clicks into a project they have to open first.
The execution board shows Scope, Schedule, and Spend health as three independent rings, each with its own status and its own one-click Update action. Tango sits alongside as an insight feed, not a separate destination, surfacing risk patterns and historical precedent inline with the work itself.
The sparkle icon's animation rate is the severity, not just its colour. Watch the three states below run at their real cadence.
Up-level, end to end
Four real screens from the working prototype, in sequence. Not mockups, this is the actual flow a PM walks through to move a project's status forward.
Tango flags it before you go looking
The grid view never makes a PM hunt for what's stale. Tango reads update timestamps and blocker flags directly: "Meridian Digital status hasn't been updated in 2 days, UAT milestone is at risk." Each flagged row gets its own Up-level button inline, plus a bulk action when several projects have gone quiet at once.
Up-level from the grid, see the diff instantly
Click Up-level and the change doesn't just save silently. A banner shows exactly what moved: Scope 78% → 84%, Schedule confirmed On Track, Spend confirmed On Track, and a new RAID item logged automatically (an assumption about UAT completion). An animated trail visibly connects the quick action to the health rings it just updated, so the PM sees cause and effect, not just a refreshed number.
Or skip the form entirely: tell Tango what happened
"Catch me up" is the other entry point: one free-text box. "Share what changed since last update, Tango will parse scope, schedule, spend and flag any risks automatically." A PM writes a sentence the way they'd say it out loud. Review & commit stays disabled until there's something to parse, so it's never an empty submit.
Committed, logged, and visible in the activity feed
A toast confirms what changed: "Up-level committed. Health cards updated, 1 RAID item added." The same update appears in the project's activity feed as "Status committed, Scope → 84%, Schedule → 56%, via Review & commit," timestamped. Nothing about the update is invisible after the fact.
Three independent health rings instead of one rolled-up status.
A single 'at risk' badge hides which dimension is actually the problem. Splitting Scope, Schedule, and Spend into three rings, each independently up-levelled, means the Schedule can be at risk while Scope and Spend stay calmly on track, and everyone can see exactly which lever needs attention.
The sparkle icon's animation rate IS the severity, not just its colour.
An on-track item gets a slow breathing pulse: a gentle scale and glow on a 3.5-second cycle, about 17 times a minute, calm enough to ignore. An at-risk item gets a visible wiggle on a 2-second cycle, about 30 times a minute, enough motion to catch peripheral vision without being alarming. A critical item gets a single deliberate shake (four quick steps across 400 milliseconds) followed by a long rest, repeating on a 1.1-second cycle, about 54 times a minute. That pacing was deliberate: constant vibration reads as background noise the eye learns to filter out, but one sharp burst followed by stillness reads as a distinct alarm each time it fires.
Two entry points into the same update, grid Up-level and free-text Catch me up.
Some updates are a single confirmed number, on-track stays on-track, and a one-click Up-level is correct. Other updates are a paragraph of context a PM already has in their head and doesn't want to decompose into three separate fields. Catch me up takes the sentence and has Tango parse it into Scope, Schedule, Spend, and any risks, so the PM writes once in their own words instead of filling a form.
Up-level moved from a hover-only button to an always-visible cell.
An internal UX sync flagged that hover-only actions are invisible until a PM happens to mouse over the right row, which means stale projects stay stale simply because nobody hovered. The redesign made the update cell permanently visible, carrying both the freshness state (how long since the last update) and the action together, so staleness itself becomes a visible, scannable signal across the whole grid, not something you discover by accident.