Lets begin by creating a Strategy<\/em><\/strong> for a new product (system\/app\/site etc). (150-200 words) that could give our users a better morning. The strategy should outline the user’s needs so, to better understand your user, create 3 user profiles.<\/strong> Knowing your user’s needs will allow you\u00a0to define your goals for the new product. Through understanding who you are designing for you should be able to answering the following questions: What do you as the creator of your product hope to achieve through its creation? And what will your product \u00a0users hope to gain or achieve by using it?<\/p>\n Part 1.2<\/p>\n Second, define the Scope<\/em><\/strong> of the product.\u00a0by choosing the features and functions it will have (250-300 words). The features you choose must help you meet the goals defined in the strategy,\u00a0for example a goal<\/strong> is: to sell a product; a feature<\/strong>\u00a0to meet that goal would be a shopping cart and method for collecting payment. For the shopping cart to work it will need a database to store products & inventory, and a merchant account to process credit cards to function. In other words features are what the users see<\/strong>, functions are what makes things work<\/strong>. These two\u00a0elements are due next week and must be ready before we move onto benchmark 2.<\/p>\n In class outline a Structure<\/strong><\/em>, aka an information architecture\/ user flow<\/a>, based on your Strategy and Scope. This should illustrate how users can navigate through your product (this should be done in your sketchbook first, then polished in illustrator, photoshop or omnigraphle). This should determine the organization methods.<\/p>\n With your Structure complete, create the Skeleton<\/em> (wireframes),<\/strong> of your product. This should determine the types of navigation used (i.e. global<\/strong>, local<\/strong>, supplementary<\/strong>, contextual<\/strong> and courtesy<\/strong>), as well as, outline the placement of content, navigation, images, video, etc.<\/p>\n Before the end of class photocopy your information architecture and wireframes so everyone in the group has the same set.<\/p>\n As the final step of part 2, construct a paper prototype<\/strong>\u00a0that shows all of the necessary navigation outlined in your Structure and follows the the design of the Skeleton. A robust prototype is due next week and should be ready for user testing.<\/p>\n Individually, shift your focus to the Surface<\/strong><\/em> stage of the design process by creating final design comps that highlight the most important pages of product. These comps should be based on your groups refined wireframes and paper prototypes and use any or all of the following: photoshop, illustrator and\/or fireworks. The visual design should be yours, however it must be based on the group\u2019s structure<\/strong> (information architecture) and skeleton<\/strong> (wireframes). These comps should be either printed and mounted on matte board using dry mount, or presented using google slides.<\/p>\n Lastly, bring the individual parts of your process back together. Create a PDF of your brainstorming notes, proposal (your strategy<\/strong> & scope<\/strong>), architecture, wireframes (make photo copies so everyone has the same set), script and tasks for user testing, reflection on user testing, and comps. Treat this as a portfolio ready piece that will showcase the forethought and planning behind your final visual solution.<\/p>\n Part I Lets begin by creating a Strategy for a new product (system\/app\/site etc). (150-200 words) that could give our users a better morning. The strategy should outline the user’s needs so, to better understand your user, create 3 user profiles. Knowing your user’s needs will allow you\u00a0to define your goals for the new product. … <\/p>\nPart II<\/h1>\n
Articles and Resources:<\/h2>\n
\n
Part III<\/h1>\n
Resources for final comps<\/h2>\n
\n