iSixSigma

Process mapping detail

Six Sigma – iSixSigma Forums Old Forums General Process mapping detail

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #31519

    Perryman
    Participant

    Hello all,
    I am working on developing a reference tool to help BB and GB with mapping processes.  One of the recurring problems encountered is the inconsistent level of detail from one map to another and even within maps.  For example, in one task level map we’ll have : REVIEW THE CONTRACT, ADD COMMENTS, OBTAIN APPROVAL, SUBMIT FOR TYPING.  While in another we’ll have : REVIEW THE DOCUMENT, ADD COMMENTS,  OBTAIN APPROVAL, INITIAL COVER SHEET, MAKE 2 COPIES, SUBMIT ONE COPY FOR TYPING, FILE OTHER COPY….We intend to provide guidelines to help determine process tiers but I am wondering just how much detail should be included in a task level (lowest level) map.  I am aiming for mapping consistency and also would like to have the real detailed stuff documented as supporting instructions.  Does anyone have an easy definition of what constitutes a task that we could use? Or suggestions/lessons learned…….
    Thanks,
    Patch

    0
    #88517

    Perryman
    Participant

    I didn’t get any replies to my post in February so I thought I’d give it another try………….
    Hello all,
    I am working on developing a reference tool to help BB and GB with mapping processes.  One of the recurring problems encountered is the inconsistent level of detail from one map to another and even within maps.  For example, in one task level map we’ll have : REVIEW THE CONTRACT, ADD COMMENTS, OBTAIN APPROVAL, SUBMIT FOR TYPING.  While in another we’ll have : REVIEW THE DOCUMENT, ADD COMMENTS,  OBTAIN APPROVAL, INITIAL COVER SHEET, MAKE 2 COPIES, SUBMIT ONE COPY FOR TYPING, FILE OTHER COPY….We intend to provide guidelines to help determine process tiers but I am wondering just how much detail should be included in a task level (lowest level) map.  I am aiming for mapping consistency and also would like to have the real detailed stuff documented as supporting instructions.  Does anyone have an easy definition of what constitutes a task that we could use? Or suggestions/lessons learned…….
     

    0
    #88535

    billybob
    Participant

    Hello folks,
    There is so many different ways to process map.  Are you only concerned with value added operations, or each time material moves into machines or stock areas.  Do you care to know the takt time at each step for a production lot for production runs?  For an office process I’m sure the steps are different, but there are still process steps that need to be accomplished to complete a task which the map must describe.
    Maybe the people creating and using the maps need to sit together and standarize the process as to what is critical to quality of the map and the information it provides.  Lets face it, if the process map isn’t usefull to the people using it; trash it.
     
    Just my 2 pounds of possum poop!
    Later,
    Billybob 

    0
    #88536

    Perryman
    Participant

    Billybob,
    I agree that the process map must be useful.  In fact we intend to baseline all our processes for several reasons:

    So we understand what it is we are actually doing
    So others could understand what we are doing (especially new employees)
    So we could measure and then identify improvement opportunities
    So in answer to your question, no we are not only concerned with VA activites.  We want an accurate picture of the AS IS in sufficient detail to permit someone to read it and do the job.  What I’m trying to get is some advice on other similar experiences in deciding what level of detail should appear on the map or in an accompanying instruction, for example.
    Thanks for the CTQ idea, though…
    Patch

    0
    #88539

    billybob
    Participant

    Hello folks..you too Patch,
    Thats the question only you folks can answer…whats important in your process that you need to see on your map.  Sit together, brain storm, make a map. When you’re done have “fresh eyes” look it over for clarity and details you might have missed or things you could omit.  You’ll find a way….
    And by “fresh eyes” i don’t mean me looking into the girls locker room either.
    Later, Billybob

    0
    #88544

    Adam Bowden
    Participant

    Best explanation of “fresh eyes” I’ve seen in a long time !!
    Adam
     

    0
    #88546

    Edwards
    Participant

    This is the definition I use. 
    Definition of a task/activity:
    An activity requires an input, which only arrives at the beginning of the activity, and an output which only exits at the conclusion of the activity, and where the number of resources to perform one iteration of the activity does not change during.
    -David
     

    0
    #88549

    Leung
    Participant

    Consider using the detail process charting methodology (ANSI Y15.3M) that was developed specifically for documenting business processes.  It provides far better visibility – all items (forms, reports, screens, emails..), person, place, value-added, non-value added, delays… and level of detail is much less of an issue. It breaks work down into doing work, checking work, moving work from one location to another and nothing happening.  You add another step (symbol) whenever the type of activity (symbol) changes. You can find a description of this methodology at http://www.processchart.com

    0
Viewing 8 posts - 1 through 8 (of 8 total)

The forum ‘General’ is closed to new topics and replies.