Beyond the Gatekeeper: Navigating "Quality Blindness" and the Rise of the Quality Guild

Georgios Kogketsof
Apr 7
2 min read

Updated: Apr 8

The Evolution Paradox: Traditional gatekeeping offered total visibility but at the cost of speed. Today’s embedded models offer maximum velocity, but are we accidentally creating a "Quality Blindness" that masks long-term risk? — **The Evolution Paradox:** Traditional gatekeeping offered total visibility but at the cost of speed. Today’s embedded models offer maximum velocity, but are we accidentally creating a **"Quality Blindness"** that masks long-term risk?

Introduction

For years, the QA Manager was the final safety switch. We stood at the end of the conveyor belt, holding the big red "Stop" button. But as we move toward the age of AI agents, MCP (Model Context Protocol), and decentralized squads, that red button is disappearing.

Today, we are seeing a radical shift in how quality is managed. The traditional QA department is being dismantled and rebuilt inside Engineering. But as we transition, we are uncovering two distinct phenomena that will define the next five years of our industry: Quality Blindness and the emergence of Quality Guilds.

The Peril of Quality Blindness

As QA teams move to report directly to Engineering Managers (EMs), a dangerous side effect is emerging. EMs are naturally incentivized by velocity—sprints, story points, and release dates.

When there is no longer a dedicated QA voice at the leadership table, organizations develop Quality Blindness. This isn't an intentional disregard for bugs; it’s a structural loss of perspective. Without a "Quality North Star," we stop looking for systemic risks and start focusing purely on "green builds."

The question for 2026 isn't "Do we have bugs?" but "Are we even looking in the right direction anymore?"

The "Quality Guild" as the Antidote

Figure 1: The Structural Shift. Moving from a centralized Gatekeeper model—where quality is a final phase—to a decentralized Quality Guild model, where expertise is embedded within squads and connected by a shared community of practice. — **Figure 1: The Structural Shift.** Moving from a centralized **Gatekeeper** model—where quality is a final phase—to a decentralized **Quality Guild** model, where expertise is embedded within squads and connected by a shared community of practice.

If the centralized department is dead, how do we maintain standards? The most successful organizations I see are moving toward a Quality Guild model.

In this decentralized world, testers are embedded in squads, but they belong to a professional Guild that defines the "Dojo" rules—the standards, the tooling (like the AI-agent frameworks we've discussed here before), and the ethics of testing.

The Guild ensures that even if you report to a developer, your soul belongs to Quality.

Why I'm Bringing this to the Round Table

On May 12th 2026, I’ll be moderating a discussion with leaders

Rolandos Koulas - Agile Actors

Selim Cakar - Betsson Group

BJORN BOISSCHOT - Cegeka

Iulia Neacsu - Netcompany

Anthi Margellou - Qualco Group

Panagiotis Tzagkarakis - XM

Panagiotis Leloudas - Yodeck

We aren't going to talk about how to write a test case. We are going to talk about survival:

Ownership vs. Accountability: If everyone owns quality, who gets the "blame" for a production outage?
The EM Trap: Can a leader without a QA background effectively prevent Quality Blindness?
The AI Orchestrator: As we move from manual scripts to autonomous AI agents, is "Test Management" even the right title anymore?

Join the Conversation

The Dojo has always been about mastering the craft. But mastering the management of that craft is the next frontier.

I’m curious to hear from you before the session: Does your organization have a Quality Guild, or are you currently suffering from Quality Blindness?

Stay tuned for the highlights from our upcoming Round Table: "The Future of Test Management — Who Owns Quality Now?"