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:  Vulnerability Applied to Leadership

Getting Naked:  A Business Fable About Shedding The Three Fears That Sabotage Client Loyalty (book, Kindle), is Patrick Lencion’s latest fable-on-the-go book, and it’s as good a read as all of his books (see list of the ones I’ve read and reviewed at the end of the post).

The book talks about the power of vulnerability as a character trait for those who provide service to clients in that they are rewarded with levels of client loyalty and intimacy.  Besides cringing as I remembered my own personal experience as an overpaid and underqualified 21 year old analyst at how ridiculous some aspects of the management consulting industry are…the book really made me think.  The challenge to the conventional wisdom of “never letting ‘em see you sweat” (we *think* vulnerability will hurt success, we *confuse* competence with ego, etc.) is powerful.  And although vulnerability is often uncomfortable, I believe Lencioni is 100% right – and more than he thinks.

First, the basic premise of the book is that consultants have three fears they need to overcome to achieve nirvana – those fears and the mitigation tactics are:

1. Fear of losing the business:  mitigate by always consulting instead of selling, giving away the business, telling the kind truth, and directly addressing elephants in the room
2. Fear of being embarrassed:  mitigate by asking dumb questions, making dumb suggestions, and celebrating your mistakes
3. Fear of feeling inferior:  mitigate by taking a bullet for the client, making everything about the client, honoring the client’s work, and doing your share of the dirty work

But to my point about Lencioni being more right than he thinks…I’d like to extend the premise around vulnerability as a key to success beyond the world of consulting and client service into the world of leadership.  Think about some of the language above applied to leading an organization or a team:

• Telling the kind truth and directly addressing elephants in the room:  If you’re not going to do this, who is?  There is no place at the top of an organization or team for conflict avoidance
• Asking dumb questions:  How else do you learn what’s going on in your organization?  How else can you get people talking instead of listening?
• Making dumb suggestions:  I’d refer to this more as “bringing an outside/higher level perspective to the dialog.”  You never know when one of your seemingly dumb suggestions will connect the dots for your team in a way that they haven’t done yet on their own (e.g., the suggestions might not be so dumb after all)
• Celebrating your mistakes:  We’re all human.  And as a leader, some of your people may build you up in their mind beyond what’s real and reasonable.  Set a good example by noting when you’re wrong, noting your learnings, and not making the same mistake twice
• Taking a bullet for your team, making everything about your team and honoring your team’s work:  Management 101.  Give credit out liberally.  Take the blame for team failings.
• Doing your share of the dirty work:  An underreported quality of good leaders.  Change the big heavy bottle on the water cooler.  Wipe down the coffee machine.  Order the pizza or push the beer cart around yourself.  Again, we’re all human, leaders aren’t above doing their share to keep the community of the organization safe, fun, clean, well fed, etc.

There’s a really powerful message here.  I hope this review at least scratches the surface of it.

The full book series roundup as far as OnlyOnce has gotten so far is:

• The Three Signs of a Miserable Job (post, book)
• The Five Temptations of a CEO (post, book)
• The Four Obsessions of an Extraordinary Executive (post, book)
• Death by Meeting (post, book)
• The Five Dysfunctions of a Team (post, book, Field Guide)
• Silos, Politics and Turf Wars (post, book)
• Getting Naked (post, book)

How to Get Laid Off – an Employee’s Perspective

One of my colleagues at Return Path  saw my post about How to Quit Your Job about 5 years ago and was inspired to share this story with me.  Don’t read anything into this post, team!  There is no other meaning behind my posting it at this time, or any time, other than thinking it’s a very good way of approaching a very difficult situation, especially coming from an employee.

In 2009 I was working at a software security start up in the Silicon Valley.  Times were exceedingly tough, there were several rounds of layoffs that year, and in May I was finally on the list. I was informed on a Tuesday that my last day was that Friday.  It was a horrible time to be without a job (and benefits), there was almost no hiring at all that year, one of the worst economic down turns on record.  While it was a hard message,  I knew that it was not personal, I was just caught up on a bad math problem.

After calling home to share the bad news, I went back to my desk and kept working. I had never been laid off and was not sure what to do, but I was pretty sure I would have plenty of free time in the short term, so I set about figuring out  how to wrap things up there.  Later that day the founder of the company came by, asked why I had not gone home, and I replied that I would be fine with working till the end of the week if he was okay with it.  He thanked me.

Later that week, in a meeting where we reviewed and prioritized the projects I was working on, we discussed who would take on the top three that were quite important to the future of the company.  A few names were mentioned of who could keep them alive, but they were people who I knew would not focus on them at all.  So I suggested they have me continue to work on them, that got an funny look but when he thought about it , it made sense, they could 1099 me one day a week.  The next day we set it up.  I made more money than I could of on unemployment, but even better I kept my laptop and work email, so I looked employed which paid off later. 

That one day later became two days and then three, however, I eventually found other full time work in 2010.  Layoffs are hard,  but it is not a time to burn bridges.   In fact  one of the execs of that company is a reference and has offered me other opportunities for employment.

