Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Blog Feed Post

Reinventing IT in Times of Digital Disruption

First came Data Processing (DP), as massive, arcane behemoths of computers crunched numbers for select enterprises and government agencies. DP evolved into Information Systems (IS) and in turn, Management Information Systems (MIS). Next up: Information Technology (IT) and its cousin, Information and Communications Technology (ICT).

Data processing back in the day.

Data processing back in the day.

As the corporate department responsible for enterprise technology evolved, so too did the title of the executive in charge, eventually settling on the Chief Information Officer (CIO) – in spite of the fact that CIOs are rarely if ever in charge of an organization’s information per se.

Throughout these changes, the role of the organization we now label IT has evolved, and with it, the focus of the CIO. Today, with digital transformation upending the status quo across the entire enterprise, IT is transforming once again.

Given its history, then, will the IT organization become as digital transformation works its magic? And correspondingly, what is the new role for the CIO – assuming we’ll even need a CIO in the digitally transformed future?

The First Three Roles for IT

To make sense of the role the digitally transformed IT organization must play, it’s essential to review the roles that IT has served over its history – not only to understand the past as prologue, but also because each of these roles remains part of the story.

In other words, each role layers on top of the previous ones, adding complexity to an already complex organization. These layers of complexity, of course, are high on our priority list of things we’d love to transform.

The first role for IT – the most universal of all the roles – is IT as cost center.

Of everything an enterprise does, the traditional reasoning goes, some things bring in the bucks and some don’t. IT is firmly in the second camp, consisting entirely of overhead.

As a result, the CIO’s primary role is cost containment. Do more with less is the mantra – and when times are tight, it becomes do less with less. Little if any of the IT budget is earmarked for innovation.

Layered on top of the cost center role is role #2: IT as service provider. True, IT costs are still overhead, but the CIO’s focus shifts from managing costs to serving the business.

Interactions between IT and the rest of the business become service interactions – often leveraging a ticket-based service management system where people ask IT for services and then wait in line to get them.

For the CIO, the service provider role has clear advantages over the cost containment role, as the value IT provides to the business is now quantifiable. As long as the IT organization can innovate in order to provide better service, the reasoning goes, then the CIO is likely to be able to justify the additional expense.

However, CIOs still struggle with the service provider role, because it is entirely tactical. To warrant the ‘C’ in the CIOs title – C as in C-level – the CIO must have a strategic role in the business.

That’s where the third role for IT comes in: IT as partner with the business. The C-suite finally recognizes that IT is strategically important to the enterprise, and as a result, invites the CIO to join in as a full-fledged member.

Sounds good, right? CIOs who have truly reached the lofty heights of the strategic C-suite may finally feel they have reached the pinnacle of their careers as CIO.

But – and this is a big but to be sure – partnering with the business is no longer good enough. In fact, it’s a dot-com era holdover, from when organizations first came to realize that the Internet and the Web in particular were strategic assets.

True, the Internet opened the C-suite door for many CIOs, and today, the enterprises that survived the dot-com boom and bust are the ones that got the Internet right. Kudos to them.

But digital transformation represents the next generation of change. Partnering with the business won’t cut it anymore.

The Multifaceted Nature of Digital Transformation

Compared to digital transformation, the Internet revolution was decidedly one-dimensional: either you got the Web or you didn’t.

In contrast, the IT-related transformations enterprises are facing today are numerous, complex, and intertwined. Four component transformations in particular are worth calling out.

We have the move to the cloud, transforming how enterprises deploy, pay for, and manage their IT assets.

We have the rise of mobile technologies, changing how customers (and everyone else) interacts with businesses, and as a result, transforming what customers expect from the companies they interact with.

Add to this mix: Software-Defined Everything (SDX). Combining the last decade’s principles of Model-Driven Architecture with the technical advances in Software-Defined Networking, we’re increasingly able to represent our technology infrastructure as software models. Deploy or redeploy any aspect of our technology, from our network to our applications, with a push of a button.

The Fourth Role for IT

Perhaps most important for understanding the new role for IT, however, is the advent of DevOps. By leveraging the power of Software-Defined Infrastructure, developers, ops personnel, and testers have hammered out entirely new ways of building and deploying software.

