Why a little friction is good for your product team

Two people playing tug of war

Frustration, not failure, is often where good product decisions begin.

It’s tempting to aim for perfect harmony in a product team: smooth meetings, unanimous decisions, consensus with no pushback. But when everything flows too easily, there’s a risk: no one’s challenging the status quo.

Friction isn’t just inevitable in cross-functional collaboration; it’s necessary. That’s especially true in B2B teams building complex products with long sales cycles, layered user needs, and multiple stakeholders.

When handled well, a little tension can sharpen thinking, expose blind spots, and bring more depth to decision-making. Done poorly, it causes confusion, resentment, and delays.

So, how do you use friction as fuel, not fire, for better outcomes?

Let’s explore how healthy disagreement can actually drive stronger strategic alignment in your product team.

Two people contradicting, one agrees and the other disagrees

Friction leads to better product decisions

When you bring people together with different perspectives, design, engineering, sales, and customer success, they’re bound to disagree. And that’s the point.

Done right, disagreement produces:

  • A broader range of ideas

  • A deeper understanding of the problem

  • Better-tested assumptions

  • More thoughtful trade-offs

Teams that always agree are usually not aligned. They’re just avoiding conflict. Worse, they might be trapped in groupthink.

In fact, studies have shown that workplace conflict, when productive, leads to better decisions and stronger engagement. It helps teams explore less obvious ideas, pressure-test assumptions, and spot opportunities for improvement.

But friction only works if the team environment supports it. That means:

  • Clear psychological safety

  • Open and transparent communication

  • Respect for each other’s roles and expertise

  • A culture of curiosity, not blame

Without those in place, conflict turns toxic.

That’s why strategic alignment isn’t about agreement. It’s about shared understanding, healthy challenge, and commitment, even when opinions differ.

Strategic alignment thrives on healthy debate

Strategic alignment doesn’t mean everyone agrees. It means everyone understands the "why" behind decisions, even if they’d choose differently.

In real product environments, especially B2B, achieving that alignment requires a level of friction. When designers push back on prioritising tech debt or engineers question UX trade-offs, those discussions can feel tense.

But when teams debate priorities and constraints transparently, they’re more likely to:

  • Align on real user needs

  • Understand business goals in depth

  • Feel ownership of the product vision

That’s the kind of alignment that sticks. It’s not surface-level buy-in. It’s deep, durable, and resilient when plans change.

An image of message bubbles with 3 different texts each saying Yes, Maybe, and No

Design sprints and conflict by design

One reason design sprints work so well is that they force disagreement early. Teams have to rapidly explore different ideas, debate solutions, and converge on one path.

The time-boxed structure and clear ground rules create space for constructive tension without it becoming personal.

In that environment, a little friction is energising. It helps teams:

  • Move faster by testing assumptions early

  • Avoid wasting time on ideas that don’t hold up

  • Align quickly before investing in building

That’s strategic alignment in action: moving forward with clarity, not just consensus.

UX research methodologies as friction tools

User research often introduces productive friction. It challenges internal assumptions with real-world data. When a research insight contradicts what a team believed, it can spark disagreement, but that tension is valuable.

By integrating UX research methodologies into your product process, you’re not just validating solutions, you’re provoking better conversations.

Make research a regular part of the rhythm, not just a checkbox before launch. Let it raise questions. Let it force trade-offs. That’s where the learning happens.

Leading through tension: The role of CPOs and product leaders

It’s up to product leadership to set the tone for how friction is handled. That means being comfortable with tension, modelling respectful disagreement, and making sure all voices are heard.

The goal isn’t to avoid conflict, it’s to manage it in a way that builds trust and momentum.

Here’s how strong product leaders create space for healthy friction:

  • Set clear goals and decision criteria

  • Define roles and responsibilities early

  • Promote alternative viewpoints, especially from quieter voices

  • Intervene when debates become personal or unproductive

This is especially critical in cross-functional collaboration, where power dynamics can easily distort conversations. If sales always wins, or if design always defers to engineering, your team isn’t aligned; they’re just complying.

True alignment requires balance, challenge, and shared ownership.

A hand drawn rock paper scissors game with text at the top saying Manage Conflict

Why comfort can be dangerous

Teams that avoid friction often mistake comfort for clarity. But smooth interactions aren’t always a sign of alignment. They can be a sign of disengagement.

When no one questions roadmaps, mocks, or priorities, it usually means:

  • People don’t feel safe pushing back

  • The team is rushing to ship, not to solve

  • Leaders are unintentionally signalling that a challenge isn’t welcome

In those environments, teams miss real risks. They build features no one uses. They scale ideas that haven’t been validated.

Without friction, teams work fast, but not focused.

When friction becomes a problem

Of course, not all tension is productive. Here’s when friction turns toxic:

  • Conflict is personal, not about ideas

  • Team members dominate conversations

  • Disagreements drag on without resolution

  • There’s no follow-through after decisions

To avoid this, anchor your team in shared outcomes, not egos. Return often to the product vision, the business goals, and what success looks like for your users.

Use tools that structure tension:

  • Pre-mortems before a launch

  • Red team reviews during planning

  • Decision logs to record how and why calls were made

These techniques help teams process friction, not bury it.

When that balance is in place, even disagreement can become one of your team’s strongest creative tools.

The upside of disagreement in product development

A little friction is good for your product team because it leads to sharper thinking, better decisions, and stronger strategic alignment.

It encourages diverse perspectives, reduces the risk of groupthink, and ensures that ideas are rigorously tested before being executed. But it only works when psychological safety, respect, and good leadership are in place.

A wooden-made used to illustrate people on a crowd while two are on a platform

Friction is a feature, not a bug

The best product teams aren’t the most agreeable. They’re the ones who can disagree productively, challenge assumptions, and stay aligned even through tension.

Especially in B2B environments, where complexity is high and stakes are long-term, friction is part of the work.

When your team has strategic alignment, psychological safety, and strong leadership, friction becomes a force multiplier, not a blocker.

Don’t aim for perfect harmony. Aim for productive tension, held in a container of trust.

That’s how great products and resilient teams get built.


Want to turn tension into a strategic advantage?

We help B2B product organisations build collaboration models that embrace healthy friction: reducing groupthink, encouraging rigorous thinking, and strengthening decision-making across product, design, and engineering.

Let’s talk about building a product team that thrives on smart disagreement and shared outcomes.


Previous
Previous

The UX debt no one budgets for, but everyone ends up paying

Next
Next

How can you identify when your product team is misaligned on mindset and priorities?