Here you can provide a high-level summary of the project and your involvement, as well as briefly introduce the client, along with some context leading up to the project.
Company: Name
Length: Project duration
Completed: Project completion date
Team: Team member 1, 2, 3
Tools: Research, Design and Prototyping Tools
Here you can briefly outline what the business goals and objectives are, and how the project will help achieve these.
Here you can elaborate on the challenge my team was tasked to solve, by explaining why and how it was hurting users and in turn the business. You can also mention any constraints you were operating under.
Here you can describe what pieces of the project you was solely responsible for, and what was your contribution to the more collaborative efforts.
This is an example activity carried out in the research or exploration phase of the design process. Other research activities could include UX audit, analytics review, user/stakeholder interviews, user testing, heat mapping etc. The purpose here is to first communicate why the chosen research activity was the most suitable one, given the context and constraints. Subsequently, demonstrate how you developed a better understanding of the problem and users, that will help define your hypothesis, UX metrics as well as inform your designs.
Building on the discovery work, here you can showcase your initial designs created in an iterative fashion at varying degrees of fidelity, from sketches, wireframes to mockups and interactive prototypes. You could also show how you defined user flows and the intended user behaviour with the product feature.
Here you can show key deliverables such as flowcharts, design specs, a prototype demo and any other accompanying design assets required for implementation and QA testing. You can also present the feedback gathered from the prototype testing.
Here you can outline the A/B test results from the limited release of the product feature. This includes showing whether the hypothesis has been validated or rejected, but also evaluating the impact of UX changes to both the quality of user experience and the goals of the business and/or brand.
Similar to a product design team retros, you can share what worked well in this project, that could also be applied in other cross-functional projects. The purpose of this section is to help identify best practices and methodologies that best align and support your project goals.
Similar to a product design retros, you can share what was challenging about this project that could inform your future work. The purpose of this section is to be honest and transparent in that no project goes perfectly smooth, and that there are always obstacles to overcome and learn from.
