SPEAKER_01: 0:00

You know, there is this really specific, almost tragic trajectory that successful companies tend to follow.

SPEAKER_00: 0:07

Oh, yeah. The startup phase versus the enterprise phase.

SPEAKER_01: 0:10

Aaron Powell Right. Picture a startup. It's uh it's three people in a garage or a WeWork. They're scrappy. They know every single customer by their first name. And if Mrs. Jones cancels her subscription, the CEO takes it personally. They actually call her up. They are just obsessed with the reality of the user experience.

SPEAKER_00: 0:28

Aaron Ross Powell Right. Because at that stage, I mean, reality is the only thing keeping them alive. You can't really hide behind a dashboard when you only have 10 customers.

SPEAKER_01: 0:36

Aaron Powell Exactly. But here is the paradox we found in the source material for today's deep dive. As these companies succeed, as they grow, get funding, hire hundreds of people, they actually get worse at understanding their users.

SPEAKER_00: 0:50

Yeah, it's totally counterintuitive.

SPEAKER_01: 0:51

It is. They get faster at shipping code, sure. They get more structure, but they lose the single most important asset they started with, which is that closeness to the user's reality.

SPEAKER_00: 1:00

Aaron Powell It's what the sources call the paradox of growth. And uh it's not because people stop caring. I think that's a really important distinction the texts make. Right. No product manager wakes up and thinks, you know, I'm going to ignore my users today. It's that the mechanism of scale itself creates distance. When you're small, you watch people. When you're big, you watch metrics.

SPEAKER_01: 1:22

And that is exactly what we are unpacking today. We've got a really fascinating stack of research on this concept of digital empathy.

SPEAKER_00: 1:30

Yes. And we should clarify what that means right away.

SPEAKER_01: 1:33

Definitely. Our main source is a comprehensive guide called How Growing Product Teams Build Digital Empathy at Scale. We're also looking at a specific checklist for decoding digital body language and a massive case study from Michelin.

SPEAKER_00: 1:48

Yes, the tire giant.

SPEAKER_01: 1:49

A tire company, yeah. On how they actually did this across a hundred different websites globally. Our mission today is to figure out how teams can build this empathy back into their DNA.

SPEAKER_00: 1:58

And before you tune out, because digital empathy sounds like you know a soft skill or some HR workshop, let's be very clear about how our sources define this.

SPEAKER_01: 2:07

Aaron Powell It's not warm and fuzzy.

SPEAKER_00: 2:08

No, not at all. It is a rigorous technical discipline. It's essentially about solving a data problem.

SPEAKER_01: 2:14

Aaron Powell The metric trap.

SPEAKER_00: 2:15

Precisely. The metric trap. As you scale, you rely on things like Google Analytics, right? GA4, Adobe Analytics. Right. You see that conversion drop by half a percent last Tuesday. You have the what, but you have absolutely zero insight into the why.

SPEAKER_01: 2:29

It's like the dashboard is basically gaslighting you. It tells you everything is fine or that something is wrong, but it treats every single user as a number.

SPEAKER_00: 2:38

A data point.

SPEAKER_01: 2:39

Yeah. It doesn't tell you that the drop happened because, say, a button was broken on mobile or because the phrasing on the checkout page was confusing.

SPEAKER_00: 2:46

Aaron Powell Exactly. The emotional signals, the frustration, the confusion, the anxiety, they're completely invisible in a standard spreadsheet.

SPEAKER_01: 2:53

So the whole point of this deep dive is to figure out how we get that visibility back right. How do we use technology to essentially read minds through mouse movements?

SPEAKER_00: 3:03

Aaron Powell I love that framing. Reading minds through mouse cursors.

SPEAKER_01: 3:07

Sounds totally like sci-fi.

SPEAKER_00: 3:09

It does. But as we'll see with the checklist later, it's actually very grounded in behavioral psychology. And we aren't just talking about theory here. We are going to look at how to operationalize this. Because if you don't, the sources argue, you end up with opinions replacing reality.

SPEAKER_01: 3:27

Oh man, this one hit home for me, the hippio effect.

SPEAKER_00: 3:30

Aaron Powell The highest paid person's opinion.

SPEAKER_01: 3:32

Right. The source material paints this perfect picture of a corporate meeting room. You've got sales, marketing, product, legal, and everyone is just arguing about what the user wants.

SPEAKER_00: 3:41

I think the button should be blue. Trevor Burrus, Jr.

SPEAKER_01: 3:43

