Your conference proposal got accepted. Now the actual work starts, and it's a different task than the one that got you accepted. Writing the proposal meant describing what you do. Building the session means teaching a room full of strangers who don't know your students, your building, or your context, and that's a much harder version of the same lesson.
The lesson that works in your room won't survive unchanged
A lesson works in your classroom partly because of things that don't travel: your relationship with the students, the routines they already know, the three weeks of context before this specific lesson landed. A conference audience has none of that. If you present the lesson exactly as you'd teach it, without rebuilding the missing context, the room will nod politely and remember almost nothing by the drive home.
What changes when the audience is teachers, not students
1. Lead with the problem, not the activity, your audience needs to recognize their own version of the problem you were solving before they'll care about your solution; open with the "here's what wasn't working" moment, not the slide of what the final activity looked like
2. Build in a moment where they do the thing, not just watch you describe it, a five-minute hands-on version of your activity, done by the audience in pairs, sticks far longer than you narrating what your students did
3. Bring the messy version, not just the polished one, showing an early draft or a version that didn't work gives the room permission to adapt it imperfectly in their own room, instead of feeling like they have to replicate a finished product exactly
Getting from lesson to slide deck without losing a weekend
Our [workshop slide builder](/workshop-slides) turns your session outline and key talking points into a structured deck with the pacing built in, so you're refining slides instead of building the visual structure from a blank template the week before the conference. If you're still shaping the overall session flow, timing, and hands-on segment before you get to slides, our [workshop designer](/workshop-design) helps map the full 45 minutes so the audience-participation moment lands at the right point instead of getting cut for time at the end.
What still has to come from you
- The story of what actually happened when this didn't go as planned in your room, that's the part no tool can generate, and it's usually the part people remember afterward
- Reading the room and adjusting pacing live, a session built for 45 minutes might need the hands-on segment stretched or trimmed depending on how the specific group responds
- Answering the "but my kids are different" pushback with genuine flexibility, not defending the lesson as a fixed recipe
A good conference session doesn't hand people your lesson to copy. It hands them a problem they recognize and a structure they can rebuild for their own room. That's a different deliverable than the lesson plan that got you the acceptance email, and it's worth the extra planning time to build it as its own thing.
