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
120
Spree
pfac
0
120
Workshop Git 2013
pfac
2
130
Other Decks in Business
See All in Business
サステナビリティレポート2025
hamayacorp
0
170
Sreake事業部説明資料
3shake
0
350
【Progmat】Monthly-ST-Market-Report-2026-Jan.
progmat
0
280
アシスト 会社紹介資料
ashisuto_career
3
150k
会社説明資料
xinghr
0
140
ARI会社説明
arisaiyou
1
21k
ネクストビート 新卒向け会社紹介資料
nextbeat
1
350
【northernforce#54】AIの歴史と仕組みから学ぶAIエージェント入門
yoshi17
0
250
株式会社Gizumo_会社紹介資料(2026.1更新)
gizumo
0
520
Le bon Mindset – Gymnastique Québec
jdejongh
PRO
0
110
プロダクトにAIを。 確率的なふるまいと向き合う。
sugitlab
1
360
40代データ人材のキャリア戦略
pacocat
4
3.9k
Featured
See All Featured
The Limits of Empathy - UXLibs8
cassininazir
1
210
Thoughts on Productivity
jonyablonski
74
5k
Optimising Largest Contentful Paint
csswizardry
37
3.6k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
35
2.4k
Designing for Timeless Needs
cassininazir
0
130
How to Build an AI Search Optimization Roadmap - Criteria and Steps to Take #SEOIRL
aleyda
1
1.9k
Ecommerce SEO: The Keys for Success Now & Beyond - #SERPConf2024
aleyda
1
1.8k
Speed Design
sergeychernyshev
33
1.5k
The Cost Of JavaScript in 2023
addyosmani
55
9.5k
[SF Ruby Conf 2025] Rails X
palkan
0
740
DevOps and Value Stream Thinking: Enabling flow, efficiency and business value
helenjbeal
1
90
Building a A Zero-Code AI SEO Workflow
portentint
PRO
0
300
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