Skip to main content
Large People ModelHuman Operating Architecture
Needs new dataCommunicationpercent

Meeting density

How much working time is consumed by meetings.

Formula

Meeting density

(meeting hours / available working hours) * 100

Unit

percent

Direction

Lower is better

Cadence

Monthly for overloaded groups.

Numerator

Meeting hours in period

Denominator

Available working hours in period

Worked Example

Calendar sample for product managers.

Meeting hours

14.5

Working hours

40

Calculation

14.5 / 40 * 100

Result

36.3%

Interpretation

More than a third of work time is in meetings.

Recommended action

Audit meetings that do not produce decisions, commitments, or shared context.

Why it matters

This metric helps leaders see whether the communication layer is healthy enough to support execution and AI readiness.

What it reveals

Whether meetings are becoming a substitute for clear ownership, decisions, and communication design.

Manual assessment method

Review calendars for a sample group and calculate meeting hours as a share of available work time.

Lapemo calculation path

Not a current platform capability; it requires calendar data or a meeting instrumentation model.

Interpretation Bands

Healthy

0-10%

Low and manageable.

Watch

11-20%

Rising signal that should be reviewed.

Risk

21-35%

High enough to indicate structural friction.

Critical

>35%

Likely blocking execution or governance quality.

Required inputs

  • Calendar sample
  • Working hours
  • Meeting categories

Data sources

  • Calendar export
  • Meeting audit
  • Team survey

Common pitfalls

  • Ignoring meeting quality
  • Averaging away overloaded roles

Recommended actions

  • Remove low-output meetings
  • Clarify decision forums
  • Set meeting purpose rules

Measure Before You Scale

Measure the operating model before AI amplifies it.

Use the Metrics Library to understand what to diagnose, what to monitor, and where Lapemo can turn framework metrics into operating intelligence.