Large Project Management: A Step-by-Step Guide for Creative Teams
Updated: Oct 2
TL;DR
A clear structure keeps large projects on time and true to their vision.
Scope comes before anything else: Scope of Work (SoW) prevents confusion and scope creep that derail most large projects.
Budget for revisions, not just materials: Most big projects go over budget because teams plan for one feedback round and end up with three, so contingency belongs in both the money and the schedule.
Ownership assignment over meetings: A shared tracker with one named owner per task reduces overlap and stalled work more than extra check-ins.
Large-scale art projects, whether it's a mural, a game asset pipeline, or a multi-artist illustration series, take more than talent to pull off. Alongside drawing, design, or technical skills, they demand planning, communication, and coordination among everyone involved. Without these, even a skilled team can run into trouble: a deadline slips, the budget runs over, scope creep sets in, or two people end up working on the same asset without noticing for days.
The real gap, in most cases, is that no one mapped the project before the work began.
This guide is for anyone tracking other people's deadlines, budgets, and deliverables on a large creative project, not just their own: creative project managers, studio leads, senior artists, and freelancers.
This article covers the step-by-step project planning process behind creative project management, from the role of a creative project manager to project management tools for artists – everything you need for effective project management for creative teams.
Table of Contents
Why Is Project Management Important? 8 Steps to Managing Large Art Projects Key Takeaways Frequently Asked Questions (FAQs) Author’s Bio
Why Is Project Management Important?
The combination of structure and flexibility sounds like chaos ready to happen, but you'd be surprised to know that it has more pros than cons. With some trial and error, you will find that your projects run smoothly and within the agreed timeline.
The cost of skipping structure isn't hypothetical. More than 11% of every dollar invested went to waste on average due to poor project performance, and teams that undervalue project management see roughly 67% more of their projects fail compared to teams that don't. Large creative projects carry the same risk, just with fewer industry benchmarks to point to.
Three causes repeat across almost all of this research: no documented scope, no clear ownership, and no consistent tracking once work is underway.
8 Steps to Managing Large Art Projects
Here's the process broken down, step by step:
Define the scope of the project
Plan and schedule the work
Budget and allocate resources
Manage the team and collaboration
Choose the right framework
Execute and monitor progress
Document and keep records
Close and review the project
Step 1: Define the Scope of the Project
Start by clearly defining your project goals and objectives. This first step provides clear direction and purpose, ensuring everyone involved in the project understands and shares the same vision of desired project deliverables.
This clarity serves as a reference point for evaluating progress and success, allowing the stakeholders to measure outcomes at the end of the project to reflect on what could have been done better and what went well for continuous growth.
Knowing the project scope allows for better planning and allocation of resources, including time, projected budget, and materials. This ensures that the necessary resources are available when needed, avoiding setbacks in your project’s timeline and mitigating potential risks.
Moreover, it also helps manage the expectations of clients, stakeholders, and team members. Everyone involved knows what to expect in terms of deliverables, timelines, and outcomes. While this helps make it easier to fulfil the needs of key stakeholders, it also holds you and your team accountable.
Step 2: Plan and Schedule the Work
Start by breaking the project into smaller tasks with a work breakdown structure (WBS). Keep tasks at a size the team needs to track. On an animation project, "finish the walk cycle" works as a task; "draw frame 14" doesn't need its own line on the tracker; it just adds noise.
Once the tasks are mapped out, turn them into a timeline. Treat it as a living document: plot milestones, deadlines, and task dependencies at a high level first, then adjust as the work moves.
Milestones do double duty on a long project. They show how far the work has come, and they give the team a reason to pause and recognise progress. Motivation dips on projects that run long without visible wins, so don't skip this second part.
Creative projects touching on identity, culture, or public space also carry consequences beyond the creative brief itself. Think through how the work will land with the audience it represents, alongside the audience it's made for, while the project is still being planned.
Step 3: Budget and Allocate Resources
Start budget planning by listing every expense category before the project kicks off. Run through a list of potential additional costs, like transportation and marketing. Record everything in a spreadsheet or budgeting tool, then track actual spend against the estimate as the project moves forward.
Because large creative projects run into unplanned costs often enough, a contingency fund belongs in the budget from day one, not as an extra. This contingency planning falls into two buckets: budget contingencies, for costs nobody saw coming, and operational contingencies, for everything else, for example, like a corrupted file.
Both are worth preparing for in advance. Backing up project files and lining up a backup supplier take less than an hour to set up, and either one can save the project days of recovery time later.
Step 4: Manage the Team and Collaboration
Most friction on creative teams traces back to one pattern: two people assume the other owns a task. Defining who's responsible for what before work starts and putting that in writing somewhere visible removes that potential friction.
Here's how that plays out on an actual project: A studio is producing a 20-piece exhibition with a six-person team. Two illustrators are each waiting on the other to finalise a shared background asset, each one assuming it's the other person's job. The project lead notices the asset sitting untouched on the shared tracker, reassigns it to one illustrator on the spot, and the work moves again within the hour.
That's the real case for centralising communication. Status updates buried in chat threads or passed along verbally tend to get lost in the noise of a busy week.
TESSR's Woohoo feature handles this by showing task ownership at a glance, so a stalled task surfaces on its own instead of waiting for someone to ask who's responsible. One tracker, one shared file, one place everyone checks. That single source of truth removes most of the guesswork about who owns what and where a task actually stands
Step 5: Choose the Right Framework
Frameworks like Agile and Kanban models are good for creative work because they allow projects to evolve as ideas develop, something rigid waterfall planning struggles with. Agile suits teams iterating on a single deliverable across defined sprints. Kanban, on the other hand, fits teams managing a steady flow of smaller tasks spread across multiple projects. Hybrid approaches combine elements of both, making them a practical choice for studios balancing a large exhibition build with several smaller client projects at the same time.
A short list of questions helps narrow the field before adopting a new framework:
Does it support visual timelines, not only flat lists?
Can it handle proper file versioning for creative assets?
Does feedback live on the file itself rather than being scattered across a separate tool?
Does the pricing scale with team size without a steep jump at some arbitrary headcount?
Can clients or outside collaborators get limited access without buying full licenses?
Step 6: Execute and Monitor Progress
A weekly stand-up, or an async update for a remote team, keeps everyone working from the same picture of where the project actually stands. TESSR Insights feature supports this by tracking each member's progress and capacity in real time and rolling it up into a clearer picture of overall project health, so a stand-up starts from actual data instead of everyone reporting their own status from memory.
Running feedback sessions deserves the same structure. Book them ahead of time rather than waiting for something to look off so the project's vision stays consistent across contributors who each bring their own instincts to the work. Feedback given early is easier to attend to, while feedback that surfaces late costs far more in time and effort.
Step 7: Document and Keep Records
Good documentation should be a part of daily workflow. Maintain consistent file naming and a clear folder structure so anyone on the team can quickly locate assets and documents. Record key decisions and feedback throughout the project as well, making it a valuable reference for future work.
Projects involving public spaces or outside collaborators bring legal considerations: a copyright notice, permission agreements for third-party work, and, depending on the country, a statutory declaration.
Step 8: Close and Review the Project
Closing a project means delivering the final output, securing formal client approval, and confirming every obligation has been met. Once done, an internal review should follow. This step often gets skipped when the team is tired and another project is waiting, yet a project retrospective is quite vital.
What went right, and what fell short of expectations?
What did the team learn, and what feedback surfaced along the way?
What should change before the next project starts?
Write the answers down in a document the team can easily find later.
Key Takeaways
Large art projects tend to succeed or fail on the same handful of fundamentals: a documented scope, a realistic schedule, and a team that knows exactly who owns what.
Creative work adds variables traditional PM frameworks rarely plan for, like revision cycles and the occasional creative block, but the underlying discipline still holds: build in buffer time, document as the project moves rather than only at the start and end, and treat the post-project review as part of the deliverable, not an optional step once the client signs off.
Frequently Asked Questions (FAQ)
How much buffer time should I build into a larger project’s schedule?
A reasonable starting point sits around 15 to 20 per cent of total project time. A range commonly suggested for schedule contingency, with the exact amount depending on how much risk and uncertainty the project carries. Tasks tied to client revisions or outside vendors usually deserve the largest buffer, since delays there sit outside the team's direct control.
Who should own scope changes on a creative project, the client or the project manager?
The project manager owns the process for evaluating and approving changes, even when a client initiates the request. That means logging every request, weighing its impact on timeline and budget, and getting sign-off before anyone on the team acts on it. Changes that move directly from client to artist without timeline check-in are what make scope creep quietly form.
What's the difference between a milestone and a deadline in project planning?
A milestone marks a point of progress, like "concept sketches approved", while a deadline marks the date a deliverable is due. Milestones help a team track momentum across a long project; deadlines apply pressure at fixed points. Large projects need both, since deadlines alone won't reveal whether work is on pace until it's already too late to adjust course.
How do I manage a team where roles overlap?
Define primary and secondary responsibilities for that person separately, and decide ahead of time which one takes priority when the two pull in different directions. A shared task tracker that assigns ownership per task, rather than per person, handles this kind of overlap better than a fixed org chart ever could, since the same person can show up as owner on one task and contributor on another.
What's the most common reason large projects go over budget?
Underestimated material costs paired with unaccounted-for revision rounds. Teams often budget for the planned quantity of materials and a single round of client feedback, then run over once a second or third revision round shows up. A contingency fund and a budget line for at least two feedback rounds, built in from the start, head off most of this risk before it happens.
Author’s Bio
The TESSR Editorial Team is a collective of creatives and project management practitioners who enjoy sharing real-life experience on project management, creative workflows, and well-being in the creative industries. The team wants to help creative leaders, project managers, and individuals in animation, design, and creative studios understand the benefits of project management. So, creatives can all create with more freedom and, together, build a more sustainable creative culture.
Check out their LinkedIn page here.
Comments