Notes
Notes I write to think through design work more clearly. Mostly small conversations with myself about messy product decisions, team discussions, and the details I do not want to forget.
- Product thinking
- Decision making
- Design maturity
Design is more than making good screens
A note between me and myself about the point where design stopped being only about screens for me. It is about explaining decisions, handling tradeoffs, and helping the team move with more clarity.
- UX details
- States
- Design QA
Small UX details that real products teach you
A note about the small things I used to treat as polish, but now see as product quality. Copy, empty states, loading, long content, and QA are often where the user actually feels the product.
- Collaboration
- PMs
- Product decisions
How designers can work better with product managers
A note on working with PMs without turning design into a handoff machine. The useful part is not winning the argument, it is making the product decision clearer together.
- Pocket FM
- Solo design
- Systems
What I learned as the first designer at Pocket FM
A personal note from being the first designer at Pocket FM, when there was no design system or clear process to lean on. I learned that the job was not to touch everything, but to make the team clearer.
- Research
- Tradeoffs
- Premium
How to practice product research without getting lost
A note on keeping research close to the decision instead of collecting endless notes. I use examples from subscription, paywall, player, and creator flows because research gets useful when it changes the next product move.
- Error states
- Recovery
- Trust
A practical guide to error handling in product design
A simple note on designing what happens when the product cannot do what the user asked. Error states are where trust can break, so the message, recovery path, and saved progress all matter.