8 Service Design Mistakes That Create Efficient Misery

by Braden Kelley and Chateau G Pato

What Is Efficient Misery — and Which Service Design Mistakes Create It? (Short Answer)

Efficient misery is a service that meets internal efficiency and SLA-like targets while customers — and often employees — experience higher effort, lower dignity, and no path to succeed without heroics. Eight service design mistakes that create it: (1) happy-path-only design, (2) channel efficiency over job success, (3) orphan seams, (4) self-service as unpaid labor, (5) designing to the SLA, (6) recovery left to heroes, (7) policy and fine print as the real design, and (8) frontline without recovery power.

Efficient misery is not a culture problem. It is service design that succeeded at the wrong job — making the organization look fast while humans absorb the cost.

Why Do Efficient Services Still Make Humans Miserable?

I have sat in service reviews where every KPI was on target and every human in the story was exhausted. Cost-per-contact was down. Digital deflection was up. The dashboard was green. The job still failed — unfinished, retold, or rescued by someone who was not supposed to need a hero.

That is efficient misery: local throughput and SLA optics winning while the human job gets harder. Soft landings for service require designing for human success — not mistaking channel speed for a finished experience.

Mistake	Feels efficient	Misery
1. Happy-path-only	Fewer flows; cleaner demos	Stressed paths become unpaid workarounds
2. Channel over job	Cost-per-contact drops	Unfinished jobs; more contacts later
3. Orphan seams	Local SLAs look healthy	Retelling tax; unowned waits
4. Self-service as unpaid labor	Headcount and handle time look better	Homework and failed DIY
5. Design to the SLA	Clear, vendor-friendly scoreboard	Fast wrong closes; green/miserable
6. Recovery as heroes	Don’t fund recovery until crisis	Dignity costs; apology theater
7. Policy as real design	Speed to launch	Surprise denials; broken promises
8. Powerless frontline	Scripts and controllable cost	Known fixes that cannot ship

1. How Does Happy-Path-Only Design Create Efficient Misery?

The mistake: Design and fund the average case; treat exceptions, life context, and “edge” humans as noise.

Why it feels efficient: Fewer flows, cleaner demos, cheaper builds.

The misery: The people who need the service most become unpaid workaround engineers — or churn silently.

Redesign: Design for the struggling moment and the recovery path as first-class journeys. Measure success for the median and the stressed path.

2. Why Is Channel Efficiency Over Job Success a Service Design Mistake?

The mistake: Steer humans to the cheapest channel — bot, portal, IVR — without making that channel able to finish the job.

Why it feels efficient: Cost-per-contact drops. “Digital adoption” rises.

The misery: More contacts, wrong doors, unfinished jobs, and anger mislabeled as “resistance.”

Redesign: Optimize for job completion and time-to-confidence across channels — not deflection rate. Cheap unfinished is still expensive.

3. How Do Orphan Seams Produce Green Steps and a Red Journey?

The mistake: Each team owns a step; nobody owns the handoff, the wait, or the story that must be retold.

Why it feels efficient: Local SLAs and team KPIs look healthy.

The misery: Story-retelling tax, unowned waiting, “not my department” at the moment of truth.

Redesign: Name a journey or seam owner with authority to fix the cliff — before you celebrate step metrics. For the frictions maps miss at those cliffs, see 12 Friction Points Customers Feel Before Your Journey Map Does.

4. How Does Self-Service Become Unpaid Labor?

The mistake: Move work to the customer — or employee — without reducing complexity, providing context, or owning failure modes.

Why it feels efficient: Headcount and handle time look better.

The misery: Homework before entry, identity theater, DIY that fails into a worse contact.

Redesign: Inventory unpaid labor. Kill it or redesign it as a supported step with less burden and a human escape hatch that works.

5. What Happens When You Design the Service to the SLA?

The mistake: Shape flows, scripts, and closures around uptime, response, resolution, or handle-time targets instead of human success.

Why it feels efficient: The scoreboard is clear and vendor-friendly.

The misery: Fast wrong closes, defensive ticket hygiene, green dashboards with miserable humans.

Redesign: Demote SLAs to enabling conditions. Design and govern with experience-level measures of human success. For the maturity path, see 5 Stages from SLAs to XLAs.

6. Why Is Recovery Left to Heroes Still a Design Mistake?

The mistake: Assume things will work; when they don’t, recovery is improvised by “great people.”

Why it feels efficient: You don’t fund recovery capability until something breaks publicly.

The misery: Dignity costs, status opacity, powerless moments, brand trust spent on apology theater.

Redesign: Design recovery as a product — powers, playbooks, and metrics for make-right — not a personality trait.

7. How Do Policy and Fine Print Become the Real Service Design?

The mistake: Experience teams draw the happy path; legal, risk, and ops freeze the real rules after “done” — or hide them in terms nobody can act on.

Why it feels efficient: Speed to launch. Compliance parked elsewhere.

The misery: Surprise denials, bait-and-switch constraints, agents who cannot keep the brand promise.

Redesign: Bring constraint honesty into the design. Name what must not be faked. Write policy as experience — not only as a liability shield.

8. How Does a Frontline Without Recovery Power Create Efficient Misery?

The mistake: Script and meter the people closest to the customer while denying decision rights, tools, or permission to make things right.

Why it feels efficient: Consistency, compliance, and controllable cost.

The misery: Humans who know the fix and cannot do it. Customers who escalate to survive. Employees who quit the dignity of the job.

Redesign: Design empowerment with the service — recovery bands, escalation that works, metrics that don’t punish care. For the rulebook, see 10 Agent Empowerment Rules Your Customer Deserves Before They Quit. If your CX program is managing the number instead of the journey, use 11 Signs Your CX Program Is Scorekeeping, Not Sense-Making.

How Do You Audit Efficient Misery Before the Next Service Redesign?

Before the next service redesign, run five go/no-go questions:

Whose efficiency are we optimizing — and whose effort absorbs the savings?
Which seam has no owner?
What unpaid labor did we just invent?
Which metric could make the dashboard green while the job fails?
Who can make it right at the moment of truth — with what power?

Stop designing services that look fast. Start designing services humans can finish with dignity.

Frequently Asked Questions

What is efficient misery?

Efficient misery is a service that meets internal efficiency and SLA-like targets while customers — and often employees — experience higher effort, lower dignity, and no path to succeed without heroics. The organization looks fast; humans absorb the cost.

What are common service design mistakes?

Common service design mistakes include happy-path-only design, optimizing channels instead of job completion, orphan seams with no handoff owner, self-service that shifts unpaid labor, designing to SLAs instead of human success, leaving recovery to heroes, freezing policy after “done,” and denying frontline recovery power.

Why are SLAs green but customers unhappy?

SLAs can be green while customers are unhappy because SLAs measure whether the service ran — uptime, response, resolution — not whether humans finished the job with dignity. Designing to the SLA produces fast wrong closes and defensive ticket hygiene while the journey stays red.

How does self-service create bad CX?

Self-service creates bad CX when it shifts complexity to the customer without reducing burden, providing context, or owning failure modes. Headcount looks better while humans do homework, fail DIY, and escalate into a worse contact. Real empowerment finishes the job; deflection theater does not.

How do you redesign a service for human success?

Redesign for human success by designing stressed paths and recovery as first-class journeys, optimizing for job completion over deflection, naming seam owners, killing unpaid labor, demoting SLAs to enabling conditions, funding recovery as a product, bringing policy into the design early, and giving the frontline real make-right power.

Image credits: Pixabay

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Google Gemini and Cursor to clean up the article, add images and create infographics.

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

The Reality Rule for Business

1 Reply

The Reality Rule for Business

GUEST POST from Shep Hyken

Most of us learned the Golden Rule at a young age: “Do unto others as you would have them do unto you.” This is a perfect rule for business, and specifically customer service and customer experience (CX). It translates into treating customers the way you want to be treated. It makes sense … or does it?

My colleague Dr. Tony Alessandra came up with a version of the Golden Rule he calls the Platinum Rule: “Do unto others as they would like done unto them.” Changing two words, you to them, in this rule means not everyone wants to be treated the in same way you might like to be treated. And in a broader sense, not everyone wants to be treated the same way.

However, when it comes to certain customers, no matter how you treat them, it doesn’t matter. If you don’t recognize this, it can break both employee satisfaction and customer satisfaction. That means it can also break a business.

The Expectation Trap

Recently, I read Give Hospitality by Taylor Scott, which tells the story of an employee who left her job because of a toxic workplace culture and found the perfect job where people, both employees and customers, were treated with respect and dignity. In her second week of training, she read a quote displayed on the company’s training room wall:

“Nothing in the Golden Rule says others will treat us as we have treated them. It only says we must treat others the way we would want to be treated.” – Rosa Parks

This quote from the legendary civil rights activist highlights a basic truth about customer service: exceptional treatment of customers doesn’t guarantee the customer will respond the same way. Yet many front-line employees and managers fall into the expectation trap and become frustrated when customers remain difficult despite receiving outstanding service.

The Danger of Misplaced Expectations

When employees expect customers to change their behavior to mirror that of employees, there is a possible danger of:

Employee Burnout: Front-line staff become disillusioned when their exceptional effort to take care of their customers isn’t appreciated or met with a more positive response. This is one of the top reasons it’s hard to keep good customer service reps. They say, “I can’t take it anymore,” and quit.
Inconsistent Customer Service: Frustrated employees may begin to take on the attitudes of their difficult customers, creating an inconsistent and bad experience for other customers.
Customers Leave: Difficult customers can become your most loyal customers when their problems are resolved with patience, kindness and professionalism, even if they don’t show it in their reactions. To avoid this, employees must be persistent and follow a new rule. (Read on!)

The Danger of Misplaced Expectations

The Reality Rule

Up until now, we have had the Golden Rule and the Platinum Rule. Now we have the Reality Rule:

Treat customers well, even if they don’t treat you well.

This isn’t about unacceptable abuse from a customer. Customers who cross the line with verbal abuse and threats fall under the category of Customers Who Aren’t Worth Doing Business With. Customers are allowed to be angry and agitated. They may be upset about the company or a product, and sometimes their behavior is driven by factors beyond your control.

The Reality Rule has three components:

