HELP! Why are reporting requirements so difficult. The user seems to need to see the report before they can tell me what they need. Does anyone have any comments, suggestions to make this process easier.
I developed a simple-to-describe three step process to define high level reporting requirements while avoiding mock-up madness. It takes some experience and maturity (as a BA or in the organization or both), but it's very effective. I know this technique is being used by some of my former colleagues with very beneficial impacts, and I use it all the time. It's become second nature - in fact, now that I think of it, I used it earlier this evening. It's not widespread yet, but with some CRM it works wonders.
At a high level you're going to ignore most data elements and all presentation and formatting. Instead you're going to focus on the decision or action that the report supports and the people or groups who take that action. After you've worked out the Decision-Actor pairs, figure out the information that each pair needs to do a good job.
Decision: What needs to happen based on the report?" To be informed" is never a valid answer. Something tangible or practical happens because of the report, or you don't need it.
Actor: Who is going to make that decision or take that action? Often an actor will be a stakeholder in the project and say 'I need this information in this format!' Your job is to focus them on the decision, and then ask who else might make similar or related decisions. You can find other pairings by looking at the processes that are triggered by the report, or the processes for which the report is an outcome.
Information: After - and ONLY after - you have determined the pairings above, figure out the categories of information that the actors need to take action. It's fine to re-examine your actors and decisions once you've found the information; you may discover that there are synergies or reuse scenarios for a report that can save millions (not an exaggeration, unfortunately).
Keep'em at a high level with an action focus
I developed a simple-to-describe three step process to define high level reporting requirements while avoiding mock-up madness. It takes some experience and maturity (as a BA or in the organization or both), but it's very effective. I know this technique is being used by some of my former colleagues with very beneficial impacts, and I use it all the time. It's become second nature - in fact, now that I think of it, I used it earlier this evening. It's not widespread yet, but with some CRM it works wonders.
At a high level you're going to ignore most data elements and all presentation and formatting. Instead you're going to focus on the decision or action that the report supports and the people or groups who take that action. After you've worked out the Decision-Actor pairs, figure out the information that each pair needs to do a good job.
Good luck!
J