An organization can make decisions faster than it can learn from them.
That is the tension behind my talk, Faster Isn't Smarter. AI can shorten the time between noticing a problem, interpreting information, choosing a response, and taking action. The consequences of that action may still take days, weeks, or months to become clear. Speed creates an advantage when we can use it well. It also makes it easier to repeat a mistake before we recognize the first one.
Imagine a customer-support team introducing AI-assisted replies. Employees respond more quickly. The queue shrinks. Managers see an encouraging early result and expand the system's role.
A week later, repeat contacts begin to rise. Some customers received incomplete answers. Others were sent to the wrong team. Experienced colleagues are now checking and correcting work that used to arrive more slowly. The first dashboard recorded a productivity gain. It did not yet capture the consequences.
This is an illustrative scenario, but it makes the management problem visible. Different parts of the same workflow run on different clocks.
The decision loop includes sensing, interpreting, deciding, acting, observing, and learning. Accelerating the first four steps does not guarantee that the last two keep pace. Sometimes AI can help there too, by surfacing patterns or connecting signals that were previously scattered. Sometimes the evidence simply takes time: a customer has to try the solution before we know whether it worked.
When leaders change direction repeatedly during that interval, they also make learning harder. Was the result caused by the new tool, a policy change, different staffing, or a change in the mix of cases? If everything moves at once, it becomes difficult to know what to repeat.
My starting point is to separate three questions that often become blurred in AI reviews.
Who is using the system? What work became faster? Did the outcome improve?
Usage tells us something about access, relevance, and adoption. Output measures tell us what people or systems produced. Outcome measures tell us whether the work achieved its purpose. Each is useful. Each answers a different question.
For the support team, that means looking beyond response time to repeat contacts, resolution errors, review effort, and total cost per resolved issue. It also means agreeing on what counts as resolved. Closing a ticket is an action in a system. Solving the customer's problem is the intended result.
One of the most useful exercises is to bring the team celebrating an AI productivity gain together with the team receiving its output. Trace an actual piece of work. Ask what the recipient needs before trusting it, where it waits, and what must be checked or redone.
That conversation can reveal a genuine improvement. It can also reveal that the bottleneck moved. Either finding gives leaders a better basis for their next decision.
The next question is what AI should be allowed to do within that workflow. I use four considerations: how quickly reliable feedback arrives, how clearly we can connect actions to results, how reversible the action is, and how serious the consequences could be.
Drafting a reply and issuing a refund are different decisions. A draft can be edited before it reaches anyone. An incorrect refund may be difficult to recover. Many small refunds can create substantial exposure before someone notices a pattern. The same model can therefore deserve different authority at different points in the process.
The graduated autonomy ladder makes that distinction practical. AI may observe, advise, prepare work for approval, act within defined bounds, or coordinate a workflow under delegated authority. Movement along the ladder should follow evidence and effective controls. Authority can also decrease when conditions change.
There is no requirement for every workflow to reach the highest level. An assistant that helps a leader challenge a strategic assumption can be extremely valuable while never being permitted to commit resources.
Before expanding authority, define what would justify the change. In the support example, compare representative cases with the existing process, agree on acceptable quality and cost, and allow enough time to observe repeat contacts. Decide in advance which errors trigger an immediate pause and who can restore human review.
This protects the learning process without requiring the organization to stand still. Teams can monitor continuously, investigate emerging issues, and intervene when harm appears. Routine changes can wait for an agreed review when doing so preserves the ability to interpret the evidence.
For leadership teams, this creates a different conversation about speed. The useful question becomes how quickly the organization can reach a trustworthy conclusion and act on it. A rapid action followed by weeks of invisible repair may be slower, in business terms, than a deliberate decision that holds.
In your next AI review, choose one celebrated speed gain and ask when its downstream consequences become visible. Does the decision to expand wait for that evidence, or has the organization already moved on?