Yet Another Pointless Tagline
Permanently Uncached header image 1

Entries Categorised as 'Product'

Calculating Amazon Kindle List Pricing

November 19th, 2010 · No Comments · Product

I am not a mathematical genius, but I can still do basic math like 2+2 and 15% of £8.99, but Amazon have seemingly turned the art of basic arithmetic into something that requires a PhD.  Surely when they ask you for the list price of a Kindle eBook you would expect them to ask you for the final price to appear on the site, and from which they can then deduct the VAT, eventual royalties and any digital delivery charges.

I must say that I have always respected Amazon.  Not for their amazing design sensibilities or incredible UI, but because their no nonsense approach to doing business on the web has frequently led to industry accepted standards in UI and Layout.  That being said, in this instance, they have really turned the simplest task into an impossible mess … Either that or I am a complete idiot … Watch it!

For those of you who are not familiar with the process of publishing your eBooks to Amazon for Kindle, here is a screen shot of the relevant part of the publishing screen:

As you can see they have neatly included a nice event to trigger the update of the anticipated royalty per eBook, but when it comes to anything else, how am I supposed to figure it out?  Indeed, if they know the list price I want, they know the size of the file and any charges they need to levy in respect of that, and they know what royalties to pay, surely they can just as easily do the math for the respective selling territories?

I have contacted Amazon, but the frustration as per usual is that any response takes days, not minutes.  Surely they can validate a price change and don’t need to review the eBook every single time!  It seems to be a bit redundant in this day and age to have to tell Amazon how to build better forms, or design for their web site, but in this case it most certainly makes sense to call bullshit on this online shopping behemoth.

Any bright sparks out there with an idea on how to calculate up the price for an £8.99 or $14.99 end point?

Tips from the Obama for America New Media Campaign

June 12th, 2010 · 1 Comment · Development, Product

Scott Thomas, Design Director for New Media and overseer of the ‘Obama for America’ election campaign web site, took time out to go over what made the campaign a success from his perspective.  What techniques, means, methods and more they used to achieve their ultimate goals.  The video available over at The 99 Percent is worth every minute of watch time.

For those less interested in watching and more interested in a summary of the 14 minute talk, Scott Thomas highlights some interesting core notions, ideas and areas, but to preface what he says and to quote the 99% website:

Scott Thomas is constantly seeking the simplest answer to complex problems.

With that said, here are the salient points of note from the lecture given by Scott Thomas:

Design Consistency

From the outset the team realised that they would need consistency of design throughout, from the digital, right through to the traditional.  Consistency was essential not just for brand awareness, but also in terms of being ‘on message’ and in providing strength to the campaign.

He doesn’t say as much but there is clear value in consistency, on many different levels, and to this end they derived processes that would help drive this need forward, defining consistency of output in terms of colour, elements, message using:

  • Mission statements … helped define everything that was being done.  They focused on an ethos of making sure every aspect of design was “clear” and “concise” and that all design should engender “hope” and “experience”.  Slogans that encapsulated these ideas were created and posted everywhere, forcing the team to think about them at all times.
  • Brand Groups .. were used to help define exactly how these mission statements were to be executed.  Consider them as mini corporate design guides, that make it easy to consistently deliver output int he same clear and structured fashion sot hat it hits the target.

Effective Triage

The reality is that when you are in a fast moving environment, and you need everything done “now” the design process will reach a bottleneck at some point.  It is therefore important to have effective triage; to be able to sort tasks on a basis of need and to be able to defer responsibility or things more readily.  Not necessarily by giving up your core design values, but but opening up access to assets for others, providing transparency and for the ability of other stakeholders to feel like they are more involved in the process.

Effective apportioning of tasks and responsibilities, as well as letting go with clearly defined rules and guides, as outlined in point one, makes it a lot easier to accomplish much higher level and more important tasks.  If you focus on the minutae, it is super simple to lose control of the bigger picture and of the more important things.

Use IT to Better Ideas

Simplicity is key to success, and information technology should be used to improve upon ideas for the sake of that simplicity.  Lots of processes are over-complicated and can be reduced down, thus enhancing their efficacy and conversation rates.  When you want to involve people, you need to lower the barriers to entry.  Open you door, let people in easily, and ask pertinent questions later by deferring the need for them.  This is a definite key to their grassroots success, with individuals being able to start cold calling fellow politicos in no less than 3-4 clicks.

