Chat expires; work does not
Chat is optimized for now. Search is weak, context scrolls away, newcomers cannot reconstruct why. When a thread produces a decision, a procedure, or an answer you will need twice, graduate it to a durable page and link back.
Graduation triggers
Promote chat to a doc when any is true:
- Decision with cross-person impact
- How-to used more than once
- Incident timeline worth learning from
- Spec changing while people argue in-thread
- Onboarding answer you typed twice
Otherwise leave it in chat.
How to graduate in five minutes
- Create a short page (or ticket section).
- Paste the conclusion, not the whole argument.
- Link the chat thread for archaeology.
- Replace future answers with the link.
- Name an owner for freshness.
Keep notes lean: useful work notes. Decisions: document decisions without bureaucracy.
Bad vs good habits
| Bad | Good |
|---|---|
| “It’s in Slack somewhere” | Link from the work item |
| Pasting novels into wiki | Conclusion + owners + date |
| Never updating | Revisit when process breaks |
| DMs for team knowledge | Team-visible doc |
Failure modes
Wiki landfill. Graduating everything. Use triggers.
Link rot. Docs that move with no redirects. Prefer stable paths.
Chat nostalgia. Refusing to graduate because “we’re a Slack-first culture.” Culture that cannot remember its choices is not a strategy.
Chat starts the conversation. Documents finish the institutional memory: async communication. ## Forked threads and lost context
Side DMs during channel threads create two histories. Promote once in the canonical place; link from DMs.
Example: incident thread
Example: Forty messages during outage. Postmortem due Monday.
Before closing incident channel, owner posts summary on ticket: timeline, root cause hypothesis, action items with owners.
Search finds ticket; chat archived as reference only.
Templates reduce friction
Keep a text expander or snippet: Topic / Decision / Links / Open / Thread.
Two keystrokes beat blank page syndrome.
Bots and auto-summary
Auto-summary drafts help if a human verifies decisions. Wrong summary worse than no summary.
Legal and client visibility
Some threads must become client-visible docs. Scrub internal jokes; keep facts and commitments.
Long threads without decision
If twenty messages pass without close, facilitator calls: decide, defer with date, or meeting with doc.
Wiki rot prevention
Link from code README to decision doc. Code review checks link when behavior changes.
Onboarding path
New hire doc lists five canonical homes for decisions: product, eng, ops, support, security.
Archive policy
Chat retention expires; tickets and repos persist. Promote before retention window if your tool deletes history.
Pair with document team decisions
Promotion is the habit; four-field record is the content.
Respect deep work during promotion
Promotion takes two minutes at end of debate, not constant note-taking during thinking.
Batch promote at end of overlap window.
Chat negotiates; documents remember. Build the ninety-second bridge between them or pay the archaeology tax forever. ## Design and product threads
Figma comments plus Slack debate need one promoted summary on epic with link to frame.
Example: pricing copy debate
Example: Twenty messages on headline. Marketing picks one; eng never updates app strings.
Promoted record links chosen copy and ticket for string update.
Thread closure etiquette
When promoted, react with "captured" and stop debating in chat unless new data.
Search keywords in summary
Include terms future you will grep: error code, feature flag name, client name.
Attachments in durable home
Screenshots in chat expire or scroll away; attach to ticket when decision depends on image.
Multilingual teams
Summary in working language of implementers; link translation if client-facing.
Reduce thread length proactively
At message fifteen, facilitator asks: decide now or move to doc?
Postmortem promotion
Incidents promote to ticket within twenty-four hours while memory fresh.
Promotion discipline is respect for teammates who were not in the room - or were asleep when the room was open. ## Operational summary
Name the finish line before the block ends. Write one crumb for the next session. Match task shape to energy when the day goes sideways. These boring steps compound more than any single app feature. ## Slack canvas or pin
Pin promoted link in channel during active project so newcomers find canonical record.
Example: design approval
Example: Design approves in thread. PM copies approval into ticket with screenshot link before eng starts.
Thread length alerts
Bot or norm at twenty messages: promote or schedule decision doc.
Durable != long
Durable means findable and accurate. One paragraph beats five pages.
Cross-tool promotion
Chat decision promoted to Jira comment and linked from GitHub issue when work spans tools.
Training in onboarding
First week exercise: find decision on ticket from last month without asking human.
Promotion is hygiene like commit messages - skip it and pay interest forever.
Thread types that always promote
Incidents, pricing decisions, scope cuts, security exceptions, and customer commitments should promote every time - no judgment call.
Example: customer promise in chat
Example: Support promises refund policy exception in thread. Without promotion, finance and engineering never know. Promote to ticket with customer id and approver name.
Editing promoted records
When decision changes, edit with Updated line rather than new orphan thread.
Search and titles
Title promoted summary with words people will grep: error code, client name, feature flag.
Attachments and screenshots
Put screenshots on ticket or doc; chat images scroll away.
Training facilitators
Long threads need someone to call "promote or decide" at message twenty - not optional nicety.
Reducing thread length upfront
Post options doc early instead of debating forty messages in chat.
Compliance retention
Know chat retention policy; promote before expiry if your tool deletes history. ## Operational summary for the week
Pick one finish line per day that matches the energy you actually have, not the energy you post about. Write one crumb for the next session before you close the laptop. When the day fragments, name the type of work you are doing so guilt does not invent a story about failure. These steps look boring in a blog post; they are what make next Tuesday start without a twenty-minute reopening tax.
Remote work removes the commute edge and the office cue that someone else saw you stop. That means the habits in this article are not productivity decoration - they are how you keep evenings and mornings from blending into one long partial-attention shift. If you only adopt one change, adopt the smallest honest version on your worst day, not the heroic version on your best day.
Keep the habit smaller than your worst week
When travel, illness, or client fires hit, the version of this practice that survives is the one you can do in ten minutes or less. Protect that version on good days so it is automatic on bad days. Finishes matter more than ritual completeness.
Write one sentence before you stop: what finished, what is next, what is blocked. That sentence is enough context for tomorrow when you cannot face a full shutdown checklist.