Book short:  Life Isn’t Just a Wiki

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

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

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

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

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

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

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

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

Book Short:  Multiplying Your Team’s Productivity

No matter how frustrated a kids’ soccer coach gets, he never, ever runs onto the field in the middle of a game to step in and play.  It’s not just against the rules, it isn’t his or her role.

Multipliers: How the Best Leaders Make Everyone Smarter by Liz Wiseman and Greg McKeown (book, Kindle) takes this concept and drives it home.  The book was a great read, one of the better business books I’ve read in a long time.  I read a preview of it via an article in a recent Harvard Business Review (walled garden alert – you can only get the first page of the article without buying it), then my colleague George Bilbrey got the book and suggested I read it.  George also has a good post up on his blog about it.

One of the things I love about the book is that unlike a lot of business books, it applies to big companies and small companies with equal relevance.  The book echoes a lot of other contemporary literature on leadership (Collins, Charan, Welch) but pulls it into a more accessible framework based on a more direct form of impact:  not long-term shareholder value, but staff productivity and intelligence.  The book’s thesis is that the best managers get more than 2x out of their people than the average – some of that comes from having people more motivated and stretching, but some comes from literally making people more intelligent by challenging them, investing in them, and leaving them room to grow and learn.

The thesis has similar roots to many successful sales philosophies – that asking value-based questions is more effective than presenting features and benefits (that’s probably a good subject for a whole other post sometime).  The method of selling we use at Return Path which I’ve written about before, SPIN Selling, based on the book by Neil Rackham, gets into that in good detail.  One colorful quote in the book around this came from someone who met two famous 19th century British Prime Ministers and noted that when he came back from a meeting with Gladstone, he was convinced that Gladstone was the smartest person in the world, but when he came back from a meeting with Disraeli, he was convinced that he (not Disraeli) was the smartest person in the world.

Anyway, the book creates archetypal good and bad leaders, called Multipliers and Diminishers, and discusses five traits of both:

• Talent Magnet vs. Empire Builder (find people’s native genius and amplify it)
• Liberator vs. Tyrant (create space, demand the best work, delineate your “hard opinions” from your “soft opinions”)
• Challenger vs. Know-It-All (lay down challenges, ask hard questions)
• Debate Maker vs. Decision Maker (ask for data, ask each person, limit your own participation in debates)
• Investor vs. Micromanager (delegate, teach and coach, practice public accountability)

This was a great read.  Any manager who is trying to get more done with less (and who isn’t these days) can benefit from figuring out how to multiply the performance of his or her team by more than 2x.

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:  Choose Voice!

I took a couple days off last week and decided to re-read two old favorites.  One –Ayn Rand’s The Fountainhead — my fourth reading — will take me a little longer to process and figure out if there’s a good intersection with the blog.  One would think so with entrepreneurship as the topic, but my head still hurts from all the objectivism.  The second — Exit, Voice, and Loyalty, by Albert O. Hirschman — is today’s topic.

I can’t remember when I first read Exit, Voice, and Loyalty.  It was either in senior year of high school Economics or Government; or in freshman year of college Political Philosophy.  Either way, it was a long time ago, and for some reason, some of the core messages of this quirkly little 125 page political/economic philosophy book have stayed with me over the years.  I remembered the book incorrectly as a book about political systems, and I think it was born consciously in the wake of Eugene McCarthy’s somewhat revolutionary challenge to a sitting President Johnson for the Democratic Party nomination in 1968.  But the book is actually about business; it’s just about businesses and their customers, not corporations as social structures (the latter being more of an interest to me).  Written by an academic economist (I think), the book has its share of gratuitous demonstrative graphs, 2×2 matrices, and SAT words.  But its central premise is a gem for anyone who runs an organization of any size.

The central premise is that there are really two paths by which one can express dissatisfaction with a temporary, curable lapse in an organization:  exit (bailing), or voice (trying to fix what’s wrong from within).  The third key element, Loyalty, is less a path in and of itself but more an agent that “holds exit at bay and activates voice.”

You need to read the book and apply it to your own circumstances to really get into it, but for me, it’s all about breeding loyalty as a means of making voice the path of least resistance, even when exit is a freely available option (few of us run totalitarian states or monopolies, after all).  That to me is the definition of a successful enterprise, both internally and externally.

With your customers:  make your product so irresistible, and make your customer service so deep, that your customers feel an obligation to help you fix what they perceive to be wrong with your product first, rather than simply complain about price or flee to a competitor.

With your employees:  make your company the best possible place you can think of to work so that even in as ridiculously fluid a job market as we live in, your employees will come to their manager, their department head, the head of HR, or you as leader to tell you when they’re unhappy instead of just leaving, or worse, sulking.

