Three months after launch the icon is still on the desktop and to-dos are empty. Leadership asks why nobody clicked after the spend. The empty dashed box is not a verdict. It only says the official path is still open. If WeChat approvals and paper still work, the back office stays an elective.
If nobody opens it, you can usually see why in three places
First, the entry. Real leave, expenses, and seals still live in WeCom, email, and hallway talk. The system opens only for inspections. What happens when every approval lives in WeChat: see What happens when every approval lives in WeChat. If groups and chats stay open, more training is a performance.
Second, speed. Twice the paper fields, three extra nodes versus a verbal yes, and a form that will not open on a phone—the floor votes with its feet. How to diagnose a slower system: see The system made work slower: how to diagnose it. Third, ownership. Nobody can sign “this ticket must enter the system.” Exceptions all go to the group; rules live only in the manual.
Worth it depends on whether you will change the work
If the company decides leave, expenses, and seals are official only in the system—and WeChat is only a notice—the back office is worth building, even if phase one is three–five flows. Logins rise after the path is mandatory. If you “launch and see if people like it,” you will likely return to the empty box. Filing cabinet after the fact versus work entry on the spot: see Filing cabinet vs. work entry: two ways to treat the system.
The “worth it” bar is specific: phase one covers only high-frequency approvals; each role can finish in ten minutes; name a system admin and exception owner; close formal group approvals within two weeks. Talk cost inside that scope; see What an OA / management system costs, and how long it takes. Shipping extra modules nobody walks is more wasteful than shipping one fewer module.
When the dual-run ends, only system tickets count
Week one after launch is the riskiest: some people start, some stay in the group, two progress tracks exist. Set a dual-run day count; after that, only system tickets count. Leaders look up tickets in to-dos and stop accepting “I have a WeChat screenshot.” If reviews still ask only “is it done?” and never “did it enter the system,” the floor will keep backfilling. One written rule—“no expense and no seal unless it is in the system”—beats three pep rallies.
DaXi writes which old path will close into acceptance. To close on your floor, go to the Management systems service page and describe how you approve today. The full path: see From brief to launch: how a management system is built. Why management has to leave hallway talk for a back office: see also Why companies need a management system.