To do some more pushups on the internet There may be a lot of things that have to be studied, but there is also what I call "occupational therapy for the opposition" that says, send them off to do some more pushups on the internet. You need to be mindful that it is possible to use information, and the need for information, as a delay for the call for action. Ursula M. Franklin, Every Tool Shapes the Task informationethicswwwjustice
Good design is practical design In the context of web design, Dieter Rams’ principle is not only a resounding criticism against mindless trends and meaningless decorations. It is a humanist reminder to put material honesty and social responsibility above the pursuit of the “pixel perfect” design. Chuánqí Sun, A case against "pixel perfect" design Dieter Rams: As Little Design as Possible fashionethics
An ethics of mutual care Foregrounding maintenance and repair as an aspect of technological work invites not only new functional but also moral relations to the world of technology. It references what is in fact a very old but routinely forgotten relationship of humans to things in the world: namely, an ethics of mutual care and responsibility. Steven J. Jackson, Rethinking Repair ethicshumanitymoralitytechnology
The mirror test In the early years of this century, the most highly respected diplomat of all the great powers was the german ambassador in London. He was clearly destined for great things...yet in 1906 he abruptly resigned rather than preside over a dinner given by the diplomatic corps for Edward VII. The king was a notorious womanizer and made it clear what kind of dinner he wanted. The ambassador is reported to have said, "I refuse to see a pimp in the mirror in the morning when I shave." This is the mirror test. Ethics requires that you ask yourself, What kind of person do I want to see in the mirror in the morning? Peter F. Drucker, Managing Oneself ethicsvalues
An equivalence In both early Christianity and Islam, theologians made a claim about architecture likely to sound so peculiar to modern ears as to be worth of sustained examination: they proposed that beautiful buildings had the power to improve us morally and spiritually. They believed that, rather than corrupting us, rather than being an idle indulgence for the decadent, exquisite surroundings could edge us towards perfection. A beautiful building could reinforce our resolve to be good. Behind this distinctive claim lay another astonishing belief: that of an equivalence between the visual and ethical realms. Alain de Botton, The Architecture of Happiness ethicsaestheticsgoodness
An objective matter We have been taught that there is no objective difference between good buildings and bad, good towns and bad. The fact is that the difference between a good building and a bad building, between a good town and a bad town, is an objective matter. It is the difference between health and sickness, wholeness and divided ness, self-maintenance and self-destruction. In a world which is healthy, whole, alive, and self-maintaining, people themselves can be alive and self-creating. In a world which is unwholesome and self-destroying, people cannot be alive: they will inevitably themselves be self-destroying, and miserable. Christopher Alexander, The Timeless Way of Building ethics
If you run a website If you run a website and you put official share buttons on your website, use intrusive analytics platforms, serve ads through a third-party ad network or use pervasive cookies to share and sell data on your users, you're contributing to a user-hostile web. You're using free and open-source tools created by thousands of collaborators around the world, over an open web and in the spirit of sharing, to subvert users. Parimal Satyal, Against an Increasingly User-Hostile Web wwwethics
What to refuse to do, even for the money. Michael Sorkin, Two Hundred Fifty Things an Architect Should Know ethicsdesign
Undoing the Toxic Dogmatism of Digital Design An Essay by Lisa Angela lisa-angela-fftv.medium.com Design educators and industry leaders have never reached a consensus about what comprises a “good enough” foundational education for digital design. We do not properly retire methods (or ways of conducting them) that have been shown to be ineffective. Design team seniority levels are meaningless. We’ve collectively lost the safety (and subsequently the desire) to explore and fail. We afford well-known design leaders too much power to dictate how design is discussed and conducted. We have no ethical standards. Inclusive design and accessibility are afterthoughts — both in design education and in practice. Design Discourse is in a State of Arrested DevelopmentWaking up from the dream of UXSermon for WIAD Bristol 2021On Design Thinking ethicsuxsoftware
Learning About Work Ethic From My High School Driving Instructor An Essay by James Somers www.theatlantic.com Should we really demand that the guy who checks ticket stubs at the movie theater hones his craft? Well, yes. No job is too low to not warrant care, because no job exists in isolation. Carelessness ripples. It adds friction to the working of the world. To phone it in or run out the clock, regardless of how alone and impotent you might feel in your work, is to commit an especially tragic—for being so preventable—brand of public sin. Bob [the driving instructor] oozes concern; he wants to infect the state of New Jersey with good driving habits. He respects his public role, the fact that the minute he's done with these kids they head straight for their parents' car keys and out onto the roads we share. When I asked him what he likes to do outside of work, he laughed: "This is my life." His reward is the pleasure of depth itself. craftworkethics
The Questions Concerning Technology An Essay by L.M. Sarcasas theconvivialsociety.substack.com What sort of person will the use of this technology make of me? What will the use of this technology encourage me to notice? Does the use of this technology bring me joy? What limits does the use of this technology impose upon me? Upon what systems, technical or human, does my use of this technology depend? Are these systems just? technologyethicscollections
A Mindful Mobile OS An Article by Clo S. thistooshallgrow.com I read and loved Potential's "iOS 15, Humane" proposition. Published earlier in June by co-founders Welf and Oliver, it tackles how iOS could help us better protect our attention. As a designer who cares about and writes about digital wellness, I'm profoundly aligned with their suggestions. Persuasive design Disclosure requirement From infinite feeds to pages Was this time well spent? Regret tax Conditions of use moralityethicsuxsoftwaredesign
Weighing up UX An Article by Jeremy Keith adactio.com Metrics come up when we’re talking about A/B testing, growth design, and all of the practices that help designers get their seat at the table (to use the well-worn cliché). But while metrics are very useful for measuring design’s benefit to the business, they’re not really cut out for measuring user experience. Two levels of vetoOur obedience to the king metricsuxbusinessresearchethics
The Design of Design A Book by Frederick P. Brooks, Jr. www.goodreads.com Design process models: A summary argumentThe spiral modelA grossly obese set of requirementsRequirements proliferationThe architectural contracting model+9 More Design System as Style Manual With Web Characteristics designsoftwarearchitecturemakingstyle
What's Wrong With This Model? A Chapter What's wrong with the rational modelDeciding what to designEvaluating goodnessChanging constraintsThey just don't work that way+1 More
Design process models: A summary argument A formal design process model is needed, to help organize design work, to aid communication in and about projects, and for teaching. Having a visual, geometric representation of a design process model is crucial, for designers are spatial thinkers. They will most easily learn, think about, share, and talk in terms of a model with a clear geometric picture. The Rational Model of design occurs naturally to engineers. The linear, step-by-step Rational Model is highly misleading. It does not reflect what real designers do, or what the best design thinkers identify as the essence of the design process. The bad model matters. It has led to the too-early binding of requirements, leading in turn to bloated products and schedule/budget/performance disasters. The Rational Model has persisted in practice despite its inadequacies and plenty of cogent critiques. This is because of its seductive logical simplicity, and because builders and clients needs “contracts." Several alternative models have been proposed. I find Boehm’s Spiral Model the most promising. We need to keep developing it.
The spiral model The spiral shape certainly suggests progress. It associates successive repetitions of the same activity. The geometric shape is easily understood and memorable. The model emphasizes prototyping, starting with user-interface prototypes and user testing long before an operational prototype is possible. Since a development model is principally used by developers, I believe having it designer-centered is entirely appropriate. With Boehm and against Denning and Dragon, I advocate frequent but not continuous interaction with representative users, with successive prototypes as the vehicles. I strongly believe that way forward is to embrace and develop the Spiral Model. design
A grossly obese set of requirements Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun. The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing. Requirements proliferationA Plea for Lean Software features
Requirements proliferation Any attempt to formulate all possible requirements at the start of a project will fail and would cause considerable delays. — Pahl and Beitz, Engineering Design As Project Manager, I had to reject the requirements document as totally impractical, and have a quite small team of architects, marketers, and implementers extract the essence. Requirements proliferation must be fought, by both birth control and infanticide. YagniA grossly obese set of requirementsFeatures and complexity features
The architectural contracting model It is the necessity for contracts, whether within an organization or between organizations, that forces the too-early binding of goals, requirements, constraints. The pressure for a complete and agreed-upon set of requirements run into the hard fact, that it is essentially impossible to specify any complete and accurate set of requirements for any complex system except in iterative interaction with the design process. How have the centuries-old building design disciplines handled this perplexity? Fundamentally, by a quite different contracting model. The client develops a program, not a specification, for the building. He contracts with an architect, usually on an hourly or percentage basis, for services, not for a specified product. The architect elicits from the client, the users, and other stakeholders a more complete program, which does not pretend to be a rigid contractable product specification. The architect does a conceptual design that approximates the reconciliation of program and the constraints of budget, schedule, and code. This serves as a first prototype, to be conceptually tested by the stakeholders. After iteration, the architect performs design development, often producing more detailed drawings, a 3-D scale model, mockups, and so on. After stakeholder iteration, the architect produces construction drawings and specifications. The client uses these drawings and specifications to enter into a fixed-price contract for the product. Notice how this long-evolved model separates the contract for design from the contract for construction. Even when both are performed by the same organization, this separation clarifies many things.
The rational model of design Engineers seem to have a clear, if usually implicit, model of the process of design. It is usually an orderly model of an orderly process as the engineer conceives it. The notion that the design process should be modeled as a systematic step-by-step process seems to have first developed in the German mechanical engineering community. Herbert Simon independently argues for design as a search process in The Sciences of the Artificial. He was motivated to lay out a strictly rational model of design precisely because such a model was a necessary precursor to automating design. His model remains influential even if today we recognize the "wicked problem" of original design as one of the least promising candidates for AI. In software engineering, Winston Royce independently introduced a seven-step Waterfall Model to bring order to the process. In fact, Royce introduced his waterfall as a straw man that he then argued against, but many people have cited and followed the straw man rather than his more sophisticated models. Even if ironically, Royce's seven-step model must be considered one of the foundational statements of the Rational Model of Design. Large combinatorial spacesThe ordering of steps
Design process models Any systematization of the design process is a great step forward compared to "Let's just start coding, or building." It: Provides clear steps for planning a design project Furnishes clearly definable milestones Suggests project organization and staffing Helps communication within the design team Is readily teachable to novices, and tells novices facing their first design assignments where to begin. The Rational Model in particular brings yet more advantages. The early explicit statement of goals, secondary desiderata, and constraints helps a team avoid wandering, and it breeds team unification on purposes. Planning the whole design process before starting coding or formal drawings avoids many troubles and much wasted effort. Casting the process as a systematic search of a design space broadens the horizon of the individual designers and lifts their eyes far beyond their previous personal experiences. But the rational model is much too simplistic, even in Simon's richly developed version.
The dual ladder The first task for growing designers, as opposed to managers, is to craft a proper career path for them, one whose compensation and sociological status reflect their true value to the creative enterprise. This is commonly called the dual ladder. It it easy to give corresponding salaries to corresponding rungs, but it requires strong proactive measures to give them equal prestige: equal offices, equal staff support, reverse-biased raises when duties change. Why does the dual ladder need special attention? Perhaps because managers, being human, are inherently inclined to consider their own tasks more difficult and important than design and need to deliberately assess what makes creativity and innovation happen. Senior craftsperson work
A platonic ideal As the architecture design progressed, I observed what at first seemed quite strange. For the architecture team, the real System/360 was the Design Concept itself, a Platonic ideal computer. Those physical and electrical Model 50, Model 60, Model 70, and Model 90 things under construction out on the engineering floors were but Plato’s shadows of the real System/360. The real System/360’s most complete and faithful embodiment was not in silicon, copper, and steel, but in the prose and diagrams of IBM System/360 Principles of Operation, the programmer’s machine language manual. I had a similar experience with the View/360 beach house. Its Design Concept came to be real long before any construction began. It persisted through many versions of drawings and cardboard models.
The design concept Is there positive value to recognizing an invisible Design Concept as a real entity in design conversations? I think so. First, great designs have conceptual integrity—unity, economy, clarity. They not only work, they delight, as Vitruvius first articulated. We use terms such as elegant, clean, beautiful to talk about bridges, sonatas, circuits, bicycles, computers, and iPhones. Recognizing the Design Concept as an entity helps us to seek its integrity in our own solo designs, to work together for it in team designs, and to teach it to our youth. Second, talking frequently about the Design Concept as such vastly aids communication within a design team. Unity of concept is the goal; it is achieved only by much conversation. Thus, moviemakers use storyboards to keep their design conversations focused on the Design Concept, rather than on implementation details. Dependence is more profitable than educationI mix it with two in my thought
The Idea The design is thus the mental formulation, which Sayers calls “the Idea,” and it can be complete before any realization is begun. Mozart’s response to his father’s inquiry about an opera due to the duke in three weeks both stuns us and clarifies the concept. For most human makers of things, the incompletenesses and inconsistencies of our ideas become clear only during implementation. Thus it is that writing, experimentation, “working out,” are essential disciplines for the theoretician. Everything has been composed making
The boldest decisions In retrospect, many of the case studies have a striking common attribute: the boldest design decisions, whoever made them, have accounted for a high fraction of the goodness of the outcome. These bold decisions were made due sometimes to vision, sometimes to desperation. They were always gambles, requiring extra investment in hopes of getting a much better result. Design with courage design
Intuition and systems Systematic design excluding intuition yields pedestrian follow-ons and knock-offs; intuitive design without system yields flawed fancies. How to weld intuition and systematic approach? How to grow as a designer? How to function in a design team? designteamwork