Showing posts with label organizational structure. Show all posts
Showing posts with label organizational structure. Show all posts

Friday, July 16, 2021

Support for Support Teams

In my work with cooperative group (water I've been swimming in professionally since 1987) I notice trends. In particular, where do groups struggle and what might help. Sometimes this leads to thinking about generic issues, such as communication, understanding consensus and navigating its challenges, meeting facilitation, diversity, and working with emotions (to name a few things that I offer concentrated assistance with).

I also specialize in organizational structure—right relationship between plenary and committees (or teams), and where the hot spots (and weak spots) are. I observe patterns, and I try to develop solutions to the challenges. In general I've come to the view that the big four committees that groups often need help with are:

Steering

Process—under which there are two potent subcommittees: Facilitation and Heart (offering assistance to members in interpersonal tension who are not able to find their way through it on their own).

Membership

Participation (non-monetary contributions to the well-being and maintenance of the community)

I have written about all of these previously in this blog (you can search by key word). Today I want to add a new concept that has recently emerged for me: The Support Team.

The basic idea is that members occasionally need help with meeting basic needs and may find it awkward to ask for it—especially if the only channels available are an announcement in plenary, a notice on the common house bulletin board, or with a message posted on the community list serve. 

While some do not have any trouble asking for what they need; others do. Perhaps they don't want to be a burden, perhaps they feel uncomfortable because they are uncertain about whether they'll be able to respond in kind and don't want to run a social capital deficit, perhaps it's embarrassing to discuss personal needs outside the household, perhaps fear of being turned down is too excruciating to take the risk of asking, perhaps they feel overwhelmed at the prospect of organizing and making good use of positive responses, perhaps they are unsure what to ask for and don't want to be vague or inarticulate. There are a number of reasons why putting out the call may not be easy.

The need for this tends to be episodic and can be wide ranging. It could be temporary debilitation (recovering from knee surgery) or permanent (an amputated leg). It could be acute (a bout with pneumonia) or chronic (think emphysema). While it tends to effect older folks more,* anyone can be affected. Even where there this a basic understanding that community members aspire to provide support to one another in time of need—and there is a wealth of heartwarming stories about how this has worked well (even heroically) relying solely on spontaneous personal initiative, there is also a sad underside to this, where help often is extended unevenly—mostly because members are unaware of the need or how they can help. In short, there is a dearth of coordination, where spontaneity and courage fall short. It's not anyone's fault, but there is nonetheless a fault line.

* This concept has terrific potential to be an integral part of how a community can sensitively offer substantive support for people aging in place. Just be aware that needs are not limited to seniors.

As I've become sensitized to this situation I've been thinking about what might help. The response I've come up with is the concept of a Support Team, whose job it would be to work behind the scenes to coordinate a flow of up-to-date information about household needs, shopping the situation discreetly among the membership, and then coordinating responses.

As I envision it, it would work like this:

—The Support Team would be available for any resident to approach it and discuss their household situation. This could be done with the whole team or with just a single member—whoever the resident would feel most comfortable with. The Team (or its rep) would listen carefully and compassionately, help the member get clear on their situation and the specific needs that are being requested. Note that requests will be tailored to that household's situation and can be wide ranging—anything from walking the dog at 8 am to dropping by for a chat and a cup of tea at 4 pm.

—The team would then draft a summary of the information, to be sent to all community members as a private communication, though only after its wording has been approved by the requesting household.

—Part of the communication would be a delineation of the specific things that others are being asked to sign up for. People who are willing to help can offer a one-off (cooking a pan of lasagne next Saturday) or an ongoing commitment (doing grocery shopping every other Thursday morning for the next three months), It's up to them. 

By doing it this way, people can respond discreetly, minimizing concerns about how their offer—or the lack of one—may be perceived by neighbors. The point of this is that you want offers to be made guilt-free, and minimally impacted by peer pressure. Responses can vary, depending on a number of factors: the responder's personal relationship with the requester, the responder's history with having received support from others in the past, the bandwidth in the responder's life to carve out support time for the requester, the comfort/skill level of the responder relative to what is asked for, etc.

—The team will then collate offers, clear up ambiguities, and slot shifts into a support chart specific to the requesting household, minimizing double-booking, and troubleshooting to fill unmet needs to the extent possible. Responders will be given their assignments and the chart will be handed over to the requesting household. While all slots may not be filled, half a loaf is better than none.

—The team will periodically check back with the requesting household to see if the situation has substantially changed and pass along updated information to the community as appropriate. Oftentimes community members appreciate getting updates (helping them track what's going on with their neighbors) even if they are not in a position to offer assistance. 

—If people miss shifts, the team may be on-call to assist the requesting household find a last-minute replacement.

—Annually the team could offer a summery report on how many requests it handled, roughly how many hours it devoted to the work (so that the community had a solid sense of how much the team was doing), any trends it noticed, and any ideas it had about how things could be enhanced.

It is important to understand that there would be no guarantee that all (or even any) requests for help will be answered. However, if you don't ask, the answer is always "no." It would not be the Support Team's responsibility to cheerlead or cajole; they would simply be passing along important and sensitive information accurately and with compassion—both for the requester and for potential responders.

No one would be required to use the Support Team's service; it would just be something available if you want their help. Similarly, no one would be required to respond to requests for help; it would just be an option. The Support Team would be a coordinating service intended to grease wheels that might otherwise be stuck or sidetracked on the road to compassionate support.

I'm thinking that this role might be filled by a team of 2-3 folks with the following qualities:

• compassionate

• empathetic

• good listener

• patience for working with people when they are under stress and possibly confused and disorganized

• organizational skills

• good communication skills

• discreet with sensitive personal information

• have the bandwidth to be able to respond relatively promptly to requests

• good with logistics and problem solving

• ability to collaborate well with others on the team

Anyway, that's my inspiration. If you like the general concept, feel free to tweak this in any way that you think might be a better fit for your situation. Think of it as a way I can support you and your group.

Saturday, November 27, 2010

Board to Death

I recently got the following email from a person in distress about how her community was being governed. After hearing what I had to say about options in organizational structure at a workshop, she wrote:

You mentioned that a community could allow everyone to be on the Board and still satisfy the bylaws. Could you provide more details about how to create that? My group uses consensus and there's tension between the Board and the group.
It's not hard to do. Most communities are legally structured as corporations and the law (established on the state level, but remarkably similar in most cases) requires you to have a board and officers. You can simply make every member of the community automatically a member of the Board, and then make the officer positions titular (that is, you give them no power). Under this structure, all the power rests with the plenary (meetings of the whole), or its designates.

To be clear, I am not advocating that all decisions be made in plenary; only that there be a clear understanding that all power resides there. Once a group gets past a certain size (6-8?) it generally works better if quite a bit of the group's work is delegated to managers or committees. At a slightly larger size (12-15?) it typically works well to have a particular subgroup, let's call it the Steering Committee, that handles coordinating functions and is available to exercise power on behalf of the group in case of emergencies—which is something that should not happen often, yet is nice to have in place ahead of need. As I envision it, the two main functions of the Steering Committee would be to draft plenary agendas and monitor tasks, troubleshooting as needed.

In the context of a community that uses consensus, one of the big problems with an active Board (if it's a subgroup, and not a committee of the whole) is that you effectively have two governing bodies (the community and the Board) and it can be a nightmare sorting out which body has power over what decisions. The most common division attempted in such arrangements is that the Board handles financial and legal functions, and the community oversees social functions. However, many issues don't sort themselves that cleanly into one category and it gets to be a real mess. (Imagine that a couple of community kids get into mischief and damage several air conditioners in the
neighborhood by pouring sand into the vents. One neighbor calls the police and files a formal complaint. How much of this issue will be tackled by the community, and how much by the Board?)

Goldoni wrote a play a few centuries back, a farce entitled The Servant of Two Masters. The humor is based on the ridiculous situations that a servant can get into when trying to please two masters who have differing ideas about what the servant should be doing and never discuss how to coordinate their requests. In my experience, communities that simultaneously try to operate by consensus and under the aegis of an active Board also tend to be a farce. It's much better, in my view, to have a single government—whether it be a community council composed of carefully selected members, or a plenary that operates by consensus—than to attempt employing both, where each trips over the others' feet.

I feel our Board does not represent our community; it is acting separately. Five households recently received a letter from a Board member that was an attempt to enforce a pet policy agreed on five years ago. In my view, this policy is outdated and no longer fit the needs of many members. On top of its being out-of-date, not all members of the Board saw it before it was sent out. How best can we respond in this situation?


Now the story gets more complicated, and I want to attempt to tease out the threads. While I'm a big fan of consensus, let's suppose the inquirer's group was persuaded of the folly of dual governments and decided to abandon consensus in favor of being fully governed by an elected Board (a representative democracy).

Issue #1: Good Representation
It can't be a good sign that a substantial portion of the membership feels that the Board does not represent their views. This raises a bunch of questions:

o How carefully were Board members chosen? (In general, it's highly valuable that a Board have balanced representation, such that everyone in the group feels there's at least one Board member that is easily accessible to them and understands their perspective. Note however, that "understanding one's perspective" is not necessarily the same as agreeing with one's thinking.)

o How good a job is the Board doing of educating itself about what community members think about the issues that the Board is wrestling with?

o How well does the Board make clear to community members the rationale for its positions, and why they believe their actions are in the group's best interests?

Issue #2: Updating Agreements
Maybe the 2005 pet policy needs to be reviewed for how well it fits the community today. Do community members know by what pathway policies can be reviewed and altered? The fact that the correspondent believes the pet policy to be outdated does not necessarily mean that all community members feel that way, or even a majority. Absent an agreement to change the policy, the old one stays in effect.

Issue #3: Board Members Going Rogue
While Sarah Palin is trying to breathe life into her ersatz political career by entitling her recent book, Going Rogue, for the most part there's a problem if someone attempts to arrogate to themselves the power of a governing body that they have not consulted with before acting. If that's actually what happened in this instance (as the correspondent implies), then it appears that the Board member may have overstepped their authority, and there needs to be a way to address that.

On the other hand, it might be a good idea to check with other Board members about the possibility that: a) consulting did happen, just not in plain view; or b) the Board member who wrote the letter had been authorized by the Board to handle pet policy matters without consulting. I'm not saying that their action was smart; I'm only cautioning that it may not have been bad process. Check your facts.

In summary, the correspondent may have a real problem with the group's pet policy, yet that might continue even if the Board were the whole group. You may also have a problem with how to handle the situation where someone perceives agreements to have been broken. Changing the governance system will not make these issues go away—though it may help provide a clearer pathway for dealing with them.