Medical Project Owner

Eli Lilly Eli Lilly · Pharma · IN: Lilly Bengaluru

This role is a Medical Project Owner responsible for coordinating and tracking the end-to-end execution of medical and scientific content projects within Eli Lilly’s Global Content Hub. It focuses on project execution, workflow coordination, and operational visibility, ensuring projects move efficiently through initiation, development, review, approval, and closure. The role involves tracking milestones, managing workflows across tools like Veeva and Adobe Workfront, facilitating handoffs, and ensuring project setup and reporting accuracy. It is not an AI/ML development role.

What you'd actually do

  1. Drive execution tracking across the full project lifecycle after kickoff — from initiation through development, review readiness, approval, and closure — ensuring every stage is documented and progressing within agreed SLAs
  2. Coordinate workflow movement across Adobe Workfront, Veeva Vault, and supporting tools — ensuring smooth transitions between development, review, and approval stages
  3. Create and manage project structures in Adobe Workfront, ensuring all projects are initiated with the required metadata, workflow templates, and system readiness for execution
  4. Work closely with Functional PMs, BU leads, content owners, GCH teams, DRM, and MCA teams to ensure alignment on execution priorities, deliverable timelines, and quality expectations
  5. Maintain clear, real-time visibility of project status, risks, and bottlenecks through structured tracking, dashboards, and regular

Skills

Required

  • Project management
  • Workflow coordination
  • Stakeholder management
  • Process improvement
  • Veeva Vault
  • Adobe Workfront
  • Medical-Legal-Regulatory-Operational (MLRO) review processes
  • SLA tracking
  • Risk identification and mitigation

Nice to have

  • Experience in a regulated environment (healthcare/pharma)
  • Content lifecycle management

What the JD emphasized

  • end-to-end execution
  • MLRO review workflows
  • cycle times are minimized
  • end-to-end
  • cycle-time delays
  • turnaround against defined SLAs
  • parallel MLRO review
  • minimizing sequential bottlenecks
  • efficient processing
  • alignment on timelines
  • dependencies
  • next steps
  • execution workflows