Get more stuff like this
in your inbox
Subscribe to Ruvna's mailing list to get updates in your email inbox.
With all of the excitement surrounding the “amazing possibilities” of technology in schools, there is something important often left out of the conversation: are these tools intuitive for schools to use?
Ask any teacher, they’ll have no shortage of frustration regarding software mandated by their school. Whether it’s student portals, email systems, grading software, you name it, they complain about it. This software apathy is not limited to teachers; I recall administrators frequently unhappy with almost every part of their school’s software tools.
This theme drives us to make the Ruvna experience incredibly intuitive, especially considering the alternative, pen and paper.
Let’s examine the current experience for teachers during fire-drills: using a clipboard – call out a name, see if the student is present, check the student off. Rinse and repeat for all of the students in the class. Write down the names of students that are in the class but not on the list. Done. Now consider what happens at the end of the check-in process with a clipboard: teachers have to communicate with administration to figure out where their missing kids are. Moreover, teachers frequently will end up alerting administrators of missing students who were simply absent from school, rather than actually missing. This process requires much more work than checking off the students present, and it can be a time consuming and frustrating process that doesn’t end up improving emergency response.
Clearly this is a process ripe for improvement. However, helping teachers during emergencies doesn’t mean schools should abandon all of their protocols. Very often, improving systems is a better solution than “starting over”. In fact, some of the most widely used EdTech software, such as Moodle, Socrative, and Remind, do exactly that! They are so successful because they incorporated previous best practices, rather than abandoning them and starting from scratch.
Now, consider a teacher’s experience of using Ruvna: Call out a name, see if the student is present, tap to check the student in. Rinse and repeat for all students on the list. Pick up an extra student? Simple, add them to your list. That sounds like using a clipboard doesn’t it? It should, except Ruvna is taking care of every other time consuming, outdated, and dangerous step in accounting for students. Ruvna allows teachers to immediately get back to securing the safety of their students.
Ruvna isn’t a complete replacement for emergency protocols, and it doesn’t add steps to existing protocols. Instead, Ruvna is an intuitive tool that makes schools’ existing emergency protocol work better.
Jack Ruppel (@jack_ruppel) is Ruvna’s CTO. At only 20 years old, Jack has been Ruvna’s lead developer for 3 years. In addition to being a brilliant and gifted technology mind, Jack is an expert on intuitive user experience engineering.