Skip to main content

Free Nexus 5 from Google

I had broken my Samsung Galaxy S2 on my European trip. So as soon as I got back home I started to look for a new phone. I decided that I would just invest in an expensive smart phone and be ultra careful with it (I am not the type of person to care much about the protection of phones....or sun glasses)

I purchased a Nexus 5 from the Google play store. About 5 minutes latter I found an old HTC in my drawer and decided that I needed the cash I used to buy the phone. So I cancelled the order.  About a week after that, I received a package at work. It was the Nexus 5.

At first I was confused. I thought I canceled the order. So I checked the Google play store and my credit card statements. All seemed to confirm that I didn't pay for the phone.

I then gave Google a call and they apologised for any inconvenience caused. The customer care representative on the other line advised me that I have two options. Firstly, I can send it back and receive $25 credit. Or, keep the phone. I obviously took the latter.

What got me thinking afterwards though was the level of customer care that Google has. This standard is what all companies should be aspiring to achieve. On the phone, the Google representative did three key things.

1. Acknowledged an "error" on the side of Google explicitly. That is, he used the word "error".
2. Apologised on behalf of the company.
3. Provided ways to rectify the error.

This is the customer-centric mentality that creates great companies for employees and customers!


Popular posts from this blog

from zero to production in eighty days

When I mean zero, I literally mean zero. A brand new project, a PO that's new to IT, no existing processes in place and a small team of four including myself and the PO.

The departmental organisation we were working for doesn't have any developers, scrum masters, product owners working for them. Everything they did was either done by another department or outsourced completely.

This is a story how we went from zero to production in eighty days.

My first time speaking at a conference

Since time immemorial we humans have valued the art of public speaking. Today, I want to share with you my experiences in speaking at conferences for the first time. Recently, I spoke at both DDD Melbourne and DDD Perth. Both of which were positive experiences that I learnt a lot in.

Have You Ever Produced Negative Value in a System!?

As developers we encourage our product owners to order the priority of their backlog in order of value. However, every time a new feature is implemented by a development team, there is a certain degree of risk associated with the introduction of that new code. Namely, risk of breaking another part of the product and maintenance cost. When a development team pulls in a new feature to implement there is a certain acceptance of this risk. In many cases, the risks that arise due to additional code complexity doesn't justify the value added by the new feature itself, so the development team can start implementing it.

Are there scenarios where the value added to a software product can be negative though?