UX Writing Glossary of Terms #217
Labels
dependency
feature: website
PBV: MVP - Closed
role: design
role: ux writing
size: 1 pt
1 point = 6 hours or less
Overview
For the meantime, the project is pivoting away from containing a workshop/educational component to focusing exclusively on serving as a data access point for open government data. Past UX writing (#87) was based on the old design.
The nomenclature audit (#216) confirmed that copy on the wireframes and current public-facing Access the Data content still discusses the data literacy components of the project, which are now on the back burner.
We need to clarify terminology around Access the Data: what terms we want to use and what terms we want to avoid in the first iteration of the website that we will make public (i.e., the data catalog without the data literacy component).
I recommended in the audit that we develop a glossary of terms.
Additional Information
A prior UX writer expressed a major blocker is the broad range of documents, iterations, and research reports related to the development of the website. This creates a large learning curve. I am facing this same blockage as well as I familiarize myself with the project.
Accomplishments so far:
As a team, we have succeeded in developing Brand Voice chart (#215).
We do not have a style guide.
UX Writing can benefit from a glossary of terms.
Brand writing tone has been described as:
trustworthy and simple language
Talking to - you
3rd grade/children’s book-short sentences, conversational
Action Items
Resources/Instructions
Nomenclature Audit #216
Brand Voice Chart #215
ATD UX Writing Resources on the ATD Website Wiki Page
Completed Work
The text was updated successfully, but these errors were encountered: