Read the Directions
I’d like to nominate the term "faculty-driven" as a candidate for disinvestment and elimination.
After serving as a director of composition and as the coordinator of a general education program at universities in the Midwest, I am beginning my second year as department head here at a university in West Texas. At our first all-faculty meeting of the year, it was announced that we are on the verge of two major academic initiatives that will require a substantial commitment of institutional time and energy. The first is a program review process, and the second is a quality enhancement project required by our accreditor.
Both of these efforts are necessary and, I suspect, will result in needed improvements. I have faith in the best practices upon which we will model our efforts. I also believe in the goodwill and good intentions of our academic leadership.
I just wish our administrative team would stop saying these efforts will be "faculty-driven." It’s a term that has little, if any, persuasive power. It may in fact, for many faculty, have the opposite effect. Rather than sweetening the pot, it may just as likely leave a bitter taste.
It's possible academic leaders inside higher ed believe that "faculty-driven" is synonymous with “shared governance” (another term I’d nominate for the trash bin) or "grassroots consensus-building." However, these terms only mask how power actually circulates in academe.
Let me be clear: I’m not opposed to how power functions in colleges and universities. I think the decision-making hierarchy in my university is appropriate and benefits faculty, staff, and students. And it’s quite evident who has authority and who doesn’t. Our operational policies tell the story of power and process quite well, and our organizational chart clearly illustrates the verticality of institutional authority.
I'm only saying that academic leaders should be more careful about how they talk about what we do. Faculty don’t drive processes that come down from accrediting agencies or the administration. They execute them. That’s why a better term is "faculty-executed."
Faculty members are directed to execute program review. Faculty are directed to execute a quality enhancement process. Faculty are directed to develop and assess student learning outcomes. Faculty are directed to appear at convocation and commencement. It may be that faculty don’t like to follow and execute these directives, but that’s really beside the point .
Let me share with you to the last two stanzas of a poem I like very much by William Stafford called “A Ritual to Read to Each Other.”
And so I appeal to a voice, to something shadowy,
a remote important region in all who talk:
though we could fool each other, we should consider --
lest the parade of our mutual life get lost in the dark.
For it is important that awake people be awake,
or a breaking line may discourage them back to sleep;
the signals we give -- yes or no, or maybe --
should be clear: the darkness around us is deep.
We may fool each other even when it’s not our intention. So we should take as much care as we can. We should use language that clearly depicts institutional power and its supporting policies and processes. And "faculty-driven" is a smudge.
If faculty drive anything, it’s student learning — the central ritual of any academic enterprise. Certainly, there's many an institutional directive that drive faculty away from that focus. But what drives faculty to distraction even more is language that misses the opportunity to do good work.
My preference is that academic leadership should talk straight about the parade of our mutual life. Leaders should tell faculty what they want faculty to do and, just as importantly, they should tell them why. And tell them often. Not fly-by mission statements and core values on overhead slides. But in public and in person, boots on the ground. Follow me. This way. Here we go.
I would also urge faculty to remind themselves of our larger enterprise more frequently. We can all make the easy case of how overworked we are. But we’re not running backhoes or bouncing along on the back of garbage trucks. We’re lucky enough to work in fields of our own choosing.
From my perspective, program review and enhancement projects offer us the opportunity to make the case for values and valuing, a chance not only to remind ourselves of why we do what we do, but also to remind others — especially those above us in the vertical leap — of our unique and vital contributions to the knowledge pie.
(And we should be beating that drum in our classrooms, too!)
Many faculty think they are undervalued or have no voice in the scheme of things. Why then would we resist a directive to tell our story? Otherwise, the line that threads through all we do may become loose, unravel, or, worse yet, break.
I believe very good and persuasive reasons often exist for why faculty should execute what we are directed to do. But there’s a difference between giving directives and giving directions. The first is a means; the second, an end. But they can be easily confused. And frequently are. When directives become ends in themselves, we lose our way in the dark.
Please take out the directions and read them again.
Laurence Musgrove is a professor and chair of English at Angelo State University, in San Angelo, Texas, where he teaches composition, literature, creative writing, graphic narrative, and visual thinking. His work has previously appeared in Inside Higher Ed, Southern Indiana Review, The Chronicle of Higher Education, Concho River Review and Journal for Expanded Perspectives on Learning. He blogs at www.theillustratedprofessor.com.