Publish and review
Design descriptions, review packs and the hazard picture, published to Confluence, Teams and Notion for the people who never open Dalus. And the comments, decisions and actions they leave there read back and mapped to the model, so a review leaves a trace instead of a memory.
8 workflows
Confluence design description
The architecture, published where people who never open Dalus will read it.
Confluence stakeholder review pack
A pack scoped to one decision, with numbered questions, that reads the comments back afterwards.
Confluence hazard log mirror
The hazard picture published for people outside the safety team, with implemented kept apart from verified.
Apply Notion design review decisions
What the review decided, applied on a branch. What it merely discussed, left alone.
Google Docs reviewer comments to model
Margin comments worked back into the model, each with the blast radius the reviewer could not see.
Find the decisions the model missed
The design changed in a thread on a Tuesday. The model still says the old thing.
Assess a change proposed in a Teams thread
What the thread is about to change, and who is not in it.
Pre-review agenda to a Teams channel
Three things that need a decision today, not a checklist of everything wrong.
