"Build to learn" is waste.
"add this feature to the app so that users can use it" is no better than "write me this article so that people can read it" aka working for exposure.
spavel.medium.com
Stop building features “for exposure”
Without a coherent hypothesis for both user outcomes & business impact, a product team’s outputs are waste rather than value
