Agents / Skills

Stakeholder Update

Skill

Writes the recurring update that keeps stakeholders informed and off your back: progress against what was promised, the problems stated before they are discovered, the asks made explicit — in the five minutes they will actually give it.

Best for

  • Updates that are either novels nobody reads or vagueness nobody trusts
  • Managing upward without the weekly interrogation meeting
  • Building the trust that comes from hearing bad news from you first

What you give it

  • The period's reality: progress, problems, numbers — and what was promised last time

What you get back

  • The update in the shape that works: headline state, progress against commitments, problems with owners and plans, asks with deadlines — skimmable in two minutes, complete in five
  • The bad news engineered properly: stated plainly, before discovery, with the plan attached — the format that builds credit instead of burning it
  • Continuity against last update: what was promised, what happened to it — the thread that makes updates trustworthy instead of episodic

How it works

  1. Leads with the true headline: the state in one sentence, including the uncomfortable part — readers decide in ten seconds whether to trust the rest.
  2. Reports against commitments, not activities: what was promised last time, what happened to each — the continuity thread is what separates updates from newsletters.
  3. Engineers the bad news: plainly stated, found-by-you not discovered-by-them, with the plan and the revised promise attached — the format that converts problems into credibility.
  4. Makes the asks unmissable: what you need, from whom, by when, and what delay costs — buried asks are unanswered asks.

Example

You: Write this month's board update; last month we promised the migration would finish and it did not.

Result: The update led with the honest headline (migration 80% done, two weeks late — the why in one sentence, the revised date with what changed to make it credible), not buried under three paragraphs of wins. Progress listed against last month's actual promises (the thread: four kept, one late-with-plan, nothing silently dropped), the two problems stated with owners and dates before anyone could discover them, one explicit ask (the contractor approval, needed by the 15th, with the cost of delay quantified), and the wins where they belong — present, brief, after the substance. The board meeting spent its time on the ask instead of the interrogation; two members separately noted the update's candour. That is the asset compounding.

Limits — please read

  • The update's honesty is yours; it structures candour but cannot supply it — and softened problems read as either naivety or spin when they surface later.
  • Different stakeholders may need different exposures (the board, the team, the customer) — one truth, fitted versions, never contradicting.
  • A cadence kept is half the value; the structure makes keeping it cheap.