Most engineers describe their work in activities: closed tickets, merged PRs, shipped features. Product Engineers describe their work in impact: adoption, retention, revenue, cost reduction, support tickets avoided, customer behavior changed. In this hands-on workshop, attendees will use the Product Engineer playbook to move a vague product request up the Clarity Ladder: from activity, to output, to result, to impact. We will define why the work matters, scope what should be built, use AI-assisted prototyping to pressure-test the plan, and design the measurement loop before shipping. Participants leave with practical artifacts they can reuse immediately: a problem brief, build scope, AI context packet, and ship-review template.