Reading :: Blue Ocean Strategy

Blue Ocean Strategy: How to Create Uncontested Market Space and Make Competition Irrelevant
By W. Chan Kim and Renee Mauborgne

Blue Ocean Strategy is an international bestseller on strategically developing new market space. The authors invite us to consider a "marketing universe composed of two sorts of oceans: red oceans and blue oceans" (p.4).

Red oceans are existing, known market spaces in which rules are known; in these spaces, products are commodities, competition is fierce, and margins become thinner (p.4). Here, the rule is incremental improvement and the competition makes it a battlespace (p.7).

Blue oceans, in contrast, are untapped market spaces in which rules are in the process of being made, competition is thin, and margins are consequently fat (p.5). Blue oceans are more profitable (p.7). They require value innovation, in which "instead of focusing on beating the competition, you focus on making the competition irrelevant by creating a leap in value for buyers and your company, thereby opening up new and uncontested market space" (p.12).

The authors include multiple examples of blue ocean strategy, most memorably Cirque de Soleil, which made traditional circuses irrelevant by eliminating, reducing, and raising certain aspects of the traditional circus while creating new value in the experience. Another example is [yellow tail], the Australian wine that was marketed in sharp contrast to other wines in the US market. In these and other examples, the authors use analytical tools to demonstrate how the cases contrasted sharply with existing products, allowing them to create blue oceans.

The notion of creating a new market is not especially revolutionary. But the book provides several linked heuristics that allow readers to analyze the current market, see possibilities, develop strategy, and execute it. That, I think, is what made it such a valuable book. Like most bestsellers, this one is now available very cheaply on the used book market (which is where I got my copy). But it's still valuable if you're planning to market a product, or even if you're thinking about analogous ways to distinguish your work from others. (I can imagine academics using some of these heuristics to identify large research holes and gaps in current theory, for instance.) The book is readable, easy to grasp, and well illustrated with examples. If marketing is interesting to you, I suggest picking it up.

Writing :: Chapters in the Handbook of Writing and Textual Production

Handbook of Writing and Text Production
Ed. Eva-Maria Jakobs and Daniel Perrin

Here's another entry in my series on writing publications.

As I mentioned in an earlier entry, in 2011, I met Eva-Maria Jakobs at the Writing Research Across Borders conference in Washington, DC. She and coeditor Daniel Perrin were trying to recruit authors for a visionary collection on writing and textual production, one in which each chapter would be coauthored by two scholars from different continents. My mentor David R. Russell introduced us, and we hit it off immediately—we chatted about the proposed structure, discussed what scholars to approach for some of the chapters, and agreed that I would coauthor one of the chapters (on writing in professional domains) with her.

When we got back to our respective institutions, we began Skyping and sharing drafts, and quickly discovered that we had the same approach to scholarly writing—write quickly, iterate rapidly, read and cite extensively. We coauthored the chapter, but also the introduction to the section in which it appeared:

• Jakobs, E.-M. & Spinuzzi, C. (2014). The domain perspective in text production research. Handbook of Writing and Text Production, ed. Jakobs, E.M. & Perrin, D. De Gruyter: Berlin/New York. 325-332.
• Jakobs, E.-M. & Spinuzzi, C. (2014). Professional domains: Writing as creation of economic value. Handbook of Writing and Text Production, ed. Jakobs, E.M. & Perrin, D. De Gruyter: Berlin/New York. 359-384.

I greatly enjoyed this collaboration, and I'm especially happy with the work we did on "Professional Domains," which synthesizes work on professional writing across Europe and North America and suggests future developments. Sometimes collaborations don't go well, and sometimes they are adequate, but this collaboration really worked brilliantly for at least three reasons:

• We both made it a priority. People have lots of demands on their time, and often a collaborative writing project will take a back seat to other priorities. In this case, Eva and I both made these chapters a priority. We had frequent Skype meetings in which we agreed upon writing and research tasks, then faithfully executed those tasks before the next meeting. More than that, we read and commented on each others' writing and we suggested sources and read each others' sources. And we kept a calendar of changes so we always knew where the endpoint was.
• We appreciated each others' work while still providing critical comments. It's sometimes tricky to critique people's work, but in this collaboration, it was easy. We respected each others' expertise and collaboratively developed angles that we wouldn't have been able to provide on our own.
• We read widely. Eva reads English and French; I unfortunately read only English. But Eva was great at providing me with appropriate translations and pointing to English works that I hadn't read yet; I was able to tie in some work in English that she hadn't seen. In our Skype meetings, we worked to integrate all of this scholarship and prune redundant work as appropriate. The result was a pair of chapters that crossconnected a lot of research across two continents.

Overall, it was a great collaboration, and I hope you'll find the resulting chapters to be useful too.