Control Your Response: While you can’t control the customer’s behavior, you have complete control over your attitude, effort and professionalism. Don’t let your angry customer’s behavior cause you to derail.
Be Consistent: You know what it takes to deliver a great experience. Stay true to the core value of taking care of customers and, as just mentioned and worth mentioning again, don’t let your angry customer’s behavior cause you to go off track.
Turn Foes into Friends: This is more of a goal than a rule, but it’s a goal you must start with in every tenuous interaction. My annual customer service and CX research finds that 81% of customers said they would consider returning to a company if it actively sought to make amends for a bad customer experience. When you handle a complaint properly, the customer will have higher confidence in you and your company than if the problem had never happened at all.

Final Words

When your team embraces the Reality Rule, magic happens. Difficult customers often transform into loyal advocates. Employee satisfaction increases when they understand their role and what they have control over. And your organization builds a reputation for taking care of customers, even when there are problems or complaints.

Remember, you’re not treating customers well because you expect them to change their behavior, although it’s nice when it happens — and sometimes it does. You’re doing it because it’s the right thing to do, knowing in the long run it pays dividends to properly manage problems and complaints. The Reality Rule creates the kind of experience that gets customers to say, “I’ll be back!”

This article was originally published on Forbes.com.

Image credits: Google Gemini

Sign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

9 Jobs-to-Be-Done Prompts Every Product Team Should Run

Leave a reply

9 Jobs-to-Be-Done Prompts Every Product Team Should Run

by Braden Kelley and Art Inteligencia

What Jobs-to-Be-Done Prompts Should Product Teams Run? (Short Answer)

Nine jobs-to-be-done prompts every product team should run: (1) the struggling moment, (2) the progress definition, (3) the trigger, (4) the competing workaround, (5) the hiring and firing criteria, (6) the anxiety and trust barrier, (7) the dignity and emotional cost, (8) the constraints that govern, and (9) the behavior you will falsify. Run them before roadmaps freeze — in customer contact, synthesis, and review — or you will optimize features for a job nobody is actually trying to get done.

A persona describes who marketing hopes exists. A job prompt reveals who showed up trying to make progress — and what they hired instead of you.

Why Isn’t the Backlog the Job?

I have watched product reviews that felt like feature auctions. Requests on the left. Capacity on the right. Someone asked what progress a human was trying to make. The room reached for a persona slide the way a drowning person reaches for a brochure.

Jobs-to-be-done is not a workshop poster. It is a set of prompts you run — in interviews, synthesis, roadmap reviews, and falsification — before the backlog freezes. AI can summarize after contact. It cannot replace the prompts that force contact with reality. Specs and roadmaps can follow. They should not lead.

Prompt	Surfaces	Costume version
1. Struggling moment	Situation, stakes, real language	Generic pain points; scraped reviews as “research”
2. Progress definition	The job in their words	“Users want faster reporting”
3. Trigger	Why act now; switching energy	Evergreen needs with no trigger
4. Competing workaround	Shadow tools, heroics, effort	Competitor cards without workaround archaeology
5. Hiring and firing criteria	Trust, good enough, non-negotiables	Feature parity with no fire criteria
6. Anxiety and trust	Fear, undo, recoverability	“Frictionless UX” that ignores stakes
7. Dignity and emotional cost	Shame, trapped, alone	Sentiment tags without a story
8. Constraints that govern	Policy, politics, system of record	Discovery that ends at the happy path
9. Behavior to falsify	Observable success hypothesis	Roadmap items with no testable behavior

1. What Is the Struggling Moment Prompt?

The prompt: “Walk me through the last time this was hard.” Ask for a specific recent episode — not opinions about the category.

Surfaces: Situation, stakes, context, and language that could not have been invented in the building.

Costume: Generic pain points; scraped reviews mistaken for contact; synthetic personas with fluent prose and no episode.

Run it: One interview rule — no hypotheticals until the story is concrete. If you cannot point to a moment, you do not have a job yet. You have a market segment.

2. How Do You Define Progress in the Customer’s Words?

The prompt: “What were you trying to get done?” Separate the job from the feature request; ask in their words, not your taxonomy.

Surfaces: Functional and emotional progress — not “use our dashboard.”

Costume: Requirements that name features while the decision or relief the human sought stays invisible.

Run it: Write the job as a verb phrase a human would say out loud. If it sounds like a roadmap item, rewrite it. For sharper framing before specs freeze, see 10 Design Questions That Beat a 40-Page Requirements Document.

3. What Is the Trigger Prompt in JTBD?

The prompt: “What changed that made you act now?” Why this moment, not last quarter.

Surfaces: Urgency, switching energy, events that open a hiring window.

Costume: Evergreen “needs” with no trigger — roadmap fiction that could ship any quarter.

Run it: Map triggers to release timing and onboarding moments. Timing is part of the job.

4. How Do You Surface Competing Workarounds?

The prompt: “What did you use instead — including the ugly fix?” Ask for spreadsheets, email chains, heroics, shadow tools — not only named competitors.

Surfaces: Real competition (often internal); effort, failure demand, and dignity cost of the workaround.

Costume: Competitor battle cards without workaround archaeology.

Run it: List every workaround; rank by frequency and dignity cost. For friction customers feel before any map names it, read 12 Friction Points Customers Feel Before Your Journey Map Does.

5. What Are Hiring and Firing Criteria in Jobs-to-Be-Done?

The prompt: “What would make you choose this — and what would make you leave?” Force tradeoffs; ask what “good enough” means and what breaks trust.

Surfaces: Minimum viable trust; switching costs; non-negotiables.

Costume: Feature parity matrices with no firing criteria.

Run it: Pair hire/fire lists before prioritization. If you cannot name fire criteria, you do not know the job — you only know your backlog.

6. How Do You Design for Anxiety and Trust?

The prompt: “What were you afraid would go wrong?” Ask what almost stopped them — embarrassment, rework, blame, compliance fear.

Surfaces: Anxiety as design input; recoverability, undo, and escalation at the moment of truth.

Costume: “Frictionless UX” that ignores stakes; demos that assume infinite confidence.

Run it: Design recovery paths from named anxieties, not generic “error states.” Trust is a job outcome.

7. Why Ask About Dignity and Emotional Cost?

The prompt: “Where did this make you feel stupid, trapped, or alone?” Ask where the experience taxed dignity — repetition, visibility, powerlessness.

Surfaces: Emotional job; shame and confidence; EX/CX overlap when employees deliver the experience.

Costume: Sentiment tags without a human story; NPS without a “why.”

Run it: One dignity cost per journey; owner and measure if you claim to be human-centered. Dignity is not soft. It is design surface.

8. What Constraints Should Govern the Job Map?

The prompt: “What rules, tools, or politics could you not ignore?” Ask what policy, staffing, time, or system-of-record reality shaped the attempt.

Surfaces: The real design surface — not infinite “yes” in the prototype.

Costume: Discovery that ends at the happy path; surprise policy after “done.”

Run it: Constraint map beside job map before solutioning. For what AI can assist versus what humans must own in the craft, see 5 Elements of Human-Centered Design That AI Cannot Own.

9. What Behavior Will You Falsify?

The prompt: “What will people do differently if this job gets easier?” Name one observable behavior — complete in one try, abandon workaround, time-to-confidence.

Surfaces: Testable hypothesis; adoption signal; anti-demo theater.

Costume: Roadmap items with no falsifiable behavior; applause demos that teach nothing.

Run it: One behavior per bet; measure what people do, not what they clap for. For method costume that skips falsification, see 7 Ways Design Thinking Gets Misused.

How Do Product Teams Check JTBD Before the Roadmap Commits?

Before the next roadmap commit, run five go/no-go questions. If you cannot answer them with contact-backed evidence, you are prioritizing features, not jobs:

Did we run contact-backed prompts — not only desk research and generated personas?
Can we state the job in their words — as a verb phrase, not a feature cluster?
What workarounds are we competing with — including the ugly internal ones?
What anxieties and dignity costs are in scope — with recovery designed in?
What behavior falsifies success — not what demo are we showing?

Optional 90-minute JTBD sprint: One journey, one room, nine prompts as a wall — answers as evidence, not slogans. Then a thin backlog that traces back to the prompts. Requirements should be the receipt of understanding — not the substitute for it.

Run the prompts before the backlog owns you.

Frequently Asked Questions

What are jobs-to-be-done prompts?

Jobs-to-be-done prompts are structured questions product teams run in discovery — about struggling moments, progress sought, triggers, workarounds, hire/fire criteria, anxiety, dignity costs, constraints, and falsifiable behaviors — to understand what job a human is trying to get done before freezing features or roadmaps.

How do product teams use JTBD?

Product teams use JTBD in customer interviews, synthesis, roadmap reviews, and testing — running prompts that surface real episodes, language, workarounds, and trust barriers, then tying backlog items to observable behavior change rather than feature requests alone.

What is the difference between JTBD and personas?

Personas often describe demographic or attitudinal segments. JTBD focuses on the progress a person is trying to make in a specific situation — including competing workarounds, triggers, anxieties, and firing criteria. Personas can inform marketing; job prompts should inform product bets.

How do you run JTBD interviews?

Start with a concrete struggling moment — no hypotheticals. Walk through progress sought, what triggered action, what they used instead, hire/fire criteria, fears, dignity costs, and governing constraints. Close by naming one behavior that would change if the job got easier, then test for it.

Can AI replace jobs-to-be-done research?

AI can assist after contact — summarizing interviews, clustering themes, drafting job maps — but it cannot replace lived episodes, workaround archaeology, or judgment about trust and dignity. Synthetic insights without contact produce fluent decoration, not product discovery.

Image credits: Google Gemini

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Resilient Innovation

4 Replies

Why the Future Belongs to Organizations That Think in Three Dimensions

LAST UPDATED: March 11, 2026 at 6:56 PM (SPANISH LANGUAGE VERSION)

by Braden Kelley and Art Inteligencia

I. The Spark: A Venn Diagram That Captures a Powerful Truth

Inspiration for this article came from a simple but powerful visual shared in a recent post by Hugo Gonçalves. The image illustrated the relationship between Future Thinking, Design Thinking, and Systems Thinking using a Venn diagram that placed Resilient Innovation at the center.

At first glance the framework seems obvious. Each discipline is already well established in the innovation world:

