Cross Functional Team Example: 5 Expert Tips for Success (2022)

Tips and Tools for Better Cross Functional Teams

What is a Cross Functional Team?

A Cross Functional team (or Cross-functional team) is a group of people from different disciplines, performing specialized tasks, coordinated to deliver value. A Cross Functional team has a common vision and a clear goal. It has a definition of “done” or “what success looks like” with buy-in from everyone on the team. Team members make the success of the project a priority, and they allocate enough time to make it happen. Continue reading for a helpful cross functional team example.

Cross Functional Team Example Checklist

Figure: Cross Functional Team Checklist

Download Cross Functional Team Checklist

"*" indicates required fields

Name*
Newsletter Signup
Sign up if you are interested in Product Development & Innovation.
Hidden
Hidden
This field is for validation purposes and should be left unchanged.

Benefits & Examples of Cross Functional Teams

Accountability is a major benefit of Cross Functional project teams. Consistent use of teams is a proven way to accomplish any corporate objective that requires multiple disciplines to produce a result that is accountable. 

Cross Functional teams foster innovation. Innovations often come from combinations of disciplines. Cross Functional teams often exceed expectations because of the catalytic nature of putting talented minds together. Cross-pollination can occur when distinctions from one domain port to another, generating an environment that facilitates innovation. We can’t say Cross Functional teams cause innovation, but they are correlated with it.

In product development projects, cross functional teams reduce time to market and increase product throughput and efficiency because they have a more effective decision-making process. While product development is one example, cross functional teams have many applications:  in a marketing team, IT, construction, finance, HR, and process improvement activities.

Cross Functional teams also encourage employee engagement. A Cross Functional team works together as part of a cohesive effort with a common goal. These working groups form a social milieu that many people find uniquely rewarding. More engaged employees perform better, and work longer and harder, with satisfaction. 

A Cross Functional team also concentrates resources and improves efficiency. Team leaders check to see that there are no gaps in skills or required resources. They use resources in a targeted way that employs them and then releases them when the project has no further need for them.

Most companies underestimate or overlook the benefit and opportunity that come from high performance Cross Functional teams. They also fail to account for the opportunity cost of sub-optimal team performance: both in hard costs

  • delayed revenue 
  • higher product costs 
  • higher support costs for low-quality products

And soft costs

  • poor product reviews
  • lack of innovation
  • team fatigue
  • low morale

How Do You Develop Cross Functional Collaboration?

Begin With the Team Leader 

The process of developing a cross functional team begins with the leader. In most organizations a team leader is appointed (self-managed teams, where the leader emerges from the group, are an exception). The leader must have the skills and experience to coordinate teams, and deliver successful results, on time and on budget.

Often this leader is from product development, program management, or the product management functional organizations. A development team may often draw upon technical project managers, as well. 

When a project starts, leaders need to understand the organizational goal of the project and what skills are necessary to achieve it. Leaders need to analyze the skill sets required for success, populating the team with the right individuals, from different areas within the company. The leader works with senior managers to populate the product team with the key skills, calling out where there are gaps, and where the organization might need to acquire resources.

The leader’s responsibility to the cross functional team is:
1) to communicate to the team the vision of the project and its specific goals and,
2) to develop a path to get there.

The leader is also responsible for acquiring the right resources for the team, and for ongoing project management, such as tracking deliverables and milestones. In the case of product development, additional responsibilities are required such as the ability to work with the sales team and finance organizations to ensure that their requirements are satisfied and that communication is fluid.

Have Clear Decision-Making

Once formed, the team and team leader agree on their respective roles and responsibilities. Divide the project into tasks and map their external dependencies. They also determine and map the internal interdependencies between each task, and the related functions and individuals. Assign a Directly Responsible Individual to each task. Here’s a template for a modified RACI chart that can help. 

Resource the Team with Subject Matter Experts, too

Rarely do project teams start with adequate resources to deliver on a predictable schedule. More likely, one of the key risk mitigation efforts is to manage the ebb and flow of resources as individuals work on different projects at different times – but when you need a subject matter expert, the team cannot wait until one is available. And then, invariably, something falls through the cracks, and throws the project off the rails because you didn’t have the right resources in place. 