Reading :: Journey to the West

Monkey - Journey to the West
By Wu Cheng'en

Journey to the West is a famous collection of stories about Sun Wukong, a monkey who achieves immortality and then creates chaos in Heaven, only to be sent back to Earth to pay for his crimes. He is imprisoned for 500 years underneath a mountain, then tasked with accompanying a monk on his journey to the West (India) to fetch the Buddhist scriptures. Like any fairy tale, it's full of magic and lots and lots of killing. It also satirizes inept bureaucracy—the version of Heaven described here seems pretty ineffectual.

Journey to the West has been produced many times, in many different versions. (For instance, the Japanese version of the name Sun Wukong is Son Goku, who should sound familiar if you've ever watched Dragon Ball Z.)

In fact, stop reading this review right now and go search YouTube for Journey to the West.

Are you back? Yeah. Whatever video you clicked on, that is exactly what the book was like. Supposedly someone refilms the story in Asia at least once a year. Here's the latest one, with Chow-Yun Fat in the starring role.

The book itself is an odd mixture of Grimm's Fairy Tales and Pilgrim's Progress. But, as I mentioned earlier, it's much more violent. If that appeals to you, check it out—or just watch more of those hallucinogenic YouTube videos.

Reading :: Babylonians and Assyrians: Life and Customs

Babylonians and Assyrians, Life and Customs
By the Rev. A.H. Sayce

I was looking for some pleasure reading a couple of months ago, so I downloaded this public domain book on Kindle. It's what you might expect from a book published in 1899, with phrases such as "Of this there is no proof" and lots of superfluous hyphens. Still, it paints an interesting and entertaining portrait of the Babylonians and Assyrians as they were then understood.

The book covers what was then known about Babylonia and its inhabitants; the family; education and death; slavery and free labor; manners and customs; trades and land; banking; government; law; writing; and religion. I was particularly interested in the last two.

Can I recommend this book? Not as scholarship—it's too dated and too imprecise. Not as entertainment—it's not really a page turner. But if you're the kind of person who becomes curious about a particular topic, such as Babylonian religion, and finds himself spending way too much time reading about it on Wikipedia, this might be a good way to learn a little more about it for free.

Reading :: 76 Fallacies

76 Fallacies
By Michael LaBossiere

Some people like to learn about, name, and examine logical fallacies in detail. I confess that I'm not one of them. Identifying fallacies is a detail-oriented proposition, and although I can focus on details, I tend to look at the big picture first. So, clearly, I needed to read a book like this one. And 76 Fallacies is only 99 cents on Kindle.

I'm glad I did. Although I won't be memorizing the names of all 76 fallacies anytime soon, I enjoyed the spare text and clear examples supplied by the author. In paging through the fallacies, I gained some appreciation for what makes a fallacy a fallacy, how fallacies relate, and how one might use a reference such as this one to spot them.

If you're interested in fallacies—or even, like me, just interested in gaining some appreciation for their pursuit—take a look.

Reading :: Totemism

Totemism
By Claude Levi-Strauss

"Totemism is like hysteria," Levi-Strauss says in the first sentence of this slim book, "in that once we are persuaded to doubt that it is possible arbitrarily to isolate certain phenomena and to group them together as diagnostic signs of an illness, or of an objective institution, the symptoms themselves vanish or appear refractory to any identifying interpretation" (p.1). Like hysteria, he says, totemism involves bracketing certain phenomena as outside one's own moral universe (p.1).

Levi-Strauss develops this argument throughout the book, as here: "it is not because they are totemic that such systems must be regarded as irregular; it is because they are irregular that they can only be totemic" (p.53). Through a careful examination of the then-extant work on totemism, Levi-Strauss developed this influential work, calling into question what was up to that point a broadly held assumption about how "savage culture" worked.

I'm not an anthropologist, so although I enjoy Levi-Strauss' works, I can't evaluate the argument directly. But as a scholar of rhetoric and writing, I do recognize the approach—identifying a well known concept, taking it apart, and seeing how well it stands up to scrutiny. Levi-Strauss does this well and methodically, and as a result, the concept of totemism (at least, as a universal phenomenon) declined after this book made its impact. If you're interested in totemism—or in how concepts disintegrate—take a look.

Reading :: The Schlumberger Adventure

The Schlumberger Adventure
By Anne Gruner Schlumberger

Just a brief review here. In 1997, I came to Austin to intern with Schlumberger Well Services at their Austin Product Center—a very rewarding experience, leading to my first qualitative research project and three publications. The APC, alas, has been closed for a while, but I think of it fondly. I reminisced about it when I read Geoff Bowker's Science on the Run, in which he described the history of the company based on its archives and ancillary sources. Although I don't have the book at hand, I'm pretty sure one of them was The Schlumberger Adventure. So when I saw it at a used bookstore, I snapped it up.

The Schlumberger Adventure was written by Anne Gruner Schlumberger, the daughter of one of the brothers who founded the company and (for a while) the wife of Henri Doll, one of the key leaders in the company. It's not a history so much as a memoir of how the company grew from a couple of brothers conducting experiments in a bathtub to a multinational corporation. The author treats everyone evenhandedly, noting both their strengths and their foibles, and focusing more on the difficulties than the triumphs. The book is a collection of moments: driving across Oklahoma in an unreliable car; seeing their Russian partners become more withdrawn and agentless as Stalin took hold, then finally disappearing; trying to avoid the Second World War. It's a fast read and a sensitive portrait. If you're interested in the history of the company, I'd recommend it.

Reading :: Swarmwise

Swarmwise: The Tactical Manual for Changing the World
By Rick Falkvinge

His bio says "Rick Falkvinge is the founder of the Swedish and first Pirate Party, which has representation in the European parliament and has spawned Pirate Parties in more than 60 other countries." And in this book, accessible as a free download (PDF) and a printed book, he discusses how he founded it, organized it, grew it, and led it to victory.

Specifically, he discusses how leading a swarm is different from leading other sorts of organizations:

A swarm organization is a decentralized, collaborative effort of volunteers that looks like a hierarchical, traditional organization from the outside. It is built by a small core of people that construct a scaffolding of go-to people, enabling a large number of volunteers to cooperate on a common goal in quantities of people not possible before the net was available. (p.14).

Swarms, he says, are not leaderless—they need leaders. But that leadership involves articulating and projecting values and then persuading others—anyone who chooses to join the swarm—to take them up in specific projects:

A key aspect of the swarm is that it is open to all people who want to share in the workload. Actually, it is more than open — everybody in the whole world is encouraged to pick work items off a public list, without asking anybody’s permission, and just start doing them. There is no recruitment process. Anybody who wants to contribute to the goal, in his or her own way and according to his or her own capacity, is welcome to do so. (p.19).

Another key aspect is that it is transparent—in values, participation, operation, etc. Falkvinge does a nice job of alternating between describing such principles and telling the story of the Pirate Party, a story that nicely illustrates his points. Throughout the rest of the book, he describes how to launch and organize a swarm, how to control the vision without controlling the message, lead the swarm daily, avoid the traps of too much democracy (getting bogged down in votes) or too much bureaucracy, and managing radical growth. Each chapter is clear, concise, engaging, and well illustrated.

If you've been following this blog, you may see a lot of overlap with Arquilla & Ronfeldt's work, although there are differences as well. Arguably, Falkvinge's is a more radical concept, but I can certainly see productive contact points. Compared to that earlier work, this book is less scholarly, less analytical, and more of a how-to.

It's also very easy to read and engaging. Although the PDF is about 300pp, I read nearly all of it in one sitting. If you're interested in developing and leading swarms, or just in how they might operate, you should too.

Upcoming seminar: Writing persuasive business proposals

If you're in Austin, consider my November seminar on writing persuasive business proposals. It's offered through the Human Dimensions of Organizations program here at UT, and it should give you a solid background for structuring your own proposals.

Questions? Email me!

Topsight > Book Signing

Sorry for the late notice, but if you're at SXSWedu today, please swing by my book signing for Topsight. Here's the details:

Monday, March 3
4:30PM - 4:50PM
Austin Convention Center BR D Pre-Function Area
500 East Cesar Chavez Street

Topsight > A year of Topsight, and thoughts on the second edition

A little over a year ago, I launched my book Topsight: A Guide to Studying, Diagnosing, and Fixing Information Flow in Organizations. In the intervening year, I've been really pleased with how things have unfolded.

Topsight is an introductory text for field researchers who are interested in how information flows through an organization, where it gets stuck, and how to get it unstuck. It's based on my own research approach, but also on years of teaching field research to writing majors. One of the things I have really liked about writing Topsight, and teaching from it, is that I have been able to express what's fun and intriguing about field research. Sure, not every part is fun—I don't enjoy putting together consent forms, for instance—but most of it is. And it gets more fun when you have enough guidance to get you through the rough spots: pitching your project to a site, getting stakeholders on board, writing a research proposal that will pass the IRB but still be flexible enough to address unexpected contingencies, and coding the mountain of data you gather, for instance.

Since I launched Topsight in January 2013, I've used it for four courses (three undergraduate, one MA). I've Skyped with two graduate courses at different universities about it. I've received emails from several graduate students whose advisors suggest they read Topsight. And I've been really happy with the response.

At the same time, a book can always be improved. I've been keeping a running list of things I want to revise for the (eventual) second edition. Some improvements include:

• Streamlining the research proposal, consent form, and protocol examples.
• Revising the interim report example to better illustrate the principles in the chapter.
• Revising the coding chapter to emphasize process, provide more grounding on coding, and refer to solid coding resources such as Saldana's Coding Manual for Qualitative Researchers.
• Discussing organization types and organizational lifecycles in a dedicated chapter.
• Framing the analytical models within the larger qualitative research tradition of analytical models, e.g., in Miles, Huberman, & Saldana's Qualitative Data Analysis 3ed.
• Developing an overview of participatory design techniques for testing recommendations.
• Addressing miscellaneous typos and formatting issues.
• Perhaps going to larger book dimensions.

If you've used Topsight, I'm sure you also have suggestions. Please don't hesitate to send me your suggestions or comments!

Reading :: Digital Detroit

Digital Detroit: Rhetoric and Space in the Age of the Network
By Jeff Rice

First, a confession: When I read Jeff Rice's first book, I don't think I really got his project. Rice was patient enough to explain it a bit in the comments. I suspect that I wasn't the first person he had to wearily correct.

Over the intervening years, I've become better acquainted with Rice's trajectory and his writing style (which Cynthia Haynes describes as "a cross between Rod Serling and Bob Dylan") and am perhaps in a better position to get what he's doing. In this book, he's interested in applying the concept of network to Detroit—network in the sense of associational links—to analyze how implicit and explicit arguments can resonate across these associations. As he says in the introduction, after name-checking chora:

I am... networking Detroit by tracing its accounts. Despite the possible readerly discomfort, I find this method advantageous for how it allows me new kinds of opportunities to explore a space; by using a network to examine Detroit as a digital concept, I am made aware of connections I would not have discovered otherwise. The disadvantage of this method, however, is that it can, at times, feel confusing. (p.13)

At times, yes. In fact, Rice's writing style is sometimes arresting, relying sometimes on repeating the same noun at the end of subsequent sentences, putting the emphasis on old rather than new information, sometimes sounding weary. Haynes hears Rod Serling in this voice; I hear Andy Rooney. Either way, it's a very different style, one that often seems to circle around to (or build slowly to) the point. This style is sometimes disrupted by uncharacteristic, heavy forecasting and other metadiscourse—I suspect that these are due to reviewers' comments rather than being organic to Rice's style. Too bad. Although I'm a big fan of clear signaling and forecasting, there's something to be said for following along at the pace the author sets.

And that style and pace are well suited for what Rice is trying to do here. Rather than describing a phenomenon out there, a shared social phenomenon, he is describing an idiosyncratic understanding based on associations:

All of my information is a network. All of my information I gather and assemble is internal to that network. These previous references—a contemporary op-ed, a 1940s historical book, a kitschy song, a novelist's travel memoirs, a car commercial—are database items within that network. Everything I produce, therefore, is a network as well. ... This book is an exploration and creation of that network. It attempts to be an information system. (p.24)

Readers might naturally wonder why the idiosyncratic network of associations that Rice describes could be useful to them. What's intrinsically more interesting about the network of associations that Rice pieces together about a specific time and place, versus, say, our own associations? Essentially this is the question that I asked about the year 1963 when I reviewed The Rhetoric of Cool. The answer that I was too task-oriented to see back then, but that I think I see now, is this: What's interesting is not the topic around how the network forms, nor the person who has assembled the network, but how such networks work, both for individuals and communities. In particular, how they function rhetorically, persuading and shaping perceptions. "Indeed, as I will argue throughout each chapter of this book," Rice adds halfway through, "networks move and are moved; they transform and translate experiences and ideas as they form and break connections. They do things" (p.70).

In his earlier book, Rice discussed such associations via the notion of chora. In this one, he draws on Latour, particularly Reassembling the Social. But whereas others in writing studies have applied Latour to empirical studies, Rice applies Latour to circulating rerepresentations in much broader, more idiosyncratic ways. As he does so, he opens the possibilities for applying such associational insights to rhetoric, demonstrating how they can help us to understand why these associations can be so persuasive in shaping our understanding of identities. Detroit is the case, but the real contribution of the book is the approach. I hope I've done justice to it—and if you're interested in networked rhetoric, I recommend you read the book.

Reading :: An Inquiry into Modes of Existence

An Inquiry into Modes of Existence: An Anthropology of the Moderns
By Bruno Latour

I've cited Latour quite a bit in my scholarship and reviewed his works on this blog, so when I found out this book was being published, I bought it immediately, along with Rejoicing. The book is respectably thick, 486 pages—which is actually much shorter than it could have been, since Latour omitted parenthetical citations and did not include a bibliography. You can see the citations at the book's website, which also hosts the book's glossary, visual materials, notes, and articles, as well as a column for readers' commentary and critiques. (If you want an index, too bad, use the online search function.) It's an interesting, though quite centralized and controlled, experiment.

For now, though, I'll keep my critique decentralized on this blog. But what a daunting challenge it is to critique a thick book by a world-renowned scholar. Especially when the scholar draws on such a broad set of significant works. Especially when the scholar writes in ways that often seem oblique and metaphorical, And especially when the resulting book seems like a capstone, one that reviews practically all of the author's scholarly output. That's essentially what the book is, from what I can tell: an attempt to tie all of this previous scholarship together into a single broad-based inquiry.

So what is this inquiry? Essentially, it's a taxonomy of different processes that yield different, yet internally coherent, contexts or meanings. Throughout his career, Latour has studied how meaning and knowledge are produced in the sciences, in technology, in law, in religion, in economics, and in politics. Here, he argues that these represent separate processes for developing meaning, processes that are internally consistent but that appear at odds when they come into contact. Those processes are all ways for making meanings and truth—ways with different logics, aims, and standards of proof. But it's difficult to get these modes of existence to interact well for two reasons.

First, it's easy to make category mistakes, mixing up their separate felicity conditions.

Second, and related, it's easy to assume that the different modes of existence are essentially compatible, boiling down to the same mode of existence and ideally following the same logics, aims, and standards of proof (something that Latour describes using the figure of "double click"). For instance, when someone tries to apply the felicity conditions of science to politics, or those of technology to religion, s/he is invoking the "double click," assuming that there can be transportation without transformation.

With that in mind, Latour patiently discusses each mode of existence, then how those modes interact. Patiently, but not economically, because Latour is not an economical writer. Fortunately for us, he lists the modes of existence in the back of the book:

• reproduction
• metamorphosis
• habit
• technology
• fiction
• reference
• politics
• law
• religion
• attachment
• organization
• morality
• network
• preposition
• double-click

Each has its own hiatus (loosely speaking, a disruptive condition), trajectory (i.e., results of transformations), felicity/infelicity conditions (when they thrive vs. when they crash), beings to institute (i.e., objectives to produce), and alteration (i.e., the way in which they are transformed). (I'm not sure how happy Latour would be with my parenthetical explanations, but since he has not provided an index, I'm going to stick with these.) 

You'll notice that some of these modes are tied to fields (e.g., politics, law, religion) while others are not (e.g., habit, organization, network). Activity theorists will note that habit, which AT would associate with the operational level of activity, is presented as a separate mode. Yes, these modes are entangled in practice, and I'm not always clear on why a field-oriented mode (e.g., science) is on the same footing as a mode that is inevitably going to be instantiated in every other mode (e.g., habit). But Latour is not simply attempting to examine these modes as separate, but as inevitably crossing and producing hybrids. For instance, he talks about the crossings between networks and prepositions (p.63), reproduction and reference (p.106), reference and politics (p.128), reproduction and metamorphosis (p.202), technology and networks (p.212), and so forth. In defining each mode along basic canonical questions (hiatus, trajectory, felicity/infelicity, beings to institute, alteration), Latour has presented a way to systematically investigate each mode and how each mode interacts with the others. 

To describe the project in an overgeneralized way, the book is an attempt to get at polycontextuality via a taxonomy of processes that yield different, coherent contexts/meanings. Once the taxonomy is laid out, we can use it to systematically investigate how these processes interact. Along the way, Latour draws on his vast set of publications, discussing Latourean concepts from networks to black boxes to quasi-objects and quasi-subjects to factishes, and on and on. If you haven't read Latour yet, this is probably not the book to start with. The number of concepts is overwhelming, as is the overall scope of the project, and Latour's often elliptical, often metaphorical writing style makes it difficult to keep the concepts and scope straight. 

For those who have read most of Latour's major works, this book is worthwhile. But it's not a walk in the park for those folks either: after all, the book is attempting to reframe key parts of Latour's work, often by re-presenting some of the original material within the newly expanded scheme. In practice, this means that it's easy to begin skimming a chapter ("ah, this is his basic argument from that chapter in Pandora's Hope") only to realize near the end of the chapter that Latour has added a new term, concept, or connection. This problem is compounded by the fact that the printed book has removed some of the key signals that help readers to detect updated arguments: citations and footnotes. Nevertheless, the book synthesizes a vast body of work into a more coherent understanding of what's at stake. Those who have seen Latour primarily as a sociologist of science because of his earlier books should now be able to see how those early projects connect with his overarching ontological project.

At least in outline. As Latour says apologetically on p.478, "I am well aware that I passed over each mode too quickly, and that each crossing would require volumes of erudition, even if the modes and crossings are more fully developed in the digital environment that accompanies this text" (p.478). Latour's hope, I think, is that the digital environment will allow others to work out these ideas more fully, connect the modes more firmly, and examine the crossings more fully. Latour has provided this vast infrastructure, so won't you build on it?

Will I? Probably not. I expect that I'll return to this book over and over—as a sourcebook. But as a work of scholarship, it was too exhausting, too unwieldy, and too sprawling for me to take in. (Longtime readers may note that this review is shorter than those I've written for similarly massive books.) The scope itself was not the only problem. Latour's writing style, which can be immensely enjoyable in 150pp books, wore on me in this longer format, and I began to fervently wish that some editor had been licensed to ruthlessly edit for concision. Frankly, I think this book could have been sweated down to 200 lean, well-organized pages, and the result would have been much easier to absorb and navigate.

