The vocabulary, defined plainly.
These terms get used loosely, and the looseness is expensive: two people agreeing on the word while meaning different things is how a requirement passes review and fails in testing. Each entry says what the term means and what distinction actually matters when you are evaluating something.
175 terms
No term matches
Try the acronym, or a single word.
Strategy
Balanced scorecard
Kaplan and Norton's framework for measuring strategy across four perspectives — financial, customer, internal processes, and learning and growth.
Deliberate strategy
The component of strategy that is intentionally formulated and deployed top-down through objectives, targets and initiatives.
Dynamic capabilities
An organization's ability to sense opportunities and threats, seize them, and reconfigure its resource base in changing environments.
Emergent strategy
A strategic pattern that emerges from actual operations rather than from prior planning.
Goal
The quantification of a strategic objective for a given period, with a threshold and an accountable owner.
Initiative
A time-bound effort that mobilizes resources toward one or more strategic objectives.
OKR
A strategy management framework in which objectives express qualitative intent and key results make it measurable and time-bound.
Operational effectiveness
Performing the same activities as competitors, but better. It is distinct from strategy, which means doing different things or doing them differently, and on its own it does not sustain a…
Resource-based view
The theory that sustainable competitive advantage stems from resources and capabilities that are valuable, rare, hard to imitate and well exploited by the organization.
Strategic objective
An outcome the organization commits to achieving within a defined horizon. In the metamodel it is the first object in the chain, and it is not considered governable until quantified into at…
Strategy execution management
The discipline — and software category — of connecting strategic objectives to the initiatives, processes and indicators that deliver them, and tracking the delivery on live data.
Strategy map
A representation of an organization's objectives connected by explicit cause-and-effect relationships.
Total alignment
An approach requiring vision, strategy, roles, accountabilities, objectives and indicators to be connected within a single execution logic, so that each person can see how their work…
Business architecture
Business architecture
A structured, coherent representation of how an organization creates, delivers and captures value.
Business capability
What an organization must know how to do, expressed independently of who does it or which system supports it.
Business model
The starting point of the architecture: it describes how the organization creates, transforms, delivers and transfers value.
Business Model Canvas
A tool describing on a single canvas how an organization creates, delivers and captures value, covering segments, value proposition, channels, relationships, revenue, resources, activities,…
Business structure
The component of the business model describing how the enterprise organizes itself to produce the value it offers: units, roles and accountabilities.
Capability map
A hierarchical model of an organization's capabilities, classified by type (core, strategic, enabling) and criticality.
Digital twin of an organization
A dynamic software model of how an organization operationalizes its business model, responds to change and delivers value.
Enterprise architecture tools
Software that captures the relationships among capabilities, processes, applications, information and technology, so architecture decisions can be analysed rather than argued.
Executable Business Architecture
Business architecture whose artefacts are the objects a platform actually runs, rather than diagrams describing it from outside.
Ontological model
The formal vocabulary of the business: the actors, objects, events, transactions and outcomes the organization handles, and how they relate.
Operating model
An explicit decision about which processes are standardized and which data are integrated across business units.
Service portfolio
The set of services an organization offers, understood as the operational expression of its value proposition rather than an administrative list of request types.
The eight business architecture models
A framework inherited from Villalobos describing the organization through eight interrelated models: business, financial, strategic, capability, organizational, process, resource and indicator.
Value proposition
A concrete statement of what outcome a stakeholder expects, under what condition they recognize the value as delivered, and which indicators verify it.
Value stream
The end-to-end sequence of value-adding stages that produces an outcome for a stakeholder.
Traceability and metamodel
Architectural integrity constraint
A rule defining what is methodologically valid, beyond what is structurally possible.
Architectural object
Each of the sixteen element types the metamodel recognizes, from strategic objective to evidence.
Cardinality
A rule defining how many instances of one object may or must relate to another. It is not a modelling technicality: it encodes business decisions, such as every offering executing exactly one…
Chain link
Each of the seven levels of the traceability chain. Skipping a link produces the pathologies the methodology seeks to avoid: processes without a service, services without capabilities, and…
Living repository
The set of architectural objects and relationships as they exist on the platform at a given moment.
Metamodel
The formal definition of which object types exist in the architecture, how they may relate, with what cardinalities, and which configurations are invalid.
Methodological conformance
A property of an implementation whose repository satisfies the ten integrity constraints.
Traceability
The ability of an artifact to demonstrate which other artifacts it relates to and why it exists.
Traceability chain
The ordered relationship from strategy through capabilities, services, offerings, processes and data to the indicators that verify results.
Services and offerings
Criticality
The degree to which the interruption of a service, capability or process affects the organization's operations or compliance.
Requestable offering
The condition met when an offering is visible, current, and its process has an operational entry point.
Service
A unit of value the organization offers to an internal or external stakeholder, underpinned by capabilities and resources.
Service catalogue
The register of an organization's services and offerings with owner, value proposition, criticality, cost or price, implementing capabilities and supporting CIs.
Service offering
The concrete, requestable form in which a service is presented and consumed; the user-facing side of the service.
Value co-creation
The principle that value is not produced by the provider alone but arises from the interaction between provider and consumer.
Process design
Activity
A human or automated unit of work within a process. In an executable architecture it is not a box on a diagram: it is a point of interaction between work, data, rules, permissions, evidence,…
Adaptive process orchestration
Forrester's 2026 category for orchestration that combines deterministic flows with AI agents to meet declared business objectives — a category still forming.
AND/OR decomposition
A technique for breaking down complex objectives. In an AND decomposition the parent is satisfied only if all sub-objectives are; in an OR decomposition the sub-objectives are design…
AS-IS
A model of the process as it operates today. It is captured only to the depth required to redesign, and must answer three questions: what prevents achieving the objective, what should be…
BPM
The discipline and software category for designing, executing, measuring and improving business processes as governed assets.
BPM lifecycle
The sequence of process identification, discovery, analysis, redesign, implementation and monitoring.
BPMN
The international standard notation for modelling business processes, precise enough that a diagram can be executed rather than only read.
Business orchestration and automation technologies (BOAT)
Gartner's category for consolidated platforms that deliver enterprise automation by orchestrating processes, people, systems, documents and — increasingly — AI agents.
Business process
A coordination of activities, decisions, roles, data and rules aimed at producing a valuable outcome.
Design constraint
A non-negotiable design condition, typed as time, cost, compliance, quality, risk or experience.
Digital process automation
The name the process automation market carried between BPM suites and today's orchestration categories — still widely searched, largely superseded.
Escalation
A design mechanism that raises a case to a higher level of decision or attention when a condition is met, typically the risk of breaching a deadline or threshold.
Expected outcome
The business state that must be reached when the process ends correctly. It should not be confused with a document output: an output is an approved form; an outcome is a supplier cleared to…
Gateway
A point in the flow where the process branches or converges. A gateway without explicit data and rules is not a decision: it is ambiguity drawn as a diagram, and the methodology rejects it.
Governed exception
A deviation from the normal course that the design anticipated and resolved explicitly: resolve, compensate, escalate, reject or close with evidence.
Happy path
The main trajectory of a process, in which everything happens as planned and without exceptions.
iBPMS
Intelligent business process management suite — a BPM platform extended with analytics, decision management, integration and AI capabilities.
Intent sheet
The first-phase design artifact that locates the process within the traceability chain, answering why it exists, what value it delivers and which capability it operationalizes.
Objective conflict
A tension between criteria that cannot be maximized simultaneously, such as speed versus control or cost versus experience.
Objective-Driven Process Design
Designing the future process as the mechanism that maximises a verifiable objective, instead of optimising the current one.
Objective-outcome-KPI matrix
A second-phase artifact linking each expected outcome to the indicator that verifies it.
Organizational white space
The space between the boxes of the org chart, where work crosses boundaries and delays, rework and lost accountability tend to appear.
Process instance
A concrete, individual execution of a process: a case, a request, a file. It is the unit on which evidence accumulates, timings are measured and fulfilment of the objective is verified in…
Process mining
Reconstructing how a process actually runs from the event logs its systems already produce, rather than from what people describe in workshops.
Process objective
The specification of the outcome a process must produce, not a declarative sentence on a form.
Process orchestration products
Everest Group's category for platforms that coordinate end-to-end processes across the systems, people and documents they cross.
Process reengineering
The tradition holding that automating a fragmented structure accelerates a bad design rather than fixing it, and that redesign must start from the customer, the outcome and the complete flow…
Process sheet
The process charter that must be completed before drawing the BPMN, covering identity, objective, classification, accountability, relationships to the value chain and service, and inputs and…
Risk as a design condition
Treating risk not as a documentary warning but as an architectural requirement. If the risk is fraud, the process incorporates verification or segregation of duties; if it is missed…
Satisfaction criterion
An evaluable predicate that makes an expected outcome verifiable. It answers what must be true at completion, what must not occur, and which data prove fulfilment; without criteria, the…
SIPOC
A framework characterizing a process by its suppliers, inputs, process, outputs and customers.
State and transition
How the executable process is implemented: states represent the situations a case can be in, and transitions the conditions allowing movement between them.
Strong satisfaction
The level of fulfilment in which every normal trajectory reaches an expected outcome while meeting criteria and thresholds, and every exceptional trajectory ends in a governed exception with…
Threshold
The quantification of the tolerance allowed for a satisfaction criterion, with a target, a band and a direction (maximize, minimize or stay within range).
TO-BE
The design of the future process. Here it is not an optimized AS-IS but the mechanism built to maximize the fulfilment of a verifiable objective, together with its data, rules, risks,…
Trajectory
Each possible path a process instance can follow from a start event to an end event.
Unsatisfied objective
The situation in which some normal trajectory leads to no expected outcome, or some criterion lacks the data to be evaluated.
Weak satisfaction
The level of fulfilment in which normal trajectories reach the outcomes but breach non-critical thresholds, or where ungoverned exceptions remain.
Well-formed objective
An objective that satisfies all well-formedness rules across its nine components: purpose, stakeholders, outcomes, criteria, thresholds, constraints, risks, capabilities and evidence.
Decisions and rules
Business rule
A constraint, calculation, validation, derivation or policy governing activities and decisions.
Decision automation
The delegation of a decision to a rules engine or model. It is justified when the decision is structured, repeatable, traceable and based on reliable data, and when it improves timeliness,…
DMN
The standard for specifying business decisions and rules, designed to work alongside BPMN.
Operational decision
A determination made within a process to select a path, assign a resource, approve or reject, compute a priority or trigger an exception.
Data and information
Attribute
A declared property of an entity or metamodel object. It is the unit on which measurement rests: every indicator quantifies an attribute of an identified measurement object.
Business entity
An object, actor, event or transaction the organization needs to know about, manage or evaluate, such as Customer, Request, Contract or Payment.
CMDB
The repository of configuration items and the relationships between them, which is what turns an incident into a question you can answer.
Configuration item
A governable element that supports services and processes: applications, assets, technology components or critical resources.
Data architecture
The definition of the data types and sources needed to support the business, expressed in a way stakeholders can understand.
Data as a business asset
The view of data as a resource that enables operating, deciding, controlling, measuring and learning, and which therefore demands its own policies, roles and management standards, like any…
Data lineage
The trail revealing where a data item came from, which process captured or transformed it, which rule modified it, which system received it and which indicator used it.
Data model
The structuring of business concepts into entities, attributes, relationships, domains, keys and referential integrity.
Data owner
The role accountable for the definition, quality, use, integrity, security, lineage and evolution of a critical entity.
Data quality
The degree to which data are accurate, complete, consistent, timely, valid and unique.
Document management
The custody market for documents — versions, permissions, retention, signature, evidence. The current name of what was once content services platforms, and before that ECM.
ECM (enterprise content management)
The retired name of the document market — Gartner replaced it with content services platforms in 2017 and today publishes the Magic Quadrant for Document Management.
Historisation
The preservation of how a data item changes over time, so its value at any past moment can be reconstructed.
Intelligent document processing
Extracting, classifying and validating information from unstructured documents so that business processes can act on it.
Mandatory by state
A rule defining which data are required at each point of the process, rather than demanding everything up front.
Master data
Shared reference entities consumed by multiple processes and systems, such as customer, supplier or product.
Metadata
Data describing other data: their meaning, origin, format, value domain, owner and usage.
Purposeful data
The rule requiring every captured data item to declare its function: execute, decide, comply, evidence, measure or integrate.
Referential integrity
The condition ensuring relationships between entities remain valid and free of broken references.
Related Data
The mechanism connecting the data model to process execution, associating with each activity the tables it captures or queries, with state-based mandatory fields, scope filters and in-place…
Semantic coherence
The condition in which every area uses the same concept with the same meaning. Its absence produces automations that work technically and fail commercially, as when customer, user and third…
Semantic control at the point of creation
The principle that reuse precedes creation: before creating an entity, one must check whether the concept already exists.
Measurement and evidence
Achievement indicator
An indicator measuring whether the process's expected outcome was actually achieved, as distinct from those measuring flow, quality or control.
Base measure
The direct quantification of an attribute using a defined measurement method and scale.
Correlation and causation
Two measures moving together is correlation; one producing the other is causation — and a dashboard can only show the first.
Decision criterion
The threshold or rule that turns a measure into actionable information, signalling whether performance is acceptable, needs attention or demands intervention.
Derived measure
The result of combining two or more base measures through a formula, such as a compliance percentage or an average cycle time.
Evidence
The set of data, documents, logs, states, decisions, signatures, timings and integrations that demonstrate what happened in a process instance.
Goal-Question-Metric
A disciplined procedure for deriving indicators: from each goal one derives questions that characterize its fulfilment, and from each question metrics that answer it with data.
Indicator families
The classification of indicators by the chain link they measure: strategic, capability, service, process and data.
KPI
A measure that quantifies a declared attribute of something in the architecture, and therefore verifies whether an objective was met.
Measurement object
Any metamodel object on which an indicator rests: capability, service, offering, process, activity, entity or CI.
Orphan metric
An indicator computed because the data exist, but which answers no relevant question and connects to no objective.
Process intelligence platform
A platform that mines, analyses, models and monitors processes from the event data real systems already produce.
Governance
Architecture contract
The instrument governing implementation and deployment to ensure conformance with the defined architecture.
Audit
The ability to demonstrate who did what, when, from where and on which object. It rests on per-instance trails recording action, date, time, user and device, for both active and closed instances.
Code signing
Digitally signing distributed software so that its origin and integrity can be verified before it runs — a supply-chain control, not a formality.
Compliance by design
An approach in which compliance is built into the system design rather than verified afterwards through audit.
Deny by default
An authorization posture where nothing is permitted unless explicitly granted — what is not conceded is neither shown nor executed.
Govern versus manage
The distinction between evaluating needs, directing through prioritization and monitoring compliance (governing), and planning, building, running and monitoring the activities aligned to that…
Governance by design
The principle that when a methodological rule can be implemented as a native platform control, the control is preferred over the procedure.
Impact matrix
The analysis of which artifacts a change affects, which tests must be repeated and what must be re-approved.
Post-go-live governance
The set of practices that preserve architectural coherence after go-live: reviewing the catalog and capability map, re-approving processes when they change, and evolving the data model by design.
Process owner
The single role accountable for a process's objective, design, performance, approval, changes and improvement.
Quantum resistance
The property of a cryptographic scheme that a cryptographically relevant quantum computer would not break in any practical sense.
Segregation of duties
A control preventing one person from accumulating incompatible permissions, such as requesting and approving.
Single-tenant
A deployment model where each client runs on its own dedicated application and database, with no infrastructure shared between clients.
Versioning and reapproval
The regime by which every material change to a process, rule, data item, service level, offering or indicator is versioned and re-approved.
Implementation and validation
Change Data Capture
A technique that detects changes in a source system and automatically triggers the corresponding integration processes.
End-to-end test
A full validation that traverses the process from the portal request through to the report, covering execution, service levels, notifications, closure and survey.
ETL
The mechanism that extracts, transforms and loads data between systems, integrating them into workflows.
Ex-ante simulation
Testing designed time thresholds against the real or observed distribution of cases before activating them.
Executable configuration
The materialization of the design on the platform: states, activities, forms, transitions, rules, related data, assignments and notifications.
Five-dimension validation
The minimum scope of integral testing: functional, data, rules, objective and evidence.
Interoperability
The ability to exchange data and coordinate operations with internal and external systems without requiring their replacement.
Layout
The arrangement of fields through which an activity captures or queries data. It is not a data entry screen but a point of data governance: each field must correspond to a justified entity,…
Orchestration
The coordination of people, processes, data and information systems from the platform, so the process executes its design without requiring replacement of the existing technology ecosystem.
Improvement and maturity
Backlog
The volume of cases awaiting attention at a given moment. It is a flow indicator that anticipates deadline breaches before they occur and signals mismatches between demand and capacity.
Bottleneck
The point in a process where available capacity limits overall throughput, producing waiting and case build-up.
Business Process Maturity Model
A reference model defining five levels of process maturity, from initial to innovating, describing the shift from inconsistent practice to quantitative management.
Conformance checking
The quantification of the proportion of real cases that respect the approved design, its rules and its controls.
Demonstrable maturity
The principle that maturity assessment rests on evidence extractable from the platform rather than on declarative self-assessment.
Dexon maturity model
A five-level scale running from basic documentation to governed executable architecture.
Event log
A structured trail in which each process instance records case, activity, timestamp, user and action.
Evidence-based continuous improvement
The practice of redesigning from operational data (timings, backlog, rework, exceptions, data quality, satisfaction) rather than opinion or perceived efficiency.
PDCA
A four-step improvement cycle: plan, do, check, act. Here it translates into interpreting indicators and forming a hypothesis, adjusting in a controlled environment, validating end-to-end and…
Process enablers and enterprise capabilities
The distinction between what makes a process mature (design, performers, owner, infrastructure and metrics) and what makes an enterprise mature (leadership, culture, expertise and governance).
Rework
The repetition of work already performed because of errors, incomplete data or returns.
Change and adoption
ADKAR
A model holding that organizational change requires individual change through five outcomes: awareness, desire, knowledge, ability and reinforcement.
Organizational adoption
The extent to which people actually use the designed process, capture data with quality and use indicators to decide.
Role governance
The assignment of permissions and accountabilities by institutional function rather than by individual, so the solution does not depend on specific people.
Role-based training
An approach organizing training around each person's operational accountability rather than by generic tool functionality.
ITSM and artificial intelligence
Agentic process automation
Automation where LLM-based agents execute activities with bounded autonomy inside a process — the emerging frontier of the orchestration market.
AI applications in ITSM
The use of AI — classification, prediction, grounded answers, agents — inside IT service management practices, and the market that evaluates it.
AI management system
A framework requiring artificial intelligence systems to be managed with objectives, roles, impact assessment and continual improvement.
AI subordinate to the objective
The principle governing the incorporation of artificial intelligence into a process: every AI intervention must be justified by its contribution to the objective, a constraint or an…
AI that assists versus AI that decides
An operational design distinction: AI may decide autonomously when the decision is structured, reversible and auditable; it assists but does not decide where expert judgement, ambiguity or…
Enterprise service management
Applying the discipline of IT service management — catalogue, requests, SLAs, knowledge — to services delivered by any area of the organization.
Entitlement
What the organization is licensed to use — contracts, quantities and conditions — as opposed to what a scan finds installed.
Evidence of AI intervention
The record of which model intervened in a process, with what input, what output it produced and what action followed.
Integrated ITSM general criteria
Cross-cutting requirements a tool must meet beyond each individual practice: integration across practices, security, audit, reporting and usability.
ITIL
The most widely adopted framework of IT service management practices, describing what to manage rather than prescribing a tool.
ITSM
The practice of managing IT as a set of services with owners, commitments and evidence, rather than as a collection of technology.
ITSM platform
The software that runs IT service management — portal, catalogue, incidents, requests, changes, assets, CMDB, knowledge and service levels — as one operation.
ITSM practice
A set of organizational resources designed to perform work or achieve an objective within service management.
PinkVERIFY
Pink Elephant's certification scheme verifying that a tool genuinely supports ITSM processes, in functionality and in terminology.
Predictive analytics
The use of trained models to anticipate an outcome before it occurs, such as a service level breach.
Service value system
The ITIL 4 model whose core is a value chain running from plan and improve through to deliver and support, fed by practices and governed by guiding principles such as focus on value and…
SLA
A committed and measured level of service, meaningful only when the commitment is calculated against real operations and can be explained.
Missing a term?
If a concept shows up in your RFP or your evaluation and is not here, tell us. We will define it and add it.