Overview
In this episode of the Expert Insights Series, Greg Brown of Blue Margin sits down with Anthony Algmin, a data luminary whose perspective on what data is actually for cuts through the technical complexity that often obscures the point. The conversation is refreshingly direct: data’s value is not in its existence or its architecture. It is in whether it changes what people do. Everything else is infrastructure in service of that outcome.
For data leaders and business executives trying to connect data investment to business impact rather than just technical capability, this episode provides both a philosophical reframe and a practical set of priorities for where to focus. See how Blue Margin’s Managed Analytics & Insights helps organizations build the visibility and alignment that turns data from a technical asset into a genuine change agent for the business.
What This Episode Covers
Data as a Change Agent (1:30 – 2:35)
Algmin’s framing is precise and worth internalizing: data is the closest thing to truth an organization has, but its value is only realized when it drives new decisions or changes in activity. Data that is collected, stored, and reported without producing any change in behavior is infrastructure without a return. The goal of every data initiative, properly understood, is not to produce information but to produce change, and evaluating initiatives by that standard produces a fundamentally different set of priorities than evaluating them by technical completeness.
The Business-First Mentality (5:30 – 7:20)
Chasing the latest technology trend without a clear connection to a business problem is one of the most consistent ways data initiatives fail to deliver. Algmin’s recommendation is to start with visibility: use data to understand where the business actually stands and where the problems are before deciding what tools or approaches to apply. The Chicago Transit Authority example he references illustrates the point concretely, showing how visibility into an operational problem creates the clarity needed to address it rather than obscuring it behind the complexity of a solution in search of a problem.
Curiosity over Certainty (9:10 – 10:40)
The distinction Algmin draws between data-driven and data-justified leadership is one of the most practically important in the episode. Data-justified leadership uses data selectively to validate decisions that have already been made, which produces the appearance of rigor without the substance. Data-driven leadership approaches data with genuine curiosity, looking for what is actually true rather than for confirmation of what is already believed. That distinction is primarily a mindset distinction rather than a technical one, and it is what determines whether data actually informs decisions or merely decorates them.
The Flashlight Approach (7:40 – 8:25)
Rather than using data immediately as a carrot or stick to evaluate and incentivize performance, Algmin recommends using it first as a flashlight: illuminating where problems exist and creating the shared visibility that allows teams to solve them collaboratively. That approach builds trust in the data and in the process of using it, which is the foundation that more sophisticated applications depend on. Organizations that skip the flashlight phase and go directly to accountability tend to produce defensiveness rather than improvement.
Master the Basics Before Scaling (13:30 – 14:50)
Algmin’s practical advice on sequencing is consistent with what the most experienced practitioners in this space recommend: clean transactional data and solid master data management are prerequisites for complex AI and machine learning projects, not parallel workstreams. Organizations that attempt to build advanced capabilities on a foundation of unreliable basic data find that the advanced tools amplify their data quality problems rather than compensating for them. Getting the basics right is not a delay. It is the most direct path to making the advanced capabilities actually work.
Visibility and Organizational Alignment (16:00 – 17:20)
New reporting that increases the volume of available information without improving how decisions are made adds noise rather than value. Algmin emphasizes that the goal is not more data but better-aligned data: reporting that connects directly to the decisions that affect business operations and that is understood and trusted by the people making those decisions. Organizational alignment around what the data means and what it is asking people to do is what converts reporting from a reporting function into a decision support function.
Who It’s For
This episode is worth your time if you are a data leader or CDO trying to frame the value of data investment in terms that resonate with business leadership rather than technical stakeholders, an executive who has invested in data capabilities without seeing the business behavior change those investments were supposed to produce, a practitioner who wants a grounded perspective on how to sequence data initiatives from foundational visibility through advanced analytics without skipping the steps that make each layer work, or anyone who has noticed that the data in their organization is being used more to justify decisions already made than to genuinely inform decisions yet to be made.
Why It’s Worth a Listen
Algmin’s framing of data as a change agent rather than an asset or a capability is one of the cleaner articulations of what data work is actually for, and it produces a useful test for evaluating any data initiative: will this change what people do, and if so, how? Initiatives that cannot answer that question with specificity are worth examining before they consume significant investment.
The data-driven versus data-justified distinction is worth carrying into every conversation about how an organization uses its reporting. The two look similar from the outside, but they produce fundamentally different organizational relationships with data over time. Organizations that are genuinely curious tend to find things they did not expect and act on them. Organizations that are primarily seeking confirmation tend to find what they are looking for and stop there. The difference shows up most clearly when the data says something inconvenient, which is exactly when it is most valuable.
And the flashlight approach is a genuinely useful reframe for organizations trying to introduce performance visibility without triggering the defensive reactions that accountability-first approaches consistently produce. Illuminating problems before assigning responsibility for them creates the collaborative problem-solving dynamic that makes data culture sustainable, and this episode articulates why that sequence matters in a way that is practical enough to apply immediately.
