Taking Farmers to Markets Service Delivery Handbook

Delivery teams

A multidisciplinary team (MDT) has the skills needed to understand and solve people's problems.

Organisations traditionally put people with similar skills in the same functional areas. MDTs break these silos by combining people form different disciplines.

Why we work in MDTs:

  • A broad range of skills and roles and quick decision-making processes mean the team can change and adapt as the service evolves.
  • Teams can efficiently grow and retract as the service moves into different phases of development.
  • Team members are given opportunities to stretch their own skill sets by working closely with other disciplines.

MDTs follow human-centred design practices and agile approaches.

# Roles in a multidisciplinary team

MDTs can change in size, but maintain a core group to research, build, learn and improve. The MDT is led by an experienced product manager with decision-making responsibility.

Usually there are 10 roles in multidisciplinary teams:

  • service manager
  • product manager
  • delivery manager
  • tech lead
  • subject matter expert
  • user researcher
  • service designer
  • content designer
  • interaction designer
  • developer.

# Service manager

An experienced senior leader responsible for the overall delivery and operation of the service. They are responsible for the overall experience and ensuring the quality of the service.

Involvement: across all stages, as needed.

# Product manager

Has overall responsibility for the product and team. Works with the team to create the vision for the product, and sets the day-to-day priorities to fulfil that vision and ensure the team delivers. Manages expectations and has input into service-level prioritisation.

Involvement: across all stages.

# Delivery manager

Supports the team, removes blockers to progress, and coaches the team on agile tools and processes.

Involvement: across all stages.

# Tech lead

The most senior technical person in the team. Helps to prioritise technical work and requirements, coaches technical team members, identifies technical options and informs architectural approaches.

Involvement: across all stages, as needed.

# Subject matter expert

Provides in-depth expertise and high-level knowledge (as an authority) in a particular subject area, including policy, legal, regulatory, financial and other disciplines.

Involvement: across all stages, as needed.

# User researcher

Helps the team develop a deep understanding of users, their needs and helps test the service.

Involvement: across all stages.

# Service designer

Works from the user research to identify how a service could be delivered so that it better meets user needs.

Involvement: across all stages, particular focus in Discovery.

# Content designer

Identifies the right format to meet people's needs. Makes sure written, visual and interactive content is clear, accessible and meets user needs.

Involvement: across all stages, particular focus in Alpha and Beta.

# Interaction designer

Responsible for designing accessible and user-focused interfaces, and making use of established design patterns.

Involvement: across all stages, particular focus in Alpha and Beta.

# Developer

Builds quality, well-tested software, sites and architecture according to standards and best practice. May take the role of tech lead if no other senior technical person is needed.

Involvement: across all stages, particular focus in Alpha and Beta.

# Other roles you may need

The team will change through the stages of the service design and delivery process. This is to make sure the team has the right skills to keep learning.

Roles you may need to add to the team:

  • content strategist and information architect
  • business analyst
  • change management experts
  • web operations engineer
  • support operations staff
  • ethical hacker and IT security specialists
  • performance analyst
  • procurement and contract managers