24 Hours interaction was one day design hackathon where I picked two complex interaction problems and tried solving them for a web experience. The goal was to exercise and focus on the defining the problem, building research and then mocking up a few user journeys for the solutions. Most of the documentation below is intial sketchs and wireframes. The two problems I picked were : Image organizer and a booking platform for a circular journey ticket.
Today, anyone with a digital camera will end up with thousands of images on their computer within a short span of time. If the photos are not organized properly, it is difficult to find the needed photograph. All digital photographs have date and time information. Design a photo viewing and organizing software that solely works on date on time information available in digital photographs. The main goal was to design an image viewer and management application that could either be a desktop client, or a RIA application hosted online. Another important specification of the brief required me to design the application such that it solely works on date and time information that every digital image carries.
For this project I used a bunch of UX techniques like: Content audits , Competitor analysis, Heuristics Analysis, Mental models, Affinity diagrams. I decide to design a desktop client for the same. The main task of this project involved defining the information model of the application. I started defining the task in the following manner: Primary: 1. General application layout and navigation. 2. Layout for image sorting based on date information. 3. Layout for image sorting based on time information. Secondary: 1. Basic operation modeling. 2. Detailing the primary and secondary features. 3. Defining additional features. 4. Refining the visual components.
The task at hand was to design an application to book ‘Circular journey’ tickets offered by the Indian Railways. I have ensured that while meeting the specifications and requirements of the design brief, I have also extended the brief to incorporate more details and a rich user experience. The main goal was to design an application that users could access in order to book circular journey tickets offered by the Indian Railway. Based on this core requirement, I decided to design a module of the IRCTC website that could offer an option to book these tickets.
The project involved designing interactions and data visualizations for several aspects of the system. I broke the entire project into several smaller tasks in the following order: Primary: Understand the existing offline booking process. Understand the working, benefits and details of a circular journey. Define a set of personas and scenarios that could serve as potential users. Ultimately map the offline booking process to an online process. Secondary: Building the workflow based on scenarios. Placing real content in the design to gauge it’s usability. Building better data visualization. Improving the overall user experience and interactions. For this project I used a bunch of UX techniques like: Content audits, Competitor analysis, Heuristics Analysis, Mental models, Affinity Diagrams, Use cases & Personas
The first step involved understanding what exactly are these circular journey tickets. Having absolutely no clue of how they work, I spent a while with a travel agent who willingly explained the whole procedure to me. Once I broke down the concept of a circular journey, I quickly analyzed parts of it, like Costing factor Validity factor Distance factor I was prepared with my business requirements as well as the user requirements. At this stage I also defined low-level personas. I realized there were generally 2 kinds of users that opted for this journey. 1. Families and groups travelling on a holiday / pilgrimage. 2. International tourist wanting to complete an entire tour of India commonly refereed to as the ‘Great Indian Circular Railway Challenge’. Content audits and heuristic analysis helped me understand and categorize the features, primary operations, secondary operations, functionality and usability related components of online booking systems. This gave me insights into simple aspects like not bothering a user for personal details unless he is content with his journey selection and costing. My objective was to first, define a new information model, build a rich data visualizations and enhance the interactions. Even after laying out the design on wireframes and sketches, I iteratively improvised on each page layout to help refine its content and functionality. Key players here were, affinity diagrams that helped me sort logic, data and functionality. Apart from that mental models helped me shape a sequence diagram and define a general workflow for the system.
General rules & assumptions: