Chat moves on. The paper keeps the record.

Paperbeam is a short company newspaper, written from the tools your teams already use and checked against them, so each team knows what the others did yesterday. This post is about the part people underrate until they need it: that it's written down, dated and kept.

The decision nobody can find

Someone in a planning meeting asks why you moved the enterprise tier's reader limit in the spring. Three people remember it differently. One is sure there was a Slack thread. Twenty minutes of scrolling later, the thread turns up. It has 140 replies, two side conversations, and a decision that was quietly reversed in a different channel a week later.

Every growing company has this meeting. The information existed. It was said, out loud or in chat. It just wasn't written, in the sense that matters: in one place, with a date, in a form someone could find and trust later.

McKinsey Global Institute estimated in 2012 that workers spend nearly 20% of the workweek looking for internal information or tracking down colleagues who can help. Industry estimates vary. The experience doesn't.

Said is not the same as written

Chat is excellent at what it's for: fast, conversational, in the moment. Those same strengths make it a poor record.

• It scrolls. Yesterday's decision is under today's lunch order.
• It's fragmented by team. The sales decision is in #deals, the product reason is in #eng, and the customer context is in a support tool.
• It has no edition. There's no moment where someone says "this is what happened today" and stands behind it.

Chat summaries help with the first problem and none of the others. A summary of #eng is still only about #eng, it's read once, and it's gone the next day.

What a record needs that a summary doesn't

A useful company record has five properties a chat summary usually lacks:

1. It's dated. You can link to the day something was decided.
2. It's cross-team. One page covers what sales, product, CS, ops and engineering each did.
3. It's checked. Every claim traces to a source you can click through to.
4. It's searchable. You can find the story, not just a keyword in a sea of messages.
5. It follows stories. Today's update knows about last month's, so the record shows how something developed, not just where it ended up.

That's a description of a newspaper. It's also, deliberately, what Paperbeam is.

Why a paper and not a wiki

Wikis are where documentation goes to age. They're written once, by whoever had time, and updated by nobody. A record that depends on someone remembering to write it will always be incomplete.

A paper is written for you, on a schedule, from the tools where the work already happens: chat, the CRM, call recorders, issue trackers, support tools. Nobody has to stop and document. The record is a side effect of the company reading its own news.

And because the whole company actually reads it, mistakes get noticed. A wiki page can sit wrong for a year without anyone opening it.

What Paperbeam keeps, and for how long

Specifics, because "archive" can mean a lot of things:

• Every published edition lives in your archive, browsable by calendar or list, with a link to each edition.
• Search works at the story level, ranked by relevance, and matches word prefixes and simple plurals.
• Every story on the web edition lists its sources and citations, so the record carries its own evidence.
• The paper remembers. It won't repeat yesterday's headlines. Open questions stay open until something answers them. "From the Archive" brings back a past story when it's relevant.
• History at setup depends on plan: 1 month on Starter, 3 on Growth, 12 on Business, and full history on Enterprise. Add-ons extend it.
• Ask the archive (a question answered from past editions, with sources) is on Business and Enterprise.
• Raw source data is kept for a window an admin sets, from 7 to 365 days. That's a setting for the underlying source items.

The new-hire test

Here's the cleanest way to see the difference between chat and a record.

A new head of CS starts on Monday. With chat, onboarding means asking six people to retell six months of decisions, each from their own team's point of view. With a paper, it means reading back through the editions: what closed and why, what was promised, what shipped, what broke, and how each of those stories developed.

Chat moves on. The paper keeps the record.

Paperbeam is 14 editions free. No card required. (Fine print: your free trial is 14 editions or 30 days, whichever comes first.)

Related: The promise CS never heard and Whose permissions does your company digest read with?.