Saturday, February 13, 2010

Paralyzed by Procedures

We often work with clients who have documentation in place. Of course, more often, we work with clients who DON'T! That aside, though, those who may have documentation, procedures documented in support of their processes, often wonder why, after all the investment in documentation, things still don't work. There are a lot of reasons for this but, simply said, just writing down your procedures will not guarantee a smooth running infrastructure. Questions we have to ask include:
  1. Have you considered the hierarchical "Policy-Process-Procedure" model whereby they support a higher, overall, more holistic objective or goal?
  2. Are your procedure truly written in support of the process?
  3. Have you considered the interdependencies and interfaces between your processes and procedures?
  4. Do you have buy-in for the processes?
  5. Is your documentation formally published in a common and controlled repository, under version control and change management, and available to all those who need visibility?
  6. Do you have defined process owners with authority to monitor, manage, and improve their processes?
  7. Is there a chance your procedures are driven by the tool selected for automation rather than the process itself?
  8. Have your procedures been tested?
  9. Can you measure the performance of your processes and procedures and is there a feedback loop to drive improvement?
  10. Do you encourage compliance to process and procedures?
Think about these questions in the context of the procedures our TSA personnel use at the airport security checkpoints. Here we have very well defined procedures ranging from what liquids you can pack in carry-on, the ID check, and the "stuff" one needs to put on the X-ray belt. However, ask yourself this one question: "Are we simply executing to the 'letter of the law (defined procedure)' to the exclusion of the objective of these procedures?"

I would submit that the procedures used by TSA actually get in the way of the overriding objective. If you have been through a European security check lately, you'll know exactly what I'm saying. While they have these procedures too, they haven't lost sight of the overall objective. They see the procedures as one component - critical component indeed - but just one component of an overall system designed to achieve an objective.

Put your processes to this test: "Do our processes and procedures effectively serve the overall objective?"

Labels: , , ,

Saturday, May 24, 2008

What's a Statement of Work Worth?

Nothing, if it's not signed.

Imagine a project that started before all stakeholders had reviewed and then signed the Statement of Work. Imagine this same project that began incurring expenses before the "i's" were dotted and the "t's" crossed. Imagine a project team that developed deliverables on-the-fly while the delivery organization and the client were still negotiating the SOW. Oh and think about the impact on the project team as the objectives and deliverables were being defined, redefined, and restated again and again while the project was underway!

It happened. And it's probably happening right now many times over.

The downside to this is not the litigation that resulted; not even the frustration of the client and delivery organization. Nor is it the sleepless nights of the project team, project manager turnover (a total of three project managers bit the dust during the 9 month project), and overall frustration of all involved. The real tragedy here is the squandering of a really great idea and the enthusiasm of a project team because of a decision to move to execution prematurely.

Labels:

Thursday, September 06, 2007

Aggravating Transactions? Why Didn't We Ask the Customer First?

ComputerWorld's September 3 issue carried an opinion piece that demonstrates, so vividly, just how backward many organizations can be when it comes to process. The article describes a bank, which was determined to be "customer focused." Apparently they turned to technology to "make it happen" by implementing a CRM system. The design was to ensure that the branch bankers could offer, "the right products every time they interacted with customers" (ComputerWorld, Sept. 3, 2007, p. 30). As I might have predicted, the technology failed to do anything but upset the customers. This is a perfect example that I have seen over and over-technology is implemented with no insight, understanding or even the slightest consideration of the customer needs: only those of the business. The business knew what they wanted. But they didn't take the time (didn't budget for) to understand the customer. Somehow industry today seems to think that every problem has a technology solution and just by putting code in place, the problem will be resolved. The article goes on to describe just what a mess this b-ass a-kward approach created.

Unfortunately, the author of the opinion missed the point of the whole case. As I read this piece, he claims that "...process design works against this kind of re-vamp. IT needed to step back from technology and envision the future...". OK, I agree that IT needed to step back. But it needed to step back further than he suggests. Process design DOES NOT work against such an effort if, in fact, the process design is executed by a professional with an understanding of how to capture the "voice of the customer." THAT, not technology, is where you start such an undertaking. I am regularly amazed at the number of organizations that refuse to talk to the customer first: to establish the criteria that will become the specifications for the solution. Is it fear? Are they afraid to talk to the customer? Or do they just not know any better?

I find it amazing, and a wee bit amusing, that many organizations never have the money to understand the customer before setting criteria that will dictate code that will ultimately impact the customer. Yet they find the money for a "do-over" once the initial effort fails. This, however, costs them in terms of Good Will. On the surface it's an intangible. But it's a real cost. Put a price on that will ya!

Labels: