this post was submitted on 23 Jun 2024
97 points (98.0% liked)

askchapo

22710 readers
252 users here now

Ask Hexbear is the place to ask and answer ~~thought-provoking~~ questions.

Rules:

  1. Posts must ask a question.

  2. If the question asked is serious, answer seriously.

  3. Questions where you want to learn more about socialism are allowed, but questions in bad faith are not.

  4. Try [email protected] if you're having questions about regarding moderation, site policy, the site itself, development, volunteering or the mod team.

founded 4 years ago
MODERATORS
 

I've had a few events so far where the discussion/feedback part had 1-2 white guys doing longgggg monologues about something unrelated to the main topic. Last time had some stoner guy ranting about the confusing service at airports here (the event was about Gaza). Before that it was some boomer guy trying to explain Madonna to the non-white teens in our group (the event was about trans rights). Sometimes it's just two white guys monologuing back and forth. It's super counter productive and cringe.

I'm just thinking of a hard rule. Like "if you're a white guy, you're welcome, but please try to listen more and keep unrelated monologues to a minimum."

For the record, I am a white dude.

(page 2) 17 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 3 months ago

Meeting minutes, perhaps?

Maybe do a briefing on what exactly you're trying to accomplish at any given meeting and lay down that we only have so much time to meet? Like, I highly doubt they're being intentionally disruptive so just making them aware of that fact might do something.

[–] [email protected] 5 points 3 months ago

I was in an organization previously that had different hand signals for the audience to give a speaker if they were droning on too long. You'd put your arm across the top of your head if they were going on a tangent and raise an arm with a limp hand if they were beating a dead horse.

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago)

I took a course on social organizing. And every time a question like this was asked (how do we convince x....) I would try and come up with a clever way of doing it. Then the instructor would provide several examples of what you might say and they were all direct.

So here's what you could do:

Tell them to shut the fuck up and let someone else talk.

I'll add to this: Trying to be nice to people who are disruptive in an organization, or people you dislike for some reason, will undermine the cause/organizing/institution etc. It is far better to personally deal with issues rather than let them fester and lead to resentment.

That doesn't mean kick someone out (necessarily), but confront them and do the uncomfortable thing. We have power through numbers, which means all our efforts are necessarily social.

It will be hard, it will suck, you might even need to go home and have a cry afterwards. But you, your organization, and your comrades will form stronger bonds, and experience far more wins than are otherwise possible.

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago)

One of two methods, depending on the meeting, the constituency, etc.:

  • Progressive stack - A queue of speakers is kept, but people who haven't spoken yet are prioritized, and non-cis/-het/-white/-male people may also be bumped in priority.
  • Rounds - Go around the room and give everyone in turn a chance to speak (or pass). This can be great for people who are normally hesitant to speak up or put themselves on the queue, while offering the no-pressure chance to pass if they really don't want to speak.

Plus sometimes a person who volunteers to do temperature checks, remind people if they are taking inordinate amounts of time or are simply repeating stuff that's already been said, etc. Depending on the dynamics of the meeting (e.g. when most people form a well-knit group who trusts each other to do well) this might be handled collectively instead of with people in the particular role.

load more comments
view more: ‹ prev next ›