🔎
Apr 5 2020

State of Colorado COVID-19 Innovation Response Team, Part VII – Retrospective

(This is the seventh and final post in a series documenting the work I did in Colorado on the Governor’s COVID-19 Innovation Response Team – IRT.  Other posts in order are 1, 2, 3, 4, 5, and 6.)

I’ll start the final post in this series by sharing the overview and retrospective deck that we created my last day and the two days after.  Governor Polis is going to share this with the National Governors Association in case other states are interested in our model or learnings. This pdf, which you’re welcome to download or just view in SlideShare, is a good overview of what we did and where things stood as of Saturday, March 28, noting that by the time you’re reading this post, half of it may be obsolete! 

https://www.slideshare.net/mattblumberg/irt-strategyoverview032720

I am normally a small government guy.  But not when this kind of thing hits. This whole thing calls for consistent national government response to the disease – potentially even global government coordination at a level we’ve never seen before (let alone the level that’s fashionable these days).  I’m not sure I’d want a Chinese style lockdown (although that may prove to have been effective), but South Korea’s pattern of learning from SARS and MERS, bulking way up on labs, reagents, epidemiologists, ventilators, etc., and then passing legislation that allows for deeply intrusive tracking in case of a public health emergency like this seems to be the way to go.  

Certainly, leaving responses up to individual states, counties, and cities is a problem.  It’s inefficient and on average ineffective, although I think our group made some extraordinary progress on a few fronts.  But the scale of the effort in an individual state of 6mm people with the associated resources just pales in comparison to what a strong federal response would be.  Of course…the federal government has to actually believe in the need for a rapid and comprehensive response and have the wherewithal to pull it off for that to work.

As for our federal government’s economic responses, that’s a different story.  At some point, the government literally won’t be able to afford to fill in the economic holes left behind by the virus (you could argue that we can’t even afford the $2T we’ve already ponied up since we are terrible at saving money when times are good and run huge deficits even then).  I’m not sure what will happen then.  

But government aside, I hope the response across the country and the world is enough to take the edge off this disease long enough for supply chains and healthcare systems to be able to properly respond.  I hope that people who have the means will continue to support local businesses and individual/freelance service providers like housekeepers, gardeners, music teachers, tutors, and coaches through this stretch, even if those people aren’t able to provide those services.  And I hope all the people who are on the ground working the problem – from frontline healthcare workers to my new friends in the Colorado state government and on the volunteer side – get the recognition they deserve for the extraordinary efforts they are undertaking to drive solutions and get everyone through this.

Special thanks to Governor Polis and his staff for the opportunity to do this work, to Brad for roping me into it and then letting me rope him into leading the private sector side, and to Kacey, Kyle, and Sarah, my new friends, for making it all work and for continuing the work after I left.

Dec 28 2006

Just Because You Can Do Something, Doesn’t Mean You Should

Just Because You Can Do Something, Doesn’t Mean You Should

This has always been one of my favorite axioms for life and for entrepreneurship.  Today’s example comes from Brad’s new running blog, and ultimately from an AP story reported in the Northwest Florida Daily News.  The full story is here, but this teaser ought to get you hooked enough to click through, much as drivers slow down to see accidents on the other side of the road:

Pain doesn’t defeat unshod marathoners

Last month, after returning from an eight-mile run, Tsuyoshi Yoshino heated up a three-inch sewing needle until it turned bright red. Then, he says, he plunged the glowing instrument into the ball of his foot, puncturing a three-inch-long blister.

Despite the risk of infection, he walked around his San Diego house for 20 minutes on the open wound to get used to the pain. “It’s not something I like doing,” he says. “But I have to.”

Apologies to the squeamish.  Happy New Year!

Aug 18 2004

What's Your Preference?

More thoughts on some of Fred’s and Brad’s points about VC deal algebra, valuation, and liquidation preferences for venture-funded startups. My apologies if this gets a little too technical or too long!

