Overview
In this episode of The Dashboard Effect, Tracy Hockenberry, Senior Program Manager at Eaton and former Director of Enterprise PMO at New Story Schools, shares her firsthand experience leading BI initiatives through the organizational and human challenges that determine whether a data project delivers lasting change or a technically functional tool that nobody uses. The conversation covers the full arc of what a successful BI implementation requires, from executive alignment and stakeholder management through change management and adoption, with the kind of specificity that only comes from having navigated these dynamics in real organizations.
For anyone responsible for delivering a data initiative that needs to change how people work rather than just how data is stored, this episode offers a practitioner’s account of what that requires. See how Blue Margin’s Managed Analytics & Insights brings the external expertise and structured implementation approach that Tracy describes as essential for organizations that want to move quickly without building long-term internal overhead.
What This Episode Covers
The Necessity of Data Visibility (3:08 – 4:22)
As organizations grow, the fragmented, manual processes that served them at smaller scale become a liability. Spreadsheets maintained by individuals, reports assembled through email chains, and data living in disconnected systems create a version control problem and a visibility gap that limit decision-making quality. Tracy describes the implementation of a formal data strategy as a scaling necessity rather than a technology upgrade, and the goal of a single source of truth as the organizational benefit that justifies the investment.
Balancing Perfection vs. Progress (4:54 – 6:04)
The temptation to perfect data before building anything is one Tracy has encountered repeatedly, and her advice is consistent with the theme that runs through many conversations on this podcast: start, and use the process of starting to identify what actually needs to be fixed. She describes the fail forward approach as a faster path to accurate, trustworthy reporting than a data cleanup effort conducted in isolation from the reporting needs it is supposed to serve. The gaps that matter surface when you try to report on the data, not before.
Strategy and Stakeholder Alignment (10:18 – 12:56)
Three conditions are required for a successful data project according to Tracy’s experience: clearly defined strategic goals established at the executive level, genuine buy-in from stakeholders from the beginning rather than as an afterthought, and change management that builds individual employees’ awareness of and desire for the new habits the project requires. Each condition addresses a different failure mode, and the absence of any one of them tends to undermine the other two regardless of how well-executed the technical work is.
The Role of Project Management (14:47 – 16:14)
Tracy’s recommendation on stakeholder group size is specific and practical: too many voices in the dashboard design process stalls progress without improving the outcome. A smaller, focused group with clear authority to make decisions maintains the efficiency and clarity that complex design work requires. The broader stakeholder community has a role in adoption and feedback, but the design process itself functions better with fewer decision-makers rather than more.
Working with Outside Vendors (20:56 – 23:41)
Tracy makes the case for external expertise in two situations: when internal teams lack the specific skill sets a project requires, and when an organization wants to deliver specialized capability without building and maintaining a permanent internal function around it. She describes the value of a partner like Blue Margin in terms that are grounded in project reality rather than vendor promotion, which makes the endorsement more credible and more useful for organizations evaluating whether to build or partner.
Driving Adoption (24:20 – 27:04)
Technology does not drive adoption. Connection to individual motivation does. Tracy’s framework for adoption centers on helping employees see how clear, simple insights make their daily jobs easier and more impactful. That connection has to be made at the individual level, not just at the organizational level, because the people whose behavior needs to change are making decisions based on their own experience of the tool rather than the business case that justified building it. Adoption work that addresses that individual motivation is the kind that actually changes behavior.
Who It’s For
This episode is worth your time if you are a program manager, project lead, or data team director responsible for delivering a BI initiative that requires organizational change as well as technical delivery, an executive sponsor trying to understand what is required beyond technology selection and implementation to make a data project succeed, an internal team evaluating whether to build a BI capability in-house or partner with an external vendor and wanting a practitioner’s perspective on when the external route is the right one, or any organization where previous data initiatives have delivered technically but failed to produce the adoption and behavior change they were designed to support.
Why It’s Worth a Listen
Tracy Hockenberry brings a perspective that is grounded in organizational reality rather than technical prescription, and the specific details she offers about what stakeholder alignment, change management, and adoption actually require in practice are more useful than the same concepts stated in the abstract. Her experience spans different organizational contexts, which gives her observations broader applicability than a single-company case study would provide.
The project management recommendation around stakeholder group size is one of the most immediately applicable pieces of advice in the episode. The instinct to include more stakeholders in design decisions to build broader buy-in is understandable, but Tracy’s observation that too many voices stall design without improving outcomes is consistent with the experience of most practitioners who have managed complex projects. A smaller design group with clear authority and a broader communication strategy for the rest of the organization tends to produce better results and faster delivery.
And the adoption framing around individual motivation is worth carrying into every rollout conversation. The organizational case for a new tool is not what changes individual behavior. What changes individual behavior is a clear and personal answer to the question of how this makes my job better. Building that answer deliberately into the adoption strategy, rather than assuming it will emerge from the quality of the tool itself, is what Tracy identifies as the difference between rollouts that stick and rollouts that produce initial activity followed by quiet abandonment.
