We use google design sprint. The first time was a bit of figuring the exercise that work for our process, trial run. Second time was when you really narrow in on the process. When you push through the first day (Understanding) and everyone is running in the same direction, that's really exciting, to have the whole team solving the right problem. Define the right problem is crucial in your success, do not take this phase lightly or the rest of the week is pointless.

Martin, we've now published how we run sprints. I hope you'll find it useful.

https://medium.com/nordnet-design-studio/design-is-a-team-sport-231a602fc072#.buigjvg2u

Best,

Marcus

Design Sprints has become our way of working. For every initiative we work on, we use Design Sprints.

It's a Design Thinking approach in disguise. Using Design Sprints has made (in our opinion) our organization more customer-focused and design driven.

I feel that the method is a game-changer for our profession. I foresee that designers will become more and more like facilitators of a design process. Designers shouldn't be the only ones dictating the customer experience. Everyone should feel ownership and be involved in the journey. Design sprinting is a way to push that notion.

At work, we talk about "Design is a team sport". I feel that that's where we're heading. If you want to solve a problem, you need to involve many different perspectives. Designers are only one part of the equation.

If you're interested in learning more about how we run Design Sprints, please check our podcast. In the following episodes, we talk in detail about how our way of working:

https://soundcloud.com/slowtofast/slowtofast-ep-01-on-diamonds-and-happiness

https://soundcloud.com/slowtofast/slowtofast-ep-06-using-resource-limitations-creative-chaos-agile-happiness-to-your-advantage

We're also working on an in-depth Medium article about our sprinting approach.

Best of luck and have a great weekend,

Marcus

We use design sprints in almost all our conceptual work. It's a great way of coming up with, and testing stuff, fast and efficient. Works great with clients. Takes some gettings used to, and some variations based on the project and client (unpack for example usually takes 2-3 days in a normal project for us - decide less than a day). Start on an internal project before testing it out on clients is my recommendation.

Very hard to carve out time for the whole team to participate in a formal design sprint. But I use elements of the process like design studio all the time: http://www.bigspaceship.com/design-studio/

Anytime you can bring together the team to define and breakdown a problem together, magic happens.

I've been part of one or two design sprint style projects. The difficult part for us was fitting in user testing or some other kind of validation into the sprint. Haven't read the book so looking forward to finding out how to do this more effectively.