NPS Blog

Podcast: Stoking the Entrepreneurial Spirit , with FireDisc’s Griff and Hunter Jaggard

jaggard-brothers-220x207For years, farmers in West Texas have been using the plow discs from their tractors to cook outside. After all, the metal discs resemble woks when turned sideways, making them perfect for frying bacon and eggs for a crowd or making fajitas on a camping trip.

Two brothers have parlayed that piece of Texas farm culture into an innovative tool: the FireDisc. It’s a portable propane cooking surface that has become required gear among outdoor enthusiasts. firedisc-cooker-220x207

I recently talked to cofounders Griff and Hunter Jaggard about their plans for the FireDisc and the role of customer feedback. They launched their company in 2010 and have been using Net Promoter to help guide their efforts.

You can listen to our conversation through iTunes, Stitcher or through the player below.

4 Responses to Podcast: Stoking the Entrepreneurial Spirit , with FireDisc’s Griff and Hunter Jaggard

  1. Just listened to this episode and really enjoyed it. So different from the type of thing we hear from high-tech companies. Great examples of continuous improvement, and constant listening to customers. To use a buzzword, I would call it ‘agile’ product development. Get it out there and keep listening and improving.

  2. Hey guys, great episode! My company uses NPS but I believe we are only scratching the surface of analyzing our results. Our typical survey questions include the NPS question, an open-ended comment question, open-ended suggestion question, then questions on key service areas where clients rate our consistency. My concern is, these questions seem diagnostic (what went well, what didn’t) as opposed to behavioral or predictive. I don’t think we have a clear understanding of our clients’ behavior other than satisfied or not satisfied or how that behavior varies based on Promoter or Detractor. Can you guys speak to the ideal design of an NPS survey? A mix of behavioral and diagnostic questions? Ideal question amount? Thanks!

    • Nick, there’s no “perfect” answer to this. But there is empirical evidence of a few things:

    • Shorter is better. Not only do you get better initial completion rates with fewer questions, but you also get better repeat response rates (same person responding to requests for feedback over time).
    • Simpler language is better. The more you qualify or complicate questions, the bigger the “cognitive load” you place on customers to interpret what you are asking, and the harder it becomes for them to respond. Over time, this both depresses response and reduces quality of response (fewer words per verbatim, for example).
    • Higher quality learning comes from follow-up calls than from additional questions on the initial request for feedback. As smart as we all are, it’s typically impossible to anticipate all the issues customers might encounter, and if you could, the length of the questionnaire would deter customers from responding.
    • As a result, Bain clients generally keep their requests for customer feedback very short. Likelihood to recommend, impact of the most recent episode on likelihood to recommend, why, and what could we do better. Four questions. A few of our clients add a question or two (no more than four) at the end to verify that the customer’s issue was resolved fully, or to measure specific elements of the experience that have proven to be important for shaping the outcome for customers. But they do this ONLY if they can’t find data in their own systems that would provide the answers to these questions.

  • Nick, when I see companies ask a series of questions about ‘key service areas’, a question always jumps into my head: Who says they are key areas? These lists of questions are often driven by a desire to provide scores or other feedback to each department in an organization, regardless of whether the customers feel they are key areas or not. In my experience, if a customer never mentions a particular area, you have nothing to improve, and don’t need to worry about it. Indeed, if never mentioned either as an answer to the ‘Why?’ or the ‘What could we do better?’ question, it is probably a hygiene factor, meaning something customers only notice when it goes wrong.

    I know Rob likes to use credit card approval as an example fo such a process. Nobody notices it unless it does not work. However, if you decide you absolutely must have a score for the people who handle credit card approval on your team, you will add it anyway.