Protected Page

NEXT Content Authoring

OBJECTIVE

Simplify and automate approval cycles across countries, and enable quick creation and assembly of pharma digital assets.

OBJECTIVE

Simplify and automate approval cycles across countries, and enable quick creation and assembly of pharma digital assets.

OBJECTIVE

Simplify and automate approval cycles across countries, and enable quick creation and assembly of pharma digital assets.

 SKILLS

Product Thinking, Concept Development, Wireframing, Visual Design, Prototyping, User Testing, Team management

 SKILLS

Product Thinking, Concept Development, Wireframing, Visual Design, Prototyping, User Testing, Team management

 SKILLS

Product Thinking, Concept Development, Wireframing, Visual Design, Prototyping, User Testing, Team management

A prominent global pharmaceutical company, sought to enhance the efficiency of its digital content management for its brands spanning North America and Europe. Their primary objective was to streamline and automate the approval processes across various countries while facilitating the swift creation and integration of digital resources. However, they encountered several challenges. These included an antiquated and labor-intensive method for identifying digital assets, limited asset repurposing capabilities, fragmented asset distribution among brands, inadequate asset analytics, a lack of a dedicated digital search and discovery system, and a deficiency in well-defined and rule-based components.


It is key to understand the pharma landscape before diving into the solution

Standard drug lifecycle

The lifecycle of a drug can be divided into several key stages, starting with drug discovery and development. In this initial phase, researchers identify and test potential compounds for their therapeutic properties. Promising candidates move on to preclinical studies, where their safety and efficacy are evaluated in laboratory and animal models. Once a drug shows potential, it progresses to clinical trials, which involve three phases of testing in human subjects to determine safety, dosage, and effectiveness. Regulatory agencies like the FDA closely review trial data, and if the drug is approved, it enters the market.


After market approval, the drug enters the post-marketing phase, during which its safety and effectiveness are continuously monitored in a real-world setting. The drug's manufacturer may also seek additional approvals for new uses or formulations. Eventually, as patents expire, generic versions of the drug become available, leading to increased competition and potentially lower prices. Throughout its lifecycle, a drug's success depends on its ability to meet medical needs, demonstrate safety, and deliver a positive benefit-risk profile for patients.



Success rate

<1% of compounds that go into test eventually become licensed medicines

Success rate

<1% of compounds that go into test eventually become licensed medicines

Cost Involved

Average cost to research & develop each successful drug is ~$ 2.6 Billion

Steps Involved

Discovery and Development, Pre-clinical research, Clinical Research, HA review, HA post-market safety monitoring

Drug discovery - Content lifecycle

Key challenges in the pharma industry around content creation

Why we need Module Manager?

Key personas involved


Pharma company

Pharmaceutical companies hold multifaceted responsibilities in drug content approval. They provide essential clinical data derived from trials, ensure compliance with regulatory guidelines, communicate product risks and benefits effectively, and collaborate with creative agencies to create engaging, informative content suited to the target audience.


Design Agency

Pharmaceutical companies face the challenging task of bridging the gap between complex scientific data and the general audience, a task that necessitates collaboration with creative agencies. However, this partnership can be costly, particularly due to the iterative nature of the content development process. Creative agencies must possess in-depth knowledge of the pharmaceutical industry, regulatory requirements, and the nuances of communicating medical information effectively. Their expertise is vital in creating content that meets both regulatory standards and engages the target audience, making their involvement indispensable despite the associated expenses.


Health Authority

The Health Authority, such as the FDA or EMA, safeguards drug safety and efficacy. They offer regulatory guidance, make final approval decisions, and engage in collaborative feedback and communication with pharma companies.

Competitor Analysis

What module manager does in simple terms

One of the aims of Module Manager is to establish a standardized template for modular content creation while allowing room for individual component customization. This could also serve as a distinct selling point within Module Manager's product offerings when compared to our competitors, who currently provide standardized templates at the final asset level.


Approach to establishing a Module Manager standard Modular Content Template includes:


  1. Defining a template for creating standardized Modular Content.

  2. Outlining the modular structure's layout with reference to existing standard templates.

  3. Incorporating component-level distribution within the modular layout.

Sample marketing tactic & module generation

Information Architecture

The UX Flow

Shared understanding session on user journeys

The product team arrives with prepared user journeys. These user journeys are presented and discussed within the context of a Mural workflow during a collaborative grooming session. This interaction serves to ensure that both teams are on the same page, enabling a shared understanding of how the feature or requirement should function and its place within the broader product framework.

Shared understanding session on user journeys

The product team arrives with prepared user journeys. These user journeys are presented and discussed within the context of a Mural workflow during a collaborative grooming session. This interaction serves to ensure that both teams are on the same page, enabling a shared understanding of how the feature or requirement should function and its place within the broader product framework.

Defining use cases


The UX team and the product team work together to collectively establish the use cases and determine their order of importance or priority. This collaborative effort ensures that both teams are actively involved in defining the specific scenarios and tasks that the product needs to address, and it allows for a shared understanding of which use cases are of greater significance in the development process.

Defining use cases


