When it comes to reporting the status of our testing projects, we usually believe in fact-based analysis of the available raw data aka data-driven decision-making. It may seem obvious that cold, hard numbers are simply the best and most reliable way to make important decisions during the famous go/no go meetings. But aren't we fooling ourselves by believing that data-driven decisions are objective and unbiased? This question becomes even more relevant because testing must address value assurance in addition to quality assurance and quality control. Where value has many aspects, it requires a kind of subjectivity to assess and evaluate whether the software or product meets the value expectations of the end user. Therefore, I would argue for subjective reporting (also called intuition-based reporting). This kind of reporting conveys information based on personal opinions, interpretations, assumptions or beliefs. It certainly has its merits if you use it in the right way and form. Moreover, it is definitely a step forward towards better understanding and communicating with our stakeholders about the status of our projects. I will show some concrete examples of subjective report layouts that you can use for your own projects.