Monday, May 10, 2010

Proposal Writing: What Do Clients Really Want? (Learning from our Failures)

OK, “failure” is kind of a strong word in this case. But here’s the story: We recently had the opportunity to do a “post mortem” kind of meeting on a deal we didn’t get (hey, you can’t win them all, right?) We thought we knew why, or had some ideas at least, but we wanted to find out for sure.


The client was generous enough to give us an hour of his time, and honest enough to give us really candid and open feedback. So what did we learn? Some of the things we had assumed were true, but there were others. The one that resonated most for me is the Business version of the grammar school advice to “Show your work”.


Our team had spent hours discussing this project, formulating an approach, and really drilling down into the details. In an effort (and it did take some effort) to make a clear proposal, we eliminated all the details behind our recommendations. Unfortunately the client interpreted that as a lack of analysis, and why not – he didn’t see it, so in his world it didn’t exist.


This really hit home for me. I was always a proponent of the short, sweet, clear proposal. I don’t’ know about others but I typically don’t want to read 20 pages of what someone thinks, but (ha – fortunately :-) ) not everyone is like me. Looking back it seems obvious that we should have included all the “sausage making details”, perhaps as an appendix or perhaps in the main proposal with an executive summary. I’m curious, what do others do?

No comments:

Post a Comment