I catch your point but honestly, developers are in a better place to make those kinds of decisions. It just takes some mindset training.
When a potential customer has a problem, they go through several hoops before they have any hope of finding a solution. First, they have to recognize and identify a problem. Second, they have to motivate themselves to solve that particular problem over all others.
Once a potential customer has made those leaps, they are potentially your potential customer. That’s when the language leap comes into play. My favourite example is “I built a scraper but it turns out the market wants an automated tool to crawl their entire website and return some data.” Catch what happened there?? I built a scraper but the paying market doesn’t know what a scraper is.
If your language matches up with a potential customer’s language, there is a chance they will see you, pay attention and decide that you could solve their problem. That’s around the time when marketing campaigns will make you question Darwin but try to act surprised…:)
Once you catch that stuff, it’s easier to push back on shitty bloatware marketing feature requests. What’s the real problem here? Does that new feature solve a problem or does it just increase the chances that a potential customer will find you??
If it increases the chance a customer will find you, it might be a good feature. In my experience, it usually means you should do some tech support calls so you can figure out what words your customers use…
When a potential customer has a problem, they go through several hoops before they have any hope of finding a solution. First, they have to recognize and identify a problem. Second, they have to motivate themselves to solve that particular problem over all others.
Once a potential customer has made those leaps, they are potentially your potential customer. That’s when the language leap comes into play. My favourite example is “I built a scraper but it turns out the market wants an automated tool to crawl their entire website and return some data.” Catch what happened there?? I built a scraper but the paying market doesn’t know what a scraper is.
If your language matches up with a potential customer’s language, there is a chance they will see you, pay attention and decide that you could solve their problem. That’s around the time when marketing campaigns will make you question Darwin but try to act surprised…:)
Once you catch that stuff, it’s easier to push back on shitty bloatware marketing feature requests. What’s the real problem here? Does that new feature solve a problem or does it just increase the chances that a potential customer will find you??
If it increases the chance a customer will find you, it might be a good feature. In my experience, it usually means you should do some tech support calls so you can figure out what words your customers use…