Systems
A new gestalt
Why aim small?
The number of ways in which things work
Inputs and outputs
Taylorism
Sets and systems
Every paper cut is felt
Technology is a system
Technology is not the sum of the artifacts, of the wheels and gears, of the rails and electronic transmitters. Technology is a system. It entails far more than its individual material components. Technology involves organization, procedures, symbols, new words, equations, and, most of all, a mindset.
Notes on the Legibility War
An Article by David R. MacIverThe basic idea of legibility is that the act of making something comprehensible enough to control is itself an act that shapes the thing to be controlled, often with far greater consequences than the control itself. This is because it removes complexity that is deemed as irrelevant that makes it harder to control, and that complexity may be in some way essential to the health of the system.
Primitive design
An Article by Matt Webb- I want it to feel intuitive
- I want any new features to be platform features, not one-offs.
And the second of those is weird, right? It’s like sketching out a toy spaceship, having a list of rules about play, and attempting to simultaneously invent the shape of the Lego brick.
That’s platform design I suppose. Redesigning a newspaper will mean bouncing between comps and style guides, designing both. Inventing the iPhone user interface will have seen apps and app paradigm evolving together.
Design Systems, Agile, and Industrialization
An Article by Brad FrostI’ve come to the conclusion that “enterprise web development” is just regular web development, only stripped of any joy or creativity or autonomy. It’s plugging a bunch of smart people into the matrix and forcing them to crank out widgets and move the little cards to the right.
In these structures, people are stripped of their humanity as they’re fed into the machine. It becomes “a developer resource is needed” rather than “Oh, Samantha would be a great fit for this project.” And the effect of all this on individuals is depressing. When people’s primary motivation is to move tickets over a column, their ability to be creative or serve a higher purpose are almost completely quashed. Interaction with other humans seems to be relegated to yelling at others to tell them they’re blocked.
Reading “AS PER THE REQUIREMENTS” in tickets makes me dry heave. How did such sterile, shitty language seep into my everyday work?
When Customer Journeys Don’t Work: Arcs, Loops, & Terrain
An Article by Stephen P. AndersonThinking [in terms of loops and arcs] allows us to let go of a specific journey or sequence, and imagine dozens of scenarios and possible sequences in which these skills can be learned. This doesn’t mean there aren’t more fundamental skills that other skills build upon, but we can let go the tyranny of how, precisely, a person will move through a system. We’re free to zoom in and obsess on these loops, which does two things for us:
- Approach the design of a system as the design of these as small but significant moments of learning.
- Consider the many ways these loops might be sequenced, with the exact order being less important.
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 Art of Systems Architecting
A Book by Mark W. Maier & Eberhardt RechtinThe 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.
Design System as Style Manual With Web Characteristics
An Article by Dorian TaylorIn my opinion, what makes a designer competent is precisely their ability to credibly justify their conclusions. If you can’t do this as a designer—no matter how successful your results are—then neither I nor anybody else can tell if you aren’t just picking things at random.
What I am proposing, then, is no less than to make a designer’s entire line of reasoning a matter of permanent record. On the surface is the familiar set of prescriptions, components, examples and tutorials, like you would expect out of any such artifact. Attached to every element, though, is a little button that says You click it, and it tells you. The proximate explanation will probably not be very satisfying, so you click on the next until you get to the end, at which point you are either satisfied with the explanation, or you aren’t.
Now I get it
An Article by Ralph AmmerTo design a system means to orchestrate the interplay of its elements.
Such a system is considered “interactive” if it is open, which means that there are ways to engage with the processes that are happening inside of it. There is of course a range of interactivities which spans from very basic reactive behaviour to highly complex conversational interactions.
What Good Means
The center of the way
The advice I’ve received from those who are close to the center of this timeless way of building is to start small. Like with a piece of tile, or a tea tray. And to then imagine along with Christopher Alexander:
What it would be like
to live in a mental world
where one’s reasons
for making something
functionally
and one’s reasons
for making something
a certain shape,
or in a certain
ornamental way
are coming
from precisely
the same place
in you
.Seduction
“The classic pervasive seduction to designers is finding a solution instead of the truth.” — Richard Saul Wurman
What the material wants to be
Part of how Lou Kahn made things be good was to ask the material what it wanted to do and be. He asked brick what it liked, and would get a different answer depending on the context for the building. In Dacca, the capital of Bangladesh, brick said it liked an arch. For the Korman House in Philadelphia, brick said it liked two giant fireplaces with a lintel between them for a doorway beneath and a balcony above.
Asking yourself some questions
All of the moves that we make in space will tend toward being in accord with this phenomenon of wholeness / beauty / life if we’re willing to bring the requisite level of care to the doing of our work.
Alexander says that each of us possess the means for accessing this order within ourselves and — here’s where he loses most other architects and many in the so-called sciences in academia — he contends that what we’re connecting with inside of ourselves is an objective criterion for what good means.
Applying the criterion is easy: you ask yourself some questions:
With any action you might take with regard to placement, and with regard to the situatedness of things in space you ask yourself: does this move increase wholeness / beauty / life?
Does the intervention you’re taking intensify the feelings of wholeness in you as the maker when you are performing the work?
How does your work on this one part enhance what’s going on among wholes at the system level?
Losing meaning
The people who’ve proven that they can make very good individual products with the radical focus of a spotlight seem to be pushed ever further from making good ecosystems.
Products are being made “consistent” with the application of so-called “design patterns,” and rather than bringing coherence to these various touch-points, the painting-on of interface standards and interaction patterns did something far less valuable.
Rote consistency, in the way many seem to be going about it (Material Design being just one example), is at odds with making things be good. It simplifies what needs to remain complex.
Always, when simplification is underway, meaning is being lost.
Two coffee trays
We speculate that the shop owners designed and built an initial quantity of these remarkable coffee trays, replete with what Alexander considers to be the fifteen geometric properties that correlate with wholeness / beauty / life.
Then they got busy. And then they got successful. They needed more coffee trays, and our hypothesis is that somebody decided to simplify the trays to ensure they could be produced in the quantities and at the price that worked for their budget, within an urgent food-service timeline.
The simplified tray fulfills every function the more complex tray does, with less fuss in manufacturing on account of having standardized its geometry. The simplified tray works, but isn’t alive. It lacks the gradients, local symmetries, levels of scale, contrast, and boundaries that are all present and accounted for in the tray that’s got wholeness / beauty / life. The tray with wholeness isn’t necessarily better than the simpler one. But it is good.