Co-Creating Experience With Ecosystem Partners in B2B2C

A bank's most important customer conversation this year will probably not happen in a bank branch. It will happen at a car dealership finalising a loan, in a real estate agent's office structuring a mortgage, or inside a telecom partner's shop bundling a device plan. The brand on the signage is rarely the brand that owns the moment. That single fact is the whole problem with partner experience design, and almost nobody designs for it properly.

Most enterprises still try to solve this with documentation: a partner playbook, a brand-standards PDF, a service-level agreement with penalty clauses. None of it works for long, because none of it makes the partner want the outcome. My thesis, after years of watching principal companies try to control experience they don't operationally own, is simple: you cannot brief your way into a good partner experience; you can only co-create your way into one. Ecosystem partners who help design the journey, the script, and the recovery protocol defend it as their own. Partners who are handed a finished journey treat it as someone else's homework — and mark it accordingly.

What does "co-creating experience with ecosystem partners" actually mean?

Co-creating ecosystem experience means designing the customer journey with the intermediaries who deliver it — distributors, agents, resellers, franchisees, marketplace sellers, brokers — rather than designing it centrally and pushing it downstream for compliance. It treats the partner not as a distribution pipe but as a co-author of the moments that carry your brand promise.

This matters because in a B2B2C model, the principal company owns the brand promise but rarely owns the delivery. The partner owns the till, the counter, the call script, the technician's van. Every service blueprint that stops at "handover to partner" is a blueprint with a hole in the middle — precisely where the customer's experience of your brand is actually formed. Closing that hole requires bringing the partner into the room while the journey is still a draft, not after it has been finalised and laminated.

Why do most partner experience programmes fail before they start?

They fail because they mistake compliance for commitment. A journey map handed down from head office is a compliance document, not a commitment device — and compliance documents get followed exactly as far as someone is watching.

Three specific failure patterns recur across sectors:

• Design-then-deploy sequencing. The principal designs the full journey internally, then trains partners on the finished version. Partners have zero authorship, so they have zero investment in defending it under pressure.
• Sludge disguised as governance. Approval workflows, reporting templates, and mandatory scripts pile up as "controls" but function as friction that makes the compliant path slower than the shortcut. The behavioral economist Richard Thaler named this pattern "sludge" in a 2018 Science piece — the excessive friction organisations build into a process, often in the name of oversight, that quietly pushes people toward the easier, non-compliant route.
• Misaligned loss exposure. The principal absorbs brand risk when a partner underperforms, but the partner absorbs the cost of any change to their process. Loss aversion, described by Daniel Kahneman and Amos Tversky in their 1979 paper "Prospect Theory: An Analysis of Decision under Risk" (Econometrica), predicts exactly what happens next: partners resist change roughly twice as strongly as they'd embrace an equivalent gain, so a mandated journey redesign reads as a threat to be managed, not an opportunity to be seized.

Fix the sequencing and the incentive asymmetry, and most of the "partner won't comply" problem dissolves on its own.

What does behavioral economics say about co-creation?

It says ownership changes valuation — and valuation changes behaviour. The clearest evidence comes from Daniel Mochon, Michael Norton, and Dan Ariely's research on what they called the IKEA effect: people place disproportionately high value on things they built themselves, even when the finished product is objectively unremarkable. In their study "The IKEA Effect: When Labor Leads to Love," published in the Journal of Consumer Psychology in 2012, participants who assembled their own IKEA boxes, built origami, or constructed Lego sets valued their own creations far more highly than identical items they hadn't built — and were willing to pay premium prices for their own, ordinary-looking output.

Apply that mechanism to a distribution partner. A branch manager who helped script the complaint-recovery flow doesn't experience the script as an instruction; they experience it as their own work. That's the entire behavioral case for co-creation over dictation: labour — even a single structured workshop's worth — creates attachment that a finished manual never will.

There's a second, quieter mechanism at play: the endowment effect, the tendency to overvalue something once you feel you own it. Partners who contribute to a journey don't just execute it better; they defend it harder when a customer, a competitor, or a cost-cutting initiative threatens to strip it out. Co-creation, in this light, isn't a workshop technique. It's a retention strategy for the experience itself.

How does co-creation change a partner's motivation to deliver well?

It shifts the partner from rule-follower to outcome-owner — and outcome-owners self-correct without being told. A partner who was consulted on why a particular step exists (say, a mandatory ID verification before a policy payout) understands the customer risk it prevents. A partner who was simply told to do it treats it as a box to tick, and boxes get skipped the moment volume spikes.

Co-creation also lets you use the goal-gradient effect deliberately — the well-documented tendency for effort and motivation to increase as people perceive themselves nearing a goal. Ecosystems that build partner capability in visible, structured stages (bronze, silver, gold tiers of enablement, for instance, each unlocking more autonomy or better economics) give partners a finish line to accelerate toward, rather than an undifferentiated compliance list with no sense of progress.

None of this requires giving up control of the brand promise. It requires giving up control of exactly how that promise gets executed at the local level, in exchange for partners who protect it because they helped write it.

What does a real co-creation process look like in practice?

It looks less like a rollout and more like a joint design sprint, run before anything is finalised. A workable sequence, tested across intermediated categories from banking to automotive retail, runs like this:

