Project Overview
This case study examines the comprehensive content strategy and management system for a large federal agency’s human resources (HR) website serving more than 600K employees. The project involved establishing standardized processes for managing 500+ web pages in a heavily regulated environment, instituting a rolling editorial calendar, processing routine and complex content change requests daily, creating new web pages, archiving outdated web pages, and ensuring compliance with federal accessibility requirements and style guidelines while coordinating across multiple departments and stakeholder groups and maintaining a comprehensive change record.
Client
Large federal agency
Project
Manage the content for a newly updated human resources website
Scope
Continually update 500+ web pages across multiple HR domains while maintaining brand voice and tone, adhering to the style guide and design templates.
Project Brief
The agency’s HR website serves 600,000+ federal employees. 25 content owners across 14 HR divisions provide initial text, and the content managers refine the text and ensure it complies with all accessibility requirements as well as brand and style guides. Content managers processed 1,200+ formal change requests annually.
Problem
The agency’s old HR website had grown organically over many years, resulting in uneven content quality, outdated information, walls of text, and fragmented user experience.
Key Challenges
Process Inefficiency: No standardized workflow for content updates, leading to delays and incompatibilities
Quality Control Issues: Style guides and design templates applied erratically across pages
Compliance Risks: Failure to meet Section 508 accessibility requirements and federal plain language standards
Stakeholder Coordination: Inconsistent communication among content owners, developers, and UX teams
My Role
As one of three content managers, I served as the team editor in addition to processing content changes, participating in all phases of content management beginning before release 1:
- iterating and updating the project style guide and design template;
- writing and iterating a comprehensive change request submission guide for content owners;
- reviewing content change requests for adherence to project style guides and federal requirements, editing as needed;
- ensuring that content met design and technical requirements before forwarding to the design team;
- quality-checking mockups before delivering to the dev team;
- establishing and maintaining naming conventions, version control, and content change history;
- setting up and following the editorial calendar; and
- tracking the progress of change requests from receipt to delivery to the dev team.
Methodology & Implementation
Phase 1: System Implementation (Months 1-6)
Content Management Infrastructure
- Established a collaborative 4-team structure and workflow
- Designed a centralized tracking system
- Instituted version control protocols with clear naming conventions
- Developed an editorial calendar for planned updates and reviews
Quality Control Framework
- Established metrics tracking for process improvement
- Established component library integration with approved design patterns and templates
- Created consistent design template application across all pages using US Web Design System (USWDS) framework standards
Phase 2: Process Standardization (Months 7-12)
Guiding Documents
- Created a comprehensive executive change request guideline that cleared roadblocks, log jams, and redundant work
- Reviewed, standardized, updated, and synched the style guide and design template
- Refined the change tracking system and version control procedures
Phase 3: Process Optimization (Months 13-18)
Workflow Iteration and Improvement
- Integrated multi-layered compliance checking for Section 508, WCAG 2.1 AA, USWDS design standards, and the Plain Language Act
- Developed Section 508 compliance documentation and testing protocols for all content updates
- Implemented automated accessibility testing tools and manual WCAG validation procedures
- Implemented batch processing for similar content types
- Performed periodic process retrospectives and iteration
Results & Outcomes
Quantitative Improvements
Key Metrics Summary
- 500+ web pages maintained with consistent quality standards
- 1,200+ change requests successfully processed annually with 98% on-time completion
- 65% reduction in content errors
Processing Efficiency
- Average change request processing time reduced from 18 days to 5 days
- Average content management time reduced from 3 days to 1 day
Qualitative Improvements
Content Quality Enhancement
- Established consistent voice and tone across HR communications
- Enhanced user experience through consistent navigation and design elements
- Strengthened brand consistency across digital properties
Collaboration Effectiveness
- Improved communication among content managers, UX designers, and developers
- Enhanced project visibility and accountability through centralized tracking
- Established clear escalation procedures for complex requests
Key Success Factors
Stakeholder Engagement
Strong leadership support and training ensured buy-in from content owners. Regular feedback sessions and iterative improvements maintained momentum throughout implementation.
Process Documentation
Detailed procedures provided clear guidance for both routine and exceptional situations, reducing dependency on institutional knowledge.
Lessons Learned
Implementation Insights
Change Management: The phased rollout of a minimal viable product proved more effective than organization-wide implementation due to our managed and limited change schedule.
Communication Strategy: Regular updates to leadership, collaboration with content owners, and transparent progress reporting built confidence, trust, and support.
Process Refinements
Flexibility Balance: While standardization improved efficiency, maintaining flexibility for unique requirements proved essential for meeting user needs and content owner demands.
Automation Limits: Human judgment remains critical for complex editorial choices.
Stakeholder Expectations: Clear communication about realistic timelines prevented frustration and improved relationships.
Technology Integration
Enterprise Tools and Automation: Leveraging existing enterprise tools while implementing specialized accessibility testing software and component libraries reduced adoption barriers and integration complexity.
The integration of automated WCAG validation tools into the content and design workflow prevented accessibility issues before publication, improving user experiences and reducing rework.
Conclusions
The content management system implementation successfully transformed a fragmented, inefficient process into a streamlined, compliant, and scalable operation. The standardized approach to change requests, combined with robust quality control measures and effective stakeholder collaboration, delivered measurable improvements in both efficiency and content quality.
This project demonstrated that systematic process improvement supported by appropriate technology and comprehensive training can significantly enhance content management capabilities even in complex organizational environments with multiple stakeholders and strict compliance requirements.
HR image attribution: Easy-Peasy AI under Creative Commons license
Thank You