Introducing Cross-Functional Teams: Prerequisites and Pitfalls

A cross-functional team brings together specialists from several functions for a shared outcome, and introducing one succeeds when the team holds its own budget and decision rights. In many programs, reporting lines stay in the functions even though new teams are formed. The team then owns the outcome without owning the means, and handovers simply move elsewhere. This article sets out prerequisites and pitfalls and describes a four-step approach. This article provides an overview and does not constitute legal advice.
What makes a cross-functional team
Any team that brings together specialists from several functions for a shared outcome is cross-functional. The form that delivers reliably is the permanent one, in which members belong to the team for most of their time, as distinct from temporary project groups and task forces in which every member remains answerable to two managers and two sets of objectives. The outcome is a product, a customer segment or a value stream, such as order processing from inquiry to invoice.
A cross-functional team differs from an interdisciplinary team in its point of reference. Interdisciplinary describes a mix of academic or professional disciplines, such as engineering and business administration, regardless of department. Cross-functional describes a mix of business functions such as sales and procurement, combined with shared accountability for an outcome. In everyday usage the two terms are often used interchangeably. For the rollout, the only thing that counts is whether the team can deliver an outcome without handing over to other units.
Cross-functional teams exist well beyond IT. One example is order-to-cash teams drawn from sales and scheduling, which take an order from inquiry to invoice. A second is product development teams drawn from engineering and production on the principle of simultaneous engineering. Key account teams combining sales and service also belong here. The overall framework of structure and delivery capability is described in the article characteristics and metrics of a high-performing organization.
What are the advantages and disadvantages of cross-functional teams?
Cross-functional teams shorten lead times and give the outcome a single owner, at the price of specialist depth in the functions and a new steering model. The advantages arise in delivery: decisions are made where the knowledge sits, and waiting times between departments disappear. The disadvantages arise in the functions. Specialists are spread across several teams, so exchange among peers declines. Standards drift apart when nobody maintains them.
The disadvantages can be managed. Redefining the role of functional heads and setting up a regular cross-team exchange for each discipline secures specialist depth. The effect of team size on speed is covered in the article Team size: why small teams deliver faster.
Five prerequisites
Whether a team delivers is decided before its first working day. Five prerequisites make up the test grid.
- An outcome with a metric: the team is accountable for a figure against which it can be measured, such as lead time per order or revenue per customer segment. Without a metric it remains a working group.
- Complete skills: every capability needed for the outcome sits in the team. If a role is permanently missing, the very handover the team was meant to remove reappears.
- Clear decision rights: the team knows what it decides alone and where it needs approval. Methods such as RACI and RAPID and their limits are described in the article Clarifying decision rights.
- Allocated budget and fixed capacity: people and resources belong to the team. As a rule, each person has no more than one main team, with at least 80 percent of their working time.
- Clear leadership: day-to-day professional leadership sits with a role in the team, such as a product owner or team lead. Line management is settled and known to the team.
Who line-manages a cross-functional team?
Line management sits either with the team lead or with the functional head, and the choice follows two criteria. If members belong to the team for at least 80 percent of their time and for more than a year, line management sits with the team lead. If the professional development of specialists is the critical bottleneck, as with a small number of highly specialized engineers, it stays with the functional head, who then serves as the professional home for standards and talent.
In both cases one rule applies: appraisal is based on results in the team. A functional head who appraises against functional targets while the team is steered by outcomes creates exactly the dual structure on which rollouts fail.
Pitfalls in the rollout
Rollouts fail on recurring obstacles that can be checked before the start.
The first obstacle is the dual structure. The team appears on the organization chart, but the functions keep targets and appraisal. Members then work in a matrix in which two lines lay claim to them. When that works and when it paralyses is shown in the article Matrix organization: when it works and when it paralyses.
The second obstacle is part-time membership. Anyone working in three teams at once loses a noticeable share of capacity to coordination and context switching. The team formally has the skill but cannot draw on it.
The third obstacle lies in the target systems. If the annual targets of functional heads stay unchanged, they keep optimizing their own area. The team receives its outcome target, yet its members are appraised against the old functional targets. In a conflict, the function therefore always wins.
The fourth obstacle concerns the role of functional heads. It shifts from issuing instructions to acting as professional advocate, safeguarding standards and talent in the discipline. If this task is not described explicitly, functional heads look for impact by intervening operationally in the teams.
The fifth obstacle is the handling of co-determination. Under German law, new assignments are regularly transfers under Section 99 of the Works Constitution Act (BetrVG), which require works council consent in companies with more than 20 employees entitled to vote. New appraisal procedures fall under Section 94 BetrVG, and a broad restructuring can constitute an operational change under Section 111 BetrVG. Each of these points belongs on the table of the employee representatives before the start, and the individual case is assessed by employment law specialists.
How long does it take to introduce cross-functional teams?
The rollout takes around eighteen months in two stages: a pilot over two to three quarters, followed by expansion in the following year. The pilot needs this time because lead times can only be measured reliably after a start-up quarter.
- Choose the scope: a value stream or product with a clear metric and manageable interfaces becomes the pilot. The choice falls where waiting times between departments are visible today.
- Staff the team and set the rights: members and decision rights are agreed in writing, as are budget and capacity.
- Change the steering: targets and reporting follow the team, as does appraisal. Functional heads receive their task as professional owners.
- Evaluate and expand: after two to three quarters the pilot is assessed against its metric. Only then are further teams scoped.
Cross-functional teams as a delivery task: the role of Niehues Consulting
Niehues Consulting designs and leads the introduction of cross-functional teams from a delivery perspective. Founder Marin Niehues builds organizations that deliver, in projects from VC-funded scale-ups to DAX 40 groups and in 20+ countries on six continents. Delivery management and organization design create structures and decision paths so that the organization delivers reliably in daily business and in transformation. Where needed, Niehues Consulting takes on steering as delivery manager, project manager or product owner and holds the pilot teams to their metric until the line fills the role itself.
The approach follows the Niehues Delivery Model with the phases Understand, Build and Roll out. Three checkpoint questions matter for cross-functional teams. Who decides, who delivers, who uses? Which roles, decision paths and interfaces does operation require? Which metric shows after 90 days that the team is taking hold? The entry point is a free initial consultation of 30 minutes.
Frequently asked questions
What is a cross-functional team?
A cross-functional team brings together specialists from several functions for a shared outcome that it delivers without handing over to other units. In its permanent form, members belong to the team for most of their time and hold budget and decision rights for that outcome.
What does a cross-functional team need to succeed?
A cross-functional team needs five prerequisites: an outcome with a metric, complete skills, clear decision rights, allocated budget with fixed capacity and clear leadership. If one is missing, handovers move elsewhere.
Why do cross-functional teams often fail?
Cross-functional teams mostly fail because of a dual structure in which the functions keep targets and appraisal. Part-time membership of several teams makes the problem worse. In every case, the team lacks control over resources or decisions.
What are the pros and cons of cross-functional teams?
The main advantage is shorter lead times through fewer handovers and clear accountability for the outcome. The main disadvantage is less exchange among peers, which a redefined role for functional heads offsets.
What is the difference between cross-functional and interdisciplinary teams?
Interdisciplinary describes a mix of disciplines, cross-functional a mix of business functions with shared accountability for an outcome. In everyday usage the two terms are often used interchangeably.
What are examples of cross-functional teams outside IT?
Examples include order-to-cash teams drawn from sales and scheduling or product development teams drawn from engineering and production. What matters is a measurable outcome that the team delivers without handovers.
Who is the line manager in a cross-functional team?
For members who work at least 80 percent of their time in the team for more than a year, the team lead is the line manager. If the professional development of highly specialized staff is the bottleneck, line management stays with the functional head. In both cases appraisal is based on results in the team.
How long does the rollout take?
The rollout takes around eighteen months: a pilot over two to three quarters, followed by expansion in the following year. Further teams are formed only once the pilot has been assessed against its metric.
Let’s talk about your initiative.
In 30 minutes we clarify where your organization stands and which step will pay off most now.
Request a consultation30 minutes · free · no obligation


