Communication load
Volume of communication carried per person or channel.
Formula
Communication burden
messages, updates, and meeting hours per person per week
Unit
index
Direction
Lower is better
Cadence
Monthly for overloaded teams; quarterly baseline otherwise.
Worked Example
Product team communication sample.
Meeting hours per person
18/week
Messages per person
420/week
Calculation
Review load against team baseline and decision output
Result
High communication burden
Interpretation
Communication volume is high enough to require channel and meeting design review.
Recommended action
Reduce recurring meetings and convert status traffic into structured records.
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 teams are spending too much energy transmitting messages instead of creating clarity.
Manual assessment method
Estimate meeting load, message volume, update frequency, and communication burden across a sample team or workflow.
Lapemo calculation path
Not a current platform capability; message or activity volume requires future connector data.
Interpretation Bands
Healthy
Low and declining
Gaps are being removed on cadence.
Watch
Flat
The operating model is not improving.
Risk
Rising
Debt is accumulating faster than teams are resolving it.
Critical
Concentrated in critical work
Escalate for owner action.
Required inputs
- Meeting hours
- Message volume
- Update frequency
- Team size
Data sources
- Calendar sample
- Collaboration tools
- Team survey
Common pitfalls
- Treating all communication as waste
- Ignoring role differences
Recommended actions
- Redesign meeting architecture
- Define channel purposes
- Move decisions into records
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.