146 karma · joined December 21, 2008
Coordinated marketing and product launches make sense in the context of a Product Development model but cut into your ability to learn in the context of a Customer Development model. Instead of allowing your initial customers to teach you about your product, you are skipping that step and going straight to teaching the market about your product.
I propose the attribute table pattern, which I've used to decent amount of success. It's not as sexy as ff's, but it is simple, easily cached, and queried. Here's an example schema of attributes you could set against a userId.
CREATE TABLE `Attributes` (
`userId` int(11) NOT NULL,
`attributeId` int(11) NOT NULL,
`charValue` varchar(512) default NULL,
PRIMARY KEY (`userId`,`attributeId`),
) ENGINE=InnoDB;CREATE TABLE `AttributeMap` (
`attributeId` int(11) NOT NULL auto_increment,
`attributeName` varchar(64) NOT NULL,
PRIMARY KEY (`attributeId`),
KEY `attributeName` (`attributeName`)
) ENGINE=InnoDB;And, combine that with arbitrage pricing of futures and you'll see that the current price of your commodity, in this case, the Dow index, includes these future expectations in its current price.