Book Short: Faster Than The Blink of an Eye

Michael Lewis is one of those authors for whom my general point of view is “read whatever he writes.” Flash Boys: A Wall Street Revolt  was no exception.  It’s a book about the high-frequency trading business, how a difference in microseconds can make a difference, and how the complexity of trading has led to enough confusion that virtually no one on Wall Street actually understands how it works any more.

I am a capitalist through and through, and I never begrudge Wall Street for making money, even though I do have moments where I doubt the amount of value that finance creates relative to the amount of income they swallow up.  However, that all goes out the window when there is evidence that some pocket of Wall Street isn’t playing by the rules.  I define “the rules” as either the law, or as something more like “a basic sense of morality and fairness.”

Some of what has been going on in the high-frequency trading business, as Lewis describes in this book, may or may not be legal (let’s assume it is), but is almost certainly not following a basic sense of morality and fairness.  It’s worth noting that I am purely going off what Lewis wrote in the book, so to the extent that his research is incomplete or his writing is misleading, I am happy to retract that statement.  But based on what I read, I’d challenge some of the people in the HFT business to defend what they’re doing publicly, to their mothers or to their own clients.  That’s the ultimate test of morality or fairness.

It’s amazing to me that this topic hasn’t gotten more play in the media or with regulators.  Maybe it’s just too complicated for anyone to understand or to articulate.  In any event, even though not strictly a business book, it’s fascinating and worth a read, as I think all Michael Lewis books are.

Book Short:  A Primer on Viral Marketing

“People talk about Andy,” writes Seth Godin in the foreward to Andy Sernovitz’s new book, Word of Mouth Marketing:  How Smart Companies Get People Talking.   “He’s a living, breathing example of the power of word of mouth.”  Andy’s the CEO of WOMMA, the Word of Mouth Marketing Association, and a former colleague of mine.

Ever since reading The Tipping Point, I keep looking for the secret sauce around viral marketing.  What is it that makes something cool enough to buzz about?  My conclusion from reading Andy’s book is that secret sauce doesn’t exist.  Like everything else, being buzzworthy comes from hard work, being inherently good, AND using the techniques and understanding in Andy’s book.  Tables like “The Three Reasons People Talk About You” and “The Five T’s of Word of Mouth Marketing” are worth the price of the book in and of themselves, as they explain how to manage, handle, and drive viral marketing — once you have your own secret sauce down.

Andy’s wanted to write a book for a long time (in fact, he got us started on ours), and I’m glad he finally did it.  If you’re interested in an easy-to-follow, practical, hands-on guide to viral, or word-of-mouth marketing, this is the book for you.

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: Stick Figures That Matter

I have read a bunch of books lately to try to improve my presentation skills. The latest one, The Back of the Napkin: Solving Problems and Selling Ideas with Pictures, by Dan Roam, was good, and quite different from some of the others I’ve read recently like Presentation Zen and Beyond Bullet Points, both of which are much more focused on effective use of Powerpoint.

The Back of the Napkin takes a different approach. The focus is much more on creating compelling visuals. It’s not about Powerpoint so much as it is about teaching how to crystallize concepts into tight and compelling schematics. Roam creates two pretty good frameworks for thinking about this: one that breaks down the message of a given slide into its most simple element — are you describing a who (use a portrait), what (chart), when (timeline), where (map), why (plot), or how (flowchart)? And a second that takes that element and asks five questions about the best way to convey the information — simple vs. elaborate, quality vs. quantity, vision vs. execution, individual vs. comparison, or change state vs. as-is.

Both frameworks are good, and if you’re already doing really good presentations, this will help improve them. In short, I’d say The Back of the Napkin is a good read if you’re obsessed with creating compelling visuals, but it’s more of a deeper drill than the two books I noted above. I’d read and master the material from Presentation Zen for 101, then dive into this topic for the 201 course.

Book Short:  Catchiest Title in a Long Time

You have to admit, a book called The 4-Hour Workweek: Escape 9-5, Live Anywhere, and Join the New Rich has a pretty enticing title.  The email geek in me thinks that if it were a subject line, it would have a good open rate.  Anyway, the book, by Timothy Ferriss, is a breezy read that  blends self help with entrepreneurship, has a lot of good resource lists in it, and is worth reading  if you don’t take it too  seriously.

There are some good central points to the book.  First, life has changed, and people don’t want to slave away until they’re 65 any more so they can do all the fun stuff in their old age — they want to change directions, unplug more regularly, and enjoy life with their families when they’re younger.  I buy that.
Second, good companies are increasingly allowing employees more degrees of freedom in the where and when and even how of getting things done, just as long as they get things done — and people should take advantage of that.  I buy that as well — we practice that at Return Path, generally speaking.  Third, startups that are mainly virtual organizations and internet-based are easier, cheaper, and potentially more profitable than most businesses have been, historically speaking.  Ok, fair enough.

