Category Archives: Innovation

Moral Uncertainty Engines

Leave a reply

Designing Systems That Know They Might Be Wrong

LAST UPDATED: March 6, 2026 at 5:07 PM

Moral Uncertainty Engines

GUEST POST from Art Inteligencia

I. Introduction: The Next Frontier in Responsible Innovation

As artificial intelligence and algorithmic systems take on increasingly consequential roles in our organizations and societies, a new challenge is emerging. The most dangerous systems are not necessarily the ones that make mistakes. The most dangerous systems are the ones that operate with complete confidence that they are right.

Innovation has always involved uncertainty. But when technology begins influencing decisions about hiring, healthcare, financial access, mobility, and public policy, uncertainty is no longer just a business risk—it becomes a moral one.

This is where a new concept begins to take shape: Moral Uncertainty Engines.

A Moral Uncertainty Engine is a decision architecture designed to recognize that ethical clarity is often elusive. Instead of embedding a single moral framework into a system, these engines evaluate decisions through multiple ethical lenses, quantify disagreements between them, and surface those tensions for human oversight.

In other words, they are systems designed not just to make decisions, but to acknowledge when the ethical landscape is ambiguous.

This represents a profound shift in how we design intelligent systems. For decades, the goal of technology was optimization—finding the single best answer. But the reality of human values is messier. What maximizes efficiency may conflict with fairness. What benefits the majority may harm the vulnerable. What is legal may not always be ethical.

Moral Uncertainty Engines do not attempt to eliminate these tensions. Instead, they illuminate them.

In doing so, they create the possibility for organizations to move beyond simplistic “ethical AI” checklists toward something far more powerful: systems that actively help leaders navigate complex moral tradeoffs.

Because the future of responsible innovation will not belong to the organizations that claim to have solved ethics. It will belong to the ones humble enough to admit they haven’t—and wise enough to design systems that help them think through it anyway.

II. What Is a Moral Uncertainty Engine?

Before we can explore the potential of Moral Uncertainty Engines, we need a clear understanding of what they are and why they matter. At their core, Moral Uncertainty Engines are decision-support systems designed to recognize that ethical certainty is often an illusion.

Traditional algorithms are built to optimize for a defined objective—maximize profit, minimize cost, increase efficiency, or predict outcomes with the highest statistical accuracy. But real-world decisions rarely involve just one objective. They involve competing values, conflicting priorities, and ethical tradeoffs that cannot always be resolved with a single formula.

A Moral Uncertainty Engine is a system designed to evaluate decisions through multiple ethical frameworks simultaneously and to acknowledge when those frameworks disagree.

Instead of embedding a single moral rule set into a system, these engines assess potential actions across different ethical perspectives and quantify the level of uncertainty or conflict between them. The result is not necessarily a single definitive answer, but a clearer picture of the ethical terrain surrounding a decision.

In practice, a Moral Uncertainty Engine typically performs several key functions:

  • Multi-framework evaluation – analyzing decisions through several ethical lenses rather than relying on a single rule set.
  • Ethical tradeoff analysis – identifying where different value systems produce conflicting recommendations.
  • Uncertainty scoring – measuring how confident the system can be in a morally acceptable course of action.
  • Transparency and explanation – making visible the reasoning behind recommendations.
  • Human escalation triggers – flagging decisions where ethical disagreement is high and human judgment is required.

To understand how this works, consider the most common ethical frameworks used in moral reasoning. A Moral Uncertainty Engine might evaluate a decision using several of these simultaneously:

  • Utilitarianism – Which option produces the greatest overall good?
  • Rights-based ethics – Does the decision violate fundamental rights?
  • Justice and fairness – Are harms and benefits distributed equitably?
  • Care ethics – How does the decision affect the most vulnerable stakeholders?

When these frameworks align, the system can move forward with confidence. But when they conflict—as they often do—the engine highlights the disagreement and surfaces the ethical tension instead of burying it.

This is the key insight behind Moral Uncertainty Engines: ethical complexity should not be hidden inside algorithms. It should be surfaced, measured, and navigated deliberately.

In many ways, these systems represent the next step in the evolution of responsible innovation. Rather than pretending that technology can eliminate moral ambiguity, they acknowledge that ambiguity is part of the landscape—and they help leaders make better decisions within it.

III. Why Moral Uncertainty Matters Now

The concept of Moral Uncertainty Engines might sound theoretical at first, but the forces making them necessary are already here. As organizations deploy increasingly autonomous technologies and algorithmic decision systems, they are encountering ethical dilemmas at a scale and speed that traditional governance structures were never designed to handle.

In the past, ethical decisions were typically made by humans, often slowly and with room for debate. Today, many of those same decisions are being influenced—or outright determined—by automated systems operating in milliseconds.

That shift creates a fundamental challenge: machines are excellent at optimizing defined objectives, but they struggle when the objectives themselves are morally contested.

AI Systems Are Increasingly Making Moral Decisions

Consider how many domains already rely on algorithmic decision-making:

  • Autonomous vehicles determining how to react in unavoidable accident scenarios
  • Healthcare systems prioritizing patients for scarce treatments
  • Hiring algorithms screening job candidates
  • Financial models determining who receives loans or credit
  • Content moderation systems deciding what speech is allowed online

Each of these systems contains embedded value judgments—whether explicitly designed or not. The problem is that most organizations treat these judgments as technical questions rather than ethical ones.

There Is No Universal Ethical Consensus

Humans themselves rarely agree on the “correct” moral answer in complex situations. Different cultures, organizations, and individuals prioritize different values. Some emphasize maximizing overall benefit, while others prioritize protecting individual rights or safeguarding vulnerable populations.

When technology is designed around a single ethical assumption, it risks imposing that value system invisibly and at scale.

Moral Uncertainty Engines acknowledge this reality by recognizing that ethical frameworks often produce conflicting recommendations. Instead of pretending consensus exists, they surface the disagreement so that organizations can navigate it deliberately.

The Risk of Moral Overconfidence

Perhaps the greatest danger in modern algorithmic systems is not error—it is overconfidence. Many AI systems produce outputs that appear authoritative, even when the underlying ethical reasoning is incomplete, biased, or based on questionable assumptions.

This can create what might be called moral automation bias, where humans defer to algorithmic recommendations simply because they appear objective or mathematically grounded.

Moral Uncertainty Engines introduce a critical counterbalance: they explicitly communicate when a decision is ethically ambiguous, contested, or uncertain.

The Innovation Opportunity

Organizations that learn how to operationalize moral uncertainty will gain an important advantage. They will be better equipped to:

  • Build trust with customers and stakeholders
  • Navigate regulatory scrutiny
  • Avoid reputational crises driven by opaque algorithms
  • Make more resilient long-term decisions

In other words, acknowledging ethical uncertainty is not a weakness. It is a capability—one that responsible innovators will increasingly need as technology becomes more powerful and more deeply embedded in human lives.

IV. How Moral Uncertainty Engines Work

To understand the potential of Moral Uncertainty Engines, it helps to look at how such a system might actually function in practice. While the concept is still emerging, the underlying architecture draws from fields like decision science, AI safety, machine ethics, and risk management.

At a high level, a Moral Uncertainty Engine acts as a layered decision-support system. Rather than producing a single optimized answer, it evaluates potential actions through multiple ethical perspectives and identifies where those perspectives align—or conflict.

A simplified architecture typically includes four key layers.

Layer 1: Situation Awareness

Every ethical decision begins with context. The system first gathers relevant information about the situation, including:

  • The stakeholders involved
  • The potential consequences of different actions
  • Legal or regulatory constraints
  • The scale and reversibility of potential harm

This layer ensures that the system understands the environment in which a decision is being made before attempting to evaluate its ethical implications.

Layer 2: Ethical Framework Evaluation

Next, the system analyzes the possible courses of action through multiple ethical frameworks. Each framework evaluates the decision according to its own principles and priorities.

For example:

  • Utilitarian perspective: Which option produces the greatest overall benefit?
  • Rights-based perspective: Does any option violate fundamental rights?
  • Justice perspective: Are harms and benefits distributed fairly?
  • Care perspective: How are vulnerable stakeholders affected?

Each framework generates its own assessment of the available choices.

Layer 3: Moral Aggregation

Once the frameworks have evaluated the options, the system compares their recommendations. In some cases, the frameworks may converge on a similar outcome. In others, they may strongly disagree.

Several approaches can be used to combine these evaluations, including weighted voting models, scenario simulations, or expected moral value calculations. The goal is not necessarily to produce a single definitive answer, but to understand the balance of ethical considerations across the frameworks.

Layer 4: Uncertainty and Escalation

The final layer measures how much disagreement exists between the ethical perspectives. If the frameworks align strongly, the system may proceed with a recommendation. If they diverge significantly, the system can flag the decision as ethically uncertain.

At this point, several actions may occur:

  • The system provides an explanation of the ethical tradeoffs
  • A confidence or uncertainty score is generated
  • The decision is escalated to human oversight

This is the core value of a Moral Uncertainty Engine. Instead of hiding ethical tension behind an optimized output, it reveals the complexity of the decision and invites human judgment where it matters most.

In many ways, these systems function less like automated decision-makers and more like ethical copilots—tools that help organizations think more clearly about the moral consequences of their choices.

V. Case Study: Autonomous Vehicles and the Trolley Problem

