You keep hearing that UX and product designers should build. Yet, most designers don’t.

Why is that? Are designers right? Is it just a case of social media nonsense?

To find out, we looked at what happens when someone actually does it.

Not a side project they’ll finish later (but never do) or another concept that never makes it out of Figma.

It is a real product and it is live. All in one weekend. And for Tyler, the designer who built it, it changes everything.

In this episode of the Design Table Podcast, we discuss just that; what actually happens when a designer stops talking about building and forces the constraint to ship something real.

We get into the tools, the process, and what surprised us once the product was live and usable.

But more importantly; what this changes about how you think about your career (and what stays the same).

Because once you realize it’s possible to go from idea to something real that fast, you stop looking at job applications, portfolios, and “waiting your turn” the same way.

This episode is about what happens when the builder mindset stops being theory and becomes real.

In this episode you’ll learn:
🔸 Why most designers stay stuck in the idea phase
🔸 What actually happens when you try to ship in a weekend
🔸 The tools that make building possible without a dev team
🔸 What surprised us after launching something real
🔸 Why this changes how you think about portfolios and jobs
🔸 What it means to stop waiting and start building

⏱ Chapters
00:00 From layoffs to building
05:00 Why talking about building isn’t enough
10:00 The weekend challenge
15:00 Tools used to build the product
20:00 What actually worked and what didn’t
26:00 What changed after shipping
32:00 Why this changes your career strategy

Subscribe to The Design Table Podcast
https://www.designtablepodcast.com/subscribe

More about Tyler and Nick
Tyler: https://www.designtablepodcast.com/hosts/tyler-white
Nick: https://www.designtablepodcast.com/hosts/nick-groeneveld

You lose your job. No warning. Or maybe you felt it coming. Either way… now you’re sitting there thinking:

“What the hell do I do next? How do I find a new product design role?!”

In this episode of the Design Table Podcast, we discuss what actually happens after getting laid off as a product designer and how to succeed at the job search that follows.

We talk about the emotional side of layoffs, what goes through your head in those first few days, and how quickly reality sets in when you realize you need to find your next role.

We also get into real strategies that worked for us (we found out the hard way), including how job searching has changed, why job boards aren’t as effective anymore, and how to approach applications in a much more intentional way.

This episode is about getting back on your feet and moving forward with a plan. It is a must-listen for any designer who's been part of layoffs or is preparing for their next role.

In this episode you’ll learn:
🔸 What goes through your mind after getting laid off
🔸 Why job boards don’t work like they used to
🔸 How the design job market has changed
🔸 The difference between volume and quality applications
🔸 Why tailoring your resume actually matters
🔸 How to manage rejection without burning out

⏱ Chapters
00:00 Getting laid off as a designer
03:00 The emotional aftermath
07:00 Job search strategies then vs now
12:00 Why job boards are less effective
18:00 Volume vs quality applications
24:00 Building a real application strategy

Subscribe to The Design Table Podcast
https://www.designtablepodcast.com/subscribe

More about Tyler and Nick
Tyler: https://www.designtablepodcast.com/hosts/tyler-white
Nick: https://www.designtablepodcast.com/hosts/nick-groeneveld

You join a new company. First of all; congratulations!

You arrive on day one and what do you see? There are engineers, product managers, marketers, and a sales team. But there is no design team. Turns out you are the only product designer. Yikes!

In this episode of the Design Table Podcast, we discuss what it’s actually like to be the first or only designer at a company, how product designers can survive those early months without burning out, and how you can start to build real design influence.

We talk about the reality of introducing design into organizations that have never had it before, why trying to fix everything at once usually goes wrong, and how to gradually build trust across engineering, product, and leadership.

This episode is about learning how to create impact when you’re alone. It is a must-see for founding designers, startup designers, and anyone stepping into their first solo design role.

In this episode you’ll learn:
🔸 What to focus on during your first 30–90 days as the only designer
🔸 Why improving the process is more important than perfect design
🔸 How to build allies across engineering and product teams
🔸 Why presenting aesthetics alone often fails
🔸 How internal usability tests can build credibility quickly
🔸 How to grow design influence inside non-design organizations

⏱ Chapters
00:00 The reality of being the only designer
03:00 Tyler’s founding designer experience
07:00 Why you shouldn’t try to fix everything at once
11:00 The “meet in the middle” process strategy
15:00 Why design language must change for stakeholders
20:00 Meeting everyone across the company
24:00 Using usability tests to build influence
29:00 The politics of internal visibility
33:00 When to take work outside your role
38:00 When it’s time to grow the design team

