#Notion organization software#

What details need documented differs by solution, but a rule of thumb is to anticipate and satisfy the most common needs your end-users and future solution providers will have before they need to use, maintain, build, or improve the solution. There are meaningful aspects of it that have stabilized and need to be captured as documentation. However, when a solution is delivered and ready to be used by its target end-users, the solution is no longer a speculative idea.

With collaborative context being scattered across many different tools and synchronous Zoom meetings with no paper trail, this information is simply too noisy and incomplete to parse through in pursuit of any reliable knowledge of your organization’s current state-of-the-art. This collaborative context can be useful to understand how a solution got to its current state, but it isn’t a source of truth for the current state itself.

#Notion organization software#

Though, I appreciate the “why” and see a lot of value in using Notion for collaboration or to fill software need gaps in a pinch, I believe Notion spreads a poison that can lead to an organization’s death spiral.Īs members of your organization collaborate using a mashup of Microsoft Office, G Suite, Slack, Email, meeting notes, etc., collaborative context is generated leading up to the delivery of a solution to a problem faced by team members internally or by customers externally. Put simply, Notion wants you to make Notion what you want it to be.

This can be interpreted as, Notion believes software should be customizable enough to meet the needs of anyone, and their aim is to be the ultimate malleable software used for toolmaking. We want everyone everywhere to feel empowered to customize the software they use every day to their exact needs. Our mission is to make toolmaking ubiquitous.