How Mass General Brigham moves marketing innovation beyond the pilot
Healthcare marketers are being asked to innovate while cutting costs. Mass General Brigham's approach offers practical lessons on protecting time for experimentation, learning from pilots, and making successful changes part of everyday marketing work.
Healthcare marketers are faced with a seemingly impossible mandate: to simultaneously cut costs and innovate. AI has added to those expectations, but campaign deadlines and website requests haven't slowed down.
When everything is urgent, innovation gets squeezed into the margins. Someone tests a promising tool between campaign deadlines and website requests, but nobody has the time or responsibility to turn that result into a better process. After enough false starts, it's easy to see why the next big idea gets met with “that won't work.”
Mass General Brigham’s approach to innovation caught my attention because it gives that work a structure. I asked Julia Sorensen, Vice President of Marketing, about how her department protects time for experimentation and brings successful pilots into everyday use.
I wanted specifics that other healthcare marketers could borrow, especially those without MGB’s resources.
“We don’t have the time or staff for innovation.”
Giving your team permission to experiment requires making room in their workload. Otherwise, people have to choose between a campaign deadline and an experiment they can postpone.
“You definitely have to carve out time … all the pressures that are on us every day will take over otherwise.”
Julia Sorensen
MGB makes that commitment explicit through a separate innovation function. Within its AI Change Champions program, participants dedicate up to 20% of their time to specific projects that redesign workflows with AI. The department also uses existing staff meetings for shared training, alongside twice-monthly lunch-and-learns.
What to borrow from MGB
Use an existing team meeting to identify a recurring problem or an inefficient workflow. Discuss whether a new tool or a change in process could help, then reserve separate time to test one idea. A smaller organization may also have fewer approval layers to navigate: an advantage worth using.
You probably can't give people a full day every week. That's fine. Decide how much time you can protect and which requests will have to wait. Make that decision yourself on the leadership level. Asking an overloaded team to “find time” for innovation passes the tradeoff down to the people least able to change the priorities.
“We can’t afford experiments that go nowhere.”
Taking someone away from campaign work or website updates to test an idea has an obvious cost. But suppose a small pilot shows that a new content workflow actually creates more review work than it saves in drafting. That’s a valuable lesson, even if the project ends there.
MGB now invites employees to submit short proposals describing a problem and an idea for addressing it. Selected proposals become detailed briefs. Projects get a defined scope and an executive sponsor, giving the team boundaries within which to experiment.
At some point, the team has to decide what happens next. Does the idea deserve another round of testing? Is it ready to become part of everyday work? Or have they learned enough to stop?
“If you don’t have pilots failing, you’re not being bold enough and you’re not pushing the limits of what you can do.”
Julia Sorensen
That requires more than permission to fail. MGB is also working to capture lessons through playbooks and after-action summaries. Julia acknowledged that making this knowledge easy to access and reuse remains a work in progress.
What to borrow from MGB
For your next pilot, agree on what you need to learn and when you’ll review the results. Document enough detail to inform another attempt. A note that says “the test didn’t work” isn’t helpful. What did you discover that should change next time?
Calling something a learning experience should come with an obligation to make it useful. Otherwise, another team might spend its limited time reaching the same conclusions.
“The pilot works, but the team goes back to the old process.”
Suppose your editors try a new publishing workflow while preparing a service-line campaign. But then, they get stuck when a clinician requests revisions. With a deadline approaching, they return to the old process. Before calling that “resistance to change,” figure out what stopped them.
MGB involves the people who will eventually own a new process while the pilot is still taking shape. Julia calls them the “ball catchers.” They know the approvals, handoffs and exceptions that could derail the improvement once the innovation team steps away.
“Nothing is going to live in innovation forever.”
Julia Sorensen
When a pilot succeeds, those teams lead implementation. Innovation colleagues can advise, but they won’t run the new process indefinitely.
One example is MGB's work on generative AI search. The team tested changes to its technical and content practices, then incorporated what it learned into a playbook used in everyday marketing work.
What to borrow from MGB
Test the proposed workflow with a real service-line update. Have a clinical reviewer request revisions, then let another editor pick up the work. Watch what happens when someone other than the pilot team needs to finish the job. Fix those problems with the people who will own the process before asking everyone else to switch.
What does your team get to stop doing?
The pressure to innovate while cutting costs doesn't disappear when a pilot ends. What I like about MGB's approach is that the people who will eventually own a successful innovation are involved long before the pilot ends.
For your next pilot, plan the transition alongside the test. Set aside time for people to put a successful result into practice. And be equally clear about which old steps they can stop doing.
Leaving both processes in place erases the time you hoped to save.
You had to free up capacity to experiment. Getting that capacity back should be part of how you measure success.
