Why Cross-Functional Teams Move So Slowly

Cross-functional teams often move slowly because everyone shares ownership and nobody has clear decision rights. When every function can stop a decision and no one person can make it, the team waits. Members also answer to two sets of priorities, the team's and their own department's, and the department usually wins. A cross-functional team speeds up when it has its own Purpose, Outcomes, and Methods (POM), clear roles for each decision, and operations with clear owners.

Companies build these teams for good reasons. A product launch or a new patient intake process touches more than one department at once, and bringing those departments together should cut down on handoffs and surprises. When these teams stall, the cause is usually in how the team was set up.

Everyone Can Say No

On a typical cross-functional team, each member represents a function. The finance representative is there to protect the budget, and the legal representative is there to manage risk. Every member has a good reason to slow a decision down, and each one can.

Very few of them can say yes on their own. A decision that needs agreement from five functions needs five people to be ready at the same time, with the same information. If one person is out for a week or wants to check with their boss, the decision waits. The team meets again, reviews the same slides, and leaves with the same open question.

The longer this goes on, the more decisions get pushed up the chain. Senior leaders end up settling questions the team was created to answer. That is slow, and it also teaches the team that its own decisions don't count for much.

The team lead is often stuck in the middle. They are responsible for the team's results, but they have no say over anyone's schedule or review. Without help from a senior sponsor, the lead can ask and remind, and little else. A sponsor who agrees with each department head on how much time their person will give the team solves much of that problem for the lead.

Two Bosses, Two Sets of Priorities

Members of a cross-functional team usually keep their regular jobs. Their home department still sets their workload, and their department head still writes their review. When the team's needs and the department's needs compete for the same week, most people choose the department, because that is where their performance gets judged.

Leaders sometimes see this as a lack of commitment. In most cases the structure is the cause. A person cannot give their best effort to two sets of goals that compete for the same hours, and asking them to try produces a team where every task is slightly late.

Give the Team Its Own POM

A cross-functional team needs a POM of its own, separate from the POMs of the departments its members come from. The Purpose answers why the team exists. The Outcomes describe what will be true when the team makes meaningful progress. The Methods lay out how it will get there, in order. They start with the factors necessary, which are the strategies. Next come the tactics that move each factor. Last come the operations, the specific actions that have an owner and a date.

When the team's POM is written down and agreed on, members have a written agreement to point to when their department asks for their time. The department head can see the team's Outcomes and decide, with the team lead, how much of a person's week the team needs. That conversation is much easier to have early than in the middle of a missed deadline.

CliftonStrengths can also help a cross-functional team decide who takes which operation. Members from different departments rarely know each other well. When they share their Top 5 themes at the start, the team can match operations to people who have talent for them. A member high in Arranger may be the right person to coordinate schedules across departments, and a member high in Analytical may be the right person to check the data behind a decision.

One Person Accountable for Each Decision

A simple tool for decision rights is Responsible, Accountable, Consulted, and Informed (RACI). For each major decision or activity, the team agrees on who fills each of the four roles.

The Responsible person does the activity. The Accountable person makes sure it happens, which for a decision means making the final call. The Consulted people give input before the decision or action. The Informed people are told after it is made.

Only one person should be Accountable for any decision. Finance can still be Consulted on the budget, and Legal can still be Consulted on risk, but neither one is waiting for the other to say yes. The Accountable person listens to both and decides, and the team can act. People who are Informed no longer need to attend every meeting, which shortens the meetings for everyone.

Disagreements between functions still come up, and they should. Our Communication4Alignment (C4A) approach asks people to advocate reality, which means the facts decide. When Finance and IT disagree about a timeline, each can bring the numbers behind their view. The Accountable person then decides based on what the numbers show, and the debate does not turn into a contest over whose department has more influence.

A RACI chart takes an hour to build. The hard part is the conversation about who is Accountable, because people often want a veto they never use. Settling that conversation early saves the team many hours later.

Give Every Operation an Owner

Cross-functional teams often leave meetings with action items assigned to a department and not to a person. "Finance will look into it" means nobody will look into it until the next meeting. Every operation needs one owner and one date. When the team reviews its progress, it reviews those operations by name, and each owner reports on their own operation.

The team lead also needs to watch where the team is on the Alignment Meter. A cross-functional team that is waiting on decisions and missing dates will slide toward Struggle, and people will describe the team as a waste of time. Clear decision rights and clear owners give the team visible wins, which helps move it back toward Traction.

The next time a cross-functional team stalls, a leader can start with one question for each open decision: who is Accountable for making it? If the team cannot answer in a sentence, that is the first thing to fix.