Forum

Welcome Guest 

Show/Hide Header

Welcome Guest, posting in this forum requires registration.





Pages: [1]
Author Topic: Managing Disruption When All Else Fails (An "I Call Bravo Sierra" Work Group Hearing)
Guest
New User
Posts: 5
Permalink
Post Managing Disruption When All Else Fails (An "I Call Bravo Sierra" Work Group Hearing)
on: February 26, 2012, 19:10
Quote

Managing Disruption When All Else Fails

An "I Call Bravo Sierra Work Group" Hearing

Monday, March 5th, 2012

Terra Organica

6 p.m. to 8 p.m.

"... Although ordinary societies seldom have occasion to discipline members, an organization or assembly has the ultimate right to make and enforce its own rules, and to require that its members refrain from conduct injurious to the organization or its purposes. No one should be allowed to remain a member if his retention will do this kind of harm." Robert's Rules of Order, RONR (11th ed) p. 643, ll. 6-11

The term Bravo Sierra is taken from the military phonetic alphabet, as used in radio communications. Bravo for the letter B. Sierra for the letter S. Bravo Sierra is a somewhat congenial way of saying BULLSHIT.

The "I Call Bravo Sierra" Work Group is about calling bullshit.

The purpose of this hearing is to determine what #OB is willing and able to do in the event that its normal measures to maintain order at its General Assemblies catastrophically fail. No other issues will be addressed at this hearing.

Recently, there was a significant modification of the official #OB website, which took the name of Operation Phoenix. This modification of the website, and the implications of this modification, was an item taken up by #OB at the February 10th, 2012, General Assembly. During deliberations on this item, about half of the attendees walked out of the GA, including most of the Facilitation Team. I take this spontaneous self-combustion of the GA itself to be a catastrophic failure of #OB's normal measures to maintain order at a GA.

After that meeting, and in response to the events of that GA, I made a proposal to take severe disciplinary action against two persons in #OB who actively participated in Operation Phoenix. The responses to that proposal (a proposal that was never put to a vote) were powerful.

After the initial attempt to put my proposal to a vote, and after modification of the proposal in response to feedback from #OB members, I attempted to engage in discussion on the matter on Tuesday, February 21st, at both the Facilitation Work Group and the General Assembly to address the matter of what #OB is willing to do in terms of reacting to severe disruption. The Work Group preferred that the matter be taken to the General Assembly and the General Assembly preferred that the matter be taken to a Work Group.

So be it.

I am satisfied that there is profound reluctance on the part of many in #OB to even discuss the matter of how to enforce order, or how to cope with severe disruptions, at our GAs.

Those who are willing to address this issue are invited to attend this hearing.

***

The Hearing Agenda

6:00 p.m. Introduction. Background information. Iteration of meeting's purpose ("to determine what #OB is willing and able to do in the event that its normal measures to maintain order at its General Assemblies catastrophically fail.")

6:10 p.m. A description of the actions I am prepared to take, and the implications of those actions. There will also be a brief description of an ongoing, unresolved matter involving members of the Internet WG. I will not be yielding the floor to anyone for any reason during this portion of the meeting.

6:25 p.m. The hearing is scheduled to begin at this time. The remainder of the meeting will be devoted to a discussion among attendees on actions they are willing to take, and how to implement those actions. This allows for over 90 minutes to ask clarifying questions and make points of information about my recommended actions, which I deem more than adequate.

8:00 p.m. Adjourn

***

Beyond the items on the meeting agenda, the tone of this meeting will be as follows:

This is not a normal Work Group meeting. This is a hearing.

This hearing will not be run by consensus. It will be run by me. I will make all decisions about how the hearing will be conducted unilaterally, including who has the floor and how long that person has the floor. The agenda posted here is not a draft agenda, it is the official agenda of the hearing.

This approach is such a departure from how #OB, and any Work Group, normally conducts business that it may offend the sensibilities of some members of #OB. If you are one of those members, don't bother attending.

This approach is being employed in response to the fact that attempts to address this matter in traditional Work Group settings, and at General Assemblies, have been tried and have failed.

