How Strategic Design Turns Imagination into Reality Without Losing Its Intent

Organizations don’t fail because they lack ideas or execution.
They fail because they cannot translate one into the other.

I recently participated in a three-day design innovation workshop with the US Air Force Pathfinder Program alongside Colonel Jason Trew, PhD (USAF Ret.), former Commandant and Dean of the School of Advanced Air & Space Studies and author of The Icarus Solution. It was the kind of environment where ideas are quickly confronted by operational reality, shaped by people who understand constraint not as theory, but as a daily condition.

Over those three days, we moved continuously between two very different modes. At times, conversations were grounded in structure, mission requirements, operational realities, and the discipline required to execute in highly constrained environments. At other moments, the room opened into broader exploration, allowing participants to question assumptions, reframe problems, and imagine possibilities beyond existing systems.
What became increasingly clear was not simply that both modes were necessary, but that neither produced meaningful outcomes in isolation. The strongest ideas did not emerge from creativity alone, and the most viable solutions did not emerge from structure alone. They emerged in the tension between the two.

That friction did not slow the work. It revealed it.

And once you begin to recognize it, you start to see it everywhere. Including in the way organizations are designed to operate.

Control Is Not the Problem. Overcontrol Is.

Organizations are built to create order.
Strategy defines direction. Processes create consistency. Governance reduces uncertainty. Over time, these mechanisms become the foundation of how work gets done and how success is measured. In stable environments, this architecture enables scale, efficiency, and reliability.

But most environments are no longer stable.

For example, a global financial institution recently completed a multi-year transformation of its digital platform. Execution was exemplary. Timelines were met, risks mitigated, dependencies managed. Internally, it was considered a success. Yet within months of launch, adoption lagged significantly behind expectations. Competitors had already redefined what “good” looked like. The organization had delivered precisely what it had planned, but what it had planned no longer mattered.

This is the paradox. Organizations are becoming more efficient at executing against defined objectives while becoming less effective at adapting those objectives to a changing reality. The system improves its ability to deliver, while losing its ability to sense.

Control, on its own, is no longer enough.

Icarus Was Never the Problem

That instinct toward control is not new. The story of Icarus has reinforced it for centuries. Do not fly too high. Do not let ambition outrun discipline. Respect limits.

But this interpretation is incomplete.

In the original myth, Daedalus, the master craftsman, builds wings for himself and his son Icarus to escape captivity, warning him not to fly too close to the sun. Icarus, driven by ambition, ignores the warning and falls.
At a glance, the story feels like a familiar dichotomy. Icarus as ambition and imagination, the instinct to rise. Daedalus as discipline and craft, the structure that makes flight possible. It mirrors the way we often frame creativity and logic, exploration and execution, as opposing forces. As Trew reflected in our conversations:

“I grew up in an organization that was biased towards Daedalus — special rooms, organizations, and even statues all created in his honor; I didn’t realize that Icarus was not just a fool but perhaps the true hero of the story.”

As Trew reframes it, Icarus and Daedalus are opposing forces held in necessary tension, interdependent elements of the same system. Icarus represents imagination, ambition, and the instinct to push beyond what exists. Daedalus represents discipline, craft, and the structures that make flight possible. Innovation emerges not by resolving that tension, but by learning how to operate within it.

Remove Icarus, and nothing new is attempted.
Remove Daedalus, and nothing survives.

This dynamic is not confined to myth. It is embedded in the history of innovation itself. In the early development of airpower, pilots operated ahead of doctrine, experimenting, learning through practice, and shaping the very theories that would later define the field. Practice did not follow strategy. It informed it.

Yet most modern organizations behave as if ideas must conform before they are allowed to exist. And that misunderstanding does not stay theoretical. It shows up directly in how organizations operate today.

Two Forces. One System. Rarely Designed Together.

Organizations do not fail because they lack ideas.
They do not fail because they cannot execute.

They fail because they cannot carry ideas forward without losing what made them valuable in the first place.

Ideas rarely collapse all at once. More often, they are gradually reshaped by systems optimized for predictability, governance, and scale until the original intent becomes almost unrecognizable.

This is the failure that rarely appears in reports. Not failure to deliver, but failure to preserve intent.

To understand why this happens, you have to look at the underlying system. At a fundamental level, every organization operates between two forces.

Exploration is where ideas are born. It is fast, ambiguous, and driven by curiosity. It challenges assumptions and expands possibility. Throughout the workshop and the conversations surrounding it, this was often the mode where assumptions loosened, perspectives shifted, and entirely different possibilities began to emerge. It is the space where the system stretches beyond what it currently understands.

Execution is where ideas survive. It is structured, disciplined, and oriented toward scale. It translates concepts into systems, processes, and measurable outcomes. It is where ideas are forced to prove their value under constraint.

Most organizations are designed to optimize one of these forces.
Few are designed to integrate them.

During conversations surrounding the Pathfinder workshop, I had a particularly insightful discussion with Paul Propster, Senior Strategist in the NASA/JPL Office of Strategy, around this exact tension: how organizations balance engineering rigor, operational constraints, and the need to radically rethink entrenched systems. That conversation naturally led to the broader transformation unfolding across aerospace itself. When SpaceX began challenging the economics of spaceflight, Elon Musk pushed engineers, many of them shaped by NASA’s legacy systems, to question assumptions that had long gone unexamined. Why are rockets so expensive to build? Why are they discarded after a single use? Why is reusability treated as an exception rather than a baseline?

The answers were rarely about physics. They were about precedent. Not because they were optimal, but because they were inherited. Because the system had been designed that way. Because constraints had been accepted rather than interrogated.

What followed was not incremental innovation. It was a redesign of the system that governed how rockets were conceived, built, and deployed.

Discipline was not removed. It was restructured.

Extended development cycles gave way to rapid iteration. Testing became continuous rather than sequential. Failure, within controlled bounds, became a mechanism for learning rather than a point of termination.

In effect, SpaceX did not choose between exploration and execution.
They redesigned how the two interacted.

The result was not simply lower cost or reusable rockets. It was a fundamentally different relationship between imagination and scale, one where ideas could evolve without being prematurely constrained, and scale without losing their original intent.

That is the real challenge. Not choosing between these forces, but designing systems where both can operate without canceling each other out. And even when organizations recognize these two forces, something still breaks.

The Gap Where Good Ideas Go to Die

The breakdown rarely occurs in exploration or execution themselves. It occurs in the transition between them.

A financial services firm developed a simplified onboarding experience that significantly improved completion rates during testing. The concept was validated. The value was clear. But as it moved toward implementation, it encountered regulatory constraints, legacy systems, and fragmented ownership across teams. Each adjustment made sense. Together, they altered the experience fundamentally.

By the time it launched, the solution complied with every requirement and delivered only a fraction of the original value.

This is the invisible gap.

It is not a failure of ideas.
It is not a failure of execution.

It is a failure of translation.

That same dynamic surfaces around the broader challenge of accelerating the design, production, and deployment of drones and unmanned systems within highly constrained environments.

The question was deceptively simple: how do you move from concept to deployed capability in a fraction of the time, when operating within the realities of government attribution, acquisition protocols, and layers of Pentagon governance designed for control, not speed?

In traditional models, this process is linear and heavily sequenced. Requirements are defined upfront. Programs are scoped, funded, and approved through rigid cycles. Vendors are selected. Systems are designed, tested, and eventually deployed. Each step is optimized for accountability and risk reduction. And each step introduces delay.

By the time capability reaches the field, the context it was designed for has often shifted.

What emerged from our conversations was not a rejection of these constraints, but a different way of thinking about how organizations operate within them. Instead of treating exploration and execution as separate phases, conversations repeatedly returned to the idea that these modes could operate in parallel rather than sequentially. Rapid prototyping alongside evolving requirements. Modular architectures that allowed components to be developed, tested, and deployed independently. Tighter feedback loops between operators, engineers, and decision-makers.

The shift was subtle but significant:

From: Design > Approve > Build > Deploy
To: Explore > Test > Adapt > Scale

All happening continuously, not sequentially.

The challenge was not removing Daedalus, the structures of governance, compliance, and control. Those remain essential in environments where failure carries real consequences.

The challenge was allowing Icarus, exploration, iteration, and learning, to exist within that system without being suppressed.

Because in environments where timelines compress and threats evolve rapidly, the inability to translate ideas into deployed capability is not just inefficient.

It is a strategic vulnerability.

This Is Bigger Than Organizations

This breakdown is not isolated. It is not confined to companies. It is visible across entire systems.

Startups routinely outperform incumbents not because they have better resources, but because they are structurally closer to Icarus. They explore faster, iterate earlier, and allow practice to shape direction. Incumbents, by contrast, are optimized for Daedalus. They scale efficiently, govern effectively, and protect stability, often at the cost of adaptation.

You can see the same tension in artificial intelligence. Research labs push boundaries at extraordinary speed, exploring what is possible. Enterprises struggle to translate those capabilities into scalable, governed systems. The gap is not technical. It is structural.

Even at the geopolitical level, the pattern holds. Nations invest in advanced technologies faster than they evolve the governance systems required to manage them. Capability accelerates. Coherence lags.

Across domains, the same dynamic repeats.

Exploration advances faster than systems can absorb it.
Execution scales faster than meaning can keep up.

This is not an isolated organizational issue. It is a structural condition of complexity.

What we are seeing is not simply a shift in how organizations innovate. It is a shift in how systems evolve under pressure. As complexity increases, the ability to translate imagination into reality becomes the defining constraint. Not technology. Not talent. But the structure through which ideas are allowed to survive.
Which raises a more fundamental question.

The Missing Discipline No One Owns

If this gap is so consistent, why don’t organizations have a discipline to address it?

Execution has been industrialized. Innovation is increasingly structured. But the capability that connects the two remains underdeveloped.

Translation is not a handoff. It is the discipline of preserving intent while adapting form. It requires identifying what is essential within an idea and ensuring those elements survive as the idea encounters constraints.

In healthcare, this challenge is particularly visible. A system may design a seamless, patient-centered experience that improves outcomes in pilot environments. But scaling that experience requires integration across clinical workflows, regulatory frameworks, and legacy technologies. Without a disciplined approach to translation, the experience fragments. What began as transformation becomes incremental improvement.

This is where most value is lost.

Not in the idea.
Not in the execution.

In the space between.

Innovation Without Gravity

When organizations attempt to compensate, they often swing too far in the other direction. If over-structuring kills ideas, the opposite failure is equally common.

Organizations that over-index on exploration often create environments rich in ideas but poor in outcomes.

A large technology company invested heavily in innovation labs across multiple regions. These labs produced compelling prototypes, future-state visions, and bold concepts. They were showcased internally and externally as evidence of innovation. Yet very few translated into products that generated sustained value.

The issue was not creativity. It was the absence of a system capable of carrying ideas into reality.

Without structure, exploration does not collapse.
It dissipates.
Which brings us to the real opportunity.

Design as the Translation Layer

This is where design shifts from a discipline to a system function.

Not as a discipline focused on artifacts, interfaces, or even experiences alone, but as the system responsible for translation.

At its highest level, design becomes the mechanism that translates imagination into executable reality. It preserves the intent of ideas as they move through strategy, funding, governance, technology, and operations.

Across the workshop and the conversations surrounding it, this tension became especially visible. The teams that made the most progress were not the most creative or the most structured. They were the ones that could move between both without losing coherence. They understood how to test ideas without diluting them, and how to structure solutions without stripping away their core value.

This is not a supporting capability. It is an operating necessity.

In complex systems, the ability to translate is what determines whether organizations evolve or stagnate. But recognizing this role is not enough.

Designing for Tension

If tension between exploration and execution is inherent, the goal is not to eliminate it. It is to design for it.

This requires recognizing that these modes operate under different conditions:
• Exploration needs space, speed, and tolerance for ambiguity.
• Execution requires clarity, alignment, and discipline.

Forcing them into a single operating model creates friction without progress. More importantly, it requires designing the pathways between them. How ideas are validated, how evidence is generated, how decisions are made, and how ownership transitions without fragmentation.

These pathways are where most organizations fail. Not because the ideas are weak. But because the system cannot carry them forward.
And if this is true, then it changes how performance should be measured.

From Insight to Practice: Operating Inside the Tension

Traditional metrics emphasize execution: efficiency, predictability, delivery. But in environments defined by change, execution alone is insufficient. A more meaningful measure is the ability to translate. Are insights turning into action? Are ideas becoming durable systems? Is the organization scaling what matters, or simply what is easiest to manage?

Understanding the tension between exploration and execution is one thing. Operating within it is another. For designers and strategists, this is where the work changes. Not in what you produce, but in how you move.

Three shifts begin to define the difference:

1. Design in Dual Modes, Not Linear Phases

Most teams still treat innovation as a sequence. First explore, then define, then deliver. Discovery happens upfront. Execution happens later. Once a direction is chosen, the expectation is to move forward, not revisit.

In reality, the most effective teams operate differently. They move back and forth between exploration and structure as insight evolves. Even late in delivery, they continue to test assumptions. Even early in discovery, they introduce structure to understand what might actually work.

In practice, this shows up in small but critical moments. A team in delivery pauses to revisit a core assumption after new user feedback. A prototype is tested before requirements are fully locked. A roadmap is treated as directional, not fixed, allowing space to adapt as new information emerges.

This requires resisting the urge to “lock” ideas too early. It means allowing concepts to remain fluid long enough to understand what truly matters, while introducing just enough structure to test their viability. The work is not to separate thinking from doing, but to let each continuously inform the other.

The question is not “Are we done exploring?”
It is “Are we structuring the right thing?”

But operating in dual modes is only the beginning.

2. Protect Intent as Ideas Scale

As ideas move through organizations, they are reshaped by constraints. This is inevitable. What is not inevitable is the loss of intent.

Most organizations attempt to preserve intent through familiar artifacts: a vision statement, a North Star, a set of guiding principles. But too often, these remain static declarations, documents referenced occasionally but rarely used to shape decisions, disconnected from execution.

High-performing teams do something different. They make intent actionable. They define what must not change, even as everything else adapts. They treat the core value of an idea as something to be actively preserved, not passively assumed.

In practice, this becomes visible in how decisions are made day to day. Teams anchor every major trade-off against a small set of non-negotiables. When scope is reduced, when timelines compress, when technical constraints emerge, the first question is not “what is easiest to cut?” but “what cannot be compromised?”

This takes concrete forms. Design principles that travel WITH the idea across teams and are referenced in reviews, not just documented. Clear articulation of the experience or outcome that must survive, even if everything around it changes. Decision frameworks that require teams to justify how a change still aligns with the original intent.

Without this, every constraint becomes an erosion.
With it, constraints become design inputs.

But even when intent is protected, something still breaks.

3. Design the Pathways, Not Just the End State

Most teams focus on either the idea OR the outcome. They invest heavily in defining a vision, or in delivering against a roadmap. Few spend time designing what happens in between. But that is where success is actually determined.

In practice, this is where things tend to break. An idea leaves a workshop and enters funding conversations. It moves from strategy into delivery teams. It gets translated into requirements, tickets, and timelines. At each step, decisions are made by different functions, often with different incentives. Without intentional pathways, the idea does not evolve coherently. It fragments.

Designing pathways means making these transitions explicit. It means defining how ideas mature as they move through the system. What evidence is required to move forward. How trade-offs are evaluated across teams. How ownership shifts without losing continuity.

You see it in how teams operate. Joint reviews where design, product, engineering, and business stakeholders evaluate decisions together. Clear checkpoints that are based on evidence, not just approval. Shared artifacts that carry intent across pathways instead of resetting it at each transition.

It also means recognizing that this is not a one-time handoff. It is a continuous process of translation, where ideas are refined without being reduced.

The strongest teams do not just create solutions.
They create the conditions for solutions to survive.

These shifts do not eliminate tension.
They make it usable.

The System That Can Fly

In the end, all of this points to a different kind of challenge.

The work is not simply to generate better ideas or execute more efficiently. It is to design systems that can continuously move between what exists and what could exist without losing either.

Because the real risk is not ambition. It is building systems that cannot translate it forward.

The tension between Icarus and Daedalus does not disappear.
It intensifies.

The organizations that endure will not resolve that tension. They will learn to operate within it, continuously. And in doing so, they will build something far more difficult than balance.

They will build systems that can fly.

(Disclaimer: The companies, projects, and examples mentioned in this article are based on publicly available information and industry best practices. No proprietary or confidential information has been disclosed, and all references are for illustrative purposes only. This article does not represent insider knowledge or violate any non-disclosure agreements. Some AI tools could have been used for basic editing, research and visuals, but the insights and perspectives are entirely human.)

We are no longer designing services. We are designing the systems that define reality.

A few weeks ago at SXSW, Amy Webb, CEO of Future Today Strategy Group and renowned futurist, introduced the Convergence Outlook 2026, a report that makes one thing impossible to ignore: We are no longer operating in a world of isolated trends, but in one where multiple forces collide and reshape systems at once.

