Solution validation: Workspace/namespace naming & terminology
What did we learn?
Results |
---|
2-3 sentences to summarize the results |
- Link to Dovetail project |
What’s this issue all about?
In &6473, we identified the need to update our information architecture by creating the workspace layer and consolidating projects and groups into a more generic namespace object.
What hypotheses and/or assumptions do you have?
Some of the terminology associated with this information architecture update may be confusing and feel too technical.
What questions are you trying to answer?
Core questions
- Do users understand this terminology? If not, how should we be speaking about it?
- How do we communicate this change in an elegant way to users?
What persona, persona segment, or customer type experiences the problem most acutely?
- Annoying answer... all personas really.
- But at a minimum, it would be useful to understand the difference in perception between
- Admin - a person who sets up GitLab
- Software developer - More technical users
- Project manager - Less technical users
What business decisions will be made based on this information?
- Naming conventions for our organisational constructs and how they relate to each other
- Ways of communicating the changes to our customers going forward
Edited by Nick Post