Being liked and being chosen are two very different things. And after sitting in on a Channel Focus panel this week called Winning the Partner Experience Battle, I don't think most partner programs know the difference.

Partner experience is what I own in my current role. It is the thing I sit down thinking about every morning. So when the panel opened with the reframe that stopped me mid-note, it hit exactly where I live.

Most vendors think they are winning if partners speak well of them in a satisfaction survey. But partners are not paid to like you. They are paid to make their own numbers, in front of their own customers, on their own margins. The way they show you what they actually think of your program is where they put their time, their people, and their pipeline.

Satisfaction is what they say. Preference is what they do.

That distinction is the whole game.

The Question I've Been Asking Myself Since

If a partner has three vendors in the same category and they can only put real weight behind one this quarter, which do they choose? And more importantly, why?

If the honest answer is "us, because we are easier to work with than the others," you are winning. If the honest answer is "us, because our product is technically better," you are winning for now. If the answer involves any hesitation, that is your program telling you where the work is.

So here is a question worth sitting with. When was the last time you asked a partner why they chose to prioritize you this quarter over another vendor in your category? Not through a survey. In a conversation. The answer is often not what the satisfaction score suggests.

Design From the Outside In

One of the sharpest observations across the panel was that most partner programs are still designed inside out. What is good for our compliance team. What is good for our legal team. What is good for our finance controls. What the process looked like the last time we ran it.

Every one of those things is a legitimate concern. And every one of them, unchecked, becomes a small drag on the partner experience.

The question I now think every partner program builder should be asking on repeat is a simple one. Why do we need this? Not "should we change it," which is a question that invites defensive answers. Just why. Why seven layers of approval in this region. Why five days between claim submission and the first response. Why this piece of documentation that we ask for every time and never actually reference.

Sometimes the answer is a real reason. Often the answer is that no one has questioned it in years.

Pick one process in your partner program right now. Ask three people why it works the way it does. If the answers come back different from each other, or if any of them start with "I think it's because," that process is a candidate for redesign.

Where the Friction Actually Lives

One of the more practical points from the panel was that friction is often not about whether you have a step. It is about where that step happens in the process.

Validation at the moment of submission means the partner gets immediate feedback and can fix a mistake while they are still in the workflow. Validation days later means the partner has to context switch, dig up what they submitted, remember what they were trying to do, and get back into a stalled thread. Same step. Completely different experience.

That principle applies to nearly every partner-facing workflow. Where does the delay live? Where does the handoff happen? Where does the partner have to wait?

If you traced the partner journey through your program end to end, could you point to every moment the partner has to stop and wait for you? Have you counted them? Have you timed them? Most programs cannot answer that question in specifics. That itself is the diagnostic.

AI Is for Your Friction, Not for Your Ego

The AI conversation on the panel was refreshingly grounded. Every panelist made some version of the same point. Applying AI to apply AI is a distraction. Applying AI to the specific places your program creates friction is where the leverage lives.

Claim processing. Invoice image reading. First-line support with a clean handoff to a human when the question turns nuanced. Form wizards that walk a partner through what used to be a fifty-field submission. Personalized program communications inside your brand guardrails.

None of these are transformational on paper. All of them are transformational to the partner who no longer has to spend a Friday afternoon on your paperwork.

What are the three highest-friction moments in your partner journey today? And would AI actually shorten those, or would it just make them look more sophisticated?

Segmentation Beats AI

This one was my favorite point of the day because it names something I have been trying to articulate in my own work.

Most partner programs are not underpersonalized because they don't have AI. They are underpersonalized because they never segmented properly. A tier based on how much a partner sold is not segmentation. It is scoring. Real segmentation knows what the partner sold, who they sold it to, what they are certified in, what their business model actually is, and whether their trajectory is up or down.

Do that work first. Then think about AI.

If you had to describe your best partner and your worst partner using only what your program actually tracks about them today, would the two descriptions look different in a way that matters? If not, that is your segmentation gap.

The Human Touch Is Not Optional

The counterintuitive point that came up across multiple panelists was that as technology takes over more of the routine interactions, the human moments become disproportionately valuable.

Automation handles the small things well. But when something goes wrong, when a payment is late, when a claim is disputed, when a partner is stuck, that is when a real human on your team either wins loyalty or loses it. Automation cannot buy loyalty in a bad moment. A named person who cares about the outcome can.

When something goes wrong in your program, who owns the recovery? Do they have the authority to actually fix it, or are they just the first line of contact who then has to route it somewhere else?

Speed Is Now Table Stakes

One of the panelists made a point I keep coming back to. Partners are not waiting on you in a vacuum. They are waiting on you in front of their end customer. When you take a week to answer a question they need to answer in a meeting, you have not just delayed them. You have made them look bad.

Two shifts in how we should be measuring speed.

First, stop measuring from ticket opened to ticket answered. Measure from the moment the partner needed to know something to the moment they could actually act on it. Those are two very different numbers, and the second one is the one that shapes how the partner feels about your program.

Second, stop hiding behind averages. A program that resolves fifty issues in three days and one issue in eleven weeks does not have a three-day average experience. It has an eleven-week reputation. The worst week is the reputation. Everything else is noise.

What is your worst response time this quarter? Not your average. Your worst. That is how a partner remembers you.

What I'm Taking Back

Two things I am putting into my own week.

The first is the chosen versus liked test. I am going to start asking partners a version of that question directly, not in a survey. Which vendor in our category are you prioritizing this quarter, and why?

The second is a friction audit. I am going to pick one workflow in our program and walk it end to end from the partner side. Not the internal side. Not the version in our runbook. The version a partner actually experiences. And I am going to time it, count the handoffs, and note every place they have to wait on us.

Because the panel was right. This is not the technology battle. Every vendor has technology within a whisker of the next one. This is the ease-of-doing-business battle. And the vendors who take that seriously are the ones being chosen.

So what are you doing this quarter to make sure it is you?

Have thoughts on this? Connect with me on LinkedIn.