Beyond UX Design copertina

Beyond UX Design

Beyond UX Design

Di: Jeremy Miller
Ascolta gratuitamente

Beyond UX Design’s mission is to give you the tools you need to be a truly effective UX designer by diving into the soft skills they won’t be teaching you in school or a boot camp. These soft skills are critical for your success as a UX professional.Jeremy Miller Arte
  • We Cut Figma. Here's Why. // What Survives E01
    Sep 24 2026

    It’s a regular Thursday sync until my manager cuts our Figma license and hands the whole product team one month to go fully AI. In this one I walk through who made that call, the surprisingly solid case for it, and the very selfish panic running through my head while I said nothing.

    When the tool you spent a decade mastering loses its market value in a single meeting, what exactly are you afraid of losing: your job, or your identity?

    This is the episode about the day the call actually came down. I’m at my kitchen counter with a fresh coffee, hopping on a normal weekly UX sync, when my manager announces the entire product team is moving to a 100% AI workflow by the end of the month. And by the way, the Figma license is getting cut. No debate, no “what does everyone think.” The decision was made in a room I wasn’t in, then delivered to a room full of designers who had about a month to deal with it.

    I do two things in this one. First, I try to be fair to the decision, because it deserves it. I get into the cost math leadership was staring at in early 2026, the pricing question Bob Baxley raised after I posted about the switch, and why ripping the band-aid off with a brutally short deadline was probably the right move and not the reckless one it felt like. Then I tell you the less flattering half: what was actually going through my head in that meeting. Spoiler, not one of those thoughts was about our users or the work. Every single one was about me, my title, and whether being “the person who knows Figma best” was ever a real skill to begin with.

    I also get into the part nobody sat us down to talk about, which is that these tools blur the lines between design, engineering, and product in every direction at once, and introduce the “in the loop, on the loop, out of the loop” question that runs through the rest of the season. If your company hasn’t had this meeting yet, I’d gently suggest not assuming it isn’t coming. Give this one a listen, then let me know about your own version of the kitchen counter moment.

    Topics:

    • 0:00 The day they cut our Figma license

    • 3:00 The cost play: why pay for two tools?

    • 4:05 Not my call: where I sit in the org

    • 4:50 Nobody said "adapt or quit" (the soft mandate)

    • 5:30 The fair case, and Bob Baxley's pricing question

    • 7:15 Ripping the Band-Aid: off the dock, into the boat

    • 8:40 What was really in my head: "just UI engineers now?"

    • 9:45 Kevin the plumber

    • 10:50 Watching a decade of skill depreciate

    • 11:50 How remote teams process shock

    • 13:10 Does engineering even want us in the code?

    • 14:00 Every role blurs at once

    • 15:10 The walk

    • 15:55 In the loop, on the loop, out of the loop

    • 17:10 Next time: what we traded away

    —

    Thanks for listening!

    We hope you dug today’s episode. If you liked what you heard, be sure to like and subscribe wherever you listen to podcasts! And if you really enjoyed today’s episode, why don’t you leave a five-star review? Or tell some friends! It will help us out a ton.

    If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

    • ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Get a FREE audiobook AND support the show⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

    • ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Support the show on Patreon⁠⁠⁠⁠⁠⁠⁠⁠⁠

    ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Check out show transcripts⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

    • ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Check out our website⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

    • ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on Apple Podcasts⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

    • ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on Spotify⁠⁠⁠⁠⁠⁠⁠⁠⁠

    ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on YouTube⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

    • ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on Stitcher⁠

    Mostra di più Mostra meno
    19 min
  • Not Invented Here: When “We’re Different” Is Just an Excuse to Ignore Outside Work
    Sep 17 2026
    Ever notice an idea gets a cold reception the moment it comes from another team? That’s Not Invented Here. This week I dig into why our brains treat “not ours” as “not good,” what it cost teams I worked on at GE, and how to catch it early.When your team says an outside idea “won’t work for us,” are you evaluating the idea, or just the team it came from?Not Invented Here is the tendency to reject or undervalue ideas, tools, and research that come from outside your own team, while overvaluing the stuff you built yourselves. The catch is that it never announces itself. It feels like you have standards, or you know your users, when really the source of the idea is doing the evaluating for you in the background. The term goes back to a 1982 study by Ralph Katz and Thomas Allen at MIT, who tracked fifty R&D groups and found that the longer a team stayed together, the less it talked to the outside sources it most needed to hear from. Performance slid as a result. Later work from David Antons and Frank Piller reframed it as an attitude rather than a behavior, a standing negative feeling toward anything labeled “external,” whether that label comes from a different company, department, discipline, or just a different job title.On product teams, this shows up everywhere once you start looking. Engineers’ UX suggestions get waved off because usability is “our lane.” Agency research gets its methodology questioned the second it contradicts the team’s assumptions, while a single hallway conversation gets treated as solid evidence. Ten squads rebuild nearly the same component ten different ways because the shared version doesn’t quite work for us, and then nobody trusts the design system anymore.If your team has ever quietly shelved a good finding because it came from the wrong people, this one’s for you. Give it a listen.Topics:• 00:00 - The reflex that rejects an idea before you've even looked at it• 03:00 - The GE story: a mandate to adopt one design system called Cirrus• 04:00 - Every team pushes back with the same "that won't work for us"• 05:00 - Defining not invented here and the 1982 Katz and Allen study• 06:00 - Why long-tenured teams stop talking outward, and the shift from behavior to attitude• 07:00 - Why your brain does it: ownership, effort, identity, and the IKEA effect connection• 08:00 - The measurable cost, and Spolsky's defense of building in-house• 09:00 - How the bias hides behind "our context is different"• 10:00 - How it hits research and design systems, and where the IKEA effect sneaks in• 11:00 - Engineering rewrites, competitor patterns, and acquired teams• 12:00 - Turning the bias around with "proudly found elsewhere"• 13:00 - Separate the source from the substance, and watch your team's own boundaries• 14:00 - Give ownership before adoption, and treat build versus adopt as a real decision• 15:00 - Audit your outside input, and back to the Cirrus lesson—Thanks for listening! We hope you dug today’s episode. If you liked what you heard, be sure to like and subscribe wherever you listen to podcasts! And if you really enjoyed today’s episode, why don’t you leave a five-star review? Or tell some friends! It will help us out a ton.If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.• ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Get a FREE audiobook AND support the show⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Support the show on Patreon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Check out show transcripts⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Check out our website⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on Apple Podcasts⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on Spotify⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on YouTube⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on Stitcher⁠
    Mostra di più Mostra meno
    17 min
  • When Figma Was Just How We Worked // What Survives E01
    Sep 9 2026
    A late-night DM from a listener named Chris asked me something I couldn’t answer: did I lose my identity as a designer? My team just went one hundred percent Cursor, no more Figma. This season, I figure out what AI actually changes about the work, and what it never touched.When the tool that defined your job for a decade disappears overnight, what part of “designer” actually leaves with it?This is the first solo season in the history of Beyond UX Design. No guests, no interviews, just me working through one question that landed in my DMs late one night from Chris, a listener I’ve known for years. He asked whether I felt like I’d lost my identity as a designer after my team dropped Figma and went fully into Cursor. My gut said no. Thirty seconds later, I realized I didn’t actually know. That question became this whole season.Episode one is about the world right before the change, back when Figma was just how we worked. I walk through what a normal design process looked like on my team, and then I get honest about something we don’t talk about enough: how much of “being a good designer” got quietly measured by tool fluency. Named layers, auto layout, clean files. None of that is capital-D design, but it stood in for it because it was the thing we could see, screenshot, and post about on LinkedInI also take on a good question from the original LinkedIn thread that inspired this. If you could always design and build in code, why is this suddenly a big deal now? My answer comes down to opportunity cost, and it reframes what AI actually changed. Spoiler: it wasn’t the ability to code. It was the time. If any of this sounds familiar, whether your team already made the switch or you can feel it coming, hit play and come along for the season.Topics:• 00:00 – The DM from Chris: “Do you feel as if you lost your identity as a designer?”• 02:40 – The late-night LinkedIn message• 03:20 – Why the identity question never crossed my mind• 04:10 – 127 comments, and why they were almost all tactical• 05:30 – This isn’t just a designer problem: PMs and engineers too• 06:00 – What “normal” looked like: the old design-to-handoff process• 07:30 – How designers quietly ranked each other on tool fluency• 09:20 – Why tool skills got mistaken for design skills for a decade• 10:40 – Derek’s challenge: “We could always design in code, so why now?”• 11:20 – My front-end dev origin story and why it doesn’t settle the debate• 12:50 – The real answer: opportunity cost, not ability• 13:50 – What AI actually changed: collapsing the time to do both• 14:40 – Were there warning signs? The pilots I read as experiments• 16:00 – The real danger isn’t replacement, it’s belief• 16:30 – What survives so far: research, flows, judgment, taste• 17:10 – What still gets me, and a look ahead to episode two—Thanks for listening! We hope you dug today’s episode. If you liked what you heard, be sure to like and subscribe wherever you listen to podcasts! And if you really enjoyed today’s episode, why don’t you leave a five-star review? Or tell some friends! It will help us out a ton.If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.• ⁠⁠⁠⁠⁠⁠⁠⁠⁠Get a FREE audiobook AND support the show⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠Support the show on Patreon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠Check out show transcripts⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠Check out our website⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on Apple Podcasts⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on Spotify⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on YouTube⁠⁠⁠⁠⁠⁠⁠⁠⁠• ⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe on Stitcher⁠
    Mostra di più Mostra meno
    19 min
adbl_web_anon_alc_button_suppression_t1
Ancora nessuna recensione