Few examples illustrate the challenge of moral uncertainty more clearly than autonomous vehicles. When self-driving systems operate on public roads, they must continuously make decisions that involve safety tradeoffs. Most of the time these choices are routine—slow down, change lanes, maintain distance. But in rare circumstances, a vehicle may face an unavoidable accident scenario where harm cannot be completely prevented.

These moments resemble the classic ethical thought experiment known as the “trolley problem,” where a decision must be made between two outcomes, each involving some form of harm. While philosophers have debated such scenarios for decades, autonomous vehicle developers must translate those debates into operational decisions inside real-world systems.

The difficulty is that different ethical frameworks often produce different answers. A strictly utilitarian approach might prioritize minimizing total casualties. A rights-based perspective might argue that intentionally choosing to harm one person to save others violates fundamental moral principles. A fairness perspective might question whether certain groups are systematically placed at greater risk.

Many early attempts to address these questions focused on encoding a single rule or priority structure into the vehicle’s decision logic. But this approach assumes that there is one universally acceptable ethical answer—an assumption that rarely holds across cultures, legal systems, or public opinion.

A Moral Uncertainty Engine offers a different approach. Instead of hard-coding a single moral rule, the system evaluates potential actions across multiple ethical frameworks and identifies where they agree and where they conflict.

For example, the system might:

  • Analyze the scenario from a utilitarian perspective focused on minimizing total harm
  • Evaluate whether any potential action violates protected rights
  • Assess whether the risks are being distributed fairly among stakeholders

If these frameworks converge on the same outcome, the system can act with greater confidence. If they diverge significantly, the vehicle may default to a predefined safety posture—such as minimizing speed and impact energy—rather than making an ethically aggressive tradeoff.

More importantly, the decision framework itself becomes transparent and auditable. Engineers, regulators, and the public can examine how ethical considerations were evaluated rather than treating the system as a black box.

The lesson from autonomous vehicles extends far beyond transportation. As technology becomes increasingly embedded in complex human environments, organizations will need systems that can recognize ethical tension instead of pretending it doesn’t exist.

Moral Uncertainty Engines provide a path toward that future—one where intelligent systems are designed not only to act, but to reflect the moral complexity of the world they operate within.

VI. Case Study: AI Medical Triage and the Ethics of Scarcity

Healthcare provides one of the most powerful real-world examples of why moral uncertainty matters. Medical systems regularly face situations where resources are limited and difficult prioritization decisions must be made. During public health crises, such as pandemics, these tradeoffs can become especially stark.

Hospitals may need to decide how to allocate ventilators, ICU beds, specialized treatments, or transplant organs when demand exceeds supply. Historically, these decisions have been guided by medical ethics boards, physician judgment, and carefully developed triage protocols. Increasingly, however, algorithmic systems are being introduced to help manage these decisions at scale.

Many triage algorithms are designed to optimize measurable outcomes such as survival probability or expected life-years saved. While these metrics may appear objective, they can create serious ethical tensions when translated into real-world policy.

For example, prioritizing expected life-years may unintentionally disadvantage older patients. Models that rely heavily on historical health data may penalize individuals from underserved communities who have historically received less access to preventative care. Systems designed purely around statistical survival probabilities may overlook broader ethical considerations about fairness, dignity, or social vulnerability.

This is precisely the kind of scenario where a Moral Uncertainty Engine could provide meaningful support.

Instead of optimizing for a single metric, the system evaluates triage decisions through several ethical perspectives simultaneously. A utilitarian framework may prioritize maximizing the number of lives saved. A justice-based framework may emphasize equitable access across demographic groups. A care-based framework may highlight the needs of the most vulnerable patients.

When these perspectives align, the system can offer a strong recommendation. But when they conflict—as they often do in healthcare—the engine surfaces that conflict rather than hiding it behind a numerical score.

The result is not an automated moral verdict. Instead, clinicians and ethics boards receive a clearer picture of the ethical tradeoffs embedded in each decision. The system may present alternative allocation scenarios, highlight potential bias risks, or flag cases that require human deliberation.

In this way, the technology functions less as a replacement for human judgment and more as a decision companion. It expands the visibility of ethical consequences while preserving the role of human responsibility.

Healthcare leaders already recognize that medical decisions involve more than statistics. Moral Uncertainty Engines simply help bring that ethical complexity into the design of the systems that increasingly shape those decisions.

VII. Leading Companies and Startups Exploring Moral Uncertainty

Moral Uncertainty Engines are still an emerging concept, but the foundational components of this category are already being developed across the technology ecosystem. Large technology firms, AI safety organizations, governance platforms, and startups focused on responsible AI are all contributing pieces of what could eventually become full ethical decision infrastructures.

While few organizations are explicitly using the term “Moral Uncertainty Engine,” many are working on the critical building blocks: AI alignment systems, ethical reasoning frameworks, transparency tools, and governance platforms designed to ensure responsible decision-making.

Large Technology Companies

Several major technology companies are investing heavily in AI alignment and responsible innovation. Their research programs are exploring ways to ensure that increasingly autonomous systems operate within acceptable ethical boundaries.

  • OpenAI – Research into alignment methods such as reinforcement learning from human feedback and systems designed to incorporate human values into AI behavior.
  • Google DeepMind – Work on AI safety, scalable oversight, and constitutional approaches to guiding model behavior.
  • Microsoft – Development of responsible AI frameworks, governance tools, and organizational guidelines for ethical AI deployment.

These companies are helping to define the infrastructure that future ethical decision systems will rely upon.

Emerging Startups

A growing number of startups are focusing specifically on governance, auditing, and ethical oversight for AI systems. These organizations are building platforms that help companies monitor algorithmic behavior, detect bias, and ensure compliance with evolving regulatory standards.

  • Credo AI – Provides governance platforms designed to help organizations operationalize responsible AI practices.
  • Holistic AI – Offers tools for auditing AI systems, identifying bias, and evaluating risk across machine learning models.
  • CIRIS – Focuses on runtime governance layers designed to help organizations manage the behavior of AI agents in production environments.

These companies are not yet full Moral Uncertainty Engines, but they are building the monitoring and governance layers that such systems will likely require.

Academic and Research Institutions

Some of the most important advances in machine ethics and moral decision systems are emerging from research institutions exploring how ethical reasoning can be integrated into AI architectures.

  • Stanford Human-Centered AI
  • MIT Media Lab
  • Oxford’s AI safety and governance research community

Researchers in these communities are experimenting with methods for translating ethical theory into operational systems capable of evaluating tradeoffs, measuring moral uncertainty, and providing transparent reasoning.

Taken together, these organizations represent the early ecosystem surrounding what could become one of the most important innovation categories of the next decade: technologies designed not just to make decisions, but to help society navigate the moral complexity that accompanies them.

VIII. The Innovation Opportunities

If Moral Uncertainty Engines sound like a niche academic concept today, history suggests that may not remain the case for long. Many of the most important innovation categories begin as abstract ideas before evolving into entire industries. Cloud computing, cybersecurity, and digital trust platforms all followed similar paths.

As AI systems become more deeply embedded in critical decisions, the ability to surface ethical tradeoffs and navigate moral uncertainty will become an increasingly valuable capability. This opens the door to several new innovation opportunities for entrepreneurs, technology companies, and forward-looking organizations.

Ethical Infrastructure Platforms

One opportunity lies in the creation of ethical infrastructure platforms—systems designed to plug into existing AI models and decision engines to provide moral evaluation layers. These platforms could function much like security software or monitoring tools, continuously assessing algorithmic behavior and flagging ethical risks.

Capabilities in this category might include:

  • Multi-framework ethical scoring for algorithmic decisions
  • Real-time bias detection and mitigation
  • Transparency dashboards for regulators and stakeholders
  • Ethical risk monitoring across large AI deployments

In effect, these platforms would provide the ethical equivalent of observability tools used in modern software systems.

Organizational Decision Copilots

Another opportunity lies in decision-support tools designed specifically for human leaders. Instead of automating decisions, these systems would act as ethical copilots—helping executives, policymakers, and product teams evaluate complex tradeoffs before implementing new technologies or policies.

Such tools might help organizations:

  • Simulate the ethical consequences of product features
  • Evaluate policy choices across competing value systems
  • Identify stakeholder groups most likely to be affected by a decision
  • Stress-test innovations against potential ethical controversies

In this model, the goal is not to replace human judgment, but to strengthen it with better visibility into ethical complexity.

Ethical Digital Twins

A particularly intriguing possibility is the development of ethical digital twins—simulation environments where organizations can test how different decisions might impact stakeholders across multiple ethical frameworks before deploying them in the real world.

Just as engineers use digital twins to simulate the performance of physical systems, leaders could use ethical simulation environments to anticipate unintended consequences, reputational risks, or fairness concerns before they emerge.

The Birth of a New Category

If these opportunities mature, Moral Uncertainty Engines could become the foundation for a new category of enterprise technology focused on ethical intelligence. Organizations would no longer rely solely on legal compliance or reactive crisis management to address ethical challenges. Instead, they would have systems designed to help them navigate those challenges proactively.

In a world where innovation increasingly shapes society at scale, the ability to operationalize ethical awareness may become just as important as the ability to write code or analyze data.

IX. The Risks and Criticisms of Moral Uncertainty Engines

Like any emerging technology category, Moral Uncertainty Engines bring both promise and potential pitfalls. While these systems could help organizations navigate complex ethical terrain more thoughtfully, they also raise legitimate concerns about how moral reasoning is translated into software and who ultimately holds responsibility for the outcomes.

