Content Design › EE
Content designer, working with a UX designer, scrum master and product owner.
The data showed that many device updates were failing because people were submitting the same request again before processing was complete.
My hypothesis was that it was not clear enough when an update was in progress or how long it would take. The problem was urgent, but the team did not have the capacity to change the structure of the platform. We therefore focused on the interface content to prevent people from submitting the same request again.
50% fewer failed updates. After our changes, the proportion of failed updates gradually fell and stabilised at a level 50% lower than before.
I prioritised the most important information
The previous message contained a lot of information without a clear hierarchy and did not give enough prominence to processing times. I simplified the copy and reorganised the information, highlighting what people needed to decide how to proceed. I then rewrote the CTA so that the action would be clear even at a glance.
I removed ambiguity
I also rewrote the submission confirmation. The previous version, “Your service updates have been successfully submitted”, confirmed that the request had been submitted, but a quick reading could suggest that the update itself had already been completed. Removing “successfully” avoided this ambiguity.
We made updates in progress visible
An organisation’s mobile fleet may be managed by several people. Someone using the platform might therefore be unaware that a colleague had already requested an update. We designed a banner to show that updates were being processed and prompt people to check the request log before submitting new requests.
We warned users before they submitted a duplicate request
When someone requests an update that is already being processed, a more prominent message warns them again about the possible consequences. It lets them choose whether to check the request log or submit the request anyway.
We clarified what to do after an update failed
When an update failed, many users understandably submitted the request again. However, a technical issue meant that submitting a new request for an update that had already failed could cause all subsequent requests to fail too. We therefore designed a banner that flags failed updates and tells people to contact customer support before trying again.
The work resolved an urgent problem, but also revealed other difficulties with service management. CTAs for different actions were inconsistent, some names did not clearly explain the available functions, and information about the selected devices could be confusing. These observations, later confirmed by qualitative research, helped initiate a broader redesign, starting with the network features.
Content Design › EE
Content designer, working with a UX designer, scrum master and product owner.
The data showed that many device updates were failing because people were submitting the same request again before processing was complete.
My hypothesis was that it was not clear enough when an update was in progress or how long it would take. The problem was urgent, but the team did not have the capacity to change the structure of the platform. We therefore focused on the interface content to prevent people from submitting the same request again.
50% fewer failed updates. After our changes, the proportion of failed updates gradually fell and stabilised at a level 50% lower than before.
I prioritised the most important information
The previous message contained a lot of information without a clear hierarchy and did not give enough prominence to processing times. I simplified the copy and reorganised the information, highlighting what people needed to decide how to proceed. I then rewrote the CTA so that the action would be clear even at a glance.
I removed ambiguity
I also rewrote the submission confirmation. The previous version, “Your service updates have been successfully submitted”, confirmed that the request had been submitted, but a quick reading could suggest that the update itself had already been completed. Removing “successfully” avoided this ambiguity.
We made updates in progress visible
An organisation’s mobile fleet may be managed by several people. Someone using the platform might therefore be unaware that a colleague had already requested an update. We designed a banner to show that updates were being processed and prompt people to check the request log before submitting new requests.
We warned users before they submitted a duplicate request
When someone requests an update that is already being processed, a more prominent message warns them again about the possible consequences. It lets them choose whether to check the request log or submit the request anyway.
We clarified what to do after an update failed
When an update failed, many users understandably submitted the request again. However, a technical issue meant that submitting a new request for an update that had already failed could cause all subsequent requests to fail too. We therefore designed a banner that flags failed updates and tells people to contact customer support before trying again.
The work resolved an urgent problem, but also revealed other difficulties with service management. CTAs for different actions were inconsistent, some names did not clearly explain the available functions, and information about the selected devices could be confusing. These observations, later confirmed by qualitative research, helped initiate a broader redesign, starting with the network features.