A Word About Employee Stock Options

There's been a bunch of talk in blog circles about employee stock options over the last couple of weeks. I wrote a quick thought on this topic in a comment on a blog post the other day and thought I'd post it here as well. Put simply, in order to have an effective stock option plan that motivates and rewards employees, the employee must know three things:

1. The number of options they have.
2. The current valuation of the company.
3. The total number of shares outstanding in the company.

If an employee doesn't know these three things they should place no economic value on their options. Don't get me wrong, employees should take the options if they're offered, especially if they believe they're working for a high growth company, but the options should not be considered a measurable part of their compensation package.

You can't value something if you don't know its value.

ACOs: Cost vs. Convenience

Uber’s announcement that they’re launching an online delivery service is the latest sign that more and more consumers want more and more convenience. Personally, among other things, I book travel, buy groceries, order takeout, book dinner reservations and buy concert tickets from my iPhone. Amazon Prime and one-click shopping is now my expectation for a quality online shopping experience. People want convenient and easy and simple and beautiful in all aspects of their life. Slick apps like Kayak and OpenTable and Stubhub have caused consumers to be more and more spoiled.

We’re seeing this manifest itself in healthcare as well now with the explosion of urgent care centers, concierge medicine and tele-health sites.

This trend in healthcare is not only not going to not stop, it’s speeding up. When consumers want convenience, lots of companies pop up to give it to them.

It is this continuing demand for hyper-convenience -- and the willingness of organizations to offer it -- that makes me skeptical about the future success of Accountable Care Organizations (ACOs). Given the demand for convenience, will large portions of the population agree to be locked into a narrow network that limits choice, flexibility and ease of use? Do consumers (patients) want that?

The answer is complicated. But I think it hinges on an ACO’s ability to lower costs significantly enough that consumers are willing to start making some sacrifices.

When you consider the pendulum of convenience versus cost in healthcare, there are clearly defined markets on the fringes -- there are patients that will be happy to pay more for convenience and patients that will be happy to have less flexibility in return for lower costs. But the reality is that most patients are somewhere in the middle. The huge segments in the middle where convenience and cost matter is where the money will be made.

Providers' ability to walk this fine line between cost and convenience will be the thing that dictates the winners and losers and will be the key to the adoption of quality-driven accountable care.

People are going to want Uber to deliver their groceries, but if the price point is too high they'll just drive themselves to the store.

Facebook's Defensibility Is Gone

Traditionally when people have thought of Facebook and their defensiblity, they've pointed to its ubiquity and the size of its network – at last check they had something like 1.1 billion active users. People reasoned that Facebook would continue to dominate social because it's the one place that has profiles for all of your friends. All other social  networks would be forced to plug-in to the Facebook ecosystem. But as Facebook’s defensive purchase of WhatsApp shows, this is no longer the case. Users are bouncing from social network to social network. Social apps are much, much less sticky than initially thought.

Benedict Evans and others have pointed to the seemingly minor but incredibly impactful fact that any newly launched social app can easily tap into your mobile phone's address book and instantly build out a network equal to -- or better than -- Facebook's.

This wasn't a big a issue when most users accessed Facebook through the desktop site, but now that most users access it through their mobile app, Facebook's unbundling has accelerated.

More and more users are migrating to WhatsApp for messaging, Vimeo for video, Instagram for photos, Foursquare for location sharing, etc. And there are niche players internationally that are focused on badges, stickers and other features valued in those communities.  There are now dozens and dozens of social apps in the app store with more than one-million downloads.

Facebook's strategy of running the social ecosystem seems to be shifting more rapidly than they had planned. Because of the mobile phone's address book, the approach of plugging social apps into Facebook may be losing steam. Instead of just letting them plug-in, the better approach, it seems, might be to buy them.

5 Ways To Address The 'Build Versus Buy' Question

When a prospect says something like, "well, at this point, our decision really comes down to build versus buy", don't fear, you've already won most of the battle. Your prospect has recognized that they need a product like yours and that they have to act. Getting a prospect to act -- and act quickly -- is the hardest part of selling innovation.

That said, you still have to address the issue.

I've always believed that the best way to address this concern isn't to give an opinion or a pitch; instead, the best approach is to give the prospect some topical things to consider as they look to make a decision. You're an expert in this area, you know lots of stuff that they don't. Help them think it through.

Here are five things you can encourage them to consider.

1. Specialization -- the world is complicated, companies need to focus on what they do well. Your prospect is good at their business and you're good at your business. Is it worth it for them to deviate from what they do well to try doing what you do well? Could that energy and those resources be better utilized on their core business? As Peter Drucker said, "do what you do best, and outsource the rest."

2. Unintended costs -- project and product managers know that when they begin a new project they don't know what they don't know. There are always unintended costs, requirements, hurdles and delays that come up when pursuing a new venture. It can be helpful to lay out, based on your own experience, what some of those unintended costs might be as your prospect sets out on building it themselves. Give examples. Highlight some of the things you've learned yourself.

3. Leverage with vendors -- because your prospect would be building the product for just one client (themselves) there are no economies of scale and little leverage with vendors. The costs could be far greater than they might think. List some vendors where this might apply.

4. Risk --  in my experience, when a company is considering building something themselves, they generally don't believe that the thing that they're looking to build is all that important. They'd admit that they might not do it as well as an expert but, "what's the big deal?" It's worth having a few ideas about what might make it a big deal if your prospect doesn't build it well; e.g. "if you don't want to be very high quality in this area, that's ok, but here are some potential consequences."

5. Experience -- over the last few years I've interviewed lots of consultants at top consulting firms. I always push them on describing why they're valuable. That is, how do they justify going into a business that they know nothing about to people there what to do?  The answer is the same every time: "experience". They've worked on similar problems with similar companies in similar industries. They've been through it before. The same thing exists in 'build versus buy'. If you're really good at what you do, it's generally not because you hit a few home runs, it's usually because you've done all of the little things over the years, learned some tough lessons and iterated to make the product better. Your prospect is going to have to go through that pain too. Is it worth it?

As Drucker says in the quote above, if a project deviates from a company's core mission, it's generally best to outsource it. Pushing a prospect to consider these five things not only positions you as a thoughtful expert but it also helps screen out clients that aren't a good fit.

That said, be sincerely open to the fact that building might be the right thing for your prospect. So don't "tell" them, help "guide" them. If after considering each of these factors your prospect still decides to build it themselves, that's a good outcome. It truly is. It means that they don't value the uniqueness of your mission or product offering and likely won't make a great partner down the road. There's nothing wrong with that.

When a prospect is considering build versus buy, raise the five issues above. You'll typically find that the way your prospect addresses these concerns will either help them see your value more clearly or will help you screen out a partner that isn't a great fit.