The [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.
In 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.
That’s the primary difference between an axiom like “Curiosity Killed The Cat” and an axiom like “You Are Not Your User. ” The former rings true in common experience. It’s test-able, like striking a tuning fork or dangling a bit of yarn in front of a kitten. The latter is just some stuff that somebody said.
Sometimes, axiomatic sayings like “You Are Not Your User” no longer have a who that’s saying them. They cease being an actual instruction, and instead serve as a kind of identity, to identify the person who’s repeating the axiom as One Of Us.
The technical term for when an axiom devolves into an ID card is shibboleth: a custom, principle, or belief distinguishing a particular class or group of people, especially a long-standing one regarded as outmoded or no longer important.