Mind-blowingly great post from Firefox’s lead designer (now a dead link) Aza Raskin on the power of prototyping as communication, why you need to start with design and how to communicate ideas visually since it’s all about influencing people. Like, wow… And very topical for my team at the moment (which does not have a designer or front-end engineer). And it definitely re-affirms Agile as a process.
To Design is to inspire participation.
No matter how good you are there is no substitute for trying it. You are wrong.
Even love the way he’s distilled the principles into a checklist:
- Your first try will be wrong. Budget and design for it.
- Aim to finish a usable artifact in a day. This helps you focus and scope.
- You are making a touchable sketch. Do not fill in all the lines.
- You are iterating your solution as well as your understanding of the problem.
- Treat your code as throw-away, but be ready to refactor.
- Borrow liberally
- Tell a story with your prototype. It isn’t just a set of features.
Also, I’d highly recommend Asa’s So You Want to Be a Designer post (dead link) as well. Gold.
via O’Reilly Radar.