After reading Hooked by Nir Eyal, which I highly recommend, I really began to think about the difference between a habit-forming application and an addiction. Eyal brings the topic up in his book,
Working in a big company can make me feel like I am a lone designer. That isn’t to say that I am the only designer or that I have no design support. Rather, I get put into the situation a lot where, because I am embedded on my sprint teams, I have a specific set of work I need to get done in a given period of time. When paired with everyone else...
If it was a trade off between designing for purpose or designing for simplicity, what would you choose? It is a hard question because there are many other variables that come into play, including timeline, requirements, and what type of project this is. So the real answer is
So what’s better, designing with or without data? Most, if not all, designers will tell you that designing with data is always better, and it would be wrong to tell you otherwise. So where does that leave designing without data?