.png)
aka How Founders Introduce Automation Without Causing a Mutiny
Picture it. You’ve seen what’s possible - invoices that chase themselves, orders that flow from e-shop to warehouse without a human ferrying them across, a Monday report that quietly builds itself on Sunday night. So you call a meeting. You say the word “efficiency” with real feeling.
And your team reacts like a cat being shown its new bathtub.
They’re not anti-technology. These are people with robot vacuums - they love automation when it’s theirs. They’re nervous because for you, automation is leverage. For them, it feels like an audition. You own the upside; they’re worried they are the downside.
Five moves fix most of it.
1. Say the quiet part out loud
The question in every head is “Is this how I get replaced?” - and nobody will ask it in the meeting. Answer it before they can: “We’re automating the invoice-chasing, not the invoice-chasers.” Spell out what the software takes (the copy-paste, the re-typing, the chasing) and what stays gloriously human (the judgement, the clients, the final say - nothing important leaves the building without a person’s sign-off). Skip this step and people will write their own answer. It’s never the nice one.
2. Let the team pick the first victim
One question: “Which task would you pay actual money to never do again?” Whatever wins - the report formatting, the numbers re-typed into a fourth system, the documents printed purely so they can be scanned again - automate that first. It won’t look impressive in a board deck. It doesn’t need to. When automation kills a chore everyone hates, it does its own internal marketing. Nobody holds a candlelight vigil for manual data entry.
3. Start insultingly small
Microscopic. Subatomic, ideally. Fine: one process. Not fourteen tools and a Digital Transformation with its own steering committee. One small automation that works this month converts more skeptics than a grand vision arriving “in Q3.” (Which Q3? The vision never says.)
4. Deputize your skeptic
Every company has one person who can find the flaw in anything within four seconds. Let’s call her Doris. Do not route around Doris - hand her a badge and make her the official tester. On the one hand, her objections are free quality control. On the other hand, an automation that survives Doris will survive anything, and her grudging nod converts the rest of the office faster than any launch email ever could.
5. Don’t confiscate the time you save
If every freed-up hour gets instantly refilled with new tasks, your team learns that efficiency is a punishment - the reward for digging faster is a bigger shovel. Let some of the reclaimed time visibly turn into things they actually want: deeper work, that workshop or conference they’ve been wanting to attend for three years running, or simply going home on time. People protect what helps them. What doesn’t help them tends to develop mysterious syncing issues.
Skimmed straight to the bottom? Bold. Respect.
The short version: answer the scary question first, let the team choose the target, start absurdly small, give your toughest critic the tester badge, and let people keep a slice of the time you save. Do automation with them, not to them - and the same people who greeted the word “efficiency” with folded arms will soon be queueing at your door with ideas for what to automate next.
And the building part - the actual software, wired into your systems, sturdy enough to survive Doris - that’s the part we do all day, happily.
Book a call. You bring your most hated process (and Doris). We’ll bring the plan for its dignified retirement.