Why do decisions end up in direct messages, and what should you copy out?

A decision ends up in a direct message because that room is small, fast, and has no filing cost. Two people can say yes without inviting anyone who might object, and without naming an object the rest of the company can open. Private conversation is often appropriate. The outcome still needs a home the next team can find.

This guide traces one pricing exception from a DM to an invoice, then offers a habit that keeps the private talk. You do not have to ban DMs. You do need a rule for what may not live only there. The Problems hub is the wider series; search is not memory is the general case. A DM is the same idea with a smaller room and a worse search.

Why do decisions end up in direct messages?

They go to the smallest available room. That room holds nobody who can object in public, and no duty to write the result into a system. Policy decks say exceptions go to a manager. The DM is open now. The slide is not.

Speed is the other reason. Typing “ok go 12” is faster than opening the quote. Asana’s Anatomy of Work Index (2022), a survey of more than 10,000 knowledge workers, found that 58% of the day went to work about work — coordinating, searching, chasing status. Chasing “did we agree 12 or 8” is that 58%, paid by people who were not in the DM.

People also use DMs because the topic is sensitive: a person, a customer complaint, a number that should not sit in #general. That instinct can be right. The mistake is treating privacy of the conversation as privacy of the outcome. Finance still has to invoice. The next seller still has to explain the margin.

AI makes the small room feel more complete. A model can draft the customer email from the DM. The guess gets a better tone, not a field. A fluent paragraph in the same window is still a second unofficial copy.

What goes wrong when the only yes is in a DM?

Tuesday, 16:12. A seller and a customer-success manager are in a Slack DM. The customer has asked for 12% off SKU A-440 on quote Q-8841, sterling, for a renewal that invoices on the first of next month. The rate card says 8%.

The seller types: “ok go 12, I’ll sort it.” The CSM replies with a thumbs-up. No one opens the quote. No one names the currency again. No one says whether 12% stacks with the existing rebate.

That message is the whole decision. It has a time from Slack’s clock, two display names, and a number. It has no object ids the billing system uses, no signer whose role owns exceptions, and no place finance is allowed to see.

The seller means to update Salesforce after the next call. The call overruns. A new thread starts about another account. On Wednesday the customer thanks them “for the 12” on an older email — a second unofficial copy, still not a field.

Finance never saw it. The sales manager never saw it; exceptions above 10% were supposed to go to her. Legal never saw it; twelve percent stacked with a rebate may breach another clause. Operations will pick the order against the list price. The next seller, when the first one leaves in six weeks, will not know to search for “A-440” in someone else’s private history. collaborative AI for legal and compliance review often starts here: one team has a memory, the other has a system, and both are sincere.

On the first of the month the billing job reads Salesforce. The opportunity still has 8%. The invoice prints 8%. The customer refuses it. A credit note is raised for the difference, reason code “goodwill.” Two versions of the truth are now in official systems: the invoice at 8, the credit at the gap to 12, and a CRM that still says 8. The company funded a discount it cannot point to.

Six months later a new finance manager asks why margin does not match the rate card. She has no access to the original DMs. Slack retention on DMs was 90 days. Reconstruction becomes interviews. Votes are not controls.

Rule 37(e) is the US civil procedure test many counsel already know: if electronically stored information that should have been preserved is gone, a court can sanction the failure. A pricing exception that changed revenue is the kind of thing a later dispute asks for. Sarbanes-Oxley (2002) does not mention Slack. For companies that file with the US Securities and Exchange Commission, it does require a control trail for how a number became the number. “We think Sarah said 12” is not that trail.

A wider room is not automatically the fix. Ban business DMs, open a #decisions channel, buy DM capture so compliance holds everything: an archived DM still may have no object id, no signer role, and no field. The exception did not always need a bigger audience. It needed one authorising record.

How do you keep private conversation without losing the outcome?

Keep the DM for “can you join at 3,” for a sensitive personnel note, for colour the customer should not see in a channel. Stop closing money only in that window.

One approach is a same-day rule: any change to price, credit, date, or scope that another team will be measured on gets written into the object that team uses, the same day, with a named signer. One sentence, usable in a sales meeting, and it requires nobody to read private chat.

Practical catches that respect privacy:

• Invoicing rejects a discount that is not on the quote.
• CRM requires a reason code and an approver on overrides above a threshold.
• The job that proposes the exception is visible to finance before the invoice runs.
• Fail-closed on the write: if nobody approves, nothing happens. The field stays at 8 until a signer moves it.

Sellers can keep DMs. The company can refuse to invoice from them. You cannot police a customer’s WhatsApp. You can refuse to treat it as the quote.

What should you copy out of a DM?

Copy the outcome, not the chat. Four lines are enough:

1. The decision, with object names the systems use (SKU, quote id, currency, percent).
2. Who was allowed to make it.
3. Who signed, with a timestamp from the system, not from memory.
4. Where a stranger would find it in six months.

Do not copy the jokes, the back-and-forth, or “I’ll sort it.” Do not paste the whole DM into a channel “for visibility.” Visibility is a link to the object.

If AI drafted the customer email from the DM, say so on the record, and send the email from the quote, not from the paste. Write-back — when AI changes a live system — should wait for the signer. The model may draft. It may not land from a private window.

Search is not memory is why “we can always find the DM” fails: private history, retention sliders, and the next owner’s missing access. What an AI workstream is is one named place those four lines can live.

How do you start with one recurring decision?

Ask accounts receivable for the last three credit notes marked goodwill and try to find the authorisation without talking to the seller. The ones you cannot find are your DM problem, already in cash.

Then pick one recurring class — pricing exceptions, ship-date changes, credit notes — and apply the same-day rule to the next instance only. Keep every other DM as it is.

If you want the chain in product form, governance is one place to hold who may approve a write. You can start this week with the quote object and a named signer. Private rooms will stay useful. What changes is that the decisions that leave those rooms have a home that is not an interview.