Meeting KPIs: Decision Velocity, Completion, and Load

Most teams measure meeting time. They count hours and attendees, then stop. They can't answer the questions that matter: how many decisions got made this week? How long did each take? What percentage of action items finished on time? This post gives you the 12 metrics that answer those questions — with formulas, thresholds, and decision triggers for each one.

The problem: meetings are a black box

Teams report "12 hours per week in meetings" but can't say how many decisions came out of them. Meeting time climbs 2–3% annually, decision velocity stagnates, and action completion hovers around 60–70%.

Leaders see the symptoms — missed deadlines, decisions that get reopened, scope creep — but not the root cause. The root cause is almost always the same: no one is measuring what meetings produce.

The 4-tier framework

Meeting effectiveness lives in four layers. Every metric in this post belongs to one of them.

Tier 1 — Input: do we have the right people and preparation?

Tier 2 — Process: did we run the meeting well and decide?

Tier 3 — Output: did we document decisions and assign follow-up?

Tier 4 — Outcome: did we execute and deliver?

Start with Tier 1 and Tier 4 — input and outcome. Add Tier 2 and 3 once you have a baseline.

Tier 1: input metrics

Meeting size

Formula: average attendees per meeting.

Target: Decision meetings — 3–5 people. Alignment — 6–10. Planning — 8–12.

If over target: audit your RACI matrix. Remove 2–3 roles that are Informed, not Advisory.

Pre-read completion rate

