Overview (Client / Company)
TIP: 1 – 3 sentence summary of the company or product.
After reading this, someone should get the “gist” of what this product or company was all about and the primary goal of the project.
Problem Statement
TIP: What was the purpose of this project? What problem was this trying to solve? Or if it was a research project, what were you trying to learn?
After reading this, someone should have a clear understanding of why this project exists, and what problem it was created to solve.
Users & Audience
TIP: Who was the user of this product?
Sometimes, that might also be internal stakeholders. Were there use cases, personas etc? Get specific, don’t just refer to them as “users”.
Roles & Responsibilities
TIP: What did you do? How big was the team? What were the other roles on the project team? Was this conducted remote? Was there an external company or partner involved?
This is crucial because people want to know that you can collaborate with others, and if you can show any ‘real world’ context, the more, the better.
Scope & Constraints
TIP: Where there unique factors for this project? A short timeline? A small budget? Did the scope change during the project?
Provide some context about what you had to work with on this project.
Process & What You Did
TIP: This will be the bulk of the case study, but for this outline focus on addressing the high level of what you did.
Think of this like a set of instructions or recipe, so that if someone else had to do this project, they could see the steps they’d need to take.
Outcomes & Lessons Learned
TIP: What happened in the end? Did you reach the goal that you had at the beginning of the project?
If it was a research project, did you learn what you wanted to learn? If it was an MVP, did it work/launch?
If you have any quatifiable outcomes, such as numbers, benefits, testimonials etc, make sure to include them.
Don’t forget to be reflective and consider things like: what did you learn, did anything go wrong, what would you do differently next time etc.