How You Analyze Your Community Can Effect Your Collective Impact

Submitted by Jay Connor on March 3, 2014 - 8:21am
SWOT v. SOART

I’m often asked: what is the most surprising aspect of your work with over 75 communities in their efforts to achieve better outcomes? 

Whether it is a city, town, school, or district, what has surprised me most is that I have never had to talk a community down from too high an aspiration.  I have never felt the need to pull back the reigns because a community was getting their expectations too far ahead of their potential grasp. 

Now this isn’t to ignore the sorry reality that communities often fail to achieve suboptimal results, but, as I have seen time and time again, that is a function of implementation and not of aspiration.  In fact, in my experience, those communities that tend to stretch the limits of expectation also tend to apply more rigor to their implementation, understand the need to reach across the community, and emphasize measurement planning because they intuitively know that this transcendent goal requires them, as a community, to get out of the “same ol’ same ol’” mindset of most past “community betterment” endeavors.  

We’ve talked about some of the potential speed bumps before (see my blog posting on “Traps”), and avoiding them is at the center of what I have called “Working Differently.”  Here is one simple suggestion to get your analysis off to a better chance to get to the “Big Hairy Audacious Goal” that Jim Collins underscored as a fundamental driver in those organizations moving from “Good to Great.”

SWOT v. SOART

Most of us, who have ever participated in or facilitated a strategic planning session, are very familiar with the warhorse of organizational analysis – SWOT.  Strengths, Weaknesses, Opportunities, Threats.  The group would take several hours to fill several pages of flipchart paper with their assessment of community characteristics that fit under each of these headings.  I used the process for years.  It engendered a lively discussion and helped to get people with vastly different perspectives, biases or sector experience closer to being on the same page.

So far so good.   But over the years, I began to suspect that this very process was effectively lowering the horizon.  In the same way that a gun sight can be bent forward, SWOT tended to create a context where the ultimate shot was low.  Under achieving became self-fulfilling. 

I think there are two dynamics at play here.  First, a community usually only opens itself for a “strategic” review when it already knows that it has problems.  An intuitive sense of community weakness is at the heart of the “call to action.”   This is anecdotally born out by the fact that usually the newsprint sheets labeled “weakness” often had significantly more entries and more unanimity than any of the other headings.  Second, “weaknesses” tend to give permission to the problem.  How many times have we heard something “outside our control” as the reason we have the problem – the why we can’t succeed.  Poor parenting: school outcomes.  Fast food: obesity health care.  Economic deterioration: pollution.  Media: teen pregnancy.  All of which, serves to confirm why we have the problem without serving to sufficiently guide us to the transformative solution. Even the 180-degree different strengths-emphasis of asset maps tends to fail in this development of a clear guide, because these asset maps are most often framed as activity resources from the problem perspective rather than from the solution point of view.  (Is it an asset to have more slots for early childhood, if the number of children who become k-ready doesn’t change?)

What I saw was needed was more intentionality about the aspiration and then more rigor regarding the characteristics of achieving that aspiration – that transformative outcome.  We all have weaknesses; it is those of us who focus on the change state that soar above those weaknesses.

That is why, several years ago, I switched to SOART.  Strengths, Opportunities, Aspirations, Resources, and Threats.  In many ways, it is very much the same flipchart process, but by re-defining the headings (i.e., the sight line of the participants) and encouraging iteration across the sheets I witnessed significantly enhanced discussions. The results have been eye opening.  Not only are the collective sights raised but also the ultimate time to result has shrunk.    

Don’t be naive about your weaknesses, but also, don’t let them limit your expectations.

Comments:
SOART v SWOT

Your assessment that the SWOT gives "permission to the problem," Jay, is spot on.  Recently, in my own blog and now republished by Tamarack, I wrote about SOAR v. SWOT.  In that article I relayed a very similar experience of filling up stacks of flipchart paper with weaknesses and threats only to use a half-sheet each, it seemed, for strengths and opportunities. I did note, however, that most of my work has been with people in public health and social work that have traditionally been trained to seek and fix problems wherever they can.  I noticed that you continue to use "threat" assessment and I'm not convinced this is necessary.  My experience has been that the threats organically emerge and definitely make an appearance if a planning process follows the SOAR.  Also, since SOAR's foundation is in Appreciative Inquiry, I also wonder if the inclusion of "threat" assessment doesn't move the experience away from those positive phychology-influenced roots and leave participants with less of a "can do" attitude after the experience. If you'd be inclined to say more about these, it would be appreciated and useful. Tom

SOAR! with a T

Hi Tom:

Great comments.  

For me the issue around "threats" is a manner of emphasis.  I have perhaps had less errosion of the "can do" attitude because I frame threats not in the traditional external (passive) force against an organization or system, but rather from an internal (active) "what is the treat to our sustaining this work of achieving our aspiration."  

In this way, "naming the treat" inoculates against the inevitable psychological trough that the hard effort of working differently for collective results tends to run in to at some point.  By discussing the threat as something from us -- that means that the solution (the way through the trough) is also from us.  

In this context, threats like use of jargon, lack of agreed upon measures, blurry outcome definitions, discomfort with rigor, failure to push the boundries of engagement ... etc ... are seen as likely distractions, but also, as easily dealth with.  We've actually had communities appoint "sargeant at arms" to be on the lookout for these process threats.

I think "strategic thinking," which is what all these approaches are attempting to instill, is fundamentally about understanding and uncovering your groups' ownership and responsibility for that better future.  Talking about threats to your own ownership is ultimately a resevoir we can draw on to sustain the work to the outcome.

Best,

Jay

 

Hi Jay, Thanks for unpacking

Hi Jay,

Thanks for unpacking that a bit for me. It makes a lot of sense. I like your framing of the threats as internal not external which, also, as you alluded to in your response, shifts the responsibility and power for addressing them back to the people in the room. Again, thanks for insights and time.

Best wishes,

Tom