Design sessions with the Studio
A design session is a focused 45 to 60 minute working meeting where your team moves from a well-defined use case to a usable build. Faculty bring students, districts bring teams, and organizations bring the people closest to the problem. Everyone leaves with something real to keep testing.
Three parts, one outcome
Before: the use case tool
When your session is scheduled, we send the Studio's use case development tool. Your team completes it together before the session. It is the pre-work that makes 45 minutes enough: by the time we meet, you have named the problem, the people it affects, and what better would look like. The tool is proprietary to the Studio and provided to registered teams for their session.
During: think, identify, build
In the session we pressure-test the use case, identify the data and content the build needs (and whether you are allowed to use it that way), and then build: a working assistant, tool, or workflow, shaped live with your team at the table.
After: test and refine
Participants leave with a usable build or workflow that belongs to them, plus a clear sense of what to test next. The session ends; the learning continues in your context, with our resources behind you.
What the session looks like
Sessions run 45 to 60 minutes on video, with a Studio facilitator. A typical arc:
Ground in the use case
Your team walks us through the completed use case tool. We sharpen the problem statement and agree on what a win looks like by the end of the hour.
Identify the data
What information does the build need? What do you already have, what is missing, and what are you permitted to use? This is where many use cases get honest.
Build together
We construct the first working version live: drafting the instructions, loading the right content, and testing it against real examples your team brought.
Plan the refinement
We name what to test, what to watch for, and when to revisit. You leave with the build and a short list of next steps.
Bringing students into the session
Design sessions work well as a class experience. Students form teams, complete the use case tool as an assignment, and join the session as the builders. They practice the full arc of responsible AI development: defining a problem worth solving, interrogating the data, building, and planning how to evaluate what they made.
Faculty tell us the pre-work is where the learning starts and the session is where it lands. Teams of three to six students work best, and multiple teams can be scheduled as a block.
Your team's checklist
A completed use case development tool, one per team. The people who will actually use what gets built, in the room. Any documents or examples the build should draw on, with permission to use them. And a note-taker, because the hour moves.
Ready to schedule?
Tell us about your course, team, or organization and the problem you want to work on. We will follow up with dates and the use case tool.
Get in touch