Jeffery Harvey

So, yes...it's a textbook. On qualitative research, at that.

But I still enjoyed it.

I enjoy qualitative research. It's not that I am "for" it at the expensive of the quantitative work, it's just that I believe qualitative research can provide the context that's necessary for really understanding phenomena. Merriam and Tisdell's text is a functional introduction to qualitative research full of helpful advice, graphics, and samples. As the authors note, there is no substitute for getting into the field and doing some qualitative research. Still, having a reference or two on the shelf is handy when it comes time to check one's assumptions.

My thoughts on this one are complicated.

By happenstance, I read it when the story was set, and in one case, I read a journal entry on the day the main character "entered" it.

I'm typically not a science fiction or post-apocalyptic literature fan, though I'm a sucker for a good story. I'm not sure the story is here, though the development of the Lauren Olamina character is rich and layered. I wanted more of that from some other characters, but I get this is the first of two in a series (and, from what I read, potentially was the first of three before Butler's untimely passing). There are eerie elements that read like prognostications on Butler's part, and while one can still hold hope that things won't get that bad, it's not hard to see how it could.

I also have trouble reading novels structured as vignettes, journal entries, flashes, etc. I find myself being lost in the details, trying to remember every little thing on the off chance they're foreshadows for something down the road. Oddly, though, I find the pace of novels structured as such to be too fast for absorption. So, yes, this paragraph definitely describes a "me thing," but I need to make note of it in my review.

One might think that this is a negative review, but as I said, it's complicated. I couldn't put the book down; when I would, I had to force myself to not "just go one more page." I found myself really enjoying the Earthseed verses, and I would have been interested in Lauren's reflection on them. How did she wrestle with the concepts and the language? As the narrator, Lauren notes that she revised them substantially. As such, I would have enjoyed seeing earlier "drafts," or possibly even recreations of the handwritten journal pages as images to see some of the scribbles that we all make when revising our work.

The writer of the afterward shared similar reflections. She said it took her three tries to really dig the book on a personal level. Maybe I'm like that. If so, I'm game for a re-read down the line.

I found my copy of On Language when cleaning out a closet. I purchased it in 2001 while with my wife on our honeymoon. At that time, I had grand designs on a master's degree in linguistics that progressed, but never completely panned out.

Still, I am a lover of language and finding this one all dusty at the bottom of a closet was like getting a gift.

It takes me a bit to get back into the swing of Chomsky's writing because he has a bit of snark that is simultaneously engaging and off-putting. The one thing that snark does do, though, is makes reading this feel like being in a conversation. Speaking of conversation, I found the Language and Responsibility section to be the more enjoyable of the two books under this one cover. The interview elements between Chomsky and Ronat ebbed and flowed, focusing on language but not being afraid to touch on numerous other subjects. It was organic and informative (and much faster to read).

I enjoyed the Reflections on Language section, but if I'm being honest, I could take or leave the final chapter. I appreciated the insights and the details, but there were times when the writing felt like a tired man yelling at clouds. I should qualify that statement. Much of the issue was my own unfamiliarity with the writings of the authors to whom Chomsky was responding. I recognize that if (a) I was a working linguist in the 1970s and 1980s or (b) I was more educated and active in the contemporary world of linguistics, these arguments would be more accessible to me. As such, that qualifier is critical. I also recognize that I'm reading a volume that was responsive to the current discourse at the time of its publication 50 years after its original publication - another critical qualifier.

Finally, I want to acknowledge how much I enjoyed reading this through the lens of what has become my academic and professional career. At the time of this review - i.e., early 2025 - I am reading a lot of literature about discursive leadership. The sections of Chomsky's interview with Ronat where they discussed Foucault were fascinating to read against that backdrop, knowing what I've come to understand about (D)iscourse. Thinking of communication (broadly) and its effects on leadership while deconstructing the structure of the language forming "communication" was a fruitful mental exercise. Poet Irene McKinney once wrote something like, "Why should the worm care what it eats?" in a poem called Fodder. I love that poem because it captures the mindset of the bookworm (pun intended). When we read, we can't help but relativize the content to our unfolding experience. Diving into the structure of language, as a tool for communication, which is so important to the act of leading...that's what made my brain smile.

I have read about adaptive leadership for some time, which includes summaries of it, studies based on it, etc. It only made sense to go back and read the seminal work.

I enjoyed Heifetz's book. I am glad to see that, over time, the five "steps" of adaptive leadership have been given empirical attention because, at a basic level (and once one accepts the premise that adaptive challenges are those that require leadership while all others require management or technical solutions), they are intuitive. In particular, it's difficult to "identify the adaptive challenge," and I'm reminded of the readings and reflections I've done on discursive modes of leadership. There's a wonderful opportunity to utilize discursive tools to defined the adaptive challenge. "Give the work back to the people" also resonates with me. As defined herein, there is some ambiguity, but generally getting a team to align behind a challenge and work - participatively - toward a resolution are elements of leadership, broadly defined (and well beyond just the work of "adaptive leadership").

