Ohio University wanted to get started with analytics (business intelligence) but didn't have much money. This Campus Technology magazine case study explains how they did it and what they learned:

Also working to give input and feedback to Wykoff's team was a committee of various users. That committee, which has met weekly for a year and continues to meet and give input, includes representatives from budgeting, finance, the registrar, the bursar, and other academic personnel. As the group gains an understanding of just what BI solutions can do, Wykoff said, excitement is building. "There's starting to be a little line [of people] saying, "How can we get on the BI list and be next?'"

One lesson Wykoff offered as the project moves into its second year is this: Delivering the right data to end users through BI is an iterative process. "Once [users] see the data, they're going to ask a different set of questions [than the first time around], or realize some assumptions," she noted. That makes BI different from a more traditional software development project, in which user needs are researched, then a system is installed, modified, and left to run.