3
Home | Book Store | Toolstore | Consulting Room | Contact | FAQs & Search | About Process Management Related Books Process versus procedures The language of the 20000 revision to the ISO 9000 series significantly moves away from procedure to process so is this change any more than simple semantics or is there something fundamental going on? Identifying and managing critical business processes is a vital factor in the effective management of successful organizations. This appears to be a fairly obvious statement. At the heart of the business excellence model there is a strong beat generated by the emphasis on process management. Within the context of quality management standards, and more specifically IS0 9000, 'procedure' is a key word which has acquired a particular meaning over the years. The term process on the other hand might appear to be new in ISO 9001:2000 but the concept of an organization being a network of processes was addressed in ISO 9000:1994 so it is not new. What is new is the concept that the results an organization achieves are the product of the interaction between its processes and not its procedures. The following table illustrates the difference between procedures and processes. Procedures Processes Procedures are driven by completion of the task Processes are driven by achievement of a desired outcome Procedures are implemented Processes are operated Procedures steps are completed by difference people in different departments with different objectives Process stages are completed by different people with the same objectives departments do not matter Procedures are discontinuous Processes flow to conclusion Procedures focus on satisfying the rules Processes focus on satisfying the customer Procedures define the sequence of steps to execute a task Processes transform inputs into outputs through use of resources Procedures are driven by humans Processes are driven by physical forces some of which may be activated by humans Procedures may be used to process information Information is processed by use of a procedure Procedures exist they are static Processes behave they are dynamic Procedures cause people to take actions and decisions Processes cause things to happen Procedures In its simplest form a procedure is a way in which one works to accomplish a task. It can therefore be a sequence of steps that include preparation, conduct and completion of a task. Each step can be a sequence of activities and each activity a sequence of actions. The sequence of steps is critical to whether a statement or document is a procedure or something else. Specifications, contracts and records are not procedures as they do not tell us how to do anything. These describe the outputs resulting from carrying out procedures or tasks, leaving us to decide any further actions necessary to use these outputs. The output will more than likely be used as inputs to other procedures. We need procedures when the task we have to perform is complex or when the task is routine and we want it to be performed consistently Hence procedures are intended to make something happen in a certain way. If we are not concerned about how something is done and are interested only in the result we do not produce procedures but issue instructions such as 'post the letter', 'repair the spin drier' or 'recruit another person'. These are work instructions as they intend us to do 'quantitative' work without telling how to do it or the 'qualitative' standard to which the work should be carried out. Instructions are not procedures unless they follow in a sequence and enable us to perform a task. A set of selfassembly instructions is a procedure as it tells how to proceed to assemble the product. But the wording on the label telling us not to put hot objects on the surface is an instruction or a warning (a special type of instruction). As procedures are normally used by people they are designed with a user in mind. The user is normally an individual or a group of individuals, although procedures can cover a sequence of steps each of which is performed by different individuals or groups. However, perceptions of procedures vary considerably depending on the context in which they are created and used. Any sequence of steps, no matter how simple or complex, can be expressed as a procedure that is intended to cause someone to act in a certain way to accomplish a task. The key is that the steps follow a sequence. A random collection of statements is not a procedure unless we rearrange these in a sequence that enables someone to proceed. Is it a procedure or a misnomer?

Process vs Procedure

Embed Size (px)

DESCRIPTION

Process vs Procedure

