Design Thinking (DT) is a human-centered approach used in innovative problem-solving. In software development projects, it can be usually applied as a toolbox, mindset or process. Moreover, DT has seen a large rise in popularity over the past decade, especially in its upfront use for eliciting requirements. Despite its many benefits and successful use cases in this scenario, some of the shortcomings related to its uses in Requirements Engineering (RE) have started to show up. One of them lies in the difficulty with eliciting other non-functional requirements (NFR) – besides usability –, possibly jeopardizing the subsequent software development life-cycle if these requirements are not properly addressed. This article presents a qualitative survey conducted via LinkedIn with 53 software developers that have had previous experiences with the use of DT as an upfront process in software projects. The focus of the research has been on identifying the existence of problems, how they became manifest, and whether the software community has tools for mitigating them. The results suggest the neglect of DT for requirements other than those of a functional or usability nature in this situation. Since this use of DT is focused on improving the users’ experience, and identifying their needs, we argue that such needs are not limited only to the functions of a software or its usability. In fact, we also advocate that other aspects that are intrinsic to NFR, such as performance and reliability are part of such needs.