Judgment, improved.
The Judgment Dojo
A weekly practice program for engineering teams, 8 to 16 weeks, on realistic codebases, ours or yours. From €8,000 per team.
A weekly practice program, 8 to 16 weeks, where your engineering team sharpens judgment the way a martial-arts dojo sharpens technique. Not a one-time event: show up every week, work on the fundamentals, get sharper over time.
Teams of 6 to 12 engineers. Curriculum tracks (pick one per Dojo):
- AI Code Judgment: evaluating AI-generated code, knowing when to accept, reject, or refactor. When "good enough" isn't good enough.
- Architectural Thinking: domain modeling, design decisions, trade-off reasoning. The decisions AI can't make.
- Refactoring Judgment: knowing what to change, when, and why. Reading code intent, not just code syntax.
- TDD and Quality Practices: Test-Driven Development as a thinking tool, not a compliance exercise.
How it runs
- 1
Week 1: the baseline and the track
We pick the track with you and take a baseline reading of the team.
- 2
Every week: a two-hour session
Theory through a structured exercise, applied practice on an example codebase or your own, and a group review. A practice assignment between sessions, sized so it fits next to delivery.
- 3
The last week: the reading again
The baseline reading repeated, so you see what changed. The team keeps the exercises, the review checklists, and the habits.
What you get
From €8,000 per team
The price depends on program length, 8 to 16 weeks. Open enrollment is possible per person when a cohort fills from several companies. The per-person price is quoted on request. Prices exclude VAT.
- Code reviews that get sharper and more structural.
- Architectural decisions questioned before the fact, not after.
- A shared vocabulary that stakeholders understand.
- A before-and-after reading of the team across the four dimensions of CODA (Comprehension and Ownership Depth Assessment).
- The exercises and checklists, yours to keep running.
Not to be confused with the Software Craftsmanship Dojo® we deliver with BriX: that one trains craft, this one trains judgment.
Who it's for
- Teams of 6 to 12 engineers who use AI coding tools daily and want to build judgment on purpose, not through on-the-job osmosis.
- Not for a team that wants a one-day workshop. The habit is the product, and changing habits takes weeks.
What to expect
A two-hour session a week, plus a short assignment, on realistic code, not toy problems: our example codebases, or your own where that serves the track better. Sessions run on site or remote. We coach, the team does the work. Where AI is in the room, it's the subject, not the instructor.
Questions engineering leaders ask
No. The first conversation is enough to pick a Dojo track or scope a Sprint. A Scorecard before and after gives you the measured change if you want it.
No. By default we practice on example codebases built for the track: no NDA needed, safe to break, and they work for cohorts mixing several companies. Where the track benefits, we use your code instead, under the same NDA and read-only terms as an assessment.
Yes, each team runs its own Dojo with its own track and baseline. Open enrollment mixes engineers from several companies when a cohort fills.
It will, some weeks. The program is built for it: the assignments between sessions are sized in hours, and a missed week is caught up, not skipped.
What a program at scale taught us: the case study.