A recurring pattern across the Practice Notes is that organizations rarely stop developing, assessing or operating a subject merely because the original understanding behind it has weakened. The work continues. Systems still need to be changed. Products still need to be developed. Capabilities still need to be assessed. Decisions still need to be made. But when the original basis for those decisions becomes harder to reconstruct, something else tends to take its place.
An existing system becomes the definition of what its replacement should do. A process becomes the definition of a capability. A framework becomes the definition of good practice. A backlog becomes the definition of the product. Requirements become the complete definition of intent. A familiar example becomes the standard against which alternatives are judged. The Practice Notes repeatedly describe this mechanism without always naming it directly.
Taken together, they suggest a distinct concept:
When explicit understanding of what should exist weakens, organizations tend to substitute a surviving realization, representation or convention as the reference for future Development and Assessment. This is Reference Substitution.
The Need for a Reference Does Not Disappear
Assessment requires some basis for judgment. The Practice Notes distinguish the Reference Model from the Assessment Model: one establishes what matters, while the other determines how evidence is gathered, interpreted and judged. Development has the same dependency from another direction. If an organization wants to change a subject deliberately, it needs some understanding of what matters, which effects are intended and which characteristics should be preserved or changed.
The need for such a basis does not disappear simply because the basis becomes implicit or incomplete. People still need to answer questions such as: What should the new system do? What should this capability look like? Which product characteristics matter? What should be preserved? What should be changed? What counts as improvement? If explicit understanding is available, those questions can be answered against an explicit Reference Model.
If it is not, the organization still needs an answer. That creates the conditions for substitution.
What Survives Acquires Authority
The Practice Notes repeatedly observe that artifacts and realizations tend to survive longer than the reasoning that produced them. A system may continue operating long after its designers have left. A capability may retain processes after nobody remembers why they were introduced. A backlog may continue evolving after its connection to product intent has weakened. The surviving object then has an important advantage over the missing understanding: it is available.
The old system can be inspected. The process can be read. The framework can be downloaded. The requirements can be found. The backlog can be queried. The current organizational structure can be observed. That availability can gradually be mistaken for authority. The question shifts from: What should this subject be? toward: What does the existing subject currently look like? And eventually: How closely does the future or assessed subject resemble what already exists?
The substitution is often not deliberate. Nobody necessarily decides that the legacy system is the ideal reference. The legacy system simply becomes the richest surviving source of information.
Reference Objects Can Replace Reference Models
The Practice Notes draw an important distinction between a Reference Model and what might be called a reference object. A Reference Model represents the significant characteristics and relationships that matter while remaining sufficiently independent of a particular realization. A reference object is one concrete example that begins to stand in for the model. The Practice Notes use an everyday analogy to expose this mistake. A particular watch may be one realization of a dress watch. It is not therefore the definition of what a dress watch must be. Comparing every other watch directly against that example risks turning its contingent design choices into universal assessment criteria.
The same mechanism appears professionally. A successful department becomes the template for capability design. A current system becomes the template for replacement requirements. A well-known framework becomes the template for transformation. An existing process becomes the template for maturity. The problem is not using examples. Examples contain useful evidence.
The problem begins when the properties of one example are silently promoted from:
This is how one realization works
to:
This is what the subject should be.
The Legacy System Becomes the Requirement Source
The strongest form of Reference Substitution appears when an old realization becomes the primary source for a new one. The Practice Notes concerning legacy systems show why this happens. An old system may contain business rules, interfaces, dependencies and behavior whose original rationale has disappeared. The organization may no longer know which parts remain essential, which were historical compromises and which have become obsolete.
Yet modernization still requires requirements. The easiest source is the existing system. That produces a familiar chain:
Existing system → reconstructed requirements → new system → tests against those requirements
The reasoning can look highly disciplined. Requirements are documented. Traceability exists. Tests pass. Acceptance criteria are satisfied. But the chain may still reproduce historical accident because the original question was never re-established:
What does the organization actually need now?
The Practice Notes explicitly warn that requirements are selected translations of a wider Product Reference Model rather than complete product understanding.
When that wider understanding disappears, the realization can become the requirement source by default. Reference Substitution therefore provides one mechanism through which obsolete behavior survives modernization.
Processes Can Become Capability Definitions
The same pattern appears in organizational capability. A capability concerns what an organization can reliably accomplish. Processes, roles, practices, tools and governance arrangements may contribute to that ability, but they are not identical to the capability itself. When understanding of the underlying ability weakens, however, the visible arrangements are easier to preserve than the purpose they were meant to serve. The Practice Notes repeatedly push assessment away from questions such as:
- Does the process exist?
- Is the document available?
- Is the role present?
- Has the activity been performed?
toward:
- What organizational ability was this arrangement intended to create?
- Is that ability actually present?
The Discipline of Curiosity makes this move explicit:
visible arrangements can provide evidence without establishing that the subject is doing what it needs to do.
Reference Substitution explains what happens when that distinction disappears.
The process becomes the capability reference. Then capability improvement naturally becomes process improvement. The organization may become increasingly compliant with its chosen process model while becoming no more capable of producing the effects that actually matter.
Frameworks Can Become Ambition
Established frameworks are particularly attractive substitute references. They carry professional credibility. They provide vocabulary. They contain accumulated knowledge. They often make invisible organizational problems easier to discuss. The problem is not their use. The Practice Notes explicitly recognize the value of reusable professional knowledge. The problem arises when the framework stops informing the organization-specific reference and starts replacing it.
At that point:
Framework adoption becomes Development
and:
Framework compliance becomes Assessment.
The organization no longer asks whether a particular element is necessary for the effects it needs to produce under its conditions. Instead, the presence of the framework element itself becomes evidence of improvement. Reference Substitution therefore helps explain why transformation initiatives can become exercises in implementing frameworks rather than developing organizational capability.
The Practice Notes make this distinction directly: if transformation has become an exercise in implementing a framework, the real question is not how to implement the framework more faithfully, but which capabilities need to change and which interventions might help.
Representations Can Replace the Subject
Reference Substitution does not require a physical realization. Representations can substitute too. Requirements can substitute for Product Intent. A backlog can substitute for product strategy. Test cases can substitute for requirements. Documentation can substitute for understanding. A dashboard can substitute for performance. A maturity score can substitute for capability. Each representation may be useful. The failure occurs when its scope is forgotten.
For example, requirements may capture selected expected behaviors but omit significant qualities, operating conditions, stakeholder expectations or intended outcomes. If requirements then become the complete reference, omitted concerns become difficult to see. The representation does not merely simplify the subject. It starts defining the subject.
Reference Substitution Creates Circularity
The deepest consequence is circular reasoning.
Consider:
Current process → definition of capability → assessment of current process
or:
Existing product → requirements → tests → confirmation of existing product behavior
or:
Framework → transformation objective → maturity assessment against framework
The subject or its realization has contributed substantially to defining the criteria against which it is judged. The assessment may therefore prove consistency without proving suitability. This is why implementation independence matters. The Practice Notes argue that a Reference Model should separate intended understanding from current realization so that the subject can be developed and assessed without treating the current implementation as the definition of correctness.
Without that separation, Assessment can become self-confirming. Development can become reproduction.
Substitution Often Begins as a Practical Shortcut
Reference Substitution should not automatically be treated as negligence. Organizations often face incomplete understanding. People have left. Documentation is fragmented. The original business context no longer exists. The subject still needs to be maintained or changed. The current realization may therefore be one of the best remaining evidence sources. Using it is rational. The mistake is epistemic rather than practical: evidence about what exists becomes authority about what should exist.
A legacy system can tell us:
- what behavior currently exists;
- which interfaces currently operate; which dependencies appear active;
- which rules are encoded;
- which conditions the system has historically encountered.
It cannot by itself tell us:
- which behavior is still required;
- which interfaces should survive;
- which business rule remains justified;
- which historical compromise should be preserved;
- which quality characteristics matter now.
The realization is evidence. It is not automatically the reference.
Reference Substitution and Understanding Debt
The Practice Notes on old systems expose an important relationship. Organizations may keep systems alive not because they know the systems remain necessary, but because they no longer know enough to conclude safely that they are unnecessary. The retirement note describes exactly this condition: an obsolete-looking mainframe survives because nobody is sufficiently confident that some obscure process or dependency will not break if it is removed.
Loss of understanding therefore gives historical realization additional authority. The less the organization understands why something exists, the harder it becomes to distinguish necessary characteristic from historical accident.
That creates a paradox. The realization becomes more authoritative precisely because the understanding needed to challenge it has become weaker. Reference Substitution can therefore be viewed as one consequence of Understanding Debt.
Understanding Debt removes the basis for deliberate reasoning. The surviving realization fills the gap.
Substitution Can Preserve the Wrong Things
This mechanism explains a recurring organizational behavior. Organizations often preserve structures even when the function those structures were designed to serve has changed. A governance body survives. A process remains mandatory. A report continues to be produced. A system remains online. A requirement continues to be implemented. A role remains part of the operating model. Over time, the reason for the structure becomes less visible than the structure itself.
The organization then optimizes or protects the realization because it can still see it. The original function may no longer be examined. This means that continuity cannot simply mean preserving existing realizations. Sometimes continuity requires changing or removing them. To do that responsibly, the organization must preserve enough understanding to ask: What function needs to survive, rather than which structure needs to survive?
Reference Substitution makes those questions harder because the structure itself has become the reference.
Breaking the Substitution
The Practice Notes suggest that the response is not to ignore existing systems, frameworks, processes or requirements. They are valuable sources.
The response is to restore the distinction between source and reference. An existing realization can inform the Reference Model. A professional framework can inform the Reference Model. Requirements can form part of the Reference Model. Stakeholder views can inform the Reference Model. Operational evidence can challenge the Reference Model. But none of these automatically becomes the complete reference.
The practical questions therefore become:
- What is this source actually evidence of?
- Which parts represent enduring intent?
- Which parts reflect historical conditions?
- Which parts are assumptions?
- Which parts are still justified?
- Which important concerns are absent?
What alternatives would become possible if the current realization were not treated as authoritative?
These questions reopen the space for Development and Assessment.
Emerging Principle
The Practice Notes separately establish that explicit understanding weakens over time, surviving artifacts outlive their rationale, current realizations should remain distinct from Reference Models, requirements and frameworks are partial sources rather than complete definitions, and loss of understanding can make obsolete systems difficult to change. Taken together, they reveal a recurring substitution mechanism: When explicit understanding weakens, organizations tend to promote what survived from evidence about the subject into authority over what the subject should be.
This is Reference Substitution. Or more compactly:
When the reference disappears, the realization tends to take its place.
Synthesis Basis
This Synthesis Note was derived from Practice Notes concerning Reference Models, implementation independence, requirements, capability, transformation, Understanding Debt, legacy systems and preservation of rationale.
Primary Practice Notes
- A Reference Model Does Not Preserve Understanding by Itself: provides the clearest direct mechanism. It observes that when understanding becomes implicit and context disappears, surviving systems, processes, frameworks or requirements may become implicit definitions of what should exist. It also argues that the Reference Model should separate intended understanding from current realization. Loss of explicit understanding creates a vacuum that surviving realizations can fill.
- Building on Established Reference Models: establishes implementation independence as a defining property of the Reference Model perspective. The model must preserve intent and relationships without becoming inseparable from one implementation. A reference must remain sufficiently independent from one realization to support deliberate alternatives.
- What If Requirements Are Reference Models?: demonstrates that requirements may form part of the reference while still being incomplete. It explicitly asks whether missing quality attributes, stakeholders and success criteria undermine the assessment basis. A partial representation can become a substitute reference when its limited scope is forgotten.
- How Many Systems Did You Retire Last Year?: shows the practical consequence of lost understanding. Old systems may remain because the organization cannot confidently determine which behavior or dependencies still matter. Loss of understanding can give historical realization authority simply because the organization can no longer justify departing from it.
Supporting Practice Notes
- The Discipline of Curiosity: repeatedly moves Assessment from visible arrangements toward the purpose behind them and warns that the existence of a process, document or role does not establish the underlying ability. Visible realization should remain evidence about the subject rather than becoming the definition of the subject.
- Practice Notes concerning Product Reference Models establish that requirements stories and acceptance criteria are translations of wider product understanding, not substitutes for that understanding. Downstream representations become dangerous when they are promoted into complete upstream intent.
- Practice Notes concerning transformation and the recurring movement from What toward Why distinguish improving an existing process or implementing a framework from strengthening the underlying capability. Development can become trapped in the realization when the realization itself supplies the criterion for improvement.
- reference objects: provides the clearest everyday analogy. One realization can illustrate a category without defining it. An example becomes a substitute reference when its contingent properties are treated as universal criteria.
How the Synthesis Emerged
No single Practice Note needs the general concept of Reference Substitution. Several describe fragments of the pattern. One says that explicit understanding disappears while artifacts remain. Another distinguishes Reference Models from particular implementations. Another shows requirements as partial representations. Another shows frameworks and processes becoming mistaken for capability. Another shows legacy systems surviving because their rationale and dependencies can no longer be reconstructed.
Another shows concrete examples becoming implicit standards. Read separately, these are problems of documentation, assessment, transformation, modernization and abstraction. Read together, they reveal the same mechanism. Organizations still require a basis for judgment and Development after explicit understanding weakens. Something therefore occupies that role. The surviving object is usually the easiest candidate. Its original status changes silently:
realization → evidence → proxy → reference
That transition is Reference Substitution. The final synthesis is therefore: When an organization can no longer sufficiently reconstruct what a subject should be, it tends to infer that answer from what has survived. And that is how history can become authority without ever being deliberately chosen.
Leave a Reply