A weekly update can list everything a team did and still leave its reader unsure what to do next.
Try a smaller format: one outcome, the evidence for it, one unresolved problem, and the decision needed.
Here is a fictional input:
We processed 18 requests this week. Four remain open. Two are waiting for a specification from the customer; two need an internal review. We could clear the internal reviews if someone is available Tuesday, but nobody has been assigned.
“The team is making great progress” would be an interpretation. “All remaining requests will close Tuesday” would be an invention.
A useful draft might say:
Status: 18 requests processed; four remain open.
Blockers: Two await customer specifications. Two await internal review.
Decision needed: Assign a reviewer and confirm whether Tuesday is feasible.
Try this prompt:
Draft a weekly update from the facts below. Use four labels: status, evidence, blocker, decision needed. Keep observations separate from interpretations. Do not infer a trend from a single period. Do not invent an owner, deadline, cause, or forecast. End with one clear request, marked as proposed if it was not already agreed.
Then do a quick review. Do the figures refer to the same period? Does “processed” mean completed, touched, or received? If the source doesn’t say, resolve that definition before treating the update as a performance comparison.
Keep the update short enough that its reader can find the request. Background belongs underneath the decision, where someone can inspect it if necessary.
The measure of a useful update is whether it helps the next person act with the right information. A longer summary isn’t automatically more useful.
This week, take one existing update and underline its actual request. If you can’t find it, start there.