Statistics

Open Organization → Statistics. The page lists every statistic WePeople knows about for connected modules, grouped by pillar. Each row shows label, description, which SPACE dimensions it feeds, and two independent toggles.

Inactive integrations still list their statistics but cannot collect new data until connected.

Statistics are organized into pillars for scanning:

• Activity — volume and consistency signals.
• Communication — collaboration metadata (Slack when connected).
• Delivery — shipped work (commits, merges, releases).
• Review — review and feedback loops.
• Knowledge — documentation and shared artifact signals.

Pillar badges are organizational — they do not map 1:1 to SPACE letters. Check each row’s feeds dimensions list for scoring impact.

Each statistic has two switches:

• Dashboard — show on monitoring tiles, person summaries, and report metric rows.
• Scoring — include in SPACE dimension math for workers with scoring enabled.

You can expose a metric for transparency without letting it move scores — enable Dashboard only. Conversely, a scoring-only stat influences SPACE without cluttering the board (rare; usually both are on).

Built-in modules ship default statistics owned by the engine or extractors:

• Slack — messages, reactions, presence-derived metrics.
• GitHub — commits, PRs, reviews, merge cadence.
• Jira — story points, tasks done, in-progress counts.

Disabling a statistic for an integration stops it from contributing to new rollups; historical aggregates remain within your retention window.

Developer apps register custom statistics via the Apps API. They appear alongside built-in rows with custom:<app-slug> integration ids and can declare which SPACE dimensions they feed.

Push values with POST snapshots or derive them from ingested events. Full guide: Custom statistics.

Custom stats require developer API access (Pro and Enterprise by default).

1. Connect integrations first — otherwise statistics have no source.
2. Review defaults; disable noisy stats (e.g. low-signal channels) before opening monitoring to the whole team.
3. Enable scoring toggles only for stats aligned with your SPACE interpretation.
4. Save changes — pending toggles batch on the Statistics page (Owner role required for some orgs).
5. Revisit after adding Jira projects or custom apps; new stats appear automatically.

• “More enabled stats is always better.” Extra noise lowers confidence and misaligns scores with intent. Curate deliberately.
• “Dashboard off means data is deleted.” Ingestion continues; the stat just stops appearing in UI and rollups going forward.
• “Custom stats need code in the web app.” They live in developer apps — the Statistics page only toggles visibility and scoring participation.