Watching

Only three things can make a position wrong. The river can move, a competitor can move, or you can be wrong. One question each, re-asked on a rhythm.

They never get finished. They get re-answered, and the answer is supposed to change.

Start by naming the outcomes. Every question below gets asked about a specific outcome you own. Asked about AI in general, they collect news and change nothing.

Two objects

The river. What agentic AI is doing: how fast capability is advancing, and how fast real adoption is happening.

Your boat. What you're doing about it: how far toward reimagine you have gone on each outcome, and how you have set the three tensions.

A competitor is another boat on the same river. That is the third way a position goes wrong, and it is the one you see late.

Question 1. The river.

Has a capability crossed from demo to deployable against the work behind this outcome?

Look past the announcement. What you want is a capability, a way to deploy it against work you can structure, and controls you can defend, all arriving in the same window. The press release is not the signal.

Question 2. Your competitors.

Has someone reset what good looks like for this outcome?

You will see this late. Another company's operations are invisible to you, so what arrives is the downstream evidence: their pricing, their turnaround times, their job postings, their headcount against their revenue, or your own customer mentioning that somebody else does this faster. By the time it's unambiguous, the gap is usually a year old.

So Question 1 is where you act. Question 2 is where you find out whether you acted in time.

Question 3. Your own boat.

Has anything you assumed about your own position on this outcome stopped being true?

Two modes, and both are needed.

Go and look. Every triage you made was a bet that certain outcomes could wait. This one needs a date in the calendar, because a bad bet stays quiet. The work you set aside confidently is the work most likely to surprise you, precisely because you stopped looking at it.

Watch for it. Budget tightening, a merger, a governance board narrowing what agents may do, losing the people who held the context. These usually have a long engagement cycle in front of them, and you are in that cycle. Being told about one is the failure case.

Assumptions break in both directions, on three axes:

• Timing. Something is moving faster or slower than you assumed.
• Means. You can commit more or less than you assumed.
• Permission. You are allowed more or less than you assumed.

The favorable breaks matter as much as the adverse ones, and they get acted on far less. Nobody calls a review because the budget went up. But if the CFO doubles the AI budget, or the governance committee relaxes constraints because the built-in governance you put in place actually worked, your position is now sitting further back than it needs to be. That is a gain sitting unspent, and it expires quietly.

Two things that will trip you up

The test is where a change lands, not what caused it. A rebudgeting driven by rising demands for real return on AI spend starts out on the river and reaches you through your CFO. It is still a Question 3 item, because it landed on your boat. So is a competitor's public reversal that makes your own board cautious: their failure changed what you are permitted to try, rather than what good looks like. Without this rule, somebody reasonable will argue the budget cut is really Question 1 because AI economics caused it, and you'll spend the meeting on filing instead of on watching.

Now is different from coming. A capability that has crossed means move. A credible signal that one is about to cross means prepare, and preparing carries a start date: the point at which you would have to begin in order to be ready. Writing up a coming change as though it already happened is the most common error in this whole discipline.

You cannot hand this off

A market-intelligence team can feed the watch. So can an analyst subscription, a consultancy, or a research agent you set up yourself. All four are inputs. The watch itself stays with you.

An outside party can tell you a capability now exists. Only the people steering an outcome can say whether it changed the water around that outcome, because that call depends on knowing the work from the inside. Sensing that gets delegated out of the operating seat quietly turns back into a report you read on a schedule, which is the thing you were trying to get away from.

When the answer is yes

A yes sends you back into the work, and how far back is the measure of how much it matters.

A no obligates nothing, except that you asked. For most of what crosses your desk, the right answer is to note it and carry on.

One rule governs the two rhythms. You sense at the speed of the river, and you commit at the speed your organization can absorb. Watching is cheap and can happen often. The moves it triggers are expensive, land in the middle of operations, and cannot. If your sensing runs at the same slow rhythm as the moves it triggers, you're back to reassessing once a year with extra steps.

Working out how far back a given yes sends you, on an outcome you own, with the two or three executives who own the rest of it, is the harder half. That part takes a session.