What Today’s Product Conversations Are Really About

The Meeting That Wouldn’t End

Last week, I sat in on a project review that ran forty minutes over time. Not because the team was unprepared—but because no one could quite agree on who was supposed to decide what happened next.

The designer was waiting for clearer constraints. The project manager was tracking dependencies and timelines. The product manager was trying to understand whether the customer insight was strong enough to justify a shift in direction. Everyone was competent. Everyone cared. And still, the conversation kept looping.

I’ve seen versions of this meeting everywhere lately—in client engagements, in community discussions, in the articles making the rounds this week. On the surface, they’re about roles: product vs. project management, how UI/UX professionals work with others, why user research feels harder than it used to. But underneath, they’re circling a deeper tension.

We’re struggling to agree on where judgment lives when the work is complex, human, and no longer neatly bounded.

When Roles Blur, Responsibility Gets Louder

A lot of recent writing tries to redraw clean lines. Project managers manage delivery. Product managers manage outcomes. Designers design interfaces. Researchers gather insights. In theory, this clarity should help.

In practice, the work refuses to stay inside those boxes.

Take the ongoing debate about product management vs. project management. I’ve worked with exceptional people in both roles, and the most effective teams I’ve seen don’t obsess over definitions. They obsess over decisions.

Here’s what I notice instead:

Project managers are increasingly asked to make judgment calls about scope tradeoffs that directly affect user experience.
Product managers are pulled into operational detail because timing and sequencing now shape strategy.
Designers are expected to advocate for users in rooms where user research is incomplete or ethically constrained.

According to a 2024 PMI survey, nearly 60% of project managers report being asked to contribute to product strategy decisions, not just execution. That’s not role confusion—it’s reality catching up with how intertwined these decisions have become.

The problem isn’t blurred roles. It’s unclear ownership of judgment.

When no one is explicitly responsible for making sense of tradeoffs, everyone feels the weight—and meetings get longer, not better.

Research After Certainty

Nowhere is this more visible than in user research.

Several of the conversations this week focused on post-COVID research realities: safeguarding plans, in-person ethics, working in health, education, and social care contexts. These aren’t just logistical updates. They’re reminders that research isn’t neutral work.

I was recently advising a team doing in-person discovery with frontline healthcare workers. The original research plan was solid on paper—consent forms, session guides, success metrics. But two days into fieldwork, the team realized something uncomfortable.

Participants were emotionally exhausted. Not disengaged—overextended.

Continuing exactly as planned would have produced data. But it would have violated the spirit of care that made the research worthwhile in the first place.

So the team adapted:

Shortened sessions by 30%
Let participants opt out mid-session without explanation
Treated incomplete data as a signal, not a failure

The result? Fewer transcripts. Better insight.

This aligns with a broader pattern. The Nielsen Norman Group reports that research studies prioritizing participant well-being see up to 25% higher insight validity, largely because participants are more candid when they don’t feel managed.

The quiet shift here is important: good research now requires moral judgment, not just methodological rigor.

Evidence Is Cheaper. Sensemaking Is Not.

One article making the rounds this week described how ten customer conversations over two weeks unlocked $2M for a Fortune 500 company. It’s a great story—and a true one. I’ve seen similar outcomes.

But there’s a misleading takeaway floating around: that talking to customers is the hard part.

It isn’t.

What’s hard is deciding what to do after you hear something inconvenient.

I once worked with a fintech team that ran a tight, structured interview program. Clear scripts. Clean synthesis. Strong themes. One insight kept surfacing: small business users didn’t trust automated decisions, even when outcomes were favorable.

The data was consistent. The implications were uncomfortable.

Addressing that distrust meant:

Slowing down certain flows
Adding explanation instead of efficiency
Accepting slightly lower short-term conversion

The metrics argued against it. The people didn’t.

Ultimately, the team chose to redesign the experience without adding a single new feature—just clearer language, better timing, fewer surprises. Three months later, support tickets dropped by 18%, and retention improved modestly but steadily.

This echoes another trend piece: improving UX without changing features. It’s not magic. It’s respect for cognitive and emotional load.

As one study from Google’s UX research team puts it, perceived usability is often more predictive of loyalty than raw task speed.

The Cost of Uncertainty (And Who Pays It)

Another article circulating says: Users don’t resist change. They resist uncertainty. That line stuck with me because it reframes so many “adoption problems” I see teams wrestle with.

When adoption is low, the instinct is to push:

More onboarding
Louder announcements
Stronger nudges

But uncertainty isn’t solved by volume. It’s solved by trust-building over time.

Here’s where team dynamics matter.

If product, design, and research aren’t aligned on:

What uncertainties users are carrying
Which ones matter most
Which ones the product can responsibly resolve

Then the burden shifts to the user.

And users respond predictably: hesitation, workarounds, silence.

A McKinsey study found that 70% of digital transformation initiatives underperform largely due to user resistance rooted in unclear value and trust, not technical failure. That’s not a UX problem alone. It’s a collective decision-making failure.

What I’m Seeing Beneath the Noise

When I step back from this week’s conversations, a pattern emerges.

We’re not actually debating tools, roles, or methods.

We’re asking:

Who is responsible for making hard calls when data is incomplete?
How much care are we willing to extend—to users, participants, teammates—when speed is rewarded?
What does good judgment look like when no framework fully applies?

The teams that navigate this well tend to do a few things consistently:

They name tradeoffs out loud. Not as risks to mitigate, but as values in tension.
They protect space for sensemaking. Not every insight needs immediate action.
They assign decision ownership explicitly. Collaboration doesn’t mean consensus.
They treat uncertainty as a design input, not a flaw.

None of this shows up cleanly in job descriptions or process diagrams.

But it shows up unmistakably in outcomes.

The Work We Don’t Screenshot

There’s a kind of product work that doesn’t travel well on social media. It doesn’t fit neatly into case studies. It happens in long meetings, uncomfortable pauses, revised plans, and quiet decisions that never get attributed to anyone.

It’s the work of judgment.

As product leaders, designers, researchers, and project managers, we’re being asked to do more of this than ever before—often without explicit permission, sometimes without support.

My hope is that instead of arguing about who should own which piece, we get better at recognizing when the work has crossed from execution into judgment—and treating it with the seriousness it deserves.

Because when we don’t, someone still pays the cost.

Usually, it’s the user. Sometimes, it’s the team. Often, it’s both.

And the meeting runs forty minutes over.

— Jordan Taylor