Source: https://wiity.ai/resources/why-automation-should-scare-your-spreadsheets-not-your-staff
Reading version: https://wiity.ai/resources/why-automation-should-scare-your-spreadsheets-not-your-staff.md

[← All resources](https://wiity.ai/resources)

People & adoption / PRACTICAL GUIDE

# How to introduce automation without losing your team’s trust

A recruiter spends Friday afternoon copying interview notes into three places. You offer to automate it. Their first question is not about the software. It is what the change means for their job. That is a reasonable question, and it deserves a straight answer.

[Jordan Betteridge](https://wiity.ai/about#jordan-betteridge) AI Experience & Change · 15 years in recruitment technology Updated 20 October 2026 · 3 min read

![PEOPLE → CONFIDENCE → MORE HUMAN TIME](https://wiity.ai/assets/resources/why-automation-should-scare-your-spreadsheets-not-your-staff.svg)

IN THIS GUIDE

[Start with the work people want help with](https://wiity.ai/resources/why-automation-should-scare-your-spreadsheets-not-your-staff#part-1) [Give the task a clear brief](https://wiity.ai/resources/why-automation-should-scare-your-spreadsheets-not-your-staff#part-2) [Walk through one task before asking people to trust a platform](https://wiity.ai/resources/why-automation-should-scare-your-spreadsheets-not-your-staff#worked-example) [Make practice part of delivery](https://wiity.ai/resources/why-automation-should-scare-your-spreadsheets-not-your-staff#part-3) [Decide what the time is for](https://wiity.ai/resources/why-automation-should-scare-your-spreadsheets-not-your-staff#part-4) [Measure confidence as well as activity](https://wiity.ai/resources/why-automation-should-scare-your-spreadsheets-not-your-staff#part-5) [Take this into your next team conversation](https://wiity.ai/resources/why-automation-should-scare-your-spreadsheets-not-your-staff#put-it-to-work) [Questions worth asking](https://wiity.ai/resources/why-automation-should-scare-your-spreadsheets-not-your-staff#reader-questions)

THE PRACTICAL VIEW

The adoption conversation needs to happen before the tool arrives. People should understand what is changing, what stays with them and how they can influence the design.

## Start with the work people want help with

Ask recruiters where their day disappears: chasing documents, copying notes between systems, preparing updates or finding the latest version of a record. Observe the work before deciding what to automate. The person doing it will often know the exceptions that a process diagram misses.

## Give the task a clear brief

Explain the purpose, approved inputs, expected output and limits. An agent drafting a candidate update needs accurate context and communication rules. It also needs to know when to stop. Clear instructions help, but they cannot remove every model error or compensate for missing information.

WORKED EXAMPLE · ILLUSTRATIVE

## Walk through one task before asking people to trust a platform

Consider interview notes. The recruiter records the conversation in an approved tool. AI prepares a structured draft. The recruiter checks the facts and removes anything inappropriate. Only then does the approved summary enter the candidate record. The useful change is specific: less formatting and copying. The recruiter still owns the account of the conversation.

### Where it can go wrong

If checking the draft takes longer than writing the note, do not tell the team they are resisting change. Find out whether the template is wrong, the recording is poor or the tool is inventing details. Adoption is useful feedback about the design.

## Make practice part of delivery

Use familiar scenarios and anonymised examples. Let people compare the original task with the proposed workflow, question the output and rehearse a handover. Give managers enough understanding to support the change. A poor result should prompt investigation into the tool, data, instructions and workflow, rather than blame.

## Decide what the time is for

Freed capacity can support client conversations, candidate care, business development or learning. Agree that purpose with the team. Do not promise a fixed number of hours saved before measuring the workflow, including the time spent reviewing and correcting outputs.

## Measure confidence as well as activity

Track adoption, exceptions, rework and time spent on the task. Ask whether the new approach helps people do their job. Wiity on Assignment brings discovery, delivery, training and coaching together so the change can become part of everyday work.

PUT IT TO WORK

## Take this into your next team conversation

Tick off the points you have covered. This is a working checklist, not a compliance score. Selections reset when you leave the page.

Practical review checklist

Ask the team which task they would most like help with.

Write down what the person will still own.

Practise a normal case and an exception together.

Agree how released time will support clients, candidates or learning.

0 of 4 points covered

Reset checklist

## Questions worth asking

How do we measure whether people are adopting the workflow?

Look beyond logins. Check how often the intended task is completed, how much correction is needed and whether people choose to return to the old process. Ask what made the latest attempt easy or difficult.

Should we promise that automation will never change a role?

Only make commitments the business can keep. Explain the intended change honestly, involve people in the decisions and give them a route to discuss concerns. A reassurance that later proves false will undermine trust.

Continue with [Recruitment AI Roadmap: A Practical Planning Guide](https://wiity.ai/resources/ai-led-tech-roadmap-for-recruiters) .

**About this guide**

This guide builds on Jordan’s Hyper Automate resource library, updated for Wiity. Worked examples illustrate the approach; they are not customer case studies.

![Jordan Betteridge](https://wiity.ai/assets/team/jordan-betteridge.webp)

YOUR AUTHOR

## Jordan Betteridge

**AI Experience & Change**

15 years of recruitment technology experience.

Jordan leads Wiity’s brand, experience and hands-on solution design. He shapes how people discover, experience and use what we build, from websites to bespoke applications. He brings recruitment technology experience to making complex ideas clear and creating practical tools that fit the way people work.

KEEP EXPLORING

## More useful next steps.

[How to build a recruitment AI roadmap without collecting disconnected tools ↗](https://wiity.ai/resources/ai-led-tech-roadmap-for-recruiters) [How to prepare your team’s devices for AI without buying hardware you do not need ↗](https://wiity.ai/resources/is-your-recruitment-teams-hardware-ready-for-ai)

FROM IDEAS TO EVERYDAY WORK

## Make the next step work for your people.

Explore a focused AI project, a transformation roadmap or connected recruitment data with Ella.

[Let’s talk about your business ↗](https://wiity.ai/contact)
