Creative Operations
Creative resource and workflow operations
Resource planning, freelance allocation and workflow standardization across a fast-moving creative team.
- Client
- Global creative agency
- Year
- 2025–
- Category
- Creative Operations
- Role
- Resource Manager
- Concurrent projects
- MultipleConcurrent projects
- Blended capacity model
- Permanent + freelanceBlended capacity model
- Bilingual environment
- EN / JABilingual environment
Project-scope indicators, not personal achievement claims.
Overview
Ongoing resource management for a creative team running multiple concurrent projects. The work covered capacity planning, freelance sourcing and allocation, contracting and invoicing, and standardizing how work moved through the team.
Context
Demand arrived unevenly across the year and across disciplines. Permanent capacity could not absorb every peak, so freelance support had to be planned rather than improvised, and the commercial side of that support handled properly.
Challenge
Capacity, demand and freelance support were each visible to somebody, but not to everybody in one view. Allocation decisions were being made without a shared picture of what the team was already committed to.
Scope
Scope
- Capacity planning across disciplines and projects
- Freelance sourcing, briefing and allocation
- Contracts, purchase orders and invoicing for external talent
- Workflow standardization across the team
- Utilization visibility and forward demand view
Team
Team
- [CONFIRM TEAM SIZE]
Stakeholders
Creative leadership, project management, production, finance and external freelance talent.
Role and ownership
What the organization delivered
The agency delivered creative work across multiple concurrent client projects.
What I personally owned
- Led resource planning and allocation across concurrent projects
- Sourced, briefed and managed freelance talent
- Managed contracts, purchase orders and invoicing for external support
- Supported standardization of how work was briefed, assigned and tracked
- Maintained a forward view of demand against available capacity
What resulted
- Improved visibility of capacity, demand and commitments in a single view
- Made allocation decisions traceable rather than ad hoc
- [CONFIRM UTILIZATION OR EFFICIENCY EVIDENCE]
Operating model
Forward demand view
Capacity was planned against known upcoming demand, not only against what had already landed.
Freelance as planned capacity
External support was treated as a planned part of the resource model rather than an emergency measure.
Commercial hygiene
Contracts, POs and invoicing were handled as part of allocation, so engaging support did not create finance debt.
One allocation record
Assignments lived in one place so competing claims on the same person were visible before they were made.
Tools and systems
- Resource and capacity tracking
- Asana
- Google Workspace
- Purchase order and invoicing workflows
Risks and constraints
Risks and constraints
- Demand peaks exceeding permanent capacity
- Freelance availability at short notice
- Allocation conflicts between concurrent projects
- Contracting and payment delays affecting talent relationships
- Undocumented informal assignments creating hidden load
Key decisions
- 01
Plan freelance, do not scramble for it
Building expected external support into the forward plan removed most last-minute sourcing.
- 02
Make commitments visible before confirming them
An assignment was checked against existing commitments before being agreed, not after.
Deliverables
Deliverables
- Resource allocation matrix
- Forward capacity and demand view
- Freelance roster and engagement records
- Contract, PO and invoice tracking
- Standardized briefing and assignment workflow
What changed
Allocation moved from individual knowledge to a shared record. Conflicts over the same person surfaced during planning rather than after a commitment had been made.
Lessons learned
- Resource management is mostly the work of making existing commitments visible.
- Freelance support is a planning problem before it is a sourcing problem.
- Contracting and invoicing are part of resourcing, not an afterthought to it.
Next case study
Enterprise business development