Five Ordinary Places Where Everyone Can See If You Followed Through

None of these five systems were built by behavioral economists. A software platform, a gift registry, a fundraising office, and an office kitchen all independently arrived at the same fix for the same problem that shows up whenever a task only has to answer to itself: a private intention is easy to drop, and a witnessed one is harder to.

GitHub’s contribution graph

Every public GitHub profile displays a grid of squares, one per day, shaded darker the more code a developer commits that day. Nothing about the grid is required. No employer mandates it, no algorithm penalizes an empty one directly. And yet “don’t break the graph” has become a genuine motivator across the developer community, common enough in blog posts and forum threads about deliberately committing a trivial change at 11:58 p.m. to count as its own minor internet phenomenon.

The color is beside the point. What matters is that anyone, a recruiter, a collaborator, a stranger, can pull up a developer’s profile and see the exact pattern of any given week without asking. The commitment (write code regularly) was always private and internal. The graph turns the record of keeping or breaking it into something permanently checkable by someone else.

The wedding registry’s “already purchased” tag

Claim a gift on a couple’s registry, and the listing updates for every other guest browsing it: taken, no longer available, sometimes with your name attached depending on the platform’s settings. That single status change does two things at once. It coordinates the group, so nobody buys six identical blenders. And it commits the claimant, because backing out after claiming a named, visible line item carries a different weight than never having said anything.

Couples rarely build their registries with this in mind. It’s a byproduct of coordination software that happens to double as a soft public ledger of who promised what.

The capital-campaign donor wall

Walk into a hospital wing, a university building, or a renovated library, and there’s a good chance a wall near the entrance lists names by donation tier: names in small type for smaller gifts, larger engraved letters for larger ones. Nonprofit fundraisers have used named, tiered donor recognition for well over a century, and development offices will say plainly that recognition, not just the tax deduction, is part of what motivates a gift at the size that gets a name on a wall rather than a receipt in an inbox.

This is the most deliberately engineered of the five. Unlike the GitHub graph or the registry tag, an institution’s fundraising staff chooses the tiers, chooses the placement, and chooses exactly how visible each gift becomes, on purpose, because they’ve learned visibility itself moves the number people are willing to give.

The marathon fundraising page

Sign up to run a race for a charity, and most platforms generate a personal page: a goal amount, a running total, and, critically, a list of who has and hasn’t donated yet among the people invited to see it. Nobody’s forced to check the page. Plenty of people do anyway, and the runner knows the list is sitting there, checkable, for weeks before race day.

What’s happening here is close to the GitHub graph, a running, checkable number attached to a name, but the audience is smaller and more personal: coworkers, family, whoever actually got the fundraising email. A stalled total stays invisible to strangers while staying entirely visible to the handful of people whose opinion the runner probably cares about most, which is a narrower and often sharper form of the same pressure.

The office potluck sign-up sheet

The least sophisticated of the five, and possibly the most universally recognized: a shared spreadsheet or paper sign-up with names next to dish assignments. Nobody signs a contract to bring deviled eggs. The entire enforcement runs on everyone in the office being able to see the sheet, and everyone noticing the empty chair where the deviled eggs should be.

It’s a useful floor for the whole list precisely because it’s so low-stakes. If a shared sign-up sheet, with no money and no institution behind it, reliably gets people to show up with a dish they said they’d bring, that’s a fairly strong data point for how much of performance is actually about who’s watching, stripped of every other incentive.

Where visibility backfires instead

None of this works unconditionally. A donor wall can shade into vanity rather than accountability once the recognition itself becomes the point, divorced from the actual cause. A GitHub graph famously produces junk commits, one-line whitespace changes made purely to keep a streak alive, which is visibility optimizing for the appearance of the commitment rather than the commitment itself. A potluck sheet can shame someone into a rushed, resentful dish rather than a good one. The line between “visible enough to matter” and “visible enough to distort behavior toward looking good instead of doing good” isn’t fixed, and all five systems above sit closer to that line than their designers probably intended.

What the five have in common, and where they differ

All five replace an invisible private intention with a concrete, checkable public fact. Where they differ is audience size and stakes: a donor wall is public and permanent, a potluck sheet is small and temporary, a fundraising page sits in between and targets a chosen circle rather than the general public. None of them involve a financial penalty for failing to follow through, which is what separates all five from a cancellation fee or a forfeited deposit. The visibility alone is doing the work, which is roughly the same principle a social accountability app tries to formalize on purpose: not a fine for missing a goal, just making the miss impossible to hide from a person who’d otherwise never know it happened.