BlogU

  • Speaking on Behalf of...

    By Dean Dad October 7, 2009 11:09 pm

    A little while back I was involved in a meeting at which a relatively contentious issue was debated. One person prefaced her statement with something along the lines of “the such-and-such committee has discussed this, and passed a motion saying x. I'm just here to convey that.” I took issue with x, and gave my reasons. She took umbrage at my answer, and responded that “well, I'm just conveying the message, and I think that ought to be respected.”

    I don't know what “respect” means in that sentence.

    It could mean “obeyed,” but that conveys a serious lack of respect for the larger group. It could mean “held immune from criticism,” but that actually means either “obeyed” or “ignored.” I guess it could mean “considered,” but how you consider something without evaluating it is honestly beyond me.

    (If I were an abrasive jerk, I suppose it could refer to demeanor. I'll just ask the reader to trust that my demeanor was civil.)

    Moments like these are why I get impatient with the advocate/constituent model of meetings or decisionmaking. (For those keeping score at home, I'm siding with 'trustee' representation over 'delegate' representation.) Someone who feels bound to represent the Final Word of a given group has no real ability to compromise or to engage others in meaningful discussion about it; the Word is the Word, end of story.

    But the real work of decisionmaking isn't just smashing people into each other and seeing who wins. It's about finding solutions that allow for the best considerations behind the various positions to find expression, even if not in the form originally imagined. It's about discerning the difference between 'spirit' and 'letter,' and being willing to sacrifice the latter for the former. But you can only do that if you're able to move beyond “I've said what I've said and that's what I've said.” You can only do that if you own your words enough to change them.

    When confronted with “I've said what the group had to say, and that's that,” I feel like the meeting has been hijacked. Now it's not about whether x or y or some variation is the best idea; it's about the relative standing of the group that issued the dictat. Instead of solving problems, we're dealing with internal politics and wounded egos. At best, it's distracting. At worst, it leads to decisions made for all the wrong reasons.

    I've seen a variation on this theme in customer service situations way too many times. A policy is enacted for a particular reason. The front-line people don't know the reason; they're just directed to enforce the policy. So a policy gets forced onto a situation where it makes no sense. The front-line people don't 'own' the policy in any meaningful way, so they don't feel entitled to make judgment calls, no matter how obvious they might seem.

    Wise and worldly readers -- have you found a graceful way around this?

Advertisement

Comments on Speaking on Behalf of...

  • What "ought to be respected"
  • Posted by Cecelia Munzenmaier , Adjunct at Kaplan University, Des Moines Campus on October 8, 2009 at 7:30am EDT
  • Perhaps the spokesperson was declaring herself to be just a messenger and asking that her noncombatant status be respected. Her response did cut off discussion, so you need a way to pursue the issue while keeping her out of the line of fire. One response might be "I understand that Group X's position is... Who could explain the reasons behind that position to me?" Another would be to have the meeting leader set a policy that whoever states a group's position should be prepared to provide a rationale and to carry feedback from those at the meeting back to the group. As an adjunct, I don't have to sit through a lot of faculty meetings, so that policy may be unrealistic. However, the dodge only works as long as people who use it are allowed to assume that being a messenger fulfills their role as delegate. John F. Kennedy's _Profiles in Courage_ argues eloquently against that position.

  • Posted by Andy , VPAA on October 8, 2009 at 9:15am EDT
  • This is an area where I could certainly use some guidance. This happens frequently with constituent groups, and the unsaid message truly is that "respect = obey". If we don't do what they want, we don't respect them, or worse yet, we haven't heard them. However, the opposite is really true. We are ready, willing and able to have discourse. I like the idea from the previous comment about bringing rationale to the meeting, that would go a long way to understanding an issue. In the long run, some of the best ideas come from the constituencies and I don't want to shut off creativity or their willingness to share ideas, but I also have boundaries or constraints within which I am required to work, and not all ideas are doable.

  • Posted by Jason on October 8, 2009 at 10:15am EDT
  • This type of approach appears often when serious debates arise about changes to current practices, new initiatives and, of course, financial matters. I find it helpful to start with a polite acknowledgment of then a few questions that help to redirect the dialogue back to the larger charge or priority debate. "As ______ notes, there are strong positions about this matter. As we work to [recommend difficult cuts / reposition the program / institute meaningful services that advance student learning], we must consider evidence, recommendations and the practical implications of any decision. Given this, _______ please share/send us details that led to this position. We will all do the same in advance of our meetings so that we may be able to engage in a critical dialogue before reaching a final decision."

    Part of the reason this behavior exists is that too often the concept of shared governance is misunderstood. While there must exist open and transparent means for the conveyance of ideas, the ultimate decisions come from those charged with making them. I find that when the following understanding exists, there are fewer turf wars or protectionist battles.

    1. There is a clear understanding that X really does want to know and will seriously consider ideas/recommendations
    2. X will evidence this to you/your group
    3. It is understood that X makes the final decision

  • Hierarchy
  • Posted by Eric Gates , Sr. Consultant at ALEKS Corporation on October 8, 2009 at 11:45am EDT
  • Dear Dean Dad,

    As it happens, I AM a jerk.

    And, I have the ironic priveledge of seeing academia from the inside, while being an outsider.

    To put it mildly, you guys are funny, and you make my tummy jiggle with laughter.

    but this is a serious business, educating children, so the laughter often hardens into first ironic distance, and, later, when I think about it, anger.

    You see, the inmates run the asylum in most academic institutions. This is a result of the PhD. and tenure.

    A PhD is not a license to foul up the works with your petty, ill-considered, pointless turf-battle stupidity.

    A Phd IS (especially at a community college where teaching is the sum total and entire point) a license to continue raising the often half finished children and adults who show up seeking knowledge, skills, wisdom, and a piece of paper.

    Nothing more.

    So, you need what we have in the real world--A BOSS!

    My advice? Be the boss. Make your mistakes. Live with them. But streamline the process with a simple hierarchy. For those uninitiated by military training, it goes like this (publicly messing with or challenging anyone above you in this hierarchy without significant cause can get you in BIG trouble):

    General (That's the President)

    Colonel (That's the VP of Academic Affairs)

    Major (Is that you, Dean Dad?)

    Captain (That's a Serious, successful, cooperative, smart, helpful, concerned faculty person, it is hard won, and not conferred automatically through Time in Service)

    Lieutenant (this is Jr. Faculty)

    Washout (that's someone who dares gum up the works at an important institution with a critical mission....screw these people, Seriously)

    See, and then the juniors DEFER to the seniors. BUT they are allowed to (privately and face-to-face) criticize and question authority, carefully, thoughtfully, and only when necessary...this is not a just-for-fun-because-I'm-bored- and-anyway-I-have-tenure type of thing.

    However, PUBLICLY and GLEEFULLY criticising your superiors results in immediate, severe correction.

    Hi Tallyrand...I bet you like meetings.

    Eric Gates
    Sr. Consultant
    ALEKS Corporation

  • Posted by talleyrand on October 8, 2009 at 2:30pm EDT
  • Somebody remind me not to hire the ALEKS Corporation to work with us on assessment or governance matters.

    On the other hand, I expect I'll remember on my own.

  • R-E-S-P-E-C-T
  • Posted by Mike , asst prof English at community college on October 8, 2009 at 2:30pm EDT
  • I think the committee member in question wants to make sure that the work of that committee is considered in whatever final decision gets made.

    The real problem actually arose before the meeting in question--a committee was created (intentional passive) to tackle some issue, and the committee created a solution or policy statement or whatever--it did, in short, its job. And this took effort and time and some intellectual ledgerdemain to bring forth whatever was brought forth. Now that committee feels its work was for naught--if whatever it developed was ignored/steamrollered/trumped by executive fiat rather than by the same deliberative process used by that committee. If echelons above the committee felt the committee's work would be trumped, etc., those same echelons shouldn't have created it in the first place. And if committees come up with answers, etc., that are unexpected by the hierarchy, then the hierarchy hasn't thought through what it really wants. Other posters have offered very useful ways, it seems to me, to include "respect" for the process and outcomes in future deliberations. But the bosses should have anticpated possible outcomes from committees ahead of time, and been prepared to accept those.

    The military analogue is an interesting one. I'm a retired Army officer teaching full-time in a community college, and find the two worlds not really very different at all. Most serious work in the service is committee work--the only difference is that a committee in the service can propose a solution and a commander can simply disregard its work--but then be prepared to suffer any adverse consequences if his or her decision to override is wrong. In academic life, accountability is much less clear-cut.

    My years in the Pentagon were actually extremely useful preparation for academic life; in that environment particularly, hierarchy is even less important. Consensus is absolutely vital because there are so many moving parts to an organization operating in 140 countries and with zillions of internal constituencies. No one peson can possibly keep track of them all, so committee work is the only way to get advice and ideas from other folks. And a really good committee will make recommendations to the boss that channel the decision into a relatively narrow band of options--the committee, in effect, decides for the decider. And really good bosses know that, and grant their subordinates (or committees) the power to decide for them.

    Maybe the lesson for Dean Dad and his colleagues is to be careful when delegating authority; one cannot empower only to listen when the response is convenient.

  • Finding Solutions
  • Posted by Derick Bonewitz , Adjunct Instructor, ESL on October 8, 2009 at 3:30pm EDT
  • I like your approach to finding solutions. In contentious situations, I try to have people write down (i) want they want and (ii) what they're willing to live with.

  • Trustee vs delegate
  • Posted by Kathy at NowhereU on October 9, 2009 at 9:30am EDT
  • In many years of academic committee work, both standing and ad hoc groups, members confusion about their role frequently caused friction. As a committee chair, I always found it useful to clear this up early in any process: were the participants only there as respresentatives of a specific constituency or group--thus limited in their ability to contribute and come to agreement/compromise; or were they there as full participants, factoring in what or who they represented but working towards the best choice for the entire organization. Sometimes that discussion freed people to more fully participate.

    I also agree with an earlier poster that many committee members equate "being heard" with "being obeyed". I can hear you--but not agree. This is difficult for highly educated and dedicated people to accept sometimes.

    Finally, this dicussion brings back a polisci 101 discussion about why the Founding Fathers created two houses of Congress--one short-term house of representatives (or delegates) and one longer-term Senate (or trustees). Another balancing act by TJ and friends....