Monday Reading Roundup Take #26

What I think you shouldn’t have missed last week…

Reading Our weekly roundup has been MIA for quite a while now. But we’re back with 5 great articles I stumbled across last week. I’ll make it short and sweet and as always invite you to add to the list!

A great way to learn is to find out what you should never ever do, no matter who does it and thinks it’s cool. Darren Rowse of Problogger came up with a top of the worlds’ 10 worst strategies to promote your blog.

When you send an invitation to a party, people expect to show up and join the fun. Not to first submit a form and then get a second approval to attend the party. Karen Swim perfectly explained how this situation applies to social media in general and Twitter in particular.

There are some words or phrases that we hear on a daily (or should I say hourly?) basis. We’re so used to them, that we sometime believe just hearing them is enough to know what they mean. Open source is one of those phrases. Before starting to use it and other related terms, read this list of definitions published by Seth Godin.

Readers’ attention is hard to get and even harder to mentain. We are in a rush, a little bored and sometimes lazy. So grab words, as explained by Alex Cristache of Blogsessive, are always a great way to make sure we read a piece you’ve wrote.

Bloggers are a growing force when it comes to PR and Marketing. That is why a lot of companies and agencies what them to cover their stories. But bad pitches are common, so here’s another article on how to pitch bloggers from the VallyPRBlog.

Hope you like this week’s articles! Till next week, feel free to share your own findings :)

Popularity: 11% [?]

Building Reputation: Transparency in Software Development

If there is something everyone loves about Open Source software (FLOSS) is that every issue ever discovered with it is known, there are no surprises. All incompatibilities, if discovered, are out there and anyone trying out the software knows what to expect before they begin. The main benefit of such transparency is that customers are never outraged by bugs. And let’s face it, there is no bug-free software, especially if you try to make it work on Windows :)

When it comes to closed source software, I’ve been in the industry enough to know the rule of “hush-hush” is the preferred business model. Known issues, bugs, incompatibilities? Keep them buried and hope no one finds out. The perfect plan to have everything blow in your face.

I thought a series debating all the aspects of this “hide it all under the carpet” strategy would help software vendors understand that transparency can actually be a great selling point. No customer likes to be bullshitted and asked to remove programs without any real explanation. That is why I’ve come up with a series focusing on how important respect and telling the truth are in this competitive industry and what the lack of these values can lead to. Up to now, I’ve thought of 4 parts, but things might get more complex around the way:

  1. How Much Do Sales People Know and How Much of that Do They Hide?
  2. Should the Marketers and Communicators Care about What’s Wrong With the Product?
  3. When Everything Goes Wrong, Do Support Engineers Eventually Come Clean?
  4. Software Utopia: Transparency All the Way! Any Benefits?

This is indeed a large and complicated topic, so while posting each entry of debating the subject of transparency in the software industry, I’d love to hear your thoughts, your pleasant encounters and horror stories involving tech support, sales people and marketer in the software industry.

So stay tuned, and let’s start debating!

Popularity: 14% [?]