Unclear definitions of roles – like program manager, the core team, and adjacent teams  – lead to communications and decision-making issues that cause schedule slips, cost overruns, and organizational chaos. This is especially true for companies with organizational silos, but can even hamper small companies and startups.

Developing Agile Teams 

Cross Functional teams are a small portion of Agile development. In Agile development, Cross Functional teams (called Scrums) hold brief, daily standup meetings to eliminate blockers. Roles such as the ScrumMaster, Product Owner, and Team Member are carefully defined. Teams divide their work into Sprints and assess their progress with Story Point burndown charts.

Although Cross Functional teaming is a part of Agile, it is not dependent on any other aspect of it. Organizations performing project-based work of any type, be it a new product development project or an infrastructure improvement effort, can use Cross Functional Teams to great advantage.

Departments and Functions Support High Performance Teams

By its very nature, a Cross Functional Team crosses different departments including your own department (assuming you are in a traditional organizational structure which is functionally organized).  No matter if you are in the sales department, marketing department, or engineering department, high performance teams depend on collaboration and breaking down the barriers of various departments allowing the group members to “swarm”  (Agile scrum term for self managing teams) and collaborate on a project.  

Often these departments are called “functional homes” because members are assigned to teams over the duration of the project, but when the projects are done, they return to their own departments.  If team members can easily flow between their home and teams where they are needed you have the best organizational structure – team members are aligned with projects and contribute to their success but their professional growth and career development is overseen by the department from which they came.  Functional homes are not a bad thing either, if you are trying to build your core competencies and standardize processes. Keep in mind the tools and resources needed in establishing high performance teams.

Cross Functional Team Example: Core Team Model

This Cross Functional Team Model is from a new product development project, showing the typical functions for a system level product containing hardware and software (apps). Also known as the Project Team Wheel, this organizational diagram is based on a core team concept.

Put the team leader in the center of the team wheel. Then sketch out the core team around the leader, including the key functions and individuals within them. Outside of the core Cross Functional team, place the extended team members. The extended team includes the functions that will support or augment your team intermittently throughout the project (including a marketing team, developers, analytics team, etc.)

Cross Functional Team
Cross Functional Team

Figure: Product Development Cross Functional Team Example Diagram

Most projects are interdependent and complex. They require technical skills but not on a full time basis. The Project Team Wheel identifies which Cross Functional team members cover which functions. 

Using the Project Team Wheel at the beginning of a project ensures that you have a clear team structure with established leadership, and with all necessary functions on board. The tool also helps you to establish who has responsibility for top-level deliverables. It also:

  • Identifies skill gaps on a team.
  • Ensures you’ve accounted for all stakeholders.
  • Minimizes unwelcome surprises when you fail to have needed resources.

How to Build Cross Functional Teams

Define roles and responsibilities as clearly as possible

Defining team roles and responsibilities seems like a trivial task that is more bureaucratic than useful. But the lack of clarity around cross functional deliverables and dependencies causes missed opportunities to reduce cycle time, manage resource gaps, and stem team chaos. Creating cross functional teams correct takes some time, but is well worth it.

Having clarity around who is doing what and when will free up teams to focus on the work required to innovate and deliver products to market. You might want to tackle this as part of a team building activity.

Implement a core-team model for the Cross Functional team

Implementing a core team model is the most effective way to optimize a specific project team’s performance, reduce cycle time, and ensure that the extended team is functioning efficiently.

Cross functional teams typically consist of four to six team members, under a team leader (or Product Owner), drawn from different functional areas or various departments. For example, in a product development project these leads might include representatives from program management, product management, engineering, design, manufacturing, and quality assurance. The team shares the responsibility of delivering the project within the defined objectives.

The core team meets frequently, typically once per week. It is responsible for communicating with the extended team. With an emphasis on strong leadership skills, the team can serve as an effective nucleus for driving execution, escalating project issues, and managing cross functional dependencies.

Empower the Cross Functional Team with a high level of authority

If you establish a culture of team accountability across your organization, and empower your team to drive daily decision-making, you will see measurable gains in the team’s ability to creatively innovate and shorten cycle time. While there are some circumstances where command-and-control leadership is appropriate, we’ve found that if you use it as the norm, it will result over time in lower accountability, demotivated teams, and delays. 

