Two dozen things we have learned from running design sprints
Design sprints have become pretty popular with the advent of agile approaches to development. According to the good folks at Google Developers, a design sprint is "...a structured brainstorm based on design thinking and agile development." Done well, they can springboard your product development. Done badly, they can waste a lot of people's time, lead to poor decision-making, agenda stacking and recrimination. We've done both.
This talk will give a warts-and-all-view of what to do and what not to do from our experience.
Martin is a Senior UX Researcher at Trade Me in New Zealand. He’s been working in the digital industry since before the web started. He once told the editor of the British Weekly Telegraph that there was this thing called ‘the Internet’ that he should consider putting his paper on.
Martin started his career at BT Research Laboratories Human Factors Unit where he worked on projects as diverse as the interaction design of collaborative virtual environments, the world’s first TV-on-demand service, and the development of design standards for BT, which included the design of the striped tents that cable engineers brew their tea in.
At Trade Me, Martin is part of a five-person team responsible for getting the user’s voice heard across the company, providing research-based knowledge and insights to support business decisions.
More Wonderful Speakers
Under the influence: Exploring Dark Patterns and the power of Persuasive Design
UX Car Crash: What we can learn from the agonizing defeats and spectacular triumphs of people's first attempts at UX design