Archive for May, 2009

Don’t Kill Your RSS Reader! Add To It

Crime Scene TapeFarhad Manjoo wrote an interesting blog post on Slate Magazine on Friday (thanks to @johnmjones on Twitter for pointing it out). In it he describes a classic case of Blog Overload. He describes his joy at discovering RSS and Feed Readers. And his frustration at the eventual overload from too many feeds that he can’t keep up with. Then he describes his radical solution: quit his RSS reader and go back to manually checking for updates on a regular schedule in his web browser.

Nooooooooooooo!

So close yet so far. Farhad is in pain. That I understand. But to try and solve the pain all he could do as to cut off the use of his only tool. Talk about cutting off your nose to spite your face.

Then the conversation erupted. Other folks started to chime in.

On Slate’s forums, the usual suggestions were made for things like filters by people like Horatio Nelson. Over at Mashable, Ben Parr joined in to ask the musical question “Do You Use an RSS Reader?” And his informal poll currently has 72% of his readers who use one “all the time”. Just after that, Steven Cahill wrote a blog post proclaiming that “RSS is Not Dead“. His conclusion, “Give me RSS any day.”

Once again I see the same need to combat Blog RSS Overload. And, I see the same frustrations and proposals. When people ask why we created Bscopes, this is exactly what drove us.

But, I don’t want to just go on and on summarizing this problem. I want to try and point out to Farhad, Ben, Steven and all the others suffering out there that we think we can help. Not to replace your trusty RSS feed reader, but to supplement it.

In Farhad’s original Slate Magazine post, there was this plea:

Moreover, I hated the software’s bland interface; when you read blogs through RSS, you’re only getting text, not design, so every blog looks like every other blog. But I didn’t want Gawker to look like the New Republic; I needed a visual difference, in the same way that I want the National Enquirer to look distinct from the New York Times.

That is the essence of the Bscopes approach. A picture, not more text. A visualization, not simply filtering.

For example, here is a Bspace (a picture of multiple blogs) that I added based on Farhad’s initial post.

Bspace of multiple blogs related to Farhad Manjoo

Rather than get overloaded and then just hit “mark all read”, try picturing a slice of the blogosphere using Bscopes. Check out one blog. Or a group of blogs related by a tag. Or even a Bspace of all the blogs you read.

Use Bscopes to give you an overview of what is happening. You can check out the relationships at any given minute betweeen blogs. Or, over time, look for changing weather patterns in the blogosphere (a la Christophe).

But the key thing is to not give up. Don’t kill your feed reader. After all, a mime (type=”application/rss+xml”) is a terrible thing to waste.

Post Footer automatically generated by Add Post Footer Plugin for wordpress.

Share:
  • TwitThis
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Live
  • LinkedIn
  • MySpace
  • Reddit
  • SphereIt
  • Slashdot
  • StumbleUpon
  • Technorati
If you enjoyed this post, then make sure you subscribe to the Bscopes RSS Feed.

Continuous Feature Release — Business at the Speed of the Internet

Escher's Drawing HandsWe have been thinking about how we’ve structured things here at Bscopes. Several recent exchanges with bloggers like April Dunford and Seth Godin have been helping us to articulate our philosophy of product creation.

Our Fundamental Business Rule

For a Web 2.0 startup, IONSHO, the fundamental thing is to be prepared to move at the speed of the Internet. No matter what your size. It’s not like dog years, it’s worse. This is a direct contrast to how we spent 25 or 30 years in the product and services industry. 18 – 24 month product cycles were common there. On the web, people talk about 60 or 90 day cycles. We disagree. We say that a continuous approach to product development is required. Product creation both drives and is driven by the business needs and goals. Our new name proposal: The Escher Business Product Model. Let’s be clear here, if you are Microsoft or Oracle, then you do what you want. When you are two guys in your garage you are much more constrained. This model is based on that situation and those constraints. If you already have VC funding, you can stop reading now.

Constraints Of Small Companies (Two Guys in a Garage)

