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: Fuck It Ship It
Publish your prototype as soon as possible, instead of trying to build a full product.
The sooner you put your product in front of users, the sooner you’ll get valuable feedback. Build the minimum viable product that makes sense and release it as soon as you can. It doesn’t need to be perfect, and it doesn’t need to be complete.
In all likelihood at least some of your assumptions about your product are wrong. The best way to find out which ones is to test them on real users. It’s far cheaper to discover them sooner, when you can correct them cheaply, than to discover them later after wasting a lot of time and money.