Misfit Radar

A small internal tool that collects the quiet signals a product already produces (changed settings, repeated support tickets, workarounds people describe) and groups them into misfits: places where the product and its people disagree.

Why it exists

Teams notice misfits one at a time, usually late. Misfit Radar makes them visible as a category, weekly, before anyone has to complain loudly.

How it works

Each signal is tagged with the screen, the setting or the task it touches. Signals that touch the same thing are clustered, named in plain words, and ranked by how many people they affect and how often they come back.

A cluster is not a bug list. It is a sentence that starts with “people expect” and ends with “but the product assumes”.

What it changed

Roadmap reviews start from the top five clusters instead of the loudest request. Two features were simplified rather than extended.

Behind this

concepts
Misfits as signalsPsychographic defaults
connections
Settings are complaintsERP misfits meet product UXPersonality meets defaults
notes
Every setting someone changes is a tiny complaint.The same support ticket, for the third time this month.Reading: Jegorova and Grabis on LLM-assisted ERP misfits.The feature nobody uses is still a feature someone maintains.Defaults decide more than recommendations do.Personalise to values, not to clicks.