If organizations are not careful, the very tools designed to improve ethical decision-making could inadvertently create new forms of risk.

The Danger of Moral Outsourcing

One of the most common criticisms is the risk of moral outsourcing. When organizations rely too heavily on algorithmic systems to evaluate ethical decisions, leaders may begin to treat those systems as final authorities rather than decision-support tools.

This can create a dangerous dynamic where responsibility quietly shifts from humans to algorithms. Instead of asking whether a decision is morally defensible, leaders may simply ask whether the system approved it.

Moral Uncertainty Engines should never replace human judgment. Their purpose is to illuminate ethical tradeoffs—not to absolve decision-makers of responsibility.

The Illusion of Objectivity

Another concern is the possibility that ethical scoring systems may create a false sense of precision. Numbers, dashboards, and scores can make complex moral questions appear more objective than they actually are.

But ethical frameworks themselves contain assumptions and value judgments. The choice of which frameworks to include, how they are weighted, and how outcomes are interpreted can all influence the system’s conclusions.

Without transparency, these embedded assumptions may go unnoticed by the people relying on the system.

Cultural and Societal Bias

Ethics is deeply shaped by culture, history, and social context. A system designed around one set of moral priorities may not reflect the values of another community or region.

If Moral Uncertainty Engines are built primarily by a narrow set of organizations or cultural perspectives, they could unintentionally export those values into systems used around the world.

Designing these systems responsibly will require diverse input from ethicists, policymakers, technologists, and communities affected by the decisions being modeled.

The Complexity Challenge

Finally, there is a practical challenge: ethical reasoning is incredibly complex. Translating philosophical frameworks into computational systems is difficult, and oversimplification is always a risk.

Not every moral dilemma can be captured in a model, and not every ethical conflict can be resolved through structured analysis.

Recognizing these limitations is essential. The goal of Moral Uncertainty Engines should not be to mechanize morality, but to provide better tools for navigating difficult decisions.

If designed thoughtfully, these systems can serve as valuable companions to human judgment. But if treated as definitive authorities, they risk becoming yet another example of technology that promises clarity while quietly obscuring the deeper questions that matter most.

X. The Leadership Imperative

The rise of Moral Uncertainty Engines underscores a critical lesson for leaders: technology alone cannot solve ethical complexity. Organizations that rely on automated systems to make moral decisions without human oversight risk both moral and reputational failure.

Leaders must approach these tools as companions rather than replacements—systems designed to illuminate ethical tradeoffs, measure uncertainty, and support thoughtful deliberation.

Key Principles for Responsible Leadership

  • Accountability: Leaders retain ultimate responsibility for decisions, even when supported by Moral Uncertainty Engines.
  • Transparency: Ensure that the reasoning behind system recommendations is visible, understandable, and auditable by humans.
  • Human Oversight: Use automated insights as decision-support, not as authoritative directives. Escalate ethically ambiguous scenarios to human judgment.
  • Ethical Culture: Encourage organizational practices that prioritize ethical reflection alongside operational efficiency and innovation.
  • Diversity of Perspectives: Incorporate insights from ethicists, technologists, and stakeholders representing different communities and cultural contexts.

Moral Uncertainty Engines are powerful because they make ethical ambiguity visible. But the value of that visibility depends entirely on the people interpreting it. Leaders who are willing to engage with these systems thoughtfully—questioning assumptions, evaluating tradeoffs, and embracing uncertainty—will turn ethical complexity into a strategic advantage.

In short, the technology alone does not create ethical outcomes. It is the combination of human judgment, responsible leadership, and machine-supported insight that allows organizations to navigate moral uncertainty successfully.

XI. Conclusion: Designing Systems That Know Their Limits

Moral Uncertainty Engines represent a profound shift in how we think about technology and ethics. They are not designed to replace human judgment, nor to provide definitive moral answers. Instead, they offer a framework for surfacing ethical tradeoffs, quantifying uncertainty, and supporting deliberate decision-making in complex contexts.

The systems of the future will need to balance intelligence with humility. They must optimize for outcomes while acknowledging the moral ambiguity inherent in most consequential decisions. By doing so, they create space for leaders, teams, and organizations to reflect, deliberate, and choose responsibly.

Across industries—from autonomous vehicles to healthcare triage, from hiring algorithms to public policy—ethical complexity is unavoidable. Moral Uncertainty Engines give organizations the tools to confront that complexity openly rather than hiding it behind optimization metrics or opaque algorithms.

In practice, these engines act as ethical copilots. They illuminate areas of tension, highlight disagreements between frameworks, and provide decision-makers with richer, more nuanced insights. The true measure of their success is not perfect moral accuracy, but the degree to which they enable human leaders to make informed, accountable, and ethically aware decisions.

Ultimately, the organizations that thrive in an increasingly automated and interconnected world will be those that design systems capable of acknowledging their limits—and that pair those systems with leaders willing to navigate uncertainty thoughtfully. In this way, Moral Uncertainty Engines may become one of the most important tools for fostering responsible innovation in the 21st century.

Frequently Asked Questions

1. What is a Moral Uncertainty Engine?

A Moral Uncertainty Engine is a decision-support system designed to evaluate choices through multiple ethical frameworks, quantify areas of disagreement, and provide transparent guidance or escalation when ethical uncertainty is high. Its purpose is to help organizations navigate complex moral tradeoffs rather than replace human judgment.

2. Why are Moral Uncertainty Engines important today?

As AI and algorithmic systems increasingly make decisions that affect people’s lives, the ability to surface and manage ethical uncertainty becomes critical. These engines reduce risks of overconfidence, bias, and hidden ethical assumptions, enabling organizations to make more responsible, accountable, and trusted decisions.

3. Which industries or applications can benefit from Moral Uncertainty Engines?

Any sector where complex decisions with moral implications are made can benefit, including healthcare triage, autonomous vehicles, hiring and HR systems, financial services, content moderation, and public policy. Essentially, any domain where decisions have significant ethical consequences can leverage these systems to guide thoughtful human oversight.

Disclaimer: This article speculates on the potential future applications of cutting-edge scientific research. While based on current scientific understanding, the practical realization of these concepts may vary in timeline and feasibility and are subject to ongoing research and development.

Image credits: Google Gemini

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

Do You Have an Empty Tank?

Leave a reply

Do You Have an Empty Tank?

GUEST POST from Mike Shipulski

Sometimes your energy level runs low. That’s not a bad thing, it’s just how things go. Just like a car’s gas tank runs low, our gas tanks, both physical and emotional, also need filling. Again, not a bad thing. That’s what gas tanks are for – they hold the fuel.

We’re pretty good at remembering that a car’s tank is finite. At the start of the morning commute, the car’s fuel gauge gives a clear reading of the fuel level and we do the calculation to determine if we can make it or we need to stop for fuel. And we do the same thing in the evening – look at the gauge, determine if we need fuel and act accordingly. Rarely we run the car out of fuel because the car continuously monitors and displays the fuel level and we know there are consequences if we run out of fuel.

We’re not so good at remembering our personal tanks are finite. At the start of the day, there are no objective fuel gauges to display our internal fuel levels. The only calculation we make – if we can make it out of bed we have enough fuel for the day. We need to do better than that.

Our bodies do have fuel gages of sorts. When our fuel is low we can be irritable, we can have poor concentration, we can be easily distracted. Though these gages are challenging to see and difficult to interpret, they can be used effectively if we slow down and be in our bodies. The most troubling part has nothing to do with our internal fuel gages. Most troubling is we fail to respect their low fuel warnings even when we do recognize them. It’s like we don’t acknowledge our tanks are finite.

We don’t think our cars are flawed because their fuel tanks run low as we drive. Yet, we see the finite nature of our internal fuel tanks as a sign of weakness. Why is that? Rationally, we know all fuel tanks are finite and their fuel level drops with activity. But, in the moment, when are tanks are low, we think something is wrong with us, we think we’re not whole, we think less of ourselves.

When your tank is low, don’t curse, don’t blame, don’t feel sorry and don’t judge. It’s okay. That’s what tanks do.

A simple rule for all empty tanks – put fuel in them.

Image credit: Pixabay

Subscribe to Human-Centered Change & Innovation WeeklySign 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:

  1. Did we run contact-backed prompts — not only desk research and generated personas?
  2. Can we state the job in their words — as a verb phrase, not a feature cluster?
  3. What workarounds are we competing with — including the ugly internal ones?
  4. What anxieties and dignity costs are in scope — with recovery designed in?
  5. 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

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.

Subscribe to Human-Centered Change & Innovation WeeklySign 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

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:

  1. Are we designing only for today’s customers, or tomorrow’s realities?
    This question tests whether your innovation anticipates future needs and scenarios.
  2. 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.
  3. 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.

Subscribe to Human-Centered Change & Innovation WeeklySign 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 2026Drum 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:

  1. Three Myths That Kill Change and Transformation — by Greg Satell
  2. Why a Customer Experience Audit is Non-Negotiable in 2026 — by Braden Kelley
  3. Innovation Lessons from the 50 Most Admired Companies of 2026 — by Braden Kelley
  4. Is Your Customer Experience a Lie? — by Braden Kelley
  5. Important or Urgent? — by Stefan Lindegaard
  6. The Greatest Inventor You’ve Never Heard of — by John Bessant
  7. 5 Simple Keys to Becoming a Powerful Communicator — by Greg Satell
  8. Do You Have What It Takes to be a Visionary? — Exclusive Interview with Mark C. Winters
  9. Temporal Agency – How Innovators Stop Time from Bullying Them — by Art Inteligencia
  10. 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:

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!

