A Minimum Viable Product (MVP) is the early stage of a product that allows teams to test and validate new features based on the needs of the user. A MVP helps get products to market faster with features that benefit their target audiences.
Scaling itself has multiple meanings, sometimes referring to increasing the amount of work the application can do or increasing the amount of resources available to the app.
Any unvalidated or untested information formed out of the given problem and is assumed to be true. Assumptions formed can be based on what we know about who will use the product, uncertainties around the product, scenarios that may occur during the use of the product, etc.
Card Sorting
Card sorting is a design exercise that guides us toward creating the most coherent information architecture of a product. During a card sorting session, participants are asked to associate two sets of flashcards by grouping them. While the first set of flashcards contains categories, the second set contains sample content.
Decider / Product Owner
The individual in this role has final say for the product. Typically, our client.
Design Debt
Design debt is the lesser-known cousin of tech debt. Design debt represents the full spectrum of design work that has been banished to the dusty backlog. It includes everything from lack of design thinking processes to specific UI bugs that need fixing. It's what happens when the gap between your first feature and your 50th is so wide that you've given up on creating new things in the context of what's already happening in your product.
Dot Voting
This technique is a collaborative method used to conduct a silent critique. It is done by giving each participant an equal number of dots they can use to vote on a set of items. It could be used to narrow concepts, discussion topics, strategies, or concepts.
Empathy Map
A visualization of information about a particular users’ motivations, thoughts, feelings and behaviors in order to base design decisions off of what those users need most. This collaborative exercise is done to step outside our own perspective to better diversify our understanding.
The individual in this role leads the exercises and discussion during the design sprint. Since this is a demanding role, it can be two people rotating in and out.
Fidelity refers to the level of detail and functionality built into a design concept. Lo-fidelity consists of a barebones representation of what a product will look like, while Hi-fidelity will more closely match the final product.
How Might We (HMW)
"How Might We" (HMW) statements are questions that act as a starting point for finding potential solutions to problems discovered during user research. HMW statements are open-ended and are often used during the Understand Phase of a Design Sprint.
Ideation is the process of generating a broad set of solutions to problems that impact a product. This can be done through design thinking and brainstorming exercises.
Information Architecture
Information architecture is a blueprint of the structure, hierarchy, and content within a product. It also defines how that information is organized including naming conventions and definitions around product functionality.
A mockup is a high-or-low-fidelity visualisation (colors, graphics, etc) of a website or app. Mockups generally represent the final version of the product to be built.
Pain Point
Pain points are moments of frustration and friction that occur while a user is navigating a product or the customer experience around it.
Problem Statement / Job To Be Done (JBTD)
A problem statement or “job to be done” is a description of the problem that needs to be solved. Clearly identifying the problem is the first step in determining the work necessary to better understand issues surrounding the problem and to rally support from stakeholders. This discovery work will eventually lead us to exploring potential solutions.
A prototype is a representation of a product with basic features used to test and validate ideas before product or feature launch. Prototypes can come in two flavors: Low-Fidelity wireframes or High-Fidelity mockups. Both can be used for testing at different stages of the product's lifecycle depending on the team's and the user's needs.
Recorder / Note Taker / Scribe
The individual in this role is in charge of the documentation for the design sprint.
Scaling itself has multiple meanings, sometimes referring to increasing the amount of work the application can do or increasing the amount of resources available to the app.
Silent Critique
Silent Critique is the process of silently reviewing a document and adding feedback digitally. This method used to gather unbiased and individual feedback in a focused environment. It also cuts down on time so that each person isn’t presenting each of their own ideas.
A stakeholder is anyone who has interest in the product or anyone you need to collaborate with or get buy-in from in order to make the product successful.
A chronological set of images or sketches that communicate a story, journey, or process. Creating storyboards is used as a design thinking exercise after the group has had some time to think individually about the problem and many possible solutions to it.
Technical Debt
In its classical formulation, technical debt is described as intentionally taking shortcuts and cutting corners in code quality in order to speed up development. While this can be valuable in the short term, over the long term it makes the overall codebase more bug-prone and future features slower to develop. Eventually you “pay back” the debt by cleaning up the original code.
To define a start and an end to an activity within a specific amount of time.
User Interview
A user interview is a research technique used to gather information about your experiences, preferences, and behaviours that will help inform a product’s design.
User Journey / Journey Map
A user journey is the path a user takes to navigate through a product to get to their desired goal. In product design, identifying a user journey or creating a “journey map” allows product designers to discover the best ways to enable the user to achieve their goal as efficiently as possible.
User Persona
A User Persona is a character used to represent a user type. For a dog walking app, two user personas would be “A pet parent” and “A dog walker”.
User Story
A user story is a description of a product’s features that is written in natural language and from the perspective of a product’s user.
Validation is the process of stress-testing your assumptions. Broadly, what you’re trying to uncover in this process is whether or not your product will be desirable to customers, viable for your business, and feasible to build.
A wireframe is an outline of a website or app -- think its skeleton. A wireframe provides the architecture, layout, and functionality of a product in its early stage and is used primarily for testing with users. Usually, wireframes refrain from styling the product too much and focuses more on verifying the overall flow and experience of the product matches the user's expectations.