The business of writing for business
RSS icon Email icon Home icon
  • Why God Made Case Studies

    Posted on June 26th, 2009 Dan M. Comments

    In a recent post on Positive Disruption, blogger and marketing veteran Tom Martin wondered why prospective clients could intuit the benefits of social media as a marketing tool, and yet still demand some proof-of-concept before committing. An excerpt:

    But alas… the lack of good case studies impedes the adoption of a [social media] strategy… People need proof in order to believe. Even God needed to show proof of his being, whether it was a burning bush, parting a sea or the ultimate case study, resurrection of his son from the dead.

    …While we’d like to be able to just say something is so and have others agree, case studies are the currency of persuasion.”

    Photo credit: Athena's Pix

    Photo credit: Athena's Pix

    Go read Tom’s post here, if you like. I’ll wait…

    Tom is dead on. It’s a lot easier for clients to take a leap of faith (i.e. divert precious time, resources or money) when they know they’ll land on their feet.

    Case studies testify to that. Written like a three-act play, they describe a problem, the solution you offered and the subsequent benefits enjoyed. By the last act, your prospective customer has real-world proof that a past client not only landed on their feet, but actually profited from putting faith in you.

    The problem is the solution
    The problem is that benefits don’t necessarily close the deal.

    To take Tom’s theme one loaded step further, not even God could get people behind his program by simply promising its benefits – and nobody can sell the bennies like God.*

    Many case studies (i.e. those written by less rigorous and talented freelance copywriters) make a similar mistake. They briefly identify the problem, briefly mention a product solution, and then spend reams of text describing the benefits. Benefits, the reasoning goes, resonate emotionally with customers. And that’s true.

    The problem, in part, is that we’re not reasonable creatures. Prospective customers may indeed recognize the benefits of your solution. They may even trust you can deliver those benefits. But they’re only human, and humans don’t necessarily act in their own best interests. They balk, analyze, consider and reconsider their options no matter how attractive the promised benefits, or credible the source…

    Irrational? Yes.

    Wise? Also, yes.

    Your customers should question how long and difficult an unfamiliar path will be before it delivers on the promised benefits. Some of God’s beta customers might have something to say about a forty-year desert sojourn that was not clearly disclosed in their contract to be the Chosen Ones bound for the Promised Land.

    By the time God began preparing to update his book, The Testament, he realized he needed to invest less in selling benefits and more in educating people about the practical, progressive steps that would lead to those benefits. (How lucky for him he had a kick-ass marketing professional in the family who happened to know some crackerjack copywriters.)

    Alright… dead horse… Let’s wrap up…

    My point is this: Illustrating a clear path to benefits can be just as persuasive to customers as the promised benefits themselves.

    Case studies can and should address the unconscious assumptions that lead the doubting Thomas’s to balk. They should illustrate how simple and painless your proposed path toward a better world can be. Some often forgotten questions include:

    • How long before I can expect to see results?
    • How much time and money can I expect to invest up front?
    • What trade-offs or lessons learned, if any, have past customers encountered?
    • What staffing resources will I need to divert before, during and after implementation?
    • How much will implementation disrupt my day-to-day business operations?
    • How well did the vendor anticipate and/or overcome unexpected challenges during past implementations?

    These are legitimate concerns, and none of them have anything to do with the benefits your solution has provided in the past.

    When case studies rush to describe benefits, they miss an important and often critical opportunity to sell a smooth implementation process – which, regardless of what you’re selling, contributes just as much to building trust in new business relationships.

    *Opinions voiced here are not necessarily reflected, endorsed or even tolerated by Tom Martin, who is,  I’m sure, an altogether professional, decorous fellow who only occasionally uses salty content to illustrate a point.

    • A little off topic, but since your post is about case studies, I hope you will indulge me. However, I've often wondered how effective and/or detrimental it would be to use case studies both for projects that worked and projects that did not work.

      On the one hand it is good to know that a particular course of action was perfect and delivered results.

      On the other hand, if we are being transparent, things rarely go as planned and we make mistakes. Momma always said that's the only way we learn, right?

      Are clients interested in only seeing perfection? Or, would they appreciate seeing brutal honesty of process and thinking, accompanied by the realization that it didn't work out like we had planned. But, we became wiser and will be better prepared to handle similar situations going forward.

      Any thoughts?

      I don't want to attempt to find a Biblical example to illustrate my point, but I'm sure someone could figure out how to do it.
    • That's good food for thought, Jake. But I can't imagine it getting much traction with many marketing people, much less CEOs. The problem is that prospective clients might stop reading before they reach the magic "lessons learned" part. Another potential drawback is that a clever competitor could get hold of the content, and present it out of context.

      For the sake of argument, however, there are a couple ways that I might imagine this approach working.

      One approach would still see the case study ending happily, with a solution eventually found and benefits served. The underlying message, however, would need to be how committed the vendor was to solving intractable problems. The case study would also need to take pains to emphasize that, as a matter of vendor policy, no extra costs were incurred during the learning curve.

      The more notoriously difficult the problem, the better. If the vendor found a way, for example, to travel faster than the speed of light, all its failed early attempts would just add to the compelling narrative. Then again, if this were the case, a white paper, trade article or some other format favoring "thought leadership" might be a better way to present the story.

      The other condition where your proposal might work would be if the case study was part of a large, very cohesive integrated marketing campaign that emphasized integrity, transparency and a larger success rate. For example, let's say a vendor developed a breakthrough crowd-sourcing platform designed to provide design solutions to paying subscribers. If the vendor could demonstrate its platform provided actionable solutions 80% of the time, then a transparent marketing campaign describing aberrational failures alongside a pattern of success might work. The important part is that the case studies of failed attempts would be clearly presented against the backdrop of an 80% success rate.

      Bottom line - and I find this to be particularly true for freelance business writers: A "willingness to learn" is NOT a highly valued commodity among prospective clients.
    • Love the "path" analogy. It hadn't hit me before, but as I read this post it came home... what's wrong with so many case studies is they are just brag pieces. Here was the problem. Here was our brilliant solution. Blah!

      We don't take the time to show the path we took from A to B, which is where the real brilliance is located.

      Thanks Dan. Glad you thought enough of my post to write this... you just made me a bit smarter... owe you one!
      @TomMartin
    blog comments powered by Disqus