Future Thinking helps organizations anticipate multiple possible futures.
Design Thinking focuses on solving problems through a human-centered approach.
Systems Thinking encourages examining systems holistically to understand complexity.

But what makes the diagram compelling is not the individual circles. It is the insight revealed at their intersections. When these disciplines operate together rather than in isolation, they unlock capabilities that are difficult for organizations to achieve otherwise.

At the intersection of Future Thinking and Design Thinking, organizations begin designing solutions for future scenarios rather than merely reacting to present conditions.

Where Design Thinking meets Systems Thinking, innovation becomes both human-centered and system-aware, producing solutions that account for real-world complexity and ripple effects.

And where Future Thinking intersects with Systems Thinking, organizations gain the ability to prepare systems for long-term sustainability and increasing complexity.

Resilient Innovation

When all three perspectives come together, something more powerful emerges: the ability to create innovations that are not only desirable and viable today, but resilient enough to thrive across multiple possible futures.

In a world defined by accelerating change, uncertainty, and interconnected systems, resilient innovation may be the most important capability organizations can develop. And as this simple diagram suggests, it thrives at the intersection of three powerful ways of thinking.

II. The Problem with One-Dimensional Innovation

Most organizations pursue innovation through a single dominant lens. Some lean heavily into design thinking workshops and rapid prototyping. Others invest in strategic foresight to anticipate future disruption. Still others focus on systems analysis to understand complexity and organizational dynamics.

Each of these approaches provides valuable insight. But when used in isolation, each also has significant limitations.

Design thinking, for example, excels at uncovering human needs and translating them into compelling solutions. Yet even the most desirable idea can fail if it ignores the larger systems it must operate within — regulatory structures, supply chains, cultural norms, or organizational incentives.

Future thinking helps organizations explore uncertainty and imagine multiple possible futures. Scenario planning and horizon scanning can expand strategic awareness and reduce surprise. But foresight alone rarely produces solutions that people are ready to adopt.

Systems thinking provides the ability to map complexity, understand feedback loops, and identify leverage points within interconnected environments. However, deep system insight does not automatically translate into solutions that resonate with human users.

When organizations rely on only one of these approaches, innovation often stalls. Ideas may be creative but impractical, visionary but disconnected from human behavior, or analytically sound but difficult to implement.

The challenge is not that these disciplines are flawed. The challenge is that they are incomplete on their own.

Innovation today takes place in environments that are simultaneously human, complex, and uncertain. Addressing only one dimension of that reality inevitably leads to blind spots.

Resilient innovation requires something more: the integration of multiple ways of thinking that together allow organizations to anticipate change, understand complexity, and design solutions people will actually embrace.

III. Future Thinking: Anticipating Multiple Possible Futures

One of the most dangerous assumptions organizations can make is that the future will look largely like the present. History repeatedly shows that markets, technologies, and societal expectations can shift faster than even experienced leaders anticipate.

This is where Future Thinking becomes essential, and the FutureHacking™ methodology helps everyone be their own futurist.

Future thinking is not about predicting a single outcome. Instead, it focuses on exploring a range of plausible futures so organizations can prepare for uncertainty rather than react to it after the fact.

Practitioners of future thinking use tools such as horizon scanning, trend analysis, and scenario planning to identify emerging signals of change and imagine how those signals might combine to shape different future environments.

By examining multiple possible futures, organizations expand their strategic imagination. They begin to see opportunities and risks that would otherwise remain invisible when planning is based solely on past performance or current market conditions.

Future thinking helps leaders ask better questions:

What changes on the horizon could reshape our industry?
Which emerging technologies or behaviors might disrupt our assumptions?
How might our customers’ needs evolve over the next decade?

When organizations incorporate future thinking into their innovation efforts, they gain the ability to design strategies and solutions that remain relevant even as conditions change.

However, foresight alone does not create innovation. Imagining the future is only the beginning. Organizations must also translate those insights into solutions that people value and systems can support.

That is why future thinking becomes far more powerful when combined with other perspectives — particularly the human-centered creativity of design thinking and the holistic understanding provided by systems thinking.

IV. Design Thinking: Solving Problems with a Human-Centered Approach

If future thinking expands our view of what might happen, design thinking helps ensure that the solutions we create actually matter to the people they are intended to serve.

Design thinking is grounded in a deceptively simple premise: innovation succeeds when it begins with a deep understanding of human needs, behaviors, and motivations. Rather than starting with technology or internal capabilities, design thinking begins with empathy.

Practitioners use methods such as observation, interviews, journey mapping, and rapid prototyping to uncover insights about how people experience products, services, and systems in the real world.

Through this process, organizations move beyond assumptions and begin designing solutions that reflect genuine human needs. Ideas are then explored through iterative experimentation, allowing teams to quickly learn what works, what doesn’t, and why.

This approach offers several powerful advantages:

It surfaces unmet or unarticulated customer needs.
It encourages experimentation and rapid learning.
It increases the likelihood that new solutions will be embraced by the people they are designed for.

Design thinking reminds organizations that innovation is not simply about creating something new. It is about creating something people will choose to adopt.

However, even the most human-centered solution can fail if it ignores the broader systems in which it must operate. A beautifully designed product may struggle against regulatory constraints, supply chain limitations, or cultural resistance within organizations.

This is why design thinking alone is not enough. To create innovations that truly endure, organizations must also understand the complex systems surrounding those solutions.

V. Systems Thinking: Seeing the Whole System

While design thinking focuses on people and future thinking explores uncertainty, systems thinking helps organizations understand the complex environments in which innovation must operate.

Modern organizations do not exist in isolation. They function within interconnected systems made up of customers, partners, suppliers, regulators, technologies, cultures, and internal structures. Changes in one part of the system often create ripple effects across many others.

Systems thinking encourages leaders and innovators to step back and examine these relationships holistically rather than focusing only on individual components.

Practitioners use tools such as system maps, causal loop diagrams, and stakeholder ecosystem mapping to identify patterns, dependencies, and feedback loops that influence outcomes over time.

This perspective provides several critical advantages:

It reveals hidden interdependencies within complex environments.
It helps identify leverage points where small changes can create large impact.
It reduces the likelihood of unintended consequences when introducing new solutions.

Many innovations fail not because the idea was flawed, but because the surrounding system was never designed to support it. Incentives may be misaligned. Processes may resist change. Infrastructure may not exist to scale the solution.

Systems thinking helps innovators recognize these structural realities early, allowing them to design solutions that fit within — or intentionally reshape — the systems they operate within.

Yet systems thinking alone can also fall short. Deep analysis of complexity does not automatically produce solutions that resonate with people or anticipate future shifts.

This is why resilient innovation emerges not from any one perspective, but from the intersection of future thinking, design thinking, and systems thinking working together.

Resilient Innovation Infographic

VI. Future Thinking + Design Thinking: Designing Solutions for Future Scenarios

When future thinking and design thinking come together, innovation shifts from solving today’s problems to designing solutions that remain meaningful in tomorrow’s world.

Future thinking expands the time horizon. It helps organizations explore emerging technologies, evolving social expectations, and potential disruptions that could reshape the environment in which products and services operate.

Design thinking brings the human perspective. It ensures that ideas developed in response to these future possibilities remain grounded in real human needs, motivations, and behaviors.

Together, these disciplines allow organizations to design solutions not just for the present moment, but for multiple possible futures.

Rather than asking only “What do customers need today?” teams begin asking deeper questions:

How might customer expectations evolve in the next five to ten years?
What new behaviors could emerge as technologies mature?
How might shifting social norms reshape what people value?

Several practices emerge from this intersection:

Creating future personas that represent how users might behave in different scenarios.
Building scenario-based prototypes that test how solutions perform under different future conditions.
Using speculative design to explore bold possibilities before they become reality.

This combination helps organizations avoid a common innovation trap: designing solutions perfectly optimized for a present that is already beginning to disappear.

By integrating foresight with human-centered design, organizations create innovations that are better prepared to evolve as the future unfolds.

VII. Design Thinking + Systems Thinking

Human-centered innovation is most powerful when it takes the wider system into account.
Integrating empathy with complexity awareness ensures that solutions are not only desirable but also viable and scalable within real-world systems.

Many well-intentioned innovations fail because they neglect system dynamics—leading to unintended consequences that can undermine adoption, efficiency, or long-term impact.

Example Practices

Journey Mapping + System Mapping: Understand the user experience alongside the broader system in which it operates.
Stakeholder Ecosystem Analysis: Identify all the players, relationships, and dependencies that influence outcomes.
Designing for Policy, Culture, and Infrastructure Simultaneously: Ensure solutions are compatible with the real-world environment, not just ideal scenarios.

Benefit: Solutions that scale effectively and endure within complex systems, reducing risk and maximizing long-term impact.

VIII. Future Thinking + Systems Thinking

Combining anticipation with structural understanding enables organizations to prepare systems for long-term sustainability and complexity. This intersection ensures that strategies and innovations are not just reactive but resilient to change and disruption.

Many organizations fail because they plan for the future without considering system-wide dynamics, leaving them vulnerable when change inevitably occurs.

Example Practices

Resilience Mapping: Identify system vulnerabilities and strengths to anticipate risks and opportunities.
Adaptive Strategy Design: Develop strategies that can flex and evolve as conditions change.
Long-Term Capability Building: Invest in skills, processes, and structures that sustain innovation over time.

Benefit: Organizations become prepared for volatility, able to respond to complex challenges without being derailed by disruption.

IX. The Center of the Venn Diagram: Resilient Innovation

True innovation resilience happens at the intersection of all three disciplines: Future Thinking, Design Thinking, and Systems Thinking. Organizations that operate here anticipate multiple possible futures, design solutions humans actually want, and understand the systems those solutions must survive inside.

This holistic approach moves beyond isolated innovation efforts, ensuring solutions are desirable, viable, and adaptable in a complex world.

Capabilities at the Center

Adaptive Innovation Portfolios: Maintain a diverse set of initiatives that can pivot as conditions change.
Experimentation Across Future Scenarios: Test solutions against multiple possible futures to validate robustness.
Human-Centered System Transformation: Redesign processes, structures, and policies to align with real human needs within systemic constraints.

Benefit: Organizations achieve resilient innovation that can thrive amidst uncertainty, disruption, and complexity, rather than merely surviving it.

Innovation Resilience Insights Quote

