← Back to Issue

How do I create accountability without authority?

From Leadership in Tech · subscribed via aiste.ulozaite@gmail.com · original ↗ · unsubscribe

Cross-functional leaders often assume that once a commitment is made in a meeting, it will hold. It rarely does without deliberate structure to support it. Accountability in a matrix organisation must be built through precise agreements, visible records, and early conversations about competing priorities. The goal is habits the whole group owns, not just the leader, so accountability survives long after any single person moves on.

• View Larger Image

How do I create accountability without authority?

I was coaching a Transformation Lead three months into a cross-functional cost-reduction programme. The launch had gone pretty much okay. She had built influence with the key functional heads. She had invested time to build a network that spanned several divisions. She had run a steering group that, by every measure of convening, had worked. People left meetings with clear commitments. Energy was high. Then, at the end of the quarter, she pulled together the numbers. Fewer than half of those commitments had actually been delivered.

Nobody had pushed back in the room. Nobody had openly abandoned their commitment. They had simply not done it. When she raised it, the explanations were reasonable. Resourcing had shifted. A line manager had reprioritised. Something more urgent had come up. Every individual explanation made sense. Together, they meant the programme was quietly failing. This is a common issue I see in many organisations.

She had not built an accountability problem by accident. She had built it by assuming that commitment, once made, would hold on its own.

This is one of the most common and least discussed gaps in matrix leadership. Influence creates support. Networks create connection. Convening creates commitment in the room. None of these capabilities answer a different question: what happens when a commitment starts to slip, and you have no formal authority to enforce it? In a hierarchy, accountability is structural. It is built into the reporting line, the performance review, the consequence for non-delivery. In a matrix, none of that structure exists for the commitments that matter most. You are accountable for outcomes that depend on people you cannot direct. The accountability has to be created, deliberately, or it does not exist at all.

What accountability actually means without authority

Consider two versions of the same missed deadline.

In the first, a programme director discovers a commitment has slipped and goes straight to the line manager. The manager applies pressure. The work gets done, eventually, but the relationship between the programme director and the function cools. The next commitment is hedged before it is even made. In the second, a different leader notices the same kind of slip early, because she had built a habit of checking in before deadlines rather than after them. She names what she is seeing, asks what is getting in the way, and works out with the person what needs to change. The work gets done. The relationship, if anything, strengthens.

Both leaders cared about the outcome. Only one built accountability. The first relied on positional pressure borrowed from someone else’s authority. The second built something that did not depend on anyone’s authority at all.

Accountability cannot be assigned in the way a task can be assigned. A manager can hand a piece of work to a direct report and trust that performance management will eventually catch any failure to deliver. A matrix leader has no equivalent lever. Accountability has to be built differently: not imposed on people, but chosen by them, because the agreement they made was clear enough to hold them to it.

This distinction matters more than it first appears. Most accountability problems are not motivation problems. They are clarity problems. A commitment that sounded firm in the meeting often turns out, on closer inspection, to have been vague enough that everyone could interpret it differently. “I’ll look into resourcing” is not a commitment. It is an intention with no shape. It cannot be missed, because it was never specific enough to be met. When accountability breaks down in a matrix organisation, the first question worth asking is rarely why didn’t they deliver. It is usually: was the agreement specific enough that both of us would have described it the same way a week later?

This is also where accountability without authority differs most clearly from accountability with authority. A hierarchical leader can compensate for a vague agreement with positional pressure. A matrix leader cannot. The agreement has to do all of the work. The quality of the agreement matters far more than it does in a reporting relationship.

This article is a deep dive on accountability, the fourth of the four capabilities explored in How do successful leaders create commitment in matrix organisations? That article introduced the full framework: influence, networks, convening, and stewardship. This article takes the stewardship capability and applies it to the specific practice of holding people, and yourself, accountable when you have no formal authority to do so. The other deep dives in this series cover what a matrix organisation is and why companies adopt one, how to build influence without authority, how to build a powerful internal network, and how to convene people who don’t report to you.

Why accountability fails in matrix organisations

Before exploring what works, it is worth naming the patterns that quietly undermine accountability in environments without formal authority.

Mistaking agreement for accountability: A steering group nods along to a plan. Everyone appears aligned. Agreement in the room and accountability for delivery are not the same thing. Leaders who treat them as interchangeable are repeatedly surprised when commitments evaporate without anyone openly disagreeing.

