In Search of Automated Relevance

A bunch of us had a free form meeting last week that started out as an Email Summit focused on protocols and ended up, as Brad put it, with us rolling around in the mud of a much broader and amorphous Messaging Summit.  The participants (and some of their posts on the subject) in addition to me were Fred Wilson (pre, post), Brad Feld,  Phil Hollows, Tom Evslin (pre, post), and Jeff Pulver (pre, post).  And the discussion to some extent was inspired by and commented on Saul Hansell’s article in the New York Times about “Inbox 2.0” and how Yahoo, Google, and others are trying to make email a more relevant application in today’s world; and Chad Lorenz’s article in Slate called “The Death of Email” (this must be the 923rd article with that headline in the last 36 months) which talks about how email is transitioning to a key part of the online communications mix instead of the epicenter of online communications.

Ok, phew, that’s all the background. 

With everyone else’s commentary on this subject already logged, most of which I agree with, I’ll add a different $0.02.  The buzzword of the day in email marketing is “relevance.”  So why can’t anyone figure out how to make an email client, or any messaging platform for that matter, that starts with that as the premise, even for 1:1 communications?  I think about messaging relevance from two perspectives:  the content, and the channel.

Content.  In terms of the content of a message, I think of relevance as the combination of Relationship and Context.  The relationship is all about my connection to you.  Are you a friend, a friend of a friend, or someone I don’t know that’s trying to burrow your way onto my agenda for the day?  Are you a business that I know and trust, are you a carefully screened and targeted offer coming from an affiliate of a business I trust, or are you a spammer? 

But as important as the relationship is to the relevance of your message to me, the context is equally important.  Let’s take Brad as an example.  I know him in two distinct contexts:  as one of my venture investors, and as an occasional running partner.  A message from Brad (a trusted relationship) means very different things to me depending on its context.  One might be much more relevant than the other at any moment in my life.

Channel.  The channel through which I send or receive a message has an increasing amount to do with relevance as well.  As with content, I think of channel relevance as the combination of two things –  device, and technology.  For me, the device is limited to three things, two with heavy overlap.  The first is a fixed phone line – work or home (I still think cell service in this country leaves a lot to be desired).  The second is a mobile device, which could mean voice but could also mean data.  The third is a computer, whether desktop or laptop.  In terms of technology, the list is growing by the day.  Voice call, email, IM, Skype, text message, social network messaging, and on and on.

So what  do I mean about channel relevance?  Sometimes, I want to send a message by email from my smartphone.  Sometimes I want to send a text message.  Sometimes I want to make a phone call or just leave a voicemail.  Sometimes I even want to blog or Twitter.  I have yet to desire to send a message in Facebook, but I do sometimes via LinkedIn, so I’m sure I’ll get there.  Same goes for the receiving side.  Sometimes I want to read an email on my handheld.  Sometimes a text message does the job, etc.  Which channel and device I am interested in depends to some extent on the content of the message, per above, but sometimes it depends on what I’m doing and where I am.

So what?  Starting to feel complex?  It should be.  It is.  We all adjusted nicely when we added email to our lives 10 years ago.  It added some communication overhead, but it took the place of some long form paper letters and some phone calls as well.  Now that we seem to be adding new messaging channels every couple weeks, it’s becoming increasingly difficult to get the relevance right.  Overlaying Content (Relationship and Context) with Channel (Device and Technology) creates a matrix that’s very difficult to navigate.

How do we get to a better place?  Technology has to step in and save the day here.  One of the big conclusions from our meeting was that no users care about or even know about the protocol – they just care about the client they interact with.  Where’s the ultra flexible client that allows me to combine all these different channels, on different devices?  Not a one-size-fits-all unified messaging service, but something that I can direct as I see fit?  There are glimmers of hope out there – Gmail integrating IM and email…Simulscribe letting me read my voicemail as an email…Twitter allowing me to input via email, SMS, or web…even good old eFax emailing me a fax – but these just deal with two or three cells in an n-dimensional matrix.