Book Short:  Choose Voice!

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

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

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

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

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

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

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

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

Book Short:  Awesome Title, So-So Book

Strategy and the Fat Smoker (book, Kindle), by David Maister, was a book that had me completely riveted in the first few chapters, then completely lost me for the rest.  That was a shame.  It might be worth reading it just for the beginning, though I’m not sure I can wholeheartedly recommend the purchase just for that.

The concept (as well as the title) is fantastic.  As the author says in the first words of the introduction:

We often (or even usually) know what we should be doing in both personal and professional life.  We also know why we should be doing it and (often) how to do it.  Figuring all that out is not too difficult.  What is very hard is actually doing what you know to be good for you in the long-run, in spite of short-run temptations.  The same is true for organizations.

The diagnosis is clear, which is as true for organizations as it is for fat people, smokers, fat smokers, etc.  The hard work (pain) is near-term, and the rewards (gain) are off in the future, without an obvious or visible correlation.  As someone who has had major up and down swings in weight for decades, I totally relate to this.

But the concept that

the necessary outcome of strategic planning is not analytical insight but resolve,

while accurate, is the equivalent of an entire book dedicated to the principle of “oh just shut up and do it already.”  The closest the author comes to answering the critical question of how to get “it” done is when he says

A large part of really bringing about strategic change is designing some new action or new system that visibly, inescapably, and irreversibly commits top management to the strategy.

Right.  That’s the same thing as saying that in order to lose weight, not only do you need to go on a diet and weigh yourself once in a while, but you need to make some major public declaration and have other people help hold you accountable, if by no other means than causing you to be embarrassed if you fail in your quest.

So all that is true, but unfortunately, the last 80% of the book, while peppered with moderately useful insights on management and leadership, felt largely divorced from the topic.  It all just left me wanting inspirational stories of organizations doing the equivalent of losing weight and quitting smoking before their heart attacks, frameworks of how to get there, and the like.  But those were almost nonexistent.  Maybe Strategy and the Fat Smoker works really well for consulting firms – that’s where a lot of the examples came from.  I find frequently that books written by consultants are fitting for that industry but harder to extrapolate from there to any business.

Book Short:  Multiplying Your Team’s Productivity

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

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

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

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

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

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

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

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

The Advantage: Why Organizational Health Trumps Everything Else In Business is Patrick Lencioni’s newest book.  Unlike most or all of his other books (see the end of this post for the listing), this one is not a fable, although his writing style remains very quick and accessible.

I liked this book a lot.  First, the beginning section is a bit of a recap of his Five Dysfunctions of a Team which I think was his best book.  And the ending section is a recap of his Death by Meeting, another really good one.  The middle sections of the book are just a great reminder of the basic building blocks of creating and communicating strategy and values – about driving alignment.

But the premise, as the subtitle indicates, is that maintaining organizational health is the most important thing you can do as a leader.  I tell our team at Return Path  all the time that our culture is a competitive advantage in many ways, some quantifiable, and others a little less tangible.

A telling point in the book is when Lencioni is relaying a conversation he had with the CEO of a client company who does run a healthy organization – he asked, “Why in the world don’t your competitors do any of this?” And the client responded, “You know, I honestly believe they think it’s beneath them.” Lencioni goes on to say, “In spite of its undeniable power, so many leaders struggle to embrace organizational health because they quietly believe they are too sophisticated, too busy, or too analytical to bother with it.”  And there you have it.  More examples of why “the soft stuff” is mission critical.

Lencioni’s “Recipe for Organizational Health” (the outline of the book):

–          Build a Cohesive Leadership Team

–          Create Clarity

–          Overcommunicate Clarity

–          Reinforce Clarity

And his recipe for creating a tight set of “mission/vision/values” (the middle of the book):

1. Why do we exist?

2. How do we behave?

3. What do we do?

4. How will we succeed?

5. What is most important, right now?

6. Who must do what?

While there are lots of other good frameworks for doing all of this, Lencioni’s models and books are great, simple reminders of one of the CEO’s most important leadership functions.  We’re recrafting our own mission and values statements at the moment at Return Path, and we’re doing it using this 6-Question framework instead of the classic “Mission/Vision/Values” framework popularized a few years back by Harvard Business Review.

The full book series roundup as far as OnlyOnce has gotten so far is:

• The Three Signs of a Miserable Job (post, book)
• The Five Temptations of a CEO (post, book)
• The Four Obsessions of an Extraordinary Executive (post, book)
• Death by Meeting (post, book)
• The Five Dysfunctions of a Team (post, book, Field Guide)
• Silos, Politics and Turf Wars (post, book)
• Getting Naked (post, book)
• The Advantage (book)

5 Ways to Get Your Staff on the Same Page

[This post first appeared as an article in Entrepreneur Magazine as part of a new series I’m publishing there in conjunction with my book, Startup CEO:  A Field Guide to Scaling Up Your Business]

