Kano Categories

Goal

Our roadmap was constantly churning which prevented any kind of planning ahead so I offered up bringing user data into the conversation. This allowed us to slow the churn which enabled us to plan ahead better.

Participant Breakdown

Method

  • Screener questions to find the right participants.

    • 588 Took screener; Passed and gathered data from 61

  • 27 Different features with one sentence description.

  • 3 Questions associated with each feature

  • Categorized each feature into a Kano Bucket

  • 6 Additional insights

  • Paired with qualitative data from interviews that included the same Kano Survey

  • Reviewed with Stakeholders

 

impact

The study facilitated the conversation around how do we leap frog the competition and we made it a goal to balance our releases with "must have"(table stakes) and "attractive"(participants wanted but could or was living without) features. We ended up moving items out of our 60-90 roadmap into the backlog and moved others from the backlog to be planned for beta/GA.

Blurred out roadmap after being assigned Kano category.

 

My Booster Conference talk on this subject

Your product roadmap can basically set your life course as a designer/researcher so why is it so often that User feedback can get lost in the discussion over “Feasibility” of implementation. Without a clear Roadmap Research and Design can often not have the lead time needed for activities. Leading to a state of forever catching up and being reactionary. I am here to talk about my successes and failures trying to bring the user back into the roadmap discussion. I will touch on different prioritization techniques and other research activities that helped me in the fight to bring research into the discussion. Without Research influencing product strategy the product might only have internal stakeholder influence and we all know how that goes. https://2018.boosterconf.no/talks/945 Recorded 15 March 2018 at the Booster conference in Bergen, Norway. www.boosterconf.no