Q&A
Q-0018 · 2026-11-17How Operations Leaders Build Shared Accountability Across Teams
When teams share work, unclear ownership can turn small delays into major setbacks. This article offers practical ways to build accountability, clarify handoffs, and keep progress on track. It also includes insights from experts in the field to help leaders strengthen collaboration across teams.
The perspectives in this article were written by the named contributors and submitted through Connectively. Connectively's automated system selected them and used AI to write the headline, introduction, section headings, summary sections, and illustration, and to make minor edits for clarity. Articles are assembled and published automatically. Report errors to corrections@connectively.us. How we make our content
What the experts said
25 signed answersPut a Single Person in Charge, Report Weekly
Louis DucruetFounder and CEO, EpreztoProjects stall when everyone is involved and nobody is responsible, so what worked for us was making ownership personal instead of shared.
At Eprezto the rule is simple. Whoever proposes an experiment owns it end to end, even if it touches marketing, product and operations at the same time. That person pulls in the help they need from other teams, but the outcome is theirs. The following week they present the results to the team, whether it worked or not.
That weekly cadence does most of the work. When you know you will be in front of the team in seven days with data, competing priorities stop being a good excuse. You go and get the time you need from the other teams because you have to show something. It also keeps the decisions grounded in data instead of in whoever argues hardest in the meeting.
It builds accountability without adding much process. In my experience culture comes from habits you repeat every week, not from slogans.
If I had to give one practical step, it would be to put a single name next to every cross-functional project and a date when that person reports results. Shared accountability works better when it starts with one person who cannot hand it off.
Expose Delay Costs With Pre-Mortems
Competing priorities are often a portfolio problem disguised as a collaboration problem. When every department can declare its own work urgent, the organization has no real priority system, only louder advocates. The remedy is to make the cost of delay visible across the business, including the revenue, risk, or customer friction created by waiting.
We run a pre-mortem before major cross-functional work begins. Each function explains how the initiative could fail, what it needs from others, and which early signal would prove the plan is drifting. Those answers become commitments, not meeting notes. I have seen this reduce behavior because teams are no longer arguing opinions, they are protecting against failure modes they identified together.
Appoint a Coordinator, Set Firm Deadlines
Tammy SonsFounder/CEO, TN NurseryIn my experience if more than one department is involved in a project you end up with shared ownership and no actual ownership. The team will be doing the work but there will be no one actually owning the project. At the nursery we have projects running around inventory, shipping, customer service and technology and there are team members in each of those departments with very different priorities and very different needs. The strategies we've used that have worked are to appoint a single project co-ordinator to own the project as a whole while still allowing the departmental ownership of the project activities, to set specific deadlines and other expectations and to have very short meetings to go through the project status and issues. I don't think you need any more formal meetings, you just need to have someone who is aware of the potential for delays in one department's project work. Greater awareness of project ownership by the team has led to better project and other outcomes.
Name Accountable Interteam Handoffs
Roman SurikovFounder & CEO, Ronas IT | Software Development CompanyI put a named handoff on the plan when several functions share an outcome and none owns the whole project. The sender must provide a complete package, and the receiving person must be able to identify what is missing. Then a priority conflict becomes a decision about a specific input and the work it blocks. A shared deadline alone can't reveal which team is waiting for whom.
We mapped our sales-to-delivery transfer after a project manager got materials that weren't complete. Sales had no single place holding the full package. The manager couldn't read the sales correspondence to fill the gaps, and no one had checked completeness. We also found that sales' reading of the client's context, the scope boundary and the budget ceiling could enter the estimate as established fact; the divergence surfaced later as cost. We changed the transfer: an assistant gathers materials from CRM records, inventories what's present and asks about gaps. A person fills those gaps and confirms the package. The confirmation makes someone accountable for what the next team can use.
For an operations team, I'd write down what each next function needs to proceed and name who checks the handoff. The team should also identify who resolves a rejected package and where a blocker goes when priorities conflict. Keep a brief shared record of the outstanding item, its owner and the decision it holds up. Someone able to reprioritize across functions can act on that record.
Review rejected handoffs with both sides. If the same omission keeps recurring, change what the sender must provide and what the receiver confirms at the transfer.
Acknowledge Every Message Within 24 Hours
Filip PesekCEO, DonnaProWhen no single team owns the outcome, projects stall because everyone assumes someone else is handling it. We deal with that through one very simple rule. If we message you internally, on email or anywhere else, you acknowledge it within 24 hours. You don't have to do the task yet, you just reply. "Got it, I'll handle this by Friday," or "Got it, here are my thoughts." The point is clarity and rhythm, not speed.
For cross-functional work, that habit removes the silence people hide behind. Nobody gets to say they missed the message. We pair it with keeping context visible through written updates, because when people lack context they start making wrong assumptions, and that is when alignment breaks.
Designate Liaisons for Cross-Group Alignment
David JolesChief Operating Officer, PURCOR Pest SolutionsWhat has really helped us out here is making sure that each project and each team always has a team leader. Not only does this person help guide their team, but they also act as the point of communication between other teams. When there are multiple teams working on multiple projects, it helps to have one person at the helm of each one so that it is always known who to go to for questions or help. These point people can meet and talk with each other as needed to make sure that even as each team is working on something different, there is still general alignment and clear accountability.
Document Actions, Rulings, and Due Dates
Stephanie Lewis MSW, LCSW, LICSW, CCTP, C-DBTVP of Clinical Operations, Epiphany WellnessAlthough many departments may be involved in the work, there should still be an owner who is ultimately responsible for the outcome, without necessarily doing all the work.
Delegating responsibility and work to others is a critical project management skill. In addition, a milestone marks a specific point in a project and may have a set of concrete deliverables and a deadline associated with it. Good milestones can involve a number of tasks that teams must complete. Deciding which one(s) have priority can be difficult, especially when there are many vested interests to consider. So, in case of conflicts, it is important to agree on priorities early in the project. This allows the different perceptions and priorities of the individual members to surface and be discussed.
It may seem simple, but project management action logs are incredibly helpful for keeping everyone on the same page. You can also use an action log as a way to keep track of progress made throughout each project. In particular, an action item should have one clearly identified responsible party. Key deliverable dates are agreed to and also documented. The tracking process is also used to monitor the project and each team member's commitment. Likewise, a decision log is a record of all the important decisions your team makes during the course of a project. On larger projects, all change requests, whether pending, approved or declined, may also be kept in a change log.
Rotate Facilitators and Publish Progress Scores
Make a single outcome visible to everyone and give one person temporary control over the process, not the outcome. At Cyber Techwear we've moved away from fuzzy ownership: for each cross-functional project we name a rotating project lead who runs the cadence, keeps a shared task board updated and has authority to call quick decisions across teams.
That person is accountable for delivery milestones, while domain teams remain accountable for their tasks. The practice that built shared accountability was a weekly 30-minute cross-team sync plus a public metrics card linked to the task board.
The sync forces small, fast trade-offs instead of long debates, and the public card shows progress or blockers in one line so blame can't hide in e-mail threads. It changed behaviour: teams start logging delays early and negotiable scope moves to the project lead, so projects actually move despite competing priorities.
Empower an Independent Arbiter With Brief Updates
Kenneth ShenCEO, Founder, PigmentThe honest answer is that most cross-functional projects stall because everyone agrees the work is important but nobody agreed on who makes the hard calls when priorities collide. You can have the best project plan in the world, and it will die the moment two teams have to choose between their own deliverables and the shared one.
What works for us is naming a single decision-maker for the project who is not from any of the teams involved. At Pigment, when we run something that touches product, marketing, and customer success, I'll assign one person whose only job on that project is keeping it moving. They don't do the work. They own the decisions about sequencing, tradeoffs, and deadlines. When someone says "we can't get to this until next week," the decision-maker has the authority to either accept that or escalate it.
The practice that's built the most shared accountability is something simple: a weekly five-minute written update from each contributing team that answers two questions. What did you complete? What's blocked? No meetings, no long status calls. Just those two answers in a shared channel. The transparency alone creates a gentle pressure that's more effective than any accountability framework I've tried. Nobody wants to be the team that writes "nothing" two weeks in a row while everyone else is delivering.
Rely on Confirmed Briefs to Connect Transfers
Neil WebsterCEO, Mills ShelvingFor a shelving project, the customer experiences the quote, product selection, delivery and installation as one job. We keep those decisions connected by working from the same confirmed layout, component list and required date. If a change affects stock or timing, it needs to reach everyone involved before the customer is given a new commitment. That shared project brief makes a handover more useful than a long meeting: each person can see what has been agreed and what still needs a decision.
Anchor Trade-Offs to a Common Metric
Kyle BarnholtCEO & Co-founder, TrewupWhen we face competing priorities, we ask leaders to agree on one operating metric before work begins. It could be cycle time, forecast accuracy, or the cost of delay. This metric makes tradeoffs easier to see because every team understands how postponing a decision affects the wider outcome. It also gives everyone a shared basis for making choices.
Each function then identifies one commitment it can control and one dependency it needs from others. We review both during a short checkpoint without using slides. When priorities clash, we compare them against the agreed metric rather than giving in to the loudest request. This makes alignment a regular practice, not just an exercise in goodwill, and helps us raise constraints early while changes are still easy to manage.
Expose Interdependencies at Work Boundaries
Nikita Patil BrennanSenior Project ManagerCross-functional projects often lose momentum because each team is measured against its own priorities, while the overall outcome belongs to no one. I've found that the key is to make interdependencies visible and assign accountability at the points where work moves from one team to another.
In practice, this means involving the people who understand the day-to-day work, not just those who formally own the function, when defining responsibilities and handoffs. During one of my HR systems implementations, looking beyond job titles to understand who actually made decisions helped us design a more effective approval workflow and improve the age of pending approvals.
Shared accountability doesn't mean everyone is responsible for the outcome in the abstract. It means each team understands what it must deliver, what it depends on from others, and how its delays affect the larger operation.
Secure Reciprocal Commitments After Each Meeting
Brian HansenPresident, Rocket PilotsA useful accountability habit is ending every cross-functional meeting with reciprocal commitments. I ask each team to state one action it will take and one action it needs from another group before the next review. Both commitments are recorded together, so dependencies remain visible rather than becoming separate follow-up items.
This structure encourages balanced participation. No team can leave with a request for others while offering nothing concrete in return. At the following meeting, the discussion starts with those paired commitments and any barriers that prevented completion. Over time, the practice creates a culture where coordination is treated as real operational work, not an informal courtesy.
Validate Responsibility Before Completion
Shared accountability is strongest when the project has a single, measurable definition of done that reflects the customer experience. For example, a readiness initiative is not complete because documents exist or controls were discussed. It is complete when a customer-facing team can answer questions confidently, an engineer can follow the process, and leadership can verify the evidence.
I encourage teams to hold a final ownership rehearsal before declaring success. Representatives walk through the real scenario, including exceptions, escalations, and missing information. This reveals where responsibilities are assumed rather than agreed. The rehearsal also creates useful pressure, since unresolved gaps are visible to every function at once. It replaces abstract alignment with proof that the operating model works under real conditions.
Compare Consequences Before You Reprioritize
Chirag KulkarniFounder & CEO, TacoWe ask each leader to estimate the cost of delaying their part of the project. We consider what could become more expensive, risky, or difficult to reverse if a decision is postponed. This turns a general debate about priorities into a clear comparison of consequences. It also helps us understand which tasks need attention first.
We record these costs on a single page and review them whenever another urgent request enters the queue. A project moves forward not because someone argues the hardest, but because its cost of waiting outweighs other uses of time. This allows teams to disagree on methods while accepting the same priorities. When priorities change, we record the reason for the pause to prevent work from being quietly abandoned.
Measure End-to-End Flow, Diagnose Variance
Cross-functional work accelerates when measurement follows the customer journey or production flow, rather than departmental activity. A team may complete its portion on time yet still damage the outcome through weak inputs or delayed feedback. I recommend one indicator that changes only when every function performs its part, supported by measures that cannot override it.
In environments, the mechanism is an operating review built around variance, not status. Teams examine where throughput, quality, or cycle time diverged, then assign actions at the point of origin. This avoids updates and directs attention to system behavior. It creates a record for discussions, reducing the tendency for a stakeholder to define urgency.
Unify Functions Around Clear Outcomes
Scott ShirleyFounder & CEO, Pledge ItWhen no team owns the outcome, I'd give the project one shared goal tied to the customer. A goal like "nonprofits can run their spring walks without exporting data between tools" gives product, customer success, and sales the same finish line to work toward.
Competing priorities usually come from each team protecting its own work. Our team is small and spread out, so we rely on direct communication. People say what they need from each other and by when, and the trade-offs get settled openly.
The practice I'd recommend is a short weekly check-in where each team answers one question: What do you need from another team to keep this moving? It turns vague delays into specific requests with names attached.
People on our team bring ideas from outside their job descriptions, and a regular check-in gives them a natural time to raise those ideas. When a request has a name and a date, the person receiving it can plan around it.
Build a Success Standard Through Quality Gates
Carol Grojean PhDConsultant, Grojean ConsultingWhen no single team owns the outcome, I've found the answer is to give every team the same outcome to own, and make it visible.
At Microsoft, I led the reengineering of the Developer Division's engineering system after a Visual Studio release shipped 15 months late, with a backlog of more than 30,000 bugs. Dozens of teams each had their own priorities, and each one was succeeding on its own terms while the product failed. So we started with the leadership team defining shared values together, including one that became our anchor: we ship a product, not an organizational structure. Every team aligned to one plan instead of to the org chart.
Then we did something that felt counterintuitive. The entire division stopped new product development for four months to rebuild how we worked. We called it the people's milestone. The people doing the work submitted more than 120 improvement proposals, and we executed 31 of them. Accountability is easier to share when people have authored the system they're accountable to.
Three practices made it real. First, we replaced each team's private definition of "done" with seventeen quality gates that every feature had to pass. Second, we tracked engineering debt as a single number the whole division owned, so no team could look healthy while another sank. Third, we organized work into small cross-functional feature crews that designed, built, tested and delivered together.
The next release shipped in 18 months instead of 39, and estimates went from 50 to 600 percent off plan to within 10 to 15 percent. Shared accountability came from a shared definition of success that everyone could see, and helped build.
Clarify Next Steps With Richer Issue Context
Rahul AgrawalFounder & CEO, QuickIntellI start by separating the owner of the outcome from the people contributing work. A project can involve several teams, but someone still needs to notice when the result has fallen between them. That person should be able to bring an unresolved trade-off to the people who can decide it.
One useful practice from QuickIntell is improving the issue description that operations hands to engineering. We've used AI to organize the context, surface missing information and draft test cases. As I described in a published example, that made communication clearer and handoffs more consistent.
My next step would be to put three things beside that shared description: who owns the next action, what they need from the other team and what evidence will show the issue is resolved. If priorities conflict, that gives the discussion something concrete to work with. "We are both busy" becomes "This dependency is blocking this outcome; which commitment moves?"
I'm speaking as a founder coordinating healthcare software work. Shared understanding helps, but it needs an explicit person responsible for moving the next decision forward.
Set Decision Deadlines, Then Proceed
Nick BaudoinFounder & President, AlkaliWhen no single team owns the outcome, what usually holds a project up is a decision each group assumes someone else will make. What's helped us is putting a date on that decision.
Our projects run across our team and the client's, and the client side often has more than one person with a say. When a decision stalls, we record a short Loom. It walks through the options, says which one we'd recommend and why, and ends with a date we'll go ahead on that recommendation unless someone objects. We put the Loom on the task in ClickUp, where the owner, deadline and blockers already live.
On one website rebuild, the homepage direction sat for about three weeks between two people on the client's side who liked different versions. We sent the Loom with a go-ahead date, and one of them replied the next day with a small change. Then we moved forward.
Once there's a date, saying nothing means we go ahead, and the decision sits on the task where everyone can see it.
It won't settle a real disagreement about priorities. If both sides object, the question goes to whoever can break the tie.
Track Broken Promises to Drive Fixes
Emma RusbyDirector, Zenvy BeautyShared accountability comes from a promise customers can see. When the outcome is written on the website, nobody can quietly treat it as somebody else's job. Cross-functional work stalls in a small retailer for the same reason it stalls in a big company: stock, customer service and marketing each have their own urgent list, and the project that needs all three waits.
Delivery is our clearest example. Express delivery is £9.99, next working day for orders placed before 11am, Monday to Friday (https://zenvy-beauty.com/pages/faqs). Keeping that promise needs stock levels to be right on the site, packing to happen the same morning, and customer service to know what to say when a courier runs late. No single person owns all of it, but every part of the business can see when the promise is broken, because a customer emails within the day.
The practice that built accountability was a short shared log of every missed promise, with the cause and the fix. It is not a blame list. It records that a styler showed in stock when it was not, or that an order missed the cut-off because the label printer jammed, and it names who will make sure that particular failure does not repeat. Reading it together each week turns competing priorities into one conversation about the customer, and the fixes get picked up because the next missed promise would show up in the same log with the same cause next to it.
Surface Friction Beyond Task Completion
Cross-functional work often stalls when we measure success only by completion. Finishing quickly can hide problems, especially when one team creates extra work for another. We review friction at key project stages to catch these issues early. Each team reports new workarounds, unclear responsibilities, or repeated follow-ups instead of focusing only on completed tasks.
This approach helps us spot hidden work while there is still time to address it. It also encourages people to speak openly about problems without fearing blame. We treat leaders who identify these issues as contributors rather than obstacles. We measure progress through both completed work and reduced effort across teams.
Tie Incentives to Collective Results
AlexSandra SislerKeynote Speaker & Retail + Aesthetics Executive, EmpowerServeI find it helps to set a shared team outcome before setting individual goals. In one setting, we tied a quarterly bonus to reaching a team revenue goal focused on improving the patient experience. When team members raised concerns about differences in individual contributions, we added individual goals on top of the shared incentive. Those individual incentives could be earned only after the team met its goal, keeping shared accountability at the center.
Define the Buyer’s Finish Line First
Melody DevemarkCEO, SnoreStopWhen no single team owns the outcome, I write the finish line from the customer's side before any work starts, one sentence describing what a customer will see or receive when the project is done, and every team signs up to that sentence rather than to its own task list. Teams with competing priorities can each finish their part perfectly and still leave the customer with nothing, so the shared sentence is what stops "our bit is done" from counting as progress. Each team then commits, in front of the others, to the date its part will be ready, because accountability between equals comes from promises made in public, not from a manager chasing. Progress meetings start by asking how close we are to that customer sentence, which keeps the conversation on the outcome instead of on whose list is longest.
Use Milestone Feedback to Adapt Processes
Xavier BerknessPresident & CTO, PERC EngageShared accountability improves when the project has a defined learning loop, not just a deadline. In operational work, assumptions fail quickly. A new intake process may create data but slow frontline staff, or an automation may reduce clicks while creating exceptions. Without a way to raise those signals, teams protect workarounds and the project drifts.
I use brief milestone reviews focused on process results, not compliance. The group compares the expected handoff, time, or quality result with reality, then changes one rule, template, or system configuration. Small corrections keep ownership shared because every function sees that feedback produces action. The project becomes a joint experiment, not a departmental mandate.