Nevertheless, if you have a few Latour books on your shelf, I encourage you to pick it up. In fact—although I obviously didn't try this—you might consider blocking off six months to read the book in concert with Latour's major works. For instance, when the present book mentions religion, you could bookmark it and read On Rejoicing. When it mentions law, you could bookmark that passage and read The Making of Law. When it discusses factishes, you could read Pandora's Hope and On the Modern Cult of the Factish Gods. If you do this, let me know how it goes.

Reading :: Innovation, Human Capabilities, and Democracy

Innovation, Human Capabilities, and Democracy: Towards an Enabling Welfare State
By Reijo Miettinen

Reijo Miettinen is a professor of adult education at the University of Helsinki, where he works alongside and often collaborates with several other activity theorists (such as Engestrom and Sannino). His work has typically involved case studies of scientific and technical innovations, case studies in which he has applied activity theory. In this book, however, he's less interested in contextualized case studies, instead focusing on the question of why Finland has excelled at innovation in educational and business contexts. That is, this book is focused on policy, using activity theory as a framework for understanding how Finland's educational policies have worked.

Interestingly, in Chapter 2, Miettinen applies rhetoric to the question of policy making, drawing on Burke and Perelman. This move allows him to examine policy and its drivers, setting the stage for an historical analysis of stakeholders and shifts in how those stakeholders have interpreted policy terms and concepts. He also examines the educational system, innnovation and technology policy, and capability-cultivating services. The result is a deeply textured examination of the unique mix at play in Finland.

