Welcome!

Microservices Expo Authors: Elizabeth White, Liz McMillan, Pat Romanski, Yeshim Deniz, Zakia Bouachraoui

Related Topics: @DevOpsSummit, Microservices Expo, Linux Containers, Containers Expo Blog

@DevOpsSummit: Article

The DevOps Virus | @DevOpsSummit #Agile #DevOps #ContinuousDelivery

Selecting such teams throws a wrench in the entire works, limiting the value of self-organization

Whenever the conversation in a large organization circles around to how to be more innovative, someone always brings up a skunkworks.

According to Wikipedia, the original Skunk Works is Lockheed Martin's Advanced Development Programs (ADP), responsible for the design of several aircraft - an effort that continues to this day.

Over time, however, the term skunkworks has taken on a broader meaning. Innovation thought leader Everett Rogers (the fellow who coined the term early adopter) defined a skunkworks as "an especially enriched environment that is intended to help a small group of individuals design a new idea by escaping routine organizational procedures."

Rogers goes on to point out that "the research and development (R&D) workers in a skunkworks are usually specially selected, given special resources, and work on a crash basis to create an innovation."

For a large organization struggling with rigid hierarchies and the inflexible decision making that characterizes them, spinning off a skunkworks team seems to make sense. Set up a chic office space in a remote location, choose some particularly creative individuals, and tell them to go forth and innovate.

What could possibly go wrong?

If you've been following my research on self-organization, you might be able to discern the problem. When I talk about driving innovation with self-organizing teams, I emphasize that such self-organization includes expecting the participants to organize their own teams, give themselves their own goals, and determine for themselves how to measure their success.

In contrast, Rogers' definition of skunkworks points out that members of such teams are "usually specially selected." Good thing he added the word usually - because specially selecting such teams throws a wrench in the entire works, limiting the value of self-organization and thus the ability for the organization as a whole to become more agile.

The Skunkworks Catch
There are a number of reasons why assigning people to special teams responsible for driving innovation can be counterproductive - what I like to call the skunkworks catch.

First, the individuals in the team may find that their teammates are not their preferred choice for such an effort. Good managers will be familiar enough with the skill sets as well as the personal relationships and work preferences of the people they assign to a skunkworks team, but there's a measure of guesswork for even the best manager - and of course, many are far from being the best.

Perhaps the most significant problem with assigning people to a skunkworks team, however, is what such an assignment does to the morale of their colleagues left behind.

People generally regard getting selected for such a team as a privilege, with a variety of tangential perks as well as the core opportunity to work on something innovative. From the perspective of the other people in the organization, however, they're left with the grunt work - only now, even more grunt work as some of their colleagues had the good fortune to leave such drudgery behind.

Even if we set aside the adverse morale impact of a skunkworks team on the rest of the organization, there's always the real possibility that some of the people left off of the team are also particularly creative, and would thus have some real value to contribute toward developing innovations that move the needle for the business.

Reinventing the Skunkworks
The Agile Digital Transformation approach to building self-organizing teams, in contrast, is to expect individuals to form the teams themselves.

People should approach their work environment overall with a volunteer mindset, keeping their eyes open for better ways to provide value to the business.

If someone thinks they can come up with an innovation - either because they have an idea that might fly or simply because they would like to participate on a skunkworks team - they can chat with their colleagues across the organization and attempt to form such a team.

For organizations that have business agility as a strategic business driver, the role of management in this process is to communicate the strategic goals of the organization, provide the necessary resources, delineate the required constraints (for example, regulatory and security constraints), and then get out of the way.

Once the organization gets up to speed with self-organization, however, managers should no longer assign people to teams, assign tasks to teams, establish goals for teams, or decide on how teams' progress toward their goals should be measured. The people on those teams should take care of those tasks for themselves.

The self-organizing teams that result may decide to tackle various tasks depending upon the goals set out for the organization as a whole. Some such teams will focus on innovation, while others will decide to work on more tactical efforts.

Self-Organizing Beyond the Skunkworks

If you're used to thinking about large organizations in conventional ways - as most people are wont to do, unfortunately - then you're likely to see two problems with my suggestions regarding self-organized skunkworks teams: first, won't everybody jump at being on a skunkworks team, leaving routine work unfinished? And second, won't this whole process lead to a chaotic free-for-all, producing useless innovations that don't align with corporate goals or strategy?

The answer to these two problems is to learn the lesson of the DevOps Virus: self-organization should extend beyond the team level.

As we move to an organizational model consisting of a number of fluid, self-organizing teams, then self-organization will emerge at what we might call the ‘team of teams' level. In other words, if a skunkworks team is getting off-track, where its innovations appear to be misaligned to the goals of the organization, then other teams can decide amongst themselves to interact with the skunkworks team in question in order to bring the errant group back in line.

In other words, just because a team has decided to go the skunkworks route doesn't mean that lines of communication and influence that connect it to other teams are entirely severed. After all, people can still move into and out of teams as they and the teams decide, depending both on their personal preferences as well as the preferences of each team as a whole.