Right. Or I think we need a massive pop-up here. But because there's no qualitative data in the room, the loudest voice wins.

SPEAKER_00: 3:49

Aaron Powell Or the most senior voice. And the problem is all those internal voices are fundamentally biased. They're suffering from what the text calls the curse of internal language.

SPEAKER_01: 3:59

Aaron Powell This is such a great concept. We have all been victims of this. The source uses the example of multi-factor authentication.

SPEAKER_00: 4:07

Oh, that's a perfect example.

SPEAKER_01: 4:08

To a product manager or an engineer saying, enable MFA is just as natural as breathing, it's precise, it's an industry standard.

SPEAKER_00: 4:17

It's technically correct.

SPEAKER_01: 4:18

But imagine a regular user. Let's say it's someone's grandmother trying to log in to check her tire warranty. She sees enable MFA and she just freezes.

SPEAKER_00: 4:29

Yeah, she has no idea what that acronym means.

SPEAKER_01: 4:31

To the internal team, it's totally clear. But to her, it's a brick wall.

SPEAKER_00: 4:35

Aaron Powell That is a total failure of cognitive empathy. The team has completely forgotten what it's like not to know. And the source makes a really critical point about the consequence of this.

SPEAKER_01: 4:46

Aaron Powell What happens when they hit the wall?

SPEAKER_00: 4:48

Right. When that user hits that confusing jargon or that broken link, they usually don't scream.

SPEAKER_01: 4:53

They definitely don't call customer support to complain about the UX.

SPEAKER_00: 4:57

Rarely. What they do is they engage in quiet disengagement, they just leave. They bounce. Yeah. And on your analytics dashboard, that bounce looks exactly like someone who just wasn't interested in buying tires today.

SPEAKER_01: 5:08

Wow.

SPEAKER_00: 5:08

But in reality, it was a failure of design. It was a struggle you never even saw.

SPEAKER_01: 5:12

So if the dashboard is hiding the struggle, we obviously need a new way to see. And this brings us to the digital empathy checklist provided in our source stack. This is the mind reading part.

SPEAKER_00: 5:23

The behavioral translation.

SPEAKER_01: 5:24

Exactly. The text argues that just like we have physical body language in the real world, we actually have digital body language online.

SPEAKER_00: 5:33

Right. In a face-to-face meeting, if I say something confusing, I can see you furrow your brow. I see you lean back or hesitate.

SPEAKER_01: 5:40

But online, we don't have faces.

SPEAKER_00: 5:42

We don't. But we have the mouse. The mouse is the proxy for the user's attention and their emotion.

SPEAKER_01: 5:48

So let's break down these specific signals. The source material pairs specific digital behaviors with actual emotions. I really want you, the listener, to picture your own websites right now while we go through this. Let's start with anxiety. How exactly does a mouse show anxiety?

SPEAKER_00: 6:04

Anxiety usually manifests as hesitation. The checklist highlights something called form field retyping. This is a classic tell.

SPEAKER_01: 6:11

How I do this.

SPEAKER_00: 6:12

Right. Imagine you're transferring a large amount of money or you're entering passcore details.

SPEAKER_01: 6:18

Yeah.

SPEAKER_00: 6:18

You type it, you delete it, you type it again, you pause.

SPEAKER_01: 6:22

Or I'll hover over the submit button, but I just won't click it yet.

SPEAKER_00: 6:25

That hover is data. If you see users consistently hovering near a call to action, but then moving away, or going up to check the FAQs and then coming back down, that is not just time on site.

SPEAKER_01: 6:36

Right.

SPEAKER_00: 6:36

That is doubt. That's a user looking for reassurance. Maybe they want a security badge or a clear explanation of what happens next, and they just aren't finding it.

SPEAKER_01: 6:45

It's basically a cry for help. Okay, so that's anxiety. What about frustration? This feels like it would be a bit louder.

SPEAKER_00: 6:51

Oh, it is. The industry term for this is just fantastic. They call them rage clicks.

SPEAKER_01: 6:55

Rage clicks? It sounds like a punk band.

SPEAKER_00: 6:58

It really captures the energy perfectly. A rage click is when a user rapidly, repeatedly clicks on a specific element.

SPEAKER_01: 7:04

Aaron Powell Just hammering the mouse.

SPEAKER_00: 7:06

Exactly. Usually it's because they expect something to happen, like a photo to zoom in or a link to open and nothing changes. The design has failed them, and they are physically venting that frustration on their trackpad.

