Who should video analytics be designed for?
For the people who can act on it every day: store managers, department heads and shift supervisors. Head office needs a unified view and audit teams need a compliance record, and both should get them. But lasting change only happens when the people on the ground use the output because it helps them, not because they are watched from outside.
Ask who the user of a video analytics project is and the answer is usually head office. Head office signed the order, wants one view of every site and reviews the dashboard. The audit or quality team usually comes next, using the same data to check compliance. Both are good reasons to buy. Neither, on its own, changes how a store runs.
Head office: a unified view
Central teams need to compare sites, spot patterns and decide where to spend. That is what video analytics does well: the same checks, measured the same way, across every location. It tells head office where the problems are. It cannot fix them.
Audit and QA: compliance across the organisation
Audit and quality teams use the output to check standards are met everywhere, every day, not just on the day of a visit. That is a real step up from sampling. But on its own it turns the system into an inspector, and people behave differently when they feel inspected: they fix what is being counted, for as long as it is being counted.
People on the ground: where change happens
The store manager, the kitchen lead, the department head and the shift supervisor are the only people who can change what happens at a site, hour by hour. If the output is designed for them, it becomes a tool they reach for. If it is designed about them, it becomes something to explain away.
- Give them their own view first: their site, their list, in plain language, on the phone they already use.
- Lead with what to fix today. Comparisons with other sites can come second.
- Let them mark an alert wrong and see it corrected. Trust grows when their feedback changes the system.
Make it worth their while
People use what helps them and what they are rewarded for. Tie the output to things they already care about: an easier audit, a better store score, a smoother shift, an incentive they recognise. When a store manager can show improvement using the same data head office sees, the system is working for them, not on them.
Pulled, not pushed
Change forced from outside lasts as long as the pressure does. Change the site owns keeps going. The test of a rollout is simple: after six months, do store managers open the output because they want to?
Where Tarsyer fits
Every site gets its own view: a daily score, a short list of things to fix and alerts on WhatsApp, with one tap to mark an alert wrong. Head office and audit teams see the same data across every site. At one fashion chain, more than a thousand store managers start each day this way.