top of page

Refinitiv Developer Portal

Project | 06

Synopsis

The Refinitiv developer portal provides an entry point for potential customers and returning customers to discover Refinitiv API products and to onboard with Refinitiv (Risk & Finance APIs formerly Thomson Reuters).

The project required existing content on the portal to be migrated across to the new solution and AEM platform with any new requirements captured from stakeholders.

The initial tasks involved gaining as much familiarity with the existing content as possible and coordinating engagement with the product owner and stakeholders to understand the importance of each piece of content set and gain insights into the business direction and vision.

The content was then cross referenced with analytical data in order to understand which pages were most visited and how. The analysis then helped me to understand what was working and what wasn't on the current site.

Based on the gathered knowledge I worked with the product owner to build out design requirements with a priority rating given to content, whilst also performing benchmark analysis on existing developer and API offerings in the market. The output of this was discussed with the stakeholders to continue to shape the vision.

When the team had a firm understanding of the vision and all were agreed, I started to work on the most important aspect of the portal which included the discoverability of API's, creating information architecture whilst understanding the user personas in order to cater for them and organise content and its discoverability based on these persona types.

For the APIs I worked towards creating screens in Sketch and sharing them with stakeholders to obtain feedback and to iterate designs. After agreement, I put the designs into InVision to test with users to ensure that the logic could or couldn't be validated and then improved if necessary.

After iteration from user testing, I worked with a cross operational digital standards team on component designs and also worked with visual designers where needed. This process happened in parallel with working within developer scrum teams to build out the pages. 

Whilst the API pages were being developed, I ensured that I worked on creating the designs for other areas of the site and repeating the processes to get validation and then working with the developers.

 

Throughout my time at Refinitiv I worked to push for UX standards if I thought they were being compromised in favour of developer efficiency or due to organisational biased views.

 

I ensured that I understood where the developer portal fitted in with the wider context of the organisation and it's ecosystem on or offline. I aligned with other design streams that were happening with other Refinitiv products and made sure there were relevant links between these entities in terms of the discovery of the developer portal and users being able to cross reference product information and opportunities.

Having delivered the UX for the developer portal, I continued to work with Refinitiv on other API related products connected with the developer portal and their API platform.

Homepage Dev Portal unauthenticated.png
Homepage - Unauth'd - mobile.png
Design Process

Benchmarking and market awareness

Persona development

Workshops & discovery sessions
User Testing (10-20 participants)

Stakeholder awareness & engagement

Board Level presentations and validation
Project/time management

Working with both onsight and offshored development team

Tools used: Sketch, InVision, Zeplin, Jira (for dev process)

Design Deliverables

Content analysis

Persona development

Information Architecture

Wireframes / Designed pages in Sketch

Prototypes for testing

Screen Designs for Desktop & Mobile

Content Analysis & Audit
Screen Shot 2020-10-22 at 11.35.21.png
Customer Journey Mapping

Interest Exposure, Evaluation, Purchase, Support.

Artboard-API-Onboarding.png
Persona Development
Screen Shot 2020-10-22 at 11.48.28.png
Screen Shot 2020-10-22 at 12.48.03.png
Test Plan

Test Facilitators: 1
Total Duration: 1 hour
Test Subjects:  10 people

Areas covered:

Participant profile, Developer Community homepage, API catalogue, Overview, Quick Start, Documentation, Downloads, Tutorials.

Screen Shot 2020-10-22 at 12.02.06.png
User Testing

 

For the testing stream, I worked closely with a UX researcher to help define the test content The user testing had several objectives, to help identify and validate user types as per assumptions and existing knowledge base:

To learn of the target audience’s typical workflow and how well the prototype supports this.

 

To ensure a developer can find an API within the catalogue.

To discover any problems with accessing and understanding the documentation for an API.

To check the relevance and comprehensibility of the related material provided on the Homepage.

Screen samples
Download CTA (with LHSM).png
vids.png
Dev_content_APIS.png
bottom of page