And now, the DevOps virus is spreading, infecting the entire enterprise with new ways of organizing itself along horizontal, self-organizational lines.

If we extend these trends into the future, it becomes clear that the entire idea of an IT department as a separate organizational silo within a hierarchically-organized enterprise is becoming obsolete – because hierarchical organizational models themselves do not support the business agility enterprises need to remain competitive in the face of the multifaceted disruption that characterizes today’s software-driven business environment.

As a result, digital transformation represents a rethink of enterprise organization from hierarchical and top-down to horizontal and self-organized. DevOps represents early steps to this vision, and SDX is what will make the change practical and cost-effective.

The fourth role for IT, therefore, is for IT to become the business. Every part of the organization, regardless of the nature of the business, becomes software-empowered. Business operations (the role of the COO) and technical operations (the ops part of today’s CIO role) become one and the same.

We must still manage technology costs, serve users, and partner with lines of business – but none of these roles alone or taken together tell the story of how fundamentally and comprehensively digital transformation impacts the IT organization and its leadership.

The Intellyx Take

Even though our vision of IT becoming the business is unquestionably bold, don’t fall for the straw-man trap of concluding that the digitally transformed enterprise doesn’t need an IT effort at all. That fallacious conclusion aligns more with the early, cost center role for IT, reducing costs to zero by extinguishing the department altogether. Clearly, reaching that conclusion is entirely disingenuous.

The reality is subtler and more profound. This transformation, in fact, shakes the C-suite to its core, as the point of the C-suite today is to be the top of the hierarchical pyramid that represents how every large organization structures itself. Do away with the hierarchy, and corporate leadership must transform accordingly – and with it, the role of the CIO.

What will such a digitally transformed enterprise look like? We don’t really know, as we only have glimpses as organizations progress along their digital transformation roadmaps.

Remember, however, digital transformation has no end state. For change to become a core competency, today’s enterprises will always be in flux – and the ones that embrace that disruption will be the only survivors.

Copyright © Intellyx LLC. Intellyx publishes the Agile Digital Transformation Roadmap poster, advises companies on their digital transformation initiatives, and helps vendors communicate their agility stories. As of the time of writing, none of the organizations mentioned in this article are Intellyx customers. Image credit: Energy.gov.

Read the original blog entry...

More Stories By Jason Bloomberg

Jason Bloomberg is the leading expert on architecting agility for the enterprise. As president of Intellyx, Mr. Bloomberg brings his years of thought leadership in the areas of Cloud Computing, Enterprise Architecture, and Service-Oriented Architecture to a global clientele of business executives, architects, software vendors, and Cloud service providers looking to achieve technology-enabled business agility across their organizations and for their customers. His latest book, The Agile Architecture Revolution (John Wiley & Sons, 2013), sets the stage for Mr. Bloomberg’s groundbreaking Agile Architecture vision.

Mr. Bloomberg is perhaps best known for his twelve years at ZapThink, where he created and delivered the Licensed ZapThink Architect (LZA) SOA course and associated credential, certifying over 1,700 professionals worldwide. He is one of the original Managing Partners of ZapThink LLC, the leading SOA advisory and analysis firm, which was acquired by Dovel Technologies in 2011. He now runs the successor to the LZA program, the Bloomberg Agile Architecture Course, around the world.

Mr. Bloomberg is a frequent conference speaker and prolific writer. He has published over 500 articles, spoken at over 300 conferences, Webinars, and other events, and has been quoted in the press over 1,400 times as the leading expert on agile approaches to architecture in the enterprise.

Mr. Bloomberg’s previous book, Service Orient or Be Doomed! How Service Orientation Will Change Your Business (John Wiley & Sons, 2006, coauthored with Ron Schmelzer), is recognized as the leading business book on Service Orientation. He also co-authored the books XML and Web Services Unleashed (SAMS Publishing, 2002), and Web Page Scripting Techniques (Hayden Books, 1996).

Prior to ZapThink, Mr. Bloomberg built a diverse background in eBusiness technology management and industry analysis, including serving as a senior analyst in IDC’s eBusiness Advisory group, as well as holding eBusiness management positions at USWeb/CKS (later marchFIRST) and WaveBend Solutions (now Hitachi Consulting).

@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.