Formula: (# who read ÷ # invited) × 100

Target: 85% or higher.

If below 70%: reduce pre-reads to 2 pages, post 48 hours before, add an explicit deadline.

Accountable attendance rate

Formula: (# meetings where Decider attended ÷ # needed) × 100

Target: 95% or higher.

If below 80%: the Decider has too much on their plate. Reduce their meeting load or reassign decisions.

Tier 2: process metrics

Meeting time adherence

Formula: (# ending on time ÷ # held) × 100

Target: 85% or higher.

If below 70%: add a 15-minute buffer or implement hard stops for open discussion.

Decision made in meeting

Formula: (# meetings with a clear decision stated ÷ # scheduled) × 100

Target: 80% or higher.

If below 60%: add a pre-decision checklist — Is the Decider present? Is advisor input gathered? Reserve the first 30 minutes for the decision only.

Decision velocity

Formula: days from issue raised to decision logged.

Target: Routine decisions under 3 days. Cross-team under 7 days. Strategic under 14 days.

If over target: gather advisor input before the meeting, not during. Escalate routine decisions stuck over 3 days to the Decider's manager.

Tier 3: output metrics

Decisions documented rate

Formula: (# with owner + deadline + rationale ÷ # made) × 100

Target: 100%.

If below 90%: use a one-page memo template. Send to the Decider within 30 minutes for confirmation.

Actions assigned with deadline

Formula: (# with owner + due date + decision link ÷ # assigned) × 100

Target: 100%.

If below 85%: enforce the template. Every action needs an owner name, a specific date, and a blocked-by list. Run a weekly blocker check.

Risk escalation rate

Formula: (# risks documented ÷ # that should be) × 100

Target: 80% or higher.

If below 60%: add a Risks section to your notes template. End every meeting with "What could go sideways?" Capture 2–3 risks.

Tier 4: outcome metrics

Action completion rate

Formula: (# finished by due date ÷ # assigned) × 100

Target: 80% or higher.

If below 75%: cap at 10–12 actions per week. Make dependencies explicit. Run a weekly blocker standup. Anything blocked over 1 day gets escalated.

Decision re-debate rate

Formula: (# re-debated ÷ # closed) × 100

Target: under 10%. Elite teams: under 5%.

If above 15%: document dissent at decision time. When a decision gets reopened, cite the original decision and the dissent log.

Action blocker rate

Formula: (# blocked on dependencies ÷ # assigned) × 100

Target: under 20%. Elite: under 10%.

If above 25%: run a weekly blocker standup. Owner has 4 hours to unblock. Anything blocked over a week escalates.

All 12 metrics at a glance

If/then decision rules

Decision velocity

If a routine decision is over 3 days → escalate to the Decider's manager.

If a cross-team decision is over 7 days → require an advisor feedback doc 24 hours before the sync.

If a strategic decision is over 14 days → re-scope the decision frame or escalate to the CEO.

Action completion

If below 75% → diagnose first: are actions unclear? Dependencies broken? People overloaded?

If two actions per person are blocked over 1 day → escalate within 4 hours to the blocker owner's leader.

If the same person misses deadlines 3 times → re-scope their load or reassign the actions.

Meeting load

If IC load is over 30% → audit the calendar and remove all "Informed" meetings.

If manager load is over 40% → remove status meetings, keep decisions and planning only.

If exec load is over 50% → delegate decisions or cancel 2 recurring meetings.

Benchmarks by org size

Meeting load targets by role — individual contributors: under 8 hours/week (25%). Managers: under 14 hours (35%). Executives: under 20 hours (45%).

3 real examples

Tech startup (50 people)

Baseline: 12-person meetings, 60% pre-read, 65% decisions made, 75% completion, 18-day velocity.

Changes: added RACI structure, one-page memo template, and weekly metric tracking.

Result: 6-person meetings, 87% pre-read, 87% decisions made, 89% completion, 5-day velocity. 40% fewer meeting hours, decisions 35% faster.

Enterprise sales team (80 people)

Baseline: 90-minute pipeline reviews with 15 people, 45% action completion.

Changes: split into Monday async status and Wednesday sync decisions.

Result: 80% completion, re-debate rate dropped to 4% (was weekly), meeting load per rep 6 hours/week (was 9).

Executive leadership (5 execs)

Baseline: 2-hour sync, verbal decisions, 70% completion, decisions reopened weekly.

Changes: added one-page memo, dissent log, action template, weekly check.

Result: 75-minute meeting, 5 written decisions per session, 90% completion, under 3% re-debate. Saved 45 minutes per exec per week.

Common mistakes and how to fix them

Measuring input only, ignoring outcome

Tracking time and attendance while ignoring execution produces vanity metrics. Pair every input metric with an outcome metric. Small meetings that don't execute are still waste.

Tracking 30 metrics that nobody acts on

Limit yourself to 12–15 metrics. In your weekly review, discuss red items only. Assign one owner per red item. Delete any metric that never goes red.

Thresholds without triggers

Marking velocity as red without defining what to do next means nothing changes. Every metric needs a target, a threshold, and an if/then rule.

Blaming people instead of systems

Low completion almost never means the team is lazy. It usually means someone scoped the actions badly, nobody mapped the dependencies, or the team is carrying too much. Diagnose the system before pointing at individuals.

Dashboard only seen by leadership

If the team never sees the metrics, the metrics don't change behavior. Post the dashboard in your team channel every Friday. Walk through it in Monday standup.

7-day launch plan

Day 1: Collect baseline data from 5 recent decision meetings — size, pre-read rate, decisions made, actions assigned, completion rate.

Day 2: Set realistic targets based on your org size using the benchmarks table above.

Day 3: Build your tracking sheet. 12 rows, one per metric. Columns: Metric | Formula | Baseline | Target | Status | If Red, Then.

Day 4: Assign one person to refresh the dashboard every Friday.

Day 5: Run your first weekly review. 15-minute Monday huddle. Walk the metrics, pick one red item for a system fix.

Day 6: Make one system fix — memo template, agenda timing, decision clarity, pre-read process, or role definition.

Day 7: Share the dashboard with the full team. Explain the targets. Schedule a standing Monday 9am review at 15 minutes.

How Spry tracks this for you

Building a meeting metrics dashboard manually means someone spending 3–5 hours every week pulling data from calendar exports, meeting notes, and task trackers. Most teams start tracking, keep it up for two weeks, and then it goes dark.

Spry's calendar analytics calculate the metrics that live in your calendar automatically — meeting load per person and team, agenda readiness, meeting frequency, and week-over-week trends. You get the before/after numbers without the manual work.

For the metrics that require decision and action tracking, Spry gives you the meeting load data as the foundation. You can see which teams are over their load targets, which recurring meetings are running without agendas, and where meeting cost stacks up — the inputs that explain why velocity and completion numbers move.

FAQs

How often should we review these metrics?

Weekly 15-minute huddle covering red items only. Monthly 1-hour deep dive on trends. Quarterly review to raise targets once you've hit them.

Which metrics matter most?

In order: action completion rate, decision made rate, decisions documented, re-debate rate. Start with these four before adding the rest.

What if a metric stays red for 3 weeks?

Something in your system is broken. Stop adjusting the target and diagnose the root cause. Red for 3 weeks means the if/then rule isn't working — either the trigger isn't firing, or the fix isn't addressing the real problem.

Can metrics be gamed?

Yes. Prevent it by defining every metric precisely, running spot-check audits on 5 recent decisions, and making the dashboard visible to the whole team — not just leadership.

Should we pilot with one team or roll out org-wide?

Pilot with one team for 4 weeks. Roll to 3 peer teams in weeks 5–8. Org-wide adoption after you have a proven playbook and at least one visible win to point to.

How long until the metrics improve?

Input metrics improve in 1–2 weeks once processes are in place. Process metrics take 3–4 weeks. Outcome metrics take 6–8 weeks to show sustained improvement.

What's the actual ROI?

Organizations waste roughly 10% of payroll on unproductive meetings. For a 100-person org at $100K average salary that's $1M in annual waste. Improving velocity by 30–40% and completion by 10–15% saves $300–400K per year — roughly 3–5x ROI in year one.