The UXW/Content team was introduced to the Sean’s Legacy’s TechFleet project in Phase 2. Their handoff document reviews the work they completed and recommendations for the Phase 3 Content team.

Style guide

Thrive Out Loud Content Style Guide (NEW)

We expanded on and added many topics in the style guide throughout this phase.

Content team Figjam

The process we used

• Select Priority property
• Status: To do | Topic header added to SG with “TBD - work in progress” in red | Ways topics were identified: Phase 2 notes written directly into SG, naturally as needs and questions arose during Phase 3, and through the audit & comparative analysis completed mid-phase | | Topic assigned to a team member | - Update Assign property
• Select Sprint property
• Select Deadline property
• Status: In progress | | Assignments were mostly voluntary based on interest and team member's ability to meet deadlines | | Team member completes editing or adding topic | - Status: Done | Team member posts on #seans-legacy-project-content Slack channel that they have completed their section and asks others to review | Team members researched by reading other company SGs and incorporated research into editing/adding the assigned topic to our SG | | Other team members review | | Other team members make comments on what could be revised | | | Original writer resolves comments | | ”TBD - work in progress” removed from topic header | When at least 2 team members agree on a comment (one person suggests a revision and a second person agrees), changes are implemented and the comment is resolved. The second person can be the original writer. |

Sprints 1-2

At first, the leads considered the expansion of the style guide a low-priority task that could be worked on throughout the phase. We saw many topics Phase 2 had started and noted for Phase 3 to finish. While we worked on those topics, we prioritized tasks supporting other teams (read on to Cross-functional Collaborations for details).

List of things we edited/added during Sprint 1 and 2:

• Common use cases
• Accessibility

The pivot

By the end of Sprint 2, we wanted to have more ownership of our deliverables versus primarily playing a support role to other teams with their deliverables. We were feeling underworked and ready to take on more. We brainstormed together using Figjam to come up with ideas on what we’d like to work on.

Content team Figjam

The top two deliverables we decided to focus on were the style guide and the mentor onboarding kit and the resource handbook. Based on the MPH intern's limited availability and projected timeline for completion, we realized focusing primarily on the style guide would allow us to finish it by the end of the Phase. Not completing the style guide would have greater implications in the future (ex. having to re-audit existing designs whenever new material is added to the style guide).

Sprints 3-4

Style Guide Audit & Comparative Analysis

Until now we had relied on Phase 2 Content team’s directives to identify what topics we needed to add to the style guide. With a renewed focus, we decided to complete an audit of our style guide and create a comparative analysis against 4 other style guides.