Contact T: 01138187800 Email, Twitter or Quick Index

Connected-uk.com

All posts tagged KISS

It’s well known that simple-to-use site work better than complex one but that’s not what I’m talking about here. I want to cover briefly the major components of a web-site and specifically where and how they should be developed. Many web-sites re-invent the wheel (for example a site search function?) costing in development resource and also in lack of function. Taking the example of site search, would it not be easier and better to provide Google’s site search on your site rather than pay for a development company to develop a custom search function?

Well, there are pros and cons for each approach so I thought I’d explore some of the major functions expected on a site and see which ones are, on balance, seriously worth considering but before I start this I thought I take a generic look at the advantages and problems or using third-party widgets on your site.

Advantages

  • Best of breed is possible here, you can potentially have a widget that’s had thousands or even millions of man-days of development. That has got to be attractive
  • Many of these widgets are hosted on the cloud, provided as SaaS maybe, reducing the load on your own hosting / server / communications infrastructure
  • The cost model for most widgets it based around either low-cost license or medium-cost capex. Very rarely do you see an expensive capex widget
  • Changing widgets can be pretty simple, allowing you to move with the times and adopt the latest, greatest, newest thing out there
  • Using industry-standard widgets (Google search, Facebook Like) means visitors do not require a learning curve
  • Ongoing improvements by the suppliers can usually be incorporated
  • Browser and platform support is carried out by a third-party, reducing costs, overhead and (usually) lead-time
  • Some widgets have APIs to allow add-on development
  • Ease of adding new gadgets and widgets can quickly create a more interactive environment

Disadvantages

  • Can be difficult to bespoke build some items, risk of shoe-horning the business needs into the widget and not the other way round
  • Costs can mount up for simple license terms over time, especially if the widget has a poor RoI
  • Managing lots of suppliers for different elements requires good project and cost management
  • Suppliers come and go quicker, they stop developing a widget, or get bought, or go bust so you need succession planning
  • Ownership of data can be a little blurred generating possible privacy and regulatory issues
  • Easier for your competition to “copy” you be installing the same widgets
  • Harder to differentiate your offering if you use standard tools
  • Dependent on the uptime of the third-party providers (only recently Amazon EC3 servers went down and currently Sony’s Playstation Network is down!)
  • Ease of adding new gadgets and widgets can quickly create a more dis-jointed environment

Overall it is worth considering a mix of approaches, some standard functions are actually better served as widgets (site search is a good example) but where the web-site is reflecting or providing key functions that differentiate you from the competition is is probably better to stick to bespoke and custom-built applications. By way of example; a good search engine is expected on most sites but is very rarely critical to it’s success (unless you are a search engine).

Before we dig into the actual widgets (part 2) it’s worth considering the Free vs Paid vs Freemium model for widgets. Obviously, a free service has the benefits of costing nothing to run but usually has the downsides of your videos being used as a revenue generation method via adverts, interstitials, sponsored links etc. Paid is a better option as that usually entails some service level agreement and sometimes the ability to “white-label” the widget. Freemium sits half-way in between and has seen its’ historical credibility waver a little recently but a great way to try something for free and then upgrade to the paid-version if it works for you. However, if the fully-paid-up version is only £50 a month then you’d be nuts to go for the free version if it costs only £50 to try out the real, industrial-strength, version.

(…contd)


Competition, competition, competition.

I think I have been naughty. I have completed the creation of the Big.TOE spec ready for formal sign-off… and I did it before looking in detail at the competition. Hmm, naughty indeed.

“But, but, but, I was really busy and everything was…” SHUT UP! Leave the excuses and move on. As it turns out we’re safe, and this is due to Big.TOEs collaborative element. Big.TOE had been guided by colleagues into a niche that not only exists, but suits our ethics here at Connected.

Phew, thanks guys!

So I spent a day looking at the competition in detail, and then sighed with relief. They are all so complicated. Even the free stuff. You’ve got to spend hours of annoying time-waste to get the answer to the simple question “How well are banners doing?”. And when you get the answer you’re surrounded by an infinite number of ways to see it. Very very naff and annoying.

Another ‘sigh-of-relief-inducer’ is that they nearly all use third-party cookies which a visitor can opt out of. Woah. What a way to undermine your reporting. Cue shameless Big.TOE plug:

  • Big.TOE is server side reporting, so no third-party cookies.
  • Big.TOE follows the principle of KISS (Keep It Simple Stupid) and will be bloody easy to use!!

So bring on the competition!

—-

This week we also delved a layer deeper into the inner workings of Big.TOE and gulped again.

Actually it doesn’t look too bad. We have a list of features for the first release and a technical plan (first draft) of how it will be achieved. There is some stuff to learn (like xml and excel) but it should piece together fine. The eye opener is how much bigger things look when you go deeper, it really is like descending from 30,000 ft.

—-

Well, now I have just gone and changed everything.

We – almost all of the company techs – were unanimously decided to base Big.TOE on XML. XML was to be the glue to stitch the different parts together. But now I have found something called Highcharts, which is just luuurvely. Its a 100% JavaScript graph building suite… and its luuurvely.

Highcharts is very attractive for many reasons; here are the main ones:

A example highcharts graph

An example HighCharts Graph

  • The graphs are just ace. The graphs are really really really ace!
  • Its on the front end, offering tasty interaction between the graphs and the clients
  • Very flexible with the data sent to them.
  • Its JavaScript, giving opportunity to develop it, or tweak it.
  • The graphs are just ace.

