Single programme
A team or role that needs to build one clear skill on your platform.
2 to 4 weeks, fixed scope
- Skills assessment for the group
- Hands-on labs
- Written standards for their main tasks
- Follow-up session
We train your engineers, analysts, and data owners on your own platform and in your own code, so the standards we agree are the ones your team keeps using.
A new platform is only as good as the number of people who can use it properly. Without training, engineers copy whatever they find in the repository, analysts build their own versions of the same table, and the standards agreed during the project fade within months. Generic courses do not help much, because they teach a tool in the abstract. We teach on your platform, using your code and your data, and we leave behind the standards and examples to keep it consistent.
Training that happens in your own environment, on your own code, with materials you keep afterwards.
Each group learns something different, because they use the platform in different ways.
What we teach
Building and testing pipelines, writing maintainable models, handling failures, and releasing changes safely.
What they can do afterwards
Deliver and support a new pipeline end to end using the team’s own standards.
What we teach
Working from the governed model, writing efficient queries, and designing reports for decisions.
What they can do afterwards
Answer questions from trusted data without building a separate copy.
What we teach
Capacity and cost control, workspace and access setup, monitoring, and release practice on Fabric or Databricks.
What they can do afterwards
Run the platform from code and respond to common incidents.
What we teach
What ownership means, how to define a metric, and how to handle quality problems and access requests.
What they can do afterwards
Take responsibility for their data and keep its definitions current.
What we teach
How to read cost and quality reports, judge proposals, and set priorities for data work.
What they can do afterwards
Ask better questions and sponsor the right work with confidence.
We start with one cohort, learn what works in your organisation, then widen it.
Phase 1
1 week
You receive
Skills findings, a programme outline, and baseline measures.
Phase 2
2 to 3 weeks
You receive
Course materials, labs, and draft standards.
Phase 3
4 to 8 weeks
You receive
Trained cohorts and a body of reviewed, real work.
Phase 4
Ongoing
You receive
Results report, internal leads in place, and refreshed standards.
Choose a single programme, a full rollout, or ongoing support for teams already trained.
A team or role that needs to build one clear skill on your platform.
2 to 4 weeks, fixed scope
Organisations introducing a new platform to several teams at once.
2 to 4 months
Teams already trained who want help as the platform and the team change.
Monthly
What you keep when the programme ends, and the tools we teach with.
We teach on the platforms and tools your company has already chosen, not ours.
Your own. Labs use your pipelines, tables, and infrastructure, so what people practise is what they will work on.
We assess first and group people by level and role. Beginners and experienced engineers are not taught in the same room.
We set baselines in phase 1 and measure again afterwards: review quality, time to deliver, incidents, and people’s own confidence. The report compares them.
Workshops work best with 12 to 20 people. Engineering labs are smaller, usually 6 to 10, so everyone gets feedback.
Your internal leads keep the practice going, and you keep all the materials. Many clients add the monthly clinic for the first six months.
Just launched a new platform and want more people using it well? Tell us who needs to learn what, and we will suggest a first cohort.
Book a discovery callStart a conversation