Back to Magazine

Digital Project Team: Roles, Size and How to Build One

Digital Project Team: Roles, Size and How to Build One

Digital Project Team: Roles, Size and How to Build One

Designer and developer testing a service prototype

A digital project team is a small, multidisciplinary group that owns a digital product or service from research to delivery. It is led by a coordinator or project manager and staffed with the skills the project needs, whether those people sit inside your company or come from outside suppliers. Italy’s public design manual describes it as an interdisciplinary group, internal or sourced externally, whose size and skills match the project. This guide explains what the team does, who belongs on it, how to size it and how to run it.

Hooop
Build a Team That Fits Your Project
Hooop connects companies with carefully selected professionals, helping you find the skills your digital project needs.
Explore Hooop

TL;DR

  • A digital project team is an interdisciplinary group covering user research, prototyping, design and delivery. It is not a single role and it is not the project manager alone.
  • At minimum you need a designer, a developer and a project manager. Add a product owner, researchers and content or data specialists as the scope grows.
  • Keep it small. Official guidance describes effective teams as having fewer than 10 members, with the authority to make decisions.
  • Define the problem before you recruit, then clarify who does what with a stakeholder map and a RACI matrix.
  • If you cannot hire everyone, assemble the team from vetted freelancers, as a managed engagement.

Table of Contents

What a digital project team is and what it does

The Italian operational design manual defines the team as an interdisciplinary group, internal or supplied by vendors, with a breadth of skills that fits the project. Its work spans user research, prototyping, and the design and building of services, interfaces and content.

The Australian government’s guidance puts it in similar terms. A multidisciplinary team is a group of digital specialists that builds services quickly and iteratively, using user research, user-centered design, data and testing.

The common thread is that the team is built around a problem, not around a department. Marketing, design, development and data people work in one group toward one outcome, instead of passing a brief from desk to desk.

What counts as a digital project

A digital project produces a digital output or runs in a digital environment. According to an Italian project management academy, typical examples are web or mobile applications, CRM or ERP systems, marketing automation, e-commerce and SaaS solutions, including in fintech, edtech and healthtech.

A university library describes a digital project as the development of a digital product complex enough to need sequential phases: ideation, design, development and promotion or publication. Its examples include a website, software, an e-book and an interactive app.

Italian public bodies offer concrete cases:

  • UCRONIA, Rome. The waste company AMA built a digital twin that combines AI, IoT and predictive simulation. According to Cityvision, it analyzes more than 200 million geospatial data points across over 100 layers and tracks in real time more than 3,000 vehicles over 11,000 km of roads.
  • ANGELA, Gualdo Tadino. A virtual assistant on the municipality’s website that handles FAQs, navigation, bookings, document requests and reports, using conversational AI and natural language processing.
  • PID Veneto. A program that, according to Unioncamere Veneto, involved 175 small and midsize companies, 3 universities and 5 chambers of commerce in training, workshops and pilots on digital marketing, industry 4.0 and AI.

Most businesses will not build a digital twin. The same logic applies at smaller scale: a new e-commerce store, a lead-generation funnel or a marketing automation setup all need several skills working to a shared plan.

Digital project team, project manager and traditional team: how they differ

These three terms are often mixed up, so it helps to separate them.

Digital project manager Digital project team Traditional project team
What it is One role A group of several disciplines A group organized by function or department
Main job Plan, coordinate, track results, time, cost and risk Research, design, build and test the product or service Execute assigned tasks in sequence
Typical rhythm Reporting and governance Iterative: short cycles, regular reviews Often phased, with handoffs
Decisions Coordinates them Holds the skills and authority to make them Frequently escalated up the hierarchy

The manager is part of the team, not a substitute for it. The Italian public design guidelines expect a project manager and an interdisciplinary team with research, prototyping and development skills, and they note that the composition varies with the size, characteristics and phase of the project. Italy’s digital heritage guidelines likewise give the project manager responsibility for results, time, quality, cost, resources, risks and indicators.

