The licences are bought, governance sits with your IT, and still hardly anyone uses Copilot. That is exactly where my part begins. I bring people in a regulated environment to Copilot, safely and productively. Practical, accompanied and measured against real everyday work.
A Copilot licence changes nobody's way of working. Once the technical prerequisites are in place, the value comes down to a single question. Do people really use Copilot, and do they even dare to in a regulated environment?
Cleaning up permissions, Purview, DLP, data residency, this technical preparation belongs in the hands of your IT and security teams and has to be in place before the rollout. I do not implement it. For a sense of what needs doing, there is my oversharing checklist on the blog.
Even a well prepared environment does not get used on its own. In banks there is caution on top of that. Anyone who fears mistakes will not try anything out. Adoption here does not happen by itself, it is hands-on work.
Every assigned but unused Copilot licence is paid for, and surveys often show only 20 to 30 per cent weekly usage. Why that happens is in the post on why Copilot licences go unused.
I bring people to Copilot, not with a one-off training but with a guided learning journey that works in the everyday routine of a bank.
Role-based and practical, from back office to executive board. No clicking through features, instead the concrete tasks that really come up day to day.
Building and supporting internal ambassadors who carry the knowledge into every team and bring their colleagues along, the most effective lever for lasting usage.
Which use cases create value, and what is better left out of the prompt? I show your people the safe and sensible way to work with Copilot, the behavioural counterpart to your IT's technical guardrails, not a replacement for them.
Make it verifiable who uses Copilot and how, then adjust where it counts. That way the investment becomes visible to the executive board and internal audit, not merely asserted.
I do not sell licences, I get value out of the ones you already pay for. No licence bias, no sales quota, only the question of whether people really use Copilot.
I have no stake in licence sales. My recommendation follows what really helps in everyday work, not what sells.
I guided M365 and Copilot adoption in a Swiss private bank with several thousand employees over four years. I know the regulated environment from practice, not from slides. You can read the anonymised case study.
Adoption and usage are backed with concrete numbers, so you can prove progress to your executive board and internal audit instead of claiming it.
You work with me throughout, not with rotating junior teams from a consulting machine. One contact person who keeps the context across the whole rollout, remote and on site. What that means for access and confidentiality is set out under security and trust.
The questions that always come up before a Copilot adoption in a bank, answered honestly.
No. The technical preparation and protection is the job of your IT and security teams, and it is the prerequisite. I know the topics, I make sure they are addressed before the rollout, and afterwards I take on the part that decides success: that people use Copilot safely and productively.
In principle yes. In Switzerland, cloud use is possible under the cloud guidelines of the Swiss Bankers Association if the data is adequately protected. Outside Switzerland the same question runs through your own supervisor and data protection regime, in the EU the GDPR. Whether and how it applies in your case is for your compliance and IT to clarify. Once that is settled, I make sure Copilot actually gets used.
I guided Microsoft 365 and Copilot adoption in a Swiss private bank with several thousand employees, continuously over four years, from the first Teams training to the Copilot learning path. I know the regulated environment and its caution from practice.
A mix of role-based training, e-learning, a champions community, use cases per department and continuous usage measurement, over weeks and months, not as a one-off appointment. We match the scope to your size and your level of maturity.
I teach your people how to work safely: which use cases are permitted and sensible, and what is better not typed in. That is the behavioural complement to your IT's technical guardrails, not a substitute for them.
No. I am an M365 and Copilot adoption consultant, not a legal or compliance adviser. The legal and regulatory assessment stays with your own specialist functions.
In a free intro call we look at your starting position, where Copilot stands today and how well people are keeping up, and we name the next steps. No sales pitch, no obligation.
Book a call now or fabrizio.marra@worksmart365.ch