Included on this page are instructions for what should go into a Goal-Directed-Design-based Process Page. If you have questions, please contact Prof. Lahey via Teams or email.
This section acts as a summary of your entire page and is something you should strongly consider. What are the important things someone might want to know at a glance? This is an important section for job recruiters and the early stages of the interview process. Keep it short so that it exists totally (or mostly) over the scrolling break. (Also, consider steering away from templates with huge hero-style image sections at top because it pushes your content down too far.) You should consider all the information below in some similar order:
Approach. GDD (you'll elaborate below)
App idea. Distill it down to a sentence.
Objectives. What did you set out to achieve?
Role. What was your specific role?
Team size. How many?
Duration. How long did you work on this project?
Tools. What tools did you use to complete this project?
Links. Include links to all important files and/or other relevant information.
In this section, you should lay out what the reader will experience in more detail. In short, you are elaborating on the Executive Summary. Consider:
In this section, you'll explain your method, GDD. Remember to explain it to someone that might have no experience with it but keep it as short as possible.
In this section, you'll explain how your team navigated the GDD Research Phase.
In this section, you'll explain how to synthesized your research into persona(s). Put another way, you will explain the results of the Research Phase and how your persona(s) came to be. Follow the 4-part model.
In this section, you'll explain how your team created a list of requirements for your app. Put another way: How did you turn your persona(s) into a list of actionable items for shifting from research to wire framing? Follow the 4-part model.
In this section, you'll explain how your team created a low-fidelity wireframe (Key Path + Validation Scenarios) and how you transitioned to prototyping a high-fidelity version of your app. Put another way: How did you turn requirements into a wireframe? Follow the 4-part model.
In this section, you'll explain how your team refined your prototype via usability testing. Put another way: What did you learn from usability testing and how did you integrate it into your prototyping? Follow the 4-part model.
The most important thing to do in the Conclusion is to discuss lessons you learned from the process. (This is important for internship and job interviews.) What would you have done differently if given another chance or more time? Did you have any issues during the Phases? Did you have to change anything because of user feedback? Employers understand that not everything works out perfectly; how you deal with adversity and how you can reflect on past projects shows your ability to grow.