Meet Tsuno at Sirha Lyon 2027 · Stand S.57Learn more
EN FR
Try the demo
Menu

Team and management

Why teams reject new tools

Teams reject a tool that adds unpaid work, feels like surveillance, gets in the way at the station or arrives without them. Nine causes, and what defuses each.

Published on

In the break room, two employees eye a tablet lying on the table with suspicion, arms folded.

Teams reject new tools for specific reasons, rarely on principle. On the staff side: extra work that isn't paid, fear of being watched, a tool designed for the office, a patronizing tone, a breakdown at the worst moment, yet another login, and nobody asking for their opinion. On the management side: no time to train and no go-to person. Each cause has a fix, as long as you name it before you try to convince anyone.

Tuesday, 3:10 p.m., in the break room

The tablet arrived that morning. It sits on the break room table with a note from Cyril, the head chef: "From Monday, checklists are done on this. Set up your account over the weekend."

Naïma, a commis who has been there three years, looks at it without touching it. Marius, on the dish station, folds his arms: "This weekend I'm at home. And what's it for, knowing what time I did the walk-in?" Naïma adds: "We had the last app for two months. It crashed on Saturday nights."

Nobody said no. On Monday, the paper checklist will be filled in as usual.

(Fictional scene and characters.)

A refusal is information, not a tantrum

"They don't like change": the explanation is comfortable, and almost always wrong. A kitchen team changes menus, suppliers and rotas all the time. What it rejects is a tool that costs it something and gives nothing back.

How to roll out a tool is covered in the tool, but how? Adopting AI without losing the craft. This piece is the diagnosis: nine causes, and what defuses each one.

The seven reasons on the staff side

Extra work, and unpaid

"Set up your account over the weekend." "Watch the tutorial at home." It sounds harmless. For Marius, it means half an hour of his Sunday for a tool he never asked for. In France, the time during which an employee is at the employer's disposal and follows its instructions is actual working time (Labour Code, Article L3121-1). Elsewhere, check the local rules on working time.

The fix: everything happens on paid time. Creating the account, the first walkthrough and the first questions all take place on site, at the start of a shift, with someone alongside.

Fear of being watched

A tool that knows who did what and when is unsettling, and that is normal. Marius isn't asking what the tablet is for: he is asking what it will reveal about him. As long as nobody answers in writing, the team assumes the worst.

To defuse it, pin up one plain sheet in the locker room: what is recorded, who sees it, what it is for and what will never be done with it. In France, this prior notice is a legal requirement anyway (Article L1222-4). The signs that tip a support tool into surveillance are set out in why management software can quickly feel like surveillance.

A tool designed for the office

Tiny buttons, nested menus, a screen that locks after thirty seconds. With gloves on, wet hands or a tray in your arms, it is a chore. Naïma isn't refusing the tool: she is refusing to dry her hands four times to tick off a checklist.

Before choosing, test the tool at the station, in real conditions, and count the steps.

A patronizing tone

Confetti for every task ticked, "Well done, superstar!" messages, badges to collect. Cooks with twenty years in the trade feel treated like children, and beginners aren't fooled either.

The answer is a tool that talks to people like professionals, and recognition that comes from a person, backed by facts. That is the subject of recognition at work: use facts, not childish badges.

A breakdown at the worst moment

Saturday, 8:30 p.m. The tablet freezes, there is no signal at the back of the storeroom, the temperature check doesn't save. Once is enough. By Monday, the whole team knows "the app doesn't work", even if it worked fine for the previous twenty days.

You need a fallback everyone knows about (the paper checklist in the binder, at least for the first month), and a tool that keeps entries when the network drops. What a field tool must keep doing without a connection is covered in no network: what a field tool must keep doing.

Yet another password

The rota in one app, messages in another, checks in a third, each with its own login. Every new tool adds a forgotten password, a reset email, a colleague logging in on someone else's account to save time.

Better: short, personal access that works on a shared device, and a tool that replaces another one instead of piling on top.

Nobody asked for their opinion

This is often the real reason, hiding behind the others. The tool was chosen at head office or by the manager, announced by message, imposed with a date.

The fix is simple: ask before you choose. Which task wastes your time? People who were consulted defend the tool; people presented with a done deal wait for it to fail. The same logic applies to voice, with its own stakes, in impose or offer voice to your team?.

The two reasons on the management side

No time to train

Cyril is juggling service, orders and two absences: training on a tool comes last. Everyone learns alone, badly, and the tool is judged on those failed attempts. Yet in France the employer must ensure employees are adapted to their job, including as technology changes (Labour Code, Article L6321-1).

A short walkthrough is often enough: fifteen minutes at the start of a shift, on a single routine, in pairs.

No go-to person

If, when something gets stuck, people call the manager, every snag lands on the busiest person in the building. By the third unanswered bug, the team gives up.

