To me, if I think about Data Vault, I think about a proven, repeatable methodology that with the right ingredients and knowing how to mix them together, will deliver the outcomes you put the effort into, like baking bread!
A Data Vault (like baking) is not developed in isolation; it is reliant on people to be invested in the process and responsible for its outcomes, let’s list who they are.
Enterprise (data) architect (recommended-input) — to provide an overall picture of the enterprise business and data landscape. This role will also be aware of the current and future business capabilities, data governance practices. Providing clear definitions of important business roles, functions, policies, and interactions and where they see the data warehouse as a part of the enterprise capabilities.
Data architect/data steward (required-input/responsible) — in liaison with the EA the DA is aware of the current principles, policies, and practices within the data architecture space as well as data governance, data lineage, metadata management,
Solution architect (recommended-requirements/responsible) — a role familiar with current technology landscape and with the business hat on, the SA can also assist in identifying technology stack requirements (ex. ELT/ETL), Cloud infrastructure, data flows
