Tyk referenced my API Hierarchy of Needs, which I created ~12 years ago, to explain how API Governance affects what developers can or can’t do. It’s interesting to see how a concept never gets old and how you can reuse it to introduce new ideas.

Found at “How to implement API governance without stifling developer creativity and agility” on 2025-03-24 16:30:58 +01:00.

Clearly, governance can help drive improvements in reliability, functionality, and usability. However, does it become a constraint as we head towards the top of the pyramid, holding back creativity?