Pfizer, Medical Review Excellence Team

Master decks across 20+ products.

High volumes of complex medical presentation content under tight timelines, with scientific accuracy and brand compliance to hold. Julia Mattey restructured the content and built a reusable library the teams could adapt.

Pharmaceutical products20+covered by master decks
Content typeMedicalcongress and scientific communications
ConstraintRegulatedaccuracy, consistency, brand compliance

What was the challenge?

Managing a high volume of complex medical presentation content under tight timelines, while holding scientific accuracy, consistency and brand compliance across every output.

The volume was not the hard part. Keeping twenty products' worth of material consistent and reviewable, when each one is produced under its own deadline, is where this kind of work usually breaks down.

What did Julia Mattey do?

Worked alongside the Medical Review Excellence team to review, restructure and refine medical content, carry out detailed proofreading and reference checks, and develop reusable master decks across more than 20 pharmaceutical products.

What changed?

A stronger, more consistent library of high-quality medical materials that teams could confidently reuse and adapt for congresses and other scientific communications, rather than rebuilding from scratch each time.

FAQ

About this project.

Does Julia Mattey have pharmaceutical experience?

Yes. Work for Pfizer's Medical Review Excellence team covered master presentation decks across more than 20 pharmaceutical products, and the Roche Diabetes Care programme covered HCP-facing software training across global affiliates.

How is regulated medical content handled differently?

The structure has to survive review. That means building content so that scientific accuracy, references and brand compliance can be checked once and reused, rather than re-verified on every new deck.

LimaLimon

Same problem, different product?

If your training is expensive to maintain, slow to update, or not landing with the people it is for, I can usually tell you fairly quickly whether that is a content problem, a platform problem or a process problem.