Library
Articles
Shorter Library articles on rates, focus, meetings, and working days. Guides remain the longer methods.
Articles
-
Availability
Why "available all day" is a bad system for remote output
Always-on chat looks like teamwork and behaves like an open inbox on your brain. Replace it with visible windows, response tiers, and one protected block.
-
Estimates
A personal estimate postmortem template that stays honest
A private, practical postmortem for when your estimate missed - causes, math, and one process change. Not team blameless theater, not self-punishment.
-
Debugging
Why interruptions are expensive during debugging
Mid-debug you are running a mental simulation. One ping can erase it. Signs you are in the fragile zone and how teams reduce damage.
-
Communication systems
Why “just ping me” is not a communication system
Replace informal ping culture with owners, written requests, and response windows - so distributed work stops depending on whoever is online.
-
Capacity
Why planning eight hours of work into eight hours fails
Meetings, messages, and recovery time are not optional extras. A honest capacity sheet and how to plan a day that can actually finish.
-
Status
How to write async status updates people actually read
Done, open, blocked, with links and dates. A scannable format, weak examples rewritten, and habits that make status trustworthy.
-
Next actions
Why remote workers need a clear next action
Topic-shaped tasks stall remote days. Rules for rewriting them as startable actions, plus a worked conversion of messy meeting notes.
-
Outcomes
The difference between being busy and finishing work
Busy is a record of where your attention went. Finished is a record of what changed. How to tell them apart before the week ends.
-
Developers
Deep work for developers: what actually counts
Coding depth is not long hours. Working set, test loop, review boundaries, and how to end a block so tomorrow’s restart is cheap.