On Wednesday evening the 1st of May 2019, we put together an event to try and assemble the Manchester Design Sprint community to start creating a dialogue amongst ourselves. I learned a lot speaking to experts in their fields individually and knew that as a city we had come so far since the original Sprint book came out. Suffice to say it was a brilliant night despite football attempting to take the spotlight as usual.
Event link: https://tsf.tech/2TtgvIP
Not sure if it’s worth reading on? See what some of our attendees thought.
Tom Highton on LinkedIn: "Great event last night at Federeration House, MCR to discuss #UX…
May 2, 2019: Tom Highton posted on LinkedIn
For those that didn’t manage to make it but wanted to know more about the experts that generously gave their time to be there, here are all their details again. In order of how Medium imported the images 😂:
For the open questions section we had a variety of compelling and thought-provoking questions. Some questions were reasonably straightforward with the collective expertise we had, but others were recurring problems that we had all encountered and didn’t have one bullet-proof answer to share. One thing for certain was that communicating with stakeholders and getting alignment was a strong recurring theme.
Here’s a replay of the questions answered on the night:
- Can I replace my design processes with Design sprints?
- Whats the 1 quickest way to learn everything you need to know to run your first design sprint, without information overload.
- How do you ‘sell’ design sprints to stakeholders or clients?
- What problems can occur when looking to implement design sprints into a organisation for the first time?
- How do you handle design sprints where stakeholders are dropping in and out of the process?
- What are best practices to feed the output from the Design sprint into the development process?
- How did you get into carrying out design sprints?
- How do I tell a good designer from a bad one? I can run a crazy eights session but it doesn’t mean I understand the process.
- User testing with 4–6 users seems small to get useful feedback, have you ever tried a larger sample?
- Is there a checklist type of resource, like a printable for the facilitator to use during the sprint. (this one’s free: view the pdf here)
- When is it best to avoid using the design thinking or design sprint methodology?
- Have you ever tried to validated the ‘stickiness’ of a product as part of a design sprint — and how?
- Design thinking is the new cool thing for execs to do. How do we ensure it is seen as an operational process?
- Is there anyway to apply the design sprint to personal life?
- What is the weirdest design sprint you’ve ever done?
- If you could rename the design sprint to something that would resonate with the client and reflect what it does what would you call it?
- What pre-research do you do prior to a design sprint?
If you want the answers, you’ll have to reach out to us individually or look out for the next event 😉.
Lastly, here’s a few common resources that people asked for, or mentioned during the night. It’s not exhaustive so if I missed anything please let me know and I’ll add it and credit (!) you.
Thanks again to all the experts, to the Co-op Foundation and The Federation, in partnership with Luminate for the venue, tsf.tech for pizza and beer, and finally all the attendees for making it worthwhile organising this event.
You can engage with me on Twitter (@chuckwired) about anything design, Design Sprints, or tech startup.