10 · Usage & ongoing use · Whether anyone finishes the menu
A menu existing does not mean anyone works that document
Product operations watches whether anyone finishes a function. Not renewal. Not who coupons go to. Menu length is not a score.
In use: Receiving, closing variance — documents finish every day. Keep the entry stable. Do not move it on a whim.
Nobody taps: Wave picking live two weeks, zero. First check whether they cannot use it, or the floor does not work that way at all.
Misuse: Someone uses remarks instead of a state. Hand the repeating sentences in remarks to product, and see whether the rule is missing.
Product operations owns whether a function enters daily work
The product owner decides what the next version fixes. Product operations supplies use facts at function grain: which menu is used every day, which has never finished a single document from day one, where people always type in remarks. The mark of the role is not treating “do a training” as the answer to every zero-use. Zero use may be a deep entry, privilege never opened, or a floor process that never had this step. He gathers evidence first, then recommends. Recommendations go to product. He does not tell development to change the menu himself. Whether a whole main path has fallen back to WeChat, and which one thing to chase before renewal, sits with customer success. Coupon lists sit with user operations.
Metrics must match the data architect’s definition. A completed receiving document means status received, not a page that was opened. Opened pages counted as use hide that nobody submitted.
Zero times on the wave menu
The distribution centre went live with wave picking. Two weeks, not one completed wave document. Product operations walked a pick and found pickers still picking by store. The supervisor was not going to change, because the dock does not support consolidation. The function was a wish someone added after presales. Product operations handed the observation to the product owner: disable the entry so a new hire does not tap in and make a half document; whether to rebuild waits until the floor actually changes the job. After the entry was disabled, what he verified was completed-document counts, not whether the customer was satisfied. Pick errors did not rise, which meant this menu had only been interference. For entries still in use, do not change the position for two versions in a row. Move the position and completed volume drops, then it is misread as a business decline.
How function facts enter the next plan
Product operations splits recommendations into fold, keep, and rebuild. Each class carries completed-document counts, sample document numbers, and a verification date. Mix the three and product will treat them as the easiest keep. Clicks, impressions, and whether a whole path fell back to WeChat do not go on this fact table. Whether a path returned to WeChat is chased by customer success. This role only answers whether anyone finished one document on this menu. On misuse, first count how many documents used remarks as a state. A small count may be one person’s habit. A large count means the rule is missing an exit. Sample document numbers go to the product owner. Adding a state or folding the entry is product’s decision. Operations changing the menu itself will cause the next version to add the entry back. A recommendation with no verification date is the same as not handling it.
At the next-version planning meeting, product operations brings only one function-fact table. Each row is menu name, two-week completed-document count, recommendation type, verification date. If a zero-count menu is recommended to fold, write the substitute action: pickers keep picking by store, the entry is hidden from new hires. Write only “improve the experience” and implementation will be chased on the floor, and the entry will be put back temporarily. A menu whose completes rose and whose errors also rose is marked on another row: the entry let in people who should not work this document. That row goes to the product owner. It is not packaged as activity. Whether a whole main path fell back to WeChat does not appear on this table. That is a number customer success chases by week. This role’s score is: a folded entry is still folded on the verification date, and a kept entry’s completed-document count did not drop to zero because the position moved.