» Asking about a specific problem causes people to ignore the other problems they have
» Make time for product discovery in small steps, not all at once
» Biases reduce cognitive load for our brain when it processes new information
» An opportunity solution tree is a way to externalize your thinking
» Don’t specify rigid requirements to your delivery team, have a collaborative conversation instead
» Try out lots of different solutions to the same problem
» Don’t be pressured to rush through discovery and prototyping
» Share knowledge around your team
» Avoid misunderstandings through constant communication with stakeholders
» Focus your prototyping on the moments that matter most to users
» Prototypes range in fidelity, but remain throwaway
» Prototyping brings tangibility to intangible experiences
» Be clear about what you want to learn, and what assumptions you want to test
» Design simply to deliver early and learn quickly
» Learning is more valuable than being successful and not knowing why
» You can experiment with the content and layout of any web-based product with basic skills
» The success rate of experimentation is higher if there is no penalty for failing
» “If you have a good idea on a Monday and can design, test and learn by the Friday, then innovation explodes.”
This is a little post about some ways to convince a reluctant development team that experimentation is A Good Thing.