It does not describe a distant future. It names the reality we are already operating inside, one where change no longer arrives in clean sequences, industries no longer move independently, and strategy can no longer wait for clarity before committing.

If you have been paying attention, none of this feels surprising. The contours of this shift have been forming for some time. In earlier work, I described it as the emergence of a Geostrategic layer to Design. What this report does is bring that layer into sharp focus.

The convergence era is here, and service design is uniquely positioned to evolve and lead in this new era, building on its systemic foundation to address a more complex, interconnected reality.

We’ve Entered a New Operating Reality

For years, we treated change as something that unfolds in sequence. One trend emerges, another follows, industries adapt, recalibrate, and move forward. That model no longer holds. As Amy Webb puts it, “the future no longer arrives one trend at a time.”

Change is no longer linear, contained, or predictable in isolation. Multiple forces now collide at once across technology, economics, geopolitics, and human behavior. They don’t move in parallel. They interact, amplify, and destabilize each other.

Disruption doesn’t just move forward anymore. It spreads sideways, and when it does, the effects are no longer incremental. They are systemic.

Most organizations can see this happening, but they are still responding with models built for a different era: Strategy assumes time, design assumes boundaries, innovation assumes separation.

None of those assumptions survive the new concept of convergence. This is why decisions about AI, supply chains, regulation, and infrastructure are now shaping customer experience more than any interface ever could.

Because convergence is not a cluster of trends. It is a structural shift that cuts across domains, moves non-linearly, redistributes power, and once it takes hold, is difficult to reverse.

It doesn’t stack on top of existing systems. It rewrites them.

What once felt improbable becomes inevitable. Value moves, advantage shifts, and boundaries dissolve. And when those boundaries disappear, so does the idea of competition as we understood it.

You are no longer competing within a category.

You are competing across ecosystems that did not exist a few years ago.

Reality is Already Being Rewritten

If this still feels abstract, it shouldn’t. The signals are already here, and they are compounding.

Identity is no longer something you present. It is continuously inferred, tracked, and verified. Anonymity is quietly disappearing.

Infrastructure is no longer global. It is fragmenting along geopolitical, energy, and regulatory lines, reshaping how and where systems operate.

Labor is detaching from value creation as automation scales, concentrating power around ownership of systems rather than human effort.

At the same time, systems are no longer waiting for users to act. They predict, decide, and intervene before intent is even expressed. Surveillance is no longer exceptional; it is embedded, normalized, and financed by the very services we depend on.

Emotional support is shifting from human relationships to always-on, machine-mediated environments. And the human body itself is entering the system, as augmentation moves from experimentation to expectation.

None of these shifts are happening in isolation. Together, they are rewriting something deeper: Behavior, trust, agency, and experience.

Not gradually, but fundamentally.

The System is Already Making Decisions for You

A customer wakes up and checks their phone. Before they take a single action, the system has already acted on their behalf.

Their device has authenticated them through biometrics. Their news feed has been filtered based on where their data is allowed to flow. Their banking app has flagged a transaction before they notice it. Their health app has adjusted recommendations based on patterns detected overnight.

They didn’t ask for any of this.
No button was pressed. No journey was initiated.

At the same time, the infrastructure behind these services is shifting. The data they generate is routed through region-specific cloud systems. The AI models interpreting their behavior are tuned differently depending on regulatory constraints. The services they rely on are no longer operating in a global system, but in fragmented, politically defined ones.

And when they reach out for support, they are just as likely to interact with a machine as a human.

What looks like a series of separate experiences is not separate at all.

It is a single system, continuously observing, predicting, and acting across contexts that no longer have clear boundaries.

And it is already shaping decisions before they are made.

The Terrain is Shifting Across Five Domains

To understand convergence, you have to see where pressure is building, not as isolated trends but as forces reshaping entire parts of the system at once.

• Compute becomes physical: Constrained by energy, geography, and geopolitics
• Machines act autonomously: Decisions and workflows move from humans to systems
• Everything is observed and measured: Environments and identities become data streams
• Systems begin to feel alive: AI, sensors, and biology merge into adaptive systems
• Humans shift their dependence: Care and decision-making increasingly route through machines

Individually, each of these shifts would be significant. Together, they change the nature of the environment itself.

This is no longer digital transformation.
It is the transformation of reality as a system.

The Real Risk is Not Disruption. It’s Hesitation.

Most organizations believe disruption is the threat. It isn’t.

The real risk is seeing what’s coming and failing to act on it. Because that is exactly what most companies will do. They will recognize the signals, analyze the shifts, build the decks, and then wait.

Traditional planning assumes that clarity comes before commitment. That with enough data, analysis, and time, the right decision will reveal itself. That assumption no longer holds.

In a convergence environment, waiting is not neutral. It is a decision, and it is usually the wrong one.

The decisions that matter most now are irreversible. They redefine what your organization becomes, and they must be made before the outcome is clear.

This is where strategy fundamentally changes. It stops being an exercise in optimization and becomes an act of commitment under uncertainty.

Winning Organizations don’t Move Faster. They Decide Differently

Not every organization gets caught off guard by shifts like this. But the ones that navigate them successfully don’t just move faster. They think differently.

They operate with clarity and conviction that most organizations never fully develop. They map where value is moving before it becomes obvious, make explicit bets they cannot easily reverse, choose what they will not do, and define the signals that will trigger action before they need them.

NVIDIA is a clear example. Long before generative AI became mainstream, it made a decisive shift toward becoming the infrastructure layer for AI. That choice required years of investment, ecosystem building, and a willingness to move beyond its original identity. By the time the market caught up, the position was already established.

This is no longer just about speed. It is about clarity of position and the willingness to sacrifice what works today to build what will matter tomorrow.

This is Where the Service Design Discipline Evolves

Not at the edges, but at its core. And once you see it, it becomes difficult to ignore.

Because the shift described here doesn’t just validate a direction. It exposes a gap between how we have been designing services and what the world now requires us to design.

In earlier work, I referred to this shift as geostrategic design. What is now becoming clear is that this is no longer a conceptual extension of the discipline.

It is becoming its necessary evolution.

From Services to Systems to Strategy

Service design was never wrong. It was scoped for a different world, one where systems were stable, journeys could be mapped, and touchpoints existed within boundaries that held.

That world is dissolving.

Change is no longer happening at the level of the service. It is happening at the level of the system. Technology, economics, geopolitics, and culture are no longer adjacent forces. They are intertwined, shaping each other in real time.

As they converge, value no longer sits neatly inside a journey or a product. It moves across ecosystems.

Which means the unit of design must change.

You are no longer designing services within systems. You are designing the systems themselves. This is the shift from service design to system design to something more expansive. What I previously framed as geostrategic design.

Geostrategic design is a discipline that operates across forces, environments, and time horizons, where orchestration matters more than optimization and the system is the only place where that orchestration can happen. And once you shift the unit of design from service to system, everything else begins to change.

Designing for Systems that Act, not Users who Choose

Systems are no longer waiting. They are acting.

What was once initiated by a user is now triggered by prediction. Decisions are made before intent is expressed, and actions are taken without a clear moment of interaction. Machines don’t just support decisions; they make them, transact, optimize, and operate continuously in the background.

This is not an extension of service design. It is a redefinition of what the “user” even means.

In previous work, I described this as a shift toward machine-centered design. What we are now seeing is that this shift is not isolated. It is part of a broader systemic transformation.

This fundamentally changes the role of design.

You are no longer designing for a user moving through a journey. You are designing for systems that interpret, decide, and act on behalf of that user.

As this shift accelerates, experience itself begins to disappear.

For decades, we designed experiences as journeys with a beginning and an end. That model is breaking down. The experience is no longer something you enter. It is something that surrounds you.

Identity is continuously tracked. Systems act before you do. Emotional support becomes always-on and machine-mediated. There is no clear starting point, no obvious interaction, no defined boundary.

There is no journey to map.

The experience becomes ambient, predictive, and invisible. And with that, the work changes from mapping journeys to shaping behaviors, from designing touchpoints to orchestrating continuous environments.

What used to be visible becomes embedded. What used to be explicit becomes inferred.

And what used to be designed at the surface now has to be designed at the level of the system.

Design is No Longer Neutral

As systems become more intelligent, predictive, and embedded, something else begins to surface.

Power.

Not as an abstract concept, but as a direct outcome of design decisions.

When environments are continuously observed, identity is biometric, and behavior is shaped in advance, design stops being about experience alone. It starts determining who has agency and who does not.

These are not just technological shifts. They are designed systems of influence that shape what people see, feel, trust, and depend on, and ultimately what they believe is normal.

This changes the responsibility of the discipline.

As explored in earlier work on geostrategic design, design is no longer confined to experience. It operates within systems shaped by power, governance, and global dynamics.

You are no longer designing services and experiences. You are designing power structures, behavioral feedback loops, and emotional dependencies at scale.

Design moves into governance, control, and consequence.

In the convergence era, it is no longer just an experience discipline.
It is a power discipline.

Design Moves to the Center of Strategy

Service design has long lived downstream, shaping how things work after decisions are made. That separation no longer holds.

The decisions that matter now are identity-defining. They determine what an organization becomes and how it creates value, and they are inseparable from design.

Capital allocation, capability building, and structural positioning all shape the systems people experience. These are design decisions.

Which means design cannot remain a delivery function. It moves upstream into strategy, investment, and transformation, not as support, but as direction.

Service design stops being about execution.
And becomes a way to define the future position of the organization.

Designing When There is No Clarity

For decades, design relied on understanding the user, reducing uncertainty, and validating before committing. That model assumed time.

That time is disappearing.

The decisions that matter now must be made before clarity exists. They reshape identity, lock in direction, and cannot easily be reversed.

Waiting does not reduce risk.
It transfers it.

Design can no longer rely on validation. It must operate with conviction, not blind conviction, but informed, system-aware conviction that accepts uncertainty as a condition.

Because the role of Design is no longer to prove what works.
It is to decide what to build before the world makes that decision for you.

The Shift is no Longer Theoretical

If everything here could be reduced to a single idea, it is this:

“We are moving from designing Services within Systems to designing Systems that define Reality.”

That is the line.

And once you see it, it reframes everything.

This is not an evolution. It is a repositioning from experience to systems, from delivery to direction, from validation to commitment.

What was previously emerging as a new layer of thinking is now becoming unavoidable. Geostrategic design is not a future concept. It is an emerging necessity, a way to operate across converging forces, design value where it actually moves, and engage with decisions that are deeply consequential and not easily reversible.

This is not a future to anticipate. It is a reality already taking shape.

The organizations that recognize this shift early will not just adapt.
They will define what comes next.

(Disclaimer: The companies, projects, and examples mentioned in this article are based on publicly available information and industry best practices. No proprietary or confidential information has been disclosed, and all references are for illustrative purposes only. This article does not represent insider knowledge or violate any non-disclosure agreements. Some AI tools could have been used for basic editing, research and visuals, but the insights and perspectives are entirely human.)

A practical guide to building an agentic workflow with off-the-shelf AI tools

In the previous article, we introduced the Agentic Decision Engine: A strategy-led workflow where AI agents help designers move from sense-making to decision-making. But understanding the concept is only the first step.

The real question is: How do you actually set one up?

This is a very practical guide for designers and strategists who want to move from theory to execution using available tools like ChatGPT or Claude. You can do this as a single designer, on your own, without asking for permission (Check your company data policies before sharing proprietary data with an open AI agent).

You do not need to start with complex systems or engineering teams.
You start small. You structure the workflow. And over time, you build not just one agent, but a system of agents working together to support decisions across your organization.

1. Start with the Decision

Do not begin with AI.
Begin with one decision that matters. If you are unsure where to start, pick a decision you are already involved in this week. It does not need to be perfect. It just needs to be real.

Ask:
• What decision are we trying to improve?
• Where are we operating with incomplete context?
• Where are we relying too heavily on intuition or fragmented data?

Write it clearly:
We need to improve the quality of [decision] by increasing the context available before it is made.

Then define:
• The business objective
• The expected outcome
• The key trade-offs

Also identify:
• Who makes the decision
• Who influences it
• Who executes it

If there is no clear decision owner, stop.
You do not yet have a real use case.

Finally, map how the decision is made today:
• Where are the gaps?
• Where is context missing?
• Where is the process manual or siloed?

That is where your agentic system will create value.

2. Define the Context the System Needs

Once the decision is clear, define the signals behind it.
Think in two layers.

• Core signals

The minimum data required to make the decision:
• Sales
• Inventory
• Pricing
• Operational data

• Expanded contextual signals

The signals that improve judgment:
• Weather
• Events
• Competitor activity
• Regional trends
• Behavioral patterns

Then map where these signals and data come from (see section 4 for your potential data sources):
• Internal systems
• External data sources
• Manual inputs

You are not building yet.
You are defining what your system needs to see.

3. Design the Agent System

Do not build one complex agent.
Start with simple roles: (see the complete classes of AI Agents in our previous article Agentic Decision Engine)

• Signal Agent

Collects and organizes inputs, surfacing what changed.

• Context Agent

Interprets patterns, identifying what matters.

• Recommendation Agent

Proposes actions, explaining trade-offs.

Optionally later:

• Monitoring Agent

Tracks outcomes, improving the system over time.
Treat each agent like a team member.

Define:
• Purpose
• Inputs
• Outputs
• Boundaries

Then design the output before anything else.

Ask: What should the decision-maker receive?

Here is a useful structure to start with:
• What changed
• Why it matters
• Options
• Recommended action
• Confidence level
• Risks or unknowns

If the output is not useful, the system will not be adopted.

What you are designing is not a single tool.
It is the foundation of an agentic system that can scale from one decision to many, from one designer to an entire team.

4. Configure Your First Workflow

This is where most teams get stuck. It is also where things become surprisingly simple.

You can set up your first version in ChatGPT, Claude, or similar tools in less than an hour.

If you can use ChatGPT, you can build your first agent system.

No engineering required.

• Step 1: Create your first agent (inside GPT or Claude)

Open your tool and create a new chat or custom GPT/project.

Give it a name:
Signal Agent, Context Agent, Decision Assistant…

Then paste a simple instruction like this:

You are a decision-support agent.
Your role is to analyze business signals and produce a short decision brief.

You do not make final decisions.
You expand the context before a decision is made.

Always return:
what changed
why it matters
risks
recommended actions
confidence level

Congratulations! You now have your first working AI agent!
It will not be perfect. That is expected. The goal is not to get it right on the first try, but to start improving how you structure decisions.

Note: Where Does the Data Come From?

At this stage, you do not need perfect or fully integrated data systems.
Start with what you already have access to.

Most designers can begin with a mix of:
Internal data:
• Dashboards (Tableau, Power BI, Looker)
• Spreadsheets (Excel, Google Sheets)
• CRM tools (Salesforce, HubSpot)
• Product analytics (Amplitude, Mixpanel)
• Internal reports or slide decks

External signals:
• Weather data (simple forecasts from public sources)
• Market trends (Google Trends, industry reports)
• Competitor activity (websites, pricing pages, newsletters)
• News and events (Google News, RSS feeds, social platforms)

Manual inputs:
• Stakeholder insights
• Field notes
• Customer feedback
• Operational updates from teams

At the beginning, it is completely acceptable to copy and paste data manually into your agent.

The goal is not automation.
The goal is to structure the decision and expand the context around it.

As the workflow proves valuable, data access can be automated later with engineering support.
If you can access it, you can use it. You do not need a perfect data pipeline to get started.

• Step 2: Feed it structured input (not random data)

Do not just paste raw data from the sources mentioned above.

Create a simple agent input block like this and reuse it every time:

Decision:
Weekly inventory allocation

Objective:
Improve availability while reducing excess inventory

Data:
Sales: [paste data]
Inventory: [paste data]
External signals: [paste weather, events, etc.]
Constraints: [paste issues or limitations]

Paste this into your agent. You now have a repeatable workflow.

• Step 3: Improve the output format

If the output feels messy, tighten it.

Add this to your prompt:
Keep the response under 200 words.
Be concise. Prioritize clarity over completeness.

This alone dramatically improves usability.

• Step 4: Create a second agent (Context Agent)

Open a new chat (or new GPT).

Paste:
You analyze decision summaries and identify what matters most.

Focus on:
key patterns
trade-offs
risks
uncertainty

Return:
top insights
key trade-offs
areas of uncertainty

Now copy the output from your first agent into this one.

You’ve just created a 2-step agent system.

• Step 5: Add a third agent (Recommendation Agent)

Create another new chat.

Paste:
You generate decision recommendations based on analysis.

Provide 2–3 options.
Explain trade-offs clearly.

Return:
recommended actions
why
risks
confidence

Now feed it the Context Agent output.

• Step 6: Run the full workflow manually

Your workflow is now:

1. Paste data → Signal Agent
2. Pass output → Context Agent
3. Pass output → Recommendation Agent
4. Review with human

No automation needed yet.

This is your Agentic Decision Engine v1.

