Leadership Insights

The Same Behavior, Two Different Labels 

Read Time:

A senior colleague’s pushback gets called rigor. But that same pushback from someone junior is sometimes called a collegiality problem.

On Monday, we named collegiality as a currency. It’s not an account that’s official, but everyone holds one, and it shapes how people show up with you. Today, we look at how that account gets debited—and who tends to pay the price.

For instance, here’s one common pattern: A senior faculty member pushes back hard in a meeting. Some people of those present call it rigor. However, a junior faculty member raises the same objection—with the same tone and the same evidence, in the same meeting—and some call it a collegiality problem.

What’s the difference between the two? The behavior didn’t change. The account balance did. The senior faculty member has experience and relationships built up over time. People “know” what they were getting at. The junior faculty member is less known, and some will give this person the benefit of the doubt while others will not.

This pattern occurs in many places around the academy, not just around the tenure table.

In academic affairs. A tenure letter notes that a candidate is “not always collegial,” without specifying what that means. In this case, what it means is that the candidate asked hard questions in department meetings or declined to go along with a decision they thought was wrong.

In a supervisory role. A team lead raises a concern about a cross-departmental decision, clearly and professionally. Within a few weeks, they notice they’re not being looped into the planning conversations anymore. No one said they were difficult. But the invitations stopped, right after the pushback, and not before.

In advancement. A gift officer raises a concern in a strategy meeting that a proposed ask oversteps what the donor wants. Leadership moves forward anyway. Afterward, a colleague pulls the gift officer aside to say that the pushback “wasn’t the best look” in front of the VP. For the next ask strategy session, they’re not on the invite list.

When the Label Is Actually Earned

To be clear, collegiality concerns can be very real, and treating all negative reactions as a disguised punishment for honesty does a disservice to people who’ve genuinely had to manage a difficult colleague.

The distinction usually comes down to three things:

  • Whether it’s a pattern or a single incident
  • Whether the delivery (not just the content) caused harm
  • Whether the concern can be stated in terms of specific behavior rather than a vague sense that someone is “hard to work with”

A colleague who repeatedly interrupts, dismisses, or undermines others has a real collegiality problem. While a colleague who disagrees once, clearly, and moves on, may not have a collegiality problem at all. The more a concern looks like the first description, the more it deserves to be taken seriously. The more it looks like the second, the more it deserves a second look.

Members must be logged in to view this content.

 
 
Sophia Spotlight

How to Use Sophia as an Advancement Professional

Aligning with an Emerging Donor

Being honest with a donor about a mismatch, without losing the relationship over it, is exactly the kind of judgment call this week has covered: saying the true thing in a way that doesn’t cost you more than it needs to. Sophia can help you think through how to approach the conversation.

“A new donor wants to give to [cause] and our university doesn’t currently prioritize it. I want to be honest with them and still find a meaningful way to work together. Help me think about how to approach this.”

Watch the demo video below to see this prompt in action.