Ship the Right Things Fast with Kano Analysis

Now that we can ship at crazy speed, it's important to think about what you should ship as fast as you can, and what needs more time and preparation for your customers to absorb.

How to decide? Kano analysis is my favorite tool here.

It helps you think about a capability and where it fits on the not implemented vs. implemented scale, and how much it's leading to dissatisfaction vs. satisfaction for your customers + users.

Don't have a capability and your customers are not happy about it? Ship it yesterday. They already know what it is and have expectations on how it will work. Squash bugs. Add that csv export.

Creating something net new that will delight your customers if you do it right? Go fast, but prepare around it. Got a new AI feature that handles a big chunk of workflow automatically? Get all the product marketing, enablement, success, and support functions aligned around a gated release. Too many net new things without that, you will disorient your customers and adoption will suffer.

The nice thing about the Kano model is it helps you reason through things that were "delighters" in the past being table stakes today.

How are you deciding where to let it rip and where to bring the broader organization in before releasing?

Join the conversation on LinkedIn