• anomaly-analysis Use when asked to detect anomalies/outliers in data — statistical, machine-learning, and deep-learning detection methods, supervised vs. unsupervised approaches — as distinct from trend-analysis's focus on overall patterns over time rather than individual deviant points.
  • change-request Use when asked to write or process a change request — a formal request to modify a specific system, process, or environment under IT/ITIL-style change control — as distinct from [[enterprise-change-management]], which governs organizational and people change (reorgs, new processes, culture shifts) rather than controlled technical or operational changes to a system.
  • data-pipeline Use when asked to design, document, or troubleshoot a data pipeline — an automated sequence that extracts data from a source, transforms it, and loads it into a destination on a schedule or trigger — as distinct from [[data-quality]], which measures whether the data moving through the pipeline is actually accurate and complete, not how it's moved.
  • data-quality Use when asked to define, measure, or improve data quality — whether data is accurate, complete, consistent, and fit for its actual use — as distinct from [[data-governance]], which is the policy and ownership framework around data, not the measurable property of the data itself.
  • demand-forecasting Use when asked to project future customer demand for operational planning — how much to produce, stock, or staff for — as distinct from [[demand-analysis]] (market-sizing and opportunity assessment for a business decision) which this is not; demand forecasting is the ongoing operational forecast that drives inventory and capacity decisions.
  • itil-5 Use when asked to apply, explain, or adopt ITIL 5, the PeopleCert ITIL release that emphasizes digital product management and AI governance alongside service management. Distinct from [[iso-iec-20000]] (certifiable standard), [[verism]] (organization-wide approach), and [[product-management]] (general product practice).
  • kaizen Use when asked to apply Kaizen — continuous, incremental, all-employee process improvement built on the Plan-Do-Check-Act cycle (see plan-do-check-act) — as distinct from a project-scoped Six Sigma DMAIC effort (see dmaic), which is heavier-weight and typically team-led rather than everyone-participating.
  • key-risk-indicators Use when asked to define or choose a Key Risk Indicator (KRI) — an early-warning metric for organizational risk — as the risk-focused counterpart to key-performance-indicators's performance-focused metrics, typically used together for a full view of health.
  • machine-learning-model-card Use when asked to write or review a model card — a document accompanying a trained ML model that describes what it does, how it was trained and evaluated, and its known limitations — as distinct from [[mlops]], which covers the infrastructure for deploying and monitoring a model rather than documenting it for downstream users.
  • maturity-models Use when asked to design, apply, or explain a maturity model — level naming conventions, top-down vs bottom-up construction, or well-known examples (CMMI, DevOps, Agile maturity models) — grounded in joelparkerhenderson/maturity-models, including documented rebuttals.
  • mlops Use when asked about MLOps — the practices and infrastructure for deploying, monitoring, and maintaining ML models in production reliably — as distinct from the model-development and training work itself, and from [[machine-learning-model-card]], which documents a model for downstream users rather than operating it once it's live.
  • postmortem Use when asked to write or facilitate a postmortem — a blameless, after-the-fact analysis of an incident, its timeline, root cause, and follow-up actions — as distinct from an [[incident-response-plan]] (what happens during the incident, not after) and a routine [[agile-reflection]] (triggered by an incident, not run on a scheduled cadence).
  • release-notes Use when asked to write release notes — the announcement accompanying one specific release, aimed at users deciding whether and how it affects them — as distinct from a [[changelog]], which is the complete, cumulative running history across every version rather than one release's announcement.
  • roi-analysis Use when asked to calculate or compare the return on investment (ROI) of a decision or initiative — net benefit relative to cost — as distinct from a [[budget-forecasting]] projection, which tracks overall income and expense over time rather than evaluating one specific investment decision.
  • root-cause-analysis Use when asked to investigate why a problem happened, rather than just its symptoms — the identify/gather-data/analyze/identify-cause/plan/implement steps of root cause analysis (RCA) — used across engineering, manufacturing, healthcare, software, and business management.
  • runbook Use when asked to write a runbook — a step-by-step operational procedure for a specific, recurring task or system situation, such as restarting a service, rotating a credential, or failing over a database — as distinct from an [[incident-response-plan]], which governs roles and communication during an incident rather than the precise technical steps for one specific action.
  • service-catalog Use when asked to build or document a service catalog — a structured, discoverable list of the IT or business services an organization offers internally or externally, what each includes, and how to request it — as distinct from a [[service-level-agreement]], which defines the performance commitment for one specific service rather than listing what services exist at all.
  • service-level-agreement Use when asked to draft or review a service level agreement (SLA) — defining expected service performance such as uptime, response time, or support tiers between a provider and customer — as distinct from a statement-of-work, which defines a project's specific deliverables and scope rather than ongoing performance standards; for general guidance only, not legal advice, so always direct the reader to consult a qualified lawyer for their specific situation and jurisdiction.
  • service-management-metrics-maintainer-skill Helps maintainers write and check Service Management Metrics topics against the spec. Use when drafting, reviewing, or renaming a topic, or when running the quality gates.
  • service-management-metrics-skill Helps readers find the right topic, metric definition, gaming vector, guardrail, discussion question, or AI prompt in the Service Management Metrics book. Use when someone asks how to measure an agile or ITIL practice (incidents, changes, flow, service levels, experience, assets, cost, risk, people, AI).
  • software-engineering-metrics Use when someone wants to apply this book's guidance to their own team or organization -- choosing a metric, naming its gaming vector and guardrail, applying the Flow Framework, SPACE, or DORA, filling in a metrics charter or dashboard spec, or running the maturity self-assessment. Not for editing the book's own chapters; use software-engineering-metrics-maintainer for that.
  • statistical-analysis Use when asked which statistical technique fits a data question — descriptive vs. inferential statistics, regression, time series, factor/cluster analysis, data mining — as the umbrella technique-selection layer above more specific methods like bayes-theorem-analysis, chi-square-analysis, and monte-carlo-analysis.
  • survey-design Use when asked to design a survey, questionnaire, or feedback form — writing questions and response scales that actually measure what they're meant to without leading or confusing respondents — as distinct from a [[user-interview-guide]], which is a qualitative, open-ended conversation rather than a standardized instrument.
  • trend-analysis Use when asked to analyze data over time to identify patterns and forecast — regression, moving averages, exponential smoothing — as distinct from anomaly-analysis's focus on individual deviant points rather than the overall directional pattern.
  • value-stream-map Use when asked to build a value stream map — a lean process-analysis diagram tracing material and information flow through a process, distinguishing value-adding steps from waste and quantifying time — as distinct from a plain swimlane-diagram (see below), which shows who does what without that waste analysis.