Ethan Marcotte
Stress systems
An Article by Ethan MarcotteThe [Lake Erie] ecosystem underwent a series of changes, each of which were related. There was an increase in the human population; which led to higher phosophorus levels in the water; which led, at last, to an increased level of algae in the lake. In effect, Lake Erie’s ecosystem was rewritten. Changed by human activities into…something else.
But Franklin cites the study because it’s doing something slightly novel: applying Selye’s principle of stress to ecological systems, suggesting that they are, much like humans, just as susceptible to external stressors. And I’ve been thinking about that a lot lately, especially this week. Because Franklin’s suggesting that the work begins not by “fixing the system.” Rather, she suggests it’s about shifting the priority a little: to removing whatever stress you can.
The design systems between us
A Talk by Ethan MarcotteIn the early days, design systems promised us more consistent interfaces, more collaborative teams, and improved shipping times. While they’ve certainly delivered on some of those fronts, they’ve introduced new challenges too. Let’s talk through what’s working well—and what could be working better—as we take a closer look at the systems between us and our work.
Web Brutalism, seamfulness, and notion
How a tool for sensemaking reconciles two distinct software design ideologies.
- Seamful vs. seamless
- Reveling in infrastructure
- The brilliance of notion
- How our understanding is working
Seamful vs. seamless
At the core of the Brutalist ethos is a tension between two philosophies that have been the topic of a long-standing debate in information design: the merits of “seamless” and “seamful” design, “seams” in this context taken to mean revelations of an object’s inner workings.
Designers typically take seamlessness as the de facto standard for our work, emphasizing clarity, consistency, simplicity, efficiency, reducing cognitive load. We seek to minimize distractions.
Yet what if we can achieve a clearer understanding by intentionally revealing how a system works?
Reveling in infrastructure
Hunstanton Secondary School (1954) in Norfolk, England, designed by Alison and Peter Smithson. Photo by Anna Armstrong (2011)
When the Smithsons placed the water heater for the Hunstanton Secondary School prominently above the school’s roofline, they weren’t just revealing the building’s infrastructure, they were reveling in it. What does it look like to do this on the web?
Of course there’s no single answer, because the web is simultaneously a physical and digital medium. It is material and it isn’t. It depends on how literally you interpret the question. But taking it somewhere in-between, seeing the web as primarily an information medium, we can ask the question a little differently: what does it look like to design something that is true to the material of digital information?
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.
How our understanding is working
The concept of seamfulness prompts designers to ask how an object can aid understanding and usage by showing its users what’s going on inside. How can we create what Mark Weiser, later revising his ideas of seamless design, calls “beautiful seams” — thoughtfully-crafted moments of revelation? Notion doesn’t show us how it’s literally working — the background processes constantly running to enable editing, collaboration, and the like. We don’t need to see our car’s engine to know it’s running. But it shows users how their understanding is working, how our ideas are structured, connected, and evolving.