Keynote: Get Rich Quick
Hard for business owners to translate from what they actually want to functional requirements. Challenge is to give what they need. To the user, the interface "is" the application. Separate two elements: aesthetics of the interface and the user experience. First isn't hard to convey, second is.
Answer agile development [ed: who didn't see that coming?]. But: problem = phase 2 development often requires refactoring or redesign of phase 1 datamodel. Use agile approach to build UI in phases without backend development.
"High fidelity prototyping". Look for user's emotional response to proposed design. But building prototype has to be efficient.
- Paper. Pro: fastest. Con: only for early phases, doesn't work for distributed teams.
- static html wireframe – lots of effort, too much to throw away
- photoshop - – good for aesthetic design. Still hard work. Lo-fidelity for rich apps.
- HTML scripts – generated server side, so how to handle that in a rapid prototype. Don't want to have to spend a lot of time programming / simulating server side code
- Ajax - either have to mock ajax calls, or build server-side mocks
Build a prototype in days or weeks. Build a prototype that is not throwaway, but will be the UI for the final app. Expectation management is key: users must not believe the app is done.
Goals: Avoid CGI. Has to be simple. Easy to mock, and replace post-prototyping phase.