WORKFLOW PRESENTATION · OPERATING BLUEPRINT

Pipeline reporting

How a pipeline shows you what's stuck before it's already dead.

6 STAGESFINAL REVIEW
STAGE 101 / 06

The current state

Deals sit across the pipeline stages and, at a glance, the board looks calm. That glance shows position, not motion.

STAGE 101 / 06

The current state

Deals sit across the pipeline stages and, at a glance, the board looks calm. That glance shows position, not motion.

STAGE 202 / 06

What it should say

Each deal should show how long it's sat in its stage and whether that's normal: position plus motion, not just position.

STAGE 303 / 06

Where it breaks

Without a threshold rule, a stalled proposal looks like every other proposal. The board can't surface what it doesn't mark.

STAGE 404 / 06

What it costs you

By month-end, the stuck deal is finally obvious, but the follow-up moment has aged. The issue was invisible while it mattered.

STAGE 505 / 06

The rules

A stage threshold checks Over SLA?, sets a stuck flag, and pings the owner. Stuck becomes a visible state, not a vigilance habit.

STAGE 606 / 06

The instrument

One view surfaces the stuck deal first, so the thing that stopped moving is the thing you see before it is gone.

FINAL REVIEW

Before vs after

A pipeline board tells you where deals are. Reporting should tell you which ones have stopped moving while you can still act.

BEFORE

Stalled deals looked identical to active ones until they surfaced, already cold, at month-end.

AFTER

Deals flag themselves when they exceed a stage threshold, and the stuck one is what you see first.

SYSTEM LIBRARY

Related systems.