> Honestly, I would not hire a single manager from these big companies because they operate in an environment where they're playing with monopoly money and don't know what reality is.
In part, to unpack why part of this glib take is missing the complexity, "don't know what reality is", is that finding reality is slow and costly.
Perhaps your team provides a platform which is used internally by several other teams building various products. It supports a bunch of use cases, but it's hard to evaluate the actual ROI of the platform you provide, both because no one knows how much better/worse those products would have been without your platform. Would they have taken months longer to implement? Would they have not been possible without spinning up a team like yours?
Further, some of those products actually are used by paying customers, and others are still in development. Of the products used by paying customers, it's unclear which they would actually pay to use vs which they use because it's available in their subscription basket (e.g. is Dropbox Paper making money or is it just that some Dropbox customers use it but would pay the same sync subscription if Paper was killed?). Of the products that are not yet in customers hands, how should you value them? If your small team supports multiple in-development products, that must be worth something even if they're not revenue-producing yet.
Similarly, suppose you're a manager who runs a team building a product which has dependencies on multiple platform/infra teams -- do you really have visibility into the real costs that your team's requests create? Can you really know the ROI of your team, to guide choices about various investments?
This kind of ambiguity means that even when leadership wants to see which teams are really contributing value and how much, it's quite difficult to see. Teams may optimistically estimate their own value because they cannot see all of the costs to which they contribute, or because they cannot see which revenue-affiliated use is actually valuable.
In part, to unpack why part of this glib take is missing the complexity, "don't know what reality is", is that finding reality is slow and costly. Perhaps your team provides a platform which is used internally by several other teams building various products. It supports a bunch of use cases, but it's hard to evaluate the actual ROI of the platform you provide, both because no one knows how much better/worse those products would have been without your platform. Would they have taken months longer to implement? Would they have not been possible without spinning up a team like yours?
Further, some of those products actually are used by paying customers, and others are still in development. Of the products used by paying customers, it's unclear which they would actually pay to use vs which they use because it's available in their subscription basket (e.g. is Dropbox Paper making money or is it just that some Dropbox customers use it but would pay the same sync subscription if Paper was killed?). Of the products that are not yet in customers hands, how should you value them? If your small team supports multiple in-development products, that must be worth something even if they're not revenue-producing yet.
Similarly, suppose you're a manager who runs a team building a product which has dependencies on multiple platform/infra teams -- do you really have visibility into the real costs that your team's requests create? Can you really know the ROI of your team, to guide choices about various investments?
This kind of ambiguity means that even when leadership wants to see which teams are really contributing value and how much, it's quite difficult to see. Teams may optimistically estimate their own value because they cannot see all of the costs to which they contribute, or because they cannot see which revenue-affiliated use is actually valuable.