Collaboration used to be “can you ask if they replied.” With trackable nodes it becomes three things: I know who is blocking; the system chases at the clock; if someone is out, the ticket can be reassigned. Favors still exist. They are no longer the only engine.
First change: status moves from asking around to self-serve
Staff open to-dos and see “finance received, invoice missing.” Managers sort the list by overdue instead of answering from memory. Two kinds of noise drop: repeat chasing, and “I thought you approved.” Why chat approvals split at scale: What happens when every approval lives in WeChat. If the system is more winding than chat, cycle time gets worse. Cut fields and nodes to the main path—see The system made work slower: how to diagnose it.
Second change: exceptions have an exit, instead of all landing on the owner
Trackable is not “send every ticket to the GM.” After amount and department splits, the owner sees exceptions and overdue escalations. When people change jobs, to-dos can be reassigned, so exit does not break the chain—see How to-dos and permissions survive when a manager leaves. Packaged OA with too many nodes that fight your habit is almost as bad as none—see A packaged OA nobody uses is almost as bad as having none.
Feishu, DingTalk and WeCom can carry reminders. What actually changes collaboration is the state machine in the back office: who is current, what happens when overdue, which attachment version. How platforms and custom split: Feishu, DingTalk, and a custom back office: what actually differs. DaXi writes chase rules into phase one, instead of “optimizing UX” after launch. To build routing to your cycle-time target, tell us how many times a ticket is chased today on the Management systems service page.
Chasing is not @ again. Reassignment is not lending an account
The time bar has to answer three numbers: hours from submit to close, dwell at each node, and who received the overdue escalation. Without those three, chasing is still a favor. Proxy and reassignment must leave a trail, or a traveling manager hands the password to an assistant and the permission matrix tears on the spot—see How clear permissions cut disputes and leaks. The more nodes you add, the longer the bar, the faster people return to WeChat. Cut conditions, do not retrain. Visible efficiency starts with one fewer “did they approve?”—see Visible efficiency a management system can deliver. Put the three numbers in the weekly meeting, and collaboration moves from “ask for me” to reading the bar. The owner chases from the overdue list, not by naming names in the group, or the bar will not be taken seriously.
Chase channels can land in Feishu or WeCom. “Current owner” can have only one system of record. Two to-do lists ringing at once, and people mute the louder one. Write time limits and escalation into routing in phase one. That is closer to better collaboration than a wall-screen homepage.