Triple Book Short: For Parents

People who know me know that I am a voracious reader.  Among other things, I probably read about 25-30 books per year — and I wish I had time for more.  I probably read about 50% business books, which I blog about.  Most of my other reading is in a couple specific topical areas that interest me like American History and Evolutionary Biology.  Over the last few years, Mariquita and I have discovered and read a handful of books about parenting that have been foundational for us as we work deliberately at raising our three kids, and two of them have roots in some of the same philosophies, psychologies, and research as a lot of contemporary business literature.  So for parents everywhere, I thought I’d devote a book short to these three books.

The first one is Healthy Sleep Habits, Happy Child, by Marc Weissbluth.  Having kids who sleep long and well has been the foundation for us to have a well functioning household.  Well rested kids are much easier than tired ones.  Well rested parents are more effective.  We have found that the principles in this book have consistently served us well on this front.  All three of our kids more or less slept through the night starting at 6-8 weeks and have been great sleepers since then.

Unconditional Parenting, by Alfie Kohn is basically, for those in the HR/OD field, “Action/Design” for parenting.  The principles in this book have applied to kids as young as 1 year old, and the examples in the book go through the teenage years.  Our main learnings from this book have been around moving away from more traditional forms of reward, punishment, and control and towards helping our kids make decisions as opposed to follow directions by understanding our kids perspective on things, working to help them articulate their own understanding of a situation, and helping them see the perspective of others.

Raising an Emotionally Intelligent Child, by John Gottman, builds on a lot of the same underlying work that Daniel Goleman writes about in articles and business books around Emotional Intelligence (in fact, Goleman wrote the forward to this book as well).  The book lays out a process the author calls Emotional Coaching to help kids learn empathy and problem solving by showing kids empathy, teaching them to understand and label their own emotions, and working with them to craft solutions on their own, but doing the whole process in a very calm and 1:1 manner.  One of my favorite parts of the book, which is so unusual in business books and any kind of self-help book, is that the author has a whole section devoted to when NOT to use this process.

Parenting is a very personal thing, and there isn’t a right or wrong way to go about it.  I have a friend who is fond of saying that parenting is a little bit like the way comedian George Carlin used to describe “other drivers” on the highway.  People who are going slower than you are “a**holes” and people who are going faster than you are “crazy.”  Only you drive the “right way.”  So true, but if you’re a parent, there’s no more important thing to be deliberate about practicing than parenting, and these books have been a good practice guide for us.  We have found a full read of these three books to be very helpful to us in our work with our kids, and we have been very lucky that our main babysitter has been aligned with us on philosophy (and has been willing to read these books with us).

Book Short:  Steve Jobs and Lessons for CEOs and Founders

First, if you work in the internet, grew up during the rise of the PC, or are an avid consumer of Apple products, read the Walter Isaacson biography of Steve Jobs (book, kindle).  It’s long but well worth it.

I know much has been written about the subject and the book, so I won’t be long or formal, but here are the things that struck me from my perspective as a founder and CEO, many taken from specific passages from the book:

• In the annals of innovation, new ideas are only part of the equation. Execution is just as important.  Man is that ever true.  I’ve come up with some ideas over the years at Return Path, but hardly a majority or even a plurality of them.  But I think of myself as innovative because I’ve led the organization to execute them.  I also think innovation has as much to do with how work gets done as it does what work gets done.

• There were some upsides to Jobs’s demanding and wounding behavior. People who were not crushed ended up being stronger. They did better work, out of both fear and an eagerness to please.  I guess that’s an upside.  But only in a dysfunctional sort of way.

• When one reporter asked him immediately afterward why the (NeXT) machine was going to be so late, Jobs replied, “It’s not late. It’s five years ahead of its time.”  Amen to that.  Sometimes product deadlines are artificial and silly.  There’s another great related quote (I forget where it’s from) that goes something like “The future is here…it’s just not evenly distributed yet.”  New releases can be about delivering the future for the first time…or about distributing it more broadly.

• People who know what they’re talking about don’t need PowerPoint.”  Amen.  See Powerpointless.

• The mark of an innovative company is not only that it comes up with new ideas first, but also that it knows how to leapfrog when it finds itself behind.  This is critical.  You can’t always be first in everything.  But ultimately, if you’re a good company, you can figure out how to recover when you’re not first.  Exhibit A:  Microsoft.

