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

Running a Productive Offsite

A couple OnlyOnce readers asked me to do a post on how I run senior team offsites.  It’s a great part of our management meeting routine at Return Path, and one that Patrick Lencioni talks about extensively in Death by Meeting (review, book) – a book worth reading if you care about this topic.

My senior team has four offsites per year.  I love them.  They are, along with my Board meetings, my favorite times of the year at work.  Here’s my formula for these meetings:

–          WHY:  There are a few purposes to our offsites.  One for us is that our senior team is geographically distributed across 4 geographies at the executive level and 6 or 7 at the broader management team level.  So for us, these are the only times of the year that we are actually in the same place.  But even if we were all in one place, we’d still do them.  The main purpose of the offsite is to pull up from the day-to-day and tackle strategic issues or things that just require more uninterrupted time.  The secondary purpose is to continue to build and develop the team, both personal relationships and team dynamics.  It’s critically important to build and sustain deep relationships across the Executive Team.  We need this time in order to be a coordinated, cohesive, high trust, aligned leadership team for the company.  As the company has expanded (particularly to diverse geographies), our senior team development has become increasingly critical

–          WHO:  Every offsite includes what we call our Executive Committee, which is for the most part, my direct reports, though that group also includes a couple C/SVP titled people who don’t report directly to me but who run significant parts of the company (7-8 people total).  Two of the four offsites we also invite the broader leadership team, which is for the most part all of the people reporting into the Executive Committee (another 20 people).  That part is new as we’ve gotten bigger.  In the earlier days, it was just my staff, and maybe one or two other people as needed for specific topics

–          WHERE:  Offsites aren’t always offsite for us.  We vary location to make geography work for people.  And we try to contain costs across all of them.  So every year, probably 2 of them are actually in one of our offices or at an inexpensive nearby hotel.  Then the other 2 are at somewhat nicer places, usually one at a conference-oriented hotel and then one at a more fun resort kind of place.  Even when we are in one of our offices, we really treat it like an offsite – no other meetings, etc., and we make sure we are out together at dinner every night

–          WHEN:  4x/year at roughly equal intervals.  We used to do them right before Board meetings as partial prep for those meetings, but that got too crowded.  Now we basically do them between Board meetings.  The only timing that’s critical is the end of year session which is all about budgeting and planning for the following year.  Our general formula when it’s the smaller group is two days and at least one, maybe two dinners.  When it’s the larger group, it’s three days and at least two dinners.  For longer meetings, we try to do at least a few hours of fun activity built into the schedule so it’s not all work.

–          WHAT:  Our offsites are super rigorous.  We put our heads together to wrestle with (sometimes solve) tough business problems – from how we’re running the company, to what’s happening with our culture, to strategic problems with our products, services and operations.  The agenda for these offsites varies widely, but the format is usually pretty consistent.  I usually open every offsite with some remarks and overall themes – a mini-state-of-the-union.  Then we do some kind of “check-in” exercise either about what people want to get out of the offsite, or something more fun like an envisioning exercise, something on a whiteboard or with post-its, etc.  We always try to spend half a day on team and individual development.  Each of us reads out our key development plan items from our most recent individual 360, does a self-assessment, then the rest of the team piles on with other data and opinions, so we keep each other honest and keep the feedback flowing.  Then we have a team development plan check-in that’s the same, but about how the team is interacting.  We always have one or two major topics to discuss coming in, and each of those has an owner and materials or a discussion paper sent out a few days ahead of time.  Then we usually have a laundry list of smaller items ranging from dumb/tactical to brain-teasing that we work in between topics or over meals (every meal has an agenda!).  There’s also time at breaks for sub-group meetings and ad hoc conversations.  We do try to come up for air, but the together time is so valuable that we squeeze every drop out of it.  Some of our best “meetings” over the years have happened side-by-side on elliptical trainers in the hotel gym at 6 a.m.  We usually have a closing check-out, next steps recap type of exercise as well.

–          HOW:  Lots of our time together is just the team, but we usually have our long-time executive coach Marc Maltz from Triad Consulting  facilitate the development plan section of the meeting.

I’m sure I missed some key things here.  Team, feel free to comment and add.  Others with other experiences, please do the same!

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: Hire Great

It’s certainly not hiring season for most of America The World The Universe, but we are still making some limited hires here at Return Path, and I thought – what better time to retool our interviewing and hiring process than in a relatively slow period?

