Over the years of refining our Problem Framing process, we’ve heard lots of great questions that helped us shape our approach. Here, we summarize the best & most repeated questions we’ve heard.

Stories, tools, and resources for facilitators and innovation teams hoping to begin running remote design sprints. Plus, a new option to review with your team.

My story of discovering, first-hand, how important psychological safety is to teams using design thinking and design sprints to spur innovation. And some simple techniques for you to consider in your next sprint.

After nearly 3 years of training individuals, teams, and organizations on design sprints, 1 thing I’ve learned is that you can never create and gather enough materials to share with people who are hungry to learn. And so today I come bearing gifts.

The most important lesson I’ve learned about design thinking that’s helped me appreciate its real value.

Instead of writing a recap, I decided to share a story about my personal relationship with design sprints and how the conference provided me with validation, clarity, pride, and inspiration for the journey I’ve been on over the past few years… plus a few pics :)

In this article, we’re going to walk through Step 3 by getting familiar with the overall user experience surrounding this problem.

A walkthrough of the design thinking process we use inside New Haircut to discover, prioritize, and humanize critical business opportunities. It’s our go-to practice we use prior to running a design sprint.

How to successfully introduce and implement sprints inside corporate environments.

Agile was never meant to be the silver bullet that consultants claim it to be or that which revenue-obsessed executives bet the farm on.

Three things product leaders can do to evolve from endless discussions about changing priorities and # of shipped features, to building better products in less time that the entire team is proud of.

13 things you can do to get senior leadership to say yes to design sprints…and subsequently make yourself one of the most highly sought after resources in your company.

One of our most liked and shared articles from last year, attempted to answer the most popular question we hear when helping teams run design sprints — “What happens before a design sprint?”

How to spend 1 day getting your team aligned around a big, important problem, before plunging into prototypes and MVPs.

How some companies thrive with completely dispersed workforces while others flounder with last-century control policies like punch-clocks.

Two things you must do as a CEO if you want to help your product development teams build scalable technology businesses (not just an app).

Google Design hosted the first ever Sprint Conference this past week in San Francisco (#SprintCon17). The conference brought together the most trailblazing of design sprint leaders.

Turns out, when companies grow to several thousand employees, and certainly several hundred thousand, it becomes necessary for someone to make sure information is getting shared. Shared across people, functions, departments, delivery centers, and continents, as effectively as possible.

How and when to connect these powerful frameworks to create new products or rethink existing ones.