With your company (you as employee):  make yourself indispensible to the organization and do such a great job that if things go wrong with your performance or with your role, your manager’s loyalty to you leads him or her to give you open feedback and coach you to success rather than unceremoniously show you the door.

Ok, this wasn’t such a short book short — probably the longest I’ve ever written in this blog, and certainly the highest ratio of short:actual book.  But if you’re up for a serious academic framework (quasi-business but not exclusively) to apply to your management techniques, this short 1970 book is as valid today as when it was written.  Thanks to David Ramert (I am pretty sure I read it in high school) for introducing it to me way back when!

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

Book Short: Not About Going With The…

Flow: The Psychology of Optimal Experience, by Mihaly Csikszentmihalyi (book, Kindle), was a great read and a nice change from either strictly business books or my regular fiction/non-fiction reading. It’s basically about the process of achieving happiness through control over one’s inner life, but it’s far from a self-help book. It’s almost more of practical psychology deep dive into what brings about happiness and peak performance – a state the author calls Flow but others have called other things over time, like being “in the zone.”

The author talks about achieving this control as synonymous with the enviable ability to persevere despite obstacles and setbacks and transform hopeless situations into challenges to be overcome, just through the force of personality. This ability comes directly from ways to order consciousness so as to be in control of feelings and thoughts. The normal entropy/chaos of the mind is the enemy. There were a few key moments or takeaways in the book for me.

1. When one’s experience is most positive – when one is achieving Flow – people cite the following conditions in this order of importance:

– Confront tasks we have a chance of completing

– Able to concentrate

– Concentration is possible because the task has clear goals and…

– …provides immediate feedback

– Act with a deep but effortless involvement that removes from awareness the worries and frustrations of everyday life

– Exercise a sense of control over actions

– Concern for the self disappears, yet paradoxically the sense of self emerges stronger after the experience is over

2. Becoming more Autotelic – learning how to make experiences ends in and of themselves – coming from the Greek words for “self” and “goal,” this concept is savoring a given activity for its own sake, NOT for its consequences and is a key to achieving Flow. Whether you create a mental construct around beating a personal record, doing math or pattern matching in your head, or something else, being able to focus enough energy on the task at hand and not be distracted by the world around (present or future) is key. It’s a little like what I wrote a few months ago about how achieving mental discipline in the small areas of one’s life can lead to much greater things by building confidence and clearing mental clutter.

3. The concept of the “Flow channel” – as skill increases, challenges must also increase proportionally in order for us to continue learning, growing, and excelling – and achieving Flow.

4. Transformational coping is the ability to cheat chaos – transforming a hopeless situation into a new flow activity that can be controlled and enjoyed and emerge stronger from…

– Unselfconscious self-assurance – ego absent but confident, not at odds with environment but part of it

– Focusing attention on the world – looking outward, not inward

– The discovery of new solutions – being able to perceive unexpected opportunities as a result

5. How to develop the autotelic self

– Set clear goals

– Become immersed in the activity

– Pay attention to what’s happening

– Learn to enjoy immediate experience

The book reminded me of a couple other things I’ve read, in case any of these resonate with you. First, Tim Gallwey’s “Inner Game” books where he talks about “relaxed concentration,” basically the Flow state, and the inner conflict between focus on the event and focus on the consequences, between mental chaos and mental discipline, personified as Self 1 and Self 2. If you haven’t read these, any are good and give you the general idea, depending on which piques your interest the most: The Inner Game of Golf (book, Kindle), The Inner Game of Tennis (book only), and The Inner Game of Work (book, Kindle). Second, David Allen’s Getting Things Done theory about how a clear, uncluttered mind can do its best work. As Flow says, achieving an ordered mental condition is difficult – unless a person knows how to give order to his or her thoughts, attention will be attracted to whatever is most problematic at the moment.

I’m not sure this book short does the book justice. It’s pretty complex and is rich with examples, but Flow (book, Kindle) is well worth a read if you’re into the theory of self control leading to better results and more happiness in life. Thanks to my friend Jonathan Shapiro for this book.

Book Short:  Way, Way Beyond Books

The Everything Store: Jeff Bezos and the Age of Amazon, by Brad Stone, was a great read.  Amazon is a fascinating, and phenomenally successful company, and Jeff is a legendary technology leader.  The Everything Store is a company and personal biography and totally delivers.

Forget about the fact that Amazon is now almost $100B in revenues and still growing like mad.  I find it even more amazing that a single company could be the largest ecommerce site on the planet while successfully pioneering both cloud computing services and e-readers.  The stories of all these things are in the book.