The UX team and the product team work together to collectively establish the use cases and determine their order of importance or priority. This collaborative effort ensures that both teams are actively involved in defining the specific scenarios and tasks that the product needs to address, and it allows for a shared understanding of which use cases are of greater significance in the development process.

Defining use cases


The UX team and the product team work together to collectively establish the use cases and determine their order of importance or priority. This collaborative effort ensures that both teams are actively involved in defining the specific scenarios and tasks that the product needs to address, and it allows for a shared understanding of which use cases are of greater significance in the development process.

White boarding & Wire framing

We organize a design thinking workshop involving a broader audience to collectively examine the initial wireframes. The purpose of this workshop is to address any questions, resolve potential roadblocks, and confirm that the design is progressing in the correct direction. This inclusive approach aims to ensure that all stakeholders have a chance to provide input, clarify concerns, and collectively steer the design process toward its intended goal.

White boarding & Wire framing

We organize a design thinking workshop involving a broader audience to collectively examine the initial wireframes. The purpose of this workshop is to address any questions, resolve potential roadblocks, and confirm that the design is progressing in the correct direction. This inclusive approach aims to ensure that all stakeholders have a chance to provide input, clarify concerns, and collectively steer the design process toward its intended goal.

User Testing

We adapt our user testing sessions based on user availability and specific project needs. In these sessions, we establish scenarios and key checkpoints within the design flow. We set up a temporary or prototype site, created by the engineering team, and invite users to engage with it. During this process, we meticulously observe and record their interactions, documenting usage patterns, identifying pain points, and noting what aspects they found satisfying. The primary objective during this phase is to pinpoint areas of concern and transform subjective user feedback into quantifiable and objective parameters. This approach enables us to enhance the user experience in a data-driven manner.

User Testing

We adapt our user testing sessions based on user availability and specific project needs. In these sessions, we establish scenarios and key checkpoints within the design flow. We set up a temporary or prototype site, created by the engineering team, and invite users to engage with it. During this process, we meticulously observe and record their interactions, documenting usage patterns, identifying pain points, and noting what aspects they found satisfying. The primary objective during this phase is to pinpoint areas of concern and transform subjective user feedback into quantifiable and objective parameters. This approach enables us to enhance the user experience in a data-driven manner.

Design System

The Indegene Design System 2.0 was crafted with a dual focus on accessibility and efficiency. It incorporated proven design practices from established systems, ensuring a faster creation of Visual Designs while prioritizing accessibility for a wide user base. This approach aimed to streamline the design process and maintain high-quality standards for improved user experiences.

Design System

The Indegene Design System 2.0 was crafted with a dual focus on accessibility and efficiency. It incorporated proven design practices from established systems, ensuring a faster creation of Visual Designs while prioritizing accessibility for a wide user base. This approach aimed to streamline the design process and maintain high-quality standards for improved user experiences.

Visual Designs ( 600+ screens )


After taking into account and integrating all feedback and necessary revisions, the final VDs are completed. At this stage, a review session is scheduled with the stakeholders to seek their final approval. This ensures that the design aligns with their expectations and requirements before moving forward.

Visual Designs ( 600+ screens )


After taking into account and integrating all feedback and necessary revisions, the final VDs are completed. At this stage, a review session is scheduled with the stakeholders to seek their final approval. This ensures that the design aligns with their expectations and requirements before moving forward.

Click here to view prototype

Design Handover to Dev

Once all stakeholders have given their approval, the VDs are made accessible through Zeplin. These designs are then linked to their corresponding stories in JIRA, signifying that they are prepared for development work to commence.

Design Handover to Dev

Once all stakeholders have given their approval, the VDs are made accessible through Zeplin. These designs are then linked to their corresponding stories in JIRA, signifying that they are prepared for development work to commence.

UX review during sprint

As the story proceeds into testing phase in the QA bucket, the UX team thoroughly examines the development build. To ensure pixel-perfect precision, we create a comprehensive report by submitting a UX bug ticket on JIRA. It's important to note that no story can progress to the product review stage without prior UX approval.

UX review during sprint

As the story proceeds into testing phase in the QA bucket, the UX team thoroughly examines the development build. To ensure pixel-perfect precision, we create a comprehensive report by submitting a UX bug ticket on JIRA. It's important to note that no story can progress to the product review stage without prior UX approval.

What Next?

The next steps involve the introduction of a unified suite offered by Indegene, which comprises essential components such as Module Manager, Content Studio, Email, Banner, and eDetail. This integrated suite promises a comprehensive and streamlined solution for managing and optimizing content across various digital platforms in the pharmaceutical and healthcare industry. With Module Manager at its core, the suite ensures the creation of standardized modular content templates while allowing for individual customization. Content Studio complements this by enabling efficient content creation, editing, and management. The Email and Banner modules enhance targeted communication and outreach, while eDetail provides a specialized platform for engaging with healthcare professionals. Together, this unified suite promises a holistic approach to content management, offering the pharma industry a competitive advantage in delivering valuable, compliant, and engaging content.

Let's create something together

Let's create something together

Let's create something together