Most teams don’t ignore data because they’re lazy or indifferent. They ignore it because that’s how the system was built. Data comes in at the end of a cycle, leadership reviews it, and the conversation is about what happened. By the time anyone is looking at the numbers, the work that produced them is already done.

Pete Caputa, CEO of Databox, describes this as the report card problem. In school, you got your grades at the end of the semester. Some students used that information to feel good about what they’d done. Others used it to feel bad. Almost nobody used it to change how they studied, because by the time the report card arrived, the semester was over.

Most companies operate the same way.

Where the Habit Comes From

The report card cycle isn’t accidental. It developed because data used to be genuinely hard to access. Getting a report meant asking someone to pull it, which took time, which meant it only happened when it really had to — at the end of a quarter, before a board meeting, when something went obviously wrong.

The technology has changed. Most companies today have dashboards that update in real time, CRMs that track activity as it happens, and analytics tools that can surface trends before they become problems. But the behavior hasn’t caught up. Teams still wait for the scheduled review. Leaders still treat the monthly report as the primary signal. The habit of checking data only when required is deeply embedded, even when the friction that created it no longer exists.

The second driver is cultural. When leaders don’t share performance data openly with their teams, those teams don’t develop a relationship with the numbers. They do their jobs, they execute their tasks, and they find out how things went when someone tells them. You can’t build a data-driven culture on top of that structure. People can’t use data to make better decisions if they never see the data.

What Changes When Teams Look at Data in Motion

The difference between a team that reviews data after the fact and a team that uses data while work is in progress isn’t just speed. It’s the nature of the conversation.

After-the-fact review produces explanation. Here’s what happened, here’s why, here’s who’s responsible. It tends to be backward-looking and, in a lot of organizations, carries some amount of defensiveness.

In-motion data use produces adjustment. Here’s what we’re seeing, here’s what it might mean, here’s what we could try. It’s forward-looking by definition, because there’s still time to change something.

When a marketing team can see mid-campaign that one audience segment is engaging at twice the rate of another, they can shift budget before the campaign ends. When a sales manager can see on Wednesday that call volume is down across the team, they can address it before Friday. When an ops leader can see that a new process is producing slower cycle times than expected, they can diagnose it before it affects the quarter.

None of that is possible if the first time anyone looks at the data is after everything is already done.

The Two Cultural Blockers

Caputa identifies two specific cultural problems that keep companies in the report card cycle, and they operate at different levels of the org.

At the individual level, some people resist data because it introduces accountability they’d rather not have. If the numbers are visible, performance is visible. If performance is visible, underperformance is visible. For people who’ve built their sense of mastery around knowing how to do a specific job a specific way, real-time data can feel threatening rather than useful.

At the leadership level, the blocker is usually about control. Some leaders keep data close because sharing it feels like giving up authority. If the team can see the numbers, they might start asking questions, drawing their own conclusions, or pushing back on decisions. That can feel uncomfortable, especially for leaders who are used to being the primary interpreter of how the business is doing.

Both of these are real and understandable. But both of them are also expensive. A team that can’t see its own performance data can’t self-correct. And a leadership team that hoards information ends up becoming the bottleneck for every analysis and every decision.

Making the Shift

The shift from report card to real-time doesn’t require a new tech stack. It requires two things: access and expectation.

Access means making performance data visible to the people doing the work. Not just to their managers, and not just in aggregate. The people running campaigns should be able to see how their campaigns are performing. The people making calls should be able to see their own activity metrics. The people managing projects should be able to see whether the early indicators are trending in the right direction.

Expectation means building a rhythm where looking at data is a normal part of the work, not something that only happens at review time. That might be a weekly team check-in where everyone looks at the same dashboard. It might be a standing question at the start of every project meeting: what are the numbers telling us right now? It doesn’t have to be elaborate. It just has to be consistent.

When both of those things are in place, data stops being a report card and starts being a tool. The team’s relationship with the numbers changes. Decisions get made with better information. And problems tend to surface earlier, when there’s still something to be done about them.

Listen to the full podcast episode here.

Related Resources

• Why Growing Companies Are Drowning in Data (And What to Do About It)
• Inputs, Outputs, Outcomes: The Framework That Connects Your Team’s Work to Your Results
• Looking Out the Windshield: Why Forward-Looking Metrics Matter More Than Scorecards
• Cross-Functional Data Sharing: Why Breaking Down Silos Is a Growth Strategy