ABSTRACT
Documentation and governance are often the first things to suffer when pressure on the delivery team occurs. The longer that it is left to implement, then the harder it is to make it part of the structure of the code and the solution. If it is not done, then people will pay for this later down the line, when it must be bolted on and maintained separately. A well-designed data solution should be self-describing. The benefits of this are that it will be transparent, a little bit like showing people workings out when they are answering an exam question. This metadata will take the form of data quality dashboards, lineage, and provenance alongside their results. In the finance industry, this practice is now part of the regulatory framework that is monitored by the regulators, and the executives in the sector are held directly accountable for the accuracy and completeness of their reporting and operational data.
