UI Design

M2030 - motivating data entry of emission savings (B2B)

Improving UX/UI of reduction plans

Enhancing the features of the reduction plan and project details: showing how Suppliers are actioning out their carbon emission reductions

Responsibilities: UX/UI design, UX research, data analysis
Length: 4 months
Team: HoP, DataOps, PMs, Customer Support, Engs.
Year: 2023

HMW improve understanding and engagement in emissions reduction projects and plans

The main project of my time at M2030 was to improve engagement and usability of the reduction plan features. I started with discovery work, to answer the main questions relating to: what makes a quality reduction plan and why do Suppliers not evidence them on the platform?

The goals of the work

Discovery

Focusing on the first problem of Suppliers calculating and inputting environmental savings: these could be calculated as an estimate or an actual, prior to and/or during its actioning.

The platform allowed for estimated or actual savings, in units only. Yet emission reduction targets were usually expressed in a %: absolute or by intensity. With the PM, we came up with the hypothesis of: could Suppliers be encouraged to input savings if the platform allowed %s that mirrored their targets.

Above, the data indicates that there is uncertainty at shortlisting an action of its actual impact. Therefore, any visibility of the Suppliers is reduced by not inputting any estimated savings data, or even the act of going ahead with a reduction action.

I analysed the current paths and %s of users that were shortlisting an action from viewing it once opening it up in a new tab.

I looked at how many users, within 6 months, then entered savings data within an adopted/shortlisted action.

I also looked at the the comparison data between viewing the action library, to viewing an action, to adopting an action.

Although the action library obtained a lot of figures of viewing, there was a distinct drop in the event of viewing any further details. This may have been down to lack of time, lack of relevance or something else. However, viewing an action to adopting it had a stronger correlated relationship.

I explored further with the task of Five Whys, to better explain the problems to see how different teams could address the multi-factor problem of the Product ask and SCO-need.

For each idea within this work initiative, I created a diagram for each of the ideas, to showcase the processes I intended to design. Above is the diagram for importing an .xls reduction plan file, along with the prototype designs. This piece of work did reach development, but was descoped to reach MVP status.

Development

Before
Design 1
Design 2

Below are some other variations, including user selection to showcase progressive disclosure of energy text fields.

Prototype 1 - rework of layout of action details to make savings more prominent

Adding savings within the current layout

All Recent Work