Readying the "clone-a-survey" feature for kanochart v2, so that you can compare surveys over time and between segments.
Nope - bad idea. See later posts :)
Big shift in kanochart v2's datamodel. Refactoring done.
Surveys used to be the focal point of Kanochart, but that doesn't make sense. The *feature* should be front and center. After all, that's what a user is interested in. This "discovery" of mine led to a lot of changes in the underlying data model, but this opens up many many possibilities for the future.
Asking feedback from current users about what should go in v2
Fixed a bug where highly Indifferent features were ranked higher than low Indifferents (should be the reverse of course)
Response labels are now customizable in your survey
Added basic frequency-based categorization to the v2 reports
Created a script to migrate surveys and analyses to the new kanochart datamodel
Brought down the time to do a Kano analysis of 1.000 responses from 14 seconds to < 0.1 second 🏎️
Spent quite a bit of time deciding on the ranking algorithm for the new kanochart.com
This one is for the Kano nerds 🤓
Features are prioritized as follows:
- Features in the positive quadrant (the area enclosed by dashes) rank higher than the one outside the quadrant, even if their category is higher (see features ranked #1 and #4, where #2 and #3 are of a "lesser" category, but still fall within the positive quadrant);
- Then, feature category determines priority. Must > Perform > Attract > Indifferent > Reverse > Questionable. Features that fall in the latter two categories shouldn't be on your roadmap anyway; you should rethink them.
- Features in the same category are ranked according to their distance from the middle of the positive quadrant (x:Live With, y:Expect). #2 is a stronger Perform feature than #3 and therefore ranks higher.
Features are prioritized as follows:
- Features in the positive quadrant (the area enclosed by dashes) rank higher than the one outside the quadrant, even if their category is higher (see features ranked #1 and #4, where #2 and #3 are of a "lesser" category, but still fall within the positive quadrant);
- Then, feature category determines priority. Must > Perform > Attract > Indifferent > Reverse > Questionable. Features that fall in the latter two categories shouldn't be on your roadmap anyway; you should rethink them.
- Features in the same category are ranked according to their distance from the middle of the positive quadrant (x:Live With, y:Expect). #2 is a stronger Perform feature than #3 and therefore ranks higher.
Finally got around to creating more interactive charts
Finalized the summary Kano chart
Display charts per feature
Found out about Vega-Lite (https://vega.github.io/vega-lite/docs/) and its awesome configurability. Can't stop playing with it -- the new kanocharts.com will live up to its name :)
Completed first version of independent Kano analysis library
First draft of the new survey format for kanochart.com
Implemented a more flexible email/password authentication for the kanochart.com overhaul
But why do I keep rolling my own 🙄
Installed the @SourceryAI plugin to learn and increase code quality
Added login endpoints
Making it harder for myself by making sure things work when user has disabled JavaScript too
When creating a survey, set the order of the questions through drag & drop.
Setup a FastAPI + TailwindCSS + AlpineJS dev environment to start the kanochart.com overhaul
After 2 years of intense use by myself and user feedback it's time to rebuild kanochart.com and make it even more valuable to product managers and makers.
First to-do: survey creation overhaul.
First to-do: survey creation overhaul.
Added extra features to help people who want to do large-scale surveys
Improved the machine-learning algorithms 🤖 to segment user answers
Talked to a user from yet another agency
- ◄ Previous
- 1
- Next ►