Successful implementation of Fedena or any other ERP solution in your institution requires 5% technical skills and 95% social & political skills.
Strategy 1 – A Team
Make a team with maximum 5 employees of your institution and call this the A Team for fedena implementation. This team can include teachers and non-teaching staff. Link the successful implementation of Fedena to the performance appraisal of the A Team members. Always choose the best team possible. Give members the authority, the autonomy and the time to ensure that the implementation is done quickly and done well.
Strategy 2 – One thing at a time
You don’t have to implement the entire features of Fedena all at once. We have noticed that a phased approach works well for Fedena implementation. This is a much safer and advisable way and has many benefits over the conventional “big bang” approach of implementing all at once. Start with login access of teachers and employees. Then go to timetable and attendance. Start some group discussions. Tell some of the parents to login and take part in discussions. Avoid external emails and use the inbuilt message system of Fedena. All depends on your leadership style and strategy.
Strategy 3 – Rewards & Punishments
A carrot and stick strategy works very well for increasing the usage and success rate of employees in your organization. The admin should demand the daily usage of the system and associate rewards with the successful usage of the school management system.
FAQ: How to make teachers and employees of my institution to use Fedena efficiently?
Fedena is an enterprise solution which demands commitments from Teachers and non-teaching staffs of your organization to achieve its full potential and increase the efficiency of your organization.
- Understand that people fear to make mistakes. The employees of your institution may fear that a simple mistakes done while entering the data to the software will be ridiculed by the technical team or other staff. So train your employees well and assure that there is no problem in making mistakes.
- Don’t give the job of daily data entry to teachers initially. Let it be done by a technical employee who can update the data of the system as suggested by teachers offline.
- Carrot and Stick model. Let there be rewards associated with usage of the software and punishments for not using it.