When a new tool changes how work gets done, employees need more than an announcement about efficiency. They need to understand the purpose, what will change, who remains responsible and where to raise concerns. Human-centred leadership means making those questions part of the decision—not treating people as an implementation detail.
This is a leadership discussion guide, not an AI deployment checklist or a promise that automation will improve performance. Technical, privacy, security, employment and accessibility questions need the appropriate expertise.
Start with the work and the people affected
Describe the problem before choosing a product. Is information hard to find? Are requests passed between teams without an owner? Are staff repeating a task that could first be simplified? A clearer process may be enough; a new tool is not automatically the answer.
Speak with the people doing the work and those receiving it. Ask what must be preserved, where errors would matter and what support would make a change workable. Include different shifts, responsibilities and access needs rather than relying only on the most enthusiastic users.
Keep responsibility visible
An automated output still needs an appropriate decision process around it. Identify the person accountable for the use case, the checks required before an output is used, and a route for correcting mistakes. Give reviewers enough time, information and authority to challenge an output rather than simply approve it.
The NIST AI Risk Management Framework provides voluntary guidance for managing AI risks. Its generative-AI profile includes risks such as confidently presented false information. A polite or convincing response is not evidence that its content is correct.
- Specify the task the tool may support and uses that are out of scope.
- Agree which information may be entered; do not put personal or confidential material into an unapproved service.
- Decide what must be checked against an authoritative source or by a qualified person.
- Provide a practical way to report errors, pause use and continue the work safely.
Listen without pretending to read minds
Concern about technology may reflect workload, job uncertainty, an inaccessible interface or a genuine flaw in the proposed process. Do not label every objection resistance to change. Ask what the person has observed, check your understanding and explain what you can and cannot resolve.
Useful questions include: “Which part of this change creates extra work?” and “What would need to be true for you to use this confidently?” Follow up with a decision or an explanation, including when a suggestion cannot be adopted. Do not promise confidentiality that the reporting arrangements cannot provide.
Keep discussions about work conditions separate from assumptions about someone’s mental health. Managers and business coaches should not diagnose employees. Where specialist support is needed, use the appropriate qualified service and established workplace processes.
Budget for learning and the transition
A subscription price is not the whole cost of a change. Consider preparation, training, review, correction, support and any period of running two processes. There is no universal spending ratio between technology and employee development.
Give people realistic practice tasks and time to learn. Explain limitations as well as features. Check whether the training is usable for the people involved, and whether responsibilities or workloads need adjustment. Do not assume that time saved on one task becomes spare capacity elsewhere.
A hypothetical customer-service trial
Imagine a small service business testing a tool that drafts answers from approved public information. Staff review each draft before sending it. Complaints, sensitive details and requests outside the approved scope go through the existing human process.
The team compares total handling time—including review and corrections—with the previous approach. It also records inaccurate answers, unresolved requests and staff feedback. If checking takes longer or important errors persist, the team can change or stop the trial. This is an illustration, not a client result or a recommendation to deploy a particular system.
Make connection part of the review
Choose a review point suited to the risk and pace of the work. Ask whether the original problem improved, what new burdens appeared and who may have been overlooked. Keep a human contact route where people need clarification or wish to challenge a decision.
Human-centred leadership is not opposition to technology. It is a commitment to examine its effects, make responsibility clear and respond honestly when the evidence does not support the hoped-for benefit.
Discuss a leadership challenge
Coaching can help you examine priorities, communication and your own leadership decisions. It does not replace technical implementation, legal advice or clinical care. Book a free 15-minute fit call to discuss whether coaching is appropriate.
You can also apply for two weeks of free coaching. Joel personally reviews applications; acceptance is not guaranteed.
