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: The Anti-Level-5 Leader

The Five Temptations of a CEO, another short leadership fable in a series by Patrick Lencioni, wasn’t as meaningful to me as the last one I read, The Four Obsessions of an Extraordinary Executive (post, link), but it wasn’t bad and was also a quick read.

The book to me was the 30 minute version of all the Level-5 Leadership stuff that Collins wrote about in Good to Great and Built to Last. All that said, it was a good quick read and a reminder of what not to do. The temptations are things that most CEOs I’ve ever known (present company very much included) have at least succumbed to at one point or another in their career. That said, you as a CEO should quit or be fired if you have them in earnest, so hopefully if you do have them, you recognize it and have them in diminishing quantities with experience, and hopefully not all at once:

– The temptation to be concerned about his or her image above company results

– The temptation to want to be popular with his or her direct reports above holding them accountable for results

– The temptation to ensure that decisions are correct, even if that means not making a decision on limited information when one is needed

– The temptation to find harmony on one’s staff rather than have productive conflict, discussion, and debate

– The temptation to avoid vulnerability and trust in one’s staff

I’m still going to read the others in Lencioni’s series as well. They may not be the best business books ever written, but they’re solid B/B+s, and they’re short and simple, which few business books are and all should be!

Book Short:  Crazy Eights

In honor of Return Path being in the midst of its eighth year, I recently read a pair of books with 8 in the title (ok, I would have read them anyway, but that made for a convenient criterion when selecting out of my very large “to read” pile).

Ram Charan’s latest, Know-How:  The 8 Skills That Separate People People Who Perform From Those Who Don’t, was pretty good and classic Charan.  Quick, easy to skim and still get the main points.  The book lost a little credibility with me when Charan lionized Verizon (perhaps he uses a different carrier himself) and Bob Nardelli (the book was published before Nardelli’s high profile dismissal), but makes good points nonetheless.  Some of the 8 Skills he talks about are what you’d expect on the soft side of leadership — building the team, understanding the social system, judging people — but his best examples were particularly actionable around positioning, goal setting, and setting priorities.  The book reminded me much more of Execution and much less of Confronting Reality (which is a good thing).

For years I’ve felt like the last person around to still not have read The 7 Habits of Highly Effective People, so I thought I’d skip straight to the punchline and read Stephen Covey’s newer book, The 8th Habit:  From Effectiveness to Greatness.  Fortunately, as I’d hoped, the new book summarizes the prior book several times over, so if you haven’t read the first, you could certainly just start with this one.  The book also comes with a DVD of 16 short films, some of which are great — both inspirational and poignant.  Unlike most business books, the 8th Habit is NOT skimmable.  It almost has too much material in it and could probably be read multiple times or at least in smaller pieces.  The actual 8th habit Covey talks about is what he calls Find Your Voice and Help Others Find Their Voices and is a great encapsulation of what leading a knowledge worker business is all about.  But the book is much deeper and richer than that in its many models and frameworks and examples/tie-ins to business and goes beyond the “touchy feely” into hard-nosed topics around execution and strategy.

Now I’m looking for the DVD of the first season of Eight is Enough!

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.

This post was inspired by Startup CXO and was originally published by Techstars on The Line.

If you’re new to the Chief Customer Officer role, we’d like to share some advice we wish we had learned earlier in our careers. There are a few common misconceptions about customers and the service organization. If you don’t realize these as misperceptions, you can spend a lot of time dealing with issues that are not real, but perceived. We have identified five of these common misperceptions, although we are sure there are more.

Misperception #1: The service organization fully controls churn (customer attrition)

In a lot of organizations you’ll see the service organization be measured solely on customer churn. If you really think about it, there are many elements that come into play that impact churn, including

• How the customer is sold
• The quality of the product
• How easy it is to onboard the customer
• How easy it is to use the product
• How easy it is for the customer to understand what kind of value they’re getting out of the product

Of course, the service functions do have a critical role, but they’re not the only functions in a company that impact churn. The responsibility for churn also lies with sales, engineering, marketing, and other teams. One reason why you need a C-level senior person in charge of all service operations is because you need someone who understands the customer experience broadly and that person has to work cross-functionally to ensure customer retention.

Misperception #2: The service organization is just a cost center

