Glossary
The language behind modern execution
A growing glossary of product, technology, execution, and business terms we use across the site — from core product concepts to the operating language behind speed, systems, and transformation.
a.
A/B Testing
A method of comparing two versions of a product or feature against each other to determine which one performs better.
Acceptance Criteria
Specific conditions that a product must meet to be accepted by a user, customer, or stakeholder.
Adoption Curve
A model that describes the rate at which a new product is adopted by consumers over time.
Agile
A flexible and iterative approach to software development that emphasizes collaboration, customer feedback, and small, rapid releases.
Alpha Testing
Early testing of a product conducted by internal teams to identify bugs before releasing it to external users.
Analytics
The collection and analysis of data to inform product decisions and understand user behavior.
API (Application Programming Interface)
A set of rules and protocols for building and interacting with software applications, allowing different systems to communicate with each other.
Automation
The use of technology to perform tasks without human intervention, improving efficiency and consistency.
b.
Backlog
A prioritized list of features, bug fixes, and other tasks to be completed in a product development cycle.
Behavioral Analytics
The analysis of user interactions and behaviors with a product to gain insights into usage patterns and preferences.
Beta Testing
Testing a product with a select group of external users to gather feedback and identify issues before a full launch.
Burndown Chart
A visual representation of the amount of work completed versus the total work remaining in a sprint or project.
Business Model Canvas
A strategic tool used to visualize and develop a business model, including key partners, activities, and revenue streams.
Business Transformation
A significant change in how a company operates, grows, or delivers value in order to perform better in a new reality.
c.
Competitive Analysis
The process of analyzing competitors' strengths and weaknesses to identify opportunities for differentiation.
Contextual Inquiry
A research method where users are observed and interviewed in their natural environment to understand their needs and workflows.
Continuous Delivery (CD)
A software development practice where code changes are automatically built, tested, and deployed to production environments frequently.
Continuous Integration (CI)
A practice in software development where code changes are automatically tested and merged into a shared repository frequently.
Critical Path
The sequence of tasks that determines the minimum time required to complete a project.
Cross-functional Team
A team composed of members with different expertise and roles, working together to achieve a common goal.
Customer Feedback Loop
A process of gathering, analyzing, and implementing customer feedback to improve products and services.
Customer Journey Map
A visual representation of a customer's interactions with a product or service, used to identify pain points and opportunities for improvement.
Customer Persona
A fictional representation of a target customer based on market research and user data, used to guide product development and marketing strategies.
d.
Design Sprint
A time-boxed process for solving design problems through ideation, prototyping, and user testing, typically over five days.
Design System
A collection of reusable components, guidelines, and patterns used to maintain consistency and efficiency in product design.
Design Thinking
A problem-solving approach that emphasizes empathy, ideation, and prototyping to create user-centered products.
DevOps
A set of practices that combine software development and IT operations to improve collaboration and automate processes.
Discovery Phase
The initial stage of product development where research and exploration are conducted to define the problem and identify potential solutions.
Domain Model
A conceptual representation of the key entities and relationships within a particular business domain.
e.
Empathy Map
A tool used to gain insights into users' emotions, thoughts, and behaviors by visualizing their experiences.
Engagement Metrics
Measurements used to assess how actively users interact with a product, such as time spent, frequency of use, and interactions per session.
Epics
Large bodies of work that can be broken down into smaller tasks or stories in Agile development.
Experience Design (XD)
The process of creating products that provide meaningful and relevant experiences to users, often involving UX and UI design.
Experimentation
The process of testing new ideas, features, or changes to gather data and insights that inform product decisions.
f.
Feasibility Study
An analysis that assesses the practicality and potential success of a proposed project or solution.
Feature Creep
The tendency for a product to accumulate more features than originally planned, often leading to complexity and delays.
Feature Flag
A technique that allows specific features to be enabled or disabled in a product without deploying new code.
Framework
A structured approach or set of guidelines used to design and develop products, such as design frameworks or software development frameworks.
Front-end Development
The development of the client-side portion of a web application, focusing on user interface and experience.
Functional Prototype
A prototype that includes some level of functionality and interaction, used to test specific features or user flows.
Functional Requirements
The specific behaviors or functions a system must have to meet users' needs.
Funnel Analysis
The process of analyzing the steps users take to complete a desired action, used to identify drop-off points and optimize conversion rates.
g.
Gamification
The integration of game-like elements into a product to enhance user engagement and motivation.
Gantt Chart
A project management tool that visually represents a project schedule, showing tasks, timelines, and dependencies.
Go-to-Market Strategy
A plan for launching a product and promoting it to the target market, including distribution channels, marketing tactics, and sales strategies.
Growth Hacking
A marketing strategy focused on rapid experimentation and low-cost tactics to grow a product's user base.
Growth Metrics
Key indicators used to measure the growth and success of a product, such as user acquisition rates and revenue growth.
h.
Heatmap
A visual representation of where users click, scroll, or hover on a web page, used to understand user behavior and optimize design.
Heuristic Evaluation
A usability inspection method where experts evaluate a product based on predefined heuristics or best practices.
High Agency
The habit of taking ownership, making progress, and solving problems without waiting to be managed step by step.
High-Fidelity Prototype
A detailed and interactive prototype that closely resembles the final product in design and functionality.
Human-Centered Design
An approach to design that prioritizes the needs, preferences, and experiences of users.
Hypothesis Testing
The process of testing assumptions about a product or market through experimentation and analysis.
i.
Incremental Delivery
A development approach where a product is released in small, functional increments rather than as a complete product.
Information Architecture (IA)
The organization and structuring of information in a product to facilitate navigation and usability.
Intellectual Property (IP)
Legal rights and protections for creations of the mind, such as patents, trademarks, and copyrights, related to product innovations.
Iterative Development
A development approach that involves repeatedly refining and improving a product through cycles of feedback and iteration.
j.
Journey Mapping
The process of creating a visual representation of a user's interactions with a product or service, similar to a customer journey map.
k.
Kanban
A visual workflow management method used in Agile development to visualize work and optimize flow.
KPIs (Key Performance Indicators)
Metrics used to measure the success and performance of a product or project.
l.
Launch Plan
A comprehensive strategy outlining the steps and activities required to release a product to the market successfully.
Lean Development
A methodology focused on minimizing waste and maximizing value in product development.
Learning Curve
The rate at which users become proficient with a product or system as they gain experience.
Low-Fidelity Prototype
A simple, often paper-based representation of a product used for early-stage testing and feedback.
m.
Market Research
The process of gathering and analyzing information about a target market, competitors, and industry trends.
Milestone
A significant point or event in a project timeline that marks progress or completion of a major phase.
Minimum Marketable Product (MMP)
A version of a product that has just enough features to be marketed and provide value to early adopters.
Mockup
A static visual representation of a product's design used to demonstrate its appearance and functionality.
MVP (Minimum Viable Product)
A version of a product with the minimum features needed to gather user feedback and validate assumptions.
n.
Needs Assessment
The process of identifying and analyzing the needs and requirements of users or stakeholders to guide product development.
Net Promoter Score (NPS)
A metric used to measure customer loyalty and satisfaction based on the likelihood of recommending a product or service.
Non-Functional Requirements
The quality attributes of a product, such as performance, security, and usability, not directly related to its functionality.
o.
OKRs (Objectives and Key Results)
A framework for setting and tracking goals and outcomes in an organization.
Onboarding Experience
The initial interaction and orientation provided to new users to help them understand and use a product effectively.
Open Beta
A testing phase where a product is made available to a broader audience to gather feedback and identify issues before the official launch.
Operating Leverage
The ability to create disproportionately larger business results without increasing cost at the same rate.
Operational Efficiency
The ability to deliver products or services in the most cost-effective manner without sacrificing quality.
Operational Excellence
The practice of running work with clarity, discipline, and repeatability so speed does not turn into chaos.
p.
Pilot Program
A trial run of a product or feature with a limited user group to test its effectiveness and gather feedback before a full-scale launch.
Pivot
A significant change in a product or business strategy based on feedback or market conditions.
Product Backlog
A prioritized list of tasks and features that need to be completed for a product, often used in Agile development.
Product Lifecycle Management (PLM)
The process of managing a product's entire lifecycle, from conception to disposal.
Product Roadmap
A strategic plan that outlines the vision, direction, and progress of a product over time.
Product Strategy
A high-level plan that outlines the vision, goals, and direction for a product, including market positioning and competitive differentiation.
Project Management
The practice of planning, executing, and overseeing projects to achieve specific goals and objectives.
Prototype
An early, often functional version of a product used to test concepts and gather feedback.
q.
Qualitative Research
The collection and analysis of non-numeric data to gain insights into user behavior and preferences.
Quality Assurance (QA)
The process of ensuring that a product meets the required quality standards through testing and validation.
r.
Rapid Iteration
The practice of quickly making and testing changes to a product based on feedback and learning.
Rapid Prototyping
The quick creation of a functional model of a product to test ideas and gather feedback.
Release Management
The process of planning, scheduling, and controlling the deployment of software releases.
Release Notes
Documentation that provides information about new features, bug fixes, and improvements included in a product release.
Requirement Gathering
The process of collecting and defining the needs and expectations of users and stakeholders for a product.
Risk Management
The identification, assessment, and mitigation of potential risks that could impact a project or product.
s.
Scoping
The process of defining the boundaries, objectives, and deliverables of a project or product.
Scrum
An Agile framework for managing complex projects, emphasizing iterative progress and team collaboration.
Stakeholder
Anyone with an interest or investment in a product or project, including customers, team members, and investors.
Story Points
A unit of measure used in Agile development to estimate the effort required to complete a task or user story.
SWOT Analysis
A strategic planning tool used to identify strengths, weaknesses, opportunities, and threats related to a product or project.
System Architecture
The structured design of a system, including its components, interactions, and technologies used.
t.
Technical Leadership
The ability to guide technical decisions, architecture, delivery quality, and engineering direction in a way that supports the business.
Test-Driven Development (TDD)
A software development approach where tests are written before the code to guide development.
Time-to-Market
The period it takes for a product to move from conception to being available for purchase.
Timebox
A fixed period allocated for completing a specific task or phase of development, used to manage time and resources effectively.
u.
Usability Testing
The evaluation of a product's ease of use and user satisfaction through observation and feedback.
Use Case
A detailed description of how a user will interact with a product to achieve a specific goal.
User Acceptance Testing (UAT)
The final phase of testing where end users evaluate the product to ensure it meets their needs and requirements before release.
User Experience (UX)
The overall experience a user has with a product, including its usability, accessibility, and design.
User Flow
A visual representation of the steps a user takes to complete a specific task or goal within a product.
User Story
A short, simple description of a feature or functionality from the user's perspective, often used in Agile development.
v.
Value Proposition
A statement that explains the unique benefits and value a product provides to its users.
Value Stream Mapping
A lean management tool used to analyze and optimize the flow of value through a process or system.
Vulnerability Assessment
The process of identifying and evaluating security weaknesses in a product or system.
w.
Waterfall Model
A linear approach to software development, where each phase is completed before moving on to the next.
Wireframe
A low-fidelity visual representation of a product's layout and structure, used for planning and design.
Workflow Automation
The use of technology to automate repetitive tasks and processes within a product or system.
x.
XP (Extreme Programming)
An Agile software development methodology that emphasizes customer satisfaction, teamwork, and continuous improvement.
y.
YAGNI (You Aren't Gonna Need It)
A principle in software development that encourages building only what is necessary and avoiding unnecessary features.
z.
Zero-Based Design
A design approach that starts from scratch without assumptions, often used to rethink and innovate existing products.
Zero-Day Release
The launch of a product or feature that is available to users immediately without prior notice or pre-release testing.
Zero-to-One Product Development
The process of turning an idea, hypothesis, or unmet need into a first real product people can use, test, or react to.