• Step 7: Add simple guardrails

Update each agent with:

If data is missing, say so.
Do not invent information.
Clearly label uncertainty.

This is what makes the system trustworthy.

• Step 8: Save and reuse

• Save prompts in a doc
• Save your input template
• Reuse weekly or daily

Consistency is what makes this work.

• Step 9: Only automate once it works

Once this manual flow is useful:

Then connect to:
• Google Sheets
• Slack / Teams
• Zapier / Make

Do not automate before it works manually.
Once the workflow is working, the next step is to operationalize it.

You can now create as many agents as you need, based on your current and future needs. Imagine a team of AI agents working tirelessly and seamlessly to support and guide your decision-making.

From here, each new agent you add expands your system. Over time, this evolves into an orchestrated network of agents supporting multiple decisions across the organization. In effect, you are building an agentic layer around your decision-making, not just a single workflow.

5. Pilot, Measure, and Scale

Start small.

Choose:
• One decision
• One team
• One use case

Run a short pilot.

Keep a human in the loop:
Agent output → human review → decision

Measure:
• Time saved
• Quality of insights
• Decision confidence
• Business outcomes

Log everything:
• Recommendations
• Decisions
• Outcomes

Then improve:
• Remove noise
• Add missing signals
• Refine outputs

Only then should you scale.
This is where the shift happens: from a single workflow to a repeatable decision capability that teams can adopt and extend.

Expand gradually:
• More signals
• More users
• More decisions
• More automation

A Simple Way to Start This Week

If you want to begin immediately:

Day 1
Pick one decision and define the objective.
For example:
• Which users should we prioritize this week?
• Which feature should we improve next?
• Which customer segment needs attention?

Day 2
Create one agent and one input template

Day 3
Add a second agent and chain the outputs

Day 4
Add a recommendation agent and test scenarios

Day 5
Review with a stakeholder and refine

That is more than enough to get you started.

Designing How Decisions Are Made

The goal is not to build AI agents.
It is to improve how decisions are made.

Start with one decision.
Expand the context around it.
Keep a human in the loop.
Then scale.

Over time, what begins as a simple workflow becomes something much more powerful: A system of agents supporting decisions across teams, functions, and domains.

This is how designers move upstream.

From shaping experiences, to shaping services, to shaping how organizations think, decide, and act.

That is how an Agentic Decision Engine becomes real.

(Disclaimer: The companies, projects, and examples mentioned in this article are based on publicly available information and industry best practices. No proprietary or confidential information has been disclosed, and all references are for illustrative purposes only. This article does not represent insider knowledge or violate any non-disclosure agreements. Some AI tools could have been used for basic editing, research and visuals, but the insights and perspectives are entirely human.)

How Agentic AI Helps Designers Turn Strategy into Context-Driven Decisions

Most conversations today about AI are dominated by one obsession: Speed.

Faster research. Faster insights. Faster execution.

But speed has never been the real bottleneck in complex strategic decision-making. The real limitation has always been limited contextual insights.

Organizations rarely fail because they move too slowly. They fail because decisions are made with incomplete information, fragmented signals, and narrow perspectives.
Most organizations are trying to move faster, but the real advantage comes from seeing more clearly.

The true power of AI is not acceleration.
It is context amplification.

“AI will not replace human judgment. It will redefine the amount of context available before a decision is made.”

For the first time, organizations can generate, synthesize, and evaluate vast landscapes of information before making decisions. When used correctly, AI does not simply automate work. It expands the contextual field in which judgment occurs.

This article explores how agentic AI can support the journey from sense-making to decision-making, helping designers and strategists gather information, evaluate signals, generate recommendations, and justify strategic choices.

More importantly, it introduces a simple idea: AI should not be treated just as a productivity engine. It should be designed as a context engine built to enable strategy.

Strategy defines the direction > Designers frame the questions > Agentic AI gathers and interprets the signals needed to execute that strategy with greater clarity.

From Speed to Context

The early narrative around AI has mostly focused on productivity gains. Generate faster. Produce more. Automate work.

“Strategic work does not fail because it is slow. It fails because it lacks context. Speed without context simply drives organizations faster in the wrong direction.”

Poor business decisions usually emerge from:
• Incomplete information
• Fragmented signals
• Biased interpretation
• Weak connections between insights and strategic objectives

Today, AI changes this dynamic.

By generating and evaluating vast volumes of information, agentic systems allow designers to construct richer contextual landscapes before making decisions.

The result is not simply faster work.
It is better judgment.

Example: Retail Intelligence at Walmart

Walmart increasingly uses AI systems that monitor supply chains, consumer demand patterns, weather forecasts, and logistics signals simultaneously. Instead of reacting to individual data points, these systems build a contextual model of demand across thousands of stores. When weather patterns predict increased demand for certain products in specific regions, supply adjustments happen automatically.
The decision is not faster simply because it is automated. It is better because it is informed by a far broader context.

The Agentic Decision Engine

To understand how AI supports strategic work, it helps to think in terms of what we call the Agentic Decision Engine (ADE).

This engine combines AI agents, data intelligence, and strategic evaluation to help designers operationalize strategy and move confidently from sense-making to decision-making.

The strategy itself does not come from the agentic engine. It comes from human judgment, business objectives, and design leadership.

Rather than replacing human judgment, it expands the contextual intelligence available before a decision is made.

“The future of AI is not faster answers. It is deeper situational awareness.”

Instead of simply accelerating tasks, agentic AI expands the informational landscape that surrounds a decision.

The agentic decision engine unfolds in four stages:
1. Gathering information
2. Evaluating and contextualizing signals
3. Generating strategic recommendations
4. Justifying and validating decisions

Each stage increases the depth and clarity of context, allowing organizations to move from fragmented signals toward confident action.

In this sense, AI becomes less of an automation tool and more of a strategic intelligence layer embedded inside the organization.

Agentic AI can support a structured decision flow composed of four core stages:

1. Gathering Information

Once strategic objectives are defined, the first role of AI agents is expanding access to the data required to pursue them. This includes:
• Market intelligence
• Customer signals
• Operational data
• Competitive analysis
• Cultural and geopolitical context

At this stage, the goal is purely information breadth.
AI agents collect signals across multiple sources and platforms, helping designers move beyond limited datasets.

We will explore the seven classes of AI agents later, but two types are particularly relevant at this stage:

• Simple Reflex Agents
  Agents that respond to immediate inputs using predefined rules.
• Model-Based Agents
  Agents that build an internal model of the environment to interpret new information more intelligently.

Together, these agents help construct the initial knowledge landscape.

Example: Spotify’s Music Discovery Intelligence

Spotify uses AI systems that constantly gather signals from listening behavior, playlist interactions, skip rates, and global listening patterns.
Simple agents react immediately to listening signals while model-based agents build complex user taste profiles.
This continuous information gathering allows Spotify to understand evolving music preferences at a global scale. The result is not simply music recommendations. It is an evolving map of cultural taste.

2. Evaluating and Contextualizing Information

Once information is gathered, the next challenge is interpretation.

Raw data alone does not create insight. Strategic intent determines which signals matter and which can be ignored. AI agents can help evaluate patterns, detect anomalies, and organize information into meaningful structures.

Here two additional types of agents become critical:

• Goal-Based Agents
  These agents evaluate information based on defined objectives. They help determine which signals matter and which do not.
• Utility-Based Agents
  These agents compare potential outcomes and prioritize the options that maximize value.

In strategic design, this stage transforms scattered signals into coherent context. This is where sense-making happens.

Example: Healthcare Diagnostics at Mayo Clinic

The Mayo Clinic uses AI-assisted diagnostic systems that analyze patient data, imaging, research literature, and historical medical records.
Goal-based agents evaluate possible diagnoses relative to patient symptoms. Utility-based agents help prioritize treatment paths based on outcomes and risks.
Doctors still make the final decisions. But AI dramatically improves the contextual landscape in which those decisions are made.

Example: Central Banks Interpreting Economic Signals

Central banks have traditionally relied on economic reports that appear weeks or months after economic activity occurs.
Today, institutions such as the Bank of England and the Federal Reserve are experimenting with AI systems that analyze real-time economic signals.
These systems ingest massive streams of information, including shipping data, satellite imagery of industrial activity, retail transactions, job postings, and financial market signals.
Goal-based agents evaluate how these signals relate to macroeconomic targets such as inflation, employment, and productivity. Utility-based agents help policymakers explore possible policy responses and their expected outcomes.
Human policymakers still make the final decisions. But AI dramatically expands the contextual picture in which those decisions occur.
Instead of relying only on lagging historical indicators, economic leaders can begin interpreting emerging economic patterns as they unfold.

3. Preparing Strategic Recommendations

Once context is clear, AI can assist in building structured recommendations.

This is where agentic systems begin generating potential pathways forward, including:
• Service innovations
• Operational improvements
• Market expansion strategies
• Ecosystem partnerships
• Technology integration opportunities

At this stage, AI agents help generate strategic options while designers frame the problem, evaluate trade-offs, and determine which directions align with the organization’s strategy.

The key business value often emerges through three capabilities:
• Automating repetitive tasks: Reducing operational friction and freeing human time for strategic thinking.
• Learning and adapting: Learning agents refine recommendations as new information appears.
• Working across platforms: Agentic systems synthesize data across tools, departments, and systems.

This creates recommendations that are more informed and more adaptive.

Example: Automotive Design at BMW

BMW uses AI-driven simulation environments to explore thousands of design variations and manufacturing options before a vehicle reaches production.
AI systems analyze aerodynamic performance, material constraints, cost models, and sustainability targets. Design teams review the generated options and select the most promising directions.
Instead of replacing designers, AI expands the space of possibilities designers can explore.

4. Justifying the Decision

A strong recommendation must ultimately lead to a decision.

AI can support decision justification by mapping proposals to strategic goals, constraints, and expected outcomes.

This stage focuses on answering critical questions:
• What problem are we solving?
• What strategic objective does this support?
• What value does this create?
• What risks remain?

By structuring these relationships, AI agents help make decisions more transparent and defensible.

The role of AI here is not to replace judgment but to strengthen the logic behind it. The final decision remains a human responsibility tied to strategic accountability.

Example: Netflix Content Investment

Netflix relies heavily on data intelligence when deciding which original content to fund.
AI models analyze viewing patterns, genre preferences, regional demand, actor popularity, and storytelling trends. These insights do not dictate the decision. Instead they help justify investments by linking creative ideas to measurable audience signals. Human creative leadership remains central, but the strategic rationale becomes clearer.
These capabilities rely on several foundational agent architectures that designers should understand at a conceptual level.

NOTE: If you’re wondering how to actually build and deploy this in practice, we’ve put together a simple step-by-step guide on setting up your own Agentic Decision Engine.

Seven Types of AI Agents Designers Should Understand

To fully leverage agentic AI, designers should understand the main families of agents that power these systems:

• Simple Reflex Agents
  Operate through predefined rules and immediate responses. These agents react directly to specific inputs without considering past events or broader context. If a condition is met, a corresponding action is triggered, much like a basic automation rule responding instantly to a signal.
• Model-Based Agents
  Maintain an internal representation of their environment to make more informed decisions. Instead of reacting only to immediate inputs, these agents track how conditions evolve over time and use that internal model to interpret new information within a broader context.
• Goal-Based Agents
  Evaluate possible actions based on clearly defined objectives. Rather than simply reacting to conditions, these agents consider different paths forward and choose the one most likely to achieve a specific goal, such as improving efficiency, reducing risk, or reaching a target outcome.
• Utility-Based Agents
  Assess multiple possible outcomes and select the option that delivers the greatest overall value. These agents weigh trade-offs between competing factors such as cost, speed, performance, or risk in order to determine which decision produces the best overall result.
• Learning Agents
  Continuously improve their performance by analyzing feedback and new data. Over time, these agents adapt their behavior, refine predictions, and update their models, allowing them to respond more effectively as environments and conditions change.
• Hybrid Agents
  Hybrid agents combine multiple reasoning mechanisms within a single system. For example, an agent may include simple reflex responses for fast reactions, a model-based component to understand context, and a learning module that improves performance over time. The goal of a hybrid architecture is to balance speed, adaptability, and strategic evaluation within a single decision system. In practice, many modern AI systems are hybrid because complex environments require more than one type of reasoning.
• Hierarchical Agents
  Hierarchical agents organize decision-making across multiple levels of control. Higher-level agents define goals or strategic direction, while lower-level agents execute specific tasks required to achieve those goals. Each layer focuses on a different level of abstraction, allowing complex problems to be broken down into manageable decisions. For example, a strategic agent may decide to optimize supply chain resilience, while subordinate agents manage routing, inventory adjustments, and logistics execution.

Understanding these models helps design strategists build better AI-assisted workflows.

Linking Agentic AI to Strategic Objectives

Technology alone does not create value.
Value appears when technology is aligned with strategy.

“Strategy defines the destination. Agentic AI helps organizations navigate the terrain.”

Before deploying AI systems, organizations should answer several strategic questions:
• What are the biggest opportunities we face?
• What obstacles slow down our decisions?
• Where could efficiency unlock scale?
• Which strategic initiatives require stronger intelligence?

Once these questions are clear, AI can support the organization in:
• Unlocking operational bottlenecks
• Accelerating strategic initiatives
• Scaling intelligence across teams
• Improving decision quality

In this sense, agentic AI becomes a form of organizational cognition. It extends how institutions perceive, interpret, and act on complex environments.

Example: Amazon Logistics Optimization

Amazon uses AI systems to orchestrate global logistics across warehouses, transportation networks, and delivery routes. Instead of optimizing isolated operations, agentic systems continuously balance cost, speed, capacity, and demand across the network. The result is a logistics ecosystem capable of adapting dynamically to changing conditions.
AI becomes a strategic enabler rather than simply a tool.

Example: Geopolitical Risk Monitoring in Global Supply Chains

Global companies now operate in an environment shaped by geopolitical instability, trade fragmentation, and regulatory shifts.
Logistics companies such as Maersk and DHL deploy AI-driven intelligence platforms that monitor thousands of signals across the global system, including shipping flows, political developments, sanctions regimes, energy markets, and regional conflict indicators.
These systems continuously analyze news sources, trade data, port congestion, and diplomatic announcements. When signals suggest potential disruption, companies can simulate alternative supply chain routes and sourcing strategies.
Instead of reacting after disruption occurs, organizations gain the ability to anticipate geopolitical friction and reposition supply networks in advance.
In this environment, AI becomes a strategic sense-making layer for navigating an increasingly complex global economy.

Strategy First, Technology Second

The biggest mistake organizations make with AI is starting with the technology. They experiment with tools before defining strategic intent.

The correct order is the opposite.
First define:
• The strategic objective
• The expected outcomes
• The decision challenges
• The business value

Only then should technology be deployed to support those goals.
AI should amplify strategy, not define it. But what does this look like in practice?

From Strategy to Execution: A Simple Example

To make this concrete, consider a fictional retail brand facing declining in-store performance.

A service designer is tasked with improving demand forecasting and reducing stockouts across regions. The team defines a clear objective: Improve product availability while reducing excess inventory.

From there, the designer frames the problem:
• What signals are we missing?
• Where are decisions being made with incomplete context?
• Which teams are operating in silos?

AI agents are deployed to gather and synthesize signals across the system:
• Real-time sales data
• Regional weather patterns
• Local events and demand spikes
• Supply chain constraints
• Competitor pricing signals

Model-based and learning agents build a dynamic view of demand across regions.

Goal-based and utility-based agents evaluate trade-offs between cost, availability, and speed.

The system begins generating recommendations for inventory allocation and replenishment strategies.

At this stage, the designer and business stakeholders review the outputs, align them with strategic priorities, and validate the direction.

Finally, the work is operationalized.

The designer collaborates with engineering teams to translate these capabilities into production systems:
• Defining data pipelines
• Specifying agent behaviors
• Integrating with existing platforms
• Establishing feedback loops for continuous learning

The result is not just a model or a dashboard. It is a decision system embedded into the organization, continuously improving how decisions are made.

Where to Start with Agentic AI

For many designers and strategists, the question is not what agentic AI is, but how to actually begin.

The starting point is simpler than it appears.

You do not begin by building complex AI systems.
You begin by identifying one decision worth improving.

• Step 1: Identify a High-Value Decision

Focus on a decision that is:
• Repeated frequently
• Currently based on incomplete information
• Impactful to business performance

For example: Inventory allocation, pricing adjustments, or customer segmentation.

• Step 2: Map the Signals Behind the Decision

Before thinking about AI, map the inputs:
• What data informs this decision today?
• What signals are missing?
• Where are the blind spots?

This defines what your future agents will need to observe.

• Step 3: Start with Off-the-Shelf Agents

You do not need to build everything from scratch. Most organizations begin by using existing tools:
• LLM-based agents (OpenAI, Anthropic, etc.)
• Workflow automation platforms (Zapier, Make, etc.)
• Data platforms (Snowflake, Databricks)
• BI tools with AI layers

