A comic strip that illustrates the series of actions that consumers need to take while using the product. Translates functionalities into real-life situations, helping designers create empathy with the consumer while having a first look at the product scope.
A relatable snapshot of the target audience that highlights demographics, behaviors, needs and motivations through the creation of a fictional character. Personas make it easier for designers to create empathy with consumers throughout the design process.
That can be hard to do at first; it’s normal to look around a conference table at a lot of people whose job titles start with the word “chief” and be afraid to speak up for fear of looking stupid. But staying silent is just as bad. After all, the reason you are in a meeting like that is because those chiefs want your help. Everyone is trying to solve a problem together — your titles don’t matter.
Affordances — all possible interactions the control is designed for Perceived affordances — what interactions people think the control provides (which can be ambiguous) Signifiers — specific indicators to convey what actions are possible (make the perceived affordance clear)
Another crucial point for engineers is to know how things will react in different scenarios. Think about error state of input or where to show error message. Same as how disabled state of submit button will look like, where to put spinner in input etc. It’s super easy for engineers go just through your Symbols artboard and style one by one element before they even start coding all screens thanks to having a Sketch file as Lego blocks. Styleguide and visual overview of all elements is actually one of the most requested features/designs for the next update of my Dashboard UI Kit.