top of page

FIELD NOTE | 

January 13, 2026

Stability Is Not the Opposite of Change

Stability isn't always about making conditions predictable. Sometimes it's about developing enough trust, capacity, and judgment to respond when they aren't.

Gaucho is probably the most well-bred horse we own.

He's also the most difficult.

He's opinionated, willful, and perfectly capable of ignoring a request he doesn't particularly care to entertain. More force doesn't reliably improve the situation. Sometimes he braces against it. Sometimes he gets agitated. Sometimes he simply pushes through and does what he intended to do anyway.

When my thirteen-year-old daughter decided she wanted to become the best rider she could be, I encouraged her to start riding different horses, including Gaucho.

At one point, she came to me frustrated, she coulnd't get him to do what she wanted and exasperated, she finally landed on “I just don't know what motivates him.”

I suggested that maybe she was paying so much attention to what she wanted him to do that she wasn't paying enough attention to what was happening with him.

Something changed after that conversation.

She started paying closer attention to his responses and looking for ways to work with him rather than simply insisting on what she'd originally asked for.

She became less frustrated. She started enjoying him.

She also developed a better sense of which days were good days to ride Gaucho and which days another horse might be a better choice.

She hadn't abandoned her goal of becoming a better rider. She was learning that being a better rider involved more than being able to get a horse to do something.

Sometimes it meant knowing what to ask, how to ask, and when not to ask at all.

Gaucho didn't become a different horse. My daughter didn't need to become a different person. What changed was their relationship.

She began paying attention to what was happening between them rather than focusing entirely on the outcome she wanted. That gave her more ways to respond, even when Gaucho remained stubborn.

She wasn't gaining control by eliminating his resistance or uncertainty. She was developing enough understanding to make decisions without every disagreement becoming a contest.

And that made their relationship more dependable.

I've been thinking about how often we treat stability and change as competing goals.

We imagine stability as preserving what exists and change as disrupting it. But sometimes changing how the parts of a system relate to each other is precisely what creates stability.

My daughter didn't become more confident because Gaucho became easier. She became more confident because she developed a better understanding of how to work with him.

The relationship could accommodate more variation without every disagreement becoming a struggle.

That's a different kind of stability.

It doesn't require everything to stay the same. It creates more ways to respond when things don't go as expected.

Stability isn't the same as control

Organizations often try to create stability by making individual behaviors more predictable.

We standardize processes. Define roles. Establish approvals. Reduce exceptions. Create rules for how work should move from one place to another.

There are good reasons to do these things. Consistency matters. People need to know what to expect. Some decisions should not have to be renegotiated every time they arise.

But control and stability aren't interchangeable.

A process can be highly controlled and still fragile. It works beautifully until something happens that the process wasn't designed to accommodate.

A team can follow every established procedure and still fail to coordinate with the team beside it.

An organization can have clear ownership within every function and remain deeply confused about what happens between them.

In those situations, adding more control to the individual parts may not resolve the instability.

Sometimes it makes the problem worse.

More approvals slow down the response. More detailed procedures create additional exceptions. More tightly defined boundaries make it harder for information to move.

The problem wasn't necessarily that people needed clearer instructions.

It may have been that the relationships between them weren't working.

I think about this when organizations describe a team as resistant to change.

Maybe they are.

But I want to understand what they're responding to before deciding resistance is the problem.

What does the proposed change require of them? What happens to the work they're already responsible for? What information are they missing? What have previous changes taught them to expect? What happens if they try something new and it doesn't work?

Those questions don't eliminate the need for change.

They help us understand what the system can currently absorb.

Sometimes the relationship is the thing that needs to change

We tend to locate problems in identifiable parts of a system.

The employee isn't collaborative. The department is too slow. The process is inefficient. The technology is outdated.

Sometimes those assessments are accurate.

But a system is more than the collection of its parts. It also includes the relationships between them.

