Christine Pinto (@christinepinto) shared the following in This Week in Testing
Quality is speed and competitive advantage
How cool!
What “two words” come to mind for you?
Quality is <insert word 1> and <insert word 2>
Feel free to share more than one idea if you like. 
little abstract from my talk as context:
Quality is speed because it eliminates rework, reduces uncertainty, and builds the confidence to move fast without looking back.
And quality is your competitive advantage because in a world where AI accelerates everything, the only thing that compounds faster than features is failure.
Quality is how you scale trust at speed.
Quality is subjective and context-dependend.
Quality is care and everywhere.
Quality is care because quality naturally arises when people care about what they are building.
Quality is everywhere because it is a glue role.
Quality is ‘customer focused’ and ‘magic’ as people at large don’t see what/how we have done it when it is done well
Quality is ROI (not just for customers, but for product engineering teams too) and delighted stakeholders (not just delighted customers, but a delighted product engineering teams too)
Quality is “Love” and “Care”
Quality is what people love most and care about it, if not they hate n dont care about 
Quality is “Engineered” + “Conscious”
Quality is perceived and misunderstood.
It’s a value relationship someone has to something. I think bananas are gross, most people think they are nice. We do not share a quality perspective on bananas.
Once you have that concept down the rest of the way people sometimes talk about quality starts to be a little shaken sometimes. It becomes hard to make objective or measurable or comparable or even just one idea. It becomes different things to different users, not to mention different employees in different departments for different reasons.
I think the “make it good” simplicity found at the heart of a nicely simplified abstract version of quality leads people to base decisions about quality without considering for whom they’re making something. Quality to the majority of the user base, to users with disabilities, to the company and the product’s place in the market, all different ways to look at quality and generate different questions and different, valuable information. They’re never wrapped up in one idea or document or meeting, they’re about social norms, trends, demographics, support feedback.
There’s the word quality, the subjective valuation of something, then there’s whatever your company thinks whenever it’s said aloud.
Excellent, rapid feedback + superb, detailed discipline
Implementing Lean Software Development by Mary and Tom Poppendieck (2007, Chapter 8 Quality)
@simon_tomes
Quality is “Passion” and “Perfection”
Quality is “Stable product” and “context-driven” and “returning end users”
Sorry, I added z as well along with x and y.
When we use a product we look for it’s stability, how smoothly and easily we are able to use it. If we like the content, we keep navigating, tapping and look for more exciting features which keep us engaging. This level of satisfaction make us a returning user who love to visit the product(application) again and again.
Quality is necessary and mandatory
Quality is Awareness and Dedication
It takes a team to be aware of the lack of quality to do something about it.
Then it takes some dedication to actually do something about it 
Quality is Needs and Requirements.
Subjective and slippery