We all need each other in product development; each mindset—design, engineering, product management—brings unique value that cannot be replaced. I believe design should report to engineering because it allows design to be considered phase zero of the engineering process, ensuring that what ships at the end is well-integrated and technically feasible.

Design is fundamentally a problem-solving methodology; the more clarity you provide upfront, the more efficient the design process will be.

Designing things twice can lead to better outcomes, as the first idea is often not the best; forcing oneself to think of alternatives can yield superior solutions.

Inviting customers to design the product can lead to better outcomes, as they often have valuable insights and skills that can enhance the final product.

The two main approaches to software design are top-down and bottom-up, each with its own advantages and pitfalls, and effective design often involves a combination of both.

Design can significantly impact a company's success, and it’s essential to fight for good design in a competitive market.

Learning by doing is essential; producing designs, even bad ones, helps you understand what works and what doesn't.

Everything you build should solve a problem for someone; this is the core of design thinking, where you identify problems, research solutions, and validate your ideas.

Design is about creating things for users that work well and delight them.