I'll be honest: I'm not terribly interested in policy. But Miettinen conducts a solid, detailed analysis and does his best to enliven what is inherently a dry topic. I am interested in activity theory, but it is applied here rather than extended; you won't see new insights into AT here, just a model application of it.

If you're interested in policies, innovation, and education, or an application of AT to these topics, pick up this book. If you're not, consider picking it up anyway, but take it slow.

Reading:: Qualitative Research: Studying How Things Work

Qualitative Research: Studying How Things Work
By Robert E. Stake 

Whenever I pick up an article on qualitative research, it seems, I see Stake referenced in the methodology section. So when I bought several methodology texts recently, I tossed Stake on the heap.

That was a worthwhile decision: Stake provides a clear, understandable, and (in some places) passionate discussion of qualitative research and its applications. As an introductory text, it works well, covering basic concepts and stages such as the researcher-as-instrument, data collection, literature review, analysis, action research, and reporting.

But at the same time, as with Charmaz's book, this one is pitched as an introductory text. Consequently, I found myself skimming a lot and sometimes skipping chapters. If you're interested in an introduction—for yourself or your students—this might be a good book to use. But if you've conducted a few studies already, I'd look for something a little more advanced.

Reading :: Constructing Grounded Theory

Constructing Grounded Theory: A Practical Guide through Qualitative Analysis
By Kathy Charmaz

