Just like "success," "quality" should be objective, not subjective; not having an objective definition of quality can create a disconnect with stakeholders and affect customer interactions. In this week's MMMM, Justin shares a quote from his good friend and mentor, Ed Kless, and offers insight to help your organization create a definition of quality.
Your candid opinions are appreciated. If you have feedback, drop us a line at firstname.lastname@example.org.
Transcription of Video:
Hey everybody, this is for the sixth Monday of 2018 and this is the next version of the Monday Morning Mobile Minute. Today I want to start off with a quote that comes to me by a dear friend and mentor of mine: Ed Kless. He will attribute it to somebody else but since I heard it from him, I'm going to attribute it to Ed. And the phrase is:
"Quality is conformance to a requirement, not a measure of goodness."
And this is ... it's come up a bunch in the last couple of weeks as we've talked about several different customer projects, and we realize that there's a disconnect often times, between what the business customer expects, what IT is expecting, what the developers and the architects are building into the solution. And often, what it comes down to is what that definition of quality really means to all of the stakeholders, and the only way we solve the communication gap is to actually define what we mean by quality.
So we can't just say that we're going to build a high-quality application with a high-quality user experience or user interface, or high-performance system on the back end. We have to define what quality really means, and we have to take something that seems subjective and turn it into something more objective. And I'm not suggesting that we should go crazy with trying to define every single possible area in the application so that it becomes burdensome. But what I am suggesting is that we all have a responsibility to define what success will look like from our vantage point and communicate in a way where we all understand what that objective really is. So that's the real thought for this week in terms of how we define quality. Quality is conformance to a requirement, not a measure of goodness. I think if we spent a little time thinking about that this week, we'll be able to build better systems and make sure that we're all on the same page in terms of our expectations. Thanks for spending a minute and we'll see you again next week.
Our team is always looking to connect with the business community. Do you have questions about Venado Technologies, the companies we serve, and how we can positively impact your business? Contact us - we'd love to connect with you! You're also welcome to call at 888.556.9761.
At Venado Technologies, our passion is helping customers solve important business problems by applying technology the right way. We believe that emerging technologies will continue to change the way work gets done. Venado Technologies helps business leaders and their most critical workers use technology in a way that makes their work easier, better, and safer.
Venado Technologies provides the brainpower and processes to ideate, create, run, and refresh digital experiences where mobile workers connect with the physical world. By bridging the divide between IT and line-of-business demands, Venado strikes a balance between the mobile worker experience and secure, reliable enterprise technology requirements to drive business outcomes.