Getting into Design Sprints – an AMA Interview "Product people - Product managers, product designers, UX designers, UX researchers, Business analysts, developers, makers & entrepreneurs 9 August 2017 True AMA, Brainstorming, Collaboration, Design Sprint, Facilitation, Ideation, Interview, Product Design, Prototypes, Prototyping, Ux, Mind the Product Mind the Product Ltd 1843 A Design Sprint session, facilitated by C. Todd Lombardo Product Management 7.372
· 9 minute read

Getting into Design Sprints – an AMA Interview

I recently had the pleasure of taking part in an Ask Me Anything (AMA) discussion in the Mind the Product Slack community, where we talked about Design Sprints, how I take my coffee (a cortado), and my favorite board game (Chutes ‘N Ladders!). I’ve pulled together the Design Sprints bit of the conversation, as I imagine that will be the most interesting to the most people, and I hope you find some of it useful!

Let’s Start With What Design Sprints Actually are

It’s design while wearing running shoes and a track suit!

But seriously, a Design Sprint is a time-boxed problem-solving format that is part design process, part scientific method and part agile mindset. That’s a lot of buzzwords, I know. So let me break that down.

It’s usually five days, one phase/day, though I’ve seen and done many iterations

  1. Understand – dig into the problem, its context, and your assumptions around it
  2. Diverge – generate solutions for the problem
  3. Converge – Select which solutions to prototype and test
  4. Prototype – Build the one or two solution concepts to test
  5. Test – Get the prototype in front of those who will use/buy/interact to observe them and gauge their feedback

Why and when would you use a Design Sprint? And where would you not use them?

Don’t use it to do something simple, like “Where should we add this form?” That likely doesn’t need a Design Sprint. It’s better for when you have a big problem to solve and you don’t have lots of answers. Or there are a lot of assumptions and the team’s unsure of which direction to go.

They’re great when exploring new product areas or product redesigns.

On Understanding Design Sprints

What would be the key distinctions between Design Sprints and Lean UX?

So many similarities! Sometimes I think they’re different sides of the same coin. Both are very experimental in nature (hence the science + design overlap)

  • Design Sprints: I think of it as a time-boxed one-week focused activity
  • Lean UX: approaches could take days or even months depending on what the experiment requires, not quite as structured (for activities) either.

Do you encounter objections in taking engineers away from productive work for five days in order to deliver “just one day of code”?

All the time. The framework encourages, almost by force, a collaborative decision process. This helps the team come to an agreement during the sprint.

My colleague Jill Starret always says:

If your job can survive a week’s vacation, it’ll thrive after a week’s Design Sprint

Are there any technical prerequisites to having an effective Design Sprint and prototypes to test?

Some ideas and prototypes may require live data to test effectively – what we’ve done in those situation is mock it up. For one sprint, we knew who the test participants were and we mocked up six different prototypes with data appropriate to them in order to reduce distraction and increase relevance. Some of the newer prototyping tools allow for these type of data-intensive prototypes.


You’re not building to build, you’re building to answer. The prototype is thrown away after a sprint 99% of the time.

Do you find that the solution that comes out of a Design Sprint is a visiontype, or have you figured out a way to make it a narrow enough scope to complete in a single epic?

That all depends on how you define and narrow the problem on the first day. Sometimes the problem is clear and the range varies greatly. But this would be / should be identified on the first day, and maybe by the second you’ll start to gauge how the solutions you’re generating can be implemented. That’ll also help day three conversations when you select the concepts to build and test.

Could you recommend five prototyping tools to help make the sprint flow smoothly?

In no particular order:

  • Sketch + InVision or Adobe XD (similar IMHO)
  • HTML/CSS /JS if you can code it up quick
  • Paper prototyping
  • Axure
  • Keynote

The GV Design Sprints put the prototype in front of five users. Is five enough?

“Five on Friday” is a great alliteration – Nielson says so (I usually book seven to nine to allow for no-shows)

On Pitching Design Sprints

What’s the most successful Design Sprint you’ve been a part of?

That depends on your definition of success. I did one with a large pharma company (18 people in the room!) and when we asked how long it would have taken them to get where we ended up without a Design Sprint their response was “years!”

As someone that works with clients, do you often come up against them being uncomfortable with ambiguity? And how do you help them understand that uncertainty about the final result is okay?

All the time. You have to manage expectations up front in the sales process (even if just “selling” internally). Many people conflate output and outcome, and it’s always wise to separate the two. While you do create a prototype, the Design Sprint really gets you answers and clarity. Yes, they are intangible, though often far more valuable.

