Measurement
Measurement is part of how an ontology becomes operational.
If the ontology is going to support governance, organisational learning, and agents, it needs ways to describe not only what exists, but how well it performs, how much value it creates, how much risk it carries, and how strong the underlying knowledge is.
Product measurement
One important measurement family concerns products and product-like outputs.
Examples include:
- growth of contribution margin
- percentage of total contribution margin
- growth in market share
- market share percentage
- growth of revenue
- percentage of total revenue
- time to value
- expansion revenue
- average revenue per user
- net churn
- virality or network effect
- number of user actions per session
- customer satisfaction score
- customer acquisition cost
- monthly recurring revenue
- traffic, paid or organic
These measures help describe the performance and value dynamics of products, services, and organisational outputs.
Capability measurement
Another family concerns capabilities.
Examples include:
- performance
- priority
- business complexity
- level of management
- level of information
- process maturity
- levels of resource
- impact measure
- functionality level
- operational efficiency
- operational risk
- design execution
- technical risk
- technical complexity
- business value
- reliability level
- usability level
These measures help describe how capable, mature, risky, or valuable a given organisational capability is.
Why this matters for the ontology
The ontology should be able to represent not only entities and relationships, but also measured qualities attached to them.
That means products, capabilities, workflows, services, applications, and even parts of the knowledge base can all carry measurable indicators.
This matters because it allows the ontology to support:
- comparison
- prioritisation
- governance
- improvement tracking
- rule-based evaluation
- agent reasoning over quality and performance
Relation to Knowledge Fog
Measurement is not only about business performance. It also connects to the quality of understanding itself.
That means the ontology can support measures of:
- completeness
- confidence
- evidence strength
- ownership clarity
- recency
- consistency
- dependency visibility
Those are the kinds of dimensions that feed Knowledge Fog.
So measurement in this model has at least two roles:
- measuring the organisation and its outputs
- measuring the quality and clarity of the organisation's knowledge about itself
Design implication
A mature ontology should allow indicators to be linked to:
- entities
- capabilities
- products
- workflows
- services
- decisions
- risks
- domains
That makes measurement part of the structural knowledge base rather than a separate spreadsheet culture floating outside it.
Diagram
If the embedded viewer does not load, open directly:
- /assets/gxp/diagrams/Data-Modeling-Tech-Overview.drawio