Relying on goodwill instead of structure: Many matrix leaders, lacking formal authority, default to relationship as their only accountability mechanism. They hope that because people like and respect them, commitments will be honoured. Goodwill matters. It is not a system. It does not survive contact with a competing deadline from someone’s actual line manager.

Confusing escalation with accountability: When a commitment slips, the instinctive response is often to escalate to the person’s manager. This can occasionally be necessary. Used as a default, it teaches people that accountability is something done to them by someone above, rather than something they hold for themselves. It also damages the relationship the matrix leader depends on for the next initiative.

Accountability that exists only in the room: Commitments are made in a meeting and never referenced again until the next one, by which point the specifics have softened into something closer to a general intention. Without a visible record, accountability has nowhere to live between gatherings.

Nobody owning the gaps between functions: Each function may be entirely accountable for its own piece of work and still produce a collective failure, because nobody held accountability for the handoffs, dependencies, and white space between functions. In a matrix, the most important failures often live exactly where nobody has formal ownership.

The five practices of accountability without authority

Practice 1: Make commitments specific and visible

A commitment that lives only in someone’s memory of a meeting is not yet an agreement. It becomes one when it is specific enough that both people would describe it the same way a week later: what will be done, by whom, by when, and what they need from others to make it possible.

A regional sales director once told me about a quarterly business review that had run for two years with the same pattern. Each function reported progress, each leader nodded at the others’ updates, and the meeting closed with what felt like alignment. When a new finance lead joined and asked to see a written record of what had actually been agreed in the previous three meetings, nobody could produce one. The commitments had existed only as a shared impression in the room, and that impression had been quietly different for each person who held it.

The Transformation Lead found something similar when she went back through her own meeting notes. Her steering group had been ending sessions with a shared sense that everyone knew what they needed to do. The actual commitments were almost entirely undocumented and largely unspecific. “Finance will look at the budget implications” had been recorded as an action. Nobody, including the finance representative, could have said with confidence what doing that actually required, or by when.

She changed two things. She stopped ending meetings with a summary she wrote herself, and started asking each person to state, in their own words, what they were committing to before they left the room. She began circulating a short written record afterwards: who committed to what, by when, what they needed from others. The record was deliberately brief. Its existence changed the social dynamic. A commitment that has been written down and shared is harder to quietly let slide than one that only ever existed as a shared impression in a meeting.

Questions you can use to sharpen vague commitments into accountable ones:

• “If I described what you’ve just agreed to do, in one sentence, would you describe it the same way?”
• “What does done actually look like for this, and how will we both know when it has happened?”
• “What do you need from someone else in this room to make this possible, and have they heard that?”
• “Is there anything about this commitment that still feels vague to you?”
• “What would make this commitment fail to happen, even though everyone meant it sincerely?”

Practical actions:

•  Go around the room and have each person state their commitment in one sentence, in their own words, before anyone leaves. If they can’t say it clearly, it isn’t a commitment yet,  it’s still an intention.
• Send the written record within 24 hours, while the meeting is still fresh enough for anyone to correct a misunderstanding before it hardens into a different version of events.
• Test every commitment with one question before you accept it: What would have to happen for this not to get done? A vague answer means the commitment is still too vague.

Practice 2: Hold the system to account, not just individuals

It is tempting, when accountability breaks down, to look for the individual who failed to deliver. In a matrix organisation, this is often the wrong unit of analysis. The most damaging failures frequently occur not because any single person dropped their commitment, but because nobody held accountability for what happened between functions: the handoff that was assumed but never confirmed, the dependency that one team didn’t know existed until it was too late.

A technology director described a launch delay that had taken weeks to diagnose properly. Engineering had delivered on time. Marketing had delivered on time. Customer support had delivered on time. The launch still slipped, because nobody had been accountable for confirming that the three workstreams were actually synchronised with each other. Each function had met its own commitment. The system had still failed.

Effective matrix leaders learn to ask a different first question when something goes wrong. Not who missed this, but where in the system did this fall through, and was anyone actually accountable for that gap? Often the honest answer is that nobody was, because the work had been divided cleanly between functions and the connective tissue between them belonged to no one.

The Transformation Lead discovered this directly when a delay in one workstream caused a downstream problem for another. Her instinct was to ask the first team why they had been late. The more useful question turned out to be why nobody, including her, had been tracking the dependency between the two workstreams in the first place. The individual teams had each been accountable for their own piece. Nobody had been accountable for the join.

Questions you can use to surface systemic rather than individual accountability gaps:

