UX design is struggling because it abandoned its core unit of measurement. Here's what that means for digital teams in Southeast Asia and how to fix it.
Somewhere between the proliferation of device sizes and the rise of AI-generated layouts, digital design teams quietly lost the thing that used to anchor every decision: a reliable unit of measurement. Not pixels — those never meant what we thought they did. Something more fundamental: a shared, stable reference frame for what “correct” actually looks like.
As UX Collective’s Kai Wong argued this week, that loss is not cosmetic. It’s structural. And from where I sit — building the data pipelines that are supposed to tell design teams whether their work is landing — the downstream effects are exactly as messy as you’d expect.
When the Reference Frame Breaks, So Does the Data
The screen used to be a reasonable proxy for context. Desktop meant focused intent, mouse precision, full attention. Mobile meant quick lookup, thumb reach, distracted user. Those assumptions were always imperfect, but they gave design teams a starting coordinate — a place to reason from.
That coordinate is gone. In Southeast Asia, where Shopee’s average session involves a user toggling between app, browser, and messaging their friend on LINE about the same product, the “screen” as a unit tells you almost nothing. A 6.7-inch display running the Lazada app in a Bangkok market stall is a completely different design environment than the same screen size on a commuter train in Singapore — same pixel dimensions, radically different context, attention level, and intent.
The result is that A/B test results become unreliable. You optimise a checkout flow for “mobile” and see a 12% lift — but that lift is entirely concentrated in one device/context cluster that your analytics aren’t disaggregating. The design decision looks validated. It isn’t.
The Tactile Reminder That Constraints Are Generative
There’s an instructive parallel in what illustrator Lia Sued C. described this week when reflecting on her shift away from pure digital practice: returning to physical materials forced her to work with constraints that digital tools had abstracted away. Paper has grain. Ink bleeds. Those limitations aren’t bugs — they’re the reference frame that makes craft decisions legible.
Digital design teams abandoned a version of this when they chased infinite scalability. Responsive design was supposed to solve the measurement problem by making everything fluid. Instead, it deferred the problem. Fluidity without a fixed reference point isn’t adaptability — it’s ambiguity with good PR.
The fix isn’t retreating to pixel-perfect Figma files. It’s identifying what your actual unit of measurement should be for each context: task completion time, thumb-reachable interaction zone, cognitive load at a specific moment in a user journey. These are harder to design to, but they’re honest about what you’re actually optimising for.
Building the Infrastructure to Measure What Actually Matters
This is where the data architecture question becomes a design question — and vice versa. Most Southeast Asian brand teams I’ve seen are running event tracking that logs what happened (tap, scroll, purchase) without capturing the contextual signals that explain why. Device type, yes. Connection speed, sometimes. But ambient context — location type, session origin, prior touchpoints across platforms — almost never.
The practical implication: if you want design measurement that’s actually reliable, you need an event schema that captures context as a first-class dimension, not an afterthought. That means deciding, before you instrument anything, what your reference frame is. What constitutes a “successful” interaction for this specific user type in this specific context? That definition needs to be codified in your data model, not reverse-engineered from aggregate dashboards after the fact.
For teams on platforms like Shopee or Grab that operate within walled garden analytics environments, this often requires building a parallel contextual layer using first-party signals — session sequencing, entry path, device fingerprinting — to reconstruct the context the platform doesn’t expose. Not glamorous infrastructure. Essential infrastructure.
The Cultural Dimension No Design System Addresses
There’s one more layer that Southeast Asian design teams consistently under-index on: cultural reference frames that affect what “good” design feels like to users, independent of any technical measurement.
Zara Larsson’s breakout moment in 2026 — analysed this week by Gary Grimes — offers an oblique but useful data point. Her visual world resonated partly because it tapped a specific generational nostalgia: noughties internet aesthetics that felt earnest, lo-fi, pre-ironic. That’s a reference frame her audience shared viscerally, even without being able to articulate it. It made her design choices legible and trustworthy to a specific cohort.
Brand design in Southeast Asia has an equivalent challenge. Colour associations, typography density expectations, the acceptable ratio of text to imagery in a promotional banner — these vary meaningfully between Thai, Filipino, Indonesian, and Vietnamese audiences. Not because users in these markets are irrational, but because their reference frames are different. A design system that doesn’t encode these distinctions isn’t truly localised; it’s just translated.
The measurement problem and the cultural problem are the same problem: design teams are optimising against a reference frame they haven’t explicitly defined, measured against metrics that don’t capture what they actually care about, and wondering why the results feel unreliable.
Defining the unit comes first. Everything else — the system, the instrumentation, the iteration — follows from that.
Key Takeaways
- Audit your current design measurement framework: identify whether you’re tracking outputs (clicks, conversions) or the contextual signals that explain them — and close that gap first.
- For multi-platform Southeast Asian campaigns, define a context taxonomy (device + entry path + session intent) and instrument it explicitly before running any optimisation tests.
- Treat cultural reference frames as a design system input, not a localisation afterthought — document audience-specific conventions for colour, density, and layout at the component level.
The deeper question worth sitting with: if your design team can’t articulate its unit of measurement in one sentence, what exactly are your optimisation sprints actually optimising for? Consistency without a reference frame is just organised guesswork — and in markets as competitive and contextually complex as Southeast Asia, organised guesswork has a cost.
At grzzly, we work with marketing and digital teams across Southeast Asia to build the data infrastructure and design measurement frameworks that make iteration actually mean something — not just more dashboards, but clearer signals. If your team is scaling design across markets and finding that results don’t travel cleanly between contexts, that’s a solvable problem. Let’s talk
Sources
Written by
Chunky GrizzlyDesigning the foundational plumbing — data warehouses, lakehouse models, and ETL pipelines — that separates organisations with genuine intelligence from those drowning in dashboards.