On liquidation preference: Preferred stock makes sense, participating preferred makes less sense. Sure, a VC who puts capital at risk in a startup should be entitled to get his or her money out before management and common shareholders who are paid to run the business. But I’ve always had an issue (even when I was in the venture business, although admittedly not as a partner) with the participating preferred security which allows VCs to get their money out first, and then still receive their proportional share of the rest. Fred calls this “a loan with an option,” and that’s the best presentation I’ve ever heard of the security. But what’s always struck me as a bit over the top about this is that it gives VCs downside protection at the same time they’re negotiating even more upside in a deal.

One simple solution to this, if you can negotiate it, is a “kickout” provision which makes the participation feature on the security go away if the company becomes worth a multiple (usually 2x or 3x) of the post-money valuation of the financing. In other words, it gives the VC the downside protection they want but gives you and other shareholders more of the upside if things go really, really well.

On valuation and deal algebra: I completely agree that valuation is a derived number and that it’s completely misunderstood in early stage investing. However, I think that while there may be low correlation between valuation and what the business is worth today, there are a few things that have always bugged me about VC valuations:

While I understand that valuation is more a function of future potential than current value, it sometimes feels like companies get punished for having a track record. Let me clear about my point – it’s not that that I actually think VCs lower valuations unfairly when companies demonstrate poor results. It’s actually the opposite. VCs are quick to bid up the valuation on companies that don’t have revenue or even a lot of operations just because the idea is cool or because the theoretical market is large (Friendster, anyone?). I don’t think VCs as a group do a good enough job of risk-adjusting or future-competition-adjusting valuations for new companies, or they get caught up in what Fred once called Venture Fratricide and just pour money into new sectors en masse. This has the unintended side effect of making management teams of existing companies feel like their ideas aren’t interesting any more because they’re not new and shiny.

Second, it’s interesting to note that while VCs use valuation as a way of placing limits and getting protection on their bet about the future potential of the company and entrepreneur, entrepreneurs have no corresponding mechanism to place limits or receive protection against having a bad VC. (VCs actually have many tools at their disposal to reign in poorly performing management teams once the deal is signed – they can fire them, cram them down, force all their common stock to be on a vesting schedule or subject to clawback.) But make no mistake about it – a bad VC can almost kill a company, or certainly keep it from realizing its full potential, and once that deal is signed, the entrepreneur typically has little recourse. I’m not sure there’s an easy solution to this particular problem either, but it’s one that’s worth thinking through with a good lawyer the next time you negotiate a term sheet with a new venture investor (and certainly one that is easier to negotiate if you either have a good track record as an entrepreneur or multiple VCs interested in your company). I made one suggestion around participation in future financings in my earlier posting on term sheet negotiations — item #8.

The final thing that’s bugged me about valuations stems from what Fred calls the 1/3 rule (1/3 of a VC’s investments work out well, 1/3 go sideways, 1/3 go bad). As a result of the rule, valuations and deal structures can end up being about VCs getting as much upside as possible out of their winning deals to cover their losses from their zero-return deals. What bugs me about this is that entrepreneurs don’t have that same luxury of a diversified portfolio – they are 100% invested in terms of their human capital and often their investment capital in their company. I fully realize that this is the nature of the beast, but I’ve always felt as a result that entrepreneurs should negotiate – and VCs should be willing to give – proportionally much more upside to management in the event that the deal turns out to be a big winner. This point relates back to my first point about participating preferred securities.

Next up in this series…Reverse Engineering Venture Economics, and managing other kinds of investors (Angel and Strategic).

May 10 2006

Blogiversary, Part II

Blogiversary, Part II

So it’s now been two years since I launched OnlyOnce.  Last year at this time, I gave a bunch of stats of how my blog was going.

The interesting thing about this year, is that a lot of these stats seem to have leveled off.  I have almost the same number of subscribers (email and RSS) and unique visits as last year.  The number’s not bad — it’s in the thousands — and I’m still happy to be writing the blog for all the reasons I expressed here back in June 2004, but it’s interesting that new subs seem to be harder to come by these days.  I assume that’s a general trend that lots of bloggers are seeing as the world of user-generated content gets more and more crowded.

Not that I’m competitive with my board members, but I believe that Brad and Fred have both continued to see massive subscriber increases in their blogs.  They attribute it to two things — (1) they have lots of money they give to entrepreneurs, and (2) they write a lot more than I do, usually multiple postings per day, as compared to a couple postings per week. 