So I just read Who: The A Method for Hiring, by Geoff Smart and Randy Street.  It’s a bit of a sequel, or I guess more of a successor book, to the best book I’ve ever read about hiring and interviewing, Topgrading, by Geoff Smart and his father Brad (post, link to buy).  This one wasn’t bad, and it was much shorter and crisper.

I’m not sure I believe the oft-quoted stat that a bad hire costs a company $1.5mm.  Maybe sometimes (say, if the person embezzles $1.4mm), but certainly the point that bad hires are a nightmare for an organization in any number of ways is well taken.   The book does a good job of explaining the linkage from strategy and execution straight to recruiting, with good examples and tips for how to create the linkage.  That alone makes it a worthwhile read.

The method they describe may seem like common sense, but I bet 95 out of 100 companies don’t come close.  We are very good and quite deliberate about the hiring process and have a good success average, but even we have a lot of room to improve.  The book is divided into four main sections:

• Scorecard: creating job descriptions that are linked to company strategy and that are outcome and competency based, not task based
• Sourcing: going beyond internal and external recruiters to make your entire company a talent seeker and magnet
• Selection: the meat of the book – good detail on how to conduct lots of different kinds of interviews, from screening to topgrading (a must) to focused to reference
• Sell:  how to reel ’em in once they’re on the line (for us anyway, the least useful section as we rarely lose a candidate once we have an offer out)

One of the most poignant examples in the book centered around hiring someone who had been fired from his previous job.  The hiring method in the book uncovered it (that’s hard enough to do sometimes) but then dug deep enough to understand the context and reasons why, and, matching up what they then knew about the candidate to their required competencies and outcomes for the job, decided the firing wasn’t a show-stopper and went ahead and made the hire.

I’d think of these two books the way I think about the Covey books.  If you have never read The 7 Habits of Highly Effective People, you could just get away with reading Stephen Covey’s newer book, The 8th Habit:  From Effectiveness to Greatness, though the original is much richer.

Boards That Lead, by Ram Charan, Dennis Carey, and Michael Useem, was recommended to me by a CEO Coach in the Bolster network, Tim Porthouse, who said he’s been referring it to his clients alongside Startup Boards. I don’t exactly belong in the company of Ram Charan (Brad and Mahendra probably do!), so I was excited to read it. While it’s definitely the “big company” version to Startup Boards, there are some good lessons for startup CEOs and founder to take away from it.

The best part about the book as it relates to ALL boards is the framework of Partner, Take Charge, Stay out of the Way, and Monitor. You can probably lump all potential board activities into these four buckets. If you look at it that way…these are pretty logical:

• Monitor – what you’d expect any board to do
• Stay out of the Way – basic execution/operations
• Partner – strategy, goals, risk, budget, leadership talent development
• Take Charge – CEO hiring/firing, Exec compensation, Ethics, and Board Governance itself.

There was an interesting nugget in the book as well called the Central Idea that I hadn’t seen articulated quite this way before. It’s basically a statement of what the business is and how it’s going to win. It’s about a page long, 8-10 bullet points, and it includes things like mission, strategy, key goals, and key operating pillars that underlie the goals. It basically wraps up all of Lencioni’s key questions in one page with a little more meat on the bones. I like it and may adopt it. The authors put the creation of the Central Idea into the Take Charge bucket, but I’d put it squarely in the Partner bucket.

Other than that, the book is what you’d expect and does have a lot of overlap with the world of startups. Its criteria for director selection are very similar to what we use at Bolster, as is its director evaluation framework. The book has a ton of handy checklists as well, some of which are more applicable than others to startups, for example Dealing with Nonperforming Directors and Spotting a Failing CEO.

All in, a good read if you’re a student of Boards.

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.

Half the Benefit is in the Preparation

This past week, we had what has become an annual tradition for us – a two-day Board meeting that’s Board and senior management (usually offsite, not this year to keep costs down) and geared to recapping the prior year and planning out 2009 together.  Since we are now two companies, we did two of them back-to-back, one for Authentic Response and the other for Return Path.

It’s a little exhausting to do these meetings, and it’s exhausting to attend them, but they’re well worth it.  The intensity of the sessions, discussion, and even social time in between meetings is great for everyone to get on the same page and remember what’s working, what’s not, and what the world around us looks like as we dive off the high dive for another year.

