FG-0808 Methodology Evolution
Description
The framework that governs the work must itself improve, or it ossifies into bureaucracy. Methodology Evolution treats the methodology as a versioned, evidence-driven artifact: methods are added when a pattern proves out across repeated practice, refined as evidence accumulates, and deprecated when superseded. Most methods exist because something went wrong and the system was built to prevent it, which means the methodology is never finished. It evolves on evidence drawn from the daily work it governs.
Implementation
Treat the methodology as a versioned artifact with an explicit changelog. Add a method only when a pattern has proven itself across repeated practice, not on a single instance or a theoretical concern. Refine existing methods as evidence accumulates about where they succeed and fail. Deprecate methods that are superseded, and record why. Review the methodology on a regular cadence against the failures and successes of the period, so the framework that governs the work is shaped by the work itself.
Success Indicators
- New methods enter only after a pattern has proven out across repeated practice
- The methodology has an explicit version and changelog, not silent edits
- Methods are refined and deprecated on evidence, with recorded rationale
- Each method can be traced to the real failure or success that motivated it
Failure Modes
- Adding methods from theory or a single incident, inflating the framework with untested process
- Letting the methodology calcify, so it governs the work long after the work has moved on
- Changing the methodology silently, so practitioners cannot tell what changed or why
- Never deprecating, so superseded methods accumulate and dilute the ones that matter
Sub-Methods 3
A method earns its place only after the pattern it describes has proven out across repeated practice. Adding methods from a single incident or a theoretical worry inflates the framework with process that has not been tested against reality.
Treat the methodology like any other versioned artifact: an explicit version, a changelog, and recorded rationale for every addition, refinement, and deprecation. Silent edits leave practitioners unable to tell what changed or trust that a change was deliberate.
When a method is superseded, deprecate it deliberately and record why, rather than leaving it in place. Superseded methods that linger dilute the framework and send practitioners down paths the evidence has already abandoned.