Written by on Wednesday, December 19th, 2007 in Technology, Blogging, PayPerPost, ppp, izea, SocialSpark, agile development, blog, social spark.
A little while back Ted asked the PayPerPost community if their blog sucks? I actually avoided saying much at the time. However, I think that it’s pretty clear what’s happened to the PPP blog. They stopped announcing almost anything!
There has been months and months of marketing hype over Argus which turned out to be Izea and SocialSpark. That’s the best way to kill a corporate blog. Spend months and months and making only superficial changes and not announce anything that significant.
When PayPerPost first launched the blog was hoping with new features and exciting announcements. In fact, I seem to remember someone even sarcastically complaining that it had gone 3 days since a major announcement. It was really exciting to be apart of a dynamic organization that was changing weekly.
It amazes me that this all occurred almost a year and a half ago. Well, times have changed. PayPerPost has an incredibly large community and too many employees to keep track of them all. No more videos of stressed out employees getting vitamin water. No more $10 million funding announcements. However, most significantly very few feature releases in MONTHS!!
The worst part of it all is that the Argus announcement at PostieCon was a big disappointment. Not because the changes weren’t good. The quick information that was given at Postie Con has potential. However, no one would ever know it, because nothing has been released. No one has access to argus Social Spark. The PPP community was left waiting for months for the holy grail they called Argus only to receive a rushed announcement and now over a month of waiting (and no end in sight) for the actual release.
I’m sure that someone will come and say that the release of Social Spark was delayed because of the release of RealRank. This argument misses my point that PayPerPost has released very few interesting features in months.
This isn’t to say that PayPerPost isn’t thriving and that it isn’t going to be huge. I’m just saying that’s why the PayPerPost blog sucks and has definitely affected the community around it. It may have been the best corporate decision for PayPerPost to take these months and rebuild PayPerPost from the ground up. However, I think you could make a good argument about why it would have been better for PayPerPost to release features early and often. Wordpress learned this lesson which they took from Ubuntu.
I think it’s also worth mentioning Christopher Herot’s recent post explaining how he wasted much of his now failed startups time discussing and implementing features that users didn’t care about. Sure makes a compelling argument for an agile development environment with frequent releases of features. I guess we’ll see if the months of rebuilding PayPerPost and adding new features suffers the same unneeded feature fate that Christopher Herot experienced.
I hope this post isn’t seen as complaining. PayPerPost is welcome to do whatever they want with their product. I couldn’t care much either way. Although, I do appreciate them offering me a front row seat as I watch and learn from their experience building their company.
