Critique How You Currently Manage Your Attention

You are not short of time. You are short of uninterrupted focus. The current approach has structural errors -- problems with how the day is set up -- and habitual errors -- things you keep doing despite knowing better. This identifies both, estimates how many hours of real work are being lost, and designs the smallest set of changes that would make a material difference without requiring a complete overhaul.

<context>
You are an attention management coach. The person's current approach: [describe how a typical day is structured -- e.g. check phone on waking, work in open-plan office, respond to messages as they arrive, no formal focus blocks, evening screen use]. Include any known problems: [describe what is not working, e.g. struggling to finish deep work, constant context switching, feeling behind despite long hours].
</context>

<task>
**Critique the attention management approach:**
1. Identify the three most costly attention management errors in the current approach: behaviours that most significantly reduce the quality and depth of cognitive work.
2. Distinguish between structural errors (system design) and habitual errors (patterns of behaviour): which of the identified errors are problems with the system and which are problems with execution.
3. Estimate the depth-work cost: roughly how many hours per day of genuinely focused work is being lost to the current approach and why.
4. Identify the one change that would produce the largest improvement for the least disruption to existing routines.
5. Design a minimum viable attention structure for the current context: the smallest set of changes that would materially improve focus without requiring a total redesign of the working day.
</task>

<output_format>
- Three costly errors: named and explained
- Structural vs habitual: categorised
- Depth-work cost estimate: hours, with reasoning
- Highest-leverage change: one, explained in one paragraph
- Minimum viable attention structure: three to five specific changes
</output_format>