Discover
Business context, user research, data, competitive analysis. Align with PM and engineering on the actual problem.
About
I'm Amr Kamel — a product designer and design lead focused on the structural side of design: systems, process, and the decisions made before anything reaches a screen.
Sixteen years in, my through-line hasn't changed. The design work that matters most is rarely the most visible — it's the infrastructure underneath that determines whether a product scales or strains. That's where I do my best work, at the seam where product, systems, and engineering meet.
How I work
Four steps that turn an ambiguous problem into a shipped product.
Business context, user research, data, competitive analysis. Align with PM and engineering on the actual problem.
Synthesize into a sharp problem statement and success metrics. This is where the requirement gets reframed — and where stakeholder buy-in happens, before pixels.
Explore multiple directions, critique internally, prototype, test. Diverge before converging.
Refine, spec, hand off to engineering or co-build, QA the implementation, measure against the metric set in Define.
Capabilities
Figma (Variables, Tokens, Dev Mode, Auto-Layout, Components, Variants, custom plugins), Adobe XD, Affinity, FigJam, Miro
Rive, Lottie, Spline — generative-AI moments, empty states, loaders, identity work
Claude, ChatGPT, Lovable, Google Stitch, Figma AI (daily) · Gemini, Manus, Perplexity (research)
Asana, JIRA, Confluence, Slack, Notion, Azure DevOps
HTML, CSS, Angular, React, Vite, Supabase — fluent enough to partner with engineering, not just hand off
Hotjar, journey mapping, discovery workshops, usability testing
Education & credentials