Accountability Is Not the Problem You're Looking to Solve
We look at why a lack of accountability is a symptom of a larger problem among Agile development teams, and what to do about it.
Join the DZone community and get the full member experience.Join For Free
a frequent answer i receive when i ask about an outcome organizations are looking for out of their agile transformation is greater accountability. leadership will say things like "we need our people to be accountable for what they say they're going to do!"
that doesn't sound like accountability to me, that sounds like commitment and conviction. simply put, what is accountability? it's who is responsible for something. accountability does not directly correlate or cause commitment to get it done, just who is responsible if that does not happen. if we're wanting people to be more responsible for things and think that they are not, we have a different issue to solve and need to ask why. let's investigate!
lack of accountability often means an absence of trust
perceived lack of accountability is a symptom of a larger problem in the organization. if the organization believes their people are not accountable or responsible, that points directly to a deficit in trust. we see both in patrick lencioni's hierarchy of the 5 dysfunctions of a team, though avoidance of accountability is not the root problem, absence of trust is.
what i often see as i get to the heart of the accountability issue is that in a command and control culture, "lack of accountability" is a synonym for the blame game. "it's not my fault!" "who was supposed to do that?" "who is supposed to be responsible for that?" "we have to spend time proving the problem was not caused by us." when sentiments like that frequently arise during my interactions at an organization, it's a huge indicator of a problem. i also see an indicator of this issue in role confusion and the frequent ask for a raci (responsible, accountable, consulted, informed) diagram to further pinpoint where every function of a role fits.
does it really matter who needs to do every little thing? or is it more important for those things just to get done? sure, people need to have accountability for their responsibilities but when everything down to the smallest task needs to be assigned out, we are essentially micromanaging ourselves and that is defeating a main purpose and benefit of self-organizing teams (at all levels of management).
yes, our people do need to be accountable, but they need to be accountable to each other before they can be accountable as a team. we must believe that the people we work with are driven by motivations for their work, want to succeed, and are working under the prime directive:
"regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand." -norm kerth, project retrospectives: a handbook for team review
organizations can unknowingly sabotage trust
one way management often hinders teams in forming trust is by frequently changing their members around, thus causing them to have to re-form relationships. how can we expect people to be accountable to people they have never worked with before and immediately deliver on everything that is expected of them? those are unfair expectations and teams are at a disadvantage from their inception (which repeats every time a member is relocated).
another way trust is hindered is lack of involvement in the actual plan that the accountability is perceived to be lacking on. a key piece of information i've taken out of graduate change management classes is that we need to invite people to the change and invite them to be a part of the solution. agile trainings have missed this point at times when discussing product ownership and product management. those roles have the final priority win - every time - but if they are not collaborating and involving the people doing the work they are more likely to get it wrong. priorities will lean toward subjective over objective and as a result the team will not be as invested, committed, accountable to the plan because they have less trust for it (and it's likely worse for the customer, too).
organizations that do not include the necessary players' input in forming plans often face constant change and churn of that plan. team players are not only development teams but the teams that help to prepare the work for them to develop. often management teams spend much time delegating to the teams they lead, but it's the teams they are a part of who cause the majority of the politics and conflict in consistently and rapidly changing priorities for the teams they lead.
changing a plan is not bad, but the excuses and frequency often are and the implications turn to distrust in the organization and management. the shifts organizations feel they need to make are driven more by internal politics than market need. we think our organizations need to be able to shift priorities any and all the time if necessary; we're "agile" after all, right? that is not what "being agile" means. this is not pivoting relentlessly, it's pivoting recklessly. if leadership/management teams cannot commit and be accountable to a plan for a short period of time (and a quarter is short in context), how can we expect the teams we lead to commit to the plans? the development teams pay the price for not delivering on something that is far from certainty because it's often viewed as lack of accountability to a plan they weren't trusted advisors in.
accountability was never the problem; trust and inclusion are what translate to true commitment and conviction. until we solve those problems at all levels of the organization, we will always wrongly see accountability as the issue and chase relentlessly after a symptom while ignoring the root of the problem.
Published at DZone with permission of Natalie Warnert, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.