The more time spent on defining archetypes, the easier it will be for your team to understand exactly what the system needs to do.
- Archetypes make an emotional connection between the goals of a prototypical user of the application and the software team. Team members will have an easy-to-understand example of a person that prototypically will use your application. Rather than discussing individual features in the application, the team will be able to refer to functions that the archetype will want to regularly use to accomplish their personal goals.
- Archetypes bring discussions of feature, form, and function in the application from a vague general topic to a focused user goal-oriented discussion.
- Archetypes give the team an understanding of where new functions, bugs, and problems need to be prioritized in the overall schedule.