Morale assessment
An anonymous survey, interviews and small-group conversations. Leadership gets a picture of morale and risks — at group level only.
Human component · led by a psychologist
AI rollouts rarely fail because of the technology. More often, they fail because of job security fears, overload and a lack of trust in leadership decisions. Alongside the technical implementation, we add support from a psychologist to protect your team’s well-being: we assess morale and workload, and prepare your communication and your managers.
Why
The licenses are bought, the pilot went well, and a quarter later only a handful of people use the automation. Usually there are four things behind it that never show up on the project plan: resistance to a new way of working, fear of losing one’s job, overload from change piled onto an already full calendar, and eroding trust in leadership.
This component doesn’t replace the implementation — it complements it. We design the technology as we always do, with a human in the loop, while in parallel a psychologist looks after employee well-being: making sure the team understands the purpose of the change, doesn’t carry it at the cost of overload, and can talk about concerns safely.
Scope
An anonymous survey, interviews and small-group conversations. Leadership gets a picture of morale and risks — at group level only.
Leadership messaging, a timeline aligned with the rollout and answers to the hard questions, including about jobs.
A workshop on how people react to change, and confidential consultations ahead of difficult conversations with the team.
When roles change
The decision belongs to leadership. How it’s carried out will determine what remains in the company: trust or fear. We don’t assess employees and we don’t take part in selecting who leaves.
Before
Conversation scenarios, a walkthrough of typical reactions and how to respond to strong emotions.
During
Supportive conversations and help coping with the initial shock.
After
Meetings and consultations that help rebuild a sense of security.
Confidentiality
FAQ
Yes, although we most often combine it with an implementation run by the studio — that way, communication and training move in step with the build and testing.
A psychologist who works with the studio, with experience working with adults, following a professional code of ethics and working under supervision. You’ll meet them before we start working together, and we agree on the rules for working with your team in writing.
It can improve it by taking routine work and overload off people’s plates, but it can also undermine it when the change is unclear, too fast or triggers fears about jobs. That’s why we assess morale and workload before and after the rollout, and make sure the team knows what’s changing in their work and who makes the decisions.
No. We don’t assess employees and we don’t take part in selecting who leaves. That role would undermine the trust that a psychologist’s work with a team depends on.
That’s exactly why we put the confidentiality rules in writing before we start and present them to the team. Without them, the assessment would show what people consider safe to say — not what they actually think.
Related
Services
An automation map: what to automate first, what to leave alone, and why.
Learn moreServices
n8n workflows and CRM, ERP and API integrations — no more retyping data by hand.
Learn moreServices
AI skills for teams and leadership — in response to Article 4 of the EU AI Act.
Learn moreHuman component
Let’s talk about what you’re implementing and who the change affects.