Juliane Jeske - UX/UI and Product Management Design Glossar

Design Terms From A - Z

01. Discovery
- Discovery is a preliminary phase in the UX-design process that involves researching the problem space, framing the problem(s) to be solved, and gathering enough evidence and initial direction as well as consensus on what to do next.
- The Outcome of a Discovery: At the end of the discovery, the team has a detailed understanding of the problem and what outcomes to aim for, as well as where to focus its efforts. They may also have some high-level ideas for solutions that they can take forward and test. In some cases, the end of a discovery might be a decision not to move forward with the project because, for example, there isn’t a user need.
- Discovery isn’t about producing outputs for their own sake. However, the following might be produced to help the team organize learnings about the problem space and users:
- A finalized problem statement: a description of the problem backed up with evidence that details how big it is and why it’s important Finalized maps, such as a user-journey map or service blueprint, User-needs statements, Personas,High-level concepts or wireframes (for exploring in the next phase)
- All discoveries strive to achieve consensus on a problem to be solved and its desired outcomes.
02. UX Research
- A Discovery should result into the following Research:
- Understanding of users: Through user research, the project team achieves an understanding of who the users are and how they are affected by a particular problem, as well as what they need, desire, and value from a solution (and why).
- Understanding of the problems to be solved and of the opportunities: Through investigative work, the team understands how and why the problem(s) occur, and what effect the problem has on users, as well as on the organization. It understands the magnitude of the problem and opportunities for the organization, product, or service.
- Understanding of existing constraints: By learning about current business processes, solutions, and available compatible technologies, the team can identify feasible solutions to explore after discovery.
- Shared vision: During discovery, the team works with stakeholders to understand overarching business objectives and desired outcomes and get answers to questions such as “What do we want to achieve?” or “What does success look like?” This approach, in turn, focuses the team on the problems (and later the solutions) that will have the greatest impact on that outcome. The team should also have an idea of what to measure going forward, to understand whether the solution is working towards the desired outcome.
03. UX Web Audit
- We gather a Screen inventory of the Landingpage or Service Page and check if the UX is consistent based on Usability Heuristics and Contextual Inquire.
- Those insights are listed into the Design Sprint Backlog for future planning and prioritisation mapping.
04. UX Brand Audit
05. UX Lean Canvas
06. UX Survey
- We create an UX SURVEY to gather feedback about a brand design, grafik assets, an app or website perception, or for business insights of stakeholder.
- We explain the WHY? and HOW ?
  describe the hypothesisis, problem statement, the product or experience the survey is for,
- The type of feedback you're aiming to gather QUALITATIVE = behaviour,(e.g., viability, functional, usability, satisfaction, accessibility), QUANTITATIVE = numbers, results,
- our target audience (e.g., general users, beta testers, internal team)
07. UX Maturity
08. UX Strategy
- ...talking about STRATEGY, I always find those Grafiks from IxDF - Interaction Design Foundation very useful to explain the thought process for an UX Strategy (Iceberg).
- I added 2 Elements: Budget and Unknown Entity to my own Grafik Exploration, because to execute a Strategy, and to hit a fancy design - we need to know the invest and consider unknown risk barriers. Its never all said. never all known. so its important to stay curious for the unknown.
09. UX Analysis
- ..would you like me to focus on anything specific,
  like UX usability (audit), UI aesthetics, Navigation (flows), Accessibility, Competitors or SEO conversion optimization?
10. UX Reports
- Methodology: how you went about the evaluation, what tasks you asked the users to perform, what data was collected, what scenarios were used, who the participants were and their demographics
- Test Results: An analysis of all the data collected, including illustrations such as bar charts and textual descriptions of the findings, and user comments that might be particularly illustrative or enlightening. Depending on whom you are communicating the report to, this section may contain some more technical details, such as the type of statistical analyses used.
- Findings and Recommendations: what do you recommend, based on the data that you collected and your findings?

- terms I use to explain my process -

