Without the why and who, we create nothing for nobody.
- Who are the people that will use the applications?
- Why would they use this?
- What problem does this solve for them?
- Is the user the buyer?
- What does the team think?
- What have they tried in the past?
- What do people say about the application?
- What do people actually do with the application?
- What data can we study?
- What is the competition doing?
- What is the business value?
- What business domain does the app exist in?
- What are the norms of the domain?
Fail often and fail early.
- Generate Ideas.
- Write a user story.
- Pencil sketch.
- Draw a wire frame.
- Establish shared vision.
- Is this what you expected?
- Negotiate with team and stakeholder.
- Do Technical validation.
- Can we do this?
Devil in the Detail
- Map the application flow.
- Design the details of every screen.
- Show first time experience.
- Align to brand
- Establish application visual design
- Craft tone, voice and messaging
- Work on iconography, illustration and photography
It's cheaper to fail with a prototype than an application.
- Create a clickable interactive simulation
- Create it based on expected behavior
- Use animation to orient the user
What people say, people mean, people do - three different things. What we care about is do.
- Run a real test with actual users.
- Can a user execute the task?
- Does the user find value?
Move forward when you succeed. Step back when you hit wall.