Tailored workshops
Half-day sessions built around your actual stack and conventions, covering infrastructure as code, Kubernetes and pipelines, with exercises drawn from work your team recognises.
Optimisation & Advisory
Training & Team Enablement
Your engineers leave able to run the platform, not just watch someone else do it.
The work
What this actually does
Training that happens away from your codebase rarely survives contact with it. We build the curriculum around the systems you actually run, using your repositories, your cluster and your pipelines as the exercises. Sessions are short and repeated rather than a single intense week, because most platform skills only stick when they are practised on real problems over time.
Every engagement starts with a skills map: what the team can already do unaided, what it can do with help, and what nobody currently owns. From there we agree the handful of capabilities worth building this quarter, then pair on live tickets to build them. You keep the workshop material, the internal notes and the runbooks your team writes along the way.
If any of these sound familiar
- Only one person understands how the cluster is wired
- Training runs are generic and forgotten within a fortnight
- Contractors leave and take the operational knowledge with them
- New joiners spend weeks reverse-engineering the setup
Scope
What's included
Every engagement on this page covers the following, sized to your setup rather than delivered as a fixed package. If something here is not relevant to you, it comes off the scope and off the price.
Pairing on real work
We sit on your tickets rather than a sandbox, writing the Terraform, manifests and pipeline changes together so the reasoning behind each choice is visible.
Code review coaching
Review comments on genuine pull requests, explaining what to change and why, so standards spread through the team instead of arriving as a policy document.
Internal knowledge base
Runbooks, decision notes and troubleshooting guides written by your team with our help, stored in your repository and reviewed like code so they stay current.
Skills map and plan
An honest picture of what the team can do unaided, where the gaps are, and a quarterly plan naming who is learning what and by when.
Readiness check
At the end we watch your engineers run a change without us, and report whether they are ready to own it or need another round.
What changes
What teams typically see
4Engineers enabled per cohort
1 quarterTypical enablement cycle
0Single-owner critical systems
Handover
What you keep
Everything produced during the engagement is yours: the repositories, the accounts, the documentation. There is no proprietary layer and nothing to unlicense if you take the work in-house.
- Workshop material tailored to your stack
- Skills map with gaps and named owners
- Paired changes committed under your engineers' names
- Internal runbooks, decision notes and troubleshooting guides
- Quarterly enablement plan with review checkpoints
Tooling
Tools we use here
A starting point, not a requirement. We work in whatever you already run wherever it does the job.
Terraform
Kubernetes
Docker
GitHub
GitLab
Argo CD
Prometheus
How it runs
From first call to handover
The same four steps on every engagement. You see each one before it starts and can stop at any of them.
- 01
Map the skills gap
We watch how the team works today, talk to the people on call, and agree which capabilities matter most for the next quarter rather than listing everything at once.
- 02
Design the curriculum
A written plan naming sessions, exercises, who attends and what each person should be able to do unaided when the quarter ends.
- 03
Teach and pair
Sessions run in short blocks, with the theory kept brief and most of the time spent on your tickets, your pull requests and your incidents.
- 04
Hand over ownership
We deliberately reduce our involvement, letting your engineers lead the change while we review from the side and step in only when asked.
Questions
Asked before we start
Can you train a team with mixed experience levels?
Yes, and most teams are mixed. Sessions are split by what people can already do rather than by job title, and the pairing lets stronger engineers explain their reasoning while newer ones get their questions answered on real work.
What if our tooling changes halfway through?
We expect it to. The curriculum covers concepts and habits that survive a tool swap, and the workshop material is versioned in your repository so it can be updated when your stack moves on. We would rather teach transferable practice than a fixed tool manual.
How do you know the training worked?
We check whether your engineers can make a change without us: raising the pull request, explaining the trade-offs and handling the follow-up. That readiness check is done at the end of the engagement and repeated at the next quarter review.
Is this classroom-style training or hands-on?
Hands-on, almost entirely. Short theory blocks set context, then we work in your repositories on tickets the team already owns. Nobody learns Kubernetes by watching slides about namespaces; they learn it by breaking a cluster that is not production.
Optimisation & Advisory
Often needed alongside this
Optimisation & Advisory
DevOps Assessment & Enablement
A maturity assessment that produces a prioritised roadmap, then hands the team the skills to run it.
- Delivery, reliability and security maturity audit
- Prioritised 90-day improvement roadmap
- Hands-on training, pairing and runbook handover
Optimisation & Advisory
Technical Documentation & Runbooks
Diagrams, decision records and step-by-step runbooks that turn a 3 a.m. page into a checklist.
- Architecture diagrams kept in sync with reality
- Operational runbooks for every alert
- Architecture decision records and onboarding guides
Platform & Containers
Internal Developer Platform
A paved road for your developers: self-service environments and golden-path templates in one portal.
- Backstage portals and service catalogues
- Golden-path scaffolding for new services
- On-demand and ephemeral preview environments
Worth a conversation about Training & Team Enablement?
Bring the specific problem. We will tell you honestly whether this is the service that fixes it, and what it would take.