Welcome!

Microservices Expo Authors: Dalibor Siroky, Elizabeth White, Pat Romanski, Scott Davis, Stackify Blog

Related Topics: SDN Journal, Microservices Expo, Microsoft Cloud, Agile Computing, @DXWorldExpo, @DevOpsSummit

SDN Journal: Blog Feed Post

Creating High-Performance Teams: Get Rid of Judgment

Real teams are formed around a common purpose, not a common manager

The biggest difference between high-performance teams and more average teams is that the high-performance group actually acts like a team.

That statement is so obvious, I am going to let it stand on its own.

If you look at most groups, they tend to act less like teams and more like loose affiliations of individuals that are connected through a common manager. The manager is an orchestrator, maybe even a facilitator at times, but that doesn’t mean the group is really a team. Rather, they are individual contributors that are linked by a common task management protocol.

Too many people make the mistake of thinking that teams are natural byproducts of a reporting structure. We should be clear: a reporting structure is useful for defining lines of communication and determining who is responsible for the administrative tasks of people management (expense reports, PTO requests, reviews, and so on). But a reporting structure has nothing at all to do with forming a team. Think of reporting structure more as a necessary evil because of the HR systems that we use.

Real teams are formed around a common purpose, not a common manager. A group of people all committed to a single end goal is a team. Who they report to is irrelevant; it’s the objective or the mission that defines the team. This is why open source projects can be effective. Even when people report into entirely different corporate entities, they are capable of working together to deliver a common objective. That is teamwork.

But what separates the good teams from the bad teams?

The best teams work in concert to accomplish something. They work in concert. This is different from the way many “teams” operate (quotes used for emphasis). Think about how a typical team works. There is some team lead who works to break the objective down into a set of tasks. These tasks are then farmed out to the team members based on their skill set or interest or seniority or whatever. The hope is that by pushing the individual activities out, people can execute against their parts in parallel, effectively speeding up the project.

The subtle point here is that the first thing the leader does is break the objective down into parts so that the team can go off and act independently. This isn’t teamwork; this is a hub-and-spoke management model. In fact, for many teams, the only time they come together as an actual team is on weekly staff or project calls designed to solicit status from each of the isolated individuals.

How do you know this isn’t teamwork? How many of us has been on one of these status calls, bored to tears because 97% of the discussion is irrelevant to us? We hate listening to people give status because we don’t actually care that much about what they are doing. It doesn’t impact us, so we find the detail irrelevant at best and absolutely maddening at worse. When someone takes time to get into the details of what they are doing, we think they are either grandstanding or rat-holing. If you ever have felt these things, you know you are not part of a team.

Real teams work together. They are engaged not just in their tasks but also more broadly in the initiative as a whole. They talk. They brainstorm. They strategize. They celebrate each other’s success. They share in each other’s setbacks. The real measure of a team is how well they collaborate.

Collaboration hinges on the free exchange of ideas. And there is no greater killer of collaboration than judgment.

Whenever people work in a group setting, they are taking on risk. The challenge of teams is that your performance is public. It is difficult to hide when everything you do is out in the open. When you perform well, it is exhilarating because everyone sees it. But when you fall short, it is terrifying because everyone sees it. And if those failures carry with them too much judgment, the person will naturally pull back until they are an individual working alongside a team.

When you give critical feedback, it is important to be specific and honest. But it is equally important to withhold judgment. You want to comment on the performance without judging the individual. You want to talk about actions, but refrain from commenting on character. When someone falls short – even if it is more frequent than it ought to be – you want to talk about the performance and not the individual. Someone might not be prepared, but that does not necessarily indicate laziness or lack of dedication. An individual might offer up a poorly thought out idea, but that does not mean the person is inferior or incapable. Talk about the idea, not the person. By keeping the discussion about the performance, you can have a very candid conversation without assailing the individual.