The practical difference with a traditional team is how it is composed and empowered. The Australian guidance says a multidisciplinary team should have the skills and the authority to deliver the service and make decisions, which reduces dependencies on other groups. A functional team that waits on approvals from three departments does not have that.

The roles you are likely to need

There is no single correct line-up. The Italian design manual lists the skill areas rather than fixed job titles: planning and management, primary and secondary research, data analysis, service design, content, interaction and interface design, interface development and transversal skills. Roles and specializations vary by project.

A workable way to think about it is in three layers.

The core three

The UN Development Programme says launching a digital product takes at least three core capabilities: a designer, a developer and a project manager. If you have fewer than that, you are covering gaps with someone’s spare time.

The roles that make it stronger

The same UNDP page names user research, UX/UI, product management and sector knowledge as relevant additions. Italy’s public service guidelines ask for an internal product owner who represents the organization’s goals, knows the service being digitized and keeps attention on user needs. The Australian guidance calls the product manager and the user researcher foundational roles.

For a marketing-led project, this often translates to:

  • a product owner or project lead who decides priorities;
  • a UX/UI designer;
  • a front-end or full-stack developer;
  • a content specialist or copywriter;
  • a performance marketer or data analyst;
  • a project manager who keeps the plan moving.

This list is our practical translation of the skill areas above, not a prescribed structure. One person can cover two areas on a small project. The Italian heritage guidelines make the same point: when you cannot include every specialization, transversal skills help fill the gap.

Specialists you call in for a phase

Some skills are needed only at certain points: a conversion specialist before launch, a data engineer for an integration, a legal adviser for privacy. Plan for them in the schedule so they do not appear as surprises.

How big should the team be?

Smaller than most people expect. Digital.gov.au says a multidisciplinary team is normally small, with fewer than 10 members. A group that size can meet daily, decide quickly and share context without heavy documentation.

If the project is bigger than a team of that size can handle, split it by service or by problem rather than adding people to one group. Each sub-team keeps its own skills and decision authority.

How to assemble the team, step by step

1. Define the problem first

Five steps for assembling a digital project team

UNDP advises defining the problem and the solution before forming the team, and warns that recruiting before the problem is clear risks bringing in skills that do not match the real need. Write one paragraph: who is affected, what is not working, what a good result looks like.

A discovery workshop is a fast way to get there. It should leave you with a clear problem statement, a shortlist of priorities and a view of which skills you need.

2. Map what you already have

UNDP recommends mapping the skills already available in your organization before looking outside. It also suggests including people with direct experience of the problem. In a company, that usually means someone from sales or customer service.

3. Name a coordinator

The Italian design manual says to identify a coordinator who forms and coordinates the group, represents the organization’s goals, monitors progress and promotes collaboration, keeping users at the center. In public administration, that person may be the digital transition officer or the RUP. In a company, it is the project lead or a project manager. If you do not have one, a freelance project manager is a common way to add that skill for the length of the project.

4. Fill the gaps

For the roles you cannot cover internally, choose between hiring, outsourcing a work package or assembling a team of specialists. Each has a different effect on cost, speed and control. Our guides on hiring digital talent in Italy and on when outsourcing marketing makes sense compare the routes in more detail.

UNDP also recommends interviewing suppliers and holding regular meetings with them, at least twice a month.

5. Clarify responsibilities

The Italian manual recommends a stakeholder map and a RACI matrix so that everybody knows who is responsible, accountable, consulted and informed. Our guide to the RACI matrix in marketing has templates you can adapt.

How to coordinate it once it is running

The Italian manual suggests choosing tools, timing and costs, preferring open, collaborative methods inspired by agile, and setting regular meetings, progress checks and retrospectives.