It can work with xml, but it doesn’t off the shelf. Now I want to use this, cos I like it. So I just have to persuade everyone else to agree to its loveliness. We can keep xml – if we still want it – for later upgrades. Trust me ;-)

Enhanced by Zemanta

Probably the most frequent question we are asked is “how can I make my call-to-action web form convert better?”. Here’s a quickie, 10 minute read to get you started.

There’s not much we don’t know about web forms.

We’ve been designing forms on web sites since 1996 and were one of the first companies in the UK to utilise the form as the engine of the site in 1999. Since that time our approach has been widely adopted, copied and used as examples of best practice by some of the leading minds in this field.

Form best practices

Start by clearly defining the purpose of the form, many of these aims are pretty diverse to make sure you set a clear and SMART objective for each and every form. You are allowed to have a secondary objective but you must take care the ensure that the secondary objective a) doesn’t confuse or distract the visitor from the first objective and b) has it’s value clearly understood compared to the first to avoid selective reporting. Ensure your testing method would stand clinical scrutiny.

Secondly, you should set a performance target for the form, a fill or completion rate. This sets a bar by which you can measure it’s current and future performance

Thirdly, the form must be designed with the visitor/user in mind. You need to protect yourself from HiPPOs, at all costs.

Once you have agreed the objectives, targets and approach you can set about designing the form.

Keep in mind the following golden rules:

1. Short forms rock! It is well documented that visitors dislike long or complicated forms. Keep it short and simple and be wary asking for information that visitors might feel is either sensitive or intrusive.

2. Label the form clearly. Each input field requires the visitor to click the box and fill in details so make sure it is 100% clear what you are asking and use helper buttons, mouseovers and text to guide them through the input procedure. You must clearly mark a field as mandatory if required and it’s worth explaining why it is mandatory.

3. The layout of the form should dictate the design and that should be a naturally readable as possible and, if the form is a significant call-to-action, should stand out against the background of the page through the use of colour, reverse, font or size.

4. A large percentage of forms are filled-in incorrectly so you should always adopt a soft-error approach to dealing with errors. Soft-error management can double the fill rate of the form and needs careful consideration. Not all errors are equal; the visitor may have missed a mandatory field or typed an invalid email address or illegal telephone number / postcode. Each type of error needs dealing with uniquely and sympathetically – a massive great red box saying “Error, please fill the form in properly” is not very useful!

5. Always be testing. No matter how brilliant your first attempt at the form is you can always improve so go back and continually test every form you have – ideally you should be continually trying to improve key calls-to-action. Without continual testing you won’t get continual improvement and it’s an easy win. Be careful with your testing mechanisms, if you are using a third-party hosted service such as Google Analytics then you might find the result increasingly unreliable as privacy opt-ins become mandatory. Consider using a server-side, in-house, solution if possible.

6. Watch out for privacy. It’s fast becoming a hot topic so you should take care to have a simple and clear privacy policy that doesn’t detract from the form fill. As part of this you need to consider what tools you are using to track visitors; there is a strong movement in the US and mainland Europe to make most third-party reporting systems (such as Google Analytics) an option for visitors with the default position of “opted out”.

Magic stuff

There are a few great tricks, some of which I am sure you are using but it’s worth listing the standard list of winners/losers and red-herrings.

1. Lightweight wins, every time. The heavier the logical page is the worse it will convert – try to get you form-based pages under 50k in size but certainly no heavier than 150k.

2. Red buttons do work. Use them.

3. Always make the button text the nature of the call to action, never “submit”. Never put a “reset” button on the form.

4. Need lots of information? Break the forms down into multiple stages.

5. Pre-fill the forms; always remember what a visitor types into a form, never make them re-enter information they have already given you.

6. Make sure the “Thanks page” has further Calls-to-action on it and where possible send the visitor an email thanking them for their time and explain what happens next at the same time giving them further things to do via additional links.

7. Never ask “where did you hear about us”, you should be able to work this o

8. If you are going to validate form fields make sure you get it right and are not over-fussy with spaces, commas, capitals and numbers etc.

9. Spend some time understanding Choice Architecture to permit gentle coaxing of visitors in the right direction.

10. Remember the mobile world. Smartphone/iPads/tablets are becoming commonplace and these typically have very different input methods that can make traditional forms difficult to complete. As part of this…never use flash.

Finally, small improvements compounded over a period of time make for big improvements in conversion rates with little risk and low cost. Alternatively – huge changes tested continually will, if monitored properly,  generate quicker improvements and a huge pile of discarded ideas; but might be more expensive. Why not mix and match, going after small changes continually and then every now and again chucking in an odd on…why not try single box multiple entry?

Enhanced by Zemanta

I do hope not but sometimes we do slip into bullshit-speak (or wanky-baby talk as I like to call it). So spare us 5 minutes of your time and tell us which pages are good and which pages are crappy. Some pages too long? Too unreadable? Too serious? Too flippant?

Best comments and suggestions before we break-up for Christmas will win a funky iPod Touch. Go on, 5 minutes to try and win an iPod. Anyone can enter except me (Martin Dower) and my decision is final. No doubt I’ll find out in due course that this offer/competition, somehow, breaches 24 laws.

Please add your comments and suggestions in the comment box at the foot of each page. Enjoy.