Project Title
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
CLIENT
Relofriend
ROLE
Solo Product Designer
SCOPE
Mobile-First Website
CONSTRAINTS
2 user flows
TIMELINE
Aug, 2026
TOOLS / SOFTWARE
Figma
project background
Project background and design problem is clearly defined. Could include market research (optional).
research plan (optional)
Outlines the research methods used, reasons for selecting research methods
primary research: competitor analysis
(Required for Feature Add and End-to-End, optional for Responsive Website)
- The analysis has least 3 competitor's primary service and product features
- Written explanation provides details on summary of key findings, identified opportunities, competitors' strengths and weaknesses[Optional]
- The analysis includes screenshots and explanation for the competitors and their features
primary research: user interviews
Interview results clearly address the research goals and questions from the research plan
Results do not assume a solution
Written explanation provides a summary of key findings
user persona
Persona is relevant and based on research results
The persona not only shows a character (demographics and background bio), but their role in relation to the product is very clear
The persona specifies pain points, goals, and other important details related to the project
Written explanation discusses key findings such as relevency to the project, personality traits, highlights of user pains and needs
Research Synthesis
(ie. Affinity Map, Empathy Map,
Customer Story Map,
Journey Map, Storyboard,
How Might We, etc.)
(1 type of synthesis is required for each case study. You can have different ones for each case study, or similar ones.)
Includes sufficient key findings from all executed tests
Presentation is clear and has subcategories and other aspects to go more in depth
Goes into detail with specific comments from users
Reflects the chosen persona in a relevant way, offering key learnings of the persona's life with quotes and key insights about their day-to-day experiences in relation to the product
Feature Roadmap/ Product Requirements
(Required for at least 1 out of 3 case studies)
Essential and main elements are reflected in the document
- Written explanation discusses prioritization rationale
Sitemap
(Required for at least 1 out of 3 case studies)
All important pages are represented and well placed on the sitemap
Sitemap is easy to understand and is very thorough and represents more than just the basic or essential pages
Written explanation discusses rationale behind the design of the sitemap focusing on key items
Task Flow / User Flow
Includes at least either user flow or task flows
Flow diagram uses symbols correctly (diamonds for decision points, circles for start and end points, rectangles for everything else)
Written explanation discusses rationale behind the flows based on prior research
Written explanation includes key takeaways, findings, and opportunities identified
Branding
Yes*, required for End-to-End, Optional for Responsive Web Design & Add a Feature
The branding and logo matches the brand values and the audience
Logo is optimized and ready for many different sizes and usages
Written explanation discusses rationale for logo concept, inspiration, colors, etc
Lo-fi Wireframes
Wireframe shows exploration and iterations
Good and clear presentation of at least 5 key screens
The wireframes clearly show that the content and purpose of every block on a screen
Enough wireframes of key screens were created to test a complete flow
The wireframe elements have been thoughtfully considered, and the annotations make sense in context
Written explanation discusses design rationale, thought process behind iterations, and details for key screens
Hi-fi Wireframes
Wireframe shows exploration and iterations
Good and clear presentation of at least 5 key screens
The wireframes clearly show that the content and purpose of every block on a screen
Call out a few key screens to discuss at a deeper level of detail
Enough wireframes of key screens were created to test a flow
The wireframe elements have been thoughtfully considered, and the annotations make sense in context
Written explanation discusses design rationale, thought process behind iterations, and details for key screens
UI/ Visual Design
Final design shows exploration and iterations of visual design and UI design
Call out a few key screens to discuss at a deeper level of detail
Written explanation discusses design rationale, thought process behind iterations, and details based on branding and art direction
UI Kit
(Required for at least either the Responsive Website or the End to End case study. Not Required for the Add a Feature)
UI kit includes all key elements
- UI elements are properly labeled and easy to understand
Usability Test Results
Testing conducted with at least 3-5 participants
Provides a summary of synthesis including observations, insights, and opportunities
Revisions
Revisions were applied based on highest priority based on the feedback from evaluative research and insights
Written explanation discusses the changes and iterations in detail
Prototype
(Required for at least 2 case studies)
Prototype is interactive and includes at least 5-8 screens to test key hypotheses
Final Results
The conclusion discusses:
Personal reflection and learnings as a designer looking back into the project, lessons learned, achieved goals
Next steps and key takeaways from the project itself
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Posuere Curabitur.
