About Bersin by Deloitte

Bersin by Deloitte is a subscription based service that delivers research and strategies to the HR professional

Quick Summary


Situation

Some customers are leaving the site due to challenges in distinguishing new research from old and finding content that matches their interests. As a result, forum engagement has declined, and membership cancellations have risen.

Task

  • Encourage customers to return to the site more frequently by designing a notification center that delivers new research tailored to their preferences, keeping them engaged with relevant content
  • Retain existing members and drive new subscriptions

Action

Develop a minimum viable product (MVP), evaluate its impact through research, and iterate based on customer feedback.

Result

Early research showed an 32% increase in website participation over four months since implementation. While membership renewal feedback is still pending, customer responses in forums and help tickets have been positive.

Client

Deloitte, San Francisco CA

My role

UX Designer

Team

Product owner, developer, content strategist and UX designer

Tools

Adobe Illustrator

Timeline
Four sprints — 20 days

Date

2017

Discover

Problem Statement • Research • Features for MVP

Problem statement

Some customers are leaving the site due to difficulty distinguishing new research from old and finding relevant content. This has led to lower engagement, especially in forums, and an increase in membership cancellations.

What makes a good notification?

What is the structure of a good notification?

Strategy session

Our team held a strategy session to explore different types of notifications and, considering the timeframe, determined which features to prioritize for the initial release.

We discussed the different notification types.

  • User Subscribed Notifications – New and related research based on user preferences
  • Community Generated – Community forums, ask the experts, news feed likes, and comments
  • System – Resetting passwords, updates
  • Push Notifications – Pushed by the server rather than by a request from the client
  • Passive Notification – Weather updates, no action required
  • Smart Notifications – The system can sense user interaction levels

Then we discussed the notification structure.

  • Most recent notification — Position top
  • Urgency — Use color
  • Read/Unread — Differentiate by contrast
  • Notification type — Filter
  • Title/Message
  • Source/Type of message
  • Urgency
  • Actions

We chose the following features for MVP

Features for future release

The need for ongoing user testing

Notification model

Define

Wireframes • Specifications

Anatomy


Wireframe


Design explorations


Final design


Specifications

Conclusion

Customer feedback was very positive, with many subscribers appreciating the notifications featuring content tailored to their interests. There were no complaints about the notifications being a nuisance, likely due to our light and thoughtful implementation.

Early research showed an 32% increase in website participation over four months since implementation. While membership renewal feedback is still pending, customer responses in forums and help tickets have been positive.