for-teams
A company team is a cohort that already exists.
We profile the team, write the plan around your systems and the thing you actually need to ship, and run it with your tooling. Same model as an open cohort, with the cohort decided by you.
when
When it makes sense
A migration is coming
Moving to Kubernetes, to a new cloud, to infrastructure as code. The team learns on the migration itself.
You inherited infrastructure
The people who built it are gone. The team needs to understand, document and take control of what runs.
Security has to become everyone's job
No security team, or a small one. Engineers and admins need to harden, detect and respond as part of normal work.
Juniors need to become productive
A group of new hires or switchers who need the engineering habits, with mentors who review their real work.
difference
Open cohort versus team cohort
| open cohort | team cohort | |
|---|---|---|
| Cohort | 6–12 strangers with the same target | Your team, 2–25 people |
| Profiling | Individual skills maps | Skills map for the team plus a review of your systems |
| Plan | Written for the cohort | Written for the team and a concrete goal: a migration, a service, a security baseline |
| Labs | Our lab infrastructure | Your stack where possible, ours where it is safer |
| Capstone | A portfolio project | Something you needed anyway, shipped during the cohort |
| Format | Live online | Online, or on site by arrangement |
| Price | Per person | Per cohort, fixed in the proposal |
deliverables
What you get
- Team skills map and a written plan you can approve before anything starts
- Mentor team chosen for your stack, with named people and hours
- Two live sessions a week plus labs and mentor hours, scheduled around your sprints
- A capstone on your systems, with handover documentation
- Written closing report: what the team can now do, what is next
for-teams#request
Request a proposal
We reply within two working days to set up a scoping call. The written proposal follows the call. Prefer email? [email protected]