What “Inside Apple” Teaches You about Product Marketing and Product Management

September 4, 2012

Introduction

While reading “Inside Apple,” Adam Lashinsky’s book about “how America’s most admired – and secretive — company really works,” Apple Computer became the most valuable U.S. company in history. Apple’s market capitalization reached $623.5 billion, exceeding a record set by Microsoft in late 1999.

I’m a PC” aptly describes my lifelong experience with computers (aside from college and post-college years with assorted variations of Unix). Recently, however, Apple devices have made their way into my household. There was the iPod Nano (for me, in 2005), the iPod Touch (for my daughter, in 2009), then the iPad and Macbook for my wife.

Some evenings, I’d peer across the family room to see all family members using Apple devices: daughter on the iPod, wife on the iPad and me on the iPhone. Apple has made a large dent in corporate America as well. At my workplace, many users have moved to the Macbook. And, emails sent during the evening hours typically say “Sent from my iPad.”

So with all that in mind, I wanted to read Lashinsky’s book, not only to discover Apple’s secrets, but also to gain insights into their product marketing and product management.

Insights on Product Marketing

Build anticipation and suspense around your product launches.

Well before Lashinsky’s book was published, we all knew how insanely secretive Apple is, with just about everything. Apple has clearly demonstrated, however, that secrecy works wonders as far as product launches go. Apple’s product launches are like The Super Bowl, the Oscar Awards and the Election: monumental, “must see” events with a massive amount of coverage.

Why Apple does this:

  1. The build-up of anticipation creates heightened excitement and intensity when the big announcements (i.e. new products or product features) are made.
  2. Minimizes deferred purchases, which affect sales of existing products (e.g. “I’m not buying the iPhone 4 because the iPhone 5 is due out soon.”)
  3. There’s a danger to pre-announcing products or features that you don’t end up delivering. HP pre-announced the sale of its PC business, then later changed its mind.
  4. Pre-announcing product details gives the competition a head start in responding.

While reading the book, in fact, TechCrunch published a piece about a Silicon Valley start-up whose product launch was ruined by a broken embargo. While Apple never would have done this, it must be said that Apple’s position affords it the ability to do “big news” product launch events.

Start-ups, on the other hand, face a chicken and egg problem: they need to brief reporters on their new product in order to get the coverage (to some day be as prominent as Apple).

Tie each and every deliverable to a single owner.

Chapter 4 describes Apple’s approach to event marketing planning. The event marketing group creates a document called “At a Glance,” a detailed schedule for the event. “Each item, along with the time and place it will occur, includes a DRI.” (DRI stands for “directly responsible individual”).

DRI’s are used not only in event marketing, but throughout Apple. Every single task, no matter how small, would have a DRI assigned to it. Jobs “made committee a dirty word at Apple.” With DRI, you knew whom to contact when the signage never appeared at your trade show booth. You don’t contact the event marketing team, mind you – instead, you contact an individual.

Insights on Product Management

Product development process.

Apple uses a repeatable process to build product. It’s called ANPP – the “Apple New Product Process.” Once the design of the product is under way, two parallel tracks begin: the supply-chain team (who determines how and where to source the component parts) and the engineering team (who figures out how to build and assemble the parts).

Related to the DRI concept, the supply chain effort is headed up by a Global Supply Manager (GSM) and engineering by a Engineering Program Manager (EPM). Based at headquarters, but spending most of their time in China, these individuals head up each team.

Most companies will follow through on a product development process until the product ships. Apple is different. “But once Apple is done designing, building, and testing a product it starts designing, building, and testing all over again.” This process happens every four to six weeks.

An extreme focus on the user experience.

User experience not only defines the ease with which end users operate your device or application, but it can also create emotional bonds. The user experience is a key reason why Apple has an adoring fan base of intensely loyal users.

This segment from the book tells it all: “.. the modern obsession with user experience has created a shorthand for how Apple employees communicate .. At Apple, thirteen of fifteen topics get cut off after a sentence of discussion. That’s all that’s needed.”

Pillars of Simplicity

Image source: User JoshSemans at flickr.

In the building housing Apple’s marketing and communications team, a large wall reads “SIMPLIFY, SIMPLIFY, SIMPLIFY.” And a line is drawn through the first two SIMPLIFY’s. Apple is all about simplifying, from product design straight through to product marketing.

Simple is hard.

You may be inclined to think, “simple is easy.” Simple means less things to include, less to say, less to do. That’s easy, right? Wrong. Simple is hard and doing simple right is even harder. That’s part of Apple’s competitive advantage: they do simple well.

What makes “simple” challenging:

  1. Adding more features is far too easy.
  2. Saying “no” to particular features is hard.
  3. Simple means less – and when you have less, what remains (the features, the design, etc.) must be world class.
  4. As such, simple raises the bar on every nook and cranny of your product.

Simplicity in the product line.

You can see Apple’s simplicity in its product portfolio. You could once fit their entire product line on a conference room table (this may no longer be possible). Even with a company of Apple’s size and stature, they focus on a few key things at a time. “The minute you’re doing a hundred things, you can’t possibly do things the Apple way,” said a former executive there.

Simplicity in product marketing.

Think about doing product marketing for the iPhone. A conventional approach may be to list all the amazing and unique features that it has. You might list this out in a matrix, alongside competitors’ phones, showing all the areas you beat the competition.

If you ask Bob Borchers, who ran product marketing for the iPhone, “the best messaging is clear, concise and repeated.” Apple boiled down the iPhone messaging to:

  1. A revolutionary phone.
  2. The Internet in your pocket.
  3. The best iPod we ever created.

The approach here is to highlight what makes the iPhone stand out, then give “consumers only as much as they needed to get excited.” According to Borchers, “Just use the same words over and over again. That will turn into the same words that the consumer hears, which ultimately will turn into the same words that they then use to define the product to their friends.”

Conclusion

Lashinsky’s book provided interesting insights on the Apple Machine. Some insights can be applied directly to your product marketing and product management, while others are completely unique to Apple (this post attempts to distill what you can apply directly).

To summarize some of the key points:

  1. Product launches are hugely important events. Figure out how to best manage the information you provide around them.
  2. Assign deliverables to individuals, rather than groups or committees.
  3. Develop, refine and continually re-use a product development process.
  4. KISS (keep it simple, sir).

Buy the book at Amazon:

http://www.amazon.com/Inside-Apple-Americas-Admired-Secretive-Company/dp/145551215X

Note: I invite you to connect with me on .


How Vendors Should Evolve Their Virtual Event Platforms

July 10, 2010

The following is a collaborative posting by Miguel Arias, Steve Gogolak and Dennis Shiao.

Content creation and collaboration was facilitated by a PBworks wiki – the wiki page can be found here: http://allvirtual.pbworks.com/How-Vendors-Should-Evolve-Their-Virtual-Event-Platforms

To evolve their platforms for enhanced experiences and broader adoption, virtual event platforms should consider the following:

Make it easier to experience

Most virtual event platforms are easy to use – on a first-time visit, users tend to grasp the overall user experience and can figure out where to go (and how).  That being said, for wide scale adoption, virtual events needs to be as easy as Facebook.  That is, our grandmothers need to be able to access the site and figure things out.  On Facebook, grandmothers can update their profile, read their “friends” posts and write updates to their Walls.  Can a grandmother login to a virtual event, update her profile and participate in a group chat?  We’re not so sure.  Similarly, navigation and interactions need to be easier.  Most virtual events are intuitive to navigate (e.g. Lobby, Auditorium,  Lounge, etc.) – but may not be so intuitive with regard to message boards, chat, blogging, rating, etc.

Along with a simplification of interfaces and the use of usability and navigation conventions, many customers and users seem to be demanding more immersive environments. While presenting a brand and hosting an interactive experience in a convention centre, it seems an interesting field to add some real-time rendered environments using engines like papervision3D or Unity3D. This said, it is unlikely that avatar-based real time rendered environments will make it to a mainstream audience. Key considerations (or obstacles) are plugins or applets downloads, system performance and learning curve barriers.

Make it easier to find

