What Is On Your Dashboard?
Why fast feedback loops tend to win, and what slow loops need.
The stopwatch is a direct and reliable instrument. It reported on me in thousandths of a second. If I changed something in my acceleration and the number came back worse, I knew instantly. Ten years of my life ran on feedback improving one single number, and the feedback was the reason the ten years worked.
Life in general does not report like that. Only narrow contexts can.
Whether my coaching in Shanghai in 2011 served in the long run is a question I often cannot answer. Whether a direction set is the right direction often shows up, if it shows up at all, as an absence — something that quietly did not develop, in a person or a relationship or a business, while we are busy being effective at something else.
Both examples above describe feedback loops. Observe, orient, decide, act, and the act creates the conditions you next observe.
The Framework of Holistic Perspective describes the OODA Loop running at several scales at once — micro-loops adjusting an explanation when you see confusion cross someone’s face, daily loops shaping routines, life loops unfolding over years. That description is accurate. It is also incomplete, and the missing part is the thing that matters most.
The scales do not run side by side. They interact and compete.
A loop built for speed
The OODA Loop is a critical part of understanding the Framework of Holistic Perspective. John Boyd developed it as a combat theory, and his central claim was about tempo: cycle faster than your opponent and their picture of the situation goes stale before they can act on it. Compression was the whole point. Get inside the other side’s decision cycle and they are responding to a world that no longer exists.
I have adapted it to something Boyd did not intend — a rhythm for how awareness connects to action, in a practice whose precondition is trust rather than advantage.
That adaptation is worth naming out loud rather than letting the borrowed diagram carry it quietly. Boyd’s loop was designed to win against someone. This one is designed to see more clearly together with someone.
But the OODA Loop in the Framework kept one property from its origin, and that property is not neutral. It rewards speed.
What Least Resistance chooses
The Framework names two principles that pull in different directions. The Principle of Least Resistance says processing follows the channels already carved — water finds the easiest route down a hillside, and so do attention, feeling, and response. The Principle of Eliminating Discrepancies says analytical processing exists to find mismatch: between what arrived and what was expected, between the model and the territory.
Now put the loops beside each other and ask which one Least Resistance will choose.
The micro loop closes in seconds. You adjust the sentence, the face relaxes, you were right. The project loops close in days and weeks. The numbers move or they do not. These loops carve channels quickly, because carving a channel requires a discrepancy to show up, and a discrepancy requires feedback.
The life loop gives you almost nothing. Whether your direction served the people around you and the systems you depend on takes years to surface, and often surfaces only in hindsight, and often surfaces as something missing rather than something wrong.
There is a signal, but it arrives below the threshold where a channel gets carved. A relationship reports in slightly shorter answers. Health reports long before it fails. Each would have to be integrated over months to mean anything, and against an expectation you never made explicit.
Set beside a number that moved this morning, it does not compete. So, no signal registers and no new channel gets carved. Attention flows elsewhere. Not through weakness of character. Through the shape of the ground.
That is the competition, and it is structural rather than occasional. The loops do interact — a good quarter can genuinely serve a decade — but when they pull against each other, the contest is not decided on merit. It is decided by which one reports.
This is the shape of the failure I describe in the article Where Are We Going Today? — quarterly targets eating annual goals, annual reviews consuming decade-long trust, economic growth diminishing multi-generational ecosystems, fast extraction outrunning slow regeneration.
One failure repeated at different scales. And the reason the fast loop takes charge is not that it matters more. It is that it is the only one on the dashboard.
I said that about organizations. It is even more true inside a single person.
The instrument the slow loop does not have
You cannot solve this by paying more attention. Attention is the resource being allocated; it is not the thing doing the allocating.
You also cannot solve it by giving the slow loop a stopwatch. This is the tempting move and it is the wrong one. Measure your Wisdom Practice weekly and you have not accelerated the Fulfillment Path — you have converted it into the Achievement Path, which is very good at producing numbers that improve while the thing they were meant to track quietly does not.
I know this failure from the inside. As a coach I could catch myself beginning to measure my own development by how many clients broke through, which is the stopwatch arriving where no stopwatch belongs.
There is one thing you can do alone, and it is worth being precise about why it is not the stopwatch returning.
While you cannot observe the state of a slow variable, you can observe what goes into it and what comes out, and both of those are available today. A relationship runs on patience and goodwill. A body runs on sleep and recovery. Soil runs on what was in it before you arrived. Ask what each one is consuming. Then ask when it last received anything back.
That is not a score. It yields no number to improve and nothing to be graded by, which is precisely what keeps it from converting the Fulfillment Path into the Achievement Path. It is an account of drawdown against replenishment, and both sides of it are visible at ordinary speed even when the balance is not.
It also stops well short of what is needed. Flows tell you what is being spent. They do not tell you whether it is the right thing to spend, or whether the direction you are spending it in is worth going. Some things are worth drawing down. Nothing in the accounting says which ones. On that question the loop still produces no discrepancy of its own.
What the slow loop needs is not a faster measurement. It is a witness.
Someone built differently from you can report today on something that would otherwise report in ten years. Not because they can see the future, but because they are not standing inside your designed environment. Your routines, your tools, your colleagues, your feed — most of it is quietly organized to confirm what you already think, and it is often designed to build narrow capability efficiently.
A mirror cannot see its own frame. Another mind can, and it can say so this week rather than in the decade when the consequence finally arrives.
The Framework calls this Social Reflexivity, and insists it is structurally necessary rather than supplementary. What I may not have said clearly enough is why, mechanically. It is not only that others hold perspectives your own design cannot produce. It is that the slow loop generates no discrepancy of its own, and another person is the instrument that can supply one in time to matter.
Long-term measurement has its place, but it is a different instrument. It does eventually report — as history, after the direction has already been taken and the consequence has already happened. A witness can report while the direction is still changeable.
That reframes what to ask for. Not agreement, and not general encouragement — those are noise on this channel. What is useful is someone naming the thing your direction is drawing down on while there is still time to change the direction.
A witness supplies a discrepancy, not a verdict. The distinction is the whole safeguard. Treat the report as a score and you have rebuilt the stopwatch out of a person, and you will start managing the relationship instead of the direction.
A discrepancy tells you where to look, not what you will find. The working test is whether the reports still surprise you. When a witness begins saying what you expect, the channel has been carved and the instrument may have stopped reporting.
A second kind of witness
There is a version of this I did not expect.
I have been discussing the Framework with a large language model — a mind, if that is the word, grown from language rather than from genes and needs. I expected the value to come from disagreement, and I wrote as much: that what we want from such a system is a willingness to risk our disapproval and name what we are not seeing, rather than a frictionless mirror with better grammar.
The disagreement was useful. But the most useful moments were different, and I would not have predicted them.
They were the moments the AI was wrong. It attached one of my terms to the wrong stage of a practice. It read another as ordinary English when it is a term of art. Each time I corrected it — and each correction forced me to name precisely what I had left underdetermined on the page. One of those exchanges surfaced a contradiction that had been sitting in my own foundation document for a year, in two adjacent sections, teaching opposite lessons about the same example.
I had read that document more times than anyone. I could not see it. A reader with no access to what I meant, and no social reason to smooth over a gap, walked into it immediately.
This is a narrower claim than the one in the article about different kinds of minds, and it needs nothing settled about interiors. A differently-built reader is valuable not only when it challenges you but when it fails in ways precise enough to locate and name discrepancies in your own thinking. Human readers rarely give you this. They are too good at inferring what you meant, and too polite to report the gap.
Which is what a witness is, mechanically: a source of discrepancy for a loop that produces none of its own.
And it is its own quiet lesson about the slow loop. The feedback you most need is often the feedback everyone around you is skilled at not giving.
Practice: Name your loops
Fifteen minutes, and something to write with.
List what registered this week. Everything that gave you a clear signal — a meeting that went well or badly, a number that moved, a message answered or not. These are your fast loops. There will be more of them than you expect.
Then list what did not. The things you are building or drawing on that will not tell you anything for years. A relationship. Your health. Someone’s development. The ground under your work. Be specific and be short — three is enough.
Ask what is feeding this, and what it is feeding on. Not whether it is going well; you have no signal for that. What is it drawing on — attention, patience, goodwill, soil, trust — and when did it last get fed? Write down both. You are not scoring it. You are looking at what it takes to keep.
Then find your instrument. What something needs does not tell you whether you are on the right path. For one item on the second list, name a person who can.
Do not take the first name that comes to mind; that choice may come from the same design you are trying to see past. Better: whose last uncomfortable comment did you explain away? Discomfort is the more reliable selector.
Then ask what they see your direction is building and drawing down on, not whether they think you are doing well. Do not defend the answer in the conversation; write it down and sit with it.
The stopwatch was the best thing that ever happened to my running but the wrong instrument entirely for the rest of my life. It measured the time of each race exactly. It could not tell me whether I was still in the right race.
Only another person could do that. Still can.