Daily management
Pipeline management board
Pipeline management board is licensed CC BY 4.0. Attribution: Katafacts (katafacts.com).
Customise with AISkill file ↓1 · What it is
What it is
A pipeline management board is the same tiered huddle cascade as the canonical version — what each level reviews, who runs it, and the concrete condition that sends something up to the level above — pointed at a sales pipeline instead of a shop floor. The lean connection is exactly master-plan §4.2's Sales Funnel Management thesis: a stalled deal is WIP, a recurring loss reason is a defect pattern, and the whole reason a tier system exists is the same reason it exists on a floor — the rep huddle catches a single stalled deal today, RevOps catches a pattern across pods this week, and VP Sales tracks whether the strategies from this year's revenue plan are actually moving the number. Who specifically runs each huddle is never guessed — every tier starts unassigned until you name a real person.
2 · When to use it
When to use it — and when not to
Use it when
- Deals or patterns genuinely need to move from the rep level to leadership on a real cadence, and you want a checkable escalation condition instead of whoever remembers to mention it in a 1:1.
- You want each tier to add something the tier below it doesn't already show — a real pattern or trend, not the same pipeline report read aloud at three different altitudes.
- You already have (or are building) a revenue Hoshin or a funnel value stream map — this is the daily/weekly rhythm that keeps either one honest between planning cycles, not a replacement for either.
Not when
- There's genuinely only one level of review — a two-tier minimum is enforced because a single tier isn't tiered; a single sales team's daily standup doesn't need this structure.
- You don't have real people to name as owners yet — that's fine, the board will honestly show the gap; don't invent a name to make it look complete.
3 · How to fill it in
How to fill it in
- Tier ladder
- Drafted from each tier's name, cadence, attendees, and a rough note on what it watches — assign a real, named owner to each tier afterward.
- Narrative
- Drafted from the ladder actually built.
4 · What good looks like
What good looks like
The example below is Beacon Analytics' own three-tier pipeline cascade — the same company as the deal A3 and revenue Hoshin worked examples elsewhere in this catalogue. The AE pod huddle catches exactly the stalled-deal and win-rate-risk pattern the deal A3 diagnoses, and the VP Sales huddle tracks progress against exactly the win-rate target the revenue Hoshin commits to. Two of three tiers have a named owner; the middle tier is honestly left unassigned rather than padded with a placeholder name.
Same example, as a downloadable xlsx workbook.
Download .xlsxTiered huddle board
Beacon Analytics — Pipeline Management Huddle Cascade
Outbound-sourced mid-market pipeline — new business
Renee Okafor, VP Sales · 2026-03-09
Tier ladder
2 of 3 tiers have a named owner
VP Sales leadership huddle
Renee Okafor, VP Sales
Weekly, Monday, 4:00pm, 20 min · Renee Okafor (VP Sales), Sam Cole (Sales Enablement)
- Quota attainment trend: Attainment trend against plan, not just the current week's number in isolation.
- Win-rate trend vs. annual target: Win rate on outbound-sourced mid-market deals against this year's Hoshin target, and whether the current strategies are actually moving it.
- Resourcing and enablement risk: Whether a recurring pattern surfaced below points to an enablement gap, a staffing gap, or a process fix — and who owns deciding which.
↑ RevOps pipeline huddle escalates here when: Pipeline coverage for the quarter drops below 3x of the remaining quota gap, or a loss pattern spans three or more pods in the same week, escalates to the VP Sales leadership huddle.
RevOps pipeline huddle
UnassignedTuesday and Thursday, 2:00pm, 15 min · Priya Anand (RevOps), pod leads
- Pipeline coverage: Coverage ratio against the remaining quota gap, by segment, not just the team total.
- Forecast risk: Deals moving stage-to-stage slower than historical velocity for that stage, flagged before they slip the quarter.
- Cross-pod loss patterns: Objection or loss-reason patterns showing up across more than one pod, not just isolated to a single rep's deals.
↑ AE pod huddle escalates here when: Any deal stalled 10 or more business days in a single stage, or three or more deals in one week showing the same loss reason, escalates to the RevOps pipeline huddle.
AE pod huddle
Jordan Ellis, Sales Manager
Daily, 9:15am, 10 min · Account executives, Jordan Ellis (Sales Manager)
- Stalled deals: Any deal with no logged activity in its current stage for 10 or more business days, by rep and stage.
- Win-rate risk: Deals showing the same objection pattern behind the team's current win-rate gap — pricing pushback before a demo, or a stalled multi-thread after the first call.
- Activity gaps: Reps below their weekly outbound activity target, and whether it's a capacity problem or a pipeline-quality problem.
Narrative
Three tiers cascade from the pod floor to VP Sales: the AE pod huddle catches stalled deals and win-rate-risk patterns daily, the RevOps pipeline huddle looks for coverage and cross-pod loss patterns twice a week, and VP Sales leadership reviews quota and win-rate trend against the annual Hoshin target weekly rather than daily. Two of three tiers have a named owner — the RevOps pipeline huddle doesn't yet, worth naming soon since it's the tier that's supposed to catch cross-pod patterns before they ever reach leadership.
5 · Common mistakes
Common mistakes
Every tier reviewing the same pipeline report, just to a bigger audience.
The entire value of tiering is that each level up sees patterns and exceptions the tier below surfaced — if VP Sales is looking at the same stalled-deal list the pod huddle already reviewed, the extra meeting is pure overhead with no leverage.
Writing an escalation condition like 'if a deal looks risky' or 'when it becomes a problem.'
An unchecked condition can't actually be checked — a real cascade needs a concrete trigger (a stage-age threshold, a repeat-loss-reason count), or nobody can tell when something should have moved up and didn't.
Naming a placeholder owner just to make every tier look assigned.
A tier with a fake owner is worse than an honestly unassigned one — it hides exactly the gap the coverage check exists to surface.
6 · What it connects to
What it connects to
upstream
Deal A3
A stalled deal or a recurring loss pattern the pod huddle flags is frequently the trigger for a deal A3's own root-cause work, as in the worked example.
downstream
Revenue Hoshin Kanri — X-Matrix
What VP Sales actually sees week over week at the top tier is the real-world check on whether the annual Hoshin's strategies are moving its metrics, not just a forecast of it.
7 · Where AI helps
Where AI helps
Judgement — stays yours
- Deciding who's actually the right owner to run a given tier's huddle
- Deciding whether a drafted escalation condition is realistic given how the sales org actually works
Analysis — AI helps
- Drafting each tier's review categories and a concrete escalation condition from a rough description of what it watches
- Drafting the narrative from the ladder actually built
Drudgery — automated
- Counting how many tiers have a named owner
- Identifying which tiers are still unassigned
- Exporting to xlsx in the house format
9 · Rate this kata