New

Now in Claude, ChatGPT, Cursor & more with our MCP server

Back to blog
Sector trends9 min read

Quality Culture, Not Just Quality Assurance: Why a Feedback System Is Necessary but Not Sufficient

You can run every evaluation cycle perfectly and still have no quality culture. The EUA has spent two decades arguing that compliance and culture are different things — and course evaluation is where the difference shows.

Koji Education Team

Product ·

The short answer: Quality assurance is the machinery — the surveys, the cycles, the reports, the ESG compliance. Quality culture is whether the people in the institution actually value and act on what that machinery produces. The European University Association has argued for twenty years that you can have flawless assurance and no culture, and that course evaluation is exactly where the two diverge. A perfectly administered evaluation that no one trusts or acts on is assurance theatre, not quality.

A distinction the sector keeps collapsing

Walk into most universities and ask about "quality" and you will be shown a system: a course-evaluation tool, a response-rate dashboard, an annual monitoring template, a committee that signs it off. All of that is quality assurance — the formal, often externally-mandated apparatus for demonstrating that standards are met.

The European University Association has spent two decades insisting this is only half the story. Its long-running Quality Culture project, beginning in the early 2000s, framed quality culture as something assurance procedures alone cannot deliver: "quality is not viewed as a process that can be operated through evaluation and measurement procedures alone, but as values and practices that are shared by the institutional community and that have to be nurtured" (EUA, Quality Culture in European Universities: A Bottom-Up Approach). The EUA's formulation has two components: a cultural/psychological element of shared values and commitment, and a structural/managerial element of processes and tools. Assurance supplies the second. Culture requires both (EUA, Examining Quality Culture).

This is not a semantic nicety. The European Standards and Guidelines (ESG 2015) themselves locate the responsibility in the community: quality assurance is "everyone's responsibility", and Standard 1.9 requires that programmes are acted upon on the basis of the information collected (ENQA/EUA, Standards and Guidelines for QA in the EHEA). An institution can satisfy the letter of the standard — it collected feedback, it held a meeting — while failing its spirit entirely.

How course evaluation exposes the gap

Course evaluation is the sharpest place to see assurance and culture come apart, because it is the point where the system touches every student and every teacher. Three symptoms of assurance-without-culture show up there repeatedly:

  • Falling response rates. When students believe nothing happens with their feedback, they stop giving it — and declining participation is one of the most visible signals that the cultural element has hollowed out. We cover the mechanics in Evaluation Fatigue.
  • The action gap. Collection is the easy part; acting visibly on what was said is the hard 80% that ESG 1.9 actually demands and that most institutions under-deliver. See The Action Gap.
  • Faculty distrust. When teachers experience evaluation as a compliance ritual or a managerial weapon rather than a developmental tool, the values element is gone even if the paperwork is immaculate. We address this directly in Why Faculty Distrust Course Evaluations.

Each of these can coexist with a perfectly functioning assurance system. The dashboard is green. The cycle closes on time. And the culture is dead. That is the EUA's entire point: measurement is necessary but not sufficient.

Why the bottom-up element matters

The EUA's recurring emphasis is that culture cannot be installed top-down by a quality office. Its reports stress engagement, empowerment and ownership — the participation of all university actors, supported (not replaced) by leadership and by assurance processes (EUA, Engagement, Empowerment, Ownership). Applied to evaluation, that reframes the entire instrument. The question stops being "did we collect the data and close the cycle?" and becomes "do students and staff experience this as something they own and that changes their experience?"

This is why the move from respondents to partners matters — students treated as data sources will behave like reluctant data sources, while students treated as co-owners of the process behave differently (Students as Partners).

But isn't "culture" just an excuse for soft, unaccountable quality?

A serious objection, and one a rigorous reader should press.

  • Culture without assurance is unaccountable. If "we have a great quality culture" replaces measurable evidence, it becomes a way to dodge scrutiny. The EUA model does not pit culture against assurance; it insists culture needs the structural element. A warm feeling about teaching is not evidence. The two are complements, not substitutes.
  • "Culture" can be unfalsifiable. Unlike a response rate, culture resists measurement, which makes it easy to assert and hard to audit. The discipline is to look for observable proxies — participation, evidence of action taken, trust measured directly, staff and student engagement with results — rather than treating culture as an article of faith.
  • External QA still requires the machinery. ENQA reviews, national bodies like NVAO, and accreditation will always need documented processes. Nobody is arguing you can replace the assurance apparatus with good vibes. The argument is that the apparatus is the floor, not the ceiling.

The honest position is that quality culture and quality assurance are in tension only when one is offered as a substitute for the other. A feedback system with no culture is theatre; a culture with no system is unaccountable. You need both, and the design challenge is building assurance machinery that actively cultivates the culture rather than crowding it out.

What this means for how you design evaluation

If measurement is necessary but not sufficient, the implication is that the design of the evaluation either feeds the culture or starves it:

  • Make acting on feedback visible. "You said, we did" is not a slogan; it is the single most effective intervention for rebuilding the cultural element and arresting response-rate decline.
  • Make the instrument feel like dialogue, not surveillance. A form that extracts a rating signals extraction; an exchange that listens signals partnership.
  • Give teachers developmental, not just summative, data. Formative, mid-cycle evaluation is what turns evaluation from a judgment into a conversation staff can own.

How do you measure something as soft as culture?

The fair worry about "culture" is that it cannot be audited. But the EUA model is more tractable than its language suggests, because culture leaves observable traces. Rather than asking staff to rate the culture, look at proxies that are hard to fake: response-rate trends (are students re-engaging or disengaging?), the proportion of feedback themes that have a documented action attached, the time between collection and visible response, and directly measured trust — do students believe their feedback changes anything, and do staff experience evaluation as developmental or punitive? None of these is culture itself, but together they triangulate it the way a validity argument triangulates an unobservable construct. The point is not to reduce culture to a single index — that would repeat the original error of trusting one number — but to make the cultural element accountable enough that "we have a quality culture" is a claim with evidence behind it.

Where Koji fits

The EUA distinction is, in the end, a design brief — and it is the brief Koji for Education is built against. A static survey is pure assurance machinery: it collects, it reports, it closes the cycle, and it does nothing to nurture the values element. Koji is designed to make the act of being evaluated feel like the dialogue a quality culture depends on. Its AI-moderated conversational interviews listen and probe rather than extract a number, which is what students experiencing the process as partners — not data sources — actually requires.

On the action side, Koji's closing-the-loop action tracking turns ESG Standard 1.9 from an aspiration into a workflow: feedback is linked to the actions taken in response, so "you said, we did" becomes auditable rather than rhetorical. Its automatic thematic analysis and programme- and institution-level reporting give quality offices the structural evidence external review demands, while its formative, mid-cycle collection gives teachers developmental data they can own. Koji cannot manufacture a quality culture — culture is people, not software — but it can stop the evaluation instrument from quietly corroding the very culture it is meant to serve. (The main Koji platform applies the same listening-not-extracting engine to customer and employee research, where the compliance-versus-culture gap is just as real.)

You can run a flawless evaluation cycle and have no quality culture. The institutions that close the gap are the ones that stop treating the dashboard as the goal and start treating it as the floor.

Build evaluation that cultivates a quality culture, not just satisfies the audit — explore Koji for Education.