Team Deliverables

Please list the major accomplishments/updates that your team accomplished this phase.

Team	Major Accomplishments	Recommendations	Important Links
Product	- Completed user stories, features list and accepted criteria for both the Educator and Student MVPs

Assisted UXR with usability testing
Assisted Design Teams A and B to ensure the completion of lo-fi screens, games and levels.
Designed 5 different user personas for student and educator side
Completed 4 journey maps for both the Educator and Student side to show the effective customer journey throughout the App life cycle. | - Make sure to assess teams skills and experiences upfront to best task and assign cross-functionality.
Establish cross-functional relationships as early as possible.
Keep leadership during work-sessions fluid to experience to create an open learning space.
Teach concepts used in phase 02(mindmap, journey map;if needed) in phase 03, to help new peoples create a cohesive team voice. | PRD Figjam Board | | UXR | - Tested key functions with six students, showing success in onboarding and gameplay exploration, with intuitive design elements
Tested with five educators on tasks like dashboard use and student tracking, highlighting app simplicity and areas for improvement
Refined the student persona to reflect real user experiences
Identified potential program partners for app content (Energia SOI, GraphoGame, Dynseo, Nessy)
Researched local device trends to inform future app development
Created user testing guides with approachable language for students and educators, collaborating with UX teams for refinement | - Conduct further usability testing of educator side of app with DFN trainers if possible (consider unmoderated usability testing if scheduling is difficult)
Use terms like “character” instead of “avatar” for student side of app
Make game tutorials interactive and step-by-step rather than a video
Simplify reset password steps, with options for parental management or alternatives like touch/face ID
Add multi-invite and class code options for faster onboarding
Add visuals and clickable profiles for better student progress
Ensure smartphone compatibility for regions with limited internet for both students and educators
Refine student and educator personas based on usability test findings

| Main deliverables Findings from Usability Testing

Internet Access & Device Usage in Nigeria

Student persona Classroom teacher persona Trainer persona

Potential partner research

Other artifacts Student usability test guide Educator usability test guide

Student prototype used for testing Educator prototype used for testing | | Design A | - Lo-Fi concept prototype for UXR testing based off assumptions & dummy data

Redefined user flow -Created LoFi UI Kit | -Review UXR report and refine wireframes based of data and findings -Review UXW feedback -Align on behaviors & patterns used by each team mate to create a similar experience across the app -redefine the IA based on research & conversations with Development teams in phase 3
Work with UXD B, PS, & Mr.Ben to create Style Guide for both apps
Based on Style Guide create Design System | LoFi -Designs, Userflows, UI, IA, File history UXD-A working file

UXR Testing file | | Design B | - Completed seven different lo-fi scenario based prototypes for usability testing.

Handed off two combined onboarding+game prototypes with happy path and error path to UXR for usability testing.
Added states/levels in puzzle selection screen.
Refined lo-fi screens based on UXR + UXW feedback. | - Implement recommendations and insights discovered during usability testing.
Continue building UI Kit to start high fidelity designs.
Sync up UXD-A and UXD-B dashboards.
Improve low-fidelity wireframes based on usability testing insights
Decide the error feedback screen vs short error feedback based on usability testing insights - more details in Phase2 Figma file
Plan to increase puzzle complexity by providing different levels.
Create a combined Design System for UXD A and B teams | Can be found here | | UXW | - Provided feedback on the microcopy in the Figma files refined by UXD team B including onboarding screens, dashboard, game screens
Completed a comprehensive competitor and comparator analysis to evaluate effective UX writing strategies and feedback mechanisms for literacy apps aimed at children with dyslexia
Created instructions, captioning and feedback for the cognitive game puzzle screens from UXD team B
Provided Feedback on copy for UXD A prototype for UXR usability testing (for student profile, sign up, and dashboard) | - Review content style guide
Review UXW competitor analysis
Continue working with UXD to review and give feedback on the designs they create (according to the content style guide)

**Our work was heavily contingent on the UXD A/B teams. Our progress was closely tied to the screens they designed and the opportunities we had to provide feedback on the copy. | Content Style Guide

Competitor & Comparator Analysis

UXD B Cognitive Game Puzzle Screens

UXD Prototype with Copy Annotations and Feedback (student profile, sign up, and dashboard) | | Solution Architecture | Settled for AWS as it elastic and scalable, responsive to changing seasonal and daily demand, and reliable to learners.The following AWS services fits the technical requirements:

Architecture requirements: Using AWS Amplify for front-end Hosting.

Data Processing: Resolved on using Amazon Polly for Text-to-Speech like an audio playback

Amazon Transcribe for real-time Speech-to-Text recognition.

For user management and secure log in, Amazon Cognito.

Amazon S3 for storing learning materials, audio, and visual aids. Then AWS DynamoDB as a database for storing user progress. | Collaboration between UX teams, Solution Architect and Developers.

Using Amazon Key Management Service (KMS) for Data Encryption, Amazon QuickSight for usage data and progress tracking, and Amazon CloudWatch for app performance.

Design a high-level architecture diagram of how the app should look like. | | | | | | |

Please see the following link for an example. NOTE: It does not have to be as elaborative but should give the next team a clear idea of work accomplished, links to key information and recommendations for the next phase.