In practice:

  • Short cycles. Two-week sprints with a visible backlog work well for marketing and product work. See our guide to Scrum for marketing, or Kanban for marketing if your work is a continuous flow of requests.
  • One place for communication. Public Italian guidelines point teams to shared environments for documentation, discussion and code. Your equivalent is a single workspace and channel, not five.
  • Structured feedback. Design reviews go faster when comments are consolidated and prioritized. Our method for managing design feedback shows how.
  • Co-design sessions. The design manual describes technical tables as co-design sessions that bring together designers, users and stakeholders, and recommends a facilitator who guides the discussion and ensures active participation.
  • Regular improvement. Review how work flows, not only what ships. Two companion guides cover improving project delivery and team collaboration.

Academic research gives a useful frame. A study in Business Horizons identifies four levers of innovative digital teams: diverse and targeted composition, iterative goal setting, continuous learning and talent management.

The PID Veneto case adds a point: digital projects in small and midsize businesses also need organizational learning and cooperation between companies, universities and institutions, not just technology.

Our perspective

Most digital projects we see do not fail on talent. They fail on assembly. A company hires a designer here, a developer there, a freelance copywriter somewhere else, and then the founder or marketing manager becomes the full-time coordinator of people who have never worked together.

That is the problem we built Hooop to solve. We select professionals through a rigorous, personalized vetting process and look at cultural fit as well as skills, because a team works only if the people can actually work together. Our approach is designed to give you a cohesive group that integrates into your company, so your time goes to strategy instead of managing individual freelancers.

If you are building a digital project team, our advice is to start with the problem, keep the team small and make the coordination role explicit. If you cannot staff all of it internally, a curated team with a shared workflow and workload monitoring is a faster and more predictable route than assembling it one profile at a time.

Marco

Build your team with Hooop

If you need specialists for a digital project and do not want to coordinate a collection of individual freelancers, we can assemble the team for you. Our offer for companies includes Talent as a service, HOOOP Studio and Fractional Management, all built around hand-picked marketing, creative and digital professionals who are vetted for skills and for fit with your company.

Hooop

See how we work with companies or read how team as a service works and when it makes sense. For a first conversation, our company page describes each service. If you need leadership rather than execution, our guides on fractional managers and the fractional CMO explain that model.

Common mistakes to avoid

  • Recruiting before defining the problem. It produces a team with the wrong skills, as UNDP warns.
  • No decision authority. A team that must escalate every choice behaves like a traditional team, whatever it is called.
  • Too many people. Beyond about 10, communication cost grows faster than output.
  • Unclear responsibilities. Without a RACI or similar, two people do the same task and nobody does the other.
  • No product owner. Someone on the client side must represent the goals and keep user needs in focus.
  • Treating the project manager as the whole team. The manager coordinates, the team delivers.

A simple example: an e-commerce relaunch

Imagine a midsize Italian retailer relaunching its online store. The problem statement: checkout abandonment is high and the site is slow on mobile. The marketing director acts as product owner. A freelance project manager coordinates. A UX/UI designer redesigns the flow, a developer implements it, a copywriter rewrites product pages and a performance specialist aligns campaigns with the new funnel.

That is six people, under the 10-person ceiling, with each discipline covered and a clear coordinator. They work in two-week sprints, review progress at the end of each and keep one backlog. The RACI matrix settles who approves copy, who signs off on design and who owns tracking. This is an illustration of the method, not a client case.

FAQ

What does a digital team do?

It researches user needs, prototypes, designs and builds digital services, interfaces and content, then tests and improves them. In a company, that may mean a website, an app, a campaign funnel or an automation setup. The work happens in short cycles, with regular reviews.

What is the role of a project team?

The team brings together the skills needed to deliver the project, while a coordinator forms the group, represents the goals, monitors progress and encourages collaboration. The project manager tracks results, time, quality, cost, resources and risks. Each member owns a discipline and shares the outcome.

How many people should be on a digital project team?

Official Australian guidance describes multidisciplinary teams as normally having fewer than 10 members. For a small project, three to five people covering design, development and coordination can be enough. Add specialists only when the scope requires them.

Can a digital project team include freelancers?

Yes. The Italian design manual says the team may be internal or provided through suppliers. The key is clear coordination, shared tools and defined responsibilities. A curated network such as ours helps you assemble freelancers who already fit your way of working.

Sources