Book Short:  Entrepreneurial Lessons

The Startup Playbook: Secrets of the Fastest-Growing Startups from 42 Founders, by David Kidder, is the ultimate coffee table book for entrepreneurs and people who are interested in how they think about running their businesses.

David is the author of the Intellectual Devotional series (here’s a link to one of the five or six books in the series), he’s a good friend of mine and a member of a CEO Forum that I’m in, and my major disclosure about this blog post is that I’m one of the 42 entrepreneurs David interviewed for and profiles in the book.

The Startup Playbook is very different from my own book (in progress) on being a Startup CEO.  Where my book is going to go deep on different topics – think of it as a bit of a field guide – David’s book is extremely broad in its coverage of different entrepreneurs and their stories.  Taken together, the book paints a great picture of how CEOs think about the most important parts of the job.  It’s also a nice change of pace (for me, anyway) that David profiles some entrepreneurs who aren’t in the Internet/tech space.

It was an honor to be included in The Startup Playbook next to entrepreneurs like Reid Hoffman and Elon Musk.

Book Short:  Deep Dive on Customer Development

I continue to be on a tear reading books about startups as I finish and get ready for the publication of Startup CEO (now available for pre-ordering at Amazon).   This week’s selection was The Startup Owners Manual:  A Step-by-Step Guide for Building a Great Company, by Steve Blank and Bon Dorf.  This book is a significantly more detailed version of Blank’s first book, The Four Steps to the Epiphany, which was a revolutionary book a few years ago that helped spawn the Lean Startup movement.

And when I say significantly, I mean it!  The Startup Owners Manual is 600 pages of really detailed how-to around the first two steps of Blank’s four steps, Customer Discovery and Customer Validation.  It doesn’t get into the last two steps at all, Customer Creation and Company Building.  It has a lot of overlap with Ash Maurya’s Running Lean (post, book), although it’s significantly more detailed.  And essentially, especially around the topic of “Company Building,” my book starts where this one stops.

One of Blank’s great lines in the book is that a “A startup is a temporary organization in search of a scalable, repeatable, profitable business model.”  That frames the whole Lean Startup movement really, really well.  The whole concept of Customer Discovery and Validation, of testing hypotheses, is critical to getting product-marketing fit right in a capital-efficient manner.  If I were starting Return Path today, we’d be using these methods from the get-go.

But Lean principles are wholly compatible with larger companies, as well, and in fact we use all of these principles in our product development organization today.  We adapt them for our size and scale and the fact that often we are selling either new or enhanced versions of existing product into existing customers, but our product teams have all embraced the Lean principles and the vocabulary around them, and our goal is that we should never bring a product to market that isn’t already being bought.

Book Short – A Smattering of Good Ideas that further my Reboot path

Ram Charan’s The Attacker’s Advantage was not his best work, but it was worth the read.  It had a cohesive thesis and a smattering of good ideas in it, but it felt much more like the work of a management consultant than some of his better books like Know How (review, buy), Confronting Reality (review, buy), Execution (review, buy), What the CEO Wants You to Know ( buy), and my favorite of his that I refer people to all the time, The Leadership Pipeline (review, buy).

Charan’s framework for success in a crazy world full of digital and other disruption is this:

Perceptual acuity (I am still not 100% sure what this means)

1. A mindset to see opportunity in uncertainty
2. The ability to see a new path forward and commit to it
3. Adeptness in managing the transition to the new path
4. Skill in making the organization steerable and agile

The framework is basically about institutionalizing the ability to spot pending changes in the future landscape based on blips and early trends going on today and then about how to seize opportunity once you’ve spotted the future.  I like that theme.  It matches what I wrote about when I read Mark Penn’s Microtrends (review, buy) years ago.

Charan’s four points are important, but some of the suggestions for structuring an organization around them are very company-specific, and others are too generic (yes, you have to set clear priorities).  His conception of something he calls a Joint Practice Session is a lot like the practices involved in Agile that contemporary startups are more likely to just do in their sleep but which are probably helpful for larger companies.