Subscribe to The Design Table Podcast
https://www.designtablepodcast.com/subscribe

More about Tyler and Nick
Tyler: https://www.designtablepodcast.com/hosts/tyler-white
Nick: https://www.designtablepodcast.com/hosts/nick-groeneveld

Designers can ship code now. That's what social media and your manager is telling you. AI tools, vibe coding, and new prototyping workflows mean designers are getting closer to production than ever before.

But just because we can ship faster doesn’t mean we should.

In this episode of the Design Table Podcast, we discuss the growing pressure for designers to ship quickly, why the “just ship it” mindset can backfire, and how teams should think about quality in a world where building things fast seems more important than building things well.

We talk about the collapse of the gap between design and engineering, why shipping too fast can remove the “bad idea filter,” and why guardrails (like pull requests and review processes) are becoming essential.

This episode is about navigating speed, experimentation, and responsibility in modern product teams. It is a must-see for designers trying to understand how AI and new tooling are changing the role of product design.

In this episode you’ll learn:
🔸 Why designers are starting to ship production code
🔸 The hidden risk of the “just ship it” culture
🔸 How AI tools are accelerating product experimentation
🔸 Why teams need guardrails when everyone can ship
🔸 When rapid experimentation actually improves products
🔸 How pull requests and reviews protect product quality

⏱ Chapters
00:00 Everyone is shipping now
02:00 Designers getting access to GitHub
06:00 The rise of vibe coding
09:00 The “bad idea filter” problem
13:00 When shipping fast hurts product quality
18:00 Why too many people shipping creates chaos
22:00 Pull requests as design guardrails
26:00 The danger of constant product changes
30:00 Nick ships an AI-built feature

Subscribe to The Design Table Podcast
https://www.designtablepodcast.com/subscribe

More about Tyler and Nick
Tyler: https://www.designtablepodcast.com/hosts/tyler-white
Nick: https://www.designtablepodcast.com/hosts/nick-groeneveld

AI won’t replace designers. But designers who don’t know how to use AI properly are already falling behind. That's what you see a thousand times a day on social media. It is maddening.

In this episode, we counter that and go deep on how two product designers actually use AI in real design projects. No LinkedIn hype. No “just vibe code bro.” Instead, we talk about prompting, context building, early-stage exploration, and where AI genuinely saves time versus where it doesn't.

We discuss how AI fits into modern product teams, how designers are replacing wireframes with working prototypes, and why prompting is quickly becoming a core design skill.

This episode is for designers who want to move faster without losing their mind.

In this episode you’ll learn:
🔸 Why prompting is more important than the tool you use
🔸 How to structure prompts with goals and context
🔸 When AI should explore ideas vs. deliver output
🔸 Why wireframes are getting replaced by working prototypes
🔸 The real meaning of “vibe coding” (and what it is not)
🔸 How AI fits into professional, production-level workflows
🔸 Why generalist designers adapt faster to AI-driven teams

⏱ Chapters
00:00 Why designers struggle with AI adoption
03:18 What “vibe coding” actually means
07:02 Context first, prompts second
10:22 Replacing wireframes with real prototypes
14:05 AI as exploration, not final output
18:41 Prompting mistakes designers keep making
23:12 When to restart instead of fighting the model
28:10 Making prototypes realistic for stakeholders
33:05 Prompting tips that actually work
41:02 Why AI reinforces the generalist shift

Subscribe to The Design Table Podcast
https://www.designtablepodcast.com/subscribe

More about the hosts
Tyler: https://www.designtablepodcast.com/hosts/tyler-white
Nick: https://www.designtablepodcast.com/hosts/nick-groeneveld

Should you specialize or become a generalist as a product designer?

Everyone has an opinion. Social media says pick a niche. Job listings say “end-to-end.” Who's right?! Designers are stuck wondering which path actually leads to getting hired and staying hired.

In this episode, we solve the generalist vs. specialist debate from the reality of today’s product teams. We talk about why pure specialists are becoming risky outside of massive enterprises, why generalists are quietly back in demand, and how the best designers are combining deep industry knowledge with end-to-end execution.

This episode is based on real hiring trends, Tyler's in-house experience, Nick's freelance work, and what actually happens inside modern product teams.