The most exhausting part is probably the preparation for the meetings.  We probably send out over 400 pages of material in advance – binders, tabs, the works.  It’s the only eco-unfriendly Board packet of the year.  It feels like the old days in management consulting.  It takes days of intense preparation — meetings, spreadsheets, powerpoints, occasionally even some soul searching — to get the books right.  And then, once those are out (the week before the meeting), we spend almost as much time getting the presentations down for the actual meeting, since presenting 400 pages of material that people have already read is completely useless.

By the end of the meetings, we’re in good shape for the next year.  But before the meetings have even started, we’ve gotten a huge percentage of the benefit out of the process.  Pulling materials together is one thing, but figuring out how to craft the overall story (then each piece of it in 10-15 minutes or less) for a semi-external audience is something entirely different.  That’s where the rubber meets the road and where good executives are able to step back; remember what the core drivers and critical success factors are; separate the laundry list of tactics from the kernel that includes strategy, development of competitive advantage, and value creation; and then articulate it quickly, crisply, and convincingly. 

I’m incredibly proud of how both management teams drove the process this year – and I’m charged up for a great 2009 (economy be damned!).

Book Short:  Internet Fiction

It’s been a long time since I read Tom Evslin’s Hackoff.com, which Tom called a “blook” since he released it serially as a blog, then when it was all done, as a bound book.  Mariquita and I read it together and loved every minute of it.  One post I wrote about it at the time was entitled Like Fingernails on a Chalkboard.

The essence of that post was “I liked it, but the truth of the parts of the Internet bubble that I lived through were painful to read,” applies to two “new” works of Internet fiction that I just plowed through this week, as well.

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.

The Circle

While not quite as new, The Circle  has been on my list since it came out a few months back and since Brad’s enticing review of it noted that:

The Circle  was brilliant. I went back and read a little of the tech criticism and all I could think was things like “wow – hubris” or “that person could benefit from a little reflection on the word irony”… We’ve taken Peter Drucker’s famous quote “‘If you can’t measure it, you can’t manage it” to an absurd extreme in the tech business. We believe we’ve mastered operant conditioning through the use of visible metrics associated with actions individual users take. We’ve somehow elevated social media metrics to the same level as money in the context of self-worth.

So here’s the scoop on this book.  Picture Google, Twitter, Facebook, and a few other companies all rolled up into a single company.  Then picture everything that could go wrong with that company in terms of how it measures things, dominates information flow, and promotes social transparency in the name of a new world order.  This is Internet dystopia at its best – and it’s not more than a couple steps removed from where we are.  So fiction…but hardly science fiction.

The Circle  is a lot longer than Uncommon Stock and quite different, but both are enticing reads if you’re up for some internet fiction.

Pret a Manager

My friend James is the GM of the Pret a Manger (a chain of about 250 “everyday luxury” quick service restaurants in the UK and US) at 36th and 5th in Manhattan.  James recently won the President’s Award at Pret for doing an outstanding job opening up a new restaurant.  As part of my ongoing effort to learn and grow as a manager, I thought it would be interesting to spend a day shadowing James and seeing what his operation and management style looked like for a team of two dozen colleagues in a completely different environment than Return Path.  That day was today.  I’ll try to write up the day as combination of observations and learnings applied to our business.  This will be a much longer post than usual.  The title of this post is not a typo – James is “ready to manage.”

1. Team meeting.  The day started at 6:45 a.m. pre-opening with a “team brief” meeting.  The meeting only included half a dozen colleagues who were on hand for the opening, it was a mix of fun and serious, and it ended with three succinct points to remember for the day.  I haven’t done a daily huddle with my team in years, but we do daily stand-ups all across the company in different teams.  The interesting learning, though, is that James leaves the meeting and writes the three points on a whiteboard downstairs near the staff room.  All staff members who come in after the meeting are expected to read the board and internalize the three points (even though they missed the meeting) and are quizzed on them spontaneously during the day.  Key learning:  missing a meeting doesn’t have to mean missing the content of the meeting.

2. Individual 1:1 meeting.  I saw one of these, and it was a mix of a performance review and a development planning session.  It was a little more one-way in communication than ours are, but it did end up having a bunch of back-and-forth.  James’s approach to management is a lot of informal feedback “in the moment,” so this formal check-in contained no surprises for the employee.  The environment was a little challenging for the meeting, since it was in the restaurant (there’s no closed office, and all meetings are done on-site).  The centerpiece of the meeting was a “Start-Stop-Continue” form.  Key learning:  Start-Stop-Continue is a good succinct check-in format.

