SlideShare ist ein Scribd-Unternehmen logo
1 von 36
Engaging Your Execs
Telling Great Observability
Tales Inspiring Action
Eric D. Schabell
Director Evangelism
@ericschabell{@fosstodon.org}
19 May 2023
KCD Czech & Slovak
chronosphere.io
chronosphere.io
1. What’s storytelling
chronosphere.io
1. What’s storytelling
2. The physiology
chronosphere.io
1. What’s storytelling
3. Telling great tales
2. The physiology
chronosphere.io
What’s storytelling?
chronosphere.io
It’s a conversation, not a performance
chronosphere.io
Authenticity… Be Yourself
chronosphere.io
*100 attendees x 45 mins = 4500 mins = 75 hours
chronosphere.io
The physiology
chronosphere.io
You have 5 mins….
chronosphere.io
1. What’s storytelling
3. Telling great tales
2. The physiology
chronosphere.io
1. What’s storytelling
chronosphere.io
1. What’s storytelling
2. The physiology
chronosphere.io
1. What’s storytelling
2. Storytelling physiology
3. Telling great tales
chronosphere.io
chronosphere.io
chronosphere.io
chronosphere.io
The physiology
chronosphere.io
It’s a conversation, not a performance
chronosphere.io
You have 5 mins….
21
chronosphere.io
Authenticity… Be Yourself
chronosphere.io
chronosphere.io
24
chronosphere.io
“It’s remarkable how common this situation is, where
an organization is paying more for their observability
data, than they do for their production infrastructure.”
chronosphere.io
Data volume
Experiment:
- Hello World app on 4 node
Kubernetes cluster with Tracing,
End User Metrics (EUM), Logs,
Metrics (containers / nodes)
- 30 days == +450 GB
chronosphere.io
87%
of engineers say using cloud
native architectures have
increased the complexity of
discovering and
troubleshooting incidents
chronosphere.io
10 hours
on average, per week, trying to
triage and understand incidents
- a quarter of a 40
hour work week
chronosphere.io
88%
reporting amount of
time on issues
negatively impacts
them and their
careers
chronosphere.io
33%
said those issues disrupted
their personal life
chronosphere.io
39%
admitting they are
frequently stressed out
chronosphere.io
22%
said they want to quit
Cloud Native Observability at
Scale
chronosphere.io
1. What’s storytelling
2. The physiology
3. Telling great tales
chronosphere.io
References
● Presentation Zen, New Riders; 2 edition (December 15, 2011), ASIN: B006R4H5FG
● The Naked Presenter, New Riders; 1 edition (Dec 9, 2010), ISBN 0321704452
● PetchaKutcha.org
● 2023 Chronosphere Observability Report
● Example: Are developers the real emerging technology
● Storytelling slides external: (http://bit.ly/storytelling-slides)
● Speaking Bites: 5 Traits Putting Your Audiences to Sleep
Questions?
Eric D. Schabell
Director Evangelism
@ericschabell{@fosstodon.org}

Weitere ähnliche Inhalte

Mehr von Eric D. Schabell

OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureEric D. Schabell
 
Checking the pulse of your cloud native architecture
Checking the pulse of your cloud native architectureChecking the pulse of your cloud native architecture
Checking the pulse of your cloud native architectureEric D. Schabell
 
3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud DataEric D. Schabell
 
Observability For You and Me with OpenTelemetry (with demo)
Observability For You and Me with OpenTelemetry (with demo)Observability For You and Me with OpenTelemetry (with demo)
Observability For You and Me with OpenTelemetry (with demo)Eric D. Schabell
 
3 Pitfalls Everyone Should Avoid with Cloud Native Observability
3 Pitfalls Everyone Should Avoid with Cloud Native Observability3 Pitfalls Everyone Should Avoid with Cloud Native Observability
3 Pitfalls Everyone Should Avoid with Cloud Native ObservabilityEric D. Schabell
 
Observability For You and Me with OpenTelemetry
Observability For You and Me with OpenTelemetryObservability For You and Me with OpenTelemetry
Observability For You and Me with OpenTelemetryEric D. Schabell
 
Roadmap to Becoming a CNCF Ambassador
Roadmap to Becoming a CNCF AmbassadorRoadmap to Becoming a CNCF Ambassador
Roadmap to Becoming a CNCF AmbassadorEric D. Schabell
 
SRECon EU 2023 - Three Phases to Better Observability Outcomes
SRECon EU 2023 - Three Phases to Better Observability OutcomesSRECon EU 2023 - Three Phases to Better Observability Outcomes
SRECon EU 2023 - Three Phases to Better Observability OutcomesEric D. Schabell
 
Optimizing Observability Spend: Metrics
Optimizing Observability Spend: MetricsOptimizing Observability Spend: Metrics
Optimizing Observability Spend: MetricsEric D. Schabell
 
Optimizing Observability Spend: Metrics
Optimizing Observability Spend: MetricsOptimizing Observability Spend: Metrics
Optimizing Observability Spend: MetricsEric D. Schabell
 
Observability For You and Me with OpenTelemetry
Observability For You and Me with OpenTelemetryObservability For You and Me with OpenTelemetry
Observability For You and Me with OpenTelemetryEric D. Schabell
 
Open Source 101 - Observability For You and Me with OpenTelemetry
Open Source 101 - Observability For You and Me with OpenTelemetryOpen Source 101 - Observability For You and Me with OpenTelemetry
Open Source 101 - Observability For You and Me with OpenTelemetryEric D. Schabell
 
3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud DataEric D. Schabell
 
3 Pitfalls Everyone Should Avoid with Cloud Native Data
3 Pitfalls Everyone Should Avoid with Cloud Native Data3 Pitfalls Everyone Should Avoid with Cloud Native Data
3 Pitfalls Everyone Should Avoid with Cloud Native DataEric D. Schabell
 
DZone webinar - Shift left Observability
DZone webinar - Shift left ObservabilityDZone webinar - Shift left Observability
DZone webinar - Shift left ObservabilityEric D. Schabell
 
Trajectory 2022 - Shifting Cloud Native Observability to the Left
Trajectory 2022 - Shifting Cloud Native Observability to the LeftTrajectory 2022 - Shifting Cloud Native Observability to the Left
Trajectory 2022 - Shifting Cloud Native Observability to the LeftEric D. Schabell
 
PromCon EU 2022 - Centralized vs Decentralized Prometheus Scraping Architectu...
PromCon EU 2022 - Centralized vs Decentralized Prometheus Scraping Architectu...PromCon EU 2022 - Centralized vs Decentralized Prometheus Scraping Architectu...
PromCon EU 2022 - Centralized vs Decentralized Prometheus Scraping Architectu...Eric D. Schabell
 
How to Wrestle Your Observability Data Demons and Win!
How to Wrestle Your Observability Data Demons and Win!How to Wrestle Your Observability Data Demons and Win!
How to Wrestle Your Observability Data Demons and Win!Eric D. Schabell
 
DevConf.US 2022 - Exploring Open Source Edge Success at Scale
DevConf.US 2022 - Exploring Open Source Edge Success at ScaleDevConf.US 2022 - Exploring Open Source Edge Success at Scale
DevConf.US 2022 - Exploring Open Source Edge Success at ScaleEric D. Schabell
 

Mehr von Eric D. Schabell (20)

OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability Adventure
 
Checking the pulse of your cloud native architecture
Checking the pulse of your cloud native architectureChecking the pulse of your cloud native architecture
Checking the pulse of your cloud native architecture
 
3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data
 
Observability For You and Me with OpenTelemetry (with demo)
Observability For You and Me with OpenTelemetry (with demo)Observability For You and Me with OpenTelemetry (with demo)
Observability For You and Me with OpenTelemetry (with demo)
 
3 Pitfalls Everyone Should Avoid with Cloud Native Observability
3 Pitfalls Everyone Should Avoid with Cloud Native Observability3 Pitfalls Everyone Should Avoid with Cloud Native Observability
3 Pitfalls Everyone Should Avoid with Cloud Native Observability
 
Observability For You and Me with OpenTelemetry
Observability For You and Me with OpenTelemetryObservability For You and Me with OpenTelemetry
Observability For You and Me with OpenTelemetry
 
Roadmap to Becoming a CNCF Ambassador
Roadmap to Becoming a CNCF AmbassadorRoadmap to Becoming a CNCF Ambassador
Roadmap to Becoming a CNCF Ambassador
 
SRECon EU 2023 - Three Phases to Better Observability Outcomes
SRECon EU 2023 - Three Phases to Better Observability OutcomesSRECon EU 2023 - Three Phases to Better Observability Outcomes
SRECon EU 2023 - Three Phases to Better Observability Outcomes
 
Optimizing Observability Spend: Metrics
Optimizing Observability Spend: MetricsOptimizing Observability Spend: Metrics
Optimizing Observability Spend: Metrics
 
Optimizing Observability Spend: Metrics
Optimizing Observability Spend: MetricsOptimizing Observability Spend: Metrics
Optimizing Observability Spend: Metrics
 
Observability For You and Me with OpenTelemetry
Observability For You and Me with OpenTelemetryObservability For You and Me with OpenTelemetry
Observability For You and Me with OpenTelemetry
 
Open Source 101 - Observability For You and Me with OpenTelemetry
Open Source 101 - Observability For You and Me with OpenTelemetryOpen Source 101 - Observability For You and Me with OpenTelemetry
Open Source 101 - Observability For You and Me with OpenTelemetry
 
3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data
 
3 Pitfalls Everyone Should Avoid with Cloud Native Data
3 Pitfalls Everyone Should Avoid with Cloud Native Data3 Pitfalls Everyone Should Avoid with Cloud Native Data
3 Pitfalls Everyone Should Avoid with Cloud Native Data
 
DZone webinar - Shift left Observability
DZone webinar - Shift left ObservabilityDZone webinar - Shift left Observability
DZone webinar - Shift left Observability
 
Shift left Observability
Shift left ObservabilityShift left Observability
Shift left Observability
 
Trajectory 2022 - Shifting Cloud Native Observability to the Left
Trajectory 2022 - Shifting Cloud Native Observability to the LeftTrajectory 2022 - Shifting Cloud Native Observability to the Left
Trajectory 2022 - Shifting Cloud Native Observability to the Left
 
PromCon EU 2022 - Centralized vs Decentralized Prometheus Scraping Architectu...
PromCon EU 2022 - Centralized vs Decentralized Prometheus Scraping Architectu...PromCon EU 2022 - Centralized vs Decentralized Prometheus Scraping Architectu...
PromCon EU 2022 - Centralized vs Decentralized Prometheus Scraping Architectu...
 
How to Wrestle Your Observability Data Demons and Win!
How to Wrestle Your Observability Data Demons and Win!How to Wrestle Your Observability Data Demons and Win!
How to Wrestle Your Observability Data Demons and Win!
 
DevConf.US 2022 - Exploring Open Source Edge Success at Scale
DevConf.US 2022 - Exploring Open Source Edge Success at ScaleDevConf.US 2022 - Exploring Open Source Edge Success at Scale
DevConf.US 2022 - Exploring Open Source Edge Success at Scale
 

Kürzlich hochgeladen

DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsSergiu Bodiu
 
The State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptxThe State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptxLoriGlavin3
 
SALESFORCE EDUCATION CLOUD | FEXLE SERVICES
SALESFORCE EDUCATION CLOUD | FEXLE SERVICESSALESFORCE EDUCATION CLOUD | FEXLE SERVICES
SALESFORCE EDUCATION CLOUD | FEXLE SERVICESmohitsingh558521
 
Developer Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLDeveloper Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLScyllaDB
 
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024BookNet Canada
 
Moving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdfMoving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdfLoriGlavin3
 
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024BookNet Canada
 
Time Series Foundation Models - current state and future directions
Time Series Foundation Models - current state and future directionsTime Series Foundation Models - current state and future directions
Time Series Foundation Models - current state and future directionsNathaniel Shimoni
 
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptxPasskey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptxLoriGlavin3
 
Rise of the Machines: Known As Drones...
Rise of the Machines: Known As Drones...Rise of the Machines: Known As Drones...
Rise of the Machines: Known As Drones...Rick Flair
 
Ensuring Technical Readiness For Copilot in Microsoft 365
Ensuring Technical Readiness For Copilot in Microsoft 365Ensuring Technical Readiness For Copilot in Microsoft 365
Ensuring Technical Readiness For Copilot in Microsoft 3652toLead Limited
 
The Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and ConsThe Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and ConsPixlogix Infotech
 
Unraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfUnraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfAlex Barbosa Coqueiro
 
Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Manik S Magar
 
"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr BaganFwdays
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Commit University
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024Lorenzo Miniero
 
A Journey Into the Emotions of Software Developers
A Journey Into the Emotions of Software DevelopersA Journey Into the Emotions of Software Developers
A Journey Into the Emotions of Software DevelopersNicole Novielli
 
DevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenDevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenHervé Boutemy
 
What is Artificial Intelligence?????????
What is Artificial Intelligence?????????What is Artificial Intelligence?????????
What is Artificial Intelligence?????????blackmambaettijean
 

Kürzlich hochgeladen (20)

DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platforms
 
The State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptxThe State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptx
 
SALESFORCE EDUCATION CLOUD | FEXLE SERVICES
SALESFORCE EDUCATION CLOUD | FEXLE SERVICESSALESFORCE EDUCATION CLOUD | FEXLE SERVICES
SALESFORCE EDUCATION CLOUD | FEXLE SERVICES
 
Developer Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLDeveloper Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQL
 
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
 
Moving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdfMoving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdf
 
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
 
Time Series Foundation Models - current state and future directions
Time Series Foundation Models - current state and future directionsTime Series Foundation Models - current state and future directions
Time Series Foundation Models - current state and future directions
 
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptxPasskey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
 
Rise of the Machines: Known As Drones...
Rise of the Machines: Known As Drones...Rise of the Machines: Known As Drones...
Rise of the Machines: Known As Drones...
 
Ensuring Technical Readiness For Copilot in Microsoft 365
Ensuring Technical Readiness For Copilot in Microsoft 365Ensuring Technical Readiness For Copilot in Microsoft 365
Ensuring Technical Readiness For Copilot in Microsoft 365
 
The Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and ConsThe Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and Cons
 
Unraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfUnraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdf
 
Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!
 
"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024
 
A Journey Into the Emotions of Software Developers
A Journey Into the Emotions of Software DevelopersA Journey Into the Emotions of Software Developers
A Journey Into the Emotions of Software Developers
 
DevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenDevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache Maven
 
What is Artificial Intelligence?????????
What is Artificial Intelligence?????????What is Artificial Intelligence?????????
What is Artificial Intelligence?????????
 

Engaging Your Execs - Telling Great Observability Tales Inspiring Action

Hinweis der Redaktion

  1. Key Takeaways - Attendees to this session will be given a small yet powerful set of examples to help them effectively tell their cloud native observability tales to motivate their executives into action. Humans listen to stories (tales) more than they pay attention to pages of charts, dashboards, and data. Learn how to tell your tales, terrifying and educational, with tips and tricks to engage your executives into believing your need for organization’s observability improvements. Abstract: Anyone embedded in the cloud native observability teams in any organization can voice their frustrations at not being taken seriously by their executive decision makers. This leads to way too much on-call stress, frustrations, and eventual burnout. With research showing us DevOps spending over 10 hrs a week on issues in their environments, we could all use quick action by our executives when we find ways to fix our cloud native issues. The trick is to tell the tales we accumulate in such a way as to engage, inspire, and effect change in our organizations. This session provides attendees with ample cloud native bedtime stories, tricks that make your tales land within the executive human mind, and actionable insights to head home with immediate results. Join me for a half hour of power where you are empowered to tell better observability stories for better executive decision outcomes.
  2. Our storytelling today is a journey…. It has a start and a finish with 3 things you’ll use to understand better building and delivery of your stories.
  3. The first starts with framing storytelling as a way to influence, align and motivate people to your way of thinking.
  4. The second discusses some of the physical aspects that you need to know about how your audience perceives your message, how they view your images and how they absorb your information.
  5. Finally, you’ll be given some examples of how building a story includes your personal experiences and apply them in a few example of storytelling based on 2017 experiences from the presenter. These are the 3 things needed to understand when building and delivering stories.
  6. What’s this all about, telling a story? Let’s start by looking at what the basic elements are of storytelling before we look at how to apply them to your individual needs.
  7. It’s not about entertainment… it’s not acting… it’s not a talent...it’s not unstructured…. it’s not magic…. and it’s not hard… the power of storytelling is about having a conversation instead of giving a performance. If you it into a conversation then you have won half the battle. Try engaging the audience, avoid lectern and stand at front edge of the stage, move around to engage all of the audience and make it personal. Questions being asked? Walk over to the person asking, engage and repeat for audience. Just a few of the things you can do to make it a conversation and get the audience involved and engaged.
  8. Each telling of a story is unique, just as the audience is unique Think, work and rework the story all the time The telling gets better after 10 and 20 and 50 times Improvise when needed…. Dropping story script completely if needed Knowing story well allows for jumping and skipping as needed Spontaneity and economy can be elegant and powerful
  9. Contract between speaker and audience You devote time and attention My responsibility to invest time and effort proportional to total hours committed 100 attendees x 45 mins = 4500 mins = 75 hours Do I spend 3 hours in prep? Great tellers prepare obsessively Understand what audience knows about, cares about and wants to hear Keep them curious and interested and engaged in the journey
  10. The physiology of storytelling is crucial for your understanding of the most effective ways to reach your audience. Whether it’s a one-to-one or one-to-many session, you can make simple adjustments to your current way of interacting with your audiences to make the most of your stories.
  11. Cognitive research shows humans focus at best for 5 mins, so: 5 mins to reach audience Best compliment: “I didn’t touch my phone once”
  12. Remember this slide…..
  13. …..used to ensure in first 5 mins I have the info in your cognitive channels.
  14. …..used to ensure in first 5 mins I have the info in your cognitive channels.
  15. …..used to ensure in first 5 mins I have the info in your cognitive channels.
  16. The human mind works on the photographic principle of thirds. By dividing up any image into the above grid, where the lines cross is where the human cognitive recognition will focus, so make sure your important imprintable elements of your slides and images are aligning that way. For western civilization, work from top left to bottom right is a simple and effective manner of transporting visual images.
  17. The house and person in this image are presented in the crossroads using the principle of thirds. Notice for western societies, reading the slide top left to bottom right is comforting for your brain.
  18. While this slide is more comfortable for brains in cultures that read in the opposite direction…. Learn your audiences and adapt your content accordingly.
  19. Let’s look back at the slides we used, are we remaining true to our teachings? Did we position the images and text to reflect the cognitive minds of our audience? The images and text fit to the 4 points that draw our attention to what is being said. In summary: Photography and location on slides Visual over words Slides should almost be useless without storyteller
  20. Let’s look back at the slides we used, are we remaining true to our teachings? Did we position the images and text to reflect the cognitive minds of our audience? The images and text fit to the 4 points that draw our attention to what is being said. In summary: Photography and location on slides Visual over words Slides should almost be useless without storyteller
  21. Let’s look back at the slides we used, are we remaining true to our teachings? Did we position the images and text to reflect the cognitive minds of our audience? The images and text fit to the 4 points that draw our attention to what is being said. In summary: Photography and location on slides Visual over words Slides should almost be useless without storyteller
  22. Let’s look back at the slides we used, are we remaining true to our teachings? Did we position the images and text to reflect the cognitive minds of our audience? The images and text fit to the 4 points that draw our attention to what is being said. In summary: Photography and location on slides Visual over words Slides should almost be useless without storyteller
  23. Practice is what you need to get better at this… but not just tech presentations, try something new and watch others present at a Petcha Kutcha event (http://www.pechakucha.org). 20 sec x 20 slides = 6:40 full automated slides.
  24. Telling your story…. How you can apply what you learned here to your daily messaging, selling, and other influential moments.
  25. And for what purpose? If these organizations could draw a straight line from more data to better outcomes — higher levels of availability, happier customers, faster remediation, more revenue — this tradeoff might make sense. But in many cases, this isn’t true. “Paying more for logging/metrics/tracing doesn’t equate to a positive user experience. Consider how much data can be generated and shipped. $$$. You still need good people to turn data into action.” It’s remarkable how common this situation is, where an organization is paying more for their observability data (typically metrics, logs, traces, and sometimes events), than they do for their production infrastructure. -- The Growth of Observability Data is out of Control
  26. Example of data volumes… shocking. (Source: The Hidden Cost of Data ObservabilityZ)
  27. How do you survive cloud native complexity? With great observability, according to a 2023 Cloud Native Observability Report. This observability report is based on a survey of 500 engineers and software developers who weighed in on ways cloud native complexity makes their jobs harder and the hours longer. With observability, the report concludes, businesses can quickly mitigate incidents, teams innovate faster, and engineering time ROI improves. When done right, observability helps improve both the top and bottom lines. 96% spend most of their time resolving low-level issues 88% reporting that amount of time negatively impacts them and their careers because so much time is spent troubleshooting IT issues. 33% said those issues disrupted their personal life 39% admitting they are frequently stressed out 22% said they want to quit 40% frequently get alerts from their observability solution without enough context to triage the incident 59% said half of the incident alerts they receive from their current observability solution aren’t actually helpful or usable 49% struggle with inconsistent performance using their current approach to observability 45% said their current observability solution requires a lot of manual time and labor 42% of those using a vendor solution said they experienced high-severity incidents quarterly or more versus 61% relying on a platform they built Among organizations not using a vendor solution, the majority said they would consider doing so to enhance team productivity (61%) or improve reliability (54%). https://go.chronosphere.io/2023-observability-report.html
  28. How do you survive cloud native complexity? With great observability, according to a 2023 Cloud Native Observability Report. This observability report is based on a survey of 500 engineers and software developers who weighed in on ways cloud native complexity makes their jobs harder and the hours longer. With observability, the report concludes, businesses can quickly mitigate incidents, teams innovate faster, and engineering time ROI improves. When done right, observability helps improve both the top and bottom lines. 96% spend most of their time resolving low-level issues 88% reporting that amount of time negatively impacts them and their careers because so much time is spent troubleshooting IT issues. 33% said those issues disrupted their personal life 39% admitting they are frequently stressed out 22% said they want to quit 40% frequently get alerts from their observability solution without enough context to triage the incident 59% said half of the incident alerts they receive from their current observability solution aren’t actually helpful or usable 49% struggle with inconsistent performance using their current approach to observability 45% said their current observability solution requires a lot of manual time and labor 42% of those using a vendor solution said they experienced high-severity incidents quarterly or more versus 61% relying on a platform they built Among organizations not using a vendor solution, the majority said they would consider doing so to enhance team productivity (61%) or improve reliability (54%). https://go.chronosphere.io/2023-observability-report.html
  29. How do you survive cloud native complexity? With great observability, according to a 2023 Cloud Native Observability Report. This observability report is based on a survey of 500 engineers and software developers who weighed in on ways cloud native complexity makes their jobs harder and the hours longer. With observability, the report concludes, businesses can quickly mitigate incidents, teams innovate faster, and engineering time ROI improves. When done right, observability helps improve both the top and bottom lines. 96% spend most of their time resolving low-level issues 88% reporting that amount of time negatively impacts them and their careers because so much time is spent troubleshooting IT issues. 33% said those issues disrupted their personal life 39% admitting they are frequently stressed out 22% said they want to quit 40% frequently get alerts from their observability solution without enough context to triage the incident 59% said half of the incident alerts they receive from their current observability solution aren’t actually helpful or usable 49% struggle with inconsistent performance using their current approach to observability 45% said their current observability solution requires a lot of manual time and labor 42% of those using a vendor solution said they experienced high-severity incidents quarterly or more versus 61% relying on a platform they built Among organizations not using a vendor solution, the majority said they would consider doing so to enhance team productivity (61%) or improve reliability (54%). https://go.chronosphere.io/2023-observability-report.html
  30. How do you survive cloud native complexity? With great observability, according to a 2023 Cloud Native Observability Report. This observability report is based on a survey of 500 engineers and software developers who weighed in on ways cloud native complexity makes their jobs harder and the hours longer. With observability, the report concludes, businesses can quickly mitigate incidents, teams innovate faster, and engineering time ROI improves. When done right, observability helps improve both the top and bottom lines. 96% spend most of their time resolving low-level issues 88% reporting that amount of time negatively impacts them and their careers because so much time is spent troubleshooting IT issues. 33% said those issues disrupted their personal life 39% admitting they are frequently stressed out 22% said they want to quit 40% frequently get alerts from their observability solution without enough context to triage the incident 59% said half of the incident alerts they receive from their current observability solution aren’t actually helpful or usable 49% struggle with inconsistent performance using their current approach to observability 45% said their current observability solution requires a lot of manual time and labor 42% of those using a vendor solution said they experienced high-severity incidents quarterly or more versus 61% relying on a platform they built Among organizations not using a vendor solution, the majority said they would consider doing so to enhance team productivity (61%) or improve reliability (54%). https://go.chronosphere.io/2023-observability-report.html
  31. How do you survive cloud native complexity? With great observability, according to a 2023 Cloud Native Observability Report. This observability report is based on a survey of 500 engineers and software developers who weighed in on ways cloud native complexity makes their jobs harder and the hours longer. With observability, the report concludes, businesses can quickly mitigate incidents, teams innovate faster, and engineering time ROI improves. When done right, observability helps improve both the top and bottom lines. 96% spend most of their time resolving low-level issues 88% reporting that amount of time negatively impacts them and their careers because so much time is spent troubleshooting IT issues. 33% said those issues disrupted their personal life 39% admitting they are frequently stressed out 22% said they want to quit 40% frequently get alerts from their observability solution without enough context to triage the incident 59% said half of the incident alerts they receive from their current observability solution aren’t actually helpful or usable 49% struggle with inconsistent performance using their current approach to observability 45% said their current observability solution requires a lot of manual time and labor 42% of those using a vendor solution said they experienced high-severity incidents quarterly or more versus 61% relying on a platform they built Among organizations not using a vendor solution, the majority said they would consider doing so to enhance team productivity (61%) or improve reliability (54%). https://go.chronosphere.io/2023-observability-report.html
  32. How do you survive cloud native complexity? With great observability, according to a 2023 Cloud Native Observability Report. This observability report is based on a survey of 500 engineers and software developers who weighed in on ways cloud native complexity makes their jobs harder and the hours longer. With observability, the report concludes, businesses can quickly mitigate incidents, teams innovate faster, and engineering time ROI improves. When done right, observability helps improve both the top and bottom lines. 96% spend most of their time resolving low-level issues 88% reporting that amount of time negatively impacts them and their careers because so much time is spent troubleshooting IT issues. 33% said those issues disrupted their personal life 39% admitting they are frequently stressed out 22% said they want to quit 40% frequently get alerts from their observability solution without enough context to triage the incident 59% said half of the incident alerts they receive from their current observability solution aren’t actually helpful or usable 49% struggle with inconsistent performance using their current approach to observability 45% said their current observability solution requires a lot of manual time and labor 42% of those using a vendor solution said they experienced high-severity incidents quarterly or more versus 61% relying on a platform they built Among organizations not using a vendor solution, the majority said they would consider doing so to enhance team productivity (61%) or improve reliability (54%). https://go.chronosphere.io/2023-observability-report.html
  33. Data flood is reality of o11y at scale…. drowning.
  34. Remember this slide….. Used to ensure in first 5 mins I have the info in your cognitive channels and shown 3 times to ensure it’s embedded and you’ll not forget what the highlights of this session are!
  35. References to help you on your journey!
  36. Key Takeaways - Attendees to this session will be given a small yet powerful set of examples to help them effectively tell their cloud native observability tales to motivate their executives into action. Humans listen to stories (tales) more than they pay attention to pages of charts, dashboards, and data. Learn how to tell your tales, terrifying and educational, with tips and tricks to engage your executives into believing your need for organization’s observability improvements. Abstract: Anyone embedded in the cloud native observability teams in any organization can voice their frustrations at not being taken seriously by their executive decision makers. This leads to way too much on-call stress, frustrations, and eventual burnout. With research showing us DevOps spending over 10 hrs a week on issues in their environments, we could all use quick action by our executives when we find ways to fix our cloud native issues. The trick is to tell the tales we accumulate in such a way as to engage, inspire, and effect change in our organizations. This session provides attendees with ample cloud native bedtime stories, tricks that make your tales land within the executive human mind, and actionable insights to head home with immediate results. Join me for a half hour of power where you are empowered to tell better observability stories for better executive decision outcomes.