|
AI is not developing your people. It may be improving their outputs, accelerating their work, and making their decisions better informed. Those are real benefits. None of them is development. The distinction between what AI is doing for the people who use it, and what it is doing to them, is the question most organizations have not yet asked. The longer it goes unasked, the more consequential its absence becomes.
Development is not the same thing as performance. A person can perform at a high level while their underlying capacity remains static or erodes. The output looks right. The work gets done. The metrics move in the right direction. What is not visible in any of those measures is whether the person doing the work is developing the judgment, the reasoning capability, and the tolerance for uncertainty that consequential decisions require. Those capabilities are not produced by good outputs. They are produced by the struggle that generates them. Remove the struggle and the output can remain while the development stops.
This distinction has always existed in leadership development. The executive who delegates every difficult judgment call protects their schedule and undermines their own capability. The leader who avoids every uncomfortable conversation maintains organizational harmony and loses the ability to navigate conflict when it cannot be avoided. The development that does not happen is invisible. The deficit it produces becomes visible only when the situation demands what the person can no longer supply.
AI has introduced this dynamic at a scale and with a sophistication that makes it categorically different from any previous version of the problem. AI handles well the cognitive work that is most central to human development at senior levels: constructing an argument rather than transcribing one, synthesizing across competing inputs, generating options under genuine uncertainty, and producing coherent analysis from ambiguous starting conditions. These are not peripheral to human development at senior levels. They are central to it. They are the cognitive activities through which judgment develops. They are the struggle through which uncertainty becomes manageable. They are the process through which a person learns what they actually think about a difficult problem, as distinct from what a well-configured system thinks they should think.
When AI handles that process and delivers the output, the person receives the result of reasoning. The reasoning has not occurred. Not their reasoning. The output is indistinguishable from the output that would have been produced through genuine cognitive engagement. The difference is entirely in what happened to the person in the process of producing it. In one case, something developed. In the other, something was bypassed while its appearance was produced.
The bypass is not always wrong. AI that removes the administrative, the repetitive, the merely logistical, and the work that consumes cognitive resources without developing anything, extends human capacity by redirecting it toward what actually develops it. A leader who spends less time formatting reports and more time thinking through the strategic implications of what those reports contain is being genuinely developed by the tool they are using. The person is being stretched in the direction that builds capability rather than rerouted around it.
The bypass becomes a problem when it operates on the cognitive activities that are themselves the development. When the argument is generated rather than constructed. When the options are produced rather than identified through the friction of genuine uncertainty. When the judgment call is informed by a synthesized recommendation rather than formed through the discomfort of genuine ambiguity. At that point the person is not using AI to do more. They are using AI to avoid the experience that would have made them more capable of doing it themselves.
Organizations that have not distinguished between these two modes of AI use are making a governance decision without knowing it. They are deciding, implicitly and at scale, whether AI is a development tool or a development substitute. The outputs in both cases look similar enough that the decision is not visible in any standard organizational measure. It becomes visible over time, in the capability profile of the organization’s people, in the quality of judgment when AI is not available or not appropriate, and in the resilience of the organization when the situation demands what the organization’s people can actually do rather than what their tools can produce on their behalf.
The organizations that will compound their capability through AI are the ones that use it to extend human reasoning, to push people further into the productive difficulty that develops them, and to reduce the noise around genuine developmental challenges while preserving those challenges. The organizations that will hollow out their capability are the ones that use AI to produce the outputs of development without the process. Both are happening now. Neither is visible in the productivity data.
The question is not whether AI is improving outputs. The question is whether it is improving people. Those are different questions. Most organizations are equipped to answer the first. Almost none are asking the second.
© 2026 Gianni Fracchia | Contact | Privacy Policy