A Five-question Series

⏳ Approximate reading time: 3 mins

The latest bulletin from The Common Table reached subscribers last Wednesday, May 29, this time announcing an article titled “Food Thinking.” The article’s premises were inviting, in that it works across a few theoretical beacons, Anna Tsing, Horst Rittel, and Anthony Dunne and Fiona Raby, to expand the thesis that food studies is suited to dusting off design thinking, reviving again those dimensions of design thinking that have worn thin or blinked out. You’ll find good stuff there, worthy of reading and worthy of returns, on mindsets, or questioning attitudes; with such practiced, inquisitive dispositions follows something almost ritualistic in noticing taken-for-granted interdependencies, in a feel for the organism, whether the corn plant or the baby bok choy leafing dark green hopeful from the raised beds where we planted them in mid-May. I don’t quite identify with design powerfully enough to prefer that same language (or field of specialization), but I did read in this piece something akin to a foodwise network sense, an atoll whose cartographic attempts I imagine would be delicious and intriguing at once. And this, in turn, relayed me to look around at more of The Common Table, to explore a few of the other recently published pieces beyond “Mother’s Hand Taste,” the piece on Jiwon Woo’s ever-fascinating work about son-mat, which I wrote about a few months ago and also explored in the spring semester with students who were taking Food Writing.

There is much to admire, appreciate, and learn from at The Common Table. I found especially standout the series “On Food and Education,” which follows the pattern of five-question interviews. The five questions invite responses from a host of respondents, and each is featured in elegant, readable posts, organized with the questions as the governing structure. The five questions are

  • How would you explain your perception of food as an educational discipline or tool to someone who might think that means just cookery lessons?
  • What are you doing/have you done to change understanding related to food?
  • Who are you trying to reach and teach and why?
  • Where would you like to take your work in this field; what are your goals?
  • What is the big-picture perspective in terms of the future of food education and where is it coming from?

The repeating pattern causes me to find the series more inviting as a series; there is so much good stuff here. It got me thinking, too, and again, about the substitutive interplays with food, writing, and visuality, about how this interviewing format, because it is simple and consistent, coheres multiple responses and fashions them into a genre unto itself. Semi-structured, multi-phase interviews have, as I conceive of them, ascended as the interview method that has the best chance of summoning in-depth perspectives, yet these strictly structured, one-phase interviews, like we find in The Common Table‘s series, offer just as much for the researching writer’s repertoire. I suspect that part of what explains my quiet, unchecked bias in favor of semi-structured interviews is that academic publications rarely publish in plain view the uncut and unfiltered responses from interviewees. This is a meandering way of expressing my own realization that the value of the strictly structured interviews has been skewed by wading too deep for too long in academically styled prose. What would a five-question series on writing be? Or visuality? What would the questions be? Who would be the interviewees?

So many pieces in the five-question series prompt new ideas and invite thoughtful responses, such that it is hard to choose one as a paragon, though I suppose “On Food and Education: Marije Vogelzang” rises to the top because I have already bookmarked it for a future section of Food Writing. Her response to the first question strikes connection with our lesson on apple and orange mindfulness, the day when, with Thich Nhat Hanh’s guidance, we linger, slowing down with a piece of fruit to listen for the crunch or to test edges as we pull a Mandarin orange apart, segment by segment. Vogelzang’s lists are rangy and uncanny, playful but not self-consciously so. I love this as a model for the inventional copia generated from something simple, ordinary, everyday. That this piece strikes in so many directions—and all from the repeating five-questions—is why I am holding onto it, tagging it for returns in my teaching, my writing, and my glimpsing thoughts for what would one day be a striking feature in a rhet/comp journal, perhaps.

Wicked and Tame

⏳ Approximate reading time: 3 mins

This afternoon I finished re-reading Selber’s Multiliteracies for a Digital Age (2004), which we’ve picked up in ENGL516 for its tightly applicable yet expansive heuristic: functional, critical, and rhetorical literacies. For Tuesday we’re also looking at a complementary tier, network literacy. There’s not a lot I want to recount or highlight about the Multiliteracies book in general this time through, but one specific section drew me in more this time than when I first read the book a few years ago.

