A month ago, someone on Mykola Konrad’s team was still building prototypes by hand. Today, an agent does it.
That’s how fast the ground is moving under UX teams right now. And when we ask product leaders where design is headed, nobody agrees. Is it all agents from here? Does AI design everything?
Mykola has a more practical answer than most. He’s CPO at Euna Solutions, which builds software for government agencies. Before that, he spent 25+ years in product at companies like Microsoft, Avaya, and Brightcove. At Euna, UX reports directly to him, so the question of what happens to design isn’t theoretical. He’s making those calls right now.
In this episode, we get into:
Which UX work is moving to PMs, developers, and agents, and the “If you can, then do” mantra Euna is using to get there
Why customer contact, high-stakes flows, and accessibility still need a human making the final call
Myk’s change management playbook for getting a team through AI adoption, and why token spend is a useful (if imperfect) signal
How Euna is running two delivery flows side by side, AI-enhanced and full-AI, and why customer adoption may be the real speed limit
1. The UX work that’s already succeeding: “If you can, then do”
Myk doesn’t think all of UX is up for grabs. But some of it is moving out of the UX team
The work on its way out is the work that doesn’t need deep taste or customer context: design system upkeep, adding new components, first drafts, early exploration, and getting from a PRD to a prototype. That work still happens. It just happens somewhere else.
“The activity still happens, but it will move to a different persona within the organization. And right now we are actually having some product managers do that, and we’re also having some developers do that, ‘cause I’m not sure exactly 100% where it’s gonna land.”
Rather than deciding up front who should own it, Euna is letting people volunteer:
“If you as an individual believe you have the aptitude or the skill set or just the desire to try to prototype something using Claude Code or Claude Design, then do it. Don’t wait for the UI/UX team to help you out, just try it.”
Product takeaway: You don’t need to know exactly where every task will land before you let people start. Give anyone with the aptitude permission to pick up the lower-stakes design work now, watch who takes to it, and use what you learn to redraw the roles later. Just be upfront that “optional” won’t stay optional forever.
2. What stays human?
So what doesn’t move? For Myk, it comes down to three things.
1. Direct customer contact. Myk has been interviewed by an AI agent himself, and it was fine, up to a point.
For some of Euna’s customers, it’s not even a matter of quality. Several large state and provincial governments simply won’t work with an agent:
“They will not accept an agent interfacing with them. I wouldn’t even call it regulatory, it’s partly the way that that particular government entity needs and wants to operate. They want a human being doing it.”
2. The final call on high-stakes flows. Euna owns the rails on its payments product, and it builds compliance flows and audit trails. AI can give you a first pass, but someone with deep UX expertise needs to decide what actually ships.
3. Accessibility and regulated work. Even as AI improves and takes on more interviews and insight work, Myk expects accessibility and compliance to keep a human in the loop.
Product takeaway: Sort your UX work by the cost of getting it wrong, not by how hard it is to do. Low-stakes, easy-to-review work is where AI should go first. Anything involving money moving, regulators, or users with accessibility needs should keep a human making the final call (even if the AI draft looks good).
3. Getting your team through the change
How do you get an existing team ready for a future that looks this different? Myk starts with change management 101: almost nobody likes change. Some people just get through the skeptical phase faster than others.
From there, Myk’s approach is solid:
Pick the tools: Euna’s design team is a two-tool shop right now: Figma Make plus Claude Design for prototyping. Everyone gets trained on both
Map the new handoff: How does work move from design agents to product to the “software factory”?
Reset expectations on time: If a design used to take three weeks, try three days and see what happens
Watch for signals: Myk wasn’t trying to monitor anyone, but token spend made it clear who was jumping in and who wasn’t. It’s not a productivity metric on its own, but someone using almost nothing probably isn’t changing
He also recommends asking your team directly where the bottleneck is. When Euna’s product and dev teams went agentic, the answer that came back was UX. From there, the question is whether it’s a data-in problem (user research isn’t done because customers haven’t responded yet) or a data-out problem (the research exists, but designs aren’t moving fast enough).
Product takeaway: Be honest about your timeline before you design your change plan. The length of the window you can give people should shape how much training, patience, and support you build in. And don’t guess where the slowdown is: ask the team, then figure out whether it’s a process gap or a data gap before you try to fix it.
Chapters
00:00 Introduction
02:20 Myk's path from electrical engineer to CPO
03:21 Will AI replace UX?
05:07 UX work shifting to PMs, developers, and agents
06:35 Where UX still needs humans: Customer research, payments, and compliance
13:47 Myk's change management playbook and token spend as an adoption signal
17:20 Finding bottlenecks in an agentic delivery process
19:05 AI-enhanced vs. Full-AI workflows from product to dev
24:31 Customer adoption is the real speed limit
25:43 Conclusion
Links
What does LogRocket do?
LogRocket’s Galileo AI watches user sessions for you and surfaces the technical and usability issues holding back your web and mobile apps. Understand where your users are struggling by trying it for free at LogRocket.com.