I read the book over a year ago, and am finally getting around to blogging about it.  That time and distance were helpful in distilling my thinking about Charan’s words.  Probably my biggest series of takeaways from the book – and they fit into my Reboot theme this quarter/year, is to spend a little more time “flying at higher altitude,” as Charan puts it:  talking to people outside the company and asking them what they see and observe from the world around them; reading more and synthesizing takeaways and applicability to work more; expanding my information networks beyond industry and country; creating more routine mechanisms for my team to pool observations about the external landscape and potential impacts on the company; and developing a methodology for reviewing and improving predictions over time.

Bottom line:  like many business books, great to skim and pause for a deep dive at interesting sections, but not the author’s best work.

Book Short:  Is CX the new UX?

Outside In: The Power of Putting Customers at the Center of Your Business, by Harley Manning and Kerry Bodine from Forrester Research, was a good read that kept crossing back and forth between good on the subject at hand, and good business advice in general.  The Customer Experience (CX) movement is gaining more and more steam these days, especially in B2B companies like Return Path.  The authors define Customer Experience as “how your customers perceive their interactions with your company,” and who doesn’t care about that?

A few years ago, people started talking a lot more about User Experience (UX) as a new crossover discipline between design and engineering, and our experience at Return Path has been that UX is an incredibly powerful tool in our arsenal to build great technical products via lean/agile methods.  The recurring thought I had reading this book, especially for companies like ours, was “Is CX the new UX?”

In other words, should we just be taking the same kind of lean/agile approach to CX that we do with technical product development and UX — but basically do it more holistically across every customer touchpoint, from marketing to invoice?  It’s hard to see the answer being “no” to that question, although as with all things, the devil is in the implementation details.  And that’s true at the high level (the authors talk about making sure you align CX strategy with corporate strategy and brand attributes and values) as well as a more granular level (what metrics get tracked for CX, and how do those align with the rest of the companies KPIs).

The book’s framework for CX is six high-level disciplines: strategy, customer understanding, design, measurement, governance, and culture — but you really have to read the book to get at the specifics.

Some other thoughts and quotes from the book:

• the book contains some good advice on how to handle management of cross-functional project teams in general (which is always difficult), including a good discussion of various governance models
• “to achieve the full potential of customer experience as a business strategy, you have to change the way you run your business. You must manage from the perspective of your customers, and you must do it in a systematic, repeatable, and disciplined way.”
• one suggestion the book had for weaving the customer experience into your culture (if it’s not there already) is to invite customers to speak all-hands meetings
• another suggestion the book had for weaving the customer experience into everyone’s objectives was one company’s tactic of linking compensation (in this case, 401k match) to customer experience metrics
• “Customer Experience is a journey, not a project. It has a beginning but it doesn’t have an end.”

Thanks to my colleague Jeremy Goldsmith for recommending this book.

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.

Book Short:  Not As Deep As You’d Like

Deep Change, by Robert Quinn, is a reasonably interesting collection of thoughts on management and leadership, but it doesn’t hang together very well as a single work with a unified theme.  The promise is interesting — that we must personally abandon our knowledge, competence, techniques and abilities and “walk naked into the land of uncertainty” to undergo great personal change that can then lead us to organizational change — but the book doesn’t quite deliver on it.

That said, I enjoyed the book as a quick read for a few of its more interesting concepts.  For example, Quinn has a great crystallization of many things I’ve observed over the years called “the tyrrany of competence” where organizations can get paralyzed by people who are technically strong at their jobs but who are either disruptive culturally or who have such a chokehold on their role that they hold back the organization as a whole from growing.  Another good concept is a chart and some related commentary about how a person transforms from an individual contributor, to a manager, to a leader — great for any growing company.  The last interesting one was a grid mapping out four different types of CEOs — Motivator, Vision Setter, Anazlyer, and Taskmaster.  Quinn goes into some detail about the characteristics of each and then circles back to the inevitable conclusion (like most Harvard Business Review articles) that the best CEOs exhibit all four characteristics at different times, in different circumstances.

