Many newsrooms have an editorial workflow in theory. In practice, they have a collection of individual habits, email threads, and spreadsheets that more or less hold things together, until the cracks become impossible to ignore. 

The gap between the two is rarely obvious until something goes wrong: a story gets published twice, a deadline is missed because it changed in one place but not another, or an editor spends an afternoon chasing updates that should have been visible from the start. 

The challenge isn't a lack of effort or intention. It's that planning is distributed rather than centralised, which means it's never fully visible to everyone who needs to see it. And when visibility breaks down, alignment follows. This is exactly the problem that editorial workflow software is designed to solve by connecting the tools that already exist. 

When Planning Is Invisible, Problems Are Predictable 

The warning signs tend to be consistent across newsrooms regardless of size or structure. 

Story ownership becomes unclear during production. Teams inadvertently publish overlapping or duplicate coverage. Planning is tracked across spreadsheets and emails that only some people have access to. Coordinating across platforms or brands requires constant manual follow-up rather than a shared system anyone can check. 

At Mediengruppe Pressedruck, Alexander Sing described the reality before introducing a structured planning tool: coordination relied on "spreadsheets, calendars, and constant follow-ups" just to stay aligned. It worked until the volume and complexity of their output made the gaps impossible to manage. 

Heise Medien experienced the same pattern across their portfolio of publications. Without a central newsroom management system, different editorial teams would occasionally release articles on the same topic at the same time. As Jan Mahn, Deputy Editor-in-Chief at Heise Medien, put it: 

"In the old world, every part of our team was working on their own brand and did their own planning, and sometimes we released the same topic out of two editorial teams." 

This is what a distributed workflow looks like at scale. Everyone believes they are on track. The problem only becomes visible after the fact. 

A Calendar Is Not a Workflow 

Many newsrooms mistake a shared calendar for an editorial workflow management system. The distinction matters. 

A calendar tells you when something is due. A structured editorial planning system tells you what is happening, who is responsible, what stage it is at, and how it connects to everything else in production. Those are different things and conflating them is often where the visibility problem starts. 

What most newsrooms need is not a better calendar. They need a connected system where planning, production, and publishing are part of the same process, rather than three separate activities managed in three separate places. 

That is the shift Heise Medien made, and the difference it produced is worth examining in detail. 

How Heise Medien Built a Connected Workflow 

Heise's transformation was not primarily about adopting new software. It was about using editorial workflow software to make their actual workflow visible and shared across teams. 

The starting point was integration. Heise connected Kordiam with their CMS tools, InterRed for online publishing and Xpublisher for print, creating a two-way flow between planning and production. When a layout artist updates a story's status, editors see it immediately. When a deadline changes, it changes everywhere. The workflow becomes a single shared reality rather than a set of parallel versions maintained by different teams. 

This solved the timing and duplication problems directly. With full visibility across publications, the situation Jan Mahn described, where two teams independently publish the same story, becomes structurally impossible rather than just unlikely. 

The second change was bringing performance data into the planning process. Heise integrated Upscore audience analytics directly into their Kordiam planning views, so editors can see metrics like article views and conversions without switching systems. Data that previously arrived as a post-publication report now informs decisions before they are made. 

As Nina Berger from Upscore described it: 

"The most valuable insights are the ones that support real decisions, in real time." 

The goal was not better reporting after the fact. It was more audience-focused planning, clearer editorial priorities, and faster feedback loops for editors and writers. 

Read more about Heise’s data driven strategy here. 

What a Structured Workflow Actually Changes 

The practical impact of this kind of system is less dramatic than it sounds, and more valuable than it appears. 

Editors stop spending time chasing updates and start spending it on editorial decisions. Duplication disappears not because people are more careful, but because the system makes it visible before it happens. Performance data stops being a retrospective assessment and starts shaping what gets planned next. 

None of this requires a complete reinvention of how a newsroom works. It requires connecting the parts that already exist into a system where information flows automatically rather than manually. 

That is the difference between an imagined workflow and a real one. The stories still get published either way. But with the right editorial workflow software in place, the process behind them is visible, shared, and something the whole team can actually rely on, giving editors and writers the clarity to focus on what they do best.