Docs are the memory of the team
Decisions that live only in chat are lost within a week. I make Confluence the durable record, with decisions, specs and the why behind them, so nobody re-argues a settled question or onboards by osmosis.
Structure so people can find things
An unstructured wiki is a landfill. I design a space that maps to how the team thinks, with clear hierarchy, naming conventions and templates, so finding the current answer takes seconds, not a Slack archaeology dig.
One current version, not five stale ones
The enemy of a wiki is out of date pages people no longer trust. I keep a single source of truth per topic, archive the rest, and date decisions, so readers know what is live and what is history.
Write for the person who was not there
Good documentation assumes the reader missed the meeting. I write decisions with enough context to stand alone: what we chose, what we rejected, and why, so the doc answers questions instead of generating them.
Real example
Bridging Japanese and international teams, I used Confluence to keep bilingual decision records so nothing was lost in translation between a Tokyo standup and a stakeholder abroad. The wiki became the neutral ground both sides trusted.