Is the portal made to manage the complexity of consumably exposing a large API portfolio?
An excellent unified or federated enterprise developer portal makes it possible to organise a large portfolio of APIs and other digital capabilities into an experience that remains understandable and navigable. Whether that experience is achieved through stronger central coordination or through federation across business domains is secondary to the outcome.
Once a company decides to fully manage and document their APIs, put emphasis on an API-first strategy, and streamline digital governance, they start looking for a developer portal that can support a unified developer experience. They might need to share certain documentation only with partners or customers, and styling needs to always be on-brand.
In this category, we are only looking for portals that were created to serve as a federated platform for the API portfolio of large and complex corporations (due to organic growth, mergers and acquisitions, or any number of other reasons). Portals that expose the corporation's extensive integration affordances in a unified way that makes it easier for users to form a mental model through one comprehensive system.
The awards intentionally avoid prescribing a single architectural answer because the right operating model depends on the composition of the portfolio and the experience it is trying to create. A unified portal often has an easier path to coherence because more decisions are made centrally. A federated portal has a harder job because coherence has to emerge across independently managed domains, technologies, and products.
The jury will evaluate coherence, not uniformity. A federated portal will not lose points because different domains legitimately have different interaction patterns or visual identities. It will lose scoring points if users lose their bearings. Likewise, a unified portal will not automatically score higher simply because everything looks the same. Uniformity without clarity is not a better experience.
Award Criteria
When reviewing nominations, the jury will ask:
- Is the portal made to expose a complicated, large API portfolio? Is this portfolio the result of combined enterprise units and alliances?
- Does the portal serve the user with some form of a domain model?
- Does the portal have a structure that clearly represents the vision on how the offerings are documented and why they are as such?
- Is there a smooth, unified user experience for the many integration interfaces? Is the customer journey cohesive with your brand, your offerings, and the desired outcome?
- How do you streamline integrations between various offerings?
- Is the portal supported by higher management? Is there long term maintenance and support ensured? How do you keep the portal sustainable?
- Is there any user feedback mechanism to inform new product development?
Nominate now!
Think your portal belongs here? Nominate your portal and show how you're tackling enterprise complexity with clarity, structure, and vision.
