Architectural Katas

Practice System Design as a Team

Code gets cheaper every day, and an AI agent can now write a working feature in seconds. Every feature still carries design decisions, and making them on purpose takes practice.

Four people gather around a table covered in system diagrams.

In an architectural kata, your team agrees on what matters, sketches a design, and backs every choice with a reason the others can follow. You leave with the design, the reasons behind it, and a list of what you still don't know.

Why Design Takes Practice#

Most developers design a system from scratch only a few times in their career. Judgment about trade-offs grows with repetition, and a kata gives you far more of it than real work does:

On a Real ProjectIn a Kata
How often you decideA few times in a careerMany times in one sitting
When the consequences show upMonths or years laterWithin minutes, when someone asks why
What a wrong choice breaksA system people rely onNothing, because nothing ships

An architectural kata is a practice exercise where your team designs a system that doesn't exist yet from a short brief, with no code to write and no correct answer. You can try an idea, see what it costs, and change your mind as often as the discussion needs.

Why AI Makes Practice Necessary#

Writing code used to be slow enough that design decisions came up along the way. Now an AI agent can write a working feature in seconds, and that feature answers questions nobody put to it:

  • Where does the data live?

  • What happens when a call fails?

  • What will the next change have to touch?

If nobody answers them on purpose, the code answers them anyway, and nobody notices until the answer costs something. You can no longer afford to forget about architecture, because the code no longer gives you time to notice it's missing.

The skill that matters now is seeing which decisions a change involves and weighing what each option costs. A kata is where you practice that, with a team that asks you to explain every choice.

Where to Start#

Each page builds on the one before it, so they read best in this order. If you only want to try a kata with your own team, the first three pages are enough:

  1. What Is a Kata?

    See what a kata asks of you and read the conference brief that the next page works through. Notice the gaps it leaves, because they shape the design as much as the stated needs.

  2. How Do You Work Through a Brief?

    Follow a team through that same brief, phase by phase, from setting priorities to defending the design. Read it from top to bottom, because each phase starts from what the last one left you with.

  3. Which Tools Do You Need?

    Learn the decision records, release timelines, and C4 diagrams a kata uses, and find more katas to practice on. Keep it open beside the Guide and jump to a tool whenever the Guide points you there.

  4. What Happens in a Workshop?

    See how a kata runs in one hour at a tech event, with a team of people you just met. It shows what changes when the clock is shorter and the table mixes specialties.

  5. Where Do We Run It?

    Find the tech events where we run the workshop, with the date, venue, and session details for each. It also explains why a tech event changes how a kata plays out.