The goal is for all the teams taken together to have a naturally emerging self-correcting process that keeps everyone on track, even as business needs evolve and unexpected innovations change the playing field.

Just as individual teams can self-correct by deciding to eject a member, say, the entire organization can self-correct by influencing wayward teams to get with the program.

The Intellyx Take
By applying the principles of self-organization at both the team level and the team-of-teams level, we're essentially recommending an inclusive approach to skunkworks-based innovation rather than the traditional exclusive approach.

Whenever management imposes a separation on an organization where some people get a perceived benefit that others do not, morale issues quickly form and the end result is counterproductive. This is just as true for innovation as it is for Bimodal IT, where fast, digital teams get the perceived benefit over the poor souls relegated to slow, traditional IT.

In contrast, if the expectation is that people can choose their own teams and teams can choose their own goals, then the organization benefits in two fundamental ways: the morale issue goes away, and furthermore, the fast-moving, creative, innovative aspects of every individual in the organization can be brought to bear not just to drive business velocity and innovation, but to transform those parts of the organization that would otherwise velocity and innovation back.

The one missing piece of this Cortex which will have to wait till a future issue is the question of incentives (click here to subscribe to the Cortex newsletter). Given the freedom to choose their tasks, people will naturally gravitate toward the more interesting ones, and thus other important, but less fulfilling tasks risk getting neglected.

Instituting the appropriate incentives can help to balance this equation. However, traditional incentive strategies frequently go wrong. Agile organizations, therefore, must reinvent their incentive processes and policies as well. Stay tuned!

Intellyx 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: Greg Schechter.

More Stories By Jason Bloomberg

Jason Bloomberg is a leading IT industry analyst, Forbes contributor, keynote speaker, and globally recognized expert on multiple disruptive trends in enterprise technology and digital transformation. He is ranked #5 on Onalytica’s list of top Digital Transformation influencers for 2018 and #15 on Jax’s list of top DevOps influencers for 2017, the only person to appear on both lists.

As founder and president of Agile Digital Transformation analyst firm Intellyx, he advises, writes, and speaks on a diverse set of topics, including digital transformation, artificial intelligence, cloud computing, devops, big data/analytics, cybersecurity, blockchain/bitcoin/cryptocurrency, no-code/low-code platforms and tools, organizational transformation, internet of things, enterprise architecture, SD-WAN/SDX, mainframes, hybrid IT, and legacy transformation, among other topics.

Mr. Bloomberg’s articles in Forbes are often viewed by more than 100,000 readers. During his career, he has published over 1,200 articles (over 200 for Forbes alone), spoken at over 400 conferences and webinars, and he has been quoted in the press and blogosphere over 2,000 times.

Mr. Bloomberg is the author or coauthor of four books: The Agile Architecture Revolution (Wiley, 2013), Service Orient or Be Doomed! How Service Orientation Will Change Your Business (Wiley, 2006), XML and Web Services Unleashed (SAMS Publishing, 2002), and Web Page Scripting Techniques (Hayden Books, 1996). His next book, Agile Digital Transformation, is due within the next year.

At SOA-focused industry analyst firm ZapThink from 2001 to 2013, Mr. Bloomberg created and delivered the Licensed ZapThink Architect (LZA) Service-Oriented Architecture (SOA) course and associated credential, certifying over 1,700 professionals worldwide. He is one of the original Managing Partners of ZapThink LLC, which was acquired by Dovel Technologies in 2011.

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), and several software and web development positions.

Microservices Articles
Using new techniques of information modeling, indexing, and processing, new cloud-based systems can support cloud-based workloads previously not possible for high-throughput insurance, banking, and case-based applications. In his session at 18th Cloud Expo, John Newton, CTO, Founder and Chairman of Alfresco, described how to scale cloud-based content management repositories to store, manage, and retrieve billions of documents and related information with fast and linear scalability. He addresse...
Adding public cloud resources to an existing application can be a daunting process. The tools that you currently use to manage the software and hardware outside the cloud aren’t always the best tools to efficiently grow into the cloud. All of the major configuration management tools have cloud orchestration plugins that can be leveraged, but there are also cloud-native tools that can dramatically improve the efficiency of managing your application lifecycle. In his session at 18th Cloud Expo, ...
The now mainstream platform changes stemming from the first Internet boom brought many changes but didn’t really change the basic relationship between servers and the applications running on them. In fact, that was sort of the point. In his session at 18th Cloud Expo, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss how today’s workloads require a new model and a new platform for development and execution. The platform must handle a wide range of rec...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
SYS-CON Events announced today that DatacenterDynamics has been named “Media Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY. DatacenterDynamics is a brand of DCD Group, a global B2B media and publishing company that develops products to help senior professionals in the world's most ICT dependent organizations make risk-based infrastructure and capacity decisions.
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true ...
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
DevOpsSummit New York 2018, colocated with CloudEXPO | DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term.
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.