Jackie and Ben have a great blog with Church of the Customer but their PODCAST is even better.
In this podcast, they were talking about how to create emotional connections with your customers/products - something that most FoxPro developers get. And in it, they spoke about a scale that was used by Gallup that was broken into four areas: rational , emotional, pride and passion.
It's an interesting exercise, especially considering the last MS FoxPro survey.
1. Rate your satisfaction with Visual FoxPro on a scale of 1 to 10.
2. How likely are you to buy/use Visual FoxPro again?
A: Depends on what the need is.
3. How much would you recommend Visual FoxPro to a colleague?
A: Depends on what the need is.
1. Is FoxPro something you can always trust - Yes or No?
2. Does FoxPro always delivers on what it promises - Yes or No?
1. Microsoft/FoxPro always treats me fairly -
2. If a problem arises, will my problem be resolved ? - Yes/No
1. Are you proud to be a FoxPro developer?
2. MS/FoxPro always treats me with respect
1. FoxPro is the perfect product for people like me. - Y/N
2. I can't imagine a world without FoxPro . - Y/N
Is this survey flawed?
Jackie and Ben do a great job of tearing apart the concept of a satisfaction survey by asking:
How do respondents define "respect", "fairly", "pride" or 'satisfaction'?
From their point, the only questions that really mean something as far as creating that emotional intent is the one that refers to recommendability.
When I tried the above survey with FoxPro as my product, the only areas where I could even come up with a complete answer (one without it depends or N/A) were the last two on the topic of passion.
Compare this with the recent Microsoft survey. After going through all of the questions in that survey , the one that still stands out in my mind was:
a) what features make you want to buy/upgrade FoxPro?
This is where Microsoft sees the product revenue. VFP 9 is chock-full of developer goodies that require the developer to grow them into a meaningful application. That's great to satisfy the developer - but eventually, the developer has to answer to the customer and the customer , unfortunately, needs the eye-candy. (see my post on Office style tools)
Sure, there were lots of other questions but that one is the key point because one needs to have some reason to recommend upgrading and recommendability is likely the biggest area where Visual FoxPro suffers, overall as a developer tool.
At this stage, readers may be going "I always recommend FoxPro" but the answer for a recommendation in development tools should almost always be "it depends on the need".
Every solution is not in need of a hammer and when someone asks for a database, the first word on everyone's lips is NOT FoxPro, it's likely MySQL or SQL Server or _____. (and if you've ever heard Jim Duffy speak, FoxPro and database simply aren't two words that should ever be used together).
And if you ask about programming languages, you'll likely get a wide variety of responses as well. You want OOP - Why not use C++ or C#?
The recommended tool should always depend on the need.
And often, I find, the FoxPro developer, although loud in the community, doesn't beat the drum loud enough in their own organization to get it recommended. Maybe it's because they're tired of always having to defend the product. It was different in the early 90s because everything was about speed, an area where FoxPro wins hands-down. Now, it's also about security, maintainability, user interface, access and design.
So then the person asking the question "what tool should I use?" asks the next best person, who would be _________.
So who is that person?
Is it an IT person? IT won't likely recommend a FoxPro solution because they can't control it.
Is it Sales? Microsoft Sales won't recommend VFP because they make more $$ from other tools but there's an implied disingenuous feel here because their job is to make money. Likewise, a retail sales person won't recommend it because, well, when was the last time you saw FoxPro in a retail store?
Is it Marketing? (see Sales)
Who do YOU think that person is?
The podcast is only 30 minutes but the section on creating the emotiional connection is in the first 15 minutes and well worth the listen.
Church of the Customer: Podcast: Can't get no satisfaction; creating emotional connections