Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Pins and Needles

Freshness Warning
This blog post is over 16 years old. It's possible that the information you read below isn't current and the links no longer work.

Vonage recently sent me an email asking me to update my account and create a PIN. They explain the new requirement...

Your PIN is a four-digit number that’s unique to you and should be easy for you to remember. Providing your PIN is a quick and easy way for us to validate you as the account holder any time you contact us.

It would seem that all the other identifiers on my account like my password or my credit card number are no longer enough. I need to create a new secret code that only I will forget know.

I can imagine the execs over there at Vonage planning this new security feature. To enhance security they’ll add this new secret code that’s the only way you can possibly access your account. But what if someone forgets their PIN? Vonage has you covered.

When you choose your PIN, you will also be asked to set up an account security question. In the event you forget your PIN, the correct answer to this question will help us validate that you are the appropriate account holder.

So my PIN is the only way into my account. Unless I forget it. Then my security question will let me in. Why do I need the PIN then? How about just using the security question?

COD
December 3, 2007 3:30 PM

Well duh! Then you'd need the pin number as a failsafe for when you forget the answer to your secret question!

Joost Schuur
December 3, 2007 5:25 PM

It's often easier to remember a few digits in a pin (most people probably pick a memorable number with sentimental attachment) than the exact spelling to a security answer. Favorite movie... best buddy at High School, even the exact spelling of your place of birth can be non obvious (the place I was born has a hyphen in it, which my bank doesn't support), or change over time.

This discussion has been closed.

Recently Written

Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.
Build the whole product (Oct 6)
Your code is only part of the product
Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.