I don’t see either of those aspects of my blog changing any time soon, so if those are the root causes, then I’ll look forward to continuing this for my existing readers (and a few more here and there) into 2007!

Mar 29 2005

I'm Sorry, What Year Is It?

I’m Sorry, What Year Is It?

My colleague Tami Forman saw the attached leaflet posted on the subway in NYC.  I’m not sure which is funnier — that someone wrote it and put it up, or that two people ripped off the phone number to make follow-up calls.  Fred, Brad, Greg, anyone interested?Internet_startup_seeking_funding_1

Jan 5 2005

How to Negotiate a Term Sheet with a VC, Part IV

How to Negotiate a Term Sheet with a VC, Part IV

Brad is making  new postings easy this week.  Here’s another good one from the VC’s perspective on liquidation preference.

Oct 6 2006

links for 2006-10-06

May 19 2004

Blog Blacklists: A New View of Internet Vigilantes

I always thought that spam blacklists were well intentioned but problematic for the email ecosystem, since they are vigilantes in action and have no accountability and trackability. Periodically, I’ve even pondered whether or not they violate someone’s first amendment rights. It’s maddening to know you’re a good guy in the email world, you can get put on a blacklist because some anti-spam zealot decides he or she doesn’t like you on a whim, you can’t complain or get off of the list, you may not even know you’re on the list, then you’re downloaded thousands of times by naively trusting or equally zealous sysadmins, and boom — your emails aren’t getting through any more.

Then yesterday, I was looking at what’s probably the first blacklist for blog comment spam, dubbed by Brad Feld as BLAM. I immediately found myself using it myself to prevent my blog from getting overrun by the newest Internet evil. (Of course, I should be so lucky…my fledgling blog has all of one comment on it, but I’m sure there are scores of people ready to comment at a moment’s notice.)

So here we are at the dawn of a new era: the beginning of the blacklist for blam. I’m an early adopter of Jeff Nolan’s pioneering list and proud of it, which made me rethink my view of email blacklists for about five minutes. It didn’t ultimately change that view — email blacklists still have all the problems I mentioned above and have run amok — but it does make me hope that there’s a better long-term solution for stopping blam than the one the world of email has ended up with. Fred Wilson has some good thoughts on better tools for this as well.

Necessity, as always, is the mother of invention, but hopefully the blam blacklist situation won’t get out of control before someone tries to fix it, which may be too late. What I think we need now to solve the blacklist problem is a blacklist of blacklists, but that’s another story for another posting.

Oct 27 2004

Why is Seth Godin so Grumpy?

Why is Seth Godin so Grumpy?

Permission marketing guru Seth Godin says we should all Beware the CEO blog. His logic? Blogs should have six characteristics: Candor, Urgency, Timeliness, Pithiness, Controversy, and maybe Utility — and apparently in his book, CEOs don’t possess those characteristics.

Certainly, CEOs who view blogs as a promotional tool are wasting their time, or are at least missing a fundamental understanding about the power of blogs and interactivity.

But many of the ones I read (and the one I write) do their best to be anything but promotional. One of my colleagues here describes my blog as “a peek inside the CEO’s head,” which is a great way of putting it. And I still stand by my earlier posting about the value of the blog to me and to the company — hardly “annual report fluff.”

How’s that for honest, timely, controversial, and pithy, Seth?

Jun 16 2011

Keeping It All In Sync?

Keeping It All In Sync?

I just read a great quote in a non-business book, Richard Dawkins’ River out of Eden, Dawkins himself quoting Darwinian psychologist Nicholas Humphrey’s revolting of a likely apocryphal story about Henry Ford.  The full “double” quote is:

It is said that Ford, the patron saint of manufacturing efficiency, once

commissioned a survey of the car scrapyards in America to find out if there were parts of the Model T Fird which never failed. His inspectors came back with reports of almost every kind of breakdown:  axles, brakes, pistons — all were liable to go wrong. But they drew attention to one notable exception, the kingpins of the scrapped cars invariably had years of life left in them. With ruthless logic, Ford concluded that the kingpins on the Model T were too good for their job and ordered that in the future they should be made to an inferior specification.

