Today, Seth tackles fuzzy-wuzzy specifications. Arguing that a clear spec is clearly (hah!) the best way to get what you want, he asks why so many specs are not clear: vague, murky, and even contradictory.
If you write a great spec,
we get to blame you if it doesn’t work out.
Maybe that’s why so many SOWs and even proposal instructions are, to quote the master, “vague, murky, and even contradictory.” Maybe it’s fear of blame and/or accountability.
Maybe it’s also because, to quote George W. Bush, it’s hard.
It’s hard to clearly specify the work we want. We must first know it well enough to define the outcomes we want and then distinguish those from the methodology used. We must be able to fairly evaluate methodologies that are not the same-old way we’ve always done things. It requires a high level of domain knowledge and some ability to think outside the box.
It’s hard to sensibly specify the response we want. We must first know how we’re going to distinguish between proponents: what we need to know about them or their plans to help us make a high-confidence selection. Otherwise, we’ll just keep asking for the same-old plans that drive immense work for bidders and that our in-house evaluators might not even be able to assess or to differentiate.
Professionally risky + hard = ???
It doesn’t look like an equation that would add up to success, does it? Usually it doesn’t. Recognizing that fact is the place to start on doing better.