Found an error? Design a process!
Tuesday, May 19th, 2009When you find an error in your process or system, you should do an analysis of the reason you made that error. Many times, you may find out that the reason that an error was made is that you don’t have a process - or that the process wasn’t followed (but that’ll be another post…)
So, if you don’t have a process - design one!
HOW do you design a process? Easy peasy - map the process out. How do you map a process? Write down the steps that need to be done in order, try following those steps, then refine it until you’ve got it where you want it.
Here’s an example: we rent our Texas beach house out on VRBO and HomeAway. During this time of year, we get a LOT of requests for summer rentals. The big risk is to rent the place twice for the same night(s) - double booking, so we want to make sure that we have a process in place. Sure enough, we didn’t have our process in place, and ended up with a double booking this year; luckily, we caught it within an hour of accepting the second booking, so only had to apologize profusely and refund the deposit. [It would've been MUCH worse if both families had shown up at the beach place expecting to stay for a week!]
So the problem remained - we had double booked. How to revise our current process?
- we stopped letting all folks take and make reservations - I am now the linchpin for the reservation process, and although others can check the account and answer queries, I’m the only one who accepts a deposit.
- We track every reservation and deposit on a spreadsheet - and the process has to be followed in order. So, a reservation has to be logged in and the calendar dates have to be blocked out before we deposit the money, as an example - to ensure that money isn’t accepted prior to verifying that the calendar is available. The spreadsheet is sorted by date, so this should ensure that we don’t double-book.
- Our double check for this is to make a copy of the check or credit card deposit, and to file those by dates in a paper backup file. [That's how we found out that we had double booked - the calendar hadn't been updated, but we had a deposit for that week already.]
- Then, and only then, do we let our guests know that they have secured the reservation and continue the process.
We are hopeful that these tweaks will work for us, but are vigilant to identify possible ‘loopholes’ in the process, and plug them up. This is the essence of effective corrective action - monitoring to ensure that the process design is robust enough to prevent recurrence of the problem.
Have you had a problem, or made an error, and put a process in place to ‘fix’ it? Post it here or contact me at marymcd@mcdcg.com - I’d love to hear about it!
|
|
|
|
|
![]() |




