Case study

UX Copywriting for MPB

Overhaul the copy for MPB's Customer-facing platform. This large task involved Chief-level stakeholders across different departments. I used Notion to build a sitemap of the platform, familiarising myself with the various flows and make copy improvements based on UX Copywriting best practices.
Back to Projects

Overview

Prior to MPB launching its 5 year long rebuild of the platform, I performed this extensive review to bring congruency and UX Copywriting best practices to the platform.

UX Copy and Ev

UX Copywriting that started off as somewhat of a side-interest of mine that I self-developed through online research and local content creation conferences I was going to. Having worked alongside some genius copywriters, I know content is king. In conjunction with design, it builds mental models in the mind to help make new concepts and interfaces more intuitive.

How

With multiple chief-level stakeholders for this project, time was key. A quick, intuitive method for review was needed.
To ensure I was user-centric, I went through each journey manually, mapping out each piece of copy into a custom Notion database that was organised in a sitemap format.
Prior to this, I was aware of no sitemap existing, this later became the foundation for the Customer Journey Map and Service Blueprint I built.

Role:

UX Copywriter

Tools:
  • Notion
  • Jira

Problem

  • The tone of voice was B2B, inconsistent and without personality.
  • Microcopy was generic and misleading.
  • Jargon developer terms hadn't been replaced.

UX Research

To ensure I was user-centric, I went through each journey manually, mapping out each piece of copy into a custom Notion database that was organised in a sitemap format.

Round 2 - In-person User testing:

Following in-person user testing I conducted on the platform, I gained some new insights on copy.
With the success of round 1, the key stakeholders were happy with me making the copy implementations straight to JIRA tickets.

Design

Development

I wrote these up into Jira tickets, and these were updates were added and QAed within a single sprint.