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.

In Search of Automated Relevance

A bunch of us had a free form meeting last week that started out as an Email Summit focused on protocols and ended up, as Brad put it, with us rolling around in the mud of a much broader and amorphous Messaging Summit.  The participants (and some of their posts on the subject) in addition to me were Fred Wilson (pre, post), Brad Feld,  Phil Hollows, Tom Evslin (pre, post), and Jeff Pulver (pre, post).  And the discussion to some extent was inspired by and commented on Saul Hansell’s article in the New York Times about “Inbox 2.0” and how Yahoo, Google, and others are trying to make email a more relevant application in today’s world; and Chad Lorenz’s article in Slate called “The Death of Email” (this must be the 923rd article with that headline in the last 36 months) which talks about how email is transitioning to a key part of the online communications mix instead of the epicenter of online communications.

Ok, phew, that’s all the background. 

With everyone else’s commentary on this subject already logged, most of which I agree with, I’ll add a different $0.02.  The buzzword of the day in email marketing is “relevance.”  So why can’t anyone figure out how to make an email client, or any messaging platform for that matter, that starts with that as the premise, even for 1:1 communications?  I think about messaging relevance from two perspectives:  the content, and the channel.

Content.  In terms of the content of a message, I think of relevance as the combination of Relationship and Context.  The relationship is all about my connection to you.  Are you a friend, a friend of a friend, or someone I don’t know that’s trying to burrow your way onto my agenda for the day?  Are you a business that I know and trust, are you a carefully screened and targeted offer coming from an affiliate of a business I trust, or are you a spammer? 

But as important as the relationship is to the relevance of your message to me, the context is equally important.  Let’s take Brad as an example.  I know him in two distinct contexts:  as one of my venture investors, and as an occasional running partner.  A message from Brad (a trusted relationship) means very different things to me depending on its context.  One might be much more relevant than the other at any moment in my life.

Channel.  The channel through which I send or receive a message has an increasing amount to do with relevance as well.  As with content, I think of channel relevance as the combination of two things –  device, and technology.  For me, the device is limited to three things, two with heavy overlap.  The first is a fixed phone line – work or home (I still think cell service in this country leaves a lot to be desired).  The second is a mobile device, which could mean voice but could also mean data.  The third is a computer, whether desktop or laptop.  In terms of technology, the list is growing by the day.  Voice call, email, IM, Skype, text message, social network messaging, and on and on.

So what  do I mean about channel relevance?  Sometimes, I want to send a message by email from my smartphone.  Sometimes I want to send a text message.  Sometimes I want to make a phone call or just leave a voicemail.  Sometimes I even want to blog or Twitter.  I have yet to desire to send a message in Facebook, but I do sometimes via LinkedIn, so I’m sure I’ll get there.  Same goes for the receiving side.  Sometimes I want to read an email on my handheld.  Sometimes a text message does the job, etc.  Which channel and device I am interested in depends to some extent on the content of the message, per above, but sometimes it depends on what I’m doing and where I am.

So what?  Starting to feel complex?  It should be.  It is.  We all adjusted nicely when we added email to our lives 10 years ago.  It added some communication overhead, but it took the place of some long form paper letters and some phone calls as well.  Now that we seem to be adding new messaging channels every couple weeks, it’s becoming increasingly difficult to get the relevance right.  Overlaying Content (Relationship and Context) with Channel (Device and Technology) creates a matrix that’s very difficult to navigate.

How do we get to a better place?  Technology has to step in and save the day here.  One of the big conclusions from our meeting was that no users care about or even know about the protocol – they just care about the client they interact with.  Where’s the ultra flexible client that allows me to combine all these different channels, on different devices?  Not a one-size-fits-all unified messaging service, but something that I can direct as I see fit?  There are glimmers of hope out there – Gmail integrating IM and email…Simulscribe letting me read my voicemail as an email…Twitter allowing me to input via email, SMS, or web…even good old eFax emailing me a fax – but these just deal with two or three cells in an n-dimensional matrix.