Build a Common Language of Innovation on your team

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:

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

Has AI Killed Design Thinking?

Leave a reply

Or Just Removed Its Excuses?

LAST UPDATED: March 2, 2026 at 5:13 PM

Has AI Killed Design Thinking?

by Braden Kelley and Art Inteligencia

I. The Question Everyone Is Whispering

Something fundamental has changed in how products are created.

Artificial intelligence can now generate working software in minutes. Designers can move from an idea to a functional prototype without waiting for engineering. Engineers can generate interface concepts, user flows, and even early product ideas with a few well-crafted prompts.

The traditional product development cycle — design, then build, then test — is collapsing into something faster, messier, and far more fluid.

In the past, the biggest constraint in innovation was the cost and time required to build something. Today, AI dramatically reduces that barrier. Entire features, experiments, and even applications can be created almost instantly.

Which raises an uncomfortable question that many product leaders, designers, and engineers are quietly asking:

If we can ship almost immediately, do we still need design thinking?

At first glance, the answer might seem obvious. Design thinking was created to help teams understand people, define the right problems, and avoid building the wrong solutions. Those goals have not disappeared.

But when the cost of building approaches zero, the role of design inevitably changes. The traditional pacing of discovery, ideation, prototyping, and testing begins to compress. The boundaries between designer and engineer begin to blur.

And as those boundaries dissolve, the question is no longer simply whether design thinking still matters.

The deeper question is whether the discipline itself must evolve to survive in a world where almost anyone can turn an idea into working software.

II. Design Thinking Was Built for a World of Scarcity

To understand how artificial intelligence is reshaping product creation, it helps to remember the environment in which design thinking originally emerged.

Design thinking did not appear because organizations suddenly discovered empathy or creativity. It emerged because building things was expensive, slow, and risky. Every product decision carried significant cost, and mistakes could take months or years to correct.

In that world, organizations needed a structured way to reduce uncertainty before committing engineering resources. Design thinking provided that structure.

Its now-famous stages helped teams move deliberately from understanding people to building solutions:

  • Empathize — deeply understand the people you are designing for.
  • Define — frame the real problem worth solving.
  • Ideate — generate a wide range of possible solutions.
  • Prototype — create rough representations of potential ideas.
  • Test — validate whether those ideas actually work for people.

The goal was simple: avoid spending months building something no one actually needed.

Design thinking slowed teams down in the right places so they could move faster later. It created space for exploration before the heavy machinery of engineering was set in motion.

But this entire framework assumed one critical constraint:

Building was the most expensive part of innovation.

Prototypes were often static mockups. Experiments required engineering time. Even small product changes could take weeks or months to ship.

In other words, design thinking was optimized for a world where the biggest risk was building the wrong thing.

Today, AI is rapidly changing that assumption. When working software can be generated in minutes rather than months, the bottleneck shifts — and the role of design must evolve with it.

III. AI Has Flipped the Innovation Constraint

For most of the history of digital product development, the limiting factor in innovation was the ability to build. Even the best ideas had to wait in line for scarce engineering resources, long development cycles, and complex release processes.

Artificial intelligence is rapidly dismantling that constraint.

Today, AI tools can generate functional code, working interfaces, and interactive prototypes in minutes. What once required a team of specialists and weeks of effort can often be produced by a single individual in an afternoon.

Designers can now:

  • Create interactive prototypes that behave like real products
  • Generate front-end code directly from design concepts
  • Rapidly explore multiple product directions

Engineers can now:

  • Generate user interfaces and layouts
  • Experiment with product concepts before committing to full builds
  • Quickly iterate on product experiences

The barrier between idea and implementation is shrinking dramatically.

As a result, the core constraint in innovation is no longer the ability to build something. The new constraint is the ability to decide what should actually be built.

When creation becomes cheap, judgment becomes the scarce resource.

Organizations can now generate more ideas, features, and experiments than they have the capacity to evaluate thoughtfully. The risk is no longer simply building the wrong thing slowly.

The risk is building thousands of things quickly without enough clarity about which ones actually matter.

This shift fundamentally changes the role of design. Instead of primarily helping teams avoid costly mistakes in development, design increasingly becomes the discipline that helps organizations navigate overwhelming possibility.

IV. The Blurring of Roles: Designers Reach Forward, Engineers Reach Back

One of the most profound effects of AI in product development is the erosion of traditional professional boundaries.

For decades, the technology industry operated with relatively clear separations of responsibility. Designers focused on user needs, interaction models, and visual systems. Engineers translated those designs into working software. Product managers coordinated priorities and timelines between the two.

That structure was largely a reflection of technical limitations. Designing and building required specialized tools, knowledge, and workflows that made cross-disciplinary work difficult.

AI is rapidly dissolving those barriers.

Designers can now reach forward into the domain that once belonged exclusively to engineering. With AI-assisted tools, they can generate working interfaces, produce front-end code, and simulate complex user interactions without waiting for implementation.

At the same time, engineers can reach backward into design. AI systems can help them generate layouts, propose interface structures, and explore experience flows that once required specialized design expertise.

The result is a new kind of creative overlap:

  • Designers who can prototype in code
  • Engineers who can explore experience design
  • Product creators who move fluidly between disciplines

The traditional model of work moving through a linear chain — research to design to engineering — begins to give way to a far more integrated creative process.

The future product creator is not defined by a job title, but by the ability to move fluidly between understanding problems and building solutions.

This does not mean design expertise or engineering skill become less important. If anything, the opposite is true. As tools make it easier for everyone to participate in creation, the depth of real craft becomes more visible and more valuable.

But it does mean the rigid boundaries between “designer” and “builder” are beginning to dissolve, creating a new generation of hybrid creators who can move seamlessly between imagining, designing, and shipping experiences.

V. The Death of the Handoff

For decades, most product development operated like a relay race. Work moved from one team to the next through a series of formal handoffs.

Researchers gathered insights and passed them to designers. Designers created wireframes and mockups that were handed to engineering. Engineers translated those designs into working software and eventually passed the finished product to testing and operations.

Each transition introduced delays, misinterpretations, and loss of context. The original understanding of the problem often became diluted as it traveled through the system.

Artificial intelligence is accelerating the collapse of this model.

When individuals can move rapidly from idea to prototype to functional product, the need for rigid handoffs begins to disappear. A single person can now:

  • Explore a user problem
  • Design a potential solution
  • Generate working code
  • Launch an experiment

Instead of waiting for work to pass from one discipline to another, creators can stay connected to the entire lifecycle of an idea.

The distance between insight and implementation is shrinking.

This shift has profound implications for how innovation happens inside organizations. Instead of large teams coordinating complex handoffs, smaller groups — or even individuals — can rapidly test ideas and learn from real-world feedback.

Product development begins to look less like an industrial assembly line and more like a creative studio, where ideas are explored, built, and refined continuously.

The most effective teams in this environment will not simply move faster. They will maintain ownership of ideas from the moment a problem is discovered all the way through to the moment a solution is experienced by real people.

VI. What AI Actually Kills

Artificial intelligence is not killing design thinking.

What it is killing are many of the habits that organizations adopted in the name of design thinking but that were never truly about understanding people or solving meaningful problems.

For years, some teams have mistaken the appearance of innovation for the practice of it. Workshops replaced experiments. Sticky notes replaced decisions. Slide decks replaced prototypes.

When building was slow and expensive, these behaviors were often tolerated because teams needed time to align before committing resources. But in a world where working solutions can be generated almost instantly, those habits quickly become friction.

AI removes the excuses that allowed these patterns to persist.

Process Theater

Innovation workshops that generate energy but not outcomes become difficult to justify when teams can build and test ideas immediately.

Endless Ideation

Brainstorming sessions that produce dozens of ideas without committing to experiments lose their value when ideas can be rapidly turned into prototypes and evaluated in the real world.

Documentation Instead of Exploration

Detailed reports, long strategy decks, and static artifacts once helped communicate ideas across teams. But when AI allows concepts to be expressed through working experiences, documentation becomes less important than experimentation.

Safe Innovation

Perhaps most importantly, AI challenges organizations that use process as a shield against risk. When it becomes easy to test bold ideas quickly and cheaply, avoiding experimentation becomes a choice rather than a necessity.

AI doesn’t eliminate design thinking. It eliminates the distance between thinking and doing.

The organizations that thrive in this environment will not be the ones with the most polished innovation processes. They will be the ones that are most willing to replace discussion with discovery and ideas with experiments.

Has AI Killed Design Thinking Infographic

VII. The New Role of Design: Decision Velocity

When the cost of building drops dramatically, the nature of competitive advantage changes.

In the past, organizations succeeded by efficiently transforming ideas into products. Engineering capacity, technical expertise, and operational discipline were often the primary constraints.

But when AI can generate working software, prototypes, and experiments almost instantly, the challenge is no longer how quickly something can be built.

The challenge becomes how quickly and wisely teams can decide what is actually worth building.

In an AI-driven world, innovation speed is no longer about development velocity — it is about decision velocity.

This is where the role of design evolves.

Design shifts from primarily producing artifacts — wireframes, mockups, and prototypes — to guiding the choices that shape meaningful innovation.

