Onboarding teachers

Most school deployments fail not because the product is wrong but because teachers are asked to learn three new tools at once. ClassPods onboarding is deliberately small.

The 45-minute first session

Run a single 45-minute teacher workshop with this agenda:

• 5 minutes — why we're rolling this out (school admin context)
• 10 minutes — walkthrough: log in, dashboard, language switcher
• 15 minutes — hands-on: every teacher creates one quiz from a topic they're teaching this week
• 10 minutes — host that quiz live with the other teachers as students (so they see both sides)
• 5 minutes — Q&A and next-step assignment

That's enough to make ClassPods usable in the next school day. Lesson packs, assignments, and the signal layer come later, by themselves.

Don't over-train

Resist the urge to walk every teacher through every feature. The friction in ClassPods is not feature complexity — it's just trying it the first time. Once a teacher has hosted one live session, they discover the rest on their own.

Designate a "first-pass" teacher

In every pilot, one teacher tends to get it faster than the others. Lean on them — they answer the small questions in the staff room more efficiently than support tickets.

The 2-week follow-up

Two weeks after the workshop, the school admin (or ClassPods rep) checks in:

• How many sessions has each teacher run?
• Any teacher who hasn't logged in?
• What's blocking the ones who haven't started?

This is light-touch — not a compliance review. The goal is to catch the one teacher who got stuck and needs a 15-minute one-on-one.

When to expand

If most of the pilot teachers are running at least one session a week by week three, the school is ready to expand. If not, the right move is usually to tighten the pilot scope, not the rollout speed.