When Charmaz published this book in 2006, it became an instant classic. Researchers working with grounded theory found it to be an accessible, useful guide for conducting qualitative research. They're right: Charmaz covers the basics of grounded theory, discusses how to collect data, code it, write analytical memos, conduct theoretical sampling, develop theory, and write it up.

The book is accessible. But I was only lukewarm about it. I don't think that's the book's fault, though. Rather, I think that the book is simpler than I wanted it to be—especially just after reading Saldana and Miles, Huberman, & Saldana, both of which explore parts of the qualitative research process in great detail. Those books taught me something; Charmaz's book is more of a primer—which, to be fair, is what it's supposed to be.

But for that reason, I'd consider using Charmaz's book for a graduate or even undergraduate class in qualitative research. It's accessible, clear, and perhaps more lucid than any other explanation of grounded theory that I've read. If you're just learning about qualitative research in general or grounded theory in particular, pick it up.

Reading :: Qualitative Data Analysis: A Methods Sourcebook

Qualitative Data Analysis: A Methods Sourcebook
By Matthew B. Miles, A. Michael Huberman, and Johnny Saldana

Miles and Huberman's Qualitative Data Analysis is a classic sourcebook for qualitative researchers. I have the second edition on my shelf in the office—the one that I bought as a new assistant professor at Texas Tech. Unfortunately, Miles and Huberman passed away before they could produce a third edition, and in the intervening years, qualitative research has gone through transitions. For instance, computer-aided qualitative data analysis (CAQDAS) packages have become commonplace, diversified, and become available on various platforms. Coding has become more systematized, partially because of Saldana's efforts.

