Rumbling with discomfort to discover my most meaningful work as a facilitator.

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.

As designers and innovators, why are we so quick to practice empathy & compassion with our users but not our fellow team members? The real work required to generate results from innovation programs starts with the relationships we nurture inside our teams.

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.

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.

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.

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.

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.

Learn how a global publishing powerhouse that’s nearly 2 centuries old is using design sprints to power their product innovation.

When we think about design sprints, design thinking, and innovation, cancer probably isn’t often the first topic that comes to mind.

One of the biggest assumptions the Sprint book made was that readers already understood how to select the most critical, most appropriate challenges on which to run a design sprint.

First impressions are lasting, especially when they cost time, money, and reputation.

In our last discussion we talked about the #1 design sprint question we hear — “What happens after a design sprint?”

Back in March of 2016, myself and everyone at New Haircut read the Sprint book by the team at GV. We were excited about the framework but weren’t exactly sure how to get started. As well-structured and easy-to-digest as the book was, we still had a myriad of questions…