How should you choose KPIs for a video analytics project?
Treat them as a flexible set of rules, not a fixed framework. Start with the few checks that matter most now, review them on a schedule, retire the ones that are under control, add new ones as conditions change, and let each site run the checks that fit its own problems.
At the start of a project, someone writes a list: queue length, staff at the counter, PPE, whatever mattered that quarter. The checks get built, the dashboards get built around them, and then the list is left alone. Two years later the business has a new format, a new season and a new problem, and the cameras are still measuring the old one.
1. Start with what hurts now
Pick the three or four checks tied to the problem the business is feeling this quarter: long queues in the festive season, hygiene complaints, a rise in stock loss. Not every check you might one day want. A short list gets acted on; a long one gets a dashboard.
2. Review the list on a schedule
Put a date in the calendar, monthly or quarterly. For each check, ask three questions. Is this still a problem? Is anyone acting on the alerts? Has it been fixed? A check nobody acts on is noise, and noise teaches people to ignore the checks that matter.
3. Retire checks that have done their job
When a problem has been under control for a while, stop alerting on it. Keep a light weekly count so you notice if it comes back, and spend the attention on the next problem instead.
4. Let each site run its own mix
Every location has its own set of things to improve. A mall store’s problem is the Saturday queue. A high-street store’s is an unstaffed counter at quiet hours. A store in a new format needs to see how customers move through it. Forcing every site onto the same list means most sites measure something they don’t need and miss what they do.
5. Write them as rules, not a framework
A rule is small and specific. For example: at this store, tell the shift manager when more than five people have waited at billing for over three minutes, between 5 and 9 pm. Rules can be added, tuned for one site, paused for a season and switched off, without re-planning the project. A framework is decided once and then defended forever.
What a year can look like
- Festive season: billing queues and counter staffing, at the mall stores only.
- After a store refit: how customers move through the new layout, at the refitted stores.
- Stock loss rises in one region: after-hours checks at those stores; queue alerts paused there.
- Queues under control: alerts retired, replaced by a weekly count.
Where Tarsyer fits
Every Tarsyer check runs on the same device, so adding, changing or retiring one is a configuration change, not a new project. Each site, and each camera, can run a different mix, and the list can change as quickly as the business does.