What should I ask myself when designing an experience?
1 min readMar 15, 2016
- Who am I designing for?
- How am I improving upon existing behavior/functionality?
- How can I reduce any perceived learning curves?
- What are the main features of <product>?
- Why does <user> need <product/feature>?
- Which device will the user be most likely to use for <product/feature>?
- What does <product/feature> help the user accomplish?
- Is <feature> a common UI pattern on <device/operating system>?
- How do I encourage <behavior> for <feature/product>?
- When/where is the user most likely to engage with <feature/product>?