So not my favorite book overall, but some good tidbits.  Probably worth a quick read if you’re a student of management and leadership.  Thanks to my former colleague Kendall Rawls for this book.

I’ve written a bunch on this blog and in Startup CEO, about Agile Development and the Lean Canvas and Lean Startups in general (see a really old post on Agile Development from 10 years ago when we first adopted it here, and one on Agile Marketing here).  The basic premise of all of this is that there is an old way to build software products and businesses, and a new lighter way loosely based on Toyota’s lean manufacturing principles.  The old way is HEAVY — you spec out a product and build it and hope you got it right; you write a big business plan and start raising money and executing on it and hope your assumptions are correct.  The new way is LIGHTER — you co-create product with customers and develop a Minimum Viable Product so that by the time it’s ready to sell, some customers are already buying it; you create a business plan that is all about systematically testing the underlying assumptions first, then raising money and charging forward after you know what you’re dealing with.

As readers of this blog know, Return Path is a software/services company that cares about building a robust business, and we also have a lot of passion around building our organization and culture.  We’ve always been fairly progressive with our People practices and programs, and we’re also always trying to innovate to make those things more impactful, easier, and more fun.  And that brings us to the subject of this post.

Over the last 2 years, we have been working to make teams more effective (creatively, we called this work “Effective Teams”); we loosely used Patrick Lencioni’s 5 Dysfunctions of a Team as the framing for the work we do with teams.  We ensure they develop strong, trusting relationships, have the skills and courage to have healthy conflict, which means they can commit to the decisions they make; they then hold each other accountable and ultimately get better results.   In addition to regular team development activities, our teams now give each other regular feedback including team-based peer-to-peer feedback through a facilitated quarterly session.   We saw improvements in team development which were verified by an increase of 13% of positive results in team effectiveness surveys.

We are now working to ensure that teams are working in a more agile way, and that their stakeholders are involved in the creation and evaluation of team goals.   Through our “Agile Everywhere” initiative, our Effective Teams work is expanding to help teams develop more agile operating systems.  By June 30, teams will be using some of the agile methodologies to:

break work down into smaller pieces

check in frequently on progress

share feedback among team members and stakeholders

tune practices based on feedback

report results publicly and

establish a predictable operating system.

As with most of our People practices, we modeled this on the Executive Committee, and we’ve instituted  things like Daily Stand-ups and Trello Boards for a pretty disparate set of teams.  We’ve found some practices useful, and we’ve adapted some practices to meet our needs.  We are now in process of piloting these practices with 15 teams throughout the company.  Stay tuned!

Book Short:  Just One Minute

What The One Minute Manager does for basic principles of management and goal setting, The One Minute Manager Meets the Monkey does for delegation.  Both are blessedly quick reads (the classic “airport” book), and Ken Blanchard really nails some of management’s most critical components with simplicity and grace.

I’m a fan of the One Minute Manager school, and it does work well for some of the basics, but it has its limitations in terms of how broadly it can be applied.  My colleague Whitney McNamara‘s words in an email to me a few months back say it all:

OMM has actually been useful.  I have to agree that it’s got a bit of a “Jonathan Livingston Seagull” mystical simplicity thing going, but as you say, simple is sometimes what works best.

It’s really strong in that the basic lessons are at root so simple that they’re easy to forget about day to day…having them articulated in a similarly simple way, so that they stick at the top of mind easily, is nice.

The other side of that is that it presents such a simplified, best-of-all-possible-worlds sort of scenario that I did sometimes find myself wanting to set fire to the OMM’s office building and scream “let’s see you deal with *this* in 60 seconds, buddy”…but on balance a pretty good experience. 🙂

In the end, it’s not that good management is easy — but it can be quick and relatively painless if done well and regularly.

Book Short:  Reality Doesn’t have to Bite

