A whole team up to level,
working the same way
Team training is not only about what people learn, but about what they agree on afterwards. This page lists the training that moves a department forward in one go, and how to set such a day up.
What plays out in a team
Four situations a department recognises, and the topic that does something about each.
Not just learning the buttons, but agreeing together how you will do it from now on. Ways of working
One shared starting point and clear ground rules, so the gap does not widen. Copilot & prompt engineering
One agreed structure in Teams and SharePoint that the team maintains itself afterwards. Teams & SharePoint
Concrete commitments at the end of the day and a follow-up session to check them. Making it stick
Training for a whole team
Every training below is in-company and made to measure. For team training we look not only at content, but also at group composition, differences in level and what happens after the day.
AI in the daily workflow
Everyone at the same starting point, under the same ground rulesMicrosoft 365 Copilot
The broad foundation for a whole team: Copilot in Word, Excel, PowerPoint, Outlook and Teams. Everyone at the same starting point, with agreements on what you do and do not use it for.
Copilot Chat
The version without a paid licence. Ideal for introducing a whole department to AI before you decide who gets a full Copilot licence.
Prompt engineering
The difference between a nice answer and a usable one. Writing effective prompts for Copilot, ChatGPT and Claude, and judging what comes back.
Framework adoption (AI adoption)
For when a single training is not enough to make a department genuinely switch. Assessment, ground rules and change management following proven methodologies.
Collaborating & organising
One way of working instead of ten habitsMicrosoft Teams
Setting up channels, meetings and files so the team keeps to the same agreements. The difference between using Teams and making Teams work.
SharePoint
One agreed place for the department’s documents. Structure, metadata and permissions you set together and the team maintains itself afterwards.
Planner Premium
Making tasks and workload visible inside Teams. Who does what, when it is due and where it stalls, without a separate project tool.
Ways of working & security
How you work together and what to watch forAgile Scrum
A way of working a team carries itself: short cycles, clear roles and meetings that lead somewhere. Useful well beyond software development.
Effective communication
How do you address each other when something is off? A shared way of giving and receiving feedback, practised with situations from your own team.
Cybersecurity Awareness
One careless click hits the whole department. Recognising phishing, sharing safely and knowing what to report, practised with examples from your own sector.
Copilot aimed at one department
When a department works with its own documents, its own questions and its own yearly rhythm, we would rather practise on that work than on general examples.
Also requested regularly
Less common, but certainly possible as part of your programme.
Three ways to start
Examples of programmes organisations put together. Not fixed packages: in the intake we tailor the content to your team.
Agreeing one way of working
For departments where everyone does the same thing, only slightly differently.
- Setting up Teams and SharePoint in practice
- Agreeing ways of working together
- One folder and naming structure
Making the team AI-capable
For departments introducing AI broadly rather than person by person.
- Day 1: Microsoft 365 Copilot for everyone
- Day 2: prompt engineering and depth
- Ground rules for responsible use
Department track in several groups
For departments too large for one room.
- Several groups of twelve at most
- Spread over a few weeks
- Follow-up session to review the agreements
Only one or two colleagues?
An in-company day is often not the most practical format then. Our training calendar lists fixed dates with open enrolment, including Microsoft 365 Copilot and prompt engineering. Online or on-site in The Hague, twelve participants at most.
Training for teams and departments
Twelve participants per group at most. For a larger department we split it across several groups, spread over a few days or weeks. Above twelve, hands-on guidance noticeably suffers.
Yes, but the grouping matters. With large differences we advise grouping by skill level rather than by job title or team. Within a group we also work with exercises at two levels.
If the department fits into a single group of twelve, yes. If it is larger, it becomes several days. We prefer to schedule those close together, so everyone continues with the same agreements.
We close every team training with concrete commitments: what will you do differently, and who follows up. A return session after a few weeks to review those agreements works best.
Yes, and that happens often. Teams and SharePoint together, for instance, or Copilot with agreements on responsible use. In the intake we determine what realistically fits into a day.
Let us put the right programme together
Tell us what you are running into. We respond within two working days with a tailored proposal. No obligation.