DataData Culture

Data literacy programs that actually change behavior

Most data literacy programs teach tools and terminology, then declare victory. The ones that move the needle on board-level ROI do something different: they change how people make decisions, not just what they know.

🎙️

Listen to the podcast

4 min

The concept at stake here is behavioral transfer: the degree to which learning acquired in a training program actually changes how someone behaves in their job. In data literacy, this is the gap that explains why organizations spend six or seven figures on training curricula and still find their managers making gut-call decisions, their analysts producing reports nobody reads, and their data teams frustrated that "nobody uses the data." The program ran. The behavior did not change. The board asks why the investment is not showing up in outcomes, and nobody has a clean answer.

This distinction, between knowledge transfer and behavioral transfer, is where most corporate data literacy efforts quietly fail.

Why it matters for CDOs specifically

A CDO making the case for data investment to a board or CFO needs to show return. That return can take several forms: faster decisions, fewer errors in pricing or inventory, better customer segmentation, reduced regulatory risk. All of these are behavioral outcomes. They require people to act differently, not just to score higher on a post-training quiz.

The problem is that most data literacy programs are designed around content delivery. They cover SQL basics, dashboard interpretation, statistical thinking, maybe some AI concepts. Completion rates look good on a slide. But if the regional sales director still ignores the demand forecast in the weekly review meeting, the investment has produced knowledge, not change.

For CDOs, this matters because the board measures you on outcomes. A 40% training completion rate across 3,000 employees is a process metric. A documented reduction in forecast error after a targeted literacy intervention in the commercial team is a business metric. The second one survives a budget conversation. The first does not.

How behavioral transfer actually works

The psychology here is not complicated, but it is consistently ignored in corporate programs. Behavioral transfer requires three conditions: the learner must be able to do the new behavior, they must be motivated to do it in context, and the environment must make doing it easier than not doing it.

Most programs address only the first condition. They build capability and stop. The result is what learning scientists call the "knowing-doing gap," a concept documented at length by Jeffrey Pfeffer and Robert Sutton in their Stanford research from the early 2000s, still accurate in 2026.

Here is a concrete example. Booking Holdings ran a well-documented internal experiment several years ago in which teams were given access to A/B testing tools but not structured support for interpreting results. Tool adoption was high. Decision quality changed minimally. When they restructured the program to include peer review rituals where teams had to present test results and justify decisions based on data, behavior shifted. The social accountability element changed the environment, not just the capability.

The mechanics of programs that do produce behavioral transfer share four characteristics:

  • Learning is attached to real decisions the person actually makes. Not hypothetical case studies, but the pricing review they will attend next Tuesday.
  • There is a rehearsal loop. The learner practices the behavior, gets feedback, and repeats it in context, not just in the training room.
  • Managers are explicitly enrolled. If a participant's direct manager does not ask data-informed questions in their next one-on-one, the training signal fades within weeks. Research from McKinsey's learning and development practice (acknowledging McKinsey is a consulting firm with commercial interests in this space) consistently points to manager reinforcement as the single highest-leverage variable in transfer.
  • Progress is measured at the behavioral level, not the knowledge level. This means observing decision processes, not administering tests.

A practical design implication: a 90-minute e-learning module on "understanding dashboards" produces negligible behavioral transfer. A four-week sprint where a marketing team uses actual performance data to revise their channel allocation, presents findings to leadership, and defends their interpretation under questioning produces measurable change. The second is harder to scale. It is also the one that generates ROI you can report to the board.

When to use this approach, and when not to

Designing for behavioral transfer requires significantly more investment, per person, than conventional content-based programs. It demands real business problems, which means business unit cooperation. It requires manager involvement, which means the CDO must have organizational relationships outside the data function. It involves smaller cohorts, which limits scale in the short term.

This approach is the right call when the target behavior is specific, consequential, and observable. Sales teams using customer lifetime value in deal prioritization. Finance teams adjusting forecasts based on leading indicators rather than last month's actuals. Operations teams catching anomalies in production data before they become incidents. All of these are behaviors with clear dollar values attached.

The approach is poorly matched to broad, mandatory "data culture" programs aimed at thousands of employees with no specific decision context. Those programs have a different purpose: building a common vocabulary, reducing anxiety about data, signaling organizational values. They serve a function, but do not confuse them with ROI-generating interventions. When a CDO presents them to the board as proof of data ROI, the argument eventually collapses under scrutiny.

The honest position is to run both types and be precise about what each one is for. Mass awareness programs build the floor. Targeted behavioral interventions build the outcomes you can measure. Only the second one pays back in the terms a board cares about.

If you are reporting data literacy results to your board this year, the diagnostic question is simple: can you point to a decision that changed because of the program? If the answer is no, you have a training program. If yes, you have an ROI story. Build the next intervention around decisions, not topics, and the numbers will follow.

Go deeper

The lessons that take this article further, free to read.

  1. 1Building a data literacy programData culture & organization
  2. 2Decision rituals: getting data into the roomData culture & organization
  3. 3Calculating the ROI of data initiativesData strategy & the CDO role
  4. 4Communicating with the board and c-suiteCDO leadership & executive presence
  5. 5Driving cultural change to data-drivenData culture & organization

Finished reading?

Validate your read to earn XP and feed your radar.