X. What Leaders Must Do to Build This Capability

Building resilient innovation requires leaders to shift their mindset and practices. It’s no longer enough to treat innovation as a siloed department or isolated initiative. Leaders must actively create the conditions that allow foresight, design, and systems thinking to work together.

Practical Leadership Shifts

Stop Treating Innovation as a Department: Embed innovation across teams and functions, not just in a single unit.
Build Foresight, Design, and Systems Capabilities Together: Develop cross-disciplinary skills that enable three-dimensional thinking.
Encourage Cross-Disciplinary Collaboration: Foster communication and shared problem-solving across different expertise areas.
Measure Resilience, Not Just Efficiency: Track long-term adaptability, system impact, and future-readiness, not only short-term outputs.
Design Organizations That Can Evolve Continuously: Create structures and processes that allow constant learning, adaptation, and iteration.

By adopting these leadership practices, organizations can ensure that their innovation efforts are not only creative but also resilient and scalable within complex systems.

XI. A Simple Test for Your Organization

To evaluate whether your organization is truly building resilient innovation capabilities, ask three critical questions:

Are we designing only for today’s customers, or tomorrow’s realities?
This question tests whether your innovation anticipates future needs and scenarios.
Do our solutions work only in pilot environments, or within real systems?
This evaluates whether innovations are scalable and resilient within the complex systems they must operate in.
Are we solving human problems, or just optimizing processes?
This ensures that your solutions are genuinely human-centered, not just operationally efficient.

If the answer to any of these is “no,” the missing capability likely lies at one of the intersections of Future Thinking, Design Thinking, and Systems Thinking. Addressing these gaps is critical for achieving resilient innovation.

XII. Final Thought: Innovation Is No Longer Linear

The world has become too complex for single-method innovation. Organizations that thrive in the future will be those that operate at the intersection of:

Anticipation: Preparing for multiple possible futures.
Human Understanding: Designing solutions people actually want and will adopt.
System Awareness: Ensuring solutions can survive and scale within real-world systems.

Resilient innovation does not come from seeing the future clearly. It comes from being prepared for many possible futures and designing systems and solutions that can adapt when they arrive. Organizations that master this approach are the ones that will endure, evolve, and thrive.

FAQ: Resilient Innovation

1. What is resilient innovation?

Resilient innovation is the ability of an organization to anticipate multiple possible futures, design solutions humans actually want, and ensure those solutions survive and scale within complex systems. It emerges at the intersection of Future Thinking, Design Thinking, and Systems Thinking.

2. Why do organizations struggle with one-dimensional innovation?

Many organizations rely on a single approach—such as design thinking, systems thinking, or future thinking—without integrating the others. This can lead to solutions that are desirable but not viable, or insightful but not actionable, resulting in innovation that fails to scale or adapt.

3. How can leaders build resilient innovation capabilities?

Leaders can foster resilient innovation by embedding cross-disciplinary collaboration, developing foresight, design, and systems capabilities together, measuring resilience (not just efficiency), and designing organizations that can continuously learn, adapt, and evolve.

p.s. Kristy Lundström posed the question of whether regenerative would be a better adjective than resilient, and I responded that it depends on where you draw the boundaries on the word resilient. I tend to think of it as an active word instead of a passive one, meaning the way that I look at the word incorporates elements of regeneration and making *#&! happen. Keep innovating!

Image credits: ChatGPT, Google Gemini

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from ChatGPT to clean up the article and add citations.

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

VC-Backed Firms in Regulated Industries

Leave a reply

The Times They Are A-Changin’

VC-Backed Firms in Regulated Industries

GUEST POST from Geoffrey A. Moore

This week I have had conversations with executive teams of VC-backed firms working in three different regulated industries: Healthcare, Telco, and Financial Services. All of them reported that their sales pipelines were around 3X what they were a year ago. We didn’t dig into why, although I expect that it means the incumbent providers are under increasing pressure to modernize their operating models and streamline their infrastructure models to meet customer demand and pricing pressure.

The reason we did not get to discuss why this is happening is that each of the teams was more focused on how — how do we adapt our playbook to this new development? You might not think an upsurge in demand would be a problem, but all three of these firms are at least an order of magnitude sub-scale to properly address the demands of their target customers. How do you ride such a wave demand without wiping out? How do you scale and not break your company?

Understanding the Dynamics of the Situation

The easiest way to see what is going on here is to examine it through the lens of the Hierarchy of Powers. Here’s how it plays out:

Category Power. The category is shifting from resisting the next wave to embracing it, albeit reluctantly, because the status quo is deteriorating, and it is clear something has to change. This leads to the upsurge in RFPs and RFIs that each company is now seeing. Budget is being created whereas before it had to be scrounged. This is great news for each enterprise, but it has its challenges.
Company Power. Compared to the Tier 1 prospects each of these companies is targeting, their own is tiny indeed. All of them lack the global reach and depth of personnel their customers require. Nonetheless, these are their most valuable prospects, so they must find a way to engage. That’s the core of the challenge.
Market Power. Each company has already focused on a single vertical—that is how they got as far as they have. Now they are going to have to focus even more rigorously in order to control their exposure to too much demand coming at them too fast and too soon. To secure market power, to become the go-to vendor for their category of offer for this vertical, they must prioritize the right subset of prospects and do whatever it takes to get them over the line.
Offer Power. This is where each company shines. It is why they are each attracting the attention of companies that a year ago were not returning their calls. Their products, however, are highly complex, and the implementations even more so, so they cannot support runaway growth. Moreover, the regulated industries they serve impose rigorous, one might even say onerous, demands, creating a whole series of hoops to jump through before they can get to the other side. How do you “catch the wave” when the sign on the beach says “proceed with caution”?
Execution Power. At the end of the day, this is the crux of the challenge. How can a subscale company with a world-class offer meet the demands of a regulated industry dominated by behemoth enterprises? How should it adapt its playbook?

Adapting the Playbook

Given this change in dynamics, here are the kinds of adaptions that are called for:

Control your destiny by narrowing your focus. The key for all three enterprises is to win a handful of Tier 1 accounts that the rest of the industry looks to for best practices. Winning these accounts will establish them as the go-to choice for the industry as a whole. This objective trumps all others, and every organization inside the company needs to reprioritize its workload accordingly.
Hold fast to your priorities. This is an internal transformation that requires strict discipline to execute. In the past, it was OK to step off the path to address an impromptu request because the demand for everyone’s time was less insistent. Now it is not. Use weekly commits as a way to make workloads visible, and intervene whenever they are drifting off course.
Stay very focused on your top-tier target accounts. Every one of them is a priority, even when they may not be giving you all the reception you want. Conversely, all other prospects are a distraction even when they are inviting you in.
Continue to serve your existing customer base. These are not the Tier 1 players we are targeting, but they are references that can help win those accounts. In addition, they are the early adopters who put their faith in you. You must do right by them.
Align with a big friend. Your target customers need you to bring many more resources to the table than you have inside your company. The good news is that these same customers work with global service providers who specialize in helping them on-board next-generation offers. You need to secure strong support from at least one of these, and you probably cannot easily support more than one, so pick one you think you can trust, and go all in with them on your go-to-market planning.
Let the big friend help you clear your regulatory hurdles. Time is your scarcest resource, and unfortunately, regulated industries are not good at moving swiftly. It’s a mismatch in operating models. VC-backed companies take risks to save time; regulated industries take time to reduce risk. This is not something you are well positioned to deal with. Global services firms, on the other hand, already have relationships with the regulatory authorities you must interface with, not to mention the bandwidth to work through the mandated processes. Do whatever you can to get their help in expediting whatever needs to be done.
Create the solution playbook that you and your GSI friend will co-deliver. Do not let the GSI take over the implementation. You know a lot more about what it takes to make your solution work than they do. But you can make sure that the work is profitable for them by giving them the playbook and letting them bill for their time. You don’t need the services revenue anywhere near as much as you need the Tier 1 account win.
Defer inbound requests that take you off strategy. You don’t have to say no. You just have to say, not yet. Given the amount of stress that any Tier 1 engagement will put on your firm, taking even one account that is off-script risks breaking your camel’s back.
Defer inbound interest around an acquisition. You are at an inflection point in value creation that is potentially extraordinary, the very outcome you and your investors have been preparing for. This is not the time to let go of the reins, particularly if they are going to get handed to an established enterprise whose culture is likely to clash with yours. Moreover, you cannot afford the distraction of all the due diligence that M&A discussions necessarily entail. M&A cannot solve your Tier 1 problem. You have to do that yourself.

Now, to be clear, there are exceptions that could overrule any one of the prescriptions above, so each team needs to review them in light of its own history and circumstances. The key point is that when the market is shifting from a state of scarcity to one of abundance, there is a short time window to catch that wave. The large competitors cannot move fast enough to do this themselves — that is why they are interested in making an acquisition. You are agile enough to do so, but you are painfully subscale — hence the need for the somewhat drastic prescriptions above. Navigating this part of the journey is tricky, but if you stay focused on winning (and keeping!) a handful of Tier 1 accounts, you are making the best bet.

That’s what I think. What do you think?

Image Credit: Google Gemini

Sign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

5 Elements of Human-Centered Design That AI Cannot Own

Leave a reply

5 Elements of Human-Centered Design That AI Cannot Own

by Braden Kelley and Chateau G Pato

What Elements of Human-Centered Design Can AI Not Own? (Short Answer)

Five elements of human-centered design AI cannot own: lived contact with people doing the job, problem framing before solutions, constraint and tradeoff honesty, behavior falsification (not demo applause), and adoption design for Tuesday. AI can draft personas, journey maps, wireframes, and “How might we…” at volume. It cannot bear dignity costs, name what you are empowered to change, choose under uncertainty with accountability, measure what people do, or own the seam after the workshop.

When generation is cheap, the elements that require a body in the room become the whole design — not the wallpaper around the model.

Why Are Artifacts Cheap and Judgment the Design?

I have watched the same room light up twice — once when sticky notes arrived, and again when the model could generate a persona, a journey map, and a clickable prototype before lunch. The second room felt more advanced. It was often less honest.

AI did not retire human-centered design. It made the human elements more urgent. Models can invent users who never existed, roadmaps that answer the wrong question beautifully, and pilots that prove the demo while the operating model stays frozen. Generation got cheap. Design judgment is still expensive — in the right way: contact, stakes, mandate, falsifiable learning, and adoption.

This is not a list of things to ban. It is a division of design labor. AI can assist each element. Humans must own them — because each requires someone who bears stakes, accountability, and contact with Tuesday.

Element	AI can assist	Humans must own
1. Lived contact	Summarize interviews, cluster themes	Field time, dignity costs, reality that contradicts the roadmap
2. Problem framing	Explore options inside a human-set frame	The question, the mandate, killing the wrong problem
3. Constraint honesty	Retrieve policy, model scenarios	Tradeoffs, winners and losers, what we stop doing
4. Behavior falsification	Generate flows, demos, copy variants	What to test, what people do, when to kill the idea
5. Adoption design	Draft rollout plans and training outlines	Owners, seams, shadow-process kill dates, Tuesday

1. Why Can’t AI Own Lived Contact in Human-Centered Design?

The element: Understanding humans by contact — jobs-to-be-done, friction, dignity costs — in their language and context, before the artifact freezes the story.

AI can assist: Summarize interviews, cluster themes, draft empathy maps after contact. Useful synthesis once reality has entered the room.

The costume: Synthetic users, scraped reviews, generated personas nobody met; empathy theater at machine speed. Fluency mistaken for evidence.

Humans own: Field time, ride-alongs, the awkward conversation where reality contradicts the roadmap. If the insight could have been invented in the building, it is not design. It is decoration.

2. Why Is Problem Framing a Design Element AI Cannot Own?

The element: Naming the right problem, constraints, and stakes before freezing solutions — the frame that makes options meaningful.

AI can assist: Explore options inside a human-set frame; draft scenarios; challenge assumptions once the frame exists.

The costume: Instant roadmaps and solution spam that answer the wrong brief beautifully; “innovation” that skips the question entirely.

Humans own: The mandate to sit with the problem; kill ideas that solve a different problem; sponsor alignment on what is actually being designed. Faster wrong is still wrong — and now it ships faster too.

3. What Design Tradeoffs Must Humans Own That AI Cannot Fake?

The element: Surfacing policy, power, incentives, risk, staffing, and dignity limits that govern what can actually ship — and naming winners and losers.

AI can assist: Retrieve policy, summarize regulations, model scenarios within declared constraints.

The costume: Infinite “yes” in the prototype; designs that assume permission nobody has; surprise policy after “done.”

Humans own: The political work of tradeoffs; what we will stop doing; who loses if this works. Design without constraint honesty is a portfolio piece, not a plan. For sharper framing before specs freeze, see 10 Design Questions That Beat a 40-Page Requirements Document.

4. How Do Humans Own Behavior Falsification When AI Makes Prototypes Cheap?

The element: Prototyping and testing to falsify a named human behavior hypothesis — completion, workaround abandoned, time-to-confidence — not to win a room.

AI can assist: Generate clickable flows, agent demos, copy variants for tests. Speed to artifact, not speed to truth.

The costume: Applause demos; portfolio pieces; A/B theater without a behavior theory. Gorgeous output that teaches nothing about Tuesday.

Humans own: Choosing what to falsify; interpreting what people do; killing the idea when the evidence says kill. A beautiful demo that teaches nothing is still theater — and AI makes theater cheaper every quarter.

5. Who Owns Adoption Design That AI Cannot?

The element: Designing for who operates the journey after the markers dry — owners, handoffs, incentives, retirement of the old path, recovery power at the moment of truth.

AI can assist: Draft rollout plans, comms, training outlines — inside a human-owned adoption frame.

The costume: Workshop output that ends at the wall; maps without operators; “we’ll figure out ownership at scale.”

Humans own: Named workflow owner; seam owners; kill date for shadow process; enablement as practice, not completions. Design that stops at demo day is not human-centered. It is human-decorated. For friction customers feel before any map names it, read 12 Friction Points Customers Feel Before Your Journey Map Does.

How Do You Check the Division of Design Labor Before an AI-Assisted Sprint?

Before the next AI-assisted design sprint, run five go/no-go questions. If you cannot answer them, you are buying artifacts without a design:

Who did we talk to — real humans doing the job, in their words?
What problem are we empowered to change — decide, ship, or stop?
What constraint or tradeoff are we naming out loud — policy, power, dignity, what we stop?
What behavior are we falsifying — not what demo are we showing?
Who owns Tuesday after the workshop — workflow, seams, shadow process retired?

For the broader work humans should keep when glue work shrinks, see 11 Human Endeavors AI Should Free (Not Replace). For habits that protect these elements in innovation practice, read 9 Habits of Human-Centered Innovators That Still Matter in the Age of AI. For method costume that skips them, see 7 Ways Design Thinking Gets Misused.

AI can own the draft. Humans own the design — contact, frame, tradeoffs, behavior, and adoption.

Frequently Asked Questions

What elements of human-centered design can AI not replace?

AI cannot own lived contact with real users, problem framing before solutions, honest constraint and tradeoff work, behavior falsification in testing, or adoption design for Tuesday. It can assist each — drafting, clustering, prototyping — but humans must bear stakes, mandate, accountability, and contact with reality.

Can AI do human-centered design?

AI can accelerate artifacts inside human-centered design — personas, maps, wireframes, copy — but it cannot do the design discipline on its own. Without human-owned contact, framing, tradeoffs, falsification, and adoption, AI produces fluent decoration: faster artifacts, same theater.

What is the difference between AI-assisted design and AI-owned design?

AI-assisted design uses models after humans set the problem frame, gather real evidence, and clarify decision rights — then to explore, draft, and test faster. AI-owned design lets generation substitute for contact, framing, tradeoffs, learning, and adoption — producing impressive artifacts that never land on Tuesday.

Why do AI-generated personas fail in human-centered design?

They often replace lived contact instead of summarizing it. Synthetic personas feel researched because the prose is fluent, but they optimize for a human who never existed — skipping dignity costs, workarounds, and the awkward truth that contradicts the roadmap. Empathy theater at machine speed.

How do you keep design human with AI?

Keep humans owning contact, problem framing, constraint honesty, behavior falsification, and adoption design. Use AI inside that frame for synthesis and speed. Run a division-of-labor check before each sprint: real humans in the evidence, empowered problem, named tradeoffs, falsifiable behavior, and an owner for Tuesday.

Image credits: Gemini

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

You Need a Customer Experience Risk & Revenue Leakage Diagnostic

8 Replies

Why You’re Losing More Than You Think — and Don’t Even Know It

LAST UPDATED: May 29, 2026 at 6:27 PM (SPANISH LANGUAGE VERSION)

You Need a Customer Experience Risk & Revenue Leakage Diagnostic

by Braden Kelley and Art Inteligencia

I. The Invisible Cost of Friction

Most organizations measure revenue. Some measure profit. A growing number measure customer satisfaction. But very few measure revenue at risk — and almost none systematically measure experience-driven revenue leakage.

The hard truth is this: what customers experience today determines what finance reports tomorrow. Friction in the customer journey rarely shows up immediately on a balance sheet. Instead, it accumulates quietly — in hesitation, in doubt, in abandoned transactions, in unresolved issues, and in eroding trust.

Every confusing onboarding flow. Every policy that makes sense internally but frustrates externally. Every moment where a customer has to work harder than they expected. These are not minor inconveniences. They are micro-withdrawals from future growth.

When friction compounds, it becomes invisible leakage:

Customers buy less than they intended.
Customers delay decisions.
Customers quietly explore alternatives.
Customers leave without complaint.

Because traditional dashboards focus on lagging indicators, leaders often miss the early warning signs. By the time churn rises or margins compress, the experience damage has already been done.

Customer experience is not a “soft” discipline. It is a leading indicator of financial performance. If you are not measuring friction financially, you are tolerating it culturally.

The first step toward sustainable growth is acknowledging a simple but uncomfortable reality: what you cannot see is already costing you.

II. What Is a Customer Experience Risk & Revenue Leakage Diagnostic?

A Customer Experience Risk & Revenue Leakage Diagnostic (aka Customer Experience Audit) is a structured, cross-functional assessment designed to uncover where your organization is unintentionally creating friction, eroding trust, and putting future revenue at risk.

It is not a satisfaction survey. It is not a brand perception study. And it is not a one-time journey mapping workshop.

It is a strategic instrument that connects customer experience directly to financial performance.

At its core, the diagnostic is designed to:

Identify friction across the end-to-end customer journey
From awareness and onboarding to service and renewal, it reveals where customers hesitate, struggle, or disengage.
Quantify the financial impact of experience breakdowns
It translates moments of frustration into measurable revenue exposure, cost-to-serve distortion, and lifetime value erosion.
Prioritize improvements based on risk and recovery potential
It enables leadership to focus on interventions that reduce risk, restore trust, and unlock trapped growth.

Unlike traditional CX metrics that tell you what happened, this diagnostic helps you understand why it happened — and what it is costing you.

By integrating operational data, customer feedback, employee insight, and financial modeling, the organization gains a clear view of:

Where revenue is quietly leaking
Where trust is weakening
Where internal complexity is surfacing as external pain
Where competitors are gaining advantage through simplicity

In short, a Customer Experience Risk & Revenue Leakage Diagnostic reframes customer experience from a qualitative aspiration into a measurable performance and risk management discipline.

III. Why Traditional Metrics Fail

Most organizations believe they are measuring customer experience effectively. They track Net Promoter Score (NPS), Customer Satisfaction (CSAT), conversion rates, churn rates, and average handle time. These metrics are familiar. They are benchmarked. They are reported to leadership regularly.

The problem is not that these metrics are wrong. The problem is that they are incomplete — and mostly lagging indicators.

They tell you what happened. They rarely tell you why it happened. And almost never do they tell you what it is costing you before it shows up in revenue.

The Three Core Limitations

They Measure Sentiment, Not Exposure
A customer can report being “satisfied” while still experiencing friction that reduces purchase frequency, basket size, or long-term loyalty.
They Are Aggregated and Diluted
Journey-level breakdowns are often hidden inside company-wide averages. A single high-friction touchpoint can erode trust even if the overall score appears stable.
They Are Backward-Looking
By the time churn rises or referrals fall, the experience damage has already compounded. Leadership is reacting to symptoms, not preventing causes.

