-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Research for Coordinator User Stories for Flow and Impact Across Stages 2, 3, and 4 #786
Comments
@gabcdominic you might find this old closed issue helpful for your research: #267 |
@gabcdominic also for matching section Jasina has written an epic and several stories which should be helpful! #618 |
9/27/24: Updated the spreadsheet (Feature tab and Roadmap tab). Next steps: I’ll coordinate with @lasryariel to confirm the User Story GitHub, as some stories appear interconnected. Additionally, I’ll request his input for Sections 3 and 4. |
10/3/24: Reviewed and refined key user stories and feature statements for the MVP / post-MVP features (link here). Focused on enhancing clarity, alignment to Handbook, and measurable outcomes across features. The goal was to empower users, provide data-driven insights, and create actionable features that save Coordinators time and support program improvements over time.
|
10/24/24 Identifying best practices for designing, customizing, and optimizing real-time notifications. Displaying new item counts can encourage users to check sections more often and help them prioritize tasks based on what’s updated. It keeps important actions visible, especially in onboarding or relationship management, and makes the experience feel more personalized. On the downside, too many notifications could overwhelm users, clutter the interface, and lead to notification fatigue, making updates less effective over time. To make it work better, we can prioritize the most important items, let users customize what they want to see, and keep the design clean and straightforward to avoid overload. |
Overview
This issue is for tracking design work related to [User Story #635 ]. [COORDINATOR can view submitted applications for Hosts & guests].
As the new PM, research the coordinator role and user stories across Stages 2, 3, and 4. Review Google Drive and Figma to identify workflows and user stories and note any areas for improvement. Ensure Stage 2 captures all necessary data for accurate matching and integrates seamlessly with Stage 3 to support efficient guest/host tracking and onboarding.
Action Items
[ ] Think of potential User Stories for Coordinator role in Stages 2, 3, and 4. Think about functionality, features, and what's needed for MVP
Notes for this exercise
Stage 2: Application and Onboarding Process
As a coordinator, I need to review and verify host and guest applications, schedule interviews and training sessions, and ensure profile completion to facilitate the onboarding and matching processes. The system provides tools for application tracking, document verification, interview and training scheduling, profile management, and automated alerts for missing or incomplete tasks.
Stage 3: Matchmaking / Relationship Creation Process
As a coordinator, I need an automated tool to generate host matches based on guest preferences, review and approve host profiles, confirm guest-selected matches, and allow hosts to review guest profiles for informed decision-making before finalizing the matches.
Stage 4: Relationship Management / Monitoring Process
As a coordinator, I need to regularly check in with hosts and guests, manage and document issue reporting and contract updates, handle emergency requests, and oversee the end-of-stay process to ensure a smooth partnership so that both parties feel supported, issues are promptly resolved, and compliant with agreed terms.
Resources/Instructions
The text was updated successfully, but these errors were encountered: