Photo Credit: PauliePaul on Flickr

• There are no off-the-shelf plug and play solutions that can fully address the needs of all end user(s).
• There are no “one-size-fits-all” solutions!
• The process of bringing all affected interests together to collaborate toward a shared goal seems impossible.

These are all challenges on any data warehouse development project or for that matter on any project I have been involved with. After close to 12 years helping organizations’ of all shapes and sizes develop and implement a data warehouse, I have found one issue or flaw that keeps the project from getting full organizational buy-in: inadequate end user(s) or functional user(s) input during the planning and development stages of the project.  We always wait until the last phase of the project “reporting” to allow them to tell us what the reports should look like and what data they currently have.  Why not ask them “what data do you need, but don’t have?” or “how can we make your job easier through data and reporting?” My thought is simple we should take a “bottoms-up” rather than a “tops-down” approach for Data Warehouse development and implementation. 

One of the best resources for insuring the success of any project is the people using what you are building. So why wait until the end – let’s have them drive the project. When we get to the implementation stage, we will have users banging on the door to get in versus us forcing it done their throats. There’s probably a group of people already in your organization who will volunteer to help design the system and evaluate it. Think of these people as Power User(s).

Finding the best power user(s) requires a little effort. The following list should help you identify, inspire, and make best use of the Power User(s) in your organization:

1. Why do I need Power User(s)?

Power User(s) work side-by-side with regular users – the same people you’re trying to reach with your data warehouse project. If your Power User(s) are excited about the data warehouse, you can be sure they’ll let their colleagues know and that excitement can be contagious. Power User(s) are also vital to testing. They can help you identify potential problems and areas of improvement you may not have found on your own.

2. How do you identify these Power User(s)?

You will need the managers of the functional area in the organization to suggest candidates. Do not, however, let managers pick the Power User(s) for you. Their idea of what may make a good Power User may not match yours or the projects.

3. Qualities of a good Power User

• Likes to try new things and able to provide honest, useful feedback
• Excited about volunteering time to make the project a success, and has the time and support of their management team to add this to their schedule
• Able to get up in front of their peers and tell them that data warehouse will make their lives easier
• Very organized, not only in their own jobs, but also as they work with others
• Clear communication

Power User(s) should represent a good cross section of the organizations workforce. I suggest avoiding employees that have been at the organization less than a year, while they can offer you outside experience, they could slow down your efforts by providing too much basic information about the organization.

Power User(s) do not need to have advanced computer skills already. In fact, having advanced computer skills may be a disadvantage. Advanced users may not help you identify problems less experienced users would see.  Technical skills can be taught; the ability to speak for and to others cannot.

4. Management on Power User(s)?

Even if you don’t use managers as a Power User, try to keep them involved in the process. The more involved they are, the more excited they will be about the deployment, and the more they will work to make sure it’s a success. Ask them to nominate Power User(s) and to check in regularly with the users. This helps managers see the success of the project. It will also help motivate the Power User(s), since they will see their boss is invested in the project.

5. How many do I need?

Ideally, you want one at least Power User per functional area. Of course, the number of users needed varies by organization. In a very large organization, you may want a couple of Power Users per functional area.

Comments