Reduce Reuse Recycle

I’m an avid reader of the 2000 bloggers blog. It gives me a break from the normal techie and cms stuff that I review in my rss reader. I recently read a post titled the same as this post. Needless to say my brain started to run thinking wow is that a content management mantra or what. Write more meaningful pieces, allow for other to use your content, and when your content is irrelevant archive it. Of course the actual post was about fruit.

Sometimes we implementers of Content Management software take this mantra a little too much to heart. We try and design content solutions that will strictly enforce the Customer to Reduce, Reuse, and Recycle. When I say strictly I mean we programmatically implement software that enforces the “rules” with immediate actions taking place. For instance I was handed a requirement once that said every piece of content on a web site needs to be review every quarter or face removal from the web site. So as the developer of the system I write code that sends a note to the content manager of the piece that is 3 months after the last time it was modified or reviewed. A week later the same code removes the piece from the web site if the content wasn’t reviewed. For the most part this could be ok but we all know that this rule will execute on something like the contact us page or the legal disclaimer. Oops, my bad, I just coded what you asked for right? Well not really, but this is a poorly analyzed requirement. This is where the solution and project leads need to proof the requirement and make sure that the developers can’t infer requirements or implement risky unrefined requirements. When I proofed requirements in the past I’ve been passed over by others saying well Travis you just need to think a little more high-level. Well sorry I know that requirements like the one mentioned above happen every day and there are real ramifications because of vague or “high-level” requirements going to the implementers of content management software. So beware of vague and unproofed content requirements.

Comments are closed.