The Content-Action Model origin story
Beyond the Core Content Model and into organisations, actions.
(An aside to the Content-Action Method for Web Systems post)
I started to use Core Content Model methods (first enshrined by Ida Aalen), and found them to be incredibly useful—but not quite right. The Content-Action Method for Web Systems took shape when I started to radically adjust the format and scope to suit the needs of our organisation and its diverse users and—wait for it—our strategy.
How is the CAM for Web Systems different?
The CAM for Web Systems was originally based on the Core Content Model idea (see Figure 1).
The CAM for Web Systems (in our experience) has proven very effective when workshopping new websites. (We also use the HEART Framework for new, more creative thinking.) The CAM for Web Systems has worked better for on-going maintenance, consensus building, evaluation and improvement of existing sites.
Advantages of the CAM
There are a few reasons why our CAM for Web Systems (built on the Model) works well for evolving existing sites:
- Database friendly: The CAM for Web Systems uses a less free-thinking format (i.e. a text and/or database record), so the information is richer for comparing with other records (and much easier to use forensically). The format lends itself particularly well to internal communication and arbitration.
- Interlinking: The framework is designed for internal cross-referencing, both within a CAM Record and across many of them.
- Wider focus: The CAM for Web Systems closes the loop on:
- evaluating success
- change over time
- user types
- organisational placement.
More on the CAM?
This post only discusses how the CAM compares to the Core Content Model method, for more about the CAM: read the overview of the Content-Action Method for Web Systems