Article Organizational Strategy 4 min read
The Key to Better Accountability
Associations often get mired in the inability to meet particular goalsâleading some to play the blame game. According to one expert, the secret to getting a handle on accountability might involve taking a higher-level look at your processes.
Heads up: this content is over 5 years old, so some information may be out of date.
When a project goes off the rails, leaders and stakeholders are often eager to point fingers.
But the truth is, if a project has gone wrong, it might just be a sign that your approach to accountability isnât working.
Accountability was one of many points of discussion in the recent âAssociation Apocalypse (opens in a new tab)â report from the consulting firm Propel. The report noted, among other things, the ways that accountability often collapses in organizations. According to a Partners in Leadership report (opens in a new tab) cited by Propel, 93 percent of surveyed employees struggled to align their work with an accountability strategy at all.
Part of the reason for that, says Propel (opens in a new tab) Cofounder Jamie Notter, is that the view of accountability is often quite limitedâand not really correct.
âI think most associations are still stuck on viewing accountability as blaming people for not doing what they said they could do,â Notter says. âAnd if you want to blame people for not doing what they said theyâre gonna do, that is fine. Just donât call that accountability.â
Clearing the Air on Accountability
Instead, organizations should treat accountability as a way to ensure that results are happening based on stated goals. The challenge, of course, is that goals often change midstream, leading to confusion and making it hard to figure out how much progress has been made.
One way to manage moving goal posts, as Notter wrote in a recent blog post, is to think in terms of broader models (opens in a new tab) that work across years and can be adjusted as needed. Basically, by considering the work that youâre doing in a long-term context, you can ensure that a project is working in the spirit of a broader model rather than a narrower plan, even if things change in the middle.
âSo, stop obsessing over whether your 13-week plan is the exact right plan and just say, âWell, this is my model for how weâre going to get there. And then weâll adjust,ââ he says.
To put it another way, accountability should be about the big pictureârepresented by your overarching modelânot just narrower goals.
Donât Think in Terms of Failure
One thing that can lead to a poor accountability practice is an approach that seems focused on blame rather than organizational results. In this context, Notter says metrics can help lead the way to broader goals. Some organizations will use those metrics to figure out where their weaknesses might be when finishing a projectâbut thereâs a real risk of âhaving a culture where the metrics are about failure,â as Notter puts it.
âIf you get a culture thatâs defending whether youâre behind as opposed to learning from when youâre behind, then youâre kind of in trouble,â he says.
Think Systemically
Ultimately, the solution comes from treating accountability as an organizational process in which everyone has a role to ensure that things are working. One way to achieve this is by giving people ownership of specific processes. Thereâs a real distinction between ownership and blame, Notter notes. He says ownership is a matter of knowing that âsomeone has got this.â
âKnowing that someone is paying attention to the trajectory of this particular goal does not mean that person is the one in charge, or can be blamed for it,â Notter says.
What it does mean, however, is that someone can help look at the project at a higher level and ensure that itâs moving along, building trust in knowing that someone is owning the process. Thereâs room for systemic thinking at lower levels as well. One example: Notter and fellow Propel Cofounder Maddie Grant help encourage accountability in their day-to-day tasks by using a software application that flags where in a project something gets âstuck.â The idea is that the lack of completion might be holding up the overall project, but the terminology avoids blame and instead contextualizes the hold-up in the larger scope of the project. If someone missed something, it treats accountability as a systemic issue to solve, so that âstuckâ gets unstuck and the project keeps moving. Eliminating blame from the process can help move things along, Notter says.
Â
(designer491/iStock/Getty Images Plus)
Comments
Comments are for ASAE members. Learn more about comments on this site.
Log in to your member account or join ASAE!