I often have a weird feeling when reading a book from before that is filled with real-life examples featuring actors whose futures we know. This book appeared in 1994, and I can't help but read the passages on President Carter without knowing about his time from the 90s to the recent present. This book does not fall victim to the fate of a book like Collin's Good to Great because of the future performance of featured firms, but I felt similar in reading it.

My explorations of adaptive leadership are not done. I'll read Heifetz's follow-up, and I'll continue reading more empirical considerations of the adaptive style. My interests ensure that I'll consider adaptive leadership through a discursive lens.

After a long time and much gnashing of teeth, I come to the end of The Brothers Karamazov. My thoughts on it are complicated.

Do I find this one worthy of its "classic" status? No, not really. Yet, I recognize that I am not well versed on the Russian history I imagine Dostoevsky integrates through conversations between characters, references to other parts of the country, or even satirically. Maybe there really is more going on with it.

I find long passages and tangents unnecessary. The centrality of Father Zossima, followed, after the monk's death, Ilusha, are examples. They are interesting, but they drag the pace of the novel down to excruciatingly slow. This book is at its best in the scenes where the investigators question Mitya and even Book 12 as the trial unfolds.

The narrator's voice also confounds me. It is an external voice, and I am comfortable with that. As the novel progresses, though, the narrator becomes more and more capable of interpreting the thoughts of the characters. For me, it is jarring, and it pulls me away from thinking of the narrator as someone else that resides in their town.

Still, though, I find myself glad to have read it. It came to me as a title on a "100 books to read" list, and I'll readily admit that I would not have otherwise picked it up. My goal by working through said list was exactly that: to pick up books I otherwise would have no reason to want to read. It brings to mind how limited our (i.e., the western mindset of the U.S.) understanding of pre-Soviet Russian history is. I also find myself reflecting on the image of Dostoevsky portrayed by friends and family. The writing is not miserable. The story itself (and the accompanying storytelling) were not terrible. I can see where he could have a tendency to dive into period-specific Russian context, that is, commentary on those events that were current and widely-known at the time the novel was published. Familiarizing oneself with that history could be helpful, but a heavy lift for the casual reader.

I enjoyed this text immensely. Long before undertaking graduate study in strategic and executive leadership, I studied linguistics. I've always been a fan of language, and the first 20 years of my career saw that fandom evolve into being a fan of the many uses of language. That, in a nutshell, is why discursive leadership piqued my interest. I've read several of Fairhurst's article on the framing, communications, discourse, and organizational discourse analysis (ODA), so I was excited to dive into this volume.

It did not disappoint. Fairhurst does a great job of making the abstract accessible, primarily through example. Her extended use of the Officer Conway example, for instance, helps the reader to not only understand the initial idea, but also to build on that understanding ("setting it," so to speak). The work is thoroughly cited, leaving the readers with an interest with a trove of future readings.

The tone of this book, though, is the star. When I work with my students, there's an implicit, albeit misguided, understanding that theories of (or approaches to) leadership replace one another chronologically. Framing the discursive approach as a stand-alone concept OR a complement to leadership psychology study was insightful and skillful. I find myself thinking about certain approaches as "what leadership is" and others as "how leadership happens." I try to convey that to students (with, admittedly mixed results), yet the way Fairhurst approaches that conversation in the opening and concluding chapters of this text give me new ways of going into it with future students.

This review was written right after finishing the text. I journaled along the way, jotting down general notes, connection to various research projects of my own, and insightful passages. I'll go through those in due time. But for now, my first blush of this one is a strong recommendation to anyone who is interested in the communicative aspects of leadership or how leadership happens.

For years, I'd have students come into my doctoral classes eager to cite Northouse. I had read scanned snippets of earlier versions, but I set about to read the latest version I could find cover to cover. From a content standpoint, it did not disappoint. Northouse provides an introduction to a range of leadership theories, and the consistent structure of the chapters, though a tad dry, is effective at giving readers comparative points for the theories/approaches included. The book was a dense read, but it was not a hard read. Each chapter took me about an hour, give or take just a few minutes.

The only chapter with which I'd quibble regarding content was the final one of team leadership (contributed by a guest author). I have studied shared and distributed leadership, and I found that chapter to be a bit limiting because of an over-reliance on process. I fully admit that the chapter focused on team leadership rather than shared or distributed leadership. Thus, the structure related to the work team context. Still, there were some passages that tried to integrate shared and distributed leadership into the team context, and I did not feel the author was as successful as she could have been.

The reason this book did not receive a five-star rating from me is its publishing. It's a Sage book, and I have always found Sage to be a quality publisher with solid editing. Yet, this edition was littered with typos and mistakes, ranging from missing spaces between words to obvious misspellings in section headings (e.g., "Inclusjve" instead of "Inclusive"). If this is the direction in which Sage is heading, it will soon find itself knocked off its pedestal as a quality publisher of leadership and management texts.