dreamlydia. — Product Designer & Design Engineer

← CASE STUDIES

CASE STUDY · DESIGNER'S RETROSPECTIVE

Turning the weekly report into something a system does

Methodology for moving a recurring manual chore into an automated pipeline — without losing the judgment that made it worth reading.

automationprocess-designmethodology

Turning the weekly report into something a system does

↔ THIS CASE STUDY IS ABOUT

A structured review-trail plugin that turns scattered design feedback into addressable, statused, traceable records — so critique stops dying in chat threads.

VIEW PRODUCT →

↔ THE PRODUCT

A structured review-trail plugin that turns scattered design feedback into addressable, statused, traceable records — so critique stops dying in chat threads.

VIEW PRODUCT →

OTHER CASE STUDIES

Why review feedback keeps dying in group chatsA recurring annoyance became a data model, then a shipped plugin — the full trail from problem discovery to the decision that shaped it.READ CASE STUDY →

The handoff doc nobody reads — so I made it executableDesigning a CLI as a design deliverable: what changes when the spec is something engineers run instead of skim.READ CASE STUDY →

RELATED WRITING

✎Versioning a design system beyond the Figma library2026.06 · 7 MIN ✎Where AI-assisted design review stops being useful2026.05 · 6 MIN