Comments on: A quick lesson on how not to design your calls to action

By: Sridhar

Tue, 23 Mar 2010 13:57:06 +0000

I happened to stumble upon your website from one of the tweets from my contacts. I would like to tell you that you have got a very informative website. Or to be more precise, a thought provoking website which specializes in UI experience. I haven’t seen such a quality website on UI design until I saw your blog. Good work.

Coming to the article that you wrote. The design and user experience was really poor in the Athens museum website. Like you said, we make schoolboy errors time to time. I guess the reason for this could be lack of experience or lack of passion to create something useful. If you hire a bunch of cheap programmers and force them to finish a task, this is what you get.

Great review. Looking forward for more quality articles such as this.

]]>

By: Harry Brignull

Tue, 06 Oct 2009 13:47:44 +0000

I suppose it was a bit of a cheap shot, but I’ve yet to see a clearer example of how not to do it…

]]>

By: Rory Fitzpatrick

Tue, 06 Oct 2009 11:59:02 +0000

On the whole I think this was a bad example to pick on, it has so many issues on every aspect of design, usability, accessibility…you name it, it’s done it wrong, so to expect a decent call to action is stretching the boat a bit ;-)

For a good LOL moment, try entering a quantity more than 5 on the step 1 form :o)

]]>

By: Ted Goas

Tue, 29 Sep 2009 20:47:28 +0000

It’s nice how you made smaller preview images of these screens for your post above. While glancing at each image, it was hard to tell if there was a CTA or what the page is even for. I had to read your paragraphs for an explanation of each page.

Probably not good.

Confirmation page looked ok until I read your bit about no confirmation email… Sheesh!

]]>

By: Harry Brignull

Tue, 29 Sep 2009 20:01:52 +0000

It sends you an email with the credit card receipt info – from the payment provider – but without your museum ticket number.

]]>

By: Alex

Tue, 29 Sep 2009 20:00:17 +0000

Why the silly progressive disclosure on the ticketing page? It’s actually LESS work for them to just show the lot without JS wizardry.

Confused about the lack of email confirmation – does it actually not send one at all, despite claiming to do so?

]]>

By: Steve

Tue, 29 Sep 2009 19:40:08 +0000

Good example of form over function. They’ve tried to make it too slick and in the process damaged the ux. Would be interesting to see how users got in with this in testing (if it ever was tested).

]]>