Under rhetorical literacy, the section on deliberation (152), Selber refers to a 1973 article by Horst Rittel and Melvin Webber, “Dilemmas in a General Theory of Planning.” Both professors at Cal-Berkeley, Rittel (Science of Design) and Webber (City Planning) differentiate between wicked problems and tame problems. Selber summarizes their position this way:

Although tame problems can be enormously complex, their complexities are largely technical in character, as are their solutions. In contrast, wicked problems are more intractable in that wicked problems do not have single solutions, only interim and imperfect solutions. Adjustments in tax rates, changes in school curricula, procedures to reduce crime–these problems can all be understood, addressed, and resolved in countless ways because there are elusive social dimensions that muddy the causal waters. (153)

Selber continues for another page or two to apply the wicked/tame distinction to challenges facing interface designers. That design planning and implementation is wicked, not tame, reminds us of the important limitations of technical rationalism for addressing situated social problems at a variety of scales (e.g., poverty to usability). I am inclined to accept the proposition that follows for Selber, which is that deliberation ensures a humanistic perspective in response to HCI challenges. Among questions that remains for me, I still wonder after tracking down and reading the Rittel and Webber article whether deliberation makes a wicked problem less wicked. In other words, what does deliberation do to the problem? Does it make it appear more tame? Does it blunt (or defer) its wickedness? I find it easy to value deliberation, but I wonder whether deliberation sometimes seduces us to conceiving of wicked problems as tame.

To enlarge the context–and with it these questions–a bit further, here is one point when Rittel and Webber compare tame and wicked problems:

The problems that scientists and engineers have usually focused upon are mostly “tame” or “benign” ones. As an example, consider a problem of mathematics, such
as solving an equation; or the task of an organic chemist in analyzing the structure
of some unknown compound; or that of the chessplayer attempting to accomplish
checkmate in five moves. For each the mission is clear. It is clear, in turn, whether or
not the problems have been solved.
Wicked problems, in contrast, have neither of these clarifying traits; and they
include nearly all public policy issues–whether the question concerns the location
of a freeway, the adjustment of a tax rate, the modification of school curricula, or the
confrontation of crime. (160)

They also say that wicked problems are notoriously difficult to “define” and “locate” (159). Perhaps this is what deliberation increases–our means of defining and locating problems, of sorting out “what distinguishes an observed condition from a desired condition” and “finding where in the complex causal networks the trouble really lies” (159). Curriculum, which both sources list, is a fine example. But so is just about any composing situation, isn’t it? Writing and rhetoric strike me as deeply, constantly, willingly entrenched in wicked problems, and perhaps only in reductive notions of techne and in formulism do we find disappointing instances of writing-understood-as-tame(d).

For a closely related thought-exercise, I scraped from the Rittel and Webber article the ten traits they assign to wicked problems. Selber draws correspondences between the first three and interface design problems, which profit “from a more rhetorical and less rational view of things” (154). Others on down the list might prove more difficult to align with interface design, specifically, but they do match up intriguingly with other problems encountered by writers.

  1. “There is no definitive formulation of a wicked problem” (161)
  2. “Wicked problems have no stopping rule” (162)
  3. “Solutions to wicked problems are not true-or-false, but good-and-bad” (162)
  4. “There is no immediate and no ultimate test of a solution to a wicked problem” (163)
  5. “Every solution to a wicked problem is a ‘one-shot operation’; because there is no opportunity to learn by trial-and-error, every attempt counts significantly” (163)
  6. “Wicked problems do not have an enumerable (or an exhaustively describable) set of potential solutions, nor is there a well-described set of permissible operations that may be incorporated into the plan” (164)
  7. “Every wicked problem is essentially unique” (164)
  8. “Every wicked problem can be considered to be a symptom of another problem” (165)
  9. “The existence of a discrepancy representing a wicked problem can be explained in numerous ways. The choice of explanation determines the nature of the problem’s resolution” (166)
  10. “The planner has no right to be wrong” (166)

The original article is worth a read, particularly for the way they elaborate each of these qualities of wicked problems. The degree of overlap between composing problems and wicked problems piles up, making this both a theory of problems/planning worth returning to and one I wished I’d noticed (and also deliberated) more fully a long time ago.