Wednesday, October 06, 2004

Reading :: Participatory IT Design

Originally posted: Wed, 06 Oct 2004 08:39:36

Participatory IT Design : Designing for Business and Workplace Realities

by Keld Bodker, Finn Kensing, Jesper Simonsen

Bodker, Kensing, and Simonsen have been involved in Scandinavian participatory design for a long time, and they've done a lot to work out a systematic participatory design approach. This approach, called MUST, is the descendant of the early and relatively unstructured PD work and was presaged by the Cooperative Design approach described in the 1991 classic Design at Work. Understandably, I was eager to see their new book. And as I read Participatory IT Design, I saw that they had indeed systematized and developed those participatory design themes while keeping the political and ethical orientation of the early Scandinavian work. The many techniques that were developed in the UTOPIA project and similar projects -- prototyping, future workshops, organizational games, observations, document and functional analyses -- are here, further developed and given coherence in the MUST approach. And MUST provides a far more worked out understanding of organizations, projects, and project phases.

And yet. Have you ever met a scholar whose work you greatly admired, perhaps at a conference, and gotten to know him or her? And have you suddenly realized, this person is incredibly boring? That's how I felt about 30 pages in. The authors have provided too much structure, too much detail, and far too many scenarios to keep things straight; I could tell that there's something to the method, but it gets bogged down in the many, many details and principles and phases. Further, the methods and techniques are separated from the phases, so we don't get a solid sense of how the two relate. I can't keep from comparing this book to Beyer and Holtzblatt's Contextual Design, which -- although I have my issues with it -- really does a remarkable job of explicating phases, methods, and techniques in a more integrated manner.

All in all, I expect to refer to Participatory IT Design quite a bit in my scholarly work. But I can't imagine using it in a classroom, as I regularly use Beyer and Holtzblatt's book.

Blogged with Flock

Monday, October 04, 2004

Reading :: Networks of Power

Originally posted: Mon, 04 Oct 2004 21:38:56
Networks of Power: Electrification in Western Society, 1880-1930
by Thomas P. Hughes
Spend any time at all in the sociotechnical studies literature (broadly speaking) and you'll run across the title of this book. Latour cites it, Law cites it, Bazerman draws liberally from it, and Pickering has a detailed critique. The book is a historian's examination of how Western society became electrified between 1880 and 1930, focusing on the US, England, and Germany. Since my current project (on telecommunications) has something to do with the construction of similar networks, I decided I had to read it. So I ordered a used copy from Amazon.
The book, frankly, is daunting because it is so immense. This thing is the size of a telephone directory -- 465 pages. It's taken a while to get through it, especially since I ended up reading other books in the meantime to avoid being bogged down. But the book is worth it -- even though I have to agree with Pickering's sharp critiques of it. Networks of Power provides an unusually thorough discussion of sociotechnical networks, supported by painstaking research and some strong theoretical work. Perhaps because he is a historian, Hughes often provides more than sufficient evidence to support his points, and sometimes I think the points get lost in the narrative, but I strongly suspect the difference is one of discipline rather than unfocused writing per se.
This book is rich enough that I'm not even going to try to summarize it. Instead, I want to draw out a couple of key points.
One key point is that sociotechnical systems -- which Hughes regards as cultural artifacts -- have what he calls unique styles. These styles are shaped by cultural factors such as "geographical, economic, organizational, legislative, contingent historical, and entrepreneurial conditions" (p.405). These factors shape the style of a sociotechnical system so profoundly that styles are easily recognized (p.443) and a system of one style simply can't work elsewhere if lifted and transplanted whole. Chapter 14 is devoted to this proposition and makes the case in great detail. The foundation of the case is laid much earlier, though, in Chapter 3: Hughes argues with great success that when one applies a sociotechnical system from one set of conditions to another (e.g., when Edison tried to reproduce his New York system in England and Germany), one must see the work as technology transfer rather than as simply applying the same solution elsewhere (p.47; see also Bowker's book on Schlumberger, Akrich's work with the gazogene, etc.). Hughes' real contribution here is in doing the hard work of demonstrating this point across the mentioned factors, providing us with several examples and with a set of factors to apply to other cases. I'll certainly be using them.
Another helpful point is what Hughes calls the reverse salient, a lag in development of part of the system (p.79). (Hughes prefers this term to "bottleneck" or "disequilibrium" because of problems with those two metaphors.) "The reverse salient usually appears as a result of accidents and confluences that persons presiding over or managing the system do not foresee, or, if they do foresee them, are unable to counter expiditiously" (p.80). One example included the problem of the high cost of transmission that was faced in the direct current system.
Now to the chief problem. Like Pickering, I think that Hughes makes a mistake in separating technology and politics. He argues that in Chicago, technology was preeminent; in London, politics were; and in Germany, both participated equally. The problem, of course, is that it's not especially illuminating to separate the two, as Hughes seems at the verge of admitting several times. As his analysis suggests over and over -- particularly in the chapter on style -- technology is political and politics are technological.
In all, this is a really useful (though overly long) study and I'll certainly be using it a lot.

Blogged with Flock