When a Colleague Questions a Quality Process

When a Colleague Questions a Quality Process

It is a familiar moment for any FE and skills leader. A colleague vents their frustration, calling a quality assurance task - a course review, a data submission, a moderation meeting - 'pointless' or 'a waste of time'. The temptation is to either defend the system or sympathise and move on. A more effective response, however, is to treat this as valuable feedback.

Handled well, these moments are opportunities to either reinforce the purpose of your quality systems or to identify genuine flaws that need fixing. How you engage can determine whether you build a culture of shared ownership or one of grudging compliance.

Listen to Understand, Not Just to Reply

Before you explain or defend the process, your first step is to listen. A frustrated colleague needs to feel heard. Jumping straight to a defence of the system will shut down the conversation and make them feel dismissed. Create a space for them to elaborate on their criticism.

Use open, non-judgemental questions to explore their perspective:

• "That's interesting, can you tell me more about what felt like a waste of time?"
• "Could you walk me through your experience of the process?"
• "What was the most frustrating part for you?"
• "In an ideal world, what would this process achieve?"

By seeking to understand their specific experience, you gather crucial data and demonstrate that their professional opinion matters.

Is It a Process or a Perception Problem?

Once you have listened, you can begin to diagnose the root of the issue. The complaint will generally fall into one of two categories: either the process itself is flawed, or the colleague's perception of it is misaligned with its purpose.

• A Process Problem: The colleague might be right. Is the process overly bureaucratic? Does it duplicate effort? Is it poorly timed, creating unnecessary workload pressure? Does the information it generates ever get used to make meaningful improvements for learners? If the 'output' of the process is invisible or irrelevant, staff will rightly question the 'input'.

• A Perception Problem: The colleague may not see how this specific task connects to the bigger picture. The 'why' behind the process may have been lost or was never clearly communicated. They may not understand how this piece of evidence helps leaders evaluate achievement, ensure inclusion, or inform the self-assessment report (SAR).

Distinguishing between these is key to your next step. You are not trying to assign blame, but to identify the correct solution.

Diagnose the Specific Sticking Point

Digging deeper can reveal a more specific barrier that is fuelling the colleague's frustration. Often, a general complaint about a process masks a more particular difficulty.

• Workload: Is the task simply too onerous for the perceived benefit? It might be a well-designed process, but if it takes three hours and staff are already stretched, it will be met with resistance. The issue here isn't the process itself, but the capacity to engage with it.

• Relevance: Does the colleague feel the process is a poor fit for their specific provision-type? For example, a work-based learning assessor may struggle with a quality tool designed primarily for classroom delivery. This can make the process feel irrelevant and ill-conceived.

• Capability: Is the colleague struggling with the skills needed to complete the task? This could be a lack of confidence with a specific IT system, uncertainty on how to write an evaluative comment, or unfamiliarity with data analysis. It is often easier to call a task 'pointless' than to admit 'I am not sure how to do this well'.

Find a Constructive Path Forward

Your diagnosis will shape your response. Your goal is to move from complaint to a constructive outcome that benefits the colleague, the learners, and the provider.

• If it is a Process Problem: Thank the colleague for their valuable insight. Acknowledge the validity of their feedback and commit to reviewing the process. You could say, "This is really helpful. What you're describing is not the intention. Could we explore a more streamlined way to achieve this?" This turns the colleague into a partner in improvement.

• If it is a Perception Problem: This is a coaching opportunity. Connect the dots for them. Explain the 'golden thread' from their action to a whole-provider evaluation area. For example: "The reason we ask for this is that it's our best way of seeing if we are meeting the needs of all learner groups. It's key evidence for our whole-provider focus on inclusion."

• If it is a Workload or Capability Issue: Offer direct, practical support. This could involve protecting time for them to complete the task, providing one-to-one coaching on the system, or pairing them with a peer who is more confident. This shows you are supporting the person, not just enforcing the process.

Where this fits in QualityHero

Professional dialogue is the engine of a healthy quality improvement culture. Capturing insights from these conversations is essential for leadership and governance. The themes that emerge - whether they relate to process flaws, training needs, or workload pressures - can be tracked in QualityHero's Leadership Reports module to identify wider patterns. Where a process flaw is confirmed, a clear improvement action can be logged, assigned, and monitored in the QIP module, ensuring that a colleague's valid criticism leads to tangible, positive change.