Follow the Process

A typical morning commute was almost turned into a disaster by another commuter’s shorting of the proper process in changing lanes.  I was minding my own beezwax in my lane when the white Lexus to my left decided that it was coming into my lane whether I liked it or not.  A quick turn and slam on the brakes by me kept us from making a collision, but took me off course into a nicely located development entrance.  Clearly I must have been in this person’s blindspot.  Now I too have made this error when switching lanes when I was younger, but I have learned from it since.  I now go through a two-step process before trying to change lanes.  Step one is to look in my sideview mirror to see if there is anyone on my right.  If this appears clear, I then turn my head and physically look to my back right side to see if anyone is nestled into my blindspot.  If I don’t see anything there, then I will make my lane change.  This has caught a few hidden cars and in turn has saved me from causing a few possible accidents.

This check and check again premise is used by DDA’ers everyday, but not just on the road.  DDA’ers know that proofing is a vital step in our process to turn out flawless products, whether it is some copywriting, a custom programming application, or a corporate video.  Each one of our tireless writing staff has probably read everything that has been written on our websites at one time or another because it doesn’t get proofed just once or by just one person.  It gets proofed after being written and after it gets posted on the website and by clients and after any fixes are made and reviewed once it goes live.  Basically a lot of eyes get to scan the content to make sure it’s perfect.

Unlike the 2-step process I use for changing lanes, DDA uses something more along the lines of a 10-step process. Proofing isn’t only limited to written content though.  All programmed and interactive components need to be tested too.  These tests are more like attacks where you try to break the program in some way or another.  Tests on all types of computers and browsers are also necessary because you never know where something may not work.  A frequent specific trouble maker is for some things to not work on Firefox on a Mac computer.  It’s a very specific combination but someone out there may use it so we need to account for it and make it work.

No matter what process you need to follow for whatever task is at hand, just make sure that you follow all the steps.  Shortcuts don’t always get you the results you want.