6
Just got my team to agree on a new data privacy rule after a month of arguing
We had to pick between two ways to handle user data for our new app feature. Option one was to collect a lot of extra info to make the feature work really well, but it felt a bit creepy. Option two was way more basic and private, but it wouldn't be as smart. I pushed hard for option two, the basic one. It meant we had to spend an extra two weeks figuring out a simpler way to make the feature useful. We launched it last Friday, and the first user feedback is in. People really liked the clear note about what data we don't collect. It feels like a small win for doing the right thing, even if it was harder. Has anyone else had to fight for a less 'smart' but more private design choice?
3 comments
Log in to join the discussion
Log In3 Comments
the_lisa24d ago
Good on you for pushing through that! My old company wanted to add location tracking to a simple weather widget, just to show "hyper-local" ads. We argued it was a solution hunting for a problem that didn't exist. It took three meetings to kill it, but the relief was huge. Building trust should be the default, not an afterthought you have to fight for.
4
anna57824d ago
Glad you stuck with the basic option, that's the move every time. I mean, you can always add more data later if you really need it, but you can't really take it back once people get creeped out. We had to explain to our product team that a slightly worse suggestion feature was worth not tracking every single click. It feels like extra work now, but it saves so many headaches and bad reviews down the line.
2