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.
On my first day I literally walk across the city, to the extent it can be done…The next day I do another cross town walk, but in a different direction, filling in the blanks from the prior day’s walk.
Then, over the next week(s), I walk between 10 to 20 miles per day, picking and choosing from what I have seen before, highlighting what I like, what I want to know more about, refining the path, till by the end of my trip, I have a daily route that is roughly the same.
While that is certainly not the most efficient way to see a city, it is the most pleasant, insightful, and human. I don’t think you can know a place unless you walk it, because it isn’t about distance, but about content.