As a CEO, I enjoyed reading more of the vignettes behind the things that Amazon is reputationally known for in the tech world – doors as desks, their unique meeting formats, the toughness of the culture, the extensive risk taking of growth over profits, and what works and does not work about Bezos’ authoritative and domineering style.  And it’s always great to be reminded that even the biggest and best companies had to cheat death 10 times over before “arriving.”

This is good fun and learning for anyone in the business world.  It reminded me most of Walter Isaacson’s biography of Steve Jobs ,which I wrote about here, although it’s more of a company history and less of a biography than the Jobs book.

Book Short:  Alignment Well Defined, Part II

Getting the Right Things Done:  A Leader’s Guide to Planning and Execution, by Pascal Dennis, is an excellent and extraordinarily practical book to read if you’re trying to create or reengineer your company’s planning, goal setting, and accountability processes. It’s very similar to the framework that we have generally adapted our planning and goals process off of at Return Path for the last few years, Patrick Lencioni’s The Advantage (book, post/Part I of this series).  My guess is that we will borrow from this and adapt our process even further for 2014.

The book’s history is in Toyota’s Lean Manufacturing system, and given the Lean meme floating around the land of tech startups these days, my guess is that its concepts will resonate with most of the readers of this blog.  The book’s language — True North and Mother Strategies and A3s and Baby A3s — is a little funky, but the principles of simplicity, having a clear target, building a few major initiatives to drive to the target, linking all the plans, and measuring progress are universal.  The “Plan-Do-Check-Adjust” cycle is smart and one of those things that is, to quote an old friend of mine, “common sense that turns out is not so common.”

One interesting thing that the book touches on a bit is the connection between planning/goals and performance management/reviews.  This is something we’ve done fairly well but somewhat piecemeal over the years that we’re increasingly trying to link together more formally.

All in, this is a good read.  It’s not a great fable like Lencioni’s books or Goldratt’s classic The Goal (reminiscent since its example is a manufacturing company).  But it’s approachable, and it comes with a slew of sample processes and reports that make the theory come to life.  If you’re in plan-to-plan mode, I’d recommend Getting the Right Things Done as well as The Advantage.

I love innovation, and process is no different than product or business model in that regard. I’ve run and attended several hundred board meetings over the years, both those of companies where I’ve been CEO or Chairman, and those where I’m a director. I’ve written a lot about how I like running board meetings in Startup CEO, and as I mentioned the other day, I’m a co-author of a Second Edition of Startup Boards: A Field Guide to Building and Leading an Effective Board of Directors, which is coming out in June and is available to pre-order now, along with Brad Feld and Mahendra Ramsinghani.

There are two adaptations I’ve made to my standard board routines in the last year or so, one driven by the pandemic and one not.

In olden times (that makes me sound like I’m 400 years old, but “pre-covid” sounds so clinical), I used to have a board dinner the night before or after every board meeting, and of course, everything was in person. That was a really important ritual in my mind towards the end of building the board as an effective team, where people on the team know each other as people, share things going on in their lives, share vulnerabilities, and develop bonds of trust. Without regular in-person meetings and dinners or social events, that gets a lot harder. Even when we get back to “normal,” I imagine the most we’ll do in-person board meetings is 1-2x/year.

What’s the zoom version of this?

We now do two 30-minute Executive Sessions (directors only) one before the board meeting officially starts and observers and team join, as well as the traditional one after the meeting ends. The purposes of the two sessions are different. The standard post-meeting Executive Session follows up on the meeting and has me talk about business or team issues that I don’t want to talk about with the full group present or get feedback from the board. But the one before the meeting is almost entirely social. I try to come up with a different question or topic to get all of us talking that is not about Bolster. Last week’s meeting was a simple “what’s the best thing that’s happened to you so far in 2022, and what’s the worse?” One time I asked everyone to show a picture from their phone photo roll and talk about it. You get the idea. It’s not the same as a dinner, but it seems like an effective substitute given the medium.

The second adaptation, and full credit to Fred for suggesting this one a while back, is the post-meeting survey. Now immediately after every Board meeting, I send a simple Google form to each director with the following questions:

• What are 1-3 areas/specifics where we are doing well?
• What are 1-3 areas/specifics you’re concerned about or where we could do better?
• Did the board book have the right level of detail and commentary?  Is there anything you’d like to see change about the format or the content?
• Did the meeting meet your objectives for learning and discussion? 
• If not, why not?
• Do you have any other feedback for Matt at this time?

I get great feedback, almost immediately and always from all board members, while things are still fresh in everyone’s mind. I’m planning to do this whether or not the meeting is remote…although it’s definitely good when the meeting is remote, and things like Executive Session, Closed Session, and debrief with me after Closed Session are quick or sometimes rushed.

There’s always room for innovation, even in standard and time-tested processes like board meetings.