What Is the Creative Process in Project Management? The Phases Creative Work Actually Moves Through

The "creative process" in psychology textbooks is described in five abstract stages: preparation, incubation, illumination, evaluation, implementation. That framework was developed by Graham Wallas in 1926. It is a theory of how individual human minds generate ideas. It is not how creative work moves through a project at a working agency, studio, in-house team, or production company.

The creative process in project management is different. It is the sequence of structured phases that a creative project moves through from the moment a brief lands to the moment the final files are delivered and the team runs a retrospective. Each phase has specific tasks. Each has specific failure modes. Each has specific work the project manager owns. Working creative PMs recognize this sequence immediately because they live inside it. People asking "what is the creative process in project management" are asking about this — the actual operational lifecycle of a creative project — not a hundred-year-old theory of cognition.

This post walks through the seven phases creative work actually moves through, what happens in each, where projects most commonly fail, and what the PM is responsible for at each step. If you want the broader discipline overview, what creative project management is as a discipline covers that. If you want the role itself, what is a creative project manager does the same.

Phase 1: Brief and Discovery

The first phase happens before any creative work begins. The brief is written, refined, and approved. The team understands what they are making, for whom, why, and what success looks like. The constraints — timeline, budget, deliverables, mandatories — are explicit.

This phase looks unglamorous from outside. Inside the discipline, it is the highest-leverage phase in the entire project. A clear brief prevents most downstream problems. A vague brief is a guarantee of expensive revisions later.

What the PM owns: writing or refining the brief, identifying gaps and asking questions to close them, getting stakeholder alignment on objectives and success criteria, naming the approver explicitly, and refusing to start work until the brief is clear. The discipline to push back on a vague brief — even under pressure to start immediately — is the most important skill a creative PM can develop. How to write a creative brief that holds up covers what a strong brief actually contains.

Common failure mode: starting work on a brief that sounds clear but is actually a description of a feeling. The team produces work that meets the brief as written and the stakeholder gives feedback that contradicts the brief, and the team has to redo work that should never have started.

Phase 2: Kickoff and Team Alignment

The kickoff is the formal beginning of the project. The team, the brief, the timeline, the approver, and the process all get aligned in the same room (or video call). Roles are confirmed. Decision-making authority is established. Communication norms are set. The project officially starts.

A well-run kickoff is short — typically 60 to 90 minutes — and structurally tight. The team walks out knowing what they are making, who is responsible for what, when key milestones are, and who makes final decisions. A badly-run kickoff is a meeting where everyone listens to the brief being read aloud, no decisions get made in the room, and the project is functionally identical to one that did not have a kickoff at all.

What the PM owns: building and running the agenda, ensuring all required stakeholders attend, naming the approver and the decision-making process explicitly, capturing decisions and open items in writing, and sending a recap that becomes the contract for how the project will run.

Common failure mode: kickoffs that produce no decisions. Everyone agrees the project sounds great. No one names the approver. No one confirms the milestone dates. The first review three weeks later surfaces all the misalignment that should have been resolved in the kickoff.

Phase 3: Exploration / Divergent Phase

This is the phase that looks most like the romantic version of creative work. The team explores. Multiple directions get developed. Different angles, different executions, different concepts are produced. The output is not the final answer — it is a set of options to evaluate.

This phase is where creative leads, designers, copywriters, art directors, and producers do their craft. The PM's role shifts. In the brief and kickoff phases, the PM is at the center of the work. In exploration, the PM steps back and protects the team's time, focus, and creative autonomy. Over-managing this phase produces worse work.

What the PM owns: maintaining the timeline without forcing premature convergence, shielding the team from late-arriving stakeholder requests, ensuring the team has the resources and context they need, and managing the calendar so the team has the actual hours the brief assumed they would have.

Common failure mode: stakeholders adding "while we're at it" requests during exploration. A senior person hears the team is working on the project and asks if they can also explore an alternative angle, a different audience, an additional deliverable. Each addition expands scope silently. Strong PMs name these as scope changes and route them properly before any work happens on them.

Phase 4: Presentation and Review

The first major decision point in the project. The team presents the work they have developed during exploration. Stakeholders evaluate it against the brief. A decision gets made: which direction proceeds, what revisions are needed, what needs to be reconsidered.

The presentation is structured. The team walks through the work explicitly as a response to the brief. Stakeholders give feedback in a defined order. The approver speaks last so others are not anchored by their reaction. The meeting ends with explicit closure: what is approved, what is open, what is locked.

This is the phase where the difference between a working creative PM and a struggling one is most visible. A working PM runs reviews that produce decisions. A struggling PM runs reviews that produce more feedback. How to run a creative review that produces a decision covers the structure in depth.

What the PM owns: framing the review around the brief, routing feedback to the approver, surfacing conflicts between stakeholders explicitly, capturing decisions in writing, and sending the recap so the approval is unambiguous.

Common failure mode: reviews that end with implicit understandings rather than explicit decisions. The team thinks they have approval. The approver thinks they signaled "mostly good with changes." Two days later, contradictory feedback arrives.

Phase 5: Revisions / Convergent Phase

The second creative phase. The team takes the feedback from the presentation and converges toward the final answer. This is not the same as exploration. The constraints are tighter. The direction is locked. The work is iterating toward production-ready rather than generating new options.

Revision rounds should be defined in scope. Two rounds is typical for most agency and in-house creative projects. Anything beyond the agreed rounds is a change request, not a revision. Strong PMs treat this distinction as non-negotiable.

