Why UX Portfolio Work No Longer Proves Your Design Value

There’s a quiet crisis running through design teams across Southeast Asia right now: the work looks better than ever, and it’s being trusted less than ever.

Kai Wong’s recent essay on UX Collective put it plainly — your screens don’t vouch for you anymore. The argument lands harder than it might seem. As generative tools compress the time it takes to produce high-fidelity prototypes and polished UI, the artefact itself — the Figma file, the pixel-perfect mockup — has lost its signalling power. What used to say I am skilled now says I have access to the same tools everyone else does. For design leads at brands in Bangkok, Jakarta, or Manila managing teams under increasing AI productivity pressure, this isn’t a theoretical concern. It’s a hiring and positioning problem happening right now.

The luxury goods market figured this out decades ago. And it has something genuinely useful to teach us.

The Hermès Problem: When Craft Alone Stops Being Enough

Luxury bags don’t sell on function. A Bottega Veneta Jodie and a mid-market leather tote both carry your laptop. The delta in perceived value — and actual price — lives entirely in provenance, process, and meaning-making. Hermès artisans spend two years training before they touch a Birkin. That story is the product.

Wong’s framing maps directly onto design: when outputs become commoditised, the process, the judgment, and the strategic thinking behind decisions become the differentiator. A designer who can walk a CMO through why a particular checkout flow reduced drop-off by 18% on mobile — with the data architecture to prove it — is operating in a different category entirely from one who shows a beautiful screen and says “users preferred this.”

For Southeast Asian brands specifically, this matters at the platform layer too. Shopee and Lazada’s native UI conventions are deeply embedded in buyer behaviour — regional designers who understand why those patterns work (not just what they look like) bring irreplaceable strategic value. That contextual intelligence doesn’t render. It can’t be Midjourney’d.

The Handoff Problem Reveals What Designers Actually Own

Speckyboy’s recent piece on developer handoffs — messy transitions, unclear asset ownership, licence disputes — surfaces a related structural issue: most design processes don’t produce durable institutional knowledge. They produce files.

This is the data pipeline equivalent of building a beautiful dashboard with no documentation on how the underlying tables were constructed. Looks great. Falls apart the moment the person who built it leaves the room.

Designers who want to reclaim strategic authority need to think more like data architects: build for handoff from day one. That means component libraries with documented decision rationale, not just annotated specs. It means design tokens that map directly to engineering variables, so a colour change in a brand refresh doesn’t require a three-week back-and-forth. It means stakeholder-readable audit trails that explain why a pattern was chosen — conversion data, accessibility requirements, platform constraints — not just what it looks like.

In practical terms: before any design review, ask whether someone who wasn’t in the room could reconstruct the reasoning from the documentation alone. If the answer is no, the work isn’t finished.

---

What Film Title Design Gets Right About Meaning-Making

Teddy Blanks, the designer behind title sequences for Barbie, Weapons, and Robert Eggers’ forthcoming Werwulf, doesn’t start with typography. He starts with research — eBay doll auctions, 14th-century manuscripts, hidden AA symbolism — and lets the visual language emerge from that conceptual groundwork. The letterforms for Barbie aren’t pink because pink tested well. They’re pink because the entire sequence is a meditation on cultural memory and nostalgia, and the type needed to carry that freight.

It’s Nice That’s profile of Blanks is a masterclass in a principle that translates directly to product and brand design: every visual decision should be the answer to a question, not a starting point. When design is built this way, it’s genuinely hard to replicate — not because it’s complex, but because the reasoning is specific and earned.

For UX teams in Southeast Asia building across multilingual interfaces — Thai, Bahasa, Vietnamese, Tagalog — this approach is especially valuable. Typography and layout choices that work beautifully in English often collapse under longer strings or right-to-left reading conventions. Designers who’ve done the research, stress-tested the system, and documented the trade-offs are building something that scales. Designers who picked a typeface because it looked clean are one localisation sprint away from a crisis.

Reskilling for a World Where Screens Don’t Speak for You

Nielsen Norman Group’s UX Conference in November — five days, structured training tracks — reflects an industry aware that foundational skill-building matters more now than trend-chasing. The courses worth prioritising aren’t about learning the latest AI design tool. They’re about research methodology, systems thinking, and stakeholder communication: the capabilities that let designers speak the language of business outcomes rather than design deliverables.

The practical implication for design leads: audit your team’s output not on visual quality, but on whether each decision is traceable to a measurable hypothesis. Can your team explain what they expected to happen, why, and what actually did? If that chain of reasoning doesn’t exist, you’re not running a design function — you’re running an aesthetics service. The former has a seat at the strategy table. The latter gets briefed by it.

The question worth sitting with: if every screen your team produced was identical to a competitor’s — same fidelity, same tool stack, same visual quality — what would be left to demonstrate your value?

---

At grzzly, we work with marketing and digital teams across Southeast Asia who are asking exactly this question — and discovering that the answer usually lives in better data, clearer decision frameworks, and design systems built to survive beyond the designer who created them. If your team’s work is strong but its strategic authority is eroding, that’s a conversation worth having. Let’s talk