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
YADOKARI CULTURE DECK 2025
yadokari
0
500
Company Profile
katsuegu23
2
12k
ホワイトプラス会社紹介資料 / wp_introduction
whiteplus_recruit
0
270
VISASQ: ABOUT US
eikohashiba
15
540k
エンジニアよ痛みを知れ
nobuoooo
0
170
会社紹介資料
gatechnologies
2
140k
Dayz株式会社 / 会社案内
dayzjp
PRO
0
150
爆速入力が可能に! つよ〜い味方 Aqua Voice
panchaaan_2
0
190
目標の50記事を達成したわけだが
suzuki_tada
0
140
NicoScan - 領収書・請求書をAI-OCRでExcel自動変換
raimiura
1
260
goooods株式会社 / Company Deck
goooodsdesign
0
1.2k
株式会社スマートラウンド 会社紹介資料 / CompanyDeck
smartround
0
430
Featured
See All Featured
Speed Design
sergeychernyshev
33
1.4k
The Cult of Friendly URLs
andyhume
79
6.7k
Statistics for Hackers
jakevdp
799
230k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
25
1.7k
We Have a Design System, Now What?
morganepeng
54
7.9k
The untapped power of vector embeddings
frankvandijk
1
1.5k
16th Malabo Montpellier Forum Presentation
akademiya2063
PRO
0
32
The Curse of the Amulet
leimatthew05
0
4.9k
Reality Check: Gamification 10 Years Later
codingconduct
0
1.9k
Design of three-dimensional binary manipulators for pick-and-place task avoiding obstacles (IECON2024)
konakalab
0
320
Designing for Timeless Needs
cassininazir
0
96
AI Search: Where Are We & What Can We Do About It?
aleyda
0
6.7k
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