The problem is rarely the people. It is what nobody agreed on before the first meeting.
Cross-functional teams have become the default solution for problems that span departments. Something is not working. The pieces belong to different parts of the organization. So leadership assembles a team from each area, appoints someone to lead it, and schedules the kickoff. What nobody does before the kickoff is answer the three questions that determine whether the team succeeds: Who is in charge when departments disagree? What are the actual deliverables and by when? And what happens to the team members’ performance reviews, which still belong to their home departments?
Charmain Bogue sees this failure pattern in her strategic planning and organizational advisory work. Cross-functional teams look like a solution because they bring the right people together. They fail because nobody designed what those people are supposed to do together, who has authority to make binding decisions, or what it means when a team member’s department head has a different view from the team’s direction.
The Authority Gap
The authority question is the most common point of failure, and the most avoidable. A team lead who has been given responsibility but not authority is in a structurally impossible position. She can gather information and make recommendations. She cannot actually resolve the conflict between two departments, because that conflict exists at a level of the organization above her. Every decision that requires a real trade-off between departments will stall, get escalated, or get made without sufficient information, depending on how much pressure the deadline creates.
The Performance Review Problem
The performance review problem makes this worse in a specific way. The people on a cross-functional team work for two bosses simultaneously. Their home manager still controls their raise, their title, and their next opportunity. The cross-functional team lead has none of those levers. When a conflict arises between what the team needs and what the home department wants, most people resolve it in favor of the person who controls their career. This is rational behavior. Organizations that design cross-functional teams without accounting for it are setting up a predictable outcome and calling it a failure of collaboration.
Four Questions Before the Kickoff
Bogue’s approach starts before the team is assembled. She asks executives to answer four questions before they announce the initiative. Who has the authority to make final calls when the team is split? What do team members’ home managers know about the time and priority commitment? How will the team’s work be reflected in performance evaluations? And what is the explicit deliverable — not the vague mandate, but the specific output, by a specific date?
Those questions feel procedural. They are actually political, because answering them requires executives to commit to things they would prefer to keep flexible. Naming the authority structure means acknowledging that some department heads have more weight than others in this particular initiative. Defining the deliverable means giving up the ability to shift what success looks like as circumstances change.
The Tell
The failure mode Bogue finds most instructive is the one where everyone agrees the team was a good effort. That verdict is almost always the sign that no real decision was made, because real decisions create real disagreements, and real disagreements are remembered. A team that ended without anyone angry probably never had the authority to do anything that mattered.