Work
7 min read
In this piece
A content system should reduce decisions, not originality
Content systems are usually built after production becomes painful.
Ideas live in several documents. Deadlines appear unexpectedly. The same feedback arrives at the end of every piece. Nobody knows which version is approved. Publishing depends on one person remembering the entire process.
So the team creates a system.
There is a calendar, template, workflow, naming convention, set of pillars, approval process, format library, and dashboard. The disorder improves.
Then a different problem appears.
Every post begins to sound the same. Every article follows the same shape. The content pillars become containers that must be filled. The team can produce consistently, but the work has less reason to exist.
This creates a false choice between creative freedom and operational discipline.
The choice disappears when the system standardises the right things.
Fix the rhythm; vary the idea.
A good content system reduces recurring coordination decisions so that the team can spend more attention on the judgment each piece requires.
Every piece contains two kinds of decisions
Content work mixes operational decisions with editorial decisions.
Operational decisions include:
where an idea is captured;
who owns the first draft;
which information the brief contains;
where files and versions live;
when review happens;
which checks precede publishing;
how the final link and performance notes are stored.
Editorial decisions include:
what is worth saying;
why it matters now;
which audience tension the piece addresses;
what point of view makes it distinct;
which example earns the claim;
what form gives the idea its strongest expression;
what the audience should understand or do afterwards.
Both types matter.
The waste appears when operational decisions must be reinvented and editorial decisions are predetermined.
A writer should not spend creative energy locating the approved product description or guessing who reviews a legal claim. They should spend it deciding which detail makes the argument credible.
The system should make routine coordination boring and meaningful judgment alive.
Calendars should hold commitments, not manufacture ideas
A content calendar is useful when it answers practical questions.
What is being produced? Who owns it? Which stage is it in? What event or audience need creates the timing? Which dependency could block it?
It becomes dangerous when empty dates create the strategy.
“We need something for Tuesday” is a production requirement, not an editorial reason. If the team fills the slot because the slot exists, frequency starts generating low-value ideas that must then be made presentable.
Consistency matters. An audience cannot build a relationship with work that appears once and disappears. A team cannot learn from formats it never repeats. Distribution rewards rhythm because people have more opportunities to encounter and remember the value.
But consistency should be defined at the system level.
The team can commit to a publishing frequency, response time, newsletter day, or campaign sequence. Individual pieces still need a reason.
At Unshackled, consistent social calls to action, useful resources, referrals, testing, and reader feedback formed part of the newsletter growth system. The repeatable rhythm mattered because it gave relevance and learning somewhere to accumulate.
The calendar coordinated that rhythm. It did not make any generic piece useful merely by assigning it a date.
Pillars should create a field, not a quota
Content pillars are intended to create focus.
A product company might write about the customer problem, practical education, product use, industry change, and stories from the community. A creative studio might cover strategy, design decisions, Webflow practice, client operations, and the realities of building.
These fields help a team recognise relevant ideas.
They become restrictive when the plan requires equal output from each category regardless of what the organisation genuinely knows or what the audience currently needs.
The pillar becomes a quota.
Better pillars are questions the brand is equipped to explore repeatedly:
What makes a complex service easier to trust?
How do design and content decisions affect one another?
Which website choices determine what a client can maintain?
What does professional creativity require after inspiration?
Questions generate different forms of insight while preserving a coherent territory.
Categories classify finished work. Questions provoke new work.
Templates should preserve requirements, not phrasing
Templates are excellent at preventing omissions.
A case-study brief can require context, problem, constraints, decisions, evidence, contribution, and boundaries. A newsletter template can preserve a recognisable reading rhythm. A social brief can include the core idea, audience, source, format, and call to action.
The template becomes mechanical when it dictates the same rhetorical sequence regardless of material.
Not every case study is a heroic transformation. Not every article needs a numbered framework. Not every video needs an identical hook. Not every client story should begin with “the challenge.”
The structure should reflect what the material needs to prove.
Use templates for invariants:
factual source;
purpose and audience;
required review;
accessibility and format checks;
ownership and status;
metadata needed for publishing;
evidence boundaries.
Use flexible patterns for expression:
narrative;
comparison;
explanation;
interview;
visual sequence;
technical guide;
concise observation.
The system remembers the responsibilities. The creator chooses the form.
Approval should protect risk, not hierarchy
Review is another place where useful systems become heavy.
When everyone can comment on everything, feedback expands to fill the available authority. A subject expert adjusts tone. A brand reviewer rewrites technical detail. A senior stakeholder changes a headline because it feels unfamiliar. The creator resolves conflicting preferences rather than improving the work.
Assign review by risk.
The subject expert checks accuracy and missing context.
The legal or compliance reviewer checks consequential claims.
The editor checks argument, clarity, and voice.
The brand owner checks fit with the larger position.
The channel owner checks format and distribution requirements.
Not every piece needs every review.
The system should state who decides when feedback conflicts. Otherwise “approval” becomes an unbounded search for no remaining objection.
Clear review roles protect originality because unusual choices are evaluated by relevant criteria instead of general discomfort.
Measurement should create questions
Content systems often become more mechanical when performance data arrives.
One format receives strong engagement, so it is repeated. A headline style earns clicks, so every headline adopts it. Short posts outperform long ones in a narrow window, so deeper work is deprioritised.
The number is real. The conclusion may be too broad.
Measurement should tell the team where to investigate:
Did the topic matter or did the format improve distribution?
Did attention come from the intended audience?
Did the content help a useful next action?
Is the effect repeatable or tied to timing?
What did qualitative replies reveal that the aggregate number cannot?
Did the high-performing piece strengthen or distort the brand’s promise?
A metric is a signal inside a content system, not the editor of the next piece.
Use data to refine relevance, sequence, and distribution. Do not allow the most measurable behaviour to define the whole value of the work.
The objection: originality is not always necessary
Correct.
Some content is functional. Release notes, event reminders, product documentation, policy updates, onboarding instructions, and recurring reports benefit from predictable form. The audience does not need an original interpretation of every operational message.
The system should make those pieces efficient and accurate.
The mistake is applying the same production logic to idea-led work.
An article, campaign concept, brand narrative, or creative series must give the audience a reason to pay attention beyond the fact that the organisation published again.
Different content has different novelty requirements.
Standardise heavily where predictability helps the user. Preserve exploration where the idea is the value.
Build the minimum useful content system
Before adding another template or status field, map the decisions in one content cycle.
Mark each decision as one of four types:
Fixed: the same answer should apply repeatedly, such as file location or required source attribution.
Role-based: the answer depends on ownership, such as who approves a regulated claim.
Conditional: the answer depends on content type or risk, such as whether legal review is necessary.
Creative: the answer must be made for this piece, such as its angle, structure, image, or closing action.
Automate or document the fixed decisions. Assign the role-based ones. Create simple rules for the conditional ones. Protect time and authority for the creative ones.
Then remove any step that does not improve accuracy, usefulness, consistency, risk control, or learning.
The result may be a calendar, brief, workflow, library, and review checklist. It may also be much smaller.
The quality of a content system is not measured by how comprehensively it describes production.
It is measured by whether useful work can move through it repeatedly without losing the judgment that made the work useful.
Efficiency should return attention to the idea, not replace it.
Fix the rhythm.
Let each idea earn its own form.