Elizabeth and I (and Jamie, and Gerry Van Gyn) were sitting in Finnerty's talking about the department's recent wrestling with the idea of a final exam in upper level courses. For some of us, if you don't know, this was a very painful and depressing and frustrating debate, so frustrating as to prompt talk of leaving the department, creating a break-away programme/department/club under a sort of separatist/sovereignty-association plan. Sounds like a lot of paperwork, I said. Wouldn't it be better if we could just come to some sort of a consensus?
(Now, I'm the last person to underestimate how much work it is to come to a consensus. I am a veteran of various social-justice organizations that, in the 80s, claimed to embrace consensus decision making. I know that the process involves long meetings, and coffee, and sometimes harsh words and other forms of heart-burning. But when it is done, everyone should feel "heard" (yes, in the "counselling" sense of the word), and some kind of way forward becomes apparent. So I think in some situations, it's worth the time.)
Our current decision-making processes are not conducive to the building of consensus. Simple majority votes in department meetings are obviously not consensus-building tools, and in fact tend to alienate and marginalize those who disagree. Committee assignments are a useful and important way to build consensus, but only when the committees are composed of colleagues who represent discordant and even violently opposed viewpoints. A committee that represents all shades of opinion on a topic, and works its way through to a recommendation, is one that builds friendship and community and morale; one that is composed of people already committed to a course of action is just a tool for wielding the power of the majority. This is a point that the committee on committees doesn't always grasp.
Many of the issues we address in department meetings are ones in which it is important to have everyone "on-board." That's because decisions we take as a group have to be implemented by members as individuals. We are all smart people, responsible researchers, conscientious teachers. How foolish do we look, as a department, when a senior, tenured colleague tells his students --"I think this form of evaluation is dumb, but I have to do it because the department says so?" And believe me, a lot of this sort of thing has been going on.
In our case, consensus might be built through a wider and less structured discussion of basic issues in our profession. For example--
What do we think, as individuals and as a department, of the usefulness of various techniques of student evaluation or the place of grammar in the curriculum?
What kind of process do we expect when we collaborate to set and mark PhD exams, or evaluate course proposals?
What if we discuss this sort of thing just for fun, when there's no motion on the floor and nothing in particular at stake?
I'm not suggested we make department decisions always by consensus (the Women's Studies department used to do this, and I understand it led to some marathon meetings). Rather, I'm suggesting we just discuss some of the presuppositions we bring to our classrooms, our department meetings, and our work for the university as a whole. And that's what this blog is for.
No comments:
Post a Comment