Keep useful ideas close. Saved topics stay in this browser on this device.
Enable JavaScript to view saved topics. Browse all topics.
Tap the card to reveal · Swipe, drag, or use the arrow keys to browse
A/A testing compares nominally identical experiment variants to check assignment, exposure, metrics, and analysis behavior before relying on a new experiment system.
A/B testing randomly assigns eligible units to variants and compares predefined outcomes to estimate the causal effect of a product change.
Specific, testable conditions that describe the behavior and outcomes a work item must satisfy to be accepted by product and delivery collaborators.
Digital accessibility means designing and developing products so people with disabilities can perceive, understand, navigate, interact, and contribute.
The accessibility tree is the browser's semantic representation of relevant interface objects for platform accessibility APIs and assistive technologies.
An accessible name is the programmatically determined label that assistive technologies use to identify an interface element.
ARIA is a suite of web standards that adds roles, states, properties, and relationships so custom interfaces can expose meaning to assistive technologies.
An accordion is a set of labeled sections whose headings control whether associated content panels are expanded or collapsed.
Activation rate is the percentage of eligible new users or accounts that reach a defined early-value milestone within a specified time window.
Adaptive design selects or composes distinct layouts and behaviors for meaningful device, window, input, or task contexts rather than merely scaling.
The aesthetic-usability effect is the tendency for a visually appealing interface to be perceived as easier to use, sometimes despite interaction problems.
A collaborative method for clustering individual observations or ideas by similarity to reveal patterns, disagreements, and next steps.
A property of an object or interface that makes certain actions possible for a particular user.
Agent memory retains and retrieves selected state or information so an AI agent can maintain continuity within a task or across interactions.
An adaptive approach to creating products through short feedback loops, close collaboration, frequent delivery, and learning-led changes to plans.
An AI agent is a model-centered system that selects and executes actions in a feedback loop to pursue a goal within defined tools, permissions, and stopping conditions.
An AI hallucination is generated content that is unsupported by available evidence, inconsistent with the input, or factually incorrect while appearing plausible.
AI red teaming deliberately probes an AI model or product for harmful behavior, vulnerabilities, and misuse paths under an agreed testing scope.
AI-assisted design uses generative or predictive systems to support design work while keeping human judgment, verification, accountability, and user rights central.
Alerting turns selected system signals into actionable notifications with a clear owner and response urgency.
Algorithmic fairness evaluates and addresses unjust differences in how automated systems allocate benefits, impose burdens, or represent people.
An algorithmic feedback loop occurs when a system's outputs influence the behavior or observations later used to update or evaluate that system.
Alternative text conveys the purpose or information of non-text content to people who cannot perceive the visual or audio presentation.
Annual contract value normalizes a customer contract to a yearly amount so teams can compare deals with different durations.
Annual recurring revenue expresses the current recurring subscription base as a yearly run rate, excluding one-time charges.
A product–market growth framework that distinguishes market penetration, market development, product development, and diversification.
A managed entry boundary that routes API traffic and applies shared policies before requests reach backend services.
A secret or identifier presented by a software client to associate API requests with a project, application, or principal.
The practice of evolving an API contract while making compatibility and client migration expectations explicit.
A product-development approach that treats an API contract as a primary interface designed collaboratively before dependent implementations are built.
A defined interface through which software components request capabilities or exchange data without depending on each other's internal implementation.
A short, durable record of an architecturally significant decision, including its context, rationale, alternatives, status, and consequences.
An ARIA live region exposes dynamic content updates to assistive technology without requiring focus to move to the message.
Artificial intelligence is the broad field of building systems that infer from inputs to produce predictions, content, recommendations, or decisions toward human-defined objectives.
An unverified belief that a product decision or plan depends on being true.
A method for exposing beliefs behind a product idea and prioritizing the assumptions that are both critical and weakly supported.
Atomic design is a five-level mental model for building interfaces from small elements into components, sections, layouts, and real content instances.
A distinction between evidence about what people report or believe and evidence about what they actually do in a situation.
A rule-based or modeled assignment of credit for an outcome across prior marketing or product touchpoints.
The process of establishing sufficient confidence that an actor controls one or more authenticators bound to a claimed digital identity.
The process of deciding whether an authenticated or anonymous actor may perform a specific action on a particular resource in context.
Automation bias is the tendency to rely on automated advice in ways that cause people to miss problems or accept incorrect recommendations.
An avatar visually represents a person or entity, while an avatar group compacts several representations into a recognizable set.
Average revenue per user divides revenue for a defined period by the average number of users or accounts represented in that period.
A unit of work executed outside an interactive request so it can run later, longer, or independently.
The ongoing practice of maintaining an ordered, transparent, and strategically aligned set of potential product work so teams can make sound delivery choices.
An ongoing collaborative activity that adds appropriate detail, order, and size to near-term backlog items as the team learns more about the work.
Badges show compact counts or status, chips represent compact interactive choices or entities, and tags label or categorize content.
Banners present persistent page- or service-level messages, while alerts announce important time-sensitive information without requiring users to find it first.
A beachhead market is a deliberately narrow first market where a team can concentrate resources, establish strong value, and earn a base for expansion.
A collaborative development practice that uses concrete behavioral examples to align product, engineering, and testing before and during implementation.
Behavioral design applies evidence about human behavior to shape choices and environments while protecting autonomy, welfare, and informed consent.
A structured, limited release that lets representative users try a near-ready product so teams can reduce risk and improve it before wider availability.
A blameless postmortem examines an incident’s conditions and system behavior without making individual punishment the organizing explanation.
Blue-green deployment prepares a replacement environment alongside the live one and switches traffic after validation.
A bottom sheet is a mobile-oriented surface that rises from the bottom edge to present contextual content or actions while retaining some sense of the underlying view.
A breadcrumb is a secondary navigation trail that shows the current page's position within a hierarchy and links to its ancestors.
The break-even point is the sales level at which revenue covers the costs included in a clearly defined operating model.
The browser event loop coordinates queued tasks, microtasks, user input, scripts, and rendering while JavaScript jobs run to completion.
A structured decision about whether to create a capability, acquire it, reuse an existing option, or combine approaches based on value, cost, risk, and control.
A feedback loop that turns a risky assumption into the smallest useful test, behavioral evidence, and a consequential product decision.
Burn rate measures cash consumption per period, distinguishing total operating cash spending from spending net of operating receipts.
A burndown chart plots work remaining over time, often against a reference line that reaches zero at the end of a sprint or delivery horizon.
A burnup chart plots completed work against total scope over time, making progress and scope change visible as separate lines.
An evidence-based justification for an investment that compares options, expected benefits, costs, risks, affordability, and delivery conditions.
The Business Model Canvas maps how an organization creates, delivers, and captures value across nine connected building blocks.
Buttons trigger actions while links navigate to resources or locations, so their behavior and semantics should match the outcome users expect.
CAC payback period estimates how long customer gross profit takes to recover the cost of acquiring that customer.
A temporary store that reuses previously obtained or computed data to reduce latency, network traffic, or work on future access.
A canary release exposes a limited portion of production to a change and evaluates it before widening the rollout.
Captions synchronize speech and meaningful audio with media, while transcripts provide a separate text representation that can be read and searched independently.
A card groups a concise set of information and actions about one object or concept into a reusable visual container.
A categorization method in which participants group and sometimes label content items to reveal patterns in how they expect information to be organized.
A carousel displays a sequence of content items within one bounded area, revealing one item or subset at a time through user or automatic movement.
Cash flow records money entering and leaving a business over a period, revealing funding needs that revenue and profit can hide.
Category design is a company-level strategy for defining a new market frame, educating people about a problem, and building the ecosystem that makes it credible.
Causal inference uses assumptions, study design, and statistical methods to estimate what an intervention changed beyond observed association.
A failure to notice a visible change when attention is elsewhere or the change lacks a strong transient cue.
A governed process for capturing, evaluating, deciding, implementing, and recording proposed changes to approved project baselines or controlled items.
A structured assessment of how a proposed change affects value, people, processes, requirements, designs, systems, plans, risks, and obligations.
Chaos engineering uses controlled experiments to test whether a system remains acceptable when realistic disruptive conditions occur.
The deliberate arrangement of options and context that shapes how people make decisions.
An automated delivery workflow that builds, tests, packages, and promotes software changes through controlled stages toward production.
A resilience pattern that temporarily rejects calls to an unhealthy dependency and later probes for recovery.
An interaction model in which a client initiates requests for capabilities or resources that a server provides across a defined boundary.
Client-side rendering uses JavaScript in the browser to create or update a route's main interface after its document arrives.
Client-side routing maps URLs to browser-rendered views while changing history without loading a new document for each transition.
A model for obtaining configurable computing resources over a network on demand with measured, elastic capacity.
A structured examination of a proposed code change by someone other than its author before or soon after integration.
Code splitting divides an application into separately loadable chunks so a browser need not download and execute all code at startup.
Cognitive accessibility reduces barriers to understanding, remembering, focusing, deciding, and completing tasks for people with diverse cognitive and learning needs.
The amount of limited mental effort required to understand information and complete a task.
A learnability inspection that steps through a task from a new user’s perspective and questions whether each action and its effect will make sense.
Cohort analysis compares groups that share a starting event or characteristic to reveal how behavior and outcomes change over time.
The early-stage coordination problem in which a network or marketplace lacks enough relevant participation to create reliable value.
Color contrast is the luminance difference that helps text, icons, controls, states, and focus indicators remain distinguishable from adjacent colors.
Color in UI supports hierarchy, identity, feedback, and state while maintaining contrast and ensuring meaning never depends on color alone.
A command palette is an on-demand searchable interface for finding and running commands or navigating to destinations, usually optimized for keyboard use.
A group that develops shared capability through sustained interaction around a common domain, practice, and body of practical knowledge.
A structured map of relevant capabilities and defined proficiency levels used to discuss development, coverage, staffing, and role expectations.
A capability or position that lets an organization create and capture value better than relevant alternatives over a meaningful period.
Competitive analysis examines how customers solve a problem, how alternatives create value, and where a product can make a defensible strategic choice.
A component library is a versioned collection of reusable interface units with defined structure, behavior, states, and implementation guidance.
Concept testing evaluates whether a proposed product direction is understandable, relevant, credible, and differentiated before a team commits to detailed design or delivery.
A deliberately designed explanation of a product’s main objects, relationships, actions, and rules.
Concurrency structures overlapping work, while parallelism executes multiple pieces of work at the same instant.
A confidence interval is a range produced by a specified repeated-sampling procedure that expresses uncertainty around an estimated quantity.
Confirmation bias is the tendency to seek, interpret, or remember evidence in ways that favor an existing belief or hypothesis.
A structured approach to understanding and addressing workplace disagreement so people can reach workable decisions, repair relationships, or escalate safely.
A confounding variable is a pre-treatment factor associated with both an intervention or exposure and its outcome, creating a misleading association when it is not addressed.
Conjoint analysis estimates how people trade off product attributes by analyzing their choices or evaluations of systematically varied offerings.
Rules or boundaries that limit available actions and steer users toward valid outcomes.
A packaged application process with its dependencies and isolated runtime configuration, sharing the host operating-system kernel.
A content audit evaluates existing material against user needs and quality criteria to decide what to retain, improve, combine, or retire.
A geographically distributed service that delivers content from edge locations closer to users and shields an origin from repeated requests.
Content design uses evidence about user needs to plan, structure, write, and maintain content that helps people complete a task.
Content hierarchy orders and signals information by importance and relationship so users can scan, understand, and act efficiently.
The content lifecycle covers planning, creation, publication, maintenance, reuse, and retirement of content over time.
Content Security Policy lets a web application restrict browser resource loading and execution through a declared policy.
A content style guide records shared language conventions so contributors write consistent, understandable product content.
A context window is the maximum amount of tokenized input and output a model can consider within one inference request or active sequence.
A collaborative field interview in which researchers observe people doing real work and ask questions within the activity’s natural context.
The capability to keep software in a releasable state so changes can be deployed safely, quickly, and sustainably whenever the organization chooses.
A sustained cadence of customer contact and small research activities that informs product decisions alongside ongoing delivery work.
A development practice of integrating small code changes frequently and checking each integration with an automated build and test process.
Continuous interviewing establishes a sustainable cadence of customer conversations so product decisions draw on recent evidence rather than occasional research projects.
Contract testing checks that communicating applications agree on the requests, responses, or messages they exchange across an interface.
Contribution margin is revenue minus variable costs, showing what remains to cover fixed costs and then generate profit.
Conversion rate is the share of an eligible population that completes a defined action within a specified journey and time window.
The defined period after a starting event or touchpoint during which a later action can count as a conversion.
The observation that systems tend to reflect the communication structures of the organizations that design them.
A small piece of state that a server sets for a user agent to return with qualifying HTTP requests according to scope and security attributes.
Correlation describes an observed association, while causation claims that changing one factor changes another under a defined intervention and context.
Cost of Delay estimates the economic or mission value lost while an initiative remains unavailable, reframing priority around time.
Counter metrics test whether improving a focal metric is producing an opposing cost, distorted behavior, or unintended decline elsewhere.
Crazy Eights is a timeboxed sketching exercise that asks each participant to explore eight distinct ideas in roughly eight minutes.
A structured method for eliciting detailed firsthand accounts of specific events that materially helped or hindered an outcome.
A network-scheduling method that identifies the sequence of dependent activities governing the earliest possible project completion date.
The critical rendering path is the browser work that turns a document's initial HTML, CSS, and JavaScript into visible pixels.
A task launched automatically according to a recurring time-based schedule.
A team combining the skills needed to discover, deliver, operate, and improve a shared product outcome.
A browser-controlled HTTP mechanism through which a server declares which origins may read selected cross-origin responses.
An attack that causes a user's browser to send an unwanted state-changing request carrying ambient credentials to another site.
A web vulnerability in which attacker-controlled content is interpreted as executable script or active markup within another site's trusted origin.
Crystal is a family of people-centered Agile methods tailored to team size, system criticality, communication needs, and local context.
The CSS Object Model is the set of browser interfaces and representations used to inspect and manipulate stylesheets and computed styling.
A cumulative flow diagram is a stacked area chart showing how the cumulative count of work items in each workflow state changes over time.
Customer acquisition cost measures the sales and marketing cost required to add a new paying customer within a defined scope and period.
Customer churn measures customers or accounts lost from an eligible base during a defined period, usually as a count or percentage.
A hypothesis-driven process for searching for customers and a repeatable business model before scaling execution.
Customer Effort Score measures how easy or difficult customers perceive a specific task, interaction, or service experience to be.
A customer journey map visualizes one person’s path toward a goal, including stages, actions, questions, emotions, channels, and opportunities.
Customer lifetime value estimates the economic value attributable to a customer relationship across its expected duration.
A proactive practice for helping customers achieve intended outcomes with a product while sustaining a healthy, mutually valuable relationship.
Cycle time measures elapsed time from the defined start of work on an item until that item reaches the workflow's defined finished point.
A decision-role framework that names a Driver, Approver, Contributors, and Informed participants for an important choice.
Counts of distinct users who perform a defined meaningful activity within daily, weekly, or monthly windows.
Dark patterns are deceptive or manipulative interface practices that impair informed choice and steer people toward outcomes they may not intend.
Data labeling assigns task-specific annotations to examples so models can be trained or evaluated against defined expectations.
Data leakage occurs when model development or evaluation uses information that would not legitimately be available for the intended prediction.
A data table organizes related records into rows and columns so users can scan, compare, sort, filter, and act on structured information.
Data-informed decision making combines relevant evidence with judgment, context, values, constraints, and accountability instead of letting a metric decide.
An organized store of persistent data managed so software can create, retrieve, update, protect, and recover information.
An auxiliary data structure that speeds selected database lookups and ordering at the cost of storage and additional write work.
A versioned, repeatable change that evolves database structure or data while preserving application correctness and recoverability.
The defined structure and integrity rules that describe how a database organizes and relates its stored data.
A database unit of work that groups operations so they commit together or are rolled back while concurrent work follows defined isolation rules.
A dataset card records a dataset's origins, composition, collection and labeling decisions, permitted uses, and limitations for informed reuse.
A date and time picker helps users enter temporal values through text, structured fields, calendar or clock controls, or a combination of these inputs.
An explicit allocation of who may decide, who contributes, and how unresolved product choices are escalated.
A shared quality standard that defines when an increment is complete and usable.
A team-defined set of conditions indicating that a work item is sufficiently understood to be considered for selection.
The deliberate transfer of responsibility and appropriate decision authority while the delegating leader retains overall accountability.
The practice of identifying, reducing, sequencing, and monitoring relationships that constrain independent product delivery.
Design annotation adds concise implementation-relevant notes to design artifacts so behavior, rules, states, and intent that are not visually obvious remain explicit.
Design critique is a structured conversation that evaluates work against stated goals and evidence to produce specific, actionable feedback.
Design debt is the accumulated cost and user harm created when short-term design compromises, inconsistencies, or neglected evidence remain unresolved.
Design documentation is maintained guidance that explains a product's design decisions, reusable rules, components, workflows, and evidence to its intended readers.
Design handoff is the collaborative transfer of product intent into implementation through shared context, inspectable specifications, decisions, and continuing review.
Design maturity describes how consistently an organization integrates user-centered evidence, skills, leadership, processes, and outcomes into decisions.
Design QA is the structured review of an implemented product against approved design intent, system rules, content, responsive behavior, and accessibility requirements.
Design rationale records the reasoning behind a product decision, including the question considered, alternatives examined, evidence used, and tradeoffs accepted.
A design review is a prepared checkpoint where the right people evaluate readiness, risks, evidence, and tradeoffs before a product decision advances.
A time-boxed workshop that aligns a team on a critical challenge, selects a concept, prototypes it, and tests it with target users.
A design studio is a facilitated workshop that combines individual sketching, shared critique, and refinement to explore a design problem.
A design system is a maintained set of principles, guidance, reusable assets, and coded components for producing coherent product experiences.
Design system governance defines how decisions are proposed, reviewed, owned, released, changed, and retired across a shared system.
A human-centered approach to ambiguous problems that combines empathy, reframing, ideation, prototyping, and learning through tests.
Design tokens are named, portable records of design decisions such as color roles, spacing, type, borders, and motion values.
DesignOps improves the people, processes, tools, governance, and working conditions that help design teams deliver quality work at scale.
A method for examining the qualities and impressions people associate with a product’s visual, verbal, or experiential presentation.
A product-risk lens asking whether people want a solution, the business can sustain it, the organization can build it, and people can use it.
The quality of developers' experience of the tools, systems, processes, culture, and collaboration involved in building and operating software.
A longitudinal method in which participants record experiences, events, or reflections close to when they occur over days or weeks.
Direct manipulation lets people act on visible interface objects with incremental, reversible actions and immediate feedback instead of abstract commands.
Disaster recovery prepares an organization to restore critical technology services and data after a severe, prolonged disruption.
Disciplined Agile is a context-sensitive toolkit for choosing and continuously improving ways of working across teams and value streams.
A flexible session script that translates research questions into a consistent flow of neutral topics, prompts, activities, and follow-ups.
The Document Object Model represents a web document as a tree of objects that browser code can inspect, change, and observe.
A distributed hierarchical naming system that resolves domain names into records used to locate and configure internet services.
An approach to complex software that builds evolving models from domain knowledge and aligns language, boundaries, code, and team collaboration.
Five software-delivery performance measures used together to examine change throughput and instability for an application or service.
Dot voting gives participants a limited number of votes to reveal preferences among a visible set of options during a workshop.
A four-phase framework for exploring a problem broadly, choosing a clear focus, exploring solutions, and delivering a tested response.
Drag and drop lets users move, copy, connect, or reorder an object by holding it through a pointer movement from a source to a destination.
A drawer is an edge-anchored panel for supplementary content or actions; a navigation drawer specifically contains destinations and may be persistent or temporary.
A product-development pattern in which discovery reduces value, usability, feasibility, and viability risks while delivery builds dependable solutions.
DSDM is a full-lifecycle Agile project-delivery method that fixes time, cost, and quality while varying lower-priority scope.
An integrated project-control method that compares planned value, earned value, and actual cost to assess cost and schedule performance against a baseline.
An ecosystem map visualizes actors, resources, relationships, incentives, flows, constraints, and power within a complex service or product system.
An embedding is a learned numeric vector that represents an item so that useful relationships can be compared mathematically.
An empathy map organizes evidence about what a user says, does, thinks, and feels to support shared understanding and reveal research gaps.
Durable cross-functional teams given strategic context, meaningful problems, and authority to discover solutions while remaining accountable for outcomes.
An empty state explains why useful content is absent and, when appropriate, gives people a clear path to create, find, restore, or configure it.
A cryptographic transformation that makes plaintext unreadable without the appropriate decryption key.
End-to-end testing exercises a complete product workflow across integrated parts to check an externally visible outcome.
A specific addressable interface location where a client can interact with a software service using defined operations and messages.
A cross-team community through which engineers share expertise, coordinate practices, and improve capabilities without replacing delivery-team ownership.
The practice of creating the people, delivery, and organizational conditions in which software engineering teams can succeed sustainably.
A living view of sequenced technical investments that connects engineering constraints and capabilities to product and organizational outcomes.
A large, coherent body of product work that is too broad for one delivery interval and is progressively split into smaller items.
An error budget is the amount of unreliability permitted by a service-level objective during its evaluation window.
Field error messages explain individual problems, while an error summary gives a linked overview of problems after submission.
Error prevention designs risky choices, inputs, defaults, and constraints so common mistakes are avoided before users need an error message.
Error rate measures the proportion of eligible operations that fail a defined success condition during a reporting window.
Error recovery helps people understand what failed, preserve their work, correct the problem, and confidently continue from a known state.
An immersive qualitative approach for understanding how people create meaning, routines, and social practices within a culture or community.
An attribute describing the context or details of one recorded event instance.
An event taxonomy is a governed naming and classification system for product events and properties, designed to keep behavioral data consistent.
An architectural style in which components publish facts about state changes and independent consumers react through asynchronous channels.
A consistency model in which replicas may temporarily disagree but converge after updates stop and propagation succeeds.
An approach that enables guided, incremental architectural change by protecting important system qualities with explicit, regularly evaluated fitness functions.
An experience map shows broad human activity across contexts, independent of one product, to reveal needs and opportunities beyond current touchpoints.
Product experimentation is a disciplined system for reducing uncertainty through hypotheses, appropriate tests, reliable measurement, and learning.
Explainability is the ability to provide people with meaningful, faithful information about how an AI system produces a result or behaves.
Exploratory testing combines learning, test design, and execution so each observation can guide the next investigation.
Extreme Programming combines rapid customer feedback with disciplined engineering practices such as pairing, testing, refactoring, and continuous integration.
Faceted navigation lets users narrow a collection by combining independent attributes such as type, topic, price, status, or location.
The extent to which eligible users discover, begin using, and repeatedly gain intended value from a specific product capability over time.
Runtime controls that change product behavior for selected contexts, allowing teams to separate code deployment from user-facing release decisions.
A suggestion from a customer, employee, or stakeholder to add or change product functionality.
The proportion of eligible users who return to perform a defined feature action after first using it.
Feature-Driven Development organizes model-informed software delivery around small, client-valued features designed and built in short cycles.
A system response that shows an action was received, what changed, and what can happen next.
An environment where people routinely exchange specific, useful observations and act on them across roles, levels, and moments of work.
Few-shot prompting supplies task demonstrations in a model's input, while zero-shot prompting asks for the task without demonstrations.
Research conducted in the natural setting of an activity to observe real behavior, tools, environments, interruptions, and constraints.
File upload lets users transfer one or more local files to a product with explicit selection, constraints, progress, validation, and recovery.
Fine-tuning adapts a pre-trained model by updating some or all of its parameters using task-specific examples or feedback.
A focused test of where participants click first when attempting a task, used to evaluate initial navigation cues and visual hierarchy.
The time to reach a target depends largely on its size and distance from the starting point.
A brief-exposure test used to learn what people notice, remember, and infer from a visual design after viewing it for about five seconds.
Flight Levels improves the flow of work across teams by connecting operational delivery, cross-team coordination, and strategy.
A floating action button is a prominent circular control that stays above content to expose one high-priority action for the current context.
Flow efficiency compares active working time with total elapsed flow time to show how much of an item's journey is spent being worked rather than waiting.
Focus appearance makes the currently keyboard-focused control visually distinguishable across its states and surrounding backgrounds.
A moderated group discussion used to explore shared language, attitudes, expectations, and contrasting perspectives on a focused topic.
Focus management deliberately controls where keyboard focus moves, remains, and returns as an interface changes.
Focus order is the sequence in which keyboard navigation reaches interactive elements, preserving meaning and operability as users move through an interface.
Form design structures questions, controls, guidance, and actions so people can provide information accurately and efficiently.
Form field anatomy combines a control with its label, guidance, requirement state, and feedback to create one understandable input unit.
Form validation checks whether submitted or entered data meets defined requirements and helps users correct problems without losing valid work.
A distinction between evaluation used to improve a design and evaluation used to judge overall performance against a reference point.
A foundation model is a broadly trained model that can be adapted or prompted for many downstream tasks rather than built for only one narrow purpose.
Time-limited or usage-limited access that lets prospective customers evaluate a paid product before being charged.
Freemium offers an enduring free version of a product while charging for premium capabilities, capacity, control, or service.
A division between the user-facing software that presents and collects information and the server-side software that applies shared rules and manages protected resources.
A requirement describing a capability or behavior a product must provide in response to defined conditions.
Funnel analysis measures how eligible users progress through a defined sequence of events and where they stop or diverge.
The Gabor-Granger method asks about purchase intention at selected prices to estimate a demand curve for a fixed offering.
A time-scaled visual schedule that represents project activities as horizontal bars and can show dates, durations, milestones, dependencies, and progress.
Generative AI uses learned patterns to produce new text, images, audio, video, code, or other content in response to input.
A distinction between research that explores problems and opportunities and research that assesses a proposed or existing solution.
Perceptual grouping principles that explain how people organize visual elements into coherent wholes.
A coordinated plan for reaching a defined market, communicating value, delivering the product, and creating a repeatable path to adoption and revenue.
A typed API query language and execution model that lets clients request the fields and relationships they need.
A grid system provides shared columns, gutters, margins, and spacing rules that align interface content while adapting to available space.
Gross margin measures the share of revenue remaining after the costs classified as delivering the product or service.
Gross merchandise value measures the transaction value passing through a marketplace over a defined period, rather than platform revenue.
Gross revenue retention measures how much of a starting recurring-revenue base remains after churn and contraction, excluding expansion.
Grounding constrains or connects an AI output to relevant evidence, data, rules, or observed state available for the task.
Growth loops model systems in which the output of one cycle becomes an input that can generate additional users, content, inventory, or value.
A portfolio framework that compares relative market share with market growth to prompt investment, harvesting, repositioning, or exit discussions.
Guardrail metrics protect important product qualities by revealing unacceptable harm while a team optimizes a primary outcome or tests a change.
A one-way computation that maps input data to a fixed-length digest used for integrity, identification, and specialized secret verification.
Google’s HEART framework organizes user-experience measurement around Happiness, Engagement, Adoption, Retention, and Task success.
A structured expert review in which evaluators inspect an interface against recognized usability principles and document likely problems.
Decision time generally increases as the number and uncertainty of choices increase.
Horizontal scaling changes the number of resource instances, while vertical scaling changes the capacity of an individual instance.
A how-might-we question turns an evidenced user problem into an open design challenge that allows several possible solutions.
The application-level request-response protocol that defines shared semantics for transferring representations and operating web systems.
The request token that states the intended operation on an HTTP resource and carries standardized safety, idempotency, and caching semantics.
A three-digit response code that communicates the standardized outcome class and handling semantics of an HTTP request.
Human in the loop assigns people a defined role in reviewing, correcting, approving, or interrupting an AI system at meaningful points in its operation.
Human–AI interaction designs how people understand, direct, evaluate, correct, and recover from systems whose behavior is adaptive or uncertain.
Hydration attaches client-side application state and interaction behavior to HTML that was rendered before the browser application started.
A practice that expresses product ideas as falsifiable beliefs about users, changes, and outcomes, then uses evidence to guide design decisions.
UI iconography uses a coherent set of visual symbols to support recognition, actions, navigation, and status without relying on pictures alone for meaning.
The systematic practice of capturing, developing, evaluating, and deciding on ideas and opportunities before substantial investment.
An ideal customer profile describes the account or customer type most likely to gain strong value from an offering and support a healthy business relationship.
The property that repeating the same operation has the same intended effect as performing it once.
A collaborative planning method that links a measurable goal to actors, desired behavior changes, and possible product deliverables.
An impact–effort matrix maps options on two axes to expose quick wins, major bets, low-value tasks, and costly distractions.
Incident management is the coordinated practice of detecting, containing, communicating, and learning from service disruptions.
Inclusive design is a process that recognizes exclusion, learns from human diversity, and creates adaptable solutions with affected people.
Designing recruitment, materials, environments, methods, and participation so people with relevant access needs and varied circumstances can contribute equitably.
A usable, verified addition to a product that meets the Definition of Done and advances its Product Goal.
IndexedDB is an asynchronous, transactional browser database for storing and querying significant amounts of structured origin-scoped data.
Inference cost measures the expense of running a trained model for a defined workload, with its unit and accounting boundary stated explicitly.
Infinite scroll progressively loads more items as a user approaches the end of a collection, replacing explicit page-by-page navigation.
Information architecture organizes and connects content so people can understand what exists, where to find it, and what to do next.
Information scent is the strength of the cues that help users predict whether a link, label, or result will move them toward their goal.
The ongoing process of ensuring participants understand a study, its data use, risks, and their voluntary right to stop or withdraw.
Inline editing lets users switch content from a read state to an editable control in place, preserving the surrounding context.
A measurement discipline for judging progress in uncertain ventures through assumptions, cohorts, learning milestones, and investment decisions.
An instrumentation plan specifies the data a product must emit to answer priority questions, including event logic, properties, ownership, and validation.
Integration testing checks whether connected components exchange data and behave correctly across their actual boundaries.
Interaction design shapes how people act with a product over time, connecting goals, controls, feedback, system state, and recovery into a coherent experience.
Interaction patterns are reusable arrangements of controls, behavior, feedback, and user expectations for recurring interface problems in a defined context.
Interaction states describe a control's current condition, such as default, hover, focus, pressed, selected, disabled, loading, or invalid.
Internationalization prepares a product’s architecture and content handling so it can support different languages and regional conventions.
Six diagnostic qualities—Independent, Negotiable, Valuable, Estimable, Small, and Testable—for improving user stories and backlog items.
A controlled record of current problems, questions, or decisions affecting delivery, with ownership, priority, actions, due dates, and resolution evidence.
A JavaScript bundle is a build output that packages application modules and dependencies into one or more files for browser delivery.
A contextual requirements statement that connects a triggering situation, a person’s motivation, and the outcome they seek without relying on demographic personas.
A lens for understanding the progress people seek in particular circumstances and why they choose, switch, or reject products and services.
A text-based data-interchange syntax for representing objects, arrays, strings, numbers, booleans, and null across software systems.
A compact claims format that can be digitally signed or authenticated and optionally encrypted for transfer between parties.
An evolutionary management method that visualizes knowledge work, limits work in progress, manages flow, and improves an existing service through feedback.
The Kano model studies how different product attributes influence satisfaction, from basic expectations to attractive surprises.
A key performance indicator is a deliberately selected measure used to judge progress toward an important objective or expected level of performance.
Keyboard accessibility enables every interactive function to be reached and operated through keyboard input without traps or pointer-only actions.
Keyboard shortcuts provide efficient key combinations for frequent commands while preserving visible controls and avoiding conflicts with platform or assistive-technology behavior.
Labeling systems use consistent words and naming rules to represent categories, destinations, actions, and concepts across a product.
A large language model is a high-capacity model trained on token sequences to predict and generate language, often with capabilities that transfer across many tasks.
Large-Scale Scrum applies Scrum to multiple teams working on one product while deliberately minimizing added roles, artifacts, and coordination layers.
Latency measures elapsed time between a defined start and response point, exposing the delays users experience while a system works.
Lazy loading defers a non-critical resource or feature until it is likely to be needed instead of loading it during the initial experience.
Lead time measures elapsed time from a request or commitment point until delivery, capturing both queue time and time spent actively completing the work.
Leading indicators move early enough to guide action, while lagging indicators confirm outcomes after the relevant behavior or process has occurred.
Lean Canvas is a one-page, startup-focused model for connecting customer problems, proposed solutions, channels, economics, and advantage.
A collaborative approach to product design that treats ideas as hypotheses, favors outcomes over deliverables, and learns through small experiments.
A listbox presents selectable options with single- or multi-selection behavior, while multi-select patterns must also make the full selection set manageable and clear.
LLM-as-a-judge uses a language model to score or compare outputs against an explicit evaluation rubric.
A component that distributes incoming traffic across eligible service instances or locations.
Load testing evaluates system behavior under a defined workload to check whether expected demand can meet performance goals.
A loading state communicates that work is in progress, preserves context, and sets an honest expectation while content or an operation is not ready.
Localization adapts a product’s language, content, and regional conventions for a specific audience or locale.
Loss aversion describes situations in which a loss relative to a reference point carries more psychological weight than a comparable gain.
The LTV:CAC ratio compares estimated customer lifetime value with the cost of acquiring a customer for the same segment and cohort.
Machine learning is an approach in which a model learns patterns from data to make predictions or generate outputs rather than following only hand-written rules.
The relationship between a control, the action it performs, and the result users expect.
Market segmentation divides a broad market into meaningful groups whose shared needs, circumstances, or behavior support distinct product and go-to-market choices.
Market sizing estimates the number or value of potential customers and transactions within explicit boundaries, assumptions, units, and time periods.
A platform that enables distinct participant groups to discover, evaluate, and transact or interact with one another.
The marketplace’s ability to produce suitable, timely matches or transactions for participants who seek them.
MaxDiff estimates relative preferences by asking respondents to choose the most and least preferred items from repeated subsets.
A person’s internal explanation of how a system works and what will happen when they act.
A menu presents a compact list of commands or choices, while a menu button is the control that opens and closes that menu.
Infrastructure that accepts messages and applies routing, delivery, and protocol rules between producing and consuming systems.
A durable buffer from which consumers claim messages, allowing producers and workers to operate at different times and rates.
A meter or gauge displays a current numeric value within a meaningful bounded range, such as capacity or level, rather than task completion.
A metric tree maps a high-level product or business outcome into component measures and hypothesized drivers that teams can diagnose and influence.
Microcopy is the short, contextual text that explains controls, sets expectations, prevents errors, and helps users recover within an interface.
An architectural style that divides a system into independently deployable services aligned to cohesive business capabilities and owned end to end.
A minimum detectable effect is the smallest effect an experiment is designed to detect with specified power, error control, and assumptions.
The smallest coherent product release designed to create an intentionally satisfying experience, not merely functional tolerance, for a focused early audience.
The smallest product experiment that can deliver a meaningful experience to early users and generate validated learning about a critical business assumption.
A whole-team collaboration practice in which several people work together on one problem through a single active development environment.
A mockup depicts an interface’s proposed appearance and content so people can review visual decisions without a working implementation.
A modal dialog is an overlaid window that temporarily blocks interaction with the underlying interface until the user responds or dismisses it.
A model card documents a specific model's intended uses, evaluation evidence, limitations, and operating conditions so others can assess whether to use it.
Model Context Protocol standardizes how AI applications discover and exchange tools, resources, and reusable prompts with external servers.
Model drift describes changes in deployment data or relationships that can make a previously evaluated model less suitable over time.
Model evaluation is the ongoing practice of measuring whether an AI system performs its intended product task acceptably across representative and risky conditions.
Model inference is the runtime process of applying a trained model to new input to produce a prediction, score, embedding, or generated output.
A single deployable application organized into strongly bounded business modules with explicit interfaces and controlled dependencies.
Monte Carlo forecasting repeatedly samples historical delivery data to estimate probability ranges for how much work may finish or when a body of work may complete.
Monthly recurring revenue normalizes predictable subscription revenue into a monthly amount for tracking the recurring base and its movement.
MoSCoW sorts requirements into Must, Should, Could, and Won’t-have-for-now groups to protect a viable delivery scope.
Motion design uses purposeful change over time to explain relationships, provide feedback, and preserve orientation without delaying tasks or causing discomfort.
A multi-armed bandit repeatedly selects among options while balancing learning about uncertain choices with using choices that currently perform well.
An authentication approach requiring proof from at least two distinct factor categories to increase confidence in the claimant.
A multi-page application uses browser document navigation to request and load a new HTML document for each primary route transition.
A multimodal model processes or generates more than one kind of data, such as text, images, audio, or video, within a connected model experience.
Multivariate testing evaluates combinations of changes to multiple factors so teams can estimate component and interaction effects under a factorial design.
Mutation testing introduces small artificial code changes to evaluate whether existing tests detect the resulting behavior differences.
The percentage of a starting cohort that returns on a specified day or period number after its initial event.
Navigation design creates visible, predictable paths that help users understand their location, available destinations, and next steps.
Net Promoter Score summarizes responses to a recommendation-likelihood question by subtracting detractors from promoters.
Net revenue retention measures recurring revenue retained from a starting customer group after expansion, contraction, and churn.
A dynamic in which a product’s value to a participant changes as participation in the relevant network changes.
Nexus minimally extends Scrum so several teams can manage dependencies and produce one integrated, valuable product increment every Sprint.
Testable requirements that describe system qualities and operating constraints such as reliability, security, performance, usability, and maintainability.
A North Star Metric is a durable product-level measure intended to represent recurring value delivered to customers.
A broad family of non-relational database systems designed around models such as key-value, document, wide-column, or graph data.
A roadmap format that groups priorities into three confidence horizons instead of assigning speculative dates to distant work.
Null and alternative hypotheses specify the statistical comparison a test evaluates and the effect pattern it is designed to detect.
A delegated authorization framework that lets a client obtain limited access to protected resources without receiving the resource owner's credentials.
Object-oriented UX models a product around the meaningful objects users recognize, their attributes, relationships, and available actions.
Objectives and Key Results connect a meaningful qualitative goal with measurable outcomes that show whether progress actually occurred.
Observability is the ability to understand a system’s internal state and behavior from the telemetry and context it exposes.
A recurring private conversation between a manager and team member focused on context, support, feedback, growth, and the working relationship.
The door framework matches decision rigor and authority to reversibility, treating costly one-way commitments differently from recoverable two-way choices.
An ontology formally defines the concepts in a domain, their properties, and the relationships and rules that connect them.
An identity layer built on OAuth 2.0 that lets a client verify an end user's authentication and receive standardized identity claims.
A deliberate rhythm of recurring decisions, reviews, planning, and information sharing that helps an organization operate predictably.
A meaningful unmet need, problem, or favorable change that a product could address.
Opportunity scoring compares the importance of customer outcomes with satisfaction with current solutions to identify underserved needs.
A visual decision map connecting a target outcome to customer opportunities, possible solutions, and the tests used to compare assumptions.
Optimistic UI shows the expected result before a server confirms it, then reconciles success, correction, or rollback without hiding uncertainty.
The strategic value of preserving a future choice when uncertainty is high and commitment would be costly or difficult to reverse.
A structured practice for helping an organization move from a current way of working to a desired state while managing operational and human consequences.
Separated groups, information, or incentives that limit coordination across the work needed to create a product outcome.
Orientation accessibility allows people to use content in portrait or landscape without an unnecessary author-imposed restriction.
A roadmap organized around measurable changes in customer or business behavior rather than predetermined feature output.
A distinction between what a team produces, the change in user or system behavior, and the wider result that change contributes to.
A p-value measures how incompatible observed data are with a specified statistical model, often including a null hypothesis.
The practice of deciding which product capabilities, limits, services, and entitlements are sold together to particular customers.
The division of a large ordered result set into bounded portions that clients retrieve incrementally.
A collaborative practice in which two developers work on the same problem together, continuously reviewing and shaping the code.
The practice of finding, screening, inviting, and supporting people whose experience is relevant to a research question.
A collaborative design approach that gives people affected by a product meaningful influence over how problems are framed and solutions are shaped.
A password input accepts a secret while supporting password managers, paste, clear requirements, controlled reveal, validation, and safe handling.
A pattern library documents reusable solutions to recurring user tasks, often combining multiple components with content and flow guidance.
The peak-end rule describes how intense moments and the ending of an experience can disproportionately influence its remembered evaluation.
A performance budget sets explicit limits on measurable performance indicators or resource costs so teams can control regressions during delivery.
A three-point estimation method that combines optimistic, most likely, and pessimistic durations to represent uncertainty in project activities.
A bounded real-world implementation used to test whether a product, service, or operating model can deliver intended outcomes before broader rollout.
A trial run of a research procedure used to find and correct problems before the main study begins.
Pirate Metrics groups startup funnel measures into Acquisition, Activation, Retention, Referral, and Revenue: AARRR.
Plain language communicates necessary information in words, sentences, and structures that the intended audience can understand and use.
The practice of building and operating internal platforms as products so delivery teams can use reliable capabilities with less cognitive load.
A team that provides internal capabilities and tools enabling other teams to deliver product value with less repeated effort.
Pointer gestures use movement, direction, duration, or multiple contact points to control an interface and require simple alternatives for essential functions.
A popover is a transient surface positioned in relation to a trigger that provides contextual information or controls without permanently occupying the layout.
Practical significance judges whether an estimated effect is large enough to matter for a real product decision, regardless of whether it passes a statistical threshold.
Precision measures how many predicted positives are correct, while recall measures how many actual positives a system finds.
Pretotyping uses deliberately minimal simulations to collect behavioral evidence about whether people want an idea before the team builds a functioning product.
Pricing strategy defines how a business sets and evolves prices, packaging, metrics, and terms to support customer value and business goals.
Probability calibration describes how closely a model's predicted probabilities match observed outcome frequencies across comparable predictions.
The practice of defining which problem a team will address, for whom, in what context, and with what outcome and constraints.
Evidence-based investigation of whether a meaningful problem exists for a defined group and is worth addressing.
Early evidence that a specific customer problem matters and that a proposed value proposition plausibly addresses it better than relevant alternatives.
Product analytics uses behavioral and operational data to understand how people experience a product and to inform improvement decisions.
An emergent, ordered list of work that may improve a product and serves as the Scrum Team’s single source of planned work.
A single, ordered unit of work or value recorded in a product backlog.
A portfolio practice that treats major product investments as explicit, bounded wagers with uncertain outcomes and reviewable evidence.
A short, problem-focused document that frames a product opportunity, its intended users, strategic value, evidence, assumptions, constraints, and success signals.
Product design shapes how a product addresses user needs through its capabilities, interactions, content, and form within real constraints.
The work of reducing uncertainty about which customer problems and product solutions are valuable, usable, feasible, and viable before scaling.
A recognizable product capability or characteristic designed to help users accomplish something or receive value.
A future state that gives a product team a shared objective and context for ordering work.
Measurable, time-bounded changes in customer or business outcomes that translate product strategy into focused team direction.
The system of authority, controls, evidence, and review used to keep product decisions aligned with strategy, obligations, and acceptable risk.
A testable statement about how a product change is expected to create a measurable user or business result.
A coordinated, strategic body of product work that groups multiple efforts toward a shared objective or outcome.
The coordinated introduction of a product or major change to a target market, supported by readiness checks, communication, delivery, and learning.
The practice of setting product context, developing people and teams, shaping organizational conditions, and holding a product portfolio accountable for outcomes.
A model for understanding how a product’s market position, evidence, investment needs, and management priorities change from inception to retirement.
The discipline of guiding a product toward sustained customer and business value through evidence, strategy, decisions, and coordinated learning.
A role accountable for helping a product team create customer and business value by providing context, judgment, alignment, and evidence-based direction.
A cross-functional practice that builds market understanding, positioning, messaging, launch readiness, and adoption for a product and its audiences.
A way of thinking that treats product work as an ongoing search for customer and business outcomes through collaboration, evidence, and adaptation.
An organization-wide system for deciding which product problems matter, empowering teams to solve them, and delivering measurable outcomes repeatedly.
The discipline of improving the systems, data, tools, and routines that help product teams make decisions and operate effectively at scale.
A lightweight evaluation of whether a product opportunity merits deeper discovery or investment and what success would require.
The person accountable for maximizing product value through direction and effective management of the product backlog.
A deliberate change to a core product or business-model hypothesis that preserves useful learning while seeking a more viable direction.
The ongoing practice of selecting, balancing, funding, and reviewing products and major investments as one strategic system.
Product positioning defines the market context, audience, distinctive value, and credible reason a customer should choose a product over alternatives.
A small set of memorable decision rules that translate product strategy and learned values into guidance for recurring tradeoffs.
A documented condition, capability, or constraint a product must satisfy to address a need or objective.
A living document that aligns a cross-functional team on a product initiative’s purpose, users, scope, requirements, constraints, and measures of success.
A continuous process for identifying, assessing, treating, and monitoring uncertainty that could harm customers, the organization, or product outcomes.
A strategic communication artifact that connects product direction and desired outcomes to a changing sequence of investments.
The agreed boundary of the capabilities, qualities, users, contexts, and exclusions that characterize a product or product change.
A coherent set of choices about where and how a product will create distinctive customer value while advancing important business objectives.
A layered model connecting purpose, strategic choices, product goals, bets, and delivery evidence so decisions remain coherent across horizons.
The managed retirement of a product, feature, service, or version while reducing harm and helping affected people transition.
A concise, testable argument explaining why a particular product direction should create customer and business value under stated conditions.
A small cross-functional leadership group—commonly product, design, and engineering—that jointly guides discovery within a product team.
A concise, durable description of the positive future a product seeks to create, for whom it matters, and why the direction is worthwhile.
Product-led growth is a strategy in which the product experience is a primary driver of acquisition, activation, conversion, expansion, and advocacy.
A condition in which a defined market repeatedly chooses, uses, and values a product strongly enough to support sustainable traction.
A product-market fit survey asks experienced users how they would feel without a product and investigates the value behind their answers.
A progress indicator communicates that work is underway and, when measurable, how much of the operation is complete.
Progressive disclosure presents essential information and actions first, revealing secondary or advanced detail when users request or need it.
A progressive web app is a website enhanced with installable, resilient, and operating-system-integrated capabilities where browsers support them.
A concise authorization document that establishes why a project exists, who sponsors it, what success means, and what authority the project manager holds.
A project premortem imagines that an initiative has already failed and works backward to expose plausible causes while preventive action is still possible.
A prompt is the input context supplied to a generative model to communicate a task, evidence, constraints, examples, or desired output.
Prompt engineering is the systematic practice of designing, testing, and maintaining model inputs to improve behavior on a defined set of tasks.
Prompt injection is an attack in which untrusted input influences a model to disregard intended instructions, expose information, or misuse connected capabilities.
Property-based testing checks general rules across generated inputs, helping expose edge cases that hand-picked examples can miss.
A prototype is a selective representation of a proposed product used to explore an idea, test an assumption, or communicate behavior.
Prototype fidelity is the intentional degree of realism applied to selected dimensions of a prototype so it can answer a specific product-design question efficiently.
A shared belief that people can raise questions, admit mistakes, offer ideas, and challenge assumptions without interpersonal punishment.
A messaging pattern in which publishers send to a topic and each interested subscription receives its own copy.
A distinction between evidence used to understand patterns and mechanisms in depth and evidence measured to estimate magnitude, frequency, or difference.
A recurring planning cycle that translates strategy and current evidence into a focused set of product outcomes and investments for a quarter.
A responsibility-assignment matrix that marks who is Responsible, Accountable, Consulted, and Informed for defined work.
A consolidated control log for tracking risks, assumptions, issues, and dependencies that can affect project or programme delivery.
Randomization assigns eligible units to conditions by chance so that groups are comparable before the intervention on average.
The controlled restriction of how many operations an actor may perform within a defined scope and time window.
A rating component lets users assign an ordered score or displays an aggregate score using a bounded visual scale.
A usability principle that favors visible choices and cues over requiring users to retrieve information from memory.
A recommender system selects and ranks items to help a user discover options likely to be useful in a particular context.
A recovery point objective sets the maximum acceptable age of recoverable data after disruption, expressing the tolerated data-loss window.
A recovery time objective sets the maximum acceptable interval between a service disruption and restoration of an agreed usable service.
Reduced motion design removes or substitutes nonessential movement when users request less animation through system or product preferences.
Redundancy provides alternative components or capacity, while failover transfers service to those alternatives when a failure occurs.
The disciplined improvement of existing code structure through small behavior-preserving changes that make future work safer and clearer.
A referral program systematically encourages existing customers or partners to introduce qualified new customers, sometimes using incentives.
Reflow and zoom ensure content can enlarge and adapt to a narrow viewport without losing information, controls, or requiring two-dimensional scrolling for ordinary reading.
Regression testing checks that a change has not unintentionally broken behavior that previously worked.
Regression to the mean is the tendency for unusually high or low measurements to be followed by values closer to their typical level when random variation contributes.
A database model that represents data as relations, commonly exposed as tables whose keys and constraints express structure and integrity.
A user-facing record of product changes that explains what changed, who is affected, why it matters, and any action or limitation readers should know.
The collaborative practice of defining a release goal, viable scope, forecast, dependencies, readiness criteria, and learning plan.
An architectural style for networked systems that constrains interactions around resources, representations, stateless messages, and a uniform interface.
An interaction model in which a client sends a message asking for an operation and a server returns a message describing the outcome.
A classification of business, stakeholder, solution, and transition requirements that connects the reason for change to needs, product behavior, and adoption.
The iterative examination and modeling of needs and requirements to make them coherent, feasible, valuable, and decision-ready.
An approved, version-controlled set of requirements used as a reference for design, verification, contracts, and controlled change.
The collaborative practice of drawing out and confirming needs, constraints, rules, and knowledge relevant to a proposed change.
The ongoing practice of organizing, maintaining, tracing, prioritizing, and governing requirements as needs and solutions evolve.
The ongoing practice of ordering requirements using value, urgency, risk, dependencies, cost, and stakeholder consequences.
The ability to follow relationships from needs and requirements through designs, implementation, tests, releases, and outcomes in both directions.
Complementary checks that requirements are well formed and usable for development, and that they represent the right stakeholder and business needs.
The controlled handling of participant details, notes, recordings, transcripts, and outputs across collection, access, retention, sharing, and deletion.
Compensation offered for a participant’s time, effort, expenses, or expertise without making participation or favorable answers coercive.
The people, processes, tools, and governance that make responsible research easier to conduct, scale, share, and sustain.
A focused statement of what a study needs to learn so the team can choose suitable evidence and make a defined decision.
The possibility that being studied, observed, prompted, or placed in a research setting changes participant behavior or responses.
A research repository organizes studies, evidence, and contextual metadata so teams can find, evaluate, and responsibly reuse what the organization has learned.
A context-dependent judgment that further qualitative data collection is adding insufficient new information or meaning for a study’s analytic purpose.
A short questionnaire or script used to determine whether a prospective participant meets a study’s relevant inclusion and exclusion criteria.
Criteria for judging whether research supports the intended conclusion and whether its measurement or procedure is sufficiently consistent.
A product-management practice that integrates human rights, inclusion, privacy, safety, sustainability, and long-term effects into ordinary decisions.
Responsive design uses fluid layout, flexible media, and conditional rules so one interface adapts continuously across viewport sizes and capabilities.
Retention rate is the share of a defined starting cohort that remains active, subscribed, or otherwise retained at a later time.
Retrieval-augmented generation combines information retrieval with generation so a model can answer using selected external evidence at request time.
A recurring team reflection that examines how work happened, identifies a meaningful improvement, and turns learning into a concrete experiment or action.
A controlled repeat attempt for an operation that failed in a way likely to be temporary.
RICE ranks product initiatives by combining estimated reach, impact, confidence, and effort in a comparable score.
A rich text editor lets users create structured, formatted content through an editable canvas and authoring controls.
A maintained record of identified uncertainties, their potential effects, assessments, owners, planned responses, actions, and residual exposure.
A focused experiment that tests the assumption most likely to invalidate a product direction if it proves false.
The practice of explaining product direction, priorities, uncertainty, and change to different audiences without turning plans into false promises.
An access-control model that assigns permissions to roles and assigns users or service identities to those roles.
A runbook documents a repeatable operational procedure with prerequisites, ordered actions, verification, and escalation guidance.
Runway estimates how long available cash can support a business under stated spending, collection, and financing assumptions.
A coordinated practice that gives customer-facing sellers the knowledge, content, tools, coaching, and processes needed to help buyers make sound decisions.
A browser security boundary that restricts how documents and scripts from one origin can interact with resources from another origin.
Sample ratio mismatch is a statistically unlikely difference between an experiment’s intended allocation and its observed assignment or exposure counts.
Sample size is the number of independent analysis units included in a study or experiment, chosen to support a stated precision or detection goal.
The deliberate selection of participants or cases whose evidence can support a research question within stated boundaries.
Sampling temperature adjusts how strongly a generative model favors higher-scoring next tokens when sampling an output.
Scalability is a system’s ability to support growing workload while maintaining agreed performance and acceptable resource costs.
SAFe coordinates strategy, portfolio decisions, and multi-team product delivery through a structured Lean-Agile operating model.
A structured method for exploring several plausible futures and testing whether strategy remains useful across uncertainty.
The uncontrolled expansion of product or project scope without corresponding decisions about value, cost, time, capacity, or risk.
Screen reader design creates meaningful structure, names, states, order, and feedback that assistive technology can present nonvisually.
A lightweight framework in which a small, self-managing team delivers usable increments, inspects results, and adapts its plan around a Product Goal.
Scrum@Scale uses modular Scrum-based coordination cycles to align networks of teams while aiming for a minimum viable bureaucracy.
Search design helps users express an information need, understand system feedback, and refine results into a useful answer or destination.
A pricing model that charges according to the number of licensed users or seats with access to a product.
The controlled lifecycle for creating, storing, distributing, using, rotating, auditing, and revoking credentials and cryptographic keys.
A segmented control presents a small set of adjacent, mutually related options for switching a value, mode, or compact view.
Selects and comboboxes let users choose from allowed values, but a combobox adds a popup and may support text entry, filtering, or autocomplete.
Semantic HTML uses elements according to their defined meaning so browsers and other tools can understand content structure and behavior.
Semantic search retrieves items using learned representations of meaning or intent rather than relying only on exact keyword overlap.
Sequential testing evaluates accumulating experiment data with stopping rules designed to preserve statistical error guarantees across repeated looks.
The tendency to remember items near the beginning and end of a sequence better than those in the middle.
Server-side rendering generates a route's HTML in a server environment and sends it to the browser as the navigation response.
A service blueprint connects a customer journey to frontstage interactions, backstage work, support processes, evidence, and operational ownership.
Service design coordinates people, processes, touchpoints, and supporting systems so an organization can deliver a coherent user experience.
A service worker is an event-driven browser worker that can control requests and provide offline or background behavior for pages in its scope.
A service-level agreement is a formal commitment between provider and customer that defines service expectations and consequences for shortfalls.
A service-level indicator is a quantitative measure of service behavior that represents an aspect of reliability experienced by users.
A service-level objective sets a target value for a service-level indicator over a defined period, expressing the intended reliability level.
A bounded continuity context that associates a sequence of interactions with authenticated state and other server-recognized information.
A product-development method that shapes bounded pitches, bets on selected work, and gives small teams fixed time with flexible scope to deliver.
A perceivable cue that communicates where an action can happen and what action is likely.
An identity arrangement that lets a user authenticate through a shared authority and access multiple applications without separate sign-ins.
A single-page application loads a document shell and handles later views and navigation mainly through client-side JavaScript.
Site reliability engineering applies software engineering to operations so teams can run dependable services while continuing to change them.
A skeleton screen reserves the shape of forthcoming content to signal progressive loading and reduce disruptive layout shifts during an initial fetch.
A skip link lets keyboard users bypass repeated interface blocks and move directly to an important page region.
A slider selects an approximate value along a bounded scale, while a range slider uses two values to define an interval.
Smoke testing runs a small set of critical checks to determine whether a build or deployment is functional enough for further use or testing.
Social desirability bias occurs when people report answers that present them favorably rather than accurately describing their views or behavior.
Evidence-based testing of whether a proposed solution helps target users and can satisfy important product constraints.
A multidimensional framework for understanding developer productivity across satisfaction, performance, activity, communication, and efficiency.
A short, timeboxed investigation or prototype used to answer a specific question and reduce uncertainty before a delivery decision.
A numeric input accepts typed numbers, while a spinbutton adds controls and keyboard behavior for stepping through a bounded or discrete numeric range.
A split view shows related panes together, while a window splitter is the operable divider that lets users change their relative size.
The Sprint Goal, selected Product Backlog Items, and actionable delivery plan maintained by Developers during a Sprint.
A single objective for a Scrum Sprint that gives selected work coherence while preserving flexibility in how the team achieves it.
The Scrum event in which the whole team establishes why the Sprint is valuable, what it can accomplish, and an initial plan for doing the work.
A collaborative Scrum event where the team and stakeholders inspect the Sprint’s outcome, discuss changing conditions, and adapt what to do next.
A declarative language for defining, querying, changing, and controlling data in relational database systems.
A senior individual-contributor role that creates technical and organizational leverage across a team, domain, or multi-team initiative.
A product-innovation process that separates cross-functional development stages with evidence-based investment gates and go, hold, recycle, or stop decisions.
A deliberate practice for understanding, involving, and communicating with people who influence a product or are affected by its outcomes.
A stakeholder map identifies people and groups who affect or are affected by a decision, then makes relationships, power, interests, and engagement visible.
Static site generation renders routes into deployable HTML files before requests arrive, usually during a build or publishing process.
Statistical power is the probability that a specified test detects an effect of a specified size when that effect exists under its assumptions.
Statistical significance describes how incompatible observed data are with a specified statistical model, not whether a product result is important or true.
A step indicator communicates position in a staged task, while the multi-step flow defines the sequence, navigation, validation, and saved state behind it.
A ratio comparing active users in a shorter period with active users in a longer period to describe usage frequency.
A method for dividing a large user story into smaller, independently useful slices that preserve observable value and learning.
A storyboard uses a short sequence of scenes to show a person’s context, actions, and experience with a proposed product or service.
An incremental modernization method that routes selected capabilities to new implementations until the legacy system can be reduced or retired safely.
Explicit, consequential investment choices based on a theory of advantage, named assumptions, and evidence-based commitment stages.
A shared account of how the environment is changing, what becomes newly important, and why the organization’s chosen direction is credible.
The strategy kernel connects a diagnosis of the central challenge to a guiding policy and a coherent set of reinforcing actions.
Structured output constrains or validates model responses against a defined machine-readable shape so software can process them more safely.
Subresource Integrity lets a browser check a fetched resource against an expected cryptographic digest before using it.
A business model in which customers pay recurring fees for continuing access to a product or service.
A summary list presents related key–value facts for review, often with actions that let users change individual values.
The practice of creating questionnaires and sampling plans that measure attitudes, experiences, or characteristics with controlled sources of error.
A distinction between waiting for work to finish in the current interaction and allowing it to complete independently later.
Synthetic data consists of artificially generated records or examples created to support a defined testing, analysis, or model-development purpose.
A system prompt is an application-supplied instruction layer that sets intended model behavior, context, and constraints across an interaction.
The System Usability Scale is a standardized ten-item questionnaire that produces a perceived-usability score from 0 to 100.
A tab bar provides persistent navigation among a small set of top-level application sections while preserving each section’s place and state.
Tabs are a set of peer controls that switch between related content panels while keeping one panel visible at a time.
Take rate measures the share of marketplace transaction value captured as platform revenue under a specified revenue definition.
TAM, SAM, and SOM separate the broad demand for a solution from the portion a business can serve and the share it might realistically obtain.
A target market is the customer group a company deliberately chooses to serve with a coordinated product, positioning, channel, and commercial strategy.
The systematic study and representation of the actions, decisions, information, tools, and constraints involved in achieving a user goal.
A task list helps users plan and resume a long service by showing its meaningful tasks and the status of each one.
Task success rate is the proportion of observed task attempts that meet a predefined, verifiable success criterion.
A taxonomy is a governed system of categories and terms used to classify content consistently and support browsing, filtering, and retrieval.
A jointly created document that clarifies a team’s purpose, boundaries, membership, decision rights, commitments, and measures of success.
The mental effort a team must spend understanding and coordinating the systems, domain, and responsibilities it owns.
An adaptive organizational-design approach that uses four team types and three interaction modes to improve flow and manage cognitive load.
Team velocity is the amount of estimated or counted work one team completes within an iteration, interpreted from that team's recent history.
A way to describe design or implementation choices that provide near-term benefit while increasing the cost or risk of future software change.
The practice of guiding technical direction and execution through judgment, communication, coordination, and the growth of other engineers.
A coherent set of technical choices and investment principles that explains how technology will support an organization's strategy and capabilities.
A development practice in which programmers write a small failing test, implement enough code to pass it, and then improve the design safely.
Text inputs collect short single-line values, while textareas collect longer free-form text across multiple lines.
Text spacing accessibility keeps content and controls usable when people override line, paragraph, letter, and word spacing.
A systematic method for coding qualitative data and developing patterns of shared meaning that answer a research question.
A roadmap structured around a small set of strategic themes that connect related investments to broader product intent.
A usability method in which participants verbalize thoughts while attempting realistic tasks so researchers can connect behavior with interpretation.
A structured method for identifying valuable assets, trust boundaries, plausible threats, and proportionate security responses before and during system change.
A portfolio lens for managing current core performance, emerging growth businesses, and future options concurrently.
Throughput is the exact count of work items finished during a defined unit of time, such as a day, week, sprint, or month.
A pricing structure that offers distinct packages or applies different rates across defined quantity or usage bands.
Time on task measures the elapsed time users need for a defined task, providing an indicator of efficiency in a specified context.
The elapsed time from a defined starting point until a user first experiences a meaningful product benefit.
A limit on how long an operation may wait before the caller stops treating it as in progress.
Toasts and snackbars are brief, non-modal status messages; snackbars may also offer one concise action such as Undo.
Toggles, checkboxes, and radio buttons represent different choice models: immediate binary state, independent selections, and one selection from a mutually exclusive group.
Toil is manual, repetitive, automatable operational work that creates little enduring value and grows with the service it supports.
A token is a model's processing unit, and a tokenizer is the algorithm that converts text or other input into those units and back.
Tool calling lets a model propose a typed request to an external function or service while application code controls execution and returns the result.
A toolbar groups frequently used controls for the current view or object into a compact, consistently placed command surface.
A tooltip is a small, noninteractive popup that provides brief supplementary text for an element on hover or keyboard focus.
Touch target size measures the interactive area available to activate a control, including usable spacing that reduces accidental activation of nearby controls.
A cryptographic protocol that authenticates endpoints and protects network data from eavesdropping and modification in transit.
A task-based evaluation of a text-only navigation hierarchy that measures whether people can find where information should live.
A tree view presents an expandable hierarchical list whose nodes support structured keyboard navigation and may also support selection or actions.
The deliberate comparison of evidence from different methods, data sources, researchers, or theories to strengthen and complicate conclusions.
A source-control practice in which developers integrate small changes into one shared mainline frequently and avoid long-lived development branches.
UI typography makes interface language readable, scannable, resizable, and structurally clear across devices, languages, states, and settings.
Unicode assigns characters standardized code points, while encodings such as UTF-8 specify how those values are represented as bytes.
Unit economics evaluates the revenue and variable costs associated with a meaningful unit such as a customer, order, seat, or transaction.
Unit testing checks a small, defined piece of software quickly so developers can detect behavior changes close to their cause.
Universal design seeks products and environments usable by the widest range of people, to the greatest extent possible, without specialized adaptation.
A URL identifies a resource through a structured address whose components determine how browsers resolve and request it.
Usability is the extent to which specified users can achieve specified goals effectively, efficiently, and satisfactorily in a defined context of use.
Usability benchmarking measures a stable set of representative tasks and perceptions under controlled conditions so experience can be compared over time or across products.
A realistic, neutral activity given to a participant so researchers can observe whether and how a product supports a meaningful goal.
Observing representative participants attempt realistic tasks to identify where an interface supports or obstructs successful use.
A pricing model that charges customers according to measured consumption of a product or service.
User experience describes the broader experience of a product, while the user interface is the surface through which someone interacts with it.
A user flow maps the actions, decisions, and system responses involved in completing a specific goal within a product.
One-to-one conversations that uncover users’ goals, experiences, language, expectations, and reasoning around a product or problem.
User onboarding helps people understand a product, complete essential setup, and reach an initial valuable outcome with appropriate guidance.
A user persona is a research-grounded representation of a meaningful user pattern, created to keep needs, contexts, goals, and behaviors visible in decisions.
An attribute associated with a user or account and applied across their product activity until it changes.
A document that connects a research decision to clear questions, participants, methods, logistics, ethics, and intended use of the evidence.
A concise statement of a desired outcome from a user’s perspective that acts as a prompt for collaborative requirements and delivery conversations.
A collaborative method for arranging user activities and stories into a journey-shaped map, then slicing that map into coherent releases and learning steps.
Standard URL query parameters that label campaign source, medium, name, term, and content for traffic analysis.
A UX audit is a bounded, evidence-led review of an existing product that identifies experience risks, explains their likely impact, and prioritizes further action.
UX writing designs the words in interfaces and journeys so users can understand choices, take action, and recover from problems.
Decision-relevant learning supported by credible evidence that tests a consequential assumption about customers, value, or viability.
A testable explanation of why a defined customer would choose an offering, based on relevant outcomes, pains relieved, and alternatives.
The Van Westendorp price sensitivity meter uses four price-perception questions to explore an acceptable price range for a defined offering.
Vanity and actionable metrics distinguish impressive-looking counts from measures that are clearly defined, decision-linked, and capable of informing responsible action.
A vector database stores and searches vector representations so applications can retrieve items by similarity alongside metadata constraints.
The viewport is the browser area through which a document is viewed and against which many layout and visibility decisions are made.
Viral coefficient estimates the average number of new users generated by each existing user through a defined invitation or sharing mechanism.
Visual hierarchy uses position, scale, spacing, contrast, grouping, and sequence to reveal importance and guide attention through an interface.
A strategic mapping method that relates user needs, value-chain dependencies, and the evolution of components from novel to commodity.
WCAG is the W3C’s testable international standard for making web content more accessible to people with disabilities.
Web Components are browser standards for defining reusable custom elements with lifecycle behavior and optional DOM and style encapsulation.
Web Storage provides origin-scoped localStorage and sessionStorage key-value stores that browser scripts access synchronously.
A web worker runs JavaScript in a background browser agent so CPU-heavy work can avoid blocking a page's main event loop.
A mechanism that sends an HTTP request to a registered receiver when an event occurs, avoiding repeated polling for changes.
A protocol for maintaining a persistent connection over which a client and server can independently exchange messages in both directions.
WSJF sequences work by dividing a relative Cost of Delay estimate by relative job size, favoring valuable short-duration items.
Willingness to pay is the maximum amount a buyer would exchange for a defined offering under particular purchasing conditions.
A wireframe represents a screen’s structure, content priorities, and controls so a team can examine layout before detailed visual styling.
A prototype whose apparently automated responses are produced partly or entirely by a person behind the scenes during a moderated study.
A hierarchical decomposition of the project’s total scope into manageable deliverables and work packages that can be estimated, assigned, scheduled, and controlled.
Work in progress is the number of work items that have crossed the workflow's start point but have not yet crossed its finished point.
Explicit, team-created norms for everyday collaboration, including communication, meetings, focus time, decisions, handoffs, and conflict.
XML is a text-based markup format for representing structured documents and data using named elements, attributes, and nesting.
Choose “Save topic” on any article to find it here later.
Start typing to search titles, definitions, categories, and frameworks.