Product discovery workshops are an effective way for product teams to gain a shared understanding of the problem space and develop solutions that address it.

Become familiar with 5 indispensable discovery methods to help you avoid jumping to the wrong opportunities and building the wrong solutions.

Use the abstraction laddering exercise on your product team to define and align around a “why” before executing — or even planning — a feature or a solution.

Ship products that deliver strategic wins, prove the value of product, and secure key alliances with executive leadership.

You're already an expert at developing great products. Now it's time to apply those skills to a product of your own: your job search. (If you're currently looking, that is.) 

Outcomes over outputs is the wrong fight to pick.

Several weeks ago, we sent out a form asking those who subscribe to our newsletter to share suggestions for new terms to replace “Design Thinking.” Since then, we've received and reviewed an impressive 73 submissions. Our team synthesized these insights, pulling out key trends and aligning on one final option. We’re thrilled to share our thoughts and where we ultimately landed!

The New Haircut team is thrilled to welcome Taylor Coil as Product Strategist, supporting the company’s growing clientele of Product teams operating within Fortune 500 companies. With over a decade of experience bringing new products to market, Taylor champions collaborative discovery as a way to help clients grow their businesses through innovation. .

In 1869, Alfred Ely unveiled his Beach Pneumatic Transit. It was to be a series of underground, pressurized tubes that would safely shuttle passengers around New York City. The design was not all that different from Elon Musk's current Hyperloop. This story helps us understand that human-centered design has more stakeholders to regard than just the customer (passengers)

Silos form when Product Managers and UX Leads begin marking their territory, "Product owns this and UX owns that." They get religious about methodologies, "We have Sprint Zero, but they use Design Sprints." The best (worst) is when you hear these groups say, "We all own the customer experience." This is code for, nobody owns it. Because sharing across silos is messy.

Within UX & Product, we have a few catch phrases that end in the word 'driven:' product-driven, design-driven, and customer-driven. And if you dialed it back 10 years - feature-driven.

Problem Prioritization is the first, and arguably, most critical step, you and your team needs to take before beginning the kind ideation that happens within a Design Sprint. In fact, the success of your sprints hinges largely on this often underappreciated, and often botched, pre-step. Here’s how to do it right.