It is a best practice to identify these business questions before spending a lot of time tagging your analytics implementation. This ensures that all implementation development work is focused on what is most important to the business. Business requirements shouldn’t be too high level, nor too granular. Each business requirement should be able to be answered through a report after implementation is completed.
Analytics teams should work with internal stakeholders to review as many business requirements as possible to make sure that different options are considered. In many cases, analytics implementations don’t deliver the expected value simply because they aim too low when it comes to identifying business requirements. We recommend casting a wide net and then using prioritization to determine if and when each business requirement is implemented.