Teacher Interview Questions for EdTech Founders

Teachers are generous with their time and instinctively encouraging, which makes them a uniquely dangerous population to interview badly — ask "would you use a tool that does X?" and most teachers will say something kind and noncommittal, not because they're being dishonest but because politeness and hope are both doing more work in that answer than genuine signal. The fix is Rob Fitzpatrick's Mom Test discipline applied specifically to the classroom: ask about specific things that already happened, never about a hypothetical future tool. This twenty-question script does that, organized into three blocks.

Quick Answer: Run a teacher interview in three blocks — current workflow and specific pain (what actually happens today, in detail), current workarounds (what they've already tried or built to cope), and purchase influence (who actually decides what gets bought). Never ask "would you use this" — ask "walk me through the last time this happened" instead, and let the specific answer tell you what you need to know.

The Interview Script, Ready to Copy

Block 1: Current Workflow and Specific Pain

  1. "Walk me through how you currently handle [specific workflow — grading, parent communication, lesson planning, etc.] on a normal week."
  2. "What's the most frustrating part of that process, specifically?"
  3. "Tell me about the last time that frustration actually cost you real time or caused a real problem — what happened?"
  4. "How much time would you estimate you spend on this in a typical week?"
  5. "Has this gotten better or worse over the past year or two, and why?"
  6. "What have you already tried to make this easier?"

Block 2: Current Workarounds and Tools

  1. "What tools or systems do you currently use for this, if any?"
  2. "What do you like about your current approach?"
  3. "What's missing or frustrating about it?"
  4. "Have you ever paid for, or asked your school to pay for, a tool to help with this? What happened?"
  5. "Do other teachers you know handle this differently? How?"
  6. "If you could wave a magic wand and fix one thing about this workflow, what would it be?" (Use sparingly — this is the one hypothetical question in the script, useful mainly for surfacing language, not as validation evidence itself.)

Block 3: Purchase Influence and Decision Process

  1. "If you found a tool that genuinely solved this, what would you do next?"
  2. "Has your school or district adopted a new tool for something similar recently? How did that decision get made?"
  3. "Who would need to approve something like this — you directly, your principal, the district?"
  4. "Has your school ever piloted a new tool you were excited about? What happened to it?"
  5. "What's made you or your school say no to a tool in the past, even one that seemed useful?"
  6. "Is there budget available for something like this, as far as you know?"
  7. "Who else on your team or in your school deals with this same problem?"
  8. "Would you be open to a short follow-up conversation, or trying something in your classroom, if I built a version of this?"

Question-by-Question Intent

Questions 1 through 6 exist to get a detailed, specific picture of the actual current workflow — not a summary, but the real steps, in order, including the parts a teacher might not think to mention unprompted. Question 3 specifically ("tell me about the last time") is the core Mom Test move: it forces a concrete memory rather than a general impression, and concrete memories are much harder to unconsciously exaggerate or soften than general statements.

Questions 7 through 11 map the competitive and workaround landscape from the teacher's actual experience — what they use now, what they've tried, and critically, question 10's direct question about whether they've ever paid or requested payment for something similar, which surfaces real evidence of willingness to invest rather than just willingness to complain.

Question 12 is deliberately marked as the one hypothetical question in the script — it's useful for surfacing the teacher's own language about the ideal fix, which is valuable for your eventual product copy, but it should never be treated as validation evidence on its own, since "what would you want" answers are exactly the kind of polite, aspirational response the Mom Test warns against over-trusting.

Questions 13 through 20 are the block most edtech founders skip, and the one that matters most for actually selling anything — teacher enthusiasm alone doesn't predict a purchase, because in most schools a teacher isn't the final buyer. Question 15 in particular ("who would need to approve") often reveals that a genuinely excited teacher has no real path to getting a tool purchased without administrator buy-in, which reshapes your entire go-to-market plan if you learn it early rather than after months of teacher-focused outreach.

Filled Example: Excerpts From a Practice Interview

Interviewer, testing an idea for a parent-communication tool, talking with a 4th-grade teacher:

Q3 (last time it caused a problem): "Honestly, two weeks ago. I sent a group email about the field trip permission slip deadline, and I found out later that at least four families never got it because the email bounced or went to spam — I only found out when kids showed up without permission slips the morning of, and I had to scramble to call parents directly during instructional time."

Q10 (paid for something before): "We actually tried a paid app two years ago — I want to say it was around $8 a month out of my own pocket — but maybe a third of parents ever downloaded it, so I ended up doing email anyway for anyone who hadn't, and eventually just gave up and went back to email for everyone."

Q15 (who approves): "For anything that costs the school money, it goes through my principal, and honestly for the whole school to adopt something, it'd probably need to go to our district's ed-tech committee, which meets maybe twice a year."

This short excerpt already surfaces three separate, usable pieces of evidence: a specific, recent, costly failure (Q3), a documented prior willingness to pay combined with a real adoption-rate problem that sank the last attempt (Q10), and a purchase-approval path that's slower and more bureaucratic than the teacher's personal enthusiasm alone would suggest (Q15) — exactly the kind of concrete detail a "would you use this?" question would never have surfaced.

Adaptation Notes: Administrators vs. Teachers vs. Instructional Coaches

For administrators (principals, curriculum directors), shift Block 3 to the center of the interview rather than the end — they're closer to the actual purchase decision, so questions about budget cycles, procurement process, and what's made them say no to tools in the past deserve more time and follow-up than they would with a classroom teacher.

For instructional coaches or department heads, who often sit between teachers and administrators, ask specifically about their role in tool recommendations — a coach who's trusted by both teachers and the principal can be a genuinely valuable bridge, and understanding how they influence (without necessarily approving) purchases is worth its own dedicated line of questioning beyond what's in the base script.

For classroom teachers specifically, resist the urge to compress Block 1 to save time — the detailed, specific workflow questions are where the majority of useful, product-shaping information actually comes from, and rushing through them to get to the purchase-influence questions sooner tends to produce a shallower overall interview.

Key Takeaways

Frequently Asked Questions

How many teachers should I interview before I trust a pattern?

Eight to ten interviews within one specific grade level, subject, or workflow focus is a reasonable starting point to see whether a pain point and its specific details genuinely repeat, rather than reflecting one teacher's unusual situation — see the broader discipline in the complete guide to customer research for founders for how this scales across a validation process.

Where do I find teachers willing to be interviewed?

Teacher-focused communities on Facebook and Reddit organized around a specific grade level or subject, your own personal network if you have connections in education, and direct, respectful outreach through school websites or LinkedIn are all reasonable starting points — see where to find teachers to interview for more channel-specific detail.

Should I record these interviews?

With explicit permission, yes — recording (or at minimum, detailed real-time notes) lets you capture the specific language and details a teacher uses, which matters both for accurately understanding the problem and for later product and marketing copy that speaks in the same terms your actual users use.

What if a teacher is enthusiastic but their school has no budget for new tools?

Treat this as important, real information rather than something to argue past — it tells you either that this particular school isn't your near-term buyer, or that a free or teacher-paid individual model might be more viable than a school-funded purchase for your specific product, both valid but different paths that this script's Block 3 questions are specifically designed to surface early.