The publisher, Sage, decided that it needed a new edition. So it approached Johnny Saldana, who has attempted to preserve Miles and Huberman's insights and text while updating and extending it. Saldana does not always agree with Miles and Huberman, and sometimes signals that disagreement by specifying the source ("Miles and Huberman say...").

The book is a sourcebook, not a cookbook: any method that works is fine (p.6). And it's focused on analysis, not research design or data collection, although it touches briefly on both. You can read it through sequentially—I did—but it's really meant as a reference. It covers matrix and network displays, the two basic types of data displays, and walks through how to apply these to explore, describe, order, explain, and predict. Simple, right? Yes, but the book is 373 pages of painstaking discussion.

It's all worth it. If you do qualitative research, this book should be either on your shelf or (more frequently) open on your desk.

Reading :: The Coding Manual for Qualitative Researchers

The Coding Manual for Qualitative Researchers
By Johnny Saldana

I can't remember whether I saw this book cited in a recent article or whether Amazon suggested it to me—but I bought it alongside the third edition of Qualitative Data Analysis: A Methods Sourcebook, the classic Miles and Huberman sourcebook that Saldana recently updated. (I'll review that one soon too.)

In any case, this present book is all about coding, a move in qualitative research that involves interpreting, analyzing, and organizing data. "A code in qualitative inquiry is most often a word or short phrase that symbolically assigns a summative, salient, essence-capturing, and/or evocative attribute for a portion of language-based or visual data" (p.3). It's primarily an interpretive act (p.4).

