Hatchloom
Making design feedback feel like a conversation, not a thread no one wants to open — a focused space for async design review.
What I owned
- I [owned area one — e.g. designed the review flow from share to resolution].
- I [owned area two — e.g. shaped the commenting and threading model].
- I [owned area three — e.g. prototyped interactions and validated with X designers].
Impact
[xx][reviewers in early testing]
[xx%][faster feedback loops — or your metric]
[x][major iterations to ship]
[—][your metric]
[One line that frames async review and why it's broken.]
[2–3 sentences: the team, the origin of the project, the opportunity.]
[The problem in one sharp sentence — what makes feedback threads unbearable.]
- [Pain point one.]
- [Pain point two.]
- [Pain point three.]
Constraints
- [Constraint — e.g. freelance scope: a fixed budget of hours each week.]
- [Constraint — e.g. an existing codebase that limited interaction patterns.]
- [Constraint — e.g. async-first client, so decisions had to survive without meetings.]
[How I worked]
[Short note on your approach.]
[One insight that changed the direction.]
[The decision that mattered most]
[2–3 sentences on the tradeoff and why you landed where you did.]
The shipped experience
[One short paragraph — let the visuals carry it.]
Impact
[xx][metric]
[xx%][metric]
[x][metric]
[A line of feedback from a reviewer or teammate.]
[Name, role]
Reflection
[2–3 honest sentences on what this project taught you.]