On Facilitation

Who does Freshly Tilled Soil bring to the table when doing a Design Sprint for a client?

We bring a strategist (who’s the facilitator) and a designer, at a minimum. For some bigger sprints we’ve brought a second designer and sometimes a project manager.

The project manager helps photograph and codify all the activities into a Google Spreadsheet (yes, they transcribe all the Post-It notes, etc – super helpful post-sprint) – a good project manager does wonders.

What advice do you have on an adequate amount of prep work before starting a Design Sprint?

I’m glad you realize the need for prep work! Showing up on day one and saying “Let’s do this” is not very wise. Having general direction, team, materials and space are important. Inputs might be UX research, stakeholder interviews, market data, etc.

Have you ever started a Design Sprint and, while running it, realized that it might be not helpful at all? How did you proceed?

Oh hell yes.

Just stop, and realize it’s not the right tool for the job. We did this one where the solution was fairly baked and, two days in, the executive came in and asked what the team was doing since the problem was effectively solved – it just hadn’t been implemented in the project.

The hard part is realizing it.

Which teams do you involved in prototyping? Is it solely down to a UX team, or do you involve other teams that may have feedback as well?

A cross-functional team is best. It’s always helpful to have a designer involved from the beginning of the sprint so they can be well informed and build the prototype quickly. However we have brought in designers just for the third-day sketching sessions so they aren’t completely blind. That’s worked OK, but not quite as well as when they have the full context.

When in the converging phase, I’m finding that there can still be a lot people sticking to their original ideas – are there any techniques you could recommend for helping the team be more open to exploring together?

This is where the approach of identifying the critical assumptions (on day one) for the sprint help. This is also where we differ from the GV approach. Your assumptions become a guide for selecting which ideas to move forward. You wind up removing some of that (sticking to ideas) due to these previously identified assumptions.

If someone wants to become a great Sprint facilitator, what skills or attributes do they need to cultivate?

Just being a good designer, product manager or dev doesn’t make you a good sprint facilitator. You need to learn how to facilitate a group, which is a whole other skillset of listening, guiding, and learning how to lower, or admit, your bias. As a facilitator, you need to listen not to just what’s being said, but also what’s not being said and by whom – pay attention to body language.

For those reading, Dan Brown’s book – Designing Together – is highly recommended if you’re learning about being an effective contributor. And Michael Wilkinson’s Secrets of Facilitation is probably my favorite on facilitation. Other than that:

  • Being able to gauge a group – so “listening with your eyes” is important.
  • Commanding attention not demanding attention.
  • Let the team bungee jump: they can fall, but don’t let ’em hit the ground!

How do you collect your Friday testers, and how many days in advance?

This is always a challenge with any team I’ve worked with. While sometimes it’s difficult to arrange ahead of day one, it’s sometimes possible. I’m wary of going straight to Craigslist or similar open forums even with a solid screener, as some people participate only for the money. 70% of my experience with Design Sprints is B2B, so most often the sponsor/client can make arrangements ahead of (or during) the sprint. Usually by day three we’ve locked down the majority of test interviews and Thursday is confirmation and finalizing.

If you need prospects, call the sales team (if there is one) and get them to give you 10 prospects. If you need current customers, get marketing to surrender a similar set of 10 customers that fit the persona you seek to test with.

A colleague recently went to the Boston Public Library and did guerrilla testing and it did not go so well, so I’d use caution with that kind of random-test approach.

I’ve seen an attitude of boxing the “innovation” into the Design Sprint, and then considering it over afterwards while the “real work” continues. Are there ways to fix that?

Yeah – I’ve experienced that also. Before you even start the sprint, you need to think about what happens next. And then, during the sprint debrief, you can determine next steps. There are typically three outcomes:

  1. You got answers and everything was validated
  2. Nothing worked.
  3. It kind of worked <— this is most common

You need to determine how to address this during the day five retro and debrief. Or yes, it will just die on the vine.

Any recommendations about running sprints with the same groups over and over again? How do you keep your team from burning out on the process?

That’ll actually help you in the long run, as your team will have experience and you won’t have to explain each part of the process over and over. That said, you could look for ways to slightly change exercises. For example – change Goals and Anti-Goals to Hopes and Fears. While I’ve run over 100 sprints myself, I’ve rarely seen two run the same way!

Ask Me Anything!

I had a great time discussing Design Sprints and chatting with product people. If you want, you can always find me on twitter to ask me questions, and I’ll answer as best I can in 140 characters!

Comments 0

Join the community

Sign up for free to share your thoughts

About the author