Comment by pixl97
10 days ago
>As features keep getting added ... so things need to be hidden
Here lies the problem
Your first users were here without all the added features. It's very likely they didn't need those features to use the software. Then you add new features and clutter it... then remove features from the UX that they were using.
> then remove features from the UX that they were using
Yeah but like I said, people make mistakes. The thing about text output is that it's impossible to track if people are using it at first. You can measure button clicks and key presses. You can't measure eye gaze (at least not usually!).
The good news is, if you remove it and get complaints, you can measure complaints. If you put in a toggle to re-enable it, you can measure how many people activate the toggle. Then you actually have the data, so you can decide whether to just bring it back entirely, or keep it as a toggle, or what.
PM's and designers aren't omniscient. If a feature is view-only, you literally can't tell how much it's used, and it might be minor enough that you never ask about it in user interviews.
>You can measure button clicks and key presses.
This is a common failure complain of all large companies that use metrics but don't actually talk to people. It's not a new complaint at all. And at the day it's one only solved by users throwing an apocalyptic fucking fit at the group producing the software.
>If a feature is view-only, you literally can't tell how much it's used
Then think fucking twice and don't touch it.
I don't know why you're so angry about it.
Large companies do talk to people. User interviews are extremely common -- it's standard practice that you need to use metrics and talk to users. But like I said, interviews aren't going to cover every tiny little detail.
PM's and designers usually do think twice. But they're human, they're not omniscient. So maybe show a little grace?