00. CSD Matrix
- You're asking about the Communication Structure Design (CSD) Matrix in organizational or systems design. In that context, a CSD Matrix is typically a tool used to map out and optimize the flow of communication between different roles, teams, or systems. It helps ensure that every necessary interaction is identified and that communication channels are structured, clear, and efficient.
01. SMART Goals
02. MosCoW Priorisation
03. OKR'S and KPI's
04. HEART Framework
05. Value Proposition
06. Hypothesisis - Assumptions
07. Problem Statement

- terms I use to explain my process -

01. Emphatize Workshops
- Workshops align team members and stakeholders and are a useful tactic for discovery. Some workshops commonly used in discoveries include:
- Kickoff workshop. A kickoff workshop occurs at the beginning of the discovery and aims to create alignment on the objective of the discovery, and when it will be complete. It is normally attended by the client or key stakeholders who are invested in the discovery, as well as by the discovery team itself. It can also include agreement on the roles and responsibilities of each team member during the discovery.
- Assumption-mapping workshop. Many teams bring in experts and conduct data-gathering activities in a workshop. They question the validity of certain ‘facts’ and identify the deep-rooted assumptions that need further exploration. Part of this workshop can also include prioritizing assumptions in terms of risk to the project’s outcome. The riskiest assumptions should be prioritized in terms of research activities.
- Research-question–generation workshop. This workshop is similar to the assumption-mapping workshop, and the two are often combined; the team discusses what the unknowns are and drafts research questions. The research questions can be prioritized in terms of their importance and how well they will work to gather the knowledge needed to move forward.
- Affinity-diagramming workshop. After performing exploratory user research — such as user interviews, contextual inquiry, and diary studies — insights and observations are transferred to sticky notes and the team works to affinity-diagram them to uncover themes around problems, causes, symptoms, and needs.
- Mapping workshop. The team plots insights from user research and other investigations into a map of the problem space, customer experience, journey, or service. The map is used to create alignment, to identify gaps that need further research, and to highlight major opportunities.
- Ideation workshop. This workshop takes place at the end of the discovery. Once the team has performed the necessary research, the team crafts ideation statements like How-Might-We’s based on the problems or insights it has uncovered and uses them to generate solution ideas to explore going forward.
02. Design Sprints
- A design sprint is a digital product development method developed by Jake Knapp at Google Ventures in 2010. Design sprints provide a framework for addressing problems in digital product development. A specific problem is set for a week (5 days or 2 weeks) and KPI's are defined on Monday, a solution is sketched out, prototyped, and then tested in a very short space of time. All relevant competencies, such as product managers, stakeholders, and subject matter experts, come together for five days.
04. Brainstorming
05. Design Thinking
- A method of the UX Discovery is the Design Thinking is a non-linear, iterative process that teams use to understand users, challenge assumptions, redefine problems and create innovative solutions to prototype and test. It is most useful to tackle ill-defined or unknown problems and involves five phases (Sometimes 7): Empathize, Define, Ideate, Prototype and Test.
- We’ve outlined a direct and linear design thinking process here, in which one stage seemingly leads to the next with a logical conclusion at user testing. However, in practice, the process is carried out in a more flexible and non-linear approach.
- Empathy is crucial to problem-solving and a human-centered design process as it allows design thinkers to set aside their own assumptions about the world and gain real insight into users and their needs.
06. Double Diamond
- A discovery starts broad and requires team members to investigate the context of the problem. The double-diamond diagram introduced by the UK Design Council — and reproduced below — illustrates the high-level process of a discovery: first, the team expands its understanding of the problem by researching its full context; armed with this knowledge, the team agrees on what the problem is, before moving to the next phase of ideating and testing in the Develop stage.
07. Stakeholder Interview
- Stakeholders often have unique knowledge, insight, and data about internal, backstage processes and the users who interact with them. Interviewing stakeholders provides an additional layer of insight that helps the team understand the scale of the problem and the viability of later solutions.
- Interviewing key people in the organization can provide you with an understanding of:
- Key business objectives of the organization, individuals, or teams (These are helpful to determine if and how these broader goals tie-in to the goals of the project.) Data and insights about how problems affecting users impact backstage work (such as inquiry type and volume, additional processing) Solutions they’ve tried before that have or haven’t worked, how they implemented them, what other problems they caused, as well as why they were removed (if applicable) In addition to interviewing stakeholders, including key stakeholders in the discovery process or having them weigh in throughout not only facilitates further buy-in, it also provides more insights.
08. Jobs to be Done
- Jobs-to-be-Done Theory provides a framework for defining, categorizing, capturing, and organizing all your customers’ needs. Moreover, when using this framework, a complete set of need statements can be captured in days — rather than months — and the statements themselves are valid for years — rather than quickly becoming obsolete.
09. Use Case Definition
10. Task Analysis - User Flow
- Problem Statement-A high school teacher wants to know before the next class which homework questions are the most difficult for the most students.
- Product Design: Questions App, that would help the students to put the questions of a perticuler subject subdevided into chapters and questions of each. Can work both online and offline.
- TASK 1-students need to download the d.questions app from playstore.
  TASK2- then students need to select the question of a subject of perticuler chapter which they find difficult and put it on the class section of the app.
  TASK3-the teacher would automatically get notification from the app which she had downloaded and she can then better be able to save time as she would be able to tell the answers during the class.
