article thumbnail

How to Leverage Conflict in Product Management

Roman Pichler

Listen to the audio version of this article: [link] Why Conflict Matters Conflict is often seen as something bad that should not occur. Think of the salespeople, marketers, and customer support team members, as well as the UX designers, architects, programmers, and testers you might interact with. But in fact, it’s perfectly normal.

article thumbnail

UX Analytics: It’s Not Just About Data Collection and Methods

Userpilot

Unfortunately, the research backs this up, with a staggering 90% of users reporting that they stopped using an app due to poor performance. Poor performance includes slow loading times, complex design, confusing navigation, and unresponsive features. To assign meaning to whether the numbers are good or bad, context is crucial.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

529: Is this the best AI-powered market research approach? – with Carmel Dibner

Product Innovation Educators

How AI captures customer needs that human product managers miss Watch on YouTube TLDR In my recent conversation with Carmel Dibner from Applied Marketing Science, we explored how artificial intelligence is transforming Voice of the Customer (VOC) research for product teams. However, these early efforts faced significant limitations.

article thumbnail

The Risks of Data Fragmentation + How to Fix Fragmented Data

Userpilot

It compounds quietly across every team, workflow, and decision. When data collection is messy, product managers lose visibility, teams waste hours chasing answers, and user experience suffers. This is where tools like Userpilot come in, providing product teams with comprehensive analytics that bridge these dangerous data gaps.

article thumbnail

Product in Practice: Getting Started with Several APIs (And the Challenges I Faced)

Product Talk

But then, one day, I found myself reading Ask Your Developer by Jeff Lawson and I realized I was the one making the mistake. Dont Ask Humans to Do Tasks That Should Be Automated If you arent familiar with Ask Your Developer, its a great read. API teams need to think about onboarding just like everyone else. This got me curious.

article thumbnail

Customer Onboarding Automation: How-to Guide

Userpilot

While at it, you may even identify weaknesses in the current journey. How can I reduce the workload for my team? For instance, a project management app can check welcome survey responses and trigger Flow 1 for project managers and Flow 2 for team members. If you do, iron them out and create your ideal map before you proceed.

article thumbnail

Coherence, Outcomes, and Dictation

Tyner Blain

Just as you change collaboration patterns through changing how you develop roadmaps, you change the conversation with leaders through how you orient towards supporting them. First, the scope of work has already been defined and the team is being asked to deliver it. This is an order-giver / order-taker pattern. This is clearly insane.