• In order to institutionalize the lessons that he and his team were learning, Jobs started an in-house center called Apple University. He hired Joel Podolny, who was dean of the Yale School of Management, to compile a series of case studies analyzing important decisions the company had made, including the switch to the Intel microprocessor and the decision to open the Apple Stores. Top executives spent time teaching the cases to new employees, so that the Apple style of decision making would be embedded in the culture.  This is one of the most emotionally intelligent things Jobs did, if you just read his actions in the book and know nothing else.  Love the style or hate it – teaching it to the company reinforces a strong and consistent culture.

• Some people say, “Give the customers what they want.” But that’s not my approach. Our job is to figure out what they’re going to want before they do. I think Henry Ford once said, “If I’d asked customers what they wanted, they would have told me, ‘A faster horse!’” People don’t know what they want until you show it to them. That’s why I never rely on market research. Our task is to read things that are not yet on the page.  There’s always a tension between listening TO customers and innovating FOR them.  Great companies have to do both, and know when to do which.

• What drove me? I think most creative people want to express appreciation for being able to take advantage of the work that’s been done by others before us. I didn’t invent the language or mathematics I use. I make little of my own food, none of my own clothes. Everything I do depends on other members of our species and the shoulders that we stand on. And a lot of us want to contribute something back to our species and to add something to the flow. It’s about trying to express something in the only way that most of us know how—because we can’t write Bob Dylan songs or Tom Stoppard plays. We try to use the talents we do have to express our deep feelings, to show our appreciation of all the contributions that came before us, and to add something to that flow. That’s what has driven me.  This is perhaps one of the best explanations I’ve ever heard of how creativity can be applied to non-creative (e.g., most business) jobs.  I love this.

My board member Scott Weiss wrote a great post about the book as well and drew his own CEO lessons from it – also worth a read here.

Appropos of that, both Scott and I found out about Steve Jobs’ death at a Return Path Board dinner.  Fred broke the news when he saw it on his phone, and we had a moment of silence.  It was about as good a group as you can expect to be with upon hearing the news that an industry pioneer and icon has left us.  Here’s to you, Steve.  You may or may not have been a management role model, but your pursuit of perfection worked out well for your customers, and most important, you certainly had as much of an impact on society as just about anyone in business (or maybe all walks of life) that I can think of.

Book Short:  a Corporate Team of Rivals

One of the many things I have come to love about the Christmas holiday every year is that I get to go running in Washington DC.  Running the Monuments is one of the best runs in America.  Today, at my mother-in-law’s suggestion, I stopped i8n at the Lincoln Memorial mid-run and read his second inaugural address again (along with the Gettysburg Address).  I had just last week finished Doris Kearns Goodwin’s Team of Rivals:  The Political Genius of Abraham Lincoln, and while I wasn’t going to blog about it as it’s not a business book, it’s certainly a book about leadership from which any senior executive or CEO can derive lessons.

Derided by his political opponents as a “second-rate Illinois lawyer,” Lincoln, who arrived somewhat rapidly and unexpectedly on the national scene at a time of supreme crisis, obviously more than rose to the occasion and not only saved the nation and freed the slaves but also became one of the greatest political leaders of all time.  He clearly had his faults — probably at the top of the list not firing people soon enough like many of his incompetent Union Army generals — but the theme of the book is that he had as one of his greatest strengths the ability to co-opt most of his political rivals and get them to join his cabinet, effectively neutering them politically as well as showing a unity government to the people.

This stands in subtle but important contrast to George Washington, who filled his cabinet with men who were rivals to each other (Hamilton, Jefferson) but who never overtly challenged Washington himself.

Does that Team of Rivals concept — in either the Lincoln form or the Washington form — have a place in your business?  I’d say rarely in the Lincoln sense and more often in the Washington sense.

Lincoln, in order to be effective, didn’t have much of a choice.  Needing regional and philosophical representation on his cabinet at a time of national crisis, bringing Seward, Chase, and Bates on board was a smart move, however much a pain in the ass Chase ended up being.  There certainly could be times when corporate leadership calls for a representative executive team or even Board, for example in a massive merger with uncertain integration or in a scary turnaround.  But other than extreme circumstances like that, the Lincoln model is probably a recipe for weak, undermined leadership and heartache for the boss.

The Washington model is different and can be quite effective if managed closely.  One could argue that Washington didn’t manage the seething Hamilton and frothy Jefferson closely enough, but the reality is that the debates between the two of them in the founding days of our government, when well moderated by Washington, forged better national unity and just plain better results than had Washington had a cabinet made up of like-minded individuals.  As a CEO, I love hearing divergent opinion on my executive team.  That kind of discussion is challenging to manage — at least in our case we don’t have people at each other’s throats — but as long as you view your job as NOT to create compromises to appease all factions but instead to have the luxury of hearing multiple well articulated points of view as inputs to a decision you have to make, then you and your company end up with a far, far better result.

