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
Interruption Engineering - Part I
Search
Pedro Costa
January 15, 2016
Business
0
54
Interruption Engineering - Part I
How interruptions affect you and what can you do about it
FridayTalk @ Subvisual
Pedro Costa
January 15, 2016
Tweet
Share
More Decks by Pedro Costa
See All by Pedro Costa
The Functional Discipline
pfac
0
110
Spree
pfac
0
120
Workshop Git 2013
pfac
2
130
Other Decks in Business
See All in Business
エニグモ_会社紹介資料
enigmo_hr
0
1.7k
malna-recruiting-pitch
malna
0
9.3k
Fracta Leap 会社紹介資料
fracta_leap
PRO
0
160
拝啓、登壇回数0回だった一年前の私へ
natty_natty254
5
290
Sales Marker Culture Book(English)
salesmarker
PRO
2
6.3k
【Progmat】Monthly-ST-Market-Report-2025-Aug.
progmat
0
1k
[T2] 会社紹介資料 2025年9月
t2auto
0
7.5k
新規投資家向け資料
digitalgrid
0
510
物流の専門家がお客様に伴走するサブスク型コンサルティング
mclogi
0
470
ナウビレッジ株式会社_会社紹介資料_20250821
nowvill
0
12k
AIが実現するプロダクトオーナーと開発者の架け橋
bicstone
2
230
なぜ人はすれ違うのか_製造業で当たり前に行っていた根回しから考える、事前の配慮で顧客やチームとの対話を促進する方法
katsuakihoribe8
1
3.3k
Featured
See All Featured
Code Reviewing Like a Champion
maltzj
525
40k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
127
53k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
A better future with KSS
kneath
239
17k
The Art of Programming - Codeland 2020
erikaheidi
56
13k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
Six Lessons from altMBA
skipperchong
28
4k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
8
930
Building Adaptive Systems
keathley
43
2.7k
YesSQL, Process and Tooling at Scale
rocio
173
14k
Fantastic passwords and where to find them - at NoRuKo
philnash
52
3.4k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
Transcript
Engineering Interruptions Part I
Rules 1. Annotate your questions 2. Discuss only when the
color changes
Interruption “The suspension of one stream of work prior to
completion with the intent of returning to and completing the original stream” Boehm-Davis & Remington
Interruptions To accomplish another task Requires some judgement To wait
for something The norm in almost every workplace. Developers: ~15-20% of their time.
Anatomy 1. Trigger 2. Disengage 3. Resume
Consequences Because everything has a cost
Vulnerable to error Competition for limited-capacity cognitive resources
Time consuming Overhead of deciding and restoring context afterwards
Hurtful for performance Stress, frustration, confusion, disorientation
Targeted Ameliorations (expensive word for improvements)
Why is this urgent? Concise, fast, decisive + Easier to
decide - Subjective without a well-defined criteria
Let me just finish this. Polite, assertive, perceivable + Easier
to recall task + Intuitive - Assumes task boundaries
Post-its Silent, personal, situational + Faster return to context +
Handles long interruptions - Assumes time to register context - Error prone due to lack of details
Breadcrumbs Noticeable, proactive + Faster return to context - Assumes
time to create trail - Unfeasible for complex tasks
Overall Aids (ameliorations was already being used)
Acknowledge Predict, plan, control Acknowledge interruptions are bound to happen
Try to predict common interruptions Plan ahead to deal with them Steer your workflow around them
Communicate Notify, explain, notice Define ways to sign you’re busy
Decide beforehand what is an acceptable interruption Handle pending issues between tasks
Focus Analyse, divide, conquer Examine task before tackling Trace a
plan with multiple steps Pause between steps Avoid multitasking
In conclusion Because internet cats are not gonna watch themselves
Be aware interruptions are gonna happen Prepare for it Deep breaths, incremental improvements Find your sweet-spot
To be continued Coming soon Tips for meetings Tips for
presentations Tips for communication