Reporting Crisis

We have two reports.

The grand totals don't match.

So the business user complained.

So the Reporting Services team identified the records causing grief.

And sent the list to the business.

They forwarded the list to the programmers.

The programmers say its not an issue, the queries are wrong.


So much for group effort.

Okay, we'll take ownership of the problem.

The contractor and I did some root cause analysis on how this problem is occurring.

So we dissected the problem from a coding perspective.

And applied the logic to the business rules.

And there's a flaw in the business rules.

Which is not handled by the front end PHP application.

So we sent our analysis to the user to answer 'why' the numbers don't match.

And provided a few options on how, from a reporting perspective, we can overcome the issue.

And offered possible solutions to the Programming team.

We don't care one way or the other which number is correct, that's up to the business.

The business owns the reports, so we take their lead.

We can only point out the flaw in logic, recommend solutions and ways to plug the hole in the front end app.

That's all we can do.

People think reporting is simple, easy, anyone can do it.

There's really more to reporting than people understand.

We are part QA, part firemen, part psychologist, part mentor, part Project Manager, part negotiator, part a lot of things.

Almost like the glue that keeps everything running.

So this problem will get solved shortly.

And we'll go back to pumping out reports and making the customer's happy by providing value.

It's good to be counted on for having practical sound reasoning in times of crisis.

Reporting is more than putting numbers on a report.

We may not get recognition for what we do, but without us there would be a lot more chaos.