Training in the areas we practise in, delivered around real deployments rather than in the abstract — so the people who will run a platform learn it on their own environment, with their own policies, before we hand it over.
What we teach
Training across our areas of expertise
We deliver training in the disciplines we work in every day: microsegmentation and Zero Trust, firewall and policy management, cloud and data centre architecture, information and data governance, and programme and project delivery.
Sessions are built for the audience in front of us. Engineers get hands-on work in the environment they will operate. Service and operations teams get the run-books and the decision points. Boards and senior stakeholders get the shorter version: what changed, what it protects, and what it now expects of them.
When it happens
Built around deployment and transition
During deployment
Training runs alongside the build, so your team sees the design decisions being made and understands why the configuration looks the way it does.
At transition
Structured handover sessions before we step back: operating procedures, escalation paths, common failure modes, and supervised practice on the real system.
After go-live
Refresher sessions for new joiners or after a significant change, so knowledge does not leave with the people who were in the room the first time.
What you keep
Knowledge transfer that outlasts the engagement
Knowledge transfer is a deliverable in its own right, not a slide at the end of a project. Every engagement leaves behind written documentation, run-books and operating procedures that your team owns and can maintain.
Where it helps, we shadow your engineers and then have them shadow us, so competence is demonstrated rather than assumed before we finish.