Citation preview

  • 6/16/2015 ProcessvsProcedure

    http://transitionsupport.com/Process_versus_procedure.htm 1/3

    Home|BookStore|Toolstore|ConsultingRoom|Contact|FAQs&Search|About

    ProcessManagement

    RelatedBooks

    ProcessversusproceduresThelanguageofthe20000revisiontotheISO9000seriessignificantlymovesawayfromproceduretoprocesssoisthischangeanymorethansimplesemanticsoristheresomethingfundamentalgoingon?

    Identifyingandmanagingcriticalbusinessprocessesisavitalfactorintheeffectivemanagementofsuccessfulorganizations.Thisappearstobeafairlyobviousstatement.Attheheartofthebusinessexcellencemodelthereisastrongbeatgeneratedbytheemphasisonprocessmanagement.Withinthecontextofqualitymanagementstandards,andmorespecificallyIS09000,'procedure'isakeywordwhichhasacquiredaparticularmeaningovertheyears.

    ThetermprocessontheotherhandmightappeartobenewinISO9001:2000buttheconceptofanorganizationbeinganetworkofprocesseswasaddressedinISO9000:1994soitisnotnew.Whatisnewistheconceptthattheresultsanorganizationachievesaretheproductoftheinteractionbetweenitsprocessesandnotitsprocedures.

    Thefollowingtableillustratesthedifferencebetweenproceduresandprocesses.Procedures Processes

    Proceduresaredrivenbycompletionofthetask Processesaredrivenbyachievementofadesired

    outcome

    Proceduresareimplemented Processesareoperated

    Proceduresstepsarecompletedbydifference

    peopleindifferentdepartmentswithdifferent

    objectives

    Processstagesarecompletedbydifferentpeople

    withthesameobjectivesdepartmentsdonot

    matter

    Proceduresarediscontinuous Processesflowtoconclusion

    Proceduresfocusonsatisfyingtherules Processesfocusonsatisfyingthecustomer

    Proceduresdefinethesequenceofstepsto

    executeatask

    Processestransforminputsintooutputsthrough

    useofresources

    Proceduresaredrivenbyhumans Processesaredrivenbyphysicalforcessomeof

    whichmaybeactivatedbyhumans

    Proceduresmaybeusedtoprocessinformation Informationisprocessedbyuseofaprocedure

    Proceduresexisttheyarestatic Processesbehavetheyaredynamic

    Procedurescausepeopletotakeactionsand

    decisions

    Processescausethingstohappen

    Procedures

    Initssimplestformaprocedureisawayinwhichoneworkstoaccomplishatask.Itcanthereforebeasequenceofstepsthatincludepreparation,conductandcompletionofatask.Eachstepcanbeasequenceofactivitiesandeachactivityasequenceofactions.Thesequenceofstepsiscriticaltowhetherastatementordocumentisaprocedureorsomethingelse.Specifications,contractsandrecordsarenotproceduresastheydonottellushowtodoanything.Thesedescribetheoutputsresultingfromcarryingoutproceduresortasks,leavingustodecideanyfurtheractionsnecessarytousetheseoutputs.Theoutputwillmorethanlikelybeusedasinputstootherprocedures.

    WeneedprocedureswhenthetaskwehavetoperformiscomplexorwhenthetaskisroutineandwewantittobeperformedconsistentlyHenceproceduresareintendedtomakesomethinghappeninacertainway.Ifwearenotconcernedabouthowsomethingisdoneandareinterestedonlyintheresultwedonotproduceproceduresbutissueinstructionssuchas'posttheletter','repairthespindrier'or'recruitanotherperson'.Theseareworkinstructionsastheyintendustodo'quantitative'workwithouttellinghowtodoitorthe'qualitative'standardtowhichtheworkshouldbecarriedout.Instructionsarenotproceduresunlesstheyfollowinasequenceandenableustoperformatask.

    Asetofselfassemblyinstructionsisaprocedureasittellshowtoproceedtoassembletheproduct.Butthewordingonthelabeltellingusnottoputhotobjectsonthesurfaceisaninstructionorawarning(aspecialtypeofinstruction).Asproceduresarenormallyusedbypeopletheyaredesignedwithauserinmind.Theuserisnormallyanindividualoragroupofindividuals,althoughprocedurescancoverasequenceofstepseachofwhichisperformedbydifferentindividualsorgroups.However,perceptionsofproceduresvaryconsiderablydependingonthecontextinwhichtheyarecreatedandused.Anysequenceofsteps,nomatterhowsimpleorcomplex,canbeexpressedasaprocedurethatisintendedtocausesomeonetoactinacertainwaytoaccomplishatask.Thekeyisthatthestepsfollowasequence.Arandomcollectionofstatementsisnotaprocedureunlesswerearrangetheseinasequencethatenablessomeonetoproceed.

    Isitaprocedureoramisnomer?

  • 6/16/2015 ProcessvsProcedure

    http://transitionsupport.com/Process_versus_procedure.htm 2/3

    WithinthecontextofQMSs(andmorespecifically,ISO9000)theprocedurehas,formany,takenonparticularandsometimespeculiarcharacteristics.Such(documented)proceduresmaybewritten,notasasequenceofactivitiesorstepsbutasaseriesofrequirementsoraseriesofresponsibilities.Neitherofthesecanbeproceduresastheydonottellushowtoproceed,whatstepstotakeorhowtomeasuretheresult.

    Suchproceduresoftenfollowauniformformatwithapurposestatement,applicabilitystatement,responsibilitiesandthenprocedurestatements.Oftenthereisnoconnectionbetweenthepurposestatementandtheprocedure.Purposestatementsoftenaddressthepurposeofadocumentnotthepurposeofthetaskwhichthesequenceoftasksisintendedtodeliver.Again,ifsuchprocedures(andrarelytheydo)containmeasuresofsuccess,theseareprobablyquantitativemeasuresrelatedtothetaskitselfandnottowhytheprocedureiscarriedout.Themostcommonperceptionofsuchproceduresisthattheyaresimplyassociatedwithpaperworkandfillinginforms.

    Weseemtothinkthatwehavecreatedaprocedurebyclassifyingadocumentasaprocedure.Thesedocumentsareoftenthoughtofashighlevelprocedures.Proceduresdonothavetobedocumentedtobeproceduresanddonothavetobeonlyhighlevel.Weoftenhearofproceduresaddressingthe20elementsofIS09000andworkinstructionsbeingusedatdepartmentalleveltoguideactivities.Thesecharacteristicsofproceduresonlyservetoconstrainourthoughtsandourintent.

    Processes

    Processesproduceresultsbyconverting.transformingorsimplyusinginputstocreateoutputs.Aninputcouldbematerial,information,peopleorasetofconditionsandthesearepassedthroughasequenceofstagesduringwhichtheyareeitherused,transformedortheirstatuschangedtoemergeasanoutputwithdifferentcharacteristics.Henceprocessesactuponinputsandaredormantuntiltheinputisreceived.Ateachstagethetransformationtasksmaybeprocedural,butmayalsobemechanical,chemicaletc.Inherentlyprocessesdonotnormallyrecognizedepartmentalorfunctionalboundaries(butareoftenhinderedbythem)northeboundariesbetweencustomersandsuppliers.Eachprocesshasanobjectivewithbothquantitativeandqualitativemeasuresofitsoutputsdirectlyrelatedtoitsobjectives.Thetransformationorprocessstagesaredesignedtoensurethecombinationofresourcesachievestheobjectivesthedesiredoutputs.Ofcoursethismeansthattheprocesshastoreceivetherightinputstodeliverthedesiredoutputsandthatthecorrectresourcesareappliedattherightstages,inthecorrectquantitiesandintherightmannerItistruethataprocesscanbeillustratedasasequenceofstepsjustasaprocedureisillustrated,butthesimilarityendsthere.

    It'sthewayweusethem

    Thewayweusethewordsprocedureandprocesstellsussomethingabouthowtheydiffer.Wetendtostartandstopprocesses.Weimplementproceduresandcommenceandcompletethem.Weprocessinformation.Wedonotprocedureinformationbutwemayemployaproceduretoprocessinformation.Wehaveplatingprocessesandtheremaybeplatingprocedures.Inthiscontext,theplatingprocesscomprisestheresources,people,plantandmachinery,andtheplatingprocedurecontainstheinstructionsonhowtoplatematerial.

    Wehaveprocessinterruptbutnotprocedureinterrupt,becauseprocessesareperceivedascontinuousandrununtilphysicalintervention.Inourbodieswehaveprocesses,notprocedures.Thereproductiveprocess,thedigestiveprocess,therespiratoryprocess,theseprocessesarecertainlycontinuousandstoponlywhenaninterventiontakesplace.Theymayrequirehumaninterventioninwhichasurgeonmayemployprocedurestoeffectarepair.Proceduresontheotherhandareperceivedasbeingdiscontinuous,havingstepswhichcanbepausedwithactivitiesoractionspickeduporputdownatwill.

    Proceduresusuallyrelatetogroupsofactivitieswithagivenoutputwherethatoutputmaynotbecompleteuntilacteduponbysomeoneelseatalaterstageintheprocess.Therefore,proceduresaretheactionstakenbyindividualsinaprocessthatmayspanacrossseveralfunctionsandusemultipleresourcestodeliverapredeterminedoutputatagivenrateatagivenlocationonagivendate.

    Allchange

    Whetheranychangeisnecessarydependsuponperceptionandattitude.Ifdocumentedproceduresmerelyrespondtorequirementsinastandardtheyarenotlikelytodemonstrateaclearlineofsighttotherealpurposeofwhytheprocedureisnecessary.Thisisveryoftentherootcauseofwhythepeopleinvolveddonotseethevalueincarryingouttheactions.Itisverylikelythatmanyorganizationswillhavetoundergoafairlyradicalrethinkofthewaytheyregardtheirmanagementsystem.Inordertosatisfytherequirements,needsandexpectationsoftheinterestedparties(customers,shareholders,employees,suppliersandcommunity)organizationshavetoidentifythecriticalprocessesthatdeliversatisfaction.Itisalsoclearthattheeffectivemanagementofthoseprocessesdependsuponcommonunderstandingandmonitoringofhowsuccessismeasured.Perhapsthemostcrucialandradicalfactoristheconstantfocusandalignmentofthekeystagesonachievingtheendresults.

    Theimplicationhereisthatinmanycasestheorganizationandtheactivitiesmusthaveagreateralignment.Thepreviousnotionofa'functional'organization(forexample,wheredifferentdepartmentshavecreatedtheirowninternalagendasandcultureswithnoclearlinkagetodefinedorganizationalobjectives)hastobeseriouslyquestioned.Itisalltootemptingfororganizationstoaddressthisissuebysimplyadoptinga'crossfunctional'approachwhichinrealitymeansthattheygathertogetherrepresentativesfromdifferentfunctionalbunkersandletthemfightitout.Ingeneral,crossfunctionalteamsarenotasubstituteforprocessmanagement.Simplistically,functionstendtobeverticalinnature,processesarehorizontal,withstakeholderinterestatbothends.

    Tomakeatransitionawayfrommanagingprocedurestowardsprocessmanagement,anorganizationmustanswerwhetherithas:

    clearlydefinedwhatitsobjectivesareandhowitwillmeasureandreviewthesuccessofachievingthoseobjectives

  • 6/16/2015 ProcessvsProcedure

    http://transitionsupport.com/Process_versus_procedure.htm 3/3

    evaluatedtheimpactofthoseobjectivesontheinterestedparties,thestakeholders

    designedthecritical,endtoendprocessesnecessarytodelivertheobjectives

    assessedandprovidedtheresources,skillsandcompetencetomaketheprocesseswork

    TheunderlyingprinciplesofthebusinessexcellencemodelandthelatestversionsofISO9000,ISO9001andISO9004shouldleavepeopleinnodoubtthatthechangeinlanguagefromproceduretoprocessisnotaboutperceptionorsemantics.Thereisaveryrealchangeoffocusrequiredbymanyorganizationsiftheyaretoremaincompetitive,andwiththischangecomesthesignificantopportunitytoensurethattheirprocessesaredesignedtoconsistentlyaddvalue.

    NowlookatourFAQsonprocessesformoreinformation

    ActivescriptingneedstobeenabledinIEtousethepulldownmenusLastamended24/08/2013

    Home|Bookstore|ToolStore|ConsultingRoom|FAQsandSearch|Contact

    TransitionSupport2013