Dear Google, I Have More Than 10,000 Contacts
feld.com
feld.com
Really, this is one of those non-apology apologies that is infuriating to people with completely reasonable expectations. What is this nonsense of asking the user to formally request a feature? They just did request a feature! If it needs to go into a system, the support person should do that for them.
A better approach: actually apologize, give your explanation (or excuse), give a timeline for a solution if possible.
Abbreviated example for this situation: "Very sorry, we understand why this has caused confusion and problems… We set arbitrary limits to prevent outright abuse, and made a mistake by not having a function to override in special cases such as yours… I've forwarded your issue to our engineering dept., and I will personally inform you when we've solved your problem." Is that really so hard?
Dear <customer>,
Unfortunately, we don't allow <feature requested>. If you'd like to see us do <feature requested> in the future, please follow these instructions to request it...
Imagine the number of people who try to test the limits of Google's software. I'm sure they get thousands of issues every day with people who have intentionally tried to hit the limits on size of inbox, number of emails, length of search term, etc.
Deleted comment
That said, they do take FRs seriously, and they are incredibly (astonishingly) open about their roadmaps... depending who you are.
I am curious what one does with 10,000 contacts, though…
Bad idea, bad response.
1981: Dear user, You cannot have more than 10,000 records. Our software vendor set this limit and we don't have the source code. Sorry, IT.
1991: Dear user, You cannot have more than 10,000 records. We don't have enough room in our budget for more hard disk. Sorry, IT.
2001: Dear user, You cannot have more than 10,000 records. Our network traffic is so high that we had to set arbitrary limits. Sorry, IT.
2011: Dear user, You cannot have more than 10,000 records. The internet is full. Sorry, Google.
[EDIT: Replaced "contacts" with "records" 5 times. The general case causes less confusion. Thank you, juiceandjuice.]
In real physical rolodex you can understand the limit, because it really exists. In Gmail it's hardcoded "OK <= 10000" and that's hard to understand, specially when there's upgrade for 20,000 contacts - so 10,000 is just an artificial dumb rule.
In this case, allowing 20,000+ contacts does not reduce anything for the rest of their user base; it only positively impact some heavy (and presumably loyal) users of their system, which nets in total increased satisfaction.
If the goal is to maximize overall total satisfaction, Google should engineer their system to support maximally conceivable number of contacts.
This is oversimplification. Knowing google, they would want to track different users' contacts and mutual contacts, and email frequencies habits etc. Contact size, is larger than O(N) complexity.
Yes, but the graph is very very sparse.
Edit: See http://www.google.com/support/a/bin/answer.py?hl=en&answ... I don't think user profiles (that would be what is used for employees inside an organization) and shared contacts have a 10k limitation, only the user personal contacts have it.
Instead you decide to be a jerk.
What are you gonna do, spend five weeks calling the first 4,000 people? Send 2,500 text messages? CC 8,000 users on your annual Christmas Greeting e-mail? How the hell would you even begin to sort through that many contacts using a cell phone or a standard e-mail client?
It's Google. This company serves the general public and doesn't have the resources to tailor its service to every asshole (or Executive) with unrealistic expectations. Next time somebody asks for more than 10,000 contacts they should just flip him the bird.
For this community however I would agree there is always a tension between the 80 - 90% solution and the outliers. If you have more business than you can handle, supporting outliers seems like a waste of resources, the problem comes when someone decides to support those outliers and builds a system that can handle your customer base as well. That gives them the high ground competitively.
From Google's perspective I suspect its not like they get enough revenue from this whole Apps business to make it worth their while, it seems to be more of a way to poke MS than a product. (But disclaimer time I use Google's app)
I haven't worked in a Congressional office, but if you're keeping track of constituent corespondents with Exchange contacts associated with individual users, your system is going to break down well before 10,000 users.
A quick google says Google Apps started around feb 2006. Let's assume the user was an early adopter, and today is mar 2011. 10000 contacts / (365 * 5 years) ~= 5 to 6 new contacts a day. Seems possible; maybe in a weekend the user will have 20 new contacts and quiet the entire week... the # of contacts collected throughout the lifetime of an inbox doesn't say anything about the need to send message to all of the contacts.
Nobody can or will maintain relationships with anywhere near 10k contacts. Dunbar indicated that humans are only capable of maintaining relationships with roughly 150 people at any given point in time. This guy is overstating his requirements by nearly two orders of magnitude.
Brad Feld is not just a VC, but is co-founder of TechStars. TechStars is kind of like YCombinator, except instead of just trying to find a handful of a super specific kind of company, they're growing a network far and wide of incubators across the entire U.S. They have programs in Boulder, New York, Boston, Seattle, and are growing even further through their "TechStars Network".
I met Brad briefly on their book tour. He's very much an "I'll look you in the eye and listen to who you are and what you're doing, and see how I can help" kind of guy. Unlike YCombinator, TechStars pledges to try and help out EVERY company who applies, with advice or connections or whatever they can do, even though they can only accept a few into their program. I'm sure he's connected former applicants to TechStars (not even accepted companies, applicants) with strategic partners he meets on the road. I'm sure he makes all kinds of crazy connections between contacts. In some sense, running an incubator and being a VC.... making connections like that is his JOB.
Brad doesn't have my contact info, but if I gave him my card and he ever contacted me, or gave my info to someone else, it would be the OPPOSITE of spam. I would be stoked to see anything in my inbox from him or someone in his network. Brad is really a "water that raises all boats" kind of person, from what I've seen.
It seems to me this is why there are (for example) sales tools which help track relationships and organize aggregate contact data into a manageable system. But come on. However much of a VC rockstar Brad Feld is, he's not e-mailing or calling 10,000 people. Like most people he'll add everyone he meets to his standard contacts list, but this is not scalable, and there's probably a couple thousand people sitting in the list that either he's never had correspondence with or hasn't for a year or more, making a follow-up unlikely. Of course I am generalizing and assuming based on my own experience with PIM systems.
Instead of just adding people to a contact list and forgetting about it perhaps Brad should invest his time in a system which will provide more features tailored to the nature of his business contacts, and that way Google doesn't have to redesign its infrastructure to support 0.001% of users. That's all i'm saying.
I run into things like this when we consolidate email systems. Its always a battle.
Weird corner cases like the guy who has 50,000 folders in his inbox, cross referenced with multiple copies of messages in folders. Then you have the guy with 75,000 objects in his Inbox. Or the one with 120 GB of email dating back 20 (!) years who must have all mail on an online mailbox and cannot use archiving.
At the end of the day, supporting the bizarro corner cases can impact your ability to support the other 99% of the users.
To make it worse, in most cases, you are just on the receiving end of a power trip or attention whoring episode anyway. So, if these people are peons, you tell them to piss off. If they are bigshots, you waste money dealing with their whims.
* Review the original intent with the 10,000 limitation. Was it a precautionary measure that turned out to either be justified or incorrect? Was it a technical limitation that has since gone away with DB, browser or bandwidth improvements?
* Ask the customer about their usage patterns. Can they be served with an alternate, existing product (LDAP, mailing lists, Google Docs spreadsheets)?
* Run some stats on a sample user base and project what percentage of other users will hit this limit at what point.
* Is there an opportunity to develop a new product, not for this user in particular, but something that uses contacts in a different way for those users who have a legitimate need for this many 'contacts' (large mailing list support within Gmail)?
* Start logging the number of users with this complaint internally, so that demand can be measured even if the user doesn't file a feature request.
Regardless of whether you personally think someone can maintain 10,000 relationships (they certainly can't), you can always learn from the unexpected ways other people use your product, and figure out a way to either improve it or create a separate product that can interact with it.
I literally don't know anyone who has 10000 contacts, I also don't know anyone who actually needs 10000 contacts.
My "My Contacts" list is more than 500 people after using Gmail since September 2006, and my "Other Contacts" is more than 1100 people. So if I had work that involved even more email interchange than the work I have, I could easily get to that 10,000 limit. And if a person makes a lot of use of email, that is precisely the person who will comparison-shop for different email solutions.
I'm sure in 5+ years I may get to this point, but in a year or 2 or 5, who says what this arbitrary upper limit is. Google seems to increase capacity on just about everything else, I dont see why this would be different.
There's things like contacts for every Debian and CPAN bug I've ever filed, contacts for people who change their E-Mail address every day due to using some wildcard catch + script to generate them etc.
The thing is that people don't know ahead of time which contacts they need. They just put everyone they meet in their contacts. Then if someone says, "Hey, do you know so-and-so?" they can actually email or call that person right away.
I remember the halcyon days of the dot com era when hot redheaded sales reps from Exodus would take you on datacenter tours and treat you to dinner to secure a lucrative two-rack deal.
I remember pushy but friendly Oracle salespeople selling you on a $250k six-processor O7 license predicated on "well ebay's using it".
Nowadays I refuse to take vendor phone calls. If I need a solution, I google it or ask around my circle of tech friends.
The claim that sales is "valuable" is lost on me at this point.
I know a girl who works for a company that sells Expensive Things to a Big Lumber Company. Her full time job is to be fun to be around. Every weekend you'll find her and a few random BigCo executives (or formen depending on the weekend) riding jetskis, snowboarding or just buying rounds of tequila at the Mexican restaurant. Her office is at the BigCo plant.
It still happens in tech too. Drive past the Microsoft campus next time you're in Redmond. Notice how Intel has an office building next door?
Besides, most modern CRM/ERM systems interact with e-mail (where you bcc the CRM system to add data to it). So adding a CRM system only exacerbates the problem.
Ancient email is often important to establish the context surrounding decisions that have multi-year impact.
Also, many folks use email as an ad hoc general filing system. They rely on search to find information, and email is often the ONLY system available with reasonable search ability.
If you're in a small company, this will sound insane. But in a mega-sized org like the one I work in, its essential.
Deleted comment
1 User who says they are willing to pay is significantly different then a company who is paying for 50k employees.
The personal contacts is another thing. So having 10k or more employees isn't a problem for google apps, what is a problem is employees who have more than 10k personal contacts (not very common).
I am shocked that the "expert" was wrong.
Google is known to based their decisions on actual data, they probably noticed that most people were below eg 500 contacts and 99.9% below 9000 (or such) and decided that 10000 would be safe.
aka, an arbitrary limit, rather than a specific technical limit.
Both of these seem like odd decisions. The people using more than your data driven limit are likely power users -- who are also probably your best evangelists.
Furthermore, given that so few are using beyond the limit, unless there is a technical reason to set the data driven limit, you incur virtually no cost to keep the limit high. In fact it argues that increasing it to unheard of numbers, ala gmail back in the day, makes more sense.
Again, there may be some technical reason they did this, which is fine. But if they looked at their data and saw that only 1% of their users had more than 10000 contacts, then they deserve to lose all those customers, plus the full wrath and bitterness they have as a result. They made a calculated decision to explicitly screw you over.
Side note: Gmail offers a "Most Contacted" feature to show you who you email the most. It might be interesting if they had a "Least Contacted" feature as well, to be able to easily remove contacts you never use.
Also, 10k contacts is properly far more than most people would ever have so it is not a big deal.
99,999% of their users will never see the story. And the rest of us will have forgotten about it before the end of the week.
The limitation is there for performance reasons. Besides why is your sales guy is using gmail as his crm?
You need a CRM tool. Have you looked into SalesForce? It's online, just like Google Apps.
I guess both Google and 37signals do it because it's just a quick and dirty way to manage resources. There maybe be other reasons that we're not aware of though (e.g. people using more than that number of contacts might frequently be using the app for nefarious purposes?).
It's a shame because limitations like these ultimately place limits on your creativity. In the case of Highrise for example, I once had an idea to use it to manage and track communications for all of my applications users, but obviously that doesn't work if there are hard limits there.
Not sure I have a moral to my little story, except that arbitrary limits are understandable, but frustrating and unfortunate.
"Oh, you need more than 10,000 contacts? Well, why don't you just find a creative solution to the problem instead. Creativity comes from limits!"
Trust me, I'm sure this guy will find a creative solution to his problem, just as I ended up finding a creative solution to my own problem.
But I'd be extremely wary as a developer of presuming to know more about your customer's problem space than they do, and that all they need is a little dash of creative thinking to get around whatever limitation your software may have presented them with.
> It's a shame because limitations like these ultimately place limits on your creativity.
I understand what you mean, but this statement still bothers me. Needing more than 10,000 contacts may be a requirement for many reasons, but creativity does not seem like one of them to me.
EDIT: It's worth noting that loading near the 10k limit into your Google Contacts kills your browser. The current UI setup is probably one of the issues with having over 10k contacts.
No indication that they're paying for anything, just whining about the limits of a free contact system.
ETA: Fair enough, he does have some sort of enterprise support.
Mind you, this post sure has a lot of search-baiting links (like every single instance of the string "Google Apps", even in quoted blocks) pointed at other blog entries.
Dude, enjoy your 10K contact limit and your plummeting search ranking.
Smart developers crave this kind of feedback, so that they can figure out where their assumptions about user behavior are wrong and work to correct them.
This guy doesn't need 10k contacts--he just doesn't want to go through and remove the non-essentials.
So yeah, just use another enterprise app instead. You don't really have much choice.
I know people are saying stuff like this doesn't matter, but I manage at least 15 domains on GDomains now, and I will probably hesitate a bit before adding another. Can I trust Google Domains to grow as my business does? I can't believe you can't pay for more space..
When you have 10,000 employees, you could probably just get a team to author their own version of gmail.
10k works out to be 40 new contacts per business day( 5 days per week, 52 weeks minus 2 for vacation ) for a year. Let's assume this guy has been "at it" for 4 years. That's still 10 new contacts every day.
Nobody who has actual work to do is going to contact, establish rapport, communicate enough to know the contact would be valuable, and then most importantly, maintain the relationship with 10 NEW people every single working day for 4 years straight.
I still stand by the research that makes it evident human beings can't maintain relationships with more than a couple hundred people at a time, and I doubt very much that Feld( or any other human being )is capable of even remembering a small fraction of the people on that list.
That being said, I'm probably one of those 10K contacts and say what you will, Brad has always responded to email and been a helpful resource to myself and the community without asking for anything in exchange. Not exactly a contact whore. Or a lightweight.