Category Archives: Leadership

The Silicon Valley Canon, Circa 1998: A Stroll Down Software Memory Lane

Something fun happened today. A reader reached out who had been digging through my early-2000s and 2010s posts trying to understand the history of the software industry. That immediately got my attention because I love people who study history. It’s the best way to understand the present. And a great way to avoid repeating the mistakes of those who preceded you.

So I’m always happy when someone wants to talk about software history.

His specific request was interesting: he was looking for case studies or books that were popular at the time — something that would help him understand how people in the industry were thinking back then.

I decided to do him one better. In my view, the real canon of books that shaped enterprise software thinking was largely written before 2000. So I assembled the following reading list: a set of 1990s-era books on software, strategy, marketing, and the industry itself that many of us were reading while the enterprise software industry was taking shape.

Think of it as a reading-list stroll down software, and Silicon Valley, memory lane.

1990s Era Tech Marketing and Strategy Books

High-Tech Marketing

Positioning / Marketing Foundations

Technology Strategy / Innovation

Product Marketing Culture

Enterprise Sales / Go-to-Market

Economics of Software / Networks

Enterprise Technology Industry Case Studies

Software Engineering

Classical Strategy

Change Management and Selling Hope Along The Way

Let’s say you’re a CEO leading your startup’s migration from mid-market to enterprise. To do that, you’ve hopefully already done the following:

  • Analyzed existing success in enterprise accounts. (Most people don’t start purely from scratch, but instead have picked up a few “accidental” customers that they hope to replicate.)
  • Hired a team to pursue enterprise, ideally with dedicated AE, SCs, SDRs and even more ideally with a dedicated CSM and marketer. Concretely, that initial team might look like 1 sales manager, 4 AEs, 2 SCs, 3 SDRs, 1 CSM, and 1 field marketer. A focused team of dedicated resources is an infinitely better approach to opening a new market segment than making it everyone’s pastime.
  • Done market research to understand the competitors you’ll encounter and the buyers to whom you’ll be selling. You’ve then made an initial strategy for beating those competitors and built messaging that maps to those buyers and their business priorities.
  • Identified product gaps. Your product team has done a study to identify missing product features that customers in the new segment will demand. You’ve made a plan that combines workarounds and the product roadmap to sell successfully despite these gaps while you work to close them. (Beware that product gaps, often involving non-functional requirements, doom more new market migration initiatives than any other.)
  • Sold the initiative to both the board and the company as a valid and important priority. This will get you buy-in at both the board and team level, hopefully evoking real commitment to the new and difficult undertaking. As part of this, you may well have set initial end-state goals — e.g., getting 25% of new ARR from enterprise in six quarters, increasing your average sales price (ASP) by 50% relative to mid-market, and increasing product penetration per account from 1.5 to 3.0 products.

That’s awesome. You’re doing it by the book. So what did you forget to do? Particularly when getting to the initial end-state might take six quarters and another year or two beyond that to look at renewal and expansion rates?

What did you forget? To sell hope along the way.

I don’t mean selling hope in the metaphorical Charles Revson way. I mean selling hope in a literal way to the team and the board. Twelve to eighteen months is too long for people to wait for results. But if it takes 3 months to build the team, 3 months to ramp them, and sales cycles are 9-12 months, then your earliest possible results are 15-18 months from when you hit the “go” button with the board. Coincidentally, that approximates the MTBF for CMOs.

How do you sell hope along the way?

  • You lay out expectations, up front. You describe how you expect things to progress over time (e.g., enterprise team staffed up, first enterprise marketing event, hit enterprise pipeline of $3M, first closed new customer). And like any expectations, you set them carefully and remind people of them often.
  • You tell stories along the way. This is the part most people don’t forget. Hey, 125 people showed up at the enterprise event. Hey, we had a great meeting at BigCo. Hey, an analyst positioned us in an enterprise report. Hey, we hosted a great enterprise dinner in Philly. This is good, but the stories start to ring hollow pretty quickly in the absence of up-front expectations setting and downstream data.
  • You use leading indicators. Sure, we all know the end-state indicators that we want. A big chunk of total ARR. Faster growth. Bigger deals. Higher win rates. Increased GRR and NRR. Those are real indicators — and they’re important — but they’re lagging and, in cases, badly. You need to find some leading indicators to track and measure along the way. For example, in the enterprise segment: pipeline size, pipeline coverage, average size of oppties, high- and mid-funnel conversion rates, number of customers. Note that when moving up market, some metrics are going to get worse (e.g., stage progression velocity) so you may as well track and set expectations for those as well.

The main point here is to not make the rookie mistake of screaming: “Mid-market is dead! Long live enterprise!” Thus setting impossible expectations for enterprise all while undermining your mid-market efforts. Instead, you should carefully think through how the enterprise initiative is going to unfold, lay that out both qualitatively and quantitatively with leading indicators, and then report back to the company and board with progress reports, war stories, and metrics.