NOTE: See our simple step-by-step guide on setting up your own Agentic Decision Engine.

At this stage, agents can be simple:
• Monitoring signals
• Summarizing data
• Generating recommendations

Think of this as augmenting the decision, not automating it.

• Step 4: Define Agent Roles (Not Just Tools)

Instead of thinking in terms of tools, think in terms of roles:
• A signal agent gathers and aggregates data
• A context agent interprets patterns
• A decision-support agent generates recommendations

This aligns directly with your Agentic Decision Engine.

• Step 5: Collaborate with Engineering to Scale

Once the value is proven, the system can be industrialized.

This is where designers partner with engineering to:
• Formalize data pipelines
• Define agent behaviors and logic
• Integrate with operational systems
• Establish monitoring and feedback loops

At this stage, the system evolves from a prototype into a decision infrastructure.

• Step 6: Decide When to Build vs Buy

A simple rule:
• Buy when the capability is common (summarization, prediction, automation)
• Build when the capability is core to your competitive advantage

Most organizations start by buying and progressively build where differentiation matters.

Final Thought

The goal is not to build AI agents for their own sake. It is to improve how decisions are made.

Start small. Focus on one decision. Expand from there.

The organizations that win will not be the ones that adopt AI the fastest, but the ones that redesign how decisions are made.

The Age of Contextual Intelligence

Agentic AI represents a profound shift for designers and strategists.
Not because it makes work faster. But because it expands the contextual intelligence available before decisions are made.

By gathering vast landscapes of information, interpreting patterns across systems, generating strategic options, and supporting decision justification, AI strengthens the entire chain between insight and action.

This shift carries an important implication for designers.

As AI becomes embedded in decision environments, designers are no longer only shaping experiences or services. Designers are increasingly shaping systems of intelligence that help organizations interpret complexity and execute strategy with greater precision. In many organizations, designers are quietly becoming architects of decision environments, structuring how intelligence flows from data to action.

The role of design begins to move upstream.
From designing interactions to designing services, to designing decision ecosystems.

In a world defined by geopolitical turbulence, economic volatility, and accelerating technological change, the organizations that succeed will not simply move faster. They will see more clearly.

And in that future, the most powerful use of AI will not be automation.
It will be deeper contextual awareness.

(Disclaimer: The companies, projects, and examples mentioned in this article are based on publicly available information and industry best practices. No proprietary or confidential information has been disclosed, and all references are for illustrative purposes only. This article does not represent insider knowledge or violate any non-disclosure agreements. Some AI tools could have been used for basic editing, research and visuals, but the insights and perspectives are entirely human.)

NASA and modern Service Design demonstrate that operational resilience is built by confronting mission-critical failure points.

There was a time when people said the instant you have a plan B is the instant you’ve given up on plan A.

That line shaped entire generations of leaders. It rewarded focus, single-mindedness, and a belief in linear progress. It worked when the world had margins, buffers, and predictable cycles.

But that world is gone.

Today, clinging to a plan A without designing its corresponding unhappy path is not confidence. It is negligence.

In a global landscape defined by geopolitical tension, ecological disruption, digital fragmentation, and supply chain fragility, treating the happy path as the main path is not optimism. It is a structural risk disguised as strategy.

I’ve seen this firsthand throughout a decade of strategic and service design work. On every major project, the moments that defined the outcome were never on the happy path. They lived in the cracks: the failure states, the drop off points, the workarounds, the personal hacks, the moments when reality diverged from the immaculate journey map. The teams that succeeded were not the ones with the most beautiful plan A but the ones with the most resilient, well-designed plan B, C, D, and well, sometimes E.

This article is about why the unhappy path is now more important than ever, why ignoring it is dangerous, and how you must build it into the core of every strategy and decision you make.

The Shiny Object Delusion: Why the Happy Path Is the Most Dangerous Path

We are designing services inside a world that behaves nothing like the world most journeys were built for. Markets once followed patterns. Now they follow shocks. Geopolitical blocs realign, climate instability disrupts logistics, digital systems fragment across borders, supplier networks buckle, and cultural contexts shift faster than strategies can adapt.

Yet many leaders still design with the logic of a stable era. They optimize for best-case scenarios. They chase delight. They measure flow efficiency while ignoring failure thresholds. The result is a brittle ecosystem of experiences that collapse the moment something deviates from ideal conditions.

Every year brings a new technological promise, the next big thing destined to revolutionize the customer experience. And in the pursuit of the shiny object, companies overlook the far less glamorous realities that determine whether an experience survives contact with the real world. I have watched organizations spend months and years perfecting the ideal customer journey while leaving entire failure states unaddressed.

The patterns are painfully familiar:
• No recovery flow when authentication breaks.
• No redundancy when a logistics partner goes offline.
• No alternative journey when a digital channel fails.
• No operational slack to absorb a surge or shock.

This is not innovation. It is building on sand.

Whenever our teams lead through future state experience blueprinting, the breakthrough moment rarely comes from refining the happy path. It comes from surfacing the unloved steps, the off-ramps, the contingencies no one planned for. Those are the places where real-world strategy begins.

How a Single Failure Point Can Collapse an Entire Experience

A missing unhappy path is not an inconvenience. It is a systemic weakness. When failure states are not designed, a single breakdown can trigger a chain reaction. Trust erodes. Operations cascade. Staff improvise. Customers churn. Regulatory exposure increases.

A global telecom project I led became the clearest illustration of this. The company had engineered a beautifully choreographed experience made of 138 journey touchpoints. Months of design, research, operational planning, and orchestration went into weaving those physical, digital, and virtual steps into a seamless flow. But the entire experience depended on touchpoint number four: An automated email containing a validation code the customer needed to present in the retail shops.

When that email failed to arrive, everything came apart. Fast.

Technical errors, network delays, spam filters, or simple human error could all block that message. And when it did not arrive, the remaining 134 touchpoints instantly became utterly useless. Retail staff had no fallback protocol. Customers had no alternative path. The system had no redundancy. A multimillion-dollar customer experience hinged on a single fragile interaction. The unhappy path had never been addressed nor designed, and the experience collapsed under the weight of its own optimism.

Unfortunately, this is not an anomaly. It is how most systems are still built today.

How NASA Designs for Worst Case Scenarios

The Webb Space Telescope succeeded not because everything went right but because NASA designed for everything that could go wrong. Teams identified more than three hundred potential failure points, every single one capable of ending the entire mission with a sobering loss of $10 billion invested over two decades of development. Every hinge, latch, mirror segment, and sunshield membrane had a defined contingency strategy. Webb launched to a location in space beyond the reach of any repair mission, making it essential to engineer solutions for every possible scenario in advance. The unhappy path became the design philosophy.

As one NASA engineer put it, “Prior to launch, we had 344 single-point failures. A single-point failure meant if this one thing fails, we could potentially lose the whole mission.”

This is the mindset of an organization that treats fragility as a fundamental reality. When the margin for error is measured in microns and mission lifetimes, every scenario must be examined and resolved long before the system leaves the ground.

Webb did not succeed because the happy path held. It succeeded because the unhappy path was engineered with absolute rigor. While many companies chase seamless delight, NASA confronts seam-full complexity. Their work proves that resilience is not luck. It is the result of engineering for failure before it happens.

NASA embraces what most organizations resist. In its engineering culture, the idea that failure is an option is not a reckless slogan but a mandate for preparedness. Every mission is a stack of risks, interdependencies, and unknowns. The only irresponsible approach is pretending otherwise. In NASA’s cleanrooms and control centers, teams rehearse breakdowns repeatedly because they know resilience is built by confronting what can fail, not by assuming success.

This is the mindset modern organizations now need most.

The Unhappy Path as a Strategic Asset

Here is where the narrative turns. The unhappy path is not a fallback strategy or a pessimistic exercise. It is not a defensive posture. It is a source of intelligence. It reveals assumptions, exposes interdependencies, and forces clarity long before reality does. It is the place where the hidden architecture of a service finally comes into view.

For years, I have watched teams transform entire programs after a single unhappy-path weakness came to light. One revealed fragility can sharpen intent, reset priorities, and surface work that would otherwise remain invisible until it breaks something expensive or irreversible. The unhappy path is where real leadership shows up, because it forces teams to address what they would rather ignore and to invest in the potential safeguards that never truly feel necessary until the moment they are.

And the lessons become clear when you look at what breaks and what can still be saved.

1. The Ticketing Meltdown: When Scale Turns Against You

A global event organizer built a ticketing system optimized for peak demand on paper but not in reality. On launch day, authentication slowed, customers refreshed their screens, and the system interpreted the activity as suspicious. Thousands were locked out instantly. With no fallback channel, everything dead-ended. Call centers collapsed. Social sentiment exploded. Regulators intervened. What should have been a victory became a global case study in how a single unplanned failure state can devastate an entire brand moment.

2. The Retail Pivot: When a Failure Becomes a Better Design

On another project, a retail brand’s new appointment system collapsed repeatedly. Instead of treating the failure as a crisis, the design team treated it as feedback. Customers improvised. Small groups formed. Staff stepped out from behind the counter to guide people manually. Conversations unfolded. The team realized the human choreography mattered more than the digital precision. They rebuilt the experience around hosted arrival rather than automated scheduling. A failure became a breakthrough.

3. The Banking Outage That Exposed a Hidden Truth

A major bank once experienced a three-hour outage in its mobile app. Customers could not check balances or transfer funds. Panic spread. But the real collapse was internal: no one had rehearsed a communication protocol for service failure. Teams debated wording. Legal slowed decisions. Executives delayed acknowledgment. The unhappy path had never been designed, and the reputational damage continued long after the system recovered. The technical outage lasted hours. The trust outage lasted years.

4. The Airline Grounding That Should Never Have Happened

A leading airline grounded thousands of flights when a single legacy system failed to relay updated crew scheduling data. The entire network froze. Travelers slept on airport floors. Competitors capitalized. Analysts estimated hundreds of millions in losses. The unhappy path was not hidden. It was documented. But it had never been rehearsed, stress-tested, or prioritized. One outdated system held a modern global operation hostage.

5. The Hospital That Turned Crisis Into Strength

A hospital’s patient-intake system went offline during a regional emergency. Staff quickly shifted to manual intake processes they had practiced but never had to use. Clipboards appeared. Runners moved information between departments. Temporary triage stations formed. The process looked messy but worked flawlessly because the unhappy path had been designed, drilled, and owned. After the crisis, the hospital integrated these learnings into a new hybrid model that improved care long after systems came back online.

Why These Stories Matter

Each example reveals the same truth: Systems do not collapse because the happy path failed. They collapse because the unhappy path did not exist at all.

The difference between disaster and resilience is rarely the technology or the strategy itself. It is the preparation for the worst, the imagination to anticipate failure, and the leadership required to design for it. When organizations learn to work inside the uncomfortable space of potential breakdown, they uncover the insights that make everything else stronger.

A Practical Framework for Building Resilient Experiences

To design for reality instead of fantasy, you need a different architecture. One built on discipline rather than hope, clarity rather than assumption. A resilient service begins with a systematic view of what can fail and how the system must respond.

The core practices are straightforward:
• Map systemic pressures, not just steps
• Identify failure nodes at every touchpoint
• Design meaningful redundancy
• Create operational slack
• Test like an adversary
• Build sensing mechanisms
• Codify the choreography of recovery

This is the blueprint of resilience. It is not glamorous. It is not fast. But it is the only way to design services and experiences worthy of the world they must operate in.

And when organizations commit to this work, something powerful happens. Trust grows. Stability increases. Loyalty deepens. The brands that thrive in the coming decade will not be the ones with the sleekest journeys or the most seductive interfaces. They will be the ones that offer reliability in an unreliable world, the ones customers return to because they can count on them when things go wrong, not just when things go right.

Trust is no longer earned by perfection. It is earned by preparedness and recovery. It is earned by designing for the full spectrum of human and systemic experience. When you design the unhappy path well, you do more than prevent failure. You create a strategic advantage that is difficult to copy because it becomes embedded deep within the operating logic of the organization.

This is the work that turns fragility into strength. This is the work that builds resilience. This is the work that endures.

The Real Plan

The old saying claimed that having a plan B meant giving up on plan A. Today, refusing to build a plan B is the real surrender. It is surrendering to delusion. It is surrendering to fragility. It is surrendering to a worldview built for a past that no longer exists.

The world has changed. Our work must change with it.

If your service can only perform when everything goes right, it is not ready for the era we now live in.

It is time to design responsibly. It is time to design resiliently. It is time to place the unhappy path at the center of strategy, design, and leadership.

This is not the backup plan.
This is the real plan.

(Disclaimer: The companies, projects, and examples mentioned in this article are based on publicly available information and industry best practices. No proprietary or confidential information has been disclosed, and all references are for illustrative purposes only. This article does not represent insider knowledge or violate any non-disclosure agreements. Some AI tools could have been used for basic editing, research and visuals, but the insights and perspectives are entirely human.)

As a new global architecture emerges, the next era will belong to organizations that can interpret the geopolitical shifts, re-architect themselves, and build the resilience the new century will demand.

A world era rarely ends in a single moment. It ends with a shift.

Just as Europe did not wake up one morning and suddenly find itself in the Renaissance, world orders rarely announce their transformation. The Middle Ages gave way slowly, through structural signals, quiet innovations, and subtle fractures in the old architecture, long before anyone declared the arrival of a new era.

A subtle pivot in posture that reveals something deeper: The architecture holding the current system together has reached its limit.

And last week, something unusually quiet happened.
The reset began.
The twenty-first century announced itself.
Not with spectacle, but with a structural signal that a world completely different from the one eight billion people grew up in is arriving.

The United States’ 2025 National Security Strategy (NSS) was that signal.
Not because it was political.
Not because it was ideological.
But because it is structural.

It acknowledges that the world we all grew up in no longer aligns with the world taking shape today.
It signals the beginning of the end of eight decades of the post-WW2 global operating system. And it forces every nation, every institution, every organization to confront a truth we can no longer ignore:

“The twenty-first century is emerging, and the old world can no longer contain it.”

As we’ve explored through Geostrategic Design, the transition from one global operating system to another is never announced loudly. It arrives through structural signals, subtle fractures, and shifts in posture that most institutions notice only in hindsight. What we discussed months ago is now unfolding in real time.

We have crossed into a new era of global design, where the future will be built, and for once, not inherited.

If you lead teams, design systems, build strategy, or steward institutions, this is the moment to re-evaluate the assumptions you inherited.

The New World Is Emerging in Plain Sight

The earliest signals of a new world rarely arrive with fanfare. They surface quietly, in the gaps between old assumptions, long before institutions feel their force. Every world order carries the seeds of its own exhaustion, and those shifts become visible only when the pace of change exceeds what the old architecture can hold.

The twentieth-century system we inherited was built for a slower age;
for industrial rhythms, predictable alliances, linear progress, and clear borders.

But the world emerging through it moves faster, spreads wider, and behaves more unpredictably. It is shaped by code, networks, autonomous systems, distributed production, and supply chains that can buckle under political pressure.

When an architecture no longer fits the era it serves, it strains and eventually gives way, not suddenly, but through a series of subtle, accumulating signals.

The U.S. NSS is not the cause of this transition. It is the acknowledgment that the transition has already begun, and that the world is reorganizing itself accordingly. At blinding speed.

Moments like this are rare. Exceptionally rare. And for all the difficulty ahead, there is something extraordinary in this moment. Few generations ever realize their era is shifting while they are still living in it. We are witnessing a transformation that most only recognize generations later.

The First Domino Falls

This U.S. strategy announcement marks a fundamental shift in global posture.
The United States is stepping back from its long-standing role as global manager and moving into a selective, interest-driven form of leadership. That single pivot is reorganizing the entire world.

1. The Managerial Era Ends

For eight decades, America played the role of stabilizer.
Regions now face a future where they must define their own strategic destinies, no longer relying on a singular global anchor.
This is how new worlds begin.

2. Every Major Power Recalculates

From Europe recalibrating its security identity, to China adjusting its rise, to India accelerating its ambitions, to Africa and Latin America reassessing alliances; the global chessboard is no longer stable.
It is fluid, contested, and open.
The first domino has fallen. Others are already moving.

3. The Sovereign-Resilience Era Emerges

The old era optimized for efficiency. The new era optimizes for endurance.
Nations are shifting toward sovereignty, industrial revival, secure supply routes, technological autonomy, and cultural cohesion.

The next world order will not be defined by universal integration.
It will be defined by resilience engineered for volatility.

The Fifth Industrial Revolution: A Geostrategic Shift

Just as the Fourth Industrial Revolution (4IR) gives way to the Fifth (5IR), the world’s strategic architecture is shifting, from connected digital systems to autonomous intelligent systems.

The Fifth Industrial Revolution is often mistaken for a wave of new technologies. In reality, it is something deeper: A redesign of how value is created, how power is distributed, and how systems operate.

