AI can only help with work you can describe. And the most valuable work — yours — has usually never been described.
When these tools arrived, the people who got the most out of them were not the most technical. They were the ones who could state what they wanted: the goal, the constraints, what good looks like. The machine does not guess. It needs you to say what you mean.
Most AI training starts with the tools: which model, which prompt, which trick. We start with your work. Whatever your field and however long you have been in it, most of your method is unwritten — how you frame a problem, what you pay attention to, when you call something good enough. That unwritten method is the material the camp works with.
The camp is for writing it down. That sounds simple, and it is the whole difference: a written method is something a machine can execute, a stranger can question, and a team can improve. And it compounds — each piece of your work you make explicit makes the next thing you build faster.
The aim is not to get faster at generic tasks. It is to make your work legible enough that AI becomes a collaborator, and to leave with a way of working that keeps paying off long after the two days end.
Come for your experience, not your AI experience. The camp leans on what you already know — strategy, research, policy, craft — and mixes domains on purpose: the method transfers, and the demos are better for it.
Researchers, teachers, lab leads. People whose methods are rigorous but rarely written for anyone else to run.
Strategists, designers, writers, cultural workers. People who work by taste and want it to survive contact with the tools.
Product, operations, transformation. People who own a process a team needs to understand, not just follow.
Policy makers, public servants, civic institutions. People whose decisions must hold up when someone asks why.
You need work you care about, and the patience to say what you mean. If you would rather wait for a playbook, this camp is not the place — the people here are writing it.
Hands-on from the first hour.
Before
We ask everyone beforehand what they are working on and how they work today, so Day 1 starts from what is actually in the room rather than a round of introductions.
Day 1
You work on a real problem you bring with you, and make the method behind it explicit: the steps, the assumptions, what good looks like. Exercises with people from other fields test whether someone else could actually follow it.
Day 2
Alone or in a small cross-domain team, you put the written method to work with the tools and build something real. The day ends in demo rounds — not show-and-tell, but what did your way of working make possible.
Tell us which camp, what work you would bring, and why now.
Interested in running a version of Make It So Camp — at your university, company, or city? Partner with us ↗︎