Q
Problem solve Get help with specific problems with your technologies, process and projects.

More thoughts on why everybody isn't using Workflow

I read your response to the question about why isn't everyone using workflow. I agree with some of your answer regarding a general lack of knowledge regarding Workflow. However, your statements about Consultants implies that they tend to misinform their clients. I do not think this is the case.

I read your response to the question about why isn't everyone using workflow. I agree with some of your answer...

regarding a general lack of knowledge regarding Workflow. However, your statements about Consultants implies that they tend to misinform their clients. I do not think this is the case. Being a former SAP consultant, My pat answer regarding workflow during the initial implementation is that it should be considered a post-go-live initiative. There are several reasons for this and the major reasons are as follows: Workflow is inevitably out of scope for the initial implementation. This is because clients want to get the basic SAP functionality up an running as quickly as possible. I think there is well informed opinion regarding the cost of implementing SAP and how it can spiral unless scope is well established. Again, because of the complexities of SAP implementations, and the complexities of Workflow, I think this is the appropriate strategy. I think most Consultants correctly advise the client to consider what is already on their plate with respect to implementing basic functionality, and then consider the additional level of effort required to effectively implement workflow at the same time. If Workflow is out of scope initially, in most cases it is difficult to convince the client to accept the additional cost and the likely delay in the initial go-live date in order to implement workflow simultaneously. Again, I think the proper strategy is to inform the client what workflow can do to improve SAP's efficiency and the improved ROI that goes with it, at the same time advise them that it can be done after the initial implementation unless the client is willing to accept the additional cost and potential delay in the go-live date. In most cases the correct strategy is to implement workflow after the fact, as a follow on initiative. These are my thoughts.


You raise some good points and hence I have posted your reply to a previous answer I provided to the question Why isn't everybody using Workflow?


This was last published in December 2001

Dig Deeper on SAP workflow development

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close