TL;DR: Schools waste over $5 billion annually on EdTech software that teachers never use. 67% of licenses sit completely dormant. The problem isn’t bad technology. It’s the gap between “feature complete” and “classroom ready.” We’ve learned that successful EdTech doesn’t start with features. It starts with teacher workflows, real classroom constraints, and the hard truth that technology must reduce workload, not add to it.
The $5 Billion Lesson Nobody Wants to Learn
Here’s a number that should terrify anyone building educational technology: school districts waste over $5 billion annually on software that teachers never use.
Not underuse. Not occasionally use. Never use.
The average district has 67% of their EdTech licenses sitting completely dormant. Some have it worse. One mid-sized district we worked with was paying for 43 different learning platforms. Teachers regularly used four.
This isn’t a technology problem. It’s an implementation ecosystem problem. The chain from procurement to classroom is broken at every link.
Administrators buy based on feature lists. Vendors sell to decision-makers, not end users. Teachers get handed technology without training, support, or voice in the selection. Then everyone wonders why adoption rates hover near zero.
The LAUSD iPad initiative taught us this the expensive way. $1.3 billion to put iPads in the hands of 650,000 students. Within a week, students had hacked the security. The Pearson curriculum platform was incomplete and buggy. The FBI investigated procurement irregularities. Most importantly, teachers had zero input in the selection process.
The program was cancelled after $130 million spent. The lesson? Technology without pedagogy fails. Every time.
Why Good Learning Tech Goes Unused
The best learning technology often goes unused not because teachers are resistant, but because we failed to make it classroom-ready, workflow-friendly, and teacher-supported.
After building EdTech platforms for schools, universities, and corporate learning, we’ve identified the seven gaps that kill adoption:
1. The Procurement Gap
Decisions made without teacher input. Features evaluated in demos, not classrooms. Solutions seeking problems rather than problems defining solutions.
2. The Training Gap
One-time training sessions focused on navigation, not pedagogy. No ongoing support. Teachers expected to self-teach complex platforms while managing 30 students and 3-minute transitions.
3. The Support Gap
When the “seamless” system crashes at 7:40 AM every morning (and it will), who fixes it? Without dedicated technical support, teachers abandon tools that create more problems than they solve.
4. The Integration Gap
Stand-alone tools that don’t connect to gradebooks, LMS systems, or existing workflows. Teachers spend more time managing technology than teaching.
5. The Time Gap
Teachers work 50+ hours per week. They have approximately 3 minutes between periods. No dedicated time exists for learning new technology. Tools that require extensive setup get abandoned.
6. The Evidence Gap
Products scaled without proof they work. EdTech investors rarely ask for measures of learning effects. They prioritize user bases over educational efficacy.
7. The Workflow Gap
Technology that disrupts rather than enhances practice. Products designed for ideal scenarios, not real classrooms with unreliable WiFi, constant interruptions, and high-stress moments.
The Philosophy: Feature Complete vs. Classroom Ready
This is where most EdTech goes wrong. Teams celebrate when software is “feature complete.” All buttons work. All menus function. Code is production-quality.
But feature complete means nothing if the product isn’t classroom ready.
Feature Complete = Software has all planned functionality implemented and working Classroom Ready = Software is actually usable by teachers in real conditions to achieve educational outcomes
The difference is the difference between adoption and abandonment.
A 2023 study found that EdTech products developed with ongoing educator input showed 67% higher adoption rates than those built by technology teams alone. The products weren’t necessarily more feature-rich. They were more classroom-ready.
What “Classroom Ready” Actually Means
Pedagogical Alignment
- Supports actual teaching practices, not theoretical ones
- Aligns with curriculum standards teachers must meet
- Enables effective learning activities, not just digital versions of worksheets
- Evidence of positive learning outcomes, not just engagement metrics
Usability Under Real Conditions
- Works with typical school internet (unreliable, slow, shared)
- Functions during high-load times (everyone logging in at 8:00 AM)
- Quick to start and navigate (under 30 seconds)
- Minimal technical issues (doesn’t crash during lessons)
Workflow Integration
- Fits within time constraints (3-minute transitions)
- Connects with existing tools (gradebooks, LMS, SIS)
- Reduces rather than increases workload
- Matches classroom rhythms and bell schedules
Implementation Support
- Clear onboarding process (not just documentation)
- Ongoing technical support (not just a help desk ticket)
- Professional development resources (bite-sized, just-in-time)
- Community of practice (peer support, not vendor support)
Evidence of Efficacy
- Research demonstrating learning gains
- Successful pilot implementations in similar contexts
- Teacher testimonials from real classrooms
- Measurable outcome improvements
The “Built for Learning” framework puts it simply: “Closing the gap between EdTech design and classroom reality requires understanding both worlds.” Most technology teams understand technology. Few understand classrooms.
The Reality of Teacher Workflows
To build EdTech that gets used, you must understand the reality of teacher workflows. Not the idealized version. The actual, chaotic, constrained reality.
The Daily Reality:
- 3 minutes between periods to reset for the next class
- Hallways with 3,000 students changing classes in 5 minutes
- Multiple preps with diverse student needs
- Constant interruptions and urgent demands
- 50+ hour work weeks with increasing administrative burden
- Unreliable technology that fails at the worst moments
What Teachers Need:
- Quick lesson planning and material preparation
- Efficient grading and feedback
- Seamless classroom management
- Communication with students and parents
- Administrative compliance (attendance, reports)
- Professional development and collaboration
What EdTech Often Delivers:
- Login to multiple systems
- Duplicate data entry
- Complex navigation for simple tasks
- Context switching between tools
- Technical troubleshooting during instruction
- Additional platforms to monitor
The math is simple. If a tool saves 10 minutes per use but takes 30 minutes to learn and implement, it must be used 3+ times before breaking even. Most abandoned tools never reach that threshold.
The Integration Imperative
Here’s what we’ve learned: EdTech products that integrate seamlessly with existing workflows show significantly higher adoption rates than standalone solutions.
Teachers won’t change everything else they do to accommodate your tool. Your tool must accommodate how they already work.
The “Works For Me” Test:
Can a teacher use this tool tomorrow without changing everything else they do?
- If Yes: High adoption potential
- If No: Significant implementation challenge
What Integration Actually Looks Like:
Technical Integration
- SSO compatibility (Google, Microsoft, Clever)
- Automatic rostering from SIS
- Gradebook passback
- LMS embedding (Canvas, Google Classroom)
- Mobile access for on-the-go use
Pedagogical Integration
- Curriculum alignment and standards mapping
- Assessment connection to grading workflows
- Differentiation support for diverse learners
- Lesson planning integration
Administrative Integration
- Compliance reporting
- Attendance tracking
- Parent communication portals
- FERPA-compliant data handling
The Google Classroom ecosystem succeeds not because it’s the best learning platform, but because it integrates with G Suite, uses familiar interfaces, and works within existing Google workflows. Teachers adopt it because it doesn’t require them to learn a completely new system.
Real Examples: What Works and What Doesn’t
The $1.3 Billion Failure: LAUSD iPad Initiative
What Went Wrong:
- Zero teacher input in selection
- Security failures within a week
- Incomplete, buggy curriculum platform
- Inadequate training and support
- No infrastructure assessment
The Lesson: Technology without pedagogy and teacher buy-in is expensive shelfware.
The Success: Moreno Valley USD with Kami
What Went Right:
- Research-backed selection for literacy improvement
- Daily use expectation with support
- Teacher training and ongoing coaching
- Independent evaluation of outcomes
Results:
- 4 percentile gain in reading scores
- Measurable student engagement increases
- Sustained adoption across the district
The Lesson: Clear problem definition, teacher involvement, and evidence-based implementation drive adoption.
The Pattern We’ve Observed
After building EdTech platforms for diverse educational contexts, here’s what successful implementations share:
What Works:
- Teacher involvement from the start (not after purchase)
- Clear connection to learning outcomes (not just features)
- Robust professional development with ongoing support
- Adequate infrastructure and technical support
- Administrative commitment to adoption, not just procurement
- Realistic timeline for implementation (years, not months)
- Integration with existing curriculum and workflows
- Evidence of efficacy before scaling
What Doesn’t:
- Top-down mandates without input
- Technology-first rather than learning-first approach
- Inadequate training or support
- Unrealistic implementation timelines
- Ignoring infrastructure requirements
- Feature-focused rather than outcome-focused
- No accountability for adoption
- Treating devices as the solution rather than tools
How to Build EdTech That Actually Gets Used
If you’re building educational technology, here’s our practical framework based on what we’ve learned:
Phase 1: Research Before You Build
Talk to Teachers First
- Conduct user research with 20+ educators before writing code
- Observe classrooms to understand real workflows
- Identify actual problems, not perceived ones
- Test assumptions about how teachers work
Understand the Ecosystem
- Map existing tools and workflows
- Identify integration points
- Learn technical constraints (connectivity, devices, platforms)
- Understand compliance requirements (FERPA, state standards)
Define Success Differently
- Measure learning outcomes, not just usage
- Track teacher satisfaction, not just feature adoption
- Evaluate workflow improvement, not engagement time
- Focus on efficacy, not user base growth
Phase 2: Design for Reality
Start with Workflow Integration
- How does this fit into a 50-minute class period?
- Can a teacher set this up in under 3 minutes?
- Does it work when the internet is unreliable?
- Can it be used on a phone between classes?
Design for Cognitive Load
- Minimize clicks for common tasks
- Reduce context switching
- Use familiar patterns and interfaces
- Provide clear feedback and error handling
Build for Failure
- What happens when the system is down?
- How do teachers recover from errors?
- Is student work saved automatically?
- Can teachers continue teaching without the tool?
Phase 3: Implement with Teachers, Not To Them
Include Teachers in Beta Testing
- Recruit early adopter teachers
- Provide dedicated support during pilots
- Gather feedback weekly, not just at milestones
- Iterate based on real classroom use
Provide Comprehensive Support
- Just-in-time, bite-sized training (not one-time sessions)
- Ongoing coaching, not just documentation
- Peer mentoring programs
- Dedicated technical support (not a ticket system)
Plan for Gradual Adoption
- Start with volunteers and early adopters
- Scale based on lessons learned
- Allow teachers to integrate at their own pace
- Celebrate early wins and share successes
Phase 4: Measure What Matters
Track the Right Metrics
- Learning outcome improvements
- Teacher time savings
- Workflow efficiency gains
- Student engagement quality (not just quantity)
Gather Qualitative Feedback
- Regular teacher interviews
- Classroom observation
- Student feedback sessions
- Support ticket analysis
Iterate Based on Evidence
- Monthly review of adoption metrics
- Quarterly assessment of learning outcomes
- Annual evaluation of ROI
- Willingness to pivot if not working
The Mindset Shift
Building EdTech that actually gets used requires a fundamental mindset shift:
From: “We built great features. Teachers should want to use them.” To: “Teachers have real constraints. We built something that works within them.”
From: “One training session should be sufficient.” To: “Learning new technology requires ongoing support and practice.”
From: “Integration is a nice-to-have.” To: “Integration is essential for adoption.”
From: “Our product is feature-complete.” To: “Our product is classroom-ready.”
From: “We sell to administrators.” To: “We serve teachers and students.”
The Uncomfortable Truth
Here’s what most EdTech companies don’t want to hear: the best learning technology in the world is worthless if teachers can’t or won’t use it.
You can have the most sophisticated AI, the most engaging gamification, the most comprehensive content library. If it doesn’t fit into a teacher’s workflow, account for unreliable school internet, or provide adequate support, it will sit on the digital shelf collecting dust.
The $5 billion waste isn’t because schools bought bad technology. It’s because they bought technology that wasn’t classroom-ready. That didn’t integrate with workflows. That didn’t include teachers in the process. That prioritized features over outcomes.
Our Commitment
At Compound, we don’t build EdTech in isolation. We embed ourselves in classrooms. We talk to teachers before we write code. We test under real conditions with real students. We measure success by learning outcomes, not user registrations.
We’ve learned that educational technology succeeds when:
- Teachers are partners, not recipients
- Problems define solutions, not vice versa
- Integration is designed in from day one
- Support continues long after launch
- Evidence drives iteration
The question isn’t whether technology can improve education. It can. The question is whether we have the discipline to build it thoughtfully, implement it carefully, and support it continuously.
That’s the difference between EdTech that goes unused and EdTech that transforms learning.
Building EdTech that teachers actually use? We’d love to hear about your challenges. Contact us and tell us what you’re trying to build.