For years, newsroom workflows were built around a simpler reality: one primary channel, one publishing rhythm, and a largely linear path from story creation to publication.
That model is gone.
Today's newsrooms publish across websites, apps, newsletters, push notifications, and more, often under multiple brand identities with their own editorial voices, audiences, and strategies. According to the Reuters Institute Digital News Report 2025, the number of online networks reaching more than 10% of global audiences weekly with news has grown from just two a decade ago to six today.
Each of those platforms runs on its own timing, demands its own formats, and comes with its own technical requirements. Each new brand or platform adds its own deadlines, asset specs, metadata rules, and performance feedback loops, all variables that multiply fast and quickly overwhelm workflows that were never designed to handle them. And because those requirements all have to be managed simultaneously, by multiple teams, often in different tools, what was once a linear process has become, at its core, a coordination problem.
Where Things Actually Break Down
The problems that come with multi-brand and multi-platform publishing rarely announce themselves as structural failures. They show up as small, recurring friction: a deadline missed because it was updated in one system but not another, a story published twice because two teams were planning independently, an editor making decisions based on information that was already out of date.
Jan Mahn, Deputy Editor-in-Chief at Heise Medien, described exactly this when reflecting on how their teams used to work across the company's different magazine titles:
That's not a people problem. It's what happens when planning is fragmented across brands and channels.
At scale, the consequences compound. Before jambit built a unified middleware for Madsack's Redaktionsnetzwerk Deutschland (RND), editorial teams across more than 30 regional brands were managing three separate systems: Kordiam for planning, Arc XP for digital publishing, and Eidos Media for print. Data had to be entered manually across all three. When something changed in one system, it didn't carry over to the others. As Robert Müller from jambit described it:
Multiply that across 30 regional newsrooms, across digital and print deadlines and the cost becomes significant. Not just in errors, but in the editorial energy spent managing information instead of producing it.
This is the core problem multi-brand and multi-platform publishing creates: not too much content, but too little shared visibility across the systems and teams responsible for it.
A Different Kind of Coordination
The newsrooms getting this right are rethinking how planning and publishing relate to each other.
The core shift we're seeing is that planning and publishing can no longer operate as sequential steps. They need to function as a single connected system that serves as a live, shared source of truth for every team and every brand involved.
That changes a few things in practice.
Integrated systems. When planning, publishing, and asset management talk to each other, the friction of switching between tools disappears. Jambit built exactly this for Madsack's platform, a shared publishing infrastructure serving more than 30 regional newsrooms across Germany. By connecting Kordiam, Arc XP, and Eidos Media through a single middleware layer, any update made in one system carries automatically to the others. Deadlines, statuses, author assignments, and circulations stay consistent across digital and print without anyone having to re-enter them.
Sternwald took a similar approach with their content operations platform Hugo, integrating it directly with Kordiam so that when a story is created, a corresponding asset collection is automatically generated in Hugo. Editors can search the DAM semantically from within Kordiam, pull relevant images and articles into the story without leaving their planning tool, and have assets uploaded by external reporters flow straight into the right collection. As Bastian Metz, Managing Director of Sternwald, puts it: "You don't have the breaks between systems anymore."
Real-time synchronization. When one part of the workflow moves forward, every connected team sees it immediately. That means fewer handovers, fewer errors, and faster execution.
Output-aware planning from the start. Planning stops being about assigning stories and starts being about preparing content for multiple destinations. At Madsack, editors can now trigger the creation of a structured "smart" article.
Smart articles, based on the Smart Brevity format, are concise, visually structured versions of longer stories. Editors can generate them in Kordiam using templates and linked tasks. Smart and in-depth articles are automatically linked, helping readers and newsroom staff navigate between formats. Newsletter production also became faster. Editors tag smart articles in Kordiam with a newsletter category and edition date. This is a vast improvement from the time when editors hunted for the content manually across systems. Content is designed once and distributed across brands and channels.
Timing Is Also a Coordination Problem
Even something as seemingly simple as when to publish becomes complicated when you're managing multiple platforms and multiple brands. In a single-channel world, where timing was mostly operational, there was one key question: "When is the print deadline?" Across brands and platforms, it requires active coordination between teams, systems, and audience expectations.
Gregor Landwehr, associate manager at Highberg and co-lead of the Drive initiative, a data-sharing group of around 30 German-speaking publishers, has spent years studying how audiences actually behave across days and times. The patterns are consistent: users want context and news updates in the morning, more inspiring or diverting content at lunch, and something different again in the evening. Those needs also shift across the week. Monday morning audiences, easing back into the working week, want lighter content. Friday afternoons skew toward weekend planning and help-oriented stories.
His argument is that digital publishers need to treat this the way linear TV has for decades: plan content deliberately to meet audience expectations at predictable times and build habits as a result.
"Planning means that my product has to offer the right content which matches what my audience expects."
That level of coordination is only possible when planning, publishing, and performance data are part of the same connected system.
The Coordination Problem Is Solvable, but Not with More Tools
Multi-brand and multi-platform publishing has exposed a structural gap in how most newsrooms work: planning and publishing were never designed to talk to each other. Adding more brands and platforms made that gap impossible to ignore.
The newsrooms closing that gap aren't doing it by hiring more coordinators or running more alignment meetings. They're changing the model itself by connecting planning and publishing into a single system that keeps every team across every brand working from the same real-time information. Newsrooms like Heise are already seeing the result: less duplication, fewer errors, and a workflow that can keep pace with the complexity.
That's the real shift. Not more output, but more control over how it all fits together.
