The Everest Group goes on to identify “old school” operation models as root cause: doing things the way they’ve always been done, even when trying to “transform.” Unfortunately, that includes the reactionary method of solving operational issues. The quick fix.
With the rapidly accelerating move to digitization of all things business, the need for immediate remedies can sometime outpace the ability to wisely manage. Trying to do too much too fast often results in a tangled mess of bespoke applications, legacy technologies and point-to-point integrations created by shadow projects with little oversight or control.
Reinvigorate efforts with unified platform approach for everything. Yes everything.
Rather than using the “old school” approach of cobbling together point solutions, progressive Enterprise Architects are once again considering unified tactics for rationalizing application and data sources, controlling and standardizing across functional silos, and ending frivolous or unproductive investment choices. But what should EAs consider in a platform solution to ensure it is worthwhile? At the minimum, the solution should have power and functionality to:
- Reduce the risk of data redundancy and inaccuracy. Ad hoc implementation of applications increases the risk of overlapping functionality and duplicate data production. That makes it harder and harder to trust that business decisions are being made with the latest and greatest info.
- Replace shadow IT with delegated development. Empower departments to create no-code/low-code apps with predefined functional libraries. A transformative solution should allow freedom to self-solve, but under a watchful eye and full IT approval.
- Empower traditional developers. The platform should have the “oomph” and pro tools needed for complex, professional developers.
- Replace legacy collaboration systems. Get rid of outdated, on-premise collaboration tools that are yet another source for ad hoc data pools. Replace for flexible, cloud-friendly alternatives.
- Enable holistic reasoning across functions and departments. Empower EAs to consider application development which can solve similar issues across multiple departments.