…empfiehlt Jared Spool im Johnny Holland Magazine:
It’s easy to believe them when clients ask us, designers, to make recommendations. We want to believe they love us for our wisdom, knowledge, and experience. They want our advice. And we love giving them advice. It makes us feel smart—like they finally “get” what we’re about. They want to do the right thing and we know how to help them. So, why is it bad to make design recommendations? […]
Simple: The recommendations don’t work. […] Interestingly, in our research, the best teams don’t use recommendations. Instead they use an experimentation approach.
Er plädiert dafür, dass wir zuerst diskutieren welche Ursachen es für beobachtetes Nutzerverhalten gibt, daraus Thesen ableiten und diese im Anschluss überprüfen.
It starts with a team discussion of the underlying observations and what it means. The team explores all the different interpretations. […] Then the team guides the conversation to other research that may fill in any holes, group discussion of alternatives, and measures to signal when the users’ behaviors change in the right direction. Often, this is followed by further research, then more discussion. […]
The result is that the entire team becomes better informed about the design they are building. No one person carries the burden of improving the design. Nobody has to be in the position of being all-knowing, always right. Changes are not seen as final, but as an ongoing process of improvement.