The deadlock in enterprise AI implementation has never been about the tools.
Just yesterday, a CIO friend of a certain company in Lao Yang's group posted this passage: "Organizational efficiency improvement cannot be achieved simply by relying on tools. An efficient and agile organization can achieve high efficiency even via emails. For those who keep passing the buck and shirking responsibilities all day long, even if you give them the best software in the world for free, they still cannot make good use of it."
Coincidentally, some time ago, Lao Yang chatted with a CIO friend from a manufacturing group, who was just called out by the general manager that day: "We have already adopted AI and purchased collaboration software, why are we still arguing about cross-departmental account reconciliation in WeChat groups for three days?" He smiled bitterly and said: "The problem does not lie in the system, but in the fact that no one is responsible for the result of the account reconciliation in the first place."
This sentence pierces the illusion of digital transformation and AI implementation in too many enterprises. Lao Yang believes that the ceiling of organizational efficiency usually does not lie in tools, but in culture, consensus and collaboration mechanisms. At present, in some enterprises, technology (productivity) is advancing at a rapid pace, while the organization that carries it (production relations, collaboration mechanisms) remains stagnant. The investment and diligence in technology can only lead to unnecessary consumption in the same place.
Prioritize "People" Before "Tools" in Digital Transformation
Many top leaders of enterprises understand digital transformation as "deploying systems, purchasing SaaS, and installing models". However, the core characteristics of an efficient and agile organization are transparent information, decentralized decision-making, and clear responsibilities. With these three points, even the most primitive emails (asynchronous, traceable, group-sent for synchronization) can still achieve high efficiency, because everyone clearly knows "who to turn to, what to respond, and when to respond".
On the contrary, with fragmented internal information and ambiguous rights and responsibilities, the introduction of AI will only make wrong decisions faster, and make the reasons for buck-passing more "technical". Lao Yang once saw an enterprise that deployed an intelligent report system. When the data was wrong, everyone unanimously passed the buck to "the underlying calibers are not aligned", and no one took responsibility. You see, the tool did not improve efficiency, but instead provided a set of professional terms for buck-passing.
At this moment, a word came to Lao Yang's mind: Entropy! So how to judge whether the entropy of your organization is high? There is no need to do questionnaires, just look at one small thing: for a cross-departmental demand, from initiation to closed loop, how many groups do you need to create, how many hands does it need to go through, and who makes the final decision. The more steps you go through and the more chaotic the groups are, the higher the entropy. In organizations with high entropy, AI is not an antidote, but an amplifier. Therefore, enterprises need to sort out the information flow, rights and responsibilities first, before talking about tools.
AI Is a Lever, and the Fulcrum Is Trust and Contract
The essence of "passing the buck and shirking responsibilities" is the lack of trust foundation and result-oriented contractual spirit within the organization. AI and digital tools are, in the final analysis, levers:
In a healthy organization, the lever amplifies executive power, AI automatically generates reports, assists decision-making, and reduces repetitive work.
In an organization that is used to shirking responsibilities, the lever amplifies destructive power. AI's prediction reports become "evidence" for departments to attack each other, and automated processes become the perfect excuse to shirk responsibilities, with people saying "this is automatically judged by the system, it has nothing to do with me".
So it is not hard to see that the primary premise of AI implementation is to establish a "matter-oriented rather than person-oriented" data culture. If the team does not have the courage and consensus to "tell the truth with data", no matter how advanced the AI tool is, it can only be used to write weekly reports, or even be reduced to an excuse for buck-passing.
Lao Yang always believes that tools are neutral, and what the organization turns them into depends on the organization itself.
Tool Complexity Must Match Collaboration Maturity
The reason why some people regard email as an efficient enterprise tool is that it matches the collaboration maturity of that organization: simple, non-instant, logic-focused, and trace-focused, which is suitable for teams with high self-discipline and high consensus.
In contrast, many enterprises whose organizational capabilities are still stuck in the "agricultural era" insist on deploying "interstellar battleship" level collaboration software and AI middle platforms. As a result, employees create small WeChat groups to complain on the one hand, and fill in data that no one will read in the complex system on the other hand. The failure of AI implementation is often not caused by inaccurate algorithms, but by the fact that the organization's collaboration maturity cannot support the complexity of the tools. This is also what we often say: production relations cannot adapt to advanced productivity.
So it is not hard to see: AI implementation should "advance in small steps and reject the Great Leap Forward". Instead of deploying a full-process automated large AI platform, it is better to first find a small scenario with extremely clear pain points and extremely clear responsibility boundaries (such as financial invoice recognition, automatic classification of customer service work orders), use AI to solve one specific point, so that the team can truly feel that "the tool is helping me, not managing me". If the maturity is not enough, use light tools first, do not deploy a heavy middle platform as soon as you start, that thing is useless except for showing off.
Do Not Use AI to Patch Holes in Processes
Employees pass the buck and shirk responsibilities mostly because there are ambiguous areas in the process itself. If the process is fragmented, the intervention of AI will only solidify these holes with code, making them deeper and harder to find. But many enterprise managers are still using diligence in AI technology to replace laziness in management.
For example, an approval process that originally involved buck-passing due to unclear rights and responsibilities. After the deployment of AI intelligent approval, people no longer argue about "who should approve", but start to argue about "why did AI judge this way? Who set the rules?". The buck-passing shifts from people to algorithms, and finally the algorithm takes the blame, but the essence of management has not changed.
From the above, it is not hard to see that AI is the accelerator of processes, not the repairman of processes. Before handing over the process to AI, business process reengineering (BPR) must be carried out first, cut off the points that cause artificial buck-passing, clarify the responsibility boundaries with systems and SOPs, and then let AI enter. Otherwise, AI will only become a new battlefield for buck-passing. The first step of process reengineering is often not to draw diagrams, but to write "who on earth is responsible for the result of this matter" into the system, and execution is the key.
The Most Advanced Digital Transformation Is to Make "Consensus" the Default System Rule
The reason why efficient organizations are efficient when using emails is that every sentence in the email corresponds to clear action items and responsible persons. This is a kind of mental digitalization, where everyone has a common logic in mind.
The ultimate goal of enterprises implementing AI is not to let employees learn to operate a certain AI software, but to train the organization's best practices and consensus into the default workflow of AI. If there is no consensus on "what a good solution is", no matter how perfect the AI-generated solution is, it will be picked on and rejected by various departments based on their own interests.
Lao Yang believes that the highest state of digital transformation and AI is "system as code, consensus as algorithm". Enterprises should spend 80% of their efforts to unify business logic, precipitate knowledge assets, and clarify evaluation criteria, and the remaining 20% is for purchasing computing power and training models. How to precipitate consensus? It is not to hold meetings and shout slogans, but to solidify the review standards and adopted solutions into a reusable knowledge base and review checklist.
Final Summary
Lao Yang would like to remind here: Do not let the IT department take the blame for poor organizational efficiency!
If your team culture is fragmented, digital tools will only turn you into a fragmented group armed with data.
Lao Yang suggests here: Before an enterprise launches any major AI or digital project, hold a meeting to ask the team: if there is no internet and no software, and we can only use emails and Excel, can we still push this matter forward? If not, there must be problems with the consensus of people and the rights and responsibilities of the process. Solve the people's problems first, and then let AI amplify people's efficiency.
This article is from the WeChat Official Account "Xiangjiang Digital Review" (ID: benpaoshuzi), written by Lao Yang, and published with authorization from 36Kr.