Run

Every project, every phase, one view

What needs you today, and where everything else has got to.

Book a demo →
5
tollgates
one per DMAIC phase
3
risk levels
on track, watch, at risk
6
columns
Define through Completed
Yours
review SLA
set per organisation

The board

The queue comes first, not the tidy columns

Projects sit in six columns by DMAIC phase. Tollgates waiting on a reviewer are pinned above them, because the thing blocking other people is the thing a facilitator should see first.

Sample data/org/board

Define

Yield loss on line 3

Priya

On track

Changeover study

Amir

Watch

Measure

Scrap baseline

Chen

On track

Analyze

Root cause trial

Marta

At risk

Improve

Pilot standard work

Ravi

On track

Control

Control plan sign-off

Sofia

Watch

Completed

Line balance

Validated

On track

Flagged, and why

The score shows its working

At-risk flags come from a points model, not a prediction. Every signal is arithmetic, and the board shows the reasons it added up rather than asking anyone to trust a badge.

Past the target date

The heaviest signal in the score, worth up to 40 points on its own and rising with the number of days.

Days idle

Time without meaningful movement adds to the score, so a project nobody has touched stops looking healthy.

A rejected tollgate

A gate sent back is an explicit risk signal rather than a quiet setback.

A gate past your review SLA

Waiting counts against the project, which is what stops the queue being somebody else’s problem.

A project that is not active scores zero by definition, so finished and paused work never pads the count of things going wrong.

The queue nobody owns

Waiting becomes visible

When a tollgate passes the review window your organisation set, the system raises a notification in the app and records the breach as an event on the project. It will not raise the same one twice.

Review SLA

Set per organisation

The product does not assume a universal number of days, because a gate review in a regulated plant and a gate review in a service team are not the same promise.

Time in phase

The clock follows the history, not a field somebody edits

Time in phase is derived from the project's own append-only phase history. Roll a gate back and the transition is recorded backwards, so the clock restarts from the last time the project entered that phase and the number reflects the live sit rather than the original entry.

See it run with your own team

Bring the process you use today. Thirty minutes is enough to see it as a governed project with the decisions recorded.

Book a demo →

How SigmaForge governs the work →