Friction as a Feature
Why Europe must relearn how to slow down
The Disappearance of Friction
For decades, Europe has optimized its systems toward greater efficiency. Payments have become faster, interfaces smoother and processes increasingly invisible. What once required time, interaction and verification now unfolds in seconds, often without interruption. In this pursuit of speed, something quietly disappeared. Friction.
Not as an inconvenience, but as a structural element of how work was experienced. Friction was never only inefficiency. It was also a moment of pause—a point at which a person could reflect, verify or reconsider. It created a subtle resistance that made processes tangible and decisions visible.
When Systems Become Too Smooth
In contemporary systems, that resistance is systematically removed. Banking applications no longer ask questions unless absolutely necessary. Transactions flow without interruption. Interfaces are designed to eliminate hesitation. Everything works.
But the smoother the system becomes, the less it reveals about itself. Processes are compressed into seamless flows and the steps that once made decisions understandable begin to disappear from view.
What remains is a surface of simplicity. What disappears is the structure beneath it.
The Quiet Loss of the Human Layer
This shift is often described as progress, yet its consequences are not purely technical. Twenty years ago, banking involved physical presence. Branches were part of the urban landscape and interaction was built into the process. A transaction was not only executed; it was mediated by a person.
Today, that layer has largely vanished. Service is automated, decisions are pre-structured and interaction is reduced to confirmation. The system performs its function with remarkable efficiency, but the human role within it becomes thinner and more distant.
The individual is no longer part of how the process unfolds. They encounter it only at the edges.
A Question of Design
This transformation is not the result of technological necessity. It is the outcome of design choices. Systems have been deliberately optimized for speed, scale and consistency, often at the expense of visibility and reflection.
Enterprise platforms such as SAP sit at the center of this evolution. They are not simply tools that organizations use; they are environments that structure how work takes place. As these systems integrate artificial intelligence, they begin to encode not only processes, but also priorities.
The system does not merely execute decisions. It shapes how decisions are made.
Regulation Without Architecture
Europe is not absent from this development. The European Commission has introduced regulatory frameworks such as the AI Act, building on earlier initiatives like the General Data Protection Regulation.
These frameworks establish important boundaries. They define what systems are allowed to do, categorize risk and impose accountability.
But they operate primarily at the level of compliance. They regulate behavior, not design.
As a result, they often become procedural—checklists to be completed, requirements to be satisfied. While necessary, this approach does not address a more fundamental question: how systems should be structured in the first place.
Beyond Compliance: Designing for Humanity
If systems increasingly shape how decisions are made, then responsibility shifts from usage to architecture. It is no longer sufficient to ensure that systems comply with rules. They must be designed to preserve human presence within the process.
This requires a different principle. Not “human-in-the-loop” as an afterthought, but human-in-the-loop by design. It means deliberately creating moments where:
- decisions slow down
- assumptions become visible
- human judgment is required
Not because the system fails, but because the system is designed to make space for responsibility.
Reintroducing Friction
This is where the role of friction changes. Instead of being eliminated, it becomes intentional.
Consider a banking environment designed with this principle in mind. Transactions involving vulnerable users could follow slower, more transparent pathways. Larger financial decisions could require layered confirmation, not as a barrier, but as a safeguard. Unusual patterns could trigger visible checkpoints that invite human interpretation.
👉 Friction is not a defect in the system. It is a condition for responsibility.
In such a system, friction is not a defect. It is a form of care. It protects against error, but also against detachment. It ensures that processes remain not only efficient, but also understandable and accountable.
From Efficiency to Responsibility
The challenge, then, is not to reject technological progress, but to redefine its direction. Efficiency alone cannot be the guiding principle. Systems that optimize for speed without preserving visibility risk removing the very moments in which responsibility is exercised.
When everything becomes frictionless, decision-making becomes abstract. The system acts and the human confirms. Over time, this reduces not only control, but also engagement.
Responsibility shifts from active participation
to passive oversight.
The European Opportunity
Europe still has the capacity to shape this trajectory. Its regulatory frameworks, industrial base and enterprise systems provide a foundation from which alternative design principles can emerge.
The question is whether Europe will use that position to rethink how systems are built, rather than only how they are regulated.
This requires moving beyond compliance toward architecture. It requires asking not only what systems are allowed to do, but how they should structure human involvement.
The Final Question
Systems like SAP are not optional. They are deeply embedded in how the European economy functions. Their efficiency and scale are essential.
But dependence does not eliminate responsibility. It increases it. The question is not whether the system works. It does.
The question is whether we are still present in the processes it defines—or whether we have optimized ourselves out of the very moments that require human judgment.
Series note
This article is part of The System Rewrites Itself, a series exploring how enterprise systems are moving from supporting work to defining it.
Illustration: AI-generated, curated by Altair Media
