I’ve been reading Design is the Problem: The Future of Design Must be Sustainable. LibUx was doing it as some kind of book club thing, and while I’m horrible at book clubs, I *am* open to book recommendations. So, Design is the Problem.
It makes pretty decent bedtime reading–engagingly enough written that I can stay awake for more than a couple paragraphs, not so thrilling that I will glance at the clock and realize that I should have been asleep hours ago. I have a surprising amount of difficulty finding that balance, so it’s worth noting. Also worth noting: I don’t have my ILLed copy of the book at hand, so we’re just going to pretend that my intent was to capture broad ideas and not worry about details.
Things I like as of right now, when I’m maybe 3/4 of the way through the book:
- The focus on systems. Systems make me so ridiculously happy. Don’t just think of the system you’re designing in–think of the systems that system is a part of.
- The idea that in nature, one system’s outputs are another system’s inputs. No waste! What would that look like in a library? I keep trying to figure that out, and coming up with things like–I produce lots of data when I’m doing usability testing. I do my best to share it, but I can’t force others to reuse it, and I don’t generally have time to reuse it myself. Imagine if that were part of a larger process that I could dip into when I needed to and/or contribute my data to, and know that it would flow onward to someplace where it would see further use. Being able to reuse others’ output, whether in usability data or anything else, would mean I don’t always have to start from scratch! (And neither does anyone else.)
- Building on that idea–the idea that a subsystem’s “waste” could actually improve the larger systems it’s part of. Imagine a factory that purified a river instead of polluting it. What would be the library equivalent? Must figure this out.
- The idea of river systems vs. lake systems. In a river system, inputs come in, flow through, and pass right back out. In a lake system, inputs come in and get used and swirl around and get reused, maybe several times, before they pass out of the system. They contribute value to the system instead of just passing through.
- Recognition of the fact that there are many kinds of sustainability: social, ecological, financial, etc. Come to think of it, there are probably as many kinds of sustainability as there are kinds of systems.
- The case studies. I really enjoy the case studies embedded throughout the book; they take the abstractions and make them concrete.
Things I don’t like:
- The footnotes. I mean, I like footnotes in general. Footnotes are good, right? They often contain citations, and I like citations. But the sources this guy is citing in his footnotes–! Wikipedia, repeatedly. And news articles. I mean, nothing against Wikipedia and news articles, but seriously, these are the chief sources you use for your book?! You couldn’t even be bothered to chase down the sources those sources cited? My inner librarian is crying.
Every time I say to myself, “Oh, that’s interesting! I wonder where he pulled that from?” and then look and see it’s Wikipedia, I immediately begin to doubt the point he just made. Is it actually true? Maybe, but it just got added to the “Interesting but unverified” column in my brain.
Anyway–it’s worth a read, and possibly also worth further research to verify all the things the author relied on Wikipedia for.