You’ve already convinced people that the enterprise initiative is a good idea. Now you need to make and execute a plan to keep them excited along the way.

Six Tips on Presenting to the Board of Directors

So, you’re on the executive staff of a startup and you’ve been asked to present at an upcoming board meeting.  That’s great news. Board exposure is a key benefit of working on the e-staff. You’re getting the chance to build relationships with the venture capitalists and independent directors who sit on your board. These people can help you in many ways, e.g., providing tactical advice, acting more generally as mentors, helping you extend your network, approving your future promotion to a more important position, presenting you with outside board or advisory opportunities, and — when the time comes for it — helping you find your next company.

The board can be a tailwind accelerating your career or a headwind slowing it down. Let’s talk today about how to make a good impression in board meetings and how to start building good relationships with the members of your board.

Here are six tips:

  1. Lose the baggage. If you have authority issues or PTSD from prior board experiences, you need to lose the baggage. That may not be easy — and you may need a therapist to do it — but boards can easily sense passive aggression and inauthentic interactions. I worked with one CRO who viewed board meetings as a necessary evil, something to survive so we can all get back to work. If you feel this way, the odds are the board can tell. (Our board certainly could, and it limited his tenure as a result.)
  2. Make your presentation from scratch. Bad board sessions start with bad slides. Usually, they’re too long and detailed. This typically positions the exec as either “in the weeds” (ergo too junior and in need of an upgrade) or “stonewalling” (i.e., deliberately making an overwhelming deck to stifle conversation). The path to hell begins in the slide sorter, so do not start there. Start with a blank outline to avoid the number one mistake — starting with what you have instead of what the audience needs. Doing so is a false economy and, for chrissake, it’s your board: if anyone deserves a custom presentation, it’s them. So make a custom slides, from scratch.
  3. Cut to the chase. Boards are notoriously impatient. Individual sessions are usually pretty short. There’s no time to warm up with “How ’bout those Yankees?” or several introductory slides, including the tired highlights / lowlights slide. (That slide is appropriate once in a board deck, in the CEO’s update, and if there’s something particularly good or bad in a functional area, it should have already been raised there.) If we’ve had insufficient pipeline for the past two quarters, go immediately to the reasons why and the remediation plan. If you’re not sure what the hot issues are — itself a yellow flag — ask the CEO. Nothing will infuriate a board more than endless warm-up slides that don’t cover the important issues. Beware saying: “Great question, but we’ll get to that on slide 27.” With some boards, you may not still be employed by slide 27.
  4. Make slides that facilitate discussion. Board members like to talk, so let them. Build slides that facilitate a discussion. That usually means first baselining the board with key facts and metrics. (Remember, they might sit on 5 to 10 other boards, so they’re not going to remember everything you talked about last meeting.) Then tee-up a discussion using techniques such as: (i) making a proposal and asking for feedback, (ii) outlining three options (if you really can’t decide) and requesting input on them, or (iii) asking three questions that will help you make the decision. Be authentic. Don’t propose three options if two are patently absurd. This wastes the board’s time and they’ll see through it.
  5. ATFQ (answer the effing question). If, at any time during the meeting, the board asks you a question: answer it. Read this — among the top five Kellblog posts of all time — for advice on how to do so. If asked for your opinion, offer it. Don’t stare at the CEO and then toe the company line. The board is fully aware of the disagree-and-commit principle. They assume you’re committed. They’re asking if you agree.
  6. Ask for relevant follow-up meetings. If you’re the CRO and one of your directors is a former-CRO, ask them for an offline meeting to discuss a hot sales-related topic. While you should spend most of that meeting discussing the advertised topic, you should take a bit of time to get to know each other and start building a relationship. Invite them to a coffee if you can, as opposed to a Zoom. Drive to their office if they invite you.

If you follow this advice, you’ll make a better impression on your board than most and you’ll start to leverage board meetings to set up offline conversations that will hopefully lead to a few career-long and career-changing relationships.

As CJ Gustafson replied when we discussed the idea of building relationships, “oh, you could find a relationship like Scorsese and DiCaprio.” Yes, exactly. That worked out pretty well for both of them.

The Ten Most Read Kellblog Posts in 2024

