Welcome!

Microservices Expo Authors: Elizabeth White, Stackify Blog, Pat Romanski, Gopala Krishna Behara, Sridhar Chalasani

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
We all know that end users experience the Internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices – not doing so will be a path to eventual b...
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
"DivvyCloud as a company set out to help customers automate solutions to the most common cloud problems," noted Jeremy Snyder, VP of Business Development at DivvyCloud, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
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...
Your homes and cars can be automated and self-serviced. Why can't your storage? From simply asking questions to analyze and troubleshoot your infrastructure, to provisioning storage with snapshots, recovery and replication, your wildest sci-fi dream has come true. In his session at @DevOpsSummit at 20th Cloud Expo, Dan Florea, Director of Product Management at Tintri, provided a ChatOps demo where you can talk to your storage and manage it from anywhere, through Slack and similar services with...
Don’t go chasing waterfall … development, that is. According to a recent post by Madison Moore on Medium featuring insights from several software delivery industry leaders, waterfall is – while still popular – not the best way to win in the marketplace. With methodologies like Agile, DevOps and Continuous Delivery becoming ever more prominent over the past 15 years or so, waterfall is old news. Or, is it? Moore cites a recent study by Gartner: “According to Gartner’s IT Key Metrics Data report, ...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., 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.
In his session at Cloud Expo, Alan Winters, U.S. Head of Business Development at MobiDev, presented a success story of an entrepreneur who has both suffered through and benefited from offshore development across multiple businesses: The smart choice, or how to select the right offshore development partner Warning signs, or how to minimize chances of making the wrong choice Collaboration, or how to establish the most effective work processes Budget control, or how to maximize project result...
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...
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that e...
Without a clear strategy for cost control and an architecture designed with cloud services in mind, costs and operational performance can quickly get out of control. To avoid multiple architectural redesigns requires extensive thought and planning. Boundary (now part of BMC) launched a new public-facing multi-tenant high resolution monitoring service on Amazon AWS two years ago, facing challenges and learning best practices in the early days of the new service.
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
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...
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
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...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
"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.
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
What's the role of an IT self-service portal when you get to continuous delivery and Infrastructure as Code? This general session showed how to create the continuous delivery culture and eight accelerators for leading the change. Don Demcsak is a DevOps and Cloud Native Modernization Principal for Dell EMC based out of New Jersey. He is a former, long time, Microsoft Most Valuable Professional, specializing in building and architecting Application Delivery Pipelines for hybrid legacy, and cloud ...