Leading Cross-Functional Projects Without Authority

Takeaway: Before a cross-functional project starts, agree on the outcome, sponsor, decision rights, and named owners.

A pricing change touches finance, sales, product, and legal. The work can stall even when every participant is capable: finance needs an approved margin floor, sales wants flexibility, product needs lead time, and legal won't review language that is still changing. A chief of staff may own none of those teams, but can make the sequence and decision rights explicit.

One study offers a useful governance lens. Behnam Tabrizi studied 95 cross-functional teams across 25 leading corporations and found that nearly 75 percent were dysfunctional, failing on at least three of five measures: staying on budget, staying on schedule, meeting specifications, meeting customer expectations, and staying aligned with company goals (Harvard Business Review). The striking part is why. In this sample, weak governance was associated with poor results, including unclear ownership, vague goals, limited accountability, and weak organizational priority.

Clarify the project's governance

In Tabrizi's sample, teams classified as having strong governance succeeded 76 percent of the time, compared with 19 percent among teams without it (Harvard Business Review). Governance here doesn't mean bureaucracy. It means a small number of things being explicit that are usually left implicit: who decides, who does the work, what "done" looks like, and who is accountable when it slips.

When a cross-functional project drifts, it's tempting to read the problem as a people problem. The engineering lead isn't responsive. Marketing keeps changing the ask. Finance went quiet. Sometimes that's true. Before drawing a conclusion, check whether the goal is fuzzy, the person's role was never defined, or the work isn't a stated priority for their own manager. Clarify the structure first, then address the competing incentives or relationship problem that remains.

This is the operator's opening. You may not command these functions, but you can ask the group to make its working agreements explicit.

Start with a real charter, not a kickoff meeting

A kickoff meeting and shared document don't establish alignment on their own. Before the first working session, get four things written down and agreed.

The objective, stated as an outcome. Not "improve onboarding" but "reduce time-to-first-value for new customers from 14 days to 7 by the end of Q3." Tabrizi identified vague goals as one problem in the dysfunctional teams he studied. If you can't state the objective as a measurable outcome with a date, you're not ready to start.

The sponsor. Tabrizi found that executive sponsorship is one of the strongest differentiators between projects that work and projects that stall. A senior leader who has publicly said this matters gives you something to point to when a function deprioritizes the work. Name the sponsor, confirm they will spend real attention on it, and use their standing rather than pretending you have your own.

Decision rights. Write down who decides what. Separate the people who are consulted from the person who makes the call. Ambiguity here is what produces the endless re-litigation that kills momentum. When a decision is made, the decision log should say who made it and why, so it stays made.

Roles. A lightweight responsibility map, even a simple one that marks who is responsible, who is accountable, who is consulted, and who is informed, prevents the two failure modes at once: work with no owner, and work with three owners who each assume someone else has it.

You can draft these agreements without formal authority, but the participants and sponsor still need to accept them. Ask for that agreement explicitly.

Convert the objective into owned commitments

A charter aligns intent. Delivery comes from commitments. The operator's job in the working phase is to translate the shared objective into specific pieces of work that specific people have agreed to own by specific dates, and then to keep that list honest.

The mechanism matters less than the consistency. A single visible tracker gives the group a shared record and reduces the need for separate status requests. When status is legible to the group, contributors can see dependencies, raise constraints, and renegotiate dates before a miss surprises everyone.

Two habits keep the tracker credible. First, every item has one name next to it, never a team name. "Marketing to review" isn't a commitment; "Priya to review by Thursday" is. Second, you update it whether the news is good or bad. A tracker that only shows progress is a marketing document. A tracker that shows slippage early is a management tool, and it's the thing that lets you raise a problem while there's still time to fix it.

Influence is how you get the commitments, not a substitute for structure

Structure tells you what needs to happen. Getting busy people who don't report to you to actually do it is where influence comes in, and it's worth being deliberate about. The exchange model from Allan Cohen and David Bradford is the practical frame: people cooperate when you understand what they value and offer something that helps them get it (Cohen and Bradford, Influence Without Authority). For a cross-functional lead, the currency you control is often exactly what a stalled contributor needs: air cover on a competing priority, a cleaner decision so they stop redoing work, visibility with the sponsor, or simply removing three other things from their plate so this one can move.

Match the case to the person. Ask each contributor what outcome, risk, constraint, and competing priority matters to them. Frame the request around the contributor's goals and constraints rather than relying on your principal's wishes. This is a large enough topic that it has its own playbook, but the short version is that you lead cross-functional work by making cooperation easy and worthwhile, not by leaning on proximity to the boss.

Suppose the pricing project needs a legal owner, but the legal lead can't absorb another review cycle. Ask what would make a commitment workable: a frozen draft by Tuesday, one consolidated review instead of three, or sponsor agreement to move another request. Record the owner, dates, and accepted condition. If no tradeoff is available, take the priority conflict to the sponsor as a decision.

Reserve sponsor escalation for decisions that genuinely need it.

Drive to a close, then actually close it

Cross-functional projects can trail off rather than end. The launch happens, attention moves on, and final handoffs or documentation remain unfinished. Part of the operator's job is to create a clean close: confirm the objective was met against the number in the charter, capture what was decided so it doesn't get re-opened, hand off any ongoing ownership to a named person, and tell the sponsor and the group it's finished. A visible ending confirms the result, preserves the record, and tells contributors where ongoing ownership now sits.

FAQ

Do I really need a sponsor if I have the CEO's backing informally? Ask the executive to name the sponsor and make the priority explicit. Informal backing may not resolve a conflict between the project and a function's quarterly goals. A named sponsor who has publicly prioritized the work gives you something durable to point to.

How do I hold people accountable without authority? Record one owner and date for each commitment, surface constraints early, and use the shared review to renegotiate work or escalate a decision. The tracker supports the conversation; it doesn't create authority.

When should I escalate to the sponsor versus handle it laterally? Handle routine coordination and sequencing within the group. Escalate priority conflicts, scope decisions, or resource tradeoffs that the group can't resolve. Bring the sponsor the options, consequences, and a recommendation.

For more practical operating guidance, join The Brief, the free weekly newsletter for executive-operations professionals.