In many businesses, if a function isn’t generating new revenue, it’s seen as “second class.” From our perspective revenue retained is revenue gained and the service organization has a big impact on retaining revenue. In addition, the account management portion of a service organization is often in charge of up-sale and cross-sale opportunities which can be huge areas of growth. CCOs should work within their company to alter that misperception of service as a cost center because the service organization can have a huge impact on revenues.

Misperception #3: Service teams should focus on responding to defections

I’ve recently found a situation where the customer success team is built to focus on the clients who have raised their hand and said, “I want to leave.” This reactive approach drives low job satisfaction and isn’t the “best and highest use” of a service team’s time. By the time a customer is frustrated enough, or isn’t seeing the value enough, that they want to leave — you’ve missed a window of opportunity. The right focus should be proactively helping customers reach their desired business objectives. If you can do that, most customers will stay. That’s the theory behind the rise of the customer success team and that’s what great companies are doing today.

Misperception #4: Service’s job is to “paper over” gaps in the product

There is a widespread practice of covering for product issues by throwing service at the problem. That certainly can work, but it’s not optimal. The superior approach is to focus the service team on becoming a trusted advisor for customers, helping those customers achieve their desired outcomes. To do that, the CCO will have to work cross-functionally with the product team, the marketing team, and the sales team to drive a more friction-free customer experience.

Misperception #5: Service is boring and tactical

There is a wide-spread misperception that working in the service organization is boring. It’s mundane, it’s tactical, it doesn’t appeal to people who think strategy is grander than tactics. I don’t agree with that at all. A great service organization starts with a strategy. It starts with an understanding of customer segmentation. It includes thinking about the different customer personas and how to define an appropriate and valuable customer experience. That core strategy actually takes a while to develop. Once the strategy takes hold, it is core to driving retention over time. And, while a lot of people perceive that the service organization jobs are boring, or just answering trouble tickets or reacting to client problems, that’s not the whole role. It is a strategic role as well. 

The Chief Customer Officer has a big impact on the success of a company, especially startups and scaleups, and their function touches nearly every aspect of a company. To give your company the best chance of scaling, the Chief Customer Officer should understand, pinpoint, and manage misperceptions so that they can devote their time, energy, and resources to the real problems that help customers.

Startup CEO (OnlyOnce – the book!)

One of the things I’ve often thought over the years since starting Return Path in 1999 is that there’s no instruction manual anywhere for how to be a CEO.  While big company CEOs are usually groomed for the job for years, startup CEOs aren’t…and they’re often young and relatively inexperienced in business in general.  That became one of the driving forces behind the creation of my blog, OnlyOnce (because “you’re only a first time CEO once”) back in 2004.

Now, over 700 blog posts later, I’m excited to announce that I’m writing a book based on this blog called Startup CEO:  A Field Guide to Building and Running Your Company.  The book is going to be published by Wiley & Sons and is due out next summer.  The book won’t just be a compendium of blog posts, but it will build on a number of the themes and topics I’ve written about over the years and also fill in lots of other topics where I haven’t.

The catalyst for writing this book was Brad Feld.  Brad has been a friend, mentor, investor, and Board member for over a decade.  We’ve had many great times, meals, and conversations together over the years, not the least of which was staggering across the finish line together at the New York City Marathon in 2005.  Brad started writing books a few years ago, and I’ve been peripherally involved with them, first with Do More Faster:  TechStars Lessons to Accelerate Your Startup (I contributed one of the chapters) and then with Venture Deals:  Be Smarter Than Your Lawyer and Venture Capitalist (I wrote all the “Entrepreneur Perspective” sidebars).

Those are great books, and they’ve been incredibly well received by the global entrepreneurial community.  But then Brad got the bug, and now he’s in the middle of writing FOUR new books with Wiley that will all come out over the next year.  They are:

• Startup Communities:  Building an Entrepreneurial Ecosystem in Your City
• Startup Life:  Surviving and Thriving in a Relationship with an Entrepreneur
• Startup Metrics:  Making Sense of the Numbers in Your Startup
• Startup Boards:  Reinventing the Board of Directors to Better Support the Entrepreneur

These four books, plus the two earlier ones, plus Startup CEO, are all part of the Startup Revolution series.  While I’ll continue to do most of my blogging and posting here on OnlyOnce, I’d also encourage you to check out the Startup Revolution site and sign up to be a member of that community.  I’ll be doing some things on that site as well in connection with Startup CEO, and it’s a more concentrated place to post and comment on all things Startup.  In addition, we’ll be putting a bunch of add-ons to the book on that site closer to publication time.

