Chicken and egg aggravating? Just start somewhere …

Conversations this week with folks in multiple, different organizations I have connections to, about formal change controls. The general rule, especially for the non-public companies, seems to be reasonable levels of process, but not as well documented, automated, and not as rigidly enforced as the more rigorous among us would prefer.

It was interesting talking with the groups that were most frustrated; the developers will talk the talk, but find ways to get around the process when crunch time comes up. Of course, some will use the “boss needs this ASAP” line, but when I check with those who know their management, there is really no desire to circumvent tight process just because someone says so.

The challenge seems to be where to begin, and making the requisite time to “do it right”. How often have we made policy, captured it in an eMail and sent it ’round to the usual cc: list … and then are surprised a few months later when the same conversations come up anew.

My favorite way to tackle any documentation or process design that is at the lower end of the priority scale is what I call my Ovid approach (AKA). Each time you touch the process, just improve the documentation / design / structure a little more. Before long, you’ll notice a really nice document!

Automation is another powerful process enforcer, a favorite in our shop. It’s a lot easier to control when stuff gets pushed into production when there is only one way, automated, audited, and reversible. For us, when something needs to get on a web site, say, by 8am the next morning, that really means it’s gotta get to the staging server by 2am – else the automated push will have to wait until the next night. A structured, documented, auditable process is quite easy to “blame” when folks grouse about the lack of immediacy – quality first, yada yada.

Mind you, this is actually a hard push-back on the folks making these complaints / observations. It’s generally easier to be frustrated with the nature of things than it is to do the proper documentation / automation.

This Post Has 0 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Articles
Complexity Buzzword

Navigating Buzzword Overload: Complexity

Complexity means different things to different people in different conversations. Are we trying to simplify a process? Complexity is bad. Understand a supply chain? Complexity is good. Don't buzzword your initiatives with "complexity" until you get a wee bit more specific.

Read more
Saving For A Rainy Day ... (Innovation Budget)

Accelerate Innovation with a Simpler Budget Approach

Organizations are desperate for innovation, but these are still investment choices that require complete and credible data to enable the right decisions. Developing a simple standard for characterizing all costs will accelerate decision making.

Read more

An Author’s Journey – The Editor’s Harsh Bright Light

Second in a series of articles on the creation of Don’t Think So Much. Exposing yourself to the unbiased eye of your editor will be a humbling, but super valuable, experience.

Read more