Advisory · Organisation · Development
Data strategy & data management
1. Brief service summary
Specify the role of data in a digital transformation and organise the initial management choices required. The engagement connects business uses, systems and responsibilities to prepare data work without presuming a complete overhaul of the domain.
2. Your needs
A digital programme depends on data whose sources, definitions or owners are poorly identified. Projects envisage exchanges or analyses without sufficiently specifying usage conditions.
You wish to avoid discovering data questions late, after tool selection or commitment to work.
3. Objectives of the engagement
The engagement aims to identify the programme’s data needs, examine existing capabilities and prepare responsibilities and priorities. It helps connect architectural choices with uses actually expected.
The objective is to make dependencies and workstreams requiring examination visible, without treating all organisational data as a uniform scope.
4. Indicative scope
The work may cover domains needed for transformation, sources, exchanges, definitions and initial management rules. Quality, governance and security needs are identified with proposed responsible persons.
This service prioritises the relationship between data and digital transformation. Enterprise data strategy, detailed governance or in-depth integration architecture falls under specialist services in practice 19.
5. Possible delivery arrangements
Business and IT interviews, review of available descriptions and workshops help prepare the framework. Analysis may use authorised models or examples; access to real data is not presumed necessary by default.
6. Possible deliverables
Deliverables may include a data-dependencies map, management principles, proposed allocation of responsibilities and a plan of additional work.
7. Conditions and limitations
The engagement does not automatically perform cleansing, integration, migration or analytical processing. Usage rights, access and transfers must be checked. No overall data quality is guaranteed. The boundary with 19.02 is set in the proposal to avoid selling two equivalent scoping engagements.

