“Government is about doing together what we can’t do alone.”
Jennifer Pahlka offered this line in her TED2012 talk on civic technology. Pahlka used small public-service applications to show how digital tools could connect residents with city work and with one another. Examples ranged from adopting snow-covered fire hydrants to simplifying school information and reusing an idea across cities. Keeping the original occasion in view protects the quote from being stretched beyond its evidence.
The line defines technology as a means of collective capacity rather than a consumer convenience. Good civic software helps people coordinate around shared infrastructure, rights, and responsibilities that no individual can provide alone. The sentence becomes concrete when it is connected to interfaces, incentives, and observable results. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
An app cannot substitute for functioning institutions, public funding, or democratic legitimacy. Civic projects must serve residents who lack smartphones or technical literacy and must not turn essential services into volunteer obligations. The quotation remains useful only when its memorable wording does not erase evidence that points in another direction. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Government systems often expose organizational complexity directly to the public. Pahlka’s framing encourages teams to simplify access, reuse proven components, and measure whether technology improves people’s ability to participate—not merely whether a portal launched. That makes the quotation a tool for present decisions while respecting the limits of the original claim. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Jennifer Pahlka offered this line in her TED2012 talk on civic technology. Pahlka used small public-service applications to show how digital tools could connect residents with city work and with one another. Examples ranged from adopting snow-covered fire hydrants to simplifying school information and reusing an idea across cities. Keeping the original occasion in view protects the quote from being stretched beyond its evidence.
The source record connects the wording to her TED2012 talk on civic technology, which is the context used for this post.
The line defines technology as a means of collective capacity rather than a consumer convenience. Good civic software helps people coordinate around shared infrastructure, rights, and responsibilities that no individual can provide alone. The sentence becomes concrete when it is connected to interfaces, incentives, and observable results. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
The interpretation focuses on a decision or design principle that readers can test against actual systems.
An app cannot substitute for functioning institutions, public funding, or democratic legitimacy. Civic projects must serve residents who lack smartphones or technical literacy and must not turn essential services into volunteer obligations. The quotation remains useful only when its memorable wording does not erase evidence that points in another direction. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Government systems often expose organizational complexity directly to the public. Pahlka’s framing encourages teams to simplify access, reuse proven components, and measure whether technology improves people’s ability to participate—not merely whether a portal launched. That makes the quotation a tool for present decisions while respecting the limits of the original claim. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.