Read part 1 of this tip.
Eliminating the unbounded nature of "ad hoc" reporting entails:
- Sitting with the user to discuss the exact data elements, analysis processes, and reporting methods that are expected.
- Amending your project order to define "ad hoc" in the precise terms of the client requirements. List each feature, capability, presentation method, and results that are needed.
- Turning the "ad hoc" expectations into "designed" features of the project plan. This might require additional tool evaluations, tool purchases, or even additional data marts.
Your attention to detail and support for the complete business requirement might generate unexpected project expenses for software tools, design and construction effort, or even hardware to support the additional storage and processing. This revelation should cause some management scrutiny and raise questions of business value vs. expenditure. All of the resulting dialogue benefits the client in understanding the current state of technology tools. Most of all, you will have eliminated any surprises from ad hoc users whose needs might have otherwise been unsupported.
For more information, check out SearchCRM.com's Best Web Links on Business Intelligence
Requires Free Membership to View
When you register, you'll begin receiving targeted emails from my team of award-winning editorial writers on the latest customer relationship management (CRM)and call center technology issues today. Our goal is to keep you informed on the hottest issues facing this fast-changing industry.
Hannah Smalltree, Editorial Director
This was first published in September 2002
Join the conversationComment
Share
Comments
Results
Contribute to the conversation