When you feature a project for a stakeholder, you typically write a case study that best utilized the projects features and observations. This is usually important in the hiring process, so the hiring manager can access your skills and insights, to see if you are adapted best to the project.
When learning how to best showcase exemplars, you must have what key information drove your design decisions, and how you came to the conclusions you did. This can be showcasing the User Interface, and all its brilliant qualities, or the User Experience aspects that were drawn up from its wireframes and original mock-up.
Observing how these are broken down, analyzed, and constructed vary based on the designer’s skill set, and you can best see how to play to their range of strengths and have distinct specialties.
I have tried to frame my case studies with these steps to try to play to it’s ruling and find new dynamics for the user to explore: Find a distinct tangible overview or outline for your case studies that encompassed it.
- Tools Used
Distinct Achievable Goals set for your app, collectively from the Competitive Analysis and User Journey, Mood Board and Style Tiles.
- User Journeys
- Design Requirements
- Set up Design Trend
Utilize all your Research and User Insights are used in the reiteration and overall process throughout the user journey lifecycle
- Qualitative & Quantitative Data
- Observational Inquiries
- User Profiles
- Journey Maps
- Confirmation Bias
You also exemplify all your work that you complied to create the final product
- Any Lo Fidelity Mock-ups
- Hi Fidelity Prototypes
- Final Prototypes and Testing
- Final Prototypes and Solutions
- Impact and Results
All your work when approaching a case study is vital. Designers do them more and more often and see their work and the overall velocity increase when they start to find better solutions. These case studies encapsulate all the groundwork, and how you evolved with the project for the best possible outcomes.