Have you ever struggled with a content model that just didn’t work for your team?
After talking to many digital teams last month, I’ve noticed a common problem: content models built by developers without input from editors. These systems might be technically impressive but often leave editors stuck with confusing, complicated workflows, making content creation a frustrating experience.
These conversations got me thinking—how do we prevent this?
The solution lies in a more collaborative approach to content modeling, one that brings developers, editors, and product owners together from start to finish. This idea led to the creation of Collaborative Content Modeling (CCM).
In this post, I’ll walk you through the CCM approach: why it matters, how it works, and the benefits it offers for everyone involved.
The Challenge: Misaligned Content Models
Let’s face it—when developers design content models in isolation, they often prioritize technical requirements over usability. Editors end up dealing with overly complex systems, confusing field names, or irrelevant options that slow them down. It's like trying to find your way in a maze without a map—that’s how editors feel.
This misalignment causes problems for everyone:
- Editors get frustated: They struggle to use a system that doesn’t fit their needs.
- Developers get overwhelmed: They spend too much time fixing issues and handling support requests.
- Team miss business goals: Content production slows down, and quality suffers.
The solution? Collaboration. Let’s start working together.
The Solution: Collaborative Content Modeling (CCM)
Collaborative Content Modeling bridges the gap between developers, editors, and product owners. It’s a simple framework built around three key stages: Design, Implement, and Check. This approach ensures content models are usable for editors, scalable for developers, and aligned with business objectives.
