HBS cases I'd like to see - the AAPL NDA
In part three on an ongoing series, we take a look at one of my favorite companies, the almighty Apple...
Launched just last month, the iPhone 3G has already sold over 3MM units. Taking advantage of the "computer in the palm of your hand" concept, Apple has opened up the platform for development by 3rd party software companies. Current favorites include Twitterific, Facebook, Google, and a whole host of other applications sold exclusively through the iTunes store in the hopes of presenting a seemless and integrated user experience.
Or is it?
There has been much discussion around the blogosphere about the Nondisclosure agreement (NDA) that goes with becoming an iPhone developer. You see, the only way to get your application onto the iPhone is through iTunes, and the only way into iTunes is through Apple. In order to do that, a developer has to be certified by Apple, a process that involves, amongst other things, signing an NDA that severely restricts the developers' ability to discuss anything iPhone related with basically anyone anywhere.
As I understand it, NDA's preventing developers from disclosing details to the public aren't that uncommon, but ones limiting access to their peers are. By imposing these restrictions, which are effectively the price of entry, Apple is limiting the developer community's ability to help each other troubleshoot and offer other forms of support. Which in turn slows down the development/revision cycle and pretty much guarantees a crappy 1.0 product (the NDA also precludes beta testing).
All this from a company that's notorious for their secrecy and "proprietariness," so much so that there are those that say that it's the sole reason that APPL and MSFT aren't revered in scale and scope.
This one feels like a job for Dave Dilts, Oh He of Strategic Management of Technology. Some of the things I'd like to see discussed include:
- AAPL is a relatively small (but growing) fish in the Koi pond of personal computers. But when talking about the iPhone, are they a computer company, a phone company, or something else entirely?
- No help with debugging, troubleshooting, or beta testing means inherently less stable products. Are program crashes blamed on the software or on the iPhone in general? Are you more likely to hear "#$%^& Facebook crashed on me again," or "#$%^& iPhone, why doesn't it 'Just Work'?" What are the long term implications of that for AAPL?
- Developing for Windows or the web represents a larger market than developing for the Mac. At what point does AAPL start to worry about alienating all their outside developers? Or is that their strategy, to make sure all the toys are their own?
- If this is a case of "His Steveness" being his oft-referred micromanagerial self, at what point does the company start feeling hamstrung by that attitude? How does the Pepsi Incident factor in to that decision?
[Photo credit: Chris Radcliff via Flickr]





Your thoughts on their relative effectiveness aside, its hard to deny that the case study is a staple of the MBA diet. From Erik-with-a-"K" Peterson in first mod's LTO to Wal-Mart in mod 3's Core Strategy, stopping briefly in mod 2 to visit with Arthur Dief as well as the gang at Southwest Airlines during Core Operations, my first year at Owen saw a significant number of hours devoted to pouring over the pages of the all-too-familiar classpack, highlighter in hand and Excel standing at the ready. Add to that the hours spent discussing, writing, polishing, and paring down to fit inside the sometimes-questionably-low word limit, and its fairly safe to say that the case study represented a significant portion of our lives at the Owen School.
Like most of my classmates, I spent the first two weeks of my post-MBA-"working for the man" life locked in a series of ballrooms attending one training session after another. As part of the
Just under 2 years ago I had the good fortune of being introduced, through the wonder that is Owen Orientation, to 8 of the coolest people. Introduced via Consuela-mail (no, that's not the official term, but I'd like to see it *become* the official term) in the middle of the summer, our first official meeting was a tentative and semi-awkward Coffee Talk at the local Starbucks with 9 people trying to figure out exactly how the dynamic was going to work.
Oh.
The other day I got "looped into" an email conversation that was somewhat tangentially related to an ongoing project in one of my classes. For me, getting CC'd on the 15th email of the chain has always felt a little like walking into a room full of laughing people - you don't exactly know what's going on but you really hope they're not laughing at you.
MBA #1: Actually, my goal is to be in a Harvard Business School case study.
The case study is a staple of the MBA diet. Most of the classes I've had here at the Owen School have partaken in that age-old tradition - most were in print, but some actually embraced the new media revolution and presented online or video versions of themselves, including my personal favorite (think: dog and checkered hat).
Overheard at lunch today:
The other day I sat in yet another team meeting. Like most meetings, this one saw a handful of people sitting around a table, each separated from the larger group by an open laptop. As has been the case many times before, this group was trying to do entirely too many things at once. In addition to the multiple conversation threads bouncing around the table (only one of which, I'm sorry to say, had anything to do with the assignment that was the actual basis of the meeting), each of us had multiple things going on our respective computer screens -
Earlier tonight the VU men's basketball team hosted the Fighting Gamecocks of the University of South Carolina in the SEC opener at Vanderbilt's Memorial Gym. The 'Dores came into the regular season undefeated and ranked 13th (AP, 12th in the coaches poll). With Ole Miss falling to Tennessee, that leaves Vanderbilt and four other teams (Kansas, UNC, Memphis, and Washington State) with undefeated records.
Recent Comments