Most importantly, traditional metrics rarely connect experience breakdowns directly to financial risk. Without that connection, friction becomes normalized.

Measurement shapes behavior. If you do not measure friction in financial terms, you unintentionally signal that it is tolerable.

A Customer Experience Risk & Revenue Leakage Diagnostic shifts the focus from “How are we scoring?” to a far more strategic question:

“Where are we unintentionally putting future revenue at risk?”

That reframing changes the conversation — from reporting outcomes to preventing loss and unlocking growth.

IV. The Four Hidden Sources of Revenue Leakage

Revenue rarely disappears in dramatic fashion. It erodes quietly — through friction, misalignment, and unexamined assumptions. Most organizations don’t have a revenue problem. They have a leakage problem.

A Customer Experience Risk & Revenue Leakage Diagnostic exposes four primary sources of hidden loss.

1. Friction Leakage

Friction leakage occurs when customers encounter unnecessary effort, confusion, or delay throughout their journey.

Abandoned carts and incomplete applications
Complicated onboarding experiences
Repetitive support interactions
Opaque pricing or renewal processes

Every moment of confusion acts as a micro-tax on growth. Individually small. Collectively significant.

2. Trust Leakage

Trust leakage is more subtle — and more dangerous. It happens when promises and delivery drift apart.

Inconsistent messaging across channels
Unmet service commitments
Poor recovery after failure
Policy decisions that prioritize internal efficiency over customer fairness

Trust is the invisible infrastructure of sustainable growth. When it weakens, customers may not complain — they simply reduce engagement.

3. Capability Leakage

Capability leakage originates inside the organization but manifests externally. It occurs when employees lack the tools, authority, or alignment needed to deliver a seamless experience.

Siloed data systems
Disconnected technology platforms
Incentives that reward internal metrics over customer outcomes
Front-line employees unable to resolve issues without escalation

Internal complexity always becomes external friction.

4. Strategic Blind Spots

Strategic leakage occurs when leadership decisions unintentionally trade long-term growth for short-term optimization.

Cost-cutting that degrades customer value
Underinvestment in journey orchestration
Failure to listen to front-line and edge-of-organization insights
Overconfidence in lagging indicators

The edges of the organization are where the future first becomes visible. If leadership is not looking there, risk compounds silently.

When these four forms of leakage intersect, the financial impact multiplies. The diagnostic does not just identify them — it quantifies them, transforming abstract experience concerns into measurable business priorities.

V. The Business Case: Why This Diagnostic Is Now Essential

The question is no longer whether customer experience matters. The question is whether you can afford to leave it undiagnosed.

Market dynamics have shifted. Expectations have accelerated. Transparency has increased. Acquisition costs continue to rise. In this environment, unmanaged experience risk is a strategic liability.

1. Customer Expectations Are Compounding

Customers do not compare you only to direct competitors. They compare you to the best experience they have had anywhere. Friction tolerance declines every year.

What felt “acceptable” five years ago now feels outdated. What feels slightly inconvenient today becomes unacceptable tomorrow.

2. Digital Transparency Amplifies Experience Gaps

One broken interaction can scale rapidly through reviews, social platforms, and peer networks.

Experience inconsistency is no longer contained. Reputation moves at the speed of visibility.

3. Growth Is More Expensive Than Retention

Customer acquisition costs continue to climb across industries. When revenue leaks through preventable friction, organizations are forced to spend more just to stand still.

Protecting and expanding lifetime value is now a financial imperative — not a marketing aspiration.

4. Innovation Without Experience Discipline Fails

Organizations invest heavily in new products, services, and technologies. But innovation layered on top of broken journeys simply magnifies dysfunction.

Scale amplifies whatever system you have — good or bad. If the experience foundation is fragile, growth initiatives will expose the cracks.

5. Risk Management Must Extend Beyond Compliance

Most enterprises have mature financial and operational risk frameworks. Few have equivalent rigor applied to customer experience risk.

A Customer Experience Risk & Revenue Leakage Diagnostic closes that gap, elevating experience from a functional concern to a board-level performance and risk management priority.

In today’s environment, diagnosing experience risk is not optional. It is foundational to sustainable, human-centered growth.

CX Risk and Revenue Leakage Diagnostic Business Case

VI. What a High-Impact Diagnostic Actually Measures

If you are going to treat customer experience as a growth and risk discipline, you must measure it with the same rigor you apply to financial performance. A high-impact Customer Experience Risk & Revenue Leakage Diagnostic goes far beyond sentiment scores.

It evaluates exposure, root causes, and financial implications — across the entire customer lifecycle.

A. Journey-Level Risk Exposure

The diagnostic identifies where customers hesitate, struggle, or disengage across key stages of the journey.

Drop-off and abandonment patterns
Cycle time delays
Escalation and repeat contact rates
Inconsistent cross-channel transitions

Rather than looking at averages, it isolates specific high-risk touchpoints where friction compounds and revenue becomes vulnerable.

B. Emotional Friction Points

Not all risk is operational. Some of the most expensive leakage begins at the emotional level.

Moments of uncertainty or confusion
Moments of perceived unfairness
Moments where trust is tested
Moments where customers feel unheard

Emotional friction reduces confidence — and reduced confidence lowers commitment, expansion, and advocacy.

C. Operational Root Causes

High-impact diagnostics do not stop at symptoms. They trace friction back to systemic drivers.

Policy-driven constraints
Technology integration gaps
Siloed data and decision rights
Misaligned incentives and performance metrics

Internal complexity inevitably surfaces as external customer pain. Sustainable solutions require structural insight.

D. Financial Impact Modeling

The most critical component is quantification. Friction must be translated into financial terms.

Revenue at risk by journey stage
Lifetime value erosion
Cost-to-serve inflation
Margin compression driven by service recovery

When experience breakdowns are expressed in dollars, prioritization becomes clearer and alignment accelerates.

A high-impact diagnostic makes the invisible visible — not just emotionally, but economically.

VII. From Insight to Action: Turning Risk into Recovery

A diagnostic without activation is theater.

Insight alone does not recover revenue. Awareness alone does not restore trust. If the findings from a Customer Experience Risk & Revenue Leakage Diagnostic do not change behavior, structure, and investment decisions, then the organization has simply produced a more sophisticated report.

The goal is not understanding. The goal is recovery.

1. Capture Immediate Revenue Through Quick Wins

Every diagnostic surfaces friction points that can be resolved quickly:

Simplifying confusing onboarding steps
Clarifying pricing language
Reducing redundant approval gates
Fixing high-volume support failure points

These are not cosmetic improvements. They are revenue recovery mechanisms. When friction decreases, conversion improves. When clarity increases, hesitation declines. Early wins build organizational momentum and prove that experience discipline drives financial results.

2. Eliminate Structural Sources of Systemic Friction

Some leakage is not tactical. It is architectural.

Siloed systems. Misaligned incentives. Policy-driven complexity. Governance bottlenecks.

These require cross-functional intervention. This is where leadership courage matters. Because structural friction is usually owned by no one — and tolerated by everyone.

True recovery demands redesigning how the organization works, not just how the customer journey looks.

3. Invest in Capability to Prevent Recurrence

Experience breakdowns often trace back to capability gaps:

Frontline employees without decision authority
Teams without access to unified customer data
Leaders without visibility into journey-level risk metrics

If the organization cannot detect friction early, it will continue to leak revenue quietly. Capability investment turns reactive firefighting into proactive orchestration.

4. Institutionalize Experience Accountability

Lasting change requires governance.

That means:

Assigning executive ownership for journey health
Embedding experience risk metrics into performance dashboards
Aligning incentives with friction reduction and trust preservation

Measurement shapes behavior. When experience risk is measured financially, it stops being a “soft” concern and becomes a board-level priority.

The Shift

When organizations move from insight to action, the narrative changes.

We are not improving customer satisfaction.
We are recovering growth.
We are protecting margin.
We are strengthening trust.

A Customer Experience Risk & Revenue Leakage Diagnostic is not the finish line. It is the ignition point. What matters is what the organization does next — how quickly it acts, how boldly it redesigns, and how deeply it commits to human-centered accountability.

Because friction compounds.

But so does disciplined recovery.

Turning Risk Into Recovery

VIII. The Cultural Impact

Conducting a Customer Experience Risk & Revenue Leakage Diagnostic is not just about numbers and dashboards. It is a catalyst for cultural transformation.

When an organization quantifies experience risk, it sends a clear signal: customer outcomes are inseparable from business performance.

Key Cultural Shifts

Finance Pays Attention: Revenue leakage is now measurable and visible, making it a board-level concern rather than an abstract notion.
Operations Engage: Front-line teams see how their actions directly influence financial outcomes, motivating proactive problem-solving.
Leadership Prioritizes: Strategic planning incorporates experience risk as a key dimension alongside cost, efficiency, and growth targets.
Employees Gain Clarity: Everyone understands how day-to-day decisions impact customer trust, loyalty, and revenue.

The conversation shifts from:

“How satisfied are our customers?”

To a more strategic and actionable question:

“How much growth are we leaving on the table?”

This cultural shift embeds accountability for experience across all levels of the organization. It moves customer experience from a departmental initiative to an enterprise-wide performance discipline.

Ultimately, organizations that embrace this mindset are more agile, more resilient, and more capable of sustaining profitable growth.

IX. The Leadership Imperative

Human-centered change begins with leaders who are willing to see reality clearly. A Customer Experience Risk & Revenue Leakage Diagnostic provides the lens to identify hidden friction, quantify its impact, and prioritize action.

Leadership cannot afford to rely on assumptions, anecdotal feedback, or lagging metrics. The future of growth is determined by how well the organization prevents leakage before it appears on the balance sheet.

Core Principles for Leaders

See Reality Clearly: Recognize that friction and trust erosion are real, measurable threats to revenue and loyalty.
Measure What Truly Matters: Go beyond NPS, CSAT, and churn metrics. Quantify revenue at risk and the financial impact of experience breakdowns.
Act Proactively: Use diagnostic insights to guide immediate interventions, structural improvements, and capability development.
Embed Accountability: Make experience risk a shared responsibility across functions, not a siloed initiative.

A diagnostic without leadership activation is just a report. True impact comes when insights are operationalized, turning risk into recovery and friction into opportunity.

Ultimately, leaders who embrace this approach shift the organizational conversation from:

“Are we delivering good experiences?”

To a more strategic and urgent question:

“Where are we unintentionally putting future revenue at risk, and how do we fix it?”

This is the leadership imperative: see, measure, act, and embed a culture where customer experience drives sustainable growth.

X. Closing Thought

Innovation does not fail because ideas are weak. It fails because the experience system cannot support them. A brilliant product, service, or solution cannot thrive if friction, trust gaps, or operational constraints block its path to the customer.

If you want sustainable growth, three imperatives are clear:

Stop guessing: Uncover hidden friction and revenue leakage before it escalates.
Stop relying on lagging indicators: Traditional metrics alone will not reveal the silent risks undermining growth.
Diagnose, quantify, and act: Translate insights into immediate interventions, structural fixes, and capability investments.

Because what you cannot see will eventually show up — in churn, in margin compression, and in lost relevance. Waiting until it appears on financial statements is too late.

A Customer Experience Risk & Revenue Leakage Diagnostic gives organizations the clarity, rigor, and foresight needed to protect revenue, strengthen trust, and enable innovation to scale successfully.

In the end, the diagnostic is not just a tool. It is a strategic mindset: measure what matters, see reality, and act decisively. Those who embrace it will not just survive disruption — they will thrive in it.

Reserve your Customer Experience Risk & Revenue Leakage Diagnostic with Braden Kelley today

FAQ: Customer Experience Risk & Revenue Leakage Diagnostic

1. What exactly is a Customer Experience Risk & Revenue Leakage Diagnostic?

It is a structured assessment that identifies friction points across the customer journey, measures the financial impact of experience breakdowns, and prioritizes actions to reduce risk and recover lost revenue. Unlike traditional surveys, it connects customer experience directly to measurable business outcomes.

2. How does this diagnostic differ from traditional CX metrics like NPS or CSAT?

Traditional metrics are lagging indicators that report what has already happened. A diagnostic goes deeper by uncovering hidden sources of friction and trust erosion, quantifying revenue at risk, and linking operational and emotional touchpoints to tangible financial consequences. It transforms CX from a qualitative measure into a strategic risk and growth tool.

3. Who in the organization benefits from this diagnostic?

Everyone from leadership to front-line employees benefits. Leaders gain visibility into financial risk and opportunity, operations teams understand where to focus improvements, and employees see how daily actions impact customer trust and revenue. It aligns the entire organization around measurable experience outcomes.

Reserve your Customer Experience Risk & Revenue Leakage Diagnostic with Braden Kelley today

Image credits: ChatGPT, Google Gemini

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from ChatGPT to clean up the article and add citations.

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

12 Friction Points Customers Feel Before Your Journey Map Does

Leave a reply

12 Friction Points Customers Feel Before Your Journey Map Does

by Braden Kelley and Art Inteligencia

Why Do Customers Feel Friction Before Your Journey Map Does? (Short Answer)

Customers feel friction before your journey map does because maps are stage posters, not nervous systems. They capture channels, steps, and the happy path. They miss homework before entry, the wrong door, identity theater, story-retelling, unowned waiting, handoff cliffs, life-context tax, dignity costs, status opacity, recovery that never made the swimlane, policy after “done,” and powerless humans at the moment of truth.

A journey map is a photograph of the path you already believe. Friction is what the body pays while you are still scheduling the workshop.

The Map Is a Late Instrument

I have stood in rooms where the journey map could have hung in a gallery. Stages were labeled. Emotions were color-coded. Someone had even drawn a little heart at “loyalty.”

Meanwhile, a human was still on hold in a parking lot, assembling a stack of documents your portal already has, about to retell their story for the third time — to a person who is not allowed to help.

That is not a mapping skill gap. It is a timing gap. Maps organize the path you can already see. Lived friction shows up in voids, homework, and dignity costs that workshops flatten into arrows. If you want the artifact to catch up, start with what Tuesday already knows.

Friction	Why maps miss it	Do instead
1. Homework before entry	Mapping starts at “start”	Inventory and kill unpaid pre-work
2. Wrong door	Assumes they found the right journey	Design wayfinding, not punishment
3. Identity theater	Login is a technical box	Time-to-recognized-human
4. Story-retelling tax	Each lane has its own intake	Context that travels; own the seam
5. Unowned waiting	Wait is an arrow or omitted	Design the silence with an owner
6. Handoff cliffs	Arrows look like integration	Seam owners, not just stages
7. Life-context tax	Personas sit still at a desk	Design for interrupted humans
8. Dignity costs	Emotion is color, not requirement	Name shame with owners and power
9. Status opacity	Your stages, their fog	Progress as a product
10. Unmapped recovery	Happy path starts at browse	Map from the mess
11. Policy after “done”	Rules live in another department	Surface constraints before close
12. Powerless humans	Frontline is a box, not a constraint	Fund authority at the moment of truth

1. What Homework Do Customers Do Before Your Journey Even Starts?

What they feel: Assembling documents, researching which form, rehearsing the call, printing what your portal already has. The journey has not “started.” The labor has.

Why the map lags: Mapping begins at awareness or start service. Unpaid pre-work is off-canvas — therefore it is nobody’s job.

Instead: Inventory the homework. Kill it or own it as a designed step with less burden. If they had to prepare to be your customer, you already charged them — in time.

2. Why Is the Wrong Door Friction Your Journey Map Never Shows?

What they feel: The wrong product, phone tree, chatbot, or department — then starting over. Lost is treated as their error.

Why the map lags: Maps assume the customer found the right journey. Wrong-door is “not our segment,” which is a polite way of saying not our poster.

Instead: Design wayfinding and first-contact triage as part of the experience, not a filter that punishes the lost. The first door is the journey.

3. How Does Identity Theater Hurt Customers Before Stages Do?

What they feel: Prove who you are again — account numbers, one-time codes, “security questions,” matching a household that does not match your system.

Why the map lags: Login is a technical box, not an emotional stage. The map never scores the humiliation of being a stranger to a company that already has your money.

Instead: Measure time-to-recognized-human. Reduce proof loops. Preserve identity across handoffs. Recognition is experience, not IT hygiene.

4. What Is the Story-Retelling Tax in Customer Experience?

What they feel: Explaining the situation to the IVR, then the agent, then the specialist, then the portal. Same wound, new clipboard.

Why the map lags: Each swimlane has its own “intake.” The artifact does not feel the repeat. Only the human does.

Instead: Context that travels. If they must retell, the seam is broken — name an owner. Retelling is not thoroughness. It is failure demand with a smile.

5. Why Is Unowned Waiting Invisible on Most Journey Maps?

What they feel: Hold music, “we’ll be in touch,” tickets with no clock, overnight voids that are not a “stage.” Anxiety has nowhere to sit on the poster.

Why the map lags: Waiting is drawn as an arrow or omitted. Arrows do not have anxiety. Silence has no swimlane.

Instead: Make wait a designed moment — what they know, when, and who is accountable for the silence. If nobody owns the gap, the customer owns the dread.

6. What Is a Handoff Cliff in Customer Experience?

What they feel: Falling between teams, systems, or shifts. The map’s neat arrow is a cliff in real life. They did not “drop off.” They were dropped.

Why the map lags: Workshops love arrows. Operating models hate owning the seam. Integration on paper is not a handshake in the work.

Instead: Seam owners, not just stage owners. Test the handoff, not the poster. If the arrow cannot name a human, it is decoration.

7. How Does Life Context Create Friction Maps Don’t Capture?

What they feel: Doing this while at work, with a child, on a bus, in a language that is not the workshop’s, on a phone with a dying battery.

Why the map lags: Personas sit still at a desk in a dedicated “user hour.” Real customers do not. Interrupted life is treated as edge case.

Instead: Design for interrupted, mobile, exhausted humans. If it only works in the lab’s quiet hour, it does not work.

8. Which Dignity Costs Do Journey Maps Soften Into Color?

What they feel: Shame. Being talked down to. Proving they are not a fraud. Begging for an exception they should not have to beg for.

Why the map lags: Emotion lanes become color, not design requirements. Dignity is filed under “tone of voice.”

Instead: Name dignity failures as friction with owners — recovery power, language, and the right to be believed. If it cannot be funded, it was never a requirement. It was wallpaper.

9. Why Does Status Opacity Hurt Customers More Than Your Stages Admit?

What they feel: Not knowing what happens next, whether it worked, or who has the ball. Your internal stages are a cathedral. Their view is fog.

Why the map lags: Progress is visible to you. It is invisible to them. The map is drawn from the inside out.

Instead: Customer-facing status as a product — not a courtesy email when legal remembers. If they have to call to learn where they are, you hid the journey.

10. Why Does Recovery Friction Never Make the Happy-Path Map?

What they feel: Something already broke. The map still starts at browse, buy, onboard. Their whole journey is “please undo this.”

Why the map lags: Happy-path mapping treats failure as an exception swimlane nobody funds. Failure demand is a large share of real volume.

Instead: Map from the mess. If recovery is not a first-class journey, you are mapping a brochure.

11. How Does Policy After “Done” Betray Customers Maps Call Successful?

What they feel: Fine print, eligibility, fees, “that’s not covered” — a rule that appears after they already committed, emotionally and sometimes financially.

Why the map lags: Policy lives in a different department’s map, or in no map. The happy path ends at conversion. The ambush starts after.

Instead: Surface constraints before the emotional close. Surprise policy is not a compliance detail. It is a designed betrayal.

12. Why Do Powerless Humans Create Friction Before Your VoC Loop Does?

What they feel: A person who knows what they deserve and an employee who is not allowed to deliver it. The gap is audible in the first ten seconds.

Why the map lags: Maps show “agent / frontline” as a box, not a constraint. Voice of customer arrives after the quit or the rant — late, as maps are late.

Instead: Fund authority where the moment lives. The customer felt the power gap before your closed loop did. Enablement is not a cascade deck. It is decision rights on Tuesday.

How Do You Find Customer Friction Before You Reprint the Journey Map?

Before the next mapping offsite, answer five questions. If you cannot, you are about to photograph a path that is already lying:

Where is the unpaid homework before “start”?
Where do they retell the same story across seams?
Where is the wait unowned — silence with no clock and no human?
Where does dignity fail — shame, disbelief, begging?
Where does policy ambush “done” after they thought they had finished?

