Dale McCrory, Software and Product Management Leader at Breeze Strategy
Yeah. I mean, they're technical configurations, but they have a life cycle and that's the key thing. Um, with, with API is the moment you introduce an API. So you, you've, you've solved the risk problem by introducing the API. So you got the risk problem solved, but now you, you've done, you've added this new thing that has a life cycle, has multiple versions, and you're gonna have to live with it forever. So even as if one, if your business, if your business needs change, this API needs to change in an orderly fashion. And, and it needs to be, you know, treated like a product. And, you know, that has versions that has a business problem that it's solving, you know, that eventually might get deprecated if it's not solving the right business problem. And most classical product managers aren't able to really get their head wrapped around that. And there is direct revenue implications for it, depending on the types of integrations you're doing, um, an enterprise might be doing. A strategic integration, right? So there's a difference between a strategic integration and ecosystem, right? A strategic integration is I'm an enterprise corporation, and I'm strategically going to integrate in with one of my key suppliers, right? That actually requires a fair level of thought. That isn't a UX problem, but it will be around forever. And as your business evolves and as your suppliers business evolves, You need to keep iterating those systems and
