← All case studies Utilities

Inside a leading U.S. utility's first Technical Program Management Office for Enterprise Data & Analytics

A new TPMO transformed a growing portfolio of data and analytics initiatives into a coordinated enterprise capability, connecting business priorities, technical teams, parallel utility use cases, and measurable business value.

A program team reviewing roadmaps on a wall in a dim office overlooking a city skyline at night

Agile Brains helped one of the largest investor-owned energy delivery organizations in the United States establish its first Technical Program Management Office (TPMO) within Enterprise Data & Analytics, creating the governance, delivery structure and cross-functional coordination required to manage multiple high-value data and analytics initiatives in parallel.

About the client

The utility provides critical electric, gas and steam service across one of the world's most complex urban environments. Its regulated operations serve approximately 3.7 million electric customers and 1.1 million gas customers in a service territory of more than nine million people. It also operates the largest steam distribution system in the United States, supplying approximately 1,500 customers across some of the most densely developed commercial real estate in the country.

With a history of more than 200 years, the organization has evolved from a traditional utility into an increasingly data-driven enterprise, using advanced analytics, smart-meter data, automation and emerging technologies to improve reliability, customer experience, operational efficiency and the transition to cleaner energy. Millions of smart meters and numerous enterprise systems generate enormous volumes of operational, customer, asset and energy-consumption data, creating both tremendous opportunity and significant delivery complexity.

The challenge

The utility's Enterprise Data & Analytics organization was increasingly being asked to solve important business problems across the enterprise. Business areas were finding places where data, analytics, automation and advanced modeling could make a difference: grid and asset reliability, customer experience, operational efficiency, field operations, energy forecasting, smart-meter operations, revenue protection, clean-energy planning, customer and usage analytics, and regulatory and management reporting.

The challenge was no longer identifying valuable data opportunities. It was executing many of them simultaneously. Each use case could involve business stakeholders, data engineers, data scientists, architects, technology teams, cybersecurity, infrastructure, external partners and operational subject-matter experts. Without an enterprise-level program structure, every initiative risked operating as an independent project, with its own planning method, reporting, governance, priorities and definition of success.

Enterprise Data & Analytics needed consistent answers across the whole portfolio: which use cases are worth the most, what comes first, who owns each one, what depends on what, whether there is capacity to deliver, which decisions are blocking progress, and what value is being created.

How we helped

Agile Brains partnered with Enterprise Data & Analytics leadership to establish the organization's first dedicated TPMO, designed to work differently from a traditional PMO. Rather than functioning primarily as a reporting and administrative layer, it became an execution and orchestration capability connecting business priorities, technology teams, data capabilities and measurable outcomes: enough structure to coordinate a complex portfolio, while keeping the speed and experimentation data and analytics work requires.

A clear structure and clear decision rights. We helped define the TPMO's organizational structure, roles, governance model, delivery processes and management cadence. Enterprise Data & Analytics leadership set strategic direction, investment priorities, organizational outcomes and executive sponsorship. The TPMO owned portfolio planning, prioritization, dependency and risk management, governance, executive reporting, delivery coordination and business-value tracking. Technical program managers owned end-to-end coordination of major programs and use cases; product and business owners defined problems, outcomes, requirements and measures of success; and data and technology teams built the pipelines, analytics, models, integrations, platforms and dashboards. The result was a management layer that could see across initiatives rather than optimizing each use case on its own.

A portfolio, not a collection of projects. Analytics initiatives were treated as a portfolio of business-value opportunities rather than a collection of unrelated technology projects, moving along a structured path from identification and assessment through prioritization, planning, delivery, validation and scale. Use cases were weighed on business value, customer impact, operational efficiency, safety and reliability, strategic alignment, regulatory importance, data availability, technical complexity, delivery effort, dependencies, organizational readiness and expected time to value, so leadership could make informed decisions about where analytics capacity should be invested.

Many utility use cases, running in parallel. Utility analytics rarely involves one isolated problem. The TPMO provided a common management framework across grid and asset analytics, smart-meter and AMI analytics, customer analytics, field and operational analytics, revenue and usage analytics, energy and load forecasting, and clean-energy analytics covering electric vehicles, heat pumps and distributed energy resources. Each use case kept its own objectives and technical solution, while the TPMO kept visibility across owners, delivery teams, milestones, dependencies, risks, decisions and value. When several initiatives depended on the same data source, architecture component, engineering team, platform or stakeholder, the conflict surfaced at the portfolio level instead of late in delivery.

A consistent delivery rhythm. Use cases moved through incremental stages, from discovery and design to build, test, demonstration, learning and scale, so teams didn't have to wait months to learn whether an analytics idea would create value. Regular delivery reviews provided visibility into progress, impediments, dependencies, risks, decisions and upcoming milestones, and executive portfolio reviews gave leadership one consolidated view instead of dozens of individual project updates.

Business problems first. Data and analytics initiatives can easily become technology-driven exercises. Every initiative here started from the business problem and the desired outcome, then worked through the data required, the analytics capability and the technical delivery. Governance was built to speed decisions, not add bureaucracy: portfolio prioritization, integrated roadmaps, use-case intake, dependency, risk and issue management, decision tracking, capacity visibility, business-value tracking, delivery health reviews and clear escalation paths.

Building the technical program manager capability. Creating the office took more than designing processes. Agile Brains coached the technical program managers to operate beyond traditional project administration, at the intersection of business, data, technology, people, dependencies and value. They became the translators and orchestrators who connect teams, anticipate dependencies, facilitate decisions, remove organizational impediments, maintain executive visibility and keep multiple workstreams moving toward measurable outcomes.

The result

Enterprise Data & Analytics gained a centralized capability for managing an increasingly complex portfolio of strategic data initiatives. Leadership now has a portfolio-level view of priorities, capacity, dependencies, delivery health, risks and expected business value, and can make trade-off decisions across the portfolio rather than responding to the loudest or most urgent request. Business stakeholders have clearer visibility into where their initiatives stand and which decisions are required, and data and technology teams work iteratively with clearer priorities while staying connected to enterprise objectives.

The engagement changed the question the organization asks, from "How do we manage this analytics project?" to "How do we manage an enterprise portfolio of data investments to maximize business value?" For an organization operating one of America's most complex energy systems, the TPMO provided more than project governance. It created an execution engine for Enterprise Data & Analytics, allowing multiple teams, technologies and utility use cases to move forward in parallel while maintaining alignment, transparency, accountability and focus on business value.

What the utility gained

  • Its first dedicated Technical Program Management Office for Enterprise Data & Analytics, with a defined structure and operating model
  • Clear roles, responsibilities and decision rights
  • Standardized intake and prioritization for analytics opportunities
  • Portfolio-level planning and integrated roadmaps connecting initiatives, milestones and dependencies
  • Greater visibility into capacity and resource constraints
  • Common risk, issue, dependency and decision management, with consistent executive reporting
  • Technical program managers capable of coordinating business and technology
  • Iterative delivery practices that let teams demonstrate value earlier
  • A repeatable approach for moving analytics ideas from opportunity through production
  • A scalable management capability ready for future data, analytics, AI and automation initiatives

Next step

Bring us the problem as it actually is.

A direct conversation about where you stand and what will actually work. No deck required.

Book a consultation