Project management for a small design studio: a weekly system that fits 2 to 10 people
A small design studio does not need a project manager. It needs one place per job, one weekly meeting and a rule for who decides. Here is the system, and what to ask of a tool.
The short answer
A studio of 2 to 10 people runs projects well with three things: one page per job that holds the brief, the tasks, the files and the money; a 30 minute planning meeting once a week; and one named person on each job who answers the client. A tool helps by keeping those three things in one place. It does not replace deciding them.
Most small studios fail at this the same way. The brief is in an email, the files are in Dropbox, the tasks are in someone's head, and the invoice is a spreadsheet nobody opens until month end.
What is different about a small studio
Large agencies hire project managers, producers and account leads. A studio of six has the owner doing all three, usually while also designing.
That changes what you need.
- Nobody has time to update a tool. If it takes more than a minute to log something, it will not be logged.
- Everyone sees everything. With 6 people there is no need for permission layers or resource heat maps.
- The owner is the bottleneck. Quotes, approvals and invoices wait on one person.
- Freelancers come and go. You need to bring one in on a Monday and have them useful by Tuesday.
- Cash is tight. A late invoice or an unbilled round of changes is felt the same week.
Enterprise project software is built for the opposite case. It assumes a PM who maintains it. A small studio needs the minimum that keeps the work and the money visible.
The weekly system
Monday: a 30 minute plan
Everyone is in the room, or on a call. Go through each active job in turn. For each one, answer three questions.
- What ships this week?
- Who is doing it?
- What is blocked, and by whom?
If a job has no answer to question 1, it is either waiting on the client or it is stalled. Decide which, and write the date you will chase.
Keep it to 30 minutes. At 6 active jobs that is 5 minutes each. A longer meeting means somebody is solving a problem that belongs in a separate conversation.
Daily: one look at the list
Each person opens their own task list in the morning and picks the top item. No stand-up needed for a team under 8. If someone is stuck, they say so in the ticket, where the next person who needs the context will see it.
Friday: close the loop
Fifteen minutes. Three checks.
- Is every approved deliverable invoiced, or scheduled to be?
- Did every client who owes feedback get a nudge?
- Is Monday's list roughly right?
The invoice check pays for the whole system. A studio that bills a milestone the day it is approved is paid weeks earlier than one that bills at month end. See milestone payments for creative studios.
One page per job
Every job gets a single page. It holds six things.
- The brief, as agreed. A short text, not a 12 page PDF.
- The quote and what it covers: number of deliverables, number of revision rounds.
- The task list, with owners and dates.
- The files and the client's review of them.
- The decisions: who approved what, and when.
- The invoices, with their status.
Number 5 is the one studios skip. Write down every approval with the date: "Logo direction B approved by Sarah, 4 November." In month three, when the client says they never saw direction B, you have the date.
Tickets, not tasks
A task says "Design homepage." A ticket holds the task and everything about it: the files, the client comments, the versions, the freelancer working on it. When a job has 25 deliverables, a flat task list becomes unreadable. A ticket per deliverable does not.
A good ticket for a design studio has:
- a title that names the deliverable, such as "Poster A2, v3"
- one owner
- a due date
- the current file and the older versions
- comments from the client, tied to the file
Client review without the email chain
This is where most of the hidden time goes. A designer sends a PDF. The client replies in the body of an email, then again in a text message. Someone has to turn that into a task list.
Put the review where the work is. The client opens a link, pins a comment on the image, and approves a version. You see the comments on the ticket, and the approval has a date. For the fuller process, see client approval workflow for creative studios and how to get client feedback on design.
Agree the revision limit before you start. Two rounds included, a third billed, is a common split. See revision policy template for designers and studios.
Capacity: the number most studios guess
A designer has about 5 productive hours of billable work in a day. Over a 5 day week that is 25 hours, not 40. Add up the hours promised across all jobs for next week and compare. If you promised 70 hours and have 3 designers, you have 75 hours of capacity and no slack for a late client file or a sick day.
You do not need software for this. A table with a row per person and a column per week is enough. For the full method, see studio capacity planning.
Bringing in freelancers
A freelancer needs five things on day one: the brief, the files, the deadline, the deliverable format and who to ask. Put them on the ticket and send one link. A freelancer who has to ask for each of the five costs you a day of back and forth. See freelancer management for creative studios.
What to ask of a tool
You can run this on a shared drive and a spreadsheet for the first two or three jobs. After that the pain shows up. When you compare tools, ask these questions.
- Can I see all active jobs on one screen?
- Does each job hold the files, the client review and the invoice, or do I need three other subscriptions?
- Can a freelancer work without taking a paid seat?
- Can the client review and approve without an account?
- Does it take under a minute to add a task?
- What does it cost for 5 people, a year from now?
Tools built for software teams, such as Jira, fail question 2. Tools built for general work, such as Asana or Trello, fail it too unless you add a proofing tool. Tools built for large VFX pipelines fail question 6. See creative agency project management software for how the categories compare.
A realistic setup for a 5 person studio
- One page per job, created from a template the day the quote is accepted.
- Monday plan, Friday close, 45 minutes a week in total.
- Quotes and invoices created from the job page, so the numbers match.
- Client review on the ticket. Approval recorded.
- A project is archived the day the final invoice is paid, with its files.
That is the whole system. Add things when they hurt, not before.
Doing this in OIO
OIO is project management for small creative studios. Each job is a project with tickets, files, client review, quotes, invoices and docs on the same page. Clients review images and video through a link, with pin comments on images and comments at the second or frame on video, and approve a version without an account. Freelancers work from a ticket link and do not use a seat.
Plans are Free for 1 project, Solo at $19 a month and Studio at $99 a month for 5 seats, with a 7-day trial.
Questions
Does a small design studio need project management software?
Not for the first one or two jobs. Once you run 4 or more jobs at the same time, or work with freelancers, a shared place for tasks, files and invoices saves hours a week.
What is the simplest project management system for a design studio?
One page per job, a 30 minute planning meeting on Monday and a 15 minute invoice check on Friday. Add a tool when the page gets hard to keep current.
How many billable hours does a designer have in a week?
Plan on about 25 hours, or 5 a day. The rest goes to meetings, admin, sourcing and the unbilled time every job eats.
Is Asana or Trello enough for a design studio?
For tasks, yes. They do not hold client review of images and video, quotes or invoices, so you add other tools for those.
How much does project management software cost for a small studio?
OIO is free for 1 project, $19 a month for Solo and $99 a month for Studio with 5 seats. Other tools price per user, so check the total for your headcount.