As our CTO Andy Sautins says, software can do anything if it’s designed thoughtfully and if you have enough talent and time to write and test it.  So I believe this “messaging client panacea” could exist if someone put his or her mind to it.  One of the big questions I have about this software is whether or not relevance can be automated, to borrow a phrase from Stephanie Miller, our head of consulting.  Sure, there is a ton of data to mine – but is there ever enough?  Can a piece of software figure out on its own that I want to get a message from Brad about “running” (whatever channel it comes in on) as a text message on my smartphone if we’re talking about running together the next day, but otherwise as an RSS feed in the same folder as the posts from his running blog, but a voicemail from Brad about “running the company” (again, regardless of how he sends it) as an email automatically sorted to the top of my inbox?  Or do I have to undertake an unmanageable amount of preference setting to get the software to behave the way I want it to behave?  And oh by the way, should Brad have any say over how I receive the message, or do I have all the control?  And does the latter question depend on whether Brad is a person or a company?

What does this mean for marketers?  That’s the $64,000 question.  I’m not sure if truly Automated Relevance is even an option today, but marketers can do their best to optimize all four components of my relevance equation:  content via relationship and context, and channel via device and technology.  A cocktail of permission, deep behavioral analysis, segmentation, smart targeting, and a simple but robust preference center probably gets you close enough.  Better software that works across channels with built-in analytics – and a properly sized and whip smart marketing team – should get you the rest of the way there.  But technology and practices are both a ways off from truly automated relevance today.

I hope this hasn’t been too much rolling around in the mud for you.  All thoughts and comments (into my fancy new commenting system, Intense Debate) are welcome!

Book Short: Hire Great

It’s certainly not hiring season for most of America The World The Universe, but we are still making some limited hires here at Return Path, and I thought – what better time to retool our interviewing and hiring process than in a relatively slow period?

So I just read Who: The A Method for Hiring, by Geoff Smart and Randy Street.  It’s a bit of a sequel, or I guess more of a successor book, to the best book I’ve ever read about hiring and interviewing, Topgrading, by Geoff Smart and his father Brad (post, link to buy).  This one wasn’t bad, and it was much shorter and crisper.

I’m not sure I believe the oft-quoted stat that a bad hire costs a company $1.5mm.  Maybe sometimes (say, if the person embezzles $1.4mm), but certainly the point that bad hires are a nightmare for an organization in any number of ways is well taken.   The book does a good job of explaining the linkage from strategy and execution straight to recruiting, with good examples and tips for how to create the linkage.  That alone makes it a worthwhile read.

The method they describe may seem like common sense, but I bet 95 out of 100 companies don’t come close.  We are very good and quite deliberate about the hiring process and have a good success average, but even we have a lot of room to improve.  The book is divided into four main sections:

• Scorecard: creating job descriptions that are linked to company strategy and that are outcome and competency based, not task based
• Sourcing: going beyond internal and external recruiters to make your entire company a talent seeker and magnet
• Selection: the meat of the book – good detail on how to conduct lots of different kinds of interviews, from screening to topgrading (a must) to focused to reference
• Sell:  how to reel ’em in once they’re on the line (for us anyway, the least useful section as we rarely lose a candidate once we have an offer out)

One of the most poignant examples in the book centered around hiring someone who had been fired from his previous job.  The hiring method in the book uncovered it (that’s hard enough to do sometimes) but then dug deep enough to understand the context and reasons why, and, matching up what they then knew about the candidate to their required competencies and outcomes for the job, decided the firing wasn’t a show-stopper and went ahead and made the hire.

I’d think of these two books the way I think about the Covey books.  If you have never read The 7 Habits of Highly Effective People, you could just get away with reading Stephen Covey’s newer book, The 8th Habit:  From Effectiveness to Greatness, though the original is much richer.

I was excited to read Launchpad Republic: America’s Entrepreneurial Edge and Why It Matters, by Howard Wolk and John Landry the minute Brad sent it to me. I love American history, I love entrepreneurship, and I’m deeply concerned about the health of our country right now. I have to say…on all fronts, the book did not disappoint!

