Contribution Board or Dashboard¶

Contribution monitor — instantiates Shared-Benefit Contribution Governance

Puts each contributor's effort on a shared display, so recognition is earned in the open and lopsided load or quiet free-riding becomes a visible fact before it festers.

Contribution collapses fastest when effort is invisible: the people carrying the group go unrecognized, and the people carrying nothing go unnoticed. Contribution Board or Dashboard is the shared display that makes the contribution pattern legible at a glance — who is doing what, right now, across the group. Its defining move is that it reveals rather than adjudicates: it turns invisible effort visible so it can be honored, and invisible non-contribution visible so it cannot hide, but it stops there. It does not keep an earn-and-spend account (that is a ledger) and it does not respond to what it exposes (that is an enforcement path). Its single job is to replace vague impressions of "who's really pulling weight" with a picture everyone can see.

Example¶

A mid-size open-source project has a nagging sense that a couple of maintainers carry most of the load, while several listed "members" have gone quiet — but no one can point to it, and newcomers feel their small fixes vanish unthanked. The maintainers stand up a contribution dashboard: a contribution graph plus a board showing open reviews handled per person, issues triaged, and docs written — deliberately weighted so the unglamorous work counts, not just merged code.

The picture is suddenly undeniable. Two maintainers are doing roughly 70% of code review (overload, and a bus-factor risk), while three nominal members have not touched anything in a quarter (drift). The board punishes no one; it simply makes both facts visible — which is enough for the group to rebalance review duty before its two linchpins burn out, and to publicly thank the contributor whose steady triage had been completely unseen. The display converted a felt suspicion into a shared fact the group could act on.

How it works¶

Aggregate and display continuously. Contribution signals are gathered per person or team and shown on a live, shared surface, not compiled once and filed.
Count broadly, on purpose. The display is weighted to include low-status but real work — review, triage, mentoring, documentation — so visibility does not reward only glory tasks.
Make both tails legible. Over-contribution (overload) and under-contribution (free-riding) surface as facts, side by side.
Reveal, don't rule. It presents the pattern and hands the response to people and to other mechanisms; the board itself passes no judgment.

Tuning parameters¶

What's counted — narrow (commits, hours) versus broad (reviews, triage, mentoring, care work). Broad is fairer but harder to measure and easier to game.
Weighting — flat counts versus effort- or impact-weighted. Weighting fights the "cheap visible work beats valuable invisible work" distortion, but adds judgment and dispute.
Exposure granularity — individual names versus team aggregates. Individual drives recognition and social pressure but can breed rivalry and a surveillance chill; aggregate protects privacy but blurs free-riding.
Time window — rolling-recent versus cumulative. Recent catches current drift; cumulative honors long-haul contributors who are coasting now.
Reach — internal versus public display. Wider reach strengthens recognition and pressure but amplifies gaming and privacy cost.

When it helps, and when it misleads¶

Its strength is that recognition stops depending on who is loudest, and that overload and free-riding surface as facts rather than accusations — which makes them far easier to act on without it turning personal.

Its failure modes trace to the act of measuring. What is displayed becomes what is optimized: people chase the countable, visible contribution and starve the uncounted kind, so the board can quietly degrade the very effort it was meant to protect.^[1] A board can also curdle into a surveillance leaderboard that breeds rivalry and gaming, and — by design — it detects imbalance without repairing it, so a board with no response path just broadcasts a problem no one owns. The classic misuse is wielding it to shame, or cherry-picking its numbers to justify a decision about someone that was already made. The discipline is to count broadly, revisit what is weighted, and pair the board with a genuine response path so its picture drives action instead of performing judgment.

How it implements the components¶

contribution_visibility_layer — it is the visibility layer: a shared, continuous display that makes each contributor's effort, and its absence, legible to everyone.
free_rider_and_overload_guardrail — it supplies the detection half of the guardrail, turning over- and under-contribution into visible facts, which is the precondition for any correction.

It only reveals — it does not act on what it shows. Escalating against persistent free-riding is Graduated Free-Rider Response; repairing an overloaded person's situation is Reciprocity Check-In; and it keeps no earn-and-spend account (Time Bank or Service Credit System).

Instantiates: Shared-Benefit Contribution Governance — the board is the visibility layer that lets recognition, overload, and free-riding be seen instead of guessed at.
Sibling mechanisms: Reciprocity Check-In · Graduated Free-Rider Response · Time Bank or Service Credit System · Cooperation Retrospective · Mutual Aid Roster · Collective Threshold Pledge

References¶

[1] Goodhart's law: when a measure becomes a target, it ceases to be a good measure. A contribution board that people optimize toward stops faithfully reflecting contribution — the standard reason to count broadly and revisit what is displayed. ↩