The pressure described in this article is the pressure of the stream. Email has this problem too: there are time-sensitive discussions happening, and your brain

The pressure described in this article is the pressure of the stream. Email has this problem too: there are time-sensitive discussions happening, and your brain knows that there might be a cost to missing something. Seize opportunities to take conversations out of the stream. I do this by maintaining an internal blog that's just a Google doc linked to other Google docs. If there's an idea or a plan that is important, I summarize the Slack conversation and flesh it out in a document, then put the document in the stream. The document has its own commenting system that avoids the stream: you can discuss any point in the conversation no matter what time you're jumping in. The individual documents are discoverable because they all link back to the doc that functions as the index page for the "blog." It's a better way to think collectively. Someone should build a product around it.