Overview
In this episode of The Dashboard Effect, Brick Thompson and Caleb Oaks describe a pattern that plays out repeatedly in mid-market companies that try to build internal data teams: the turnover treadmill. The cycle is familiar to anyone who has lived through it. A capable data hire builds institutional knowledge, leaves for a larger company or better opportunity, and the organization starts over with someone new who has to rebuild what was lost. The conversation covers why this pattern is so persistent and what the structural alternative looks like for companies that want continuity without the overhead of managing it themselves.
The episode makes the case for the fractional data team model as a more sustainable approach for mid-market companies, grounded in the specific ways that model addresses the problems internal teams create. See how Blue Margin’s Managed Analytics & Insights provides the fractional data team model the hosts describe, delivering consistent expertise, preserved institutional knowledge, and the right skill set at every stage of the data journey without the recruiting, retention, and knowledge transfer challenges of building internally.
What This Episode Covers
The Challenge of Internal Teams (9:33 – 10:20)
Small internal data teams, often just one or two people, carry a disproportionate amount of institutional knowledge relative to their size. When those people leave, the knowledge leaves with them, and the organization faces not just a hiring problem but a reconstruction problem. Compounding the challenge, top-tier data talent consistently gravitates toward larger tech companies where the work is more complex, the compensation is higher, and the career trajectory is clearer. Mid-market companies are competing for talent in a market that is structurally tilted against them.
The Need for Continuity (2:52 – 3:30)
Data transformation is not a project with a completion date. It is a continuous process of iteration, maintenance, and evolution that responds to how the business changes over time. Organizations that approach it as a one-time initiative find that the work undone by turnover is not just the replacement of a person but the loss of the ongoing process itself. Continuity in the team is what keeps that process moving forward rather than resetting every time someone leaves.
The Fractional Data Team Advantage (5:36 – 6:47)
Blue Margin’s fractional data team model addresses the turnover problem structurally rather than symptomatically. By partnering with a dedicated firm, mid-market companies gain access to a full range of data capabilities without managing the hiring, retention, and knowledge transfer challenges that come with building those capabilities internally. The firm absorbs the turnover risk, maintains the institutional knowledge, and provides consistent service regardless of individual personnel changes. For PE-backed companies where data infrastructure is a value creation lever rather than a core competency, that trade-off is significant.
Flexibility in Skill Sets (7:50 – 8:50)
Different stages of a data initiative require fundamentally different expertise. Building a data lakehouse demands different skills than maintaining reports or performing advanced analytics. An internal team of fixed headcount cannot easily flex between those requirements, which means either the team is mismatched to the current phase of the work or the company hires for the average need and is underserved at the extremes. A fractional model allows the right expertise to be applied to the right problem at the right time without requiring a hiring decision every time the work evolves.
Who It’s For
This episode is worth your time if you are a CEO, COO, or technology leader at a PE-backed mid-market company that has experienced the disruption of data team turnover and is evaluating whether a different staffing model makes more sense, a CFO building a business case for data investment who wants to understand the total cost of internal team ownership including the hidden costs of turnover and knowledge loss, an operating partner or portfolio company executive trying to build a more resilient data function without adding headcount that creates its own management overhead, or any organization that has found itself repeatedly starting over on data initiatives because the people who built them are no longer there.
Why It’s Worth a Listen
The turnover treadmill framing is one of the most accurate descriptions of a problem that mid-market companies experience consistently but rarely name explicitly. Treating each departure as an isolated hiring event obscures the pattern, and this episode makes the pattern visible in a way that changes how the problem is diagnosed and what solutions are worth considering.
The skill set flexibility point is particularly useful for organizations that are at a transition point in their data maturity. The expertise required to build a data foundation is genuinely different from the expertise required to maintain and extend it, and those differences are hard to accommodate within a small, static internal team. Understanding that mismatch helps organizations make more deliberate decisions about when to hire for a permanent capability and when to partner for a specific phase of the work.
And the continuity argument is worth taking seriously as a framing for why data work is different from other project-based investments. A data platform that is built and then left without ongoing attention degrades as the business changes around it. The organizations that get lasting value from their data investments are the ones that treat the ongoing iteration as part of the commitment, not an optional extension of it.
