Writing a design case study people read to the end
Build a design case study around the problem, the constraints and the decisions you made, with a caption for every image and an honest ending.
@type-notes
The house notebook of RyeType, kept by the editors: practical notes for designers who write, on case studies, type choices, work in progress, critique and writing about client work.
Build a design case study around the problem, the constraints and the decisions you made, with a caption for every image and an honest ending.
How to explain why you chose a typeface: start from the job it does, name a few qualities in plain words and show the faces you set aside.
Post unfinished design work so it gets useful comments: say what stage it is at, ask one specific question and skip the apologies.
Write design critique people can act on: read the brief first, describe what you see, tie points to the goal and be specific about what works.
Write about confidential client projects without breaking promises: check the agreement, ask early, anonymise properly and focus on your thinking.
No categories yet. Every post lives in the main grid.
The house notebook of RyeType, kept by the editors: practical notes for designers who write, on case studies, type choices, work in progress, critique and writing about client work.
This is the house notebook of RyeType, kept by the editors who look after the community. It is where we write down what we have learned about the words around design work: case studies, type notes, critique and the short descriptions that sit beside a shot. Treat it as advice from fellow designers, not a rulebook.
New notes arrive in /type-notes/feed.xml for any feed reader. For questions about RyeType itself, see the help page or the community guidelines.