I ask you, how can you know where you are going if you don’t know where you have been?  Do you know who is doing what and what role that is in the organization no matter who sits in the role?  Do you know where your manual processes are and how you might achieve efficiencies with system support?  Do you know what rules are necessary to ensure when you follow the process that you are in compliance?  Are you aware of the boundaries and how the HR process may be impacted by the Recruitment process, or how the supply chain process may be impacted by procurement. 

It is always amazing that there is someone who indicates process is not important, or we don’t need to do that until we get into designing the system and writing the specs.  Process Analysis needs to happen up front to determine where the opportunities are for change, how change will be instantiated and communicated, what training will need to take place, does the system support the process or not?  Are there other systems that are integral to the process?

Here are some questions to ask yourself and ensure you have the answers and your processes analyzed to provide a framework and foundation for everything else in your implementation.  The foundation will be there for testing, training, security, roles, compliance and ultimately change and communication. 

Questions;

What is the purpose of the process, outcome and result?

What are the Roles and how will they change?

What are the steps?

What are the business Objects?

What are the rules?

What is manual and where does the system support the process?

What training and testing will be necessary to ensure the process is working as planned?

What are the boundaries between processes and what is the impact on pre and post process?

How will all the changes be communicated and managed?

So if you think process is not important, look to those implementations where you have been involved and determine points of failure.  And on those that were supported by Business Process or Use Case Analysis how they had an impact on success. 

I remain amazed that there are still consultants and professionals who do not understand the value of understanding and anlyzing process at the beginning of an implementation…not in design, not in construct, not in transition, not in deploy but in the beginning to provide a foundation for all stages, phases and tasks involved in an implementation.

Consultant “Do you have your processes documented?” Client: “Of course, let me show you the ringbinder where we keep them. I had to use them the last time we did an upgrade and they are somewhere here. Oh yes, here it is the red ringbinder in the back of the overhead on my cubicle. What? Do the executives review them…you have got to be kidding.”

Consultant: “Can you show me how they cross all the organizational boundaries? Where they start and where they end? What are the results and who is the owner of the process? Who is getting value at the end of the day?” Client: “Huh?, I just keep the binder of the visio documents, I don’t know who uses the process documentation.” And so on, and so on.

Process is not something to keep in a binder on the shelf, but something to review on an iterative basis. Do your processes remain static? Are the roles always the same, do they change? If so, how and who integrates the change into the organization to ensure it is accepted? It is important to identify the stakeholders, the change agents, the processes that change and how they change. Is the change a result of a policy change, a change in the system, a role enhancement, a performance concern either system performance or performance of an associate? There is an impact to the organization which will effect systems, people, process, procedure outcomes or results that must be addressed.

Who owns the process? The process owner is the person who gets value at the end of the day. What does that mean? It means the highest level ownership in the organization, the role that ensures that part of the organization is achieving the results expected and the results that support the organizational vision and direction. I wonder how many associates can explain how what they do will impact the direction and strategy of the organization..in fact, how many can articulate the vision or strategy of the organization?

Process is the absolute foundation of the organization and determines where any implementation or upgrade will go and whether or not it will be successful. It is the foundation for system, customizations, training, testing, and ongoing support of the organization so again I ask…where are your processes? In a binder on the shelf, or in the forefront of organizational and strategic discussions?

It seems Business Process templates are used on every project with varying degrees of success.I have used Rational, Visio, PDF’s, and templates that have been developed to encompass a modified Rational approach.

The current project is reviewing all the delivered processes and using them as a basis for the development of the “to be” processes for the implementation. New projects always result in a search of the “PeopleSoft” now Oracle website to find the delivered processes and each time it is a matter of wading and searching to find them.

Daniel, who is one of our business analysts on the project found this link which has provided an excellent resource for our process development work.

http://download.oracle.com/docs/cd/E17355_01/hf91bpm0/index.html

Oracle also has a PDF of the 9.1 processes. Let us know where you are in your business process work and how you developed your “to be” processes for your implementation.