One of the benefits of questions that this article did not seem to cover is that it helps one avoid solutionising. "How can we help our users feel less frustrated with our service?" inherently gives you more alternative courses of action than "we gotta optimise page load time of the checkout function".
Sometimes the question leads to the first solution that came to mind, but the technique is at its most valuable when it does not. Maybe the checkout page load time isn't as bad as the dark patterns and getting rid of them improves user flow more at a lower cost than rewriting a critical component.
Sometimes the question leads to the first solution that came to mind, but the technique is at its most valuable when it does not. Maybe the checkout page load time isn't as bad as the dark patterns and getting rid of them improves user flow more at a lower cost than rewriting a critical component.