Cross-Functional

What is a cross-functional team?

A cross-functional team is a group of people from different functional areas of a company who work together on the same goal. Members come from teams like product, engineering, design, marketing, sales, and customer support. Each member keeps their primary job in their home function and contributes to the shared project alongside the team.

The point is to combine expertise no single department has on its own and remove the handoffs that slow work down. A cross-functional team can be temporary (formed for one launch and disbanded afterwards) or permanent (a standing product team that owns a feature area).

What is an example of a cross-functional team?

A typical cross-functional team for launching a new SaaS feature would include:

• One product manager: owns the spec and the trade-offs
• Two engineers: build the feature
• One designer: owns the user experience
• One marketing lead: positions, prices, and announces it
• One support representative: flags edge cases and writes the help docs

This shape is sometimes called a "feature team" or a "squad". Spotify popularised the squad term, though the company has since said the framework is not quite how their teams really worked. Amazon calls the same shape a "two-pizza team": small enough to be fed by two pizzas, large enough to ship without outside help.

What is another name for a cross-functional team?

Cross-functional teams are also called:

• XFN team: common shorthand in product and engineering
• Multidisciplinary team: same idea, more common in healthcare and research
• Interdisciplinary team: emphasises blending of fields rather than functions
• Squad: popularised by Spotify (which has since distanced itself from the model), now used at Atlassian and similar product organisations
• Feature team or product team: when the team owns one piece of the product end-to-end
• Two-pizza team: Amazon's term, focused on team size as a constraint

The terms are not identical. Multidisciplinary leans clinical; squad implies a permanent setup; XFN is the catch-all in business contexts.

Why are cross-functional teams important?

Most real problems do not sit inside one department. A pricing change is a finance, sales, and product call. A botched onboarding is HR, IT, and the hiring manager. Treating these as single-team problems leads to fixes that work in one silo and break in another.

Cross-functional teams reduce handoffs. Handoffs are where speed and quality go to die. The team puts every needed perspective in the same room, so a decision that would normally take three rounds of email gets made once. It also builds context. The marketer learns what the engineers can ship, and the engineer learns what the marketer is selling.

What are the benefits of cross-functional teams?

• Better ideas: Different specialties produce more original solutions than a single-department team.
• Faster decisions: The people who would normally need to approve are already in the room.
• Fewer broken handoffs: Work moves through the team instead of between departments.
• Stronger communication: Members carry context back to their home functions, reducing silos.
• Employee growth: People pick up adjacent skills and a wider view of how the business works.

What are the challenges of cross-functional teams?

• Two bosses: Each member also reports to a functional manager who may pull them in another direction.
• Slower consensus: Building agreement across functions can delay decisions when authority is unclear.
• Unclear accountability: Without a single owner, tasks fall through the gap between functions.
• Resource conflicts: Departments may not want to give up their best people for shared work.
• Coordination overhead: Aligning schedules and priorities across departments takes real time.

How do you build a cross-functional team?

• Name one accountable lead: The team needs a single owner who runs decisions, not a committee. Authority for this project matters more than seniority.
• Set one shared outcome: Write one goal everyone on the team is measured against. Not five departmental sub-goals stitched together.
• Align with functional managers up front: Get explicit agreement on how much time each member can spend and how the cross-functional work feeds into their normal performance review.
• Keep it small: Five to nine people is the sweet spot. Smaller misses functions; larger slows decisions.
• Settle decision rights early: Before work starts, agree on what the team decides alone and what needs to go to a function head.
• Run short, regular check-ins: A 20-minute weekly sync beats a 90-minute monthly review when work spans functions.

What is a cross-functional employee?

A cross-functional employee is a single individual whose skills or role span multiple business functions. This is different from being a member of a cross-functional team. Examples include a marketing operations specialist who works closely with sales, finance, and IT, or a chief of staff who moves between the CEO's office and every department.

The two ideas are related but distinct. A cross-functional team is a structure (a group). A cross-functional employee is a profile (one person). Cross-functional employees often make the best leads of cross-functional teams because they already speak more than one department's language.