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
59
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Interruption Engineering - Part I
How interruptions affect you and what can you do about it
FridayTalk @ Subvisual
Pedro Costa
January 15, 2016
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
アッテル会社紹介資料/culture deck
attelu
11
17k
Corporate Story (GA technologies Co., Ltd.)
gatechnologies
0
960
パーソルクロステクノロジー_グループソリューション本部のご紹介 / Introduction_of_gs
pxt_gs_ssol
0
3.5k
Copilotで資料を作るようになって仕事のやり方が変わった話
aonomasahiro
2
550
Decentier_Corporate Deck_2026
decentier
PRO
0
470
加齢で記憶力が落ちてきた私が、obsidian × claude codeで育つ第二の脳をつくった話
ratsbane666
0
110
ITが何の略なのかも知らないままエンジニアになっちゃったのでインターネットに生き恥を晒してみた話
m_k__77
1
300
【サービス資料】toiro BPO.pdf
shiftgroup
PRO
0
370
営業、広報、開発。 多面的なAIネイティブ化のための 基盤について
timakin
0
210
BacklogとAIで変わった、 ウェブディレクターの仕事のリアル
wattlaa
0
300
VISASQ: ABOUT DEV TEAM
eikohashiba
6
44k
会社説明資料
kurashima
0
1.5k
Featured
See All Featured
The browser strikes back
jonoalderson
0
1.3k
Faster Mobile Websites
deanohume
310
32k
The agentic SEO stack - context over prompts
schlessera
0
820
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
31
10k
Rails Girls Zürich Keynote
gr2m
96
14k
Discover your Explorer Soul
emna__ayadi
2
1.1k
For a Future-Friendly Web
brad_frost
183
10k
Mozcon NYC 2025: Stop Losing SEO Traffic
samtorres
1
260
The Straight Up "How To Draw Better" Workshop
denniskardys
239
140k
StorybookのUI Testing Handbookを読んだ
zakiyama
31
6.8k
HDC tutorial
michielstock
2
720
GitHub's CSS Performance
jonrohan
1033
470k
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