This post was inspired by two comments I read online. The comments were left under a video related to the recent problem present on the latest release of the Kindle Color Soft. Thousands of customers have been reporting a strange yellow discoloration on the screen of their new devices, so I headed to Youtube to check if anyone had reported these findings in any product reviews or unboxing videos. The entire first page of search results made some mention of this yellow band defect and the first comment that struck me was "How did they get this through QA?" and under another video review a comment read "Yeah, that's why I never buy products when they first release."
The comments above made me reflect upon the current state of products and software in the marketplace. It seems to me that companies are not too bothered about releasing their products into the market without addressing problems that are often so apparent, customers like myself wonder how they ever got the green light for release in the first place. Unfortunately for customers, things have been this way for a while.
The first case of botched first releases I thought of was the infamous 'Bendgate' incident following the release iPhone 6 and 6 Plus release in 2014. Customers at the time were reporting that the phone was bending under pressure - sadly for Apple, the skinny jean fashion trend was in full force, which meant skin-tight 'pressure' around the pocket region where the phone would be kept. iPhones bent, so your legs didn't have to (not that they could in those jeans any way). After investigation, in September 2018 it was revealed that Apple knew about the structural flaw in the device all along.
Skipping forward to 2016, Samsung released the Note 7. By the end of that same year they recalling all devices after reports of batteries in the devices overheating and even exploding. Not only was this a huge safety concern for customers, the recall itself also cost the business a reported $5.3 billion! As well as being hugely damaging their reputation.
And what about software? I've been so kind as to spare you, the reader, of having to read through a long list of all the computer games and upgrades in the past few years that have been released with countless bugs in them, requiring many companies to make public apologies and even pay out refunds. To add, I've also excluded the numerous problems I, and others have reported (and keep finding!) when attempting to perform basic tasks in the day-to-day applications.
So here we are approaching 2025 and it seems we haven't moved forward much, which brings me to the recent Kindle Color Soft. Released on the 30th October it was a promising move for Amazon. There are very few companies that have released color e-ink reading devices and I must say, as an avid reader they have done great things in pushing the technology and market forward. Customers were now waiting in anticipation for their Kindle devices to arrive - finally, everything we love about Kindles (simple UI, great library, usability etc) would now have color?! Count me in..
Let's just ignore the price of the device for now, that can be argued at another time - or perhaps in the comments? .. When the Kindle Color Soft was first announced, I already knew that I would not get the first batch of the release. The tester in me said let's observe some behaviour and outcomes and time box it at 4 days tops, if all was good I'd go purchase. Why did I have this approach? Subconsciously I expected some problems in the initial release - and just totally accepted it as normal. And it appears it has indeed become the norm!
Customers that were brave enough (or just, expecting a working product as normal) to purchase, started reporting a problem with their new devices. A yellow band at the bottom of the reader - and within a few days customers had shared their updates on Youtube, Reddit and other forums mentioning that the customer service teams had instructed them to send them back and they'd immediately get a replacement sent out to them once fixed and back in stock, or a refund transferred.
I then went to the Amazon product page for the Kindle colorsoft, only to find that yes, you still can buy it but don't expect to receive it for another 3-6 months?! (now in the UK that time has reduced to 6-8 weeks)
Was this issue captured in QA/testing? Was the product under test at any point at all?
I Googled 'Does Kindle have a QA department?' - the results were old job Vacancies for QA Engineer and QA manager roles. So we'll assume in this case that they do.
On that basis, I will assume my fellow testers did indeed capture such an obvious flaw, which opens the door to other questions like:
Do these QA Engineers actually test? or are they expected to be 'Quality Coaches', 'QA Motivators', 'QA Coordinators' etc, the list goes on - basically focusing so much on quality (an endless path) that no actual testing gets done.
Or perhaps these issues were indeed reported, but not communicated effectively? Or they were communicated effectively but to a Manager that was up against some tight deadlines that viewed testing as the final chunk of development, with no problem at all slicing that chunk smaller and smaller if development/coding takes a little longer.
There are so many layers to problems that are found in products but a few things are for certain, according to me:
1. Customers are increasingly accepting the fact that first releases of products are going to be bug-ridden, what this means for businesses is, you actually might have a great product but due to lack of care for customers, your product will be affected by this and may even see lower volumes of sales for your first release, until at least the good reviews start coming in.
2. The doors of criticism for your product are many and they hold a lot of weight. Product reviews really matter - and nowadays they come with pictures attached or even video reviews containing evidence of their claims too so as to dispel any doubts about the customers' critique. As of this afternoon 11th Nov 2024, the Kindle Color Soft is rated 2.4 out of 5 stars, with 131 ratings.
Pay attention to product reviews. If you are a tester or a QA professional, treat it as test data.
3. Businesses need to listen to their testers. Go ahead and hire a Quality Coach, Quality Engineer, Quality Assurance team - they can do great things in teams and facilitate some great discussions but one thing is for sure and that is, you need somebody on your team, skilled enough, actively looking for problems in your product and you want to know what those problems are before the customers and market do.
4. There is an environmental concern around product releases and that is, where will these thousands, if not millions of product recalls end up? Recycled we hope. Not stuck in the teeth of some poor whale in the ocean.
5. As customers we should simply not expect this and in fact, I have vowed to make a conscience effort in actually purchasing the next product I want upon it's initial release. And if riddled with obvious, apparent, easily found bugs or defects - I will be publicly reviewing /even blogging about this as I think this could be a means of change - though a tiny spec in the grand scheme of things. We should keep our expectations high and not simply expect things to be faulty upon first release.
PS. This was part random rant, part random thought dump. Thank you for taking your time to read.
Meanwhile if you have an e-reader to recommend, I am indeed hoping to buy one - birthday is fast approaching people! *nudge *nudge *wink *wink