2010-12-01, 11:29 PM
While it is always healthy for the mind to research, it is incredibly flawed for a company to expect its subscribers to do any of the work to find out what is included in an update. It costs money in the end. Some potential customers don't have the time/patience to 'wait for release'.
D-Link didn't provide a customer resource manual for its DIR 655, and it hurt its sales. It's a shame really, as the router is feature packed. The more complex a product is, the higher the necessity it is to explain it, not just hype it with vague points.
Knowing this, it's also flawed for a company to assume its customers know everything about the update to come. This is why marketing is essential. And competent marketing includes information, detailed previews, etc. The videogame industry follows a standard of release dates, information presentation, and hype generation. Patch notes should be detailed because they are a core function of informing the subscriber base what to expect.
Would anyone here buy an NX item if the description was so vague and simple that its general purpose was a mystery?
We here seek the middle ground. We don't want ultra vague PR, and we don't want the source code of the patch or the math work behind every single formula. To argue for/against either extreme is flawed, and no one here is going to bite the bait. Something a little more robust than the 4th job update preview would work wonders, as opposed to more parroting of PR from Sep/Oct.
Quest text is important. It's hard to keep the rhythm of a good story when it's filled with typos and grammar issues. It is just as annoying and distracting as the typos/fail grammar in response to pseudo points in a post. Saying ''let it go'' is a thinly veiled form of being a corporate apologist with low expectations. It's not hard to do a spell check.
tl;dr: [video=youtube;8AyVh1_vWYQ]http://www.youtube.com/watch?v=8AyVh1_vWYQ[/video]
D-Link didn't provide a customer resource manual for its DIR 655, and it hurt its sales. It's a shame really, as the router is feature packed. The more complex a product is, the higher the necessity it is to explain it, not just hype it with vague points.
Knowing this, it's also flawed for a company to assume its customers know everything about the update to come. This is why marketing is essential. And competent marketing includes information, detailed previews, etc. The videogame industry follows a standard of release dates, information presentation, and hype generation. Patch notes should be detailed because they are a core function of informing the subscriber base what to expect.
Would anyone here buy an NX item if the description was so vague and simple that its general purpose was a mystery?
We here seek the middle ground. We don't want ultra vague PR, and we don't want the source code of the patch or the math work behind every single formula. To argue for/against either extreme is flawed, and no one here is going to bite the bait. Something a little more robust than the 4th job update preview would work wonders, as opposed to more parroting of PR from Sep/Oct.
Quest text is important. It's hard to keep the rhythm of a good story when it's filled with typos and grammar issues. It is just as annoying and distracting as the typos/fail grammar in response to pseudo points in a post. Saying ''let it go'' is a thinly veiled form of being a corporate apologist with low expectations. It's not hard to do a spell check.
tl;dr: [video=youtube;8AyVh1_vWYQ]http://www.youtube.com/watch?v=8AyVh1_vWYQ[/video]