You may, like me, be a little vague about what kingpins are, but it doesn’t matter. They are something that a motor far needs, and Ford’s alleged ruthlessness was, indeed, entirely logical. The alternative would have been to improve all the other bits of the car to bring them up to the standard of the kingpins. But then it wouldn’t have been a Model T he was manufacturing but a Rolls Royce, and that wasn’t the object of the exercise. A Rolls Royce is a respectable car to manufacture and so is a Model T, but for a different price. The trick is to make sure that either the whole car is built to Rolls Royce specifications or the whole car is built to Model T specifications.

Kind of makes sense, right?  This is interesting to think about in the context of running a SaaS business or any internet or service business.  I’d argue that Ford’s system does not apply or applies less.  It’s very easy to have different pieces of a business like ours be at completely different levels of depth or quality.  This makes intuitive sense for a service business, but even within a software application (SaaS or installed), some features may work a lot better than others.  And I’m not sure it matters.

What matters is having the most important pieces — the ones that drive the lion’s share of customer value — at a level of quality that supports your value proposition and price point.  For example, in a B2B internet/service business, you can have a weak user interface to your application but have excellent 24×7 alerting and on-call support — maybe that imbalance works well for your customers.  Or let’s say you’re running a consumer webmail business.  You have good foldering and filtering, but your contacts and calendaring are weak.

I’m not sure either example indicates that the more premium of the business elements should be downgraded.  Maybe those are the ones that drive usage.  In the manufacturing analogy, think about it this way and turn the quote on its head.  Does the Rolls Royce need to have every single part fail at the same time, but a longer horizon than the Model T?  Of course not.  The Rolls Royce just needs to be a “better enough” car than the Model T to be differentiated in terms of brand perception and ultimately pricing in the market.

The real conclusion here is that all the pieces of your business need to be in sync — but not with each other as much as with customers’ needs and levels of pain.

Aug 22 2013

Unknown Unknowns

Unknown Unknowns

There are known knowns. These are things we know that we know. There are known unknowns. That is to say, there are things that we know we don’t know. But there are also unknown unknowns. There are things we don’t know we don’t know.”   –Donald Rumsfeld

Say what you will about Rumsfeld or the Iraq war, but this is actually a great and extensible quote.  And more to the point, I’d say that one of the main informal jobs of a CEO, sort of like Connecting the Dots in that it’s not one of the three main roles of a CEO) is to understand and navigate known unknowns and unknown unknowns for your organization (hopefully you already understand and navigate the known knowns!).  Here’s what I mean:

  • An example of a known unknown is that a new competitor could pop up and disrupt your business from below (e.g., the low end) at any minute.  Or let’s say your biggest partner buys one of your competitors.  These are the kinds of things you and your team should be cognizant of as possibilities and always thinking about how to defeat
  • While I suppose unknown unknowns are by definition hard to pin down, an example of an unknown unknown is something like a foreign leader deciding to nationalize the industry you’re in including your local subsidiary, or a young and healthy leader in your organization dying unexpectedly, or September 11.  I suppose these are “black swan” events that Nassim Nicholas Taleb made famous in his book.

Helping your team identify potential known unknowns and think three steps ahead is critical.  But helping your team turn unknown unknowns into known unknowns is, while much harder, probably one of the best things you can do as CEO of your organization.  And there are probably two ways you can do this, noting that by definition, you’ll never be able to know all the unknowns.  As you might expect, the way to do that comes down to increasing your pool of close-at-hand knowledge.

First, you and your executive team can have as broad a view of your industry and corporate ecosystem, and of the economy at large, as possible.  It’s critical for business leaders to read diverse publications, to share insights with teammates, and to network with experts both inside and outside your space.
Second, you can design a culture so that information flows freely up, down, and sideways — so that people in your organization want to share information instead of hoard it.  That’s easier said than done, and there’s more than a blog post worth of what has to go into making that a reality.  But think about the CIA and all the flak they got about failure to connect the dots around September 11.  To close this post where I opened it, you can be the chief connector inside your organization…but you need to get your organization connecting the dots itself.