when to start implementing workflow ?

[Harmon Dan-rrfs20]

Fellow workflowers,
 
By popular demand here are the questions we ask to determine if we should do workflow or not.  Bear in mind we try to use these as guidelines, and sometimes they are not followed precisely.  Again, there was a presentation on this topic at ASUG, I suggest you look at it as well to obtain another perspective.
 
1.      Is the process a standard business process?
Yes - Proceed to the next question.
No - Stop, do not consider this process for R/3 workflow implementation.
2.      What are the results of the ROI analysis if the process were implemented using R/3 workflow?
Positive, there is a cost savings by implementing R/3 workflow - Proceed to the next question.
Negative, there is no cost savings by implementing R/3 workflow - Stop, do not consider this process for R/3 workflow implementation.
3.      What is the frequency of the process execution?
Less than 10 times per week - Stop, do not consider this process for R/3 workflow implementation.
Greater than 50 times per week - Stop, this process is a strong candidate for R/3 workflow implementation.
Greater than 10 times per week -  Proceed to the next question.
4.      Does the business process incorporate multiple organizations, departments, and/or users?
Yes - Stop, this process is a strong candidate for R/3 workflow implementation.
No -  Proceed to the next question.
5.      Does the business process require generation and retention of historical data for auditing, legal, or administrative requirements?
Yes - Stop, this process is a strong candidate for R/3 workflow implementation.
No -  Proceed to the next question.
6.      Can the business process requirements be satisfied using out of the box R/3 workflow functionality?
Yes - Stop, this process is a strong candidate for R/3 workflow implementation.
No -  Proceed to the next question.
7.      Can the business process requirements be satisfied using out of the box R/3 functionality such as transactions and reports, and not using workflow?
Yes - Stop, this process is a strong candidate for R/3 implementation without using workflow.
No -  Proceed to the next question.
8.      Is the business process mission critical for the success of the organization?
Yes - Stop, this process is a strong candidate for R/3 workflow implementation.
No -  Stop, do not consider this process for R/3 workflow implementation.
 
Regards,
Dan
> -----Original Message-----
>> From: Harmon Dan-rrfs20
> Sent: Friday, September 06, 2002 10:38 AM
> To: 'SAP Workflow Users' Group'
> Subject: RE: when to start implementing workflow ?
>
>
> Ronen,
>
> I am an R/3 workflow bigot, and we have already implemented,
> so perhaps my views are slightly jaded.  However, consider
> this analogy:  would you buy a new computer and only use it
> to play a card game?
> The real question is why will you NOT use workflow!
>
> Workflow is only as complex as the process it automates.  SAP
> provides hundreds of out of the box workflows and tasks.  Use
> them to prototype the process during blueprint.  In my
> opinion the biggest ROI is found when you use workflow to
> "re-engineer" the process.  If you are putting in a new
> system, use the new system features to improve the process!
>
> My biggest problem is dealing with a client that believes
> their existing process must be implemented "as is" in R/3.
> Always remember that a bad process will result in an equally
> bad workflow!  We have a series of questions that we try to
> answer to determine if a process should have a workflow.  Not
> every process requires a workflow!  I believe there was a
> presentation on this subject at the ASUG 2002 Spring conference.
>
> So use your blueprint to define and prototype the process,
> that can help determine if you need workflow or not.  I have
> witnessed too many missed opportunities for workflow when we
> say we will do it later and it never gets done.
>
> Regards,
> Dan
> |--------------------------------------------------------------------|
> | Dan Harmon                    |             Phone:    480-634-3090 |
> | R/3 Workflow Group Leader     |               Fax:    480-634-3761 |
> | Information Technology        |             Pager:    888-782-2030 |
> | Motorola SPS                  |            dan.harmon at motorola.com |
> |--------------------------------------------------------------------|
> | Bills travel through the mail at twice the speed of checks.        |
> |--------------------------------------------------------------------|
>
> > -----Original Message-----
> > From: Ronen Fox [mailto:Ronen.Fox at ness.com]
> > Sent: Sunday, September 01, 2002 10:23 PM
> > To: SAP-WUG at MITVMA.MIT.EDU
> > Subject: when to start implementing workflow ?
> >
> >
> > Dear workflow experts,
> >
> > One of our clients, a very large manufacturing enterprise, is
> > beginning to
> > prepare the implementation of mysap.com.
> > It would be a large project, and they are also interested
> in workflow,
> > although they have a fear that workflow is complex to implement.
> >
> > The question I would like to ask this group on their behalf is what
> > recommendations you may have as to the phase of the ERP project that
> > workflow should be introduced ? right from the beginning of
> > the conceptual
> > design ? after going live and letting the processes become
> > more mature ?
> > I guess there is more that one answer, and I would really
> > appreciate getting
> > various answers to this question that represent different
> > methodologies.
> >
> > Thank you all in advance for your kind help.
> > Best regards,
> > Ronen Fox
> > Workflow product manager
> > Ness Technologies
> >
>