Every enterprise we worked in had the same problem: nobody truly knew what applications they had, what those applications did for the business, or what would break if one of them disappeared. We decided to fix that.
Enterprise architects need portfolio data they can inspect: applications, owners, costs, lifecycle, capabilities, and dependencies in one structured model.
Aniekan Okono spent years working inside large enterprises as an enterprise architect. The same frustrations showed up everywhere.
Teams making expensive decisions based on incomplete information. Architects maintaining spreadsheets that were out of date before they were finished. Leaders approving modernization programmes without knowing which applications would be affected.
The problem wasn't lack of intelligence. It was lack of visibility.
Organizations often had the data, but it was scattered across operational systems, spreadsheets, contract records, and institutional knowledge.
Iyene started with one question: what if enterprise architects and IT portfolio leaders could connect application records to capabilities and use a named framework to assess what should happen next?
The result is a maintained portfolio workspace, not a claim of automatic discovery.
