Glossary

Methods that can be used in a similar situation but emphasize a different angle.

On detail pages, alternatives help you choose between plausible paths.

A reusable template for a typical result produced by a method.

Templates make outcomes easier to reuse, for example as a canvas, briefing, plan, or working document.

The primary domain classification of a method, such as UX Research, Architecture, or Product Strategy.

Categories are more stable than tags and provide broad orientation in the catalog.

A rough estimate of how demanding preparation, facilitation, application, or evaluation are.

Complexity helps judge whether a method fits the current maturity, time, and group.

Support for selecting, understanding, and combining methods.

methodatlas is meant to help with decisions about approach, not only collect knowledge.

Filter dimensions in the catalog, such as category, complexity, mode, maturity, or method form.

Facets narrow the result list without requiring you to know the exact method name.

Origin: The term goes back to faceted classification in library and information science.

Locally saved methods that you can return to later in the catalog.

Favorites stay in your browser and do not require a login.

An estimate of how established, widespread, or experimental a method is in practice.

Maturity helps distinguish canonical, established, and more context-dependent methods.

A traceable path toward a goal with purpose, procedure, boundaries, context, and typical outcomes.

methodatlas distinguishes methods from pure tools, loose tips, or vague framework names.

The practical shape of a method, such as workshop method, framework, canvas, mapping tool, or operating practice.

The form shows how a method translates into actual work.

Example: A canvas structures work on a shared surface, while an operating practice changes recurring routines.

The way a method is carried out: workshop, async, or both.

Mode shows whether a method needs a shared session or works asynchronously within the flow of work.

Concrete results produced by a method, such as maps, backlogs, decisions, or hypotheses.

Output artifacts show what exists after the method has been applied.

The stage of work in which a method typically applies: discover, define, design, deliver, operate, or grow.

The phase helps the recommendation prioritize candidates for the current situation.

A curated method sequence for a recurring work situation.

Playbooks connect several methods into a usable flow.

Example: The playbook 'Product Discovery starten' connects four methods into one flow.

Origin: The term comes from American football, where a playbook collects rehearsed plays.

The rule-based selection aid for suitable methods.

The explorer uses goal, team size, time, phase, mode, and complexity to prioritize candidates.

Methods that are professionally, practically, or sequentially connected to another method.

Related methods help you continue when a method becomes part of a larger approach.

A concrete execution guide for a method.

Run sheets translate a method into flow, materials, steps, risks, and expected output.

Origin: The term comes from event and broadcast production, where run sheets capture the schedule in detail.

The internal point value used to sort a method in the Recommendation Explorer.

The score combines goal category, free text, goal terms, phase, format, complexity, team size, and timebox.

An adaptable plan for applying a method in a concrete session.

Session plans turn method knowledge into a facilitatable unit of work.

Automatically derived method neighbors based on category, tags, relations, and complexity.

Similar methods surface nearby options without making you search the entire catalog manually.

External sources that make a method's term, origin, application, or quality traceable.

Source links support curation and give you a path to original or reference material.

A cross-cutting theme that connects several methods.

Tags reflect topics such as prioritization, facilitation, risk, mapping, or strategy and build the topic map.

A typical time span in which a method can be prepared, run, or evaluated meaningfully.

The timebox is an orientation, not a rigid promise.

Origin: The term comes from agile practice such as Scrum, where timeboxing sets fixed time windows.