Book Short:  Best Book Ever

The Hard Thing About Hard Things, by Ben Horowitz, is the best business book I’ve ever read.  Or at least the best book on management and leadership that I’ve ever read.  Period.

It’s certainly the best CEO book on the market.  It’s about 1000 times better than my book although my book is intended to be different in several ways.  I suppose they’re complementary, but if you only had time left on this planet for one book, read Ben’s first.

I’m not even going to get into specifics on it, other than that Ben does a great job of telling the LoudCloud/Opsware story in a way that shows the grit, psychology, and pain of being an entrepreneur in a way that, for me, has previously only existed in my head.

Just go buy and read the book.

Book short:  Life Isn’t Just a Wiki

One of the best things I can say about Remote: Office Not Required,  by Jason Fried and David Heinemeier Hansson, is that it was short.  That sounds a little harsh – part of what I mean is that business books are usually WAY TOO LONG to make their point, and this one was blessedly short.  But the book was also a little bit of an angry rant against bad management wrapped inside some otherwise good points about remote management.

The book was a particularly interesting read juxtaposed against Simon Sinek’s Leaders Eat Last which I just finished recently and blogged about here, which stressed the importance of face-to-face and in-person contact in order for leaders to most effectively do their jobs and stay in touch with the needs of their organizations.

The authors of Remote, who run a relatively small (and really good) engineering-oriented company, have a bit of an extreme point of view that has worked really well for their company but which, at best, needs to be adapted for companies of other sizes, other employee types, and other cultures.  That said, the flip side of their views, which is the “everyone must be at their cubicle from 9 to 5 each day,” is even dumber for most businesses these days.  As usual with these things, the right answer is probably somewhere in between the extremes, and I was reminded of the African proverb, “If you want to go fast, go alone. If you want to go farm go together” when I read it.  Different target outcomes, different paths.

I totally agree with the authors around their comments about trusting employees and “the work is what matters.”  And we have a ton of flexibility in our work at Return Path.  With 400 people in the company, I personally spend six weeks over the summer working largely remote, and I value that time quite a bit.  But I couldn’t do it all the time.  We humans learn from each other better and treat each other better when we look at each other face to face.  That’s why, with the amount of remote work we do, we strongly encourage the use of any form of video conferencing at all times.  The importance of what the authors dismiss as “the last 1 or 2% of high fidelity” quality to the conversation is critical.  Being in person is not just about firing and hiring and occasional sync up, it’s about managing performance and building relationships.

Remote might have been better if the authors had stressed the value that they get out of their approach more than ranting against the approaches of others.  While there are serious benefits of remote work in terms of cost and individual productivity (particularly in maker roles), there are serious penalties to too much of it as well in terms of travel, communication burden, misunderstandings, and isolation.  It’s not for everyone.

Thanks to my colleague Hoon Park for recommending this to me.  When I asked Hoon what his main takeaway from the book was, he replied:

The importance of open communication that is archived (thus searchable), accessible (transparent and open to others) and asynchronous (doesn’t require people to be in the same place or even the same “timespace”).  I love the asynchronous communication that the teams in Austin have tried: chatrooms, email lists (that anyone can subscribe to or read the archives of), SaaS project management tools. Others I would love to try or take more advantage of include internal blogs (specifically the P2 and upcoming O2 WordPress themes; http://ma.tt/2009/05/how-p2-changed-automattic/), GitHub pull requests (even for non-code) and a simple wiki.

These are great points, and good examples of the kinds of systems and processes you need to have in place to facilitate high quality, high volume remote work.

Book Short:  Sloppy Sequel

SuperFreakonomics, by Steven Levitt and Stephen Dubner, wasn’t a bad book, but it wasn’t nearly as good as the original Freakonomics, either.  I always find the results of “naturally controlled experiments” and taking a data-driven view of the world to be very refreshing.  And as much as I like the social scientist versions of these kinds of books like Malcolm Gladwell’s The Tipping Point and Blink (book; blog post), there’s usually something about reading something data driven written by a professional quant jock that’s more reassuring.

That’s where SuperFreakonomics fell down a bit for me.  Paul Krugman has described the book in a couple different places as “snarky and contrarian.”  I typically enjoy books that carry those descriptors, but this one seemed a bit over the top for economists — like a series of theories looking for data more than raw data adding up to theories.Nowhere is this more true than the chapter on climate change.  It’s a shame that that chapter seems to be swallowing up all the public discussion about the book, because there are some good points in that chapter, and the rest of the book is better than that particular chapter, but such is life.

As with all things related to the environment, I turned to my friend Andrew Winston’s blog, where he has a good post about how the authors kind of miss the point about climate change…and he also has a series of links to other blog posts debunking this one chapter.  If you’re into the topic, or if you read the book, follow the chain here for good reading.  My conclusion about this chapter, being at least somewhat informed about the climate change debate, is that the book seems to have sloppy writing and editing at best, possibly deliberately misleading at worst.  (Incidentally, the reaction in the blogosphere seems highly emotional, other than Andrew’s, which probably doesn’t serve the reactors well.)

But I’ll assume the best of intentions.  Some of the points made aren’t bad – there is no debate about the problem or the need to solve it, the authors express legitimate concern that current solutions, especially those requiring behavioral change, will be too little too late, and most interestingly, they show an interest in alternative approaches like geo-engineering.  I hadn’t been familiar with that topic at all, but I’m now much more interested in it, not because it’s a “silver bullet” approach to dealing with climate change, but because it’s a different approach, and complex problems like climate change deserve to have a wide range of people working on multiple types of solutions.  I met Nathan Myhrvold once (I almost threw up on him during a job interview, which is another story for another day), and it makes me very happy that his brilliance is being applied to this problem as a general principle.

As I said, though, beyond this one chapter, the book is good-not-great.  But it certainly is chock full of cocktail party nuggets!

Book Short:  Required Reading, Part II

Every once in a while, a business book nails it from all levels.  Well written, practical, broadly applicable to any size or type of organization, full of good examples, full of practical tables and checklists.   The Leadership Pipeline, which I wrote about here over six years ago, is one of those books — it lays out in great and clear detail a framework for understanding the transition from one level to another in an organization and how work behaviors must change in order for a person to succeed during and on the other side of that transition.  In an organization like Return Path‘s which is rapidly expanding and promoting people regularly, this is critical.  We liked the book so much that we have adopted a lot of its language and have built training courses around it.

The book’s sequel, The Performance Pipeline (book, Kindle), also by Stephen Drotter but without the co-authors of the original book, is now out — and it’s just as fantastic.  The book looks at the same six level types in an organization (Enterprise Manager, Group Manager, Business Manager, Functional Manager, Manager of Managers, Manager of Others, and Self Managers/Individual Contributors) and focuses on what competencies people at each level must have in order to do their jobs at maximum effectiveness — and more important, in order to enable the levels below them to operate in an optimal way.

This book is as close to a handbook as I’ve ever seen for “how to be a CEO” or “how to be a manager.”  Coupled with its prequel, it covers the transition into the role as well as the role itself, so “how to become a CEO and be a great one.”  As with the prequel, the author also takes good care to note how to apply the book to a smaller organization (from the below list, usually the top three levels are combined in the CEO, and often the next two are combined as well).  No synopsis can do justice to this book, but here’s a bit of a sense of what the book is about:

• Enterprise Manager:  role is to Perpetuate the Enterprise and develop an Enterprise-wide strategic framework – what should we look like in 15-20 years, and how will we get the resources we need to get there?
• Group Manager:  role is to manage a portfolio of businesses and develop people to run them
• Business Manager:  role is to optimize short- and long-term profit and develop business-specific strategies around creating customer and stakeholder value
• Functional Manager:  role is to drive competitive advantage and functional excellence
• Manager of Managers:  role is to drive productivity across a multi-year horizon, and focus
• Manager of Others:  role is to enable delivery through motivation, context setting, and talent acquisition
• Self Managers/Individual Contributors:  role is to deliver and to be a good corporate citizen

I could write more, but there’s too much good stuff in this book to make excerpts particularly useful.  The Performance Pipeline is another one of those rare – “run, don’t walk, to buy” books.  Enjoy.  For many of my colleagues at RP – look out – this one is coming!

Book Short:  Scrum ptious 

I just finished reading Scrum: The Art of Doing Twice the Work in Half the Time, by Jeff Sutherland and JJ Sutherland. This reading was in anticipation of an Agile Facilitation training my executive team and I are going through next week, as part of Return Path’s  Agile Everywhere initiative. But it’s a book I should’ve read along time ago, and a book that I enjoyed.

Sutherland gets credit for creating the agile framework and bringing the concept scrum to software development over 20 years ago. The book very clearly lays out not just the color behind the creation of the framework, and the central tenets of practice again, but also clear and simple illustrations of its value and benefits.  And any book that employs the Fibonacci series and includes Theodore Roosevelt’s “Man in the Arena” quote — my all-time favorite — is off to a good start by me.

I’ve always appreciated a lot of the underlying philosophy of Agile, such as regularly checking on projects, course correcting in response to feedback from customers or other stakeholders, and working hard to remove any impediments to progress in real time.

One of the author’s most poignant points is that “multitasking makes you stupid.”  I hadn’t focused in the past how agile allows you to clear away context shifts to focus on one task at a time, but that’s another great take away from the book.

Our Agile Everywhere initiative, which is designed to improve productivity across the organization, as well as increase accountability through transparency, is even more critical in my view after having read this book.

The thing that I am left struggling with, which is still very much a work in progress for us, and hopefully something that we will address more head on in our training next week, is the application of the agile framework to teams that are not involved in the production of a tangible work product, such as executive or other leadership teams.  That is something that our Agile Everywhere deployment team has developed a theory about, but it still hasn’t entirely sunk in for me.

I can’t wait for next week’s training session!  If you have any experience applying the agile framework to different types of teams in your company I’d love to hear more about it in the Comments.

5 Ways to Get Your Staff on the Same Page

[This post first appeared as an article in Entrepreneur Magazine as part of a new series I’m publishing there in conjunction with my book, Startup CEO:  A Field Guide to Scaling Up Your Business]

When a major issue arises, is everybody at your company serving the same interests? Or is one person serving the engineering team, another person serving the sales team, one board member serving the VC fund, another serving the early-stage “angels” and another serving the CEO? If that’s the case, then your team is misaligned. No individual department’s interests are as important as the company’s.

To align everyone behind your company’s interests, you must first define and communicate those goals and needs. This requires five steps:

1. Define the mission. Be clear to everyone about where you’re going and how you’re going to get there (in keeping with your values).
2. Set annual priorities, goals, and targets. Turn the broader mission into something more concrete with prioritized goals and unambiguous success metrics.
3. Encourage bottom-up planning. You and your executive team need to set the major strategic goals for the company, but team members should design their own path to contribution. Just be sure that you or their managers check in with them to assure that they remain in synch with the company’s goals.
4. Facilitate the transparent flow of information and rigorous debate. To help people calibrate the success, or insufficiency, of their efforts, be transparent about how the organization is doing along the way. Your organization will make better decisions when everyone has what they need to have frank conversations and then make well-informed decisions.
5. Ensure that compensation supports alignment (or at least doesn’t fight it). As selfless as you want your employees to be, they’ll always prioritize their interests over the company’s. If those interests are aligned – especially when it comes to compensation – this reality of human nature simply won’t be a problem.

Taken in sequence, these steps are the formula for alignment. But if I had to single out one as the most important, it would be number 5: aligning individual incentives with companywide goals.

It’s always great to hear people say that they’d do their jobs even if they weren’t paid to, but the reality of post-lottery-jackpot job retention rates suggests otherwise. You, and every member of your team, “work” for pay. Whatever the details of your compensation plan, it’s crucial that it aligns your entire team behind the company’s best interests.

Don’t reward marketers for hitting marketing milestones while rewarding engineers to hit product milestones and back office personnel to keep the infrastructure humming. Reward everybody when the company hits its milestones.

The results of this system can be extraordinary:

• Department goals are in alignment with overall company goals. “Hitting product goals” shouldn’t matter unless those goals serve the overall health of your company. When every member of your executive team – including your CTO – is rewarded for the latter, it’s much easier to set goals as a company. There are no competing priorities: the only priority is serving the annual goals.
• Individual success metrics are in alignment with overall company success metrics. The one place where all companies probably have alignment between corporate and departmental goals is in sales. The success metrics that your sales team uses can’t be that far off from your overall goals for the company. With a unified incentive plan, you can bring every department into the same degree of alignment. Imagine your general counsel asking for less extraneous legal review in order to cut costs
• Resource allocation serves the company, rather than individual silos. If a department with its own compensation plan hits its (unique) metrics early, members of that team have no incentive to pitch in elsewhere; their bonuses are secure. But if everyone’s incentive depends on the entire company’s performance, get ready to watch product leads offering to share developers, unprompted.

This approach can only be taken so far: I can’t imagine an incentive system that doesn’t reward salespeople for individual performance. And while everyone benefits when things go well, if your company misses its goals, nobody should have occasion to celebrate. Everybody gets dinged if the company doesn’t meet its goals, no matter how well they or their departments performed. It’s a tough pill to swallow, but it also important preventive medicine.

Book Short:  Unsung Heroes

If you like “entrepreneurship by analogy” books, you’ll like The Innovators:  The Engineering Pioneers Who Made America Modern, by David Billington.  I have to admit some bias here — Professor Billington was my favorite teacher and senior thesis advisor at Princeton (I almost majored in civil engineering because of him), and this book is one of a number he’s written that are outgrowths of his most popular courses at Princeton.  And while there’s no substitute for the length or energy of his lectures, the book works.

The book is basically a person-focused engineering history of America from 1776-1883.  Billington talks about four classes of engineering product:  public structures (mostly bridges), machines that produced power, networks like the railroads and telegraphs, and processes like steel manufacturing.

His approach is to acknowledge that the Americans innovators couldn’t do much without the right context:  learnings from their counterparts in Britain, a supportive government here at home, and abundant raw materials and capital.  But with that backdrop in place, Billington tells the tale of a number of the inventions that built our modern society with a focus on the engineers who got things right.  While some of them are familiar names (Morse, Edison), many are not (Thomas Telford, J. Edgar Thomson, Joseph Henry).

Sound familiar?  It feels at many point in the book that you could insert some different names and dates and be reading a history of the Internet or information age.  And as with the Industrial Revolution, while many of the innovators in our world today are known (Bezos, Yang, Brin/Page), there are probably an equal number who are unsung heroes — either software engineers or even buisness model pioneers who haven’t sought or won’t end up in the spotlight even though their contributions to society or to their companies are giant.  I know there are a number of unsung heroes in our own engineering department at Return Path — people who aren’t market facing and who never get quoted in press releases, but who really make a difference in how the company works and how competitive we are.  This book celebrates those people as much as it does the entrepreneurs you’ve heard of.

Warning, there are lots of pages which are full of mathematical formulas, which may or may not be interesting to you, but the book still holds together 100% if you skip over them.

I enjoy reading books written by people I know. I can always picture the person narrating the book, or hear their voice saying the words, I can periodically see their personality showing through the words on the page, and books bring out so much more detail than I’d ever get from a conversation. Loved: How to Rethink Marketing for Tech Products, by Martina Lauchengco, is one of those books. Martina is an operating partner at Costanoa Venture Capital, an investor in both Return Path and Bolster, and I’d known Martina for several years before she joined Costanoa through Greg Sands. She’s the best product marketer on the planet. She’s the also one of the nicest people around.

Product Marketing is a tricky discipline. A brand marketer on my leadership team years ago referred to it somewhat derisively as a “tweener” function, one of those things that’s not quite marketing and not quite product. We didn’t get the function right for many years at Return Path because we treated it that way, thinking “well, it’s neither fish nor fowl, so we’re not quite sure what to do with it.” Then we hired Scott Roth, who has gone on to have a storied career as a multi-time CEO. Scott’s background was in product marketing. He said to me in his interview process, “Product Marketing isn’t a tweener function with no home. It’s a glue function. It holds product and marketing together.” It’s amazing how that simple change in framing, combined with great leadership, led us to completely rethink the function and make it one of the most important functions in the company.

Martina brings that to live with Loved. Simply put, Loved is a handbook or a field guide to running the Product Marketing function. I can imagine it being a section of Startup CXO in that way — it’s incredibly practical, hands-on, how-to, and rich with examples from Martina’s amazing career at Microsoft, Netscape, Silicon Valley Product Group, and Costanoa. And she believes in Agile Marketing, which is always a plus in my book (and I find rare in marketers).

Martina has lots of great frameworks and stories in the book – key responsibilities of product marketing, key metrics, the release scale, the connection to Geoffrey Moore’s TALC, strategies for messaging, pricing and packaging, and more. I won’t spoil more than one here, but I will paraphrase one that I found particularly impactful, a bit of a checklist on the essence of great product marketing:

• Share data around shifting trends in buyer behavior
• Connect your product’s purpose with broader trends
• Rebrand to make your product seem bigger than it is (and save room for expansion down the road)
• Make it free, especially if you’re defining a new category
• Share the “why” and advance access with influencers

If the measure of a book’s impact is how many pages you dog ear or highlight, this says it all about Loved.