The authors make several points, but the one that sets the tone for the book is that like our country’s origins and culture in general, entrepreneurship is itself rebellious. It’s about upstarts challenging the status quo in some way or other with a better way to do something, or with a new thing. The balance between protecting private property rights and allowing for entrepreneurs to fail and to disrupt incumbent leaders is what makes America unique, especially compared to the way European business culture has traditionally operated (consensus-oriented) and the way China operates (authoritarian).

I loved how the authors wove a number of business history vignettes together with relevant thru lines. Business in Colonial times and how Alexander Hamilton thought about national finances may seem dusty and distant, but not when you see the direct connection to John D. Rockefeller, IBM, GE, Microsoft, or Wendy Kopp.

The book was also a good reminder that some of the principles that have made America great and exceptional also underly our successful business culture, things like limited government, checks and balances within government and between government and the private sector, and decentralized finance.

Without being overly political, the authors also get into how our political and entrepreneurial system can and hopefully will tackle some of today’s more complex issues, from climate change to income inequality to stakeholder capitalism.

At the heart of all of it is the notion that entrepreneurs’ creativity drive America forward and are a leading force for making our country and our economy durable and resilient. As a career entrepreneur, and one who is now in the business of helping other entrepreneurs be more successful, this resonated. If you’re a student of American history…or a student of entrepreneurship, this is a great read. If you’re both, it’s a must read.

Half the Benefit is in the Preparation

This past week, we had what has become an annual tradition for us – a two-day Board meeting that’s Board and senior management (usually offsite, not this year to keep costs down) and geared to recapping the prior year and planning out 2009 together.  Since we are now two companies, we did two of them back-to-back, one for Authentic Response and the other for Return Path.

It’s a little exhausting to do these meetings, and it’s exhausting to attend them, but they’re well worth it.  The intensity of the sessions, discussion, and even social time in between meetings is great for everyone to get on the same page and remember what’s working, what’s not, and what the world around us looks like as we dive off the high dive for another year.

The most exhausting part is probably the preparation for the meetings.  We probably send out over 400 pages of material in advance – binders, tabs, the works.  It’s the only eco-unfriendly Board packet of the year.  It feels like the old days in management consulting.  It takes days of intense preparation — meetings, spreadsheets, powerpoints, occasionally even some soul searching — to get the books right.  And then, once those are out (the week before the meeting), we spend almost as much time getting the presentations down for the actual meeting, since presenting 400 pages of material that people have already read is completely useless.

By the end of the meetings, we’re in good shape for the next year.  But before the meetings have even started, we’ve gotten a huge percentage of the benefit out of the process.  Pulling materials together is one thing, but figuring out how to craft the overall story (then each piece of it in 10-15 minutes or less) for a semi-external audience is something entirely different.  That’s where the rubber meets the road and where good executives are able to step back; remember what the core drivers and critical success factors are; separate the laundry list of tactics from the kernel that includes strategy, development of competitive advantage, and value creation; and then articulate it quickly, crisply, and convincingly. 

I’m incredibly proud of how both management teams drove the process this year – and I’m charged up for a great 2009 (economy be damned!).

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.

5 Ways to Spot Trends That Will Make You (and Your Business) More Successful

I’ve recently started writing a column for The Magill Report, the new venture by Ken Magill, previously of Direct magazine and even more previously DMNews. Ken has been covering email for a long time and is one of the smartest journalists I know in this space. My column, which I share with my colleagues Jack Sinclair and George Bilbrey, covers how to approach the business of email marketing, thoughts on the future of email and other digital technologies, and more general articles on company-building in the online industry – all from the perspective of an entrepreneur. Below is a re-post of this week’s version, which I think my OnlyOnce readers will enjoy.

Last week I published my annual “Unpredictions” for 2011. This tradition grew out of the fact that I hate doing predictions and my marketing team loves them. So we compromise by predicting what won’t happen.

But the truth is that the annual prediction ritual – while trite – is really just trend-spotting. And trend-spotting is an important skill for entrepreneurs. Fortunately it’s a skill that can be acquired, at least it can with enough deliberate practice (another skill I talk about here).

Here are five habits you should consider cultivating if being a better trend spotter is in your career roadmap.

