David McCoy

Scenario 1: Attended a kid birthday party at one of those game-pizza-noise places.  Everyone who comes in gets stamped with a UV readable number. Upon leaving, you take only the kids that match your number.  Fair deal.  Well, I watched families leaving and no one was checking them out.  In fact, there was no one at the exit gate.  I mentioned this to a clerk.  She was dumbfounded that I even brought it up.

Scenario 2: At the doc’s.  You know the drill.  Fill out the paperwork and swear that you have read the copy of the HIPPA rules they gave you.  Only, they didn’t give you any.  So, you ask for the rules and get a strange look like you are from Mars.  Who asks for HIPPA rules?  What was I thinking?

Analysis:  Stop lying with processes, ok?  If you create a process to protect children, the process has to be followed from end to end. It’s no good to do the front-end “aren’t we the careful company” stuff and then skip the part that really matters.  And if you mention a process step in your documentation – “I certify I have read the provided forms” – then don’t freak out when someone actually asks you to provide the forms… the ones you said you already provided.

It’s things like this that could drive me to drink.  Only, I would probably drink too much and then have to go to the doctor’s and have to pretend to read some regulation they didn’t give me.  That would add insult to injury.  Instead, I think I’ll just go grab a pizza, get a UV stamp, and run in and out the exit door, just for fun.  No one will notice.  That’s because some people build processes without any regard for whether they actually work.

Submit a Comment »

Category: Business Process Management (BPM) Business Rule Management (BRM) Philosophy Rabble-Rousing and General Hoopla     Tags:

Share