The typical “location” of a virtual event is quickly becoming outdated – microsite with registration page, with no ability to experience the event prior to completing all mandatory registration fields. The registration page serves as a “wall” not only to potential attendees, but to search engines as well.  Virtual event platforms need to move “outside the wall” and expose their technology on Facebook, on blogs and on publisher web sites.  Platforms should widen their distribution via widgets, embed code and application programming interfaces (API’s).  Facebook is not limited to Facebook.com – it has Facebook Connect, Facebook Open Graph and much more.  Virtual events platforms, on the other hand, seem to be restricted to “VirtualEventPlatform.com”

Make it easier to access

The most relevant virtual event platforms will introduce, or already have, Facebook Connect and Twitter API, and they will need to move to even wider standards like OpenID.  For public events, ease of registration is a must.  Using open methods for registering and/or connecting social networks have three-fold benefits:

  1. Registration is faster because basic information can be provided by services like LinkedIn, Facebook, etc.  Shorter registration forms increase completion, period.
  2. Intelligence gathered by the platform about the user’s existing social graph can enhance the experience within the event by automatically creating connections with other attendees based on that user’s connection outside the platform.  This will lead to more networking and awareness of actual people within the environment.
  3. Users opting into connections at the point of registration allows platforms to create publishable actions that can be spit out to twitter and facebook news feeds that can increase viral awareness of the event.  Marketing automation at its best.

On the other hand, desktop or mobile widgets to control your stand usage, statistics and reporting will be a must. Lastly, the platforms will have extensive APIs to manage their integration with various social networks, corporate databases, physical event managing software, etc.

Make the experience available on more devices

Most virtual event platforms support Windows, Mac and Linux.  They need to support more platforms, especially mobile.  On the mobile front, it’s important to consider iPhone/iPad, Android, BlackBerry, Symbian, Windows 7 Phone and WebOS (listed in our order of importance).  To start, we don’t believe the entire virrual event experience needs to be “ported” to mobile devices -rather, vendors should determine the most critical features for attendees and exhibitors – and prioritize based on importance.  For instance, chat is an important element of virtual events, so why not make a mobile app that allows exhibitors to staff their booth via their smartphone.

The entire 3D environment does not need to be supported on a mobile device, but the networking tools (visit card managing, real time conversation, etc) and the reporting tools certainly do. On the other hand, it will be interesting to see what happens with Flash and Apple, and see which vendors will try to develop their platforms using HTML5.

One of the key areas where mobile can play a huge role is the “reminder” needs that come from tons of scheduled activities within virtual events.  If attendees have the ability to build out a personalized agenda before the event and opt-in to either SMS reminders or download some kind of app that will push notifications at them throughout the day, it would be much easier to create a flexible agenda.  Currently we’re cramming so much into the shortest amount of time because we’re afraid of losing people.  If only we had better planning and reminding tools, driven by devices that never leave our pocket!

Make the platform more adaptable and flexible

Related to our point about mobile support, platform vendors have important decisions to make regarding the development platforms.  Virtual event platforms today are based on Flash, Flex, Silverlight, Java and JavaFX.  Are those the “right” platform technologies for the future – or, should platforms move in the direction of HTML5?  Does a combination off HTML5, Javascript and Ajax create a more adaptable and flexible platform?  What do we “lose” by shifting away from Flash, Silverlight, etc.?  And what are the mobile implications with the chosen direction?  All good questions for the platform vendors to consider.

Make the platform more adaptable for different customer needs and different usage

There are so many different kind of virtual events: trade shows, conferences, job fairs, corporate events, webinars, congresses… that vendors should decide in which market niche they are going to play. We will see generic platforms and other vendors delivering a tailored solution for one or many of the previous choices. It will become more and more complex to provide physical event managers with the features they need to handle their hybrid events at the same time as the platform is able to cope with the extensive data handling of the virtual job fair, or the networking tools of a professional tradeshow.

Take a hint from Apple and FaceTime

Video chat will, without a doubt, increase the effectiveness of networking.  It is the one key element that can be introduced that will get critics to come around to the idea that networking in an online environment can be as effective as the cocktail hour of a physical event.

Tweet this posting:


%d bloggers like this: