Cross-Functional Team · Cross-Functional Collaboration
Cross-functional Team
What is a cross-functional team?
- A team structure that brings people from several functions together
- Decision authority, a single goal, and allocation rates are the prerequisites
- A team with no end date just adds another layer
Mixing departments does not make work faster. What this organizational form actually changes is not the seating but the point where decisions are made. Previously, to change a single screen or component, development had to get approval from the planning team and then relay the result to marketing. On one team, those three round trips shrink to a single meeting, half a day at most. In other words, the team’s real output is not a better atmosphere but less waiting time. If the waiting time stays the same, only the name has changed.
Distinguishing it from similar structures makes the design easier. A committee is a forum for gathering opinions, a task force is a time-limited project organization, and a cross-functional team is a unit that executes and decides in the same place. Three numbers work well in practice: keep the team to 5–9 people, keep core members’ allocation at 50% or more, and keep items the team cannot decide and escalates to no more than 20% of the total. In particular, once allocation drops below 30%, it is more accurate to treat that person as an advisor than as a team member.
If you leave evaluation and reporting lines untouched, the rest of the design falls apart. If the team leader tracks the schedule without any authority over evaluations, members will handle their home department head’s instructions first the moment they arrive. Lock in that team goal attainment counts for at least a set share of individual evaluations, and put in writing, for each home department head, a statement that “this person’s first-half work is this team’s assignment.” A collaboration declared without changing the evaluation form rarely lasts past two months.
The most common misconception is that gathering people together improves communication. Gathering them without authority actually increases the number of meetings. Because everyone goes back to their own department to report again, reporting paths double and decisions get slower than before. Another mistake is not setting an end date. A team created for a single launch that is still around a year later becomes a quasi-permanent organization and ends up fighting with existing departments over where the work boundaries lie. Often, writing down the disbanding conditions at the start matters more than forming the team.
Ara LimExpert in global leadership, AI, and business communication
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum ConsultingIt spread through concurrent engineering in manufacturing, as a way to cut the inefficiency of stage-by-stage handoffs in new product development. Later, in agile development and product organizations, teams that include every needed function became the standard model.
Company A makes industrial components, with 320 employees and annual revenue of about KRW 80 billion (≈ US$59,853,400). Over the past three years, new product launches ran 5 months behind plan on average, and each design change took an average of 3 weeks to process. R&D and the production division were each blaming the other for the cause. (Hypothetical example)
- When the CEO pulled the turnaround times for the 47 change requests of the past two years, the average was 21 days per request, of which only 4 days were actual review and the other 17 days were spent waiting for approval.
- They brought together five people (the head of R&D, a production engineering manager, the quality lead, a purchasing associate, and a sales director) in the space next to the third-floor meeting room to form a “New Product Launch Team,” fixed each person’s allocation at 60%, and handed their home-department work to stand-ins.
- In the first meeting, the CEO drew the line: “Settle mold revisions up to KRW 30 million (≈ US$22,400) in this room, don’t escalate them to me.” That one sentence cut approval of change requests from four steps to one.
- The HR head redesigned the five members’ first-half evaluation forms, setting team goals at 40% of the weighting and lowering the weight of home-department results. The sales manager was no longer pulled into weekly department performance meetings.
- In week 8, the team added “disband three months after mass-production stabilizes” as the last line of the team charter, and named the quality lead in advance as the owner to inherit any remaining issues.
- The next new product launched 3 weeks behind plan, and the design change turnaround dropped from 21 days to 6. The team disbanded as promised the following March, and all five members returned to their home departments.