Designers increasingly become the people who help teams:

  • Frame the right problems to solve
  • Clarify human needs and motivations
  • Prioritize which ideas deserve experimentation
  • Interpret signals from real-world user behavior

In other words, design becomes less about shaping the interface of a product and more about shaping the direction of learning.

When organizations can generate thousands of potential solutions, the real value lies in identifying the small number that actually create meaningful value for people.

Designers, at their best, help organizations navigate that complexity. They connect technology to human context, helping teams avoid the trap of building faster without thinking better.

In the AI era, design is not slowing innovation down. It is helping organizations move quickly without losing their sense of where they should be going.

VIII. From Design Thinking to Design Doing

As artificial intelligence compresses the distance between idea and implementation, the nature of design practice begins to change. The emphasis shifts away from structured stages and toward continuous experimentation.

Traditional design thinking frameworks helped teams organize their thinking before committing to build. But in an AI-enabled environment, building itself becomes part of the thinking process.

Instead of long cycles of analysis followed by development, teams can now explore ideas directly through working prototypes and rapid experiments.

The most effective teams no longer separate thinking from building. They think by building.

This shift marks a move from design thinking to what might be called design doing.

In this model, learning happens through fast cycles of creation, feedback, and refinement. Ideas are not debated endlessly in workshops or captured in lengthy documents. They are explored through tangible experiences that can be observed, tested, and improved.

The practical differences begin to look like this:

Traditional Model AI-Enabled Model
Workshops and brainstorming sessions Rapid experiments and live prototypes
Personas and research summaries Behavioral data and real-world signals
Concept mockups Functional prototypes
Long planning cycles Continuous learning loops

None of this diminishes the importance of understanding people. If anything, the need for deep human insight becomes even more important as the pace of experimentation accelerates.

What changes is how that understanding is expressed. Instead of existing primarily as documents or presentations, insight becomes embedded directly into the experiences teams create and test.

In an AI-native organization, design is no longer a phase that happens before development begins. It becomes an ongoing activity woven directly into the act of building and learning.

IX. Human Trust Becomes the New Design Material

As artificial intelligence accelerates the speed of building, the most important design challenges begin to shift away from usability and toward something deeper: trust.

When products can be created, modified, and deployed almost instantly, the risk is not simply poor interface design. The risk is creating experiences that feel disconnected from human values, human context, and human expectations.

AI makes it easier than ever to generate functionality. But it does not automatically ensure that what is generated is responsible, understandable, or aligned with the needs of the people who will use it.

In an AI-driven world, the most important design material is no longer pixels or screens — it is human trust.

This raises a new set of responsibilities for designers, engineers, and product leaders alike.

Teams must think carefully about questions such as:

  • Do people understand what the system is doing?
  • Are decisions being made transparently?
  • Does the experience respect human autonomy?
  • Does the technology reinforce or erode confidence?

As AI systems become more powerful, the danger is not just that they might fail. The danger is that they might succeed in ways that quietly undermine the relationship between organizations and the people they serve.

Design therefore becomes a critical safeguard. It ensures that rapid technological capability does not outpace thoughtful consideration of human consequences.

In this sense, the role of design expands beyond shaping products. It becomes the discipline that ensures technology remains grounded in human meaning, responsibility, and trust.

X. The Future: Designers Who Ship, Engineers Who Empathize

As AI blurs the traditional boundaries between design and engineering, the most valuable creators in the future will be those who can move fluidly between imagining, designing, and building.

Designers will need to ship working products, not just static prototypes. Engineers will need to empathize deeply with users, understanding problems and shaping experiences that align with human needs.

The new hybrid product creator embodies both curiosity and capability, bridging the gap between thinking and doing. They are able to:

  • Rapidly translate insights into working solutions
  • Experiment and learn from real-world user behavior
  • Balance technical feasibility with human desirability
  • Maintain alignment between strategy, design, and execution

In this new landscape, design thinking does not disappear — it evolves. AI removes many of the barriers that previously prevented designers and engineers from collaborating fully and iterating quickly.

The organizations that succeed will be those where everyone has the ability to both understand humans and act on that understanding at the speed of AI.

The future belongs to hybrid creators who can navigate ambiguity, make fast decisions, and embed human trust into every experiment. In such a world, innovation is no longer the domain of specialists — it is the responsibility of anyone capable of connecting insight with action.

XI. The Real Question Leaders Should Be Asking

The debate is often framed as a dramatic question: “Has AI killed design thinking?” But this framing misses the deeper challenge facing organizations today.

The real question is not whether design thinking survives — it is whether organizations are prepared to operate in a world where anyone can turn ideas into working products almost instantly.

In this AI-accelerated environment, success depends less on the speed of coding or the elegance of design frameworks. It depends on human judgment, understanding, and alignment.

Leaders must ask themselves:

  • Do our teams know what problems are truly worth solving?
  • Can we prioritize experiments that create real human value?
  • Are we embedding human trust and ethical consideration into everything we build?
  • Are our designers and engineers equipped to operate across traditional boundaries?

In this new era, the organizations that thrive will not be the ones with the fastest developers or the slickest design processes.

They will be the organizations that can rapidly identify meaningful opportunities, make thoughtful decisions, and maintain human-centered principles while moving at the speed of AI.

Innovation will no longer belong to the people who can code. It will belong to the people who understand humans well enough to know what should be built in the first place.

The role of leadership is no longer just managing workflows — it is shaping the environment in which hybrid creators can think, act, and build responsibly at unprecedented speed.

New Tools for the New Design Reality

Get the new design thinking downloadsTo help you find problems worth solving and to design and execute experiments, I created a couple of visual and collaborative tools to help you thrive in this new reality. Download them both from my store and enjoy!

  1. Problem Finding Canvas — Only $4.99 for a limited time
  2. Experiment Canvas — FREE

FAQ: AI and the Evolution of Design Thinking

1. Has AI made design thinking obsolete?
No. AI has not killed design thinking, but it has changed the context in which it operates. Traditional design thinking frameworks assumed that building was slow and expensive. With AI accelerating the creation of prototypes and software, design thinking evolves from a staged process into a continuous cycle of experimentation and decision-making.
2. How are the roles of designers and engineers changing with AI?
AI blurs the traditional boundaries between designers and engineers. Designers can now generate working code and functional prototypes, while engineers can explore user experience and interface design. The future favors hybrid creators who can both understand human needs and rapidly implement solutions.
3. What becomes the main focus of design in an AI-driven product environment?
The primary focus shifts from producing artifacts to guiding decision-making and protecting human trust. Design becomes the discipline that helps teams prioritize meaningful experiments, interpret real-world feedback, and ensure that rapid technological development remains aligned with human values and needs.

Image credits: ChatGPT

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.

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

The Architecture of Organizational Agility

2 Replies

Beyond the Pivot

LAST UPDATED: February 24, 2026 at 5:22 PM

Architecture of Organizational Agility

by Braden Kelley and Art Inteligencia

I. Introduction: The Agility Imperative

Beyond Reactive Maneuvering toward Proactive Orchestration

The Stability Paradox

In my work with global enterprises, I often observe a recurring struggle: The Stability Paradox. Legacy organizations often possess the “fixedness” required for massive scale but lack the fluidity to respond to market shifts. Conversely, startups possess “flexibility” in spades but often collapse under their own weight due to a lack of foundational structure.

Defining True Agility

Many leaders mistake speed for agility. Speed is simply high-velocity movement in a single direction. True Agility is the architectural capability to change direction at speed without destroying the engine. It is the move from “reactive maneuvering” — constantly putting out fires — to “proactive orchestration,” where the organization anticipates the flame and adjusts its posture before the heat is even felt.

Thesis: Organizational agility is not about being liquid or formless; it is about strategic architecture. It requires knowing exactly which parts of your foundation must remain fixed to provide a stable spine, so that the rest of the enterprise can remain infinitely flexible.

Braden Kelley Flexibility Quote

II. The Human Side of Agility (Human-Centered Change)

Fueling the Adaptive Machine with Mindset and Culture

Psychological Safety as a Fuel

An agile architecture is useless if the people within it are too terrified to move. Psychological safety is the essential fuel for change. If employees fear that a “failed” experiment or a missed pivot will result in professional retribution, they will default to the status quo every time. To be truly agile, the organization must celebrate the learning gained from failure as much as the success of a win.

Shifting the Mindset: Adaptability Over Efficiency

For decades, management science focused on “Efficiency-First” — doing things right through rigid optimization. In a volatile world, we must pivot to “Adaptability-First” — ensuring we are doing the right things as the market shifts. This requires a cultural “unlearning” where we value the ability to pivot just as highly as the ability to execute.

Radical Transparency and Communication Loops

Agility requires that the “edges” of the organization — the people talking to customers and witnessing market friction — have a direct line to the “center.” By creating radical transparency and shortened communication loops, we ensure that institutional knowledge flows at the speed of the internet, allowing for collective intelligence rather than top-down bottlenecks.

The Human Truth: You cannot mandate agility; you can only design an environment where it is safe to be agile. Change doesn’t happen in the boardroom; it happens in the hearts and minds of the people on the front lines.

III. The Braden Kelley Organizational Agility Framework™

Navigating the Strategic Tension Between Flexibility and Fixedness

Introduction to the Framework