This is important because when people feel attacked, they either fight back or fall back. In the case where they fight back, the ensuing discussion is emotional. Neither side will be able to land points. There is nothing productive about this kind of exchange. If the person falls back, you run the risk of them withdrawing over time to the point where they don’t offer up thoughts or effort at allt. If this happens, you revert from team to collection of individuals.

As a leader, people will key off of your response. How do you treat your team’s setbacks? Do you offer up feedback along with a healthy side serving of judgment? Or do you comment on the performance and leave the individual out of it?

The answer might not be as clear as you think. It is difficult to self-diagnose because we frequently carry judgment not in our words but in our tone or facial expressions. If you are thinking it, people will be reading it, regardless of whether the words ever actually come out of your mouth.

There are ways to see how you are doing. If you ask your team about the status of something that is late, do you get a 15-second response or a 2-minute response? If the person you are querying gives you a lengthy description of everything they have done over the past week, she is justifying the lateness. That justification is because she is afraid of being judged. If this is a typical response, you might not be fostering the kind of judgment-free environment that you think. If instead, she gives a short answer about the status (“I haven’t finished yet, but I expect to finish by tomorrow.”), you are creating a safe space to talk freely.

When people can talk openly without fear of being judged, they naturally become more generous in sharing their thoughts. This makes collaboration easier. And ultimately this transforms groups of individuals into teams.

[Today's fun fact: Owls are one of the only birds who can see the color blue. Yeah, I don't know what the other ones are either. Our PR firm only gave me half of the fact apparently.]

The post Creating high-performance teams: Get rid of judgment appeared first on Plexxi.

Read the original blog entry...

More Stories By Michael Bushong

The best marketing efforts leverage deep technology understanding with a highly-approachable means of communicating. Plexxi's Vice President of Marketing Michael Bushong has acquired these skills having spent 12 years at Juniper Networks where he led product management, product strategy and product marketing organizations for Juniper's flagship operating system, Junos. Michael spent the last several years at Juniper leading their SDN efforts across both service provider and enterprise markets. Prior to Juniper, Michael spent time at database supplier Sybase, and ASIC design tool companies Synopsis and Magma Design Automation. Michael's undergraduate work at the University of California Berkeley in advanced fluid mechanics and heat transfer lend new meaning to the marketing phrase "This isn't rocket science."

@MicroservicesExpo Stories
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
The cloud era has reached the stage where it is no longer a question of whether a company should migrate, but when. Enterprises have embraced the outsourcing of where their various applications are stored and who manages them, saving significant investment along the way. Plus, the cloud has become a defining competitive edge. Companies that fail to successfully adapt risk failure. The media, of course, continues to extol the virtues of the cloud, including how easy it is to get there. Migrating...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
It has never been a better time to be a developer! Thanks to cloud computing, deploying our applications is much easier than it used to be. How we deploy our apps continues to evolve thanks to cloud hosting, Platform-as-a-Service (PaaS), and now Function-as-a-Service. FaaS is the concept of serverless computing via serverless architectures. Software developers can leverage this to deploy an individual "function", action, or piece of business logic. They are expected to start within milliseconds...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
From manual human effort the world is slowly paving its way to a new space where most process are getting replaced with tools and systems to improve efficiency and bring down operational costs. Automation is the next big thing and low code platforms are fueling it in a significant way. The Automation era is here. We are in the fast pace of replacing manual human efforts with machines and processes. In the world of Information Technology too, we are linking disparate systems, softwares and tool...
DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
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...
"As we've gone out into the public cloud we've seen that over time we may have lost a few things - we've lost control, we've given up cost to a certain extent, and then security, flexibility," explained Steve Conner, VP of Sales at Cloudistics,in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, 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.
"Cloud4U builds software services that help people build DevOps platforms for cloud-based software and using our platform people can draw a picture of the system, network, software," explained Kihyeon Kim, CEO and Head of R&D at Cloud4U, 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.
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...