Findings in this brief are drawn from two decades of fieldwork and data analysis, working alongside hundreds of manufacturers and watching their operating models evolve through every stage of this arc.
What this brief argues, in six lines.
- 01Every department in a manufacturer runs projects, Marketing, IT, R&D, Maintenance, Engineering, Quality, HR. Most of it is collaborative, much of it is recurring, and a meaningful slice of it is cross-functional.
- 02How that work is run matures along a predictable four-stage arc: Hands-On Coordination, The Visibility Cliff, Operational Drag, and Project Operations at Enterprise Scale[5][6]. Tooling is the visible symptom at each stage, not the stage itself.
- 03Each stage has its own breaking point. In Tier 1, the work is invisible to anyone except the person running it. In Tier 2, cross-functional visibility collapses just as departmental discipline sharpens. In Tier 3, coordination cost eclipses work cost. In Tier 4, the board expects investor-grade program governance. The failure mode changes in kind at every threshold.
- 04The expensive failure isn't the work itself. It's the coordination around it: programs that slip on invisible handoffs, recurring work rebuilt from memory, approvals stuck in email, capacity allocated by gut feel, partners bolted on through workarounds.
- 05The payoff of a shared project operating layer is not just faster projects. It is leadership capacity freed from status reconstruction and firefighting, reallocated to strategic decisions that compound.
- 06Use the tier-by-tier framework to locate your organization, the interactive explorer to see the challenges and fixes at your stage, and the self-audit to benchmark your operating maturity against peers at your size.
Project work runs in every department. The tooling under it evolves on a predictable arc.
Marketing runs campaigns and launches. IT runs upgrades, integrations, and rollouts. R&D runs NPD and reformulations. Maintenance runs PMs, turnarounds, and reliability programs. Engineering runs capex and capacity projects. Quality runs audits, CAPAs, and document control. HR runs hiring waves and training rollouts. Most of this work is collaborative, much of it is recurring, and a meaningful slice of it is cross-functional[2][3].
How that work is run matures along a predictable four-stage arc. Early on, personal coordination holds everything together. As complexity grows, each department tightens its own operating model but the cross-functional layer goes dark. Eventually the cost of coordinating across functions outweighs the cost of the work itself, and a shared project operating layer becomes the only way through[5][6]. This brief maps the four maturity stages and the failure modes that show up at each one. Tooling is the visible symptom at every stage, not the stage itself.
Departments outgrow their tools but stay on them out of inertia, layering spreadsheets and email back on top to fill the gaps. The work gets done, but it doesn't land on time, on budget, or with the cross-functional coordination needed to compound across the company.
Four tiers of operating maturity, by employee count.
Each tier is defined less by headcount than by the operating condition of the average department and the inflection point that breaks it.
Hands-On Coordination
Personal relationships hold project work together across every department.
Project work in every function, Marketing, IT, R&D, Maintenance, Engineering, Quality, HR, runs on personal coordination. Department leads know each other, know the work, and hold the plan in their heads. The visible artifacts are spreadsheets, decks, and email threads, but the operating model is one person remembering what is in flight.
When a single person being out of office stalls work in three different departments because the project lives in their inbox.
The Visibility Cliff
Departmental visibility is real. Cross-functional visibility has collapsed.
Each function has tightened its own operating model and can answer for its own work. The cross-functional layer has gone dark. Leadership can see inside any single department but cannot see across them, and cross-functional programs have no shared owner, plan, or status. The symptom is a sprawl of generic task tools, one per department; the underlying condition is that no shared operating layer exists.
When the leadership team realizes it is paying for six different project tools and still cannot answer what is in flight across the company.
Operational Drag
A PMO exists. Cross-functional coordination is now the constraint on strategic work.
An enterprise PMO or transformation office stands up, often as a small team reporting to the COO or CIO. Most departments have moved past spreadsheets and are running their own task tools well. The new problem is the cost of coordinating across them, programs that touch four or five functions take longer than the work itself warrants.
When the cost of coordinating across departmental tools exceeds the cost of standardizing on a shared one.
Project Operations at Enterprise Scale
Project work runs as an instrumented operating system. Reporting is investor-grade.
Project work is run as an enterprise operating system. Every department executes collaborative work on one shared layer, deep-domain systems (CMMS, PLM, MES, ITSM, ERP, sustainability disclosure) feed into it, PMO governance is standing, capital allocation runs on portfolio data, and strategic program status is a continuous input to investor and board reporting.
When a single bad strategic execution is a board-level event and reporting on the project portfolio is a standing input to investor materials.
Find your stage. See the challenges, the impact, and what fixes them.
Drag the slider to your employee count. The rest of this section reflects the project-management challenges most likely to be hurting your departments right now, with the corporate and team-level impact, and how a platform like Workzone resolves each one.
The Visibility Cliff
Departmental visibility is real. Cross-functional visibility has collapsed.
This is the most common stuck point. Departments have outgrown spreadsheets and each picked a tool that fits the depth of one function, Marketing on one, IT on another, Engineering in scheduling software, Maintenance in the CMMS, R&D in a third task tool, Quality on a SharePoint list. The within-function picture is sharper. The across-function picture is worse than it was at Tier 1, because the tools don't talk to each other and no two teams share a vocabulary. Leadership reporting becomes a manual reconciliation across tools, and cross-functional programs slip on handoffs no one can see.
Pick the function you care about most. The challenges below filter to the ones that department feels first. Pick All to see the full org-wide view.
Six different tools, no shared view
Marketing's tool tracks marketing work. IT's tool tracks IT tickets. Engineering's tool tracks engineering projects. None of them combine into a single picture of what the company is working on.
Leadership can ask any single department what is on its plate, but cannot see the whole picture without a manual rollup.
Cross-functional program owners spend half their week translating between tools and rebuilding the cross-tool view in Excel.
Land on a shared work-management layer that every department uses for collaborative project work, and keep specialized deep-domain tools (CMMS, PLM, ITSM) only where they are genuinely needed for that function's deepest work.
Workzone gives every function the same project workspace with department-tailored views, and rolls everything up into one portfolio leadership can actually use.
Score your operating maturity in 2 minutes.
Set your employee count, answer 12 yes-or-no questions distilled from the tier challenges above, and get a maturity score, your tier label, and the three highest-impact gaps to close first.
2000 employees · Tier 2 · The Visibility Cliff
Mark each statement yes if it is true today, no if it is not.
- 01Critical at T2
Every department (Marketing, IT, R&D, Maintenance, Engineering, Quality, HR) runs collaborative project work in one shared platform, not its own private spreadsheet or task tool.
- 02Critical at T2
Leadership has one portfolio view of every active project across departments, with sponsors, owners, status, and dependencies.
- 03Critical at T1
Requests for internal service functions (IT, Marketing, Engineering, R&D) come in through one front door with a structured brief, not Slack DMs and email.
- 04Critical at T1
Recurring programs (audit prep, line changeovers, NPD launches, software releases, plant turnarounds, onboarding) run from cross-functional templates, not memory.
- 05Critical at T2
Cross-functional projects (NPD, capex, ERP rollouts, sustainability programs) have one shared plan with a named owner per contributing function.
- 06Critical at T1
Reviews and approvals (capex, engineering changes, marketing assets, SOP revisions, change controls) flow through a structured workflow with online proofing and a per-version audit trail, not email.
- 07Critical at T1
Project files (artwork, drawings, SOPs, work instructions, plans) live attached to the project with versioning, not scattered across drives.
- 08Critical at T2
External partners (agencies, EPC firms, system integrators, contract manufacturers, consultants) work in the same project workspace as internal teams, with controlled access.
- 09Critical at T2
Department heads can show committed work versus team capacity in real time, by person and by function.
- 10Critical at T2
Leadership can see, on demand, which projects are on track, at risk, or slipping, with the late milestones, blocked tasks, and overdue approvals behind the status.
- 11Critical at T2
Dependencies between projects (an ERP cutover blocking a plant go-live, a packaging change blocking a product launch) are tracked in the system, not in a program manager's head.
- 12Critical at T2
A new employee in any department can land and contribute in their first two weeks because templates, owners, and current state are documented in the system.
- 13Critical at T3
When a project misses deadlines or budget, we can clearly identify the root cause of the variance.
- 14Critical at T3
We can accurately forecast project timelines, budgets, and resource needs before issues occur.
The operating layer that resolves these challenges.
Most of the failures above are not strategy failures and they are not depth-of-function failures. They are coordination failures at the cross-departmental, project layer: tools that don't talk to each other, recurring programs rebuilt from memory, approvals stuck in email, capacity allocated by gut feel, external partners bolted on through workarounds.
Project management software does not replace your CMMS, PLM, MES, ITSM, ERP, or sustainability disclosure platform and should not try to. It sits alongside them and runs the collaborative project work that wraps around them. The capabilities below are what platforms like Workzone deliver, mapped directly back to the tier-by-tier challenges above[5][6].
A shared project platform every department can use
One platform for collaborative project work across Marketing, IT, R&D, Maintenance, Engineering, Quality, and HR, with department-tailored views inside it. Deep-domain tools (CMMS, PLM, MES, ITSM, ERP) stay where they belong.
A single front door for project requests
Standardized intake forms with required briefs, automatic triage, and a status link the requester can check, for every internal service function.
Templated playbooks for recurring cross-functional work
Reusable cross-functional templates with named function owners, dependency wiring, and pre-set due-date offsets for every program that runs more than once.
Portfolio visibility across every department
Live portfolio view by department, sponsor, function, and program. The board view becomes a saved query rather than a quarterly reconstruction.
Online proofing and structured approval workflows
Sequenced reviews with online proofing, pinned markups on the asset itself, named approvers, deadlines, attestations, and a permanent audit trail of every version.
Capacity and resource planning
A forward view of committed work versus capacity by person and by function, so commitment conversations start from data.
Controlled external collaboration
Permissioned access for external partners so their work shows up in the same portfolio view as in-house work, with the same proofing and approval workflow.
Roll-up reporting across the portfolio
Standardized program status, milestones, and risks that aggregate from project to portfolio. Domain KPIs continue to come from CMMS, PLM, ERP, BI, and the sustainability platform.
Why we publish on manufacturing.
Workzone is project management software built for operations-heavy organizations, Marketing, IT, PMO, Engineering, R&D, Maintenance, and Quality teams running collaborative project work side by side. We have more than 23 years of real-world deployment experience and a 7-year average customer lifetime, focused on multi-site, multi-stakeholder organizations where work has to land consistently across many functions and many locations.
Process manufacturing, food, chemicals, CPG, is one of the categories where that focus matters most. These organizations have real cross-functional complexity, plant-level autonomy, an aggressive M&A and capex cadence, and investor-grade reporting pressure all running through every department's project work. Alongside, not inside, the deep-domain systems each function depends on.
We publish briefs like this one because the project-management conversation is one of the highest-leverage ones a manufacturing leader can have, and it is rarely had with the specificity it deserves.
See what an org-wide project layer looks like in Workzone.
Book a 30-minute walkthrough with a Workzone manufacturing specialist. We'll map the framework above to your current tier and show you how Marketing, IT, R&D, Maintenance, Engineering, and PMO teams at other manufacturers run project work side by side in one shared platform.
"We had people on multiple sites who needed to see materials and timelines, but we didn't have a single place to collaborate. As we scaled, we needed something to help us move faster and stay in sync. Workzone became that central hub across marketing, e-commerce, manufacturing, legal, supply chain, and regulatory. Now, any stakeholder can go into Workzone and see the status of a project, know what the next step is, and when the final materials are due. That kind of clarity reduces back-and-forth and keeps us on schedule."
Sources.
- [1]Consumer Brands Association: State of the CPG industry briefings. https://consumerbrandsassociation.org/
- [2]Deloitte: Manufacturing Industry Outlook on operating model and digital transformation. https://www2.deloitte.com/us/en/industries/manufacturing-industrial-products.html
- [3]McKinsey & Company: Operations and transformation insights for manufacturers. https://www.mckinsey.com/capabilities/operations/our-insights
- [4]Bain & Company: M&A and integration practice insights. https://www.bain.com/consulting-services/mergers-and-acquisitions/
- [5]Project Management Institute (PMI): Pulse of the Profession on portfolio and program management practices. https://www.pmi.org/learning/library
- [6]Gartner: Collaborative work management and strategic portfolio management research. https://www.gartner.com/en/information-technology/insights/program-portfolio-management