You've selected great school management software. Now comes the hard part: getting everyone to actually use it. Implementation failures aren't usually about the software—they're about people. This guide covers the human side of rolling out new school technology.
Why Implementations Fail
- Insufficient training: Staff don't know how to use the system
- Poor timing: Launching during busy periods (exams, report time)
- No champions: Nobody driving adoption
- Resistance ignored: Concerns dismissed rather than addressed
- Parallel systems: Running old and new systems indefinitely
- Missing data: Poor migration makes the new system incomplete
Implementation Phases
Phase 1: Preparation (2-4 weeks before launch)
- Appoint an implementation lead (your internal champion)
- Clean up existing data (remove duplicates, correct errors)
- Gather all data to be migrated
- Schedule training sessions
- Communicate the timeline to all staff
- Set expectations with governing body
Phase 2: Data Migration (1-2 weeks)
- Export data from current systems
- Import into new system
- Verify data accuracy
- Set up users and permissions
- Configure school-specific settings
Phase 3: Training (1-2 weeks)
- Train admin staff first (they become helpers)
- Train teachers in small groups
- Provide written/video guides for reference
- Allow practice time before go-live
Phase 4: Go-Live (Week 1)
- Launch for real use
- Have support readily available
- Expect questions and teething problems
- Celebrate early wins
Phase 5: Bedding Down (Weeks 2-8)
- Address ongoing issues
- Provide additional training where needed
- Collect feedback and adjust
- Ensure old systems are retired
Managing Staff Resistance
Some staff will embrace change; others will resist. Understanding why helps you address concerns effectively.
Common Concerns
- "I'm not good with technology": Provide extra training and support
- "The old way worked fine": Show specific benefits for them, not just the school
- "I don't have time to learn this": Acknowledge the short-term effort; emphasise long-term time savings
- "What if I break something?": Reassure that mistakes can be fixed; create a safe learning environment
Find Your Champions
Identify 2-3 tech-savvy, enthusiastic staff members. Get them trained first and involve them in helping others. Peer support is often more effective than top-down mandates. Champions should represent different departments—admin, teaching, finance.
Strategies That Work
- Involve early: Include resistors in the selection and planning process
- Show, don't tell: Demonstrations are more convincing than promises
- Address WIIFM: "What's In It For Me?" Show personal benefits
- Provide safety nets: Ensure support is available when they struggle
- Celebrate progress: Acknowledge effort and small wins
- Be patient but firm: Support transition but don't allow indefinite avoidance
Training Best Practices
Training Structure
- Small groups: 5-10 people maximum for interactive sessions
- Role-based: Teachers need different training than admin or finance
- Hands-on: Learning by doing, not just watching
- Repeated: Schedule follow-up sessions for reinforcement
Training Materials
- Quick reference cards for common tasks
- Video tutorials for self-paced learning
- FAQ documents addressing common questions
- Contact information for support
Don't Skip Training
The biggest mistake schools make is assuming the software is "intuitive enough" that minimal training will suffice. Even simple systems need proper training. Undertrained staff revert to old methods or use the new system incorrectly.
Timing Your Implementation
Best Times
- Start of academic year: Clean slate, fresh start
- School holidays: Time for setup without daily disruption
- After final exams: Lower pressure, fewer competing priorities
Worst Times
- Exam periods: Staff are stressed and busy
- Report card time: Critical period, not time for new systems
- SASAMS submission deadlines: Don't add complexity when compliance is due
Common Pitfalls to Avoid
Running Parallel Systems Too Long
Some schools run old and new systems together "just in case." This doubles workload and prevents full adoption. Set a cutoff date and stick to it.
Incomplete Data Migration
If the new system doesn't have all the data, staff will keep using old systems or paper records. Ensure complete, accurate migration before go-live.
Ignoring Parent Onboarding
A parent app is only useful if parents install and use it. Plan parent communication and support alongside staff implementation.
Over-Customising
Resist the urge to customise everything immediately. Start with standard configurations, learn the system, then adjust as needed.
Measuring Success
How do you know if implementation was successful?
- Adoption rate: What percentage of staff are using the system daily?
- Support requests: Are issues decreasing over time?
- Time savings: Are processes actually faster?
- Data quality: Is information complete and accurate?
- Parent engagement: How many parents are using the app?
- Staff feedback: What do users say about the system?
Frequently Asked Questions
When is the best time to implement?
During school holidays or at the start of an academic year. Avoid mid-term when staff are busy with assessments and reporting.
How long does implementation take?
Basic implementation: 2-4 weeks. Full adoption: one term. Complex implementations may take longer.
How do you overcome staff resistance?
Involve staff early, explain personal benefits, provide adequate training and support, identify champions, and be patient but firm.
MyEncore Makes Implementation Easy
Dedicated implementation support, training resources, and a team that's guided schools through the process.
Planning an Implementation?
Let us show you how MyEncore supports schools through a smooth transition.
Book a Demo