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
20260114_知的生産と事業創造でAIを使いこなす全技法_スライド
itarutomy
1
450
AI × アジャイルで、エンタープライズを動かす:文化に寄り添い、ビジネス価値を拡大する実践知 / AI × Agile: Driving Enterprise Transformation
yosuke_matsuura
PRO
1
1.4k
会社紹介資料 / ProfileBook
gpol
5
55k
AI時代のPMに求められるマインドセット
kozotaira
1
200
ノッカリアドベントカレンダー全記録まとめ
szkm555
0
130
Sreake事業部説明資料
3shake
0
350
株式会社ファーマインド_グループ農園各社_会社紹介資料
farmind_farm
0
120
【琉球ウェルネス】ウェルネスオフサイト:サービス概要資料
ryukyuwellness
0
180
アシスト 会社紹介資料
ashisuto_career
3
150k
会社説明資料
xinghr
0
140
【northernforce#54】AIの歴史と仕組みから学ぶAIエージェント入門
yoshi17
0
250
-生きる-AI時代におけるライターの生存戦略
mimuhayashi
0
200
Featured
See All Featured
Designing Powerful Visuals for Engaging Learning
tmiket
0
220
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
49
9.8k
Amusing Abliteration
ianozsvald
0
96
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
141
34k
Google's AI Overviews - The New Search
badams
0
900
Designing for humans not robots
tammielis
254
26k
A Modern Web Designer's Workflow
chriscoyier
698
190k
How to Talk to Developers About Accessibility
jct
2
130
What the history of the web can teach us about the future of AI
inesmontani
PRO
1
420
The SEO Collaboration Effect
kristinabergwall1
0
350
Six Lessons from altMBA
skipperchong
29
4.1k
We Analyzed 250 Million AI Search Results: Here's What I Found
joshbly
1
670
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