I just read Confronting Reality (book; audio), the sequel to Execution, by Larry Bossidy and Ram Charan.  Except I didn’t read it, I listened to it on Mariquita’s iPod Shuffle over the course of two or three long runs in the past week.  The book was good enough, but I also learned two valuable lessons.  Lesson 1:  Listening to audio books when running is difficult – it’s hard to focus enough, easy to lose one’s place, can’t refer back to anything or take notes.  Lesson 2:  If you sweat enough on your spouse’s Shuffle, you can end up owning a Shuffle of your own.

Anyway, I was able to focus on the book enough to know that it’s a good one.  It’s chock full of case studies from the last few years, including some “new economy” ones instead of just the industrial types covered in books like Built to Last and Good to Great.  Cisco, Sun, EMC, and Thomson are all among those covered.  The basic message is that you really have to dig into external market realities when crafting a strategic plan or business model and make sure they’re in alignment with your financial targets as well as people and processes.  But the devil’s in the details, and the case studies here are great.

Book short:  Myers-Briggs Redux

Instinct:  Tapping Your Entrepreneurial DNA to Achieve Your Business Goals, by Tom Harrison of Omnicom, is an ok book, although I wouldn’t rush out to buy it tomorrow.  The author talks about five broad aspects of our personalities that influence how we operate in a business setting:  Openness to Experience, Conscientiousness, Extroversion, Agreeableness, and Neuroticism.  These traits are remarkably similar to those in the popular Myers-Briggs Type Indicator that so many executives have taken over the years.

It’s not just that you want to be high, high, high, high, and low in the Big 5.  Harrison asserts that successful entrepreneurs need a balance of openness and conscientiousness in order to be receptive to new ideas, but be able finish what you start; a balance of extroversion and agreeableness so that you have enough energy but also have the ability to work with others; and not too much neuroticism, as you have to be able to take risks.

The book not only talks about how to spot these factors, but how to work around them if you don’t have them (that part is particularly useful, but he doesn’t do it for all five factors).  He also talks about the entrepreneurial addiction to success, and creating the all-important Servant CEO culture, which I certainly agree with and wrote about early on in this blog in my “Who’s The Boss?” posting.

Harrison does have a great section on how “Nice Guys” can and should be winners; how being nice and having guts aren’t mutually exclusive, and he gives a well-written Twelve Rules for expressing the Nice Guy gene:

– Don’t walk on other people, but don’t let them walk on you

– Respect the big idea in everyone

– Own everything

– Never let ’em see you sweat Keep it simple

– Never think in terms of “So what have you done for me today?”

– More is less

– Live your word consistently

– Don’t lie:  fix what’s causing you to think you need to lie

– Never forget to thank, congratulate, or acknowledge people for their efforts

– Keep your door and your heart open

– Never stand in the way of balance

The most annoying part of the book is that Harrison keeps making references to a handful of genetic studies about twins to prove on and off that traits are inherited and that inherited traits can be expressed in different ways.  These references are mildly interesting, but they detract from the substance of the book.

Overall, the book has some interesting points in it, but it’s too much like Jim Collins’ Good to Great and Built to Last, only without the depth of business research and case studies.  Plus, Harrison does the one thing I find most irritating in business books — he is clearly an expert in one thing (business), but he unnecessarily pretends to be an expert in another thing (genetics) in order to make his point.

I love me a good framework. And Geoffrey Moore is the kind of good product/marketing frameworks for technology companies. Moore’s Zone to Win: Organizing to Compete in an Age of Disruption is a must-read for anyone managing a larger technology organization (start reading it when you get to 200-250 people – it’s never too early to worry about disruption). More important, it’s really a companion book or coda to Escape Velocity: Free Your Company’s Future from the Pull of the Past, so if you haven’t read that one, start there and read both sequentially. Zone to Win is quite short and punchy, and it doesn’t disappoint.

