Slides from Five Ways to Get Product and Marketing Working Together

Last week in London, fellow Balderton EIR David Vismans and I held a joint meeting to discuss the working relationship (or moreover, the lack thereof) between product and marketing organizations.

David is a career product leader, who worked for over 8 years leading product at Booking.com.  I am a former CEO and CMO who still considers himself to have 100% marketing DNA.  So, we were both well able to represent our functions.  Additionally, because I am a B2B person and David is mostly a B2C person that added another dimension of difference for us to explore.

In the session, which was held as an interactive workshop for Balderton portfolio companies, we described the problem, shared a few war stories as examples, and then discussed the five things companies can do to get their product and marketing teams working better together.

  • Foster a culture of collaboration and respect.  This begins at the top.  Do not apply the old adage that “good fences make good neighbors,” and wall the teams off from each other.  (David had a great story where security literally kept them from visiting each other’s floors.)  Instead, do what we say in point 3, below.
  • Drive together for both PMF and PCF (product-channel fit), an idea that David brought.  This means the teams should work together to build and sell a product that solves a problem for a person (i.e., my definition of PMF) in conjunction with finding a way to economically reach that person (i.e., PCF).  David provided a few examples where he believes you could get PMF fairly easily (e.g., a hotel booking site for people traveling with dogs or who need chargers for electric cars), but have a hard time economically finding customers due to the need to compete with large vendors for contested search terms in paid channels.
  • Build a high-level interaction model.  That sounds fancy but it just means make a one-page table with three rows:  lifecycle phase, product responsibilities, and marketing responsibilities.  Taking the time to make this – typically done in a few meetings of a working group — sets expectations on both sides.  It avoids the common problem of ten people bringing expectations from ten different prior employers, which usually results in everyone being disappointed all the time.
  • Adapt your model with stage and scale.  We both like the Ansoff matrix and David uses it as a framework to adapt the product/marketing collaboration model.  He argues that the more you’re in “keep on keeping on” mode (box 1), the more is known, and the higher the fence between product and marketing can be.  But in boxes 2 and 3 you are working with one unknown dimension and that requires more collaboration.  Box 4, where both product and market unknown, is basically like starting a new company and requires maximum collaboration. (I largely, but not entirely, agree. My primary argument being that in Box 1, marketing will be more focused on features to differentiate and win deals than product usually is.)
  • When it comes time for your second album, don’t forget your roots.  I think as companies grow they forget how they innovated in the past, they forget the processes they used in the early days and end up, for example, localizing a new product into 10 languages on its initial release – because that’s what we do now with all products.   

Thanks to everyone who attended the session.  I’ve embedded the slides below.  They are available in PDF here (so the links on the resources page work).  Balderton is producing a summary of the event as well, which I’ll link to once it’s up.

Do Superachievers Read Business Books?

I spoke a while back on go-to-market scaling at the 10X CEO Accelerate conference in Deer Valley to about eighty startup CEOs. I dropped a few references to popular business books into the material (e.g., Blue Ocean Strategy, Inside the Tornado, The Crux), as I often do, and discussed them quickly in passing.

This prompted a question at the end of the session that went something like this:

“You mentioned several business books in your speech.  I must admit that I don’t read a lot of business books.  I don’t have any time.  And I don’t particularly like reading.  So, my question is do superachievers actually read these books and view reading them as part of their success?”

It was a helluva good question. 

While I certainly have my own take on the answer, I must admit that I’m an information junkie who loves reading (so my view will likely be non-representative) and while I’m an achiever, I wouldn’t say I’m a superachiever. But, I thought, I know some superachievers [1] and some of them work with other superachievers [2] so I can ask for their takes and then fuse those composite opinions into a blog post [3].

Here it is.

Do Super Achievers (Actually) Read Business Books?

Before answering, let me address the fact that it’s often presented as a loaded question, where you can almost feel the word “actually” silently slipped into the phrasing. In its loaded form, the question comes implicitly packed with some of these widely-held assumptions:

  • Business books are bullshit.
  • They’re the province of professors and MBAs.
  • At best, they contain one good idea inflated into a 250-page book because you can’t sell pamphlets for $25.
  • Wannabes read business books as a way to lead their business life by proxy as opposed to putting it all on the playing field.

To the extent you can view attitudes about MBAs as representative of attitudes towards business books [4], you can feel a further lack of love.

“As much as possible, avoid hiring MBAs.  Our position is that we hire someone in spite of an MBA, not because of one.” — Elon Musk

