Stack-ranking has been horrible every place it's been tried so I'm not really sure how this is a bad thing.
From what I've seen in my time in corporate America, poor performers are often kept around regardless of if a union is involved or not for a variety of reasons:
* firing someone for performance is a hassle even without any union representation because HR requires careful documentation,
* for the manager, firing an employee for performance means admitting that you made a mistake on hiring,
* firing the person may put the budget for their salary at risk, and
* if layoffs were to happen in the near future the manager will need the person as a sacrificial lamb to protect the rest of the team (this behavior is greatly enhanced by stack ranking, to the point where people are hired specifically so they can later be marked as non-performers and let go in the next culling).
Stack ranking is one of the worst ideas to ever hit the corporate world, and is, in general, a sign that I probably don't want to work (as an employee, at any rate) for that organization.
Collaboration is so fundamental to software development, or any creative endeavor.
Stack ranking, however, encourages heavy amounts of back-stabbing political competition.
Even if the team performs well ahead of expectations, the bottom 20% of the team will still face consequences for the "underperformance".
This is the same sort of bullshit that killed Sears.
Right. The rules for layoffs are more or less that "performance" is not a valid grounds for firing someone. The reasoning here is that the employees performance is the responsibility of the employer, who has to provide management, training etc. An employee have to basically mismanage their job to the point where it's illegal to be possible to fire.
Now, you can always fire Joe because he's a slow worker- but the union will protest. He'll likely be fired anyway, but it'll cost the employer (Joe will get a years salary and leave). The rules are basically "First in first out" - and employers have to buy each exception. The same would apply when closing a whole branch/factory for example. The employer likely knows which 20% of staff they would like to keep around, but they will have to wrestle with the union for every exception to the order. It's usually well worth the money for employers to keep the good employees and let the worst go. In Sweden this is effectively the only way you can make the "stack ranking": you move a bunch of workers to a special branch or factory. Then shut down that product/factory/office. Then pay those workers a years salary or two to not come back.
So the solution discussed in the article is meant to make it easier for companies to change strategies e.g. by laying off entire branches. Such as banks closing offices now that most people bank online, or Ericsson shutting down all their factcories that made landline phone switches. It's not about the ease of firing individual employees.
A system for making labor laws less strict to make it easier to lay off individual employees is popularly called "Flexicurity" after the model used in Denmark. Basically, the worker collective would accept liberalization of the ordering rules in exchange for public safety nets being so good that being laid off doesn't really matter (Say e.g. 80 or 90% pay in unemployment benefits). This type of model has been proposed for Sweden, but it has never really been close to being implemented yet.