• “Whose responsibility is the space between these two pieces of work, not just the pieces themselves?”
• “If this fails, will it be because someone didn’t deliver, or because nobody owned the connection between deliveries?”
• “What dependencies exist that nobody in this room is explicitly accountable for?”
• “Where are we assuming a handoff will happen smoothly without actually confirming it?”
• “If we mapped every commitment in this programme, what would be missing from the map entirely?”

Practical actions:

•  Before launch, walk through every major handoff and ask one question out loud with both functions present: what happens downstream, and to whom, if this slips by two weeks? An answer nobody can give is the clearest sign that ownership of that handoff doesn’t actually exist yet.
• Name an owner for each handoff, not just each deliverable, and make sure that person understands the consequence of the gap, not just the task either side of it. Owning a handoff means owning what happens if it fails, not simply confirming both functions are aware of it.
• When something goes wrong, resist the pull to ask who failed. Ask instead what the consequence of this gap was, who absorbed it, and whether anyone could have seen it coming from where they sat. The answer usually points at the system, not the person.
• Revisit the dependency map at every major milestone, not just at launch. Ask whether any handoff has quietly lost its owner as priorities shifted, and what the consequence would be if that gap went unnoticed until delivery.

Practice 3: Surface trade-offs before they become excuses

Competing priorities are a permanent feature of matrix organisations, not a temporary problem to be solved. Left unspoken, they tend to surface later as explanations for missed commitments rather than as decisions made openly in advance. “I would have delivered this, but my manager asked me to prioritise something else” is a trade-off that was real. It was never actually discussed with the people depending on the original commitment.

A procurement lead once told me about the moment she stopped being surprised by missed commitments. She had started asking, at the beginning of every meeting, whether anyone was holding a commitment that now felt at risk because of something else competing for their time. The first time she asked, the room went quiet. Then one person admitted it, and two others followed. Nothing about the underlying pressures had changed. What changed was that the pressures were now visible to the group instead of hidden inside individual calendars.

In the Transformation Lead’s programme, she began asking a version of the same question at the start of each steering group meeting. The first time she asked it, two people admitted, somewhat awkwardly, that a commitment was now at risk. It was uncomfortable. It was also far more useful than discovering the same thing four weeks later as a missed deadline with no warning.

Leaders who surface trade-offs early give people a structured way to flag competing demands before they quietly erode a commitment. This does not eliminate the trade-off. It changes when it is dealt with: as a visible decision made with the group’s knowledge, rather than an invisible decision discovered only when the deadline passes.

Questions you can use to surface competing priorities before they undermine accountability:

• “Is there anything competing for your time right now that could put this commitment at risk?”
• “If you had to choose between this and something your own manager is asking for, which would win, and have we talked about that openly?”
• “What would need to be true for this trade-off to be made visibly rather than discovered later?”
• “Whose priorities are we asking you to set aside in order to deliver this, and do they know that?”
• “What’s the trade-off nobody in this room has said out loud yet?”

Practical actions:

• Open every recurring gathering with a specific version of the standing question, not a generic one: “Is anything competing for your time that could put your commitment at risk in the next two weeks?” A two-week window forces a concrete answer rather than a vague reassurance.
• When someone admits a commitment is at risk, ask immediately what the consequence will be if the trade-off goes unaddressed, and who else in the room will feel it. This turns an awkward admission into shared information the group can act on, rather than a private confession that quietly gets dropped.
• Make the cost of the trade-off visible to everyone it affects, not just to the person who raised it. If finance deprioritises a commitment in favour of their own manager’s request, the group should know what that means for the workstream depending on it, not discover it as a missed deadline later.
• Resolve trade-offs in the room rather than letting each person resolve them privately against their own competing demands. A trade-off settled in isolation usually gets settled in favour of whoever has the most local pressure, not whoever has the most organisational consequence.

Practice 4: Address slipping commitments directly, without assigning blame

There is a recognisable pattern when a commitment starts to slip. The conversation moves from “I will” to “I would have, except…” Explanation replaces ownership. Often nobody quite notices the shift happen. Left unaddressed, this pattern becomes the norm, and accountability quietly dissolves into a culture of reasonable-sounding excuses.

Effective matrix leaders learn to name this shift the moment it happens, without making it personal. The skill is not confrontation. It is a simple, consistent redirection: acknowledging the explanation without accepting it as a substitute for the commitment, and bringing the conversation back to what happens next rather than dwelling on why it didn’t happen already. “We’ve moved into explaining why this didn’t happen. Let’s come back to what happens from here” does the work without triggering defensiveness, because it describes a pattern in the conversation rather than a judgement on the person.

An operations director I worked with used a version of this almost word for word in a tense supplier review. Two functions had spent twenty minutes assigning responsibility for a missed deadline before anyone proposed a way forward. She named what was happening, not who was at fault, and asked the group a single question: what can we agree to do in the next two weeks, regardless of how we got here? The tone in the room changed within a minute. The explanations did not stop entirely, but they stopped being the centre of the conversation.

There is a useful discipline underneath this move. When a commitment has slipped, there is usually an obvious question that wants to be asked first: whose fault was this? It is rarely the most useful question, because it looks backwards and invites defensiveness rather than movement. A more productive question, asked of yourself before anyone else, is: what can I do, right now, to move this forward? The first question assigns blame. The second assigns responsibility. It is far more likely to produce action.

The Transformation Lead used both of these moves with the finance representative whose vague commitment had quietly never materialised. Rather than asking why it hadn’t happened, she asked what, specifically, would need to be true for it to happen now, and what she could do to help make that possible. The conversation took ten minutes. It produced a far more useful outcome than an explanation ever would have.

Questions you can use when a commitment has slipped:

• “What can you do, starting today, to move this forward, regardless of why it slipped?”
• “What would it look like to own this rather than explain it?”
• “What’s the question behind the question you’re avoiding asking yourself about this commitment?”
• “What do you need, from me or from someone else, to get this back on track?”
• “If we set the explanation aside for a moment, what’s the next concrete step?”

Practical actions:

• Listen for the exact moment the language shifts from “I will” to “I would have, except,” and gently interrupt it there, not after the explanation has run its course. Something like: “I hear that,  and I want to come back to what happens next, if that’s okay.” Then ask what the delay has already cost and who has absorbed it. Letting the explanation run unchallenged teaches the room, quietly, that a good enough reason is an acceptable substitute for delivery.
• Before raising a slipping commitment with anyone else, answer one question for yourself: what could I have done differently to prevent this, and what can I do right now to move it forward? Bring that answer into the conversation first. Asking others to own their gap lands very differently from someone who has not first looked at their own.
• When a commitment slips, treat it as evidence the original agreement was less specific than it felt at the time, not as evidence the person can’t be trusted. Go back to it together and rebuild it to the standard from Practice 1: what will be done, by whom, by when, and what they need from you to make it possible.
• Make the consequence of the slip explicit before moving on, not as blame but as information: what has this delay already cost, and who has absorbed that cost? A group that never names the consequence of a slipping commitment will keep treating each one as a minor, isolated event rather than a pattern worth addressing.

Practice 5: Build accountability structures that outlast you

The strongest matrix leaders do not simply hold their current initiative accountable. They build habits, language, and lightweight structures that continue to generate accountability even when they are not personally in the room to enforce it.

A facilitator colleague once described handing over a long-running cross-functional forum to a successor with real apprehension, expecting the discipline she had built over eighteen months to unravel within weeks. It didn’t. The group had absorbed the habits as their own: the written record after every meeting, the standing question about competing priorities, the willingness to name a slipping commitment without making it personal. The structure had outlived the person who built it, because by the time she left, it no longer depended on her.

This is where individual practice becomes systemic capability. A steering group that has developed its own shared language for naming a slipping commitment, that expects a written record after every meeting, that has internalised the habit of surfacing trade-offs early, no longer depends entirely on one leader’s vigilance. The accountability has become part of how the group works together, not a function of any single person’s authority or persistence.

The Transformation Lead’s programme eventually reached this point. Six months in, a member of the steering group who had nothing to do with the original commitment-tracking process flagged, unprompted, that a colleague’s commitment looked at risk, and asked the group to address it. That moment told her something important. The accountability she had built was no longer hers alone to maintain. It had become the group’s.

Questions you can use to build accountability that outlasts any single leader:

• “What would this group still do, even if I weren’t in the room to ask for it?”
• “What language or habit have we built here that other people are starting to use without being prompted?”
• “If I stepped back from this initiative tomorrow, what accountability structures would survive?”
• “What are we doing now that should become a permanent part of how this group works together, beyond this initiative?”
• “Who else in this group is capable of holding accountability the way I currently do, and how do I help them develop that?”

Practical actions:

