Your First Year as a Product Designer: A Realistic Map

Portfolios are tidy. Real product work is not. If your first months feel messier than any case study you have read, that is normal, and it is not a sign you are in the wrong job.

Months one to three: listen

Your most valuable output is understanding. Learn the product, the customers, the vocabulary of the engineers and the history behind decisions that look odd. Ask why before suggesting a redesign.

Months four to eight: ship small

Take on contained problems and see them through to release. A shipped improvement to a settings page earns more trust than an ambitious concept that never leaves Figma.

“Trust in a team is built in small, finished things.”

Months nine to twelve: widen the lens

Start connecting your work to metrics, and to the roadmap. Offer a point of view on what the team should stop doing. This is where designers become partners rather than service providers.

• 01Keep a decision log so you can explain why, not just what.
• 02Pair with engineers early and often.
• 03Ask for specific feedback, such as 'Where did my rationale feel thin?'
• 04Revisit your portfolio every quarter with real outcomes.