I can’t believe is that I never blogged about Escape Velocity before since it was a very influential book in how we managed a bunch of things at Return Path in the later years when we got larger and were more in “disrupt or be disrupted” mode. I’ll start with the essence of that book before I move onto Zone to Win. Escape Velocity‘s principal framework is to divide the different product lines/lines of business you have into three planning horizons:

• Horizon 1 (H1): Current businesses that should be profitable and sustainable
• Horizon 3 (H3): Nascent R&D efforts with the potential to be disruptors or game changers
• Horizon 2 (H2): The bridge between H1 and H3 where an R&D effort that is taking off is scaled and hopefully achieves the eponymous Escape Velocity

The essence of the book is to talk about how larger companies become completely slavish to H1 businesses, their cash cows, and struggle to escape from their pull, whether that’s internal resource allocation or customer-driven demands. Failure to innovate properly beyond H1 businesses is why companies die. But the rest of the book is a lot less memorable, and it doesn’t quite prompt you into action.

That’s where Zone to Win comes in, and it helps me understand where we really got a couple things really wrong at Return Path (as an aside, Moore once met my Return Path cofounder George at a conference, and when George described our business to him, he said “Ah, a blue collar business. Those can work, too.” I think I understand what he meant by that, although it doesn’t sound like a compliment!)

In Zone to Win, Moore shows you how to put the three Horizons into action by creating an overlay framework to managing your company to help optimize all three zones simultaneously. The four zones are:

The key takeaways for me from this framework as well as the notes of where we got things wrong at Return Path, even while acknowledging that we had to play across H1, H2, and H3 simultaneously, were:

• Performance Zone: Managing your main H1 business in a way that drives growth and customer success for the long haul
• Productivity Zone: Managing your main H1 business for optimal profitability and scalability
• Incubation Zone: Starting new H3 businesses and hoping they work
• Transformation Zone: Getting your H3 business through H2 and into H1 to the point where it’s at least 10% of your overall revenue

What we got right at Return Path was first recognizing that we needed to incubate new businesses as the growth in our core business started to slow down, as well as recognizing that we needed to step up our game in managing the core business for performance. So, Moore would say something like “congratulations, you drew up the correct strategy.” But we fell down on implementation for reasons in three of the four zones. Our problem with the Performance Zone is that we discovered the three horizon model too late — there were several years where we were running R&D experiments in the middle of the core business, which created chaos. By the time we got religion around it, we were constantly playing catch up redesigning our management processes — like the teenager still wearing his kid clothes looking awkward and misfit. In the Productivity Zone, we did invest in productivity, but we weren’t aggressive enough about insisting on End of Life for some programs or products, and and we were bogged down by a convoluted legacy implementation of our CRM system that we never wholesale fixed. But the biggest problem we ran into was in the Transformation Zone, where we tried to jam two new businesses through that zone at the same time instead of focusing all our energies on one. I bet we could have pulled off even more of a transformational success with our security business (the one further along) if we hadn’t also been trying to get our consumer insights business through H2 at the same time. At least Moore notes that’s the hardest zone to get right, so I don’t feel quite so dumb.

There were probably other exogenous factors that caused us to fall down on implementation, too, but I think this had a lot to do with it. And don’t get me wrong, Return Path was a success in the end. It just could have been more successful if we had caught this book and adhered rigorously sooner. It was even published in time — somehow we just missed it. We were lured by customer traction and market pull into thinking we could do both. And it’s certainly possible that we were advised against this by one or more of our board members and plowed ahead anyway.

Moore is a masterful writer. If you haven’t read Crossing the Chasm or Inside the Tornado, for example, if you’re a GenZ founder and you think “wow those books came out before I was born, they can’t be relevant,” you should start by reading them. They’re still 100% applicable today, and Moore’s subsequent editions have updated some of the case studies, even if not totally contemporary — and these are worth reading even as a raw startup (in fact, especially as a raw startup). But once you finish those and your business gets larger, go straight into Escape Velocity and be sure to add on Zone to Win.