Status updates that actually get read

If your stakeholders are skimming (or ignoring) your status reports, the problem isn't their attention span. It's your format.

Most status reports are written for the author, not the reader. They're detailed, chronological, and comprehensive - everything a busy stakeholder doesn't want.

Reverse the structure. Lead with the one thing the reader cares about most: is the project on track? If yes, a paragraph and a link is plenty. If no, say what's wrong, what you're doing about it, and what you need from them - in that order.

The RAG (Red/Amber/Green) status is useful only if it changes behaviour. A project that's been 'Amber' for four months with no escalation isn't amber - it's green with bad reporting. Signal early, flag when you need a decision, and keep the rest short.