Thanks @Nancy_Webb_CCSF for getting a post up on this topic.
I'm personally far less jazzed about how checkpoints have been implemented, and I've registered those concerns over in the Discussions Redesign group: A Few Key Pain Points with Checkpoints. For all of the concerns I expressed in that post, the one thing I did not expect was that the SpeedGrader experience was going to be blown up in a manner that would send my faculty into an absolute panic.
I see the logic of the Previous and Next Reply buttons as one way to grade discussions, but I feel like, unfortunately not for the first time, design decisions have been made with a Canvas product that completely fly in the face of regular use cases. Please understand that AI has already radically increased the work load for faculty when it comes to discussions as they seek to sort out real posts from students using AI against assignment directions, and in some cases dealing with large numbers of fraudulent student accounts using AI. I also feel compelled to add that shoving more AI tools into Canvas will not help faculty deal effectively with the problems that AI is creating for them when students use it in unsanctioned manners or fraudsters use it and flood the environment with garbage posts.
Having a clean, quick workflow for reviewing how a student has contributed to a discussion is vital. I'm also pretty certain that the scroll animation is a big time accessibility failure. I recognize that this isn't a bug from the Canvas team's perspective, but it is effectively a severe bug in the grading User Experience for faculty who use discussions heavily. It's a smaller matter for my campus right now because we're in winter session, but a lot of schools are starting their spring terms now and this is once again a disastrous product rollout just when we're starting a term, very much like the huge mess with threaded discussions that plagued the start of the fall term. We really can't go on like this. We need our teaching and learning environment to still behave in an efficient, predictable, and as bug free ass possible manner even as product improvements are implemented. This needs a fix ASAP.
This also seems like the right place to mention again that the feature user group is set to be archived tomorrow, but given the status of the redesign this seems like an incredibly bad idea.