“Never, ever hire an MBA.  They will ruin your company.” — Peter Thiel

“When it comes to success in business, the MBA degree is optional.  But a GSD, which is only earned by getting shit done, is required.” — Christine Comaford

Overall, there is a strong sentiment in Silicon Valley that the best teacher is doing.  Then again, there is also a strong sentiment that failure is a better teacher than success, yet in 35 years I have never seen a single job specification that listed any form of failure as required experience.  Strong sentiment and action are seemingly two different things.

Now, let’s directly answer the question:  do superachievers read business books?

Remembering that there is no single mold of superachiever, I think the answer is:

  • Yes, but not religiously.
  • And they really like to read broader books as well.

I think the driving philosophies behind this are:

  • The realization that most business books really are one good idea inflated to 250 pages.  So, if they can learn the basics of a good idea without having to read the full 250 pages, then all the better. Superachievers guard their time.
  • The point is to understand the core concepts in which fluency is required to function in Silicon Valley (e.g., The Chasm, The Innovator’s Dilemma, The Lean Startup).  There are probably about 20 of these in total and the important part is understanding the concepts, not reading the book.  Superachievers are often fast learners and self-taught.  Skimming the book, reading a summary [5], or watching a video is likely enough. 
  • It is foolish not to learn from the mistakes of others.  While skeptical of finding the universal keys to success in any book, they are more open to hearing concrete stories of success and failure.  Thus, they are less interested in pop business concept books [6] than reading real stories of successful and unsuccessful companies.
  • Superachievers want to be the best versions of themselves.  They are highly motivated for self improvement and if convinced that reading certain books will help improve their performance, they will find the time to read them. But books are just one way to improve. So are conversations with other founders — a key reason why organizations like YPO and 10X CEO do so well. So is execution education, like Stanford’s great programs. So are great podcasts (e.g., Acquired, Founders) on the treadmill.
  • It is important to step outside the all-consuming world of the startup to gain perspective.   That’s why reading world history, business history, military history, behavioral economics, sports, competition, and motivation are popular topics for superachievers. It is possible to spend too much time on the standard material. Reading more broadly is both energizing and helps you get outside the proverbial box.
  • Doing is the best teacher.  While reading is great, you need to do a lot and try a lot. Move fast and break things, as they say. The Silicon Valley way.

In short, on the question of business books, I’d say that superachievers are universally well informed, if not necessarily well read.

More broadly, I’d say that superchievers are generally well read. In Silicon Valley, this results from the energizing effect of reading non-business material often combined with some intellectual flex to demonstrate your polymath abilities. That’s why you’ll find almost certainly find authors like Daniel Kahneman, Robert Cialdini, or Sun Tzu — who write one level of indirection away from startups — on most reading lists, as well as others (e.g., Robert Heinlein, Ayn Rand, William Irvine), who write several levels beyond that.

If you can’t identify John Galt, recite the three primary beliefs of the Stoics, or reveal the Martian etymology of the word grok, then well, perhaps you’re an outsider on Sand Hill Road after all. Superachiever or not.

# # #

Notes

[1] To respect privacy, I won’t do any attribution here, but simply say that I’ve spoken with successful startup founders and with deca-, centa-, and even a kilo-millionaire (aka, billionaire) about this topic. If you’re one of those people, let me thank you again for answering my questions.

[2] For example: a top-performing VC who is a superachiever in their own right and who, by virtue of their startup work, frequently engages with other achievers and superachivers.

[3] Someone could obviously do a study here — and maybe someone already has, but I couldn’t find it — and doing one on my own is well beyond the scope of a Kellblog post.

[4] After all, you certainly do read a lot of business books in b-school.

[5] For some business authors, chapter 1 of book N is an excellent summary of book N-1 (e.g., Moore, Christensen)

[6] Which tend to argue, get this one thing right and the rest takes care of itself (e.g., Storybranding, Grit, Purple Cow). This is a weakness of many pop marketing books.

Appearance on Run The Numbers Podcast: A Startup CEO’s Guide to Board Meetings

I love writing and speaking about board meetings. Why? Because:

  • They’re critically important. Board meetings can make or break careers.
  • You get little to no instruction on how to do them. Most training for CEOs and execs is of the “throw them in the deep end of the pool and see if they float” variety.
  • You don’t get much practice. At four to six times per year, board meetings are not quite frequent enough to provide sufficient reps to drive real improvement, except over long periods of time.

