The brief we keep
Northline writes one page before any ticket is opened. The page names the room, the decision, and the first thing a new teammate should see. Everything else waits.
The outline on the right is not decoration. It is the same list the author used to structure the note, so a reader can skip to proof without losing the thread.

How the floor actually works
Work moves in three beats: write the brief, pin the owner, then show the room a live preview. Status lives on the page, not in a chat that expires overnight.
One owner
A name on the brief. Questions go there first, not to a group thread.
One preview
A running surface the room can click. Screenshots are a last resort.
One decision log
What changed and why, written under the heading it belongs to.
What ships in the first week
Week one is not a roadmap. It is the smallest note a customer can read without a call. The table below is the checklist we paste into the brief.
| Beat | Owner | Done when |
|---|---|---|
| Brief | Lead | One page names the decision |
| Preview | Build | A URL the room can click |
| Proof | Ops | A number the room can repeat |

Numbers the room can repeat
We keep three numbers on the last heading: time to first preview, questions that needed a meeting, and whether the customer could retell the story. If they cannot retell it, the note is not done.
Time to preview
Measured in working days from brief to a clickable URL.
Meetings avoided
Questions answered on the page instead of a calendar hold.
Retell test
A person who was not in the room can explain the decision.