SPEAKER_01: 7:18

It's the digital equivalent of banging on a vending machine when your chips get stuck.

SPEAKER_00: 7:22

That is exactly what it is. And closely related to that is the dead click. This is when a user clicks on something that looks like a button. Maybe it's a bold headline or a brightly colored box, but it isn't actually clickable.

SPEAKER_01: 7:36

The user is telling you, I want to go here.

SPEAKER_00: 7:39

And your design is saying no.

SPEAKER_01: 7:40

That is so painful to watch in a screen recording. Okay, how about confusion? How does that show up?

SPEAKER_00: 7:46

Confusion often shows up as looping. The source describes this as a chaotic navigation pattern. The user goes from the product page to the support page to the pricing page, and then right back to the product page.

SPEAKER_01: 7:58

They're just hunting.

SPEAKER_00: 7:59

They are scavenging. They have a specific question in their head, and the answer isn't where they expect it to be. Their mental model of your site just doesn't match the actual site architecture.

SPEAKER_01: 8:09

And finally, let's talk about disappointment. Because how do you distinguish disappointment from someone just being done and leaving naturally?

SPEAKER_00: 8:17

Aaron Powell You have to look at scroll depth versus attention. If you have a long article or a landing page where the key value proposition is down at the bottom, and users are scrolling rapidly to the bottom and then immediately exiting that is disappointment.

SPEAKER_01: 8:33

They didn't read it.

SPEAKER_00: 8:34

No. They scanned, they didn't find what they wanted, and they bailed. They didn't even give you a chance.

SPEAKER_01: 8:39

So the big mindset shift here, which is central to our primary article on building empathy, is to stop asking how many people visited and start asking how many people felt anxious.

SPEAKER_00: 8:49

Right. It's just the entire conversation from volume to the actual quality of the experience.

SPEAKER_01: 8:55

Now, I know what some listeners are probably thinking right now. You're thinking this is great if I have a small Shopify store and I can just watch every single session replay. But I'm at an enterprise level. Yes. And that is exactly why the Michelin case study included in our stack is so important.

SPEAKER_00: 9:10

It is the ultimate stress test for this entire philosophy.

SPEAKER_01: 9:13

Michelin isn't just selling tires in one place. They have a digital ecosystem of over 100 websites. They have B2B sites for dealers, B2C sites for everyday car owners, truck tires, aircraft tires. They operate in dozens of languages and time zones.

SPEAKER_00: 9:29

It's a massive, highly fragmented landscape. And their problem wasn't a lack of data. They had plenty of traffic stats. They knew they sold a lot of tires. Yeah. But they had zero visibility into that behavioral layer across the whole ecosystem. Right. If a dealer in Germany was struggling to place a bulk order, the central digital team in France might never know why it failed.

SPEAKER_01: 9:50

And they had a massive constraint to deal with privacy.

SPEAKER_00: 9:53

Huge constraint. As a European company, GDPR is completely non-negotiable. They couldn't just install spyware on people's computers. Right. They needed a solution that could capture these behavioral signals, the rage clicks and the hesitations, without capturing personally identifiable information.

SPEAKER_01: 10:08

So they needed to see the patterns, not the individual people.

SPEAKER_00: 10:11

Exactly. And the source highlights that they used a tool called MouseFlow, specifically because it allowed for that anonymized analysis. But the really smart part, and I think this is the big takeaway for any listener managing a large portfolio, was how they structure the data.

SPEAKER_01: 10:26

Right, because you definitely don't want to log into a hundred different dashboards every morning.

SPEAKER_00: 10:30

That would be a complete nightmare. Michelin rejected the silo model. They grouped their websites into about 20 distinct projects based on region and time zone.

SPEAKER_01: 10:40

Okay.

SPEAKER_00: 10:40

So for example, all North American B2C websites fed into one single data bucket.

SPEAKER_01: 10:46

That is so smart because then you can spot regional trends. If you see a massive checkout failure, you know instantly if it's just one localized site or if it's a systemic issue across the entire US and Canada region.

SPEAKER_00: 10:58

Exactly. But the real deep dive nugget here, the thing that made me actually say, wow, when I read it was the integration part.

SPEAKER_01: 11:04

Oh, the Power BI thing.

SPEAKER_00: 11:06

Yes. They didn't just keep this behavioral data locked up in the UX tool. They piped the API data directly into Power BI.

SPEAKER_01: 11:13

And Power BI is the massive business intelligence tool that executives use to look at revenue and logistics.

