Hi Francisco, it is difficult to advise with certainty, when not knowing enough. So I just wanted to share an interesting source of activities I found on this website today: Hyper Island Toolbox Check it out. Perhaps, something will jump at you as appropriate for your challenge and best of luck.

I have only had 1 design sprint so far. It lasted 3 days without testing. The preparation for it was long and careful. The work after, took a lot of time and effort too. Participants were very pleased with both: the event itself and the outputs of it. However, before we tried the DS, we faced a lot of opposition from the members of the cross-functional team to the idea. What puzzles me is this paradox: people are prepared to do the daily grind day in day out in an unstructured way with not much to show for it. At the same time, an offer of a 4-day structured format with a promise of something useful and tangible, combined with incredible bonding and learning experience is resisted. I don't know what is behind it, the answers I got were "we have never tried it this way". Any ideas what explains the contradiction I refer to?

@Dana Vetan and @Bryan Guzmán Thank you for your responses. I haven't considered these as possible reasons. Next time, I will try my best to address the fears of failure and loss of control, and try to emphasise the opportunities for input which I think in hindsight were limited for the whole team because we couldn't invite everyone to the sprint.

Yes, I think you are right. It all depends on what people want to achieve. The wheels of governments sometimes move slower. Our guidance says : "How you know discovery is finished Your discovery is finished when you’ve decided whether or not you want to move on to alpha. There a couple of factors that play into this decision, including whether: - there’s a viable service you could build that would make it easier for users to do the thing they need to do - it’s cost effective to pursue the problem - this means weighing up how much it’d cost against how much of an improvement you think you could make"

An interesting question, John. Feels to me like comparing apples and oranges though ;-). Only yesterday, I watched a video https://youtu.be/MDY8IZX3IXY from Jeff Gothelf - Lean vs Agile vs Design Thinking. One of the things I learned from it: there is an artificial distinction often made between different techniques and approaches. Perhaps more useful for practitioners is to rise above these seeming distinctions and look for common principles, some of which Jeff shares in his engaging and often funny video. I also feel that we have created a language that separates us from people we call "users". I wonder whether anyone thought about the way we could go back to simple everyday language to interact with those for whom we build digital products and services?

I have recently come across a tool which I am yet to use in a workshop: LOOPY (v1.1) (ncase.me) Its purpose is to engage people in working out together the cause and effect relationships between events in a visual manner. It is very easy to use. It is free. It is visually appealing. I am looking forward to testing its powers and will be looking up the link you have shared, Dana.

Let us know what happens once you try it. And best of luck!