Unlike earlier revolutions sparked by single inventions (steam engine, assembly line, microprocessor), the Fifth is emerging from the convergence of many forces at once: Autonomous and intelligent infrastructure, supply-chain sovereignty, energy transformation, synthetic labor and cognition, new materials and manufacturing and the fusion of digital and physical systems.

But this convergence is not simply technological.
It is geopolitical.

As the NSS makes clear (intentionally or not) the next century will be shaped by sovereignty over capabilities, resilience of production, and control over the systems nations depend on.
These are not tools. They are the foundations of the world’s next operating system.

The myth is that 5IR is about speed. The reality is that 5IR is about architecture. The nations and organizations that thrive will be those able to: Build autonomous infrastructure, re-industrialize with intelligent and flexible production, design planetary-scale risk systems, embed intelligence as structural capability and create institutions that learn and self-correct.

This is no longer a competition for market share.
It is a competition for system share.

And here the U.S. NSS aligns with the deeper contours of 5IR, not through politics, but through its structural reading of the world: Resilience over efficiency, autonomy over interdependence, concentrated capability over diffuse dependency, intelligence as infrastructure and sovereign technological power.

These define the shift from:
• Production economies > Capability economies
• Globalized networks > Sovereign techno-systems
• Incremental change > Structural redesign

The U.S. NSS reflects a world currently reorganizing around new sources of power: Intelligence, infrastructure, autonomy, and design.

5IR is the world the twenty-first century is emerging into, a world built not on continuity, but on re-architecture, a world where design strategy becomes a blueprinting discipline, shaping how systems learn, adapt, and interconnect. A world that rewards those who design systems that can survive volatility, adapt quickly, and operate at the scale of nations.

This is why the stakes feel different now...
Because they are.

What This Means for Companies and Organizations

This is where structural shifts become personal.
The architecture of the world determines the architecture in which companies must operate.

The turbulence hitting nations today is already reshaping every industry on the planet. Organizations designed for the old century are colliding with the realities of the new one. Sometimes painfully.

1. The Age of Linear Planning Is Over

20th Century leaders were taught to expect stable markets, consistent demand, and predictable planning cycles.

Those assumptions are now liabilities.
Disruption is continuous, regulations fragment, supply routes break, and AI accelerates faster than governance.

> Toyota’s Wake-Up Call

Toyota perfected just-in-time manufacturing until microchip shortages exposed its fragility. The model that once made Toyota unstoppable became its greatest vulnerability.
Toyota rethought its sourcing architecture not for efficiency, but for durability, a shift that reflects the broader need for service design approaches that consider end-to-end system resilience, because efficiency collapses under systemic volatility.

2. Designers Will Become Systems Architects

Design is no longer the craft of shaping touchpoints.
It is the craft of shaping systems, systems that can survive geopolitical turbulence.
Designers must now think like strategists, technologists, diplomats, economists, and futurists.

> Maersk’s Reinvention

Maersk realized that shipping lanes alone could no longer guarantee value.
Chokepoints, tariff wars, and regional instability turned routes into liabilities. So Maersk reinvented itself not as a shipping company, but as a global logistics and supply-chain ecosystem.

They stopped designing journeys.
They started designing resilience.

This is where design strategy evolves into enterprise-level systems design, shaping not just interactions but entire operational ecosystems.

This is design strategy operating at geostrategic scale.

This is the organizational manifestation of Geostrategic Design: Companies are no longer competing within industries, they’re competing within global systems shaped by forces far beyond their four walls.

Organizations will need talent capable of:
• Designing multi-node supply networks
• Building intelligence-augmented services
• Creating trust architectures for fragile digital ecosystems
• Developing sovereign-ready platforms
• Crafting modular operating systems that flex under pressure

This is what Design looks like when the world is being rewritten.

3. Customers Will Value Stability Over Convenience

In the old era, delight differentiated brands.
In the new era, dependability becomes the ultimate currency.

> AWS’s Invisible Power

AWS does not sell delight. It sells uptime.
It sells the infrastructure that survives the unexpected.

AWS became a civilizational backbone by mastering one craft: Operational resilience at scale.

Customers in the new world will reward companies that deliver:
• Stability under stress
• Secure and sovereign data flows
• Transparent supply provenance
• Adaptive, intelligent services
• Systems that do not break

Resilience is no longer a back-end feature. It has become a front-end value proposition.

How Designers & Leaders Need to Adapt in a World Rewritten

This is where awareness becomes action.
We have crossed a threshold.
The world that shaped our lives no longer resembles the world we now face. Organizations must stop optimizing for the world that was, and begin designing for the world that is emerging, a shift that elevates strategic design and service design from support functions to critical core capabilities.

Every model, economic, operational, cultural, and technological, must be redrawn.

Leaders must now think like nation-states:
• What capabilities must we build internally to survive disruption?
• How do we ensure autonomy in a fractured world?
• Which alliances strengthen us and which dependencies weaken us?
• How do we integrate intelligence into every workflow?
• How do we design services that endure systemic turbulence?

The signs that were once faint are now unmistakable.
Here are the foundational moves every leader and designer must take as the twenty-first century emerges into form:

1. Shift From Projects to Systems

Designers must stop thinking in terms of isolated initiatives and start thinking in ecosystems.

Ask:
• What are the interdependencies?
• Where are the chokepoints?
• Where does this system break under stress?

The world ahead will reward those who can map, model, and strengthen systems model using strategic design tools, not just improve experiences.

2. Build for Variability, Not Stability

Everything designed for predictability will fail under volatility.

Organizations must:
• Add fallback modes
• Introduce redundancy
• Create modular architectures
• Design services that can flex under pressure, a hallmark of next-generation service design.

Stability now comes from adaptability.

3. Rearchitect for Sovereignty and Autonomy

Every strategy must include questions once reserved for nation-states:
• What capabilities must we own?
• What must we secure?
• What must we decentralize?
• What must we make resilient?

Leaders must reduce fragile dependencies and build structural independence into their systems.

4. Embed Intelligence Into Every Workflow

AI is not a tool. It is a force multiplier.
Organizations must redesign themselves around intelligence, not as an add-on, but as the cognitive infrastructure of the enterprise.
• Intelligent services.
• Intelligent operations.
• Intelligent decision-making.

Those who refuse will be outpaced by those who rewire their companies for synthetic cognition.

5. Build Design Capabilities That Operate Like Strategy

Service designers must now sit where strategists sit.
Strategists must now think like systems designers.

The two disciplines are converging because the new world demands it. Bring designers into: Portfolio decisions, capability planning, supply-chain strategy, resilience engineering, organizing models...

If design remains a downstream function, the organization will remain a downstream player in the new century.

6. Strengthen the Cultural Core

In a volatile world, culture becomes a strategic asset. Not slogans.
Not posters. Actual internal cohesion.

Teams must share:
• Clarity of purpose
• Shared language
• Decision-making principles
• Tolerance for ambiguity

The future belongs to organizations that can think together under pressure.

7. Rethink Value: From Delight to Dependability

The next competitive frontier is not delight. It is continuity.

Leaders must ask:
• Can we deliver through disruption?
• Through outages?
• Through geopolitical turbulence?
• Through supply-chain instability?

Companies that promise delight will be replaced by companies that promise endurance.

8. Develop a New Sensemaking Muscle

Leaders must cultivate a new literacy: Geopolitical literacy, technological literacy, and systemic awareness. Not to become experts, but to avoid designing blindfolded.

The world is shifting too quickly for decisions made from habit.
Leaders must become sensemakers before they become decision-makers.

This is not a checklist. This is the beginning.

These steps will prepare leaders and designers to operate inside the new global architecture, to build the systems, services, capabilities, and cultures that can survive and thrive in a world defined by volatility, intelligence, and geopolitical redesign.

Standing at the Threshold of a New World

The U.S. NSS is not the future.
It is the signal that the future has begun.

An old world is ending.
A new world is beginning.
The twentieth century is quickly fading behind us.
The twenty-first century is emerging as a new world of its own.

We now stand in the liminal space between global architectures, a very rare moment in history when institutions, markets, technologies, and alliances are all being rewritten at once.
A moment when the old operating system has reached its limit, and a new one is taking shape in real time. Our time.

What we build now, our systems, our cultures, our institutions, will define the character of the world to come. For once, this is not a transition we will inherit. It is one we will design.

Leaders, designers and strategists do not have the luxury of watching from the sidelines. We hold the tools that shape systems, steer complexity, and give form to what does not yet exist.

What we choose to build in this era will echo for decades.

The reset has started.
The first domino has fallen.
The twenty-first century is stepping forward and will absolutely not wait.

(Disclaimer: The companies, projects, and examples mentioned in this article are based on publicly available information and industry best practices. No proprietary or confidential information has been disclosed, and all references are for illustrative purposes only. This article does not represent insider knowledge or violate any non-disclosure agreements. Some AI tools could have been used for basic editing, research and visuals, but the insights and perspectives are entirely human.)

The New Geometry of Power: How Strategic Design Is Rewriting Power, Readiness, and Control from Earth to Space.

The Sky No Longer Belongs to Dreamers

A few weeks ago, as I stood atop Mount Haleakalā in Maui, I looked toward the U.S. Space Force’s Maui Space Surveillance Complex, home to the 15th Space Surveillance Squadron and the Air Force Research Laboratory. Its futuristic domes glowed in the thin air, silent instruments tracing the geometry of satellites far above.

Later that week, at the Advanced Maui Optical & Space Surveillance Technologies (AMOS) Conference, Gen. Chance Saltzman, Chief of Space Operations for the U.S. Space Force, outlined a future where orbital readiness, responsiveness, and resilience are necessities and described the pressure this places on acquisition and sustainment:

“Space is unforgiving. It is hard on the human body. It is hard on equipment. With space now a war-fighting domain, that puts tremendous pressure on the defense acquisition process to supply and sustain credible military space capabilities. If the United States intends to remain the world’s preeminent space power, we must fundamentally change the way we conceive, develop, and deploy novel technology for a rapidly evolving environment.”

— Gen. Saltzman, Chief of Space Operations, U.S. Space Force

The next frontier will not be won by speed, but by design, by those who can align vision, capability, and conscience into a coherent system. In this new era, strategy is no longer only written in Doctrine; it is written in Design. The challenge, as Gen. Saltzman noted, is not purely military. It is a design challenge in systems infrastructure, distributed resilience, and strategic foresight. In other words, this is exactly what design strategists are doing every day for organizations and brands on Earth.

When I say Design, I do not mean products or interfaces. I mean strategic architecture, the discipline that aligns intent, technology, and human behavior across systems. Design Strategy is the method by which vision becomes executable reality; linking decisions made in boardrooms and command centers to the systems that carry them out. This form of Strategic Design now shapes readiness, deterrence, and control.

Every concept Gen. Saltzman cited, from responsive launch to proliferated constellations and orbital logistics, points to the same truth: Design Strategy is now the foundation of execution, the geometry that turns intent into capability. It defines how vision becomes readiness and how readiness sustains power.
In fast-moving environments, Strategy and Design operate as one system. Strategy sets intent; Design Strategy makes it executable. Together they form a continuous feedback loop: Strategy defines direction, Design structures reality, and each refines the other. At the geopolitical scale, Geostrategic Design aligns political, technological, and planetary systems so intent can operate coherently.

What struck me was not only the sophisticated technologies at play, but the architecture of coordination behind them. Every single sensor, feed, and satellite belongs to a larger design ecosystem where capability, collaboration, and control must stay in balance. The structure of that ecosystem will define how we build resilience and maintain balance in orbit.

Standing on the edge of space, between its soothing silence and the hum of human ambition, one thought crystallized: What if design, aligned with command, became the organizing principle that defined how we operate, compete, and maintain advantage in orbit?

As Col. Jason Trew, Ph.D. (USAF, Ret.) former Commandant and Dean of the U.S. Air Force’s School of Advanced Air and Space Studies (SAASS), puts it: “To some military leaders, Design may seem to be a foreign concept, especially the way it operationalizes imagination; but that has always been woven into our strategic canon, from Clausewitz’s coup d’œil, to Sun Tzu’s emphasis on ‘winning without fighting,’ to the cunning of Homer’s Odysseus.”

His words remind us that Design is not an imported idea from the creative world but a rediscovery of what great strategists have always practiced, imagination made operational.

Consider the Proliferated Warfighter Space Architecture (PWSA), the U.S. network of small, resilient satellites, developed by the U.S. Space Development Agency. It embodies the full hierarchy described above: Geostrategic Design, Strategy, Design Strategy, Command, and Execution.

1. Geostrategic Design: Aligns national, industrial, and allied systems through the National Defense Space Strategy and U.S. Space Command’s integration into doctrine. It makes political, industrial, and orbital infrastructures work in concert, the geometry of power spanning nations and orbits.

2. Strategy: Sets intent. Deterrence through resilience, shifting from vulnerable, monolithic satellites to distributed constellations that can survive and reconstitute under attack.

3. Design Strategy: Translates intent into executable systems via Space Development Agency’s (SDA) “tranches,” networking hundreds of small satellites with inter-satellite laser links in a modular, upgradable architecture.

4. Command: Orchestrates operations through U.S. Space Command and Combined Space Operations, integrating intelligence, cyber defense, and orbital control.

5. Execution: Delivers and sustains capability. Space Force Delta units operate constellations, stress test resilience, and feed performance data upward to refine acquisition, design, and doctrine.

Together, they form a living feedback loop, a geometry of power already unfolding above the Earth.

The Silent Race Above the Clouds

The sky that once symbolized exploration and wonder is now infrastructure of power; a trillion-dollar choreography of satellites aligning, repositioning, watching. Invisible patterns of surveillance, defense, and ambition move like silent convoys. Space is no longer a neutral void; it is contested, congested, and competitive. The question is not whether we compete, but how decisively we design for advantage.

This is the new geometry of power, already quietly taking shape above the Earth. The Pentagon is fielding constellations of hundreds of replaceable satellites, trading perfection for proliferation. China has conducted synchronized proximity maneuvers viewed as potential rehearsal for orbital engagements. Russia has demonstrated the ability to blind or jam communications from orbit. Treaties that once defined norms in space are fast eroding.

Orbit is now an operating system of geopolitics, and Design Strategy is its interface. The question is less who controls the sky and more who shapes the architecture that governs it.

A System Beyond Command

Technology always outpaces doctrine, and space is exposing that gap faster than any previous domain. This is not only a story of power projection. It is the story of systems evolving faster than the ethics meant to guide them. We are extending Earth’s architecture of power into space faster than we are updating its moral code.

We are designing faster than we can understand, and the cost is rising. The very systems meant to preserve order now create new forms of uncertainty. In the pursuit of control, we are testing the boundaries of control itself, constructing infrastructures that think, decide, and adapt beyond human tempo.

Space, once a symbol of transcendence, has become a mirror reflecting our accelerating dependence on design as destiny. Each launch embodies a paradox: resilience through fragility, progress through peril, the design logic of systems that must survive their own vulnerability.

Responsive launch, close-proximity operations, and the debris from failed missions and anti-satellite tests now shape the orbital environment. Distributed systems promise redundancy yet can multiply vulnerability. Cislunar logistics, lunar mining, and satellite servicing are forming new economies with little governance or shared accountability.

This is the shadow of design without ethics, systems that scale faster than the wisdom required to govern them. Without governance, power is just acceleration.

Design as Power

Control is no longer achieved solely through Command. It also depends on Design Strategy, the infrastructure that shapes power itself.

The old world was vertical, defined by nations commanding assets from Earth and projecting control outward. The new world is orbital, defined by networks that are distributed, adaptive, and self-healing.

Resilience has replaced dominance as the currency of power. In disruption, survival favors networks that can reroute, not empires that seek to dominate. Across defense and aerospace, this design logic is reshaping acquisition, readiness, and sustainment. The Proliferated Warfighter Space Architecture, a 154-satellite network designed to survive attack through redundancy, exactly mirrors patterns in Earth supply chains, digital ecosystems, and AI infrastructures: Decentralization, iteration, expendability.

This is Geostrategic Design in motion, treating political, technological, and planetary systems as interdependent networks shaped by intent and consequence. These are not only engineering choices. They are acts of systemic architecture that redefine how nations operate, how companies compete, and how civilizations endure. This shift is also redefining command itself, as human and machine decision loops blur under the speed of orbital operations. Geostrategic Design now dictates the tempo at which Strategy can act.

Power is no longer held through territory. It flows through systems that adapt faster than they can be broken. These are the architectures of intent, the designs through which power learns to survive.

Design at Every Altitude

The logic that connects cockpit design and orbital command is the same: Clarity under complexity. The efficiency logic that serves Earth can create fragility in orbit. Acquisition often favors speed over adaptability. The opportunity is durability: systems that absorb shock, bend under pressure, and extend mission life.

The same principles transforming how organizations collaborate and decide on Earth are now shaping the architecture of orbit. Strategy begins where systems meet people. Geostrategic Design is the discipline that translates grand strategy into operational design and turns complexity into clarity.