A sales team and a finance team can each be doing reasonable work and still produce an unreasonable outcome together.

A manager can have good intentions and a capable employee can have good judgment, yet the way decisions move between them can make both less effective.

Two departments can each understand their responsibilities and still have no shared understanding of the commitment that passes between them.

Changing one of the parts isn't always the answer.

Sometimes what needs to change is how information moves, how decisions are made, how responsibility is shared, or how one part responds when another encounters difficulty.

And sometimes those changes are surprisingly small.

A team gets access to information it previously had to request. Someone gains the authority to make a decision they were already being held accountable for. Two functions agree on what a handoff actually means. A manager stops treating every unexpected result as a failure requiring intervention.

The people may be the same. The work may be largely the same.

But the relationships have changed.

And with them, the range of responses available to the system.

This doesn't mean every relationship can be repaired through better communication or more attentive leadership. Sometimes the structure really does need to change. Sometimes someone lacks the capacity or willingness to participate. Sometimes a boundary needs to become firmer, not more flexible.

But those are decisions I want to make after understanding what is happening between the parts, not merely what each part appears to be doing.

Support changes what becomes possible

There's a word I keep returning to: held.

Not held in place. Not protected from every difficulty. Not controlled so thoroughly that nothing unexpected can happen.

Held in the sense of existing within relationships and conditions dependable enough to allow movement.

A child can explore because there is someone to return to. A team can experiment because one unsuccessful attempt doesn't threaten everyone's livelihood. A horse can encounter something unfamiliar with a rider who is paying attention to its responses rather than treating every hesitation as defiance.

The relationships are different. So are the responsibilities involved.

But there is a common question underneath them: what becomes possible when a system has enough dependable support to encounter uncertainty without immediately becoming overwhelmed by it?

Support doesn't eliminate risk.

It changes which risks can be taken, how difficulty is experienced, and what happens when something doesn't go as expected.

And support isn't always about adding more.

Sometimes it's giving someone room to make a decision. Sometimes it's making expectations clearer. Sometimes it's providing another pathway when the usual one isn't working. Sometimes it's recognizing that the conditions aren't right and choosing not to push forward that day.

That last one matters to me.

My daughter learning when not to ride Gaucho wasn't a failure to make progress. It was part of developing the judgment that allowed her to enjoy riding him.

She had more choices because she understood more of what she was working with.

That's a form of agency that simply insisting on the original plan wouldn't have given her.

Holding something doesn't mean deciding what it becomes

I think this is where holding and stewardship meet.

I've been thinking about Held as an experience and stewardship as the work of creating and maintaining the conditions that make that experience possible.

That work moves outward and forward.

It can apply to a child, a relationship, a team, an organization, a piece of land, or something entrusted to us that will outlast our involvement.

But stewardship has a tension inside it.

Taking responsibility for something gives us influence over its conditions. It doesn't necessarily give us the right—or the ability—to determine everything it becomes.

And there is a difference between creating dependable conditions and requiring predictable outcomes.

We can provide structure without eliminating agency. We can establish boundaries without making every response a test of obedience. We can preserve continuity while allowing the relationships inside a system to change.

We can also get this wrong.

Too little structure can leave people carrying uncertainty they aren't equipped to manage. Too much can make them dependent on someone else's judgment for every decision. What feels supportive to the person providing it may feel restrictive to the person receiving it.

That means holding requires attention, not just intention.

We have to remain responsive to what is actually happening.

Gaucho is still Gaucho.

My daughter is still learning to ride him.

There will be days when they disagree, days when he doesn't want to do what she's asking, and days when another horse is the better choice.

The goal isn't to eliminate any of that.

What changed was her ability to work within it.

I keep returning to the idea that stability is not the opposite of movement.

Sometimes stability is what allows movement.

Sometimes movement is what creates stability.

And sometimes the most meaningful change isn't in the individual parts of a system at all.

It's in what becomes possible between them.


bottom of page