Another blogger who also happens to be an elected steward (this time with a CHW facility) has awoken from a self-imposed blogging slumber, and is discussing his dilemma within the Great California Union Foodfight. And while initially on the side of cooperating with Zombie UHW, all it took for him to switch sides was a bit of over-reaching on the part of SEIU, as he explains on his own blog...
Last Monday and Wednesday, I had the opportunity to talk to the SEIU representative assigned to WHC. I told her that we, as workers, had many issues involving failures by management to follow the terms of our collective bargaining agreement. We have many scheduling, assignment, and other worksite issues that need to be addressed and corrected. We, as employees, all know of decisions that managers have made that are just WRONG.Take a moment, and click over and read the rest of this gentleman's story. His motives to cooperate with Zombie UHW were absolutely directed in the correct manner (providing good representation to his peers during a trying time), but even THAT wasn't enough for the Purple Plague. They insisted on complete capitulation and domination of who he sees, and what he thinks, 24/7. And in so doing, they ended up flipping him to the NUHW side.
To this end, I met with the SEIU representative assigned to our facility. I talked to her about the need to set aside our SEIU/NUHW differences and work together for the good of the members. I told her that if she would be willing to be more available to work with our job stewards in terms of grievances, Committee meetings, etc. that I would keep her apprised of what we need and when we need her.
I also told her that I would no longer distribute information regarding NUHW at the facility. I wanted her to understand that I would work as a steward representing our contract, and only our contract, on matters involving union issues.
In the light of the current division in CHW facilities, including our own, regarding who is vs. who should be representing us (over 70% of our members signed petitions requesting a change of representation - a change that, by the way, could have been done by CHW without us having to wait for a vote), I felt that it was important to work with them (SEIU) ASAP.
There's a lot at stake here.
Our meeting seemed to be productive, and we were heading towards and understanding that would us focus on the work that needed to be done in the Hospital and Clinic.
Then the ball dropped. A dealbreaker was put in the mix. I was told that from this point on any of the stewards that has anything to do with NUHW or those working with NUHW will be removed as stewards in their facilities. I reminded her that any meetings that I or any other steward attends on our time is OUR business. Telling us who we can associate with is out of line and out of bounds. Period.
I will continue to meet and associate with who I please, as long as it is not against the law.
I was willing to forgo communicating with NUHW staff in order to build on a working situation with our SEIU representative - what a letdown.
Now I've decided to sign up for the NUHW founding convention, and yes, I had dinner with our former union rep, Lydia, this evening. So, I fully expect to be relieved of my position as job steward some time soon. I am not trying to "call their bluff", I am just doing what I believe is right.
Whenever I state that SEIU is acting as NUHW's best recruiting tool, this is the exact situation to which I refer.
Update on 4/18: It appears that the blog post referenced above has gone 404. I cannot speak to the reasons why this might have occurred, but in case there are any questions regarding the veracity of the text highlighted above, the Google cache is available, and I have procured images of the blog post in question.
I will confess to some strong opinions being espoused on ¡Adios, Andy!. However, I am also aware that when I hit the "publish post" button, that post is going to be in the Google cache until the Google gods decide to purge it - at which time the Internet Wayback machine takes over in that respect.
Update on 4/21: It's back. I can't tell if it was a system glitch or second thoughts, but the post is back with (as far as I can tell) all the original verbiage.