Teamwork & leadership:

• Learn to disagree and commit:

  You won’t agree with every decision your team makes. Healthy debate matters, but once a direction is chosen, committing to it helps you and your team move forward with agility. Don’t reopen decisions without new information. Constantly revisiting decisions kills momentum and morale.

• Strong opinions, loosely held:

  Use your intuition to reach a conclusion. Then, try to prove yourself wrong and always be open to people challenging your thinking.

• Psychological safety is foundational:

  Create a culture where people feel safe raising ideas, asking questions, and flagging concerns. Without psychological safety, teams can become dysfunctional, and important information stays hidden.

• Culture forms whether you design it or not:

  Every organization develops norms around how people communicate, make decisions, and treat one another. Shaping a healthy culture early is vital, because unhealthy patterns are much harder to change once they take root.

• Assume good intent:

  Collaboration gets much easier when disagreement starts from curiosity rather than judgment.

• Great leaders communicate concisely:

  Whether speaking or writing, they keep it clear, focused, and to the point.

• Documentation is part of the work:

  Conversations fade and memories diverge. Good documentation ensures team alignment and the sustainability of your operations, processes, and product.

Design & UX:

• Constraints increase the burden on value:

  The more friction, limitation, or effort an experience asks of users, the more compelling the value on the other side needs to be.

• Empowerment doesn’t always mean more choice:

  Giving users control can sometimes mean reducing options, clarifying defaults, and helping them focus on the decisions that actually matter.

• Respect existing mental models unless there’s a reason not to:

  Consistency and adherence to established conventions aren’t boring; they’re what let users apply mental models they already have. Breaking conventions can be worthwhile, but novelty should earn its complexity.

• Match fidelity to the question you’re trying to answer:

  Polished UI is useful when evaluating craft. It can be harmful when you’re still evaluating the idea itself. The artifact should help the team focus on the decision that needs to be made.

• Never make users stop and wonder what to do next:

  The best experiences answer the question before it’s asked.

• Design for people who are distracted and in a hurry:

  Most users won’t carefully study your interface or read every word. The experience should communicate through structure and familiarity. If education is necessary, integrate it naturally into the experience. People often understand better by doing rather than reading instructions.

• Treat your own presentations as a UX problem:

  When presenting design work, give people the right context, reveal complexity progressively, and design for how the work will be understood, not just how it will be shown.

• Not everything worth optimizing is easy to measure:

  A/B testing is powerful, but it naturally favors what can be quantified quickly, and can get teams bogged down on short-term gains. Trust, satisfaction, and long-term product quality deserve space alongside short-term metrics.

• The more senior the designer, the more important alignment becomes:

  As scope grows, design becomes less about producing the artifact and more about creating shared understanding across teams, navigating tradeoffs, and involving the right people at the right time.

• Clear ownership prevents design by committee:

  Collaboration works best when roles, responsibilities, and decision-making authority are understood. Input can be broad without ownership becoming ambiguous.

• Design starts with understanding the problem:

  Before solving anything, understand the people experiencing the problem, the context around it, and the underlying need. When a client comes to you with a solution in mind, keep asking why until you understand what they are actually trying to solve.