![](\"https:\/\/osmeusapontamentos.com\/img\/0465051367.01._AA240_SCLZZZZZZZ_.jpg\")
Chapter 9 – Designing for pleasure<\/p>\nChapter 9 – Designing for pleasure<\/p>\n
– pag.127
\n“Designing for the elastic user gives the developer license to code as he pleases while paying lip service to ‘the user’. Real users are not elastic.”
\n– pag.129
\n“As a design tool, it is more important that a persona be precise than accurate. That is, it is nore important to define the persona in great and specific detail than the persona be the precisely correct one.”<\/p>\n
– pag.147
\n“If you want to design software-based products taht make people happy, you have to know who those people are with some precision. That is the role that personas play.”<\/p>\n
Chapter 10 – Designing for Power
\n– pag.149
\n“…the quality of design isn’t so much a matter of opinion and is much more amenable to systematic analysis. In other words, in the bright light of a user’s goal, we can learn quite directly what design would suit the purpose, regardless of anyone’s opinion or, for that matter, of aesthetic quality. ‘Good interaction design’ has meaning only in the context of a person using it for some purpose.”<\/p>\n
– pag.151
\n“The essence of good interaction design is to devise interactions that let users achieve their practical goods without violating their personal goals.”<\/p>\n
– pag.151
\n“Tasks are not goals. The goal is a steady thing. The tasks are transient. That is one reason why designing for tasks doesn’t alsways suit, but designing for goals always does.<\/p>\n
– pag.155
\ndesigning for vs providing for<\/p>\n
– pag.155
\n“People are willing to put effort into tasks because they feel it is a fair exchange between equals. In other words, users area willing to invest extra effort because they know they will get extra rewards for it.”<\/p>\n
– pag.156
\n“Personal goals are always true and operate to varying extents for everyone. Personal goals always take precedence over any other goals (…) Any system that violates personal goals will ultimately fail, regardless of how well it achieves other goals.”<\/p>\n
– pag.157
\n“… Hygienic factors (…) prerequisites for effective motivation but powerless to motivate by themselves”<\/p>\n
– pag.159
\n“…humans have special instincts that tell them how to behave around other sentient beings, and as soon as any object exhibits sufficient cognitive friction, those instincts kick in and we react as though we were interacting with another sentient human being”<\/p>\n
– pag.162
\n“What makes software polite:
\n(…) polite software is interested in me
\npolite software is deferential to me
\npolite software is fothcoming
\npolite software has common sense
\npolite software is antecipates my needs
\npolite software is responsive
\npolite software is taciturn about my personal problems
\npolite software is well informed
\npolite software is perceptive
\npolite software is self confident
\npolite software stays focused
\npolite software is fudgable
\npolite software is trustwhorthy”<\/p>\n
– pag.170
\n“Our software-based products irritate us becaus the aren’t polite, not because they lack features.”<\/p>\n","protected":false},"excerpt":{"rendered":"
Chapter 9 – Designing for pleasure – pag.127 “Designing for the elastic user gives the developer license to code as he pleases while paying lip service to ‘the user’. Real users are not elastic.” – pag.129 “As a design tool, it is more important that a persona be precise than accurate. That is, it is […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[32,56,363],"class_list":["post-477","post","type-post","status-publish","format-standard","hentry","category-ler-ver-ouvir-passear","tag-alan-cooper","tag-apontamentos","tag-ler"],"yoast_head":"\n