Software runs my life

Year: 2009 Page 14 of 16

Features vs Usability

Just one more feature...

Just one more feature...

Does adding features automatically mean reduced usability?

Some bloggers strongly disagree with this sentiment, for example arguing features only reduce usability when they are implemented poorly. I would definitely agree with some of his examples, including adding PNG support to browsers which did not affect end user usability.

Another that he gave was Google search, which is a perfect example of an interface that is simple to the nth degree. Clearly Microsoft didn’t learn anything when they tried to compete with it by adding 3 sliders to “tune” your search results. Instead Google addresses this need for additional tuning into it’s back end, which by many counts analyses and balances 10’s if not 100’s of contributing factors. There is a load or cost in adding features, however it can be paid either by your users in your software, or internally through process and/or business analysis. This is a balance however, and factors like scalability, audience and resources all have to be assessed before a solution can be scoped.

So how can you tell if you got this balance right? Usability can be tested independently with a sample pool of your audience, and this doubles as a great way to involve your customer and evangelise them. It does get expensive however, mainly due to the time and specialist software packages required (such as TechSmith Morae). A quicker and cheaper method is to just ask someone who knows, a usability expert.

There is a great article on usabilitynews.com comparing the two types of usability feedback. If it is your first attempt at usability testing (or it requires a full time resource to manage) than an expert is a great way to learn the process and common techniques. The bottom line however, is that there is no substitute for the horse’s mouth. Customer comments and videos provide concrete suggestions that will help to mitigate any external or internal stakeholder objections both pre and post deployment.

Email Marketing Problems Explained

Email Delivery FlowchartEmail marketing is not just spam, it is an important way of updating and maintaining a relationship with your customers. For many however it is a black art (literally) plagued by blacklists and emails disappearing into black holes. The various explanations for failed email delivery however are often highly technical and involve trial and error to resolve rather than guaranteed solutions.

The first resource that I created is a 1 page document to explain the problem areas in the email delivery process. It is simply entitled Email Delivery Explained (click to download the PDF). It is by no means comprehensive, but it is instead targetted at first time email marketers and budding e-sales people trying to understand the world of email marketing. If you found it interesting and want to know more, or want a great email marketing provider, then check out the MailChimp Resources page.

The second resource is a very cool program called Litmus. This software validates your email marketing collateral against the various email clients (desktop clients such as Outlook and Lotus, as well as web based clients like Hotmail and Gmail). It will provide a visual image of exactly what went wrong and where, so you can keep tweaking until it looks right. Not only will it improve your email marketing presentation, it will also check the content against spam filters like Norton, SpamAssassin and many others. You really can’t be much more thorough than that!

Pipe goes International

I have mentioned Pipe Networks before, more specifically their “Project Runway” surviving a near death credit crunch experience. There have been two interesting developments since that time.

Guam Beach Cable Hole

Guam Beach Cable Hole

The first is that Pipe have put up a blog tracking the progress of the cable installation. You can view it at pipeinternational.com. As with their DC3 data centre blog they have uploaded a ton of photos and commentary on a very regular basis. I am sure customers, creditors and other participants in the Australian networking industry appreciate the transparency of information delivered through these blogs. It is fascinating to see that, in the end, the data is flowing through a rather unglamorous combination of copper, concrete, seawater and sand. It is also great to see a company recognise the power of blogs as PR delivery mechanisms. I am sure they raise the public profile of the company significantly.

Also on the PR front the Pipe Networks CEO, Bevan Slattery, participated in an interview with Business Spectator’s Isabelle Oderberg. This interesting interview starts off with a glimpse at how close the project came to collapsing, and concludes with some comments regarding the NBN process and goals. I do agree that the Government is tackling the problem from the wrong end, they should be starting at the core and moving outwards. I guess it is easier to present end solutions to the common voter, you can’t deliver bit size statistics like 50% more bandwidth will mean 50% wholesale price cuts which will mean 50% consumer broadband saving.

Maybe the same is also true for the NBN tenderers? If the tender was only for backhaul, could they be guaranteed enough customers to viably support duplicating the infrastructure? Do they need retail customers and the bundling of products to put together a firm business case and profit margin? Again the big question is, if this rollout is viable then why has no-one done it already? At the end of the day the problem always lies with Telstra, they simply own everything that matters. Scarily, this monopoly is now extending into the wireless spectrum. Backhaul competition is a great first stage, and perhaps with the current financial state the tender process should be limited to that for now. But there should always be a second stage planned, one that makes the whole end to end process competitive. Until that happens we will be facing different versions of the current monopoly.

Personally I believe that Telstra should be seperated and that the core infrastructure (backhaul, exchange buildings and ducts) should never have left the public’s hands. There is enough infrastructure around, it is just being crippled to maximise profit and prevent competition. Now we are either going to have to buy them back or build around it, either way this is not an efficient or cheap process.

Page 14 of 16

Powered by WordPress & Theme by Anders Norén