I finally got out of the rabbit hole !
My plan was to extend some battle tested method of user research to achieve my objectives (the Kano Model, maybe you'll find the pun in my version's name). It turns out that the more I looked into it, the more flaws I saw in the methodology commonly used. Not only in the data analysis part, but in the approach and expectations of it.
I spent weeks deconstructing it and rebuilding a data analysis that satisfied me and included my factors. It was a big dive into statistical sciences. It was intense but now I'm 100% confident in my approach.
The idea behind Kuma came to me during the coronavirus confinement. I watched the startup ecosystem rush to adapt to the new normal and I wondered how I would help them to understand what to build in this short time and under pressure.
As an UX designer, I see myself as a user's advocate. We have tools and methodologies to understand their needs and how to create a product that fulfill them seamlessly.
But more often than not, this research is high level (we identify pain, motivation or engagement) and useful only in the scope of UX. The product owner has to make a call when deciding what to build. If they're good, they understand the reach of the UX research. Most of the time it's a combination of personal appeal, business opportunities and a bit of user research.
What if I could design a methodology based on user research, but that could inform business implications ? What if I could help product managers and founders easily figure out what's best to build and how to build it, with actionable data ?