Interruptions and Context
15 articles on interruptions and context.
Sort Your Interruptions Into Two Piles and Only One Should Reach You
Focus time fails because it blocks real questions and repeat questions alike. Log a week, sort them, and make the second pile never arrive.
An Internal FAQ That Stays Current (Most Do Not, Here Is Why)
FAQs go stale because they mix answers that never change with answers that change weekly. Split them, and cap the stable half at twenty entries.
Nobody Reads the Docs. Here Is What They Do Instead.
People message the person who wrote the doc, because asking takes eleven seconds and works. Better search and better structure do not fix it.
Why Decisions Keep Getting Revisited (It Is Not the Decision)
Decisions get reopened because nobody wrote down who owned them. Without an owner every decision is provisional.
Decision Log Template, and the Three Fields Most Templates Miss
Most templates capture what and why. The three that prevent arguments: who can change it, when to revisit it, and what it assumes. Plus why logs stop in March.
Documenting Decisions So They Stop Getting Reopened
Recording a decision and retrieving one are different problems. Write four lines, then clear the real bar: retrieval by someone who was not there.
Tribal Knowledge: Getting It Out of Heads Without a Documentation Project
Documentation sprints last a sprint. Tribal knowledge is current state, past decisions, and dead ends.
Bus Factor of One: the Person Who Can Never Take a Holiday
Bus factor is not a catastrophe risk, it is an annual cost: one holiday, a fortnight of lost momentum. Why documentation misses it and what actually reduces it.
Knowledge Silos on a Distributed Team: the Fix Is Not Another Wiki
A silo is a routing problem, not a storage problem. Wikis fail because they ask the reader to know what the answer is called.
Answering the Same Question for the Fourth Time Is a System Failure
The fourth time you answer something, the problem is not the asker. The answer exists and is not reachable.
Slack Norms a Team Actually Keeps (Template)
Six norms, not twenty: response time, channels over DMs, whole question, threads, scheduled send, and check what they wrote down before you ask.
Protecting Focus Time When Everyone Can See Your Calendar
A focus block is visible to everyone and defended by no one. It stops meetings and not messages. Here is why it fails, and what has to exist behind it.
Reducing Slack Interruptions on a Team of Twelve
On a twelve-person team the channel becomes a support desk with one unpaid operator. Four steps in order, ending with the one that works.
Context Switching: the Cost Is in the Questions, Not the Tickets
Work-in-progress limits fix the switches you planned. The expensive ones are involuntary: someone asks where a thing is and you drop what you were holding.
What Interruptions Cost an Engineering Team, and Where They Come From
The cost of an interruption is the recovery, not the two minutes. Where interruptions come from, and why two people absorb most of them.
Your team’s week, answered from the work.
If this is your team’s week, see what a StandIn does with it.