Systems are live, but middle managers still solve problems in group chats: special approvals, rush orders, bypassing nodes. Teams learn the same habits and processes hollow out. The new skill is not making better slides—it is reading metrics (what definition does this red light use?), asking questions (real shortage or sloppy commitments?), and pulling exceptions back into process (this special approval becomes a rule or a refusal next time). Gut feel still matters, but metrics should calibrate it.
Without these three skills, middle managers become the system's biggest leak: every hard problem lands in their WeChat.
Read, Question, Pull Back
Read metrics: know the definition before the ranking. Question: drill to documents on anomalies, not attitudes. Pull back: exceptions must leave a ticket; weekly review what becomes a rule and what must stop. Special approval count is a middle-manager KPI—not proof of capability.
- Watch only two or three numbers daily, tied to your department's duties.
- Ask data owners about unfamiliar definitions—no private alternate calculations.
- Exceptions above threshold auto-escalate so managers are not permanent bypasses.
Make Special Approvals Expensive
Cheap special approvals mean nobody follows process. The XYN digital intelligence system logs exceptions as countable bypasses so managers see how many holes they opened. Training should practice these three moves—not another culture deck. When middle managers can do them, digitalization becomes a management habit, not an IT project.
Count special approvals this week. If there are many, practice pulling back before reading more reports.
