Configuration documentation is a clear example where traditional delivery practices need to evolve, as evidenced with what Oracle has recently announced with the Fusion Setup and Configuration Registry (FSCR) here. Many programmes still rely on functional configuration workbooks, security matrices and design descriptions maintained in Word, Excel or diagramming tools. These artefacts are often useful during implementation, but they can become stale almost immediately.
The opportunity, therefore, is to move from static documentation to live insight. Rather than asking teams to maintain a separate version of the truth, the direction of travel now is to deploy capabilities that can query live configuration, security models and design intent in natural language.
With this model, documentation should be generated from live system information to support and provide assurance, rather than maintained separately as a duplicate record. But remember, querying current configuration can show what is configured now – it doesn’t necessarily explain why a decision was made, who approved it or what was previously in place. Ease of live insight should therefore complement decision records, approved baselines and change history – not replace them.