3. Importance of values.  There were two forms of this that I saw today.  One was a list of 13 key behaviors with an explanation next to each of specific good and bad examples of the behavior.  The behaviors were very clear and were “escalating,” meaning Team Members were expected to practice the first 5-6 of them, Team Leads the first 7-8, Managers the first 10, Head Office staff the first 12, Executives all 13 (roughly).  The second was this “Pret Recipe,” as posted on the public message board (see picture below).  Note – just like our values at Return Path, it all starts with the employee.  One interesting nugget I got from speaking to a relatively new employee who had just joined at the entry level after being recruited from a prominent fast food chain where he had been a store general manager was “Pret really believes this stuff — no lip service.”

I saw the values in action in two different ways.  The first was on the message board, where each element of the Pret Recipe was broken out with a list of supporting documents below it, per the below photo.  Very visual, very clear.

The second was that in James’s team meeting and in his 1:1 meeting, he consistently referenced the behaviors.  Key learning:  having values is great, making them come to life and be relevant for a team day-in, day-out is a lot harder but quite powerful when you get it right.

4. Managing by checklist.  I wrote about this topic a while ago here, but there is nothing like food service retail to demand this kind of attention to detail.  Wow.  They have checklists and standards for everything.  Adherence to standards is what keeps the place humming.  Key learning:  it feels like we have ~1% of the documentation of job processes that Pret does, and I’m thinking that as we get bigger and have people in more and more locations doing the same job, a little more documentation is probably in order to ensure consistency of delivery.

5. Extreme team-based and individual incentive compensation.  Team members start at $9/hour (22% above minimum wage that most competitors offer).  However, any week in which any individual store passes a Mystery Shopper test, the entire staff receives an incremental $2/hour for the whole week.  Any particular employee who is called out for outstanding service during a Mystery Shop receives a $100 bonus, or a $200 bonus if the store also passes the test.  The way the math works out, an entry level employee who gets the maximum bonus earns a 100% bonus for that week.  But the extra $2/hour per team member for a week seemed to be a powerful incentive across the board.  Key learning: team-based incentive comp is something we use here for executives, but maybe it’s worth considering for other teams as well.

6. Integrated systems.  Pret has basically one single software system that runs the whole business from inventory to labor scheduling to finances.  All data flows through it directly from point of sale or via manager single-entry.  All reports are available on demand.  The system is pretty slick.  There doesn’t seem to be much use of side systems and side spreadsheets, though I’m sure there are some.  Key learning: there’s a lot to be said for having a little more information standardized across the business, though the flip side is that this system is a single point of failure and also much less flexible than what we have.

7. Think time.  I’ve written a little about working “on the business, not in the business,” or what I call OTB time, once before, and I have another post queued up for later this summer about the same.  Brad Feld also very kindly wrote about it in reference to Return Path last week.  Working in retail means that time to work on IMPORTANT BUT NOT URGENT issues is extremely hard to come by and fragmented.  I suspect that it comes more at the end of the day for James, and it probably comes a lot more when he doesn’t have someone like me observing him and asking him questions.  But his “office” (below), exposed to the loud music and sounds and smells of the kitchen, certainly doesn’t lend itself to think time!  Key learning:  of course customers come first, but boy is it critical to make space to work OTB, not just ITB.  Oh, and James needs a new chair that’s more ergonomically compatible with his high countertop desk.

Years ago, I spent a few weekends working in my cousin Michael’s wine store in Hudson, NY, and I wrote up the experience in two different posts on this blog, the first one about the similarities between running a 2-person company and a 200-person company, and the second one about how in a small business, you have to wear one of every kind of hat there is.  My conclusion then was that there are more similarities than differences when it comes to running businesses of different types.  My conclusion from today is exactly the same, though the focus on management made for a very different experience.

Thanks to James, Gustavo, Orlanda, Shawona, and the rest of the team at the 36th & 5th Pret for putting up with the distraction of me for the bulk of the day today — I learned a lot (and particularly enjoyed the NYC Meatball Hot Wrap) and now have to figure out how to return the favor to you!

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!