I hope Startup CEO becomes a standard for all new CEOs.  I don’t think I have all the answers, but at least others can benefit by learning from my 13 years of successes and mistakes!  Now all I have to do is go write the darned thing.

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: Wellness Redefined

Well Being: The 5 Essential Elements, by Tom Rath and Jim Harter from the Gallup organization, is a solid read and incredibly short. It’s one of those books that’s really a long article stretched and bound. But it goes beyond the basics of what I expected, which was something like “having healthy employees cuts down on absenteeism” and has a couple great elements of food for thought for leaders looking to build cutting edge and uber-productive organizations. It comes out of the same general body of research as four other very strong books I’ve written about over time — First, Break all the Rules, Now, Discover Your Strengths, 12: The Great Elements of Managing (book, review), and Go Put Your Strengths to Work (book, review).

The authors define well being as having five separate components:  career well being, social well being, physical well being, financial well being, and community well being. Ok, that makes sense, but the three most interesting points the book made from my perspective were:

1. Well being isn’t just about one of these five elements – it’s about all five, and how they interact together, and how the workplace can support all of them
2. Achieving long-term objectives around well being requires finding short-term incentives that drive the same behavior in more obvious and immediate ways, as most long-term well being drivers require short term sacrifice. So figure out how to make eating a salad better for you not just years from now but TODAY (you’ll have more energy after lunch than if you eat that cheeseburger), for example
3. Financial well being isn’t something a lot of companies focus on, and maybe it should be. Particularly in our industry we hire knowledge workers and assume therefore that they’re smart and educated about everything…but maybe there are ways that the company can support financial well being that aren’t necessarily obvious

The book is full of stats from the underlying research, most of which show that most people are shockingly unhappy, and that most workplaces dont do enough to support employee wellness. The book also notes, as is the case with most things, that promoting well being among employees requires more than just setting up programs. Doing it right requires constant vigilance, measurement, and follow up. At Return Path, we do a bunch of programs along the lines suggested by the book (but can and should do more!), but we’ve never been rigorous with follow up. Good food for thought.

Note there is also a free whitepaper on the economics of well being that you can download here.  The white paper is ok…but not nearly as interesting as the book, and note that it does not substitute for the book.  Thanks to my colleague Cathy Hawley for this book!

Book (Not So) Short:  Raise Your Hand If You’re Sure

I couldn’t get the catchy jingle from the 80’s commercial for Sure deodorant (you remember, the one with the Statue of Liberty at the end of it – thanks, YouTube) out of my head while I was reading the relatively new book, Confidence: How Winning Streaks and Losing Streaks Begin and End.  Written by HBS professor Rosabeth Moss Kantor, Confidence is one of the few business books I’ve read that’s both long and worth reading in full.

The book has scores of examples of both winning and losing streaks, from sports, business, politics, and other walks of life, and it does a great job of breaking down the core elements that go into creating a winning streak or turnaround (Accountability, Collaboration, Innovation).  Kantor also puts a very fine point on the “doom loop” of losing streaks and just how hard it is to turn them around.  The book also has a good crisp definition of why winning streaks end — arrogange, anyone? — and has consistent, but not preachy recipes for avoiding pitfalls and driving success.  All in all, very inspirational, even if many of the roots of success lie in well-documented leadership qualities like those expressed in Jim Collins’ Built to Last and Good to Great.  The book is good enough that Kantor can even be forgiven for lauding Verizon, probably the most consistently awful customer service company I’ve ever dealt with.

But even more of the roots of success and disappointment around streaks are psychological, and these examples really rang true for me as I reflected back on our acquisition of the troubled NetCreations in 2004.  That company was in the midst of a serious slump, a losing streak dating back to 2000, at the peak of the original Internet boom.  Year over year, the company had lost revenues, profits, customers, and key personnel.  Its parent company saw poor results and set it into the doom loop of starving it for resources and alternating between ignoring it and micromanaging it, and when we acquired the business, we found great assets and some fantastic people (many of whom I’m proud to say are still with us today), but a dispirited, blame-oriented, passive culture that was poised to continue wallowing in decline.

