Book Short:  Chock Full O Management & Leadership

I just finished The Better People Leader, by Charles Coonradt, which was a very short, good, rich read.  It was a pretty expansive book on management & leadership topics — 100 short pages of material that are probably covered by 1,000 pages in other books.

What separates this book from the pack is the rich examples from non-business life that Coonradt sprinkles throughout the book.  They include the tale of a special ed kid who became a mainstream student within a year because his teacher had the courage to ask his fellow students to treat him normally, and the story of how Korean War POWs died in massive numbers not from physical torture but from negative feedback loops.

The closing quote of the book says it all, from Ronald Reagan:  “A great leader is not necessarily one who does the greatest things. He is the one who gets the people to do the greatest things.”  This book gives you quick tips on how to do just that.

Book Short:  Which Runs Faster, You or Your Company?

Leading at the Speed of Growth, by Katherine Catlin at the Kauffman Center for Entrepreneurial Leadership is a must read for any entrepreneur or CEO of a growth company.  It’s one of the best books I’ve ever read targeted to that audience – its content is great, its format is a page-turner, and it’s concise and to the point.

The authors take you through three stages of a growth company’s lifestyle (Initial Growth, Rapid Growth, and Continuous Growth) and describe the “how to’s” of the transition into each stage:  how you know it’s coming, how to behave in the new stage, how to leave the old stage behind.

I didn’t realize it when I started reading the book, but Brad had one of the quotes on the back cover that says it all:  “There are business books about starting a company, but they tend to deal with the mechanics of business plans and financing.  Then there are books about ‘how to be the CEO of a Fortune 500 company.’  This is the first book I’ve seen that details the role of the CEO of a small but growing company.”  Thanks to my colleague George Bilbrey for pointing this one out to me.

UPDATE:  Brad corrects me and says that I should mention Jana Matthews, who co-wrote the book with Katherine Catlin and is actually the Kauffman Center person of the duo.

Book Short:  Great Marketing Checklists

Trade Show and Event Marketing:  Plan, Promote, and Profit, by our direct marketing colleague Ruth Stevens, is hardly a page-turner, but it is a great read and well worth the money for anyone in your B2B marketing department.  That’s true as much for the event marketing specialist as the marketing generalist.

The author brings a very ROI-focused approach to planning and executing events – whether big trade shows or smaller corporate events, which are becoming increasingly popular in recent years for cost, focus, and control reasons.  But beyond events, the book has a number of excellent checklists that are more general for marketers that I found quite useful both as a reminder of things we should be doing at Return Path as well as ways we should be thinking about the different elements of our B2B marketing mix.

Some of the best tables and charts include:  strengths, weaknesses, and best applications of trade shows vs. corporate events; comparative analysis of marketing tools by channel (this was great – talks about best applications for all major tools from events to newsletters to search to inside sales); 12-month exhibitor timeline for trade shows; a great riff on bad booth signage vs. good booth signage (hint:  don’t make the visitor do the work – be obvious!); business event strategic planning grid; pre-show campaign and post-show follow-up checklists; dos, don’ts and options for corporate events; a great section on qualifying and handling leads that extends well beyond trade shows; and several good case studies that are show-focused.

Thanks to Ruth herself for an autographed copy!  Team Marketing and sales leaders at Return Path – your copies are on the way.

Book Short:  Allegory of Allegories

Squirrel, Inc., by Stephen Denning, is a good quick read for leaders who want a refreshing look at effective ways to motivate and communicate to their teams. The book focuses on storytelling as a method of communication, and Denning employs the storytelling method fairly successfully as a framework for the book.

The specific kinds of messages he focuses on, where he says storytelling can have the biggest impact, are:  communicating a complex idea and sparking action; communicating identity – who YOU as leader are; transmitting values; getting a group or team to work together more effectively; neutralizing gossip or taming the grapevine; knowledge-sharing; and painting a vision of the future that a team can hang onto.   The book even has a nice summary “how to” table at the end of it.

Thanks to email guru David Baker at Agency.com for giving me the book.

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:  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:  Tales of Two Cities

