Welcome!

Linux Containers Authors: Jignesh Solanki, Yeshim Deniz, Karthick Viswanathan, Pat Romanski, Mehdi Daoudi

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

@DevOpsSummit: Blog Post

The DevOps Equation: Agility + Empathy = Quality | @DevOpsSummit #DevOps

Derek Weeks interviews Jeff Sussna on the importance of designing for service and responding to the unexpected

I had the chance to catch up with Jeff Sussna ahead of his keynote address on continuous design, scheduled for DevOpsDays Atlanta, April 26-27. Jeff discussed the importance of designing for service, responding to the unexpected, and the importance of building empathy across teams.

Derek Weeks: Today, I'm really happy that we have Jeff Sussna joining us for the latest in this series. Jeff, why don't you introduce yourself?

Jeff Sussna: Sure. Thanks for having me. I'm an independent consultant. I've been around since rocks were young or the 80s, whichever is older. My particular background is that I have built systems and led organizations across the entire development, QA and operations spectrum. So, I'm a little unique in that respect.

My current focus is on helping IT organizations and digital businesses really bring together their ops and design thinking so they can not only go faster and not only be more resilient, but also provide more customer value at the same time.

DW: Let's talk about that a little. How is continuous design - a subject you have written a lot about - coming into play? How can it help us be more resilient?

JS: Just to explain a little about what we mean by continuous design. It's basically bringing together the entire organization and a unifying design in operations. It's taking what we are doing in DevOps and expanding it to include product, design and support. It lets the whole organization really have an agile conversation with a market and with its customers.

The issue that we face is that we live in a service world now. The point is no longer delivering products like cars coming off an assembly line. It's much more about responding to our customers and having relationships with them. This is happening in a world that is more and more complex, while less and less is in your control. We can't figure everything out in advance. We have to have the ability to respond to the unexpected. We have to be able to do that at every level.

____

"This is happening in a world that is more and more complex, while less and less is in your control."

____

I will give you a couple examples of things that are perfect illustrations of this:

I recently wished a friend of mine happy birthday. The reason I did that was because there was a notice on my calendar that said it was her birthday. It was wrong. It wasn't her birthday. I had no idea where that notice came from. Did it come from Skype? Did it come from LinkedIn? Did it come from email? I had no idea.

We face that in IT too. Systems are becoming more complex. We develop microservices. We use public and private clouds at multiple levels. We're no longer in a situation where we can control things. We have to be able to respond and respond at all levels.

____

When we make design and operations unified and continuous, we are able to say, "Where did we think we were going? Where would we need to go? And, what do we do next?"

____

What I talk about in my book, in my workshops and in all my work is that this needs to happen at every level. It's not just a matter of designing for failure inside the data center or inside the infrastructure. We also have to do it at other levels.

Here is another example:

I was trying to get paid recently by a large enterprise client in Europe. They were trying to wire money internationally; my bank wasn't really set up for it, and they were having problems. They just kind of gave up. I kept getting these messages saying, "Sorry, we tried paying you and it didn't work." That was the end of it.

