The analytical mind behind products that move data forward.

I don't just manage data products, I architect them, govern them, and obsess over the metrics that prove they're working. From regulatory BI tools to enterprise data models, I bring strategy, technical depth, and leadership to every product I own.

7+

Years in data roles across energy, finance & public sector

71%

Reduction in data model processing time (94 → 27 mins)

98%

UAT model-to-bill alignment on regulatory billing product

How I think about data products.

Systems Before Solutions

Before I write a single requirement, I map every dependent system. Good data products don't exist in isolation, they're nodes in a larger ecosystem.

Quality is the Product

A single dirty record can invalidate a 98% accurate model. I treat data quality not as a prerequisite but as the primary feature of every product I build.

Strategy Meets Execution

I close the gap between executive vision and engineering reality. Agile delivery, clear user stories, and rigorous backlog management are how strategy ships.

My Story - From geology to governance, a career built on data.

My data journey began in the field "literally". As an intern at Chevron, I was entrusted with designing QA protocols for reservoir simulation data, where I learned a foundational truth: the quality of your data determines the quality of every decision made downstream. That lesson has never left me.

From there, I moved into Richardson Oil & Gas, where I led the data transition for an organization-wide ERP implementation. I wasn't handed a playbook, I wrote one. I built the MDM processes, trained the staff, and earned enough trust from the Managing Director to be delegated the company's entire data strategy. That was my first taste of leading without a title.

My Master's research gave me my first official data product. I built a full BI tool in Excel, connected to a structured database back-end, powered by @Risk for probabilistic modeling, to compare the economic efficacy of Nigeria's PIA against six global petroleum fiscal systems. I defined the requirements, architected the system, and delivered the insight. That was product ownership before I had the job title.

Through FIRS, VEE, and the BC Public Service, I grew from building individual reports to founding BI departments and managing the full lifecycle of enterprise data products. The defining moment came at BC, where I reduced a critical data model's processing time from 94 minutes to 27 minutes — a 71% improvement — by leading a full architectural rework with complete technical authority.

Today at NT Power, I manage a portfolio of mission-critical data products in the utility sector, from regulatory billing models to DER visualization platforms — where compliance, auditability, and performance are not nice-to-haves but core product features.

Technical Toolkit - Skills & capabilities.

Data & Analytics

Power BISQLPython / PandasExcel (Advanced)@RiskMS ProjectMicrosoft Access

Product & Delivery

Agile / ScrumBacklog ManagementUser Story WritingUAT ManagementRoadmappingSprint Planning

Governance & Architecture

Master Data ManagementData LineageData Quality FrameworksRegulatory ComplianceWBS DesignETL Pipelines

Leadership & Stakeholder

Executive ReportingCross-functional LeadershipChange ManagementRequirements GatheringTeam Building

How i work - My approach to data product management.

01

Discover & Map the System

Every engagement begins with understanding the full data landscape — active tables, relationships, dependencies, and bottlenecks. I draw the map before I plan the route.

02

Define Quality as a Feature

I establish data quality standards, governance protocols, and validation criteria before any development begins. These aren't after-thoughts — they're the product spec.

03

Build Iteratively with Stakeholders

Using Agile methodology, I run tight feedback loops between engineers, analysts, and business leads.

04

Measure, Monitor, Optimize

Delivery isn't the end. I establish monitoring procedures, track performance metrics, and iterate continuously — because a data product is only as good as its last refresh.

FacebookXLinkedInNotionGitHubInstagramMediumDiscord

Let's
Connect

Designed & Built by @Idowu 💙