christine

If you are getting bogged down in platform-level information architecture, consider drawing the site map, finding page orphans (everything at top level), and redrawing with a structural schema (top level categories + subcategories).

Design in context!!!!!!! You may have a good product feature but if the entry point or location does not naturally fit with the user's workflow/where the user is coming from/user's emotional space, then it might be overlooked or dismissed

When talking with stakeholders/partners, it is helpful to ask about emotions. What emotional state is the user in? What emotions do we want to evoke? Oftentimes product partners just forget about this part, so as design we bring this to the table

Designing for user trust: does your user feels respected? informed? safe? empowered? are you being transparent and accurately setting up their expectations?

I try to have a mental model or metaphor for my designs. It does a lot for getting people on the same page, clarifying which elements belong and which don't, and generally helps your design "make sense".

when critiquing a page: ask yourself, what is the story being told as the user moves down the page?

Consider 3 kinds of responses: visceral, behavioral, and reflective. Which are you designing for? Are you aiming for a fleeting moment of joy? trying to get user to buy something? To adopt a new value or sense of identity? I find this terminology helpful when discussing designs

Inclusivity & Accessibility: Don't just ask "How might we" also ask "For who might we". Clear heading hierarchy makes for easier tabbing for keyboard users. Try to left align & keep related elements close together for people who zoom in 400%.