If you are not prepared to have a frank discussion about what #OB is actually prepared to do in response to severe disruptions at GAs, don't bother attending.

If your only contribution to the meeting will be to talk about how these solutions make you feel or how uncomfortable you are with proposed solutions, don't bother attending. The manifest lack of comfort with this entire topic within #OB has been well documented and is duly noted, and this meeting will not become a forum for expressing this lack of comfort.

#OB has delegated no authority to this Work Group to resolve any matter on behalf of #OB, and I will call Bravo Sierra any attempt to do so at this hearing. Discussion of the events of the February 10th GA, and any other past actions involving or affecting #OB, shall be limited to illustrative purposes in support of finding a solution to future disruptions. Attendees of this hearing shall refrain from speaking about the past conduct of any individual member of #OB. It is acceptable to make reference to Operation Phoenix during this hearing, but I will consider naming any member who may have been active in Operation Phoenix to be out of line, and grounds for calling Bravo Sierra. This is not a hearing for rehashing of past events. This is not a forum for airing of grievances. This is not a forum for casting blame upon individuals. I don't know who might be the source of the next severe disruptive event at an #OB General Assembly, and neither do you. This hearing shall be a discussion of what would be appropriate for #OB to do in the event of future severe disruptions.

It is particularly crucial to the success of this hearing that attendees conspicuously refrain from calling into question the motives of any member of #OB. I will call Bravo Sierra the instant I hear this happen.

***

Reference to "when all other measures fail" calls for some explanation.

The normal measures to cope with disruption begin with the consensus process itself. Using points of process, and perhaps other hand signals, the GA is able to maintain order and stay on topic and prevent incidental disruptions from interfering with a GA performing its function as the decision making body of #OB.

The Safer Spaces agreement is a further normal measure to establish reasonable boundaries, and includes guidelines on how those boundaries might be gingerly protected to mitigate potential disruption through the consensus process to prevent disruptions from impairing the function of a GA. I strongly recommend that a more fleshed out enforcement mechanism be adopted, but that is a matter beyond the scope of this meeting.

A decision to spend time in a GA engaging in a First Nation inspired Council circle is also a measure that has been warmly received by the membership of #OB to address disruption of GAs. This seems like an appropriate measure to respond to disruption, up to a point. Nonetheless, bear in mind that a decision on the part of the GA to spend the bulk of a GA refraining from making decisions could be viewed as evidence that the normal function of a GA (which is to make decisions) is being impaired.

It is only after these normal measures have been applied, and a disruption persists to the degree that the GA's ability to make decisions remains severely impaired, or in the event that the actions of a member is causing harm to #OB... that more severe measures might be appropriate to consider.

***

There are three responses I am prepared to take, and recommend that #OB take, towards disruptive #OB members in the event that all other measures fail. The responses are listed in order of increasing severity. I repeat here, for emphasis, that these measures should be employed as a last resort. They should be the last club out of the bag, not the first club, and should only be employed in response to extraordinary circumstances, including actions taken by a member that may have caused harm to #OB.

Censure. A written reprimand. A warning that, in the event that the disruption isn't resolved to the mutual satisfaction of the group and the named person, more severe action may be taken. This would be passed by proposal.

Suspension of Voting Rights. A temporary penalty preventing an #OB member from exercising voting rights at General Assemblies. This measure doesn't prevent a person from attending GAs, or even getting on stack and discussing proposals. A person whose voting rights have been suspending could still serve on a GA facilitation team (a member who serves as process mover at a GA is effectively voluntarily suspending his or her own voting rights for that GA). Nor does it prevent a person from fully participating in Work Groups. However, a person subject to this penalty would be prevented from blocking any proposals or otherwise using the power of consensus to interfere with the clear will of the group at a GA. A member's voting rights would be suspended by proposal, and the member's voting rights would be restored by proposal.

Severing Ties. This is the "namaste... away from me" penalty. A person subject to this penalty is considered to no longer be a member of Occupy Bellingham. This would be passed by proposal.

