When does a dedicated design team make sense?
A dedicated external design team makes sense when design work continues for several months, several modules develop in parallel and the company has no design lead of its own.
For a defined piece of work, such as an audit or a first version of one module, a fixed project phase is usually enough.
A retainer is a commercial arrangement, not a guarantee of exclusivity. Agree capacity, named responsibilities, availability and how priorities or capacity may change.
Table of Contents
Summarize with:
Key facts
- A dedicated team fits continuous work across several modules.
- A roadmap planned at least a quarter ahead gives a dedicated team a backlog.
- Rotating designers between projects loses domain context.
- A shared design system keeps several designers consistent.
- For a defined piece of work, a project phase with a clear scope is usually enough.
Signs it fits
- Several modules or features designed at the same time
- A development team waiting on design every sprint
- No in-house designer to keep the design system consistent
- A roadmap planned at least a quarter ahead
Fit check
Signs it does not fit yet
- No backlog of design work beyond the current task
- No decision-maker available to review work every week
- A roadmap that changes direction every few weeks
- Development capacity too small to build what a team would design
Dedicated team or project phase
| Ongoing team capacity | Project phase | |
|---|---|---|
| Suits | Continuous work across modules | A defined scope: an audit, a new product or a first module |
| Domain context | Kept between modules | Built for the phase |
| Design system | Maintained as part of the work | Delivered at the end of the phase |
| Planning | Needs a backlog | Needs a clear brief and scope |
Common mistakes
- Booking a team before there is a backlog of design work
- Rotating designers between projects and losing domain context
- Working without a shared design system, so each designer works differently