What Creative Teams Get Wrong About Project Management

Key Takeaways

• Creative tasks are not decomposable in advance. A ticket that says "design the landing page" hides work that only becomes visible once you start.
• Estimate in rounds, not hours. The variable that drives creative timelines is how many times it goes back and forth.
• Done is an approval, not a state a maker can set. Systems that let makers mark done produce false progress.
• Status without context is useless. "In progress" tells you nothing about a design; the work itself is the status.
• Utilisation targets destroy creative output. Ninety percent booked means zero capacity for the iteration the work needs.
• Track the round trip, not the task. Most creative delay is waiting, not working.

Why Standard Project Management Misfits

The dominant project management model comes from work where the deliverable can be specified before it is made. That assumption fails in three specific places for creative work.

Tasks cannot be decomposed in advance. "Design the landing page" is a ticket. What it actually contains is unknown until someone starts: it might be three hours of applying an existing system, or it might surface that the brand has no answer for this kind of page, which is a week. Decomposing it up front means inventing subtasks that turn out to be wrong.

Engineering has this problem too and has partly solved it with spikes and estimation ranges. Creative teams usually inherit the ticket without the spike.

Estimates are dominated by a variable nobody tracks. The time to produce a first version of most creative work is fairly predictable. The time to get it approved is not, and it dwarfs the production time. A logo that takes six hours to design takes six weeks to approve. Hour-based estimates model the six hours and ignore the six weeks, which is why creative timelines are wrong in a consistent direction.

Done is not a state the maker controls. A developer can merge a pull request and it is done. A designer cannot decide their work is approved. When a system lets makers mark things done, "done" comes to mean "I have finished my part", and the project board shows a completed column while nothing has actually shipped.

A useful diagnostic: look at your board and count the items sitting in a done or in-review column that have not shipped. That number is the gap between your system's model of the work and the work.

What to Track Instead

Track the round trip, not the task

The unit that predicts a creative timeline is the round trip: work goes out, feedback comes back, revision goes out.

Track how many round trips a piece of work has had and how long each leg took. Two things become visible almost immediately.

Waiting dominates. On most creative projects, more calendar time is spent waiting for feedback than producing work. Teams that measure this for the first time are usually shocked by the ratio, and it reframes the problem: the bottleneck is not the designers.

Round count predicts trouble. A piece on its fourth round is not slightly late, it is in a different category. Something is wrong with the brief, the approver, or the alignment, and no amount of further revision fixes it. Flagging at three rounds and escalating to a conversation is far cheaper than a fifth round.

Estimate in rounds

"Two rounds included" is a better estimate than "twelve hours" because it names the variable that actually drives the timeline, and because it is a boundary the client can understand and act on.

It also converts an internal problem into a shared one. When a client knows round three is chargeable, feedback consolidates and improves. Unbounded revisions are where profitable creative projects become unprofitable.

Define done as an approval with a name

Every piece of work needs an approver, named, before it starts. Not a team, a person.

Done means that person approved it. Any other definition produces a board that says finished while the work sits in someone's inbox.

Naming the approver up front also surfaces the real problem early, which is that on many projects nobody knows who has authority. Discovering that at the start costs a conversation; discovering it at round three costs a fortnight.

Status Without Context Is Noise

A task board tells you a design is in progress. It cannot tell you whether it is any good, whether it is answering the brief, or whether it is about to be rejected.

For creative work the artifact is the status. Looking at the work in progress tells you more in five seconds than a status column tells you at all.

This is why creative teams end up with two systems: a project tool holding tickets and statuses, and a separate place holding the actual work, briefs and references. The two drift, the project tool becomes an administrative burden that describes the work rather than containing it, and people stop updating it.

The alternative is keeping the work and its context in one place, with the status derived from what is visible rather than from a field someone has to remember to change. On a Storyflow canvas the brief, the references, the current version and the feedback sit together, so reviewing status means looking at the work. Because its AI reads the whole board, asking what has not moved this week or which pieces are on their third round gives an answer from the actual project.

For resourcing, timesheets, capacity planning and invoicing, dedicated tools remain better and this does not replace them. Linear, Asana and the agency-specific tools do that job properly. The split that works is: those systems for commercial and capacity questions, the canvas for the work and its context.

The Utilisation Trap

The most damaging import from operations management is the utilisation target.

Booking a creative team to ninety percent capacity is intuitive and wrong. Creative work requires iteration, and iteration requires slack. A team with no slack delivers the first adequate version of everything, because there is no room to try the second approach that would have been better.

It also removes all capacity to absorb a round three, which means one project slipping cascades into every other project on the team.

Seventy to eighty percent is the working range for teams that need to iterate. The remaining capacity is not waste; it is the difference between adequate and good, and it is the buffer that stops a single slip becoming a quarter of firefighting.

This is a hard argument to win with finance, and the way to win it is with round-trip data: showing that projects at high utilisation take more calendar time overall because they accumulate rounds.

What Goes Wrong

Tickets without briefs. A task with no access to the thinking behind it produces work that misses, and the maker gets blamed for a specification failure.

Two systems. Status in one place, work in another. They drift and the project tool becomes fiction.

No named approver. Work sits in review indefinitely because review is nobody's job.

Hours estimated, rounds ignored. Timelines wrong in a predictable direction, every time.

Rounds unbounded. The commercial failure that turns good projects into losses.

Waiting untracked. Everyone believes the makers are the bottleneck when the data would show otherwise.

Utilisation above eighty percent. No slack, no iteration, and one slip cascades.

The Bottom Line

Creative work breaks the assumptions standard project management is built on, and the answer is not to try harder at a system that does not fit.

Track round trips rather than tasks, estimate in rounds rather than hours, define done as a named person's approval, keep the work and its brief in the same place so status means looking at the artifact, and protect twenty percent of capacity so the work has room to get better. That is a system that describes what creative teams actually do.