Pfizer · Generative AI · Enterprise SaaS
Gen AI Adoption Unlocked — Designing for Trust in a Pharmaceutical Regulatory Environment
Pfizer's marketing teams had a Gen AI copy tool — but low adoption, because marketers couldn't audit or defend generated content in medical-legal review.
Reframed adoption resistance as a transparency design problem. Implemented parameter visibility, generation provenance, and structured feedback capture — aligning cross-functional teams on the Idea Accelerator positioning before a line of production code shipped.
MVP delivered for beta onboarding. The "Idea Accelerator" reframe unlocked adoption — repositioning AI as a volume generator for human evaluation, not a replacement.
Trust
is a design problem.
Not a training problem.
Role
UX Strategist · Sole Strategic Designer
Deliverables
Stakeholder alignment, co-creation strategy sessions, customer experience blueprints, prototypes
Status
MVP delivered · Beta testing
The design challenge wasn't "how do you make this look good." It was "how do you design for trust in a system whose outputs marketers can't fully verify, inside a regulatory environment that doesn't move as fast as the technology."
I orchestrated the UX architecture for Pfizer's generative AI marketing platform. The real project was institutional: reframing AI adoption resistance as a transparency design problem — not a training problem — and standardizing that framing across marketing, regulatory, and engineering before a line of production code shipped.
01 — Context & Constraints
Pharmaceutical AI Has a Trust Problem, Not a Technology Problem
The organization
Pfizer's marketing teams develop brand-specific content across multiple channels and global markets. Content must pass medical-legal review and comply with pharmaceutical advertising regulations. The business case for Gen AI was efficiency — the design problem was making that efficiency trustworthy.
My role
Lead UX strategist — developed the customer experience blueprint, synthesized competing stakeholder needs into a unified adoption strategy, and led the co-creation sessions that produced the “Idea Accelerator” reframe.
The real constraints
Regulatory environment that doesn't move as fast as the technology
Every piece of pharmaceutical marketing copy requires medical-legal review. A Gen AI tool that generates content faster than it can be reviewed creates compliance risk, not efficiency. The review workflow had to be a first-class design feature — not an afterthought.
Marketers who didn't trust the output
Pfizer marketers arrive at pitches with 3–5 carefully developed ideas. Using AI-generated content meant staking professional judgment on output they couldn't verify. The adoption problem wasn't technological — it was trust in a system whose accuracy they had no way to independently evaluate.
Brand-specific language across multiple pharmaceutical brands
Dozens of pharmaceutical brands, each with its own approved language, tone, and regulatory constraints. The tool couldn't be a generic text generator — output had to be brand-appropriate and defensible inside Pfizer's review process.
Scalable MVP under active feature expansion
The brief covered copy generation, translation, and image generation — with significantly more on the roadmap. The UI architecture had to accommodate features that hadn't been scoped yet without requiring a redesign each time one shipped.
02 — The Strategic Frame
Reframing Adoption Resistance as a Design Problem
Reframing adoption resistance as a design problem
Low AI adoption was framed as a change management problem — resistant users needing training. The actual problem was a design failure: the system gave users no basis for trusting its output. A marketer who can't explain why copy was generated the way it was can't defend it in a review meeting. That's not a training gap. That's a transparency gap.
Positioning Gen AI as an Idea Accelerator, not a replacement
Marketers develop 3–5 copy concepts per pitch. The reframe: Gen AI generates that same volume in minutes, leaving human judgment — irreplaceable in regulated communications — for evaluation rather than first drafts. It front-loads the work the marketer was least good at.
03 — Prompt Architecture
Designing a Transparent Generation Pipeline
The generation workflow was designed as a transparent pipeline. Marketers needed to see the parameters they set, trace them through to the output, and understand why the system produced what it did — before they could defend it in a review meeting.
Generation Pipeline
Input Parameters
Engine
Brand model + regulatory filters
Output + Provenance
“Talk to your doctor about Lipitor…”
Generated from:
Feedback on output retrains the brand model — closing the trust loop
Parameters are always visible alongside the generated output
04 — Process
From Journey Map to Validated Prototype
Starting with the user journey
Mapped the user journey against business requirements and MVP features before wireframing — not as a deliverable but as a guide updated throughout the engagement as features were added. This prevented workflow design from locking in too early around a feature set that was actively changing.
Sketching → wireframes → prototype
Sketches first, then black-and-white wireframes before any visual decisions — keeping early feedback on workflow and information architecture rather than aesthetics. Iterated through user testing cycles with Pfizer marketing teams.
Co-creation strategy sessions with stakeholders
Regular sessions across multiple Pfizer teams — not to present completed work, but to synthesize competing perspectives before they hardened into blockers. In a regulated environment, surfacing compliance constraints upstream is itself a strategic outcome.
User journey map used as a guide throughout the engagement
Early sketches and wireframes before visual design decisions
05 — The Hard Part
What Wasn't in the Brief
The problems that weren't in the brief — and how they changed the design.
The trust problem
Marketers weren't rejecting the generated copy because it was bad — they were rejecting it because they couldn't explain to reviewers why it said what it said. Output quality wasn't the barrier. Auditability was. The entire transparency layer — parameter display, generation history, feedback capture — emerged from this finding, not the original brief.
The change management victory — reframing AI as an Idea Accelerator
Before the reframe
“AI will write your copy. Your job is to check it.”
Result: resistance, low adoption, professional threat framing
After the reframe
“AI drafts the first five ideas. You decide which one is right.”
Result: adoption unlocked — human judgment repositioned as the premium skill
“Idea Accelerator” came from a stakeholder workshop — not a marketing line. It was the framing that made the tool feel safe to use. Positioning Gen AI as expanding ideation volume rather than replacing it was the intervention that moved adoption.
Designing around constraints I didn't control
Generation attempt limits, duplicate content handling, content saving behavior — all engineering constraints that arrived mid-design, each requiring a full design response. How do you show a user they've hit their generation limit in a way that feels intentional rather than broken? These constraint-to-design translations were some of the most precise problems in the project.
06 — Key Design Decisions
Dual-panel layout built for future features
Right panel for Gen AI inputs and generation controls. Left rail designed explicitly as a future feature slot — every new capability has a home without restructuring the primary workspace.
Parameters visible at output time
Generated content shown alongside the parameters that produced it — brand, tone, format, constraints. Marketers needed to see not just what was generated, but why, before they could defend it in a review meeting.
Feedback capture as a first-class feature
Feedback mechanisms built in from the start — not as a product analytics play, but to improve the language model with real pharmaceutical marketing data. The loop between user judgment and model improvement was a design requirement, not an afterthought.
Design–engineering bridge on generation constraints
Generation attempt limits, duplicate content handling, content saving behavior — engineering constraints that arrived mid-design and each required a full design response. Load-bearing behaviors in a regulated environment where every output is a potential compliance artifact.
Copy generation workflow
Translation workflow
07 — MVP Feature Set
Copy generation
Brand-specific copy for web banners, emails, and advertisements — generated from parameter inputs, evaluated against brand guidelines.
Translation
Post-generation translation across markets, with error-handling for translation failures and feedback capture.
Image generation & regeneration
Image selection and generation workflow, designed as wireframes within the same generation context as copy.
08 — Outcomes
MVP delivered for beta onboarding
Copy generation, translation, and image selection — delivered and prepared for beta testers. Flexible layout means new features ship into the existing interface without redesign.
Institutional alignment around a new way of working
The Idea Accelerator reframe aligned marketing, regulatory, and leadership stakeholders — making adoption a shared goal rather than a top-down mandate. The transparency layer gave marketers the auditability to defend generated outputs inside Pfizer's existing review workflow.
“I'm not using AI to write copy. I'm using it to never start from a blank page again.”
— On the Idea Accelerator framing
09 — What I'd Do Differently
I would have pushed for a medical-legal reviewer to be part of the design research process earlier — not as a gatekeeper, but as a user. The compliance review workflow is downstream of the tool, but its requirements shaped every design decision we made. Getting that perspective in week two rather than week eight would have changed the initial framing significantly.