In this case study
Ecosystem mapping
User stories
Vision & plan
Value offerings
MVP priorities
Reflections
Ecosystem mapping
We workshopped this along with the founders, to get a clearer understanding and identification of any other actions being missed that could affect in fulfilling the needs of the actors.
Click on the image for a full screen view.
User-stakeholder stories
to begin flows for primary tasks of main user types
Vision for Dribe
Automates
various administrative tasks, increases compliance, and
makes it possible to track the performance of their students.
Recommends
routes and driving exercises that meet the competence
targets, thus increasing the student's educational benefit.
Optimizes
the workflow by tailoring the driving routes for efficient
logistics, filling the calendar, and minimizing downtime.
Workshop analysing a primary competitor and understanding context of use for it.
How does the plan work?
Value offerings
Tools & Platforms that enable these outcomes.
MVP Information Architecture
Academic Leader's pain points to focus on as priority for MVP
After a Business analysis, the founders recognised that the Academic leader would pay for the value offered. As the Biggest pain point is the reporting of documents on time. So Dribe decided, we focus on establishing key Academic Leader offerings for the MVP validation stage.
Keep track of a large number of teachers' and students'
› Evaluations overview
› Progress tracking
› Automate analogue onboarding tasks
› Reporting successfully
Next step: Flow that displays the API integrations, rules around it and outcome of the functions & prototyping to test.
Reflections
Terminologies are crucial
↳ Language to understand and be on the same page is a crucial marker to keep track of, to avoid going in circles. A huge part in progress towards the goal.
Downsizing when time
↳ Though we mapped out the end-to-end journey, the fact that checking it against the market fit is crucial in business terms. So, to be aware of the right parts implement for initial launches for validation must be agreed upon by all parties.
Involving key players early-on
↳ As most of Dribe's solution was based on automation and tech, involving tech lead would've been a sound decision. Saving us time and having an understanding of essential possibilities.