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: Think Backwards
Start by describing what you want to achieve for your users, and then work out the steps to get there.
Start with your user. Who are they and what problems do they have? What would a good solution mean for them? What might that solution look like?
Don’t get distracted by what you’re able to build, focus on what you should build. By focusing on what your user needs – and not what your team wants to build – you’re more likely to solve a real world problem and not be boxed in by old, outdated ideas and tools.