This Week’s Updates

Enabling the Team

How C-suite And Board Roles Are Being Reshaped Around AI by Tomas Chamorro-Premuzic
AI is not just changing frontline work, it is reshaping leadership itself, forcing executives and boards to rethink oversight, judgment and decision making as senior roles shift from authority and expertise toward adaptation, governance and human discernment.

How To Share Your Point Of View (Even If You’re Afraid Of Being Wrong) by Wes Kao
Sharing a point of view becomes more valuable as roles get more senior, but it lands best when people show their reasoning, explain why the problem matters, and match their language to their actual level of certainty.

Product Direction

Build To Learn Vs Build To Earn by Marty Cagan
Separating product discovery from product delivery clarifies why teams should build prototypes to learn about value, usability, feasibility, and viability, then build products to earn through reliability, scale, and support, so faster AI prototyping sharpens strategy only when teams stay clear on which mode they are in.

Synthetic Certainty: The Hidden Risk Of Genai In Product Discovery by Johannes Schott
GenAI can make product discovery feel clearer than it really is, producing polished interpretations that mask weak evidence, so teams need to stay close to raw signals and treat AI synthesis as a prompt for scrutiny rather than proof of understanding.

Continuous Research

Deprivation Studies: Take The Product Away To Reveal What Users Truly Need by Jakob Nielsen
Taking a product away for a period reveals which habits, dependencies, and workarounds actually matter, helping teams separate real value from feature bloat, captive usage, and self-reported fiction.

Ethnography Finds What Interviews Miss. Almost No B2b Product Team Does It. by Else van der Berg
Interviews and analytics surface what customers can explain, but ethnography reveals the hidden workarounds, routines and unmet needs they no longer notice, helping teams find higher value opportunities that standard discovery methods miss.

Continuous Design

Beyond The User: Why Design Needs To Widen Its Circle by Dora Czerna
Designing only for the immediate user can hide wider harm, so expanding the brief to include ecosystems, supply chains and long term impact helps teams make better design decisions without losing the strengths of human centred practice.

Claude Design Is A "clock Time" Solution For A "calendar Time" Problem by Pavel Samsonov
AI can speed up artifact production in clock time, but design work still depends on slower calendar time for coordination, reflection and shared sense making, so teams that optimise only for faster outputs risk creating more noise while weakening the conditions good decisions depend on.

Continuous Development

AI Fatigue Is Real And Nobody Talks About It by Siddhant Khare
AI speeds up individual tasks but can make development more exhausting by shifting effort into review, coordination, tool churn and nonstop decision making, so teams need guardrails and working habits that protect deep focus, judgment and sustainable pace.

The "Negative Split" Software Engineering Effect by Anton Zaides
Trying to go faster too early in software development often burns teams out later, so the better path is to slow down enough to build context, quality and stable foundations first, then speed up when the system can actually sustain it.

Seen an interesting article online? Share it with us, and we might feature it in our next issue!
Click here to share an article

Win A Team Pass To UXDX San Francisco

Don’t wait, apply now!

We’re giving one product team the chance to attend UXDX San Francisco 2026 together for free. Apply through the form, tell us what your team is doing well in AI and what you want to improve next, and UXDX will shortlist four teams to be featured in a LinkedIn community vote!

The team with the most votes will receive up to 5 tickets to UXDX San Francisco. More details and the form can be found here: Apply for a UXDX San Francisco team pass

FREE COMMUNITY EVENTS 

Video Of The Week

From Output to Outcome:
Driving Cultural Change in Product Teams

Moving from outputs to outcomes sounds simple, but it usually requires a much deeper shift in how teams define success, make decisions, and work together.

In this talk, Jay shares how Eneco moved toward a more customer-centric and value-driven way of working, using continuous discovery and delivery to connect product, design, and engineering around real customer value. A useful watch for anyone trying to move beyond feature delivery, rethink KPIs, and build the culture needed for outcome-driven product work. Check it out below:

Want to go into how careers and leadership are shifting as AI compresses the ladder? My ebook Managing Your Career In The Age Of AI explores how to build judgment, relationships, and influence in a world that keeps trying to automate the surface of the work.