— PROJECT NAME
Oct '18 to Apr '19
einsOS was the 1st iteration (2nd iteration is Kneura) of an extremely agile project, done to create a digital platform that provides everything related to education.
einsOS comes bundled with multiple applications to teach using digital whiteboard, take attendance, give assessment, get curated content, get performance reports, grading etc.
CNX hardwares (Galileo) runs einsOS app as a digital whiteboard and einsOS also gives device performance and usage tracking for the said hardwares.
To comply with my non-disclosure agreement, I have omitted and obfuscated confidential information in this case study. All information in this case study is my own and does not necessarily reflect the views of Cybernetyx.
I was responsible for laying down the developer hand-off practices, design thinking exercises, information architectures, feature discovery, researching competitions & features , usability tests, and building the user interfaces.
einsOS was a huge collaborative effort and it would have been very difficult if not for Prasad (Associate Product Manager), Noella (Senior Designer – Visual Communications), and Tarun (AVP Design) helping me out.
Branding, website design, and product hardware design attributed to Noella and Tarun.
My biggest mistake was not being in touch with the actual product. The lack of collaboration and communication led to some incorrect behaviours and many loose-ends.
The global content navigation/hierarchy was fragile from the start and we were building over that weakness. Like the einsOS apps were on the top level and inside them, you have these option to select the class (+subjects). Having all these einsOS apps as buckets in classes (+subjects) would have resulted in better navigations and we achieved this in the next iteration of einsOS, that is Kneura.
Initially, there was no final vision of what we wanted to achieve, and every app was designed individually, but later they came together to make einsOS. Because of this agile approach there were brand inconsistencies in between the einsOS application, which led to design debts. A design system would have solved it.
Through Galileo ONE (einsClass), teachers can teach geometry, painting, or write seamlessly. They can, with einsOS, create lesson plans, manage attendance and assess assignments.
einsOS come with with grading and reporting features, one can also track the utilization of installed devices in classes and monitor the progress made.
With Galileo ONE (einsClass), students can collaborate on a panel in real-time, participate in group activities and make presentations. Students can connect their personal learning devices and contribute to class discussions from their seats. They can also attend classes and give tests remotely when they’re sick.
Side Note: Diverging (then converging) to uncharted territories can be stressful for some.
The DT exercises were not only done for generating insights on what we had to do, but also to give us all a reference to work with.
We referred to “Harish” the teacher and “Rohit” the student personas during everyday discussions, which bought clarity regarding the stories we were trying to solve, and helped us all (Dev+Design+PM) empathize with the users and do the due diligence required to make our personas feel comfortable using our product.
Onboarding or the overall dashboard concept works fine for a closed platform but the number of onboarding steps, although with skip option, are too long and the actual functioning or stories are not visible until you open some app.
I revisited this issue in next iteration, in Kneura which is free for signup, we reduced the onboarding process to a single step and all the imports and creation part were packaged in their own modules. This made the users invest in the app first and when required, they had the option to create content/people.
einsClass exist at the center of the einsOS ecosystem, it runs on Galileo hardware and is used by teachers to create lesson.
It was important for the potential clients (Indian Government) to know how their ordered devices were being used by teachers and the whole institute alike.
The questions were: how the devices were being used? how much were the the teachers using the whiteboard solution (einsClass) we give with the CNX hardware? What other apps were they using? were they even using the hardware? if yes then who all were those that were using it effectively and by how much?
I was given a requirement doc, the proposal from the Indian government- EOI Doc and these were the insights that I received by consuming it:
Following is the Admin's Analytics App, it has 2 views, one is Device view that was the original 1st iteration of this app, and the 2nd view is classroom view, that was later added as other einsOS apps came into the picture.
einsLibrary was a content bucket for educators, providing them with videos, pictures or text to prepare their own lessons more effectively.
It was work in progress when I came. When I joined I revamped the whole app other than the core navigation (this is where that class+subject inside each app roots from)