• Aaron SagrayAaron Sagray, over 2 years ago

    It's great that you got one done in your company!

    Sprints are for solving big problems, not for run of the mill feature work. I don't think there's any company that operates regularly on that schedule. We've run 20+ sprints with different teams in our company over the past 1.5 years. No two sprints are the same, and we almost never use the entire GV playbook. Rather, we tailor exercises from GV, IDEO, and Luma to fit the needs of the problem we're trying to solve and the design maturity of the product team.

    The point of sprints and "design thinking" in general is to get product teams out of the Gartner magic quadrant / feature-train mindset, and instead to approach the challenge from a problem-first perspective.

    The important thing is to use sprints as another tool that you can pull at the right time to solve the right kind of problems. They aren't a substitute for long-term discovery/research projects, design iteration, data science, or usability testing.

    4 points
    • Sylvain MarettoSylvain Maretto, over 2 years ago

      Aaron is right. Sprints are a tool to get going on a big problem to solve, or to get out of a dead-end when you fill your team's creative problem solving is getting exhausted.

      2 points
    • Jennifer Nguyen, over 2 years ago

      Thanks for the explanation! That makes a lot more sense to me. Luckily my company was already doing "design thinking" and that was probably why I felt like Design Sprints moved too fast - it's what we are already doing but much faster. There definitely is a time and place for sprints but it sounds like it's not supposed to be the main go-to strategy.

      0 points