In my research and consulting, I developed the Organizational Agility Framework™ as a diagnostic tool for the modern enterprise. It moves away from the idea that everything in a business should be “fluid.” Instead, it focuses on identifying the necessary friction and structural integrity required to support rapid movement.

The Core Tension: Flexibility vs. Fixedness

The secret to sustained agility lies in the deliberate management of two opposing states:

  • The Fixed: These are your non-negotiables. They include your core values, organizational purpose, and essential guardrails. These elements provide the “stable spine” and the psychological certainty employees need to take risks.
  • The Flexible: These are your “modular” components. They include business processes, resource allocation models, and team structures. These must be designed to be disassembled and reconfigured in real-time as market conditions evolve.

Organizational Agility Framework

Managing the Equilibrium

The framework teaches leaders how to prevent “Fixedness” from decaying into Rigidity (where you become a dinosaur) and how to prevent “Flexibility” from dissolving into Chaos (where you lose your brand identity). Agility is the active, daily management of this equilibrium.

Insight: If you try to make everything flexible, you create an organization with no memory and no identity. If you keep everything fixed, you create a monument to the past. Agility is the art of knowing what to hold onto and what to let go.

IV. Designing for Modular Change

Architecting the Reconfigurable Enterprise

Loose Coupling and Micro-Structures

In a truly agile organization, we must abandon monolithic, deeply intertwined departmental silos. Instead, we move toward “Loose Coupling.” By organizing into small, cross-functional squads with clear interfaces, we ensure that one part of the business can pivot or fail without bringing down the entire system. This modularity allows for “plug-and-play” innovation.

Resource Fluidity: Escaping the Annual Budget Trap

You cannot have an agile strategy if your capital is locked in a 12-month fixed cycle. Resource Fluidity is the ability to shift talent and funding dynamically as opportunities arise. Agile organizations treat budgets as “living documents,” allowing leadership to pull resources from declining initiatives and inject them into high-growth “breakthrough” experiments in real-time.

Rapid Prototyping for Organizational Structure

We often prototype products, but we rarely prototype structure. Before committing to a company-wide reorganization, agile leaders run small-scale organizational experiments. By testing a new reporting line or a new collaborative workflow within a single “pilot” team, we can validate the human impact of the change before scaling it.

The Design Rule: Complexity is the enemy of agility. If your organizational chart requires a map and a legend to navigate, you aren’t built for speed — you’re built for bureaucracy. Simplify to amplify.

V. Measuring What Matters: Agility Metrics

Quantifying the Velocity and Resilience of Change

Time-to-Insight vs. Time-to-Action

In a traditional enterprise, the gap between identifying a market shift (Insight) and actually deploying a response (Action) can be months or even years. Agility is measured by the shrinkage of this gap. We must track our Latency of Decision — the speed at which data travels from the front lines to the decision-makers and back into the field as an executed strategy.

Learning Velocity

Success is a lagging indicator; Learning Velocity is a leading one. How quickly can your organization ingest new information, test it, and turn it into institutional knowledge? By measuring the number of validated experiments per quarter rather than just “project completions,” we shift the focus from output to outcomes.

The Resilience Score

Agility is as much about defense as it is offense. A Resilience Score assesses how much of a “shock” your organization can absorb — be it a supply chain disruption or a competitor’s surprise launch — without a significant drop in service levels or employee engagement. An agile organization doesn’t just bounce back; it “bounces forward” into a new, more relevant state.

The Measurement Shift: If you only measure efficiency, you will optimize yourself into extinction. You must measure your capacity to change, for that is where your future revenue lives.

VI. Conclusion: The Agile Organization as a Living System

Sustaining Competitive Advantage in a Volatile World

Beyond the Project Mindset

We must stop viewing “agility” as a transformation project with a start and end date. True organizational agility is a continuous practice — a state of being. It is the transition from seeing your company as a static machine to viewing it as a living system. Like any organism, your business must constantly sense, respond, and evolve to its environment to survive.

The Polymath Leader

The leaders of tomorrow must be comfortable with the “Whole-Brain” approach. They must be part scientist, using data and the Agility Framework to maintain the stable spine of the company, and part artist, using empathy and human-centered change to inspire the flexibility of the workforce. This balance is the only way to navigate the tension between what must remain fixed and what must remain fluid.

Your Sustainable Advantage

In an era where technology can be copied and capital is a commodity, your ability to change is your only sustainable competitive advantage. By architecting an enterprise that embraces both the comfort of fixed values and the excitement of flexible processes, you don’t just survive disruption — you become the disruptor.

Final Thought: Agility is the ultimate expression of confidence. It is the belief that no matter how the world changes, your organization has the structural integrity and the creative spirit to meet the moment. Let’s stop fearing the pivot and start building the platform that makes it possible.

Implementation Checklist: Activating the Agility Framework

Practical First Steps for the Human-Centered Leader

Moving from theory to practice requires a deliberate focus on the Fixed/Flexible balance. Use this checklist to audit your current state and begin the transition.

  • Identify Your “Stable Spine”:
    Document the 3-5 core values and the overarching purpose that must remain Fixed. Do your teams know these are the non-negotiable guardrails?
  • Audit for “Rigid Decay”:
    Locate one process that exists “because we’ve always done it that way” but no longer serves the customer. Mark it as Flexible and schedule a redesign.
  • Establish a “Safe-to-Fail” Zone:
    Designate one small-scale project where the team is explicitly rewarded for Learning Velocity rather than just the final ROI.
  • Assess Communication Latency:
    Track how many days it takes for a customer insight from the field to reach a decision-maker. Aim to reduce this Time-to-Insight by 20% this quarter.
  • Beta-Test a “Squad” Structure:
    Select one departmental silo and “loosely couple” a cross-functional team (e.g., Marketing, Tech, and Customer Success) to solve a single specific friction point.

Braden’s Tip: Don’t try to change the whole organization at once. Agility is built through fractal change — successful small pivots that create a blueprint for the larger enterprise to follow.

What is a Stable Spine Audit?

In my Organizational Agility Framework, a Stable Spine Audit is a strategic exercise used to identify the permanent, non-negotiable elements of an organization that provide the structural integrity required to support rapid change elsewhere.

Think of it this way: for a human to move with agility — to sprint, jump, or pivot — the spine must remain strong and aligned. If the spine is “mushy,” the limbs have no leverage. In a business, if everything is up for grabs, you don’t have agility; you have chaos.

The Core Components of the Audit

When I lead an organization through this audit, we look for three specific types of “Fixedness”:

  • 1. Core Purpose and North Star: Why does the organization exist beyond making a profit? This should be fixed. If your purpose pivots every six months, your employees will suffer from “change fatigue” and lose trust.
  • 2. Values and Ethical Guardrails: These are the behavioral non-negotiables. They define how we work. These provide psychological safety because employees know that even in a crisis, the “rules of engagement” won’t shift.
  • 3. Essential Architecture: This identifies the critical systems or data standards that must remain centralized and standardized to allow for “plug-and-play” flexibility in the branches or squads.

How to Conduct the Audit

The audit is essentially a filtering process for every major component of your business. You ask your leadership team: “Is this a Spine element or a Wing element?”

Category The Stable Spine (Fixed) The Flexible Wings (Fluid)
Strategy Long-term Vision & Purpose Quarterly Tactics & Experiments
Structure Governance & Core Values Cross-functional Squads & Roles
Process Essential Compliance & Quality Daily Workflows & Tools
People Cultural DNA & Talent Standards Specific Skills & Resource Allocation

Why It Matters for Innovation

I often see teams that are “frozen” because they don’t know what they are allowed to change. By conducting a Stable Spine Audit, you explicitly tell your team: “These five things are fixed. Everything else is a variable you can experiment with.”

This clarity actually increases the speed of innovation because it removes the “permission bottleneck.” When the spine is stable, the wings can flap as fast as they need to.

Diagnostic Questionnaire: Activating the Organizational Agility Framework

A Leadership Workshop Guide to the Stable Spine Audit

To help you activate the Organizational Agility Framework, here is a diagnostic questionnaire designed to be used in a leadership workshop. The goal is to reach a consensus on what belongs to the “Spine” (Fixed) and what belongs to the “Wings” (Flexible).

Phase 1: Identifying the Fixed (The Stable Spine)

Ask your leadership team to answer these questions individually, then compare notes. Discrepancies here usually indicate where organizational friction is coming from.

  • The “North Star” Test: If we changed our product line entirely tomorrow, what is the one reason for existing that would stay exactly the same?
  • The Value Constraint: What are the three behaviors that, if an employee violated them, would result in immediate dismissal regardless of their performance?
  • The Architectural Anchor: What is the single source of truth (data, brand guideline, or compliance rule) that every department must use to remain part of the collective whole?
  • The Non-Negotiable Promise: What is the one promise we make to our customers that we would never “pivot” away from, even for a massive short-term profit?

Phase 2: Identifying the Fluid (The Flexible Wings)

Now, look at the areas where the organization feels “slow.” These are likely things that are currently “Fixed” but should be “Flexible.”

  • The “Shadow” Processes: Which of our current “standard operating procedures” (SOPs) were created more than two years ago and haven’t been updated since?
  • The Permission Bottleneck: Who has the authority to spend $5,000 to test a new idea? If the answer is “The VP,” that process is too Fixed.
  • The Role Rigidity: Are our job descriptions based on tasks (Fixed) or outcomes (Flexible)? Can we move a person from Project A to Project B in 24 hours without a HR mountain to climb?
  • The Budgeting Cycle: If a massive market opportunity appeared tomorrow, how long would it take to reallocate 10% of our budget to pursue it?

