When Governance Becomes a Technical Job Description
You Can’t Hire Governance Into a Data Platform
I recently came across a job advertisement seeking a principal data engineer to:
Design enterprise ETL/ELT pipelines
Architect and operate modern cloud data platforms
Implement governance capabilities through Microsoft Purview
Lead operational management of Microsoft Fabric
Establish enterprise data governance standards
At first glance, the role sounded ambitious but familiar, modern organisations are increasingly searching for technical leaders capable of integrating platforms, scaling data environments, implementing controls, and enabling governance capabilities across complex enterprise ecosystems.
But the deeper I read, the more the role reflected a growing industry pattern, the belief that governance itself can be implemented primarily as a technical capability, and that distinction matters.
Because governance is not a metadata catalogue.
Governance is not a lineage diagram.
Governance is not a platform feature.
“Governance is organisational decision infrastructure” - Fernleaf Learning
It defines how authority, accountability, ownership, escalation, and trust operate across the enterprise.
Yet increasingly, organisations appear to be collapsing governance, engineering, architecture, stewardship, operational support, and platform management into single technical leadership roles, expecting technology teams to solve problems that are fundamentally organisational in nature.
This is not a criticism of technical capability, modern platforms matter enormously, but platforms do not independently create governance maturity, and no organisation can hire governance into existence solely through a data platform team.
The Unicorn Role Problem
Across the industry, organisations are increasingly advertising for what can only be described as “unicorn” data roles.
One person is expected to:
Design and optimise enterprise ETL/ELT pipelines
Architect cloud data platforms
Manage operational data environments
Implement metadata and lineage capabilities
Establish governance standards
Drive governance maturity
Support business reporting
Manage platform security and controls and somehow align the organisation around trusted data
All within a single technical leadership position. At first glance, this sounds efficient. Modern platforms such as Microsoft Fabric, Microsoft Purview, Snowflake, and Databricks are powerful environments capable of integrating data, controls, metadata, and operational workflows at scale. It makes sense that organisations want technical leaders capable of bringing these environments together.
But hidden inside many of these role descriptions is a much larger organisational assumption, that governance itself can be implemented as a technical capability. This is where the problem begins, because engineering, architecture, platform operations, metadata management, and governance are not the same capability domains.
They intersect.
They support one another.
But they are not interchangeable.
A principal engineer can design exceptional pipelines.
An architect can create scalable platform structures.
A platform team can operationalise controls, lineage, and metadata visibility.
But none of these functions independently establish organisational authority.
They do not decide:
Who owns workforce data?
Whose financial definitions become authoritative?
Who approves supplier changes?
How unresolved disputes are escalated?
What level of risk is acceptable?
Who is accountable when data impacts decisions?
Those are governance decisions, and governance decisions do not originate from technology platforms alone.
What concerns me is not the ambition of these roles, it is the organisational expectation sitting behind them. Increasingly, organisations appear to be hiring technical specialists to compensate for unresolved leadership, ownership, and accountability structures. Instead of building governance as an enterprise-wide decision framework, governance is quietly being absorbed into platform teams as though metadata tooling and technical controls can substitute for organisational alignment.
The result is predictable.
Engineers inherit accountability without authority.
Business leaders disengage from ownership.
Governance becomes heavily operationalised but poorly legitimised.
And organisations mistake platform maturity for governance maturity.
This is not a criticism of technical teams. In many cases, engineers and architects are carrying responsibilities the organisation itself has not properly defined. The issue is that governance cannot be solved solely through technology implementation, because governance is not fundamentally a technology problem.
Governance is organisational decision infrastructure.
Platforms Are Not Governance
One of the most persistent misconceptions in modern data transformation is the belief that governance can be purchased through a platform, it cannot. Platforms matter enormously and modern organisations absolutely need strong technical capability across metadata management, lineage, classification, integration, security, and operational controls.
But platforms are not governance.
Microsoft Purview is not governance
Microsoft Fabric is not governance
Snowflake is not governance
Databricks is not governance
These platforms support governed environments.
They help operationalise governance.
They provide visibility, control, and scalability.
But they do not create governance maturity on their own.
A platform can:
Catalogue metadata
Trace lineage
Classify sensitive information
Automate controls
Enforce access policies
Monitor data movement
Expose quality issues
What it cannot do is resolve organisational ambiguity.
A platform cannot decide:
Which system is authoritative for workforce data?
Who owns supplier master records?
Whose financial hierarchy definitions prevail?
How accountability is escalated?
Which risks the organisation is willing to tolerate?
How competing operational priorities should be balanced?
Those are leadership and governance decisions, and this distinction matters more now than ever because organisations no longer operate inside single-system environments, most now operate ecosystems: HR platforms, finance platforms, procurement systems, analytics environments, operational applications, cloud integrations, automation layers, and external data exchanges all continuously interacting.
Governance exists across those relationships, not inside a single product.
The danger emerges when organisations begin treating governance tooling as though it replaces governance structures.
Because metadata visibility is not organisational accountability.
Lineage is not decision authority.
And technical controls are not the same thing as enterprise governance.
Governance Is a Leadership Structure
Governance exists wherever organisational authority exists.
In HR
In Finance
In Procurement
In Operations
In executive leadership
In risk management
In transformation programs
Not exclusively inside a data platform team. This is where many transformation efforts begin to struggle. The organisation invests heavily in cloud platforms, integration architecture, and modern data environments, while governance is quietly delegated downward into technical implementation teams.
But governance is not simply about controlling data movement, it is about legitimising organisational decisions.
Who can approve structural changes?
Who owns definitions?
Who resolves disputes?
Who accepts risk?
Who determines accountability?
Who has authority when systems disagree?
These are not technical questions alone, they are organisational governance questions, and modern enterprise environments make this even more complex.
The future is not a single system of record. The future is a governed network of systems sharing trusted data across operational and decision environments. Which means governance must operate horizontally across the organisation, not vertically inside one platform team. This is why governance maturity cannot be measured purely by technical implementation.
An organisation can have:
Sophisticated cloud platforms
Advanced integration pipelines
Automated lineage
Modern catalogues
High-performing engineering teams
and still have weak governance.
Because governance maturity is ultimately reflected in organisational behaviour:
Clarity of ownership
Decision escalation pathways
Stewardship accountability
Cross-functional alignment
Executive sponsorship
Operational trust
Technology can support those outcomes.
But leadership structures create them.
The Real Risk
When governance becomes a technical job description, organisations unintentionally create a dangerous structural imbalance.
Engineers inherit accountability without organisational authority
Business areas disengage from ownership because governance starts to appear like “the data team’s responsibility”
Platform maturity becomes confused with governance maturity
Unresolved organisational issues become buried beneath increasingly sophisticated technical solutions
The consequences are visible everywhere.
HR disputes definitions with payroll systems
Procurement operates duplicate supplier records across platforms
Finance reconciles inconsistent reporting structures between operational and reporting environments
Data teams spend years building pipelines around unresolved ownership conflicts instead of addressing the underlying governance issues themselves
Meanwhile, governance initiatives become trapped in implementation cycles: more tooling, more metadata, more dashboards, more controls, and more architecture, while the core organisational questions remain unresolved.
Who decides?
Who owns?
Who is accountable?
Who has authority?
This is why many governance programs appear technically active but organisationally ineffective. The organisation mistakes operational activity for governance capability, but governance failure is rarely caused by a lack of technology.
More often, governance failure emerges from:
Fragmented accountability
Unclear ownership
Weak executive alignment
Avoidance of difficult organisational decisions
Absence of legitimate decision infrastructure
No metadata catalogue can solve that independently.
Technology Still Matters
None of this diminishes the importance of technical capability, modern governance absolutely requires strong technical enablement.
Metadata matters.
Lineage matters.
Integration architecture matters.
Security controls matter.
Operational monitoring matters.
Platforms such as Microsoft Purview and Microsoft Fabric provide critical capabilities that many organisations genuinely need, the problem is not the technology. The problem is the expectation that technology alone can compensate for unresolved organisational governance.
Technology operationalises governance, it does not replace governance.
And technical teams should not be expected to carry enterprise governance maturity alone. The strongest organisations understand this balance clearly.
Engineering teams enable trusted environments.
Architects design scalable ecosystems.
Platforms operationalise controls.
Leadership legitimises governance.
Because governance is ultimately not about tools, it is about organisational authority, accountability, and decision-making operating coherently across complex environments.
“Governance is decision infrastructure. Technology helps implement and scale it. Leadership makes it real.” - Fernleaf Learning
Organisations cannot solve governance simply by hiring increasingly technical unicorn roles, because governance failure is rarely caused by a lack of metadata, lineage, or platform capability.
It is usually caused by:
Unclear authority
Fragmented accountability
Unresolved ownership
Weak stewardship
Leadership structures that avoid difficult organisational decisions
Modern platforms are extraordinarily powerful, but no platform can independently govern HR accountability, procurement authority, financial ownership, operational escalation, or executive decision-making.
Those responsibilities still belong to the organisation itself.
The future of enterprise data is not a single platform solving governance through technology alone, it is a governed ecosystem of systems, decisions, accountabilities, and leadership structures working together to create trusted data environments.
“Platforms change. Governed data endures.” - Fernleaf Learning