Maturity is not the number of tools a team owns. It is the degree to which important decisions, versions, permissions, delivery evidence, measurement definitions, and recovery paths remain dependable when volume or risk increases.
Use the assessment below as a facilitated diagnostic. Score the workflow that exists today, not the process described in a slide deck. Ask for recent evidence: a brief, approval record, failed publish, report definition, or automation permission decision.
The eight dimensions
The assessment covers strategy, evidence, channel adaptation, approval and version control, publishing verification, analytics definitions, incident recovery, and automation or agent permissions. Each dimension is scored from zero to three.
A zero means the work is mostly implicit or absent. One means individuals use an informal practice. Two means the team has a repeatable workflow with named ownership. Three means the workflow is measured, governed, and improved from evidence.
The maximum score is 24. The total is useful for orientation, but the weakest dimensions matter more than the average. A team with polished strategy and no publishing recovery still has a real operational failure point.
How to score honestly
Choose the lowest level that can be demonstrated consistently across representative campaigns. Do not award a three because one senior person can rescue the process manually. A mature capability survives absence, handoff, higher volume, and an unusual failure.
Invite people from strategy, creation, review, publishing, community, analytics, and systems. Differences between their scores are evidence. If creators believe approval is clear while reviewers believe versions are frequently confused, inspect recent records before agreeing on a number.
Write one example beside every score. This turns the result into an auditable snapshot and makes a later reassessment meaningful.
Interpret the maturity levels
Scores from 0–7 are Reactive: outcomes depend on individuals and recovery begins after problems become visible. Scores from 8–14 are Repeatable: common work follows a recognizable pattern, but exceptions and evidence remain inconsistent.
Scores from 15–19 are Controlled: ownership, versions, permissions, delivery evidence, and definitions are generally dependable. Scores from 20–24 are Adaptive: the team can govern automation, learn from incidents and results, and change the workflow without losing control.
Do not use the level as a badge. A high score can still hide one severe weakness. Prioritize dimensions that combine low maturity with high campaign risk or frequent operational pain.
Turn the result into a 30-day plan
Select no more than two weak dimensions for the next cycle. Define an observable change, owner, evidence, and review date. For example, replace “improve approvals” with “every material-risk post records one approved version, final approver, invalidation rule, and decision time before scheduling.”
Prefer small controls that improve the operating record: a stable campaign ID, source field, version rule, delivery-state vocabulary, metric definition, recovery owner, or permission boundary. Integrate them into existing work before buying another tool.
Reassess after four to eight weeks using new evidence. If the score rises without the workflow becoming easier to inspect or recover, the scoring standard may have become too generous.
Assessment checklist
- Score current demonstrated behavior, not intended policy
- Include representatives from the full workflow
- Record one recent example for every dimension
- Inspect disagreements instead of averaging them away
- Prioritize the weakest high-risk dimensions
- Choose at most two improvements for the next 30 days
- Assign an owner, evidence, and review date
- Reassess against the same scoring standard
The interactive assessment is rendered below. Pair the result with the operations benchmark framework and the operating cost calculator when building the improvement case.
