Production work moved between briefs, files, messages and review comments. The team could complete the work, but it was difficult to see where the next decision belonged.
Making content production easier to see and run
Content Production Console - internal workflow experiment

The real issue was a handoff model with no shared language for status, ownership or what ready meant at each stage.
I mapped production states, clarified ownership at each handoff and shaped a console around the decisions the team makes every day.
Situation
Production work moved between briefs, files, messages and review comments. The team could complete the work, but it was difficult to see where the next decision belonged.
What they thought was wrong
The first instinct was to build a more polished project tracker. That would have treated the visible interface as the problem.
What I found
The real issue was a handoff model with no shared language for status, ownership or what “ready” meant at each stage.
What was worth fixing
The experiment concentrates on the minimum workflow that makes the next action visible. It does not claim a production outcome until it is tested with a real team.
What I changed
I mapped the production states, clarified the ownership at each handoff and shaped a console around the decisions the team makes every day.
What I built
- A shared production view
- Handoff states and ownership rules
- A lightweight review workflow
- A visual direction for future internal tooling
Result
This is labelled as an experiment. Replace the evidence placeholder with an observed result after a live pilot.
Reflection
The strongest version would connect the production view to capacity and margin, so the team can see what a workflow decision costs as well as what it moves forward.
Implementation comes after diagnosis.
- A shared production view
- Handoff states and ownership rules
- A lightweight review workflow
- A visual direction for future internal tooling
What is known so far.

