Databases Reference
In-Depth Information
takes additional discussion to clarify. In many instances, decisions may have
been made in a timelier manner, which may be difficult to quantify. The
most exciting part is adding all of these individual results together. There is
often a much bigger impact overall than expected. These composite results
need to be shared with upper management and across the business and IT
communities.
Adjusting Expectations to Reality
The previous section focused on identifying and quantifying results. Even
when concrete results can be measured, it is possible for the data warehouse to
fall short of expectations. How do you know what people's expectations are?
When a data warehouse project is under way, the official expectations should
be documented in the project charter and/or scope. However, individuals
may have their own expectations, which may or may not align with the
official version. Individual expectations are often shared during the process
of gathering requirements. Once the data warehouse goes into production, it
is still important to keep in touch with expectations of the user community.
Periodically, go out into the user community and listen to their concerns. This
can easily be done when gathering requirements and enhancement requests
for the enhancement planning process.
Sometimes individuals or groups seem to always have crazy ideas. Don't just
write off their input. These are often the people who can push the organization
forward into new and better ways of running the business. In other cases,
individuals bring a wealth of previous experience to the organization. This
can include ideas that no one has even dreamed of, let alone knew were
possible.
Naturally, serious problems can arise if what is delivered and supported falls
short of expectations, regardless of how unrealistic those expectations may be.
After exploring expectations across the organization, it is important to follow
up with a good dose of reality. Communicate the data warehouse priorities
back to these groups. If their needs and expectations will not be met, let them
know now. While this may not be an easy meeting, it is much better than
waiting and allowing their hopes to grow. When possible, these discussions
should be led by the business decision makers. Share the business rationale
for the priorities that have been set. If an individual or group continues to
have concerns, they should work directly with their management and the data
warehouse steering committee.
NOTE
As noted elsewhere in this topic, communication is critical to data
warehouse success. Too often, communication is viewed as telling others about
what is happening. Keep in mind that good communication involves listening too.