As our CTO Andy Sautins says, software can do anything if it’s designed thoughtfully and if you have enough talent and time to write and test it.  So I believe this “messaging client panacea” could exist if someone put his or her mind to it.  One of the big questions I have about this software is whether or not relevance can be automated, to borrow a phrase from Stephanie Miller, our head of consulting.  Sure, there is a ton of data to mine – but is there ever enough?  Can a piece of software figure out on its own that I want to get a message from Brad about “running” (whatever channel it comes in on) as a text message on my smartphone if we’re talking about running together the next day, but otherwise as an RSS feed in the same folder as the posts from his running blog, but a voicemail from Brad about “running the company” (again, regardless of how he sends it) as an email automatically sorted to the top of my inbox?  Or do I have to undertake an unmanageable amount of preference setting to get the software to behave the way I want it to behave?  And oh by the way, should Brad have any say over how I receive the message, or do I have all the control?  And does the latter question depend on whether Brad is a person or a company?

What does this mean for marketers?  That’s the $64,000 question.  I’m not sure if truly Automated Relevance is even an option today, but marketers can do their best to optimize all four components of my relevance equation:  content via relationship and context, and channel via device and technology.  A cocktail of permission, deep behavioral analysis, segmentation, smart targeting, and a simple but robust preference center probably gets you close enough.  Better software that works across channels with built-in analytics – and a properly sized and whip smart marketing team – should get you the rest of the way there.  But technology and practices are both a ways off from truly automated relevance today.

I hope this hasn’t been too much rolling around in the mud for you.  All thoughts and comments (into my fancy new commenting system, Intense Debate) are welcome!

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

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!

Triple Book Short: For Parents

People who know me know that I am a voracious reader.  Among other things, I probably read about 25-30 books per year — and I wish I had time for more.  I probably read about 50% business books, which I blog about.  Most of my other reading is in a couple specific topical areas that interest me like American History and Evolutionary Biology.  Over the last few years, Mariquita and I have discovered and read a handful of books about parenting that have been foundational for us as we work deliberately at raising our three kids, and two of them have roots in some of the same philosophies, psychologies, and research as a lot of contemporary business literature.  So for parents everywhere, I thought I’d devote a book short to these three books.

The first one is Healthy Sleep Habits, Happy Child, by Marc Weissbluth.  Having kids who sleep long and well has been the foundation for us to have a well functioning household.  Well rested kids are much easier than tired ones.  Well rested parents are more effective.  We have found that the principles in this book have consistently served us well on this front.  All three of our kids more or less slept through the night starting at 6-8 weeks and have been great sleepers since then.

Unconditional Parenting, by Alfie Kohn is basically, for those in the HR/OD field, “Action/Design” for parenting.  The principles in this book have applied to kids as young as 1 year old, and the examples in the book go through the teenage years.  Our main learnings from this book have been around moving away from more traditional forms of reward, punishment, and control and towards helping our kids make decisions as opposed to follow directions by understanding our kids perspective on things, working to help them articulate their own understanding of a situation, and helping them see the perspective of others.

Raising an Emotionally Intelligent Child, by John Gottman, builds on a lot of the same underlying work that Daniel Goleman writes about in articles and business books around Emotional Intelligence (in fact, Goleman wrote the forward to this book as well).  The book lays out a process the author calls Emotional Coaching to help kids learn empathy and problem solving by showing kids empathy, teaching them to understand and label their own emotions, and working with them to craft solutions on their own, but doing the whole process in a very calm and 1:1 manner.  One of my favorite parts of the book, which is so unusual in business books and any kind of self-help book, is that the author has a whole section devoted to when NOT to use this process.

Parenting is a very personal thing, and there isn’t a right or wrong way to go about it.  I have a friend who is fond of saying that parenting is a little bit like the way comedian George Carlin used to describe “other drivers” on the highway.  People who are going slower than you are “a**holes” and people who are going faster than you are “crazy.”  Only you drive the “right way.”  So true, but if you’re a parent, there’s no more important thing to be deliberate about practicing than parenting, and these books have been a good practice guide for us.  We have found a full read of these three books to be very helpful to us in our work with our kids, and we have been very lucky that our main babysitter has been aligned with us on philosophy (and has been willing to read these books with us).

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

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.

I love the concept of Servant Leadership.  From the source, the definition is:

While servant leadership is a timeless concept, the phrase “servant leadership” was coined by Robert K. Greenleaf in The Servant as Leader, an essay that he first published in 1970. In that essay, Greenleaf said:

“The servant-leader is servant first… It begins with the natural feeling that one wants to serve, to serve first. Then conscious choice brings one to aspire to lead. That person is sharply different from one who is leader first, perhaps because of the need to assuage an unusual power drive or to acquire material possessions…The leader-first and the servant-first are two extreme types. Between them there are shadings and blends that are part of the infinite variety of human nature.

“The difference manifests itself in the care taken by the servant-first to make sure that other people’s highest priority needs are being served. The best test, and difficult to administer, is: Do those served grow as persons? Do they, while being served, become healthier, wiser, freer, more autonomous, more likely themselves to become servants? And, what is the effect on the least privileged in society? Will they benefit or at least not be further deprived?“

A servant-leader focuses primarily on the growth and well-being of people and the communities to which they belong. While traditional leadership generally involves the accumulation and exercise of power by one at the “top of the pyramid,” servant leadership is different. The servant-leader shares power, puts the needs of others first and helps people develop and perform as highly as possible.

This is a very broad societal definition, but it’s fairly easy to apply to a more narrow corporate, or even startup environment.  Are you as a CEO oriented primarily towards your people, or towards other stakeholders like customers or shareholders?  By the way, trying to do right by all three stakeholders is NOT a problem in a world of being oriented towards one.  It’s just a philosophy around which comes first, and why.  Our People First philosophy at Return Path is fair clear that at the end of the day, all three stakeholders win IF you do right by employees, so they do the best possible work for customers, so you build a healthy and profitable and growing business.

CEOs who practice Servant Leadership aren’t necessarily focused on power dynamics, or on helping those least privileged in society (at least not as part of their job)…but they are focused on making sure that their employees most important needs are met — both in the moment, as in making sure employees are empowered and not blocked or bottlenecked, and over the long haul, as in making sure employees have opportunities to learn, grow, advance their careers, make an impact, and have the ability to live a well balanced life.

I was in a meeting a couple weeks back with another leader and a few people on his team.  He *seemed* to practice Servant Leadership the way he was speaking to his team members.  But he wasn’t, really.  He was doing something I refer to as Sucking Down.  He was telling them things they clearly wanted to hear.  He was lavishing praise on them for minor accomplishments.  He was smiling and saying yes, when what he really meant was no.  He was practicing the art of Sucking Up, only to people on his team, not to a boss.  I got a sense that something wasn’t right during the meeting, and then post meeting, he actually fessed up to me — even bragged about it — that he was being disingenuous to get what he wanted out of his people.

There’s a clear difference between Servant Leadership and Sucking Down in the long run.  The danger comes in the moment.  Just as managers need to build good detection skills to sniff out evidence of someone on their team Sucking Up, employees need to be able to understand that clear difference in their managers’ behavior as they think about how to manage their careers, and even where to work.

Book Short:  Like Reading a Good Speech

Leaders Eat Last, by Simon Sinek, is a self-described “polemic” that reads like some of the author’s famous TED talks and other speeches in that it’s punchy, full of interesting stories, has some attempted basis in scientific fact like Gladwell, and wanders around a bit.  That said, I enjoyed the book, and it hit on a number of themes in which I am a big believer – and it extended and shaped my view on a couple of them.

Sinek’s central concept in the book is the Circle of Safety, which is his way of saying that when people feel safe, they are at their best and healthiest.  Applied to workplaces, this isn’t far off from Lencioni’s concept of the trust foundational layer in his outstanding book, Five Dysfunctions of a Team.  His stories and examples about the kinds of things that create a Circle of Safety at work (and the kinds of things that destroy them) were very poignant.  Some of his points about how leaders set the tone and “eat last,” both literally and figuratively, are solid.  But his most interesting vignettes are the ones about how spending time face-to-face in person with people as opposed to virtually are incredibly important aspects of creating trust and bringing humanity to leadership.

My favorite one-liner from the book, which builds on the above point and extends it to a corporate philosophy of people first, customer second, shareholders third (which I have espoused at Return Path for almost 15 years now) is

Customers will never love a company unless employees love it first.

A couple of Sinek’s speeches that are worth watching are the one based on this book, also called Leaders Eat Last, and a much shorter one called How Great Leaders Inspire Action.

Bottom line:  this is a rambly book, but the nuggets of wisdom in it are probably worth the exercise of having to find them and figure out how to connect them (or not connect them).

Thanks to my fellow NYC CEO Seth Besmertnik for giving me this book as well as the links to Sinek’s speeches.