Skip to main content

Notary Publics

Did you know that some banks have a free notary public service? A few months ago, on a tip from a friend, I went to the Chase Bank branch a block away from my loft. They notarized my document for free.

This week, I went back to the same Chase Bank branch to get another document notarized. The manager stopped to ask me if I was a Chase customer. I told him no, I don't have a Chase bank account. He then told me that the notary services were for Chase customers only and suggested I go to my bank.

Fair enough. My Bank of America branch is just three blocks away, so I went there. They did the notarizing, and I bumped into a friend who is a teller there.

I wonder whether Chase's policy of only performing notary services for customers is wise. I would never have bothered to set foot in their lobby had I not heard about the notary service. Familiarizing myself with their branch made it more likely that I would eventually become a Chase customer. But being turned away has left me with a bad taste in mouth.

Comments

Mike Lunt said…
I like the marketing angle, but this seems like a stretch. I think only a small bit of research would suggest that (a) people don't choose banks based on free notary service, and (b) people don't choose banks based on visits to a branch.

p.s. It's too bad that people are required to get a blogger account to make comments. This surely decreases feedback to the blog.
Roger L. Cauvin said…
It's an interesting question: "On what basis do I choose my bank?" How you or I answer this question may differ from how other people answer it.

While I doubt notary public service per se factors into just about anyone's decision, perhaps familiarity, comfort level, and perception of convenience do.

Sorry about the requirement to get a blogger account. Comment spam has become a significant problem for blogs; anonymous comments unfortunately would aggravate the problem.
Unknown said…
True...But how often does the average customer need a notary service? perhaps once, maybe twice a year. I doubt the few number of visits would bring about a change in banking services.
Roger L. Cauvin said…
On the other hand, how often do customers actually visit their banks these days? An on-site visit represents a commitment from which many banks could benefit.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the