Read voraciously. I read about 50 books every year.  About half of them are business books, and I also mix in a bit of fiction, humor, American history, architecture and urban planning, and evolutionary biology.  I keep up with more than 50 blogs and I read all the trade publications that cover email.  I also read the Wall Street Journal and The Economist regularly.  What you read is a little less important than just reading a lot, and diversely.

Use social media (wisely). Julia Child once said that the key to success in life was having great parents. My advice to you is quite a bit simpler:  make friends with smart people. Facebook, Twitter, LinkedIn and others have given us a window into the world unlike any other. Status updates, tweets, and – maybe most important of all – links shared by your network of friends and colleagues gives you a sense of what people are talking about, thinking about and working on. And you can’t just lurk.  You actually have to be “in” to get something “out.”

Follow the money. Pay attention to where money gets invested and spent. This includes keeping an eye on venture capital, private equity, and the public markets, as well as where clients (mostly IT and marketing departments) are spending their dollars and what kinds of people they are hiring. Money flows toward ideas that people think will succeed. A pattern of investments in particular areas will give you clues to what might be the big ideas over the next five to 10 years.

Get out of the office: I think it’s hugely important for anyone in business, and especially entrepreneurs, to spend time in the world to get fresh perspectives. I’m not sure who coined the phrase, but our head of product management, Mike Mills, frequently refers to the NIHITO principle – Nothing Interesting Happens in the Office.  Now that’s not entirely true – running a company means needing to spend a huge amount of time with people and on people issues, but last year I traveled nearly 160,000 miles around the world meeting with prospect, clients, partners and industry luminaries. You don’t have to be a road warrior to get this one right – you can attend events in your local area, develop a local network of people you can meet with regularly – but you do have to get out there.

Take a break. While you need information to understand trends, you can quickly get overloaded with too much data.  Trend spotting is, in many ways, about pattern recognition. And that is often easier to do when your mind is relaxed.  Ever notice that you have moments of true epiphany in the shower or while running? Give yourself time every week to unplug and let your mind recharge. As Steven Covey says, “sharpen that saw”!

My long-time friend and former Board member Brad Feld has become a prolific writer on the startup world over the years and is the person (other than me) most responsible for me getting into that scene as well. Startup CEO is part of his Startup Revolution series, which followed me writing an essay for Do More Faster, and then writing a series of sidebars call “The Entrepreneur’s Perspective” in Venture Deals.

All Brad’s books are listed here. If you’re in the startup universe, I’d encourage you to read all of them. I’m excited to dive into his newest book, The Startup Community Way, which comes out this week from our same publisher, John Wiley & Sons. I’ve gotten part of the way through an early copy, and I love it already.

The approach Brad and his co-author Ian Hathaway take is to evolve their Boulder Thesis from the original Startup Communities book. They dive into the topic and examine it from the perspective of a complex system, which of course anything as fragmented as an ecosystem of public, private, and academic organizations is.

The book — and the whole topic, quite frankly — remind me of a great management book I read several years ago by General Stanley McChrystal called Team of Teams. Organizations have gotten more complex and have had to adapt their structures, and the most successful ones are the ones that have shifted from hierarchical structures to node-based structures, or teams of teams, where individual, agile teams operate with loose points of connection to other teams that focus on dependencies and outcomes.

In the same way, startup communities and the broader ecosystems that touch them have changed and adapted, and the successful ones have learned how to stay loosely connected to other startup communities, prioritize collaboration, and remain focused on inclusion and entrepreneurial leadership.

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 – Blink part III – Undo?

I just finished reading Michael Lewis’s The Undoing Project: A Friendship That Changed Our Minds, and honestly, I wish I could hit Life’s Undo button and reclaim those hours.  I love Michael Lewis, and he’s one of those authors where if he writes it, I will read it.  But this one wasn’t really worth it for me.

Having said that, I think if you haven’t already read both Malcolm Gladwell’s Blink (review, buy) and Daniel Kahneman’s Thinking, Fast and Slow (review, buy), then it might be worth it.  But having read those two books, The Undoing Project had too much overlap and not enough “underlap” (to quote my friend Tom Bartel) – that is, not enough new stuff of substance for me.  The book mostly went into the personal relationship between two academic thinkers, Daniel Kahneman and Amos Tversky.  It also touched on some of the highlights of their work, which, while coming out of the field of psychology, won them a Nobel prize in Economics for illuminating some of the underlying mechanics of how we make decisions.

