Field story 5 min

# Reporting That Produces No Decision Is Overhead

A global IT organization had plenty of reports and little use for them. Instead of building better ones, it asked what decision each report was meant to support, then rebuilt its reporting around the forums where those decisions were actually made.

The condition

Reports are produced on schedule and in volume, and leaders still call extra meetings to find out what is actually happening before they decide anything.

## Plenty of data, decisions made elsewhere

The global IT organization was not short of information. Five separate reports were assembled by hand from three different tools. Status reports compared actual hours against forecasts, but blended rates hid the true cost of the work. Formal status updates were subjective and had to be compiled from several sources every cycle. By the time leaders read any of it, it was days old.

So leaders did what leaders do when the reports cannot be trusted. They filled the gaps with extra meetings and escalations. The reporting still happened on schedule. The meetings still happened. The decisions still got made. What had weakened was the connection between the information and the decisions. The data described activity. It did not help anyone decide what to do next.

During the diagnostic, the organization's own working team had named the condition in one blunt sentence about leadership deciding on whatever someone had pulled together the day before. Naming it was the easy part. The question was what to do about it without simply producing a sixth report.

## Five reports, one question each

Before designing anything, we catalogued every report being produced across the organization and evaluated each one against the same short set of questions. Who produced it? How often? From what source? And what decision was it designed to support?

Five reports came out of that exercise. A project status update, built every two weeks by project managers from three tools and emailed around as a spreadsheet. A portfolio tracker kept by the PMO, useful for oversight but with inconsistent financial fields and no connection to source data. A monthly executive deck, compiled by hand with heavy effort, that could not be drilled into during the very meetings it was built for. An interactive portfolio dashboard, a real step toward automation, that still depended on cumbersome extracts and duplicated data held elsewhere. And a biweekly extract of open work items, generated by hand, that repeated effort already spent on the tracker.

The finding that came out of the catalogue was more useful than any single report. The organization had high data awareness and low data utilization. It knew what was happening, but only through considerable manual effort, and never in real time. Every report had a producer and a schedule. The decision each one was meant to inform was much harder to point to, which is what low utilization looks like from the inside.

## Stop building reports

The recommendation was clear and a little uncomfortable. Stop building reports as separate artifacts. Build reporting as a connected layer on top of the operating model the organization was already putting in place: the two intake paths, the shared priority forum, the single structure in the delivery tool, and the governed release path.

That meant starting with data, not dashboards. A standard set of fields went onto every work item, regardless of team or type: the business unit, the application affected, whether it was a project, a product change, an enhancement, or work to keep the lights on, its urgency and impact, its value category and score, its relative size, its planned and forecast delivery dates, and where the request came from. None of these fields existed only for reporting. They were the same fields people used to take work in, rank it, and deliver it. Reporting became a byproduct of the operating model rather than a parallel effort imposed on top of it.

Simple flow measures replaced manual status updates: how much finished in a period, how much was in progress at once, how long work took from start to finish and from request to delivery, and how long it sat in each step.

## A dashboard for each decision

The dashboards came last, and each one was built for a specific forum and the decisions made there. The intake dashboard showed the volume, age, and movement of incoming requests, so members of the priority forum walked into each session already looking at the same queue. Nobody had to compile status beforehand. The forum's own dashboard tracked performance against delivery plans and kept a decision log: a running record of what had been accepted, deferred, or cut at each session, so the line between a decision and what happened next could be traced. The release dashboard tied planning decisions to what actually shipped, showing whether each commitment made in the forum had been met, and what the delivery data said about why.

That last point is where reporting stopped being overhead. A decision made in the forum showed up in the data, the data showed whether the decision held, and the next decision started from that evidence instead of from whatever had been assembled the day before.

## Reports that answer to a decision

In the pilot, three dashboards that update themselves, one each for intake, the priority forum, and releases, replaced the five reports built by hand. Leaders and teams began working from the same numbers with the same definitions, and managers could see priorities without opening a separate tool. Participants described more consistency in what got worked on and why, and decisions became something that could be explained after the fact because they had been written down when they were made.

The design had an honest limit, and it is worth naming. A dashboard tied to a forum is only as decisive as the forum. By the close of the pilot, the priority forum was running, but it was not yet the place where every priority call got made, and year-end pressure pushed it down the list. Where decisions still happened in side conversations, no amount of reporting could capture them.

That is the real test this organization learned to apply. Asking whether a report is accurate, timely, or well designed is not enough. Ask what will be decided differently depending on what it says, and who decides it, and in which room. If nobody can answer, the report is costing time and offering the feeling of insight without the substance. If someone can, build it there, from the data people already use to do the work.

A report earns its cost only when someone can name the decision it changes. Build backward from that decision and most of the reporting takes care of itself.

Know someone running into this? Send it to them.

[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=http%3A%2F%2Fagileon.test%3A64380%2Finsights%2Ffield-note-087-reporting-no-decision%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dfield-note-087-reporting-no-decision)

Email

### Share With Your Team

Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.

Your Message

Open in Email

Share

[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=http%3A%2F%2Fagileon.test%3A64380%2Finsights%2Ffield-note-087-reporting-no-decision%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dfield-note-087-reporting-no-decision)

Email

Components

[Signal](https://www.agileon.com/insights?component=Signal)[Rank](https://www.agileon.com/insights?component=Rank)

Seen in practice
[The work that fixes this Work Management Systems](https://www.agileon.com/professional-services/work-management-systems)

Keep reading
[Rank No Urgency, No Change](https://www.agileon.com/insights/no-urgency-no-change)[Surface The Next Reorg Will Be AI-Driven. Most Will Do It Wrong.](https://www.agileon.com/insights/the-next-reorg-will-be-ai-driven)[Surface From 83 Observations to Five Things to Build](https://www.agileon.com/insights/from-eighty-three-observations-to-five-things-to-build)[Flow Promising One Hundred. Finishing Fifty-Six.](https://www.agileon.com/insights/promising-one-hundred-finishing-fifty-six)