The Audit Tally

Once you have these answers, map them out:

  1. Green Zone: Elements everyone agrees are Fixed. These are your strengths.
  2. Red Zone: Elements everyone agrees are Fixed but should be Flexible. These are your targets for immediate “unlearning.”
  3. Grey Zone: Elements where the team disagrees. This is where your cultural friction lives.

Closing the Audit

As an innovation speaker, I always remind leaders: The Spine is for Support, not for Strangulation. The goal of this audit isn’t to create more rules, but to create the clarity that allows for more freedom.

Organizational Agility: Frequently Asked Questions

1. What is the difference between organizational speed and organizational agility?

Speed is the velocity of movement in a single direction. Agility is the architectural capacity to change direction at speed without breaking the organization. While speed is about execution, agility is about reconfigurability.

2. Why does the “Stable Spine” actually help an organization move faster?

A “Stable Spine” (fixed core values, purpose, and guardrails) provides psychological safety and clarity. When employees know exactly what is non-negotiable, they no longer need to seek permission for everything else, effectively removing the “permission bottleneck” that slows down innovation.

3. How do you identify if a process should be ‘Fixed’ or ‘Flexible’?

Use the Stable Spine Audit. If a process protects your core DNA, ethical standards, or brand promise, it is “Fixed.” If a process is simply a method for delivery, resource allocation, or internal workflow, it should be “Flexible” and modular to allow for rapid adaptation to market shifts.

