Patrick Feger

I have this belief that every PM should have a hill they're willing to die on. They live at the intersection of business value and product experience. They have to have some vision for their product, which requires them to also be able to identify things that could hamstring it in the future.

2015: UX is when it takes few clicks, and the fewer the clicks the more UX it is

2025: UX is when a button labeled "✨ AI" slowly expands to cover the entire screen

I don't know who needs to hear this, but content still dictates form even in the era of design systems. Design systems should evolve based on new design patterns that come from new content + user needs to deliver a quality experience.

I always find it weird when designers say they're doing IA work when what they're actually doing is just determining the information and visual hierarchy of the elements on a single page. Am I alone in feeling like this isn't IA work?

Startup idea: an OOUX based project management system with anomaly detection for design orgs. "It looks like you're working on [object]. We've just notified 5 other designers because it impacts their work."

Recommendation engines are still in a funny state for items that are clearly one-time purchases. It's like "I see you bought a food processor, so here's 5 more food processors you might like" rather than presenting me with recs that are complimentary like a cook book, etc

The core skill I look for in a product designer is the ability to rapidly create disparate solutions to a problem. If you can do this then you can be coached on everything else.

Unpopular opinion: There are specific scenarios when small iterative releases are not worth the squeeze and it's counterproductive and not actually valuable. Sometimes larger, holistic releases make more sense. The mantra around small iterative releases is sometimes dogma.