भारतीय शिक्षा में बदलाव
Welcome to the future of education!
At Embibe, we have just one mission – to truly personalise education. Because every child deserves it. This has led us to embark on this noblest of journeys to deliver life and learning outcomes for every student! Rooted in consumer behavior, we are leveraging AI to deliver personalised achievement journeys for every student.
Embibe has traversed a long journey from a data-centric product to an AI platform. On this journey, we have realised that the most powerful teams are: 1. Vision Led in understanding student context and obsessed with success; 2. Self-Organising in defining their own agenda; 3. Intellectually Fierce and Globally Conscious in their choices, and 4. Consistently Excellent in their execution.
After exploring a deeply functional organisational structure in engineering, we are now evolving towards a problem-solving team structure that manifests at the platform and backend level as an agile team supporting a unified front-end and augmented by a strong Architect + Principal Engineer + Advisory Group for technical mentoring. This document outlines the problem statement and other aspects of the Tomorrowland team that will be at the cutting edge of UX.
We want to build a team that will ensure an awesome user experience each time a learner engages with any facet of the Embibe platform.
We are inspired by leading technology giants like Apple, which give users highly intuitive and highly usable interfaces that drive immense stickiness to the platform. It is the endeavour of this function to ensure a highly intuitive user experience to keep users engaged with the platform.
In a nutshell, this function has to ensure that the user has a great experience each time she/he engages with Embibe.
Some specific objectives are:
This team will architect the user experience; therefore, it is responsible for delivering:
In addition, the team should strive to reduce production cost and drive potential revenue.
METRIC NAME | UNIT | FREQUENCY |
---|---|---|
Count of First Time Right (FTR) Designs | Ratio of FTR/Non FTR Designs | Weekly |
Number of Product Media Built | Count Achieved/Target Count | Weekly |
Count of High Traffic Driving Marketing Banners Designed | Ratio of High Traffic Banners Designed | Weekly |
Number of Functional Bugs Found on Production | Ratio of Bugs per Feature or Media Units | Weekly |
Number of Instances of Non-Conformity on the Scaled-up Workstreams from PoC Guidelines | Ratio (%) of Conformity to Guidelines | Weekly |
Timely Completion of POC | Percentage Adherence to Timelines | Weekly |
Number of Innovations/POCs per Quarter | Count of Innovations Delivered vs. Target per Quarter | Monthly |
Number of Incremental Innovation per Quarter | Count of Incremental Innovations Delivered vs. Target per Quarter | Quarterly |
Production of Media Elements Given by Business Team on Time | Delivered/Target (Percentage) | Weekly |
Production of Media Elements Given by Product/CEO on Time | Delivered/Target (Percentage) | Weekly |
Completion of all Banners (Practice/Learn/Test) as per Exam Launch Schedule of the Month | Delivered/Target (Percentage) | Weekly |
FTR (Not More than One Iteration on Any Product Media Production) | Delivered/Target (Percentage) | Weekly |
We believe in building an organisation at the intersection of domain modelling and problem intuition. While the L1 teams give us the flexibility to have a multi-faceted view of the problem and cluster similar problems together, the L2 structure ensures independent and focused problem-solving. The following L2 teams have been suggested for the L1 problem stated above:
To Join the Tribe, send us an email on [email protected]