In all three cases, a proposal would require at least a four-fifths vote to pass, and to overcome a block, a nine-tenths vote would be required. If #OB made decisions by majority vote, or had some sort of executive board empowered to make decisions on its behalf... then there might be some legitimate concern that these proposals could be abused. In light of the fact that none of these actions could be taken without the overwhelming support of those at a GA, the risk of abuse seems vanishingly small to me.

In all three cases, a person would have to be named in the proposal. There is a palpably strong bias against the naming of names, but there appears to be no other way to enforce these actions.

More to the point, in all three cases, this action would have to be taken by the GA, and it would be inappropriate to delegate this decision to any other Work Group.

If you have better ideas, bring them to this hearing.

Ronna
Administrator
Posts: 51
Permalink
Post Re: Managing Disruption When All Else Fails (An "I Call Bravo Sierra" Work Group Hearing)
on: February 26, 2012, 20:35
Quote

I've been sick all day today and also getting ready to go away for a week. I would come to this hearing but cannot. I wish you the best. Friday's GA was a good example of things disintegrating. Both the proposals brought forth could have been amended in short order, been voted on and done with. I erred as one of the proposers in that I took some stuff personally. I will learn from that - give it to the GA once it is read. I think it would have passed despite the problem a member had with 4 words (and never did that person make a suggestion. There is little patientce for the work that needs to be done, what members call "process"

Zeke put a great fourm on and an article about how structure is important. So now we have to figure out how to do these two GAs (Tuesday & Friday). Tuesday Facilitation group should be interesting. Futureman plans to attend and do training but if that can't work out (we need both the structure and the training post haste) he has very valuable things to share with us about both.

There have been fewer disruptions but still lots of resistance to get things done quickly. There is little trust: that we can make a mistake and it will be OK, that we can make a "rule" better as we work with the structure. IS it truly that people want to be perfect or resistant?

And then there is the serious resistance to some words - like acountability. HOT BUTTON. That's part of it - knowing your hot buttons.

You did a great job a process mover (oh oh there's that word again!) I will try it one day.

deanosor
New User
Posts: 3
Permalink
Post Re: Managing Disruption When All Else Fails (An "I Call Bravo Sierra" Work Group Hearing)
on: February 28, 2012, 00:27
Quote

2 things. 1. I don't whether i will be there or not. When all hell breaks loose, All Hell Breaks Loose. I believe as when i violated at the rules at the infamous meeting by calling out David, that some of us know how to disrupt meetings much better than childish amateur. we in general won't allow people to to disrupt period. (and yes i violating your rules by naming names because i hate euphemisms, People did things, and they individually have to be called out for what they did.)

2. For those of us who lived thru the Vietnam War era, or have studied history, the term Operation Phoenix is scary. Operation Phoenix was according to Wikipedia "was a controversial counterinsurgency program designed, coordinated, and executed by the United States Central Intelligence Agency (CIA), United States special operations forces, and the Republic of Vietnam's (South Vietnam) security apparatus during the Vietnam War that operated between 1967 and 1972.[1]

The Program was designed to identify the Viet Cong Infrastructure (VCI) supporting the National Liberation Front of South Vietnam (NLF), more commonly referred to as the Vietcong (VC) and neutralize it through capture, coercion or killing its members. Phoenix Program operations were carried out by the South Vietnam’s National Police, National Police Field Force, Special Police Branch, U.S. and Vietnamese conventional armed forces; and by what became known as the Provincial Reconnaissance Units, or PRU’s.[1][2] In later years, US Army intelligence Phoenix advisors were trained at the Ft. Bragg Institute for Military Assistance and assigned throughout Vietnam. By 1972, Phoenix operatives had neutralized 81,740 suspected NLF supporters, of whom 26,369 were killed.(1)". I am usually not this paranoid, but if cutting off our website can be called Operation Pheonix, what's next?

Guest
User
Posts: 17
Permalink
Post Re: Managing Disruption When All Else Fails (An "I Call Bravo Sierra" Work Group Hearing)
on: February 28, 2012, 13:53
Quote

The name Operation Phoenix was meant to be scary, but David revealed what it was really all about the following day when he posted the suicide note.

"When I awoke, I discovered that despite having heard about the conversation the previous night, there was now a new website. People were throwing money at it to keep it alive. People had largely moved on from what I did."

All he wanted was attention.

Ronna
Administrator
Posts: 51
Permalink
Post Re: Managing Disruption When All Else Fails (An "I Call Bravo Sierra" Work Group Hearing)
on: February 29, 2012, 16:54
Quote

Best wishes for a first meeting of I call BS WG. I hope we can get over that traumatic GA at WECU (will we all have PTSD if we go there again?). We do need to work out this disruption issue and we are getting some good work done towards that end.

Guest
New User
Posts: 5
Permalink
Post Re: Managing Disruption When All Else Fails (An "I Call Bravo Sierra" Work Group Hearing)
on: March 3, 2012, 15:22
Quote

Special Report from the I Call Bravo Sierra Work Group (Shane Roth)

From the #OB Forum...

On March 2, 2012, Erin Haliburton wrote:

...I'm not coming back to OB in any form until Shane's proposal is passed. Tonight will be my last OB activity until that happens.

To Clarify: Shane's original proposal has been removed. But that is the wording I want. Not "Accountability Process" stuff, but an actual proposal cutting all ties with David Farr and banning him from any future participation.

In this same forum post, Erin attached links to two screen shots of Facebook and Twitter screens as evidence of the deteriorating relationship between Erin and David.

#OB appears to be without a webmaster now. Erin was serving as our webmaster up until March 2nd, when Erin's comments were posted on the forum.

It is difficult to overstate the many capacities in which Erin has served #OB above and beyond serving as webmaster and within the Internet WG.

It is the opinion of the I Call Bravo Sierra Work Group that if #OB takes no action then the group risks losing Erin Haliburton from #OB permanently.

This turn of events will be added to the agenda of the ICBS WG Hearing on March 5, 2012. Erin Haliburton has a scheduling conflict, so she will not be able to appear at the hearing. Beyond that, she has made it clear to me that she is not going to attend any GA or Work Group meetings any time soon.

The first response to an internal conflict should not be disciplinary action. Therefore, the ICBS Work Group strongly suggests that those members of #OB who believe they can do so should take immediate action to try and resolve or otherwise mediate this matter between David Farr and Erin Haliburton.

Recommendations from any Work Group are no substitute for GA action.

This seems to be an internal matter and it seems appropriate to discuss this matter at the next Tuesday GA.

It would be best if there were an option that allowed room for both Erin Haliburton and David Farr within the fold of #OB. It is the opinion of this WG that this option is likely no longer available to #OB. In that event this bears out, #OB may have to chose between the two members. It is the opinion of the ICBS WG that by doing nothing, #OB is effectively siding with David by default and in so doing excluding Erin Haliburton from participating in #OB.

Finally, it is the opinion of this WG that it is absurd that Erin Haliburton, or any person, should have to cope with the conduct documented on the #OB forum.

Guest
New User
Posts: 2
Permalink
Post Re: Managing Disruption When All Else Fails (An "I Call Bravo Sierra" Work Group Hearing)
on: March 6, 2012, 11:39
Quote

This was originally posted as a "reply" , rather than "quick reply", and this repost corrects for that.

Bravo Shane!

I will certainly be attending this “Bravo Sierra” Working Group,

The menace that Occupy Bellingham faces from those imposing disruption at our GA’s, and using extortion as a their admitted means of imposing darkness while calling it light, must be met with the firmness necessary to irradicate the menace. We must acknowledge that we are witnessing Coercion as toxic to Occupy Bellingham as Coal is toxic to our Earth. We must say “NO” to both.

Guest
New User
Posts: 5
Permalink
Post Re: Managing Disruption When All Else Fails (An "I Call Bravo Sierra" Work Group Hearing)
on: March 7, 2012, 14:53
Quote

Report from the I Call Bravo Sierra Work Group

Monday, March 5th, 2012

Terra Organica

6 p.m. to 8 p.m.

Attendees: Shane R.; Herb G.; Barb S.; Karen W.; Dean T.; Jeremy T.; Futureman; Terry; David F.; Boris B.;

This hearing was a tough meeting, and it was arguably the most unorthodox #OB Work Group meeting held to date. Some participants struggled more than others, and I am particularly grateful for those who participated in the face of those internal struggles.

The hearing was documented by way of streaming video. There was spirited objection to this documentation. I can't remember the last time there was such objection to streaming the video of a meeting in #OB.

This was not a meeting to prepare a proposal to present to a GA. Instead, it was a fact finding and information gathering event to determine what range of action #OB might be willing to consider.

At the beginning of the hearing, I presented three increasingly severe responses to take, in the event that the preventative measures we have in place to cope with disruption were to fail. All three of these measures would require the GA to pass a proposal by consensus to take effect.

1 Censure. A written reprimand. A warning that, in the event that the disruption isn't resolved to the mutual satisfaction of the group and the named person, more severe action may be taken.

2 Suspension of Voting Rights. A temporary penalty preventing an #OB member from exercising voting rights at General Assemblies. This measure doesn't prevent a person from attending GAs, or even getting on stack and discussing proposals. A person whose voting rights have been suspending could still serve on a GA facilitation team (a member who serves as process mover at a GA is effectively voluntarily suspending his or her own voting rights for that GA). Nor does it prevent a person from fully participating in Work Groups. However, a person subject to this penalty would be prevented from blocking any proposals or otherwise using the power of consensus to interfere with the clear will of the group at a GA.

3 Severing Ties. This is the "namaste... away from me" penalty. A person subject to this penalty is considered to no longer be a member of Occupy Bellingham.

After presenting these options, I opened the hearing to the attendees.

I took copious notes, but I am reluctant to put words in the mouths of participants, so the statements that follow are generally not attributed. In the rare cases where it was appropriate, I did establish who said what. Words that appear in parentheses are my words.

    There should be responses to conflict even if they happen outside of a GA.

    An interest in not tolerate attacks within #OB. Including between GAs.

    This is a free egalitarian movement.

    Preference for dealing with specific issues as they arise rather than in generalities.

    Interest in adjourning or taking a meeting into recess in the event of apparent disruption.

    More vigorous use of existing process, (by way of Points of Process).

    Interest in compelling a member to leave for a meeting or two.

    Ask person to leave, drag person out of meeting if necessary.

    Concerns about possibility of abuse of severe sanctions, even with consensus process.

    Preference for settling matters with conversations, and attempts at relatively informal mediation to achieve resolution of conflicts.

    This hearing feels like a trial.

    Interest in paying a professional non-violent communication mediator to assist in cases of severe conflict.

    People can decide there will be penalties for bad conduct without waiting for circumstances.

    In terms of online conflicts such as on Facebook, the admins should be able to ban individuals, subject to review by other admins.

    If resorting to voting rights suspension, it should be provisional (which I take to mean brief) particularly in the absence of evidence of conduct.

    An aversion to kicking someone out of #OB for being an asshole.

    Probation period might be an approach to disruption

    The importance of using tools to allow GAs to function without disruption.

    An interest in more educational events, conflict resolution skill building workshops, to develop a language to use for conflict resolution, non-violent communication training, consensus process training.

    Nothing should be taken off the table, all options should be open to #OB.

    Interest in something faster and more effective than using a Point of Process signal to respond to disruption. A 911 signal of some kind.

    A punishment response is a concern and is based on an old paradigm. #OB should be looking for new paradigms

    Herb G mentioned the possibility of a "three strikes" policy wherein if someone had to be censured informally three times during a single meeting, then that person's voting rights could be suspended. A person who has had their voting rights suspended three times could have ties severed from #OB. (There was a general sense of support for this concept, however there were some specific details that would need to be addressed before consensus would likely be achieved.)

    Censure (written reprimand) seems silly; a better approach would be an attempt at mediation.

    (A conversation about giving more authority to the Process Mover was spirited, but didn't seem to lead to consensus.)

    Concerns about process being used to gang up on unpopular individuals.

    A person accused of being disruptive should be given an opportunity to explain the apparently disruptive behavior.

    If someone feels threatened, that by itself should be enough. There is no need to find consensus on whether an individual feels unsafe.

    A reference to "Northwest Polite". A regional cultural bias towards over-politeness summed up as follows: Four drivers are at an intersection, each encourages the other to go first. After several rounds of that, everyone goes and they crash. (This is not an issue with the New Yorkers in Occupy Wall Street)

    We do not have patience with people who are angry. It might be appropriate to take the time to hear out a person who appears to be disruptive on the grounds that person may just be coping with anger.

    An interest in allowing for a wider range of passion than the current prevailing paradigm accommodates.

    If you are going to participate in Occupy you may need to commit to learning new skills.

    A call for a balanced approach to conflict resolution.

    An interest in forgiving past transgressions and letting go.

    A counter interest in not forgetting past transgressions. Or forgiving.

    The Encampment had to evict 4 persons from the encampment, without a process in place, for the sake of the encampment's survival. (There is a precedent for severing ties to individuals when all else fails.)

Meeting was adjourned.

Summary/Conclusions

Profound ambivalence appears to run deep within #OB on this matter. This terminal ambivalence could pose a serious threat to #OB's survival as a movement.

There are two consequences for disruptive and hostile behavior within #OB.

#OB Members who are disruptive and hostile will suffer consequences for that conduct as individuals

#OB as a group will suffer consequences for its member's disruptive and hostile conduct.

There is no third alternative. Either we deal with this problem, or the problem will deal with us.

On the matter of the concept of a "three strikes" policy or process, #OB's manifest reluctance to call even one strike must be addressed first.

While we cope with this terminal ambivalence, and analysis paralysis, people are walking away from #OB in real time. While waiting for a more perfect response to this issue, we are losing good people that we need now.

Disruptive and hostile behavior do not constitute anything new, and have no place in any paradigm of any vintage.

I have it on good authority that the human brain reacts the same to physical threats and verbal threats. We can be conscious of the difference, but our brain chemistry doesn't care. When someone is raging at you, your brain tends to take blood away from your higher rational functioning areas and sends it to your reptilian brain region, for the sake of your own survival. This makes it more difficult for you to remain calm when someone is projecting hostility in your direction. It even impairs your ability to listen to the person projecting anger at you.

The conviction that "we all need to do a better job of getting along" is contradicted by the evidence before me. There are a handful of members who have given themselves permission to treat other members in a manner that is indefensible. This conduct is such that if a guest in your home acted this way... that guest would never see the inside of your home again.

If something happens that you wouldn't put up with in your own home, then you might want to stop putting up with it at #OB.

Because #OB is your second home.

Recommendations

One: Admit that Comfort Zones are already being violated.

I heard a lot of talk about comfort zones. "I'm not comfortable with..." and then a description of some unpleasant task.

It is difficult to choose which metaphor best describes this farcical attempt to preserve comfort. I'm going to go with the metaphor of arranging deck chairs on the Titanic.

We can't even preserve a zone of safety at a General Assembly as things stand now, so I am unclear how we are going to preserve a zone of comfort in the absence of safety.

This group's collective comfort zone has already been compromised. Until you enforce your zone of safety, there is no point talking about preserving a zone of comfort.

Also, I don't know of anyone who ever changed the world from within their own comfort zone.

Two: Enough with questioning people's motives already.

I have had my motives and intent called into question repeatedly for even attempting to have this conversation. You folks need to knock that shit entirely the fuck off.

I'm not referring only to questioning my motives. I'm referring to questioning anyone's motives. I'm not the only person who has had to put up with this bullshit. I'm just the person who is calling you on it.

This habit of questioning motives and intent? It needs to end. Yesterday.

The only thing you generate when you call someone's motives in to question is heat. You don't generate any light.

And speaking of your ability to accurately gauge someone's motives...

Three: Learn how to assess threats.

There was much talk about skill sets at the hearing. Listening skills. Mediation skills. There is a skill set that needs to be worked on that was not mentioned during the hearing: threat assessment.

Let me give you a quick rundown of your current threat assessment acumen...

Scenario A

David evicts you from your own bloody website.

#OB response? "Let's hold a GA for four hours to find out what is troubling him. Then lets form a Council circle and talk for another hour about re-evaluating our listening skills."

Scenario B

Shane makes a proposal and holds a work group meeting.

#OB response? "Adjourn the meeting! Send it to a work group! Not THAT Work Group! Danger! Danger Will Robinson!"

Seriously.

This group has the most abysmal threat assessment capacity I have seen in living memory. You can't see a threat three inches in front of your face. At this point, it is entirely possible that our real external enemies could cripple Occupy Bellingham by doing little more than tossing a shiny red rubber ball into traffic in front of the door of our next General Assembly. You are going to sniff out an infiltrator or an attempt to co-opt you? Color me skeptical.

Your Spidey-Sense needs a recalibration, urgently.

Four: Stop being doormats.

No, seriously, Occupy Bellingham. Stop being doormats.

For example, there was some pointed concern about the unorthodox nature of the hearing. I invite everyone who has a concern or objection to step right up and keep that shit to yourselves.

You see, if you aren't going to call David on his bullshit (and you aren't)... and you aren't going to call Kerryn on her bullshit (and you clearly aren't)... then you are not going to call me on my bullshit.

You are acting like doormats and you are going to be treated like doormats until you... well... stop acting like goddamn doormats.

I didn't make you doormats. David didn't make you doormats. Kerryn didn't make you doormats. You acted like doormats and rendered yourselves doormats.

At this point, I'm wondering if you would be willing to take action against a member who did anything less than to gut shoot someone during a General Assembly. And even then, you would probably only take action after mediation between the shooter and the gunshot victim didn't work. And if the gunshot victim were unwilling to participate in mediation (for some mysterious reason), I have grave doubts that you would take action against the shooter then because it has been five whole GAs where no one has shot anyone so everything obviously must be fine now.

There is a difference between empathy and enabling. I am not convinced that #OB is making the distinction or is currently prepared to contemplate the distinction.

Jesus Tap-dancing Christ, folks. You are going to have to enforce your own principles and standards of conduct at General Assemblies. No one else can do that for you. No one else should do that for you.

You doormats.

Carol
New User
Posts: 2
Permalink
Post Re: Managing Disruption When All Else Fails (An "I Call Bravo Sierra" Work Group Hearing)
on: March 8, 2012, 11:14
Quote

Thank you all for taking the time to examine this painful and challenging problem. Regarding the frequent attempt to single Shane out for blame or ridicule in addressing this problem, I want to share a term a lawyer friend once explained to me:
Ad hominem which is “A fallacious objection to an argument or factual claim by appealing to a characteristic or belief of the person making the argument or claim, rather than by addressing the substance of the argument or producing evidence against the claim; an attempt to argue against an opponent's idea by discrediting the opponent himself.”
The unpleasantness and waste of time experienced by everyone attempting to work in a GA is real and, as many have pointed out, is driving people away from the group.
Reflecting on our last GA, I realized that biggest problems this time had nothing to do with tempers or rudeness but were:
1) We did not have a formal agenda (to my knowledge) and it would help if the agenda were posted prior to the meeting (a paper copy at the meetings is also helpful).
2) We did not have the an assistant to the facilitator as we discussed in the consensus group
3) Ten made a loose proposal that was out of the blue for those of us who are not on Facebook that led us all down a long and complex discussion away from the crucial issues we need to strategize about.
4) Although Dean’s announcement/proposal (?) was related to something a working group is doing, we were snagged by a lengthy debate on wording that should have been directed to the working group who could then have come back with a proposal (by the by, the one objector should be on that working group for that change or forever hold his peace….).
As Shane has cogently (but not without some unnecessary profanity) pointed out, we will have structure (order, rules…) or we will disintegrate.
I must agree with Shane’s statement that we are inadvertently “doormats” by not correcting the situation. Thanks for the grim laugh by comparing our niceties as attempting to arrange the deck furniture on the Titanic…Proposals are due to correct this situation.

Pages: [1]
Mingle Forum by cartpauj
Version: 1.0.34 ; Page loaded in: 0.138 seconds.