The Wrong Problem

The Wrong Problem

For about fifteen years, civic technology has run on a single diagnosis: citizens are disengaged. Apathetic, distracted, too busy. The tools followed from the diagnosis the way tools always do. Lower the friction. Make it one tap to contact your representative. Send the email for them. Pre-write the script. Surface the bill. Add a streak, a badge, a progress bar. If only participation were easy enough, the thinking went, people would participate.

The diagnosis is wrong. Not entirely — disengagement is real — but it identifies the wrong constraint. It solves the easy half of the problem and leaves the half that actually kills you untouched.

The half that's easy

Getting a citizen to act once is a solved problem. We have known how to do it for years. Resistbot will turn a text message into a letter to your senator. 5 Calls will hand you a script and a phone number. A hundred advocacy organizations can move tens of thousands of identical emails into a congressional inbox in an afternoon. The friction is gone. The activation problem, narrowly defined, is finished.

And it changed very little. Because the question was never whether a citizen could be made to act. It was whether acting would matter. People are not apathetic about things that work. They are apathetic about things that don't, and they are correct to be. A citizen who emails their representative and receives a templated auto-reply, or nothing, has learned something true about the channel. They are not failing to participate. They have participated, observed the result, and updated accordingly.

The friction was never the thing keeping people out. The void on the other end was.

The half that's hard

Which points at the constraint that actually binds: the supply side. Getting officials onto a platform, and — much harder — keeping them responsive once they're there.

This is the problem almost nobody solves, and it is worth being precise about why it's hard, because the difficulty is structural, not a matter of effort.

An official has no incentive to adopt a new channel. The ones they have already produce more input than they can process. A serious bill draws thousands of form letters; a town hall draws the same three voices it always draws. Adding a fifth channel doesn't help an official who is already drowning in four. It just adds a fifth place to drown.

There is reputational risk and no offsetting reward. A new platform is a new surface where something can go wrong, where a constituent interaction can be screenshotted, where silence reads as contempt. The upside — looking responsive — is diffuse and hard to claim credit for. The downside is specific and public.

And the person you're actually asking to adopt the tool isn't the official at all. It's a chief of staff or a communications director with a full plate and a strong prior that civic-engagement startups waste their time. The product has to earn its place against everything else on that person's desk, on day one, before it has proven anything.

None of this is solved by a better onboarding flow. The citizen side is a user-experience problem, and user-experience problems are tractable. The supply side is an incentive problem, and incentive problems are not moved by polish.

Why the graveyard is full of citizen-side winners

This is the part worth sitting with. Many of the civic tech projects that died were good at the easy half. Some were excellent at it. They had clean products, real users, genuine traction on citizen activation. Brigade had backing, press, and millions of accounts. The citizen experience was not the thing that failed.

What failed was the other side of the exchange. Without officials present and responsive, a participation platform has nowhere to put the participation it generates. The input lands in a void. And a civic platform with a void on the receiving end follows a reliable decay: it becomes a venting space, because venting is what's left when no one is listening; the venting becomes partisan, because outrage sorts itself by tribe faster than anything else; and the partisan space empties, because one side stops trusting it and the other side stops needing it. The sequence is almost mechanical. You can watch it happen in the comment sections of platforms that were never civic to begin with.

The lesson the graveyard keeps teaching, in project after project, is that you cannot build the citizen flywheel first and recruit the officials later. The order is backwards and the physics don't allow it. Citizen engagement without an official on the other end isn't an early version of the thing. It's the failure mode.

This is not a criticism of the people who tried

It would be easy to read the above as "they were naive." They weren't. They solved the problem that was visible. Citizen disengagement is visible — you can see the empty town hall, the unanswered survey, the low turnout. The supply-side problem is invisible until you're inside it, because officials don't announce that they've quietly stopped using your tool. They just stop. By the time the data shows it, the diagnosis looks obvious in hindsight. It rarely is in advance.

The trap is that the visible problem and the binding problem are different problems, and the visible one is more fun to solve. It has clean metrics. It produces growth charts. It feels like progress. Activating citizens generates exactly the kind of signal that convinces a founder, and an investor, that the thing is working — right up until the moment the officials disengage and the whole structure folds inward.

What follows from getting the diagnosis right

If the supply side is the real constraint, then it's the thing the entire design has to be built around — not bolted on after the citizen product is working.

That means starting with the official's actual problem, which is not "how do I broadcast more" but "what is my district actually telling me, in a form I can use, that I can't get anywhere else." It means solving their cold-start so that joining costs them almost nothing and adds value to a presence that already exists. It means treating their workload and their reputational risk as first-order design constraints rather than afterthoughts. It means building the response loop — the acknowledgment, the "incorporated into," the proof that input went somewhere — into the foundation, because that loop is the only thing that keeps the citizen side from decaying into the void.

Do that, and the citizen flywheel mostly takes care of itself. People participate when participation is real. The hard part was never convincing them to show up. It was building something worth showing up to.

The diagnosis has been backwards for fifteen years. Anyone serious about this space should start by turning it around.