The BBC miniseries based on Steward Brand’s How Buildings Learn became available on the Internet a few days ago. It’s chock-full of provocative stuff, and lays out compelling arguments about how structures succeed or fail in satisfying the needs and goals of people. (Let’s hear it for design on TV! First Mad Men, now HBL. It’s a televisual golden age!)
As I watched the opening episode, I thought of the quintessential local example of a learning building: The Ferry Building in downtown San Francisco. Built in 1898, it served as a ferry terminal for points around the Bay; as San Francisco changed and bridges eased the traffic burden, it gradually fell into disrepair. In 2004, it re-opened as gourmet food court, serving the prosperous downtown lunch crowd. San Francisco changed, and the Ferry Building “learned” to address a new set of needs. Beautiful.
Is architecture really a good analog for IxD?
Aside from all of the fascinating examples of the ways in which our built environment responds (or doesn’t respond) to change, what the miniseries reveals to me more than anything is the limitation of using architecture and construction as models for software design and development. Architecture serves as a helpful stand-in when you’re talking about the macro stuff — the planning process, the rough apportionment of the screen “real estate,” and discussions around extensibility or repurposing — e.g., Is this thing the first piece of the big structure, or is it the temporary thing that we live in while the big structure is built?
But when you’re talking about the way people experience things in a digital environment, architecture is a limited analog. Software is made up of subtle, nuanced interactions and ever-evolving technical capabilities. Interacting with software is conversation between two active participants; it’s fast-paced and packed with immediate possibilities. For example, changing context in software seems more akin to a change in facial expression than, say, a movement to a different room. (It should, anyway). The ever-evolving technical capabilities have created a world in which we’re all often experiencing some particular digital interaction for the first time; in fact, if someone wrote a book about how software is experienced, it could be called something like, “How Software Teaches Us How to Use It.”
Solutions begat problems, problems beget solutions
Of course, there’s another side of Brand’s perspective that’s relevant to our work: Most design projects (at Cooper, anyway) begin with what is presented as a straightforward task: Design a solution for the problem the clients have identified. Architects probably experience a transformation similar to ours, because the real problem is often quite different than what the client has articulated. Brand’s perspective is interesting to consider here, because our solution often simply modifies (or modulates) the problem — makes it smaller, hopefully — but still: Will our solution be able to handle the need to evolve to further reduce the problem? Of course, if anything could learn and teach at the same time, it’s software. But software that can learn … Hmm. Something sounds fishy about that. Remember that part in Terminator where they’re talking about how the computers took over?