> "When the team resolves a tricky incident in chat at 11pm, the explanation lives in the scrollback — until the scrollback rolls off." ^pain A collective capture pain. Important context, decisions, and fixes happen in Slack/Teams threads. Two months later, nobody can find them — and the same question gets re-asked across the channel, sometimes by the same people. ## Discovery questions - "When your team resolves a tricky incident in chat at 11pm, where does the explanation live a month later?" - "How often does the same question get answered in your team channels - twice, three times, ten times in a quarter?" ^discovery-questions ## Examples - The SEC fined multiple banks (including JPMorgan) over employees using WhatsApp and other messaging apps for business decisions without proper record-keeping.[^1] - Morgan Stanley paid a $200M penalty after regulators found firm personnel frequently used text and messaging platforms for business communications not preserved as required.[^2] - Robinhood outage investigations: regulators noted concerns that important operational and risk-related decisions had been made over chat systems and were difficult to reconstruct later.[^3] - FINRA books-and-records guidance warns firms that decisions made via Slack must be captured and supervised, highlighting risks when records live only in chat logs.[^4] [^1]: https://www.sec.gov/news/press-release/2021-262 [^2]: https://www.sec.gov/news/press-release/2022-135 [^3]: https://www.finra.org/media-center/newsreleases/2021/finra-orders-record-70-million-penalties-robinhood [^4]: https://www.finra.org/rules-guidance/key-topics/books-and-records