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.

As I finished up my work on the Second Edition of Startup CEO:  A Field Guide to Scaling Up Your Business and started working on a new startup, my colleagues and I started envisioning a new book as a sequel or companion to Startup CEO that is going to be published on June 9 with our same publisher, Wiley & Sons.  The book is called Startup CXO:  A Field Guide to Scaling Up Your Company’s Critical Functions and Teams.

Simply put, the first book left me with the nagging feeling that it wasn’t enough to only help CEOs excel, because starting and scaling a business is a collective effort. What about the other critical leadership functions that are needed to grow a company?  If you’re leading HR, or Finance, or Marketing, or any key function inside a startup, what resources are available to you? What should you be thinking about?  What does ‘great’ look like?  What challenges lurk around the corner as you scale your function that you might not be focused on today?  If you’re a CEO who has never managed all these functions before, what should you be looking for when you hire and manage all these people?  If you’re an aspiring executive, from entry-level to manager to director, what do you need to think about as you grow your career and develop your skills?

Startup CXO is a “book of books,” with one section for each major function inside a company.  Each section is be composed of 15-20 discrete short chapters outlining the key “playbooks” for each functional role in the company – Chief People Officer, Chief Financial Officer, Chief Marketing Officer, Chief Revenue Officer, etc., hence the title Startup CXO – which is a generally accepted label in the startup ecosystem for “Chief ____ Officer.”

Here are the front and back covers of the book, with some great endorsements we’re so proud of on the back.

This is an important topic to write about at this particular time because America’s “startup revolution” continues to gather steam.  There are only increasing numbers of venture capital investors, seed funds, and accelerators supporting increasing numbers of entrepreneurial ventures.  While there are a number of books in the marketplace about CEOs and leadership, and some about individual functional disciplines (lots of books about the topic of Sales, the topic of Product Development), there are very few books that are practical how-to guides for any individual function, and NONE that wrap all these functions into a compendium that can be used by a whole startup executive team.  Very simply, each section of this book serves as a how-to guide for a given executive, and taken together, the book will be a good how-to guide for startup executive teams in general.

Startup CXO has my name on it as principal author, and I’m writing parts of it, but I can’t even pretend to write it on my own, so the book has a large number of contributors who have the experience, credibility, and expertise to share something of value with others in their specific functional disciplines — most of my Bolster co-founders are writing sections, and the others are being written by former Return Path executive colleagues — Jack Sinclair, Cathy Hawley, Ken Takahashi, Anita Absey, George Bilbrey, Dennis Dayman, Nick Badgett, Shawn Nussbaum, and Holly Enneking.

Startup CXO is also pretty closely related to Bolster’s business, since we are in the business of helping assess and place on-demand CXO talent, and as such, the final section of the book has a series of chapters written by Bolster members who are career Fractional Executives about their experience as a Fractional CXO.

The book is available for pre-order now at Amazon and Barnes & Noble.

Oh, and stay tuned for a third book in the series (kind of) due out late this year. More on that over the summer as the project takes shape!

Book Short:  Required Reading

The Leadership Pipeline, by Ram Charan, Stephen Drotter, and James Noel, should be required reading for any manager at any level in any organization, although it’s most critical for CEOs, heads of HR, and first-time managers.  Just ask my Leaderhip Team at Return Path, all of whom just had to read the book and join in a discussion of it!

The book is easy to read, and it’s a great hands-on playbook for dealing with what the authors call the six leadersihp passages:

From Individual Contributor to Manager (shift from doing work to getting work done through others)

From Manager to Manager of Managers (shift to pure management, think beyond the function)

From Manager of Managers to Functional Manager (manage outside your own experience)

From Functional Manager to Business Manager (integrate functions, shift to profit and longer term views)

From Business Manager to Group Manager (holistic leadership, portfolio strategies, value success of others)

From Group Manager to Enterprise Manager (outward looking, handle external and multiple constituencies, balance strategic and visionary long-term thinking with the need to deliver short-term operating results)

All too often, especially in rapidly growing companies, we promote people and move them around without giving enough attention to the critical success factors involved in each new level of management.  I’ve certainly been guilty of that at Return Path over the years as well.  It’s just too easy to get trapped in the velocity of a startup someitmes to forget these steps and how different each one is.  This book lays out the steps very neatly.

It’s also one of the few business books that at least makes an attempt — and a good one at that — at adapting its model to small companies.  In this case, the authors note that the top three rungs of the pipeline are often combined in the role of CEO, and that Manager of Managers is often combined with Functional Managers.

Anyway, run, don’t walk, to buy this one!

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:  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.

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.

Book Short:  Internet Fiction, part II

I hate to write a lame post, but here’s what I wrote earlier in the year about Eliot Peper’s first Internet thriller, Uncommon Stock:

Eliot Pepper’s brand new startup thriller, Uncommon Stock, was a breezy and quick read that I enjoyed tremendously. It’s got just the right mix of reality and fantasy in it. For anyone in the tech startup world, it’s a must read. But it would be equally fun and enjoyable for anyone who likes a good juicy thriller.

