3 ms·
You need to be extremely good at marketing (or at least, have a whole lot of it) to overcome a significant technical disadvantage. I mean, it can be done, but
by lsc 17y ago
You need to be extremely good at marketing (or at least, have a whole lot of it) to overcome a significant technical disadvantage. I mean, it can be done, but it takes a lot of marketing muscle.
I think most people are better served by focusing on what they are good at. Sure, your company will always have to do some marketing, if nothing else, you need to somehow let your users know 'hey, product X exists. it does Y."
You will also have to create a product of some sort.
if you have more marketing muscle, then sure, squeeze out some fetid failure of a product that crashes every other day, and that requires a re-install every 6 months. market the heck out of it, and you can win.
but you know? without a huge amount of marketing muscle, that won't work.
If you don't have much by way of marketing skills, produce a good product. Sure, you still have to market it, but marketing it becomes much easier, because once one person sees it, she is going to tell five others how great it is.
so yeah, marketing and technical competence are substitutable to a degree. I disagree strongly with the thesis that one is way more important than the other.
To take an example from the article, sure, fogbuz is beating out other bug trackers that are about as good, that don't have good marketing. If fogbuz was not about as good as those other bug trackers, though, significantly more marketing muscle would have been required.
I think why marketing seems more important at the top end of the market (that is, it's easy to name examples of technical superiority being trumped by marketing) is that it is easier to scale marketing, if you are a large company, than to scale technical competence.
Even then, it makes sense to do a cost/benefit and say 'if we diverted x percent of the marketing dollars to dev, how much more good word of mouth would we get?' or 'if we divert x dollars from development to marketing, how many brand new customers in new markets would we get?'
This is ignoring that 'figure out what the user wants' is generally considered part of marketing, and is often an important part of building something worth having. (it doesn't need to be... you can start with 'what would be best for the user' - assuming that you can design something the user can not imagine, that the user would like once they see it because it works better. Both are valid places to start building a product.)