During the course of the campaign they used analytics and process flows to monitor what was happening, and constantly aimed to improve the situation by reducing roadblocks.  This was an on-going process and proves that there is little point in rolling out designs and code without observing and enhancing it as you go in order to avoid diminishing returns of scale.

Bring Output In-House

Back on the old cherry of ‘consistency’, the team weren’t afraid to bring any task in-house.  Ensuring quality of output wasn’t ever up for discussion and where they had to do things internally, from design digital content or even physical objects and signs for TV appearances, they would just do so.  When much larger things are at stake than merely budget, you need to keep your eye on the ball and make what would not necessarily be business-friendly decisions.  Ultimately you need to resource your teams and processes properly to maintain the aims of your campaign.  False economies only spiral out into bigger costs later, and that is not just in terms of monetary costs.

Collaborate Successfully

Success is about collaboration.  Knowing what you can and can’t achieve and working with people that inspire and motivate you.  When working closely with a set of people you need to have confidence and a desire to drive things forward.  As soon a this is lost you loose a necessary cohesion in the high-pressure environment.  Belief and passion are real drivers and tapping into those goes a long way.  It pays to draw this ideal through every strain of what you do and maintain it from the beginning to the end of any project.  It’s easy to let it wane, but with consideration can be avoided.  Who doesn’t love to work with empowered and passionate individuals, right?

Evolve Your Ideas

Evolution of ideas is important.  If you look at the ’2 year lifecycle’ of the new media campaign there is a clear evolution of the designs and implementation.  Evolution isn’t a dirty word – even if creationists thinks so – and when the pressure is on to get work done, it allows you to design and implement, and then enhance, not just the once but again and again and again.

The evolutionary process breaks down barriers to getting work signed off and implemented, and allows you to work more readily on the fly, to hit the ground running and to keep your momentum.  It’s super easy to let road blocks of design and function get in the way of rolling out product, losing sight of the most important thing, which is to have something out there, working for you which provide implicit usage feedback and which can be worked on and improved over time.

It’s A Wrap!

So there you have it.  Some golden words, thoughts, and ideas from Scott Thomas.  All things that make so much sense, but which get lost in the maelstrom of any big project.  Oh … And a last little bit of advice? Write things down.

How To Enhance Your Website Search

June 5th, 2010 · 1 Comment · Development, Product

Today I came across an interesting blog post by Dan Zambonini entitled Museum Search: Recommendations.  In it he talks about his analysis of museum web site search data and what he learned from looking at it, both in terms of trends and in terms of determining web site form and function.

I liked the post because it reflects the fact that in using a web site, your visitors are providing you with potential data, which, if you choose to capture it, can be taken and molded into enhancements that improve the usability of a site and encouraged prolonged use or, even better,  repeat visits.

Dan makes some great points, all of which back up my own experience in working with search, and matching data whilst working at Last.fm.  You really should take the time to read his brief post, but in outline the highlights the following points:

  • Any search text entry field should readily accommodate the median length strength at least (and then some).
  • Soundex, Levenstein or other such probabilistic matching techniques should be used to help smooth over typical typos, errors and misspellings. Even a library of miss-typed words could be used to speed up searches.
  • Advanced search functionality needn’t be brought to the fore.  Open up such functionality, only as required, and certainly only in the background, as an option, given that few site visitors will use it.
  • Pre-load popular search terms to help speed up the search process for a sizable number of your site visitors.
  • Use client-side validation techniques to help streamline the search strings before submitting them to the database, taking up valuable database resource by prolonging queries.  Definitely a consideration on popular sites.

All valid points and ones which I would whole-heartedly agree with.  They underline the need to ensure for an optimal experience.  To my mind in developing search you need provide for the following:

  • Speed – Any techniques that help decrease time spent search, from web service calls to pre-loaded and popular searches improves the experience.  The long tail is great, but the reality is that 9 times out of 10 people will be searching for the same, or similar things.
  • Accuracy – Smooth over the cracks.  That is to say, use whatever means to help match typos etc. whilst at the same time, use best matches, direct hits and other means to send searchers to the desired page rather than a results page, with a possible link back to the results if the chosen result is not the one they wanted.
  • Usability – Whatever you do, provide use logic in the process, and make it easy to understand for users as well as easily readable.  Auto-fill should be split into sections as necessary, such as collection, exhibitions, etc. much like on a results page.  Simplicity is required, because people will likely make a beeline straight for the search box once they hit your site.

