A featured contribution from Leadership Perspectives , a curated forum for banking, financial services, and fintech leaders, nominated by our subscribers and vetted by the Financial Services Review Editorial Board.

Brown Brothers Harriman

A Governance - First Approach To Enterprise Data

Wael Taha, VP, Enterprise Architecture, Brown Brothers Harriman

Wael Taha

Governance First Champion

Data as a Decision-Making Asset

I’ve found that enterprise decisionmaking breaks down not because data is unavailable, but because it is fragmented, inconsistently structured, and lacks clear ownership. This has shaped my approach in three ways:

• Architecting for trust, not just access - I prioritize governance, lineage, and ownership models so leaders can trust the data behind decisions.

• Simplifying the data ecosystem - Reducing tool sprawl and redundant pipelines ensures decision-makers see a consistent version of truth rather than competing narratives.

• Elevating data as a strategic asset - By shifting from project-level analytics to enterprise platforms (semantic layers, knowledge graphs, AI-assisted querying), decision-making becomes faster, consistent and scalable.

Building a Governed Data Foundation

The biggest challenges are not technical, they are structural and organizational:

• Data fragmentation and duplication - Data exists across multiple systems with inconsistent definitions and formats

• Unclear ownership and accountability - When “everyone owns it,” no one truly owns it

• Tooling sprawl and technical debt - Multiple overlapping tools create inefficiency and governance gaps

• Weak governance and lineage visibility - Lack of traceability undermines trust and slows decisions

• Direct, uncontrolled data access patterns - Creates performance, security, and compliance risks

My Approach

• Establish a clear ownership model - Define accountable owners (business, platform, data steward) with escalation paths.

• Introduce a semantic and governance layer - For example, leveraging a centralized layer to enforce access control, lineage, and consistency

• Rationalize the technology landscape - Reduce duplication and standardize on strategic platforms (e.g., Power BI-centric model).

• Shift governance “left” - Embed standards, controls, and metadata requirements early in the development lifecycle.

• Align architecture with business workflows - Ensure analytics capabilities support actual decision journeys, not just reporting outputs.

The core principle: solve for ownership, governance, and architecture first, tools come second.

Aligning Data Strategy with Business Objectives

Alignment starts by reframing data strategy as a business capability.

My approach typically follows three steps:

Start with business outcomes

• Rather than asking “what data do we have?”, I focus on:

• What decisions need to be made faster or better?

• Where are the highest-friction processes?

Connect pain points to enterprise patterns

• Fragmented reporting → platform standardization

• Manual workflows → automation and ML

• Lack of trust → governance and ownership models

This ensures the strategy is anchored in real operational pain, not abstract architecture.

Build measurable capabilities through tangible outcomes like:

• Reduced time-to-insight

• Fewer duplicate pipelines

• Improved data quality and consistency

• Increased adoption of governed datasets

Future-Proofing Enterprise Data

Several trends are fundamentally reshaping the landscape:

• Semantic layers and data virtualization - Decoupling consumption from physical data storage

• Knowledge graphs and context-driven data - Moving beyond tables to relationships, ownership, and lineage

• AI / LLM-assisted analytics - Natural language querying and automated insights

• Shift toward governed self-service - Empowering users while maintaining control

• Platform consolidation - Reducing tool sprawl in favor of integrated ecosystems

How I’m Adapting

• Designing for AI-readiness from the start - Ensuring data is well-classified, governed, and context-rich

• Building a knowledge-centric architecture - Combining enterprise search, knowledge graphs, and analytics

• Investing in semantic layers - Creating abstraction between data sources and business consumption

• Balancing self-service with governance - Enabling users without creating “desktop chaos”

• Driving platform convergence – Reducing complexity and improve scalability

“I’ve found that enterprise decision making breaks down not because data is unavailable, but because it is fragmented, inconsistently structured, and lacks clear ownership.”

Cultivating Strategic Data Leadership

To grow into leadership in this space, I’d emphasize five areas:

Tools change quickly, focus on:

• Data architecture principles

• Governance and operating models

• Decision-making frameworks

Great data leaders:

• Understand how the business creates value

• Translate data into business outcomes

• Speak the language of executives

Master data ownership and governance

• Who owns the data?

• Who is accountable for quality?

• How is it governed?

Leadership is about:

• Reducing noise

• Creating clarity

• Driving alignment across stakeholders

Success depends on:

• Driving cross-functional alignment

• Communicating clearly at the executive level

• Framing problems strategically, not technically

The articles from these contributors are based on their personal expertise and viewpoints, and do not necessarily reflect the opinions of their employers or affiliated organizations.