Stakeholder Artifacts: A Status Page You Don't Have to Update

You build the status page you've always wanted. A clean dashboard in Cowork (this week's milestones, the two slipping deliverables, the open risks, the pipeline number your boss keeps asking about) pulled straight from your tracker and calendar.

Friday afternoon you send the link to your steering committee and quietly retire the weekly update email forever.

Monday, someone asks why the numbers look like last week's. The page they opened is not the page you see. Yours refreshes when you open it; theirs froze the moment you hit share.

Cowork did exactly what you asked. You handed one object two jobs it doesn't yet do at once. "A status page you don't have to update" is real and worth building; it just has two halves, and the trick is knowing which is which.

#Two artifacts wearing the same name

An earlier article in this series drew the line between a reply and an artifact. A second line, inside artifacts, trips people up here.