The Influence Saga

Seeing the Forest Despite the Trees

Dave was a top performer until they rotated him onto a struggling team. His numbers fell off a cliff, and the metrics never told anyone why.

Layout

Dave

Dave had always been a top performer. Then they rotated him onto a struggling team and his numbers fell off a cliff.

Average Handle Time was through the roof. Resolve rates were down. Satisfaction scores were low. On paper, he looked like a manager who had lost control of his team.

Dave came to me because we’d built a good relationship. He couldn’t figure out what was wrong. The data was telling him he was failing, but he didn’t feel like that was the full story. He was right.

Why I was there

I was a contractor embedded in an AT&T call center. Samsung hired me to support their warranty program, which meant I sat in a building full of people I didn’t manage, couldn’t fire, and had no authority over. My job was to improve performance through pure influence.

The only tool I had was trust. I built it one conversation at a time, by helping people without making them feel like they needed help. I answered questions. I showed up. I didn’t act like I was above anyone.

I use “influence without authority” a lot, but that operation was where I actually learned it.

The surface numbers

Teams and schedules in that call center got rotated every so often. Dave landed on a team that was struggling hard.

Facts and feelings

Most people see a bad number and go straight to fixing the number. I have a different approach. I classify metrics into two categories: facts and feelings.

  • Average Handle Time is a fact. It’s not meaningful by itself, but it’s true. The call took X minutes. That’s not up for debate.
  • Resolve is a feeling. It’s how the customer felt at the end of the call. That matters, but it’s subjective.
  • 72-hour repeat rate is a fact. It bypasses the customer’s initial feelings. If they didn’t call back, the fix worked.
  • Satisfaction is another feeling. Important, but not the whole picture.

When I applied this lens to Dave’s numbers, one thing jumped out. He was trailing the top-performing team in every metric except one: 72-hour repeats. His team’s repeat rate was roughly the same as the best team’s.

Think about that. His calls took way longer. Customers didn’t feel resolved. Satisfaction was down. But they weren’t calling back. The fixes were working. It just took more time and left everyone feeling worse about the experience.

That told me the issue wasn’t capability. It was something else.

The deep dive

I pulled tens of thousands of records and started slicing them every way I could. What call types were driving the high handle times? Where was the team getting stuck?

One category kept rising to the top: Power, Charging, and Black Screen issues. Those calls were eating the team alive.

Power and charging issues on Android are complex. There are a dozen things it could be: the battery, the port, the software, the charger, the customer’s usage pattern. Black screen issues are even worse because you can’t see anything to diagnose it. These are the kinds of problems that make even good agents second-guess themselves.

And the standard fix for most of them was a factory reset. Which means you have to back up the customer’s data first. Every single time.

So I found the “what.” Now I needed the “why.”

Going to see the work

The data told me where to look. But it didn’t tell me why.

So I went to the floor and watched the team work. That’s when things started clicking.

Dave’s team was split roughly in half. One side was very tenured, older folks who knew the job but weren’t naturally comfortable with deep technical troubleshooting. The other side was new hires, eager but timid, afraid to make a mistake.

Neither group wanted to be the one who lost a customer’s data. So they both did the same thing: they slowed down. They stayed on calls longer. They over-researched. They transferred that anxiety to the customer, which cratered resolve and satisfaction.

To someone outside of mobile support, that might not sound like a big deal. That’s where you have to build the skill to step back and detach. What does that phone represent to the customer? Everything. Their entire lives are on there. Photos, contacts, sometimes voicemails from family members who have passed on. I’ve dealt with that one a few times.

The problem wasn’t that they didn’t know what to do. It was that they didn’t trust themselves to do it.

But I still didn’t have the full picture. I knew the problem area. I knew the emotional dynamic. But I didn’t know what to train on yet.

The missing piece

I went back to the data. There had to be another thread.

That’s when I found it. Backup and Restore. It was the other call type with high handle times, but I hadn’t flagged it in the first pass because it wasn’t as loud as the power and charging numbers.

But now, with fresh eyes from watching the team, backup and restore was the key. It wasn’t a separate problem. It was the consequence of the first one. Power and charging issues require a factory reset. A factory reset requires a backup. A backup requires telling a customer you might have to wipe their phone clean.

That’s where the fear hit the table. Nobody wants to make that call. So agents stall. They over-explain. They put the customer on hold to double-check things they already know. Handle time balloons.

Backup and restore was the tangible gap. The thing you could actually train on. You can’t train “be more confident,” but you can train someone on exactly how to back up a customer’s data until the process is automatic.

A week of reps

I spent a week working with the team during their normal team meetings. No big production, no offsites, no mandatory training certificates. Just focused, targeted sessions on backup and restore procedures. Short and specific.

The goal wasn’t to teach them new information. Most of them already knew it. The goal was to give them enough reps that they stopped second-guessing. When you’ve walked through the backup process ten times in a low-stakes setting, you don’t freeze when a customer asks “are you sure my photos will be safe?”

Three to four weeks later, Dave was back at the top of the board.

The disease

The numbers on the dashboard told a story. But it was the wrong story. AHT was high, so the instinct is to coach on speed. Resolve was low, so the instinct is to coach on troubleshooting. Satisfaction was down, so the instinct is to coach on soft skills.

All of those responses treat the symptom. None of them fix the disease.

The disease was fear. The team was afraid of the consequences of a mistake, so they moved slowly and projected uncertainty. The fix wasn’t more pressure or more coaching. It was giving them enough confidence that fear stopped driving their behavior.

The trees are the individual metrics screaming for your attention. The forest is the pattern underneath: what the metrics mean together, what they tell you when you stop looking at them in isolation.

The data will tell you where to look. But you have to go see the work to understand what you’re looking at.