Lesson 10 — IT/Hybrid Roles and Decision Rules
Use the exact work product or responsibility in the stem. Do not choose a role merely because its title sounds more senior.
IT roles
- Data Architect — senior Data Architecture and data-integration direction; enterprise or functional.
- Data Modeler — captures detailed data requirements, definitions, business rules, DQ requirements, and logical/physical models.
- Data Model Administrator — model version control and change control.
- Database Administrator — design, implementation, and support of structured data assets and enabling technology performance/accessibility.
- Data Security Administrator — controlled access to data requiring different protection levels.
- Data Integration Architect — designs technology to integrate/improve enterprise data assets.
- Data Integration Specialist — implements replication/extract/transform/load flows in batch or near-real-time.
- Analytics / Report Developer — creates reporting and analytical application solutions.
- Application Architect — senior developer responsible for application-system integration.
- Technical Architect — coordinates/integrates infrastructure and technology portfolio.
- Technical Engineer — researches, implements, administers, and supports part of infrastructure.
- Help Desk Administrator — handles/tracks/resolves information, system, or infrastructure-use issues.
- IT Auditor — audits IT responsibilities including Data Quality and data security.
Hybrid roles
- Data Quality Analyst — judges fitness for use, monitors condition, performs/supports root-cause analysis, and connects business-process and technical improvement.
- Metadata Specialist — integrates, controls, and delivers metadata; administers metadata repositories.
- BI Architect — designs the BI user environment.
- BI Analyst / Administrator — supports effective business use of BI data.
- BI Program Manager — coordinates BI requirements and initiatives into a cohesive prioritized program/roadmap.
Fast role decision rules
- Business terms / valid values / DQ business rules / assigned-data accountability → Data Steward.
- Fitness monitoring / defect condition / root cause → Data Quality Analyst.
- Enterprise architecture / integration direction → Data Architect.
- Detailed logical/physical model and requirements → Data Modeler.
- Model version/change control → Data Model Administrator.
- Integration technology design → Data Integration Architect.
- ETL/replication implementation → Data Integration Specialist.
- Architecture standards / project approval → Architecture Review Board.
- Enterprise policy / accountability framework → Data Governance.
- Operational implementation of metadata, DQ, stewardship, etc. → Data Management Organization.
Final synthesis
Chapter 16 is a decision-rights chapter disguised as an organization chapter. When uncertain, return to three questions:
- What relationship or capability is being described?
- Is the issue guidance/accountability or execution?
- What exact work product distinguishes the nearest two roles/models?
Source anchor: Chapter 16, pp. 537–539.