process
On Process
People get confused, companies get confused. When they start getting bigger, they want to replicate their initial success, and a lot of them think that somehow there’s some magic in the process that they’ve created. And so they start to institutionalize process across the company. And before very long people get very confused that the process is the content.
In my career I’ve found that the best people are the ones who really understand the content. And they’re a pain in the butt to manage. But you put up with it because they’re so great at the content. And that’s what makes great products. It’s not process, it’s content.
Just-in-time manufacturing
Get embedded in the team. Designers should use sprint planning, grooming, standup, and retro as opportunities to provide design to — and receive feedback from — the rest of the team. Designs can take the form of written or verbal descriptions, not just wireframes and high-fidelity mockups.
Only design what’s needed. Use constant communication between engineering and product partners to understand what your collaborators will need next. Then, plan on delivering only what is needed, and nothing more. Use the agile process — grooming, planning, and retro — to find any shortfalls or excesses.
Avoid creating a backlog of designs. Designs don’t age well. In the time between finishing design and shipping code, it’s likely that you’ll learn something new that changes your understanding. If you’re producing more design than can be implemented, focus more on the quality of each design.
How beautiful the world would be if there were a procedure for moving through labyrinths
Design skirmishes
it is apparent that the unfolding of the design process assumed a distinctly episodic structure, which we might characterize as a series of related skirmishes with various aspects of the problem at hand.
As the scope of the problem became more determined and finite for the designer, the episodic character of the process seems to have become less pronounced. During this period a systematic working out of issues and conditions took hold within the framework that had been established. This phenomenon is not at all surprising when we consider the fundamental difference between moments of problem solving when matters are poorly defined and those with clarity and sufficiency of structure.
Within the episodic structure of the process, the problem, as perceived by the designer, tends to fluctuate from being rather nebulous to being more specific and well-defined. Furthermore, moments of "blinding" followed by periods of backtracking take place, where blinding refers to conditions in which obvious connections between various considerations of importance go unrecognized by a designer.
How we can do better
It actually doesn't matter whether you actually have a formal retrospective. It doesn't matter whether you have four or five labels of things on your retro board, or exactly how you do the retro. What does matter is the notion of thinking about what we're doing and how we can do better, and it is the team that's doing the work that does this, that is the central thing.
Holistic and prescriptive technologies
Holistic technologies are normally associated with the notion of craft. Artisans, be they potters, weavers, metal-smiths, or cooks, control the process of their own work from beginning to finish. Using holistic technologies does not mean that people do not work together, but the way in which they work together leaves the individual worker in control of a particular process of creating or doing something.
The opposite is specialization by process; this I call prescriptive technology. Here, the making or doing of something is broken down into clearly identifiable steps. Each step is carried out by a separate worker, or group or workers, who need to be familiar only with the skills of performing that one step. This is what is normally meant by "division of labor".
That which requires caring
Today's real world of technology is characterized by the dominance of prescriptive technologies.
The temptation to design more or less everything according to prescriptive and broken-up technologies is so strong that it is even applied to those tasks that should be conducted in a holistic way. Any tasks that require caring, whether for people or nature, any tasks that require immediate feedback and adjustment, are best done holistically. Such tasks cannot be planed, coordinated, and controlled the way prescriptive tasks must be.
Prescriptive technologies eliminate the occasions for decision-making and judgment in general and especially for the making of principled decisions. Any goal of the technology is incorporated a priori in the design and is not negotiable.
Direct management
Direct Management does not include or permit the concept of profit to occur. The management is fee-based, or based as a fixed salary, and all construction costs are fixed ahead of time, and the building design is modified during construction, to make up any over-runs. The manager is not able to move money around at will, or put it in their pocket. At the same time, the design is approximately fixed, but with the understanding that it may be changed, during the evolution of the building, so that subtle adaptations can be included in the emerging building. In the Direct Management method it is the architect themselves and the direct manager who together manage the building works and all on-site construction for the owner.
Manifesto for Agile Software Development
A DefinitionWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Deadlines are bullshit
An ArticleIn software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil.
- External vs. internal deadlines
- Why are internal deadlines evil?
- Engineers who love their work
The Design Diagram
An Idea by Charles Eames & Ray EamesThis Eames drawing, often referred to as the Design Diagram, was created for a 1969 exhibition at the Louvre entitled, What is Design? Charles and Ray mailed it to the exhibition curator to augment their answers to a series of questions she had posed.
In Defence of Intuition
An Essay by Boris MüllerDesign, it seems, is not only becoming more methodical but also more scientific. This is not surprising. Design as a discipline has moved from “product beautification” to being a central part of product development. It has incorporated methodologies from human-computer interaction, sociology, and anthropology as well as advertising and management. And with the rise of design thinking, a wider range of professional disciplines are using creative methods.
I don’t want to criticize design methodologies. But against the backdrop of an overly structured design process, it is important to remind our community that there is one fundamental aspect to design that cannot be formalized in a methodology. And that is intuition.
Why we need to stop over-complicating UX
An Article by Hugo FroesMany have become so focused on the process and methodologies that they’ve forgotten the fundamentals of why we started focusing on the user and what we hope to achieve with that focus.
Beyond Artboards
An Essay by Chuánqí SunThe Pursuit of Lossless Design-Development Handoffs.
Just-in-time Design
An Article by Matthew StrömThere is a disconnect between product design and product engineering.
The Hot Potato Process
An Article by Dan MallThe big misconception I’ve seen designers and developers often fall victim to is believing that handoff goes one way. Designers hand off comps to developers and think their work is done. That puts a lot of pressure on the designer to get everything perfect in one pass.
Instead, great collaboration follows what Brad Frost and I call “The Hot Potato Process,” where ideas are passed quickly back and forth from designer to developer and back to designer then back to developer for the entirety of a product creation cycle.
Building Momentum
An Article by Dan MallFight the Waterfall
Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting.
Share Work-in-Progress Early and Often
When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum.
The care and feeding of software engineers (or, why engineers are grumpy)
An Article by Nicholas ZakasWe do say “no” very quickly, not just to designs, but to everything. That led me into thinking about the psychology of software engineers and what makes us the way we are.
The art of taking
A Quote"By making it possible for the photographer to observe his work and his subject simultaneously, and by removing most of the manipulative barriers between the photographer and the photograph, it is hoped that many of the satisfactions of working in the early arts can be brought to a new group of photographers. The process must be concealed from—non-existent for—the photographer, who by definition need think of the art in taking and not in making photographs. In short, all that should be necessary to get a good picture is to take a good picture, and our task is to make that possible."
— Edwin H. Land, co-founder of Polaroid
Painting With the Web
An Article by Matthias OttSo much about [Gerhard Richter's painting process] reminds me of designing and building for the Web: The unpredictability, the peculiarities of the material, the improvisation, the bugs, the happy accidents. There is one crucial difference, though. By using static wireframes and static layouts, by separating design and development, we are often limiting our ability to have that creative dialogue with the Web and its materials. We are limiting our potential for playful exploration and for creating surprising and novel solutions. And, most importantly, we are limiting our ability to make conscious, well-informed decisions going forward. By adding more and more layers of abstraction, we are breaking the feedback loop of the creative process.
Technical debt as a lack of understanding
An Article by Dave Rupert"If you develop a program for a long period of time by only adding features but never reorganizing it to reflect your understanding of those features, then eventually that program simply does not contain any understanding and all efforts to work on it take longer and longer.” — Ward Cunningham
Seeing With Fresh Eyes
Meaning
Space
Data
Truth
The problem with trees
Many systems are organized hierarchically. The CERNDOC documentation system is an example, as is the Unix file system, and the VMS/HELP system. A tree has the practical advantage of giving every node a unique name. However, it does not allow the system to model the real world. For example, in a hierarchical HELP system such as VMS/HELP, one often gets to a lead on a tree such as:
HELP COMPILER SOURCE_FORMAT PRAGMAS DEFAULTS
only to find a reference to another leaf: Please see
HELP COMPILER COMMAND OPTIONS DEFAULTS PRAGMAS
and it is necessary to leave the system and re-enter it. What was needed was a link from one node to another, because in this case the information was not naturally organized into a tree.
Content-responsive space
Content-responsive spaces in text can be as meaningful as spaces and line breaks in computer code, poetry, math, dialogues, cartoons.
For 1500 years, printed text has used grids indifferent/hostile to meaning. Content-responsive grids are better than imperious grid-possessed layouts. To clarify and intensity meaning, authors and editors can remodel relations between spaces and words...insisting on control of line breaks by authors (who, after all, know the content).
Personal annotations
Yehudi Menuhin, a great violinist, marked up a score for Bach's Sonata No. 2 for Solo Violin. Penciled annotations show real-time performance strategies. To outsiders, insider markups appear chaotic and cryptic, but these personal annotations are for Menuhin's eyes, the only eyes that matter. All can learn from this useful workaday grid strategy: a relevant and intense data layer can become a coherent substrate scaffold upon which to overlay additional information. Maps do this all day long.
What excellence is
Learn what excellence is, how to identify it...This is not a big reading assignment – excellence is scarce, lognormal, long-tailed. Acting on this knowledge is liberating, freeing oneself from vast piles of triviality, knock-offs, petty connoisseurship, over-publishing, and the short-sighted, trendy, greedy. Excellence is long-term knowledge, even forever knowledge.
Excellence, like good taste, is perhaps a universal quality. Analytical thinking is about the relationship between evidence and conclusions, and is fundamental to all empirical work, regardless of field, discipline, specialty. Thus it is possible at times to assess credibility of nonfiction work without being a content expert. Thinking eyes may well have an eye for excellence, regardless of field or discipline.
Sentences and words do not exist by themselves
Sentences and words do not exist by themselves, but have natural, inevitable, unavoidable interactions with their surrounding spaces, words, and other sentences. Sentences are not independent of their spatial context, and interactions can create meanings and harms. Sentences survive content-indifferent and content-hostile spacings, but surviving is not thriving. Text space should not be owned and governed by generic productions grids, which make for convenient production but inconvenient meaning. Space can and should be content-responsive, actively contributing to meaning – forever practices in poetry, maps, math, computer code, comics, theater/movie scrips, posters. Subtle visual spacing differentiates and clarifies sentences, and meaning becomes more consequential, memorable, retrievable.
Central-axis text
Central-axis provides a clear signal of the next line, so that readers and speakers don't have to search on the left margin, sometimes accidentally skipping down a line. Ragged-left typography is used for dialogue in novels and scripts. In central-axis, each line is activated at both left and right margins – unlike squared-off conventional text. Readers/speakers are aware of the length of the next line at both its beginning and end. That knowledge may also help readers detect the pace and rhythm of the words, as in reading poetry aloud.
Idiosyncratic paragraphs
Text-only paragraphs differ from one another only in their words. All the words are typographically the same – typeface, spacings, line-lengths piled up into long deep columns. Systematic regularity of text paragraphs is universally inconvenient for readers, who are unable to find and read once against a specific string of words in previously-read paragraphs. All readers have encountered this problem in essays, articles, novels, news reports. Idiosyncratic paragraphs assist memory and retrieval by readers, by uniquely activating the relevant neural substrates for retaining visual memories. Nearly every paragraph in this book is deliberately unique.
No more LittleDataGraphics
Small data sets should be shown directly...LittleDataGraphics (pie charts, bar charts) translate and encode data into areas and colors. Viewers must then mentally translate codes back into numbers. These codes are unique to the local sets of data graphics, and do not repay learning. Instead, just directly show numbers as numbers. No more LittleDataGraphics. Data visualizations are at their best when there is so much data that the only way to see it...is to see it.
An immense wordy diagram
In ~1560 Ettore Ausonia, a polymath with interests from mathematics to mirror-making, constructed an immense wordy diagram depicting reflections from concave spherical mirrors. Then, between 1592 and 1601, while teaching at the University of Padua, Galileo made this handwritten copy of the diagram, which was fortunate since Ausonio's original has since gone missing. Three helpful architectures for the off-the-grid sentences are deployed – word trees, stacklists, annotated linking lines.
Stacklists
Stacklists organize and clarify complex material in 2-space. Readers read more slowly, and that's good: to think, look again, and connect words vertically within each stack and horizontally between stacks. Instead of polyphony, conventional inline lists are a freight train of words along a one-way narrow track, making it difficult to identify which words belong to which list and to link and compare elements within and between lists.
Observe data collection at the moment of measurement
See, observe, learn how data are collected at moment and place of measurement. "You never learn more about a process than when you directly observe how data are actually measured," said Cuthbert Daniel, a superb applied statistician. See with fresh eyes. Walk around what you want to learn about. Talk to those who do measurements. See how numbers came to be.
Do those measuring know the desired answer? Are those measuring skilled, alert, honest, biased, incompetent, sloppy, tired and emotional?...Artifacts and errors in measurements measured? How are outliers adjudicated?
46 data quality issues in spreadsheets
Outcomes decide
High levels of U.S. patient satisfaction are mainly associated with hospitality (greeters at the door, empathetic staff, comfortable rooms) – but also with more treatments, high costs, and substantially higher mortality even after adjusting for baseline health and comorbidities. Several plausible stories explain these big n and replicated observational findings. Whatever the case, post-treatment patient satisfaction/gratitude does not measure whether a treatment works or not. Patient outcomes decide.
Which half?
One day when I was a junior medical student, a very important Boston surgeon visited the school and delivered a great treatise on a large number of patients who had undergone successful operations for vascular reconstruction. At the end of the lecture, a young student at the back of the room timidly asked, "Do you have any controls?" Well the great surgeon drew himself up to his full height, hit the desk, and said, "Do you mean did I not operate on half of the patients?" The hall grew very quiet then. The voice at the back of the room hesitantly replied, "Yes, that's what I had in mind." Then the visitor's fist really came down as he thundered, "Of course not. That would have doomed half of them to their death!" God, it was quiet then, and one could scarcely hear the small voice ask, "Which half?"
Good annotation
Information displays should be annotated, combining words, images, graphics, whatever it takes to describe and explain something. Annotation calls out and explains information and, at the same time, explains to viewers how to read data displays. Good annotation is like a knowledgeable expert/teacher at the viewer's side pointing and saying, "Now see how this works with that, how this might explain that..."
Signs seen and unseen
Direct instructions at point of need may encourage writers and programmers to divert diversions. Or not, because signs are seen only a few times before becoming unseen.
What is the strongest visual element?
Preparing to write the novel Catch 22, Joseph Heller composed a storyboard, a 2-dimensional list with 3,650 words arrayed in 34 × 21 = 714 interacting cells. Rows are ordered in time, and each row records when each character does what. Some cell entries are erased. It took 7 years to complete the novel's 758-page typescript.
The Catch 22 plotchart works better upon replacing optically noisy grids with ghost grids. Lightness of framing lines creates soft boundaries to maintain order and also allows words to spill across cells naturally...More generally, ask of information displays and interfaces, "What is the strongest visual element?" The correct answer is not "grid lines".
Your only language is vision
To see with fresh, uninstructed eyes and an open mind requires a deliberate, self-aware act by the observer. Abstract artworks represent themselves and should be first viewed for themselves. When looking at outdoor abstract pieces, concentrate initially on the unique optical experience produced by the artworks. See as the artist saw when making the piece.
A focus on optical experience does not deny stories, it postpones them. Viewing an artwork may evoke interesting narratives – or just tedious artchat recalling similar art or artists, concocting playful tales, realizing how scrap metal was repurposed into art, making judgments about the artist's intentions or character, or contemplating an artwork's provenance, price, politics. Let the artwork stand on its own. Walk around fast and slow, be still, look and see from
up down sideways close afar above below
, enjoy the multiplicity ofsilhouettes shadows dapples clouds airspaces sun earth glowing
. Your only language is vision.Lists consist of whatever it takes
Lists consist of whatever it takes – nouns, proper nouns, verbs, graphics, images, numbers.
...In lists, spaces have meaning, locating elements in relation to other elements. Lists are often free and independent from conventional rules of stylesheets / grammar / typography / punctuation. Lists also help us escape from the personal internalized mash-up stylesheets of every writer and reader – a continuous low-level background buzz checking to see if word usage, spelling, punctuation, grammar are 'correct'. Lists are all content – about the substance contained, not the container. An empirical theory here for reasoning about lists includes
selection of list items
list quality and completeness
comparing list models
comparing list architecturesNo wonder you think it's complicated
We were very proud of our user interface and the fact that we had a way to browse 16,000 (!!) pages of documentation on a CD-ROM. But browsing the hierarchy felt a little complicated to us.
So we asked Tufte to come in and have a look, and were hoping perhaps for a pat on the head or some free advice. He played with our AnswerBook for 90 seconds, turned around, pronounced his review:
"Dr. Spock's Baby and Child Care is a best-selling owner's manual for the most complicated 'product' imaginable – and it has only 2 levels of headings. You have 8 levels of hierarchy and I haven't stopped counting yet. No wonder you think it's complicated."
Verb List
Documents vs. decks
Decks are easier to prepare than documents, however. Documents require coherence, thinking, sentences. But convenience in preparing decks harms the content and the audience. Optimizing presenter convenience is selfish, lazy, and worst of all, replaces thinking.
Books are meant to be used
During most of the course students have their books open, either to read or to follow along. Students are encouraged to annotate the books: "Books are meant to be used. Dog-ear the pages, mark them up, put notes in the spacious margins."
Learning via teaching
The course material changes 15% each year, as the book currently in progress becomes part of the course years before it is finally published. I detect incoherencies and mistakes in the new material while teaching. This leads to refinements or even throwing stuff out from the forthcoming book. A good way to learn about something is to teach it.
Self-publishing, self-exemplifying
I sought to design [my first book] so as to make it self-exemplifying – that is, the physical object itself would reflect the intellectual principles advanced in the book. Publishers seemed appalled at the prospect that an author might govern design. Consequently I decided to self-publish the book.
...[Howard Gralla and I] spent the summer in his studio laying out the book, page by page. We integrated graphics into the text, sometimes in the middle of sentences, eliminating the usual segregation of text and image – one of the ideas Visual Display advocated.
My view on self-publishing was to go all out, to make the best and most elegant and wonderful book possible, without compromise. Otherwise, why do it? The next 4 books were financed by the previous books. I have never written a grant application.
A history of content and sources
Not all that many readers go to the back matter and look up the source for a single sentence. But the back matter can also be read as ordinary text, revealing a history of content and sources. And images and illustrations from the book in the back matter create a lovely visual/verbal summary quilt of the entire book, enjoyed by all.