Overview
In this episode of The Dashboard Effect, Brick Thompson, CEO of Blue Margin, sits down with seasoned CIO John Manzanares for a conversation that spans data strategy, the evolving role of technology leadership in PE-backed firms, and the practical realities of navigating AI adoption in an environment where the tools are advancing faster than most governance frameworks can keep up. John brings a perspective shaped by years of operating at the intersection of technology and business leadership, and his views on where CIOs create the most value are consistently more grounded than the vendor-driven narratives that tend to dominate these conversations.
For PE operating partners, technology leaders, and anyone trying to build a data strategy that delivers business results rather than just technical infrastructure, this episode offers a clear and experienced perspective on what that work actually requires. See how Blue Margin’s Private Equity Analytics & Data Dashboards helps PE-backed companies build the data foundation John describes, faster and with less engineering overhead than traditional warehouse approaches require.
What This Episode Covers
Data Strategy in Buy-and-Build (2:04 – 9:15)
For PE firms executing multiple acquisitions, building a traditional data warehouse from the ground up is a significant undertaking that often cannot keep pace with the speed of deal activity. John’s framing is business-first: the primary goal of data strategy in a buy-and-build context should be identifying the key operational metrics that drive efficiency and performance, not just achieving financial consolidation. The infrastructure choices follow from that clarity about what the business needs to see, not the other way around.
The CIO as a Business Leader (10:04 – 12:03)
John makes a point that is worth hearing directly from someone who has operated in the role: IT projects are business projects with a technical component, not the reverse. CIOs who lead with technology and seek business alignment afterward tend to build things that are technically sound and organizationally irrelevant. The ones who create lasting value are those who start with revenue impact, cost savings, or risk mitigation and then identify the technical approach that delivers it.
Data Lakes vs. Data Warehouses for PE-Backed Companies (24:28 – 29:30)
The conversation covers the practical case for data lakes over traditional Kimball-style data warehouses in PE-backed multi-entity environments. The speed-to-value advantage of a data lake approach, which enables consolidated reporting and ad-hoc analysis without the long engineering lead times a traditional warehouse requires, is particularly significant when portfolio companies are being integrated at a pace that a warehouse build cannot match. John and Brick align on this as the more practical path for most mid-market PE contexts.
The Future of AI and Data Reporting (31:16 – 35:30)
The hosts anticipate that tools like Microsoft 365 Copilot and large language models will fundamentally change how executives interact with data, potentially allowing natural language querying to handle many of the day-to-day operational questions that currently require a dashboard or a data team to answer. That shift is coming, and organizations that have built clean, well-structured semantic layers will be positioned to take advantage of it. Those that have not will find the tools producing confident-sounding answers that cannot be trusted.
Navigating the AI Wild West (37:30 – 44:00)
A significant portion of the conversation focuses on the risks that come with AI adoption at the current stage of the technology’s maturity. John is direct about the limitations: LLMs are powerful but not infallible, and hallucinations and security concerns are real risks that organizations cannot dismiss because the tools are impressive. His practical guidance is to implement strict policies around confidential data handling, focus on employee education about what these tools can and cannot do reliably, and resist the pressure to move faster than the governance frameworks can support.
Who It’s For
This episode is worth your time if you are a CIO or technology leader at a PE-backed company trying to build a data strategy that earns credibility with the business rather than just satisfying technical requirements, a PE operating partner evaluating technology leadership and data strategy across portfolio companies and wanting a framework for assessing what good looks like, a CFO or CEO navigating an AI adoption conversation internally and wanting a balanced perspective on the risks that the enthusiast narrative tends to underweight, or any organization that is executing a buy-and-build strategy and trying to understand how to build consolidated data visibility without waiting for full ERP integration to make it possible.
Why It’s Worth a Listen
John Manzanares brings the kind of perspective that only comes from having operated in senior technology leadership roles through multiple business cycles and technology transitions. His framing of the CIO as a business leader first is not a platitude. It is a description of the specific failure mode that most technology-led data initiatives fall into, and hearing it articulated by someone who has seen both sides of that failure makes it more credible and more actionable than the same point made in the abstract.
The AI wild west discussion is the most timely part of the conversation. The pressure to adopt AI tools quickly is real and often disconnected from the governance infrastructure required to use them safely with confidential business data. John’s recommendation to focus on education and strict policy before broad adoption is a measured and defensible position that organizations can actually implement, rather than a theoretical caution that leaves teams without practical guidance.
And the data lake versus warehouse comparison in the PE context is worth hearing from a CIO who has navigated both approaches in real buy-and-build environments. The speed-to-value argument for data lakes is well-established in theory, and John’s operational experience with what that difference looks like in practice gives it more weight than a vendor comparison would provide.