When a major issue arises, is everybody at your company serving the same interests? Or is one person serving the engineering team, another person serving the sales team, one board member serving the VC fund, another serving the early-stage “angels” and another serving the CEO? If that’s the case, then your team is misaligned. No individual department’s interests are as important as the company’s.

To align everyone behind your company’s interests, you must first define and communicate those goals and needs. This requires five steps:

1. Define the mission. Be clear to everyone about where you’re going and how you’re going to get there (in keeping with your values).
2. Set annual priorities, goals, and targets. Turn the broader mission into something more concrete with prioritized goals and unambiguous success metrics.
3. Encourage bottom-up planning. You and your executive team need to set the major strategic goals for the company, but team members should design their own path to contribution. Just be sure that you or their managers check in with them to assure that they remain in synch with the company’s goals.
4. Facilitate the transparent flow of information and rigorous debate. To help people calibrate the success, or insufficiency, of their efforts, be transparent about how the organization is doing along the way. Your organization will make better decisions when everyone has what they need to have frank conversations and then make well-informed decisions.
5. Ensure that compensation supports alignment (or at least doesn’t fight it). As selfless as you want your employees to be, they’ll always prioritize their interests over the company’s. If those interests are aligned – especially when it comes to compensation – this reality of human nature simply won’t be a problem.

Taken in sequence, these steps are the formula for alignment. But if I had to single out one as the most important, it would be number 5: aligning individual incentives with companywide goals.

It’s always great to hear people say that they’d do their jobs even if they weren’t paid to, but the reality of post-lottery-jackpot job retention rates suggests otherwise. You, and every member of your team, “work” for pay. Whatever the details of your compensation plan, it’s crucial that it aligns your entire team behind the company’s best interests.

Don’t reward marketers for hitting marketing milestones while rewarding engineers to hit product milestones and back office personnel to keep the infrastructure humming. Reward everybody when the company hits its milestones.

The results of this system can be extraordinary:

• Department goals are in alignment with overall company goals. “Hitting product goals” shouldn’t matter unless those goals serve the overall health of your company. When every member of your executive team – including your CTO – is rewarded for the latter, it’s much easier to set goals as a company. There are no competing priorities: the only priority is serving the annual goals.
• Individual success metrics are in alignment with overall company success metrics. The one place where all companies probably have alignment between corporate and departmental goals is in sales. The success metrics that your sales team uses can’t be that far off from your overall goals for the company. With a unified incentive plan, you can bring every department into the same degree of alignment. Imagine your general counsel asking for less extraneous legal review in order to cut costs
• Resource allocation serves the company, rather than individual silos. If a department with its own compensation plan hits its (unique) metrics early, members of that team have no incentive to pitch in elsewhere; their bonuses are secure. But if everyone’s incentive depends on the entire company’s performance, get ready to watch product leads offering to share developers, unprompted.

This approach can only be taken so far: I can’t imagine an incentive system that doesn’t reward salespeople for individual performance. And while everyone benefits when things go well, if your company misses its goals, nobody should have occasion to celebrate. Everybody gets dinged if the company doesn’t meet its goals, no matter how well they or their departments performed. It’s a tough pill to swallow, but it also important preventive medicine.

Book Short:  Unsung Heroes

If you like “entrepreneurship by analogy” books, you’ll like The Innovators:  The Engineering Pioneers Who Made America Modern, by David Billington.  I have to admit some bias here — Professor Billington was my favorite teacher and senior thesis advisor at Princeton (I almost majored in civil engineering because of him), and this book is one of a number he’s written that are outgrowths of his most popular courses at Princeton.  And while there’s no substitute for the length or energy of his lectures, the book works.

The book is basically a person-focused engineering history of America from 1776-1883.  Billington talks about four classes of engineering product:  public structures (mostly bridges), machines that produced power, networks like the railroads and telegraphs, and processes like steel manufacturing.

His approach is to acknowledge that the Americans innovators couldn’t do much without the right context:  learnings from their counterparts in Britain, a supportive government here at home, and abundant raw materials and capital.  But with that backdrop in place, Billington tells the tale of a number of the inventions that built our modern society with a focus on the engineers who got things right.  While some of them are familiar names (Morse, Edison), many are not (Thomas Telford, J. Edgar Thomson, Joseph Henry).

Sound familiar?  It feels at many point in the book that you could insert some different names and dates and be reading a history of the Internet or information age.  And as with the Industrial Revolution, while many of the innovators in our world today are known (Bezos, Yang, Brin/Page), there are probably an equal number who are unsung heroes — either software engineers or even buisness model pioneers who haven’t sought or won’t end up in the spotlight even though their contributions to society or to their companies are giant.  I know there are a number of unsung heroes in our own engineering department at Return Path — people who aren’t market facing and who never get quoted in press releases, but who really make a difference in how the company works and how competitive we are.  This book celebrates those people as much as it does the entrepreneurs you’ve heard of.

Warning, there are lots of pages which are full of mathematical formulas, which may or may not be interesting to you, but the book still holds together 100% if you skip over them.

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.