Field story 4 min

# What Existing Findings Reveal

Before observing anything new, a diagnostic team read what a large IT organization already knew about itself. Two consulting reports written years apart named the same problems, and neither had been acted on.

The condition

The organization had commissioned studies of itself for years, and the recommendations sat in folders almost nobody opened.

## Years of folders, and a grimace

Leaders usually expect a diagnostic to open with new research: interviews, surveys, someone sitting in on meetings. At one large IT organization serving several business units, the first move was older and less glamorous. We asked the sponsor's working team for what the organization already knew about itself: engagement surveys, post-mortems, retrospectives, exit interview summaries, and the consulting reports sitting in folders somewhere.

One member of the team made a face. There were a lot of those folders, and some of what was in them was decades old. The concern was fair. Findings go stale because organizations change underneath them. Headcount shifts, leaders turn over, the tool stack evolves, products are acquired or retired. So we set the terms before anyone opened a folder. Pre-existing findings are a starting point, not current truth. They show what the organization has tried, what it has noticed about itself, and where it has chosen not to act on what it noticed.

## The reports nobody implemented

Then someone asked the question we had been hoping for. The organization had commissioned several consulting reports over the years, and none of the recommendations had ever been implemented. What use were they now?

They turned out to be among the most useful documents in the building. A recommendation that never gets implemented says something about the culture that received it. The ideas that stall are often the ones that touch the parts of the system nobody wants to look at, which usually means they were closer to the real dysfunction than anyone wanted to admit at the time. The sponsor had read the reports. As far as she knew, nobody beyond two or three people had opened them in years. That is normal. Organizations bury what they did not act on.

The team listed what they could find: the two most recent engagement survey cycles, post-mortems from the largest recent product releases, the exit interview summaries HR compiled every quarter, retrospectives from the delivery teams that ran them, the consulting reports that could still be located, and internal papers written when the latest framework was rolled out. We added board materials and quarterly business reviews, vendor evaluations and tool selection memos, and recent organizational change announcements. We also asked for whatever lived outside the official document system, in shared drives, personal folders, and email attachments. The most honest internal data rarely sits in the official place.

## Four patterns that had been visible for years

We read most of it ourselves over the following week. The working team was already stretched, and reading at that volume is work an outside team can do quickly because it knows what to look for. Four patterns surfaced.

First, the organization had been studying itself without acting on what it learned. The two consulting reports the team could locate, written years apart, named the same issues: tool sprawl, unclear prioritization across business units, friction between IT and the business, and capacity nobody could see. When a second study finds what the first one found, the problem is structural, not situational. Fixes aimed at symptoms had not touched the conditions producing them.

Second, the engagement surveys had been drifting the wrong way without anyone noticing. Aggregate scores looked stable, which is probably why no one escalated them. The open-text responses had grown more specific and more pointed about the same handful of issues. People knew exactly what was wrong. The results had not been read with enough care to hear it.

Third, each of the major release post-mortems described the same failure. Cross-team dependencies surfaced late, and one team blocked another in the final weeks before launch. Each post-mortem named the same root cause and proposed the same fix, better dependency identification during scoping. The fix never carried into the next release. Fourth, the most common reason people gave for leaving was the volume and unpredictability of the work. HR compiled those summaries every quarter and reported them upward, where they were received and filed without anyone connecting them to the conditions producing them.

## Paying twice for the same answer

When we walked the working team through the comparison of the two consulting reports, the sponsor was quiet for a long moment. Then she named what the folders added up to. The organization had paid for the same analysis twice and acted on neither.

That is the most common version of this finding, and it is not a failure of the analysis. It is the organization failing to act on what it already knows, which is itself a system problem. The evidence existed in four places, and none of those places had a route to a decision. Reports went up, were received, and were filed. The post-mortem fix had no path into how the next release was scoped. The exit interview data never reached the people who could change the conditions it described.

The sponsor wrote a short instruction on the whiteboard beneath the four patterns: act on it this time. The patterns stayed on that board as the opening evidence for the rest of the diagnostic.

## From history to a live picture

The findings did not replace the diagnostic. They aimed it. The old material told the team where the organization had been and confirmed that its problems had structural roots, visible for years to anyone who knew where to look. It could not say what was happening inside the system now.

So the next step drew directly from that history. The team would sit in on twenty to thirty meetings over the following weeks, starting with the meetings where the late dependencies named in every post-mortem should have surfaced and had not. A pattern the organization had documented and re-documented became the first place to watch the system in real time.

Reading the existing evidence first does not just save research. It changes what the research is for. The team began its live observation already knowing which problems had outlasted every prior fix, instead of spending its first weeks rediscovering what insiders had known for years.

An unimplemented recommendation is not old news. It marks the part of the system nobody has been willing to touch.

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%2Fwhat-existing-findings-reveal%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dwhat-existing-findings-reveal)

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%2Fwhat-existing-findings-reveal%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dwhat-existing-findings-reveal)

Email

Components

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

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

Keep reading
[Flow The Engine Nobody Builds](https://www.agileon.com/insights/the-engine-nobody-builds)[Flow We Stopped Making Documents and Started Building Machines](https://www.agileon.com/insights/documents-versus-machines)[Surface The Seven Components of Work](https://www.agileon.com/insights/the-seven-components-of-work)[Surface From 83 Observations to Five Things to Build](https://www.agileon.com/insights/from-eighty-three-observations-to-five-things-to-build)
