Programs · Engineering Management
The Weekly Operating System For Small Engineering Teams
A four-week operating block to install the weekly cadence, written rituals, and review meetings that survive the next two hires.
- Duration
- 4 weeks · 12 hours live
- Format
- Cohort
- Stage fit
- Seed
- Leadership focus
- Operations
- Programme fee
- ₩1,450,000 (KRW) — full programme, no hidden fees
The brief
What this program is, in plain language.
Most engineering teams between five and fifteen people run on tribal knowledge that breaks at hire sixteen. This program installs an explicit weekly operating system: a Monday plan, a Wednesday review, a Friday letter — and the writing standards that hold each of them up under load.
What is included
- Four working sessions, one per week
- A written team operating doc reviewed by an external operator
- Three meeting templates with explicit timeboxes
- A Friday letter template tuned to small remote-first teams
- A peer review pair across the cohort that lasts two months
Outcomes you can defend
- A working operating system in production by week three
- A written team operating doc reviewed by an outside operator
- A peer accountability pair beyond the cohort
Frequently asked, honestly answered
Can I take this with a team of three?
Yes, but expect to skip the meeting templates and focus on writing rituals.
Does this conflict with our existing sprint cadence?
It is sprint-agnostic. We have run cohorts with Scrum teams, Shape-Up teams, and continuous deployment teams without rewriting their process.
Where this is the wrong fit
Teams larger than twenty engineers will outgrow the templates inside six months. Take this program before you reach that size.
From the cohort floor
The Friday letter template is the only ritual that survived our reorg. That alone made the program pay for itself. Chae-young Bae · Engineering Manager · Boltrange Co.
Light, useful, no theatre. The peer pair lasted four months past the end date. That is the actual result. Nicolas