I’m still having a hard time deciding whether Jonathan Berger’s session on Code as Literacy or this one was my favourite. Both sessions gave extremely practical information with a good dose of theory mixed in.
The changing role of design
- Design as team responsibility
- Cross fictional pairing
- Designer as facilitator
- Team as product owner
Research methods
- Team discussion –
- Research planning sessions create interview themes or guides
- Collect stories – what, why and when people actively do. Not what they will do in the future
- A shared framework in which everyone can debrief
- Provisional personas – different team members may have totally different views of users to understand their pain points or what may delight customers
- Defines user hypothesis
- Shared visual artifact
- Evolves over time
- Team interviewing tips
- Pair interviewing – leader and a back up interviewer working off an interview theme
- Multiple note takers – one observation or note per card only
- Group synthesis
- Visual radiator
- Sketch board for personas and research subjects
- Continuous customer engagement
- it should not be a special occasion to talk to your users
- Do testing all the time
- Talk to us button
- Just in time recruiting
- One session, multiple activities
- Listen, gather context
- Collaborative activity
- Product feedback
- If you don’t know what’s going on the profile page…then, everything goes on there
Innovation game –
– put features on sticky notes,
– ask users to choose most important 5 things. Mark them with a 1, remove them
– ask them to do it again. Do about 3 rounds
– then the team stops arguing about its opinions and starts solving issues
Leave a Comment
Let us know your thoughts on this post but remember to place nicely folks!