hierarchy
Excursus: Homage to the Square^3
The problem with trees
Many systems are organized hierarchically. The CERNDOC documentation system is an example, as is the Unix file system, and the VMS/HELP system. A tree has the practical advantage of giving every node a unique name. However, it does not allow the system to model the real world. For example, in a hierarchical HELP system such as VMS/HELP, one often gets to a lead on a tree such as:
HELP COMPILER SOURCE_FORMAT PRAGMAS DEFAULTS
only to find a reference to another leaf: Please see
HELP COMPILER COMMAND OPTIONS DEFAULTS PRAGMAS
and it is necessary to leave the system and re-enter it. What was needed was a link from one node to another, because in this case the information was not naturally organized into a tree.
The brilliance of notion
This, I think, is the brilliance of Notion, and what makes it one of the best examples of “fidelity to digital information” that I’ve come across. The structure of the app reflects the structure of the web itself: digital content is purposefully formatted, like semantic HTML elements, and exists in a hierarchical structure (directories on the web, nested pages in Notion), yet can be linked and referenced to create a complex network of information. And pages in Notion reveal the structure of the information: when nesting a page within a page, the child page always displays on the parent page. There’s no way to create a child page that doesn’t display on a parent page, no way to obscure the structure of the information. The semantic structure of Notion reflects the semantic structure of the web itself.
Separation and connection in all things
Truchet's approach was more topological than geometric, and the qualitative aspects of pattern take priority over the metric ones. His principles provide a kind of metaphor for the hierarchy of separation and connection in all things.
Dear Microsoft
We realized a few years ago that the value of switching to Slack was so obvious and the advantages so overwhelming that every business would be using Slack, or “something just like it,” within the decade. It’s validating to see you’ve come around to the same way of thinking. And even though — being honest here — it’s a little scary, we know it will bring a better future forward faster.
However, all this is harder than it looks. So, as you set out to build “something just like it,” we want to give you some friendly advice.
It's not the features that matter
First, and most importantly, it’s not the features that matter. You’re not going to create something people really love by making a big list of Slack’s features and simply checking those boxes. The revolution that has led to millions of people flocking to Slack has been, and continues to be, driven by something much deeper.
Building a product that allows for significant improvements in how people communicate requires a degree of thoughtfulness and craftsmanship that is not common in the development of enterprise software. How far you go in helping companies truly transform to take advantage of this shift in working is even more important than the individual software features you are duplicating.
An open platform is essential
Second, an open platform is essential. Communication is just one part of what humans do on the job. The modern knowledge worker relies on dozens of different products for their daily work, and that number is constantly expanding. These critical business processes and workflows demand the best tools, regardless of vendor.
You've got to do this with love
Third, you’ve got to do this with love. You’ll need to take a radically different approach to supporting and partnering with customers to help them adjust to new and better ways of working.