# 014 When Product and Design Roles Blur ![[images/Pixels-and-Priorities-artwork.jpg]] Part of [[Pixels & Priorities]] (listed in [[Pixels & Priorities - Audio Episodes 001-014]]). Previous: [[013 Build Your Network Before You Need It]]. Next: [[015 The Rise of AI Builders]] (listed in [[Pixels & Priorities - Audio Episodes 015-031]]). - Show: Pixels & Priorities, hosted by Metsy Rose and J Schuh (RSS author field) - Episode: 014, published 2026-06-30 (RSS pubDate Tue 06:00 -0500); host-only, no guest - Audio: https://dts.podtrac.com/redirect.mp3/mcdn.podbean.com/mf/web/mswisfr26bwpt36f/PP_014_Roles_Trust_AI_Edited.mp3 - Podbean page: https://pixelsandpriorities.podbean.com/e/014-when-product-and-design-roles-blur/ - Length: 46:37 (2,797.9 s measured from the mp3). The RSS `itunes:duration` says 2797 s (46:37), matching the file. - RSS description: "We explore how AI is blurring product and design roles, why trust matters more than ever, and how curiosity, communication, and feedback help teams move faster without losing perspective." - No episode-specific artwork in the feed, so the note uses the show artwork. - Transcript: faster-whisper (medium, int8, CPU) on the mp3 with VAD on, beam size 5 (about 7.4 minutes of transcription). That pass dropped or garbled a number of stretches (including 1:00-1:25, 2:20-4:10, 5:08-6:05, 7:05-7:50, 8:25-10:50, 17:40-18:10, 19:10-20:10, 23:20-25:00, 30:30-31:06, 35:15-35:35 and 40:20-44:50), which were re-transcribed in short chunks with VAD off, for about 6,493 words in total. Small gaps remain around 4:22-4:42, 16:29-16:35 and 24:30-24:50. The feed's publisher transcript (Podbean VTT made with Descript, `PP_014_Roles_Trust_AI_Edited.vtt`, about 6,750 words) was used for the outline timestamps and to check names and wording. All quotes come from the Whisper transcript (case and stray-character fixes only). Speakers are not diarized; attribution follows content (J: the oil painting, his teaching, the UX coach interviews, psychological safety, his 25 years, Black Mirror, the workshop-facilitator role; Metsy: the product-manager perspective, her developers, the employee who had to ask questions, reading a room, DiSC). Where a line is uncertain it says "likely." Correct spellings are **Metsy Rose**, **J Schuh** and **Kirsten** (Rourke; Whisper heard "Cristin"). ## Hosts - **Metsy Rose** - co-host; product manager and strategist (show open). Says she has often worked in roles with unclear edges; has a strong technical, systems-thinking background but has not been a full-stack developer. Works with developers spread across the world and in matrixed organizations where no one reports directly to her. Has managed people, and leaders have relied on her ability to read a room. A fan of DiSC and related assessments. - **J Schuh** - co-host; design strategist, educator, and creative mind (show open). Teaches a class and uses his oil-painting story in it. Started at one company as a UX coach evangelizing user experience; says he has been doing his work for 25 years. Likely the host who describes being a front-end developer, a business owner with up to 40 people on client projects, and a PM. Met Metsy at an organization that brought him in as a workshop facilitator. A Black Mirror fan. ## Outline (timestamps are mm:ss) - **0:00 Show open.** Metsy Rose introduces herself (product manager and strategist) and J Schuh (design strategist, educator, and creative mind). - **0:27 Roles are shifting.** Metsy says a topic from the Brian Sullivan conversation is also the main reason they started the podcast: design, product, developer and research roles are shifting fast amid rapid change and AI in every area of technology. She asks J what he thinks about the changing roles. - **1:25 UX designer or product designer?** J describes the debate in UX over whether to keep calling themselves UX designers or reposition as product designers (Brian suggested product researcher and product developer too). Nobody knows what putting "product" in front of a role really means for ways of thinking, responsibilities and communication; it opens a Pandora's box, and with AI and shifting priorities he expects a big shift soon. - **2:52 Blurry edges and two levels of work.** Metsy says the shift is already happening. She has often worked in roles with unclear edges and finds that a source of growth, but also stress. People will keep doing tactical work while periodically pulling out into a strategy mindset (a prototype one moment, a roadmap the next), and those two levels are hard to hold at once. - **4:35 Too close to the canvas.** J tells a story he uses in his class: in his early 20s he spent about 100 hours teaching himself oil painting on an African river sunset scene with a silhouetted boatman. His roommate Mike Mullins asked, "Why is he rowing uphill?" The horizon was slanted. J threw a fit, angry at himself, and the next time Mike just praised everything. J calls this being too close to the canvas: zoom out to see the big picture, because what you miss ripples out to stakeholders and leadership, and people who care about their work find feedback hard. - **8:17 Communication across new domains.** J wonders how good team communication is today and how it will cope when people move into domains where it is easy to misunderstand fundamentals. Where does a product designer's role begin and end? Will they own analytics, and what if two people disagree on direction? - **9:24 Fail early, fail often.** Metsy plans to steal the analogy. She notes J got feedback only after 100 hours; because she has a poor sense of time she institutionalizes fail fast, fail often and regular feedback, and says the podcast itself is built with a product mindset: build fast, get feedback, get better, don't dwell. - **10:44 Decisions at light speed.** As a new UX coach evangelizing UX, J interviewed PMs; one told him decisions she made three years earlier were the ones she was dealing with now. With AI accelerating decisions, J asks whether teams will just go faster in the wrong direction, and what rework fixing a bad path will take. - **12:31 The bug on the windshield and trust.** Metsy pictures a bug on a windshield: more speed and untested AI tools mean more mistakes. Her goal as a new product person on a team is to build trust so people will warn her about a bug coming, and so she can say "I have new information, and therefore I can change my mind." She values developers who flag delicate parts of the ecosystem; mutual trust across product, research, design and dev matters more as roles blur. - **15:06 Psychological safety and questions.** J ties trust to psychological safety. Corporate culture often treats many questions as incompetence or pushback, or answers "Don't ask me any questions, just do it," which he calls toxic. Questions signal curiosity and de-risk projects; had he asked his roommate at 10 hours, the slanted waterline would have been easy to fix. He says curiosity is one of the primary skills of the future. - **17:40 Make questions a habit.** The hosts agree trust grows when asking questions is a normal part of how a team communicates. A manager (likely Metsy) recalls an employee from a toxic organization who had been treated as a troublemaker for asking questions; for about six months he had to ask her three to six questions a day, work or not, until he trusted that her response would always be measured. - **18:59 Automation and humanity.** Metsy says AI automation will require teams to call more on each other's humanity for the complexity AI can't automate. Each person's background shapes the fuzzy edges of their role (a PM who was a full-stack developer brings something different from her systems-thinking technical background), so people need to meet each other as humans. - **20:16 Managing expectations up front.** J (likely) recalls being a front-end developer, a business owner with up to 40 people on client projects, and a PM, and says communication will need a "double-click" as roles shift; humans are not as good at conflict resolution and empathy as they need to be. When he met Metsy he told her what he was not good at and what he was exceptional at, to manage expectations. Metsy found it unusual but a great trust builder: build on your strengths, let the person next to you fill in, and expecting 100% on every task is "a recipe for burnout." - **25:16 The unicorn myth and false alignment.** J recalls Kirsten's (Kirsten Rourke, episodes 009-010) alternative view of the unicorn and a cartoon of three people thinking of a circle, a triangle and a square while saying "We're aligned." Without clarifying questions there is huge room for error, time, cost and risk. - **26:24 From IC to leader.** Great individual contributors are promoted into leadership, a whole other skill set; leaders who can't read the room miss cues until they find themselves out the door. Metsy compares it to making the best salesperson head of sales or the top solutions architect head of development, says those skills can be learned, and describes leaders who relied on her to read a room, including noticing a colleague whose spouse had died three weeks earlier. - **29:44 Who does what now?** Metsy asks whether product designers will ship, engineers do user research and PMs build prototypes. Managing defined roles is easier than teams where each pod covers the product life cycle differently; a manager will manage the life cycle, not people in boxes. - **31:19 Hiring and team dynamics.** J asks how anyone will hire for such roles, then turns to team dynamics: replacing a departed teammate with someone of similar skills still unsettles a well-functioning team ("Hey, man, I miss Bob"; Nancy who had been there 20 years and knew everybody), and multiplying the expertise each role needs makes this more complex. - **33:27 Experience versus the video you watched.** J describes being told to change something by a colleague who read a book or watched a video, after his 25 years. Veterans need to stay open to suggestions and newcomers need to be mindful that one video may not be best for the product; soft skills, conflict resolution and leadership will be the skills of the future as AI automates the rest. - **35:12 No formal authority.** Metsy says these human dynamics will only become more apparent. In agile, matrixed organizations no one reports directly to her as a PM, yet she must get hard choices implemented; more automation means more dependencies for the human team to manage, even if no human writes the code. - **36:45 Heads-up human interaction.** J notes that taking away tactical work removes the escape into code or (Metsy adds) a Figma rabbit hole, leaving more "heads-up human interaction," which colleges aren't teaching. He adds generational differences as another complicating ingredient. - **38:09 Distributed teams.** Metsy says her developers are rarely local; they are spread across the world, languages and time zones, so companies banking on AI and IT infrastructure, which are struggling to get value from it now, will need to focus on the human side. - **38:59 How do you hire for human skills?** J says human skills are hard to measure because culture varies. Hired as a workshop facilitator where he met Metsy, he knew no one would understand his value until they saw him in action; leadership changes force everyone to relearn a new boss. - **40:49 Assessments and rebuilding teams.** Metsy is a fan of some business assessments, especially DiSC, for team building and expects them to return. When one person changes in a strong team, progress slows while the team rebuilds its infrastructure, which is a valuable step that takes skill to lead. - **42:15 Know yourself.** Metsy says it all comes back to understanding yourself: what you're naturally good at, what you gained through practice, and where someone else should take over. Her goal is to get better at articulating who she is so others can work with her. - **43:46 AI interviews and bias.** J, a Black Mirror fan, imagines AI conducting interviews and gauging reactions. Metsy warns hiring models can carry their builders' biases, and describes a video of an AI interviewer asking a candidate about his background, who answered by describing his Zoom background. - **45:16 Close.** J says it's a big question how humans will evolve in expanding roles and what AI's role will be. The hosts preview an upcoming episode with Shane Ward on changing product and design roles and today's hiring environment. Show outro. ## Standout quotes (verbatim from the Whisper transcript) - 5:33 "And he goes, why is he rowing up hill?" (J, quoting his roommate Mike Mullins) - 6:50 "We sometimes are so close to the work that we do that we don't zoom out to see the big picture." (J) - 12:06 "is that gonna be a challenge that you can go faster in the wrong direction?" (J) - 13:17 "is a bug coming toward my windshield and that takes trust." (Metsy) - 13:34 "I have new information and therefore change my mind." (Metsy) - 16:11 "That is a toxic response." (J, on "Don't ask me any questions, just do it") - 17:31 "Curiosity is one of the primary skill sets of the future to be adaptable in this very fast moving environment" (J) - 23:54 "My personal philosophy is it's a better choice to build on your strengths than to spend all your time trying to build on your weaknesses when the person next to you may be able to fill in." (Metsy) - 24:18 "I think it's a recipe for burnout." (Metsy) - 25:50 "everyone says we're aligned." (J, describing the circle, triangle and square cartoon) - 28:21 "when you make the best salesperson your head of sales a lot of people struggle with that" (Metsy) - 34:38 "I really do think that those soft skills, conflict resolution, leadership, those are gonna be the skill sets of the future as AI tends to automate all the things around us." (J) - 37:20 "So AI could be inadvertently creating this scenario where all of us are not adequately prepared to deal with the more heads up emotionally based Conversations" (J) - 38:50 "They're struggling to get value out of it now." (Metsy, on companies' AI investments) - 43:09 "My goal is always get better at articulating who I am to other people to help them understand how to work with me." (Metsy) ## Books mentioned - No books are named in this episode. (J mentions "all the books I'm reading" on leadership and a colleague who "read this book," without titles.) ## Things mentioned - People: Brian Sullivan and the Big Design Conference (episodes 012-013), Kirsten Rourke (episodes 009-010), Mike Mullins (J's former roommate), Shane Ward (upcoming guest), "Bob" and "Nancy" (example names). - Tools and media: Figma, DiSC assessments, Black Mirror, Zoom backgrounds, AI interviewers. - Ideas: UX designer versus product designer (and product researcher, product developer), too close to the canvas, fail fast fail often, the bug on the windshield, psychological safety, questions as curiosity and de-risking, fuzzy edges of roles, building on strengths, the unicorn myth, false alignment (circle, triangle, square), reading the room, IC-to-manager transitions, pods of people whose puzzle pieces fit, matrixed teams without formal authority, heads-up human interaction, generational differences, distributed teams, hiring for culture and human skills, bias in AI hiring tools. - Callbacks: the myth of the unicorn from [[008 Unicorns, T-Shapes, and the Myth of Mastery]] and [[010 Unicorns, Humans, and the Future of Creative Work]]; role shifts raised with Brian Sullivan in [[012 UX Research to Product Strategy in the AI Era]] and [[013 Build Your Network Before You Need It]]. ## Good work, productivity and career ideas - **Step back from the canvas.** Get feedback at 10 hours, not 100; mistakes are much cheaper to fix early (4:35-7:15, 16:28-16:52). - **Institutionalize feedback.** If you lose track of time, build fail-fast, fail-often checkpoints into how you work, as the hosts do with the podcast (9:24-10:41). - **Watch for speed in the wrong direction.** AI compresses decisions that used to take three years to show their effects; check direction before accelerating (10:44-12:31). - **Build trust so people warn you.** Spend early time on a new team building trust, invite developers to flag delicate areas, and be willing to change your mind with new information (12:31-15:06). - **Normalize questions.** Treat questions as curiosity and risk reduction, not incompetence; "Don't ask me any questions, just do it" is toxic. One manager had a wary employee ask three to six questions a day (15:06-18:58). - **Name your strengths and gaps up front.** Tell new partners what you're exceptional at and where you need a complement; build on strengths rather than expecting 100% on everything (21:54-24:20). - **Check that "aligned" really means aligned.** Ask specific clarifying questions before assuming shared understanding (25:27-26:24). - **Learn leadership as a skill.** A great IC promoted to manager needs to learn to read the room and ask the team to say when they're missing the mark (26:24-29:43). - **When a teammate leaves, expect a rebuild.** Give the team time to rebuild its dynamics rather than treating a replacement as a drop-in (31:35-33:27, 41:27-42:13). - **Balance experience and new ideas.** Veterans should stay open; newcomers should test one video's advice against what's best for the product (33:27-34:32). - **Invest in heads-up skills.** As AI removes heads-down work, communication, conflict resolution and empathy become the core skills (34:32-38:08). - **Know yourself and explain it.** Understand what you're naturally good at versus practiced at, and get better at telling others how to work with you (42:15-43:43). ## Claims check | Claim | Check | |---|---| | DiSC can be useful for team building (40:49) | DiSC is a widely used behavioral-style assessment based on William Marston's model; it's popular for team building but isn't validated for hiring decisions. | | AI hiring systems can inherit their builders' biases (44:15) | Widely documented; for example, Amazon dropped an experimental recruiting model in 2018 after it penalized resumes mentioning women. | | Companies are struggling to get value from AI investments (38:50) | Consistent with 2025-2026 surveys reporting that many enterprise AI pilots fail to show measurable returns; not quantified in the episode. | | Episode length | RSS 46:37 (2797 s); measured mp3 46:37. | ## Added context - Audio-only RSS episode (not on the YouTube channel). It follows the two Brian Sullivan episodes and sets up an upcoming conversation with Shane Ward on hiring for changing product and design roles.