Are you required to change the password of your most frequently visited website once every two weeks and you end up changing it from T1mesSqu@re (your favorite password) to T2mesSqu@re to T3mesSqu@re and so on and by the end of the 8th week you are frustrated because you don’t remember which website is on which number?
How about a system which works something like the SecureID’s two factor authentication (http://en.wikipedia.org/wiki/SecurID) where one part of the authentication is what the user chooses and remembers and the other part is changing.
Let me explain with an example
I am creating an account on http://www.blabla.com. I will be required to choose a password “T_ _mesSqu@re”. Also I will be choosing a method that will define what the two blanks will be. Options for a method can be
Sum of DDMMYY up to 2 digits (date can be current date, anniversary date, birth date etc.)
Multiplication of date and month and adding the digits to get a 2 digit number
.. anything really that is changing (sum of the digits of the current population of India? 😉
So if I am logging onto blabla.com today (02/08/13), my password (with DDMMYY sum method) will be T14mesSqu@re (Sum is 14). While setting the password we could also have set it like T_mesSqu_@re, in which case the password now will be T1mesSqu4@re.
So now we have a password where even if the one to remember part is compromised, the digits calculated with the method will make sure the total password is still safe (safer?).
Will be happy to get some feedback on the same, or if you have seen anything similar?
After wearing different kinds of Application/ Technical/ Customer support hats in my last three organizations spanning 8 years, I realized I should write about some best practices that are my experiences in this world. They are easy to understand and implement. They have helped me and my teams in dealing with some of the toughest / craziest customers in the industry – both internal and external to the organization. Time is money so I will keep it short and precise. Most of my experience is from the extremely fast paced Investment banking / Finance domain but all of this should hold true for any other domain / sector.
You should know about a problem before your customers do. Create a list of known problems and “workarounds” that you can give to your customer when they hit the issue and call you for help. For bigger / important / known issues, you should let the customers know in advance. This also means you need to have effective monitoring/alerting systems in place so that your alerts tell you about a situation (e.g. file storage space full, user account on a shared location locked on 3 wrong password attempts) before your customers get to know about it.
Be empathetic and reasonably apologetic. Customers are paying for your product/ services and they hate late/ impersonal replies (even more in the Financial World but really everywhere). Every minute of delay might result in financial/ reputational loss for your customer. It’s obviously not easy to manage expectations but being silent never never never helps. They would like to know they are being attended to and someone in on their case. That gives them assurance and gives you some time to breathe, think and work on their case without being hammered by stinker emails. When something goes wrong, apologize and say sorry. It’s easy and customers like it. The customer may not always be right, but the customer must always win. In most cases talking to your customer on phone helps. Written communication is just 7% of the total communication while vocal tones add 38% to it.
Make sure you repeat your understanding of the problem to the customer (on email and / or phone) and get the customer to confirm that. You do not want to spend days on a problem only to realize you were solving the wrong one. Most of the times, your language will be different from the customers. You are the expert, so it’s your responsibility to speak in a language that your customer understands. You cannot expect the reverse! Do not make any assumptions and be a good listener concentrating on the tone of voice, words and importantly how they feel. You will learn a lot about actual pain point for the customer.
I remember dealing with a customer from Brazil in my first job with IBM.
Me: “Now that your computer has started, can you see ‘Windows’?”
Customer: “I am sitting next to a window and its beautiful outside”.