Writing around case studies

Case studies often become too polished. They show the final image, but hide the small decisions that made the work function: what was simplified, what was repeated, what was rejected, and where the system became easier to use.

For independent posts, I want to write around those decisions without forcing every thought into the main project page. The case remains visual and fast to scan; the blog post can explain the production logic in a more direct voice.

That split keeps the portfolio clear for clients and still leaves room for process, mistakes, and practical notes.