Watch this video to get instructions on the hand-off, credit to @Tori Gan @EJ @Rachel Newcomb for the Hand-off template

https://www.loom.com/share/079c503d9c054ef3916b1e5bd0ce9287

Phase by Phase

(as briefly told by the teams)

Major Accomplishments & Updates as told by teams per phase

Completed:

• Secondary research (Competitive analysis, SWOT analysis, best practices in language-learning technology, organizations involved with endangered language revitalization)
• Product Requirements Document
• MVP Proposal
• Value Acquisition Canvas | | UX Writing | | During this phase, we developed and elevated existing content by analyzing user feedback from usability testing insights using Affinity Mapping. Along with the iterations of existing content, came further development of the brand’s identity, the content style guide, more concise content, and a streamlined onboarding and introduction experience. We built the foundation of the brands identity by creating a Brand Voice chart that identifies four core principles to help the content throughout the app remain on brand. We also conducted gamification research from a content perspective, with the plan to synthesize with the Research team, but as we had to pivot, this research will now be used in a later phase. We also rethought Zunzún, the “mascot,” as less of a mascot and more of a Guide or companion/narrator, as this feels more on brand, and reminds the user that they are not alone. We also created a document to keep alignment with the design team close and open to communication. Our next steps are to: continue developing the brand voice and identity, continue to iterate as closely as possible, conduct competitive analysis on homepage content, and any other content/design work we would need to contribute to for this phases goals. | - Conducted competitive analysis on language-learning apps to gather insight on common UXW patterns that make for a compelling learning experience
• Created content style guide to establish content design guidelines
• Developed user stories and user journey maps as well as acceptance criteria to empathize with user needs and goals and inform UXW decisions respectively
• Assisted UXR team to brainstorm research questions for evaluating brand voice and tone and generating insight on content style decisions to be made
• Conducted literature review of Taíno history and language from Casa Areyto to inform introduction and first lesson content
• Collaborate with UXD and Priscilla to iterate on content for introduction, first lesson, and onboarding flows | User research to help define target user and problem statement

Completed:

• Research plan
• Survey
• User interviews
• Synthesis of user research (survey and interviews)
• Personas
• [tbd - ideation/design ideas/use cases]

(See UX team page for links to all important work files and deliverables) | | UX Research | | During this phase, we bolstered our participant recruitment efforts by creating a contact list from prior phases as well as outreach scripts and infographics for social media distribution, primarily targeting people of Taíno descent for our usability tests. We also produced a white paper on Gamification based on prior industry research, developed a usability testing guide, and conducted a series of usability tests to gauge the success of our introductory flow design. We organized our findings using an affinity map and prioritization matrix, which we further analyzed in our insights and recommendations for the other UX teams. From there, we brainstormed home screen ideas but soon realized we needed to develop a better understanding of our scope for this project before undergoing that process, and thus pivoted to draft a survey for Phase 3 that focused on understanding user content preferences. | I conducted a language-learning app to gather insights on all aspects of the app, language, design, content, and legion, and identified commonalities and differentiators between those apps. We conducted an Unmoderated concept test to learn the Taíno community's perception of Gamification and DuoLingo to help the team identify which features to focus on. Brainstormed ideas to create a community and a bigger sample size. Grew our research sample size. Provided feedback and consulted XFN teams based on the insights derived from our concept test. Collaborated and met with Ra Ruíz Lastly, we conducted a Moderated concept test on the "Learn Taíno" flow. | Define target users and problem statement

• Stakeholder interviews (Yazmín at Endangered Languages Project)
• Project outreach to potential partners | | UX Design | | In Phase 2 we designed a fully-interactive Figma prototype of the Learn Taíno MVP that incorporates the results of usability testing. It includes a shortened, but still content-rich, onboarding experience, a new homepage with lesson menus, and a new review tab with a feature to review learned vocabulary.

We began the phase with a Figma prototype of a content-rich onboarding experience that wasn’t fully-interactive. It introduced Zunzún, taught a lesson on the history of the Taíno people and the reconstruction of their language, taught a language lesson on Taíno greetings, and handled account creation. We started by making the existing designs fully-interactive and incorporating client feedback in preparation for usability testing. Based on the tests conducted by the UX Research team, we decided to refocus the app around a homepage, shorten the onboarding experience, and designed the MVP prototype outlined above. | - Competitive Analysis

• User Stories and User Flows (for the first 3 experiences: intro experience, first lesson, onboarding)
• Wireframes: low, mid, high fidelity
• Prototype: mid / high fidelity | | | Development /Solution Architect | | | Created the file structure that will serve as the framework to organize the files and code for the server-side and the client-side of app. The server-side is based on the MVC (Model, View, Controller) model and software design pattern. The structure organizes the independent elements and their relationships into a seamless and collaborative architecture. The app.tsx is the entry point of the program on the server-side and will run as a daemon. The created folders on the server-side are models, views, controllers, routes, logic, middleware, public; containing subfolders for fonts, images, and icons, and config[uration]. The file structure and architecture provides an organizational basis for any future work and possible additional code. Within the view folder; provided code that can generate server-side render of UI elements. Provide two options to authenticate the user: Firebase and React-Native option. Created two options to manage the database with MongoDB using mongoose library and mongodb library. The two options can be used separately or work in combination of each other. Created the basic components generic to most mobile app and those individual components contains the basic elements and code necessary to for the basic UI and functionality. The components folder contains a file with code to form the basic theme and styling that will be basis of the UI of the app; and text follows that same pattern. The Error Boundary file and code provides for graceful failure of the code in case of error in production and the code should be the basis of any future work to account for any other issues. The code should serve provide generic error management for most components in the app, but syntax for all the code has a basic starting point for error management unique to that block of code. The typescript compiler options provides configuration for the current code and any future work. Included in the code is a short-list of additional options and descriptions. Provided comprehensive configuration to enforce code syntax in the eslintrc file and some enforcement in the prettier | | | Project Management | | | | |

Team Deliverables

To avoid duplicating work efforts, and to encourage greater communication and collaboration, look over each teams’ domains of the project.

The underlined deliverables are shared with more than team.

Common Team Deliverables | Presentations Timeline status Meeting recaps Project sprint plans

————— Google Account and Calendar creation and maintenance | Roadmaps User journey maps ****Development annotations Flow charts Sprint plans ****Backlog upkeep Competitive analysis Product-market fit plans MVP and MMP scope Product requirements doc

• User stories
• Acceptance criteria
• BDD scenarios
• Annotations | Content outline Copywriting docs Content inventory Information architecture ****Brand identity Editorial style guide | User personas User journey maps Storyboards Information architecture Interaction design Affinity diagrams Research plans Presented research results Surveys Card sorts Interview questions Empathy maps | User personas Information architecture Interaction design User journey maps Flow charts and customer experience diagrams High fidelity designs Low fidelity designs / wireframes Storyboards | Code Github merges Developer documentation API libraries Code reviews Architecture Diagrams | |

TLA-3 Links | Presentations Timeline Status Meeting recaps

————— Google Account Google Calendar

| Product Roadmap MVP (Lesson One) Flow Chart High Level Screen-by-Screen Flow UXR-2 New User Flow Doc Backlog Upkeep Competitive Analysis Phase MVP MMP Scope Product Requirements Doc

| | | | |

Hand-off files and important information

Subject Matter Resources

TLA Previous Phase Handover Documentation

Related & Future Work

Models & Inspiration 🔥

Synthesized / summarized documentation 💧