The Tangerine Lesson: When the Procedure Follows Reality
Yet, their process was remarkably smooth because it remained oriented toward reality rather than mere checklist-checking.
Yet, their process was remarkably smooth because it remained oriented toward reality rather than mere checklist-checking.
There is a peculiar moment when a system designed to help human beings begins demanding that human beings adapt themselves to the system instead. This shift usually happens quietly, starting when a new procedure is introduced for a perfectly understandable reason like security, safety, efficiency, or accountability. Soon after, another procedure is added to make the first one more reliable, creating a safeguard upon a safeguard. Eventually, the resulting structure grows so dense that nobody seems to be asking whether it still corresponds to the actual reality it was originally created to serve.
I encountered a wonderfully mundane example of this phenomenon while trying to sign into Canada Post. Having forgotten my login credentials—a common enough occurrence that systems normally provide straightforward recovery options—I found myself effectively blocked after only a few unsuccessful attempts. At one point, the password-recovery system locked me out entirely and produced the illuminating message: “A generic error, please contact support team…”, complete with a reference number and a timestamp. The irony was almost beautiful; I had entered a procedure intended specifically for people who do not remember their credentials, yet the recovery tool itself was rapidly becoming inaccessible precisely because I did not remember those credentials correctly.
Although I eventually found the necessary information on my laptop, a second problem immediately appeared. I have recently changed my official residence, and because identification documents and databases do not all update simultaneously yet, different administrative representations of my identity were temporarily in disagreement. Even though the physical reality remained perfectly coherent, the abstraction suddenly became more important than the human being it was supposed to represent. While this rigidity is commonly defended in the name of security, true security is not the same thing as blind inflexibility.
The contrast became particularly striking because I had recently opened an account with Tangerine Bank. One would expect a bank, of all institutions, to be extraordinarily rigid about identity verification given the financial regulations and risks involved. Yet, their process was remarkably smooth because it remained oriented toward reality rather than mere checklist-checking. By photographing my identification and taking a requested selfie, the system brought different pieces of evidence together to verify my identity dynamically.
This distinction matters because good security asks whether there is sufficient evidence that you are who you say you are, whereas badly designed security simply asks whether you have successfully passed every procedural gate constructed. When the latter happens, an extraordinary inversion takes place: instead of the database being viewed as an imperfect representation of reality, reality begins to be treated as defective whenever it fails to correspond perfectly to the database. The map has officially become more authoritative than the territory.
Around the same time, another little drama was unfolding where I live regarding the installation of new speed bumps. While the underlying intention to slow down cars and protect pedestrians is perfectly reasonable, some of these asphalt bumps were built extraordinarily high—so much so that at least one had to be taken down again. There are also places where bicycle paths cross roads diagonally, and a similar diagonal intervention was oddly placed right on the bicycle path itself. It struck me that I was looking at the exact same phenomenon I had encountered on my computer screen, where an abstraction is translated directly into asphalt without considering real-world geometry.
When you look closely at how these crossings actually function, the disconnect between abstract ideology and physical parameters becomes glaring. For a cyclist, the safest and most natural action is to briefly drop a foot to the ground, stop, and use their unimpeded vision and hearing to check for oncoming traffic. A driver, trapped inside the literal metal cage of a car, faces a far more treacherous engineering problem. In a forested region like ours, the bicycle path emerges abruptly from dense bushes, cutting across the road diagonally. To check for a high-speed cyclist appearing from the blind spot behind the foliage, a driver must twist their head almost entirely off their shoulders, peering back over their left shoulder through the structural pillars of the vehicle. Meanwhile, the oncoming cyclist—fully bought into the modern dogma that "bike trumps car" because one is green and the other is an eco-abuse—rarely intends to slow down, believing the abstract hierarchy of righteousness shields them from the laws of physics.
By applying an oversimplified ideological narrative to a complex spatial problem, the planners engineered an intervention that twists sound logic and actually multiplies the real-world danger. The speed bump dropped right onto the diagonal path is a monument to this blindness. The chain of reasoning begins sensibly enough—cars travel too quickly, slowing them increases safety, and a raised obstruction forces them to slow down—but it completely falls apart when it fails to account for actual human sightlines, physical blind spots, and behavioral psychology. A rigid system forgets to ask practical questions: How high should the bump be? What happens to a cyclist crossing diagonally? These questions require active perception rather than blind rule-following, and perception is precisely what disappears when systems become overdeveloped.
The problem is not bureaucracy itself, nor is the solution to eliminate regulations and leave everyone to improvise, which would merely replace one abstraction with another. Modern civilization absolutely requires procedures, standards, banking regulations, and public institutions to function. The danger only begins when a procedure loses its ability to return to the reality from which it was abstracted. A rule is necessarily simpler than the world; for instance, the command to "verify the address" is simple, but a human life is not. When someone moves between provinces, records propagate through different systems at different speeds, creating temporary friction. Reality contains movement, whereas the database only contains fixed fields. When those fields disagree, an intelligent administration should be capable of asking what actually happened, but increasingly, the automated answer is simply an unyielding error.
Ultimately, we are building a civilization of proxies, operating through representations of reality rather than direct encounters with the world. We use credit scores to represent reliability, address fields to represent residence, passwords for identity, diplomas for knowledge, and metrics for competence. None of these abstractions are inherently foolish, as we cannot organize a civilization of millions of people without them, but the danger appears when we forget that these tools only represent reality. In a profound reversal, individuals with ample physical evidence of who they are become administratively questionable because two database fields disagree, roads become less safe due to officially prescribed apparatuses, and valuable employees fail to satisfy the metrics designed to measure their worth.
The most disturbing aspect of this trend is that nobody has to be stupid for the system to become stupid; everyone involved can be following the rules perfectly, yet the system still fails. What made my experience with Tangerine impressive was not just its convenience, but the fact that the system appeared capable of bringing multiple pieces of evidence together to arrive at a practical, human conclusion. It proved that technology can choose to serve reality, rather than forcing reality to serve it.
What ultimately creates friction lies in the starting point upon which a protocol is built: suspicion, or trust.