Alignment
The angle between intent and behavior. A smaller angle means the operating system is carrying the strategy more faithfully.
Research partnership, not a vendor engagement · John Brand
I work with a small number of organizations as research partners. We survey teams over time and track whether that gap is closing, holding, or widening. The work gives management a plain read on where the system is aligned, where people are compensating, and where drift is becoming structural.
One arrow points where the organization says it is going. The other points where repeated decisions, incentives, and daily behavior are actually taking it.
What is the stated priority when the organization has to make a real tradeoff?
What do people learn to do from the way work is measured, rewarded, corrected, and resourced?
The gap is alignment. The way that gap changes over time is drift.
The angle between intent and behavior. A smaller angle means the operating system is carrying the strategy more faithfully.
The direction and speed of change. A modest gap that keeps widening is more dangerous than a larger gap that is being corrected.
The time between changed behavior and management seeing it. The longer the lag, the longer the system can move in the wrong direction unnoticed.
Some variation is normal. The question is whether a deviation remains inside a deliberate boundary—or whether the boundary quietly moves to excuse it.
Regulation, physics, customers, capacity, and resources set limits that an internal story cannot negotiate away.
A meeting, action item, or closed report does not prove learning. The test is whether the behavior changes and the failure stops returning.
Effort enters a system shaped by context. Friction creates evidence. Recognition has to turn that evidence into revision. Reward and timing decide whether the loop strengthens alignment—or teaches people to work around the system.
From the original working sketch
The first model already contained the moving parts: effort, timing, contextual value, learning, error, friction, revision, recognition, reward, and performance.
The operational framework turns those relationships into three readings. I do not trust any one of them by itself.
Every quarter is read through recurrence, incentives, and coherence. When those signals disagree, the disagreement is evidence.
ERSI follows known failure patterns after corrective action. If the same error keeps returning, the system has documented activity—not demonstrated learning.
What a falling signal means: correction is surviving contact with the next cycle.
IAC compares the stated priority with what receives pay, praise, attention, protection, and status. People learn the real priority from reinforcement, not the poster on the wall.
What a weak signal means: the system is teaching people to optimize something else.
SCS tests whether leaders, managers, and frontline teams understand the same priorities and tradeoffs. Shared words do not guarantee shared meaning.
What high variance means: strategy is being lost in translation.
A healthy outcome metric can sit beside rising friction and worsening leading indicators. I read the three indices together so one strong number cannot hide the cost being absorbed somewhere else.
Organizations often look stable because people are carrying the misalignment themselves.
Somebody is usually paying for the appearance of order. The dashboard may simply be the last place that payment shows up.
People add hours, attention, and workarounds to preserve output after the process has stopped supporting it.
Necessary recovery, checking, chasing, and coordination consume capacity without appearing in the formal measure.
Experienced people teach others how to avoid failure without the organization ever recording the lesson or fixing the source.
The meeting happened. The action was assigned. The form was closed. The same failure still comes back.
When people quietly absorb friction, management sees a stable result after the operating system has already changed. Repeated measurement makes that hidden cost visible before exhaustion, recurrence, or outside failure finally exposes it.
Change the observed angle. The model translates direction into alignment and shows when behavior moves outside the selected tolerance.
Strategic intent stays fixed. Move observed behavior away from it to see how directional coherence changes.
I establish a baseline, survey the same operating system at regular intervals, and read the movement together with the partner organization. The value is in the trend.
Choose the team, process, decision boundary, and period being examined. The unit of analysis stays clear.
A structured team survey establishes ERSI, IAC, SCS, masking, and feedback-lag signals.
The core measures return quarter after quarter so change can be separated from a temporary reaction.
The partner organization receives the trend, the evidence behind it, and the next question to test, without ranking or blaming people.
The partnership produces a repeatable view of direction, not another survey deck that disappears after presentation.
“Fixed” is not assigned because an action was closed. It is earned when the next cycle shows that behavior changed and stayed changed.
Research partnership
If your organization is willing to be studied honestly, let's talk about a research partnership. The first study establishes a baseline, identifies where drift may be forming, and gives management a clear question to test next.
These case sketches show how the framework reads a system before the final failure becomes the whole story.
The O-ring problem was known, recurring, and documented. The deeper failure was that the evidence did not produce correction proportional to what it revealed.
The headline sales measure kept rising while the reward system pulled behavior away from the stated purpose of serving customers.
Neither case begins with a bad person. Both begin with a system that keeps absorbing evidence without changing direction.
The formal model explains the mechanics. The partnership tests whether those mechanics are moving inside a real organization.
The papers
A Dynamic Systems Model of Alignment Over Time defines alignment as directional coherence, drift as the rate of angular change, and the three-index method used in the partnership.
The broader body of work develops the original circle model, the masking mechanisms, and the relationship between effort, timing, recognition, reward, and performance.
About the work
John Brand developed the framework from years of watching how organizations respond to repeat problems at both the operating and leadership levels. His background combines 15 years in machine shops, a degree in law and public policy, and graduate study in executive leadership.
The rule is simple: attack systems, never people. The purpose is not to assign fault. It is to show management what the system is teaching, where the signal is being lost, and whether correction is actually holding.
Become a research partner
If your organization is willing to be studied honestly, let's talk. The first step is a conversation about the system, not a sale.