The Framework
Three questions. Ten years of fieldwork.
This research comes from inside a global IT Service Desk — not from a consulting firm looking in. From the floor. Resolving tickets, managing escalations, watching where the system breaks. Before IT, years in global hospitality operations — front office, guest experience, service delivery — where it became clear that the gap between what a brand promises and what a colleague delivers is almost always a communication problem, not a competence problem.
These three questions came from that experience. They are not theories. They are patterns observed across the US, Mexico, Southeast Asia, and Europe — documented across 10,000+ geotagged data points.
See the evidence: 10,000+ data points across 4 continents →
01 — Why does global IT lose capacity to language?
Every IT system in global enterprise assumes English. The knowledge base is in English. The incident categories are in English. The self-service portal is in English. But the people using these systems — in Kuala Lumpur, in Cancun, in rural Louisiana — do not all think in English. Some do not think in technical concepts at all.
There are users who do not recognize the word “browser.” Not because they lack intelligence — because in their daily work, they tap an icon on a screen. They have never needed that word until someone on the Service Desk asked “Are you on a browser?” and they had no framework for the question. “Applications” means nothing to someone who knows them as the pictures on their home screen.
There are tickets from users in Asia who write internal team notes in the “comments” field of a financial form — because the label says “comments,” and in their context, a comment is a note to share with colleagues. The system designed that field to mean “explain this transaction.” The user read it as “a place to communicate with my team.” Same word. Two entirely different intentions. The transaction gets flagged. Someone investigates. Time is lost.
But the Linguistic Tax is not just about words on a screen. It is about assumptions embedded in processes. In the US, it is customary to tip — and receipts include a tip line. Deploy that same receipt in a country where tipping does not exist, and a new employee who receives cash from a guest does not know what to do. Is it a gift? Is it a mistake? Should they report it? The receipt assumed one culture. The employee lives in another. The gap between those two realities is the Linguistic Tax — and it costs time, confidence, and trust every time it goes unaddressed.
Field observation suggests this accounts for 15-20% of capacity loss in global service delivery. Not because people are inadequate. Because the interface was built for one context and deployed to dozens.
02 — What does global service delivery actually look like on the ground?
New hires fail their IT onboarding — not because they are unwilling, but because the process assumes they already know how to use the device they are holding. Some of them bought that phone to get the job. The onboarding expects device literacy that the role never requires.
In hospitality, the same pattern appears from the guest side. American companies train overseas staff to clear plates quickly — stack them, sweep the table in one pass. But in some cultures, a full table of empty plates is a point of pride for the guest. It says: look how well I was served. The training assumes one culture. The guest operates in another. Neither is wrong. The gap between them is where service breaks.
Now imagine the system learned the culture instead of assuming it. Not everyone uses forks and knives. In Malaysia, guests wash their hands at the table with a traditional cleaning pot and basin. If the ordering system understood the guest’s context — through language, through location, through their membership profile — it could anticipate what belongs on that table. Hand-washing station, not silverware. Halal preparation, not a conversation with the server. Kosher, allergen-free, vegetarian — not as questions asked at the table, but as data provided at strategic points throughout the experience. Geolocation through apps and membership profiles can anticipate dietary and cultural needs before the guest sits down.
No assumptions. Just data, provided at the right moment, in the right context.
Ten years. Four continents. Every observation above came from being physically present in the environment where the breakdown happened — not studying it from a dashboard.
03 — Can the incident be prevented instead of resolved?
The current Service Desk model is reactive. A user experiences a problem. They submit a ticket. An analyst picks it up. The clock starts. The metric is Mean Time to Resolution. The entire system is optimized for responding to failure.
But the incidents have patterns. The same onboarding failures from the same types of roles. The same confusion from the same regions where the interface language does not match the user’s mental model. The same gaps between what the system expects and what the human actually needs. These are not random events. They are predictable — if someone is paying attention to the data, and if the system is designed to act on what the data reveals.
The prototypes on this site ask: what if the system could adapt to the user before the user has to adapt to the system? What if a multilingual onboarding screen could detect your language and teach you how to interact — without a single instruction in a language you do not read? What if training completion could reach 98% in 48 hours by replacing administrative language with something every human already understands — like hunger, like climbing, like growth?
These are not finished products. They are working prototypes — built from inside the Service Desk, not above it. Built by someone who resolves the tickets that these prototypes are designed to prevent.