|By Derek Weeks||
|April 29, 2016 05:00 PM EDT||
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.
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.
Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more business becomes digital the more stakeholders are interested in this data including how it relates to business. Some of these people have never used a monitoring tool before. They have a question on their mind like “How is my application doing” but no id...
Apr. 30, 2017 07:45 PM EDT Reads: 7,479
Is your application too difficult to manage? Do changes take dozens of developers hundreds of hours to execute, and frequently result in downtime across all your site’s functions? It sounds like you have a monolith! A monolith is one of the three main software architectures that define most applications. Whether you’ve intentionally set out to create a monolith or not, it’s worth at least weighing the pros and cons of the different architectural approaches and deciding which one makes the most s...
Apr. 30, 2017 07:30 PM EDT Reads: 3,079
Developers want to create better apps faster. Static clouds are giving way to scalable systems, with dynamic resource allocation and application monitoring. You won't hear that chant from users on any picket line, but helping developers to create better apps faster is the mission of Lee Atchison, principal cloud architect and advocate at New Relic Inc., based in San Francisco. His singular job is to understand and drive the industry in the areas of cloud architecture, microservices, scalability ...
Apr. 30, 2017 07:00 PM EDT Reads: 3,769
When you decide to launch a startup company, business advisors, counselors, bankers and armchair know-it-alls will tell you that the first thing you need to do is get funding. While there is some validity to that boilerplate piece of wisdom, the availability of and need for startup funding has gone through a dramatic transformation over the past decade, and the next few years will see even more of a shift. A perfect storm of events is causing this seismic shift. On the macroeconomic side this ...
Apr. 30, 2017 06:30 PM EDT Reads: 731
Cloud promises the agility required by today’s digital businesses. As organizations adopt cloud based infrastructures and services, their IT resources become increasingly dynamic and hybrid in nature. Managing these require modern IT operations and tools. In his session at 20th Cloud Expo, Raj Sundaram, Senior Principal Product Manager at CA Technologies, will discuss how to modernize your IT operations in order to proactively manage your hybrid cloud and IT environments. He will be sharing be...
Apr. 30, 2017 01:00 PM EDT Reads: 1,105
Cloud Expo, Inc. has announced today that Aruna Ravichandran, vice president of DevOps Product and Solutions Marketing at CA Technologies, has been named co-conference chair of DevOps at Cloud Expo 2017. The @DevOpsSummit at Cloud Expo New York will take place on June 6-8, 2017, at the Javits Center in New York City, New York, and @DevOpsSummit at Cloud Expo Silicon Valley will take place Oct. 31-Nov. 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Apr. 30, 2017 11:30 AM EDT Reads: 2,945
A Man in the Middle attack, or MITM, is a situation wherein a malicious entity can read/write data that is being transmitted between two or more systems (in most cases, between you and the website that you are surfing). MITMs are common in China, thanks to the “Great Cannon.” The “Great Cannon” is slightly different from the “The Great Firewall.” The firewall monitors web traffic moving in and out of China and blocks prohibited content. The Great Cannon, on the other hand, acts as a man in the...
Apr. 30, 2017 07:30 AM EDT Reads: 583
To more closely examine the variety of ways in which IT departments around the world are integrating cloud services, and the effect hybrid IT has had on their organizations and IT job roles, SolarWinds recently released the SolarWinds IT Trends Report 2017: Portrait of a Hybrid Organization. This annual study consists of survey-based research that explores significant trends, developments, and movements related to and directly affecting IT and IT professionals.
Apr. 30, 2017 05:30 AM EDT Reads: 1,966
NHK, Japan Broadcasting, will feature the upcoming @ThingsExpo Silicon Valley in a special 'Internet of Things' and smart technology documentary that will be filmed on the expo floor between November 3 to 5, 2015, in Santa Clara. NHK is the sole public TV network in Japan equivalent to the BBC in the UK and the largest in Asia with many award-winning science and technology programs. Japanese TV is producing a documentary about IoT and Smart technology and will be covering @ThingsExpo Silicon Val...
Apr. 30, 2017 03:45 AM EDT Reads: 9,497
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Apr. 30, 2017 03:30 AM EDT Reads: 6,286
Keeping pace with advancements in software delivery processes and tooling is taxing even for the most proficient organizations. Point tools, platforms, open source and the increasing adoption of private and public cloud services requires strong engineering rigor – all in the face of developer demands to use the tools of choice. As Agile has settled in as a mainstream practice, now DevOps has emerged as the next wave to improve software delivery speed and output. To make DevOps work, organization...
Apr. 30, 2017 02:45 AM EDT Reads: 9,297
Enterprise architects are increasingly adopting multi-cloud strategies as they seek to utilize existing data center assets, leverage the advantages of cloud computing and avoid cloud vendor lock-in. This requires a globally aware traffic management strategy that can monitor infrastructure health across data centers and end-user experience globally, while responding to control changes and system specification at the speed of today’s DevOps teams. In his session at 20th Cloud Expo, Josh Gray, Chie...
Apr. 29, 2017 10:45 AM EDT Reads: 3,632
This recent research on cloud computing from the Register delves a little deeper than many of the "We're all adopting cloud!" surveys we've seen. They found that meaningful cloud adoption and the idea of the cloud-first enterprise are still not reality for many businesses. The Register's stats also show a more gradual cloud deployment trend over the past five years, not any sort of explosion. One important takeaway is that coherence across internal and external clouds is essential for IT right n...
Apr. 28, 2017 05:00 PM EDT Reads: 2,008
Back in February of 2017, Andrew Clay Schafer of Pivotal tweeted the following: “seriously tho, the whole software industry is stuck on deployment when we desperately need architecture and telemetry.” Intrigue in a 140 characters. For me, I hear Andrew saying, “we’re jumping to step 5 before we’ve successfully completed steps 1-4.”
Apr. 28, 2017 02:00 PM EDT Reads: 1,994
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, will discuss how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He will discuss 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.
Apr. 28, 2017 06:00 AM EDT Reads: 4,492
In large enterprises, environment provisioning and server provisioning account for a significant portion of the operations team's time. This often leaves users frustrated while they wait for these services. For instance, server provisioning can take several days and sometimes even weeks. At the same time, digital transformation means the need for server and environment provisioning is constantly growing. Organizations are adopting agile methodologies and software teams are increasing the speed ...
Apr. 27, 2017 08:30 PM EDT Reads: 3,540
Software as a service (SaaS), one of the earliest and most successful cloud services, has reached mainstream status. According to Cisco, by 2019 more than four-fifths (83 percent) of all data center traffic will be based in the cloud, up from 65 percent today. The majority of this traffic will be applications. Businesses of all sizes are adopting a variety of SaaS-based services – everything from collaboration tools to mission-critical commerce-oriented applications. The rise in SaaS usage has m...
Apr. 22, 2017 06:15 PM EDT Reads: 5,112
The proper isolation of resources is essential for multi-tenant environments. The traditional approach to isolate resources is, however, rather heavyweight. In his session at 18th Cloud Expo, Igor Drobiazko, co-founder of elastic.io, drew upon his own experience with operating a Docker container-based infrastructure on a large scale and present a lightweight solution for resource isolation using microservices. He also discussed the implementation of microservices in data and application integrat...
Apr. 22, 2017 05:45 AM EDT Reads: 6,553
We'd all like to fulfill that "find a job you love and you'll never work a day in your life" cliché. But in reality, every job (even if it's our dream job) comes with its downsides. For you, the constant fight against shadow IT might get on your last nerves. For your developer coworkers, infrastructure management is the roadblock that stands in the way of focusing on coding. As you watch more and more applications and processes move to the cloud, technology is coming to developers' rescue-most r...
Apr. 22, 2017 04:00 AM EDT Reads: 4,285
2016 has been an amazing year for Docker and the container industry. We had 3 major releases of Docker engine this year , and tremendous increase in usage. The community has been following along and contributing amazing Docker resources to help you learn and get hands-on experience. Here’s some of the top read and viewed content for the year. Of course releases are always really popular, particularly when they fit requests we had from the community.
Apr. 22, 2017 03:45 AM EDT Reads: 3,848