Marketing is part of the product design. The decisions on what to do and what not to do when coding or designing a feature should be a result of a marketing interrogation because you're building the product to be used in some set of ways by some set of people.
Once you stop thinking about what they actually care about, you're drifting away from a successful execution.
This is from copy to code. From price to presentation to features and flow.
It's not a nice to have or something that's tacked on, it is the soul of the product in the prospects mind - the driving force for the whole effort from the first keystroke to the last signoff from QA, your product lives or dies by your market models and theories and how focused your execution of them were.
Doing this right is the difference between Creative Zen, Apple iPod and Sandisk Sansa or FirefoxOS, Android and MeeGo.
Technical competency is a necessary ingredient but it doesn't get you there alone.
If you want to build something that doesn't bomb, you need to study marketing, significantly and heavily.
Once you stop thinking about what they actually care about, you're drifting away from a successful execution.
This is from copy to code. From price to presentation to features and flow.
It's not a nice to have or something that's tacked on, it is the soul of the product in the prospects mind - the driving force for the whole effort from the first keystroke to the last signoff from QA, your product lives or dies by your market models and theories and how focused your execution of them were.
Doing this right is the difference between Creative Zen, Apple iPod and Sandisk Sansa or FirefoxOS, Android and MeeGo.
Technical competency is a necessary ingredient but it doesn't get you there alone.
If you want to build something that doesn't bomb, you need to study marketing, significantly and heavily.