After our critique on Wednesday, we realized everyone was on a different page when it came to understanding the methods behind the System Map. In conclusion, we came up with a definition for the process. A System Map is an outline of the artifact (that will be created later) that tells a story of the experience the user will have while using the product. The context should be considered as well, meaning where it will be used, who will be around while using it, and what other factors may play a role while using the product.
So I revisited my System Map, and considered where my persona will be using the product (at the ballpark), who will be around (other fans/friends/family), and what they may want to do (buy a beer, find their seat, see where the last pitch was, find their car after the game, etc.). My main goal is to enhance the ballpark experience with a handheld device without the product becoming to much and overwhelm the user. It can be used as much or as little as the user wants, depending on what they want to get out of the product.
Overall, I think Wednesday's class was very useful, and cleared up much confusion for us. Before, we were trying to think as Graphic Designers and think of only the end product, rather than Interactive Designers and thinking of the experience we want to create for our personas.
No comments:
Post a Comment