Have a look at almost any programme team's shared drive and you'll find years of it: attendance registers, intake forms, case notes, post-session surveys or a dropdown field someone added years ago that nobody has touched since. The information is there, dutifully filled in, carefully filed and rarely opened again.

This isn't a collection problem. Teams collect data because funders ask for it or because someone might need it later and because more data has always felt safer than less. The result is often folders full of information that nobody is quite sure what to do with and a quiet sense, in every team, that all this effort should be adding up to more than it is.

The real gap isn't the data. It's the question. Most monitoring systems were built to answer "what happened" such as attendance, outputs, completions, etc. Very few were built to answer "what should we do differently because of it." Those are not the same question and only one of them actually changes anything.

"What happened" produces a report. "What should change" produces a decision.

Getting to the second question rarely means collecting more. It usually means going back to a team and asking for less. Which three indicators, out of everything currently tracked, would actually change what happens next quarter? That's a harder conversation than building a new dashboard. It's also the only one worth having.

You don't need more data. You need one honest meeting about what the data you already have is for.