When Design Tells the Truth: UX Beyond Aesthetics

Most brand design fails not because it’s ugly, but because it lies. It smooths over complexity, flattens contradiction, and offers a tidy signal where the underlying reality is anything but. Three recent pieces — on a politically charged cultural identity rebrand, on protecting creative IP in the age of AI scraping, and on the UX of system tools — point toward the same uncomfortable truth: the instinct to simplify is often the instinct to deceive. And users, especially experienced ones, know it.

Complexity Is a Design Brief, Not a Problem to Solve

When London’s The Mosaic Rooms commissioned designer Samar Maakaroun to rebuild their visual identity, the brief wasn’t to make Arab culture look approachable. It was to represent it honestly — including what It’s Nice That describes as its “often fraught history.” Maakaroun’s response was a system built on entanglement: layered Arabic scripts, abstract geometries that resist clean resolution, forms that hold tension rather than dissolve it.

This is commercially significant, not just culturally admirable. Brands that try to flatten complex audience identities into a single legible signal consistently underperform with those audiences. In Southeast Asia, where a single campaign might run across Thai, Bahasa Indonesia, Filipino, and Vietnamese-speaking markets — each with distinct cultural registers — the temptation to produce one clean, culture-neutral creative is strong and usually wrong. Maakaroun’s approach suggests a different model: build a design system elastic enough to hold contradiction, and let that elasticity become the brand’s visible character. The implementation challenge is real — multilingual lockups, script-direction conflicts, platform cropping — but those are engineering problems, not reasons to simplify the idea.

Your Design Assets Are a Monetisable Product. Protect Them That Way.

UX Collective contributor Marc Andrew makes a point that’s been circling the industry for months but rarely gets stated with enough commercial directness: moral outrage about AI training on creative work is not a protection strategy. The creator’s code — the informal social contract that design work would be attributed, respected, credited — is functionally dead. What remains is legal and technical infrastructure, and most design teams in Southeast Asia have neither.

For agencies and in-house teams producing design systems, dashboard templates, data visualisation frameworks, or proprietary UI components, this is a balance-sheet conversation. These assets have quantifiable value: a well-built data visualisation library that a publisher licenses to brand partners generates recurring revenue. A design system that reduces production time by 40% across a 20-person team has a calculable annual yield. Once those assets are absorbed into training datasets without consent, that value is diluted — competitors can approximate your output without your investment.

The practical response isn’t complex, but it does require treating design output with the same IP rigour applied to software: documented ownership, clear licensing terms on any publicly visible work, and watermarking or metadata tagging on digital assets before they leave internal systems.

---

When the Interface Is the Product: System Tool UX

Smashing Magazine’s Kyrylo Levashov makes an argument that should land hard for anyone who has ever watched an analytics dashboard confuse the very people it was built to inform: design always starts with function, but when that function can’t be made invisible, the interface itself becomes the experience. Four common software design assumptions, he argues, consistently fail users of system tools — and the failure is rarely aesthetic. It’s structural.

This maps directly onto a problem I see repeatedly in data product work: dashboards built to satisfy the team that commissioned them, not the people who will operate them daily. A campaign analytics tool built for a CMO who reviews it monthly will actively obstruct a performance manager who lives in it hourly. The interaction model, information hierarchy, and alert logic need to be different — not just the data displayed. Levashov’s framework suggests auditing whether your interface assumptions match actual usage patterns, not intended ones. In Southeast Asian markets, where mobile is frequently the primary access device even for internal tools, this means rethinking interaction patterns designed for desktop cursor precision: touch targets, swipe navigation, and condensed data density all require deliberate decisions, not defaults.

For teams commissioning system tools or building internal data products, the business case for this kind of UX investment is straightforward: a dashboard that operators trust and use correctly produces better decisions. One they’ve learned to distrust — or work around — produces noise.

The Business Case for Honest Design

These three threads converge on a single strategic position: design that acknowledges and works with complexity, rather than papering over it, tends to produce more durable commercial outcomes. The Mosaic Rooms’ identity will resonate with audiences who’ve seen their culture flattened once too often. Design assets treated as IP will generate returns long after the project closes. System tools designed around actual operator behaviour will be used, trusted, and — critically — will produce the decision-quality their commissioning teams assumed they were buying.

The failure mode in each case is the same: prioritising the appearance of simplicity over the reality of how things actually work. That’s a design choice that always eventually shows.

Key Takeaways

• Build brand systems elastic enough to hold cultural complexity, especially across multilingual Southeast Asian markets — design that flattens nuance loses the audiences who know the difference.
• Treat design output as a monetisable IP asset: document ownership, apply licensing terms, and tag digital assets before distribution to protect the revenue value embedded in your creative work.
• Audit system tool interfaces against actual usage patterns, not intended ones — in mobile-primary SEA markets, desktop-default UX assumptions create measurable drops in operator trust and data utility.

The deeper question worth sitting with: as AI tooling makes it easier to produce design that looks resolved and confident, does the market premium shift toward work that’s visibly honest about what it doesn’t know? Audiences — and operators — are getting better at telling the difference.

---

At grzzly, we work with brands and publishers across Southeast Asia to build design systems and data products that are commercially rigorous from the first brief — not just visually coherent. Whether that’s a monetisable visualisation framework, a multilingual brand system, or an internal analytics tool that operators actually use, the starting point is always the same: what does this need to be true about? Let’s talk