Architecting the Change Stack

We’re used to talking about tech stacks—our infrastructure, tooling, and platforms.

With the rise of AI, we’ve evolved that language. Now, it’s all about AI stacks: models, APIs, and data pipelines.

But here’s a subtle—and crucial—thing to consider: AI stacks aren’t just technical. They’re socio-technical. They span not just codebases, but people, culture, behavior, and trust.

So maybe the real challenge isn’t just building smarter stacks.

Maybe it’s time to design what I’m calling the Change Stack.

What is a Change Stack?

Unlike traditional stacks built for speed or scale, the Change Stack is built for transformation.

It starts with a premise: human context isn’t a downstream consideration—it’s foundational.

A well-architected Change Stack would ask:

• Are people ready—not just aware?

• Are systems aligned—not just integrated?

• Is the culture equipped to hold ambiguity, resistance, and growth?

Because speed alone doesn’t drive change.

Systems do.
Context does.
People do.

So, What Stack Are You Running?

As AI stretches the boundaries of what’s possible, let’s design for more than deployment.

Let’s architect the conditions where meaningful, human-centered transformation can take root.

Start by asking yourself:
What kind of Change Stack is your organization running—and what might it need next?