Clean-room: private working surface vs shareable view

Your command center is a private working surface. It carries the raw material of how you operate: blunt notes, priority scores, half-formed drafts, internal labels, the names of whatever systems and helpers produce your work. None of that is meant for teammates, a boss, clients, partners, or an audience.

The moment any slice of the surface is shown to someone else, it has to be a clean-room view: the same underlying facts, with every private working artefact stripped. Building this separation in from the start is far cheaper than retrofitting it the first time someone asks to see your board.

What is private and never travels

• Raw scores and rankings. Your internal 1-to-10 on an item, your "why this is deprioritised" note.
• Blunt working notes. The candid version of why a deal is stuck or a person went quiet.
• Process detail. How the work got made - the tools, steps, or helpers involved - is noise to the recipient, who needs the outcome and its status, not a narration of the process. Describe work by what it is and where it stands, not by how it was produced.
• Unapproved drafts. Anything not yet cleared to be seen.
• Anything about people that you would not say to their face or in front of them.

What a shareable view shows instead

The same work, described by outcome and status in plain language:

• "Draft ready for review", not "second editing pass done, score 7/10".
• "Waiting on client", not your private note about why the client is difficult.
• Functional owner labels, not internal code names.
• Committed and in-flight work, not your raw backlog and scores.

How to build the split

1. Tag every field as private or shareable when you design the lane, not later. A field with no tag defaults to private.
2. Generate the shareable view from the private one by suppression, never by hand-copying. Hand-copying drifts and leaks.
3. Make the shareable view a distinct surface - a separate page or export - so there is no way to accidentally show the private one by turning your screen around.
4. Review the shareable view once as if you were the recipient. If a single line would embarrass you or expose how the sausage is made, it is mistagged.

Why this matters more than it looks

Two failure modes this prevents. The obvious one: a raw note or a candid score reaches the person it was about. The quieter one: process detail clutters a view that should be about outcomes - the recipient gets a narration of how the work was made instead of the decision or status they came for. A shareable view describes work by outcome and status, which is what the recipient can actually use.