Resistance is information about the work, not an obstacle to it

When experienced staff push back on a change, the content of the objection usually deserves examination.

Resistance is often treated as a problem to be managed, something that will pass once people adjust. Sometimes that is true. Frequently it is not, and what is being dismissed as reluctance is a specific and accurate warning from someone who understands a part of the work that the project group does not. The person saying this will not work for our situation may be protecting a habit, or may be pointing at a genuine flaw that nobody senior has visibility of. The only way to know is to ask what specifically will fail and under what circumstances.

The distinction is usually easy to draw once the question is asked properly. Objections about comfort tend to be general: it is confusing, it is different, the old one was fine. Objections about substance are specific and testable: this cannot handle the case where a learner transfers partway through, or this loses the note we rely on when a query comes back later. Specific objections should be written down and answered individually. Treating both types the same way guarantees that the useful ones are lost among the rest.

There is also a cost to dismissing objections that turns out to be far larger than it appears. People who raise a concern and are ignored do not usually keep raising it. They go quiet, comply minimally, and stop volunteering what they know. The institution then loses not just that one warning but the entire flow of practical intelligence from its most experienced staff, at exactly the point in a project when it needs that intelligence most.