“From cockpit interfaces to constellations of satellites, from mission interface to orbital network, every layer of these systems is both technical and human, a choreography of design decisions shaping how strategy becomes action.”

Across the military and aerospace landscape, a quiet shift is underway. Organizations once driven purely by engineering or command logic are beginning to integrate true strategy teams, interdisciplinary groups trained to think holistically about systems, outcomes, and intent. They recognize that design strategy is not about aesthetics, but about alignment, connecting technology with mission, behavior with policy, and structure with purpose.

This is why design strategy has begun to move upstream, into the rooms where power is planned rather than where it is visualized. Aerospace and defense leaders are discovering what commercial innovators learned a decade ago: That design strategy is a force multiplier. It identifies the unseen connections between capability, decision-making, and human experience. It turns complexity into coherence.

Across aerospace, defense, and space technology, design strategists are being invited into the fold. Their ability to think beyond the engineering brief, to connect human intention with technical precision, is now seen as essential to teams once defined purely by systems and code. They provide the interpretive layer that makes complex innovation coherent. That same interpretive skill is what civilian design teams use when turning strategy into service systems or brand ecosystems: The logic is identical.

Yet amid this orchestration of futuristic machines and sensitive data, the human remains the most adaptive and fragile node in the system. Every interface, every decision tree, still hinges on judgment, not just computation. Amid networks of data and satellites, the smallest unit of stability is still a single human decision.

In that sense, the ultimate design variable is still human judgment, and it remains the least predictable element in any system. In the silence between signal and response, it is human intent that gives these systems meaning.

Whether inside a satellite program or a command center, design strategists help ensure that what is built serves what must endure: Purpose, adaptability, and trust.

The Cislunar Theater

The same strategic logic linking organizations on Earth now extends beyond the planet. What began in labs and mission control is moving into orbit and beyond. This is not a race for discovery. It is a testbed for the next phase of system design.

For instance, NASA’s Commercial Lunar Payload Services (CLPS) program now outsources lunar logistics to private firms like Firefly Aerospace and Intuitive Machines. These companies are more than explorers, they are infrastructure providers. They are building tomorrow’s connective tissue between planets: Delivery systems, refueling hubs, and communication nodes.

Rocket Lab, Firefly, and Astroscale are becoming the laboratories of a new design discipline:

• Rocket Lab’s rapid-response launches echo the logic of modular and agile software deployment.
• Firefly’s lunar missions integrate analytics, logistics, and hardware in a vertically aligned stack.
• Astroscale designs satellites that extend orbital lifespans or remove debris, turning sustainability into strategy.

The Moon, once a poetic symbol, is now a logistics node for refueling, supply, and communication. Between Earth and Moon stretches a contested corridor, a cislunar highway of commerce, defense, and data. It is becoming the first infrastructure network to operate beyond traditional notions of national sovereignty.

Nation-states and startups are rapidly converging as forces designing orbital ecosystems. That convergence offers real potential when guided by shared standards and interoperable design. In orbit, design strategy is becoming diplomacy.

The Governance Gap

Every system of power meets its limits , and in orbit, those limits are arriving faster than our ability to manage them. The more we industrialize orbit, the more we expose the limits of our wisdom. We are designing faster than we can govern. That imbalance, already evident on Earth, in AI regulation, cybersecurity, environmental systems, and economic inequity, becomes blindingly clear in orbit.

Systems evolve faster than treaties. Automation outpaces accountability. Debris accumulates like the physical residue of neglect. The same logic that drives efficiency on Earth, speed and scale, risks cascading instability above it. As norms erode, secrecy expands and corporate incentives outrun oversight, creating an ecosystem optimized for technical precision and strategic ambiguity but thin on ethical design. Yet these challenges also mark a turning point, a chance to build governance into the DNA of every mission system.

This is not an engineering failure. It is a civilizational design flaw, a pattern that repeats wherever progress outpaces reflection. We design systems for performance, but rarely for peace. Ethics in space cannot be a late add-on because good governance is now a force multiplier. Systems designed with ethical integrity are also more trusted, able to connect and cooperate, and resilient under pressure. Without that integrity, design becomes strategy’s blind spot; and power its own undoing.

Designing the Strategic Operating System

At its highest level, Design Strategy becomes Geostrategic Design, the operating framework through which nations, industries, and alliances translate policy into capability. The same design logic defining how we build trust on Earth now shapes orbital systems. From vast satellite constellations to complex corporate ecosystems, the principle is identical: Distributed integrity sustains both mission and market.

The cracks in orbit’s moral foundation call for a framework that governs through foresight. Governance is not red tape; it is risk management. When embedded early, it reduces compliance cost, accelerates certification, and enables cross-domain coordination among industry, government, and allies. Embedding design early ensures that strategic intent is not slowed by complexity but accelerated through coherence. The answer is not retreat, it is redesign.

From defense acquisition to orbital infrastructure, three principles can guide the next decade. These same principles are also reshaping how we design on Earth, from brands to products to platforms. Whether on Earth or in Orbit, the geometry of power is converging: Distributed, adaptive, and governed by trust.

1. Proliferation as Protection: Move from single-point assets to distributed constellations where redundancy equals resilience. In defense, design for loss without mission failure. In markets, decentralize creativity without losing coherence.
2. Design for Dynamic Equilibrium: Build systems that anticipate flux. Pair Strategy and Design in continuous feedback between operators, engineers, and decision-makers. Treat instability as choreography, not chaos.
3. Governance as a Design Layer: Treat rules, data policies, and ethical guardrails as integral components. Embed them early to turn compliance into trust and interoperability. Design Strategy is now diplomacy.

Orbit is an operating system of geopolitics and a platform for collaboration, deterrence, and shared resilience. The role of design leadership is to architect coherence in an era of fragmentation and to ensure that the design for survival is built on intention, not inertia.

From the summit of Haleakalā to the silent corridors of orbit, one question endures: What order of power and control are we building as we extend our reach?

The Mirror Above Us

What we build in orbit is not just infrastructure, it is the mirror by which history judges intent. Orbit is not an escape, it is a reflection. Everything we build there magnifies what we already are.

The new space race is not who reaches the Moon first, but who designs the systems that define planetary life, the balance between security and fragility, progress and preservation.

Space is no longer a frontier. It is a feedback loop that amplifies intelligence and intent. Every orbiting object represents a choice about what kind of civilization we are becoming.

The frontier was never empty. It has always reflected how we think about power, collaboration, and stewardship.

The next frontier demands strategic intent and moral clarity. This is not about slowing innovation, it is about scaling progress responsibly to serve collective resilience. In the end, Design Strategy is not about form; it is about foresight, the architecture that makes strategy executable and power sustainable.

Whether building mission systems or market ecosystems, the challenge is the same: Design structures that extend human intent without eroding human judgment. Every orbit, every network, every decision is a reflection of the civilization that built it. The real frontier, military or civilian, is aligning capability with conscience, and strategy with stewardship.

(Disclaimer: The companies, projects, and examples mentioned in this article are based on publicly available information and industry best practices. No proprietary or confidential information has been disclosed, and all references are for illustrative purposes only. This article does not represent insider knowledge or violate any non-disclosure agreements. Some AI tools could have been used for basic editing, research and visuals, but the insights and perspectives are entirely human.)

How Service Design Can Turn Call Volume into Loyalty, Insights, and Lasting Customer Value.

Picture this: A customer has been on hold for twenty minutes. Their frustration rises with each passing second. On the other end, an agent juggles five screens, outdated tools, and rigid scripts, trying to keep pace with KPIs while their empathy is stretched thin. In that fragile moment, a company’s reputation and a customer’s loyalty hang in the balance.

Every brand has a frontline. Too often, executives picture it as gleaming flagship stores, beautifully designed apps, or curated digital journeys. But the real frontline is here, in the Contact Center, the unglamorous yet decisive nerve center where frustrated customers call, text, or chat when something breaks, and where trust is either built or shattered.

“Ignoring the Contact Center is like throwing away a gold nugget because it’s covered in dirt, overlooked at first glance, but priceless when unearthed.”

Today, every single company on Earth has a Contact Center. Yet too many still treat it as a cost sink rather than what it truly is: The emotional front door of the brand. Contact Centers are where frustrations are resolved, trust is built, and loyalty is made, or lost in minutes.

And in this overlooked domain lies something even more precious than gold: An unfiltered stream of consumer insights. Every call is a data point on unmet needs, broken journeys, and systemic failures that no survey ever reveals. As Greg Bieker, Director of Contact Centers Transformation at Slalom, puts it:

“Every customer interaction is a chance to strengthen the Customer Experience. It’s not just about a single point in time, it’s about continuously learning how to improve products and services that build loyalty and trust in your brand.”

The High Stakes of Contact Centers

The stakes could not be higher. For a large enterprise, a 10% reduction in call volume can mean tens of millions in annual savings. At $6 per call (an industry benchmark) and 100 million calls a year, that’s roughly $60 million saved EACH year. In a world where every organization is expected to do more with less, this is money left on the table. But the bigger risk isn’t just financial, it’s the erosion of trust, loyalty, and brand equity.

The research is clear: Customers have little tolerance for failure. PwC’s Future of Customer Experience research found: 32% of all customers would stop doing business with a brand after one bad experience; and even when people love a brand, 59% will walk away after several bad experiences. Recent studies by Zendesk and Emplifi show those expectations getting worse with about half will switch after just ONE poor interaction, and nearly 70% after two. In other words, one broken moment can trigger a lifetime of lost loyalty.

And then comes the ripple effect. A dissatisfied customer doesn’t just leave quietly, they tell others. Negative word of mouth multiplies the damage: In some surveys, customers say they share bad experiences with ~15 people, far more than they share good ones. That’s not just one customer lost; it’s dozens of potential customers influenced by their story.

These are not small cracks in the system. They are tectonic fractures.
The Contact Center is not just about transactions, it is the battleground where loyalty is defended or destroyed, one interaction at a time.

But here’s the paradox: The same frontline that can destroy loyalty can also create it, if handled with empathy.

The Service Recovery Paradox

Here’s the unexpected twist: When recoveries are handled well, they don’t just restore loyalty, they can create it. Studies show effective recovery (fair outcomes, a clear and respectful process, and genuine empathy) can yield satisfaction equal to or higher than if no issue occurred at all, and a simple follow-up is a powerful trust signal.

• Customers whose complaints are resolved report satisfaction levels 70% higher than those who NEVER experienced any issue at all.
• 70% remain loyal to brands that resolve their complaints.
• 80% appreciate follow-up after an issue, showing how crucial it is not just to resolve, but to confirm.
• 78% who receive satisfactory resolutions stay loyal, fueling repeat business and positive word-of-mouth.

This is the mind-boggling Service Recovery Paradox: Customers who have had problems, but were treated with empathy and care, become MORE emotionally invested than those who NEVER encountered a hiccup.
Let that sink in for a second.

The Service Design Advantage: Opportunities, Opportunities, Opportunities.

This paradox underscores why experience cannot be improved through efficiency alone and why design must shape both emotional and operational elements of the journey.

Traditional transformation programs often focus too narrowly on efficiency, systems upgrades, workforce optimization, dashboards, deflection. These are important capabilities: Omnichannel platforms, automation and self-service, knowledge and case management, routing and WFM, performance dashboards, and change readiness. But on their own, they’re not enough without a human-centered lens.

What separates Service Design from traditional transformation is its ability to reveal root causes across the entire ecosystem by blending qualitative insight with operational analysis.

Service Design asks:

• Why are customers contacting agents in the first place?
• What external factors shape their interaction?
• What does the emotional journey look like?
• Where are friction points across tools and teams?
• How do agents experience their own journeys?

Example: Airlines and Baggage Allowances
Across the airline industry, a significant portion of call volume has been tied to one deceptively simple issue: Baggage allowance confusion. Passengers book flights only to discover at check-in that they misunderstood the rules: Was a carry-on included? What about international versus domestic allowances? Did upgrades or loyalty status change the policies? The result has often been a wave of anxious calls, frustrated travelers at airports, and agents stuck explaining baggage policies instead of focusing on higher-value interactions.

Rather than throwing more agents at the problem, leading carriers applied a Service Design lens. By mapping the booking journey, they uncovered that the real issue wasn’t poor customer service, it was poor clarity. By redesigning booking flows to surface baggage policies in plain language, upfront and contextual to each ticket type, they addressed the root cause rather than the symptom.

Carriers like Delta have leaned into this approach, clarifying baggage information during booking so customers know exactly what to expect. The impact has been striking: Fewer calls, reduced airport friction, and travelers entering their journeys more confident and less stressed. Agents, no longer bogged down in repetitive explanations, can instead focus on complex cases and deliver more empathy-driven support.

Outcome: Reduced call spikes, smoother travel experiences, and more confident customers at booking, a win for efficiency, loyalty, and employee satisfaction.

The Forgotten Journey: Agents on the Frontline

Customers aren’t the only ones experiencing friction. Agents, too, are often trapped in broken workflows, juggling outdated systems, siloed data, and performance dashboards that measure speed instead of empathy. Contact Centers routinely battle 30–45% annual turnover, burnout from fragmented systems and high pressure is a core driver.

“Contact centers face some of the highest turnover rates in any industry, often over 30% each year, because agents are burning out in systems built for efficiency, not empathy. Imagine replacing a third of your staff every year, re-hiring and retraining in an endless cycle.”

And when agents burn out, customers feel it, every rushed interaction, every missed note of empathy.

The result? Burnout, high attrition, and a frontline that feels more like a pressure cooker than a place of service. Service Design changes that dynamic by redesigning backstage experiences: Aligning tools with real tasks, removing redundant clicks, and creating journeys that empower agents to succeed.
Consider a major retail bank that redesigned its case management system: By simplifying workflows, agents spent less time wrestling with screens and more time listening to customers. The outcome was not only faster resolution times but a profound increase in empathy delivered at scale. Service Design strengthens both sides of the equation, the customer journey and the agent journey, because one cannot thrive without the other.
When both journeys improve in tandem, organizations see measurable gains in first contact resolution, reduced cost to serve, and higher lifetime customer value.

Automation Isn’t Always The Silver Bullet

Today, Contact Center transformation is too often framed as an automation/AI/Chat bot-frenzy. But automation without design is just cost-cutting, and when it fails, it fails hard.
According to TechRadar Pro, over 70% of consumers say they’ll consider switching brands after ONE bad AI chatbot experience, proof that trust is as critical as speed. AI for the sake of AI isn’t progress, it’s a liability.
Deployed carelessly, it can erode loyalty faster than it creates efficiency, doing far more damage to your brand than good.
The real opportunity is to reframe automation through the human-control lens: Not adding more bots, but creating a smarter balance where automation is paired with the right level of human involvement:

1. Human-In-The-Loop (HITL): Precision Empathy

A system supports the agent, but the human makes the final call.

Example: Bank of America
Bank of America’s virtual assistant, Erica, now helps millions of customers by pre-collecting account information and handling routine requests before a case ever reaches a live agent. This automation removes friction, speeds up resolution, and ensures that agents have context in front of them the moment a call begins.
But the real differentiator isn’t just Erica, it’s what happens when the handoff reaches a human. Bank of America has invested in training agents to recognize stress and respond with empathy, not just efficiency. Imagine a customer who suddenly loses their debit card. Erica can capture the account details and trigger the replacement process, but it’s the human agent who reassures the caller, listens to their concern, and restores confidence. (Erica has now handled 2–3B interactions for 40M+ clients.)
This pairing of digital speed with human care illustrates the Service Design principle of solving at both the system level and the emotional level. Automation streamlines the process, but empathy transforms the experience.

Outcome: Faster resolutions, higher satisfaction, and stronger customer trust, a win for both efficiency and loyalty.

2. Human-On-The-Loop (HOTL): Guided Autonomy

The system manages the workflow, with human oversight.

Example: AT&T
Telecom providers like AT&T face a mountain of repetitive calls: Customers struggling with something as simple as resetting a Wi-Fi password. Each call took up to 30 minutes of agent time, creating frustration for customers and draining resources from more complex issues.
Rather than keep agents tied to repetitive tasks, AT&T redesigned the experience. They built an automated self-service workflow that allowed customers to reset passwords instantly through SMS or the mobile app. Service Design thinking ensured the process was intuitive, clearly worded, and easy to follow, reducing the risk of customers feeling abandoned in a purely automated loop.
Agents weren’t removed from the system; they became safety nets. When the automation flagged unusual behavior, such as multiple failed attempts that might signal fraud, an agent could step in, investigate, and resolve the exception.

Outcome: Resolution times fell from 30 minutes to 30 seconds, customers felt empowered by self-service, and agents were freed to focus on higher-value, empathy-driven interactions. The result wasn’t just efficiency, it was retention, as customers got it right the first time.

3. Human-Out-Of-The-Loop (HOOTL): Invisible Effort

Problems are resolved before the customer even notices.

