IBM Clinical Development eConsent
Design lead, UX/UI, design research contributor
Business impact
Met the urgent need of current customers
With the arrival of Covid-19, current IBM Clinical development customers needed eConsent capability urgently, and we met the demand on an accelerated timeline.Went to market in 6 months
Our team was able to go to market in six months, with full compliance, and zero downtime.Critical portfolio momentum
The launch of this offering was a big milestone for Watson Health Life Sciences’ portfolio and footing in decentralized clinical trials.
My role:
Lead the creation, ideation, iteration, and presentation of all design assets and artifacts through levels of fidelity
Facilitation of design thinking workshops and activities
Collaborate with offering management and development leads to strategize delivery of product roadmap goals, prioritization of epics + stories for release timelines, and decisions to address pivots
Planning and operation of the product volunteer end-user research and validation program
Synthesis of feedback & presentation of findings
Challenge
How might we enable current ICD customers to consent participants remotely, without increasing the burden on their trial sites?
Considerations
Solution needs to communicate with an already established Electronic Data Capture platform (IBM Clinical Development).
Accommodate traditional means of in-person walk-through at the site AND decentralized trials
Requires 3 different UIs that inform one another: Pharmaceutical Sponsor / CRO, Trial site, & Participant
Overview
Problem: With an ever-growing need for decentralized trials and broader population diversity, current IBM Clinical development (ICD) customers needed remote consent capabilities.
Solution: eConsent enables participants the ability to remotely opt-in to a clinical trial while serving as a tool for Sponsors & CROs to ensure participants are making an informed decision.
—————————
Team: Myself as Design lead + UX/UI, 1 Offering manager, 2 Development leads, 2 Developers, 2 QA
Methods
Concept validation of to-be scenario + project goals
Created initial product concept storyboards, based on initial generative research by the design research team that outlined user needs and outlined opportunities for market viability
Lead multiple design thinking sessions with Sponsor users for product concept validation, and synthesis of its findings for up-line communications
Designed and facilitated design thinking workshops for cross-functional partners to align and establish product goals with measurable outcomes
Continual design thinking activities about our users
Information architecture + site maps
Based on what we understood from initial generative research, grouped like-minded tasks in a logical structure.
As iterations of the information architecture became more solidified, they evolved the artifact to also reflect the navigational flow of screens with specific tasks in mind.
Page types
Page types: In order to ensure continuity and familiarity of actions throughout each experience, we identified common page types that could be repurposed across the application based on a task or problem to solve.
Task flows + organizing entities
In order to think through complex workflows and requirements, visual aids were created to organize entities and their intricate details for shared team understanding and alignment.
UX
In the spirit of agile, wireframes were created to not only iterate design concepts quickly but enable development to plug and play carbon design components to make progress towards the final UI.