Switch Factiva
  • Factiva
    • ❗Product Problem
    • 📌Switch Enhancement
    • 🎨Design Process
      • 1. Analysis and User Research
      • 2. Study the Current Performance
      • 3. Definition of the User Experience
      • 4. Proposal Validation
      • 5. Final Visual Design
    • ✅Enhancement Result
Powered by GitBook
On this page
  • User Benefit
  • KPIs / Smart Goals
  • First approach
  1. Factiva

Product Problem

PreviousFactivaNextSwitch Enhancement

Last updated 1 year ago

Factiva has launched a new interface that expecting simplify the consumer-like search experience, makes it more intuitive and easy to surf content, and personalize the user interests.

The new Factiva experience is working in parallel with the Classic Factiva, due to they don't have the same capabilities at this point, so to appease customers, we must provide easy access to Classic Factiva.

User Benefit

To aid with the migration of customers from Classic Factiva to New Factiva we must provide easy access from Classic Factiva to New Factiva so that they may familiarize themselves.

KPIs / Smart Goals

  • The number of visitors visiting New Factiva from Classic Factiva.

  • Retention of visitors who visit New Factiva from Classic Factiva

First approach

As part of the new Factiva releases, a button called "Factiva Toggle" was integrated into the navigation bar of both interfaces. This button allowed users to switch between the classic and new experiences. However, this feature did not perform as expected. The outcomes from the Customer Service Program revealed difficulties in its usage and it did not meet the set Key Performance Indicators (KPIs).

❗