Question 1

Bottlenecks hidden in everyday work

Accepted Answer

Most editorial teams will recognise the pattern: Manuscripts circulating as Word documents in long e-mail threads. Versions labelled "final_v3_revised_final.docx". Project status requiring input from several people. Knowledge of project status residing primarily in the heads of a few key individuals. If you are working in this environment, you have probably experienced how quickly visibility can be lost – even in relatively straightforward projects. None of these elements are inherently problematic. But taken together, they create a workflow where progress depends on manual coordination rather than a structured process. As a result, even small disruptions – a holiday, a busy period, a misunderstanding – can ripple through the entire chain.

Question 2

Communication as a hidden constraint

Accepted Answer

One of the most underestimated challenges in editorial workflows is communication. Collaboration between editors, authors, and proofreaders is inherently iterative. It requires continuous dialogue, feedback, and refinement. But when communication is spread across e-mail, document comments, and various messaging tools, fragmentation is almost inevitable. It becomes unclear: Which version is the latest.  Which changes have been approved. Who is waiting on whom. When these questions cannot be answered quickly, progress slows – not because the work itself is difficult, but because coordination is.

Question 3

Why do publications get delayed?

Accepted Answer

Delays rarely stem from a single major issue. Instead, they are the result of many small delays accumulating over time: Waiting for feedback. Unclear prioritisation across projects. Limited visibility into progress. Dependence on individuals with critical knowledge. You may recognise the situation where a project only begins to slip when it is already too late to recover without placing additional pressure on everyone involved. Without clear visibility, it becomes difficult to identify issues early. Bottlenecks are often discovered when deadlines are already under strain. The result is a stop-start process rather than a steady flow.

Question 4

Dependence on key individuals

Accepted Answer

In many publishing houses, a small number of experienced individuals "hold everything together". They know where projects are in the process, who is waiting for input, and what the next step is. This is a strength – but also a vulnerability. When knowledge of workflow and status is not systematised but resides with individuals, organisations become less resilient. Scaling becomes harder, takes longer, and the risk of errors increases.

Articles for publishers

Go back to Insights

News

Customer cases

Latest articles

Schilling ApS