I'm running a design sprint next week and need to create a Journey Map on the first day. Ideally, I'd build it beforehand based on research, but that's not possible in this case. The team is unfamiliar with Journey Maps and this type of diagrams, but is very familiar with the context of the sprint challenge as well as with the User typical experiences. I'm thinking of using ChatGPT as a starting point for the Journey Map. Does anyone have suggestions or prompt ideas?

Hello everyone!, Reaching out to all for your advice/guidance. I'm currently working with 3 startups: 1) First startup is already in the market but needs help re-validating the problem and identifying the right customer profile to work on. 2) The second startup is currently running their beta and wants to evaluate the customer experience and identify the right customer profile to target 3) The third has developed an MVP but wants to do some market discovery to identify the gaps in the market and tailor their solution accordingly. I had a briefing call with all the three and we identified the customers to reach out to for interviews and also came up with the list of interview questions to ask, but somehow the founders are finding it difficult to convince the customers to do the interviews. They are just not interested. My question to you all: 1) What could these founders do differently to get their customers to do these interviews? (In general, how can we convince our customers to do interviews to share their experience with our product or just share their pain points and problem areas) 2) From your experience, how much should I be involved with these customers in doing these interviews? Should I just let them do the interviews and wait for them to come back with the interview notes or should I participate in the interviews which not all of them would be comfortable with? My apologies for the long post but any help in this regard would be greatly appreciated! Thanks, Riaz

If a 🏃‍♀️Design Sprint takes a team from problem to solution in 1 week, how long do you think that the Problem 🔎Discovery/Definition phase should take?

At Design Sprint Academy, our shortest sprint is a 3-day sprint designed specifically for hackathon events. By reducing the prototyping phase to 4 hours and limiting user interviews to only 2, we're able to effectively compress Day 3 and Day 4 into one intense day. I'm curious, what's been your experience with short design sprint workshops?

How do you check if the exercise, the method, and the icebreaker you plan to use for your next workshop will achieve the desired result? I'm cautious with these things, as many tools are oversold, and they do not deliver in the end. For a while, I went to Liberating Structures meetups where the facilitator would try things out, and that was valuable. As a participant, I could sense how all the small activities and warm-ups affected me. But now it is more challenging to make time for this, so what do you recommend? How do you prove your selected methods?