Workflows for creative work

The problem with applying operational logic to creative work

Most project management thinking was built for execution, not exploration. You start with a known output, break it into tasks, assign owners, set a deadline, and track to completion. That model works well when the path from start to finish is already understood.

Creative work is different. The output is not known at the start. Often the brief itself is a hypothesis. You are trying to find something, not build something you have already found. The difference matters enormously when you are designing a workflow, because a workflow built for execution will actively work against the kind of thinking that creative work requires.

This is a real problem for teams building creative products. Not because process is the enemy of creativity, but because the wrong kind of process is. Teams working on All Purpose Music and Made It Out run into this constantly. The temptation is to borrow the same sprint structure, the same kanban board, the same ticket-and-point system that works for shipping software features. Sometimes it creates a kind of discipline that feels productive. But it can also flatten the very quality that makes creative work valuable: the willingness to stay in a state of not-knowing long enough to arrive at something honest.

The goal is not to remove structure from creative work. The goal is to design structure that fits the actual shape of it.

What a creative workflow actually looks like

Creative work tends to move through distinct phases, though rarely in a straight line. Understanding those phases is the first step toward supporting them well.

The first phase is capture. Ideas arrive at inconvenient moments. The quality of a creative workflow often begins with how well the team captures raw material before it disappears. This is not just about note-taking apps. It is about having a shared culture of capture: a place where half-formed thoughts, references, audio sketches, lyric fragments, or direction changes can land without being immediately evaluated. Capture is deliberately non-critical. You are collecting, not curating.

The second phase is exploration. This is where the work gets genuinely messy, and where most standard project tools break down. Exploration does not produce a deliverable; it produces orientation. You are finding out what you are actually making, which means you have to make a lot of things you will not use. For a music project like All Purpose Music, this might mean recording a dozen versions of a song's structure before anyone agrees on the direction. For Made It Out, it might mean writing multiple editorial angles on a story before the right one surfaces. Exploration is not inefficiency. It is due diligence for creative output.

The third phase is production. Once direction is established, work accelerates. This is where the standard project tools start to become useful, because now the output is knowable. You can assign tracks, set real deadlines, and hold to them without cutting something essential off.

The fourth phase is review. Creative review is not the same as a technical review. It is not only about catching errors. It is about honest evaluation of whether the thing does what it is supposed to do: whether it feels true, whether it connects, whether it is ready. This phase is the most interpersonally difficult, because it requires people to give and receive subjective feedback without that feedback becoming personal.

The fifth phase is distribution. For consumer-facing creative products, distribution is not an afterthought. Decisions about format, timing, channel, and framing are creative decisions, and they shape how the work lands. A song released at the wrong moment, or to the wrong audience framing, does not get the chance to prove its worth. Distribution deserves its own phase in the workflow, not a footnote at the end.

The review and feedback loop problem

Feedback is where most creative workflows quietly collapse. The problems are predictable. Feedback arrives too late, when changes are costly. Feedback arrives from too many directions, creating competing instructions with no resolution process. Feedback is given in the wrong format, vague when it should be specific, or specific about the wrong things. And the people giving feedback and the people receiving it often have different understandings of what they are actually evaluating.

Fixing the feedback loop requires agreeing on a few things before a project begins. First, who has decision authority at each phase. Consensus review is expensive and slow. Someone needs to be accountable for the final call. Second, what the criteria for advancement are. Moving from exploration to production should be a deliberate decision, not something that happens by default when the calendar pressure becomes severe. Third, what format feedback should take. A voice note, a written comment, an in-person session: different formats surface different things, and the right choice depends on what is being evaluated.

For Made It Out, which operates as a media and storytelling platform, the review loop is particularly sensitive because the editorial voice is load-bearing. A piece of work that sounds like it was made by committee loses the quality that makes it worth reading. The feedback process has to support the voice rather than diluting it. That means fewer voices in the room, not more, at the critical evaluation stage.

For All Purpose Music, the equivalent problem is that sonic direction can drift under accumulated feedback from people with different taste profiles. The workflow needs to include a moment where someone resets against the original intent and asks whether the current version is actually closer to that intent, or simply different.

How tools for creative workflows should feel different

Operational tools optimise for clarity and closure. A task is open or closed. A milestone is hit or missed. The language is binary and satisfying.

Creative tools need to support states that are more ambiguous. Something can be progressing well without being close to done. A direction can be right without being executable yet. The emotional register of creative work includes doubt, experimentation, and provisional confidence, none of which fit cleanly into a red/amber/green status indicator.

This does not mean creative tools should be formless. The best tools for creative work provide structure that is load-bearing but not prescriptive. They give you somewhere to put things, a way to see progress over time, and a mechanism for keeping decisions visible without over-constraining what comes next.

A few specific things that matter. First, the ability to capture and store half-formed material without having to classify it. Creative teams generate a lot of things that are not yet anything specific, and the friction of having to immediately categorise or assign material causes people to capture less. Second, a timeline view that shows phases rather than tasks, so the team has a shared sense of where they are in the creative process without being held to a task list that does not reflect how creative work actually moves. Third, a feedback mechanism that distinguishes between direction-level feedback and detail-level feedback, because those require different responses.

The tools we have built around All Purpose and Made It Out are not yet fully formed. But the principle is consistent: the tool should serve the work, not the other way around. When a creative team starts bending their process to fit the tool's assumptions, the tool is wrong.

The underlying argument

Creative work is not the opposite of operational rigour. It is a different application of rigour. The rigour shows up in the quality of the exploration phase, the honesty of the review process, and the intentionality of distribution. It is not less disciplined than execution-oriented work. It requires a different kind of discipline.

The teams building All Purpose Music and Made It Out are navigating this in real time. Both products sit at the intersection of creative production and consumer distribution. Both require workflows that can hold open-ended exploration and hard commercial decisions at the same time. That is not a comfortable place to operate, but it is the honest place.

The risk of borrowing standard project management frameworks wholesale is that you get the appearance of structure without the actual support for how creative work moves. You produce status updates and closed tickets, but the thing you are making quietly loses something in the process.

The risk of rejecting structure entirely is equally real. Creative work without any scaffolding tends to extend indefinitely, suffer from unclear ownership, and produce output that no-one has the courage to finish or release.

The answer is in the design of the scaffolding. Not more of it or less of it, but the right kind of it for the kind of work you are actually doing.

That is a harder design problem than building a standard project tracker. It is also a more interesting one.