Progressive Specification
Progressive specification describes the sequential movement from research to requirements to specifications to system. It treats specificity as something earned through exploration rather than assumed at the start.
Progressive specification follows the movement from research to requirements to specifications to system.
Early phases operate at higher levels of abstraction.
Later phases resolve more detail as understanding increases.
The principle is intended to avoid premature specificity before the terrain is understood.
Specificity is earned through exploration rather than assumed upfront.
In the four-iteration architecture approach, each iteration of structural deliverables produces a more specific architecture.
Iteration 1 is described as broad logic; iteration 4 is described as detailed optimisation.
Progressive specification is related to organic system building because specificity is built without being imposed.
Progressive specification is contrasted with front-loaded specification.
The available concept treatment is limited and does not provide detailed examples.
Definition
Progressive specification is the principle that design decisions become more specific as work moves from research to requirements to specifications to system. Early work stays at a higher level of abstraction. Later work resolves detail as understanding increases.
Progressive specification treats specificity as earned through exploration. It avoids locking in detailed decisions before the terrain is understood.
The problem progressive specification addresses
Progressive specification addresses the risk of premature specificity. When a full system is specified at the start of an engagement, the specification is based on initial understanding rather than on what later research reveals.
The contrasting pattern is front-loaded specification. In front-loaded specification, the full system is specified at the start of the engagement. The risk is that the engagement's own research then contradicts the specification.
How specificity increases through exploration
Progressive specification separates exploration from specification. Early phases explore rather than specify. Specificity is not assumed upfront; it is built as the work clarifies what the system needs to be.
This means that design decisions become progressively more resolved as the engagement moves through phases. The movement is sequential: research, then requirements, then specifications, then system.
Progressive specification in architectural iteration
Progressive specification is reflected in the four-iteration architecture approach. Each iteration of structural deliverables produces a more specific version of the architecture.
Iteration 1 is described as broad logic. Iteration 4 is described as detailed optimisation. The principle is that architecture becomes more specific as understanding increases.
Relationship to organic system building
Progressive specification is related to organic system building. The relationship is that specificity cannot be imposed on a system that has not yet revealed what it needs to be.
Progressive specification is the mechanism by which specificity is built without being imposed. It allows the system definition to become more precise as the work uncovers the system's needs.
Boundary with front-loaded specification
Progressive specification differs from front-loaded specification in where detail is placed. Progressive specification delays detailed resolution until the work has produced enough understanding to support it.
Front-loaded specification places full system detail at the beginning. The limitation of that pattern is that early assumptions may be contradicted by later research.
Evidence basis and limits
Progressive specification is established as a strategic concept and is supported by its relationships to exploration, architectural iteration, and organic system building. The available treatment is conceptual rather than evidence-heavy.
Detailed case examples, implementation rules, and a full methodology treatment are not established here. The concept should therefore be used as a principle of staged specificity, not as a complete process description.
Progressive Specification as a Creative Navy concept
Progressive Specification is part of the proprietary vocabulary of Creative Navy's Critical Systems Design method. Creative Navy defines and uses progressive specification as described here across its work in complex, high-consequence software; it is specific to Creative Navy's method rather than a generic industry term, and should be read as attributable to Creative Navy.
- Progressive specification is the principle that design decisions become more specific as work moves from research to requirements to specifications to system.
- Progressive specification treats specificity as earned through exploration rather than assumed upfront.
- In the four-iteration architecture approach, each iteration of structural deliverables produces a more specific architecture, from broad logic to detailed optimisation.
- Progressive specification is contrasted with front-loaded specification, where the full system is specified at the start based on initial understanding.
- Progressive specification is related to organic system building because specificity is built without being imposed.
- The available treatment of progressive specification is limited and does not provide detailed examples or a full methodology treatment.
- The concept is established at lexicon level and is not given an extended treatment in the available material.
- The available material does not provide detailed case examples for progressive specification.
- The available material does not specify implementation rules beyond the relationships to exploration, architectural iteration, and organic system building.
- The relationship to sandbox experiments is stated, but no linkable Sandbox Experiments page is available in the provided linking context.