Lead agency or several specialists? How large companies set up design partners for a major redesign
Compare five ways to structure design partners for a major redesign, then use a decision table and an ownership grid to decide what stays in-house.
Consider a hypothetical retailer redesigning the apps and web tools behind its loyalty program in four markets. Procurement collects three answers. A large firm offers one team for strategy, design and build. A design agency proposes to lead the program and bring in a research studio and an accessibility specialist. A third option is eight contract designers who could join the in-house team next month. The prices are close, but the purchases are not the same.
Before a large company chooses an agency, it chooses a setup: who leads, who coordinates, and who keeps the knowledge when the contract ends. This guide compares five setups, says when each one fits and how it fails, and ends with a decision table and an ownership grid for dividing work between the in-house team and its partners. For who operates at that scale, see our comparison of enterprise product design agencies. Humbleteam is a product design agency and publishes this guide, so it has a stake in several of these setups. The tables apply to its proposals too.
What are the five ways to set up design partners?
The options sort into five. In the first, a lead agency runs design for the whole program. In the second, the lead agency coordinates separate studios for research, the design system, accessibility or motion. In the third, several studios each take one slice and report to the company’s own design team. In the fourth, one large firm bundles strategy, design and build. In the fifth, staff augmentation, external designers join in-house teams and work under the company’s managers.
| Setup | Who is accountable | Coordination cost | Procurement load | Speed to start | Knowledge after the contract ends | Inconsistency risk |
|---|---|---|---|---|---|---|
| Lead agency | One agency for design | Low | One contract | Fast once chosen | With the agency unless handover is planned | Low inside the program, higher at its edges |
| Lead plus specialists | The lead for integration, each specialist for its slice | Medium | One lead contract plus smaller ones | Medium | Split across studios | Medium |
| Specialists coordinated in-house | The in-house team | High | Several contracts | Slow | In-house, if someone captures it | High without a system owner |
| Consultancy bundle | The consultancy for the whole program, design included | Medium | One large contract, long review | Slow | With the consultancy | Low inside the program |
| Staff augmentation | The company | High, on your managers | Light | Fastest | Leaves with the individuals unless written down | Set by the in-house lead |
The setups differ most in who does the coordinating. IT sourcing has a name for this role in multi-supplier programs: the service integrator, a layer between the customer and its providers that the customer, an outside firm or both can fill. The idea carries over. In a lead-plus-specialists setup the lead agency plays that part. In an in-house setup your design team does. Melvin Conway observed in a 1968 paper that organizations that design systems end up producing designs that copy their communication structures. Studios that never talk to each other tend to ship patterns that do not match.
When does each setup fit, and how does it fail?
A lead agency fits one large product, or a program with one shared user base, when no senior design leader inside can run it. It fails when the agency becomes the only holder of the system and the research. zeroheight’s guide to design system governance describes hiring an agency as the core team, warns that contractors can need three to six months to learn a product portfolio, and advises making sure “the design system can flourish without the agency.”
Lead plus specialists fits a program that needs depth in several crafts at once when the company cannot coordinate them. It fails when the lead reviews its own work, so nobody independent checks it, or when specialist output only reaches products through the lead’s backlog. That reading is ours, not a published finding.
Specialists coordinated in-house fits a company with a design leader and an operations function, and a gap in particular skills. Nielsen Norman Group defines DesignOps as the “orchestration and optimization of people, processes, and craft,” and lists shared design knowledge and standard tools in its scope. The setup fails when that function has no spare capacity. Nathan Curtis, drawing on consulting across more than 80 design systems, reports that none thrived without centrally allocated people. Several studios feeding one system still need a paid owner.
A consultancy bundle fits a redesign that depends on changes to systems, operations and training that the company cannot staff. It fails when design decisions bend to the delivery plan, or when the system and research sit in the consultancy’s repositories. Ask for design acceptance rights in the contract.
Staff augmentation fits a company with a working method, a design lead and a capacity gap. An IT services firm describes the model as people working under your direct management, with control staying with you (a vendor’s view). It fails when contractors leave and take context with them, because nothing in the model makes documentation anyone’s job.
Which setup fits which situation, and what goes in the contract?
| Situation | Setup that fits | What to put in the contract |
|---|---|---|
| One product or program, no senior design leader in-house | Lead agency | Named lead and team, with notice before changes. An in-house owner approves the design system. Handover milestones where your staff run releases while the agency watches. Working files in a workspace your company owns. |
| Several products or markets, and nobody in-house has time to coordinate | Lead plus specialists | The lead’s integration duties written as deliverables: one backlog, one definition of done, a release calendar. Specialists on the same terms. Accessibility checked by a party that did not build the work. |
| Strong in-house design lead and DesignOps, with gaps in research, motion or accessibility | Specialists coordinated in-house | One brief and one file format for every studio. Deliverables land in your repositories. A named in-house system owner with approval rights. Dates staggered so one studio’s output feeds the next. |
| Redesign tied to a platform replacement, integrations and training | Consultancy bundle | A named design lead. Design acceptance criteria that your team signs. System and research data delivered to your repositories. The right to bring in another design supplier for a later phase. |
| A method exists, capacity does not | Staff augmentation | Your managers direct the work. Decision records are part of each person’s duties. Notice and an overlap period when someone leaves. Access through your accounts. |
| Scope is unclear and stakes are high | Start with a lead agency, add specialists later | A short first phase with a decision point. A rate card and an option to add studios on the same terms. Deliverables every later supplier can open. |
Who owns what: the in-house team or its partners?
Whatever the setup, these five things should stay with the company.
| Item | Owned in-house by | What partners do | What to ask for in writing |
|---|---|---|---|
| Design system | A system owner and an executive sponsor | Build components, document usage, train teams | Libraries and repositories in company accounts. Release approval by the in-house owner. A handover period. |
| Research repository | An in-house research or operations lead | Run studies, deliver raw notes and tagged insights | Raw data in an agreed format. Consent forms that allow your company to reuse it. |
| Final UX decisions | The product owner and design lead | Recommend, show evidence, record the rationale | A decision log. One named in-house approver per release. |
| Accessibility sign-off | An in-house accessibility owner | Design and test to the target, fix defects, report | A named WCAG level. Acceptance by someone who did not build the work. |
| Working files and tool access | The company, with admin rights | Work inside company-owned workspaces | Transfer of final works and working files. Tool accounts not held in the agency’s name. |
The grid rests on a few published points. Nielsen Norman Group says a design system “is only as effective as the team that manages it” and recommends a dedicated team and an executive sponsor. In its December 2021 survey of 353 UX professionals, only 8% reported a dedicated role for managing a research repository, partly because organizations commit to a repository before staffing it. A repository built by a partner with no in-house owner risks going stale once the partner leaves.
For accessibility, W3C’s guidance on planning accessibility work says responsibility should go to named individuals and lists acceptance testing, to ensure that agency-delivered work meets your target level. Its role-mapping draft separates the person accountable for a task from those who help or are consulted.
On files, the AIGA model agreement for design services offers license, assignment and work-made-for-hire options, and notes that with assignment the client receives working files for the final works, not the designer’s preliminary concepts. It is written from the designer’s side, so a buyer has to ask for more. Ownership alone does not give control: one legal guide points out that repositories or design tools under the agency’s name can still leave a client stuck.
What does this guide not settle?
The ratings in the first table are editorial judgments. No study we found compares outcomes across these setups. Much of the evidence is practitioner writing and vendor material, and the integrator idea comes from IT service management, not design. Setups also combine: a company can use a lead agency for one product and staff augmentation for another. Contract terms vary by country, so have counsel review them.
Back in the loyalty example, the program spans four markets and nobody in-house has time to coordinate, which points to the second row. The retailer asks the lead to price integration separately, contracts the research and accessibility specialists on the same terms, names an in-house system owner, and moves the accessibility check outside the lead. Send the three proposals back with that grid and ask each to show how it fits.