Image credits: Braden Kelley (1,100+ FREE quote posters at http://misterinnovation.com), 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 Google Gemini to clean up the article and add citations.

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

Capitalizing on Disruptive Innovations

Leave a reply

Capitalizing on Disruptive Innovations

GUEST POST from Geoffrey A. Moore

In Silicon Valley, we are in love with disruptive innovations, largely because we make a lot of them and have profited exceedingly well from so doing. But for anyone on the receiving end, the relationship is not so rosy. Yes, the potential for gain is extraordinary, but the path to getting there is strewn with attempts that have fallen far short of the hype. How can one engage responsibly with this sort of opportunity? Here’s a framework that can help.

Capitalizing on Disruptive Innovations Stairway to Heaven Framework

There are four proven ways to capitalize on disruptive innovation, and they are organized here in terms of escalating risk and reward. Each stair appeals to a different persona in the Technology Adoption Life Cycle, the bottom one attracting conservatives, the second, pragmatists in pain, the third, pragmatists with options, and the fourth, visionaries. Each stair can be managed to its targeted reward, but it is very hard indeed to manage two or more stairs in tandem. Most failures occur because management is not decisive about which gains it is committed to achieving and in what priority order it should be served. Needless to say, there is a better way.

The first use of this framework is to explore the possibilities of each stair for your enterprise. That is, if you were to prioritize this stair, what would success look like, how would you expect to measure it, and what costs and risks would be entailed? You want to talk this through as a team, ensuring everyone gets heard. Specifically, you want to make sure that the adoption personas of the most powerful people in the room do not dominate this part of the dialog. They are likely going to make the call in the end, but it is critical that they hear everyone out before they do.

Let’s try this out with everyone’s latest favorite example—generative AI. Imagine you are a member of the executive team at a pharmaceutical corporation, and you have charged your IT team to come up with a GenAI strategy. Wisely, they have come back to you with an array of options, arranged in a stairway to heaven. Here’s what they might say:

  • Automate. There is a whole series of regulatory compliance obligations that today we outsource overseas to be serviced by a lower-waged workforce. Not only would automating these tasks reduce our costs, it would also lower the error rate and continuously improve performance as more and more machine learning is put to work. This is a low-risk, modest-return option. There would be no disruption to any of our other operations, and we in IT could learn a lot about a technology that is mutating far faster than anything we have ever seen before.
  • Reengineer. Our proteomics research scientists are having a real problem with the combinatorial explosion of all the possible 3D configurations a given 2D sequence of amino acids might adopt. By focusing our generative AI models on just this one problem, we can vastly accelerate our discovery phase, transforming our problem set from completely intractable to continuously improving. This is a medium-risk, high-return opportunity that is confined to a single department, thereby minimizing disruption to the rest of our value chain.
  • Modernize. Our go-to-market teams are competing for smaller and smaller slices of time from the physician offices they call upon. We need relevant messaging to get the appointment and highly personalized content to get buy-in from both the doctors and the nurses. Today we rely on experience and anecdotal data, which works OK for our long-tenured members but makes recruiting, onboarding, and ramping a nightmare. By focusing our Large Language Model on all the data in our CRM systems, combined with all our data from the labs, clinical trials, patent submissions, as well as the patient records we have access to, we can arm our GenAI with more information than any one human could process. We still will have humans in the loop to monitor and adapt this material throughout the sales process, but they will be much better equipped to compete than ever before. This is a high-risk, high-return opportunity that will impact a large portion of our workforce, so we plan to stage the implementation to capture learnings as we go.
  • Innovate. Deep Mind’s AlphaGo program taught itself to play go at the highest level by playing against itself millions and millions of times. We think we can take a similar approach to drug discovery. It’s a moon-shot idea, and our data scientists are still in their own discovery phase, but this could be a game-changer for the industry. We’d like to take a VC approach to funding this effort, ring-fencing the funding across several years, but holding ourselves accountable to meeting material milestones along the way.

As you can see, there is a case to be made for each stair, but there is only so much time, talent, management attention, and working capital to go around, so it is critical that the executive team prioritize these four options and sequence them appropriately. Different teams will come up with different priorities. You are not looking for the “right answer.” You are looking for the one that will yield the best risk-adjusted returns for your enterprise under current conditions.

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

Image Credit: Geoffrey Moore, Google Gemini

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

Why It Matters WHO Conducts Your Customer Experience Audit

Leave a reply

LAST UPDATED: May 29, 2026 at 4:42 PM

Why It Matters WHO Conducts Your Customer Experience Audit

by Braden Kelley and Art Inteligencia

I. Introduction: The Audit as a Mirror

In the hyper-competitive landscape of 2026, many organizations are drowning in data but starving for insight. They perform audits, yet the fundamental “why” of customer friction remains elusive.

The Diagnostic Gap

Most companies have more tools than ever to track clicks, bounce rates, and conversion funnels. Yet, there remains a persistent Diagnostic Gap: the distance between knowing what a customer did and understanding why they felt compelled to do it. Organizations often fail to see their own blind spots because they are looking into a mirror they’ve polished themselves.

The Core Thesis: Perspective over Procedure

A Customer Experience (CX) Audit (aka Customer Experience Risk and Revenue Leakage Diagnostic) is more than a technical inspection; it is an act of empathy. If the auditor lacks a human-centered innovation lens, the resulting report will be mathematically correct but strategically hollow. It might tell you that a button is in the wrong place, but it won’t tell you that your entire value proposition is losing its soul.

The Stakes in 2026

In today’s market, brand loyalty is fragile. A single friction point isn’t just an inconvenience — it’s a broadcast signal to your competitors that there is an opening to disrupt you. Who you choose to hold up the mirror determines whether you see a minor blemish or a structural crack that needs immediate innovation.

Key Takeaways: You cannot solve a problem using the same level of consciousness that created it. The value of an audit is not in the findings, but in the new perspective that allows your team to stop fearing the “How” of the present and start building the “Why” of the future.

II. Internal Audits: The Myth of Objectivity

While internal teams possess deep product knowledge, that very proximity often creates a “distortion field” that obscures the true customer experience.

The “Curse of Knowledge”

Internal teams are often too close to the project to see the friction. Because they know how the system is supposed to work, they subconsciously compensate for poor design. They skip over the confusing copy and ignore the lag because they have developed internal workarounds. A customer doesn’t have that luxury; they only see the barrier, not the intent behind it.

The Hidden Pressure of Internal Politics

An internal audit rarely exists in a vacuum. There is often an unspoken pressure to validate previous executive decisions or to protect the “babies” of influential departments. When the person auditing the experience reports to the person who designed it, the “truth” is often softened to avoid conflict, leading to incremental tweaks rather than the bold innovation required in 2026.

The Efficiency Trap vs. Customer Delight

Internal audits tend to focus on operational efficiency — how can we make this process faster or cheaper for us? While important, this lens often misses the emotional resonance of the journey. You might have a process that is 100% efficient but 0% engaging. Internal teams often solve for “Done,” while customers are looking for “Delight.”

Key Takeaways: You cannot read the label from inside the bottle. Internal audits are great for maintenance, but they are rarely the catalyst for breakthrough change. To find the “Why” of the future, you need a lens that isn’t colored by the “How” of your internal legacy.

III. Independent Audits: The Power of the Outsider

The greatest value an independent auditor brings isn’t just a new set of eyes — it’s a different set of experiences and the freedom to be radically honest.

Fresh Eyes and Cross-Industry Intelligence

An independent auditor lives outside your corporate “echo chamber.” They bring insights from diverse sectors — retail, healthcare, tech, and hospitality — to identify “unobvious” friction points you’ve grown accustomed to. In 2026, your customers don’t just compare you to your direct competitors; they compare you to the best experience they had earlier that morning. An outsider helps you measure up to that global standard.

Closing the “Accountability Gap”

Truth is the primary currency of a successful audit. An independent voice can speak truth to power without the fear of internal repercussions or career friction. This objectivity allows for a “radical transparency” that internal teams often find impossible. By closing the accountability gap, the independent auditor ensures that the real barriers to innovation are named, faced, and eventually dismantled.

Bridging the ‘Why’ and the ‘How’

While internal audits often provide a checklist of “How” to fix specific bugs, an independent auditor investigates the “Why” behind the customer’s emotional journey. They look at the narrative, not just the nodes. This perspective shift allows an organization to move beyond mere troubleshooting and into the realm of strategic experience design.

Key Takeaways: An independent auditor is the customer’s ultimate advocate. When you bring in an outside perspective, you aren’t just buying a report; you are investing in the clarity required to see your organization as the world sees it. Only then can you begin to change it.

IV. The Braden Kelley Edge: Beyond the Checklist

A standard audit tells you where the leaks are; my audit tells you how to change the flow. My approach integrates human-centered change directly into the diagnostic process.

Human-Centered Change as a Methodology

I don’t view Customer Experience as a series of static touchpoints on a map. I view it as a living ecosystem of human interactions. My “Edge” comes from treating the audit as an organizational change exercise. We don’t just look for technical errors; we look for where your internal culture and external experience have lost alignment. By centering the human — both employee and customer — we identify the psychological barriers to a seamless journey.

The Innovation Integration

Most auditors stop at “What is broken?” I start at “Where is the opportunity?” My lens is uniquely calibrated to find where your next innovation is hiding within your current customer friction. If a customer is struggling with a specific step, that isn’t just a bug — it’s a signal of unmet need. I help you translate that struggle into a roadmap for a new product, service, or business model that your competitors haven’t even imagined yet.

Strategic Alignment and Brand Soul

A “good” experience isn’t enough in 2026; it must be your experience. I ensure that every touchpoint is strategically aligned with your unique brand soul and ethical guardrails. An audit under my guidance ensures that efficiency never comes at the cost of authenticity. We solve for the “How” of the present while keeping a relentless focus on your “Why” for the future.

Key Takeaways: An audit shouldn’t just result in a list of repairs; it should result in a vision for renewal. When I audit your experience, I am looking for the spark of innovation that turns a satisfied customer into a lifelong advocate.

V. Why Braden Kelley is the Perfect Partner for Your CX Audit

Selecting an auditor is about trust, legacy, and the ability to translate observation into transformation.

A Legacy of Innovation Leadership

With years of experience as a globally recognized innovation thought leader, I don’t just see a customer journey; I see a competitive battlefield. My background in human-centered design ensures that every recommendation is grounded in the reality of human behavior. I have spent my career helping organizations navigate the complexities of change, making me uniquely qualified to identify the structural hurdles that prevent your team from delivering excellence.

The “Resilient Auditor” Framework

I apply the same resilience routines I advocate for in my speaking and writing to the audit process. This ensures a level of focus, objectivity, and deep synthesis that standard consulting firms often miss. I don’t provide “off-the-shelf” solutions; I provide a custom diagnostic that accounts for the psychological and operational resilience of your specific organization.

Actionable Velocity

The biggest failure of most CX audits is that they sit on a shelf. My goal is Actionable Velocity. I deliver a roadmap that doesn’t just list what’s wrong, but prioritizes fixes based on their potential for ROI and innovation impact. I provide your team with the “Why” they need to stay motivated and the “How” they need to execute immediately.

The Braden Kelley Promise: When I conduct your audit, you aren’t just getting a consultant; you are getting a partner dedicated to making your organization smart enough to solve its own most complex problems. We will bridge the gap between where you are and where the future demands you to be.

VI. Conclusion: Choosing Your Mirror

Ultimately, a Customer Experience Audit is an investment in clarity. In an era where disruption is the only constant, you cannot afford to look through a distorted lens. Whether you choose an internal review for maintenance or an independent audit for transformation, remember that the quality of the insight is entirely dependent on the perspective of the auditor.

Don’t Just Audit the Past — Design the Future

The goal of a world-class audit isn’t just to find out where you’ve been, but to illuminate where you are capable of going. By choosing an auditor who understands human-centered change and innovation strategy, you ensure that your organization doesn’t just fix the “How” of today, but masters the “Why” of tomorrow.

The mirror you choose today will determine the reflection your customers see tomorrow. Make sure it is a mirror that shows the full potential of your brand’s soul.

Ready to Transform Your Customer Journey?

Stop guessing and start innovating. Let’s work together to find the “unobvious” opportunities hidden within your customer experience.

— Braden Kelley

Ready to find your Customer Experience innovation opportunities?

Request a Customer Experience Audit

For more on Customer Experience Audits check out:

Customer Experience Audit 101
Why a Customer Experience Audit is Non-Negotiable in 2026
Is Your Customer Experience a Lie?

CX Audit: Frequently Asked Questions

1. Why is an independent CX audit better than an internal one?

Internal teams often suffer from the “Curse of Knowledge” — they are so familiar with how things should work that they miss how they actually work for the customer. An independent auditor brings unbiased clarity and the courage to name the structural issues that internal politics might keep hidden.

2. How does Braden Kelley’s approach differ from others?

Most audits look for bugs; Braden Kelley looks for breakthroughs. By applying a human-centered innovation lens, Braden identifies not just where you are failing the customer, but where the customer is signaling a need for a new solution you haven’t built yet.

3. What is the main outcome of this audit?

The primary outcome is Actionable Velocity. You won’t receive a static report; you’ll get a prioritized roadmap that balances immediate experience “quick wins” with long-term strategic innovation goals, ensuring your CX is a driver of growth, not just a line item.

Image credits: ChatGPT

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 to clean up the article and add citations.

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

Are Ethics a Constraint or Catalyst for Innovation?

Leave a reply

Are Ethics a Constraint or Catalyst for Innovation?

GUEST POST from David Sable

For centuries, innovation has lived in tension with ethics.

Some say moral codes kill progress… Others say they force progress to grow up. And sometimes… they save lives.

The truth?

It’s not binary… It’s a system with three gears:

  • Ethics can kill innovation.
  • Ethics can sharpen innovation.
  • Ethics can morph innovation and save lives.

Let’s explore all three.

When Ethics Slowed or Killed Innovation

Galileo (1633): He was tried by the Church for heresy for supporting heliocentrism. The science was sound… but ethics and religion weren’t ready. The progress paused for decades.

Human Gene Editing (2018): The CRISPR baby scandal in China sparked global bans. What could’ve been a gene-editing revolution was halted overnight. Ethics drew the red line.

Embryonic Stem Cell Research (2001–2009): Federal funding bans in the U.S. slowed a medical frontier, but the ethical blockade forced a pivot… leading to induced pluripotent stem cells. No embryos needed.

3D-Printed Guns: The blueprints spread fast. There were 100,000+ downloads. Then came the ban. Public safety over open-source freedom. Questionable innovation.

Facial Recognition Tech: It was halted by Amazon, IBM, and Microsoft in 2020. Why? Racial bias… surveillance concerns… and wrongful arrests. It didn’t die… but it had to evolve.

When Ethics Sharpened Innovation

Green Chemistry: Toxic byproducts used to be a cost of doing business. Ethical pressure gave rise to “benign by design” tech. Now it’s a growth market.

Accessibility Design: Sidewalk ramps weren’t built for travelers and strollers… They were built for wheelchairs…. and they ended up helping everyone. The “Curb Cut Effect” is now UX Evangelism.

Privacy Laws (GDPR, HIPAA): While it slowed data flows, it triggered encryption, on-device AI, and federated learning. The constraints sparked new architectures.

Explainable AI (XAI): Ethical backlash against black-box algorithms forced a rethink. Now, companies are judged on accuracy, transparency, and traceability.

Tesla’s Circular Supply Chain: The demand for ethical sourcing turned a compliance issue into an operational win. Now, Tesla is near 95% battery material recycling… lower emissions… and lower costs.

When Ethics Flat-Out Saved Lives

Vioxx Scandal (1999–2004): The drug rushed to market… praised as a breakthrough. But then came the deaths. There was a forced recall… and $4.85 billion in settlements. Ethics didn’t slow this innovation, but it should have.

Solar Geoengineering: Experiments like Harvard’s SCoPEx were shelved. Not because they didn’t work, but because the risks were planetary. Ethics didn’t just stall the idea; it saved us from playing God with the sky.

Predictive Policing Tools: It was touted as crime-busting AI. Turns out… they just automated racial profiling. The fix wasn’t a patch. The fix was a ban.

The truth is that some innovations never come back from ethical collapse. Others rise stronger from the fire. The real difference? Whether the ethics were ignored… or integrated.

What to Do Now

  1. Define your red lines early.
  2. If you wait until launch… It’s too late.
  3. Design for constraint.
  4. Let the friction shape the form… work it.
  5. Build auditable systems.
  6. Black boxes break trust. transparency scales.
  7. Know the cost of speed.
  8. The market remembers failures longer than delays.
  9. Use ethics as a strategy.
  10. It’s not just a legal risk… It’s a competitive power.

Potter Stewart ethics quote

“Ethics is knowing the difference between what you have a right to do… and what is right to do.”
— Potter Stewart, U.S. Supreme Court Justice

Innovation isn’t value-neutral. It never was.

And in 2026, ethics isn’t just the constraint… It’s the catalyst.

Image credit: ChatGPT

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