But it’s not reasonable for me to assume that readers would get that from my quip.
I think that I try this to try to break out of the paths where we inappropriately limit the scope to the point we can be sound in designing a solution that fits our narrowed scope but missed the goal that we were trying to achieve. I think in this case that the assumption that the goal is to fix google leaves out the individual who has mixed duties to the organization and themself. I probably get too emotional when I frequently see discussions that try to box me into being part of the solution and I see this quite a bit in product design. I see discussions around products where a complaint is met with discussion around the need to provide a solution. So the discussion spirals around kind of assuming the only options for users are: 1) propose solutions, 2) keep using. But there are three options: 1) propose solutions, 2) keep using, 3) stop using. And assuming that all users operate with only the first two options makes it more likely to only design around those two.