Like my memory of Hackoff, the book has all kinds of startup details in it, like co-founder struggles and a great presentation of the angel investor vs. VC dilemma. But it also has a great crime/murder intrigue that is interrupted with the book’s untimely ending.  I eagerly await the second installment, promised for early 2015.

Having just finished that second installment, called Uncommon Stock: Power Play, basically I want to say “ditto.”  Power Play was just as good as the first book, and now I can’t wait for the third. Where the first installment’s startup focus was around funding and founder dynamics, this one’s startup focus was around shipping product and customers. The thriller part was just as juicy.

It’s also kind of fun reading about the Boulder startup scene, especially from a writer who doesn’t and who has never spent a ton of time there. He gets some things remarkably accurate with crisp descriptions. I was kind of hoping for a cameo by Brad, at least in the form of a throw-away comment about the “long haired homeless-looking investor in the corner of Frasca.”

The Gift of Feedback, Part IV

I wrote a few weeks ago about my live 360 – the first time I’ve ever been in the room for my own review discussion.  I now have a development plan drafted coming out of the session, and having cycled it through the contributors to the review, I’m ready to go with it.  As I did in 2008, 2009, and 2011, I’m posting it here publicly.  This time around, there are three development items:

1. Continue to spend enough time in-market.  In particular, look for opportunities to spend more time with direct clients.  There was a lot of discussion about this at my review.  One director suggested I should spend at least 20% of my time in-market, thinking I was spending less than that.  We track my time to the minute each quarter, and I spend roughly 1/3 of my time in-market.  The problem is the definition of in-market.  We have a lot of large partners (ESPs, ISPs, etc.) with whom I spend a lot of time at senior levels.  Where I spend very little time is with direct clients, either as prospects or as existing clients.  Even though, given our ASP, there isn’t as much leverage in any individual client relationship, I will work harder to engage with both our sales team and a couple of larger accounts to more deeply understand our individual client experience.
2. Strengthen the Executive Committee as a team as well as using the EC as the primary platform for driving accountability throughout the organization.  On the surface, this sounds like “duh,” isn’t that the CEO’s job in the first place?  But there are some important tactical items underneath this, especially given that we’ve changed over half of our executive team in the last 12 months.  I need to keep my foot on the accelerator in a few specific ways:  using our new goals and metrics process and our system of record (7Geese) rigorously with each team member every week or two; being more authoritative about the goals that end up in the system in the first place to make sure my top priorities for the organization are being met; finishing our new team development plan, which will have an emphasis on organizational accountability; and finding the next opportiunity for our EC to go through a management training program as a team.
3. Help stakeholders connect with the inherent complexity of the business.  This is an interesting one.  It started out as “make the business less complex,” until I realized that much of the competitive advantage and inherent value from our business comes fom the fact that we’ve built a series of overlapping, complex, data machines that drive unique insights for clients.  So reducing complexity may not make sense.  But helping everyone in and around the business connect with, and understand the complexity, is key.  To execute this item, there are specifics for each major stakeholder.  For the Board, I am going to experiment with a radically simpler format of our Board Book.  For Investors, Customers, and Partners, we are hard at work revising our corporate positioning and messaging.  Internally, there are few things to work on — speaking at more team/department meetings, looking for other opportunities to streamline the organization, and contemplating a single theme or priority for 2015 instead of our usual 3-5 major priorities.

Again, I want to thank everyone who participated in my 360 this year – my board, my team, a few “lucky” skip-levels, and my coach Marc Maltz.  The feedback was rich, the experience of observing the conversation was very powerful, and I hope you like where the development plan came out!

Book Short:  Worth Buying Free

The cynic in me wanted to start this book review of  Free: The Future of a Radical Price, by Chris Anderson, by complaining that I had to pay for the book.  But it ended up being good enough that I won’t do that (plus, the author said there are free digital versions available — though the Kindle edition still costs money).  At any rate, a bunch of reviews I read about the book panned it when compared to Anderson’s prior book, The Long Tail (post, link to book).

I won’t get into the details of the book, though you’ll get an idea from the paragraph below, but Anderson has a few gems worth quoting:

• Any topic that can divide critics into two opposite camps — “totally wrong” and “so obvious” — has got to be a good one
• Free makes Paid more profitable
• Younger players have more time than money…older players have more money than time
• Doing things we like without pay often makes us happier than the work we do for a salary
• It’s true that each generation takes for granted some things their parents valued, but that doesn’t mean that generation values everything less
  

While Free is s probably not quite as good as The Long Tail, it does a good job of organizing and classifying and explaining the power of different economic models that involve a free component, and I found it very thought provoking about our own business at Return Path.

We already do a couple forms of Free — we practice the “third party” model, by giving things away to ISPs but selling them to mailers; and we practice Freemium by providing Senderscore.org and Feedback Loops for free in order to attract paying customers to our testing and monitoring application and whitelist.  But could we do others?  Maybe.  They may not be revolutionary, but they’re smart marketing.

As some of the reviewers write, the book isn’t the be-all-end-all of marketing, it overreaches at times, and it is more applicable to some businesses than others, but Free was definitely worth paying for.

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!

Reboot – The Fountainhead

