Hey Andrew, I agree. The right question and level of abstraction will depend on the context, and any example from this article can be less than perfect in specific conditions. Just as you show in your example

I would like to point out that ideally design sprint already starts with already defined user need. AJ& Smart (the design sprint gurus), themselves start the sprints by doing preliminary user research. So the assumption about the user need should have been somewhat validated before the sprint start.

If you start with a way too open question 'How can we help this target group?', it might work just fine if your end goal is a high-level concept, but also just miss directionality for the team if your desired end result is something more concrete.

This seems like a very politically correct answer, in the sense that I don't give a black and white reaction :) But the 'right' sprint question follows proper research (hopefully it has been done ahead of time) and also heavily depends on your goals and the context in which you are running the sprint. What do you think?