Many infrastructure development teams don’t have a product manager. That forces an architect or senior developer to manage a range of responsibilities they are not best equipped to handle: settling conflicting business priorities; internally “selling” the value of architecture; tying technical decisions to business metrics; making connections between software and end user joy.
There are some fundamental laws of tech product economics (especially software) that should drive executive-level decisions about business and product strategies. It’s easy to forget them, or decide they don’t apply to our special situation. We unpacked a few.