What the PM owns: managing the revision queue, ensuring feedback is organized and prioritized before it reaches the team, identifying when feedback conflicts with the brief versus when it is valid against the brief, and stopping the cycle when revisions are exceeding scope.

Common failure mode: the third round of revisions. By round three, the brief is usually drifting, stakeholders are reacting to preferences rather than brief compliance, and the team is being asked to thread contradictory needles. The PM's job in round three is often to escalate that the brief itself needs to be revisited rather than continuing to revise the work.

Phase 6: Approval and Final Production

The work gets formally approved. Final files are produced — production-ready design files, finished edits, locked copy, mastered audio, color-graded video. The output transitions from "in development" to "ready to ship."

This phase is where many creative projects get sloppy. The team is tired. The deadline is close. Small things get missed because the project feels done. A working PM treats approval as a discrete event with explicit closure and runs final production with the same discipline as the earlier phases.

What the PM owns: getting formal sign-off in writing, coordinating handoff to production, managing the asset delivery process, ensuring file naming and folder structure are clean, and verifying that delivered files match the approved versions. Organizing Google Drive for creative project management covers the file structure that makes this phase clean rather than chaotic.

Common failure mode: approval that is not really approval. The PM thinks the work is signed off. The stakeholder thinks they had one more round. Production starts. New feedback arrives. The team has to roll back work that was already in final production. The fix is explicit written approval before any production work begins.

Phase 7: Delivery and Retrospective

The final phase, often skipped. Final files are delivered. The project formally closes. The team runs a retro to capture what worked, what did not, and what to do differently next time.

The retro is the most under-practiced part of the creative project lifecycle. Most teams ship the final files and immediately move to the next project. The lessons evaporate. The same mistakes repeat. A 30-minute retro within one week of delivery captures most of the value at a small fraction of the cost of repeating the problems.

What the PM owns: confirming delivery and final acceptance, archiving project files, running the retrospective, capturing lessons in writing, and identifying specific process improvements for the next project.

Common failure mode: skipping the retro entirely. The project closes. The team moves on. Six months later, the same scope issue or the same brief failure happens on a different project, and nobody connects the pattern. The retro is the cheapest investment in long-term improvement available to a creative PM.

How the Seven Phases Compound

These phases are sequential but not isolated. Decisions made in the brief and kickoff phases shape every phase that follows. Failure to close decisions in the presentation phase shows up as chaos in the revisions phase. Skipping the retro at the end of one project costs the team in the brief of the next one.

This is why creative project management is a discipline rather than a collection of tactics. The phases connect. A PM who runs phase one well makes phases four, five, and six dramatically easier. A PM who skips the unglamorous early phases pays the cost in every later phase, on every project.

The Level I certification curriculum covers each of these phases in depth, along with the frameworks and templates that support running them well. For working creative PMs who want to formalize this lifecycle and add a creative-industry credential, Level I is the most direct path. Start with Level I here.

Frequently Asked Questions

What are the stages of the creative process in project management?

In a project management context, creative work moves through seven phases: brief and discovery, kickoff and team alignment, exploration (divergent phase), presentation and review, revisions (convergent phase), approval and final production, and delivery and retrospective. Each phase has specific tasks, specific failure modes, and specific work the project manager owns. This sequence is different from the Wallas creative-process theory from psychology (preparation, incubation, illumination, evaluation, implementation), which describes individual cognition rather than how creative projects actually move through a team.

What is the most important phase of the creative process for a project manager?

The brief and discovery phase has the highest leverage. A clear brief prevents most downstream project problems. A vague brief guarantees expensive revisions later. Working project managers spend disproportionate effort getting the brief right because the cost of fixing it later is much higher than the cost of fixing it before work starts. Most other phases run smoothly when phase one is run well.

How does the creative process differ from a software development process?

Software development typically moves through requirements, design, build, test, and deploy phases that assume the deliverable is defined upfront. The creative process is different because the deliverable emerges through iteration — the team produces options in exploration, narrows in revisions, and locks the answer at approval. Software methodologies like agile have influenced creative work, but the core difference remains: creative projects discover what the work should be through the process, while software projects build a defined specification.

How long does each phase of the creative process take?

Phase durations vary by project. A typical agency campaign might run two to three weeks in brief and discovery, one day in kickoff, two to three weeks in exploration, one week in presentation and revisions, one week in final production, and a 30-minute retro. Larger projects scale these proportionally. Smaller deliverables compress the phases but rarely skip them entirely; the structure is the same regardless of project size.

Who is responsible for managing the creative process?

The creative project manager owns the structure of the process and the transitions between phases. Creative leads (creative directors, designers, copywriters, producers) own the work within the exploration and revisions phases. Stakeholders and approvers own the decisions at the review and approval phases. The PM coordinates across all of these and ensures each phase has the conditions it needs to succeed.

Can the creative process be agile?

Elements of agile methodology — iterative development, rapid feedback cycles, willingness to adapt — fit well with creative work. Full agile frameworks (Scrum, sprints, story points) often translate poorly because creative deliverables do not break into independent stories the way software features do. Most working creative teams use a hybrid: structured phases with iterative cycles inside the exploration and revisions phases. Treating creative work as pure agile or pure waterfall is usually a mistake; the discipline is its own thing.

Where to Go Next

If you want to formalize your understanding of the creative project lifecycle and add a credential built specifically for creative industries, the Level I certification ($147) covers each of these phases in depth. Start with Level I here.

For the foundational primer before committing to a credential, the CPMA free eBook covers the discipline of creative project management. Download the free eBook here.

For Level I, Level II, the Project Manager Resume Kit, and the Creative PM AI Kit together, the Bundle ($297) is the better value at $201 in savings.