Welcome!

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

Related Topics: @CloudExpo, Microservices Expo, @DevOpsSummit

@CloudExpo: Blog Post

The End of Business Process in the Digital Era | @CloudExpo #Cloud #DigitalTransformation

The companies that will profit the most in the Digital Era are the ones that don’t put profit at the center of their efforts

At Intellyx, we often talk about the transition from the Industrial Era to the Digital Era, but other than the transformation of the technology itself, the details have been rather sketchy. It's time to fill in some of the blanks.

This transition has been going on for decades, of course. Another name for the Digital Era is the Information Age, which started at the end of World War II. Yet, while computers and the Internet have fundamentally changed business in several complex and multifaceted ways, we still run our organizations following the familiar patterns of the Industrial Era.

With the modern notion of digital transformation, however, enterprises are chipping away at the fundamental organizational and operational structures that have been with us since the nineteenth century or earlier.

One remarkable casualty: the business process. Business processes have become so ingrained in how we envision large organizations operating and the roles people play within them that relegating them to the scrap heap is almost unimaginable, and unquestionably transformative.

In the Digital Era, however, everything you thought you knew about business processes, and thus how human effort drives productivity and profit in the organizations we work for, is wrong.

The Rise of Business Process
The most significant impact of the Industrial Revolution was how it transformed how people worked. Handwork gave way to the operation of machines - first in factories, but over the years, machine operation came to pervade services industries as well, from banking to transportation to government.

In the early twentieth century, Frederick Winslow Taylor's Principles of Scientific Management followed, crystallizing the distinct roles of workers and management within this industrial context, focusing in particular on how to improve the means of production by making workers more efficient.

This thinking led to the invention of the business process. Using machinery operation as the template, Scientific Management extended processes across the enterprise.

In the Industrial Era, therefore, human work consisted of such process instances strung together, like cogs in a wheel, unceasingly cranking out profits for their companies.

Playing Hopscotch
Today, we have a reasonably solid idea of what we mean by a business process. They consist of a sequence of steps representing tasks or actions, with a clear beginning and an end, which represents a business goal.

Such process frequently have branches and error conditions, suggesting a flowchart as the best way to visually represent them.

As part of their day-to-day work, then, people must execute such processes as though each flowchart were a large hopscotch game, where everybody's job is to hop from one square to another.

As business process management (BPM) software came on the scene, such software represented each such traversal as a process instance.

After all, many people might be executing a particular process at the same time, each of them potentially at a different step.

Taking a Digital Journey
Every business process must have a business purpose - an organizational goal that lines up with the profit driver of every private sector company (or mission priority within the public sector).

This profit-centric alignment, however, is an Industrial Era holdover. In the Digital Era, organizations must be people-centric.

We no longer want to treat people as cogs in a wheel. We must free ourselves from our business process thinking. Instead, we start with the individual - and thus instead of processes, we must focus on journeys.

You may already be familiar with customer journeys: the representation of the sequence of interactions a person has with a company or brand. Customer journeys consist of a sequence of ‘moments,' recognizing that when people use a device to interact with an organization, they do so when and where they choose - not when or where the company chooses.

In the Digital Era, we extend the notion of customer journeys to everyone - employees, partners, suppliers, anyone involved in an organization. Instead of the ‘customer journey' terminology, therefore, let's generalize the notion to the ‘digital journey.'

Defining the Digital Journey
Such digital journeys are different from business processes in several fundamental ways. The person usually decides on the order of steps, or moments, rather than the organization laying them out beforehand.

Digital journeys also frequently have no clear end, and many not have a clear beginning, either.

Most importantly, each journey is unique to the individual. Businesses can group them together in many ways for various purposes, but the groupings don't define the journeys the way that business processes define their instances.

Since every journey is unique and each individual decides their own moments, a flowchart metaphor is a poor fit for a digital journey. Instead, characterize digital journeys as depending on constraints and dependencies.

A constraint is a limitation on the behavior within a journey that applies across the journey - but only takes effect when the conditions for the constraint are met.

A dependency is when one task or activity must take place before another can occur.

Here's an example: let's say your journey is through an airport (yes, digital journeys can be literal journeys!).

When you walk in, you might check in at a kiosk, get in line, or perhaps go to a store - it's up to you. But you must still conform to certain constraints, for example, you must have a boarding pass to go through security, and you must pass through security to go to a gate.

There are dependencies as well: getting a boarding pass depends upon having a valid ticket, for example.

As long as people conform to the constraints and dependencies, then, they are welcome to do whatever they want in whatever order they choose.

Constraints and dependencies, of course, are nothing new. In particular, Eliyahu M. Goldratt fleshed out the Theory of Constraints in the mid-1980s.

However, Goldratt placed his theory into the context of business processes - and to be sure, processes are subject to constraints and dependencies as well.

In the Digital Era, in contrast, we must free the considerations of constraints and dependencies from the business process context, instead applying them to the unique priorities and behavior of each individual.

Our airport example makes this difference clear. In the Industrial Era, people had to check in at the airline ticket counter to get a boarding pass - steps in a business process.

In the Digital Era, however, people have many ways to obtain boarding passes at different times, both at home or in the airport. This flexibility is human-centric rather than process-centric, illustrating the need to focus on the digital journey instead of the process.

Digital Journey Management vs. Business Process Management
In the 1980s, of course, technology wasn't up to the task of managing such digital journeys. Now it is.

Digital journeys are clearly different enough from business processes that yesterday's BPM software is no longer adequate. We can, however, manage digital journeys in other ways, either individually or in groups.

For example, managing the journeys of everyone with a boarding pass would be relatively straightforward, even though in today's digital world, people can use their smartphones, print the passes at home, or use a kiosk.

Digital retailers already manage customer journeys by demographic segment - an approach that we as consumers often find too limiting. Just because I'm in my fifties doesn't mean I want AARP ads in my stream, after all.

Ideally, of course, companies would manage ‘segments of one' - what we at Intellyx call individualization. In fact, you can think of individualization as fundamental to the notion of a digital journey, and by extension, to the Digital Age in general.

Best of all, we now have the technology to support this goal - if only enterprises would get their digital transformation act together.

No more bulk ‘do not reply' emails. No more tone-deaf retargeting. No more ‘press 1 to wait on hold.'

The technology part of this story has become the easy part - but organizations won't successfully enter the Digital Era until they move away from business processes.

The Intellyx Take
Will all business processes - and BPM software - be obsolete in the Digital Era? The answer: it's not quite so black and white. Just as industrialization didn't entirely displace handwork, digital journeys aren't going to fully replace business processes.

What is already happening, however, is a shift in expectation to a ‘digital journey first' mentality. Digitally transformed companies realize that to put customers and employees first, they must treat them as individuals who wish to interact on their own terms.

Perhaps the most difficult aspect of this transition from the Industrial Era to the Digital Era is the shift from profit-centricity to human-centricity. After all, isn't making money the true goal of any for-profit company?

The answer: in the Digital Era, the only way to achieve the profit goals of the enterprise is to successfully move to a human-centric model. Focusing on profits over people is counterproductive, uncompetitive, and in the long run, fatal.

The companies that will profit the most in the Digital Era are paradoxically the ones that don't put profit at the center of their efforts.

Be warned: the technology connotation of ‘digital' is nothing but a smokescreen. Digital journeys - and the Digital Era writ large - are about people. Get this right and profits will follow.

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: Ruth Hartnup.

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...
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...
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 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
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.
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...
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.