Why designers should write product specs — even when no one asks
When I started writing mini-PRDs for my own design work, my relationships with PMs changed overnight. Here's why.
I work at the intersection of design and product — turning messy problems into experiences people love and businesses measure.
Tools & Skills
Users submitted requests that disappeared into a black box. I designed both sides — user tracker + admin tool — expanding a single-surface brief into a complete operational product. 500+ requests. Zero manual emails.
Post-acquisition, 900 duplicate profiles needed reconciling. I designed a merge tool that handled complex nested data structures — after a full restart when engineering revealed the true complexity.
First AI feature in the product. IROs were spending hours piecing together investor relationship insights from individual meeting notes. I designed a summarisation experience that surfaces themes, sentiment, concerns and tone — embedded in the investor profile and the board reporting tearsheet.
After failed vendor negotiations, I built in-house. Key insight: users weren't confused by the interface — they were confused by the words. UX copy became the entire design strategy.






Amerta consistently pushes the boundaries — every solution she brings is more intuitive than what we asked for. She thinks in outcomes, not deliverables.
She's a design thinker and visionary — she sees the product three steps ahead. The kind of designer who makes the whole team think differently.
You didn't just understand our workflow — you understood our pain points and internal inefficiencies brilliantly. This is exactly what we needed.
"I ASK WHY BEFORE I OPEN FIGMA."
I'm a product designer who joined a fintech startup early — when the product was still being figured out — and stayed through growth, scale, and a global acquisition. Over 4+ years I've designed across user-facing products, internal tooling, and service design, always asking what the business needs before asking what users see.
I'm growing toward product management because I want to own the full problem — not just the screens.
OPEN TO NEW ROLES →When I started writing mini-PRDs for my own design work, my relationships with PMs changed overnight. Here's why.
It's not "what should this look like?" — it's "what decision is this design helping someone make?" Everything else follows.
Users weren't confused by the interface. They were confused by the words. Fixing the language fixed the product.
Open to Senior Product Design roles, PM-adjacent positions, and genuinely interesting problems.