So, many founders and CEOs muddle along with a series of merely good-enough board meetings, and not good ones.

I’ve written a lot about startups, boards, and CEOs. For example:

Thus, I was happy when CJ Gustafson invited me for an interview on his Run the Numbers podcast for an episode entitled A Startup CEO’s Guide to Board Meetings.

A video of the episode is embedded below. You can find it on Apple or Spotify as well.

Thanks CJ for having me.

A Friendly Reminder to Cost-Cutters: Keep the Company a Great Place to Work for Survivors

It’s been a tough year. We’re currently in peak planning season for 2024. With capital scarce and expensive, with companies increasingly trapped in Schrödinger’s startup paradox, and with more startups than ever focused on positive cashflow and The Rule of 40, it’s safe to say that Silicon Valley is still very much in a cost-cutting mood.

I’ve done a lot of cost cutting over the course of my career so I thought I’d share one key rule that sometimes gets overlooked when you’re in the thick of this process. Here’s the rule: no matter what you do, no matter how deep the cuts have to be, keep the company a great place to work for those who still work there (aka, the survivors).

Why do we forget this? As we struggle to hit top-down targets through rounds of cost-cutting, we cut here and squeeze there so much that we can develop a certain myopia. While we eventually congratulate ourselves for building a plan that finally achieves the financial targets, we often forget to sanity check that plan in two ways:

  • Achievability. Is the resultant plan even do-able? Or have incoherent cuts across departments left us close to attaining financial targets, but out of balance across functions? Are the revenue (and ergo cash collection) targets realistic? If not, the consequence is missing those targets, triggering another painful round of cuts. Always make a plan that you can beat.
  • Quality of life. What will it be like to work at the company we just created? Will the people we hope to retain want to keep working for us? Are there still free drinks in the frig? An annual company kickoff? A bonus program with non-zero expected value? More subtly, have we teed up both failure and internal warfare by overcutting marketing relative to sales? Or product relative to engineering? More simply, do we still have travel budget? Do people feel like they have the resources they need to succeed?

While this may sound basic, lots of companies mess it up. Why? Because it’s so hard to build a budget that hits the new targets in the first place, the last thing the executive team wants to do is sanity check that budget and find more problems.

In addition, the management team is likely still wedged in an incremental rather than absolute mentality — meaning that while a given function had $5M last year and needs to cut to “only” $4.5M this year (and yes, that’s after absorbing some naturally inflating costs), that $4.5M is still a heck of a lot of money and, for that matter, a lot more function budget than we had three years ago when we were in the earlier stages of building the company. To solve the latter problem, the executive team needs to first heal itself (by reframing their own thinking) and then get the rest of the management team on board with absolute rather than incremental, year-over-year thinking.

But back to quality of life. Let’s make this concrete by giving several real examples of what people get wrong:

  • No raise policy. You’re better off cutting more people in order to make room for merit increases and promotions — that is, if you really care about keeping the company a great place to work for the survivors.
  • No backfill policy. A mindless policy that basically says the C-suite can’t be bothered with headcount resource allocation and will effectively leave it to chance. And create perverse incentives to not terminate weak employees in the process.
  • Little or no travel budget. I recently spoke with a product leader with a team of about 8 PMs, none of whom were allowed to travel anymore. They’d be better off with 6 PMs and some travel budget. If you believe PMs need to meet customers to do their jobs, that is. Ditto for product marketers. Double ditto for sellers. It’s not about the travel budget per se. It’s about making the people who stay feel they can be successful.
  • Bonus targets in excess of plan targets. This is the old, “well we cut the plan but we didn’t change the bonus targets” trick and it’s simply not credible. In the end, what matters is the expected value of the bonus program to employees, and if that plan has unrealistic targets, that value quickly drops to zero. If that’s 20% of someone’s total compensation, that’s a material pay cut — and that’s certainly not keeping the company a great place for those who stay.
  • Workflation. This is the opposite of shrinkflation (e.g., the constant price for an ever-shrinking candy bar). This is where you get the same pay, but for a much bigger job. For example, if you replace managers with player-coach team leads, or if you blow up your success team and ask sellers to take on post-sales account management.
  • Killing internal events. Like it or not, wiping out the annual company kickoff or the president’s club reduces the expected value of working at the company to the employees. My advice is to cut these back, but don’t kill them.
  • Cutting supporting resources. Whether you’re cutting marketing relative to sales (and thus potentially creating a “baby robin” problem) or cutting SDRs relative to sales (putting more work on sales), or creating an imbalance by cutting product relative to engineering, you must remember that a healthy organization is a dynamic system, with interacting functions and checks and balances. Cut holistically. Instead of reducing SDR and SC support ratios across Europe, cut direct operations in a few smaller countries.