Example: Netflix
Subscription platforms like Netflix used to see call spikes whenever subscriber credit cards expired. Customers would suddenly find their service interrupted, triggering a flood of urgent support calls.
Instead of scaling agents to handle the surge, Netflix redesigned the journey to make it proactive and invisible. The system now sends automated reminders before cards expire, offers one-click updates for payment details, and even extends a short grace period to avoid unnecessary disruption.
What feels simple to the customer — “my service just kept working” — is actually the result of thoughtful Service Design: anticipating a pain point, embedding empathy into automation, and removing the friction before it becomes frustration.

Outcome: Call spikes disappeared, subscription renewal rates improved, and customers felt cared for by a service that “just works.” It proved that resolution, delivered with empathy and foresight, can build loyalty even more than flawless service.

Why Many Transformations Fail

Despite massive investments, too many Contact Center modernization programs fall short of their promise, not because of a lack of technology, but because of a lack of design intent.

Many programs fall short because they emphasize throughput and technology upgrades without understanding how people actually move through the experience:

1. Journeys are often optimized for volume, not for people. They’re engineered to move customers quickly through a system instead of actually solving the problem that made them call in the first place.

2. Improvements tend to be siloed and fragmented. Operations, technology, training, and customer experience teams all fix pieces of the puzzle, but no one steps back to see the whole picture.

3. Assumptions go unvalidated. Solutions are rolled out before the real problem is understood, leading to mismatched fixes and wasted investment.

4. Agents and customers are brought in too late, often only at rollout. The result is low adoption, friction, and resistance to change, because the very people who live the journey every day weren’t included in shaping it.

5. And perhaps most damaging of all, there’s a disconnect between the frontstage and the backstage. The customer hears one thing, the agent experiences another, and the systems running in the background don’t match either.

Even the strongest implementations stumble under these conditions. Without a holistic, human-centered approach, transformation efforts collapse under their own weight, delivering efficiency gains on paper, but falling far short of their true experience potential.

The result? Even strong implementations underdeliver, because they lack holistic design. As Greg Bieker, Director of Contact Centers Transformation at Slalom, points out:

“Modernizing a contact center isn’t simply about faster routing or new systems. Efficiency alone misses the point. The contact center is the window into your customer’s experience and the key to unlocking how to elevate it.”

What Beautiful Looks Like

In a beautiful future, when Service Design is applied, Contact Centers shift from cost centers to value creators:

• Customers feel heard and supported.
• Agents feel empowered and trusted.
• Operations run with clarity, speed, and agility.
• Change becomes transformational, not just functional.

Or put simply: The future of Contact Centers is not fewer calls, but fewer reasons to call.

The Contact Center of Tomorrow

Leaders who excel in this future will align insight mining, root cause elimination, and empathy at scale into a single operating system rather than separate initiatives.

The Contact Center is no longer destined to be a reactive cost center, it is evolving into the proactive command center of customer loyalty. Imagine a near future where predictive analytics spot issues before customers feel them, where AI resolves routine problems invisibly in the background, and where agents are liberated from repetitive tasks to serve as true advisors and brand ambassadors. In this future, Contact Centers are not measured by how fast calls are deflected but by how deeply insights are mined, how quickly root causes are eliminated, and how effectively empathy is scaled across millions of interactions.

A Future-Facing Scenario: Horizon Airlines

Imagine Horizon Airlines, a fictional carrier of the future, once plagued by waves of angry calls whenever weather caused delays or cancellations. In the reimagined contact center of tomorrow, predictive systems track storms and proactively rebook passengers before they even check the departure board.
> A traveler wakes up to a text: “Your 8:45 a.m. flight has been rerouted due to weather. You’ve already been rebooked on a 9:30 a.m. flight with a complimentary meal voucher. Tap here to confirm or choose another option.”
By the time the traveler arrives at the airport, their journey is already back on track.
Contact Center agents spend less time apologizing for disruptions and more time helping frequent flyers optimize itineraries or upgrade experiences. What was once a source of frustration becomes a seamless demonstration of foresight and care.

The organizations that embrace Service Design as the blueprint for this transformation will lead the way. They will not only modernize operations but also redefine what customer relationships look like in the 2030s: Anticipatory, human-centered, and powered by design.

Striking Gold in Plain Sight

Contact Centers are no longer just places where issues are resolved. They are mines of insight, loyalty, and emotional connection. Each call, each chat, each frustrated voice is raw ore. Without Service Design, it remains buried, overlooked, undervalued, wasted.

But when Service Design steps in, those moments are mined, refined, and transformed into treasure: Loyalty that survives bad days, trust that outlasts market shifts, and insights that reshape entire journeys. Technology alone will never deliver that kind of transformation. It takes empathy, systems thinking, and design discipline to uncover the real treasure that Contact Centers hold.

The future of customer relationships will not be won by organizations that treat their Contact Centers as expenses to cut or volumes to deflect. It will be won by those who recognize them for what they truly are: Hidden goldmines of loyalty, trust, and intelligence waiting to be unearthed. Because the richest insights and the deepest bonds aren’t discovered in polished boardrooms or glossy showrooms. They are forged in the overlooked, unfiltered conversations of the Contact Center where frustration meets empathy, where service becomes loyalty, and where every call holds a nugget of truth.

Organizations that embrace this shift will do more than modernize their Contact Centers. They will unlock the goldmine in plain sight and in striking it, they will secure the trust, loyalty, and growth that define the future of customer relationships.

The organizations that act now will convert frontline conversations into strategic intelligence while competitors continue to treat them as operational noise.

The only question is: Will you mine it, or let it go to waste?

Sources & Further Reading

1. PwC Future of Customer Experience
   PwC, “Experience is everything” (2018)
2. Zendesk CX Trends Report
   Zendesk CX Trends (2021)
3. Emplifi CX Report
   Emplifi, “Customer Experience Trends” (2024)
4. American Express Customer Service Barometer
   American Express, Customer Service Barometer (2017)
5. Service Recovery Paradox
   Smith, A., Bolton, R., & Wagner, J. (1999). “A Model of Customer Satisfaction with Service Encounters Involving Failure and Recovery.”
   Michel, S., Bowen, D., & Johnston, R. (2009). “Why service recovery fails: Tensions among customer, employee, and process perspectives.”
6. Contact Center Attrition Rates
   QATC (Quality Assurance & Training Connection). TechRepublic, “Why contact center attrition is so high” (2023)
7. AI & Customer Trust
   Acquire BPO / TechRadar Pro, “Consumers will ditch brands after a bad AI interaction” (2024). Forbes, “Why Trust Is More Important Than Speed in AI-Powered CX” (2024)
8. Call Cost Benchmarks
   ICMI (International Customer Management Institute), “How Much Does a Call Center Call Cost?”. ContactBabel, “US Contact Center Decision-Makers’ Guide” (2023)
9. Bank of America / Erica
   Bank of America Newsroom, “Erica Surpasses 1 Billion Client Interactions” (2021)

(Disclaimer: The companies, projects, and examples mentioned in this article are based on publicly available information and industry best practices. No proprietary or confidential information has been disclosed, and all references are for illustrative purposes only. This article does not represent insider knowledge or violate any non-disclosure agreements. Some AI tools could have been used for basic editing, research and visuals, but the insights and perspectives are entirely human.)

From Hype to Impact: How Designers Can Harness Applied AI to Build Intelligent Experiences, Shift Systems, and Deliver Results.

There are theoretical physicists who spend their lives contemplating the mysteries of quantum entanglement, and then there are applied physicists who take those theories and bend them into reality, building lasers, satellites, and the technology that shapes our world.

In the same way, while many are still philosophizing about artificial intelligence, our teams are already deep in the trenches: Designing with it, building with it, operationalizing it. We’re not just watching the AI revolution; we’re shaping it. This article is a look under the hood of how we’re doing that, and why designers are uniquely positioned to turn AI from hype into real-world impact.

Our design teams have been hands-on with Artificial Intelligence for nearly a decade now, long before the recent AI hype. From Computer Vision to Deep Learning, we’ve explored, experimented, built, tested, and embedded AI across internal and client-facing work for years. Long before Generative AI went mainstream, we were applying Deep Learning to predict service drop-off, using Computer Vision to analyze customer flows in physical spaces, and running real-time sentiment detection on contact center transcripts. Over the past couple of years, we’ve steadily woven Generative AI into our design workflows, not as a novelty, but as a natural evolution of how we think, create, and deliver.

But let’s be clear: The window for contemplation has closed.
If you’re still on the sidelines, debating, posturing, hesitating, you’re already behind. Yes, change can be daunting. Yes, AI can feel complex. But you don’t need to master AI to start using it. You just need to roll up your sleeves and get to work. Because it’s certainly not going away.

So stop debating. Start building. Ignite the AI machine already!

Because we are now in the post-hype era, a time when designers and strategists must move from commentary to contribution. From talking about AI… to designing WITH AI.

“We are entering the age of intelligent systems. AI is no longer something to explore, it’s a force to harness, shape, and evolve. In this new era, Design is no longer just aesthetic, it has become architectural. Those who design with intelligence today will define the world we live in tomorrow.”

Designers, especially those in service design, experience strategy, and business transformation, have a unique opportunity: To infuse Artificial Intelligence into the visible and invisible systems that power how organizations operate, adapt, and grow.

So what makes AI designable? It’s not just about outputs.
It’s about how systems listen, respond, escalate, and evolve.
AI isn’t a feature. It’s a behavior.
And behaviors are exactly what designers shape, right?

Today, too often, we witness AI being treated as a tech layer, sitting above or below Design. But AI isn’t an off-the-shelf add-on to bolt onto your experiences just to “do AI.” AI has the power to transform how services sense, adapt, and learn. That’s why AI doesn’t just need to be implemented. It needs to be designed. Thoughtfully.

Part 1: Design WITH AI

Turn your design practice into a high-performing decision engine.

Before you embed AI into your client experiences, you need to operationalize it in your own design processes. This is where the shift begins: Not with flashy prototypes or trendy buzz features, but with the quiet transformation of your daily workflows, research, modeling, prototyping, and strategy itself.

Because, designers are no longer just facilitators of insights.
They are now orchestrators of intelligence.

AI lets you see what’s too complex, too fast, or too vast for human cognition alone. It accelerates your sense-making, sharpens your foresight, and frees you to focus where it matters most: On defining the system, not drowning in its noise.

This is how design becomes exponential:

1. Discovery & Research

What signals are you missing because you don’t have the time to look?

What: Use AI to accelerate signal detection, pattern recognition, and data synthesis.

Real World Use Case: A global healthcare system had 120 transcripts from various patients, nurses, and staff across four continents. Designers used Whisper for transcription + GPT-4o to cluster themes + Claude to surface culturally specific insights.
Outcome: Three weeks of expected manual synthesis completed within 48 hours. Designers walked into the workshop with clarity and understanding.

Applied AI:
• Compress large research sets into insight clusters
• Detect linguistic and emotional shifts across cultures
• Map macro trends to micro-level design opportunities

Tools: Whisper, Perplexity, GPT-4o, Claude, Feedly AI

What This Unlocks: Designers shift from being synthesizers of chaos to accelerators of clarity, freeing up time to think strategically, not just process data.

Takeaway: This isn’t just faster research. It’s what happens when designers shape intelligence into insight, not just information.

2. Service Blueprinting & Journey Modeling

What do your journeys feel like under stress? What breaks when trust is low?

What: Transform static blueprints into dynamic simulations.

Real World Use Case: A retail bank reworked its onboarding blueprint by running simulations through GPT-powered personas (elderly, non-native speakers, digitally hesitant users). They discovered drop-off was driven not by interface complexity, but tone.
Outcome: A simple reframe of language reduced onboarding friction by 31%.

Applied AI:
• Simulate emotional and behavioral states (“anxious,” “impatient,” “skeptical”)
• Detect cold automation or failed escalation points
• Bridge frontstage experiences with back-end system logic

Tools: GPT + Journey Prompt Packs, Smaply + LLM integrations, Excel + GPT for KPI mapping

What This Unlocks: Journey maps become more than artifacts, they become living, testable systems.

Takeaway: This isn’t about fixing a broken journey. It’s about evolving static maps into responsive, intelligent systems of trust.

3. Prototyping Strategy & Service Concepts

What would happen if your boldest idea met your hardest user?

What: Use AI as a co-creator to simulate, roleplay, and iterate on concepts.

Real World Use Case: A travel tech firm prototyped an AI concierge targeting Gen Z users. GPT-4 simulated a conversation with a skeptical user. The result? Gen Z didn’t want efficiency, they wanted serendipity. The prototype pivoted from utility to “choose your vibe” exploration.
Outcome: Conversion jumped 24% in beta.

Applied AI:
• Simulate edge personas interacting with service concepts
• Generate multiple prototype variations in minutes
• Roleplay stakeholder conversations to pressure-test logic

Tools: ChatGPT-4o, Voiceflow, Midjourney, Uizard + GPT narration

What This Unlocks: Rapid prototyping becomes relational, not just visual, anchored in behavior and belief, not just interface.

Takeaway: This isn’t just rapid iteration. It’s what happens when designers use AI to simulate behavior and build belief, not just interfaces.

4. Design Strategy & Executive Alignment

Can your strategy be explained in 3 slides, or 3 sentences?

What: Accelerate strategic framing, foresight modeling, and narrative packaging.

Real World Use Case: A food delivery startup explored a new local grocery partnership. Using Claude, they modeled impacts on retention, cost-to-serve, and service load. Then used Gamma to generate a narrative-ready strategy deck.
Outcome: $4M in new funding secured.

Applied AI:
• Benchmark proposed strategies against historic business analogs
• Forecast impact scenarios (e.g., regulation shifts, operational constraints)
• Translate complexity into executive-ready narratives, fast

Tools: Claude, GPT-4, Tome, Gamma, Figma

What This Unlocks: Strategy moves at the speed of insight — not just intuition.

Takeaway: This isn’t slideware. It’s what happens when design makes foresight actionable, and complexity communicable.

Once AI becomes your internal advantage, you’re ready to embed it into the world your clients operate in.

Part 2: Design FOR AI

Shape the systems and experiences your users will navigate tomorrow.

Once AI is embedded in your own design practice, the real opportunity begins: Designing the intelligent experiences and systems your clients need, often before they realize it. This isn’t about new fancy chatbots or useless novelty features. It’s about rethinking services at the operational, behavioral, and systemic level.

“Artificial Intelligence isn’t just for massive business transformation efforts. Many levels of AI can be deployed quietly in the backstage, in support functions, improving handoffs, softening friction, sensing risk, right where no one’s looking. Not every AI use case needs to be glamorous, bold, or even visible. In fact, some of the most powerful applications of AI today are the ones you never see.”

Designers now have the power, and responsibility, to shape how AI shows up in the world. Not just as interface, but as infrastructure.
Not just for users, but for teams, systems, and outcomes.

When designed thoughtfully, AI doesn’t replace or displace humans. It amplifies empathy, precision, and scale. It can route smarter, sense earlier, nudge better, and adapt continuously, under your direction.

This is how service design evolves, from orchestrating experiences to engineering living systems of intelligence:

1. Customer Support & Frontstage AI Experiences

> When should your AI know to stop, and escalate to a human?

What: Scale empathy and speed, without dehumanizing the experience.

Industry: Telecommunications
Challenge: High call volume, low trust in automated support, and confusion around billing language.

Solution: A national telecom provider deployed an AI-powered virtual assistant trained to handle billing and plan-related queries. But instead of replacing human agents entirely, the assistant was designed to be emotionally intelligent and escalation-aware.

Key Design Features:
• Confidence Thresholds: The assistant continuously monitored its confidence score. If it dropped below 75%, it paused and escalated to a human before frustration could build.
• Emotional Tone Detection: Using sentiment analysis, it adapted responses based on user mood (apologetic tone when detecting frustration).
• Metaphorical Language: Complex billing terms were explained using metaphor (“Think of this bundle like a streaming playlist, it includes several services under one price.”)

Outcome:
• 45% reduction in call volume (AI resolved more cases on first contact)
• 12% increase in customer trust scores (measured via post-interaction surveys)

What Made It Work:
The designers didn’t aim to automate everything, they designed for when to automate, how to explain, and where to hand off. The result was an AI that felt like help, not hassle.

Designer’s Role:
• Architect escalation logic and emotional thresholds
• Design “uncertainty states” where AI defers gracefully
• Infuse brand tone and cultural sensitivity

What to Tell Clients:
“We can design a support experience that knows when to stop, and hand off with humanity.”

Takeaway: This isn’t just support automation. It’s what happens when design humanizes escalation, emotion, and trust at scale.

2. Advisory & Intent-Driven Retail Experiences

> Does your AI understand mood, meaning, and culture, or just clicks?

What: Move from segmentation to real-time, AI-driven consultation.

Industry: Luxury Retail
Challenge: Customers were overwhelmed by choice, leading to abandoned carts and missed upsell opportunities, especially during key gifting seasons.

