1 on 1 Meeting platform
One application for all employee needs
My Role
Product design lead
User research
UI/UX design
Interaction design
Team
Project Manager
2 Designers
2 Developers
QA Testers
Scope
A private meeting platform
Connecting the users for better problem solution
Eliminating the involvement of thirst person
Reducing turnaround time
Flexibility and transparency of the process
Problem Statement
Healthcare professionals (HCPs) and Key Opinion Leaders (KOLs) often require a third-party facilitator to organize their online meetings, resulting in lengthy processes. To address this challenge, the creation of an internal meeting platform would streamline coordination between both parties.
User Role and Audience
Healthcare professionals (HCPs)
Key Opinion Leaders (KOLs)
Overview
The pharmaceutical company caters to various groups, including healthcare professionals, patients, key opinion leaders (KOLs), and health experts. Due to their diverse requirements, healthcare professionals (HCPs) need to regularly connect with KOLs, with the frequency varying depending on the issue at hand. Currently, arranging these meetings involves third-party facilitation, resulting in extensive back-and-forth communication. The project's objective was to develop an internal digital meeting planning platform to streamline these interactions, aiming to save time, increase efficiency, and improve overall collaboration.
Outcomes
40%
Expected Increase in Self-care participation
20%
Projected increase in user interaction
40%
Anticipated Improvement in Mental Well-being
Process
UAT
User Testing
Amazing the developed designs
Design
Design Guidelines
Visual Library
High fidelity wireframes
Ideation
Information Architecture
Task Flow
Paper Prototyping
Low and mid fidelity wireframes
Research
Self Exploration
User Interviews
Contextual Enquiry
Persona
Competitor Analysis
Thematic Analysis
03 Design
Considering this was a pilot project, we planned to create the design guidelines from scratch. We decided on the colors with the target group 'IT professionals' in mind. The idea was to use blue as the primary color to align with the IT ecosystem and introduce bright colors as secondary and accent colors to add contrast and make the UI more engaging.
The user interface was kept simple to highlight the main elements, with plenty of white space to help users focus on one thing at a time and navigate the application freely. Visual cues were added to minimize the cognitive effort required from users.
04 UAT
Considering this was a pilot project, we planned to create the design guidelines from scratch. We decided on the colors with the target group 'IT professionals' in mind. The idea was to use blue as the primary color to align with the IT ecosystem and introduce bright colors as secondary and accent colors to add contrast and make the UI more engaging.
The user interface was kept simple to highlight the main elements, with plenty of white space to help users focus on one thing at a time and navigate the application freely. Visual cues were added to minimize the cognitive effort required from users.
Retrospective
Considering this was a pilot project, we planned to create the design guidelines from scratch. We decided on the colors with the target group 'IT professionals' in mind. The idea was to use blue as the primary color to align with the IT ecosystem and introduce bright colors as secondary and accent colors to add contrast and make the UI more engaging.
The user interface was kept simple to highlight the main elements, with plenty of white space to help users focus on one thing at a time and navigate the application freely. Visual cues were added to minimize the cognitive effort required from users.
02 Ideation
Considering the scale and the requirements of the project were not complex, and the user roles were well defined, Phase 1 explained what the stakeholders were looking for. Now, through meeting recordings, we have evaluated our assumptions. The aim of this phase is to confirm the requirements.
Initiating with information architecture
Given the nature of the application and the requirements, we were in a difficult position to confirm the requirements because the client was unsure of what was needed. Instead of writing out the understanding and requirements, we created a detailed information architecture of the application. This included all the details such as restrictions, platforms, user roles, and specific tasks.
This approach helped provide visibility to all concerned parties and facilitated faster approvals, as it was something they could visualize more easily compared to a textual plan.
For HCPs
Logging in and Blocking KOL's Calendar
Viewing / Attending Registered Events with post meeting Survey
Cancelling / Rescheduling a Registered Event
For KOLs
Setting Up Availability on Calendar
Getting Notified that HCP has Blocked Calendar
Viewing / Attending Registered Events and Viewing Past Events
Cancelling / Rescheduling a Registered Event
Account Settings / Forgot Password
User flows for plotting all minute details
One the IA was approved, our immediate step was sketcing out teh user flows, which was to be as precise of all the functionalities for each features as possible. These user flows once approved were forwarded to the development team so that we could start with the backend work - based on all the details and checks as mentioend in the flows. To ensure we map all the user actions, we listed few tas,s for both the users,
User Flow - HCPs
Blocking KOL’s Calendar
To both KOL & HCP
User Flow - KOLs
Setting up calendar availability
Structuring the application with wireframe visualizations
With the information architecture in hand, we planned to execute the wireframes considering the approaching timelines. We began by sketching our thoughts based on the IA onto paper wireframes. This approach followed best practices, as within a few minutes, we had the first actual draft of our application. This increased our visibility by providing something tangible.
01 Discover
This was a new product, and the stakeholders didn’t have clear requirements beyond the request to create an internal meeting platform. They provided a few screenshots of existing platforms similar to Monday.com. To better understand their needs and gather more information about the requirements, we initiated a process of understanding and reflecting on their needs.
Overlooking the requirements and stakeholder meeting recordings
Prior to the initial call with the design team, the project manager had several discussions with the stakeholders and management, from whom the requirements were coming. Our call with the project manager was insightful to an extent, but to form a clearer map, we requested access to the previous recordings. These recordings could help us understand exactly what the client was looking for. Our intention was to identify and address the pain points.
The recordings provided us with a clear understanding of the client’s requirements and allowed us to effectively map their pain points. The most significant issue was the need to eliminate the involvement of a third user role in the meeting scheduling process. Additionally, the stakeholders were quite fascinated by the functionality of the meeting platform used by Monday.com and expressed a desire for something similar.
Competitor analysis to understand market trends
Since the client was quite inspired by existing meeting platforms like Monday.com, we decided to conduct a competitor analysis of similar platforms. Our goal was to understand what features other platforms offer and identify what we could incorporate into our own platform to best meet the client's needs. We selected five comparable platforms and evaluated them based on the features they provide.
Feature
Monday.com
SchedulePro
MeetGuru
BookIt
QuickSch.
User Interface
Modern & Intuitive
User-friendly
Simple & Clean
Modern
Basic
Integration with
Calendars
Google, Outlook,
iCal
Google, Outlook
Google, Outlook,
iCal
Google, Outlook
Meeting
Reminders
Email, SMS, In-app
Notifications
Email, Push
Notifications
Email, SMS
Email, Push
Notifications
Customizable
Meaeting Links
Yes
Yes
No
Yes
Yes
Group Meeting
Scheduling
Yes
Yes
No
Yes
Yes
Automated
Rescheduling
Yes
Yes
No
No
Yes
Mobile App
Yes
Yes
No
Yes
No
Video Conf.
Integration
Zoom, Teams,
Webex
Zoom, Webex
Zoom, Teams
Zoom, Teams
Zoom, Webex
Reporting &
Analytics
Advanced
Advanced
Basic
Basic
Advanced
Cost
$10/month
$15/month
$12/month
$8/month
$20/month
Cost
14 days
30 days
7 days
14 days
30 days
Customer
Support
24/7 Support
Business Hours
24/7 Support
Business Hours
24/7 Support