•  Watch for the moment someone other than you names a slipping commitment, flags a trade-off, or asks for the written record unprompted. When it happens, say so out loud to the group: “That’s exactly the kind of thing I want this group holding itself to.” Naming it reinforces it far more reliably than hoping it repeats on its own.
• Hand off one piece of the process at a time, starting with the lowest-stakes: ask someone else to circulate the written record after the next meeting, then have a different person own the standing trade-off question the meeting after that. Spacing the handovers out makes the habit portable instead of leaving it dependent on a single person other than you.
• Before stepping back from any piece of the process, ask what would happen to it if you were unexpectedly unavailable for a month. If the honest answer is that it would quietly stop, it hasn’t actually transferred yet, whatever the org chart says.
• Treat your own growing redundancy as the clearest evidence the work succeeded, not as a loss of control. The cost of skipping this step shows up later and is expensive: an accountability structure that depended on one person quietly collapses the moment that person moves to the next initiative, and the group has to relearn, under pressure, habits it should already own.

Wrapping up

The Transformation Lead did not need more authority. She had already built genuine influence, a strong network, and a steering group capable of real commitment. What she had not yet built was a way to make those commitments hold once people left the room. Once she did, the gap between what was agreed and what was delivered closed sharply. Not because anyone suddenly became more reliable. Because the agreements themselves became specific, visible, and genuinely owned.

Accountability without authority is not about control. It cannot be, because the authority to control simply isn’t there. It is about clarity precise enough that people can hold themselves to it. Structure durable enough that commitments survive contact with competing priorities. Conversations honest enough that slipping commitments get addressed before they quietly become the norm. Influence creates the support. Networks create the connections. Convening creates the commitment in the room. Accountability is what makes all three of those capabilities mean something once the meeting ends.

This is also where the four capabilities complete the full picture of matrix leadership. None of them work in isolation. A leader with influence but no accountability builds support that never converts into delivery. A leader with a strong network but no accountability has relationships that never quite translate into results. The four capabilities together, not any one of them alone, are what allow a leader to create genuine movement in an organisation where formal authority was never going to be enough.

Three questions for reflection

1. Think of a commitment that was made to you recently and has since quietly slipped. Was the original agreement specific enough that you and the other person would have described it the same way a week later?
2. Where in your current initiatives are you holding individuals accountable for their own piece of work, while nobody, including you, is accountable for what happens between those pieces?
3. What accountability habit have you been carrying personally that, six months from now, you would like to see the group carrying without you?

Inspiration

Block, P. (1993) Stewardship: Choosing service over self-interest. San Francisco: Berrett-Koehler Publishers.

Connors, R., Smith, T. and Hickman, C. (2004) The Oz Principle: Getting results through individual and organizational accountability. New York: Portfolio.

Galindo, L. (2009) The 85% solution: How personal accountability guarantees success — no nonsense, no excuses. San Francisco: Jossey-Bass.

Miller, J.G. (2004) QBQ! The question behind the question: Practicing personal accountability at work and in life. New York: Putnam.

Senge, P.M. (2006) The fifth discipline: The art and practice of the learning organization. Rev. edn. London: Random House Business.

Share This Story, Choose Your Platform!

FacebookXBlueskyRedditLinkedInWhatsAppTelegramTumblrXingEmailCopy Link

About the Author: Andi Roberts

Andi Roberts is an executive coach and facilitator helping leaders, teams and organisations build clarity, collaboration, belonging and sustainable performance in complex environments. With more than 30 years in business, he works with both corporate organisations and NGOs through executive coaching, leadership development and facilitation. His work focuses on helping people navigate complexity, strengthen collaboration and build resilient, high-performing teams. His practice is grounded in systems thinking, community building and practical frameworks that support sustainable performance and meaningful organisational change.

Related Posts

How do I adapt my leadership style to engage my whole team through change?

Gallery

How do I adapt my leadership style to engage my whole team through change?

How can I ensure I and my team manage outside of work wellbeing?

Gallery

How can I ensure I and my team manage outside of work wellbeing?

How do I deal with my team members who are resisting change?

Gallery

How do I deal with my team members who are resisting change?

What do the best matrix leaders do differently?

Gallery

What do the best matrix leaders do differently?

Leave A Comment Cancel reply

Comment

Save my name, email, and website in this browser for the next time I comment.

Notify me of follow-up comments by email.

Notify me of new posts by email.

Δ document.getElementById( “ak_js_1” ).setAttribute( “value”, ( new Date() ).getTime() );

This site uses Akismet to reduce spam. Learn how your comment data is processed.