Solution: A global luxury brand launched an AI-powered concierge to assist online shoppers in choosing gifts. Instead of focusing on specs or categories, the assistant guided users through intent-based questions:
“Who is the gift for? What’s the occasion? How should it feel?”

Key Design Features:
• Mood + Occasion Matching: The concierge recommended gifts based on user emotion and event type (romantic vs. celebratory).
• Cultural Intelligence: Designers infused cultural nuance (recommending red-colored products for Chinese New Year or silver for milestone anniversaries).
• Tone Mapping + Escalation Logic: AI responses were calibrated to align with brand tone and knew when to hand off to a human stylist.

Outcome:
• 39% increase in high-value purchases during the Q2 gift season
• Improved basket sizes and lower drop-off during decision-making

What Made It Work: Designers treated the concierge like a relationship builder, not a search engine. By focusing on mood, meaning, and cultural symbolism, they created a personalized shopping experience that felt intelligent, and intentional.

Designer’s Role:
• Define personalization ontology (behavior, emotion, context)
• Design for multi-channel orchestration (when does a human join?)
• Set ethical limits on upsell, data use, and suggestive nudging

What to Tell Clients:
“Let’s build an AI concierge that understands mood, not just clicks.”

Takeaway: This isn’t personalized UX. It’s what happens when design turns mood, meaning, and culture into system logic.

3. Operational & Delivery Layer AI

> Where is your intelligence hiding, and how do you make it visible?

What: Embed intelligence where the business actually runs.

Industry: Logistics & Supply Chain
Challenge: Delivery delays were increasing due to unpredictable variables like weather, driver fatigue, and last-mile congestion. Existing dashboards overwhelmed teams with false alerts and unclear priorities.

Solution: A global logistics network integrated AI into its operations to predict and proactively manage disruptions before they cascaded into missed deliveries or unhappy customers.

Key Design Features:
• Predictive Disruption Modeling: AI analyzed weather forecasts, local events, and real-time traffic to flag potential delivery risks.
• Sentiment Analysis from Driver Logs: Using NLP, the system detected signals of burnout, frustration, or morale issues from driver comments, triggering early interventions.
• Dashboard Redesign: Designers simplified the operational dashboard to highlight only actionable signals, prioritized alerts by confidence score, and clarified handoff points between teams.

Outcome:
• 21% reduction in delay incidents
• Improved frontline satisfaction and trust in the system

What Made It Work: Instead of just adding AI, designers focused on making intelligence usable. By reframing the dashboard and building in signal confidence, they reduced noise, increased clarity, and empowered teams to act early, and act well.

Designer’s Role:
• Reframe AI from surveillance to enablement
• Design actionable dashboards and signal confidence indicators
• Build exception-handling into systems with transparency

What to Tell Clients:
“We don’t just optimize processes. We make intelligence visible and usable.”

Takeaway: This isn’t dashboard polish. It’s what happens when design makes operational intelligence visible, usable, and humane.

4. Internal Enablement & Service Design Operations

> What would your organization look like if its systems coached, not just tracked?

What: Make client teams smarter, faster, and more coordinated.

Industry: Human Resources & People Operations
Challenge: Managers struggled to detect early signs of burnout, disengagement, or team strain, leading to delayed interventions, preventable attrition, and declining culture scores.

Solution: An enterprise HR team deployed an AI-powered internal coach to support managers by surfacing trends and nudging timely, human responses.

Key Design Features:
• 1-on-1 Theme Synthesis: The AI reviewed manager notes and HR system inputs to identify recurring team concerns (workload, role clarity, interpersonal friction…).
• Burnout Signal Detection: It monitored language tone, missed 1-on-1s, and feedback patterns to flag early indicators of employee fatigue.
• Manager Nudges & Escalation Logic: Designers built discreet nudges (“Check in with Morgan this week — burnout signals rising”) and embedded clear opt-out paths with full transparency to protect trust and autonomy.

Outcome:
• Improved employee retention
• Earlier burnout detection and faster team interventions
• Measurable lift in internal culture and engagement scores

What Made It Work: Designers didn’t build surveillance. They built support systems. By combining psychological insight with transparent, opt-in AI, the system felt like a coach, not a monitor.

Designer’s Role:
• Design behavioral nudges rooted in psychology
• Ensure transparency in recommendations (“Why am I seeing this?”)
• Create opt-out paths that protect user autonomy

What to Tell Clients:
“Let’s design AI that doesn’t replace leadership, but empowers it.”

Takeaway: This isn’t employee surveillance. It’s what happens when designers embed care, clarity, and coaching into the systems people live within.

Now ask yourself: Where in your world — your team, your client, your system — should intelligence emerge next?

From AI Curiosity to AI Fluency

As a design strategist, your job isn’t to become a prompt engineer. It’s to ask:
• Where is intelligence missing from this experience?
• What adding speed unlocks here, and what must remain human?
• Where is the user still guessing, when they could be sensing?
• What invisible behaviors are shaping the experience, and how might we influence them?
• Where is complexity blocking action, and how can Artificial Intelligence create clarity?

“Applied AI isn’t about adding magic. It’s about removing friction, even at the smallest, most tedious experience levels, and unlocking what systems can truly accomplish when they’re designed to think.”

This isn’t about designing outputs. It’s about orchestrating intelligent systems that adapt, evolve, and drive results.

The post-hype AI era won’t be won by technologists or prompt engineers.
It’ll be won by designers who can understand systems, shape experiences, and operationalize intelligence with care and thoughts.

So stop debating. Ignite AI already.

(Disclaimer: The companies, projects, and examples mentioned in this article are based on publicly available information and industry best practices. No proprietary or confidential information has been disclosed, and all references are for illustrative purposes only. This article does not represent insider knowledge or violate any non-disclosure agreements. Some AI tools could have been used for basic editing, research and visuals, but the insights and perspectives are entirely human.)

Design is still a strategic force, but it’s misaligned with the realities of today’s business, and it won’t reclaim its value until it reconnects with what companies actually prioritize.

Design earned its seat at the table, but business is accelerating at blistering speed, and design is lagging behind. If we don’t reconnect with what companies actually prioritize, we risk becoming a supporting act in the story we helped start.
To understand why design is losing traction, we need to understand what business is actually focused on.

Business Is Moving On, With or Without Us

It’s July 2025. Global volatility isn’t a background condition, it’s the stage. From generative AI displacing roles and redefining business models, to trade alliances fracturing under geopolitical tension, to consumers growing savvier and less patient, the pace of change has outstripped the pace of design.

Based on what we are currently hearing across client engagements and executive conversations with our Fortune 500 partners, here’s what’s dominating the boardroom agenda today:

1. AI integration and automation
2. Geopolitical risk navigation
3. Cybersecurity hardening
4. Operational efficiency + cost reduction
5. Workforce transformation
6. Supply chain resilience
7. Customer experience retention
8. Regulatory agility
9. ESG compliance (not transformation)
10. M&A strategy in uncertain markets

These core business priorities reflect what senior executives are telling us today, and they’re confirmed by leading business reports from McKinsey, KPMG, BCG, and more.

Now, notice what’s missing from that list.
No mention of delightful experiences.
No emphasis on human-centered design, design thinking, accessibility, carbon footprint, sustainability or any current design trends.

These are mantras in the design world, repeated often, sometimes dogmatically. But in the boardroom, they’re rarely mentioned. At best, they’re footnotes. At worst, they’re considered distractions.

So why the deep disconnect? Has design become out of touch with the reality of business?

Designers are some of the most adaptive, systems-minded professionals in business, but we need to update our language, our framing, and our metrics to match the speed, stakes, and pressure of today’s business environment.

“Great ideas don’t matter if they don’t connect. Without translation and alignment, even our best work becomes a distraction, or worse, a cost center.”

When Design Solves Real Business Problems

Let’s be clear: Design can solve for growth, efficiency, and resilience. And it already has:

• Maersk tapped into strategic design during the Suez Canal blockage, mapping port operations to minimize delays, reduce cost, and restore client confidence.
• Intuit redesigned TurboTax for gig workers using service design, leading to a 20% conversion jump from free to paid.
• Bank of America’s “Keep the Change” wasn’t just a clever UX idea, it became a multi-billion-dollar customer acquisition engine built on behavioral insight.

In each case, design wasn’t cosmetic. It was a force multiplier for business value. But here’s the uncomfortable truth: These major business wins are the exception, not the expectation. And that is exactly what we must change.

The Design Bubble Is Holding Us Back — It’s Time to Break Out.

Based on what I’m hearing directly from our enterprise clients and from senior leaders in the market, the perception of design is eroding. Not because it doesn’t work, but because it’s working on mismatched business problems.

In our comfortable design echo chamber, we romanticize delight and emotion. Outside that bubble, the CFO is asking how we’ll cut operating costs by Q4.

Designers say: “We need to lead with empathy.”
Business leaders say: “We need to lead with margin discipline.”

“Business can no longer afford to wait six to eight weeks for basic UX research while market conditions shift overnight. The pace of business today is dizzyingly fast, and it’s outpacing the outdated academic rituals of design. It’s time we rethink our timelines, our roadmaps, and the true scope of our methods.”

And increasingly, we are seeing dire real-world consequences to this dichotomy:

• Multiple Fortune 100 companies have dissolved their UX Center of Excellence, not because they didn’t care about UX, but because they couldn’t prove its value.
• Several global consultancies have replaced design strategists with AI delivery leads across key digital accounts.
• Many Product orgs are shipping faster by bypassing design altogether, treating it as a bottleneck.

“Design isn’t being fired, but it is being quietly bypassed. If we want to reclaim relevance, we need to show business how design drives outcomes.”

The good news? Some design teams already are. Service, business and strategic designers have quietly embedded themselves deep inside the business engine, not just advocating for better experiences, but helping drive critical business outcomes.

Service Design In Action: Delivering on Business Priorities

While design doesn’t appear by name on most executive dashboards as seen above, service design and strategic design are actually quietly doing critical work behind the scenes.

“In fact, it’s no surprise that many executives now refer to Service Design as “Business’ Best Friend”, thanks to its deep roots in business empathy and its ability to work holistically across both the visible and invisible layers of an organization.”

These aren’t surface-level interventions. These are the disciplines working in the backstage: Employee workflows, support functions, internal policies, and command structures where business decisions actually take shape.

“Business doesn’t have to choose between delight and performance. They’re not mutually exclusive.
A well-designed experience can be a cost-saving engine, a compliance solution, a churn-reduction lever, or a trust-building mechanism. The best design delivers both.”

The truth is: We’re already solving core business problems, not theoretically, but tangibly.

What’s been missing isn’t the impact, it’s the translation.
Too often, we’ve framed our contributions as craft when they’re actually strategy. Framed as outputs when they’re actually levers for growth, resilience, and transformation.

It’s time we told the real story, not of what design wants to do, but what it’s already doing when applied at its highest level:

AI Integration and Automation

Design’s Role: Mapping new service ecosystems to integrate AI without eroding trust, jobs, or experience.
Example: At a North American financial institution, our team used service design blueprints to integrate conversational AI into customer service channels without displacing human agents, maintaining a seamless experience while reducing response time by 35%.

Geopolitical Risk Navigation

Design’s Role: Scenario planning and strategic foresight to design for unstable environments.
Example: A Fortune 500 logistics firm engaged strategic designers to model alternate service routes and customer experiences in response to trade sanctions and port disruptions, helping them pivot and retain 92% of their B2B contracts during political upheaval.

Cybersecurity Hardening

Design’s Role: Human-centered approaches to threat modeling, behavior change, and secure process flows.
Example: A major cloud platform used service design to redesign internal provisioning workflows, reducing phishing risk by simplifying the employee access journey and introducing guardrails at key moments of vulnerability.

Operational Efficiency + Cost Reduction

Design’s Role: Identifying redundancies and streamlining complex operations across silos.
Example: In healthcare, a service design team redesigned patient intake journeys across 5 hospitals. The result: 27% fewer repeat appointments due to miscommunication, saving millions in administrative overhead.

Workforce Transformation

Design’s Role: Reframing the employee experience as a journey — not just an HR process — to support hybrid work, upskilling, and retention.
Example: For a global consulting firm, strategic design was used to map the career lifecycle across hybrid work models. The insights led to a redesign of onboarding and learning touchpoints, improving first-year retention by 18%.

Supply Chain Resilience

Design’s Role: Mapping ecosystems and dependencies to increase adaptability and responsiveness.
Example: At a multinational CPG company, service designers partnered with logistics to visualize supplier touchpoints across 12 countries. This visibility helped them diversify suppliers and reduce lead times by 23%.

Customer Experience Retention

Design’s Role: Designing omnichannel service experiences that reinforce value and loyalty.
Example: A telecom provider used service design to fix a fragmented cancellation flow, redesigning it into a guided, supportive “pause or downgrade” journey. Result: churn dropped by 9% in Q1.

Regulatory Agility

Design’s Role: Making complex regulations human-understandable and designing compliant processes that don’t kill experience.
Example: An insurance startup partnered with design strategists to build a claim experience compliant with new state-level laws. The UX redesign maintained compliance and reduced processing time by 48%.

ESG Compliance

Design’s Role: Operationalizing ESG touchpoints through customer and employee journeys.
Example: A fashion brand needed to comply with new product traceability laws. Service design helped embed transparency features into the product lifecycle, resulting in 3x higher customer trust ratings on traceability disclosures.

M&A Strategy in Uncertain Markets

Design’s Role: Aligning post-merger services, branding, and internal workflows to protect value and reduce friction.
Example: Following a major tech acquisition, service designers were embedded in both companies to harmonize service offerings, reduce brand confusion, and integrate onboarding journeys — enabling a unified product rollout in 6 months instead of 12.

So how do we scale this kind of impact beyond isolated wins? Here’s the playbook.

5 Simple Moves That Turn Design Into a Business Driver

Service, Business and Strategic Design are already solving real, measurable, board-level problems, we just need to start framing them that way.

This is not about defending design. It’s about positioning design where it belongs: At the heart of transformation, not the edges of aesthetics.

Solving real problems is only half the battle. Framing them in business terms is the other half. To regain trust and relevance, we need to change how we operate, and how we communicate our value.

Design is at a crossroads. We CAN build real currency in the boardroom. Here’s 5 very simple ways to right the ship:

1. Stop Designing for “Users.” Start Designing for Outcomes.

Don’t ask: “What would delight the user?”
Ask: “What would reduce churn by 12%?”
Example: One of our B2B SaaS clients improved onboarding flows. But what got the business excited wasn’t the UX, it was a 6-week reduction in time-to-value, translating to millions in ARR acceleration.

2. Speak the Language of Business

Empathy maps are a great start. But they must translate into measurable business value to earn trust and investment. Awards celebrate creativity, but business celebrates outcomes. Let’s aim for both.
Example: A major retailer reworked their checkout UX. Design pitched it as cleaner UI. Product reframed it as a 0.8% lift in conversion, $22M in annual revenue. One got applause. The other got funding. Guess which one?

3. Design for Systems, Not Screens

Designers need to go beyond front-end polish and think like operators.
Example: In 2023, a global airline launched a beautifully designed baggage flow experience. But no one consulted IT or logistics. Backend failures led to class-action lawsuits and $20M in liabilities, all while the design team won awards. Guess how business is feeling about those awards?

4. Get in the War Room, Not just the Workshops

If you’re waiting for a stakeholder invite, you’re already behind. Show up to M&A discussions. Tie your prototype to risk mitigation, not just inspiration.

5. Drop the Jargon. Embrace the Numbers.

“We improved UX” gets eye-rolls.
“We cut support calls by 18% and saved $6.2M” gets buy-in.

Integrating Design Into Business: A Strategic Imperative

Our current work across North America confirms what the data suggests: Design still matters, but only if we can tie it to what matters most to the business.

> How to Make Design Irresistible to Business:

• Start every project with a clear business metric, not a user need alone.
• Learn your CFO’s top 3 concerns this quarter, and design for one.
• Tie every insight to a business cost, risk, or opportunity.
• Speak less about process, more about progress.
• Lead with outcomes, not outputs
• Show up where decisions are made, not where wireframes are drawn
• Translate empathy into economic value
• Prototype risks, not just features
• Measure what business values (not just what design loves)

We can’t keep designing for the world we wish existed.
We must design within the complexity of the world that exists today.

“Because business doesn’t owe design a seat at the table.
We have to earn it, every single quarter.”

The best news? Design already has the tools. We map complexity. We humanize systems. We’re fluent in both vision and implementation. We just need to speak the language of outcomes, and step fully into the business arena.
Design doesn’t need saving, it needs reframing.
Business is ready. Are we?

(Disclaimer: The companies, projects, and examples mentioned in this article are based on publicly available information and industry best practices. No proprietary or confidential information has been disclosed, and all references are for illustrative purposes only. This article does not represent insider knowledge or violate any non-disclosure agreements. Some AI tools could have been used for basic editing, research and visuals, but the insights and perspectives are entirely human.)