Content Optimization & Operations

Editorial Workflow Design

Design a production path with clear states, owners, entry criteria, exit criteria, and an exception route for work that does not follow the easy case.

Editorial Workflow Design follows real content from request to publication, identifies the handoffs and queues causing delay or rework, and turns those findings into a workflow the team can use in its existing tools. You walk away with documented states, owners, and service levels, tested against a hard case and configured in the tools the team already uses.

Trace the editorial workflow
Production board showing content moving through request, draft, review, and publish states

Some of the 500+ brands we've worked with

See all references
  • Zorlu PSM
  • Red Bull
  • Yemek.com
  • Onedio
  • AVVA
  • HDI Sigorta
  • Ekol
  • Amazon
  • BMW
  • Shell
  • Hyundai
  • PepsiCo
  • Decathlon
  • MediaMarkt
  • Bayer
  • Sanofi
  • EY
  • KPMG
  • GE
  • 3M
  • Domino’s
  • Lexus
  • Trendyol
  • Hepsiburada

How we run it

How observed work becomes a usable workflow

The process begins with real content traces, separates controls from inherited habits, defines usable states, tests difficult cases, and checks adoption after rollout.

  1. Trace real pieces from request to publication

    We follow a representative set of real pieces from request to publication and record each handoff, queue, wait, and rework loop. That observed path takes precedence over a process recalled from memory. The sample determines what the map reveals, so a strategist selects the real pieces to trace.

    A map of real states, queues, and friction points, as opposed to the process on paper.

  2. Separate necessary controls from inherited steps

    Some stages manage a real editorial, legal, or publishing risk. Others remain only because the team once worked differently. We document the reason for each step before keeping or removing it. Keeping or cutting a step remains the strategist’s decision after its purpose has been documented.

    A list of steps worth keeping, with a reason for each, and steps worth cutting.

  3. Define states, owners, and transition criteria

    For every state, we define the conditions for entry, the accountable owner, and the conditions for exit. A piece should not remain in a queue because nobody knows what happens next. The workflow owner signs off on who owns each stage before it becomes the default.

    A workflow blueprint with states, owners, and service levels attached.

  4. Create references for the moment of use

    We turn states and criteria into concise templates and reference material attached to the work itself, where people will actually see them. An editor approves the reference material before anyone is expected to use it.

    Lightweight templates and reference material tied to each state.

  5. Test the workflow against difficult cases

    We test the proposed flow with an urgent request, a rejected draft, and a localization handoff. The workflow also needs an explicit exception path for cases outside the default sequence. The strategist weighs the predicted queue against the team’s capacity and risk tolerance before accepting the design.

    A tested blueprint with an explicit exception path for cases that don't fit the default flow.

  6. Configure the flow and check adoption

    We configure the workflow in the team's existing tools, train people on both the default and exception paths, and then observe whether the new states are being used. The workflow owner sets the review date and judges whether adoption stuck or just got filed away.

    A live workflow, an adoption check, and a review date.

The evidence does not choose the workflow

Time in each state, recurring handoff rework, and likely queues under heavier volume can all be analyzed with agents. The result gives the strategist better evidence, but it cannot say whether a control justifies the friction it creates. That decision depends on the team’s capacity and risk tolerance, and it determines which stages stay, change, or disappear.

What you get

What you receive with the new workflow

The package includes the current-state evidence, the future-state blueprint, and the adoption measures used to see whether the change took hold.

  • a workflow process diagram

    Observed current-state map

    A record of the states, queues, handoffs, waits, and rework loops observed across real pieces of content.

  • a governance charter document

    Future-state workflow blueprint

    The proposed states, accountable owners, entry and exit criteria, service levels, and exception route for non-standard work.

  • a measurement note with a small trend line

    Workflow adoption tracker

    The measures and review date used to confirm whether the team follows the new flow in day-to-day work.

We call it done when: the states, owners, and service levels are documented, tested against a hard case, and the team is actually using it.

Who it fits

When handoffs keep slowing editorial work

This method addresses the operational path a piece follows through the team. Policies and decision rights belong to Content Governance.

A good fit when

  • Drafts keep slowing at handoffs between writers, experts, legal, and publishing, so queues and rework appear without one visible owner.
  • A specific piece sits in the team's tools, but nobody can see its current state, accountable owner, or next action without reconstructing the history.
  • The process on paper looks orderly, yet real pieces follow different queues and handoffs, so you want the workflow built from observed work.

Better handled as other work when

  • You need to define policies and decision rights rather than the day-to-day production path. That is Content Governance.
  • More approval stages are the goal even though no observed delay, rework loop, or editorial risk shows what those stages would control.
  • The current state may be documented, but the team will not change its states, owners, or exception path once the map shows where work stalls.

People who write and ship this content

Some of these consultants write the pages themselves. Others plan distribution or check how a piece performs once it's live, so the team below covers more than one stage of the work.

Content we've produced on this topic

Articleby Didem HimmetliVideo Marketing at 9 Steps

Tools we use

Tools behind this work

  • Notion

    the reference page a contributor opens at the exact moment a state needs one

  • Asana

    the configured states and transition rules a real draft moves through

  • Trello

    the lightweight board pick for a smaller team that finds Asana too heavy

  • Airtable

    the trace log that maps one draft's real path before the new workflow is designed

Start the work

Find the handoff that keeps holding work up

A representative set of recent pieces is enough to begin. We trace their handoff history, show where ownership or momentum was lost, and use that evidence to propose the new flow.
Talk to a Content Marketing specialist
Two people shaking hands on the start of the work

Before we start

Frequently Asked Questions

Is workflow design the same as choosing a project management tool?

Tool selection comes after the states, owners, criteria, and exception path are clear, and we then configure the workflow in a tool the team already uses effectively.

How long does current-state mapping take?

Timing depends on the number of pieces traced and the complexity of their handoffs. We prefer a close view of representative cases to a broad survey based on recollection.

What happens when a step appears unnecessary?

We document the evidence, purpose, and risk tradeoff for the step before anyone decides. Some steps turn out to be genuine dead weight. In one trace, a review stage came from an old team structure and was catching no real risk at all, so it was cut from the new flow. Others look redundant but are quietly the only thing preventing a specific failure. The people accountable for that risk make the final call, and the simulation shows them where a queue would back up before the change goes live.

Will this resolve unclear approval authority?

Not by itself. Workflow design governs how work moves, while Content Governance defines who may make each decision. The two are often designed together.