Coding is often treated in qualitative research texts, but as a chapter or a section, not an entire book. Consequently, we typically get a restricted, crabbed idea of what coding involves. By giving himself the room to really explore coding, Saldana provides a broad synthesis of what others have said about it, and he consequently is able to systematize it and provide many different strategies for it.

In Chapter 1, Saldana describes what coding is, what it involves, and how to use computer-aided qualitative data analysis software to implement it. He explains how coding represents an interpretive, analytical act and prescribes ways to code solo or as a team.

In Chapter 2, he goes on to discuss analytic memos and their role in generating codes and categories of codes.

Chapter 3 is where coding actually begins: Saldana describes first-cycle coding methods, "processes that happen during the initial coding of data" (p.58). By methods, Saldana essentially means discrete categories of coding approaches: grammatical, elemental, affective, literary & language, exploratory, and procedural methods. Each is associated with different types of codes. For instance, affective methods involves emotion coding, values coding, versus coding, and evaluation coding. That is, Saldana has developed an organized taxonomy of coding approaches that might be appropriate for different kinds of studies and research questions. And he gives us explicit guidance in selecting the right coding approach(es). By laying out and taxonomizing these coding approaches, Saldana allows us to see coding in a much more organized and expansive way than we might have when reading more restricted discussions of coding.

Chapter 3 comprises pp.58-186 of the book. It's an exhaustive discussion of each category, making this book more of a sourcebook than a discussion (much like Qualitative Data Analysis: A Methods Sourcebook).

Chapter 4 suggests what to do after first-cycle coding. It suggests performing "eclectic coding," a sort of open coding approach that "employs a select and compatible combination of two or more First Cycle coding methods" (p.188). After eclectic coding comes code mapping: listing the codes, categorizing them meaningfully, constructing major categories as moieties (group divisions), then phrasing the divisions in "versus" terms (pp.196-198). Code landscaping comes next: organizing and examining codes through basic approaches such as word clouds and outlining. Next, Saldana walks us through operational model diagramming, which depict processes in the data, and tabletop categories (i.e., affinity diagrams).

In Chapter 5, Saldana discusses second-cycle coding methods, which allow us to do further, more complex analytical work. These methods focus on Sources, Description, Applications, Example, Analysis, and Notes (p.207).

In the final chapter, Chapter 6, Saldana gives us strategies to pursue after second-cycle coding: focusing, theorizing, formatting, writing, ordering, networking, and mentorship.

If you're getting the idea that this sourcebook is essentially a portfolio or catalog of coding strategies, you're not wrong—and I'll likely turn to this book when I design my next research study. But it's also a meditation on what coding is, what it should do, and how it can furnish a stronger structure for one's analysis. If you conduct qualitative research, I strongly recommend it.

