Matvey Zakharov
RU

Management learns from anecdotes instead of facts

There is no common measurement framework for comparing performance, bottlenecks, and losses. Decisions follow whoever complains loudest, personal impressions, or isolated incidents.

The largest recorded loss is reviewed first

One event population and unchanged time costs. Only the review agenda changes.

Before
Priority by mentions
  1. Scope clarification89 min
  2. Estimate error242 min
  3. Assignment change361 min
  4. Repeated work724 min
After
Priority by recorded minutes
  1. Repeated work724 min
  2. Assignment change361 min
  3. Estimate error242 min
  4. Scope clarification89 min
Before: priority by mentions. After: by recorded rework time. Both lists display full-population minutes retrospectively for comparison.

The review covers the full recorded loss

Reviewed events cover 240 → 1,416 of 1,416 minutes. Total loss stays unchanged.

Before
Reviewed: 240 minOutside review: 1,176 min
After
Reviewed: 1,416 minOutside review: 0 min
Above water: minutes in reviewed events. Below water: the remaining records. The whole shape represents the same total minutes.
SOLUTION

Management measurement framework.

  1. Compare meeting topics with records of performance, delays and losses, checking which work entered the discussion.
  2. Define a measure, population and source for recurring decisions, comparing like work over equivalent periods.
  3. Introduce reviews ordered by measured losses with links to source events, then separately check the effect of each decision.

What an engagement produces

  • Management questions and suitable measures
  • Consistent comparison rules
  • Sources and analytical populations
  • A review process linked to source events
  • Setup in your tools, or oversight if you set it up yourself

Rules, thresholds, scripts and automation logic are engagement deliverables and are not published here.

Find out whether this is actually your constraint.

Explore another problem