Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
20250424_Reliable Communication Through Diagrams
Search
gonkun
July 27, 2025
0
1
20250424_Reliable Communication Through Diagrams
gonkun
July 27, 2025
Tweet
Share
More Decks by gonkun
See All by gonkun
20250709_What is SRE, and Why Are We Here Together?
gonkun
0
2
20240119_KEDAでスパイク負荷を迎え撃つ。メトリクスとスケジュールドリブンなオートスケールでKubernetes上のプロダクトの信頼性を高めよう/lets_use_keda_for_reliability
gonkun
1
330
20230929_SRE_NEXT_エラーバジェット運用までの取り組み-信頼性の低下に対するアクションを定義しよう / Let's define actions against unreliability
gonkun
2
3.4k
はじめの一歩を踏み出したい方へ~SREというロールを担うためにやったこと、学びや反省 / Let's start the first step to the SRE
gonkun
2
570
Featured
See All Featured
[RailsConf 2023] Rails as a piece of cake
palkan
56
5.7k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.9k
The Straight Up "How To Draw Better" Workshop
denniskardys
235
140k
How to train your dragon (web standard)
notwaldorf
96
6.1k
VelocityConf: Rendering Performance Case Studies
addyosmani
332
24k
We Have a Design System, Now What?
morganepeng
53
7.7k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
31
1.3k
Writing Fast Ruby
sferik
628
62k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
251
21k
Visualization
eitanlees
146
16k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Thoughts on Productivity
jonyablonski
69
4.8k
Transcript
Reliable Communication Through Diagrams Sasaki Yuta
Simple Diagrams Can Make Our Communication More Reliable
System Reliability
Communication Reliability System Reliability
Have you ever received messages like this? Introduction
Made you spend extra time searching for answers Does This
Sound Familiar? Introduction Invest 60 min Ask
Have you ever sent messages like this? Introduction
Triggered negative reactions due to lack of context Does This
Sound Familiar? Introduction Need ?? min Ask
Unbalanced Message Can Lead to Confusion — Like a System
Failure
Simple Diagrams Can Make Our Communication More Reliable
The Mechanism of Communication Failures
Anatomy of Communication Failures 1.Conceptualization
Anatomy of Communication Failures Transpiler (EN) Text 1.Conceptualization 2.Encode
Anatomy of Communication Failures Transpiler (EN) Text Transpiler (EN) 1.Conceptualization
2.Encode 3.Decode → Ask Something →
Anatomy of Communication Failures Transpiler (EN) Text Transpiler (EN) 1.Conceptualization
2.Encode 3.Decode 4.Mental Imagery → Ask Something →
Anatomy of Communication Failures Transpiler (EN) Text Transpiler (EN) 1.Conceptualization
2.Encode 3.Decode 4.Mental Imagery → Ask Something →
Anatomy of Communication Failures Transpiler (EN) Text Transpiler (EN) 1.Conceptualization
2.Encode 3.Decode 4.Mental Imagery Transpiler (JA) もじ Transpiler (JA) Success rate: 0.9 Success rate: 0.9 Success rate: 0.9 Success rate: 0.9 Overall success rate: 0.66 (0.9^4)
Anatomy of Communication Failures Transpiler (EN) Text Transpiler (EN) 1.Conceptualization
2.Encode 3.Decode 4.Mental Imagery Things get worse when we work with unwell known teams
How about using a diagram together?
• Visualizing Self-Understanding • Skipping the Thought-to-Language Step • Ensuring
Redundancy 3 Effects for Communication Reliability Visual Communication
3 Effects for Improved Reliability Effect 1: Visualizing Self-Understanding ?
???
3 Effects for Improved Reliability Effect 2: Skipping the Thought-to-Language
Step Success rate: 0.9 Success rate: 0.9 Transpiler (EN) Text Transpiler (EN) Overall success rate: 0.81 Skip Skip
3 Effects for Improved Reliability Effect 3: Ensuring Redundancy Transpiler
(EN) Text Transpiler (EN)
That's a nice idea, but is it practical…?
• Not knowing what to draw • Creating diagrams takes
time Common Concerns
Concern 1: Not Knowing What to Draw
Asking Is Simple — Just 4 Elements
What to Draw: 4 Essentials Concern 1: Not Knowing What
to Draw Purpose As Is To Be How What’s our ultimate goal?
What to Draw: 4 Essentials Concern 1: Not Knowing What
to Draw Purpose As Is To Be How What’s our ultimate goal? What’s the ideal situation?
What’s the current status? What to Draw: 4 Essentials Concern
1: Not Knowing What to Draw Purpose As Is To Be How What’s our ultimate goal? What’s the ideal situation?
What’s the current status? What to Draw: 4 Essentials Concern
1: Not Knowing What to Draw Purpose As Is To Be How What’s our ultimate goal? How do we achieve it? What’s the ideal situation?
What’s the current status? When Asking a Question Concern 1:
Not Knowing What to Draw Purpose As Is To Be ? What’s our ultimate goal? Need help with this part What’s the ideal situation?
A Classic Case of Communication Failure
A Classic Case of Communication Failure I want to fix
an error in CI. We're getting a permission error. Other team My team
A Classic Case of Communication Failure I want to fix
an error in CI. We're getting a permission error. ???
A Classic Case of Communication Failure I want to fix
an error in CI. We're getting a permission error. ??? • What are you trying to do? • Which AWS account? • What does your system look like? • etc…
A Classic Case of Communication Failure I want to fix
an error in CI. We're getting a permission error. Invest 60 min They wanted to deploy frontend assets to S3 using GitHub Actions but didn't know how to set up OIDC authentication correctly.
Let's Break Down Their Request!
Trying to push from GitHub repository to S3, but getting
permission errors Purpose As Is To Be To distribute frontend assets Push assets to S3 with GitHub Actions How Don't know how to set up correct Role
System architecture (ToBe)
What If This Diagram Was Shared from the Start?
This Could Have Taken Just 5 Minutes
Let’s Improve This Diagram more!
Purpose: To distribute frontend assets To Be As Is But
getting permission error Push assets to S3 Improvement: Put a system architecture
Purpose: To distribute frontend assets Improvement: Merge two diagrams
Purpose: To distribute frontend assets Actual status Desired status Improvement:
Use two types line
Purpose: To distribute frontend assets Actual status Desired status Error:
xxx permission denied. But we don’t know why… Improvement: Add messages
Concern 2: Creating Diagrams Takes Time
Yes, it does take time.
But let’s think about the total time for everyone.
Concern 2: Creating Diagrams Takes Time Common concerns Invest 30
min Reduce 30 min VS A fair trade!! → Ask Something → Text +
Concern 2: Creating Diagrams Takes Time Common concerns Invest 30
min Reduce 60 min VS → Ask Something → Text + A good deal!!
Concern 2: Creating Diagrams Takes Time Common concerns Invest 30
min Reduce 150 min VS → Ask Something → Text + − 30 min − 30 min − 30 min − 30 min − 30 min A great value!!
Let’s Respect Their Time — and Save It.
Conclusion
Three Core Values of Visual Communication • Helping yourself understand
better • Helping everyone understand quickly — even across language barriers • Saving time for everyone Conclusion
One Step to Start Tomorrow Conclusion What’s the current status?
Purpose As Is To Be How What’s our ultimate goal? How do we achieve it? What’s the ideal situation?
One Steps to Start Tomorrow Actual status Desired status Error:
xxx permission denied. But we don’t know why… Conclusion
Let’s Keep Our Communication Reliability Through Drawings!