Return Path is basically dual-headquartered in New York City and Broomfield, Colorado, so two recently published books which provide history and insights into the tech industry in those two cities were both of interest to me.

Startup Communities: Building an Entrepreneurial Ecosystem in Your City, by Brad Feld (book, kindle) came out a few months ago and is part of Brad’s Startup Revolution series which will also include my upcoming book Startup CEO, to be published this fall.  In the book, Brad uses the example of the Boulder/Denver area and a few different sectors to demonstrate a blueprint to creating an entrepreneurial ecosystem – the kind that are popping up all over the world of late.

Tech and the City: The Making of New York’s Startup Community, by Alessandro Piol (kindle only) hits on many of the same themes and topics as they relate to New York City, although the book is more of a history of the New York tech scene than a framework with examples.  The book draws heavily on quotes from Fred Wilson, like Brad, a long time friend and Board member.  One of the things the book left me thinking about was what the New York tech scene will look like in 30 years after the new Cornell-Technion campus is up and running.  That plus the current momentum of the tech industry in New York, plus the sheer commercial scale of the city, could really produce an interesting environment down the road that actually starts to rival Silicon Valley, though rival probably isn’t the right word.

All in, these two books do a good job of chronicling the industry I work in, in the two cities where I work, but they also abstract nicely to broader principles about public-private collaboration as well as sector development.

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:  Legal Aid

The Entrepreneur’s Guide to Business Law, by Constance Bagley (HBS) and Craig Dauchy (Cooley Godward), while not exactly a page-turner, is a great reference book for even experienced CEOs. It’s pretty broad in its coverage of all major legal issues an entrepreneur will face, from patent law to firing employees.

Remember, you may make fun of lawyers on occasion or grips about their fees, but they DID attend law school for three years, after all. If nothing else, the $20 on this book will almost certainly save you at least 10x that in reduced legal fees someday, for something.

Book Short:  Next, Write a Sequel

Written by Rodd Wagner and James K. Harter and billed as “the long awaited sequel to First, Break All the Rules” (one of the best management books I’ve ever read), I thought 12: The Elements of Great Managing, was good, but not great.  12…, along with the original book First… and Now, Discover Your Strengths, the latter two both by Marcus Buckingham, are all based on an extensive database of research done on corporate America by the Gallup organization over many years.  All three are valuable reads in one way or another, although I found this to be the weakest of the three.  (Note that Now… is different from the other two in that it’s not about management, it’s about self-management — very different, though based on the same research.)

Anyway, the elements of great managing, so say the authors, is all about creating employee engagement.  I totally buy into that.  And since no book short on 12… would be complete if it didn’t list out the 12…

1. Do I know what is expected of me at work?
2. Do I have the materials and equipment I need to do my work right?
3. At work, do I have the opportunity to do what I do best every day?
4. In the last seven days, have I received recognition or praise for doing good work?
5. Does my supervisor, or someone at work, seem to care about me as a person?
6. Is there someone at work who encourages my development?
7. At work, do my opinions seem to count?
8. Does the mission/purpose of my company make me feel my job is important?
9. Are my co-workers committed to doing quality work?
10. Do I have a best friend at work?
11. In the last six months, has someone at work talked to me about my progress?
12. This last year, have I had the opportunities at work to learn and grow?

The book fleshes out each of the 12, gives examples (some of which are better/clearer than others), and then addresses compensation in a very interesting chapter at the end.  Key takeaways on comp:

– Higher pay doesn’t guarantee greater engagement
– Good and bad employees are equally likely to think they deserve a raise
– Money without meaning isn’t enough
– Most employees, most of the time, feel undercompensated
– Individual pay can/should be private, but comp criteria should be very public
– People who feel well-compensated generally work harder

The book also cites a very provocative article suggesting that organizations would handle comp better if they made everyone’s comp public (in contrast to the final bullet above, yes).  I’m going to write more about compensation in future postings, so I’ll leave this section on those notes.

Finally, the book’s two closing thoughts are perhaps its most prescient:  one critical element of BEING a great manager is HAVING a great manager; and the managers who put the most into their people, get the most out of their people.

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!