Fourth, anyone can be just like the author and do all of this stuff, too, right?  Start a business that turns into a cash machine that requires little to no maintenance while becoming one of the best tango dancers in the world in South America, etc. etc. etc.  Well, maybe not.  I guess the point of self-help books is to show an extreme example and inspire people to achieve it, and I do think there’s a lot to what Ferriss says about how people can live richly without being rich, but the fact is that the world would fall apart if everyone did what he does.  And the other fact is that Ferriss is well above average in intellect and drive, and probably some physical talents as well from his descriptions of tango dancing and kick boxing, which must contribute to his success in life far more than his operating philosophy does.

But as I said, it’s a fun read, and if you don’t take it too seriously, or at least take the feedback directionally as opposed to whole hog, it’s well worth it.

Book Short:  Finishing First

The Power of Nice:  How to Conquer the Business World with Kindness, by Linda Kaplan Thaler and Robin Koval, is one of those “airport books” that takes about an hour to read.  I had an ear-to-ear grin reading the book, in part because, well, it’s just a happy book, filled with anecdotes about how a smile here or a gesture of kindness there made a difference in someone’s life — both personally and professionally.

But part of my interest in the book was also driven by a long-standing debate we have at Return Path over whether we’re “too nice” as a company and whether we should have “sharper elbows.”  I was struck by a few comments the authors made, things you would expect like “nice doesn’t mean naïve” as well as things you wouldn’t like “help your enemies.”  To me, that says it all about success in business:  you can be a fierce competitor externally and demand accountability internally and still be a warm and kind person, and that’s the best (and most rewarding) place to be.

Book Short:  Culture is King

Joy, Inc.:  How We Built a Workplace People Love, by Richard Sheridan, CEO of Menlo Innovations, was a really good read. Like Remote  which I reviewed a few weeks ago, Joy, Inc. is ostensibly a book about one thing — culture — but is also full of good general advice for CEOs and senior managers.

Also like Remote, the book was written by the founder and CEO of a relatively small firm that is predominately software engineers, so there are some limitations to its specific lessons unless you adapt them to your own environment. Unlike Remote, though, it’s neither preachy nor ranty, so it’s a more pleasant read.  And I suppose fitting of its title, a more joyful read as well. (Interestingly on this comparison, Sheridan has a simple and elegant argument against working remotely in the middle of the book around innovation and collaboration.)

Some of the people-related practices at Sheridan’s company are fascinating and great to read about. In particular, the way the company interviews candidates for development roles is really interesting — more of an audition than an interview, with candidates actually writing code with a development partner, the way the company writes code. Different teams at Return Path interview in different ways, including me for both the exec team and the Board, but one thing I know is that when an interview includes something that is audition-like, the result is much stronger. There are half a dozen more rich examples in the book.

Some of the other quotable lines or concepts in the book include:

• the linkage between scalability with human sustainability (you can’t grow by brute force, you can only grow when people are rested and ready to bring their brain to work)
• “Showcasing your work is accountability in action” (for a million reasons, starting with pride and ending with pride)
• “Trust, accountability, and results — these get you to joy” (whether or not you are a Myers-Briggs J, people do get a bit of a rush out of a job well done)
• “…the fun and frivolity of our whimsically irreverent workplace…” (who doesn’t want to work for THAT company?)
• “When even your vendors want to align with your culture, you know you’re on the right path” (how you treat people is how you treat PEOPLE, not just clients, not just colleagues)
• “One of the key elements of a joyful culture is having team members who trust one another enough to argue” (if you and I agree on everything, one of us is not needed)
• “The reward is in the attempt” (do you encourage people to fail fast often enough?)
• “Good problems are good problems for the first five minutes. Then they just feel like regular problems until you solve them” (Amen, Brother Sheridan)

The benefits of a joyful culture (at Return Path, we call it a People-First culture) have long been clear to me. As Sheridan says, we try to “create a culture where people want to come to work every day.” Cultures like ours look soft and squishy from the outside, or to people who have grown up in tough, more traditional corporate environments. And to be fair, the challenge with a culture like ours is keeping the right balance of freedom and flexibility on one side and high performance and accountability on the other. But the reality is that most companies struggle with most of the same issues — the new hire that isn’t working out or the long-time employee who isn’t cutting it any more, the critical path project that doesn’t get done on time, the missed quarter or lost client.  As Sheridan notes though, one key benefit of working at a joyful company is that problems get surfaced earlier when they are smaller…and they get solved collaboratively, which produces better results. Another key benefit, of course, is that if you’re going to have the same problems as everyone else, you might as well have fun while you’re dealing with them.

If you don’t love where you work and wish you did, read Joy, Inc. If you love where you work but see your company’s faults and want to improve them, read Joy, Inc. If you are not in either of the above camps, go find another job!

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: What’s For Dinner Tonight, Honey?

The Paradox of Choice: Why More is Less, by Barry Schwartz, presents an enlightening, if somewhat distressing perspective on the proliferation of options and choices facing the average American today. The central thesis of the book is that some choice is better than no choice (I’d rather be able to pick blue jeans or black jeans), but that limited choice may be better in the end than too much choice (how do I know that the jeans I really want are relaxed cut, tapered leg, button fly, etc.?). We have this somewhat astonishing, recurring conversation at home every night, with the two of us sitting around paralyzed about where to eat dinner.

The author’s arguments and examples are very interesting throughout, and his “Laffer curve” type argument about choice vs. too much choice rings true. While there’s obviously no conclusive proof about this, the fact that our society is more rife with depression than ever before at least feels like it has a correlation with the fact that most of us now face a proliferation of choices and decisions to make exponentially more than we used to. The results of this involve ever-mounting levels of regret, or fear of regret, as well as internal struggles with control and expectations. Perhaps the best part of the book is the final chapter, which ties a lot of the material of the book together with 11 simple suggestions to cope better with all the choices and options in life — summed up in the last few words of the book suggestions that “choice within constraints, freedom within limits” is the way to go. Amen to that. We all need some basic structure and frameworks governing our lives, even if we create those constructs ourselves. The absence of them is chaos.

Overall, this is a good social science kind of read, not overwhelming, but definitely interesting for those who are students of human psychology, marketing, and decision making. It’s squarely in the genre of Gladwell’s The Tipping Point and Blink, and Robert Cialdini’s Influence, most of which I’ve written about recently, and though not as engaging as Gladwell, worth a read on balance if you like the genre.

Thanks to my friend Jonathan Shapiro for this book.

Book Short:  A Twofer

My friend Andrew Winston, who is one of the nation’s gurus in corporate sustainability, just published his second book, this one from Harvard Business Press — Green Recovery:  Get Lean, Get Smart, and Emerge from the Downturn on Top.  It builds on the cases and successes he had with his first book, Green to Gold (post, link to book), which came out a couple years ago and has become the standard for how businesses embrace sustainability and use it to their financial and strategic competitive advantage rather than thinking of it as a burden or a cost center.

Green Recovery is a shorter read (my kind of business book), and it hits a few key themes:

• Going green not only shouldn’t wait for better economic times, it’s a key way out of this mess

• Businesses have relied on layoffs to cut costs for far too long — it’s time to get lean on stuff, not people
• This is about survival for many businesses:  Detroit died because it missed the green wave of environmental interest and rising energy prices
• And the overarching theme…Green doesn’t raise costs, it lowers them – it’s a source of profit and innovation
  

The book reminds me a lot of my post Living With Less, For Good, which I wrote at the beginning of the financial market freefall last fall, talking about how we as a company were figuring out how to cut back without cutting people (something we’ve managed to do).  Although I wasn’t talking about green initiatives specifically, the point of getting leaner on “stuff” really resonates with me.

At the end of the day, Andrew proves that steering your company to go green — no matter what industry you’re in — is a twofer:  you can increase the strength of the business and simultaneously do your part to clean up the environment.  That’s definitely the “change we can believe in” mentality applied quite pragmatically!

The Phoenix Project:  a novel about IT, DevOps, and Helping Your Business Win, by Gene Kim, Kevin Behr, and George Spafford  is a logical intellectual successor and regularly quotes Eli Goldratt’s seminal work The Goal and its good but less known sequel It’s Not Luck.

The more business books I read, the more I appreciate the novel or fable format. Most business books are a bit boring and way too long to make a single point. The Phoenix Project is a novel, though unlike Goldratt’s books (and even Lencioni’s), it takes it easy on the cheesy and personal side stories. It just uses storytelling techniques to make its points and give color and examples for more memorable learning.

If your organization still does software development through a waterfall process or has separate and distinct development, QA, and IT/Operations teams, I’d say you should run, not walk, to get this book. But even if you are agile, lean, and practice continuous deployment, it’s still a good read as it provides reminders of what the world used to be like and what the manufacturing-rooted theories are behind these “new” techniques in software development.

I am so glad our technology team at Return Path, led by my colleagues Andy Sautins and David Sieh, had the wisdom to be early adopters of agile and lean processes, continuous deployment many years ago, and now dockers. Our DevOps process is pretty well grooved, and while I’m sure there are always things to be done to improve it…it’s almost never a source of panic or friction internally the way more traditional shops function (like the one in the book). I can’t imagine operating a business any other way.

Thanks to my long time friend and Board member Greg Sands of Costanoa Venture Capital for suggesting this excellent read.