From anecdotes I have come across it would seem some staff do not want it to work.
Or, if I may, some staff don't care about PB or even FF elites. And I think the reason why they might have this feeling is because, they think they care about passengers safety, getting security checks and that done and somehow safely and comfortably get the passengers to their destination. Anything apart from this, I think, the staff think as an overhead. Sure, I'm a Platinum FF, but doesn't mean anything to the staff, more than a welcome back or is there anything I can get you.
I think when being asked to enforce PB, the mind voice of the staff goes "yea, yea, we need to board elites first, but hey, elite or no elite, we need to board everyone waiting to board and can't afford to miss anyone. So for us it really doesn't matter - just get everyone on board, safely, show them the safety procedure, serve drinks, food, go back to the galley have a nice chat, then come out during arrival into destination, get ready for the next flight service & the cycle continues". No where in these tasks/activities, would the crew think about enforcing PB. If any elite provides feedback, let's tell him " we will ensure the PB works as we said it would, thank you for your loyalty and thank you choosing Qantas, have a great day"
I may not be putting it well in words, but I'm comparing the staff attitude towards PB as what an IT service desk person has towards someone who has the blue screen problem. I mean, it's an issue, but just restart your machine and get on with it ... IT service desk people are not thrilled by and take all measures needed to look into your problem. They'd be like, "yea yea, I've seen this problem before, it's not biggie, a hard reset and you are as good as new"
hope I'm making some sense
and if not, I'd like everyone to know that my heart is in the right place
I work in the IT Service desk and when someone pops by with blue screen, we recommend a hard reset and let us know the next time it happens ... it's not because we don't want to look into it, it's just that this issue happens at random and we try to contact the hardware vendor who points us to the operating system vendor, who in turn points us to the hardware vendor and the blame game goes on and on ...