SPEAKER_00: 11:20

Yes. So they effectively put RageClicks right next to revenue on the executive dashboard. They created this a global dashboard using something called Sunburst Visualizations.

SPEAKER_01: 11:29

I looked up these sunburst charts while researching this. They are visually beautiful, but for the audio listener, can you explain what we are actually looking at?

SPEAKER_00: 11:36

Sure. Imagine a donut chart, but with multiple layers radiating out from the center. The center circle is the landing page. The next ring out is the next step the user took, and the next ring is the step after that.

SPEAKER_01: 11:48

Right.

SPEAKER_00: 11:49

It allows you to visualize the sheer chaos of user journeys.

SPEAKER_01: 11:52

Because traditional funnels are basically lies, right? We draw funnels as these perfectly straight lines, step one, step two, by but real humans are messy.

SPEAKER_00: 12:01

Real humans are incredibly messy. And a sunburst chart shows that mess. You can see the happy path, that's the slice where people go straight to purchase. But you can also visually see the unhappy paths.

SPEAKER_01: 12:11

The dead ends.

SPEAKER_00: 12:12

Right. The massive red slices or people branch off to the FAQ page or they loop back to the home page or they just drop off entirely.

SPEAKER_01: 12:20

And according to the case study, having this visualization created a shared language, the head of user intelligence at Michelin, Valentina Valcianu, makes a really great point in the text about this.

SPEAKER_00: 12:30

What did she say?

SPEAKER_01: 12:31

She says she works with stakeholders who aren't data scientists. If she shows them a giant spreadsheet of bounce rates, their eyes just glaze over entirely.

SPEAKER_00: 12:40

Of course. Oh but if she shows them the sunburst chart where a massive chunk of users hits a visual dead end, it's intuitive. Everyone intrinsically understands the concept of getting lost.

SPEAKER_01: 12:51

It totally democratizes the problem. And they actually use this to validate a massive website migration. They compared the sunburst of the old site to the sunburst of the new site and could visually prove to leadership that the new design had fewer dead ends.

SPEAKER_00: 13:05

That is the absolute holy grail of UX, proving ROI not just with a gut feeling, but with hard visual evidence.

SPEAKER_01: 13:12

So Michelin proves this can be done at an enterprise scale. But let's pivot back to the how-to for a minute. Most of you listening aren't managing a hundred global sites. You are managing a single product, a new feature, or a startup.

SPEAKER_00: 13:24

Right.

SPEAKER_01: 13:25

The primary article in our source stack, How Growing Product Teams Build Digital Empathy, gives us the actual tactical playbook for this.

SPEAKER_00: 13:32

And the headline here is rituals over one-offs.

SPEAKER_01: 13:36

What does that actually look like in practice?

SPEAKER_00: 13:38

It means empathy cannot be a project you do once a year.

SPEAKER_01: 13:42

Yeah.

SPEAKER_00: 13:43

You can't say, well, it's November, time for our annual usability audit. That just doesn't work. It has to be baped into the weekly hygiene of the team.

SPEAKER_01: 13:51

The source suggests a really specific ritual called the UX lunch.

SPEAKER_00: 13:55

I love this idea. It is so simple, but honestly so rare. You get your designers, your product managers, and crucially your engineers in a room for 30 minutes.

SPEAKER_01: 14:04

Together.

SPEAKER_00: 14:04

Yes. You bring lunch or you bring popcorn. Yeah. And you literally just watch session replays together.

SPEAKER_01: 14:10

You just sit there and watch people use the product.

SPEAKER_00: 14:12

Yes. It sounds passive, but it is actually an incredibly active emotional experience. There is almost nothing more painful for an engineer than watching a real user struggle to click the exact button they just spent a week building.

SPEAKER_01: 14:28

It totally breaks the ego.

SPEAKER_00: 14:30

Completely shatters it. When you see a user rage clicking on your feature, you can't argue with it. You can't sit there and say, well, the user's just holding the mouse wrong.

SPEAKER_01: 14:38

Right.

SPEAKER_00: 14:38

You just feel the pain. The source says real user evidence creates urgency in a way numbers cannot.

SPEAKER_01: 14:45

But I can already hear the objection from some listeners. We're too busy. We don't have time to sit around watching movies of users.

SPEAKER_00: 14:52

And that's a valid constraint. That is why the article suggests building a highlight clip culture. If a UX researcher or a designer sees a struggle during their analysis, they shouldn't just go write a JIRA ticket that says fix the navigation.

SPEAKER_01: 15:04

Because nobody reads the description in the Jira ticket anyway, let's be honest.

SPEAKER_00: 15:08

Exactly. Instead, you clip the 15 seconds of video where the user is looping and confused, you post that short clip directly in Slack, or you play that clip at the very start of your daily stand-up meeting.

SPEAKER_01: 15:19

That changes the conversation immediately. It's undeniable proof.

SPEAKER_00: 15:22

It stops the debate dead in its tracks. The text gives this classic example of the pop-up war.

SPEAKER_01: 15:29

Oh, the pop-up war.

SPEAKER_00: 15:31

We have all seen this. Marketing wants a giant pop-up to collect emails. UX hates the pop-up because it ruins the user flow. Usually they just argue about it for three weeks.

SPEAKER_01: 15:40

And usually marketing wins because they just shout leads at the end of the meeting.

SPEAKER_00: 15:44

Right. The solution proposed here is don't argue, turn the pop-up on and watch the tape. Do you see users closing it effortlessly and continuing on their journey? Or do you see rage clicks and immediate bounces? Let the user decide the debate.

SPEAKER_01: 15:59

It's so much more efficient. But there is one final step in this workflow that we have to mention, right? Closing the loop.

SPEAKER_00: 16:04

This is critical. Observation without action is just voyeurism. You have to validate and repeat. If you see anxiety on a checkout form, like that retyping behavior we talked about earlier, and you decide to change the field labels to make it clearer, you aren't done.

SPEAKER_01: 16:20

You have to go back to the videotape.

SPEAKER_00: 16:21

You have to watch fresh sessions after the fix goes live. Did the retyping actually stop? Did the hesitation disappear? If yes, congratulations, you have successfully applied digital empathy. If no, you guessed wrong. Try again.

SPEAKER_01: 16:35

It seems like such a simple feedback loop. Watch, fix, verify. But so few teams actually do the verify part qualitatively. They just check if overall conversions went up.

SPEAKER_00: 16:44

And that brings us right back to the start of the deep dive. If conversions went up, great. But maybe they went up while user frustration also went up. Maybe you just forced users through a dark pattern. Only by watching can you ensure the experience is actually healthy.

SPEAKER_01: 16:58

So let's zoom out and recap what we have covered today. We started with the paradox of growth. The idea that success inevitably creates distance. As we build more dashboards and get bigger, we lose touch with the actual human on the other side of the screen.

SPEAKER_00: 17:12

And the solution isn't to burn the dashboards down, it's to layer digital empathy on top of them. To basically give the numbers a pulse.

SPEAKER_01: 17:21

We have the signals now. We know what anxiety, frustration, and confusion look like, the hesitation, the rage click, the loop. We know from the Michelin case study that we can visualize this at a massive scale using tools like sunburst charts to align the whole company, even if you have a hundred websites.

SPEAKER_00: 17:38

And we know that to make it actually stick, we have to build rituals. The UX launch, sharing the video clips and Slack. It's about forcing the entire team to confront the reality of the user experience every single week.

SPEAKER_01: 17:51

It really comes down to humility, doesn't it? That seems to be the underlying theme of all these sources.

SPEAKER_00: 17:54

It is. I think that is the most profound takeaway here. The source material stresses this constantly. We, the people building the software, are the most biased people in the room. We know how it should work. We know all the internal jargon. We know the happy path. We are completely cursed with knowledge.

SPEAKER_01: 18:13

And the user is just out there trying to get something done in their busy, messy life. They do not care about our product roadmap or our Q3 goals. They just want the thing to work.

SPEAKER_00: 18:22

Yeah, exactly. Empathy is simply the discipline of admitting that we might be wrong and having the humility to watch the user to find out the actual truth.

SPEAKER_01: 18:33

So I want to leave you with a challenge, a provocative question for you to mull over as you head back to your own dashboards and spreadsheets today.

SPEAKER_00: 18:39

Lay it on us.

SPEAKER_01: 18:40

If you sat down right now and watched 10 random recordings of users on your most important product page, what would you see? Would you see the confident, linear journey you designed in your Figma file? Or would you see a quiet struggle that you didn't even know existed?

SPEAKER_00: 18:54

And if you do see the struggle, do you have the courage to pause the roadmap and actually fix it?

SPEAKER_01: 19:00

That is the question. Thanks for taking this deep dive into digital empathy with us. Go watch some user sessions, and we will catch you on the next one.