Sorry I didn`t respond last night - went to sleep after watching a frustrating game
I guess my frustration was primarily with putting Stanley and Pionk on the ice as a pairing - period. For a team that really struggles with exiting their zone, why put the players with the worst defensive zone failure rate (more turnovers per breakout attempt) together on one pairing? And if you are foolish enough to do so, why put them behind a set of forwards who themselves show little discipline in basic zone coverage ,or in supporting zone breakouts after puck possession is secured?
But let`s be clear - the coaching problems last night went well beyond this issue. I don`t think Bones prepared our PP for the very disciplined PK that the Flyers used. Holy crap, the Flyers set a simple 4 man diamond defensively , stayed static and refused to challenge anyone playing with the puck on the periphery, and our guys didn`t know what to do. They had absolutely no strategy for attacking or moving the defenders out of position. Combine that with some poor puck management and ...... not much happening.
Thoughtful response - nice
I agree that Stan and Pionk was a bad idea - no idea why that happened and hopefully there was a lesson learned.
Stan isn't going to be the bright spot on the D most nights - he's a 6/7 player that should be able to hold his own if paired correctly.
It's not like we don't pay attention to pairings - they are important. What's funny is that you'll see a lot of posts pointing out that any pairing with Pionk, has failed. What's interesting is that when Stan is paired with him, he takes most of the blame - odd reasoning IMO. The 6/7 guy shouldn't be taking the blunt of it on a pairing with a $6M dman that has not really played well with anyone. Watching Pionk defend is hard to do - he's out of position most of the time - chasing someone in a corner a mile away from the puck or he's trying to run someone who is not part of the play. Stan get caught puck watching in those situations - usually in front of the net - probably because he's trying to cover too much territory with his partner out of position most of the time, so he parks in front and tries to defend it all from a place where all the pucks are heading - it's a disaster.
As for coaching, we can pick it apart - there are no doubt issues with some of the decision making.
What's hard to explain is that this team can play well under the systems and matchups the coach throws out there if they play the game style that Bones has been preaching since day one. If we want to talk about major issues, I'd consider the over all drive and compete to be the major issue - and that's a tough one to put your finger on without calling out a bunch of high paid players - it was nice to see Bones actually do that.
IMO, this team is not good enough to play the game without dedicating a big pce of that plan to hard work and compete - it's been proven - when we win, we are working hard, the offense is involved at both ends, and our bottom 6 is keeping it very simple with a defensive game - and our d is not over burdened. When we lose, our best forwards are not engaged defensively and our defense is hung to dry. The narrative then shifts to how we can improve our bottom six (as if this would make up for what is going on with the top bunch), and the defense is called out for not playing well when they are abandoned when defending.
I don't believe the strategy, in terms of what the coach has been preaching, has changed. What has changed is how our best forwards are playing. They don't defend at all and we get bogged down in our end. If you spend that much time defending (or defending poorly), you'd expect the offense to look out of sync. It's a carbon copy of where we were LY - scrambling most of the shift on D and coming out of your own end late in the shift, making poor decisions with passing / puck movement that usually result in a turnover.
If we don't fix the work part, especially while defending, I don't see there being a point in evaluating the rest of it - IMO, without the work, the rest doesn't work.