Category Archives: Writing

Fieldnotes and Observation Logs

QUESTION: What’s the difference between an observation fieldnote and an observation log?

ANSWER:

FIELDNOTES typically provide as much detail as possible about everything that might be of interest to the researcher, now and in the future. They are typically narrative in form and somewhat discursive, but the focus is on what the researcher can see and hear in the field setting. They can also include reflections by the researcher about the setting and about topics or issues that come to mind in response to what the researcher sees and hears. But the emphasis is on the concrete, specific details about the field setting, actors, activities, events, and contexts–all of this tied tightly to what can be seen and heard. The research ideal is to separate these visible and audible sense data/recordings from inferences, speculation and conjecture by the researcher about what “things mean” or “portend.”

FIELD OBSERVATION LOGS provide an abbreviated and somewhat abstracted account or record of what was observed in a field setting. There’s much less detail than in a full set of fieldnotes, but perhaps a bit more structure. A common logging strategy is to link brief descriptions, comments, notes, or quotes to a timeline for an activity being observed. If the notes and descriptions were extensive, specific and very detailed, that would be considered a fieldnote. If they were brief, more general and much less detailed, that would be considered a log. But a key difference here is that fieldnotes, by definition, include much more information but take twice as much time to prepare as a log. And a log has less information but also takes half the time to prepare as a useful set of fieldnotes.

QUESTION: Can you say this more simply or in a way that someone who has never done either might understand?

ANSWER:  I can try, but the more understandable answer might also be more complex:

Let’s say that culture and social life is something like a huge swirling mishmash of millions of movies, all going on at the same time. You’re a researcher who is interested in some aspect of culture and social life, and when you ask your professor how to study the feature you’re interested in, he points you to the entire mishmash and says something like, “If you really want to understand that feature, you need to take a look at all of these movies and tell me what’s going on out there. And if you want me to believe you, you’ll have to provide not only lots of specifics but also an account of which movies you saw all the way through and which ones you skipped, just glanced at or only read about.”

Now, that might stimulate a little panic because it all seems absolutely overwhelming, but you want to learn how to do this kind of thing, so you plunge in and watch one of those millions of movies and try to pay attention and take notes about everything that you can notice while watching that one movie. And when the movie is over, you look over your notes and see words and phrases and a few sentences, a lot of which need some further explanation. And when you start filling in that explanation you remember more details about the movie you just saw–details that you had not included in your notes at the time, but that now seem at least as interesting or important as the things you did include–and by the time you’ve expanded, edited, formatted and cleaned up this material so that it’s clear enough for someone else to follow, you’ve spent more time on your notes than you did watching the original movie. Whew!

You do the same for another movie and then another. But after spending an average of 2-3 hours of writing afterwards for every  hour of film you’ve been watching, you’re exhausted–not only by how much work it takes to do something like this but also about how overwhelming it would be to try to provide detailed accounts of this sort of the many, many movies related to the “feature” you’re interested in.

So, you say to yourself, “This is impossible. I’m not going to look at any more movies. I’ll just just use the three (or five, or twenty) I’ve seen so far and wrote up in lots of detail and go with that.” But when you check in with your professor about that, she says, “Oh dear, that won’t do! If the feature you’re interested in is manifest in many different kinds of movies, you’ll need to look at many different kinds of movies, not just the ones you’ve done so far.”

Your panic comes back, but the professor is not a sadist and really does want you to succeed (which is true!), so she says: “Look you’ve got some good, detailed notes of several movies, with lots of specifics and rich descriptions. So let’s shift the focus a bit and see how these movies “compare” to some other movies that you have not yet seen. And just to make the task  more manageable, let’s cut back on how much time you spend writing up your observations, from two hours for every hour of film to an hour or somewhat less for every hour of film. Deal?”

Well, it still sounds like a LOT of work. And it IS! Even if it’s half of what you started out to do, there are still lots of movies and that means lots of time spent watching movies. But if you just watch them and don’t take notes, they’ll start blurring together and then they’ll be difficult to compare and that will reduce the significance of the ones for which you already have detailed notes.

What to do!  Well, maybe you could come up with some kind of short-hand, or summary or. . . I know, a “LOG” of each film!  . . . that would focus on some key features and include some context and basic elements but be shorter and quicker to prepare. Something you could read and analyze at a later date in connection with logs of all the other movies you’ll have to see if you want to conduct a credible study.

QUESTION: So a log is a kind of short-cut to taking fieldnotes, and fieldnotes are a kind of expanded version of a log?

ANSWER: Yes, and each has all the strengths and weaknesses you’d expect. As with other short-cuts, you can also get lost pretty quickly if you’re unfamiliar with the area, so it’s best to start with fieldnotes. Depending on the kind of study you’re doing, it may also be best to stay with fieldnotes the whole way through. Many people do!

 

Turning Big Projects into Little Chunks

Some years back I prepared a chart to keep a book-length research and writing project from overwhelming me. Each row represented one chapter the book in progress, with the working chapter title/theme on the far left. Each column represented a research or writing “step” towards completing the chapter defined by that row, and the writing steps were framed as different kinds of “chunks.” Some chunk titles represented topics, themes or arguments that I would need to write from scratch; others referred to parts of manuscripts I’d already written (as notes, parts of other draft articles, or publications); and still others referred to works by other scholars that I planned to examine as a central feature of the chapter. The cells in any one row read from left to right as a series of incremental steps for completing a chapter, so there was always one “next step” to do for that chapter until the chapter itself was done. You can see a copy of how this table looked at about the half-way point here:
Writing Themes/Chunks Matrix

Before setting up this kind of chart (as I’d typically done with previous projects), I had developed an outline for the book project—as a study of efforts by teachers to develop shared standards in a feeder school cluster–and started developing separate outlines for individual chapters. However, when trying to write from the chapter outlines, I frequently got too deep into issues tangential to that chapter but still important to the overall book. At some point, I’d step back, pull a tangential “chunk” out of the chapter I was working on and set it aside so I could push ahead with the chapter. But it was hard to keep track of the chunks I was pulling out without attaching them to another part of the outline, and they might not be developed fully enough for me to see where they could best fit. Not only that, but the research and writing for this project took place over several years. On more than one occasion, I’d start writing a section of a chapter from scratch then find a chunk I’d already written that covered the same content. A messy way to work, and very inefficient!

One way of thinking about the challenges I faced was that the various outlines, notes and chunks I was preparing did not enable me to “see” what I’d done and what needed doing. This was important for a couple of reasons: First, if I couldn’t “see” the whole project, I could get confused or bewildered about how best to move it forward. Second, without that kind of overall vision, I could get demoralized by long lists of work that remained to be done.

I remember reading once that the author John McPhee used 3×5 cards tacked or taped to the wall to organize essays and books he was working on, and I thought about giving that a try. [I just noticed that the New Yorker of Jan 7th (2013) has a new piece by McPhee about how his books and essays are organized!]. However, I’m kind of a matrix-head, so I chose instead to convert my various file folders of chapter outlines, notes, draft book outlines and work lists into a single table.

Preparing the table helped me articulate the how the concepts, organization, and tasks of writing this book might fall together. As something of a surprise, it also provided me with a nice balance of options and constraints for moving ahead. As long as I was moving from left to right in at least one of the rows, I was moving ahead with getting the book done. But if I got stuck on that particular row, or needed a break, I could also look up or down a row and find something else to work on—something that was also helping to get the book done. By turning the outlines and work plan entries for the book into research and writing chunks I could see on the grid, I could also play with the idea of moving a chunk from one chapter to another, or revising chapter titles to better reflect the chunks listed farther out along that row.

Of course, the topics, chunks and table itself were always provisional. But preparing this as a MS Word document, I could revise as I went along, coloring in cells/steps/chunks when I finished them, or highlighting a few steps from different columns and rows as my top priorities for getting the whole shebang done and out the door. By printing out and keeping copies of the table from time to time, I also documented how my thinking about the book changed as I worked on it.

These were all positive outcomes of creating the table, and I don’t remember any negatives. But I must confess that this particular project was never finished—at least not in the book form represented by the table I’ve displayed here, though that’s not the table’s fault. At a point right about where this version was current, I got caught up in a couple of other big projects and had to set this one aside. By the time those other projects were wrapped up, six or seven years had gone by. I really enjoyed the other projects and felt quite good about the work I put into them and what came out of that—but I haven’t yet abandoned the book represented by this table, which, by my reckoning is about half done. What’s interesting to me now is that almost a decade later, the table still provides a relatively precise picture of what it will take to finish off the other half, which is something I’m heading into now.

Beyond the specifics of this particular project, using some sort of table like this to organize little chunks of big projects has become an attractive routine for me in many other research and writing projects, and in designing courses I teach as well. But in the last few years I’ve also shifted somewhat from tables to databases—FileMaker Pro in particular. In the database approach, each “chunk” becomes a record that can be labeled by values from one or more fields. That opens up prospects for a lot more links between chunks than will fit well in a table. Some chunks, for example, may appear useful for more than one chapter or more than one book. “Seeing” that through a database can be useful in working across projects, and it’s also a tool for rethinking the broader significance of an individual chunk, including how that reflects back on my own intellectual growth—or lack thereof.

Reflections of this sort are interesting enough to keep me occupied from time to time, but I do also want to get a few things done, not just figure out how to do them! So at some point it’s time to stop organizing the organizing tools and do some writing. After all, what good is a matrix or database for visualizing chunks of writing if you don’t have any chunks of writing you need to visualize!