top of page
Talk Bubble black outline.png

​

"Damian gave a presentation, "The Hidden Requirements: Exploring Emotions with Placebos", which was different from any I had heard all day. It spoke to the softer skills and fundamental concepts that are below all the process, tool, project, and business issues related to this industry/any industry. It was inclusive of the social and emotional aspects of why we are creating technology in the first place. It was a breath of fresh air! Some items in these slides really spoke to me on both a professional and personal level."

-Julie Duffy, 2018 QA or the highway conference

​

Talk Bubble black outline.png

​

"As a developer this talk helped give me a better perspective on a users perception of software and how emotions have an important impact on all aspects of software design and requirements."

-Anonymous, 2018 Codemash conference

​

The Hidden Requirements

​

Summary

"Exploring Emotions with Placebos" - Support and actionable advice for the claim "the way we feel is important and should be considered".

​

Abstract

Traditionally, products and services are designed and built according to various functional and non-functional requirements - things that the product or service should be or do. While this is important, there has been a lack of focus on emotional requirements - feelings that the product or service should induce in a user. Why are these "hidden" emotional requirements important?

 

Because the way we *feel* is important and should be considered!

 

In this talk, I support this bold claim with evidence by providing relevant facts, opinions, research, quotations, examples, hypotheticals, and more.  Then, after supporting the claim, I'll offer a few practical methods by which to collect, create, and check emotional requirements. Finally, I use placebos as lens to view products and services and gain insight into emotional requirements.


Join me for a thoughtful and thorough exploration of The Hidden Requirements!

​​

Note

The portion on Placebos can be removed based on time/interest.

​

Audience

Anyone involved in making a product or service.

​

Duration

~1 hour (as a keynote or breakout session), 2-8 hours (as an interactive workshop)

​

Key Takeaways

  • Why we make a product or service

  • What are emotional requirements

  • Ways to get, make, and measure emotional requirements

​​

Media

​

 

Website by ...me!

​

bottom of page