@futurebird @aeveltstra

Yeah re: help functions maybe the more general Unified Law of Software is something like: Features are Constituted by the Expectations User Have of Them, i.e. if no one expects something to work then it never will. The only way things get fixed is if the product manager's mental model of their user is a person who would care about something being broken. One of many ways in which agile has deeply broken our expectations of the world.

@futurebird @aeveltstra I agree that this ought to be considered a core feature, but that unfortunately is the myth of progress at work.

Realistically speaking if a use case is sufficiently obscure that someone would expect to need to do an internet search to figure out how to do it/remind themselves how they did it last time, then that use case will never be considered core to the product by the product managers, and it will be lost in one or another rearchitecture. (In this case it was not lost, but explicitly moved to a plugin, away from the "core" feature set of Google Docs.)

But the social dynamic at play feels like a physical force in the development of software, once you know it well enough to recognize it.