Home

How I make product decisions

Working as a solo startup designer taught me how to move fast with imperfect information. I don't just push pixels; I focus on reducing risk, shipping functional products, and keeping the team aligned.

Here is what that looks like in practice:

1) Reduce uncertainty early (Whiteboards over polished UI)

I’d rather learn early than polish the wrong direction. Before I open Figma, I clarify assumptions and simplify the core question.

The reality: When a map feature was struggling with a 4% adoption rate, I didn't jump into Figma to redesign the UI. I used a whiteboard to map out the user psychology, edge cases, and the biggest product risks to find out why it was failing before committing to detail

2) Design for the build (No isolated features)

Product decisions need to make sense within the technical reality of the engineering team. I don’t see design as separate from delivery.

The reality: I regularly jump into the frontend code to test feasibility. Because I understand CSS Grid, breakpoints, and component logic, I design clearer, technically sound solutions that don't become a nightmare to implement for developers.

3) Move decisions forward together

Product decisions die in isolation. I don't wait for formal presentations to get feedback.

The reality: I align with developers and stakeholders from day one. Instead of designing a polished "final" version and hoping for approval, I share rough concepts early. For me, collaboration isn't just about collecting opinions at the end; it’s about building a shared understanding early enough to avoid expensive rework later.

Product Designer focused on usable, feasible products

Designing with implementation in mind.