The two most interesting pieces of their work to me, which are related in the book, are:

First, that human decision-making is incredibly nuanced and complex, and that at least 25% of the time, the transitive property doesn’t apply.  For example, I may prefer coffee to tea, and I may prefer tea to hot chocolate, but that doesn’t necessarily mean I prefer coffee to hot chocolate.

From the book, “When faced with complex multidimensional alternatives, such as job offers, gambles or [political] candidates, it is extremely difficult to utilize properly all the available information.” It wasn’t that people actually preferred A to B and B to C and then turned around and preferred C to A. It was that it was sometimes very hard to understand the differences. Amos didn’t think that the real world was as likely to fool people into contradicting themselves as were the experiments he had designed.  And the choice created its own context: Different features might assume greater prominence in the mind when the coffee was being compared to tea (caffeine) than when it was being compared to hot chocolate (sugar). And what was true of drinks might also be true of people, and ideas, and emotions. The idea was interesting: When people make decisions, they are also making judgments about similarity, between some object in the real world and what they ideally want. They make these judgments by, in effect, counting up the features they notice. And as the noticeability of features can be manipulated by the way they are highlighted, the sense of how similar two things are might also be manipulated.”

Second, what Kahneman and Tversky called Prospect Theory, which is basically that humans are more motivated by the fear of loss as opposed to the greed of gain.  I’ve written about the “Fear/Greed Continuum” of my former boss from many years ago before.  I’m not sure he knew about Kahneman and Tversky’s work when he came up with that construct, and I certainly didn’t know about it when I first blogged about it years ago.  Do this experiment – ask someone both of these questions:  Would you rather be handed $500 or have a 50% chance of winning $1,000 and a 50% of getting nothing?  Then, Would you rather hand me $500 or have a 50% chance of owing me $1,000 and a 50% chance of owing me nothing?  Most of the time, the answers are not the same.

For fun, I tried this out on my kids and re-proved Prospect Theory, just in case anyone was worried about it.

Anyway, bottom line on this book – read it if you haven’t ready those other two books, skip it if you have, maybe skim it if you’ve read one of them!

Book Short:  The Little Engine that Could

Authors Steven Woods and Alex Shootman would make Watty Piper proud.  Instead of bringing toys to the children on the other side of the mountain, though, this engine brings revenue into your company.  If you run a SaaS business, or really if you run any B2B business, Revenue Engine:  Why Revenue Performance Management is the Next Frontier of Competitive Advantage, will change the way you think about Sales and Marketing. The authors, who were CTO and CRO of Eloqua (the largest SaaS player in the demand management software space that recently got acquired by Oracle), are thought leaders in the field, and the wisdom of the book reflects that.

The book chronicles the contemporary corporate buying process and shows that it has become increasingly like the consumer buying process in recent years.  The Consumer Decision Journey, first published by McKinsey in 2009, chronicles this process and talks about how the traditional funnel has been transformed by the availability of information and social media on the Internet.  Revenue Engine moves this concept to a B2B setting and examines how Marketing and Sales are no longer two separate departments, but stewards of a combined process that requires holistic analysis, investment decisions, and management attention.

In particular, the book does a good job of highlighting new stages in the buying process and the imperatives and metrics associated with getting this “new funnel” right.  One that resonated particularly strongly with me was the importance of consistent and clean data, which is hard but critical!  As my colleague Matt Spielman pointed out when we were discussing the book, the one area of the consumer journey that Revenue Engine leaves is out is Advocacy, which is essential for influencing the purchase process in a B2B environment as well.

One thing I didn’t love about the book is that it’s a little more theoretical than practical. There aren’t nearly enough detailed examples.  In fact, the book itself says it’s “a framework, not an answer.”  So you’ll be left wanting a bit more and needing to do a bit more work on your own to translate the wisdom to your reality, but you’ll have a great jumping off point.