When writing a UX Case Study, your project overview/summary should focus on
- What you did
- How you did it
- The outcome of it all
It is in essence, a summary of the project...NOT the summary of the product itself. ๐งต๐๐พ
- What you did
- How you did it
- The outcome of it all
It is in essence, a summary of the project...NOT the summary of the product itself. ๐งต๐๐พ
Here is an example of a not so great Project Summary
"Hospitalify is a mobile app that allows the staff of a hospital to clock in and clock out with ease as well as track the time spent with patients. It also has a location feature to remind users to clock in and out"
"Hospitalify is a mobile app that allows the staff of a hospital to clock in and clock out with ease as well as track the time spent with patients. It also has a location feature to remind users to clock in and out"
The above is a product summary not a project summary. It tells us about the app you've designed but nothing about what you did.
Recruiters are more interested in your process and how this is tied to business goals and (sometimes) user needs.
Recruiters are more interested in your process and how this is tied to business goals and (sometimes) user needs.
You should definitely talk about your product/solution as your problem-solving skills is also an important highlight for the recruiter. However, the Project Summary is not the right time or place for this.
So how do you write a good project summary?
So how do you write a good project summary?
Here is an example of a better Project Summary
"I designed a mobile app for hospital staff to register work hours and this improved productivity by 20%. I achieved this by reducing time spent clocking in/out, tracking time spent with patients, and sending clock in/out reminders"
"I designed a mobile app for hospital staff to register work hours and this improved productivity by 20%. I achieved this by reducing time spent clocking in/out, tracking time spent with patients, and sending clock in/out reminders"
This tells us
1. What you did
2. The outcome/impact of what you did
3. The things you did that led to the results you got. (If you notice, it is the same features of the app mentioned earlier that were rephrased to form this)
1. What you did
2. The outcome/impact of what you did
3. The things you did that led to the results you got. (If you notice, it is the same features of the app mentioned earlier that were rephrased to form this)
You should always try to measure the impact/outcome of your work as this shows the recruiter that you are not just designing for vibes.
However, where the outcome can't be immediately measured, you can simply use the problem you are solving. i.e
However, where the outcome can't be immediately measured, you can simply use the problem you are solving. i.e
"The productivity levels among hospital staff were considerably low & in need of a boost. To solve this, I designed a mobile app for hospital staff to register work hours. My focus was on reducing time spent clocking in/out, tracking time spent with patients, & sending reminders"
I hope this helps you write better project summaries in your case studies!
Loading suggestions...