So, when you started reading this post, I’m guessing you were thinking, “oh no, we’d never do that at my company” and by the time you finished the above list you were thinking, “oh no, we did — in like three areas.” That’s why I made the list.

You can use the list to sanity check your plan or you can just derive directly from the core principle. Whenever you are cutting, always, always keep the company a great place to work for those who are going to still work there.

The alternative, frankly, is bleak. Your employees will do the last round of cuts for you — and you may not like what they decide.

The Elements of a Good Apology

After a negative customer experience on a recent fishing trip an old friend of mine said, “I judge people by the quality of their apologies.” Interesting idea, I thought.

This led to a discussion about the apology given to us by the proprietor of the ranch at which we stayed, roughly summarized as: “this only happened because it’s the end of a long, hard season, and there are things — things I can’t tell you about — that took a lot out of me.”

I, being something of a sucker, bought it — pardon the expression — hook, line, and sinker. “Oh you poor man, I hope you get through this.”

My friend, who is somewhat more skeptical, responded differently: “He didn’t really own it. He literally blamed it on something that he declared secret and couldn’t tell us about. And does that really matter anyway? Do we really care why something undesirable happened? Or do we want him to just own the mistake and apologize for it?”

This led to a conversation where I came up with these simple elements of a good apology.

  • Hear it. Let the customer talk. Hear what they say. Don’t interrupt. Don’t get defensive. Listen. When they’re done, repeat it back: “I understand that the door flew open, Fluffy flew out, and that terrified everyone.” Or, “I understand that the software repeatedly crashed and was basically unusable during your end-user onboarding session and that was horribly embarrassing for you personally and a waste of time and money for the company.”
  • Own it. Admit the mistake and say it was your fault. “I didn’t attach the schmidget properly and because of that the door flew open. It was my mistake.” In a tech context, “I’m sorry that the release was not adequately tested and caused the software to crash repeatedly during your user onboarding session.”
  • Apologize for it. Say, “I am sorry.” Don’t ask anyone to accept that apology as it feels you’re asking for absolution. You’re not. You’re apologizing.
  • Avoid deflection or transference. Don’t say, “I’m sorry that you didn’t notice the schmidget was not attached.” Or, “I’m sorry that you chose to hold your training the day after a major, new release.” Doing this is the opposite of owning it. Avoid at all costs any apology that starts with, “I’m sorry you were offended by.”
  • Optionally, say how you feel about it. “I feel terrible that your cat flew out the open door (but was happily uninjured).” Or, “I feel terrible that we hung you out to dry in front of your end users, especially after you went to bat to help us win the deal.”
  • Optionally, tell them what you’re doing about it. Some people will care about this and want to know how you’re preventing this from happening to others. Some won’t. Read the room. “I’m going to revise our departure checklist to add schmidget attachment.” Or, “I’m going to fly to India, show the team your picture, tell them how much you did to support us, and then tell them how this impacted you.” (This, by the way, is a real example and I did fly to India the next week and do precisely that.)
  • Don’t quibble over details. If it’s an online product review and it says, “the schmidget was not attached on the 20-foot vehicle,” do not reply, “our vehicles are 19 feet.” If you worry that failing to do this concedes incorrect facts, then say, “Some details notwithstanding, the important part here is the cat flew out the door, and we are deeply sorry about Fluffy and the trauma she endured.”
  • Optionally, offer compensation. Not everyone wants compensation. For some, it’s about principle. For others, it’s about ensuring future clients don’t have the same problem. For others, it’s all about compensation. For others still, it’s about putting some wood behind the apology arrow. Read the room. Ensure the compensation matches the problem: “I’m offering you a free day with our top guide on your next trip out.” If you’re unsure, you can offer in the hypothetical: “would it help if I were to offer you blank?” Avoid proposing illogical compensation: “I’ll give you two free days from the same plumber who misinstalled the pipes that flooded your house in the first place.” (No thanks!)
  • Finally, thank the customer for their business. “You are important to our company, that’s why I wanted to make this apology to you personally. And thank you for being a customer.”

I worked with a sales VP who began every customer conversation by saying, “thank you for being a customer.” It’s not a bad way to end one, either.