I want to move from agency to product

Agency work looks like this: deliverables on tight deadlines, a new client every two weeks, a landing page on Monday and an app concept on Friday. You never see what happens after handoff. You never talk to a user. You never watch your work iterated on real data.

Agency work is not bad. It teaches speed, client handling, and adaptability. The trap is that you get very fast at executing someone else's vision without ever developing your own product instinct. After a year or two your portfolio is wide but shallow: thirty touched projects, zero owned ones. Product companies hesitate, not because the work is bad but because it does not show the thinking they hire for.

If you feel stuck and want depth, that is not ingratitude. It is a sign you have outgrown the environment.

Agency portfolios read differently. Hiring managers scroll past variety looking for depth: one problem explored over weeks, not twenty solved in an afternoon.

The same title means different jobs. At an agency, UI/UX often means "make it look good and usable." At a product company it means understand the user, define the problem, design the solution, measure the impact, iterate.

You do not speak product yet. Retention, conversion funnels, activation, experiment design. This vocabulary is learnable in a month, and interviews quietly test it.

Do not throw your agency work away. Rewrite your best two or three projects as product case studies. For each one answer: what was the user problem, what were the constraints, how did you make decisions, and what happened after shipping?

The format that works: problem, discovery, exploration, solution, reflection. A hiring manager does not want fifteen screens in an embed. They want three or four screens wrapped in the story of why.

If nothing can be reframed that way, do one spec project with full product depth. Pick a popular app, find one broken flow, research why it is broken, redesign it, and document the whole process. One strong product case study beats ten agency entries.

You already know how to make things look good. That is table stakes. Now learn why things exist and how to tell whether they are working.

• Learn product metrics. Retention curves, conversion funnels, activation. Read one good product article a day for a month and you will speak the language.
• Study how real product teams work. Design blogs from strong product companies describe process problem-first, never "we made this cool UI."
• Run one usability test. Fifteen minutes, one friend, your best design. Watching someone struggle with your work rewires how you design.
• Know the difference between UI, UX, and product design. How it looks, how it works, and why it should exist at all. The third one is the job you are moving toward.

The outreach formula:

1. Find a designer or design lead at a company you want, on whatever network your industry uses.
2. Reference something specific from their recent work.
3. Ask for a 15-minute conversation, not a job. "Can I have fifteen minutes?" gets replies. "Do you have openings?" gets ignored.
4. Attach your best product-framed case study.

Do speculative work. Find a real problem in their product, redesign the flow, write it up, send it to the design lead. Nothing signals product thinking like unprompted product thinking.

Use your university and alumni network. A warm introduction is worth ten cold messages.

1. Pick your two strongest agency projects and rewrite them as product case studies this week.
2. Read one product article a day for the next 30 days.
3. Build a target list of ten companies, local and remote.
4. Run one usability test on your best design.
5. Send three outreach messages this week, asking for conversations.
6. Set a 90-day goal. Three months is enough to reframe the portfolio, build one deep case study, and have a dozen real conversations.

Agency to product is not a career change. It is a perspective upgrade. Start this week.