It’s always fun to go back and look at my stats, and my best-of page (which amazingly came in at #11) is getting sufficiently long that I need to find additional summarization mechanisms.

So this year, I thought I’d share the top-ten Kellblog posts of 2024 (year to date) regardless of the year in which they were written.

  1. Kellblog predictions for 2024. My tenth annual predictions post topped the list. I’m already working on my 2025 predictions which I hope to publish before the end of December.
  2. What it really means to be a manager, director, or VP. Written in 2015, this continues to be a top post every year and, as a result, is the all-time #1 Kellblog post.
  3. The top 7 marketing metrics for a QBR or board meeting. A 2023 post I wrote after a friend asked: “blank slate, what 5 metrics would you present to the board?” I cheated and did 7.
  4. The key to dealing with senior executives: answer the question. Another perennial favorite, this 2012 post is the one people mention to me the most. Think: “I forwarded that to my team!”
  5. The one question to ask before blowing up your customer success team. The first 2024 post on the list, I wrote this to encourage people to take a minute before Slootmanizing their CS department.
  6. Demystifying the growth-adjusted enterprise value to revenue multiple. This 2024 post explains the metric and, in a quest for syllabic parsimony, suggests naming it the ERG ratio, after the PEG ratio.
  7. Go-to-market troubleshooting, let’s take it from the top. If you’re chronically missing new bookings plan, then read this 2024 post and listen to the SaaS Talk episode that covers it.
  8. Target pipeline coverage is not the inverse of win rate. I saw one too many people invert their win rate to set pipeline coverage targets and wrote this 2024 post to show them the error of their ways.
  9. Simplifiers go far, complexifiers get stuck. This classic from 2015 starts with a poignant joke. Question: What does a complexifier call a simplifier? Answer: Boss. Learn why by reading it.
  10. Playing to win vs. playing to make plan: the two very different worlds of Silicon Valley. This 2024 post explores how the valley has fractured into somewhat distinct VC- and PE-backed worlds.

Keep an eye out for my 2025 predictions later this month. And thanks for reading.

Please God, Don’t Run Your Own Race

Of all the dime-store clichés that pass for business strategy, the one I hate the most is, “run your own race.”

Why?

  • As a quote from the winner, it’s almost always survivor bias. “How’d I win? Well, I ran my own race.” Well, I’m sure most of the losers ran their own race too, but nobody’s interviewing them for pearls of wisdom.
  • It’s frequently used to imply that you should ignore the competition. “Oh, I didn’t worry too much about the other runners, I just ran my own race and stuck to the plan.” The part they leave out is that the plan was designed to beat the other runners. Sticking to the plan was all about the other runners, even if reacting their every move wasn’t part of it.
  • It sounds oh-so-good to say. So focused. So above the fray. So wise. So unencumbered by the competitive market. And it paints such a pretty picture: just run your own race, don’t get tangled up in distractions, and you will win.

Look, it’s not a bad response to an interview question. It’s arguably a very good one. But it’s rotten management advice. “Run your own race” isn’t strategy. It’s solipsism.

Sure, if you’re running a race recreationally, by all means run your own race and I hope you have a great time.

But if you’re in business, if you’re running a startup and trying to apply this advice, then you need to consider yourself an elite competitor. You are running to win. So, if running your own race means sticking to your race plan, and that race plan is a plan to win and one that you can execute, then go ahead and run your own race. Because, by transitivity, it is a plan to win. Which is one definition of strategy.

One thing I dislike is when great executives from great companies who were in unique situations talk about “running your own race” as if everybody should. Don’t be too focused on the competition. Just focus on customers. The rest will take care of itself.

And it will — if you’re, e.g., Tableau and it’s 2010. They had an amazing product, a great team, a greenfield market — and virtually no viable competitors. They ran their own race for a long time, and it worked. But just because they could run their own race doesn’t mean that you can run yours. If you’re the number four vendor in a high-switching cost, platform market, then running your own race is more dangerous than being an Alaskan crab fisherman.

In some deep vertical SaaS markets, I’ve found companies that can ignore the competition and run their own race. That’s either because there is no competition or it’s a handful of low-growth, bootstrapped companies in a space where everyone can achieve their objectives without smacking into each other too much. (Think: there’s enough market here for everyone.)

But if you don’t happen to be in that situation. If you’re VC-backed, you’re definitionally playing to win. If you’re PE-backed you’re either playing to win or playing to make plan. (Or win, if you define “winning” as making the plan that gets your investors a 3x in 4-6 years.)

Startups are a competitive sport. Exciting new spaces attract numerous brilliant teams to fight for the emerging market. Too many retired executives forget this, preferring to dish out nostalgia over practical advice. Markets are composed of deals and deals are often streetfights. There’s big money at stake in Silicon Valley startups and lots of management teams come playing to win. Don’t bring a knife to a gunfight.

This is not the environment to run your own race, focus on your world-changing vision, and ignore the competition. This is the environment that calls for strong execution of competitive strategy to win deals and company strategy to overcome your largest obstacles.

Sure, you can run your own race. As long as your plan is the plan to win and within your ability to execute. Then go right ahead. Otherwise, make a new race plan.