I may have not been clear. I am agreeing with the entire post. I agree with your comment too that “user stories” arose most likely for the same reason as this bias.
I also agree with you that figuring out intention is an important part of development. A majority of users will use my software with the same intent.
I just meant to say that I immediately thought of “user stories” while reading this post. My initial thought was that user stories focus too much on intent. For example, if you are hyper focused on the user trying to reset their password you may neglect the user who accidentally clicked the reset password button and just want to navigate back to the log-in page. Would there be benefit to removing the user story as a goal and just make the goal, create a reset password page? I agree with you though, user stories serve their purpose and might be more of a net-good. This post just helped me recognize a potential pitfall of them.
I may have not been clear. I am agreeing with the entire post. I agree with your comment too that “user stories” arose most likely for the same reason as this bias.
I also agree with you that figuring out intention is an important part of development. A majority of users will use my software with the same intent.
I just meant to say that I immediately thought of “user stories” while reading this post. My initial thought was that user stories focus too much on intent. For example, if you are hyper focused on the user trying to reset their password you may neglect the user who accidentally clicked the reset password button and just want to navigate back to the log-in page. Would there be benefit to removing the user story as a goal and just make the goal, create a reset password page? I agree with you though, user stories serve their purpose and might be more of a net-good. This post just helped me recognize a potential pitfall of them.