Field note · 8 February 2026
How to sit with someone who turned a feature off
The people who disable a capability are often the most precise witnesses, provided you do not spend the hour trying to win them back.
Mei Ling Tan
Abandoned-Feature Interviews fail when the interviewer treats the sitting as a chance to re-explain the feature. The person already knows where the switch is. They used it. What they can tell you, if you leave the demo in the bag, is the hour they decided the capability was costing them something they valued more: quiet, speed, or the goodwill of a colleague.
We start with the last time they remember the feature doing something in front of them. Not the first time. The last time is closer to the decision. Then we ask what they did instead that same afternoon. The substitute is the real finding. It might be a paper stamp on a delivery note, a formula a teammate already maintains, or simply leaving the field blank and hoping nobody asks.
In a study of a document editor’s “suggesting” mode, several writers in a Kajang office had switched it off after a manager treated every suggestion as a disagreement. The feature was working as designed. The social reading of the red marks was what they refused to live with. No tooltip was going to repair that. The write-up had to say so plainly, even though the product group had hoped for a copy change.
Consent matters more in these sittings than in happy-path walkthroughs. People who turned something off often feel they will be blamed. We tell them, before the recorder goes on, that their employer will not receive their name next to the quote. If they still hesitate, we close the notebook. A forced interview about abandonment is worthless.
If you already have a list of accounts that used a feature and then disabled it, send the list. If you only have a feeling that “nobody likes the new pane,” we can still recruit, but we will spend the first week finding people who actually touched the switch.