April 30, 2026
Chasing MAU Kills Communities — On Leading, Intermediate, and Lagging Indicators
Why we end up chasing MAU
When you launch a community and start running it, the first thing most people care about is “how many people are here.” Member count, active rate, monthly active users (MAU) — chasing these numbers is, in fact, a very natural pull.
The reason is structurally simple: head count is visible.
The essential value of a community — the relationships between members and the chains of conversation — cannot be counted directly. Member count and MAU, on the other hand, are right there in the platform admin panel. In reports to leadership, “we added 100 members last month” lands intuitively. “Connections between core members and the middle layer have strengthened” does not.
On top of that, without conscious effort, KPIs naturally converge to “things easy to count.” The busier operations get, the more we lean on whatever number is most prominent on the dashboard. Member count, post count, MAU end up being treated, unconsciously, as proxies for community health. This isn’t laziness — it’s structural gravity.
The problem is staying pulled by it.
Why MAU only tells you “after it’s already dropped”
You’ll often see MAU (monthly active users) and total message count in community management reports. They’re easy to grasp and easy to explain to executives. But chasing only those indicators inevitably leads to “too late” at some point.
The reason is simple. MAU is a lagging indicator: it moves only after the result has materialized.
A community’s energy starts dropping months before MAU drops. Core members quietly grow tired, new members fail to make a first post and leave, conversation concentrates in one or two channels — only after these changes accumulate does MAU finally register them.
If you start acting once MAU has already dropped, recovery takes commensurate time. The problem is not at “the moment of measurement” but in events that happened months earlier.
A three-layer KPI tree
To catch community health early, it helps to organize KPIs along a causal flow — cause → state → result — in three layers.
| Layer | Type | Cadence | Representative indicators |
|---|---|---|---|
| Cause layer | Leading indicators | Weekly to monthly | Connection connectivity, core/middle ratio, beginner isolation rate |
| State layer | Intermediate indicators | Daily to weekly | Community density (intensity of buzz), temperature (level of enthusiasm) |
| Result layer | Lagging indicators | Monthly to quarterly | MAU/WAU, retention, total messages |
Lagging indicators are the ones you only notice “once it’s hard to come back.” The ideal is to pick up signals early through leading and intermediate indicators, and confirm the result with lagging indicators.
Leading indicators (cause): structural health
Leading indicators look at the structure itself of the community. The aim is to catch distortions before they show up in the headline numbers.
Connection connectivity
Look at whether members are connected across the community, not closed within one cluster. A state where “regulars only talk among themselves” or “only operators and the core exchange messages” is a sign of siloing.
How to check: simply tracking the number of members talking across multiple channels, on a monthly basis, surfaces the trend.
Ratio of core / middle / mass layers
A healthy community has a middle layer (hub layer) that connects the core and the mass. If the middle layer fails to grow, load concentrates on the core, leading to burnout and organizational collapse.
How to check: compare the number of members posting multiple times per month (middle-layer candidates) with the support volume each core member is carrying alone.
First-post rate and time-to-first-post for new members
Whether new arrivals are joining but failing to post and dropping off is something you can detect — before MAU registers it — through “first-post rate” and “median days to first post.”
How to check: track the proportion of members who post within 14 days of joining. If this number starts dropping, the onboarding design is breaking.
Intermediate indicators (state): the community’s current temperature
Intermediate indicators look at whether the community right now is at a “just-right buzz.”
Community density (spatial density)
A “just-right buzz” is a state where the flow of members against the channels is neither too much nor too little. Too low and a sparse feeling sets in; too high and the flood becomes unfollowable.
A simple proxy: “daily posts in the main channel ÷ active member count” tracks the trend.
Community temperature (enthusiasm)
Not the quantity of posts, but the qualitative state: are spontaneous reactions happening? Are topics naturally chaining? Are new members being welcomed?
Quantification is hard, but tracking weekly the “number of spontaneously formed threads in the past 7 days” or the “emoji/sticker reaction rate” works as a proxy.
Lagging indicators (result): final confirmation
Lagging indicators serve to confirm how the leading and intermediate work has played out. The use is not “let’s maximize this” but “if we keep leading and intermediate indicators in good shape, this will rise naturally.”
- MAU/WAU: monthly and weekly active users
- Retention: percentage of members still active after 90 days
- Total messages: overall message volume across the community
Dashboard design guidance
To actually run a three-layer indicator system, you must separate the cadences at which you look at things.
| Cycle | What to look at | Purpose |
|---|---|---|
| Daily | Intermediate indicators (quick density/temperature checks) | Catch anomalies early |
| Weekly | Leading indicators (first-post rate, middle-layer ratio) | Track structural change |
| Monthly | Lagging indicators (MAU, retention) | Confirm result of leading/intermediate work |
You don’t need to track everything in real time. Use leading and intermediate indicators weekly to notice “something feels off,” and use MAU monthly to confirm results — this two-layer approach prevents excessive measurement cost while still enabling early response.
MAU is “what follows”
This is not “stop chasing MAU.” The point is MAU is something to track as a result, not something to optimize directly.
When MAU drops, “let’s raise MAU” interventions, without addressing the cause, only produce a temporary recovery. If core members are tired, grow the middle layer to distribute load. If new members can’t post, lower the bar to a first post. Addressing causes is what raises MAU as a consequence.
Set the structure with leading indicators, hold the state with intermediate indicators, confirm with lagging indicators. KPI design that consciously follows this three-layer causality is the first move that prevents communities from going past the point of recovery.
Related articles
- How to Choose and Operate Community KPIs — Five Representative Metrics and Their Pitfalls
- Communities Have a “Just-Right Buzz” — On the 70% Rule
References
- 山本隼汰 (Junta Yamamoto), Mathematical Models of Online Public Spheres (2026), §8.4 — KPI tree structure and leading/intermediate/lagging indicators
- Kraut, R. E., & Resnick, P. (2012). Building Successful Online Communities: Evidence-Based Social Design. MIT Press.
Frequently asked questions
- Q. What is the difference between leading, intermediate, and lagging indicators?
- A. Leading indicators capture structural health and signal "what's coming next" (core member burnout, whether beginners and senior members are connected, etc.). Intermediate indicators capture "the current state" (community buzz density, level of enthusiasm). Lagging indicators are "the numbers that show up as a result" (MAU, retention, total messages). Lagging indicators only register after the deterioration has already surfaced, so chasing them alone leaves you reacting too late.
- Q. Should I never use MAU as a KPI?
- A. It's not that you should ignore it — it is suitable to "track as an outcome." But by the time MAU drops and you start to act, the community's energy has usually been eroding for several months. Combining MAU with leading and intermediate indicators gives you the early-warning system that matters.
- Q. How do I measure leading indicators?
- A. Speaker-network connectivity and the ratio between core/middle/mass layers can be calculated by analyzing Discord message logs. To start, even just counting "the number of members talking across channels" or "support volume per core member" reveals the trend.
- Q. Does this thinking work in small communities?
- A. The accuracy of mathematical models varies with scale, but the causal frame "leading → intermediate → lagging" works at any size. Even in a community of fewer than 100 people, simply being attentive to leading signals — "core members seem tired lately," "new members aren't posting their first message" — is enough to prevent things from going past the point of recovery.