- SOLUTION SPACE- since the teacher didnt get the responses of all students on whattsapp initially due various reasons, so she can now get the updates regarding the problems of students, and can solve them whenever possible.
11. Journey Mapping

- terms I use to explain my process -

00. Design
- Design is a discipline of study and practice focused on the interaction between a person — a ‘user’— and the man-made environment, taking into account aesthetic, functional, contextual, cultural and societal considerations. As a formalised discipline, design is a modern construct.
- Concretely, most people’s experience of design stems from their daily interaction with physical objects, built spaces and digital environments. We interact with what is around us, and each other, through designed constructs. Clothing, devices, transportation, user-interfaces, the landscape, the city, even the chair you are sitting in, were all designed by the choice we do.
01. Screen Inventory
02. SEO - Sitemap - Navigationtree
03. Webdesign (Responsive Webdesign)
04. App Design
05. Service Page Design (Landing Page)
06. SaaS Dashboards Interface
07. UI Design
- User interface (UI) design is the process designers use to build interfaces in software or computerized devices, focusing on looks or style. Designers aim to create interfaces which users find easy to use and pleasurable. UI design refers to graphical user interfaces and other forms—e.g., voice-controlled interfaces.
- UIs should also be enjoyable (or at least satisfying and frustration-free). Users don’t care about your design, but about getting their tasks done easily and with minimum effort.
- When your design predicts users’ needs, they can enjoy more personalized and immersive experiences. Delight them, and they’ll keep returning.
- Where appropriate, elements of gamification can make your design more fun.
- UIs should communicate brand values and reinforce users’ trust.
- Good design is emotional design. Users associate good feelings with brands that speak to them at all levels and keep the magic of pleasurable, seamless experiences alive.
08. UX Design
- Often confused with UX design, UI design is more concerned with the surface and overall feel of a design. UI design is a craft where you the designer build an essential part of the user experience. UX design covers the entire spectrum of the user experience (information architecture and logic). One analogy is to picture UX design as a car with UI design as the driving console.
09. Design System
- A design system is a collection of guidelines, components, and standards used to design products and services. It serves as a guide for the development and implementation of digital products.

- terms I use to explain my process -

01. Code
02. Webdevelopment
03. Squarespace or Webflow Setup
04. Git Version Control
05. Sass/Less
06. Wordpress CMS
07. E-Commerce Setup

- terms I use to explain my process -

Throughout my career, I've worked with agencies, startups, and enterprises, and I've seen and heard many definitions of UX strategy. The problem with evolving technology terminology is that it causes confusion among clients, stakeholders, recruiters, and designers alike.

These terms I use to create a general understanding about Design UX terminology, in our workflow process - to avoid missunderstandings, and to establish a smooth workaround with all team members.