Faculty may not be disagreeing with your decision. They may be questioning whether you had the right to make it the way you did.
Process conflict is one of the most frequently misread types of conflict in academic departments — and one of the most damaging when mishandled. It arises not from what was decided, but from how the decision was made. In academic culture, where shared governance and faculty voice are deeply valued, the process by which decisions happen carries enormous weight. A decision that might be entirely reasonable on its merits can generate significant resistance if faculty feel they were excluded, surprised, or not adequately consulted.
The key distinction: faculty may actually agree with your conclusion while still being genuinely upset about how you reached it. Defending the decision in those moments — explaining why it was the right call — misses the point entirely.
What Process Conflict Looks Like
You announce a decision — a scheduling change, a hiring direction, a policy update — and receive pushback that feels disproportionate to the stakes. Faculty aren’t necessarily arguing that the decision is wrong. They’re saying things like “we weren’t consulted,” “this came out of nowhere,” or “I don’t understand how this was decided.” The conflict is not about the substance. It’s about legitimacy, inclusion, and respect.
Process conflicts often mask deeper trust issues. When faculty challenge how decisions are made, they are frequently signaling something broader: that they don’t feel heard, valued, or included in ways that matter to them. The process complaint is real, but it is also a proxy for a relationship concern.
Process conflicts are fundamentally about fairness, voice, and legitimacy. Your response should focus on procedural justice — not on defending your decision. When faculty raise process concerns, the most effective move is to address how decisions get made going forward, rather than relitigating what was decided.
Transparency is your strongest tool. Clearly communicate your decision-making criteria, who is involved at each stage, and how input gets incorporated — even when you cannot include everyone in every decision.
Your First Move as Chair
Resist the urge to justify the decision. When faculty raise process concerns, the instinct is to explain why the decision was correct. That response, however well-intentioned, confirms that you are not hearing what they are actually saying. Start with: “Tell me more about what felt wrong about the process.”
Ask what a fair process would look like to them. Questions like “What would have needed to happen for this to feel legitimate?” or “How can we ensure that people feel appropriately consulted going forward?” shift the conversation from grievance to design. You are not conceding the decision — you are taking the process concern seriously.
Clarify who makes what decisions — and be honest about it. Some decisions are yours to make; some are collaborative; some come from above. Faculty can handle top-down directives when they are named clearly. What erodes trust is opacity — when people cannot tell who decided something or why, they fill the gap with the least charitable interpretation.
Five Paths Connection
How your leadership style creates process conflict — and how to catch it
Warriors tend to move fast and decide efficiently — which can leave faculty feeling bypassed. If this is your dominant path, build in deliberate consultation checkpoints before finalizing decisions, even when the answer feels obvious. The consultation is not inefficiency; it is relationship maintenance.
Critical Thinkers may make decisions through careful internal analysis and then announce the conclusion — without making the reasoning visible. If this is your dominant path, share your thinking process, not just your conclusions. Faculty who can see your logic are far more likely to accept a decision they might otherwise resist.
Relators tend to consult widely and naturally, which reduces process conflict — but may struggle to be clear about when a decision is actually final. If this is your dominant path, practice being explicit: “I have heard your input and I am making this call” prevents the confusion that comes when faculty believe consultation means consensus.
Reflect
Think about a recent decision that generated more pushback than you expected.
- Is it possible that the resistance is about the process rather than the decision itself?
- Who was consulted? Who wasn’t — and did those people know they would not be included?
- How clearly did you communicate the decision-making criteria and who had authority in this situation?
- What would you do differently in how you made — or communicated — that decision?
Describe a situation where faculty pushed back on a decision you made. Was the conflict really about the decision — or about how you made it?