If asked, will customers submit themselves as possible case study or success story candidates?
From consumer-products companies to B2B to nonprofit organizations, many now actively solicit stories with self-service “Share Your Story” links on their Web sites.
- Apple created a link for this soon after the release of its wildly popular iPhone.
- FileMaker software includes a link to “Tell us your story.”
- Girl Scouts of the USA asks former members to share their experiences for its alumnae program.
- And Toyota Motor Sales gather owners’ stories and gets usage permission through an online form.
Does customer self-nomination actually work?
Sometimes. I know it’s worked extremely well for Toyota, which has tons of customer experiences on its site.
But some B2B companies have tried the approach with hardly any submissions to speak of.
Are consumers willing to submit themselves more readily than business candidates? Perhaps.
Fortunately, it’s something that’s pretty cheap to try for while, and pull if it doesn’t generate any great story candidates.
Self-Service Story Options
You have a few different options for information that comes through “Share Your Story” links on your website:
- Collect names and customer interest, and then follow up to get the complete story.
- Create a web form that asks for more detail. Then run stories as first-person customer accounts basically verbatim—like extended testimonials. Check for typos, etc. before publishing online.
- Create third-person, professionally written stories from answers that customers provide on a web form.
Be sure to let customers know how stories will be used, and the positive benefits of being featured.
If you choose to run stories based strictly on customer-submitted information, you’ll need a way for customers to indicate their permission as they type in their experiences. Toyota has a check box that handles this.
You may also want a way for customers to upload a photo of themselves, if applicable.
In general, but not always, first person (I, we) stories seem most appropriate for consumer companies while third person (he, she, they) works best for B2B.
To decide the best approach for your company, consider your audience, and maintenance and cost considerations.
Have you tried a web form? If so, share your experience in the comments.
Want more tips for managing your case studies?
Today I'm pleased to bring you a guest post by Stephanie Tilton, the principal of Ten Ton Marketing (www.tentonmarketing.com), and founding member of and regular contributor to the Savvy B2B Marketing blog (www.savvyb2bmarketing.com). She's also a very experienced case study and white paper writer.
Issues throughout the case study development process can derail - or at least complicate - a project.
The following four examples involving a fictitious customer contact named Lucy highlight common pitfalls and ways to circumvent them.
1. Fail to understand the customer's satisfaction level
When you get on the phone to interview Lucy, you probably expect her to speak favorably about your company and its offerings. It seems reasonable enough - after all, Lucy agreed to participate in the case study.
But you just might find yourself blindsided if you don't do your homework.
Before a case study interview, touch base with the account manager or review your customer relationship management database.
It's possible that Lucy - or someone within her organization - had a poor experience using your solution or working with your company between the time you scheduled the call and the day of the interview.
If that's the case, you - or Lucy - may want to reschedule the interview. At the very least, discuss the situation with the account manager to determine the plan for moving forward.
Though not as likely, Lucy might have had a bad experience the day of your call and not yet reported it to your company. In fact, you may be the first to hear about it.
Offer to mobilize the appropriate resources to address the issue and suggest that the call be rescheduled once the issue has been fully resolved.
2. Expect the customer to rattle off project details and metrics
You probably expect Lucy to know everything about choosing and using your company's offering. But that's a poor assumption for two key reasons:
- The person who originally evaluated, chose, implemented, or used your solution may have left the company.
- Lucy might know only a portion of the story, while someone else in the company knows the remaining details. For example, perhaps Lucy knows the technical details while Joe in finance understands how the solution has benefited workers on a daily basis.
Minimize the chances of a frustrating interview by giving Lucy insight into the types of questions you'll cover on the call. Don't think it's sufficient to send a questionnaire as an email attachment - Lucy might not look at it before the call.
In the email, summarize the key questions you'll ask. Be certain to highlight the types of quantitative results you hope to capture.
This heads-up will give Lucy a chance to find the answers - or invite the appropriate people to join the call.
3. Get sidetracked during the interview
Everyone is busy these days. So when you ask Lucy to set aside 30-60 minutes for a call, be sure to respect her time. Lucy expects to be discussing her experience implementing and using your solution.
Don't distract her with questions that aren't directly related to the case study, such as how you can improve your offering.
With a set amount of time for the interview, asking irrelevant questions can mean you don't get everything needed to write the story. The last thing you want to do is bother Lucy with additional questions after the interview because you took up too much time asking tangential questions!
<4. Pressure the customer to review the draft quickly
Want a rapid turnaround once you send the case study to Lucy for review? Then make sure you get the draft into her hands as soon as possible after the interview.
If you take your time sending the case study to Lucy, it's not fair to expect a quick review.
Even if you do send the draft right away, remember, Lucy has her own busy schedule and priorities. The customer review process is out of your hands.
While you don't want to badger Lucy, there are a few things you can do to try to keep the case study top of mind for Lucy. Here's what Casey Hibbard suggests in Stories that Sell:
- Call in reinforcements. Identify someone within your company who has a strong relationship with Lucy. Ask him or her to bring up the case study during the next conversation with Lucy and find out what needs to happen to move forward.
- Help out the customer. If you find out that Lucy is trying to chase down people in her organization to review the draft, offer to take over. You can become the person who persistently follows up to shepherd the draft through the review and approval process.
- Send a thank-you gift. Many organizations send a small gift as a token of their appreciation for the customer's participation. If you follow this practice, consider sending the gift before the case study review process is complete. In this way, you can tap into the powerful urge that people feel to reciprocate when someone gives them something. (You can read more about this in Robert B. Cialdini's book "Influence: The Psychology of Persuasion.") Lucy will likely be more motivated to guide the case study through to completion.
Have your case study initiatives been derailed for other reasons? Do you have other suggestions for ensuring a smooth case study process? Please share your experiences and thoughts!