Giving the team a maximum of responsibility is a strategic investment in attracting the best talent. High-performance teams consist of high performers — both individually and as a team. High performers on cross functional teams thrive on accountability. If you make the team accountable, you will tend to attract the best people.

Foster a culture of trust and team collaboration

Teams can only achieve high performance if they work in an environment of trust and collaboration. Anything less means that individuals will shift their focus from the common good to their own survival.

Notice what happens in your organization when bad things happen: when the schedule slips, a quality issue has stopped the manufacturing line, or the product cost is exceeding the margin target. How does your organization respond? Teams achieve high performance when they know they can deliver bad news — with their recommendations for mitigation and resolution.

A Cross Functional team is more likely to achieve high performance when they work in an environment that emphasizes problem solving rather than a culture that is about finding the guilty and blaming them. And because senior managers have created an environment of empowerment and trust, they get projects back on track faster than those teams that work in a less trusting environment.

Have clear lines of communication and clear metrics to track progress (no traffic lights!)

Having ways to communicate efficiently and effectively across cross functional teams is the best way to build trust between managers and the cross functional team members.

This includes relatively “frictionless” ways to provide frequent written updates (weekly or biweekly). It can be as simple as a planning/doing/done list for Agile methods; or a project dashboard. Slack and other chat methods are effective ways to increase velocity too.

Figure: Cross Functional Team Tracking

Figure: Cross Functional Team Tracking

Reporting progress is also important. For example, with a traditional development process, drawing a vertical line drawn on a Gantt chart is one of the fastest ways to show progress. If all milestones are on track, this line is straight. If a task is behind schedule, the progress line will deviate to the left indicating the true progress of a team on that task. Traffic lights (Red-Yellow-Green) are ineffective at demonstrating progress because they are too subjective.

With Agile programs, a story burndown chart is the best way to show a team’s progress. In Agile environments, the team estimates all tasks, and only when the task (story or feature) is completed are the points subtracted from the starting backlog.

Minimum Requirements for Cross Functional Team Success:

  1. The right leader
  2. Qualified people in their roles
  3. Optimal allocation of team resources [people, budget]
  4. Explicit ground rules from management
  5. Clear team goals and clear communication

5 Tips for a Better Cross Functional Team

1. Find the right leader

The right leader is someone who is trustworthy, competent, capable and of the right stature for the challenge. The team leader ideally is someone experienced in being both a member and a leader of Cross Functional teams.

2. Have qualified people in their roles

People and their relationships are incredibly important to innovation. How much more effective do you think your most productive contributor is in relation to your average contributor? Whether you think this ratio is high in your organization or not, no one can argue the fact that individuals make a huge difference. Teams consist of people and it’s imperative to get the chemistry right.

3. Allocate team resources optimally [people, budget]

Even the best cross functional teams, with the very best members, get hamstrung without the right funding or adequate facilities for prototyping or testing. Management’s job is to make sure that the team has everything they need to be successful. Make sure your people are not spread too thin. Between one and two projects is the optimum load, though a dedicated team is best if you want the team to succeed.

4. Make explicit ground rules with management

Cross functional teams are most effective when senior leaders, the team leader, and team members have clear rules of engagement. They know their roles and responsibilities and how they relate to what everyone else is doing. Teams also have a clear and explicit escalation path to correct the team’s direction if it starts to go off track.

5. Have clear goals and clear communication

Effective Cross Functional teams have a clearly agreed-upon goal that is measurable and they also continue to communicate throughout the project. Many Agile teams have short daily meetings, which is a best practice for high performance teamwork. Clear objectives and good communication skills help propel teams to create spectacular results.

John Carter, TCGen Principal & Founder

John Carter

Principal, TCGen Inc.

John Carter is a widely respected expert on product development and product management.  He is the co-inventor of Bose’s Noise Cancelling Headphones and designer of Apple’s New Product Process (ANPP).

As Founder of TCGen Inc., he has consulted for Abbott, Amazon, Apple, Cisco, HP, IBM, Mozilla, Roche, 3M and many other organizations.

He is the author of “Innovate Products Faster,” a handbook for accelerating product development.  He currently serves on the Cirrus Logic board of directors. John has a MS in electrical engineering from MIT.