Scaling Team Impact

Overview

 

Role: Content Design Manager

Team: Content Designer (Lauren Ridenour), Brand Designer (Itzia Tapia) 

At Collective Health, our Content Design team was small (though mighty!). However, as the only wordsmiths at the company, our scope had widened to include fielding requests from several cross-functional departments.


Discovery

 

I sat down and reviewed a year’s worth of JIRA tickets, cataloging the requests, noting the time spent to fulfill them, and searching for patterns. What emerged was that we spent considerable time creating specialized, custom content for different clients. While this made those select clients happy, the impact was relatively small.

The team needed their focus back, but we didn’t want to leave departments with strategic business needs, like Client Success, out to dry. So the question was: how could we enable teams to create their own on-brand, high value content without involving Content Design every time? 

 

Option 1: Decision tree

 

I sat down with Client Success, whose requests took several hours of one Content Designer’s time (often even multiple days when fully tallied), to brainstorm how we could help them. Our first idea was to create a decision tree, which would help Client Success think through their asks before passing them to Content Design. Even in Lucidchart, this started to feel messy. 

The issue with the decision tree route was that it didn’t actually enable Client Success to create their own content. It just helped them help us—but we doubted it would actually be more efficient.

1. Content Design Decision Tree.png
 

Option 2:
Self service

 

So, what would  it take to help Client Success create content our team felt comfortable with? Well, they’d need a flexible design that was hard to mess up, and specific instructions on how to write like Collective Health. And that’s what we created. The one-pager templates offer several types of templates to choose from, with info on each about what kind of message should go in that area. It’s like paint-by-numbers for content design. 

Screen Shot 2020-12-06 at 12.11.27 AM.png
Screen Shot 2020-12-06 at 12.13.18 AM.png
Screen Shot 2020-12-06 at 12.13.37 AM.png
Screen Shot 2020-12-06 at 12.14.04 AM.png
Screen Shot 2020-12-06 at 12.11.42 AM.png
Screen Shot 2020-12-06 at 12.13.27 AM.png
Screen Shot 2020-12-06 at 12.13.47 AM.png
Screen Shot 2020-12-06 at 12.14.11 AM.png
 

Seeing it in practice

 

Our first big experiment with these new tools happened during Collective Welcome’s Open Enrollment. We wanted to create 9-12 one-pagers with detailed content on specific topics that clients could send to members. But with my plate full creating other Open Enrollment materials, we organized subject matter experts, and were delighted with the results.

Screen Shot 2020-12-06 at 12.16.46 AM.png
Screen Shot 2020-12-06 at 12.17.06 AM.png
Screen Shot 2020-12-06 at 12.17.24 AM.png
Screen Shot 2020-12-06 at 12.16.56 AM.png
Screen Shot 2020-12-06 at 12.17.15 AM.png
Screen Shot 2020-12-06 at 12.17.35 AM.png
 

Impact

The Content Design team’s JIRA queue has gone quiet. While still occasionally tapped for a final review, most content can actually be created and sent without oversight, leaving the team time and focus for their core craft and responsibility: designing products through the lens of words. 


Previous
Previous

All Hands: WFHDAP