I have now completed sixty posts.
The first retrospective examined the writing process. The second examined the emerging theory of product quality assessment. This time, the most interesting development may not be found inside any individual field note. It is found in the relationships between them.
What Happened?
During this cycle, the field notes moved across a much wider range of subjects. Some continued the work on product reference models, Product Ownership and assessment. Others explored system continuity, understanding debt, documentation and the preservation of knowledge. Then the notes wandered into watches, clothing, writing, storytelling and AI-assisted thinking.
At first glance, this might look as though the blog had started losing focus. Instead, something almost opposite happened. The same ideas began appearing in different places. A watch collection became an example of portfolio capability. A suit became an example of how an object can remain unchanged while its environment changes. A watch strap showed how changing a boundary changes what we perceive as the object. Inherited possessions became a way to understand the loss of system context. A comparison between two watches exposed the danger of replacing a reference model with a reference object.
The subjects changed. The method did not.
What Surprised Me?
The biggest surprise was that everyday observations did not merely illustrate ideas already developed in the papers. They generated new ideas.
The distinction between a reference model and a reference object emerged through a discussion about whether a Seiko could function as a dress watch. A Rolex may be one implementation of a dress watch. It is not the definition of one. Comparing another watch directly with it risks turning its particular design choices into assessment criteria.
The same mistake appears in transformation projects when the new system is expected to look and work like the old system. The old system becomes the reference object. And not even an obviously good one. It is the system that must be replaced.
That simple watch example made the software problem easier to see: We call it transformation, but make resemblance to the past the acceptance criterion.
The field note then produced a refinement that belongs back in the more formal work: A reference model describes required behavior and characteristics. A reference object shows one possible implementation of them. When the reference object replaces the reference model, one implementation quietly becomes the requirement. And QA verifies the implementation rather than the required behavior. The field notes have therefore become more than a way to communicate the theory.
They have become a way to develop it.
What Became Clearer?
Several recurring patterns are becoming visible.
The first is the separation of purpose from implementation. Requirements should describe required behavior, not merely reproduce an existing solution. Testing should verify behavior, not bind itself unnecessarily to implementation. Capability assessments should assess capabilities, not prescribe particular processes. Reference models should describe characteristics, behaviors and capabilities, not require resemblance to one preferred example.
The second pattern is continuity of understanding. A system can survive while the reasons behind it disappear. Source code, documents and tickets may remain available, while the organization gradually loses the ability to explain why a business rule exists, why a trade-off was accepted or whether an unusual behavior is deliberate.
This led to the idea of understanding debt: the accumulated gap between what the product embodies and what the organization can still explain with justified confidence.
The third pattern concerns communication. Facts do not automatically form an argument. Sentences do not automatically form a thought. Documents do not automatically preserve knowledge. Structure, context and story are not decoration added after the “real work” is complete. They help make meaning reconstructable.
The Field Notes Are Beginning to Reinforce One Another
During the previous cycle, I noticed that the product-quality notes formed a chain. This time, the effect became broader. A note about documentation strengthens a note about understanding debt. A note about understanding debt strengthens the case for Product Continuity. A note about reference objects strengthens the distinction between capability and process. A note about storytelling explains why the more conceptual notes become easier to understand when they begin with watches, clothing or inherited possessions.
Each note can still stand on its own. But later notes increasingly change how earlier ones are understood. The backlog is therefore no longer merely a queue of separate posts. It is becoming a body of work.
What Changed in the Writing?
The strongest recent notes often begin with something concrete and apparently insignificant. A watch. A suit. A photograph frame. An inherited object. A paragraph.
The reader can follow the observation without knowing anything about assessment, Quality Management or transformation. Only after the principle has become visible does the note pivot toward software or organizations. That pivot is often where the note acquires its real meaning.
Starting with transformation theory would require the reader to accept an abstraction. Starting with a watch allows the reader to discover the abstraction first. The professional problem is then judged by a principle the reader has already understood.
This may be becoming the characteristic form of these field notes:
Begin with an object.
Discover a distinction.
Follow it into another domain.
End by revealing that the original subject was never really the subject.
What Remains Unproven?
The growing coherence is visible to me because I have followed every conversation and written every note. It is not yet clear whether it is equally visible to a reader encountering the posts individually.
Several questions remain:
- Can readers recognize the recurring method without being given a map?
- Should related field notes be connected through synthesis pages or thematic collections?
- Can the new concepts be incorporated into the assessment, Product Continuity and transformation papers without making those papers unnecessarily broad?
- Do the everyday analogies clarify the professional ideas, or will some readers remember only the watches?
- Do these distinctions improve actual assessment and transformation work?
The theory is becoming richer. It must still become usable.
What Comes Next?
The next phase should probably combine continued exploration with more deliberate consolidation. The field notes can continue to capture new observations. There is no shortage of material.
But several ideas now deserve to be carried back into the formal papers:
- the distinction between reference models and reference objects;
- the danger of confusing required behavior with one existing implementation;
- understanding debt as the inability to explain what a product embodies;
- documentation as the preservation of reconstructable meaning;
- and field observations as a method for testing and refining conceptual models.
The blog itself may also need stronger thematic routes through the material. The chronological stream shows when the ideas appeared. It does not necessarily show how they belong together.
Conclusion
After the first twenty posts, I discovered a writing process. After forty, I could see an emerging theory. After sixty, I am beginning to see the method connecting subjects that initially appeared unrelated.
I thought I was collecting observations about quality, assessment, software, watches, clothing, writing and memory. Perhaps I was doing something else. Perhaps I was repeatedly asking the same questions:
- What is this really for?
- What characteristics matter?
- What should remain stable when the implementation changes?
- What knowledge must survive?
- How can we make the reasoning visible enough for someone else to continue it?
The individual field notes are becoming stronger. But their real strength may be that they are no longer entirely individual.
.
Leave a Reply