5 ms·
I think his issue was that the meeting was in bad faith. He was under the impression that he would be demoing his technology so it could get visibility within
by jedberg 14y ago
I think his issue was that the meeting was in bad faith. He was under the impression that he would be demoing his technology so it could get visibility within Facebook, not walking into a negotiation.
If they had been upfront about their intentions with the meeting, he probably would have never gone.
What do you think the purpose of the “platform developer relations” executive is?
To advocate AGAINST Facebook and for random outside developers?
Actually, yes. Usually that is what someone in that position does. They are the advocate for the customer, to help the company see things from the customer's point of view.
- notJim 14y ago> If they had been upfront about their intentions with the meeting, he probably would have never gone. I don't understand why this is a big issue. What was the cost to him in going to this meeting? It would hardly have changed the outcome (outcome: he declines their offer and they build a service which clobbers his.)
- fatbird 14y agoIt was an ambush that was designed to give FB an advantage in negotiating with him. It was hardball tactics, carried out in bad faith. Why should Dalton feel neutral about being on the receiving end of that?
- csallen 14y agoI don't understand how they gained an advantage through that meeting. It seems that, meeting or not, they already had the advantage by controlling the platform.
- fatbird 14y agoGenerally, negotiations favour the prepared. By ambushing him, FB was hoping to trick him into negotiating unprepared. Dalton, by experience or judgement or both, recognized the ambush and dealt with it well. Someone else might start talking terms because they accept what the FB execs are saying (and thus be intimidated or fearful, or grateful for what seems like a nice guy move by FB).
- klawed 14y agoDalton sums up his issue with FB's tactics pretty succinctly right here: Your team doesn’t seem to understand that being “good negotiators” vs implying that you will destroy someone’s business built on your “open platform” are not the same thing. He then goes on to call out the root-cause of the problem as FB's understandable but unfortunate focus on ad-revenue. This puts them at odds with the developers who use the platform and that's clearly not a good dynamic. Both MS and Apple have long understood that getting developers and keeping them happy was essential to keep a platform fertile. EDIT:fixing typo/poor construction in last sentence.
- tedsuo 14y agoActually, over the years both MS and Apple have heavily messed with developers in various ways. Microsoft refined the practice to the point they coined a new term for it: http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish As a recent example from Apple, they are now requiring sandboxing in the App store, which is heavily messing with a number of developers. But they are not sandboxing their own applications. EDIT: this comment appears to be unpopular? what's the disagreement? EDIT: Also, I should point out that apple didn't used to mess with developers, probably because they were primarily a hardware company, with low market share, so developers were key, and there was no competition. However, they have expanded and are now also a services company, so they have an incentive to mess with the environment in order to defend their services against competition. Microsoft, conversely, made quite a bit of money off of it's office products, so always had a reason to manipulate the environment.
- veyron 14y ago"What was the cost to him in going to this meeting?? Time, both in the meeting and in preparing, and in information transfer. He didn't specifically say what he went through, but he may have divulged pieces of the puzzle that they were unaware of.
- notJim 14y agoI mean, sure, but in business there are always meetings you attend for partnerships or offers that don't pan out. It's just the way the world works.
- veyron 14y agoYes but there's a difference between a well-intentioned meeting that didn't pan out and a mal-intentioned meeting, and it would seem that it was the latter according to the OP
- waterlesscloud 14y agoI recently had a meeting where our side came out of it literally saying "WTF was that?". We'd expected it to be about how a partnership would progress and it was more the other side questioning us about why there should be a partnership at all. In retrospect, our contact with the other side that had set up the meeting hadn't properly communicated to us what the meeting would be about, and presumably had not communicated much with his side about what they were looking for at this stage. Their side was basically dysfunctional, with each person on their team having a different agenda. I wouldn't say that meeting was mal-intentioned, just that their company was really screwed up. Facebook may be in a similar stage at certain levels.
- rhizome 14y agoThere doesn't have to be a specific badness to be mal-intentioned. Disparate, fuzzy, or nonexistent intentions are just as much a waste of time for the other side than specifically harmful goals. It's all garbage on the receiving end.
- jedberg 14y agoHis time is presumably valuable to him. The cost was his time. Time he could have spent building his product.
- jakebellacera 14y agoTime, sure, but also I think that instead of the exec-level support he wanted he instead got the impending doom that either: a) Facebook will knock on his door again at a later date asking to "acqu-hire". b) Facebook will eventually release something in-house that will compete with his app (and most likely win due to Facebook's large momentum). With the impending doom stuff aside, I still don't think that he should've expected getting exec-level support for his product walking in to the meeting. Facebook doesn't _need_ to give him anything. So yeah, he wasted his time, but that's _his_ problem, not Facebook's.
- notJim 14y agoI replied to veyron [your sibling]'s similar comment.
- Androsynth 14y agoWho knows what positions each took behind closed doors, but do you think they aren't going into a negotiation all on the same page? Do you think they would allow someone in negotiations to take a position opposite to the company line? Also, relations does not mean advocate. He has relations with the customer, he is not obliged to advocate their views. Especially not when it goes against FBs interests.
- larrys 14y agoOP is equating "“platform developer relations” " with "ombudsmen" apparently. Unfortunately this is a business. Not a university, non-profit or a government entity.
- _delirium 14y agoIt's not that uncommon for for-profit businesses to have someone in an ombudsman role, responsible for advocating on behalf of the (official) customer. It's most widespread in news companies, where most newspapers, news magazines, and TV stations have a role specifically designated to be the readers'/viewers' advocate. Of course, it's ultimately self-interested, but it's the kind of self-interest that involves convincing your customers that your organizational structure is taking them seriously. As an example from tech, I believe HN's 'jf' used to be a startup-relations person for Microsoft, whose job really did involve trying to advocate for their needs within Microsoft, reporting out of the product groups' normal management hierarchy to make sure he was giving them third-party input.
- larrys 14y ago"It's not that uncommon for for-profit businesses to have someone in an ombudsman role" I definitely understand your point but I don't think it is correct to use the phrase "not that uncommon" with respect to "for-profit businesses" without defining what types of businesses you are referring to. The overwhelming majority (anecdotal of course) of for-profit businesses do not have anything like an ombudsmen. I would agree that with respect to newspapers that statement would be correct from what I've seen and probably universities. I wouldn't want to speculate on the percentages here, but if we believe the numbers as far as the amount of businesses of all sizes that are out there, I think it's safe to say that the majority don't have an ombudsmen. So I would say it is uncommon.
- nl 14y agoI think his issue was that the meeting was in bad faith. He was under the impression that he would be demoing his technology so it could get visibility within Facebook, not walking into a negotiation. While it is true that he said the thought he would be demoing, I don't think the discussion about an acquisitions was a problem in itself: I said that if Facebook wanted to have a serious conversation about acquiring my team and product, I would entertain the idea. I think his problem was that Facebook were negotiating from a position of strength (and were honest about that), and he didn't like it.
- marshray 14y agoI think his problem was that Facebook were negotiating from a position of strength (and were honest about that), and he didn't like it. It really is odd how ecosystem developers always seem to act so shocked when they realize that the prime developer (the one who wrote the API agreement) turns out to hold all the power and control.
- alexqgb 14y agoActually, the real issue is that they're breaking their implicit promise to refrain from competing against the outside developers they rely on to improve their "open" ecosystem.
- nl 14y agoa) I disagree completely that there is any sort of implied promise not to compete with app developers. Even ignoring history on other platforms (where every single platform takes good ideas from apps and incorporates them) Facebook is too young a company for people to think they won't add something to their platform. b) Even if there is an implicit promise, in this case Facebook acted very ethically in offering to buy him our when they decided to offer the same features. I can't imagine a better way to have handled that situation from Facebook's point of view.
- alexqgb 14y ago
- CoffeeDregs 14y ago> I think his issue was that the meeting was in bad faith. Agreed, but an honest question [and I'm no fan of FB, but...]: how could FB have requested a meeting without acting in bad faith and without being dumb? Seems dumb for FB to say to Dalton: hey, we're about to launch a competitive product and, since you're going to be squashed, we wanted you to come in to talk about an aqui-hire. Now Dalton has inside-ish info on FB (which he will have post meeting anyways) and can run around telling FB's competitors that FB is bidding for his company. I suppose one of the VPs could have pinged Dalton about meeting for coffee, but then, assuming the informal meeting goes well, Dalton still has to meet all the other VPs, Dirs. Plus FB has a lot of these conversations with companies (I've been in 3 separate ones with 2 companies), so this is kind of the process. I don't particularly see a better way for FB to handle the situation. Were I Dalton, I would have given myself some cool-down-room and, rather than blowing off the discussion, would have engaged the folks in a discussion and then told everyone that I'd get back to them first thing in the morning. Then I would have gone for a long run and let my thoughts settle. Or at last that's what I did when this happened to me 4 years ago.
- 385668 14y agoThey can tell him that they're interested in an aqui-hire before hand. That's how they can act in good faith. If he shows, he gets the info they gave him at the meeting anyway. If he doesn't, they crush him, which they plan to do now, after the meeting they had in bad faith.
- freehunter 14y agoWhat else would the meeting be for? He's incredibly naive if he honestly thought that the meeting was going to be them congratulating him for making a good product and nothing more. I was hoping the outcome of this meeting would be executive-level support for my impending product launch. What executive-level support would they give him except to buy him/his product? The bad faith here is going into this meeting with no intention of entertaining their obvious position.
- 14y ago
- k-mcgrady 14y agoBad faith? Why didn't he ask them to be more specific about why they wanted a meeting. It seems the problem was that he made an incorrect assumption.