BP – Charting tool
BP has found a drop in page views and usage in the desktop application compared to their mobile app offering of their energy charting tool. They wish to find out what is causing the drop and determine if there is a way to improve the current tool. There has also been external feedback from external senior members of the Financial Times that have openly said the tool is fiddly and tough to do a single pointed task.
Task
Objectives: 1) find user pain points and ways to improve the current tool on the desktop so that it's an easier and intuitive experience. 2) The tool should be an easy experience even for someone without domain knowledge. 3) The hope is to improve the page ranking on desktop
Product mission statement
For the varied audiences of the BP Statistical Review of World Energy who need an intuitive and trusted way in which to explore and analyse the data to gain insight into world energy markets.
The BP Stats Review energy app is a data visualisation and manipulation tool that will increase engagement with the BP Stats Review and increase BP’s reputation as a thought leader and trusted voice in the world of energy economics
Project objectives
Discovery introduction
To reviewing the front end on both the desktop and app, and making sure that it is as flexible as possible to accommodate data structure changes in the future.
A detailed look at analytics within the tool to see what is working and what isn’t and review best practice examples of complex data charting tools to improve overall user experience.
Cover
What we will cover
Summary
Why its important?
Survey
and
Proto-personas
Based on Survey Monkey research results, we realised a tagging
exercise to filter results and to improve relevant findings.
Within the findings, we created tags to describe the insights: Useful, Recent Data, Long Term, Pain Point, Average Experience, Positive, Unique Case and Feature. This way we could group them by tags, annotate in post its the most relevant insights.
These are suggestions of features to solve users pain points. We still need to test the live tool to validate if these assumptions are valid. Some features can be a new addition to the currently available journey.
User Testing
Whilst we now understand the user’s needs and objectives. We needed to explore the current working tool and what it should allow the user to achieve.
With user flows we can map out how a user could reach the goals. based on the objectives we discovered in the personas workshop. This will then help us to define blocking areas within testing.
it also helps us hypothesise what we think is the reason for not reaching the intended goal.
