Epic: Audit Ticket: Use of Personal Names

[jknipes]

Status

Update each sprint until completed	Date	Status	Launch Date (see above)	Notes
10/17/24	not-started	on-track	low priority

Issue Description

• Personal names are often used on Platform Website to direct users to someone working in a position or team. As these roles change often, we may need to replace the names with the role or position, or team name, or Slack channel.
• There will also be cases where it is important to have the most current contact name for a particular role. These cases should be verified by a SME.

---

Tasks

• [ ] Conduct audit of PW for personal names
• [ ] Create list of pages with names
• [ ] Create separate edit ticket to replace names with title/position/role/team/channel

Acceptance Criteria

• [ ] All tasks are completed

  How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[jknipes]

Hey team! Please add your planning poker estimate with Zenhub @BSmolensky @CherylEvans @laucon @taylojill

[BSmolensky]

Upon Further Review: this ticket has been recategorized as an EPIC and moved to Future initiatives Column.

[BSmolensky]

Work on this epic should include:

• [ ] Dividing the PW up into small, manageable sections
• [ ] Then Assigning each PCT member a select number of pages within that section of the PW to review.
• [ ] Spreadsheet should be created to track results
• [ ] New Tickets Created to fix pages that need fixing.
• [ ] Repeat process until all 550+ pages on the PW have been reviewed and fixed

[laucon]

Writing a note here: Contact Us document

[BSmolensky]

NOTE: This Epic is labeled "Low Priority" because if we are going to review every page on the PW, we should probably review them for EVERYTHING. This Epic will likely become part of a much larger epic wherein we perform a full content audit of every page on the PW. Such an audit will likely involve several other teams. As we are finding out with the ESI audit (a very small corner of the PW), some pages will need archiving as they are no longer in active use. That will require working with SMEs and, likely, entire teams. A full PW audit, should we decided to take it on, would a major, collaborative, group effort that will need to be broken down into very small, manageable parts.