Reading :: The Collaborative Enterprise

The Collaborative Enterprise: Managing Speed and Complexity in Knowledge-Based Businesses
By Charles Heckscher

I read this book during the summer, but have been putting off reviewing it because I got so much from it—it seems as if every page has at least one sticky note on it. But it's time to discuss this book, which I found to be extremely useful for thinking through some of my recent case studies.

Heckscher came onto my radar when I read the book he coedited with Paul S. Adler, The Firm as a Collaborative Community. That book influenced me as I thought through work organization, and Hecksher's The Collaborative Enterprise, which was published a year later, extends those themes that I found so useful. Its focus is on "the power of extended collaboration," which "is the latest of a series of historical expansions of human abilities through an increase in the scope and richness of human interactions" (p.1). At this stage, "the problem at the leading edge of production is to combine knowledge and skills flexibly around changing tasks"—a problem that is not tackled well by markets or bureaucracies (p.1). At this point, "the challenge is mobilizing not effort but intelligence: to get people to use their particular knowledge and capacities in ways that continuously contribute to the success of the whole" (p.2).

Collaboration involves working with others toward a shared objective. As Heckscher puts it, collaboration involves “a shared objective that cannot be reached without the contribution of all. Thus it necessarily implies processes of dialogue and negotiation, of exchanges of views and sharing of information, of building from individual views toward a shared consensus” (2007, p.2). When we work together with others to define a project objective, when we develop a shared understanding of a problem, and when we find ways to make sure that everyone gains an advantage from our shared work, we are collaborating.

Collaboration isn't new—but until recently, "it required sharply bounded groups with enduring and homogeneous membership (p.3). Now, we can support extended collaboration, which represents a "quantum shift" in that specialists can come together briefly, rotate leadership among themselves, and flexibly adjust to changing projects (p.5). This is what interests Heckscher: the "collaborative enterprise," which is "collaboration that extends beyond the limits of permanent teams, units, or firms" (p.5). 

Collaboration contrasts with two other ways of seeing the enterprise: (1) one that centers on loyalty, long-term relationships, and diffuse commitments, typically hierarchical (p.9); and (2) one that centers on individuality and autonomy, usually expressed as a market or bureaucracy (p.11). Both work against collaboration, which demands that people hold dialogues across hierarchical levels and that they give up autonomy to "enter into each others' ways of seeing" (p.12). Yet collaboration is hard. Whereas markets and hierarchies "are simpler because they are highly restricted and simplified patterns of interaction," either restricting information (markets) or links (hierarchies) (p.13). Collaboration involves listing the restrictions on both. 

The seeds of collaboration rest even within the conventional hierarchies. Even though hierarchies formally restrict communication channels, they typically also have informal associational links (p.26), which cut across the hierarchy but which typically do not impute power to the association. This associational dimension is what becomes organized by the collaborative enterprise (p.28), which has the ability to create effective task teams—temporary, project-oriented, multispecialist teams—as needed (p.35).

As  Heckscher later argues, shifting to a project focus can support adaptive collaboration, focusing resources such as knowledge around focused problems; such organizations “reduce hierarchy considerably and emphasize project teams generated around opportunities. Size is not so important because this strategic approach narrows the focus to a small number of ‘core competencies’” (Heckscher 2007, p.63).

Such collaborative enterprises have different needs. For instance, Heckscher argues that “Mobility could be a good thing for employees as well as for companies if there were good systems in place for supporting mobile careers. These systems were unneeded in a bureaucratic order, but they are crucial now—and weak” (2007, p.272). Additionally, people in collaborative enterprises must be able to build “shared understandings and processes” by freely using the physical and service infrastructure to contact each other, collaborating via associational links without going through the levels of their organization’s bureaucratic hierarchy (Heckscher 2007, p.92). This collaborative infrastructure can and should be “deliberately managed” in larger enterprises (Heckscher 2007, p.92, 136). 

Yet, Heckscher adds, “there is no organized and systematic effort to build the infrastructure for mobile careers” (2007, p.190; cf. p.272). He sees these constraints on communications infrastructure—as well as other structures, such as benefits—as restrictors that may retard the development of collaborative enterprises.

If you've been following my readings or writings over the last few years, you can see how I'd be intrigued by Hecksher's work. This review only scratches the surface of this book, which is well argued, thorough, and thought-provoking. If you're even a little interested in the issues discussed here, check it out.

Presentation - All Edge: Exploring the New Workplace Networks

I just got back from speaking at the Austin Chamber of Commerce about how work is changing due to new information and communication technologies. Here's my presentation:

All Edge: Understanding the New Workplace Networks from Clay Spinuzzi