Information & Information Architecture
A history of content and sources
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..."
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.
No 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."
Infinite varieties of contexts
Over the course of 10 years of using Are.na, I have fully adopted the view that any piece of information can be important to a person given the right context. And on Are.na, pieces of information can be arranged in infinite varieties of contexts – their respective meaning shifts as the proximate information shifts. In other words, the more connections a block has, the more opportunities it has to be a nodal point.
Nodal points
I started thinking about all the other important “nodal points” (I don’t know what else to call this) of people, places, books, albums, websites, etc. that all played a part in shaping who I am as a person and what I think is important. These points are a combination of seeking things out myself and getting a recommendation that felt like it was actually for me. A mixture of both passive and active knowledge acquisition.
ultimately, it's the totality of those “nodal points” that indicate one’s own unique perspective. It doesn’t matter if you specifically sought out the nodal point or not, it’s the recognition that counts. When you encounter a piece of life-changing information (no matter how large the change part is), you are simultaneously discovering and creating “yourself,” becoming incrementally more complete. Your perspective (where your gaze is directed) is made up of a meandering line through these points. Learning (or maybe some precursor to learning) is a lot about developing the intuition to recognize when something you find in the world is going to be a nodal point for you.
What is a commonplace?
In all cases, a commonplace is a method of compiling knowledge for later use. In digital or analog form, this continued growth of stored ideas and projects is a key driver of intellectual development. Any time you decide to work on a project, you should attempt to collect and categorise all information that is relevant and useful.
Reveling in infrastructure
Hunstanton Secondary School (1954) in Norfolk, England, designed by Alison and Peter Smithson. Photo by Anna Armstrong (2011)
When the Smithsons placed the water heater for the Hunstanton Secondary School prominently above the school’s roofline, they weren’t just revealing the building’s infrastructure, they were reveling in it. What does it look like to do this on the web?
Of course there’s no single answer, because the web is simultaneously a physical and digital medium. It is material and it isn’t. It depends on how literally you interpret the question. But taking it somewhere in-between, seeing the web as primarily an information medium, we can ask the question a little differently: what does it look like to design something that is true to the material of digital information?
The quality of thought
It is the quality of thought and the information we use that determines yield, not the size or quality of the site.
A dot went for a walk
A dot went for a walk and turned into a line.
The dot, the line, the dance, the story, and the painting had found connections. Memory became learning, learning became understanding.Learning is remembering what one is interested in. Learning, interest, and memory are the tango of understanding.
Creating a map of meaning between data and understanding is the transformation of big data into big understanding.
The dot had embraced understanding.
Understanding precedes action.
Each of us is a dot on a journey.The need to record
With collecting comes the need to record. A specimen without a label is simply a (sometimes) pretty object. Without its associated data it is scientifically worthless.
The lapse of many years
At this point I wish to emphasize what I believe will ultimately prove to be the greatest purpose of our museum. This value will not, however, be realized until the lapse of many years, possibly a century, assuming that our material is safely preserved. And this is that the student of the future will have access to the original record of faunal conditions in California and the west, wherever we now work. He will know the proportional constituency of our faunae by species, the relative numbers of each species and the extent of the ranges of species as they exist today.
— Joseph Grinnell, 1910
Information imposters
Information imposters: This is nonsense that masquerades as information because it is postured in the form of information. We automatically give a certain weight to data based on the form in which it is delivered to us. Because we don’t take the time to question this, we assume that we have received some information.
My favorite example of this is in cookbook recipes that call for you to “cook until done.” This doesn’t tell you very much. Why bother? Information imposters are fodder for administravitis.
Like a prism
When you look at phonemes, you look through the perspective of morphemes, which are one linguistic level higher. The higher level is like a prism that splits the light in two. What was one thing, like ‘length’ at the phoneme level, looks like two opposite things ‘long’ and ‘short’ from the perspective of the morphemes. In practice, when you find both a word and its opposite, then the phoneme is not about either of these two things, but about what is common to them.
Thinking in terms of outputs
In our use of digital and analogue filing tools, we classify information through folders. An article about railway construction gets filed under ‘infrastructure’ or ‘transport’. In Evernote we tag it with ‘rail’ or ‘construction’. This is thinking like a librarian and not like a writer. We are classifying the information as an input. The reason you take notes as a writer is to produce content. It makes sense, then, to take notes in line with this goal.
Traditional filing like this tends to fail when you attempt to write your content. You are stuck trying to figure out which categories will be relevant for your proposal, paper or blog post. Interesting writing often comes from connecting separate fields through a common idea. By revealing the common denominator. By unifying two seemingly-contradictory ideas. How can you possibly achieve this if you’re looking in the same category for your information? The categories simply do not fulfil the function required by the writer.
The notes you take and indeed, the way you process information, should be with a specific project or idea in mind. You must classify information in terms of its outputs. When you take notes on a book, think about how this could apply to a specific idea you had or how it argues against a paper you read last week. The premise is that you should be organising by context and always trying to connect the dots between the content you're consuming.
Off to the races
"You get to the point where you're about to place your wager; the race is about to be run. You evaluate the sum total of the information, which has to do with how the money has been bet, what the horses looked like on the track, all this information—and it's like you run your hand over the race—I've had this happen so many times, it's the only way to explain it—you run your hand over the race. All the information is logically there, but there's something wrong. You don't know why something is wrong, but something is not correct. Then I have to reevaluate everything in terms of this feeling I have about the thing, which is derived from information, but which is so complex and so intricate and so subtle that there's no way you can put a tag on it."
The pie has been made
"In today's world, boundaries are fixed, and most significant facts have been generated. Gentleman, the heroic frontier now lies in the ordering and deployment of those facts. Classification, organization, presentation. To put it another way, the pie has been made—the contest is now in the slicing."
The Visual Information Seeking Mantra
There are many visual design guidelines but the basic principle might be summarized as the Visual Information Seeking Mantra:
Overview first, zoom and filter, then details-on-demand
Overview first, zoom and filter, then details-on-demand
Overview first, zoom and filter, then details-on-demand
Overview first, zoom and filter, then details-on-demand
Overview first, zoom and filter, then details-on-demand
Overview first, zoom and filter, then details-on-demand
Overview first, zoom and filter, then details-on-demand
Overview first, zoom and filter, then details-on-demand
Overview first, zoom and filter, then details-on-demand
Overview first, zoom and filter, then details-on-demandEach line represents one project in which I found myself rediscovering this principle and therefore wrote it down it as a reminder. It proved to be only a starting point in trying to characterize the multiple information visualization innovations occurring at university, government, and industry research labs.
Envisioning Information
A Book by Edward TufteBeautiful Evidence
A Book by Edward TufteThe Visual Display of Quantitative Information
A Book by Edward TufteThe Ladder of Abstraction
An Essay by Bret VictorThe Elements of Graphing Data
A Book by William S. ClevelandUnderstanding Understanding
A Book by Richard Saul WurmanVisual Explanations
A Book by Edward TufteInformation Visualization: Perception for Design
A Book by Colin WareThe Eyes Have It
A Research Paper by Ben ShneidermanLooseleaf
A WebsiteWikipedia
A WebsiteTinderbox
An ApplicationTinderbox is a workbench for your ideas and plans, ands ideas. It can help you analyze and understand them today, and it will adapt to your changing needs and growing knowledge.
Your Tinderbox documents can help organize themselves, keeping your data clean. We believe in information gardening: as your understanding grows, Tinderbox grows with you.
The medium is the message
A Quote by Marshall McLuhanProduct Design Resources
A Reference Work by Brandon DornThings I‘ve read, people I‘ve tried to learn from, and things I‘ve done to become a better designer. This is an idiosyncratic list reflecting what has helped me along the way, rather than an exhaustive list of design classics.
Though the list leans toward theory — principles are more durable than technique — I offer a few ideas further down about how to practice design. It also leans toward information design, because the task of presenting rich, dense information in an accessible way is ultimately the task of any digital product.
Blogging with Version Control
An Article by Will DarwinI’ve been musing for a while now on the way blog posts are typically presented—in reverse chronological order. This format has never truly made sense and does not reflect the way good writing and thinking happens.
...The main issue with the ‘pile’ system is that this post is eventually buried beneath more recent pieces of writing; there is no incentive for revisiting or updating the work. Even worse, if an author does decide to unearth the piece and make some major changes, those who read the original piece are not made aware of these alterations. The sorting order is static.
Nobody gives a hoot about groupthink
An Article by Baldur BjarnasonTwo relatively common ‘fashions’ today are real-time collaboration and shared data repositories of one kind or another.
Both increase productivity in the naive sense. We work more; everybody is more active; the group feels more cohesive.
The downside is that they also both tend to reduce the quality of the work and increase busywork.
Two types of work
An Article by Jorge ArangoThere are two types of work: growth work and maintenance work.
Growth work involves making new things. It can be something big or small. In either case, growth work often follows a loose process.
Maintenance work is different. Maintenance work involves caring for the resources and instruments that make growth work possible. This includes tools, but also body and mind.
Maintenance is ultimately in service to growth. But effective growth can’t happen without maintenance. As with so many things, the ideal is a healthy balance — and it doesn’t come without struggle.
Open Transclude for Networked Writing
An Essay by Toby ShorinWebsites are not living rooms and other lessons for information architecture
An Essay by Sarah R. BarrettWhile there is a lot that IA can learn from actual architecture or city planning, websites aren’t buildings or cities, and they don’t have to work like them. Instead, they should be designed according to the same principles that people’s brains expect from physical experiences.
Web History Chapter 1: Birth
A Chapter by Jay HoffmannHow to Think About Notes
An Article by Will DarwinWhat we have known since long
A Quote by Ludwig WittgensteinThe problems are solved, not by giving new information, but by arranging what we have known since long.
Readings in Information Visualization: Using Vision to Think
A Book by Ben Shneiderman
The Design of Design
What's Wrong With This Model?
A ChapterDesign 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.
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 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.
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.
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.
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.
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.
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.
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?