Design Problem

Whilst creating a design solution for a document update manager for Fidelity, I struggled to find a design pattern that would satisfy the need to select a large list from a larger default list. A shopping cart mechanism doesn’t manage large list very well and when you try to introduce overflow management techniques such as pagination it starts to break. The multi select box shown above was the right pattern apart from it is very inefficient in its use of space. So what to do.

Design Solution

I opted for a tab solution that shared the same list management/ overflow mechanisms and selection space as the default view.

Because the selection is hidden behind a default tab, the trick to making this work was to create a direct visual association with the selection method by feeding it back as obviously as possible.

Design problem

Shown above (top row) is a typical email validation and sign in process within which a user is asked to initially create and then enter a password (both points highlighted in pink). The user is forced to consider a password when perhaps they weren’t expecting to and the presense of a password input field on the first screen may put users off registering, hence reducing conversion rates.

Design solution

The bottom row shows the same screens with the create password input taken out of the initial registration step and deffering the create password task until the sign in stage, creating a simpler, less intimidating initial register view and removing the need to input a password twice.

Just started a a web project and this is the start of the card sorting.

And deciding the content types.

Here, I’m experimenting with an infinate Carousel freely available on the web. By repeating the carousel several times, marking up the html and using some precise css we end up with something which begins to look like a product configurator that is essentially just several unordered lists. See the demo here

Whilst using google’s analytical tools for this website, I realised that the view and format of graphs could be used to present the frequency and regularity of incoming emails. This would be especially useful for support services, who would find the presentation of spikes depicting a surge in incoming emails to be an efficiency tool.

The Image below show the initial view of the dashboard, one of the hours is highlighted after focusing the cursor on the graph area as shown below.

Selecting the pointer on the graph line expands a tool tip which reveals a scrollable list of email summaries.

The selected can be fine tuned down to a per/minute