I can hardly claim that we’ve turned the business around in full, or that I personally made happen whatever turnaround there has been, but I do think we did a few things right as far as Kantor and Confidence would see it.  Her formula for a turnaround (Espouse the new message, Exemplify it with leadership actions, Establish programs to systematically drive it home throughout the organization) is right in line with our philosophy here at Return Path.

First, we accelerated the separation and autonomy of a fledgeling NetCreations spin-off unit, now our Authentic Response market research group, and let a culture of collaboration and innovation flourish under an exceptionally talented leader, Jeff Mattes.

But that was the easy part (for me anyway), because that part of the business was actually working well, and we just let it do its thing, with more support from HQ.  The turnaround of the core list rental and lead generation business of NetCreations, the original Postmaster Direct, was much tougher and is still a work in progress.  In the last six months, we’ve finally turned the corner, but it hasn’t been easy.  Even though we knew lots of what had to be done early on, actually doing it is much harder than b-school platitudes or even the best-written books make it seem.

The one thing that Kantor probably gives short shrift to, although she does mention it in passing a couple times, is that frequently turnarounds require massive major amounts of purging of personnel (not just management) to take hold.  As one of my former colleagues from Mercer Management Consulting used to say, “sometimes the only way to effect Change Management is to change management.”  Sometimes even very talented people are just bogged down with baggage — the “ghost of quarters past” — and nothing you do or say can break that psychological barrier.

Boy, have we learned that lesson here at Return Path the hard way.  I’m extremely grateful to our team at Return Path, from the old RP people who’ve seen it all happen, to the old NetCreations people who are thriving in the new environment, to the new blood we’ve brought in to help effect the turnaround, for playing such important roles in our own Confidence-building exercises here.  And I’m super Confident that 2007 will be the year that we officially turn the old NetCreations/Postmaster losing streak into a big, multi-year winning streak.

Anyway, I realize this may redefine the “short” in book short, but Confidence is without question a good general management and leadership read.

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.

Book Short:  Required Reading, Part II

Every once in a while, a business book nails it from all levels.  Well written, practical, broadly applicable to any size or type of organization, full of good examples, full of practical tables and checklists.   The Leadership Pipeline, which I wrote about here over six years ago, is one of those books — it lays out in great and clear detail a framework for understanding the transition from one level to another in an organization and how work behaviors must change in order for a person to succeed during and on the other side of that transition.  In an organization like Return Path‘s which is rapidly expanding and promoting people regularly, this is critical.  We liked the book so much that we have adopted a lot of its language and have built training courses around it.

The book’s sequel, The Performance Pipeline (book, Kindle), also by Stephen Drotter but without the co-authors of the original book, is now out — and it’s just as fantastic.  The book looks at the same six level types in an organization (Enterprise Manager, Group Manager, Business Manager, Functional Manager, Manager of Managers, Manager of Others, and Self Managers/Individual Contributors) and focuses on what competencies people at each level must have in order to do their jobs at maximum effectiveness — and more important, in order to enable the levels below them to operate in an optimal way.

This book is as close to a handbook as I’ve ever seen for “how to be a CEO” or “how to be a manager.”  Coupled with its prequel, it covers the transition into the role as well as the role itself, so “how to become a CEO and be a great one.”  As with the prequel, the author also takes good care to note how to apply the book to a smaller organization (from the below list, usually the top three levels are combined in the CEO, and often the next two are combined as well).  No synopsis can do justice to this book, but here’s a bit of a sense of what the book is about:

• Enterprise Manager:  role is to Perpetuate the Enterprise and develop an Enterprise-wide strategic framework – what should we look like in 15-20 years, and how will we get the resources we need to get there?
• Group Manager:  role is to manage a portfolio of businesses and develop people to run them
• Business Manager:  role is to optimize short- and long-term profit and develop business-specific strategies around creating customer and stakeholder value
• Functional Manager:  role is to drive competitive advantage and functional excellence
• Manager of Managers:  role is to drive productivity across a multi-year horizon, and focus
• Manager of Others:  role is to enable delivery through motivation, context setting, and talent acquisition
• Self Managers/Individual Contributors:  role is to deliver and to be a good corporate citizen

I could write more, but there’s too much good stuff in this book to make excerpts particularly useful.  The Performance Pipeline is another one of those rare – “run, don’t walk, to buy” books.  Enjoy.  For many of my colleagues at RP – look out – this one is coming!