Even with a strong navigation, which every site should have, site visitors will use search, and you should treat it as part of the navigation of your web site.  Search isn’t just for people who are lost, it’s the clever site user’s means by which to get from A-to-B in a single click or so.

Anyhow, thanks to Dan for sharing a nice summary and info-graphic of his research of the search data.

Do You Really Need To Update…?

May 25th, 2010 · 2 Comments · Product

Whilst away on vacation I received an email from EasyDNS to say that they had updated their interface.  At first sight of this email I winced.  Why?  Not because I am a stickler for change – though no doubt some might agree – but because most of the time when there is an interface upgrade, there is no real “value added” when it comes to usability.

Any assessment and need to upgrade, update or change something should always be a value added proposition.  What’s the point really in making it no easier, or harder, even, for your userbase to go about their daily tasks, right?  So it leaves me even more mythed, when I go to login and review the new interface which seems to do nothing more than make the processes more complicated.

This is the second time in the last year that I have been faced with so-called web site upgrades, that leave me feeling nothing more than “rather meh” about the changes.  So here are a few points I think are valid in tailoring the end result of a site or service upgrade:

Implicit User Feedback

The massive opportunity in doing an “interface upgrade” is that you have existing usage data, or at least you should, if you are doing any tracking at all.  Knowing how people use your site, the process flows and such like, is a massive step in understanding how you can make their lives easier, reducing what might take 3 or 4 steps, and compressing them into one.

Usage stats, implicit in nature, are like a recommendation engine for any good UI developer.  Briefing and informing them of the next best step.  The primary question I would ask myself in the course of “upgrade” planning would be to understand what it is that users are doing, and what tools can be used to improve their processes, and no, AJAX requests and Web 2.0, are not one of them.

The real advantage of such stats at least means you are not making a complete stab in the dark when developing new functionality and layouts.  If you ever make assumptions about use cases, when you have clear data, you are only doing your company a disservice.

Explicit User Feedback

Anyone will likely tell you that any web site or service should be defined by the users.  The point about a wealth of usage stats underlines this very fact, but as clichéd as it is, so many sites and services online are designed and implemented without any regard for anything other than stakeholder’s intent (i.e. the business owners).

Obviously the larger your userbase the more fertile the ground to harvest from in terms of usage stats, but in the absence of this, the next best opportunity comes from directly questioning them.  In the early stages this means identifying those who will provide useful and coherent feedback and tapping into that, from which you can take their concerns and issues and elucidate them in terms of new features (or NOT as the case may be).

Once you have implement this round of features, the next round of testing and feedback should involve more open beta testing, not launch or soft-launch as some developers deem fit to do.  This process should bring about a final round of changes prior to a soft launch and/or further testing.  Working with your userbase the entire way through the process is a definite key to success, as I have mentioned many times before, not least as a means to circumvent negativity that can come out of sudden and unexpected changes for users.

On-going Feedback

It seems obvious, but there is money to be made in listening to your users.  Giving them the service they desire and need develops loyalty and new business. Providing support is one tool and avenue for on-going feedback, but more direct channels and requests for feedback are another means to solicit for free advise that can help improve your online offering.  You might think you know your customers inside out, but they truly do know best, even if the feedback isn’t coherent or well collated, that’s is your job, and it is to your benefit to listen.

Above and beyond this explicit feedback over a long period of time, it is worth using A-B testing and tracking to ensure that your changes are creating the desired results and are not in fact impeding users int he course of their business on your site.  This type of approach brings the view of updates full circle and provide a shining light on what can often seem like impossible to see dynamics in site use.

Making It Easier & Avoiding Pointless Changes

If your site or service has to use jargon, you are already heading down the wrong path.  Nothing says more to me that a group of developers has hijacked a good ship than if you see a pointless footer tag, proclaiming “Generated in 0.215 second(s).”  I am glad they got that one cleared up fast hahaha.

Product development and process management should be the driving forces behind changes, and these fact are underlined again and again in the points I have made.  Not sure I can make ‘said things’ any clearer, and if it isn’t an improvement it shouldn’t be introduced.  Even more so when resources and time are at a premium.

That being said, and to round things off nicely, if your are going to do nothing more than change the design and layout without improving form and function then you might as well not waste your money at all on any ‘upgrade’ to your site.  Identifying hurdles and removing them is key to your success, and this should be at the forefront of your guiding light.

Don’t forget, that providing tools that allow your users accomplish their tasks at lightning speed and seeing them use it, not least register their appreciation of that fact, is very fulfilling, and it ultimately makes the job you do a lot more fulfilling.