Acuity

Stakeholder management SaaS platform

THE BRIEF

Effectively identify the right experts for the right activities and share insights compliantly across the enterprise.

— 81QD
MY ROLE
THE TEAM

I gathered requirements, designed wireframes, conducted user research, developed iterative interactive prototypes, wrote functional specifications for development, and created final UI assets.

  • UX / UI designer
  • Project manager
  • Business analyst
  • Development lead
APPROACH

81QD aims to create a client relationship management SaaS portal tailored for medical and pharmaceutical companies. Their CRM must be customizable to fit various corporate structures while ensuring regulatory compliance across departments. Each department needs to record and display different data types according to their specific requirements.

EXECUTION

I reviewed the existing documentation since the product was already in development when I joined. My first task was to conduct a content audit and establish the information architecture.

After agreeing on the core functionality through stakeholder interviews, I created logical sections of the application and developed workflow paths for various use cases.

The product focused on Key Opinion Leaders (KOLs), who were of great interest to pharmaceutical companies. Each KOL had a profile with personal details and could have events and brief interactions associated with them.

Users could organize KOLs into groups, create and manage these groups, keep notes, and share profiles with other users.

The stakeholder, our link to end users, led the weekly design reviews and provided guidance for successful designs. Prototypes were shared with end users remotely, and their feedback was relayed to the team.

CONCLUSION

Lessons learned

This was the largest and most complex project I have been part of, including a major project dedicated to the Admin section.

  • Information architecture is crucial, encompassing site maps, content organization, and more.
  • Clients often don't know exactly what they want to build and tend to describe functionality endlessly unless their expectations are managed.
User-agent: * Disallow: /