Categories
-
Community
-
Delivery
- A Happening
- All Citizens
- As Simple As Possible
- Bridging tech capacity
- Content Before Engineering
- Correlation Isn't Causation
- Data Spills Kill The Environment
- Define Failure
- Digitize a Process
- Do Your Homework
- Don't Reinvent The Wheel
- Don't Wait, Scrape
- Eat Your Own Dog Food
- Eliminate Your Job
- Faster Horses
- Fuck It Ship It
- Gamification
- Keep The World Informed
- Kill Switch
- Launch Without A Home Page
- Launching Is Just The Start
- Make it Mobile
- Measure The Right Things
- Open Your Admin
- Say No
- Scratch Your Own Itch
- Start With The Citizen
- Think Backwards
- Worry About Abuse Later
-
Government
-
Engagement
- Big Button
- Build It They Wont Come
- Don't Educate
- Early Adopters Are Strange
- Give Someone A Headache
- Give Something Back
- Harness Self Interest
- Have a Business Model
- Intention Over Practice
- Make Your Own Reality
- Missionary Without A Cause
- Next Step
- No Score Card
- Personalize It
- Presentation is important
- Progress Bar
- Push Don't Pull
- Remove A Headache
- Something Must Happen
- The Administrator
- What Does It Do?
Pattern: Clean Room
If your project operates within any bureaucratic system, ensure that the person responsible for its design knows as little as possible about how the existing system works.
Most people hate dealing with bureaucracies. You have to jump through lots of seemingly pointless hoops, just for the sake of the system. But the more you’re exposed to it, the more sense it starts to make, and the harder it is to see things through a beginner’s eyes. Therefore, when building a system that helps someone bypass bureaucracy, start by designing how the system should be, with as little pre-knowledge as possible, and then, when you need to add any complexity, work as hard as you can to hide that from the user.