Happy New Year!  Every few years or so, especially after a challenging stretch at work, I’ve needed to reboot myself.  This is one of those times, and I will try to write a handful of blog posts on different aspects of that.

The first one is about a great book.  I just read Ayn Rand’s The Fountainhead for (I think) the 5^th time.  It’s far and away my favorite book and has been extremely influential on my life.  I think of it (and any of my favorite books) as an old friend that I can turn to in order to help center myself when needed as an entrepreneur and as a human.  The last time I read it was over 10 years ago, which is too long to go without seeing one of your oldest friends, isn’t it?  While the characters in the book by definition are somewhat extreme, the book’s guiding principles are great.  I’ve always enjoyed this book far more than Atlas Shrugged, Rand’s more popular novel, which I think is too heavy-handed, and her much shorter works, Anthem and We The Living, which are both good but clearly not as evolved in her thinking.

As an entrepreneur, how does The Fountainhead influence me?  Here are a few examples.

• When I think about The Fountainhead, the first phrase that pops into my head is “the courage of your convictions.”  Well, there’s no such thing as being a successful entrepreneur without having the courage of your convictions.  If entrepreneurs took “no” for an answer the first 25 times they heard it, there would be no Apple, no Facebook, no Google, but there’d also be no Ford, no GE, and no AT&T
• One great line from the book is that “the essence of man is his creative capacity.”  Our whole culture at Return Path, and one that I’m intensely proud of, is founded on trust and transparency.  We believe that if we trust employees with their time and resources, and they know everything going on in the company, that they will unleash their immense creative capacity on the problems to be solved for the business and for customers
• Another central point of influence for me from the book is that while learning from others is important, conventional wisdom only gets you far in entrepreneurship.  A poignant moment in the book is when the main character, Howard Roark, responds to a question from another character along the lines of “What do you think of me?”  The response is “I don’t think of you.”  Leading a values-driven life, and running a values-driven existence, where the objective isn’t to pander to the opinion of others but to fill my life (and hopefully the company’s life) with things that make me/us happy and successful is more important to me than simply following conventional wisdom at every turn.  Simply put, we like to do our work, our way, noting that there are many basics where reinventing the wheel is just dumb
• Related, the book talks about the struggle between first-handers and second-handers.  “First-handers use their own minds.  They do not copy or obey, although they do learn from others.”  All innovators, inventors, and discoverers of new knowledge are first-handers.  Roark’s speech at the Cortland Homes trial is a pivotal moment in the book, when he says, “Throughout the centuries, there were men who took first steps down new roads armed with nothing but their own vision.  The great creators — the thinkers, the artists, the scientists, the inventors — stood alone against the men of their time.  Every great new thought was opposed.”  In other words, first-handers, critical thinkers, are responsible for human progress.  Second-handers abdicate the responsibility of independent judgment, allowing the thinking of others to dominate their lives.  They are not thinkers, they are not focused on reality, they cannot and do not build
• The “virtue of selfishness” is probably the essence of Rand’s philosophy.  And it sounds horrible.  Who likes to be around selfish people?  The definition of selfish is key, though.  It doesn’t inherently mean that one is self-centered or lacks empathy for others.  It just means one stays true to one’s values and purpose and potentially that one’s actions start with oneself.  I’d argue that selfishness on its own has nothing to do with whether someone is a good person or a good friend.  For example, most of us like to receive gifts.  But people give gifts for many different reasons – some people like to give gifts because they like to curry favor with others, other people like to give gifts because it makes them feel good.  That’s inherently selfish.  But it’s not a bad thing at all
• Finally, I’d say another area where The Fountainhead inspires me as a CEO is in making me want to be closer to the action.  Howard Roark isn’t an ivory tower designer of an architect.  He’s an architect who wants to create structures that suit their purpose, their location, and their materials.  He only achieves that purpose by having as much primary data on all three of those things as possible.  He has skills in many of the basic construction trades that are involved in the realization of his designs – that makes him a better designer.  Similarly, the more time I spend on the front lines of our business and closer to customers, the better job I can do steering the ship

One area where I struggle a little bit to reconcile the brilliance of The Fountainhead with the practice of running a company is around collaboration.  It’s one thing to talk about artistic design being the product of one man’s creativity, and that such creativity can’t come from collaboration or compromise.  It’s another thing to talk about that in the context of work that inherently requires many people working on the same thing at the same time in a generalized way.  Someday, I hope to really understand how to apply this point not to entrepreneurship, but to the collaborative work of a larger organization.  I know firsthand and have also read that many, many entrepreneurs have cited Ayn Rand as a major influence on them over the years, so I’m happy to have other entrepreneurs comment here and let me know how they think about this particular point.

It feels a little shallow to try to apply a brilliant 700 page book to my life’s work in 1,000 words.  But if I have to pick one small point to illustrate the connection at the end, it’s this.  I realize I haven’t blogged much of late, and part of my current reboot is that I want to start back on a steady diet of blogging weekly.  Why?  I get a lot out of writing blog posts, and I do them much more for myself than for those who reads them.  That’s a small example of the virtue of selfishness at work.