Dignity, Strategy, Technology: Three Axes Every Change Leader Navigates

I've been watching three conversations happen simultaneously in almost every organization I work with — and watching them happen in isolation, as if they're unrelated. The first is about technology: what to adopt, how fast to move, what AI and automation will change about how work gets done. The second is about strategy: how to position, how to compete, how to deliver on commitments that were made before the landscape shifted. The third is about dignity: how people experience their work, whether the change being imposed on them respects their competence and their humanity, whether anyone is asking what this transformation costs the humans inside it.

These three conversations are not separate domains. They are axes — and every change initiative sits at a specific point in the space they create. The organizations that navigate change well are the ones whose leaders can read all three axes simultaneously. The ones that struggle are usually reading one or two while ignoring the third — and the ignored axis is almost always dignity.

I keep returning to a simple frame for this: every decision a change leader makes can be located somewhere in the tension between dignity, strategy, and technology. And getting the balance wrong — in any direction — produces a recognizable kind of failure.

The Technology Axis: What's Possible

Technology is the axis of capability. It answers the question what can we do that we couldn't before? — and in this particular moment, the answer is changing faster than most organizations can absorb.

The pull of the technology axis is real and legitimate. New tools create new efficiencies, new data creates new insights, and AI in particular is reshaping assumptions about what work requires human judgment and what doesn't. Leaders who ignore this axis fall behind. Organizations that don't invest in understanding emerging capability find their strategic options narrowing.

But the technology axis, taken alone, produces a familiar set of symptoms:

• Implementation without integration. Tools deployed before the people using them are ready, before the processes around them have been redesigned, before anyone has confirmed the change solves a problem someone actually has.

• Speed of adoption as the metric. Capability deployed becomes the deliverable. How many teams are using the new platform matters more than whether the platform is making their work better.

• Tool saturation without tool coherence. Somewhere downstream, teams are drowning in systems they didn't ask for and can't reconcile with work that still needs to get done by humans.

Technology answers what's possible. It doesn't answer what's wise or what's right. Those answers require the other two axes.

The Strategy Axis: What's Needed

Strategy is the axis of direction. It answers the question given our position, our constraints, and our commitments, what should we actually do? Strategy mediates between what's possible and what's practical — selecting from the full range of capability the moves that serve the organization's actual objectives.

Strong strategic thinking keeps the technology axis from running unchecked. It asks: does this capability serve our goals? Is this investment proportional to the return? Are we sequencing correctly, or are we building the roof before the foundation?

But strategy, taken alone, produces its own pathology. The purely strategic leader treats the organization as a system to be optimized — roles as functions, people as resources, change as a set of moves on a board. The logic is sound. The plans are coherent. And the implementation fails because the people who have to execute the strategy experience it as something done to them rather than with them.

The pattern is consistent:

• The strategy was right. The execution environment rejected it. Not because people didn't understand it, but because the strategy never accounted for what the change would feel like from the inside.

• Adoption is forced, not earned. Compliance replaces commitment. The metrics may look acceptable in the short term, but the change doesn't hold once the pressure lifts.

• The people with options leave. The people without options disengage. Strategic optimization that ignores human experience is a talent strategy in reverse.

Strategy answers what's needed. It doesn't answer what people can bear or what they deserve. That's the work of the third axis.

The Dignity Axis: What's Owed

Dignity is the axis most likely to be treated as optional — a nice-to-have, a culture initiative, something for the HR team to handle after the real decisions are made. This is a mistake that experienced change leaders learn to recognize, often after paying the cost of having missed it.

Dignity in this context means something specific. It means designing work and change processes that preserve three things:

• Autonomy — each person's ability to trigger their own actions and make meaningful choices within the work. Not just executing instructions, but exercising judgment.

• Advocacy — ensuring that the people affected by change have a voice in how it's designed. Not a seat at the communication briefing. A role in shaping what gets built.

• Agency — the capacity of each participant to govern their own delivery, to contribute skill and competence, not just compliance. Motivated by team norms toward shared goals, not by surveillance toward imposed ones.

When change efforts honor all three, people move from resistance to ownership — not because they were persuaded, but because the process treated them as contributors rather than recipients. When change efforts violate any of the three, resistance isn't a problem to manage. It's a signal that something was designed wrong.

The dignity axis asks questions that technology and strategy can't: Is this change being conducted in a way that people can respect? Are we asking people to abandon competence they built over years without acknowledging what that costs them? Are we designing roles that are worth inhabiting, or are we designing functions that happen to require a person?

These aren't soft questions. They're scope-defining questions, the same way risk tolerance and quality targets define scope. Ignoring them doesn't make the work simpler. It makes the resistance more entrenched and the recovery more expensive.

Where Leaders Get the Balance Wrong

The most common imbalances follow predictable patterns:

• Technology + Strategy − Dignity. The initiative has a clear business case, a capable platform, a well-sequenced plan — and a workforce that feels steamrolled. The plan is technically sound and humanly inadequate. This is the most common failure mode, and it's the one that produces the most expensive downstream resistance.

• Dignity + Technology − Strategy. The organization invests in people, invests in tools, and lacks a coherent direction for either. Teams have autonomy without alignment. New capabilities are adopted enthusiastically but serve no shared objective. The culture feels good. The results don't compound.

• Dignity + Strategy − Technology. These organizations know who they are, know where they're going, and are underinvesting in the capability to get there. They have the human infrastructure for change but not the operational infrastructure. They're ready but under-equipped.

The point isn't to balance all three perfectly at all times. It's to know which axis you're leaning toward — and what the lean is costing you on the others.

Leadership Reflection

• Consider the change initiative you're currently closest to. Where does it sit in the space between dignity, strategy, and technology? Which axis is getting the most attention, and which is being treated as someone else's problem?

• Think about the last time a well-planned initiative met unexpected resistance. Was the resistance about the strategy itself, or about how the change was experienced by the people inside it? What would have shifted if the dignity axis had been designed with the same rigor as the technology and strategy axes?

This post is part of Maypop Grove's Field Notes, insights and perspectives on leading the change we need.