02 Documentation
Turn fuzzy requirements into plans the team can move on.
I write documentation that doesn't just explain — it enters the design and development pipeline. PRDs, FRDs, feature specifications, user journeys, acceptance criteria, and analytics event design.
The goal is always the same: clarify product logic, business rules, and key boundaries early, so design and engineering have clear enough inputs to cut back-and-forth and rework.
01
Pawly — Product Management Intern, Growth & Strategy
Scope
PRD · MVP scope definition · Feature specification · User flows · Acceptance criteria · Analytics event design
From early product direction, I scoped Pawly's MVP and core experience and turned it into an executable product requirements document.
This case study covers: MVP feature scope, user flows, business rules, edge cases, acceptance criteria, and key event-tracking logic.
02
Uplifty AI — Product Management Intern
Scope
Feature specification · User journey mapping · Product gaps · Edge cases · Acceptance criteria
Contributed to product documentation for several core modules during the Beta phase, breaking broad product ideas into specific behaviors, user paths, and delivery requirements.
This case study covers: selected feature specs, user journey mapping, product gap identification, edge cases, and acceptance criteria.
All materials shown have been reviewed and limited to publicly shareable, non-confidential content, while preserving the original product reasoning, documentation structure, and decision logic as fully as possible.