Jump to content
The Wifcon Forums and Blogs
Guardian

Ensuring the Development of a Clearly Written SOW

Recommended Posts

Hi Folks,

I am here to confront you all with an age-old CO problem, how to get your COR to write and submit a decent statement of work.  I have a rather large, high-visibility requirement for services.  The COR started out by submitting the previous SOW, with six-year old data.  I went through this monster of a document, plastering it with track changes and an abundance of comments. I gave the COR ample time to make corrections, but not too much time.  I scheduled the submission of the revised document via Outlook, setting it up as a meeting.  The COR initially accepted, but then asked for more time one day prior.  The night before the rescheduled meeting, he called me distressed, making it apparent that he had yet again procrastinated.  He is halfway across the country from my regular work site.  Therefore, bringing him into my office and locking the door to keep him there until we can hammer out all the changes is a non-starter. 

With the exception of PhD-holding CORs with whom I've worked on R&D contracts, nearly every experience finalizing a SOW with a program office has been lackluster.  The IT folks are smart in their own respect, but typically poor at explaining themselves on paper.  Most other CORs exhibit significant shortcomings with the written English language.  At the risk of sounding smug, I read about two books a week, typically non-fiction and pedantic novels.  My first love has always been writing.  I realize most people are not going to meet my fullest expectations.  Accordingly, I have relaxed them a whit over the years.  My director is appalled by what we have for the SOW after months of time.  I figure after one spends two days going through a program office's document, offering innumerable comments, it gets the point in which you say, I have served up my best suggestions, the ball is in their court.  I have done this dance at other agencies as well.  It seems to always play out the same.  The director bellyaches that the SOW is the COR'S responsibility.  We take it as far on down the line as we possible can before that same director relents, calling me into his/her office to request that I put it in final form.  Need I make the obvious comparison to our elected officials who grudgingly and with such pained display surrender the stake of taxpaying citizens?

So then, the old standbys are either (1) to rework the document myself, sending it to the COR for approval, at which time they will say, looks great (all the while thinking to themselves, thanks for doing my job for me, sucker) or (2) have my director call their director, which may have some effect, but does little for the quality of our working relationship.  I have never understood why the Government cannot employ professional writers to script these documents, particularly when the requirements they describe involve nine-figures of taxpayer funding.  Other than these two fallback positions, is there an emotionally intelligent way to handle this that is likely to produce the desired results?

 

Share this post


Link to post
Share on other sites

I vote for (2), though sometimes CORs and I rewrite SOWs together.  I hope it helps them, but they write this way so infrequently it's unlikely.

2 hours ago, Guardian said:

I have never understood why the Government cannot employ professional writers to script these documents, particularly when the requirements they describe involve nine-figures of taxpayer funding.

Endorsed.  Division of labor is good.

Share this post


Link to post
Share on other sites

Been there, and done that many times over. At least you have a director who is concerned with having a quality SOW/PWS. My experience has been that I appear to be the only party involved who really cares that the PWS is well written. The attitude of everyone else has usually been why sweat it, it really isn't that important, and would only become an issue if we go to court, which rarely happens so why invest the time trying to perfect the document? So I usually fix what I can, as it easier to fix it yourself than to try to explain what is wrong, and end up having to do it yourself anyway.  Of course some things you can't fix yourself, so you end up with a not so good document getting into the contract.

Share this post


Link to post
Share on other sites

Using Emotional intelligence - Understand and (if its reasonable) empathize with the COR's perspective. She isn't doing bad work to irritate you and annoy her management.  Find out why she is doing what she is doing, and how it looks from her perspective.   Often, when you know this, a mutually beneficial solution is revealed.  

In my experience, the-bad-SOW-the-COR-wont'-fix is usually due to some combination of 1) Doesn't Know, 2) Doesn't Care, 3) Doesn't Have Time.    

PS.  Don't Care is the easiest to address. Find out who does care, and include them into the  group-hug that is an acquisition IPT.  

Share this post


Link to post
Share on other sites

I also agree with General.  If bad SOWs are a wide spread problem, get your management to schedule training.   A session with lots of critiquing examples goes a long way 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×