Hey friends!
Hope you had a great week! Today is the 27th edition of Pilcrow, but also my 27th birthday — I’m not feeling too old yet it’s alright! I’m grateful for the opportunities I had this past year, and I can’t wait for what’s to come. Also, thank you for continuing to read Pilcrow. I hope you have a great time every Sunday.
Here are today’s topics:
What I’m working on
Thoughts on case studies
Interesting works of the week
What I’m working on
I’m still working on moodboards.gallery ↗︎ I’ll do my best to include some previews in the next edition of Pilcrow. But right now, I’m in the phase where I hesitate between layouts, and I’m not convinced yet.
I still have the goal to ship this website by the end of the year, and I know this will be only possible by taking decisions early — which means… this month!
Thoughts on case studies
“cASe STUDieS aRe NO longER rEAd. UsE imAGEs as thE mAIn CONTEnT.”
That's the pseudo-hot take you'll see almost every time someone asks about case studies on Twitter/X. I think the reality is more complex than choosing between big chunks of text and large images.
The famous notion of "users scan, they don't read" is often cited here. While I generally agree with this statement, I believe there is a misconception about what constitutes too much text in a case study. Additionally, let's agree on the goals of a case study:
Share your work with your peers and the space
Convince a recruiter that you’re a perfect match for the role
Reflect on your own work and improve your craft
While an image can convey more info than a paragraph, an image without proper caption, context, and explanations will tell you nothing. You need to ensure that the reader has all the necessary context before delving into the actual work. This includes providing information about the space, company presentation, goals, problems, opportunities, etc.
I also tend to think that here people refer to images as an element that brings contrast and rhythm to the case study rather than their illustrative purpose. And that’s where designers can design better case studies, by bringing important info at the top, creating structure and links, and taking care of the rhythm. Here are 5 tips that will help your readers get a better experience while diving into your work:
Include a summary; Mention the space/industry, the company name, key deliverables, timeframe, and platforms.
Include a table of contents; Don't overthink it—keep it to a maximum of two levels of titles, with smooth-scrolling between anchors.
If you can, use the same structure for each of your case studies; This helps readers understand your work process while allowing you to mention specific project details.
Rewrite your case study name so it’s human-readable; You can ask a relative or a friend if they understand it, but make sure it’s not too generic. It’s about balance. (This is still something I need to be better at, to be honest.)
Include outcomes (qualitative and/or quantitative); Data can be daunting, but it's important for assessing your impact on the product, funnel, experience, company, business, etc. Make sure not to share any confidential info and ask for help if you’re not sure!
And don’t forget to credit your peers — as mentioned in Pilcrow #26.
Interesting works of the week
Matt Colangelo — Website
The Corner — Branding
Cercle Montesquieu — Branding
That’s all, friends — have a great Sunday! 🖤