Design roles are shifting fast. Here's what the craft crisis means for UX teams, hiring, and how brands in Southeast Asia build better digital products.
Design is having an identity crisis — and it’s not the kind you solve with a rebrand.
For years, the unspoken contract in design hiring went something like this: find someone with visual talent, teach them the tools, and let the craft take care of the rest. That contract is quietly breaking down. As Michael Buckley argued in UX Design this week, the traditional image of the designer — artistically inclined, tool-proficient, visually fluent — no longer maps cleanly onto what the role actually demands in 2026. The gap between that image and reality is where most hiring mistakes happen.
The Craft Isn’t Gone — It’s Just Table Stakes
Let’s be precise about what’s changing. Visual craft — typography, composition, hierarchy, color — hasn’t become irrelevant. It’s become assumed. What’s scarcer, and increasingly more valuable, is the designer’s ability to reason about systems: how a component decision in a design system propagates across 14 screens, how a navigation pattern affects completion rates in a checkout flow, or how an interaction choice on mobile web differs from what makes sense inside a super-app like Grab or LINE.
Fabricio Teixeira’s curation in UX Design this week surfaced a sharp reminder: Jakob Nielsen’s sixth usability heuristic — recognition over recall — has been baked into interface design for decades. The best designers don’t just know the heuristic; they can trace its downstream impact. When a Southeast Asian e-commerce brand like Lazada or Tokopedia restructures its category navigation, the decision isn’t aesthetic. It’s a systems question with measurable conversion consequences.
The craft crisis isn’t that designers can’t design. It’s that too many can’t yet articulate what their design decisions are optimising for.
What the Data Layer Reveals About Design Decisions
Here’s where my own lens comes in, and why this matters to brands beyond the design team itself.
When I look at behavioural data from mobile commerce flows across Southeast Asia, a pattern recurs: the drop-off points that hurt revenue most are rarely the ones that look broken. They look fine. A filter panel that’s visually clean but requires three taps instead of one. A product image carousel that performs beautifully on iOS but causes scroll jank on mid-tier Android devices — still the dominant hardware segment in markets like Indonesia and Vietnam. A guest checkout button that’s present, accessible, and completely ignored because its visual weight signals secondary importance.
None of these problems get caught by design review alone. They surface in funnel data, in session recordings, in A/B test results. The designers who catch them early are the ones who’ve already been asking: what does the data expect this screen to do? That requires fluency in the product analytics layer — not just Figma.
The implication for hiring: a portfolio that shows visual range is no longer sufficient signal. The better interview question is: walk me through a time your design decision was wrong. What told you it was wrong, and what did you change?
The Researcher-in-the-Loop Model Is the Right Direction
One structural response gaining traction — Teixeira flagged it this week — is what’s being called the researcher-in-the-loop approach: embedding research practice directly into design workflows rather than treating it as a separate upstream phase that hands off a brief.
For Southeast Asian teams, this has a specific operational texture. Research here can’t be lifted wholesale from Western playbooks. User testing in Manila or Jakarta needs to account for multi-language interfaces, strong social proof signals (local reviews carry more weight than aggregate star ratings in many categories), and platform conventions that differ sharply from what Western UX literature treats as defaults. A researcher embedded in the design loop catches these nuances before they become shipped problems.
The practical implementation path: start small. Pair one researcher with one product squad for one quarter. Instrument the outcomes — conversion delta, support ticket volume, task completion rate — and use that data to make the case for scaling the model. Stakeholder buy-in rarely comes from the argument that research is good in principle. It comes from a number that changed.
Rebuilding the Designer Profile for What the Work Actually Requires
If design education is still producing students optimised for a job that has shifted, the short-term fix falls to hiring managers and creative directors. The profile worth recruiting for in 2026 looks something like this: strong visual instincts, yes — but also comfort reading analytics dashboards, a working knowledge of design system architecture, and genuine curiosity about why users do what they do rather than just what they do.
For brands building digital products across Southeast Asia’s fragmented markets — different platforms, different device ecosystems, different trust signals, different languages on the same screen — this expanded designer profile isn’t a nice-to-have. It’s a structural requirement. A designer who can only operate in the aesthetic layer will consistently under-spec the decisions that actually move the metrics.
The organisations getting this right are treating design less like a creative service and more like a decisioning function. The output isn’t a beautiful screen. It’s a better-performing system.
Key Takeaways
- Stop evaluating design candidates on portfolio aesthetics alone — add a structured question about a decision they made that data later proved wrong.
- Embed research directly into design sprints rather than treating it as a pre-phase handoff; measure the impact in conversion or task-completion terms to build the internal case for scaling.
- For Southeast Asian digital products, design system decisions must account for mid-tier Android performance, multi-language interface constraints, and platform-specific UI conventions — these aren’t edge cases, they’re the mainstream.
The deeper question is whether design as an organisational function is ready to own the business outcomes it influences — not just the screens it produces. As the line between design, product, and data continues to blur, the teams that thrive will be the ones who stopped treating those as separate disciplines. The ones still defending territory might want to ask: what exactly are we protecting, and who is it serving?
At grzzly, we work with marketing and product teams across Southeast Asia who are navigating exactly this tension — building design functions that connect visual decisions to measurable outcomes, and structuring the data layer to inform them. If your team is trying to close the gap between what your designers produce and what your analytics reveal, we’d like to compare notes. Let’s talk
Sources
Written by
Mellow GrizzlyTranslating raw data into activated audience segments, predictive models, and decisioning logic. Comfortable at the intersection of the data warehouse and the campaign manager.