@Dana Vetan OK gotcha. Yes, we task the teams to really get to grips with functional inputs and outputs with a Data Management Plan/canvas, understand integration by mapping System Architecture (map data pipelines + AI model integration) and build with automation tools eg. Make or in-house tools eg. CoPilot directly. We include a data scientist or engineer familiar with their tool stack and do a lightning talk about it depending on their level.

@Christoph Piller I hear you! If initial conversations indicate it may be a possibility to use AI - we'd invite someone from tech to give overview eg. of tech stack and possible roadmap related to that challenge area and keep them as a 'mentor' throughout sprint if they can't join the whole thing - like a hackathon. My sprints are very hackathon-y. We'd add a short 30min training- sometimes it's easier to create directly onto these tools than to mock up a prototype.

🙌 Hackathon-fan here - but mine are very user-centric so I feel like they are condensed Design Sprints :D We've done 1-day design sprints in the past - but didn't involve user tests. My preferred format is a 4-day Design sprint including tests.

While I like the idea for workshop planning + agenda - I find existing tools (SessionLab etc) do the job well - HOWEVER I totally love those prompt examples for workshop content creation and accelerating sprint prep... narrowing down research focus solves a real pain-point for me (often gets stuck into a big idea only for it to be totally irrelevant!). An interesting use case for User Test Scripts - I tend to use my GDoc templates then replace the text related to the opening context Q, scenario prompts, key feature Q etc. But could see this helping - I'll have to check it out more! Thank you

For me Design Sprints is Design Thinking in action :D I often open the sprint with the triple diamond to outline the process.