1. Map the current journey together, gaps included. Bring principal and partner staff into the same room to build the end-to-end customer journey as it actually happens today — not the idealised version in the brand manual. Partners will surface friction the principal never sees, because they're the ones absorbing customer frustration at the counter.
2. Identify the moments of truth jointly. Not every touchpoint matters equally. Use the emotional highs and lows of the journey to isolate the two or three moments — a claim rejection, a delivery delay, a mis-sold add-on — that will define whether the customer stays. Peak-end research from Daniel Kahneman's work with Donald Redelmeier, published as "Patients' Memories of Painful Medical Treatments" in the journal Pain in 1996, showed that people judge an entire experience by its peak intensity and its ending, largely ignoring duration. That means the partner's handling of the single worst moment and the final handshake matters more than a dozen smoothly efficient minutes either side of it.
3. Co-design the script and the exception path, not just the happy path. Most partner training over-invests in the standard transaction and under-invests in what happens when something goes wrong. Build the recovery protocol with the partner in the room, since they will be the ones improvising it live.
4. Pilot with the partners who helped design it. Test the new journey first with the co-design group, not a randomly assigned rollout cohort. Their authorship gives you a fairer read of whether the design works, before wider distribution.
5. Feed the field data back transparently. Share performance data — good and bad — with the partners who contributed, not just with internal stakeholders. Partners who see their input reflected in the metrics stay engaged; partners who never hear what happened to their suggestions disengage by the second cycle.
6. Formalise the loop into governance, not a one-off event. A single workshop earns goodwill for a quarter. Standing CX governance that revisits the journey with partner input on a fixed cadence earns compounding trust.

Where does co-creation break down in B2B2C ecosystems?

It breaks down at the seams between channels and at the seams between incentive structures — the two places most partner programmes never look. A few recurring fault lines:

• Channel conflict. A direct digital channel and a partner-run physical channel quietly compete for the same customer, and the partner knows it. Co-creation only works if the economics are genuinely aligned; no amount of workshop goodwill survives a partner discovering the principal is undercutting them online.
• Inconsistent authority to resolve. If the partner's frontline staff co-designed a recovery script but have no authority to actually execute it — no discretion on a refund, no override on a policy exception — the co-created journey collapses into theatre. Escalation design has to move in lockstep with journey co-creation, or the partner's hands stay tied exactly where the customer needs them free.
• Data that never returns to the partner. Principals often collect voice-of-customer data through the partner channel and never send insight back the other way. That asymmetry — the partner supplies the customer contact, the principal keeps the intelligence — erodes the sense of shared ownership co-creation is meant to build.
• Uneven maturity across the network. A flagship partner and a small regional franchisee are not starting from the same capability base. Co-created journeys designed with the most sophisticated partner in the network often exceed what a smaller partner can operationally sustain, which is why a structured maturity assessment of the partner base should precede, not follow, the design work.

Each of these is fixable. None of them is fixable by better documentation.

How should you measure whether ecosystem co-creation is working?

Measure it the way you'd measure any investment with a return: track whether the partner-delivered experience is converging with, or diverging from, the direct channel over time — and whether the cost of achieving that convergence is falling as trust compounds. Three practical signals matter more than a generic partner satisfaction score:

• Journey consistency across channels. Compare customer effort and satisfaction scores for the same transaction type delivered directly versus through a partner. A persistent gap is a design gap, not a training gap.
• Voice-of-customer volume attributable to partner touchpoints. Rising complaint or praise volume tied to specific partner moments tells you where the co-designed script is or isn't holding under real pressure. A structured voice-of-customer strategy that tags feedback by channel and partner is the only reliable way to see this.
• Partner-initiated improvement suggestions. Counterintuitively, this is the strongest leading indicator of co-creation actually working. Partners who feel ownership propose fixes unprompted. Partners running on compliance alone report problems only when forced to.

If you want to put a number on the business case before you invest in the design work, the CX ROI Calculator is a useful starting point for quantifying what partner-channel friction is actually costing against the investment required to close it.

What's the honest limit of co-creation?

Co-creation is not consensus. The principal still has to hold the line on the handful of non-negotiables — pricing integrity, regulatory disclosure, brand safety — that no partner gets a vote on, however collaborative the process. The skill is in separating what's genuinely negotiable (how a moment is delivered) from what isn't (whether it happens at all), and being transparent about that distinction from the first workshop. Partners who sense a fake consultation, where every "co-created" decision was predetermined, disengage faster than partners who were never consulted at all. That's loss aversion again, this time applied to trust rather than money: a broken promise of influence stings more than influence never offered.

The ecosystem is the brand now

Principal companies spend enormous energy protecting brand consistency in the channels they control and comparatively little protecting it in the channels they don't — even though, in most intermediated categories, the partner channel is where the majority of customers actually meet the brand. That imbalance is the real opportunity. The organisations pulling ahead in B2B2C experience aren't the ones with the thickest partner manual. They're the ones that stopped treating partners as an audience for their CX strategy and started treating them as co-authors of it. Do that well, and the manual becomes almost unnecessary — because the people delivering the experience already believe in it.

Renascence works with principals and their partner networks to design that kind of shared ownership into the journey itself — our customer experience consulting practice builds the co-creation process alongside the governance that keeps it alive past the first quarter. If your partner network is the part of the journey you can least see and least control, that's exactly where the next design sprint should start.