Hacker News new | past | comments | ask | show | jobs | submit login

So why would anyone do an actual strike? This sounds better and more convenient.



The point of a strike is often to make a big statement, say “fire me if you dare,” and show that your unit has cohesion and resources. You want something dramatic and noticeable. For example, if you want to kick contract negotiation out of stagnation, you want to do something that the business can’t ignore for a couple months.

Work-to-rule doesn’t really accomplish that.


It's more likely to kill the parent organization than enact change. This may not be a problem for the individuals in an organization if they have reasoned that

1. Personal Growth is limited, or further upward movement is undesirable.

2. They intend to be with the organization a finite remaining time, or would welcome an early exit

A proper strike can be differentiated from a lazy workforce, self-sabotaging work cannot be.


Work to rule can be differentiated from a lazy workforce if it’s done well.

Typically, work to rule is used to highlight specific bad rules, regulations, or enforcement practices at a company.

Say a company expects employees to do non-rule “glue” work to keep the company functioning. But, randomly and capriciously the company punishes workers for doing this “non-rule” work. A union can then announce that they will only be sticking to the letter of the rules until either the rules are changed, or the arbitrary and capricious enforcement of the rule is changed.


It can also be a rational response to a company that follows "management to rule". For example, I was once on a team where almost all of my time was spent coordinating with other teams and helping other developers instead of developing myself. When performance reviews rolled around I was told that none of that stuff mattered; only the number of tickets that I completed matter.

So I switched my focus to completing tickets. A few weeks later I overheard my manager complaining about a breaking change made by another team that I had previously been coordinating with: "Why is this happening so much? We didn't used to get surprised by these sorts of problems."


This is super common in engineering organizations. Any shop with a standard performance review will have a "score card" where your contributions are summarized in a method that can be compared to others.

Being a great team player can't be quantified, and gets dropped.


I often advise teammates to follow destructive rules by management to force management to overrule or cancel rules. The employee has cover for following the rules vs breaking rules set by management to meet goals set by management.


I think they’re typically targeting different changes and different outcomes in an organization.

Work-to-rule is most effective when you’re trying to highlight particularly bad individual rules, or arbitrary punishments, etc. The work to rule action serves to clearly highlight to management why the current status quo rules are broken. This is, naturally, the most effective when there are very specific problems that lead to pretty direct consequences.

Work-to-rule would be much less effective when used for the kinds of things a strike might be used (increased pay, improved benefits, etc).

Basically, they’re just different tactics that highlight different things, and are each best used to achieve different kinds of goals.


>That's the American Way! If you don't like your job you don't strike. You just go in every day and do it really half assed.

- Homer Simpson


Work-to-rule is less dramatic than a strike and thus less effective. If, however, you can't strike for whatever reason it's a good tool to be aware of.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: