Checklists for UX designers
Problem
There are a lot of things UX needs to think about when considering the implementation of an issue. In order to prevent human error as much as possible, it might be smart to create a checklist for us to check off on when considering the solution to an issue.
Let's brainstorm here and put the outcome into our workflow documentation
Proposal
Quick proposal
### UX Designer Checklist
* [ ] Provide design specs, if necessary
* [ ] In-app language follows technical writing guidelines
* [ ] Adheres to color palette (custom solutions only when necessary)
* [ ] Leverages and conforms to design system as much as possible (custom solutions only when necessary)
* [ ] Accounts for role-based states for views and controls
* [ ] Empty states for views and controls
* [ ] Error states for views, workflows and controls
* [ ] Messaging (confirmation, alert, error and informative modals, toasts and or snackbars)
* [ ] Field labels, hints, help and validation errors
* [ ] Note non-evident functionality (e.g. is field auto-complete or no?)
* [ ] Help, such as tooltips, pop-overs and icon or text links to contextual help content
* [ ] Loading feedback, including indeterminate (e.g. spinners and skeletons) and determinate scenarios (e.g. percentage based loading bars)
* [ ] Responsive behaviors
* [ ] Mobile versions
* [ ] Graphical assets and or font icon updates
* [ ] Consider workflow diagrams, if necessary
* [ ] Design system and editorial stye guide update requests (e.g. requesting a new components be added or an existing component be updated)
* [ ] Log other UX debt created/encountered (e.g. if you added the 20th item to a bloated menu that needs to be revisited/designed but you couldn't resolve that during your work)
* [ ] Capture UX debt, if incurred, for later follow-up
Edited by Pedro Moreira da Silva