Principles
With each project that I work on, I apply these principles
Embrace Complexity
Fast doesn't always mean better. While we often measure an experience by the amount of clicks and or visual complexity, oversimplifying can end up frustrating users who need advanced features to work efficiently. Design for the complexity your users actually need, not an arbitrary standard of simplicity.
Talk to the right people
I don't design in a vacuum. Product teams have ideas about what users need, and these ideas are good starting points. But the people who use the product every day see things others miss. They know what wastes their time, what actually helps, and what would make their jobs easier. When teams talk directly to users, everyone learns something new. The best designs happen when we combine what teams know about the business with what users know about their daily work.
Developers need better experiences too
We often forget that developers are users too. The tools, systems, and processes they interact with shape the final product just as much as our user-facing designs. When we make their work frustrating or inefficient, it shows up in what we ship. Good design extends to everyone who touches the product.