Write It Once: How to Build Visibility & Alignment Through Writing
What is the first thing you do after making an architecture decision or running a new type of meeting?
Most teams do something new, learn a few things in the moment, and then move on.
The problem is that the learning does not stick. Two weeks later, you are back to, "Why did we pick this?" A month later, someone new shows up and needs the backstory. The work turns into folklore.
This week, I helped lead a conversation with a partner organization tied to our AI initiative. We got to a clear direction, and I did not want that direction to fade into "I think we said…" the next time the topic came up.
So I wrote it down, put it somewhere findable, and shared it.
That step pays off in two directions. It gives the team a reference point they can reuse, and it forces you to synthesize what happened so you understand it at a deeper level. That's the same principle behind "show your work." People give better feedback when you give them something concrete to react to.
How Writing Adds Value
Writing earns its keep when it reduces future meetings, future confusion, and future rework.
For others, writing:
- Prevents the re-explain loop. People do not need to pull you into a meeting to reconstruct context.
- Stops parallel interpretations. When the decision and the reasoning are explicit, teams are less likely to execute different versions of the plan.
- Makes follow-ups smaller. The next conversation becomes "I read it, here's the one question," instead of "Can you recap?"
- Creates continuity through change. Priorities shift. People rotate. A written trail preserves the intent.
If you have ever watched a team burn hours on follow-ups that exist only because context was missing, you have seen this cost in real life.
For you, writing:
- Forces synthesis. You turn a messy conversation into a clear story with a through-line.
- Exposes gaps while they're still cheap. Writing makes it obvious when a "decision" is still fuzzy, or when success criteria are missing.
- Builds reusable judgment. You are not only solving the problem. You are capturing how you reasoned through it.
- Creates durable visibility. The work speaks for itself because it is legible and shareable.
This is also why some organizations lean hard into narrative writing for decisions. Amazon's six-page memo culture is built around the idea that precise writing improves thinking and decision quality.
What to focus on when you write
A good write-up is not a transcript. It is a short narrative that preserves the parts people forget first, or argue about later.
When you write, focus your words here.
- Purpose
This is the anchor. Without it, people drift into debating solutions without agreeing on the problem.
- What changed
A decision. A boundary. A constraint. An agreement. If the change is not clear, the write-up becomes history instead of direction.
- Why this path won
This is where alignment lives. Constraints, tradeoffs, and the reasoning that made the decision make sense at the time. When you skip this, readers fill in the blanks with their own assumptions.
- What you ruled out
Name the alternative you did not choose and why. This is what prevents the same debate from restarting when a new stakeholder arrives.
- Next step and ownership
Writing should move work forward. If the next step is unclear or unowned, the artifact will not change anything.
If you want a formal version of this in Confluence, Atlassian's decision templates and decision logs exist for a reason. They push teams toward clarity about who is driving, approving, and informed.
In software, the ADR pattern does the same thing: captures the decision and rationale so future readers can understand why a particular decision was made.
|
|
Where can AI save you time?
My friends at Big Creek Growth put together a quick survey to spot the repetitive work you can hand off to automation.
|
|
From Updates to Durable Artifacts
Most people write as if they were posting an update. It sounds professional, but it does not hold up over time.
Here's the difference.
Typical Write-Up
Met with partner org today and had a good discussion. We aligned on next steps and will move forward with the approach we talked through. I'll follow up with additional details.
Reusable Write-Up
Met with partner org to shape a potential engagement tied to our AI initiative. The goal was to define success criteria, name the constraints we need to respect, and outline a pilot we can validate quickly (details referenced below).
We chose a narrow pilot focused on a small set of outcomes and ruled out an end-to-end engagement right now because the scope is too wide to measure cleanly.
The next step is documenting the pilot scope and decision points, and sharing them for feedback before committing to timelines.
The first write-up tells you something happened.
The second write-up preserves the purpose, the decision, the reasoning, the option you avoided, and the next step. It also points to the deeper detail that makes a 6-minute Confluence page feel worth reading. You are not asking someone to remember the meeting. You are giving them a clean way to understand it.
This is the same communication skill behind "landing the plane." Clear communication starts with a core message and ends with a usable conclusion.
If you want the benefits of doing something new more than once, you have to capture what made it work.
Write the artifact. Put it somewhere searchable. Share it with enough context that a reader understands why it matters.
The goal is not to write more. The goal is to make the work easier to repeat, easier to build on, and harder to misunderstand.