Where the design community meets.
laurenholliday.com Joined over 7 years ago
Amen to No. 2!
I do happen to know a lot about startups, as I've had a lot of my own, and I've worked for startups in the marketing department for the last 10 years.
Re No 2: Isn't that sad af?! It's all about the TEAM and that Rahul successfully founded Rapportive and has loads of YC-like connections. That's why I mention "walled garden." Also, with that much money they should have a legit website. Shows they don't value marketing and just assume they're the best.
Re No. 3: There's NO proof they have 100k people on waiting list. It only gets 169.9k visits / month, according to SimilarWeb. What would that conversion rate be? It's sad fact that A LOT of startups straight up lie. Not saying this is the case here but I would be far from surprised.
4) You're on DN. You're not a mainstream audience visitor. This was from the point of view outside this niche tech community.
not sure I understand last comment.
I'm interested in trying Webflow. I'm not sure if this counts. I always design/build websites in WP. What does everyone think about Webflow compared to WP? Think it's the "next thing?"
This is helpful!! Thank you, Benjamin! =)
Hackthejobhunt.com was a site for millennials. I was targeting millennials, and it was a fun side-project for me.
I was selling me in a sense because I'm the teacher so I wanted to show off my personality.
As for this other site in question.
This is the site: https://goskills.com.
Our audience is segmented nearly half/half -- millennials and older generations.
She said that in response to an email design I used. (I never curse in clients content -- that was for my site only).
I always think about the user first, and myself second -- unless it's a project for me for fun.
Because the site (goskills) is a course site with different categories, it seems to make sense to use different colors to differentiate so I used those different colors in the email to signal people to get used to seeing a certain color and knowing they are in their topic of interest.
Thank you!! This makes sense! =)
Thanks, Mal! =) Yep, but I'm more of a marketer, who enjoys good design. You can see a case study I did for a marketing client here: http://laurenholliday.com/sitepoint/
5 key elements of good design case studies
1. Executive summary
Hanno is a simple, but excellent example of a good executive summary.
This is a general overview of the project. It should be short and sweet for the skimmers because only a few conscientious prospects will actually read each project’s case study.
The content in this section should detail a high-level overview of the other sections, including:
Main problem: The reason they hired you. Solution: How you solved the problem. Key results: What were the deliverables or KPIs?
Productivity Tip: Write this section last, after you’ve written all the content for the other sections.
2. Context and challenge Next, you should give prospects context into the problem you were hired to solve. You can do this by answering the following questions.
a) Project background description: What context information do you have for this job?
Again, Hanno does a simple yet effective job providing a quick contextual overview for site visitors.
b) The problem: Why did they hire you?
Notice how Hanno highlights the problem in big H2s then follows up with an interesting story.
c) Goals and objectives: What were the agreed-upon goals of the projects? While difficult sometimes to get, the key here is quantifiable metrics. Think about the tangible goals of the project. Maybe you reduced the number of cart abandonments or your design increased conversions by X%.
Work&Co quantifies its contribution to the client.
Helpful Tip: At the beginning of new projects, make sure these points are clearly articulated to you by the client to save you a headache trying to figure out this section after the project is done and shipped. If you’re working on a case study for a completed project, look back to your creative brief, project description, or request for proposal (RFP) to find this information.
3. Process How did you get from the problem to your solution?
The process section should describe how you approached solving the client’s problem and why you made the decision(s) to approach the project this way. It’s helpful for prospects because it gives them a glimpse into the experience of working with you.
You’ll want to present clients with a walkthrough of your research and workflow as well as with iterations at various stages of the process. From the research you present -- anything from A/B tests to user interviews -- prospects should be able to extract key insights into how you arrived at your findings.
Efficiency Tip: Try to accumulate as much information about a client’s audience as possible. Ask for buyer personas. Talk to support and see what people are asking most frequently. This can save you time, when it comes to developing a key insight to guide your design decisions.
Most processes I found are detailed stories, making it harder to take a screenshot of. The simplest process I’ve found is by Nunrun.
4. Solution Take screenshots. Include links. Record a video. Do anything to showcase your solution in this section.
While this is the place to showcase all your hard and beautiful work, it is not the place to skimp on the textual details. Spend time refining clear copy that provides more insights into everything you present -- from navigation structure to mobile-only attributes.
Above-and-Beyond Tip: This is the place to truly impress your prospects. Take the extra effort to consider adding a video or interactive features.
Here’s part of a solution section taken from Hanno’s Uber Case Study.
5. Results Show them the numbers.
This section should showcase your success metrics from the project. Success metrics could be qualitative (a testimonial or press quote), quantitative (KPIs), or better yet, both.
Here’s a nice, compelling results’ slider that showcase bigger business objectives.
It’s vital that the metrics/results you showcase directly address the objectives you detailed in Section No. 2 (Context and challenge). This proves you directly contributed to the client meeting their big picture goals. This will increase their trust in you and differentiate you as more than just a designer, who makes things pretty.
As for testimonials, in order to be effective, they must be compelling and show that you made a measurable impact on a client’s business. Paul Jarvis details three types of effective testimonials in the Creative Class.
The before-and-after changes a client experienced from working with you. The excellent results they achieved. They unexpected value they received from your work.
Jarvis also recommends following up a few months after the project is completed.
“Following up a month or two after the end of a project is another way to collect more powerful, results-driven testimonials. Ask how your work has affected the business, created quantifiable sales spikes, or if there have been other positive changes that speak to the value of your knowledge and services.” (source)
This testimonial is perfect.
Think-Ahead Tip: Plan the experience of working with you, and build securing client testimonials into your design process so you don’t have to ask for them five months later. Also, each time you begin a new project, make sure to connect your work to quantifiable business metrics and objectives. This will make your life way easier when it comes time to build your case study later.
Tell a compelling story, and the clients will follow. While a good case study presents all of the above, there is no hard and fast rule that you have to include every section and/or present your case study in this exact order. I’ve seen loads of gorgeous and compelling case studies, yet no two tend to look the same because each designer has a unique style and personality.
In order to hit my point home, I’ve included a list of a few of my favorite case studies below. So what are you waiting for? Get inspired now.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
It's part of a blog post I'm writing, in which I dive deep into specific actionable feedback for them. I was sharing a sneak peek.