We choose one painpoint and wrote it on a piece of paper. One member of the group started with an idea that could solve the issue at hand, summarized it on a post it note and stuck it on the paper with the pain point. The next person expanded the idea and in the same manner summarized the essence of it and stuck it on the paper. When everyone had done so we discussed how this chain of solutions and designs might come togeather and visualize what such design would look like. We also tried to keep in mind the earlier interviews and what reqierments the conceptual design would meet.
The white paper is the painpoint in focus in this blogpost
The first idea was to give commuters better information on the cause of delay and which alternative itineraries throgh the existing SL-application. After a few steps it took a different turn to screens in the subway. We made this sketch and low-fidelity prototype on paper.
Quick sketch
Jan Gulliksen mentioned on a lecture of his that he’d been involved on a project involving railways in Sweden and informed us that in most cases the driver of the train doesn’t have the information about the delay but just a signal to stop. By reducing the chain of information and let the available information at HQ, from technology already in place, be presented imideatly to the user in a familiar format to them. The red dot indicates delays and the numer is estimated time before solved. The screen also lets user easily orientate themselves where they’re on the line and which stations are coming up. This way of visualizing the railway, including delays, amplifies human cognition because it's enabling users to see patterns and easily detect anomalities.
No comments:
Post a Comment