The artifact should carry the work

A good artifact makes the next decision easier. It opens with the conclusion, keeps evidence close to the claim, and gives the reviewer a clear next move.

Recommendation

Treat every artifact as a small working document, not a miniature dashboard.

  • Start with the decision.
  • Keep supporting context close to the claim.
  • End with a clear owner and next step.

Chat should point to the work. The artifact should hold it.

Working plan

StepOwnerState
Shape the draftAgentComplete
Review the substanceRichIn progress
Share the outcomeTeamNext

Notes

Links open in a new tab, inline code stays readable, and longer technical material can sit in its own block:

Owner: Rich
State: Draft
Next: Review the visual hierarchy

Open questions

  1. Does the hierarchy make the conclusion obvious?
  2. Is the page comfortable to read on a phone?
  3. What should feel quieter—or disappear entirely?