Skip to content

Context

Context is the capability to interpret observations so they become meaningful within the organization's goals, processes, terminology, relationships, and history.

Context turns information into understanding.

Role in the Organizational Intelligence Cycle

Context supports the Understand stage of the Organizational Intelligence Cycle.

It helps the organization answer:

  • What does this observation mean?
  • Why does it matter?
  • What is it related to?
  • Who or what is affected?
  • What prior experience is relevant?
  • What uncertainty remains?

Without context, the organization may collect information but fail to form Collective Understanding.

Responsibilities

The context capability should:

  • connect observations to business meaning
  • apply shared terminology
  • identify relationships between people, processes, systems, documents, events, and decisions
  • preserve assumptions and uncertainty
  • distinguish context from raw observation
  • support cross-functional interpretation
  • provide usable context to memory, reasoning, decision, and learning

Inputs

Possible inputs include:

  • observations
  • source metadata
  • business glossary terms
  • process models
  • organizational structure
  • policy and rule references
  • relationship data
  • historical cases
  • stakeholder feedback
  • external context

Outputs

Outputs may include:

  • interpreted situations
  • enriched observations
  • relationship links
  • entity and process context
  • categorized events
  • assumptions
  • uncertainty indicators
  • context summaries
  • candidate meanings for review

Controls

Context must be governed because incorrect interpretation can lead to incorrect reasoning and decisions.

Controls should address:

  • approved terminology
  • source trust levels
  • human review for high-impact interpretation
  • versioning of business rules and classifications
  • conflict resolution when sources disagree
  • explainability of derived context
  • access control for sensitive relationships
  • auditability of context changes

Quality Measures

Context quality can be assessed through:

  • consistency of terminology
  • completeness of required relationships
  • accuracy of classifications
  • traceability to source observations
  • clarity of assumptions
  • treatment of uncertainty
  • usefulness for downstream reasoning
  • cross-functional agreement where needed
  • frequency of interpretation corrections

High context quality means the organization can explain why information matters and how it relates to prior experience and current decisions.

Anti-patterns

Common anti-patterns include:

  • treating raw data as self-explanatory
  • allowing each team to define terms differently without reconciliation
  • hiding assumptions inside reports, prompts, or code
  • enriching information without provenance
  • applying outdated classifications
  • using AI-generated interpretation without review where review is required
  • losing context during handoffs between systems
  • confusing correlation with cause

Implementation-neutral Examples

Examples of context include:

  • linking a customer complaint to product version, service history, prior incidents, contract terms, and account risk
  • classifying a transaction using policy rules, party relationships, geography, prior alerts, and known exceptions
  • connecting a document to its owner, effective date, related process, and superseded versions
  • interpreting a support escalation as part of a recurring workflow failure rather than a single isolated ticket
  • identifying that two departments use different terms for the same operational concept

These examples can be implemented through many technologies. The framework requires the capability, not a specific product architecture.

Unless otherwise noted, this document is licensed under CC BY 4.0.