What Happens in a Workshop?
You take a seat at a table with three or four people you met a few minutes ago. Between you sits a brief for a system that doesn’t exist yet, and the clock starts on a one-hour session.
By the end of that hour, your team has agreed on what matters, sketched a design, and defended it in front of the room. It’s an architectural kata, run at a tech event, with every team in the room working on the same brief.
You don’t need to prepare anything or read up on architecture first. Everything the hour asks for is already at the table:
Your team is three to five people you just met, most likely from different specialties.
The session runs for one hour, from the first read of the brief to the last question from the room.
The whole hour goes into sketching, discussing, and deciding, on paper or a whiteboard. Nobody writes code.
Who You Design With#
Anyone can take part, whatever their role or experience. A tech event fills the tables with people who would rarely share a design session at work, and each of them gets something different out of it:
A developer new to architecture gets a first look at design work, with no real project at stake when a choice goes wrong.
A tech lead tests a familiar approach against people who would solve the problem differently, and has to defend it.
An architect gets more reps on a fresh brief, next to people who question choices a colleague would take for granted.
Most people at the table have only just met, so your team builds trust while it designs. Nobody knows whose opinion usually wins, which makes it easier to ask why.
A table of strangers can still fall in behind whoever speaks first, the anti-pattern known as The Loudest Voice. Give everyone a few minutes alone with the brief before the discussion starts.
How the Hour Runs#
Every team in the room gets the same brief, such as the one for a conference platform. The hour moves through three phases, and each one starts from what the last one left you with:
Understand and Prioritize
Work out who the system serves, rank the characteristics that matter most, and scope a first release.
Design
Turn those priorities into components, decide what to build and what to buy, draw the architecture, and record each key decision.
Share
Present your design to the room and question how other teams solved the same brief.
Whoever runs the session plays the organizers who wrote the brief. Ask them about anything it leaves out, such as whether the platform sells the tickets or what interacting with a talk means. Some answers won’t be clear, the way they wouldn’t be on a real project.
Making One Hour Count#
One hour is tight for a design, so you prioritize faster and leave more questions open. A few habits from the phase-by-phase guide help the hour go further:
Read the brief on your own before anyone speaks, and note the first questions it raises.
When a question can’t be settled in time, write it down as an assumption. Mark the one that could change your design most.
If time runs short, stop drawing and finish your decision records. A half-drawn diagram with clear reasons says more than a full whiteboard nobody can explain.
Picture your team stuck on whether the platform sells tickets, with half the hour gone. Write down that it doesn’t, note what would change if it did, and move on.
Another team may well make the opposite call. Comparing the two when you share is where the hour pays off, because each team sees what its own assumption cost.
What Your Team Leaves With#
Every team leaves with a design it can explain and defend. Behind that design sits the work you did during the hour:
Your top characteristics, ranked, so you know what to favor when two of them collide.
Your key decisions with their alternatives and trade-offs, written as decision records.
A diagram of the design, with each key decision numbered on it.
A release timeline that shows what ships first and what waits.
You also leave with the questions other teams asked about your design. They expose the assumptions you didn’t know you were making, and those stay useful long after the session ends.
Dates and Venues#
Each tech event gives the workshop its own date, room, and language. To see where it has run and where it’s headed next, look through the events.
Browse the tech events