A solo design project reliably breaks into six stages: brief, discovery questions, kickoff, direction-setting (moodboard), concept and feedback rounds, and delivery and handover. The stages themselves are not unusual. What changes when one person runs the whole thing is that nobody else is checking whether a stage was actually finished before the next one starts. On a team, a project manager or a second designer tends to catch a skipped step. Working alone, the only backstop is a habit of checking your own handoffs, and that habit has to be built deliberately, because nothing else is going to build it for you.
The Six Stages, Named Plainly
The sequence itself is close to the classic double-diamond model taught in most design courses: discover, define, develop, deliver. In practical solo-freelance terms it splits into six checkpoints:
- Brief — what the client actually wants, in writing, even if you had to write it yourself.
- Discovery questions — the specifics the brief alone never covers.
- Kickoff — the live conversation where the brief gets confirmed, not assumed.
- Direction-setting — a moodboard or similar tool that aligns on look and feel before real design hours go in.
- Concepts and feedback — the rounds where the actual work gets made, shown, and revised.
- Delivery and handover — the point where files, rights, and expectations all get closed out cleanly.
Every one of these has its own failure mode, and every one is more expensive to fix retroactively than to do right the first time.
Why "Solo" Changes the Process, Not Just the Headcount
On a team, each stage has an owner other than the person doing the design work: a project manager tracks whether the brief was actually signed off, an account lead notices when feedback contradicts itself, a producer chases the client for a written approval. Running solo removes every one of those checks, not just the extra staff. The work does not get harder because you are doing more tasks. It gets riskier because the tasks that used to be someone else's job to notice are now nobody's job unless you build them into your own checklist.
That is the practical reason this process is written down as a sequence rather than a mood or an instinct: a checklist survives a busy week. A vague sense of "I usually do it this way" does not.
| Stage | Who normally catches a problem on a team | Who catches it running solo |
|---|---|---|
| Brief | Account manager confirms it's signed off | You, by getting written confirmation yourself |
| Discovery questions | Producer flags an unanswered gap | You, by tracking answers against a checklist |
| Kickoff | PM writes and circulates the recap | You, immediately after the call, in writing |
| Direction-setting | Creative director calls time on the moodboard | You, against a stated stop rule, not a feeling |
| Feedback and revisions | Account lead catches contradictory notes | You, cross-checking each round against the last |
| Delivery and handover | Producer confirms the client received everything | You, with a written handover checklist |
The table is the honest version of "why is this harder alone." It isn't that any single stage is more complicated. It's that every row in the right column used to be a second person's job, and now it's a line item on your own list.
Stage 1: The Brief
A brief is the client's stated goal, audience, and constraints in a form you can refer back to later, not a mental note from a phone call. Plenty of clients will not hand you a written brief unprompted, especially ones who say some version of "just make something nice." That is not a lack of a brief, it's a symptom that the brief has to be built through a structured conversation instead of handed over ready-made. The full method, including what to do when a client won't commit to specifics, is in what to include in a design brief.
Stage 2: The Discovery Questions
Once you have a stated goal, the discovery questions fill in everything the brief alone leaves out: who actually signs off, what format the files need to land in, what happens if two stakeholders disagree. The order these get asked in matters more than most checklists suggest, because some gaps are cheap to fix late and others are not. That ordering, plus what to do when a client answers "I don't know, you're the expert," is covered in the questions to ask before you open the design file.
Stage 3: The Kickoff Call
The kickoff is where the brief and the discovery answers get confirmed out loud, in real time, instead of assumed from an email thread. Run alone, a kickoff call has one job the version with a project manager doesn't: you have to leave it with something in writing, because nobody else is going to write up notes and circulate them for you. A minute-by-minute agenda built for exactly one person on each side of the call is in how to run a kickoff call for a design project.
Stage 4: Direction-Setting
Before real design hours go into a concept, a moodboard or similar reference collection aligns everyone on look and feel at low cost. It is genuinely useful for catching a wrong direction early. It is also an easy place to stall, because it feels productive without requiring you to commit to anything a client can reject. Where the line sits between useful alignment and avoidance is in moodboards: what they're actually for, and what they're not.
Stage 5: Concepts and Feedback
This is the stage with the most ways to go wrong, and each one has its own treatment. How the work gets shown decides how it gets judged, which is why presenting design concepts without losing the room is a separate skill from making them. How many directions go into that room is a scope decision rather than a generosity one, set out in how many design concepts to present. Whether the work is shown flat or in context changes what the client believes they are approving, covered in mockups versus flat files.
Then the feedback itself. An open question produces commentary rather than a decision, so how to ask clients for design feedback is mostly a matter of question shape. And when the answer comes back as something unactionable, there is a diagnosis path for it in decoding "make it pop".
Stage 6: Delivery and the Close
Counting revisions, getting written sign-off, and the final handover each need their own treatment and are covered as this cluster continues. What carries through from every earlier stage is the same principle: each one has a specific way it goes wrong when nobody but you is watching for it, and the fix in every case is a deliberate check built into your own process rather than trusted to memory.
Deep Dives
- What belongs in a design brief
- The questions to ask before you open the design file
- How to run a kickoff call for a design project
- Moodboards: what they're actually for
- How to present design concepts without losing the room
- How many concepts should you show?
- Presenting in context: mockups vs flat files
- How to ask for feedback that's actually usable
- Decoding "make it pop": translating vague client feedback
The One Check Most Solo Designers Skip
Across all six stages, the single most commonly skipped check is getting agreement in writing at the end of a conversation rather than assuming a verbal "sounds good" means the same thing to both sides. A brief confirmed by email, a kickoff followed by a short written recap, a direction approved in a message thread rather than a phone call: none of this is bureaucratic overhead. It is the entire substitute for the project manager a team would otherwise have, and it is the cheapest insurance available in this process.
It's easy to skip because it feels redundant in the moment, you just talked to the client, you both nodded, why write it up again. The value only shows up later, usually in week three, when a client's memory of a call has quietly drifted from what was actually agreed. A written recap does not prevent every disagreement, but it turns most of them into a five-minute correction instead of a redone deliverable.
How the Rest of This Cluster Fits Together
None of these six stages works well in isolation, which is why they're written as a linked sequence rather than as separate topics. The brief feeds the kickoff. The kickoff confirms the direction work. The direction work either gets approved cleanly or exposes a gap that should have been caught during intake. Reading the individual guides in order, brief, questions, kickoff, moodboard, is closer to following one project end to end than reading four unrelated articles, and each one names exactly where it hands off to the next.
FAQ
What are the stages of a solo design project?
Brief, discovery questions, kickoff call, direction-setting (moodboard), concept and feedback rounds, and delivery and handover. The stages match the standard discover-define-develop-deliver model; what differs solo is who is responsible for checking each one was actually finished.
Do I need a project manager to run a design project alone?
No, but you do need to replace what a project manager would normally catch: a written brief, a confirmed kickoff, and documented sign-off at each stage. Those checks do not go away when you work solo, they just become your own responsibility.
How is a solo design process different from an agency's?
The stages are largely the same. The difference is that an agency spreads the checking function across a project manager, an account lead, and sometimes a producer. Solo, every one of those checks has to be built into your own workflow instead.
What's the most common mistake in running a project alone?
Assuming a verbal agreement is the same as a written one. A confirmed brief, a kickoff recap, and a written sign-off close the gap that a project manager would otherwise cover.