Build, protect and deploy apps across any platform and mobile device
Leverage a complete UI toolbox for web, mobile and desktop development
Automate UI, load and performance testing for web, desktop and mobile
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premise data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Automate decision processes with a no-code business rules engine
Mark Troester explains how CIOs need to move their thinking past APIs and onto a higher level—if they want to avoid their own deprecation.
Chief Information Officers have a lot to think about, and in this recent article on CIO.com, the author advocates that they need to plan for API deprecation. I’m going to have a little fun with this. Instead of “Why CIOs need to plan for API deprecation” it should be “Why CIOs that focus on their API strategy need to plan for their company's (hence their own personal) deprecation.”
Clearly, the technology aspects of the CIO are important, and the role depends on the size of the organization, and whether there is a CTO role within the organization, but my point is that the CIO needs to up-level their thought process to the business impact or business outcome level. While their API approach can be one element of a larger strategy, the first thing to consider is the impact of the API strategy as it relates to their business.
Their API strategy should be driven by business value. For example, what additional revenue can be gained by exposing their data, business services or digital insights as a service? How do they best monetize this strategy? What can they do with their API strategy to enter new markets or to drive more revenue through their existing business channels?
It could be that the business value is limited to cost, and they make the go forward decision based on cost, efficiency, etc., but cost should not be the only factor.
This thought process should not be limited to their API strategy. It should be the first consideration that guides every decision and every strategy, and be factored into their execution plan. A good way to approach this decision process is to embark on a larger digital transformation strategy—a digital strategy that is driven based on business value.
That will help them both determine what they should do and how they should prioritize their work. Should they focus on customer experience? Should they focus on operational efficiency? Likely it’s not one or the other, it’s what has the greatest impact on business outcome.
That is how the CIO will move from being an operational necessity to an executive imperative.
Mark Troester is the Vice President of Solutions Marketing, Digital Transformation at Progress. Mark has extensive experience in bringing application development and data integration products to market. Mark previously led product marketing efforts at Sonatype, SAS and Progress DataDirect. Before moving into marketing, Mark worked as a developer and developer manager for start-ups and enterprises alike.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.