New Code Quality Area
Project: Move a tech debt tool to a new product
Role: Content Designer
Goal: The users of the new OS cloud offer needed an area to control their technical debt. We looked into feedback received from users in Slack, ideas during previous research, and understood what to do.
Content Design
User Testing
Skills
Information Architecture
Terminology
User Research
Desk Research
Competition Analysis
I looked into other tech debt monitoring tools, mainly for inspiration to deal with data and to consider their solutions on common needs, like manipulating large data, showing new data, sorting and filtering, and the concepts used in the industry.
2. Terminology
I named the menu entry to “Code quality”.
My decision was supported by content design usability heuristics, industry research and non-moderated user tests.
Code quality is now one of the most visited portal areas. Most of the users have reported to like the term because it sounds positive for an area that used to be called technical debt.
3. Technical Writer
Worked on code patterns “How to resolve” UI copy:
Got rid of wrong capitalization in some code patterns names
Cutted descriptions — impact and how to resolve tested great!
Edited as if the experience was talking to the person
More simple terms. Example: revise to review
Checked for accessible terms, using SG: execute to run
Reduced 50% of the copy in some patterns