Name one go-to person per team, a volunteer, with a little time set aside in their rota to help and report what isn't working. Not necessarily the youngest. An experienced hand who believes in the tool is worth more than a newcomer who is comfortable with screens.

The diagnostic grid

CauseWhat you hearWhat defuses itWho acts
Unpaid extra work"I'm not doing this at home"Everything on paid time, on siteManager
Fear of being watched"Is it to know what time I did what?"A written sheet: what is recorded, who sees it, what is ruled outLeadership
Designed for the office"It's impossible with gloves on"A test at the station, wet hands, steps countedManager and team
Patronizing tone"We're not in school"A professional tone, recognition from a personLeadership
Breakdown at the worst moment"It crashes on Saturdays"Known paper fallback, entries kept offlineGo-to person
Yet another login"I forgot my code"Short personal access, one tool fewer elsewhereLeadership
Nobody asked"We found out by text"Consult before choosingManager
No time to train"We'll see after the season"Fifteen minutes, one routine, in pairsManager
No go-to person"I don't know who to call"A volunteer, with time set asideManager

Common mistakes

  • Taking silence for agreement. A team that says nothing and keeps filling in paper has already given its answer.
  • Answering rejection with more training. If the tool is awkward at the station, an hour of training won't make it any handier.
  • Making the tool mandatory to get it over with. Forced use hides the problem without solving it, and the team uses it just enough to avoid being told off.
  • Forgetting employee representatives. In France, in companies with at least 50 employees, the works council (CSE) must be consulted on the introduction of new technologies (Article L2312-8). Check the equivalent rules where you operate.

What to measure

  • Objections named and dealt with. Write down each reason you hear and what was done about it. An unanswered objection comes back stronger.
  • Use without reminders. How many routines are done on the tool without anyone having to ask? That is the only use that tells you anything.
  • Workarounds. A parallel notebook, a paper checklist filled in "just in case", a group chat for what the tool was supposed to do: each workaround points to a specific cause.

Track these three by team, never to judge an individual.

Where Tsuno fits in

Tsuno was born at Kajirō Sushi, its founder's restaurant group. On the site tablet, everyone works with their own code, and signing in needs no password, just a six-digit code or a link sent by email. Entries made offline are sent when the network comes back. The interface is available in French and English. Details are on the Features page.

On monitoring, we say things as they are. The app has a monthly leaderboard, made of points earned in training, for punctuality and for tasks completed, to keep teams engaged: present it for what it is. It is never passed to the assistant, the AI rates nobody, and nothing runs without confirmation. All of this is written on the Trust page.

Tsuno San, the intelligent voice assistant for frontline teams, follows the same rules: it only sees and does what the person can already see and do. San Voice is available as a demo, and voice remains an option, never an obligation. Try it on your own routines from the Tsuno San page.

If your team has already rejected two tools, don't add a third before you understand why.

Further reading

How to roll out a tool is in the tool, but how? Adopting AI without losing the craft. On the role of experienced staff, read old hands, first allies of a knowledge-sharing tool. For voice specifically, see impose or offer voice to your team?. And on usability at the station, technology should adapt to people who work, not the other way round. The wider context is in the future of work in hands-on jobs. To make adoption work, weigh up honestly 5 reasons to adopt a voice assistant, and 5 reasons not to.

Key takeaways

A team doesn't reject a tool on principle: it rejects what the tool costs it or what it makes it fear. Name the cause together and deal with it before trying to convince: the tool can then be judged on what it does.

Frequently asked questions

Why won't my staff use the new software?

Usually for specific reasons: the tool adds work with no time set aside for it, it raises fears of being monitored, it is awkward to use at the station, it breaks down at the worst moment, or nobody asked their opinion. Ask them which one it is. It can almost always be fixed.

Is rejecting a tool just resistance to change?

Rarely in the sense people mean. A team that rejects a tool is usually pointing at a real flaw: extra work, a worry, a nuisance on the job. Treating the refusal as bad attitude stops you from fixing that flaw.

Should time spent learning a new tool be paid?

In France, any time during which an employee is at the employer's disposal and follows its instructions counts as actual working time (Labour Code, Article L3121-1). Elsewhere, check local rules. Asking people to set up an account or watch a tutorial at home, off the clock, is a classic cause of rejection.

How do you reassure a team that is afraid of being monitored by a tool?

By writing down what the tool records, who sees it and what it is for, before it goes live. In France, no personal information about an employee may be collected by a system they have not been told about beforehand (Article L1222-4).

Do you need a go-to person to launch a tool in a restaurant?

Yes. Without someone on site who knows the tool, has time set aside to help and reports problems back, every snag ends up with the manager, who has no time. The go-to person is often a volunteer from the team, not necessarily the youngest.