In this episode you’ll learn:
🔸 Why being “only good at one thing” limits your career options
🔸 When specialization actually makes sense (and when it doesn’t)
🔸 Why startups and mid-size companies favor end-to-end designers
🔸 How generalists gain more influence, visibility, and context
🔸 The hidden career risk of staying siloed in one skill
🔸 How industry knowledge becomes the real specialization over time

⏱ Chapters
00:00 Are you a generalist or a specialist?
02:30 Skill specialization vs industry specialization
05:37 Why pure specialists struggle outside big companies
09:03 Visibility, collaboration, and career growth
13:05 Design systems, scaling, and cross-team impact
18:49 Go wide first, then go deep
22:36 Hiring trends and shrinking teams
26:30 Why the generalist is back

Subscribe to The Design Table Podcast
https://www.designtablepodcast.com/subscribe

More about the hosts
Tyler: https://www.designtablepodcast.com/hosts/tyler-white
Nick: https://www.designtablepodcast.com/hosts/nick-groeneveld

Your stakeholders say research is a waste of time. Just ship it. We’ll figure it out later. But later never comes. The product misses the mark, teams scramble, and you end up doing twice the work fixing mistakes you saw coming weeks ago. Relatable? For many designers it is...

In this episode, we’re joined by Sara Fortier, CEO of Outwitly and author of Design Research Mastery, to talk about just that, what design research really looks like today, and why it’s becoming more important as AI becomes bigger and bigger.

We talk about why research is less about methods and more about influence, how junior designers can stand out in today's super competitive market, and why the future favors designers who can connect business risk, human behavior, and product decisions instead of just pushing pixels.

In this episode you’ll learn:
🔸 Why design research is an insurance policy against bad decisions
🔸 How to introduce research in low-maturity teams without asking permission
🔸 Why AI won’t replace research but will raise the bar for designers
🔸 How junior designers can use research to stand out and get hired
🔸 When research should be deep, lightweight, or skipped entirely
🔸 Why UX generalists are becoming more valuable than narrow specialists

⏱ Chapters
00:00 Why teams say research slows them down
03:18 Research vs taste, craft, and AI hot takes
07:02 Finding champions inside low-maturity orgs
10:22 Asking forgiveness instead of permission
14:05 Research as risk reduction and ROI
18:41 Why generalists are winning again
23:12 AI, research, and the future of design roles
28:10 What junior designers should focus on right now
33:05 Tools that actually help researchers today
41:02 The skills AI can’t replace

Learn more about Sara’s book
https://www.designresearchmastery.com/

Connect with Sara on LinkedIn
https://www.linkedin.com/in/sarafortier/

Learn more about Outwitly
https://outwitly.com/

Subscribe to The Design Table Podcast
https://www.designtablepodcast.com/subscribe

More about the hosts
Tyler: https://www.designtablepodcast.com/hosts/tyler-white
Nick: https://www.designtablepodcast.com/hosts/nick-groeneveld

Users say one thing. Then they do something completely different. Nick, co-host at the Design Table Podcast, just found out the hard way.

In this episode of the Design Table Podcast, we discuss why user feedback can be misleading, why badly framed research creates false confidence, and how designers should really think about data and user research.

We talk about research methods that fail in practice, why people lie during tests, and how relying on a single data point can completely derail your product design decision making.

This episode is about moving beyond performative research and building confidence in your decisions using the right mix of qualitative and quantitative signals. It is a must-see for any designer who's interested in UX research.

In this episode you’ll learn:
🔸 Why users lie
🔸 How poorly framed questions ruin your UX research outcome
🔸 When usability testing beats surveys
🔸 Why screenshots and explanations often get ignored
🔸 How to triangulate research instead of trusting one signal
🔸 When to trust data and when to trust experience

⏱ Chapters
00:00 “Users lie” and the research crisis
04:00 Why feedback doesn’t match behavior
09:00 Choosing the right research method
15:00 Unmoderated vs moderated testing
21:00 SUS scores and false certainty
27:00 A simple research framework that works
33:00 Why research matters more in an AI-driven world

Subscribe to The Design Table Podcast
https://www.designtablepodcast.com/subscribe

More about Tyler and Nick
Tyler: https://www.designtablepodcast.com/hosts/tyler-white
Nick: https://www.designtablepodcast.com/hosts/nick-groeneveld