The cost of frictionless technology: A quality perspective

We’ve spent a decade worshipping frictionless tech, but in our rush to make everything effortless, we’ve quietly stripped away the safeguards that keep systems fair, human, and accountable.

When speed becomes a proxy for quality

Somewhere along the way, within software delivery, within modern software delivery, speed to production became synonymous with quality.

Modern delivery pipelines are designed to move fast and minimise human intervention.

If something slows a release, it’s questioned. If it can’t be automated or resolved quickly, it’s often deprioritised regardless of the risk it is associated with. The goal is momentum, measured through continuous delivery and deployment, with success defined almost exclusively by time to production.

From the outside, it looks healthy. From a testing perspective, it’s often not, because important defects and risks remain outstanding.

Quality work has never been about keeping things moving. It’s about knowing when it is appropriate to stop, pause, and consider.

The quiet failure mode of frictionless delivery

Testing exists to interrupt blind certainty. It operates on the assumption that something important has been missed, and the time and cost of discovering it exceeds the discomfort of releasing it later. Testing introduces intentional friction, not out of resistance to release, but because complex systems rarely fail in obvious ways.

When friction is removed entirely, quality doesn’t improve – instead, defects remain undiscovered.

Automation plays a valuable role. It checks the things we already understand. It confirms that yesterday’s requirements are still valid today. But automation is inherently limited by what we think to ask. It cannot question intent, notice discomfort, or recognise when a system behaves correctly but is operationally flawed.

As pipelines become more self-sufficient, human testing is often repositioned as oversight rather than full engagement. Testers monitor instead of exploring. They react instead of investigating. Over time, quality becomes something that happens after deployment, not something that actively shapes it, and issues and risks accumulate unnoticed.

Reintroducing judgement into automated systems

The answer is not to retire automation but to re-establish deliberate points of human interaction within the modern delivery system. Quality improves when responsibility is explicit and when risks are surfaced early, rather than left unidentified and being absorbed by the process.

Testing needs to be repositioned as an active, shaping discipline. Test professionals must be engaged where decisions are formed, from design, planning through to testing and acceptance. Their role is to challenge, explore edge cases, and represent the end users’ perspective and experience that cannot be captured in metrics.

Intentional friction is essential. Structures pause, explicit acceptance sign off, and documented risk discussions that hold business leaders accountable. These exist not to hinder momentum, but to ensure that progress is informed and owned.

Testing was never meant to be invisible. Its value lies precisely in its ability to slow things down at the right moment. To create space for discussion. To surface perspectives that would otherwise be excluded. To ask not only does this work, but who does this work for.

Quality gates, acceptance, and business ownership in practice

In practice, this looks like engaging test professionals on client sites early, during design and planning, rather than after build has begun. When working with a client, I intentionally add quality checkpoints into the delivery schedules, functioning as explicit quality gates that create space for discussion, challenge, and shared understanding before risks are locked in. Human input is prioritised, rather than deferred. I will review outstanding defects, risks and mitigations with key business stakeholders, ensuring everyone is consciously reviewed, owned, and accepted rather than quietly absorbed by the delivery process. As this activity is part of each test phase requiring formal sign-off, along with test exit criteria, it becomes a decision point in the project, rather than a checkpoint exercise.

Choosing the right kind of friction

The future of quality isn’t about rejecting automation or modern delivery practices. It’s about deliberately retaining resistance where judgement matters most. Human review, exploratory testing and diverse voices in risk conversations are not obstacles to delivery; they’re stabilising forces.

As systems become more autonomous, the cost of unquestioned decisions rises. The real challenge facing the industry isn’t how to eliminate friction entirely. It’s about recognising the difference between friction that wastes time and friction that prevents harm.

Quality lives in that distinction. It is exercised through conscious choice, explicit acceptance and clear ownership of risk, before systems reach the point of no return.