Attention Management in Software Development
Standard operating procedures for getting software work done with a limited supply of attention: choosing what to work on, starting, protecting focus, recovering after an interruption, finishing and shipping, and handing work to and from AI agents.
Everyone has limits to attention. These SOPs are written for anyone who builds software, alone or on a team, with people or with AI agents. Research on ADHD is one well-studied lens on attention, and the SOPs cite it where it applies; they are not an ADHD guide and they are not medical advice.
Each page is also served as raw Markdown at its .md URL,
for agents and tools that follow the SOPs directly. The agent index is
llms.txt.
SOPs
No SOP has been adopted yet. Each SOP is drafted as Version 1 and tried on real work before it is adopted.
| SOP | Version | Adopted | Status |
|---|---|---|---|
| Starting a task | 1 | Draft, in trial |
How the SOPs work
- Every SOP opens with a status line: "Version N, adopted YYYY-MM-DD. Proven on n cases."
- Research claims carry an evidence level: Strong, Some, Practice or Field.
- A big change ships as a new version with a dated entry in the changelog. Old versions stay readable.
- Changes arrive as change requests, not edits.
The details are in How it works.
Principles
- Attention is an asset to direct, not a flaw to fix. Curiosity, divergent thinking, deep focus and a wandering mind are strengths. The SOPs shape the work around them rather than asking the person to change.
- No guilt, streaks, scores or quotas. Work is "still open", never "missing" or "overdue by you".
- Choose the trip. A next step is a scouting trip the person picks for its return on effort, and they keep going until they have dug deep enough.
- Borrow structure, keep the frame your own. Outside structure helps most at the start of a task, with time estimates and with work that holds no interest. The frame itself is chosen by the person doing the work.
- Established tools over custom ones. Prefer standard products and conventions; flag drift toward building your own.
- Say "unknown". Where the evidence is thin, the SOP says so rather than filling the gap.
Jon Ash Wilson, software architect