2017 Journalist Mobile Analytics application -[UX/UI/Product Research]
A Mobile Analytics application for Journalists
Duration: 4 Months
Client: Google / The Irish Times
Responsibilities: Product Design, User Interface, UX Design, Branding
Project JOEY was our effort in the Google Digital News Initiative. The project has just been released to a beta group of user and it is going into it’s third round of 2 month long product cycle.
The objective of Project JOEY was to allow journalist to view realtime data of their own recent articles on the go. We wanted to Journalist to feel empowered to boost performance of an article. This was a proof of concept project, so I had four months to conceptualise, validate and design this mobile analytics tool.
Starting off the project with a common goal
Stakeholders interviews were an important first step in this project. Even though the team was small and co-located in the same building, I still needed to get team member’s ideas, worries and insights to help define the problem. We had the benefit of having an existing report dashboard tool and this helped us to understand major pain-points for journalists.
Some of the things I did at the beginning of this project were:
I Gathered business requirements by working with our Digital Editor and identified key Journalists to talk to and gather user requirements from.
I talked to various project stakeholders - analytics team members, editorial, developers and of course, journalists.
I looked at the what was currently being used in across the business, the data sources we could work with and to discover the market leaders in the area of reporter dashboards.
Early stage concepts & user flows
Once the all requirements were gathered, I began with mapping out the user journeys for the core features of the application and conceptualising various UI solutions.
Fig. 1 - Wireframe with data points
User flows diagram was useful to quickly get agreement on the steps of the login and to foresee and issues
Looking at multiple data often lead to confusion while talk. I created wireframes illustrating the various data sources and metrics so the team could refer back to after meetings(Fig 1).
Enter the‘Concept Car’
Sometimes wireframes aren’t enough. Along with user flows & wireframes I designed some early high fidelity concepts cars(Fig.2) so all stakeholders could really get a sense of how the product might look and how it could really benefit the end user. I knew from previous experience that finished designs can really help to get buy-in for a product concept when wireframes can sometimes be too abstract.
Fig 2 - Some early stage concepts that helped to build excitement for the project and get buy-in from stakeholders
I created a lot of user-flows for this project. Since we were working with quite a complicated & dynamic content, the team found it useful to have this diagrams to refer back to in meetings at any stage of the build of the product.
I designed flows for every path a user could potentially go down. Later on it was realised that'create an account' was not needed since there was an internal approval process to get access to the product.