• Important links/files
• Subject Matter help
• What we set out to do
• What we did
• Reflections and Recommendations
• What’s next

| Deliverables | Pre-Kick Off 9/5/25 -9/23/25 | Sprint 1 9/29/25 -10/10/25 | Sprint 2 10/13/25 - 10/24/25 | Sprint 3 10/27/25- 11/7/25 | Sprint 4 11/10/25 -11/21/25 | Recommendations for Phase 2 | | --- | --- | --- | --- | --- | --- | --- | | Overview | This period was spent on training and workshops in preparation for the work to follow. | *This sprint was spent on team formation | * 10/17/25 Client mtg to confirm audience (student age-ranges)

• Audience changed and team regrouping to discuss strategy | *Team reconsidering how to increase listenership and look at potential collaboration possibilities for BLS | *Focus was on supporting team to gather insights that could be taken forward into the next phase | *Follow suggestions of the PS and UXR team for phase 2 | | Team Ice breakers | Joined workshop to get to know team | - | - | - | - | - | | Sprint Plan | - | *Joined the meeting to gain understanding about what the team wanted to work on to bring value to the project. | *Joined the sprint plan meeting with a bit more insight on the client needs and the team’s desire to understand the audience. | *Part of the planning to continue research and discovery. The plan changed and the team chose to pivot after the stakeholder interview with the client and a more clear idea of expanding the audience and looking at collaborative opportunities for the client. | *We planned to make use of the remaining time we had to wrap phase one and conclude with gathering and summarising the insights we had. | *See as per Product Strategy and User Experience Research team | | Team RACI Charts | Joined workshop to self-organise | *Added in RACI hats for sprint in the Sprint planning. | *Added in RACI hats for sprint in the Sprint planning. | *Added in RACI hats for sprint in the Sprint planning. | *Added in RACI hats for sprint in the Sprint planning. | - | | KPI’s | | | | | | Part of the Vision boards | | Client Intake | Joined meeting/caught up to get insight to the client needs for project | - | - | - | - | - | | Team Process Definition | - | *Joined the training on 10/2/2025 | *Use the team team process map as reference | *The process map was no longer a point of reference due to the pivot as we realised we would not be designing for the client. | | | | Working Agreements | - | *Created for Sprint 1 | *Created for Sprint 2 after team retro was completed async by team. The team had challenges and solutions to try out for the next sprint. | *Created for Sprint 3 after team retro was discussed after a demo recording. This really helped with ownership and open discussion for team input. | NA | - | | Audience Personas | - | *Supported UXR after discussion was for the audience focus to be on students and policy makers | *Supported UXR after discussion shifted to different subsections of students (elementary, middle school and high school) alongside policy makers | *Pivoted as a team due to conversation with client with decision to expand audiences to larger New Orleans community (students, teachers and school administrators, policy makers, parents, possible collaborators eg organisations and individuals) | *Supported the team in developing audience personas for Mayor’s office and the school administration. | *Gain clarity on the most important personas (possibly the 2 main ones from PS) and focus on them | | Empathy Maps | - | *Gave input based on various audiences (students and policy makers) | *Focused on input for Middle Schoolers and policy makers | * Stepped back from deliverable to allow time to gain insights based on pivot for the greater New Orleans community and insight to received from possible surveys and interviews | *Worked on the empathy maps for various audiences as a team | *Once decided on personas, work with their empathy maps especially | | Current Customer Experience | - | *Completed personas and empathy maps. | *Updated personas and empathy maps. *Received the client data from their Pass The Mic Fellowship (2024-2025). | *Decided to move deliverable to end of the phase and schedule workshop in line with that as result of pivot. | *Participated in the workshop | * Look at Customer Experience and work on for phase 2. | | Generative Research Insights | - | *Joined the research test plan workshop | *Worked on researching the competitors and zoomed in on local ones offering similar programs with a potential media output. *Did market research to understand the segments and potential market size. | *Pivoted and focused on looking at research around organisations and individuals for possible collaboration. | *Focused on getting insights from organisations and companies with the use of interviews and surveys | *Utilise the information from the suggestions shared in summaries to Alex | | Evaluative Research Insights | - | - | *Receiving and reading the client data from Pass the Mic Fellowship (2024-1015) | *Sharing surveys to parents and students to gain insights on BLS. *Reaching out to organisations and individuals for interviews to understand possibilities of future collaborations. | *Focused on getting insights from organisations and companies with the use of interviews and surveys | *Utilise the information from the suggestions shared in summaries to Alex | | Product Positioning | - | - | - | *Doing research since pivot to understand the audience and therefore develop the product’s position in relation to others in the market. *Team did research on similar organisations and possible collaborators. | - | - | | Unique Value Proposition | - | - | *The team looked at competitors in the community along with a competitor analysis and SWOT analysis. | *Doing research to understand audience before we can be able to discover what client bring in relation to their competitors. | In research, discovered how BLS has different offering from other organisations in who makes the content and who it is intended for | Continue research on this considering “by youth for adults” | | Problem Statements | - | - | - | *PS team created problem statements after pivot in line with the research the team decided to focus on and tried to merge some of the sub-audiences | - | - | | Discovery Research Backlog | - | * Joined the team research prioritisation and vision boards creation based on the 2 audiences we focused on. | *Participated in the prioritisation and vision boards as the team expanded the audiences particularly for the student groups. | *Continued on the research, but due to the pivot, gave the UXR team function more freedom to focus on certain aspects of the research based on the new direction. | Put together summaries for Alex based on the information we felt would be valuable to the next phase. | Continue with research based on the direction team wants to take when it comes to the boards. | | Customer Experience Strategy | Had no workshop set up for this. | - | - | *Decided to shift to Sprint 4 | - | Research customer experience and utilise to create strategy | | MMP Vision Board | | *Joined in creating vision boards for each audience that was mentioned in the client intake. | *Joined in creating the vision boards for the students and local policy makers, along with prioritising. | *Pivoted and allowed the PS and UXR team to make decisions based on the vision boards and what needs to be prioritised and focused on. | *PS team did not change vision boards | *Utilise vision boards based on the audiences the team decides to focus on in next phase | | MVP Vision Boards | | * Joined meeting to look at various problems for different audiences and prioritised as a team | * Joined meeting to look at various problems for different audiences and prioritised as a team * Looked at student sub-sections and policy makers | *Pivoted and allowed the PS and UXR team to make decisions based on the vision boards and what needs to be prioritised and focused on. | *PS team did not change vision boards | *Utilise vision boards based on the audiences the team decides to focus on in next phase. | | MMP Release Scope | | *No scope created as we tried to pin down the audiences we’d focus on. | *No scope created as we tried to pin down the audiences we’d focus on. | *No scope created as we tried to pin down the audiences we’d focus on. | *PS team did not change release scope | *Utilise release on the audiences the team decides to focus on in next phase | | MVP Release Scope | | *No scope created as we tried to pin down the audiences we’d focus on. | *No scope created as we tried to pin down the audiences we’d focus on. | *No scope created as we tried to pin down the audiences we’d focus on. | *PS team did not change release scope | *Utilise release scope based on the audiences the team decides to focus on in next phase | | Release Roadmap | | *No roadmap created as we did not have the scope to do so. | *No roadmap created as we did not have the scope to do so. | *No roadmap created as we did not have the scope to do so. | - | - | | Epic and Feature Definition | - | *No epic and feature defined. | *No epic and feature defined. | *No epic and feature defined. | *No epic and feature defined. | - | | User Interview | - | - | - | * Joined meeting with Alex
• User Interview 10/27/25
• Team to regroup to brainstorm on how to move ahead during Team Sync meeting | - | - |