CDC Digital First Editor
The Digital First Editor (DFE) is an ongoing project designed to streamline and standardize CDC's public health communication strategies.
Duration
2021-Present
Role
UX/UI Designer
Involved
#
Interaction design
#
Wireframing
#
Documentation
#
UI Design
#
Research
The Problem
How do you create a system that allows thousands of users to write, collaborate, review, and publish content across hundreds of programs, initiatives, and policies?
The DFE is a colossal effort that requires an understanding of:
CDC web content writing and clearance processes
All the different roles and functions within the content writing process
Content patterns and outlines for 500+ different topics
Scores of CDC program and site structures
Standardizing content while still providing enough flexibilty for edge cases
Navigating the difference between politically driven needs vs. actual user needs
Ensuring that the system would integrate with existing legacy systems
(Not an exhaustive list)
The Solution
As an ongoing product intended to support CDC digital communications indefinitely, the DFE has now become a series of enhancements with no singular solution in sight.
Spearheaded the first major iteration
When I first got assigned to the DFE project in 2022, the team had just released the MVP (minimum viable product) and was in the process of designing the first major iteration. Using my previous experience from a different project I was working on at the time, I suggested several enhancements including building out separate screens and introducing a left navigation bar to start shaping the DFE into a true workspace for content management.
We focused on 6 major screens that users would need to navigate:
Page editing
File management
Publishing
Site mapping
Site management
User management
I quickly turned what started off as a rudimentary interface into a full system with several tabs and complicated interwoven elements. The release schedule was ambitious and each sprint involved a lot of moving parts. Communication and documentation were paramount, as decisions and requirements continuously and quickly changed.
The Impact
Improved documentation and reduced validation fails
Over the course of the project, I learned and adapted to our team's working style and expectations. I noticed that given the rush of each sprint and other limitations, mockups weren't being followed completely which confused QA when they needed to validate production with the stated requirements.
By developing a more detailed method of documentation, I was able to reduce the amount of failed QA validations, allow transparent communication, and collaborate more closely with devs to learn about what's "under the hood," so that I could better understand how to adjust future designs to fit the current architecture. By doing so, I also reduced nearly all instances of unnecessary rework moving forward.
Established an original design system
The DFE UI was built entirely from scratch with no existing design system. Since its inception, I have been continually polishing and documenting a more official design system that aims to keep the system scalable and modular enough for unforeseen pivots.