If your maps still end at the wall with nobody owning the seam, that is a different failure — see 7 Ways Design Thinking Gets Misused. If listening still arrives as a dead form after the moment has passed, read Conversational and Agentic VoC. If the friction is felt and still unfunded, the budget story is in 9 Reasons Companies Underinvest in CX.

If it is not on the map yet, it is already in the customer’s Tuesday. Map late if you must. Listen early.

Frequently Asked Questions

Why do journey maps miss customer friction?

Journey maps miss friction because they are stage posters drawn from the path the organization already believes. They capture channels, steps, and happy paths while customers pay in homework, waiting, retelling, dignity costs, and seams nobody owns — voids that workshops flatten into arrows.

What friction do customers feel that maps miss?

Common missed frictions include unpaid homework before entry, the wrong door, identity theater, story-retelling, unowned waiting, handoff cliffs, life-context tax, dignity costs, status opacity, recovery that never made the happy path, policy after “done,” and powerless frontline humans at the moment of truth.

How do you find friction before mapping a customer journey?

Listen in lived time: ride-alongs, contact recordings, failure-demand tickets, and the questions customers ask while waiting. Inventory homework, retells, unowned waits, dignity failures, and policy ambushes before you reprint stages. If evidence could not have been invented in a conference room, you are getting closer.

Are customer journey maps still useful?

Yes — as a shared picture after you have contact with reality, with owners for stages and seams. They fail when they lead, when they photograph the happy path only, or when they hang on a wall with no operator for broken handoffs. Maps should follow listening, not replace it.

What is a handoff cliff in CX?

A handoff cliff is the gap between teams, systems, or shifts where the customer falls even though the journey map shows a neat arrow. The arrow is not an owner. Until someone is accountable for the seam, integration exists only on the poster.

Image credits: Pixabay

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Pixbay and Cursor to clean up the article, add images and create infographics.

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Top 10 Human-Centered Change & Innovation Articles of February 2026

Leave a reply

Top 10 Human-Centered Change & Innovation Articles of February 2026 Drum roll please…

At the beginning of each month, we will profile the ten articles from the previous month that generated the most traffic to Human-Centered Change & Innovation. Did your favorite make the cut?

But enough delay, here are February’s ten most popular innovation posts:

Three Myths That Kill Change and Transformation — by Greg Satell
Why a Customer Experience Audit is Non-Negotiable in 2026 — by Braden Kelley
Innovation Lessons from the 50 Most Admired Companies of 2026 — by Braden Kelley
Is Your Customer Experience a Lie? — by Braden Kelley
Important or Urgent? — by Stefan Lindegaard
The Greatest Inventor You’ve Never Heard of — by John Bessant
5 Simple Keys to Becoming a Powerful Communicator — by Greg Satell
Do You Have What It Takes to be a Visionary? — Exclusive Interview with Mark C. Winters
Temporal Agency – How Innovators Stop Time from Bullying Them — by Art Inteligencia
Causal AI – Moving Beyond Prediction to Purpose — by Art Inteligencia

BONUS – Here are five more strong articles published in January that continue to resonate with people:

Top 40 Innovation Authors of 2025 — Curated by Braden Kelley
Win Your Way to an AI Job — by Art Inteligencia
How Engineered Living Therapeutics Are Redefining Healthcare — by Art Inteligencia
Tackle Your Toughest Challenge This Year — by Geoffrey Moore
You Cannot Be Too Busy to Prioritize — by Stefan Lindegaard

If you’re not familiar with Human-Centered Change & Innovation, we publish 4-7 new articles every week built around innovation and transformation insights from our roster of contributing authors and ad hoc submissions from community members. Get the articles right in your Facebook, Twitter or Linkedin feeds too!

Have something to contribute?

Human-Centered Change & Innovation is open to contributions from any and all innovation and transformation professionals out there (practitioners, professors, researchers, consultants, authors, etc.) who have valuable human-centered change and innovation insights to share with everyone for the greater good. If you’d like to contribute, please contact me.

P.S. Here are our Top 40 Innovation Bloggers lists from the last five years:

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Why Change Doesn’t Have to Start at the Top

Leave a reply

Why Change Doesn't Have to Start at the Top

GUEST POST from Greg Satell

In 2004 I found myself running a major news organization during the Orange Revolution in Ukraine. It was one of those moments when the universe opens up, reveals a bit of itself and you realize the world doesn’t work the way you thought it did. What struck me at the time was that nobody with any conventional form of power had any ability to shape events at all.

One of the myths that is constantly repeated is that change needs to start at the top. Clearly that is not true. It wasn’t true of the Color Revolutions that spread across Eastern Europe. Nor was it true of social movements like the fight for LGBT rights. Despite what you may have heard, it doesn’t hold true for organizations either.

What is true is that if you are going to bring about genuine change you need to influence institutions and that means you need, at some point, to involve senior leaders, but it rarely starts with them. The myth that change has to start at the top is a copout — a reason to do nothing when you can do something. Make no mistake. Change can come from anywhere.

Weaving Webs of Influence

Movements, as the name implies, are kinetic. They start somewhere and they end up somewhere else. That’s one reason why why so many successful change efforts become misunderstood. People look back at an event like the 1963 March on Washington and think that’s what made the civil rights movement successful. Nothing could be further from the truth. That wasn’t what built the movement, it was part of the end game.

Consider that the first “March on Washington,” the Woman Suffrage Procession of 1913, was a disaster. None of the others since 1963 did much either. The civil rights march came after nearly a decade of boycotts, sit-ins, Freedom Rides and other tactics that built the movement before it finally found its moment. Still, it’s the moment that people remember.

In much the same way, whenever we see a successful transformation we look to the actions of leaders. We see a CEO who gave a speech, a marketer who came up with a big product idea or an engineer who took a project in a new direction. These events are real, but they rarely, if ever, appear out of nowhere. They are products of webs of influence.

When we look more closely, we inevitably find that the CEO was inspired to give the pivotal speech from a conversation he had with his daughter. The marketer got the initial idea for the campaign from a junior team member. Or the engineer changed the direction of the project after a fateful encounter he had in the cafeteria.

Our decisions are the product of complex systems. Anything can start anywhere. Don’t let anyone tell you differently.

Going to Where the Energy Is

Transformations, in retrospect, often seem inevitable, even obvious. Yet they don’t start out that way. The truth is that it is small groups, loosely connected, but united by a common purpose that drives transformation. So the first thing you want to do is identify your apostles — people who are already excited about the possibilities for change.

For example, in his efforts to reform the Pentagon, Colonel John Boyd began every initiative by briefing a group of collaborators he called the “Acolytes,” who would help hone and sharpen the ideas. He then moved on to congressional staffers, elected officials and the media. By the time general officers were aware of what he was doing, he had too much support to ignore.

In a similar vein, a massive effort to implement lean manufacturing methods at Wyeth Pharmaceuticals began with one team at one factory, but grew to encompass 17,000 employees across 25 sites worldwide and cut manufacturing costs by 25%. The campaign that overthrew Serbian dictator Slobodan Milošević started with just 5 kids in a coffee shop.

One advantage to starting small is that you can identify your apostles informally, even through casual conversations. In skills-based transformations, change leaders often start with workshops and see who seems enthusiastic or comes up after the session. Your apostles don’t need to have senior positions or special skills, they just have to be passionate.

There’s something about human nature that, when we’re passionate about an idea, makes us want to go convince the skeptics. Don’t do that. Start with people who want your idea to succeed. If you feel the urge to convince or persuade, that’s a sign that you either have the wrong idea or the wrong people.

“You have to go where the energy is,” John Gadsby, who built a movement for process improvement inside Procter & Gamble that has grown to encompass 60,000 employees, told me. “We’ll choose energy and excitement and enthusiasm over the right position, or the person at the right leadership level, or the person whose job it is supposed to be to do that.”

Mobilizing People To Influence Institutions

In the early 1990s, writer and activist Jeffrey Ballinger published a series of investigations about Nike’s use of sweatshops in Asia. People were shocked by the horrible conditions that workers — many of them children — were subjected to. In most cases, the owners lived outside the countries where the factories were located and had little contact with their employees.

At first, Nike’s CEO, Phil Knight, was defiant. “I often reacted with self-righteousness, petulance, anger. On some level I knew my reaction was toxic, counterproductive, but I couldn’t stop myself,” he would later write in his memoir, Shoe Dog. He pointed out that his company didn’t own the factories, that he’d worked with the owners to improve conditions and that the stories, as gruesome as they were, were exceptions.

The simple truth is that change rarely, if ever, starts at the top because it is people with power that create the status quo. They are attached to what they’ve built and take pride in their accomplishments, just like the rest of us. That’s why, to bring about genuine change — change that lasts — you need to mobilize people to influence institutions (or those, like Knight, who yield institutional power).

Eventually, that’s what happened at Nike. The protests took their toll. “We had to admit,” Knight remembered, “We could do better.” Going beyond its own factories, the company established the Fair Trade Labor Association and published a comprehensive report of its own factories. Today, the company’s track record may not be perfect, but it’s become more a part of the solution than a part of the problem.

Change Is Never Top-Down Or Bottom-Up

At a pivotal moment during the height of the civil rights movement, Robert Kennedy, Attorney General of the United States and brother to the President, would turn to the activist John Lewis and say, “’John, the people, the young people of the SNCC, have educated me. You have changed me. Now I understand.”

Lewis, just a young kid in his twenties at the time, was himself the product of webs of influence. He was shaped by mentors like Jim Lawson and Keller Miller Smith, as well as by peers such as Diane Nash, Bernard Lafayette and James Bevel. They, in turn, influenced others to get out, protest and shape the minds of people like Robert Kennedy.

As I explain in Cascades, transformation isn’t top-down or bottom-up, but happens from side-to-side. You can find the entire spectrum — from active support to active resistance — at every level. The answer doesn’t lie in any specific strategy or initiative, but in how people are able to internalize the need for change and transfer ideas through social bonds.

Change never happens all at once and can’t simply be willed into existence. The best way to do that is to empower those who already believe in change to bring in those around them. That’s what’s key to successful transformations. A leader’s role is not to plan and direct action, but to inspire and empower belief.

— Article courtesy of the Digital Tonto blog
— Image credit: Unsplash

Sign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.