hackforla
Design: Guest Account Confirmation
🧩 Overview
This issue is for tracking design work related to Related User Story #440. As a Guest, I want to confirm my Home Unite Us account, so that I can log in to Home Unite Us and begin the application (Intake Profile) and onboarding process.
🧠 Context / Background
Currently, Guests do not have a way to create an account for Home Unite Us. As a result, Guests cannot access Home Unite Us to create a profile, which is a required step to find housing on the platform.
This feature enables Guests to receive invitation emails from Coordinators and complete the account confirmation process to begin their application journey.
🎯 Problem Statement
Guests need a clear method to confirm their Home Unite Us accounts after being invited by Coordinators, without this it will prevent them from accessing the platform to begin the intake and application process for housing assistance.
👤 Target User(s)
Guests who have been invited to the Home Unite Us program by Coordinators and need to confirm their accounts to begin the application process for housing assistance.
🎯 Goals & Objectives
Goal: Create a streamlined account confirmation process that allows Guests to easily validate their accounts through email invitations and begin the intake process.
Business Objective: Enable Guest onboarding through secure account confirmation, reducing barriers to program entry and ensuring proper user authentication.
User Objective: Complete account confirmation quickly and securely, understand program expectations, and seamlessly transition to the application process.
- Expected outcomes: Guests can successfully confirm accounts and begin applications
- Ties into business goals of streamlined user onboarding and program accessibility
✅ Success Criteria (Design-Specific)
*Validates that the design work itself is complete and meets quality standards (completed by PM) *
- [ ] Addresses the core user problem
- [ ] Aligns with product vision and brand guidelines
- [ ] Meets accessibility standards (WCAG 2.1 AA)
- [ ] Can be handed off to Engineering with clear assets and specs
📋 Functional Requirements (if applicable)
Only include if there are specific technical or business constraints that affect the design solution
- Data fields that must be captured (for compliance/integration reasons)
- Required integrations with existing systems
- Specific user flows that cannot be changed due to technical constraints
🧩 Functional Constraints
These are non-negotiable parameters that affect design decisions - things the designer can't change but must accommodate in their design approach. * List any constraints or guidance from Product or Tech:
- Must integrate with existing password reset functionality from issue #442
- Mobile-first or responsive
- Requires user acknowledgment and certification before proceeding
🔁 Feedback Loops & Collaboration
*(completed by Design) *
- [ ] Design kickoff meeting scheduled
- [ ] Begin wireframes or discovery
- Review Cycles: [e.g., Weekly syncs, async feedback]
- Designer: Add screenshots of design and link to Figma page in comments
- [ ] Iteration 1 - Add to Figma with explanation/comments
- [ ] Iteration 2 - Add to Figma with explanation/comments
- [ ] Final iteration - Add to Figma with explanation/comments
📋 Deliverables
(Completed by Design) What specific design artifacts are expected?
- [ ] User flows
- [ ] Wireframes
- [ ] High-fidelity mockups
- [ ] Prototype (if needed)
- [ ] Design specifications for handoff
⚠️ Known Risks or Open Questions
*(completed by PM) identifies uncertainties, potential blockers, or areas needing clarification that could impact the design work or project success. Gives designers a heads-up about potential challenges or decisions that haven't been finalized yet, so they can plan accordingly and flag issues early."
- Are there uncertainties that may affect design direction?
- Anything Engineering or stakeholders should weigh in on early?
🔗 Related Issues
- User Story: [Link]
- Research findings: [Link if applicable]
- Technical constraints: [Link if applicable]
Action Items
- Assign and Prep
- [ ] Designer: Review User Story and self-assign
- [ ] Designer: Conduct the necessary research (if applicable), clarify any questions
- [ ] Designer: Work with PM and Design Lead to clarify any questions about the User Story
- [ ] Designer: Designer work with Engineer team Lead to assign the appropriate size & complexity
- [ ] Designer/Design Lead: determine if work should be split into multiple issues, if so, create issue(s) and link them in this issue (if applicable) or create as standalone.
- [ ] Designer/Design Lead: determine and provide "start and end date" for Product to update.
- [ ] Designer: Work with Design Lead to determine appropriate place/page to Draft Design in Figma
- Draft and Review:
- [ ] Designer: Draft Design
- [ ] Designer: Change Issue Status to "For Review/Feedback Needed"
- [ ] Designer: Add Label "Ready for: Design Peer Review"
- [ ] Design 1st Level/Peer Review: Review and compare against Acceptance Criteria, provide feedback in comment section below, tag assignee.
- [ ] Design 1st Level/Peer Reviewer: Change Issue Status to "Questions/Clarification" and add label "Ready for Dev Team"
- [ ] Designer (Assignee): Change Issue Status to "In Progress"
- [ ] Designer (Assignee): Review issue comment(s) and resolve accordingly
- [ ] Repeat above steps until all Acceptance Criteria are accounted and comments are resolved
- [ ] Design 1st Level/Peer Reviewer: Change Issue Status to "For Review/Feedback Needed" and add label "Ready for: Design Lead"
- [ ] 2nd final/Design Lead: Review and compare against Acceptance Criteria, provide feedback (if any) in comment section below, add label "Ready for Design Team Member"
- [ ] Repeat above steps until all Acceptance Criteria are accounted and comments are resolved
- Let Product know that the design is ready for review
- [ ] Designer: Change Issue Status to "For Review/Feedback Needed"
- [ ] Designer: Add Label "Ready for: Product....Persona"
- [ ] Designer: Tag the PM of the related User Story in a comment below and let them know that a draft is ready for review
- [ ] Product: Review Design Screenshots and provide feedback
- [ ] Repeat above steps until design is approved
🚀 Handoff Requirements
What needs to be completed before this moves to engineering?
- [ ] Designer and Product: Review with Engineering for questions
- [ ] Designer: Add link to Figma and Screenshots to a comment in the linked User Story
- [ ] Design review and approval completed
- [ ] Engineering handoff issue created
- [ ] All design assets uploaded and documented
📎 Resources & References
- Existing Research: [Link]
- Brand Guidelines / Design System: [Link]
- Previous or Related Designs: [Link]
