How to manage cross-functional sustainability teams

Start with a defined outcome

Cross-functional work is easier to coordinate when everyone can describe the result in the same way. Choose a specific outcome, such as improving supplier data quality, assessing a product change or preparing a sustainability disclosure. Agree on what completion means, what evidence will demonstrate progress and which decisions are in scope.

Keep the first effort manageable. A focused workstream lets the team find gaps in ownership and information flow before expanding the approach. Sustainability may coordinate the work, but the people who control relevant processes and records need a meaningful role in shaping it.

Make ownership visible

For each task, record who does the work, who makes the final decision, who provides input and who needs updates. This helps avoid duplicate requests and delays caused by different assumptions about responsibility. Name a backup contact for time-sensitive tasks, and agree on response times and how to escalate a blocked decision.

Ownership should follow the work. Procurement may coordinate supplier requests, finance may explain relevant financial assumptions, and operations may hold process records. The right contributors depend on the project, so do not assume every sustainability initiative needs the same functions or technical expertise.

Create a shared evidence record

Keep working definitions, data sources, owners, deadlines, decisions and unresolved questions in one accessible record. Note where each figure or statement came from, its reporting period and any limitations. This gives reviewers a way to check the evidence and helps the team avoid relying on outdated files or undocumented assumptions.

Agree how updates will be made and reviewed. A simple shared document can be enough for a small project. Choose tools that fit existing access and record-keeping practices rather than introducing a system before the team understands its needs.

Connect sustainability work to business decisions

Different functions assess proposals through different lenses. Before asking for approval, explain the intended outcome alongside relevant costs, operational effects, risks and dependencies. Ask finance early about assumptions or investment information, and consult the teams responsible for implementation before fixing a schedule.

Invite constructive challenge. A supplier-data plan, for example, may need to account for procurement processes and the evidence suppliers can provide. A product initiative may require input from design, operations or other specialists. The goal is not to make every function an expert in sustainability, but to make decisions with the information and experience the work requires.

Build a workable team rhythm

Use short, regular check-ins with a standing agenda: progress against the outcome, decisions needed, evidence gaps, dependencies and next actions. Circulate decisions and owners afterward. Hold focused discussions for complex topics rather than filling every meeting with general updates.

Cross-functional understanding grows when people learn how other teams work. Try a brief knowledge exchange in which one function explains its process, constraints and information needs. Celebrate a resolved obstacle by describing what changed and who contributed, so the team can reuse the learning.

Template: workstream ownership and evidence

Review the record at each check-in. If responsibilities remain contested, clarify the decision-maker and revisit whether the task belongs in the workstream. If evidence is unavailable or uncertain, document the limitation rather than presenting an assumption as a verified result.