Customers don't care about five-nines reliability; they care about five-nines customer service.

-
Abridged version of my longer article "DevOps is more about customer feedback and quick learning than Culture/Process/Tools":
Your customers don't really care if you are a DevOps shop/factory; they care about how your products add value to their lives. Common misconceptions about DevOps:  #1: We are a team of developers doing operations - we are DevOps! 
#2: We are a Dev team continually deploying to production - we are DevOps!
#3: We are a team of Ops wrtiing code - we are DevOps!

Customer-focused software engineers - the missing piece of the DevOps puzzle:  
#1: They are intrapranuers
#2: They don't indulge in mindless tasks
#3: They strive to get customer feedback quickly
DevOps Patterns - from a customer's perspective:  #1: Uptime is overrated. Customers don't care about five-nines reliability; they care about five-nines customer service.
#2: Velocity is overrated; customer feedback is underrated. Your customers don't care about how many times a day you ship; they care about how quickly you can listen to them and learn from the feedback.  #3: With the democratization of Operations - everyone is Ops & everyone is a Dev. Ops is moving up the Stack; dev is moving down the Stack.  #4: DevOps is table stakes. The strategic differentiator will be how obsessed you are with your customers (both internal and external) DevOps Anti-Patterns #1: I want my software developers to focus on writing features; I don't want them to be doing low-level work like responding to alerts, running incidents, etc. So, let me insert 3 layers in between

 #2: I don't want to waste my software developers' time by having them focus on failed tests. I don't want them to do dealing with failed deployments. Heck, I don't want them to be dealing with deployments at all. Let me hire a team that will do the build, test, deploy, rollback, etc. 


 Are you really DevOps? 
Full article: "DevOps" is more about Customer Feedback and Quick Learning than Culture/Process/Tools


Comments

Post a Comment

Popular posts from this blog

Want to Solve Over-Monitoring and Alert Fatigue? Create the Right Incentives!

-
Image
Note   — I have been giving talks around the world on this topic (SREcon, Velocity, etc). Figured, I can reach more people through an article. Any/all feedback is highly appreciated! "Research has shown that 72%–99% of ECG monitor alarms are false or clinically insignificant." Quite a staggering number and quite scary given that lives are at stake. If you have ever been to an ICU, you cannot help but notice the telemetry monitors and their constant beeping (they are such a common sight). In fact, I had the first-hand experience with these monitors in the NICU where my twin boys were being cared for after being born prematurely. I still remember vividly how my wife and I used to freak out every time one of these started to go off. Being an ops guy, I could not help but relate this to being paged while on call. Because I was curious, I did a bit of a research on this topic and found that some Ph.D. students had actually published a paper on this topic in 2013. It
Read more

Artwork: DevOps Patterns and Antipatterns

-
Image
Great artwork of my DevOpsDays NYC talk last month, explaining DevOps patterns and anti-patterns; and some great feedback (from some well-respected folks):   "The topic from @KishoreJalleda is one of the best I’ve heard brought up in a long time. We need to progress closer to the customer and it’s a topic I’ve been fascinated by for a while now." "Availability is everyone’s job, not just ops!💯 @KishoreJalleda"  "YES! Uptime 9s don’t matter if users are unhappy! Hearing how much uptime is good enough makes me happy"  "Your customers don't care how many times a day you ship code, @KishoreJalleda on focusing on end users, not engineering velocity"  "It’s really important to know true empathy, live like your customers; embrace their experiences"  "Ops Engineering isn’t dead or going anywhere, but it’s time to take responsibility for our destiny."  "DevOps is table stakes. Everyone is moving toward that. The r
Read more

Difference between Junior and Senior Engineers/Managers/Leaders

-
Qualities of junior engineers/managers/leaders or just about anyone in general:  1. Struggle with brevity; struggle with coming to the point.  2. Use hyperbole to get their point across.  3. Complain about not being invited to that important meeting. 4. Jump to broadcasting a problem w/o thinking through consequences-- just to be the first one.  5. Worry more about looking smart. 6. Only state problems. 7. Love status quo or don't know how to get out.  8. Have a myopic view. Don't understand the root cause; don't ensure production defects remain fixed.   How to become senior?   1. Come straight to the point; provide details later (or, if asked).  2. Avoid hyperbole like "single-handed", "must read" (may be OK in some cultures). 3. Ask that you are invited. Simple. Don't complain; act. Be a leader.   4. Think through the problem; craft your message, and only then deliver.  5. Worry less about looking smart; put more energy into learn
Read more