In my January column, I wrote about the overall life cycle of a business performance management (BPM) project. Now it's time to drill into the first phase where you evaluate the need for BPM, define the goals and ultimately specify the requirements necessary to generate a request for proposal (RFP). Within this kickoff phase, there's a logical sequence of steps that is a prerequisite for success. The company needs to set strategic goals for the project and decide what it is willing to spend to reach them. Then, the stakeholders are interviewed to determine what BPM metrics are needed to support the overall goals and in what form those measurements should be delivered.

Next, take a careful look at what systems are already in place and which of your chosen BPM measures and processes those systems can reasonably support. The gaps - what your company needs but current systems are incapable of providing ­- will in large part define the new BPM functionality you need to acquire. Along the way, the senior team must prioritize which processes and departments to include in the scope of the BPM project. Almost certainly, they will look at whether the business processes involved are already optimal; some best practice analysis may be needed before you automate those processes.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access