I started to get frustrated, and my client within the enterprise started to get frustrated to the point where they sent a scathing email to our AP department (which they cc'd me on) saying, "Why can't we take the lead to get this guy paid?"

That's an approach that is based on resilience in the sense of assuming that something can go wrong and figuring out what he can do to fix it when it can go wrong. As opposed to the traditional approach where we've been trained to push certain buttons and take certain actions. If those actions don't work the way they are supposed to, well, I guess that is someone else's problem.

https://www.youtube.com/watch?v=ISSMHmwIMtA

DW: This brings to light some recent conversations I had with Paula Thrasher at CSRA. She was talking about developing systems and how to make them more resilient. She is using pictures as part of her conversations with people to help visualize their work. What work steps are there? What work is flowing? What is communicating with what?

Are you taking similar approaches with continuous design in how you work with clients to pursue it?

JS: Well, I try to introduce them to the principles, and I also try to introduce them to a set of practices which actually comes out of Mark Burgess' work on promise theory. It is really a conceptual model for how we think about success and failure and how we think about service. For example, Amazon helps you get everything you need in your life from shaving cream to batteries to snow tires to books as quickly and easily as possible. In order to keep that promise, they make a whole variety of other promises. Some of which filter all the way down to a promise to be able to go over change to production as quickly as possible.

Once you take that mindset, the interesting thing about a promise and the reason we use that word is because it is very intuitive. We all know what a promise is. We all make promises to each other every day. On the other hand, when we think about it in terms of service, IT or whatever, it may seem a little odd. The thing about promises is that, on the one hand, we are making commitments to do things, and on the other hand, promises sometimes get broken. That is actually good because it forces us to think. If I promised to pay my vendor, what do I do if I'm not succeeding in paying my vendor?

____

"The thing about promises is that, on the one hand, we are making commitments to do things, and on the other hand, promises sometimes get broken. That is actually good because it forces us to think."

____

It's sort of flipping our mind. Again, we are doing this in the DevOps world where you start thinking about things like mean time to repair (MTTR) instead of mean time between failure (MTBF). We shift from how do we create a situation to how do we create a situation in which nothing will ever break - which becomes less and less possible. We then need to shift to a situation where we can respond more and more quickly.

We go to executives and say we don't want to worry about how often stuff breaks anymore, and they freak out. We have to teach them and we have to teach ourselves that we can't prevent things from breaking. Instead, let's be able to fix them so quickly that maybe no one notices. My focus is on really helping people shift their mindset from thinking about ourselves to thinking about who we are helping. And from thinking about what we are doing to thinking about how well it succeeds and how well it overcomes problems.

____

"We have to teach them and we have to teach ourselves that we can't prevent things from breaking. Instead, let's be able to fix them so quickly that maybe no one notices."

____

DW: You talked about delivering on promises as quickly as possible. How does continuous design account for doing things as quickly as possible but making sure the quality is there at the same time?

JS: In two ways: One way is that when you do things in small increments, you are able to find problems more quickly. This is classic; it comes out of Lean. It comes out of integration. It's pretty basic stuff for our community now that it's much easier to find and fix a bug five minutes after you change a code than five weeks after you change the code.

When you put things like Linux, Agile, DevOps and design all together, they all focus on incremental feedback loops where you very quickly discover the gap between what you think you're accomplishing and what you're actually accomplishing. Secondly, when you take this all to the way to the marketplace and you make it part of the relationship with your customer, you can reduce a tremendous amount of waste.

The way to think about continuous design is: It's all about steering. Think about a boat that you're trying to sail across a bay. You can't just point the boat at the other side and say go because the winds are changing, and you're going to have to respond to things that you can't predict. If you sail for 20 minutes then discover you had pointed in the wrong direction, you're going to be way off course. You're then going to generate a tremendous amount of energy getting back on course.

What continuous design says is just an extension of continuous integration and continuous delivery taken all the way though the business. When we steer continuously, we steer efficiently.

____

"What continuous design says is just an extension of continuous integration and continuous delivery taken all the way though the business. When we steer continuously, we steer efficiently."

____

DW: I know you're going to be keynoting DevOpsDays Atlanta coming up in April. Chris Corriere, one of the guys on the organizing committee, tells me that you're leading a full-day workshop on continuous design before that. Maybe you could tell some of the people that are attending DevOpsDays Atlanta why they should be there a day earlier for your workshop and what things you're going to address during that time.

JS: To some degree, what I am going to address is everything we have been talking about for the last ten minutes or so - relative to DevOps. I think the key thing is - and we need to think about it - we need to think about more than just going fast. One of the big misunderstandings that I see with DevOps is this notion that it is primarily about delivering application changes to production faster. That's only half of it. We really need to think about it from the perspective of providing service.

____

"One of the big misunderstandings that I see with DevOps is this notion that it is primarily about delivering application changes to production faster. That's only half of it. We really need to think about it from the perspective of providing service."

____

You know what we are talking about is essentially developers and operations people providing better service to each other. As a result, they can deliver better service to the business.

Where we talk about microservices, you know that word service is in there for a reason. If all you do is you kind of shatter your organization and shatter your architecture into a bunch of little pieces, you still have to figure out how those pieces come back together into something coherent. The answer to that is taking a really deep service-oriented approach. That is very much what my workshop is about. What does that word even mean, and how do we do it?

DW: You mentioned thinking about interactions as delivering better service to one another within the organization. How does empathy come into your thinking around DevOps and continuous design?

JS: I'd like to say agility plus empathy equals quality. What I mean by that, in particularly empathy, I think it's important to take a minute and clarify. When we talk about empathy, we are not talking about wallowing in someone else's pain. We're not even necessarily talking about things on an emotion or feeling level. It's very simply the ability to see things as if from another's perspective. I will give you a prime example of where that comes into play and how it's important and how it helps.

____

Agility + Empathy = Quality

____

When I work with clients, I tend to look at their process using their organization from the product beginning to the support end. Oftentimes, I see support getting the short end of the stick. I see places where they get phone calls from customers with features that they don't even know exist yet. They sometimes get talked down to by development or product or even operations. They say things like, "Well, you're just supposed to support the stuff. You're the young people. You're the less experienced people."

When we have the ability to see things from their perspective, we can think about how support is actually experiencing our delivery process. If we don't think about them when we go through the process of delivering new features, they will be lost. Them being lost will show when customers call for help. That will significantly affect customer satisfaction and then even beyond.

The reason we need to empathize with support is so we can empathize with the customer. Oftentimes, when we build something, we don't think about the notion that our customers might have trouble with it. On the one hand, we have the illusion that if we design it and we build it really well, they won't have trouble. We can't perfectly predict who they are, what they need or what they will encounter. There's an inevitability to the idea that they are going to need some amount of help.

DW: I think that is probably the best description of empathy within a DevOps environment that I have heard anyone talk about. Jeff, it has been a great conversation. Thank you very much. I really appreciate it, and we look forward to seeing you at DevOpsDays Atlanta coming up.

JS: Thanks. It has been great talking to you, and I am really looking forward to the conference. It will be fun.

If you want to learn more about continuous design from Jeff, be sure to join us at DevOpsDays Atlanta. I will also be at the event giving an Ignite Talk entitled "Real Heroes Draw Pictures" focusing on lessons learned from the 31 DevOps and Continuous Delivery Reference Architectures assembled.

More Stories By Derek Weeks

In 2015, Derek Weeks led the largest and most comprehensive analysis of software supply chain practices to date across 160,000 development organizations. He is a huge advocate of applying proven supply chain management principles into DevOps practices to improve efficiencies, reduce costs, and sustain long-lasting competitive advantages.

As a 20+ year veteran of the software industry, he has advised leading businesses on IT performance improvement practices covering continuous delivery, business process management, systems and network operations, service management, capacity planning and storage management. As the VP and DevOps Advocate for Sonatype, he is passionate about changing the way people think about software supply chains and improving public safety through improved software integrity. Follow him here @weekstweets, find me here www.linkedin.com/in/derekeweeks, and read me here http://blog.sonatype.com/author/weeks/.

@ThingsExpo Stories
Product connectivity goes hand and hand these days with increased use of personal data. New IoT devices are becoming more personalized than ever before. In his session at 22nd Cloud Expo | DXWorld Expo, Nicolas Fierro, CEO of MIMIR Blockchain Solutions, will discuss how in order to protect your data and privacy, IoT applications need to embrace Blockchain technology for a new level of product security never before seen - or needed.
In his keynote at 18th Cloud Expo, Andrew Keys, Co-Founder of ConsenSys Enterprise, provided an overview of the evolution of the Internet and the Database and the future of their combination – the Blockchain. Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settle...
Leading companies, from the Global Fortune 500 to the smallest companies, are adopting hybrid cloud as the path to business advantage. Hybrid cloud depends on cloud services and on-premises infrastructure working in unison. Successful implementations require new levels of data mobility, enabled by an automated and seamless flow across on-premises and cloud resources. In his general session at 21st Cloud Expo, Greg Tevis, an IBM Storage Software Technical Strategist and Customer Solution Architec...
Coca-Cola’s Google powered digital signage system lays the groundwork for a more valuable connection between Coke and its customers. Digital signs pair software with high-resolution displays so that a message can be changed instantly based on what the operator wants to communicate or sell. In their Day 3 Keynote at 21st Cloud Expo, Greg Chambers, Global Group Director, Digital Innovation, Coca-Cola, and Vidya Nagarajan, a Senior Product Manager at Google, discussed how from store operations and ...
Imagine if you will, a retail floor so densely packed with sensors that they can pick up the movements of insects scurrying across a store aisle. Or a component of a piece of factory equipment so well-instrumented that its digital twin provides resolution down to the micrometer.
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, whic...
When shopping for a new data processing platform for IoT solutions, many development teams want to be able to test-drive options before making a choice. Yet when evaluating an IoT solution, it’s simply not feasible to do so at scale with physical devices. Building a sensor simulator is the next best choice; however, generating a realistic simulation at very high TPS with ease of configurability is a formidable challenge. When dealing with multiple application or transport protocols, you would be...
We are given a desktop platform with Java 8 or Java 9 installed and seek to find a way to deploy high-performance Java applications that use Java 3D and/or Jogl without having to run an installer. We are subject to the constraint that the applications be signed and deployed so that they can be run in a trusted environment (i.e., outside of the sandbox). Further, we seek to do this in a way that does not depend on bundling a JRE with our applications, as this makes downloads and installations rat...
Widespread fragmentation is stalling the growth of the IIoT and making it difficult for partners to work together. The number of software platforms, apps, hardware and connectivity standards is creating paralysis among businesses that are afraid of being locked into a solution. EdgeX Foundry is unifying the community around a common IoT edge framework and an ecosystem of interoperable components.
DX World EXPO, LLC, a Lighthouse Point, Florida-based startup trade show producer and the creator of "DXWorldEXPO® - Digital Transformation Conference & Expo" has announced its executive management team. The team is headed by Levent Selamoglu, who has been named CEO. "Now is the time for a truly global DX event, to bring together the leading minds from the technology world in a conversation about Digital Transformation," he said in making the announcement.
In this strange new world where more and more power is drawn from business technology, companies are effectively straddling two paths on the road to innovation and transformation into digital enterprises. The first path is the heritage trail – with “legacy” technology forming the background. Here, extant technologies are transformed by core IT teams to provide more API-driven approaches. Legacy systems can restrict companies that are transitioning into digital enterprises. To truly become a lead...
Digital Transformation (DX) is not a "one-size-fits all" strategy. Each organization needs to develop its own unique, long-term DX plan. It must do so by realizing that we now live in a data-driven age, and that technologies such as Cloud Computing, Big Data, the IoT, Cognitive Computing, and Blockchain are only tools. In her general session at 21st Cloud Expo, Rebecca Wanta explained how the strategy must focus on DX and include a commitment from top management to create great IT jobs, monitor ...
"Cloud Academy is an enterprise training platform for the cloud, specifically public clouds. We offer guided learning experiences on AWS, Azure, Google Cloud and all the surrounding methodologies and technologies that you need to know and your teams need to know in order to leverage the full benefits of the cloud," explained Alex Brower, VP of Marketing at Cloud Academy, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clar...
The IoT Will Grow: In what might be the most obvious prediction of the decade, the IoT will continue to expand next year, with more and more devices coming online every single day. What isn’t so obvious about this prediction: where that growth will occur. The retail, healthcare, and industrial/supply chain industries will likely see the greatest growth. Forrester Research has predicted the IoT will become “the backbone” of customer value as it continues to grow. It is no surprise that retail is ...
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
SYS-CON Events announced today that Conference Guru has been named “Media Sponsor” of the 22nd International Cloud Expo, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. A valuable conference experience generates new contacts, sales leads, potential strategic partners and potential investors; helps gather competitive intelligence and even provides inspiration for new products and services. Conference Guru works with conference organizers to pass great deals to gre...
The Internet of Things will challenge the status quo of how IT and development organizations operate. Or will it? Certainly the fog layer of IoT requires special insights about data ontology, security and transactional integrity. But the developmental challenges are the same: People, Process and Platform. In his session at @ThingsExpo, Craig Sproule, CEO of Metavine, demonstrated how to move beyond today's coding paradigm and shared the must-have mindsets for removing complexity from the develop...
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, led attendees through the exciting evolution of the cloud. He looked at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering m...
"Evatronix provides design services to companies that need to integrate the IoT technology in their products but they don't necessarily have the expertise, knowledge and design team to do so," explained Adam Morawiec, VP of Business Development at Evatronix, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
To get the most out of their data, successful companies are not focusing on queries and data lakes, they are actively integrating analytics into their operations with a data-first application development approach. Real-time adjustments to improve revenues, reduce costs, or mitigate risk rely on applications that minimize latency on a variety of data sources. In his session at @BigDataExpo, Jack Norris, Senior Vice President, Data and Applications at MapR Technologies, reviewed best practices to ...