02 / Who we designed for
People behind every class
Built only from the current flow the team shared with us.
Kept anonymous, with respect. Samanvay is an internal tool, so these personas carry no names, faces or places.
Persona A
Scheduler
Regional scheduling team
In the current flow
Gets a request, then checks with Ishangas manually
Keeps a Google sheet: a simple day-wise calendar for each request and Ishanga
Confirms to the Ishanga, and to the centre / requester
Then POCs, stay, etc.
What made it overwhelming
Manual checking for every request
A day-wise sheet kept by hand
Two separate confirmations, to the Ishanga and to the centre
Persona B
Centre / requester
The centre that needs the class
In the current flow
Sends the request
Receives the confirmation
POCs, stay, etc. follow the confirmation
What made it overwhelming
Depends on manual checking at the scheduling end
Affected when a confirmed Ishanga has to cancel
Persona CIshanga/VolunteerOffers themselves for classes
In the current flow
Is checked with manually for each request
Receives the confirmation
Receives POCs, stay, etc.
What made it overwhelming
No platform to inform that they are not available
So requests came for dates they already had plans
Then either the class was cancelled, or their own plans