Jeremy Bentham designed the panopticon in 1791 as an efficiency solution. A circular prison with cells arranged around a central watchtower. A single guard could observe all inmates without the inmates knowing whether they were currently being watched. The brilliance was simply economic: maximum behavioral control with minimum supervisory expenditure. The prisoners would discipline themselves because they might be observed at any moment.
Michel Foucault spent considerable effort analyzing why this didn’t work as intended. In Discipline and Punish, he demonstrated that the architecture produces docile subjects who internalize the observer’s gaze and optimize their behavior for visibility rather than effectiveness. The watched don’t become better workers or more reformed criminals. They become performers of compliance. The panopticon succeeds at producing observable order while failing at its stated objective. As fundraising technologists, are we building panopticons?
An Efficiency Trap
Nonprofit accountability pressures have intensified as boards want metrics and donors want proof of impact. The technology has finally matured to the point where comprehensive visibility is actually possible. Salesforce, Blackbaud, and their peers can track every interaction, log every activity, measure stage movement, and we can then surface it all in dashboards. Leadership can finally see what’s happening in the field.
The architecture follows naturally, because required fields ensure data completeness, stage gates create pipeline visibility, and activity logging provides proof of engagement and connection. Operations teams build processes that guarantee compliance with these requirements. The entire infrastructure from the CRM to engagement platforms, wealth screening tools, and reporting systems gets designed around a single organizing principle: can we verify that the work is happening?
Records are populated, activities are logged, and processes are followed as they fill the dashboards with impressive volumes of data. Leadership has unprecedented visibility into development activity. And yet, the fundamental questions remain difficult to answer. Which relationships are developing? Where should we deploy resources? What is working and what isn’t?
A Surveillance State
The answer lies in what the architecture actually optimizes for. Bentham thought he was designing for reformation and productive labor. He was designing for observable compliance. The prisoners learned to perform being reformed rather than to actually reform. The distinction matters because the behaviors are not the same.
Foucault’s contribution was identifying the mechanism. Surveillance architecture doesn’t need active monitoring to function. The possibility of observation is sufficient. Once subjects know they might be watched, they internalize their gaze and restructure their behavior around what’s visible to the observer. A prisoner who might be watched at any moment keeps a clean cell, maintains proper posture, and follows schedules. All these behaviors are legible to the distant observer. Whether those behaviors serve rehabilitation is secondary to whether they satisfy oversight.
A logged activity isn’t the same as a thorough documentation of a meaningful conversation. A populated required field isn’t the same as useful information. A stage movement isn’t the same as relationship development. An activity count isn’t the same as strategic judgment about when to ask and for how much. The system produces compliance with process while remaining agnostic about whether the process serves the mission.
Operations as Enforcement
The inversion runs deeper than individual behavior. Fundraising operations teams, charged with maintaining these systems, become enforcement mechanisms rather than enablers. Their effectiveness gets measured by compliance rates. They are held accountable for how many records are complete, how much activity is logged, how consistently process is followed to enable dollars raised. Given their position within the architecture, this makes sense. They’re accountable for system integrity, and system integrity is measured by data completeness and process adherence.\
Operations teams designed around enforcement cannot simultaneously optimize for fundraising effectiveness.
The mandate that artificial intelligence demands quantities of consistent data at levels we would have scoffed at a decade ago is enough on its own, but the political and fiscal environment makes this architecture nearly inevitable. Nonprofits face intensifying pressure to demonstrate efficiency and impact. Boards ask harder questions about fundraising ROI. Major donors want proof that their investments produce results. The response is that we build systems that provide visibility into operations. And that seems entirely reasonable. If we can see what’s happening, we can manage it better. If we can measure it, we can improve it.
The technology enables this at scale in ways that weren’t previously possible. Legacy systems had limited reporting capability. Visibility required manual aggregation and suffered from data gaps. Modern platforms eliminate these constraints. Nearly every interaction can be tracked, every field can be required, every process can be automated, every metric can be dashboarded. The question of whether to design for comprehensive oversight is replaced by the question of why you wouldn’t, given that the capability exists.
Goodhart’s Law in Practice
Surveillance doesn’t produce insight. It produces performance of the things being surveilled. Goodhart’s Law states that when a measure becomes a target, it ceases to be a good measure. Gift officers who know their activity counts are primarily monitored, not digested, will produce activities. Whether those activities represent good fundraising judgment is a separate question. Leadership gets the visibility they asked for: the dashboards full of data, the reports showing activity, and metrics demonstrating compliance without necessarily getting the outcomes they need.
Leadership implementing these architectures genuinely believes they’re building systems to improve fundraising effectiveness. The logic is straightforward: better visibility enables better management, better management produces better outcomes. Operations teams genuinely believe that data completeness and process consistency will improve organizational performance, and they are right. Gift officers, to the extent they have input, often request better tracking tools because they recognize the value of organized information about their portfolios.
The problem is that visibility, management, data completeness, and process consistency are means, not ends. The end is to ultimately be a better steward of your data, dollars, and people. Technology and operations infrastructure only have value insofar as they advance that end. A system that produces comprehensive visibility while making gift officers less effective at their actual job has failed, regardless of how well it satisfies oversight requirements.
What the Alternative Requires
Instead of “can we verify this is happening?” ask “does this decision move us forward to a technology ecosystem that is purpose built for our mission?” Reporting should measure whether work reflects organizational principles—are we being donor-centered, are relationships developing in ways consistent with our values, are we deploying resources strategically? These are harder questions than “how many activities were logged” but they are the questions that matter. Accountability should focus on outcomes and judgment rather than simply compliance and activity volume.
Operations teams in this model become enablers rather than enforcers. Their job is removing friction from the gift officer’s workflow, providing tools that make relationship management easier, and surfacing information that improves decision-making. System integrity still matters, and matters greatly, but it’s measured by whether the system helps practitioners do better work, not just by whether fields are populated consistently.
The Architecture Precedes the Outcome
The philosophical experiment of the panopticon failed because architectural decisions made for one purpose produce unintended consequences that undermine the stated objective. The same mechanism operates in fundraising technology and operations. Infrastructure designed solely for oversight produces compliance instead of outcomes. The dashboards fill with data while the fundamental work of fundraising: relationship development, strategic judgment, donor-centered engagement becomes harder rather than easier.
I promise that I’m not asking us to compromise on having visibility into operations. I am asking us to reflect on whether visibility is our organizing principle or if we can accept that it should be a byproduct of effective design.