Many people view the lack of resources as a hindrance, we see it as an advantage.  Things that used to cost a lot of money and take a lot of time and expertise are now able to be obtained for a few dollars a month with just a few clicks of the mouse. The services available on the Internet provide enough leverage to enable an entire company be built and launched in a few days. And then continuously evolved over nights and weekends. There were two books that helped to reinforce this Escher Business Product Model.  Seth Godin’s Purple Cow and Guy Kawasaki’s The Art of the Start. Both provided vision and helped us formulate our ideas. We had a product idea and Purple Cow helped us understand that such a unique idea could be successful and was an advantage. Guy’s book reinforced our notion that two guys could bootstrap the entire operation. This approach came with constraints:

  • Reach Exceeds Grasp: We couldn’t build even a fraction of our vision for Bscopes up front
  • No Users: We couldn’t spend months building hype with some secret “invitation only” private beta test period
  • Can’t Wait: We couldn’t wait two years to release version 2.0 — improvements would have to come quickly and continuously
  • No Revenue: We couldn’t wait until the site was “done” to provide enough value to attract a user base

This brought us to the understanding that we had to have a continuous development and release model to turn our constraints into advantages.

Build a little. Build a lot.

Bscopes couldn’t afford to be wrong in a big way. But we could afford to be wrong in a small way. And wrong a lot of times. As long as we learned and grew. We have a vision of what we want. One key to turning these business constraints into product advantages is to ensure that we bound all feature investments.  This means breaking our big ideas into small pieces. Incrementally building and releasing them. And then, getting feedback on them ASAP. This is not possible when it takes 18-24 months to go from v1.0 to v2.0.

You Can’t Always Drink Your Own Bathwater

From the Tuned In guys and the product management blog of Steve Johnson, we developed a better understanding of where we were right and where we were wrong. And, more importantly, that sometimes it is not relevant if we are right or wrong: “Your opinion, while interesting, is irrelevant”. This became our mantra and we use it to beat each other up on a regular basis. Part of the juggling act in Escher Business Product Model is to provide the user with enough capabilities so that they can use the product and give feedback, while not over-investing time in the development of any feature. The feature might be rejected, so keep sunk costs small. The key to doing this is to break everything that needs user feedback into mini-functionality releases. It’s like Einstein said, “Make everything as simple as possible, but no simpler.” It’s a continuous effort to maintain the discipline of breaking multi-month cycles into week or two features. And to make sure that week or two long features are supplemented by a number of even smaller tweaks, improvements, and bug fixes. An hour here improving the clarity of one window based on feedback from Twitter. An hour there clarifying the structure of the Bscope graph based on email responses. Continuous small investments, continuously released, yield big results for the users.

Rules For Small Startups

  1. Develop and release continuously: Don’t go a week without some changes.
  2. Keep time investments small: Be prepared to abandon ideas that don’t work.
  3. Get some feedback: Release to the community and listen to what they think.

This is our approach to Web 2.0 development. We are very interested in your approaches or thoughts on our Escher based approach. Please leave some comments below.

Post Footer automatically generated by Add Post Footer Plugin for wordpress.

Share:
  • TwitThis
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Live
  • LinkedIn
  • MySpace
  • Reddit
  • SphereIt
  • Slashdot
  • StumbleUpon
  • Technorati
If you enjoyed this post, then make sure you subscribe to the Bscopes RSS Feed.

Yet Another Successful Presentation [YASP]

Steve and Brad ready to presentA big thank you goes to Lewis Berman and the folks out at Loyolla College computer science department for having us speak at their first Advanced Technology Forum on Tuesday night.

There was a great crowd who was full of interesting questions and suggestions. They gave us some much needed praise and feedback on Bscopes. It is fun to get to have a real-time dialogue to exchange concepts and ideas.

Next time, though, Steve is considering wearning his high heels too!

Everyone in the Baltimore-DC area should keep an eye out for their next Forum. Their newletter is at www.loyola.edu/loyolacomputes. They are building a great new Software Engineering Graduate program. We are looking forward to participating again in the future.

Also, a big shout out to “He who must not be named” (who last appeared on Bscopes a year ago in this post) for making a special guest appearance in the audience. We’ll be watching for him this summer at a nearby theater.

Post Footer automatically generated by Add Post Footer Plugin for wordpress.

Share:
  • TwitThis
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Live
  • LinkedIn
  • MySpace
  • Reddit
  • SphereIt
  • Slashdot
  • StumbleUpon
  • Technorati
If you enjoyed this post, then make sure you subscribe to the Bscopes RSS Feed.