A wireframe is a simplified representation of your website or application. It consists of lines and text that can be hand-drawn or electronic. The focus of the wireframe should be structural elements that represent priority. In this stage, visual design and color are not presented.
A mockup is a high-fidelity simulation of the product. It has a richer visual element than wireframe, including graphics, layout, and overall style. While a prototype is about interaction design, mockups focus on how the users will interpret the design through its visual elements.
Compare to wireframes, prototypes are more flexible. They can be responsive and may contain images or content. Prototypes can be made from paper or digital tools like Adobe XD. All wireframes are prototypes but just low fidelity without many details. But a high-fidelity prototype is not a wireframe. It takes you as close as to a real representation of UI and should feel like real software to users.
A/B testing is a controlled experiment for comparing two versions of the design to identify which one is more successful. It is a way of testing the designers’ hypotheses. A/B testing allows them to confirm whether the hypotheses will work out well or not. It helps with making the right decisions.
Affordance is a feature of an object that made actions physically possible. Users should understand the affordance of a feature of an object without having to know how to use it. In order words, affordance is a hit for users to interact with a product. For instance, a button should be designed to look as if it should be pushed.
Accessibility is concerned with whether all users (including those with disabilities or special needs) can access an equivalent user experience. It focuses on users with disabilities. Common barriers to accessibility issues are color blindness, hearing difficulties, wheelchair-user concerns, etc.
Clickstream is a way of collecting and analyzing data to track users’ actions during their interaction with the product. It is also a method to get unbiased quantitative data about user behavior.
A Diary study is a way of a research method used to collect qualitative data about user behavior over time. It is usually designed for understanding long-term user behavior and experiences
Card sorting is a research method where participants label is written notes according to a certain number of criteria. It helps designers structure content that’s easy to navigate within the information architecture.
KPI is a way of monitoring or measuring progress towards a goal. Per to Oxford’s Dictionary definition, it is a quantifiable measure used to evaluate the success of an organization, employee, etc. in meeting objectives for performance. In other words, KPI is a way to show where the gaps are and where to put more attention. KPI’s can be used at every level in an organization to keep track.
A mood board is a collection of features, fonts, images, icons, and other UI elements for defining the artistic direction of a project. It should be also focused on meeting user needs and problem-solving.
It is a map that tells you what part of the webpage users is more focused on. It uses a color scheme, ranging from warm colors, like red and blue at the cooler end of the color spectrum. The warmer areas indicate the areas where users are focusing on more.
Eye-tracking is the measurement of eye activity on a screen. It involves measuring either where the eye is focused or the motion of the eye as an individual view a web page. You can get information on what users look at most frequently and in what order.
It is a diagram designed to visualize all the potential causes of a problem to discover the root cause. The head of the fish states a problem and bones along the spine represent categories of factors. When applied correctly, it ensures that you address the actual cause of the problem.
Lastly, technical debt or design debt is a cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer. Engineers use it when quality is compromised. For example, development teams take shortcuts to deliver functioning products faster which later needs to be refactored.