Article 011: Working from a phone is a clue, not a goal
Key Message: Mobile work reveals what must stay central. If it works on a phone, it’s probably supervisory.
Series: B — Reframing the work (Part 6 of 6) Publish Date: Monday 2026-03-30
Story Outline
Opening hook
The pride of approving a PR from a phone, checking a build status while away from the desk. It feels like progress — a loosening of the tether between software work and a specific physical setup. But mobile work is more interesting as a diagnostic than as an achievement.
What a phone allows
Walk through concrete examples of phone-friendly work: approving deployments, reviewing short PRs, checking agent run status, sense-checking a spec. All real work, but all supervisory in character — evaluating artifacts produced by other processes. The phone isn’t a constraint because the work doesn’t require more than what a phone provides.
What a phone won’t allow
The other side: debugging concurrency issues, designing system architecture, exploratory coding. These aren’t just inconveniences solvable with better apps. Debugging needs full context and the ability to trace state across files. Architecture needs many constraints held in view simultaneously. Exploratory coding needs fast iteration and full visibility. The phone constrains not just the screen but the working memory available.
The diagnostic value
The two sides together form a useful question: if I imagine doing this from a phone, does it feel plausible? If yes, the work is probably supervisory. This matters because the ratio of supervisory to execution work is shifting as agents handle more implementation. The phone test is a way of noticing where you’re the decision-maker versus the implementer.
Not a goal, but a signal
Resist the distorted version: maximising phone-accessible work as a productivity measure. That path leads to a fully supervisory role that erodes the execution experience supervision depends on. The judgment for good supervision draws on a reservoir of execution experience. That reservoir drains if never replenished.
Where the centre still sits (Close)
Final article of Phase B. The shift toward supervision and asynchronous work is real, but it doesn’t dissolve the centre — it moves it. What must stay central is the capacity to engage with execution work when it matters. The work revealed by what can’t move to the phone is what still requires full context, full engagement. Distribution of work across time and device is the direction, but the unevenness is informative.
Notes
- Closes Phase B of the series
- Central diagnostic: “if it works on a phone, it’s probably supervisory” — practical test for the supervision/execution distinction developed across the phase
- “Reservoir” metaphor: supervisory capacity depends on execution experience, drains if execution disappears
- Key tensions: phone work is real work but reveals nature; supervisory growth is genuine shift not just flexibility; maintaining execution isn’t nostalgia
- Final section ties Phase B arc together — the shift is real but the centre doesn’t dissolve, it moves