methodatlas
Engineering

Goal Question Metric

Moves technical problems, hypotheses, and next steps toward a concrete result through "formulate the goal clearly", "derive probing questions for each goal", and "set the review cadence".

Core question
Which questions must we be able to answer to know whether we are reaching our goal, and which metric answers each question?
MediumWorkshop90-180 min
Open runsheetPlan sessionStart comparison
Purpose

Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.

How it works

The team follows the steps "formulate the goal clearly", "derive probing questions for each goal", "define a metric for each question", "clarify the data source and accountability", and "set the review cadence". Each step is made visible. At the end, a GQM table and metric briefs are available so decisions, tests, or actions can continue directly.

Visual orientation

Method sketch for a quick mental model.

Goal Question Metric · Goal, Question, MetricDerive concrete metrics from goals through checking questions so no data is collected without purpose
Goal Question MetricThe visual shows the GQM derivation path from goal through checking questions to concrete metrics and data sources.Derive metrics from goals and checking questionsGQM prevents stockpiling data: every metric must answer a concrete question about a goal.Goalimprove platform reliabilityQuestionsHow often do deployments fail?checks stabilityHow fast do we recover?checks recoveryWhere do wait times appear?checks flowMetricsFailure Ratedata source: CI/CDMTTRdata source: incidentsLead Timedata source: workflowgoal first,then questionsno metric withoutchecking questionmeasurement answers the question

Flow

  1. 1Formulate the goal clearly
  2. 2Derive probing questions for each goal
  3. 3Define a metric for each question
  4. 4Clarify the data source and accountability
  5. 5Set the review cadence

The runsheet guides execution with 5 phases, timeboxes, 6 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Engineering metrics
  • DevOps programs
  • Research setups

Not good for

  • Very exploratory phases without goal clarity

Deep dive

In detail

Goal Question Metric, often abbreviated as GQM, was developed by Victor Basili for software measurement. Each goal leads to a set of probing questions, and each question leads to at least one concrete metric. The method also works beyond software engineering because it anchors data to strategy.

Facilitation

Always start with the goal, never with available data. A metric must not be collected if it does not answer a question.

Output artifacts
GQM-TabelleMetrik-Steckbriefe
Tags
metricsmeasurementengineeringalignment

Sources

GQM - Wikipediaen.wikipedia.org
Artifact templates
Goal Question Metric Working TemplateCompact working template for Goal Question Metric with context, input, output artifacts, and next step.
markdown

goal-question-metric-working-template.md

Compact working template for Goal Question Metric with context, input, output artifacts, and next step.

Goal Question Metric Working Template

Goal

Derives metrics from goals and probing questions.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • GQM table:
  • Metric profiles:

Assumptions and open questions

  • ...

Decision / next step

Owner, date, and success signal.

When to choose differently

Short decision aid for existing alternatives.

KPI Tree

Statt Goal Question Metric, wenn du Ziele in wenige Messgrößen und ihre Treiber sauber herunterbrechen willst.

Similar methods

All methods
Product Strategy
KPI Tree

Moves target group, value, goals, and priorities toward a concrete result through "define the top metric", "describe the main driver of the top metric", and "set the review cadence".

Statt Goal Question Metric, wenn du Ziele in wenige Messgrößen und ihre Treiber sauber herunterbrechen willst.

UX Research
HEART Framework

Moves observations, needs, and patterns toward a concrete result through "define a goal for each HEART dimension", "identify signals for each goal", and "agree on a review cadence".

Product Strategy
Counter Metrics

Moves target group, value, goals, and priorities toward a concrete result through "name the main metric", "collect possible unintended side effects", and "use counter metrics alongside the main metric in reviews".

Product Strategy
SMART Goals

Turns target group, value, goals, and priorities into a tangible result by drafting a raw goal, checking specificity, and defining time relevance.

Business Strategy
Strategy Map

Visualisiert strategische Ziele und Ursache-Wirkungs-Beziehungen, damit ein Führungsteam dieselbe Strategiegeschichte sieht.

Engineering
Fault Isolation

Turns technical problems, hypotheses, and next steps into a tangible result by clarifying the symptom and system boundaries, breaking the fault space into areas, and narrowing the affected area.