Team decisions / Capacity and structure
Choose the team structure your work is missing.
An established team may need a specific contribution. A separate roadmap may need a stable group with complementary skills. Both still need direction, review and accountable decisions. Choose augmentation or a dedicated team by the structure you can actually support, not by the number of people in a proposal.
The practical distinction
Add to a team, or organize a group around a roadmap.
Staff augmentation adds external capability to an existing client-led delivery system. A dedicated team is a stable group aligned to a defined roadmap, with agreed skills, interfaces and continuity. The dedicated team's day-to-day leadership may be supplied by the client, the provider or an agreed combination. Confirm that responsibility separately; the word dedicated does not transfer ownership of delivery.
- Augmentation
- The client already supplies the backlog, direction, working environment and review path. Added contributors join that system to address a defined capability or capacity gap.
- Dedicated team
- A continuing body of work gets an agreed group and team boundary. Product decisions, technical leadership, coordination and integration still need named owners.
- Managed delivery
- Delegating delivery leadership is a separate agreement about responsibility. A dedicated roster can be client-led; a provider-managed engagement needs explicit scope, authority and evidence.
Three buying situations
Start with the gap in the operating model.
These examples illustrate fit conditions. They do not prescribe team size or guarantee that a model will work. Confirm the proposed people, responsibilities and integration capacity.
A working team lacks a specific contribution
01Consider: Augmentation may fit a defined engineering, design or quality gap inside an established team.
- Fit condition
- The team can direct, onboard, review and integrate the added work without creating a separate chain of decisions.
- Client must supply
- A useful backlog, relevant context, permitted access, available leadership and a receiving reviewer.
- Test the proposal
- Walk through a representative change with the proposed contributor and the people who will direct and review it.
- Ownership
- The client keeps product and delivery direction; contributor and supplier obligations remain explicit.
- Inspect
- The contributor can explain the task and the existing team can show how the result becomes accepted work.
- Watch for
- Extra contributors wait for an overloaded lead or produce work faster than the team can review it.
- Choose differently when
- The missing capability is leadership or a coherent delivery structure rather than an individual contribution.
A continuing roadmap needs its own group
02Consider: A dedicated team may fit sustained, related work that needs complementary contributions and accumulated context.
- Fit condition
- The roadmap has a workable boundary, a product owner and a clear interface with the rest of the organization.
- Client must supply
- Direction, decision access, integration requirements and an explicit agreement about who leads the group.
- Test the proposal
- Ask the proposed group to trace a change across its disciplines and into the wider system. Inspect dependencies on client teams.
- Ownership
- The client retains business priorities and agreed acceptance authority; technical and delivery leadership are assigned by agreement.
- Inspect
- A responsibility map, coherent skill mix and reviewable work across the whole change.
- Watch for
- The group is stable on paper but isolated from business decisions or unable to integrate its output.
- Choose differently when
- The work is too fragmented to sustain a useful team boundary, or its required leadership remains unassigned.
Nobody owns the backlog or acceptance
03Consider: Resolve direction and accountability before treating either staffing model as the answer.
- Fit condition
- The proposal promises capacity while requirements, priorities or the definition of acceptable work remain contested.
- Client must supply
- An accountable product decision, a technical authority and a practical acceptance path.
- Test the proposal
- Take one unresolved request and identify who can clarify it, prioritize it and accept the resulting change.
- Ownership
- The business owner must establish decision rights; any delegated delivery responsibility needs an explicit agreement.
- Inspect
- Named owners who can act, with the context and time needed to do so.
- Watch for
- Buying a larger or more stable team disguises an unresolved management gap.
- Choose differently when
- Direction becomes usable and the remaining need can be framed as added capability or a coherent team.
Compare responsibilities
Read beyond the roster.
The columns describe the working models used here. Inspect the actual agreement where a supplier uses the same names differently. Team dedication, management responsibility and commercial terms are separate choices.
| Decision area | Staff augmentation | Dedicated team | Confirm in the proposal | Warning sign |
|---|---|---|---|---|
| Leadership | Joins existing client-led direction | Leadership explicitly assigned to the group | Who plans, resolves blockers and makes technical decisions | Dedicated is treated as a management commitment |
| Scope | Defined contribution within the client's backlog | A continuing roadmap with a useful team boundary | Work included, dependencies and changing priorities | Capacity is offered without usable work |
| Integration | Uses the existing team's review and release path | Needs clear interfaces with surrounding teams and systems | Receiving reviewer and integration responsibility | Local completion is mistaken for accepted delivery |
| Continuity | Knowledge shared with the existing team | Context maintained within and beyond the group | Assignment changes, receiving capacity and handover | One person is the only usable record |
| Accountability | Client directs delivery; supplied contribution is explicit | Client and group responsibilities agreed separately | Acceptance, defects, escalation and release authority | Both parties expect the other to decide |
| Economics | Include client leadership, onboarding and review | Include leadership, coordination and team transition | Equivalent scope, supplied roles and retained effort | A headcount or rate is the whole comparison |
Use the same change
Compare how each proposal would deliver one result.
Illustrative task: change an internal approval rule and update the interface, tests and operating notes. Under augmentation, trace how the specialist joins the existing team's path. Under a dedicated model, trace how the group handles the work and connects it back to the client. The task is an example, not a standard evaluation or promised outcome.
- 01
Name the missing contribution
Describe the work that cannot move forward and why. Distinguish scarce skills, insufficient review capacity, unclear requirements and missing leadership before choosing a staffing model.
- 02
Draw the team boundary
Show which work belongs in the existing team and which could form a coherent roadmap for a group. Mark shared systems, business decisions and dependencies that cross the boundary.
- 03
Trace the change to acceptance
Ask who clarifies the rule, plans the work, implements it, reviews the evidence and accepts integration. Include the client's actual participation instead of assuming it is free or unlimited.
- 04
Test continuity and cost
Ask a receiving participant to explain the change from the available record. Compare onboarding, leadership, review and handover effort alongside supplier charges. Keep unknowns visible.
- 05
Agree the operating responsibilities
Confirm the proposed roles, availability, decision rights, quality evidence and change process. Revisit the structure when the roadmap or retained client capacity changes materially.
Make the structure usable
Protect the work that sits between roles.
Both models depend on more than individual skill. The client and supplier need a practical way to resolve decisions, accept work and preserve context.
- Reserve leadership capacity
- Name product, technical and coordination owners, then confirm they have time to act. An impressive roster does not create review capacity or resolve competing priorities.
- Keep acceptance explicit
- Agree the evidence and responsible reviewers for a complete change. Include integration with the surrounding system and any operating responsibilities, not only completion inside one team's board.
- Maintain knowledge as work proceeds
- Keep decisions, interfaces and operating notes clear, findable and current. Test whether another permitted participant can use them. Documents need maintenance and a receiver.
- Plan assignment changes
- Agree how role changes are assessed, context is transferred and access is removed. Confirm any continuity or allocation commitment in the proposal instead of inferring it from dedicated.
Questions before buying
The label should describe an agreed working relationship.
Similar rosters can support different operating models. Make the responsibilities legible before comparing price or choosing a name.
- Does a dedicated team manage itself?
- Do not assume it does. Confirm who provides delivery coordination, technical leadership, product decisions and acceptance. A stable group can still be client-led. Supplier-managed delivery is a separate responsibility commitment.
- Is augmentation always short term?
- No fixed duration is established by the model. The relevant distinction is how contributors join the client-led work. Define the need, term, review points and continuity arrangements in the agreement.
- Does dedicated mean exclusive full-time allocation?
- Only if the proposal establishes that commitment. Ask about actual allocation, shared roles, other responsibilities and assignment changes. The name alone does not establish availability or exclusivity.
- Which model costs less?
- Compare equivalent work and responsibilities using current proposals. Include client direction, onboarding, review, coordination and transition. Different included roles or retained obligations can make headline prices incomparable.
- Can augmentation grow into a dedicated team?
- It can be reorganized that way, but adding people does not by itself create a coherent team. Revisit the roadmap boundary, leadership, dependencies, acceptance and continuity. Keep the existing structure if a separate group would mainly add coordination.
Source basis
Guidance behind the responsibility comparison.
- 01
GOV.UK Service Manual
Working with contractors or third partiesMain guidance reviewed, updated October 2024. Informs relevant skills, team integration, necessary access and knowledge transfer. Government procurement and contract preferences are not generalized.
- 02
GOV.UK Service Standard
Have a multidisciplinary teamJanuary 2026 guidance reviewed for phase-appropriate skills and decision participation. Its mandated composition, co-location and AI requirements are not imposed on private teams.
- 03
GOV.UK Service Manual
What each role does in a service teamRole descriptions reviewed; updated November 2023. Separates product, service, delivery and specialist contributions. Used as responsibility guidance, not universal commercial definitions.
- 04
GOV.UK Service Manual
Change the size of a service teamMain guidance reviewed; last updated March 2016. Supports attention to onboarding, coordination and continuity. No fixed team-size threshold or productivity forecast is adopted.
- 05
DORA
Documentation qualityCurrent capability guidance reviewed, drawing on 2021 and 2022 research. Informs clarity, findability, reliability and maintenance. Its uplift figures are not used as predictions.
Start with one real workflow
A Systems Audit is the usual starting point. If the opportunity is already clear, we can move directly into a focused build.
Show Us the WorkflowStart with the free automation readiness checklistOBSERVEQUANTIFYDECIDEBUILD