…sent the interface for a feature. This process is a mistake designers should avoid like the plague. Before we start thinking about how to design for user stories, we should try analyzing the stories and point assumptions made while these were documented.
It is important to have design opinions over political opinions. For example, instead of “I think the engineering needs to work a little more to get this sorted”, think “This user-flow makes for a better experience and we should think about how to ship this ideal flow.”
Look at interviews as a conversation for fit. I stopped using the word ‘interview’ in my own mental language. I’d book it on my calendar as, “Conversation with Lyft”. It allowed me to be calmer, and stop worrying about if they’d like me, for no other reason then to not fail.
…o come to you with some specific problem to solve. The path to getting out of being a service is to have an opinion about which problems are worth solving and convincing other people of that. I remember a specific conversation with my boss where I was voicing a similar complaint to him arou…
…rs, emphasizing an arbitrary quality bar that appeals to many but fulfills the needs of only a few. These design leaders know they can’t simply be data-driven, but instead they must be data-informed and make decisions from data that’s paired with empathy and diverse perspectives. They know that data can’t empathize or feel.