Teacher´s Helper is an easy and fast tool for teachers, which runs on a mobile device, for example a tablet. It´s built to improve and ease the daily routine of a teacher. Furthermore this tool centralizes documentation, communication and organisation on one single device. As we learned during our interviews, that the main problem of the teachers at SchlaU-Schule is that all information flow is not well organized and happens on a random basis. Teachers only working a couple of hours a week, don’t get important information, because they do not participate in the grapevine.
Our solution covers serveral fields of a teacher’s needs. Personal planning, creation of a class schedule, the “class book”, personal and public communication as well as an archive of all data, the school collected. The virtual “class book” is one of the main features, we focused on. Pupils can report themselves sick via a cell phone interface, then the teacher can use our app to check attendance in his class. He will get informed if absence has a conspicuous pattern. All internal communication of the school’s teachers and social workers can be done using our application. The virtual teacher’s lounge will present important notices and reminders for all teachers. A private communication channel can be used for one-to-one-communication.
Scheduling an appointment was never that easy: Having insight in the calendars of the colleagues even the complex fill-in-planning for sick teachers can be done by a simple touch. By far, this are not all fields we can improve with our solution.
Our aim is to reduce the amount of time and complexity for teachers in their everyday workflows. Especially because this one solution covers a big field of problems. The greatest effort of Teacher’s Helper is probable the automation of single tasks to help and support the person, who uses Teacher’s Helper. As a result of this, teachers could have more time to focus on special things like the progress of the pupils.
The first logical step would be to point out all key the key features of our software. As there are many tasks the software should accomplish, more in-depth reasearch is needed to point out concrete problems in the single tasks. After the first prototype is built an evaluation in a real class is mandatory. With the feedback the tool should be evaluated more times, until it gets to a final stadium.